Features
Every Lords Mobile automation, and the part that keeps them running
The automation list below is table stakes — most tools have some version of it. What decides whether a fleet actually earns is the recovery behaviour underneath, so that gets equal billing here.
Automation
What Apex runs while you're not looking
Table stakes, listed honestly. Everything below works today — nothing here is on a roadmap.
Resources
- Auto gather by resource type and tile level
- Guild bank deposits and transfers
- Cargo ship runs
- Treasure trove and VIP chest collection
Growth
- Building queue and upgrades
- Research queue
- Troop training and healing
- Turf, admin and guild quests
Combat
- Monster hunting by level and energy floor
- Darknest rally-fill on a /rally guild-chat command
- Shelter and shield management
- Hero stages and Colosseum
Operations
- Tag grouping across the whole fleet
- Per-account SOCKS proxy
- Start, stop and reload any account from the console
- Settings changes applied without restarting the account
What makes Apex different
It notices when something breaks, and fixes it
Not a marketing word. Three specific, verifiable behaviours that exist because running a fleet at scale surfaced these exact failures.
Stalled accounts restart themselves
A bot that silently stops is worse than one that crashes — you only notice days later. Apex watches every account's current step and its castle level together. If the step hasn't moved and the level hasn't changed, that one account restarts. Three attempts, then it's flagged for you instead of looping forever.
Corroborated against real progress, not just an idle screen — an account waiting on resources is not a stuck account.
New accounts actually progress
Fresh Lords Mobile accounts ship with an empty tutorial action table. The handlers all exist, but nothing ever dispatches them, so the account sits at castle level 1 forever no matter which bot you point at it. Apex rebuilds that table on first sight — 83 steps, bound automatically.
Verified on accounts that had been idle indefinitely: they resumed and reached castle 30 with zero manual taps.
Settings apply without a restart
Most tools load an account's settings once at launch, so changing anything means restarting the account and losing whatever it was mid-way through. Apex calls the reload directly inside the running process. The change takes effect on the next cycle.
No mouse macros, no window focus, no coordinate calibration.
The console
Your whole operation on one screen
Accounts grouped the way you actually think about them — farms, banks, mains — with the numbers that matter totalled across the fleet instead of buried one account deep.
Apex — Fleet
| Account | Status | Castle | Might | Current step |
|---|---|---|---|---|
| Banks | ||||
| AXP-Bank-01 | Running | 25 | 4.21M | Guild bank deposit |
| AXP-Bank-02 | Running | 25 | 3.98M | Cargo ship |
| Farms | ||||
| AXP-Farm-14 | Running | 17 | 812K | Gathering — stone L5 |
| AXP-Farm-15 | Recovering | 9 | 104K | Restarted — step stalled |
| AXP-Farm-16 | Running | 16 | 744K | Monster hunt — L4 |
| Mains | ||||
| AXP-Main | Stopped | 35 | 128M | Stopped by operator |
Food
0.0M
Stone
0.0M
Timber
0.0M
Ore
0.0M
Tag grouping
Group by role, not by import order. Collapse what you're not looking at.
Aggregate resources
Fleet-wide totals, so you can tell whether last night was good without opening anything.
Direct control
Start, stop or reload any account — or a whole tag — from the same screen.
Stop watching your bots. Start running a fleet.
Windows desktop. Your accounts stay on your machine. Cancel whenever it stops earning its keep.