Troubleshooting
Troubleshooting
A named cause for the common failures — and where to fix each one.
Most "it isn't working" moments have a named cause, and Evonex tries to surface the biggest ones for you rather than fail silently. Work this list top to bottom — start with the readiness check, then the usual suspects below.
Start with the readiness check
Open the instance's workspace. If anything needs setting up, a Needs setup card lists it — one row per problem, each with a coloured dot (red = a blocker that stops the run, orange = a warning) 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 gate opens listing every blocker (then any warnings). It offers Open setup (jump to the first fix), Start anyway, and Cancel.
Wrong resolution
Every template and tap position is authored against one display, so the runner refuses any other size rather than tap blindly. When it does, the reason reads:
Fix it in the emulator's own display settings (portrait 540 × 960, 120 dpi), restart the emulator so the new size takes effect, then Start again. See Emulator setup for where each emulator hides that setting. This is the single most common setup mistake.
Can't connect to the emulator
If the address is set but the emulator can't be reached, the start fails with:
- Emulator not running — launch it and make sure the game is open and logged in.
- ADB switched off — every emulator has an ADB / "local connection" toggle; LDPlayer in particular ships with it disabled. Turn it on (see Emulator setup).
- Wrong address — open the emulator's ADB setting and use the exact host:port it shows; correct it in the instance's settings.
A step can't find its target
When the bot can't locate something it expects on screen, the recognition art usually drifted — a game update changed a button or layout. Open the affected detector in the Vision Lab, capture fresh sources, re-crop or re-tune the match, and save. Because flows reference detectors by name, the fix propagates to every task that uses it — you tune once, not per task.
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, re-open Scan Generals and rescan the account (OCR 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 — if one is missing, rescan it or set its region in Edit general on the Generals page. One scan covers both the detail portrait and the smaller list tiles.
A task never runs
Check, in order: is the task's enable toggle on in the Plan? Is the instance actually started (running, not paused or stopped)? Then look at which band the row sits in and what its trigger is:
- BACKGROUND — the single task that runs continuously; other activities fill its gaps.
- SCHEDULED — runs on its own schedule, so it waits for its trigger (a daily-at-reset task won't fire until reset; an every-N-minutes task waits out the interval).
- QUEUE — no schedule set, so it runs once per session in order; once done it waits for the next Start.
Where the logs live
Everything the bot does is logged. Open Settings → Logs: pick a From / To window and an Instance (or All instances (combined log)) and click Export… to write that slice to a file for analysing a problem or sharing a report. Open logs folder opens the raw log directory, where a combined evonex.log sits alongside one file per instance.
Can't find it? Search the guide
Every page in this manual is searchable — type in the search box at the top of the left rail. 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.