Instances & workspace

Instances

Cards and the Manager: add instances, link their emulators, and start, stop and set them up one at a time or in bulk.

The Instances page lists every instance you have — one game account on one emulator each — in two views of the same roster. Cards gives each instance a card you read at a glance; the Manager is one table row per instance, built for a fleet: filters, your own order, and bulk actions that start, stop, link, name and set up many instances at once. From here you add instances, link them to their emulators and open their workspace.

123451234512345

1. Cards | Manager
2. Add instances
3. ⋯ More
4. Instance card
5. New Instance card

1. Cards | Manager
2. Add instances
3. ⋯ More
4. Instance card
5. New Instance card

1. Cards | Manager
2. Add instances
3. ⋯ More
4. Instance card
5. New Instance card

Set it up

1. Open your emulators with the game installed — see Emulator setup.
2. Click Add instances. Set How many, type a Name, and tick the emulators under Detected — one instance each.
3. Check the Preview and click Create. The new cards appear, stopped.
4. If some instances were made without an emulator, open the Manager and click Link emulators to pair them with their emulators.
5. Open each instance to set up what it should do, then press Start — on its card, in the Manager for many at once, or in its workspace.

The page header

The Cards view

Every card answers two separate questions. The status says what the bot is doing; the line under it says whether the emulator can be reached. A card can be Stopped while its emulator is up, or Running while the game is being recovered. The cards stand in the same order as the Manager’s rows.

Status

The Start / Stop button

The Manager

The Manager puts every instance in one table and acts on many at once. Tick rows — or click, Shift-click and Ctrl-click them, or press Ctrl+A for every visible row — and the bulk dock offers what can be done to them. The rows stand in your own order until you sort a column.

123456781234567812345678

1. Filter chips
2. N need a city map
3. Filter
4. Link emulators
5. Columns
6. City map column
7. Emulator column
8. Bulk dock

1. Filter chips
2. N need a city map
3. Filter
4. Link emulators
5. Columns
6. City map column
7. Emulator column
8. Bulk dock

1. Filter chips
2. N need a city map
3. Filter
4. Link emulators
5. Columns
6. City map column
7. Emulator column
8. Bulk dock

Each theme mounts the bulk dock its own way: Aurora floats it as a pill over the table's foot; Prism stands it as an inspector column beside the table that also lists the selected names and their mixed values (a pill on a window too narrow for it); Standing Watch docks it as a strip under the rows — 6 SELECTED, its keys, and Clear with its Esc key — and moves the filter, Link emulators and Columns into a head inside the table, beside a SORT · YOUR ORDER caption, with each row’s grid code (C-01 …) before its name.

Your order. The rows — and the cards — stand where you put them. Drag a row by the grip that shows left of its tickbox (a selected row drags the whole selection), or use the row menu’s Move items or Alt+Home / Alt+↑ / Alt+↓ / Alt+End. A header click sorts by that column, a second reverses it, a third goes back to your order. The order is only how the page lists them; it never changes what the bot does.

Undo. Ctrl+Z takes back the last change made here — a rename, a port, a link, a city map, a move — up to ten deep. Applying a profile and deleting instances cannot be undone, and say so before they act.

The bulk dock

Add instances

One sheet makes one instance or up to 200 at once. The recipe is on the left; the Preview on the right is exactly what Create will make — every row with its name, profile, emulator and port, before anything is created.

12345678910

1. Emulators found
2. How many
3. Name
4. Profile
5. Emulators
6. Detected list
7. Preview
8. Remove a row (×)
9. What happens next
10. Create

Link emulators

A linked instance knows which emulator on this PC is its own — MuMu Player, BlueStacks, LDPlayer or MEmu. Then Start opens that emulator if it is closed, waits for Android, opens Evony and begins the run; if the emulator closes mid-run it is started again, at most twice an hour. A linked instance’s port comes from its emulator at every Start, so a port that moves (BlueStacks picks one each time) never needs typing. Instances made from Detected are linked already; Link emulators (Manager, ⋯ menu or Ctrl+L) links the rest.

The Emulator popover

One instance’s emulator, from the row menu’s Emulator… or a double-click on its Emulator cell. The instance workspace’s Emulator card on the Settings tab shows the same panel.

123456789123456789123456789

1. Instance and port
2. LINKED HERE
3. SHARED
4. Shortcut field
5. What Start does
6. Boot on Start
7. Start emulator now
8. Unlink
9. Attach

1. Instance and port
2. LINKED HERE
3. SHARED
4. Shortcut field
5. What Start does
6. Boot on Start
7. Start emulator now
8. Unlink
9. Attach

1. Instance and port
2. LINKED HERE
3. SHARED
4. Shortcut field
5. What Start does
6. Boot on Start
7. Start emulator now
8. Unlink
9. Attach

City maps

An instance uses the city map on its own emulator — the one City Mapper linked to that emulator — unless you choose a map for it. Every instance on one emulator uses that emulator’s map. The City map column says which map each row uses; two maps on one emulator read Choose…, because Evonex never guesses.

The City map popover (one row) offers Follows its emulator, with what that finds (MuMu #3 → City map 2 · 20/20), or Choose a city map from a searchable list; with no map on the emulator it offers Auto map it or Map by hand, and an instance with no emulator Link it. A click writes at once and takes effect on the next trip into the city. For many rows, the dock’s City map or the N need a city map chip opens the sheet:

1234567

1. What happens next
2. Set all to
3. Reset all to follow emulator
4. Choose… row
5. Auto map it
6. Summary
7. Apply

Keyboard shortcuts

• Ctrl+1 / Ctrl+2 — Cards / Manager · Ctrl+N — Add instances · Ctrl+F — Filter · Ctrl+L — Link emulators.
• Ctrl+A — select every visible row · Space — add or remove the focused row · Enter — open the focused instance · Esc — close a popover, then cancel a drag, then clear the selection, then clear the filter.
• F2 — edit the focused cell · Ctrl+D — fill the focused cell’s value down the selection · Ctrl+V — paste a list into the focused column · Ctrl+C — copy the selection’s ports as addresses · Ctrl+Z — undo.
• Ctrl+Enter / Ctrl+Shift+Enter — start / stop the selection · Ctrl+B / Ctrl+Shift+B — start / shut down the selection’s emulators · Alt+Home / Alt+↑ / Alt+↓ / Alt+End — move the selection · Delete — delete the selection.

Deleting instances

1. On a card, click the trash icon; in the Manager, select the rows and click Delete… (or press Delete).
2. A card asks Delete “Ember Keep”? Its task assignments and settings are removed permanently. Generals scanned from it stay in the library. The Manager asks once for the whole selection, and at five or more asks you to type the count. A running instance is stopped first.
3. Confirm with Delete, or Cancel to keep them.

How it works

• Both views read the bots’ state every 2 seconds while the page is open (the Manager’s emulator column every 5, its city maps every 15). What the bot is doing comes straight from the running bot. Whether an emulator answers is checked in the background, so a slow emulator never freezes the page.
• One emulator, one running instance. Two instances may point at the same emulator, but only one can run there at a time: the other reads In use, and if you still try to start it Evonex refuses with Emulator in use.
• Evonex starts at most two emulators at a time, a few seconds apart; the Manager shows the rest as Queued.
• Emulator links, ports and the order of the rows belong to this PC; another PC signed in to the same account keeps its own.
• Creating and deleting instances need an internet connection. Offline, Evonex says so and changes nothing.
• Leaving this page does not stop anything. Instances keep running while you work elsewhere in the app.

Examples

• Ten farms on MuMu Player. Open ten MuMu windows, click Add instances, set How many to 10 — Detected ticks the ten open windows — type Farm, pick your farm profile and click Create 10 instances. Each one is linked to its window, so Start opens a closed window by itself.
• Starting the morning shift. In the Manager, click the Stopped chip, press Ctrl+A, then Ctrl+Enter: every stopped instance starts, and Evonex opens the linked emulators two at a time.
• Two maps on one emulator. Highmoor’s emulator has City map 4 and City map 5, so its City map cell reads Choose…. Click it and pick City map 4 — Highmoor uses it from its next trip into the city.

Troubleshooting