Help
Troubleshooting
A named cause for the common failures — and where each one is fixed.
Most “it isn't working” moments have a named cause, and Evonex tries to show it rather than fail silently. Work this page top to bottom: start with the readiness check, then look for your problem below.
- Needs setup title + count chip
- A blocker row (red mark)
- A warning row (orange mark)
- Fix button
- Needs setup title + count chip
- A blocker row (red mark)
- A warning row (orange mark)
- Fix button
- Needs setup title + count chip
- A blocker row (red mark)
- A warning row (orange mark)
- Fix button
Start with the readiness check
Open the instance's workspace. If anything needs setting up before it can run, a Needs setup card lists it — one row per problem, each with a coloured mark (red = a blocker that stops the run, orange = a warning that won't) and a Fix button that jumps straight to the setting that clears it. A clean plan hides the card entirely, so if it isn't there, readiness isn't your problem.
Press Start while a blocker is unresolved and a Needs setup before starting window opens, listing every blocker (then any warnings), with up to three buttons — Cancel, Start anyway and Open setup (the highlighted one, which jumps to the first blocker).
The emulator is the wrong size, or won't answer
Every picture Evonex looks for is authored against one display, so it refuses any other size rather than tap blindly. When it does, the reason on the instance and in the start gate reads:
Fix it in the emulator's own display settings (540 × 960 portrait, 120 dpi), restart the emulator so the new size takes effect, then Start again. See Emulator setup for where each emulator keeps that setting — this is the single most common setup mistake.
If the address is set but nothing answers there, the start fails with:
- Emulator not running — open it, and make sure the game itself is open and signed in. An instance linked to its emulator opens it on Start by itself.
- ADB switched off — every emulator has an ADB / “local connection” toggle; LDPlayer ships with it off. Turn it on (see Emulator setup).
- Wrong address — open the emulator's own ADB setting and use the exact host:port it shows, then fix it on the instance's Settings.
The instance reads In use, and Start is greyed
Two instances can't share one emulator. When a second instance points at a port another running instance already drives, it reads In use and readiness refuses the start outright — shares device 127.0.0.1:5555 with “Northwatch”, which is already running — two instances can't drive one emulator — and it can't be forced past. Give each account its own emulator window and its own ADB port.
Needs setup, but nothing looks wrong
An instance with nothing switched on anywhere — no enabled task and no enabled duty — is refused outright: has nothing enabled to run — enable a task on Plan, or a duty on Duties, before starting. Turning on duties alone, with no plan task, is fine and doesn't trigger this — the Overview simply notes that only Duties will run.
If Solo names a task, that task's own switch has to be on too: is in Solo on “…”, but that task is switched off — nothing would run. Switch it on, or turn Solo off, on Duties.
A task or duty says it needs setup
A required field left empty reads needs “…” set before it can run — pick it in the task's setup (this duty's settings for a duty). A field that asks for one of several choices reads needs at least one of … set before it can run — pick one in the task's setup. Open the task's gear, or the duty's settings, and fill in what the message names — the Fix button on the Needs setup card jumps there directly.
A bundle row pointing at a sub-task removed in Studio reads has a plan entry for a sub-task that no longer exists — it would run nothing and still report success. Remove the entry, or re-add the sub-task in Studio. The entry is its row on Duties ▸ Tasks.
City or Coordex says it isn't ready
A task that walks to a building refuses to start until that building is mapped, naming the exact task, instance, building and city map — always in that order — for example “Patrol” on Northwatch can't run: “Walls” isn’t mapped yet in “Northwatch”. Open City Mapper to finish the map. Open the map in City Mapper and place the building with Map by hand, or run Auto map on it again. An instance with no map at all needs one made on its emulator, or one picked in its Settings ▸ City map.
A task bound to Coordex needs a board picked before it can run — needs a Coordex board picked in the task's setup before it can run — and, once picked, needs that board to actually hold live targets — has no live targets on board “…” yet — run a Coordex scan to feed it. The second one is a warning, not a blocker: it won't stop the instance starting, only that one task from finding anything yet. See Coordex.
A rally task won't march with the generals or troops you set
A march slot that names a General Preset or a troop type your library can no longer name reads as a needs-setup blocker on that task, naming exactly what went missing. Rescan the generals you dropped, or fill the missing row in Resources ▸ Troops, or set the slot back to the preset's own choice in the task's setup.
A general won't get picked
A task can only seat a general the vision system recognises. If a march or rally comes up short, reopen Scan Generals and rescan the account — text recognition can misread a name, or a new general was never scanned — then check the preset the task uses. Only generals that carry recognition art are preset-ready and appear when you build a lineup; one scan covers both the detail portrait and the smaller list tiles. See General Presets.
A step can't find what it's looking for
When the bot can't locate something it expects on screen, the recognition art usually drifted — a game update changed a button or a layout. Open the affected detector in the Vision Lab, capture fresh sources, re-crop or re-tune the match, and save. Flows reference detectors by name, so the fix reaches every task that uses it — tune once, not per task.
A task never runs
Check, in order: is the task switched on, on Duties ▸ Tasks? Is the instance actually started (running, not paused or stopped)? Then look at when it is allowed to run: Plan shows what is due and what runs next, and the task's Rhythm sheet — the gear on its row — holds its timing:
- A task that runs in the background — the one that keeps watching; everything else fills its gaps.
- How often — a task set to run once a day waits for its time, and an every-few-minutes task waits out its interval.
- Only when I run it — waits for you.
- When it may run — a task kept to set hours waits outside them.
Finding the logs
Everything the bot does is logged. Open Settings ▸ Logs: pick a range (or a custom From / To), pick a Scope (one instance, or every instance combined) and click Export… to write that window to a file for reading, or for sharing a report. Open folder opens the raw log directory, where a combined log sits alongside one file per instance. See Reading the interface.
Can't find it? Search the guide
Every page in this manual is searchable. It matches page titles, headings, and a generous set of hidden keywords — dialog titles, button labels and synonyms — so a page turns up even when you don't know its name. The FAQ is a shorter, more general companion to this page.