Get started

Set up your emulator

The four settings Evonex needs in every emulator: size, dpi, ADB and English.

Size

540 × 960, portrait (width 540, height 960).

DPI

120.

ADB

On — it lets Evonex see the screen and tap.

Game

Evony installed, signed in, and set to English.

Evonex finds MuMu Player, LDPlayer, MEmu and BlueStacks by itself. Whichever you use, it needs the same four things. Set them once per emulator window, then restart that window — most emulators only change size on a restart.

MuMu Player (recommended)

1. Open the emulator’s Settings ▸ Display ▸ Resolution ▸ Custom: width 540, height 960, DPI 120.
2. In Settings ▸ Developer options, switch on ADB debug with local connection.
3. Save and restart the emulator. Open Evony and sign in.

MuMu’s first window answers at 127.0.0.1:16384, the next at 16416, then 16448 — Evonex knows this, so you rarely type it.

LDPlayer

1. Settings ▸ Display ▸ Resolution ▸ Customize: 540 × 960, DPI 120. Leave Force landscape mode off. Save settings.
2. Settings ▸ Other settings ▸ ADB debugging ▸ Open local connection. Save settings.
3. Restart the window. LDPlayer ships with ADB off: if Evonex starts the window itself, it switches ADB on first.

MEmu

1. System settings ▸ Display ▸ Resolution ▸ Customize: width 540, height 960, DPI 120. Leave Forced landscape off.
2. MEmu has no ADB switch — ADB is always on.
3. Restart the window.

BlueStacks

1. Settings ▸ Display: a custom size of 540 × 960, portrait, and 120 dpi.
2. Settings ▸ Advanced ▸ Android Debug Bridge: switch it on. The address is printed under the switch.
3. Restart the window. BlueStacks picks a new port each time it starts; Evonex reads it again at every Start when the instance is linked.

Good to know

• Graphics renderer. DirectX is a safe choice everywhere. On MuMu, DirectX and Vulkan draw the game identically, so either works.
• Frame rate. The bot reads the screen the same at 30 frames a second. With many instances on one PC, 30 or lower takes less from your PC.
• Small emulators. An emulator set to 1 CPU core or 1.5 GB of memory or less gets twice the waiting time on every screen, so it doesn’t rush ahead of the game.
• One window per account. An instance drives one emulator window. Two instances may point at the same window, but only one can run at a time.
• Other emulators work only if you type their address yourself (By port when you add an instance) and they meet the same four settings.

How Evonex checks it

At every Start, Evonex connects to the emulator, opens it first if the instance is linked and the window is closed, and checks the screen size. A freshly started emulator can take a moment to turn upright, so it looks again for up to 30 seconds before it refuses. A refused start shows the instance as Error with the reason:

123412341234

1. 1Ready Stopped, and its emulator answers — ready to start.
2. 2Offline Nothing answers at its address: the emulator is closed, ADB is off, or the address is wrong.
3. 3No emulator It has no emulator yet — link one in its Settings.
4. 4Error The last Start was refused; the line under it says why — here, the emulator isn’t at 540 × 960.

Problems?