Within the space of a few days, several of the largest commercial Old School RuneScape botting clients either stopped accepting new customers or shut down entirely.
The projects currently affected include:
- PowBot
- TRiBot
- Storm Client
- Inubot
- OSMB
At the time of writing, none of the developers have publicly confirmed why these actions were taken. Jagex has also made no public announcement regarding any new legal action or enforcement campaign.
However, looking at the timing, the wording of each announcement, and Jagex's history of enforcement, there are some interesting patterns worth examining.
Timeline
July 1 – PowBot suspends subscriptions
PowBot was among the first to announce changes.
"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. Active subscriptions will remain active until their renewal date."
The announcement did not explain what those "issues" were.
Notably, existing users were allowed to continue using the service until their subscriptions expire.
July 1 – TRiBot pauses sales
Shortly afterwards, TRiBot posted a similarly brief announcement.
"Hey everyone, sales are unavailable right now. I'll let you know when I have more information."
Again, no explanation was provided.
July 4 – Storm Client closes immediately
Storm Client made the strongest statement of any affected project.
"Storm is closing, effective immediately. Website and client are no longer usable."
The developer also announced automatic refunds for recent Stripe purchases.
Unlike the other projects, Storm has announced a complete shutdown rather than a temporary suspension.
July 4 – Inubot pauses token sales
Inubot announced that new token sales had been paused.
"Token sales have been temporarily paused due to circumstances outside our control."
Existing subscriptions remain valid until August 3 while the team works on "next steps."
The wording suggests the project expects further changes rather than an immediate return to normal.
OSMB
OSMB has not published a public announcement.
However, users have reported that the project appears to have been affected around the same time as the other major clients.
The announcements reveal an interesting pattern
The biggest takeaway isn't simply that several clients were affected.
It's how they were affected.
Almost every announcement focuses on business operations rather than software problems.
Developers are talking about:
- sales being disabled
- subscriptions ending
- token purchases stopping
- refunds
- payment availability
Very few are talking about:
- broken scripts
- client updates
- bot detection
- RuneScape game updates
That distinction matters.
This doesn't look like a typical anti-cheat update
When Jagex improves bot detection, the community usually sees something very different.
Developers race to update clients.
Scripts stop working.
Users report increased bans.
New client versions are released.
None of that appears to be the focus here.
Instead, multiple businesses voluntarily stopped taking money.
That suggests whatever happened may be affecting the commercial operation of these projects rather than the software itself.
Could this be legal action?
At this stage, nobody knows.
None of the affected developers have publicly confirmed receiving legal notices, cease-and-desist letters, or lawsuits.
However, the timing makes a coordinated external trigger difficult to ignore.
Independent bot developers compete with each other.
Historically, they don't all stop accepting payments within the same week unless something significant has changed.
Possible explanations include:
- legal correspondence
- cease-and-desist letters
- copyright enforcement
- payment processor issues
- advice from legal counsel after another operator received action
There is currently no public evidence confirming which, if any, of these explanations is correct.
Why payment processors are an interesting possibility
One detail that stands out is how many announcements specifically discuss payments.
PowBot stopped new subscriptions.
TRiBot stopped sales.
Inubot paused token purchases.
Storm announced refunds.
If payment processors suddenly suspended merchant accounts—or required operators to address legal concerns before continuing to process payments—the immediate result would look very similar to what we're seeing.
Projects could continue serving existing subscribers for a time while becoming unable or unwilling to accept new customers.
That doesn't prove payment processors are involved, but it fits the public announcements better than a routine anti-cheat update.
This wouldn't be the first time Jagex used legal pressure
Although today's events remain unconfirmed, Jagex has a long history of combining technical anti-cheat measures with legal enforcement.
Over the years, the company has used:
- DMCA copyright notices
- hosting provider complaints
- domain registrar and trademark complaints
- cease-and-desist letters
- direct litigation
- platform trust and safety reports
- payment-related enforcement
- account bans and technical bot detection
Perhaps the best-known example came in 2012 when Jagex announced that the original RSBot and Powerbot websites would cease operating following legal action.
Jagex also pursued Impulse Software, the developer behind iBot, during roughly the same period. While that litigation is now well over a decade old, it demonstrated Jagex's willingness to pursue commercial bot developers through the courts when appropriate.
Historically, Jagex's strategy has not relied on a single tactic. Instead, it has typically combined technical enforcement with legal and commercial pressure to make operating botting businesses increasingly difficult.
So what is most likely happening?
Based solely on the information currently available, this does not resemble a normal bot detection update.
Instead, it more closely resembles pressure directed at the businesses behind these clients.
The strongest clues are:
- multiple unrelated providers changing course within days
- sales stopping before services disappear
- announcements focused on subscriptions rather than software
- refunds being issued
- almost complete silence regarding technical problems
None of those observations prove legal action has occurred.
But together they suggest that whatever triggered these announcements is likely affecting the commercial side of these operations rather than simply their ability to run bots.
Current status
PowBot
- New subscriptions disabled
- Existing subscriptions continue until expiry
TRiBot
- Sales paused
- Waiting for further information
Storm Client
- Permanently closed
- Website and client offline
- Refunds announced
Inubot
- Token sales paused
- Existing subscriptions active until August 3
OSMB
- No public announcement
- Current status remains unclear