What OSRS botting actually means in 2026
A plain explanation of OSRS botting, why people do it, the client methods in use now, what modern scripts can handle, and where the ban risk sits.
Botting means using software to play an OSRS account for you. That can be an autoclicker repeating one input, a script training a single skill or a manager launching hundreds of accounts onto different tasks.
It is against Jagex's rules. It is not illegal in the ordinary sense, but Jagex can lock or ban the account. If you bot for long enough, assume you will lose accounts. Anyone selling "undetectable" scripts is selling the word, not a guarantee.
Why people bot OSRS
Some people want to skip a grind they hate. A PKer may want the quests and stats without spending weeks building another pure. Somebody else only wants extra GP for their main.
There is also a programming side. OSRS is a useful sandbox for learning state machines, pathfinding and UI automation because the result is visible. You can watch a bad script get stuck on a gate and know exactly which part of the logic failed.
Then there are farms. I started with a few accounts doing whatever experiment looked funny that week. By 2025 my dedicated servers were running a combined 2,000 accounts at once. At that scale the script is only one piece. Account supply, proxies, launches, updates, mules and replacement cost become the actual work.
| Reason | Typical scale | What usually limits it |
|---|---|---|
| Skip a grind | One account | Ban risk on an account the owner cares about |
| Side GP | Two to five accounts | Time spent checking clients and selling output |
| Write and test scripts | One to ten test accounts | Bugs, game updates and account supply |
| Run a farm | Tens to thousands | Launch management, proxies, bans and cash flow |
What a bot client does
A bot client gives scripts a way to read the game and send inputs. The script decides what to do: find an NPC, check the inventory, bank, hop world or stop after a condition is met. The client supplies the hooks underneath it.
The main approaches you will hear about are:
- Injection: code is inserted into the game client so the bot can read and interact with its state.
- Reflection: the bot reads client values without modifying them in the same way as injection.
- Instrumentation: code is attached to a normal client or runtime and uses that client's state.
- Colour or vision: the bot works from pixels and sends ordinary-looking mouse and keyboard input.
- Mobile: Android automation, either through a modified client or screen input. iOS is much less common.
Those labels do not give you a ban rate. A bad colour bot can be obvious. A bad injection script can be obvious too. What the script does with the client matters more than the marketing category on the download page.
What modern scripts can handle
The gap between an autoclicker and a full script is huge now. Public SDNs have scripts that train multiple skills, buy supplies, use the GE, complete quests, swap methods and recover from common failures.
DreamBot's P2P Master AI is an example of a broad training script. Guester handles a long quest chain, including supply buying and Ironman routing. I used that sort of automation for my "Botting to Quest Cape" series because it shows the difference better than another woodcutting clip. The playlist is still on YouTube.
Do not confuse feature count with reliability. A script advertising 200 tasks has 200 places where an update can break it. Test the exact route and settings you plan to use.
Should you bot your main?
I would not. The ban is the obvious reason, but it also changes how you look at the account. Once a script can do a grind while you sleep, doing that same grind by hand starts to feel pointless. I have watched people lose interest in accounts they had played for years before the ban even arrived.
Use a separate account if the botting itself is the project. Treat the account as disposable, even if you intend to develop it. A temporary ban, lock or clean run does not change that assumption.
Botting makes more sense if you enjoy testing scripts, building systems or seeing how far a strange method can go. I once tried to max using only scripts I wrote myself and got to about 1,900 total before selling the account. That was fun because the system was the point.
What beginners underestimate
The client is the easy download. Beginners normally lose time on the parts around it: bad account formats, broken proxies, scripts left unattended before they have been tested and no record of which setup produced which ban.
Game updates also break clients and scripts. Do not assume a script is safe to restart because the client opens. Watch a disposable account first and check the script author's support thread.
You will lose configs. You will find a script clicking one object for an hour. Sometimes the method earns less than the account and proxy cost. Keep notes, start with a number of accounts you can actually watch and decide in advance what result would make you stop the test.
The beginner botting guide covers that operating side in more detail. If you want to try one client from a clean install, use the DreamBot setup guide. Accounts with the login format and build shown clearly are on the current stock page.