Start here

Create your first instance

Add instances for one account, and how to read an instance card before you Start.

An instance is one game account on one emulator window. You add it once — a name and its emulator — and from then on its card on the Instances page tells you whether it can run, and its workspace is where you set it up.

NeedsAn emulator set up for Evonex

Open Instances (see Reading the interface for where each theme keeps it) and click Add instances at the top right, or the New Instance card at the end of the grid (Connect a new emulator), or press Ctrl+N — all three open the same Add instances sheet.

Add instances for one account: one emulator ticked under Detected, and the row the sheet will create.

Set it up

Start the emulator window this account plays in.
On Instances, click Add instances.
Leave How many at 1 and type a Name.
Under Emulators, Detected lists every emulator on this PC that no instance uses — open ones under Open, closed ones under Stopped (they boot on Start). Tick the one this account plays in. If it is not listed, choose By port and pick or type its address instead.
Check the row under Preview, then click Create 1 instance. The card appears on the grid and, within a few seconds, reads Ready.
Click the card to open the instance's workspace.

Add instances, for one account

The same sheet makes one instance or two hundred; the whole sheet is described on Instances. For one account these are the parts you use, top to bottom:

Emulators found

At the top right: how many open emulators are not linked yet, a chip per emulator app, and Rescan, which looks again (use it after opening an emulator while the sheet is up).

How many

1 for one account (up to 200 at once). The line beside it says how many will be created.

Name

The name, and what follows it. The box starts filled with Instance — type the account's name over it. For one instance the second box reads None: the name is used as typed. With the name empty, Create stays greyed (Type a name.) unless the second box is Port number or Emulator's name, which name the row themselves. You can rename it later on the instance's Settings tab.

Profile

No profile, or a saved profile whose setup the new instance takes.

Emulators

Detected (tick an emulator found on this PC — the instance is linked to it), By port (pick or type the address in Emulator (ADB); a bare port such as 5555 becomes 127.0.0.1:5555) or Link later (no emulator yet — the card reads No emulator until you set one).

Detected list

One row per emulator: its app, number, a dot that is lit while it is open, the name its own manager shows and its port — in italics while it is only the port a closed emulator usually opens, auto when the port is read as it starts. Pick all / Clear tick or clear a section.

Preview

The row Create makes: its name, profile, emulator, port and why that emulator (Picked for one you ticked).

What happens next

The plan in one line, ending nothing starts until you press Start.

Cancel / ✕

Closes the sheet without creating anything (Esc does the same).

Create 1 instance

Creates the instance and adds its card to the grid. It needs an internet connection. The new instance is stopped until you press Start.

Reading an instance card

Instance cards in the states you meet before and after the first Start.

Name

The instance's name (a long name is shortened; hover for all of it).

Trash button

Delete instance. Asks first — see Deleting an instance below.

Status

What the bot is doing, in one word — Ready, Offline, Running and so on (list below). While running, the time since Start sits beside it (12m, 1h 12m).

Address line

The emulator's address with a connection mark: lit when it answers, red when it stops answering while the instance runs, dim otherwise. While running, the task in hand replaces the address. When the instance stopped for a reason — an error, a setup gap — the reason takes this line instead (hover for the full sentence).

Start / Stop

Start runs the instance straight away (Start this instance); Stop ends it at its next step (Stop this instance). Start is greyed with Emulator unreachable — open it first while the emulator doesn't answer or another instance is using it — but not for an emulator Evonex starts itself (linked, Boot on Start on): Start opens it.

Open →

Click anywhere on the card to open the instance's workspace.

Before the first Start the status is about the connection. These are the words you will see:

Ready (blue) — the emulator answered at its address. Start is available.
Offline (grey) — nothing answered. Open the emulator and check its ADB switch; Start is greyed until it answers. An emulator Evonex starts itself (linked, Boot on Start on) reads Stopped instead, with Start available: Start opens it.
No emulator (grey) — no address is set; the address line reads No emulator address set. Set one on the instance's Settings tab, or link it with Link emulators.
In use (orange) — another running instance is driving the same emulator; the line reads in use by Northwatch. Stop that one or give this instance its own window.
Stopped (grey) — not probed yet, or stopped with a reason shown on the address line.
Needs setup (orange) — a Start was refused because something is missing; the reason is on the address line and Start stays available for when it's fixed.
Error (red) — the last start or run ended in an error, such as a closed emulator or a wrong resolution; the reason is on the address line.

The In use state only catches up every couple of seconds. Click Start in the instant another instance actually grabs the same emulator and the card hasn't repainted yet, and Start refuses with a dialog instead of silently doing nothing: Emulator in use — 127.0.0.1:16448 is already running under 'Northwatch'. Two instances can't drive the same emulator at once — stop that one first. It's the same rule the card shows; the dialog is just the moment it hasn't caught up to yet.

Each theme draws the card its own way; the words are the same. Aurora: a card with a coloured edge and the status in a pill. Prism: a cut-glass card with the state as a gem in a socket. Standing Watch: a unit chit — a state mark, a grid code such as C-01 over the name in capitals, the status in capitals, the address after a small diamond that is filled while the emulator answers, and the Start key and Open → under a rule; a card in Error or Needs setup sits tilted with an ATTENTION stamp. See Reading the interface.

How it runs

The Instances page refreshes every card every two seconds while it is open, and knocks on each emulator's address in the background. A card's Start runs the instance at once, without the Needs setup before starting window the workspace shows: if something is missing, a Needs setup message names it and the card turns orange. Starting from the workspace's Overview tab lets you review the gaps first.

Deleting an instance

Click the trash button on the card. Delete instance asks: Delete “Ember Keep”? Its task assignments and settings are removed permanently. Generals scanned from it stay in the library. If the instance is running, it adds that it will be stopped first. Click Delete to confirm or Cancel to keep it.

Deleting removes the instance's duties, plan, task settings and instance settings for good. Your generals, presets, city maps and other Resources are shared and stay.

Examples

Two accounts, two windows. Open both MuMu windows, set How many to 2 and tick both under Detected; rename the rows to Northwatch and Silverpine afterwards, or add them one at a time with their own names. Both cards read Ready, and each runs on its own.
Setting the emulator later. Add Ember Keep with Link later while you set the emulator up. The card reads No emulator; when the window is ready, link it with Link emulators or pick its address on the instance's Settings tab.

Troubleshooting

Create is greyed out.

Hover it for the reason: Type a name. (the Name box is empty), Nothing to create with these settings., or a batch still being created. If Evonex says you are offline, reconnect and try again.

Detected lists no emulators.

No emulator without an instance was found. Start the emulator and press Rescan, or choose By port and type the address from the emulator's ADB setting.

The card reads Offline.

The emulator is closed, its ADB switch is off, or the address is wrong. See Emulator setup. Linking it with Boot on Start on lets Start open it for you, and the card then reads Stopped.

The card reads In use and Start is greyed.

Another running instance has the same address. Two instances can't drive one emulator at once — stop the other instance, or give this one its own window.

I picked the wrong emulator.

On Instances, open the Manager, select the row and use Emulator ▸ Link…, or pick the right address in the Emulator field on the instance's Settings tab. It saves as soon as you pick.