PowBot Mobile Beta: On-Device Install, a Bigger Humanizer, and a New IntelliJ Plugin

PowBot Mobile is getting one of its biggest updates yet, and it's rolling out on the beta channel this weekend. If you run PowBot Mobile — the OSRS mobile bot that works natively on Android — there's a lot here for you: a completely new way to install — right on the phone or emulator you play on — a major Humanizer pass, and, for script writers, a real IntelliJ plugin with run-and-debug built in. Here's everything that's new.

Install PowBot Mobile right on your device — no PC required

The biggest change is how you get PowBot running. The old PC-based powbot-installer is gone, replaced by a brand-new flow that installs PowBot directly on the phone or device you're going to play on, in just a few taps.

No computer, no cables, no separate setup software. You download it, tap through the steps, and you're ready to bot. For anyone who found the old desktop installer and ADB setup fiddly, this is a dramatically simpler path — and everything else in this update is built on top of it. Our new Install on Your Phone guide walks through the whole thing with screenshots for every step.

The new installer works on emulators too

The new on-device installer isn't limited to physical phones — it also runs on x86 and x86_64 Android emulators like BlueStacks and LDPlayer. If OSRS ever failed to start for you on an emulated device, that's fixed: the game now loads and runs there as well.

So whether you bot on a real handset or scale up across emulators on a desktop, you get the same few-taps install — set up however suits you, a phone, an emulator, or a mix of both.

A unique device on every install

Each install can now present a realistic device fingerprint, automatically matched to your Android version and kept consistent every time you update. The practical result: your bot looks like an ordinary phone, and no two installs look identical. You don't have to configure anything — it's handled for you.

A cleaner app and smoother updates

We rebuilt the dashboard and the install/patch screens around one clear action at a time:

One button that always knows what to do — Install, Update, or Play, depending on where you are.
Plain-language progress while patching ("Downloading game files…", "Building PowBot…") instead of a wall of technical log lines. Need the detail for a support request? It's one tap away under Show details.
Anything advanced is tucked out of the way until you actually want it.

Updates got a pass too. The patcher can now update itself, new releases are detected more reliably so you actually see them when they ship, and a bug that could corrupt a re-patch is fixed.

There's also a new "Report a bug" button right in the app. Describe what went wrong and it sends us the details we need to investigate — and if the app ever crashes, it can send that report automatically. Bug reports go straight to the author of the script you were running, so problems land with the right person fast.

A big Humanizer upgrade

We did a major pass on making PowBot behave more like a real player, focused on the things that actually shape natural-looking gameplay. The goal throughout: make the bot blend in without ever slowing your scripts down or interrupting them. It's on by default and needs no setup.

A few of the improvements:

Every account behaves a little differently. Each account now has its own subtle, consistent "personality" — the way it taps, drags, types, and pauses. A fleet of accounts no longer shares one tell-tale pattern.
More natural taps and clicks. No more landing on the exact same pixel over and over — taps now scatter naturally within their target, the minimap included.
More natural drags. Drags follow smooth, curved, human-like paths, and stay inside menus instead of accidentally closing them.
More natural timing. Pauses, reactions, and typing rhythm vary the way a person's do, and a gentle fatigue effect shifts your timing over a long session. Your scripts run at the same speed — only the shape of the timing changes.
More natural sessions. Accounts favour a small handful of "home" worlds, reconnect after problems with realistic, varied waits, and put the app in the background like a real person would when logged out on a break.

Script authors get three new optional calls to add even more realism at moments only they know are safe: Humanizer.reactionDelay() for a brief, human reaction-time pause, Humanizer.idleFidget() for a small idle action like glancing at a stat or examining an item, and Humanizer.glanceAtTarget() for a subtle camera nudge. They're completely opt-in and quietly do nothing when the moment isn't right.

A new IntelliJ plugin for script writers

Writing PowBot Mobile scripts now feels like normal app development. The new PowBot plugin for IntelliJ IDEA — see the Developing in IntelliJ guide to get set up — lets you:

Create a script project from a template. File → New → Project → PowBot Script sets up everything — build file, dependencies, and a sample script — so you're writing code in seconds. You can keep many scripts in one project, and it always pulls the latest SDK automatically.
Run and debug straight from the IDE. A Run/Debug button appears next to every script. Hit it and the plugin builds, uploads, and launches your script on a connected device, with live logs streamed into the IDE and a full debugger you can set breakpoints in. Multiple devices connected? You'll get a picker.
Triage your bug reports. A PowBot Reports panel shows the in-app reports players have submitted for your scripts, with device details and logs attached. Filter them, read the logs, and mark each one open, fixed, or ignored.

The SDK now also ships its API documentation built in. Once you pull the latest Gradle dependencies, you get inline docs throughout IntelliJ — hover any PowBot class or method, or hit Quick Documentation, and you'll see what it does, its parameters, and its return value without leaving your code. New projects from the wizard always pull the latest SDK, so the docs stay current.

Develop once, run everywhere on your LAN

Pushing a work-in-progress script to each device one at a time is tedious. The new local script library fixes that:

Run the small library app on your dev machine and point it at your script projects. It rebuilds them automatically whenever you save.
Every device on your network gets a new Library tab that automatically discovers your library and lists your scripts alongside the rest — no per-device uploading. Tap to run, on any device.
Devices only re-download a script when it has actually changed, and an optional PIN keeps your library private to you.

Dozens of API fixes

A new testing setup lets us reproduce the game's API on a plain dev machine — no phone or live game needed — which surfaced a pile of long-standing bugs. If you've been working around any of these, you can drop the workaround:

Inventory.isFull() could report a mostly-empty inventory as full — fixed.
Inventory.getNearestItems(id, id) could return the same slot twice instead of two distinct items — fixed.
Combat.style() now correctly reports DEFENSIVE while defensive autocasting (it used to look like ACCURATE).
Bank.withdrawModeQuantity(...) handles "placeholder" and "all but one" amounts correctly instead of misclicking.
Area now includes its full extent — the last row/column was being dropped, and a single-tile area didn't contain its own tile.
Scrolling (Widgets.scroll) no longer overshoots above the top of a scrollbar.
Filters and matchers no longer crash on a null candidate or an invalid regular expression.
Names with special characters (multi-byte characters, embedded tags) are read correctly instead of being mangled.
A batch of rare crashes around distances, skill lookups, health percentages, ground-item bounds, and menu dragging are all fixed, so scripts are noticeably more crash-resistant.
Magic spell data was corrected against the OSRS wiki — Fire Bolt, Water Surge, Bones to Peaches, Level-2 and Level-7 Enchant, and Watchtower Teleport now have the right level and rune requirements.

Behind all of this is that new testing harness, which means these kinds of bugs get caught before they reach you — and the 60+ open API reports finally have a home where we can verify fixes.

How to try the beta

Everything above is live on the beta channel now. To get it:

Open PowBot Mobile and switch to the beta channel, or grab it fresh from the download page — the Install on Your Phone guide covers a first-time setup end to end.
Don't have an account yet? Use the /register command in our Discord to get a registration token, then create your account. PowBot Mobile starts at $2/month with a free tier to try it out.
Pick something from the 190+ mobile scripts and hit Play.

Want to build your own? Follow the Developing in IntelliJ guide to install the plugin and SDK, and you'll be running a script on a connected device in minutes.

As always, the fastest way to report a problem or share feedback on the beta is the new in-app Report a bug button — or come find us in Discord. Thanks to everyone testing on the beta channel; your reports are exactly what shapes what we ship next.

The PowBot Team