Guide
Why your new farm accounts never leave castle level 1
If you have added fresh accounts to a bot and watched them do nothing for a week, this is why — and it isn't your settings.
The symptom
You create a batch of new accounts, point your automation at them, and come back days later to find them exactly where you left them. Castle level 1 or 2. No buildings queued. No quests completed. Meanwhile an older account on identical settings is running normally.
The usual response is to blame settings, then the proxy, then the emulator. It is none of those.
What is actually happening
Lords Mobile drives early progression through a tutorial system: a table that maps each tutorial step to the routine that performs it. Building a defence tower, discovering the first PvE stage, the first rename — each is an entry in that table.
On a fresh account, that table comes up empty. Not incomplete — empty. The routines themselves all exist and all work correctly the moment something calls them. Nothing calls them, because the lookup that would dispatch them has no entries.
The result is an account whose task loop sits idle indefinitely. It isn't crashed and it isn't erroring. It is waiting for instructions that never arrive.
Why most bots never fixed it
Because it doesn't show up until you run accounts at volume. One or two accounts get tapped through onboarding by hand in a few minutes and nobody notices there was a problem. At fifty accounts, manual onboarding is the entire job, and the failure becomes the single thing standing between you and a working fleet.
How Apex handles it
Apex rebuilds the dispatch table the first time it sees an account — all 83 bindable steps, wired to the routines that were there the whole time. It runs once per account, automatically, with no configuration.
Verified on accounts that had been sitting idle indefinitely: they resumed on their own and progressed to real castle levels with zero manual taps.
The related failure worth knowing about
The same class of problem shows up on established accounts as a step that retries forever — a build ordered onto a blocked tile, for instance, where the routine has no fallback. Apex watches for a step that hasn't moved while castle level also hasn't changed, and restarts that one account. The recovery behaviour is described here.
Stop watching your bots. Start running a fleet.
Windows desktop. Your accounts stay on your machine. Cancel whenever it stops earning its keep.