Start here
Welcome to Evonex
What Evonex is, how it drives the game, and the pieces you set up.
Evonex automates an Evony account running on an Android emulator. It plays the way you do: it looks at the screen to spot things and read the numbers and timers, then taps and swipes to act on what it saw. It never touches the game's files, its memory, or your account credentials — it only sees the same picture you see and taps the same places you would.
The building blocks
The app is a handful of pieces you set up once, then leave running. Each links to its own page in this guide:
- Instances — one instance is one game account on one emulator. Each has its own workspace and runs independently.
- The task plan — inside a workspace, the ordered list of what runs and when: gathering, rallies, daily activities, and more.
- Resources — game data shared by every instance: your generals and presets, the monster, champion, black-market and recruit lists, and troop costs.
- Task duties — the daily care each account needs: a bubble on the keep, buffs kept up, and the everyday activities.
- Studio — the task library, the Task Builder (author what the bot does as a visual flow, no code) and the Vision Lab (its eyes).
- City Mapper — map your city once per emulator so tasks can walk to the right buildings.
- Coordex — live world-map targets per server, feeding the rally tasks.
- Dashboard — the whole fleet at a glance: what's running, what's done today, and how this PC is holding up.
One rule above all: the display
Everything Evonex recognises — every image it matches and every spot it taps — is authored against one canonical display: 540 × 960 portrait at 120 dpi. The bot refuses to start on any other resolution rather than tap into the wrong places. A different DPI isn't blocked, but it draws on-screen elements at a different size from the templates, so matching turns unreliable — set both.