Start here

Emulator setup

The display, the ADB switch and the address — where each emulator keeps them.

Evonex drives an Android emulator, so the emulator has to be set up for it first. Every emulator needs the same three things — the display at 540 × 960 portrait, 120 dpi, and its ADB connection switched on — it just keeps them in different menus. Find yours below. Each emulator window answers on its own address (host and port, such as 127.0.0.1:16448); Evonex finds the windows of MuMu Player, LDPlayer, MEmu and BlueStacks on its own and links each instance to its window.

123412341234

1. By port
2. Emulator (ADB) field
3. Addresses found
4. Refresh button

1. By port
2. Emulator (ADB) field
3. Addresses found
4. Refresh button

1. By port
2. Emulator (ADB) field
3. Addresses found
4. Refresh button

Set it up

1. Install the emulator and create one window (player) for each account you want to automate.
2. In each window, set the display to 540 × 960 in portrait at 120 dpi.
3. Switch on the window's ADB connection.
4. Restart the window so the new display size takes effect.
5. Install Evony, set the game's language to English, and sign in to the account.
6. In Evonex, add an instance for that window — see Create your first instance.

The settings every emulator needs

MuMu Player — recommended

1. Display — open Settings ▸ Display, set Resolution settings to Custom and enter Width 540, Height 960, DPI 120. MuMu starts in a landscape size — make sure it is the portrait 540 × 960.
2. ADB — go to Settings ▸ Developer options and set ADB debug to Enable local connection.
3. Renderer — under Performance ▸ Graphics renderer, choose DirectX.
4. Address — MuMu Player 12's first window is 127.0.0.1:16384; each further window adds 32 (16416, 16448 and so on). Evonex finds these on its own and always uses these ports for MuMu — a window may also answer on 5555, 5557 …, but BlueStacks takes ports there too, so Evonex never relies on them. A closed MuMu window is listed at the port it opens on. The older MuMu 6 is commonly 127.0.0.1:7555 — type that one in.

LDPlayer

1. Display — open Settings ▸ Display, set Resolution to Customize and enter Width 540, Height 960, DPI 120, then Save settings. Leave Force landscape mode off.
2. ADB — go to Settings ▸ Other settings, set ADB debugging to Open local connection, then Save settings.
3. Address — LDPlayer windows answer on 5555, 5557, 5559 and so on. Evonex finds them on its own and reaches them at 127.0.0.2 — 127.0.0.2:5555, 127.0.0.2:5557 … — a second address of this same PC, so an LDPlayer window is never mistaken for another emulator answering on the same port.
4. Restart the player after changing the display.

MEmu

1. Display — open System settings ▸ Display, set Resolution to Customize and enter W 540, H 960, DPI 120. Leave Forced landscape off, click OK and restart.
2. Engine — under System settings ▸ Engine, set Render mode to DirectX.
3. ABI — in System settings ▸ Preferences, set ABI to allow ARM apps (x86 and ARM) so the game installs.
4. ADB and address — MEmu keeps ADB on without a switch. The first window is 127.0.0.1:21503 and each further window adds 10 (21513, 21523 and so on); Evonex finds them on its own.

BlueStacks 5

1. Display — Settings ▸ Display: choose a custom resolution of 540 × 960 (portrait) and set 120 dpi. BlueStacks starts in landscape.
2. ADB — Settings ▸ Advanced, turn on Android Debug Bridge. BlueStacks prints the address under the switch.
3. Address — BlueStacks takes a free port each time a window starts, so the port can change. Link the instance to its BlueStacks window (Add instances ▸ Detected, or Link emulators) and Evonex reads the port again at every Start; typed by hand, use the address shown under the switch.

Several emulator windows

Give every account its own window: an instance drives one window at a time. Two instances may point at the same window — two accounts swapped on one player — but only one of them can run at a time; Start refuses the second while the first runs. How many windows a PC can carry depends mostly on its memory and cores; the This PC line on the Dashboard gives an estimate.

How Evonex checks it

1. When an address field loses focus, a bare port such as 5555 becomes the full address 127.0.0.1:5555.
2. Every two seconds the Instances page knocks on each instance's address; the card reads Ready when something answers and Offline when nothing does.
3. On Start, an instance linked to its emulator finds where that emulator answers now; if it is closed and Boot on Start is on, Evonex starts it and waits for Android.
4. Evonex connects. If it can't, the start stops with Can't reach the emulator at 127.0.0.1:5555 — open the emulator (or fix the ADB address in Settings), then Start again.
5. Then it measures the screen. Any size other than 540 × 960 portrait stops the start with Emulator must run at 540x960 (540p); got ….
6. Finally, if the game is closed or behind another app, Evonex opens it before the first job.

Examples

• Two accounts on MuMu Player 12. Two windows open at 127.0.0.1:16448 and 127.0.0.1:16480. Add instances lists both under Detected: add Northwatch with the first window ticked, then Silverpine with the second — each is linked to its own window.
• Three accounts on LDPlayer. Switch ADB on in each player. Detected lists them as LDPlayer #0, #1 and #2 at 127.0.0.2:5555, 5557 and 5559.
• A BlueStacks window. Tick it under Detected: the instance is linked to the window, so the port BlueStacks picks at each start is read again on every Start.

Troubleshooting