What the Bot Detector plugin actually is
The Bot Detector is a community-built RuneLite plugin distributed through the official RuneLite Plugin Hub. It's not a Jagex product — it was built and maintained by independent developers, though community posts suggest some degree of coordination with Jagex's anti-cheating team (unconfirmed).
The pipeline works like this:
- Data collection — the plugin uses RuneLite's API to observe nearby players: names, location, equipment worn, gear cost, and current activity
- Reporting — this data is sent (with the reporting player's name optionally anonymized) to a Python backend maintained by the project
- ML classification — classifiers trained on Jagex-labeled ban/not-ban data score each reported player
- Forwarding — high-confidence bot predictions are sent to Jagex's anti-cheating team
- Reinforcement — the model improves when Jagex confirms a ban or confirms a real player
The project reported raising its accuracy from approximately 80% to 90% between early 2021 and mid-2021. Because it's distributed through the official Plugin Hub, it complies with Jagex's third-party client rules — meaning it only reads observable game state, nothing from your local machine.
It's a legitimate, well-engineered community project doing genuinely interesting ML work. It also happens to have real consequences for automation users.
What data it actually collects
The plugin's feature set reveals exactly what signals it considers meaningful for classification:
- Player name — tracked for correlation across sightings and used for hiscore lookups
- Location — where the player is standing and what content area they're in
- Equipment worn — specific items equipped and their GE value
- Gear cost analysis — cheap, generic gear sets are a known bot signature. The OSRS Wiki specifically calls out combinations like Dragon med helm + Granite platebody + Abyssal whip + Anti-dragon shield as characteristic bot loadouts
- Skill stats via hiscores — "Stats Too Low" is an explicit ML prediction category, meaning accounts with lopsided skill distributions (one spiked skill, everything else at base level) flag harder
- Activity patterns — what the player is doing and how consistently they're doing it
What the plugin does not see: your mouse movements, your click timing, your client type, your IP address, or anything about your local machine. It operates purely on observable in-game state — the same information any player standing next to you could see by right-clicking your character and looking you up on the hiscores.
This distinction matters. The Bot Detector evaluates how you look, not how you play. Jagex's own server-side detection handles input analysis. These are two separate detection surfaces with different evasion strategies.
Does it actually get people banned?
Community reports consistently say yes. Multiple forum threads from experienced botters report that bots are being flagged and banned faster since the plugin became widely adopted. The mechanism is straightforward: the plugin provides Jagex with a prioritized list of accounts to review, effectively crowdsourcing the detection pipeline's first pass.
Important caveats from the plugin's own documentation:
- A single flag is not enough for a ban. The plugin's about page states this explicitly — one report from one user doesn't trigger anything
- Jagex makes the final decision. The plugin reports suspects; Jagex reviews them using its own detection systems before issuing a ban
- Classification isn't conviction. A bad score from the Bot Detector doesn't mean instant doom — but sustained high-confidence classification across many reports from many different plugin users accelerates review
The practical impact is volume-dependent. One player reporting you once is noise. Fifty different plugin users all reporting the same account doing the same activity for eight hours straight is a strong, consistent signal that moves your account up Jagex's review queue.
Where plugin users cluster
The Bot Detector is most useful — and most dangerous for bots — in popular, densely-populated botting hotspots:
- Motherlode Mine — high bot density meets high legitimate player density
- Wintertodt — hundreds of players in a single instance, many running the plugin
- Blast Furnace — concentrated, repetitive activity in a small area
- Rooftop agility courses — especially Seers' Village and Ardougne
- Popular fishing spots — Barbarian Village, Fishing Guild, Tempoross
- Sand Crabs / Ammonite Crabs — notorious for AFK combat bots
These are exactly the places where both bots and bot-detecting players concentrate. The plugin's value comes from volume — when dozens of independent users all report the same account exhibiting the same behavior over hours, the aggregated signal is hard to ignore.
Less populated worlds, unusual training locations, and off-meta spots receive significantly less Bot Detector coverage. A player at an obscure fishing spot on a 400-population world is far less likely to encounter a plugin user than someone at Motherlode Mine on world 303. This is a simple but effective factor in location and world choice.
The self-audit trick
The Bot Detector ecosystem includes a public account search tool that returns the ML system's current prediction for any account with public hiscores. Some automation users periodically look up their own accounts to check whether they've been classified as a likely bot.
This turns the plugin into a pre-ban early warning system. The possible classifications include predictions like "Real Player," "Bot," and "Real-World Trader" — each with a confidence score based on aggregated reports.
A bad score doesn't guarantee a ban. But a sustained high-confidence "Bot" or "Real-World Trader" classification across many independent reports is a signal to rest the account, vary activities, or change your approach before Jagex acts on the data.
One additional detail: running the Bot Detector plugin yourself with Anonymous Uploading enabled means you contribute to the detection network without uploading your own player name in the reporting data. Some users do this to participate in the community tool without exposing their own accounts in the dataset.
What this means for plugin design
The Bot Detector's feature set is a roadmap of what matters for in-game appearance — the signals that other players and their ML classifiers evaluate when they look at you:
Gear variety matters. Don't use the cheapest possible gear set. If your account has 20M in the bank but you're wearing a 50K loadout at Motherlode Mine, that mismatch is a signal. Wear varied, realistic equipment that matches your account's level and apparent wealth.
Skill distribution matters. Accounts with 90 Mining, 1 in every other skill, and 0 quest points are textbook bot profiles. The "Stats Too Low" classification exists specifically to catch this pattern. Mixed progression — multiple skills trained, some quests completed — looks dramatically more legitimate.
Location awareness matters. The most heavily monitored hotspots are the most dangerous places to automate. Off-peak hours and lower-population worlds reduce your exposure to plugin users, but the most effective mitigation is choosing locations where fewer players congregate in the first place.
Activity variation matters. Eight hours of identical activity in the same tile is exactly the pattern the Bot Detector is designed to catch. Rotating activities, rotating locations, and taking breaks that look like natural session boundaries break up the behavioral consistency that triggers classification.
These are all observable signals — things any player can see about your character. Plugin quality (mouse movement, click timing, input humanization) is invisible to the Bot Detector but matters for Jagex's own server-side analysis. They're complementary detection surfaces, and surviving both requires attention to both.
Another reason Pluginscape plugins include gear randomization options and support location variety — blending in isn't just about input patterns. How you look to other players matters too, because those other players might be running the Bot Detector.
Further reading: Anatomy of an OSRS ban wave → · How to minimize the risk of getting banned →