Five providers went dark in four days
If you run OSRS automation, the first week of July 2026 was hard to miss. Between 1 and 4 July, several of the biggest names in the space paused sales or shut down entirely.
The timeline:
- 1 July — PowBot stopped new subscriptions and renewals: "As of today it is no longer possible to purchase or renew PowBot subscriptions through the website. We have taken this decision as we work through some issues." Existing subscriptions kept running.
- 1 July — TRiBot disabled sales with no explanation: "Hey everyone, sales are unavailable right now. I'll let you know when I have more information."
- 4 July — Storm Client shut down permanently: "Storm is closing, effective immediate. Website and client are no longer usable." The developer announced automatic refunds for recent Stripe purchases.
- 4 July — Inubot paused token sales: "Token sales have been temporarily paused due to circumstances outside our control." Existing subscriptions valid until 3 August.
- OSMB never issued a public statement, but users reported it affected over the same window.
Four announcements in four days, from projects that don't share infrastructure, don't share developers, and compete directly with each other. That is not coincidence.
Nobody has said why — and it's worth being honest about that
None of the operators have explained what happened. Anyone telling you with confidence that they know is guessing.
What we can read is the shape of it. This doesn't look like an anti-cheat patch. When Jagex breaks a bot with a client update, the failure mode is a broken client and a scramble to ship a fix — sales stay open, because a broken feature doesn't stop you taking money. What happened here was the opposite: payment pages went down first, refunds went out, and the clients themselves mostly kept working.
Sales disabled, purchases refunded, subscriptions honored to expiry, "circumstances outside our control." That's the signature of commercial or financial pressure, not a technical one. Payment processors getting cautious, legal correspondence, or something else entirely — we don't know, and neither does anyone else outside those teams.
The distinction matters because it changes what you should learn from it. A patched detection vector is a problem for one bot's codebase. Pressure on the commercial layer is a problem for every provider that has a storefront.
This market has thinned out before
Jagex has a long track record of going after the business side of automation, not just the accounts running it.
The most direct precedent: on 2 October 2020, Jagex announced that "following legal proceedings, RSBot, and the Powerbot website, will be shut down, and permanently closed by midnight on 3rd October 2020". RSBot was one of the longest-running bots of its era. It didn't die because someone patched its reflection hooks — it died because the entity behind it lost a legal fight. Jagex framed it as continuous with their 2019 takedowns of the Arcus and Bogla gold-selling sites, and stated a zero-tolerance stance "both in and out of game, with bot users, developers and gold sellers."
The technical side has its own history of hard resets — Bot Nuking Day in 2011, the Java client retirement in January 2026 that killed injection and reflection bots outright. But those are different events with a different mechanism. Bot Nuking Day broke bots. The RSBot shutdown broke a company.
The pattern across the years is consistent. Jagex tolerates a great deal of noise from individual players. But when a bot becomes a visible commercial operation — a storefront, subscription tiers, a support forum, a customer base — it eventually tends to become a target. Legal action, trademark disputes, or simply enough sustained pressure that operators decide it isn't worth continuing.
None of this means every provider is in the crosshairs at once. It does mean this market periodically thins out its largest and most visible players, and July 2026 looks like one of those moments.
Three questions worth asking before you pick a replacement
If you were paying one of the providers that just went dark, you have a practical problem: choose something else, without repeating whatever just happened. Three questions do most of the work.
Does it require a modified or forked client? Every time the Old School client ecosystem shifts, tools built on non-standard clients break first. January's Java client retirement wiped out the entire injection and reflection category in a single day. Tools that run inside the client you already have — vanilla, approved, unmodified — have less surface area to be broken by a launcher change, a client update, or a hash check.
What happens to your access if the provider disappears tomorrow? A lot of people just found out, with no warning. Storm's users got refunds. Inubot's got a month of runway. Others got a sales page that stopped working and no statement at all. Ask what continuity actually looks like — where the plugin file lives, whether it keeps working if the website goes down, what you're left holding. That's a different question from what's on the feature list.
Is safety a paid add-on, or is it the baseline? If a provider sells antiban as a premium tier, they have told you how they think about your account: as an upsell surface, not as the thing the product exists to protect. Behavioral detection doesn't check your subscription tier. Botwatch analyzes the same telemetry whether you paid for the good mouse curves or not.
Where Pluginscape fits
We built Pluginscape on a boring premise: automation tooling should be stable and unexciting rather than clever and fragile.
Our plugins sideload into the RuneLite client you're already running. Not a fork, not a modified JAR, not a separate executable you have to trust — you download RuneLite from runelite.net like everyone else, and drop a plugin into it. There is no custom client for us to fail to maintain, and nothing to switch to. Antiban isn't a tier. It's on by default in every plugin we ship, because the alternative is charging you extra not to get banned.
We're not going to tell you any tool in this space is risk-free. Nobody honestly can, and providers who imply otherwise are selling you certainty they don't have. What we can do is be specific about what we've built and how it works, and let you judge it.
If you've been displaced by one of the recent shutdowns, take a look at what we ship. Vanilla RuneLite, antiban on by default, plugin files you keep.
Further reading: RuneLite vs custom clients in 2026 → · How Jagex actually detects bots →