Native clients vs
injection bots.
Updated
If you bot Old School RuneScape, the tool's architecture matters more than any marketing slogan. One approach modifies the game. The other plays the official client the way a person does. That difference is why one class of client kept getting detected in 2026 and the other did not.
Note: Botting Hub builds a native, vision-driven client, so we are not a neutral party here. This page describes how we think about the space — check the claims against the product docs rather than taking them on trust.
August 2026 note: several major public clients paused sales or announced shutdowns, RuneMate and DreamBot among them. That does not change the tradeoffs below — it just means there are fewer maintained public options. Dated snapshot: after the legacy clients.
Injection and hooked clients — the legacy pattern
Most older bot clients worked by attaching to a game client, historically the Java-based stack, and reading or controlling game state through hooks, reflection or similar techniques. The bot effectively lives inside the game process.
What it does well
- Mature script marketplaces and long-established communities
- Fine-grained access to game state, which makes complex scripts easier to write
Where it struggles
- The detection surface is tied to how the client is modified or hooked — there is something there to find
- It breaks when Jagex changes client technology; the shift away from Java hurt this whole class badly
- Behaviour can look too precise in ways real players never manage, unless heavily humanised
Native and vision-driven clients — the newer pattern
The newer approach runs the official game client, unmodified, and drives it from the outside using computer vision and input simulation. The software looks at the screen and moves the mouse and keyboard, roughly the way a person does. From the game's point of view it is the official client, because it is — there is no patched build, no attached process, nothing added to the game at all.
What it does well
- Runs the official client — nothing is injected, hooked, patched or attached, so the usual detection surface simply is not there
- Survives client updates that break injection stacks, because it never depended on their internals
- Easier to reason about — it is UI automation, not surgery on the game
Where it struggles
- Vision can fail on UI changes, latency or unusual resolutions, so it needs maintaining
- Script quality and account setup still matter — they are what is left once the technical tell is gone
Side by side
What Botting Hub does
Our client plays the official OSRS client. Nothing is injected, nothing is hooked, no game memory is read — it sees the screen and moves the mouse, and everything Jagex can observe is a real client doing real things. That is why our reported ban rates are low compared with injection-based tools, and it is a property of the architecture rather than a promise we are asking you to believe.
Around it sits account tooling, proxy support, a script store and a Python SDK for people who want to write their own routines.
The common technical reason accounts get flagged simply does not apply here — there is nothing added to the game to find.
How to choose, whoever you end up with
- Is the tool actively maintained after major Jagex client updates?
- Can you start on low-value accounts before anything that matters?
- Are pricing and support clear, without pressure tactics?
- Is there real documentation, or just “#1 undetectable” blog posts?
That last one is worth taking seriously in both directions. If a page leads with superlatives and ends with a coupon code, treat it as marketing — including when it is one of ours.