FAQ

MuMu Player is recommended — Evonex is built and tuned against it first, and it gives the steadiest screen capture. LDPlayer, MEmu and BlueStacks all work too, set up the same way: 540 × 960 portrait, 120 dpi, with ADB switched on. See Emulator setup.

As many as the PC can comfortably drive. Each instance needs its own emulator window and its own ADB address — two instances can never share one window. The Dashboard's This PC gives a rough estimate from this PC's memory and cores, and Add instances creates many at once from the emulators it finds. See Dashboard and Emulator setup ▸ “Several emulator windows”.

Yes. An instance is one account on one emulator window, and Evonex refuses to start a second instance pointed at a window another running instance is already using. Give every account its own window and its own address.

Whichever you like reading. Aurora, Prism and Standing Watch lay the app out differently, but they hold the same pages, controls and words, and the bot plays exactly the same. See Reading the interface.

Yes, but not at the same moment — Evony only plays on one device at a time, so opening the game on your phone kicks the emulator off it. With the instance's Shared device set to reclaim (the default), it waits out a short grace window, then reloads the game and takes it back, signing your phone out on its own. Turn that off if you'd rather take the game back yourself.

Evonex plays the way you would: it looks at the screen and taps and swipes — it never opens the game's files or memory and never asks for your login. Rest breaks pause an instance on a randomised work/rest cycle, with optional quiet hours — a sleep window on the days you pick — so a long run doesn't sit on one unbroken, machine-like rhythm. That said, automating any game account carries some risk under that game's own rules, and nothing can promise otherwise — pacing helps, it doesn't guarantee anything.

Every instance runs inside Evonex, so anything that stops Evonex — you closing the window, the PC restarting or losing power — stops every instance exactly where it stood. Nothing resumes on its own: reopen Evonex and press Start on each instance you want running again. Minimise the window, rather than closing it, to keep everything running.

Open the instance and read its status and, beside it, the reason. Offline means the emulator isn't answering — see Emulator setup. Needs setup means something in its setup is missing — open its Needs setup card and use the Fix button on each row. Error names what went wrong — fix that and press Start again. See Troubleshooting for the named causes.

Yes, as long as the PC stays on and Evonex stays open — a running instance needs no attention from you. It only runs on this PC; it is not a phone app and there's nothing to check in from elsewhere.

Yes. Switch on Reload after the daily reset in the instance's Settings ▸ Shared device: right after the server's daily reset it closes and reopens the game so events, the shop and daily quotas are fresh before today's daily tasks run — only while the bot is running at that time. Wait after reset (0 to 30 minutes, default 0) gives the server time to settle. It is off until you switch it on.

It can. Evonex finds things by looking at the screen, so when Evony changes a button, an icon or a layout, whatever depended on the old look can stop being recognised until it's re-captured. If a step suddenly can't find something right after an update, see Troubleshooting ▸ “A step can't find what it's looking for”.

How long the bot waits after each tap for the game to finish redrawing before it looks again — the same wait for every step of every task. Raise it on a slower PC if you see steps skipped or taps landing before a page has finished opening; lower it to make tasks quicker once you're sure the PC keeps up. It lives on the instance's Settings.

Yes — nothing about the account changes when Evonex isn't driving it. Play it on your phone or in the emulator as normal, and start the instance again whenever you want Evonex to take back over.

Each instance's Activity Monitor, on its Overview, lists every step as it happens. The Dashboard shows every instance's whole game day and today's runs across the fleet in one place, and Settings ▸ Logs exports a time window to a file. See Dashboard and Reading the interface.

Either — an instance is just one account on one emulator window, so it makes no difference whether two instances share a server or not. Coordex boards are set up per server and each account's city has its own city map, while General Presets and Troops are shared across every instance, so setting one account up makes the next one faster.