OSBot Is Closing. Your Scripts Go With It. | Botting Hub
OSRS bot clients · 2026

OSBot is closing.
Here is what to do with your accounts.

OSBot shutdown · OSBot alternative · OSRS bot client wind-down

The store has stopped taking payments. Subscriptions will run to the end of their billing period and then stop. After that, OSBot winds down. The forum is already returning errors.

We wrote in August that OSBot was still up, and that this was not the same as safe. This is the follow-up nobody especially wanted. We are a competitor, so treat the analysis below as interested rather than neutral — but the notice is OSBot's own words, and you can read it yourself on their front page.

Excellent on Trustpilot We play the official client Still trading in 2026
01 The notice

In their own words.

This went up on osbot.org. We are quoting it in full rather than summarising it, because the details matter and because it deserves to be read as written.

Dear OSBot users,

Our store is no longer accepting new payments. All active subscriptions will end once their current billing period concludes. Once existing purchases and subscriptions fully expire, OSBot will be winding down.

Thank you for everything. It’s meant more than I can say.

Discord will remain open as somewhere you can come hang out and chat!

— Maldesto and the OSBot Team

OSBot ran for the better part of fifteen years. Whatever you think of the architecture — and we have been blunt about the architecture — a lot of people learned to script there, and the team is closing it with more grace than most. That is worth saying before anything else.

The forum is already intermittently unavailable, returning server errors rather than pages. Whether that is deliberate or simply what happens when a service stops being maintained, the practical effect is the same: the archive you relied on for script support is not something to count on any more.

02 Why this was coming

The date was never
the surprise.

On 28 January 2026 Jagex discontinued the Legacy Java Client as a standalone option, describing it as part of their effort to reduce “illicit activity such as botting”. RuneLite and HDOS were explicitly unaffected. The client that bots injected into was not.

RuneMate, DreamBot, TriBot and PowBot all built on that surface and all came off the board. OSBot did something harder: rather than close, they rewrote the client from scratch. We said at the time that this was a serious piece of engineering and worth acknowledging, and we meant it.

It also meant carrying the cost of a brand-new product on the revenue of a shrinking one, in a market where the thing you are selling keeps getting harder to sell. That is a difficult position to hold, and it is the position that ends here. The full technical background is in native versus injection.

03 What it means for you

There is no shutdown date.
That is the problem.

The notice ties the ending to when subscriptions expire, not to a day on the calendar. So you cannot plan around a deadline — you have to plan around not having one.

What you have
What happens to it
Your subscriptiontime-boxed
Runs to the end of the current billing period, then stops. You cannot renew — the store has stopped taking payments.
Your scriptsthe real loss
Anything bought on the OSBot SDN stops being something you can re-download or get fixed. Scripts do not survive the platform they were sold on.
Script supportalready thin
Authors move on before platforms do. With the forum unreliable and payments closed, expect updates to stop well before the lights go out.
Your accountsunaffected, for now
Nothing about a client closing puts a ban on your account. What matters is what you were running, and for how long, on what connection.
Your proxiesworth re-checking
If you were running the rewritten client without proxy support, your farm has been sharing one IP. That is worth fixing wherever you land next.

None of this is urgent in the next hour. All of it is urgent before your billing period ends, because that is the point at which you stop having a choice about when to move.

04 Moving

Gradually,
not all at once.

The instinct when a client closes is to move the whole farm in a weekend. Do not. A farm that changes every variable on the same day is a farm you cannot debug, and a pattern that looks like exactly what it is.

Take stock while the client still runs
Write down which scripts you actually use, which accounts run them, and what each one earns. Most people are running three things and paying for twelve.
Move one account first
Pick the one you would least mind losing, run it somewhere new for a week, and see what the logs and the bans look like before committing anything else.
Give each account its own IP
Whatever you move to, this is the part people skip and then blame the client for. One connection running a dozen identical accounts is a pattern no software can hide.
Ask what the client attaches to
This is the question that separated the clients that closed from the ones that did not. If the answer is “it injects into the game”, you are buying into the same problem again with a different logo on it.

We are an obvious answer to “where next”, and we would rather say so plainly than pretend to be a neutral guide. Botting Hub plays the official client — nothing injected, nothing hooked, no game memory read. The bot reads the screen and moves the mouse, which is why the January change did not touch us. That is a genuine architectural difference and it is also, transparently, a sales pitch. Check it before you believe it.

Open and trading · August 2026

We are online, and we are not on a billing clock.

The thing that ends OSBot for you is a subscription running out. That is worth naming as a difference, because ours cannot run out.

Nothing attaches to the game

We run the official client and read the screen. There is no modified client for anti-cheat to find, which is why January removed our competitors and not us.

Pay once, keep it

One-time purchase per instance, updates included, no renewal date. If we ever went the way OSBot has, you would not lose access on a billing cycle.

Proxy support, per account

Each account gets its own IP. If you have been running a farm off one connection because the client had no proxy support, this is the first thing to fix.

Start with one account. Judge it on a week of logs, not on this page.

FAQ The obvious questions

Straight
answers.

Updated

Is OSBot shut down right now?
Not completely. The store has stopped accepting payments and the wind-down begins once existing subscriptions expire. The forum is already returning errors intermittently. So it is closing rather than closed — but there is nothing left to buy.
When exactly does it stop working?
No date was given. The notice ties it to subscriptions expiring, which means different users will lose access at different times. If you want a date to plan around, use the end of your own billing period.
Will I get a refund for time I paid for?
The notice says active subscriptions run to the end of their current billing period, which reads as serving out what you paid for rather than refunding it. Nothing is said about SDN script purchases. If you want certainty on your own account, ask them — the Discord is staying open.
Can I keep the scripts I bought?
Realistically, no. Scripts sold through a platform's own network stop being downloadable, updatable and supportable when that network goes. This is the part that costs regular users the most, and it is the argument for not concentrating everything on one platform again.
Does OSBot closing put my account at risk?
A client shutting down does not retroactively flag anything. What carries risk is what was running and how — session lengths, how many accounts shared one connection, and whether the software attached itself to the game. Closing changes none of that in either direction.
Why did the injection clients all go and not the others?
Because injection leaves something attached to the game that should not be there. Anti-cheat does not have to infer anything from your mouse when there is a modified client in front of it — the client itself is the evidence. Removing the Legacy Java Client removed the thing they attached to.
You are a competitor. Why should I trust this page?
You should not, on its own. The notice is quoted verbatim and is on osbot.org where you can read it. The January client change is documented by Jagex. The architecture argument is one you can check against any client's own description of how it works. We have an obvious interest in you moving here — that is a reason to verify, not a reason to assume the facts are wrong.
What should I actually do this week?
Check when your billing period ends, list the scripts you genuinely use, and move one account somewhere else to test. Do not migrate a whole farm in one go, and give each account its own IP wherever it lands.

Your subscription has an end date.
Your next one should not.

Botting Hub is open, trading and running on the official client. Move one account across, give it a week, and decide from the logs.

Pay once · lifetime access · free updates · no renewal date