Instances & workspace

Instance settings

Who this account is, which emulator it drives, how it recovers from trouble, and when it rests.

The Settings view holds four groups for this instance: Instance (its name, emulator address, city map and Screen delay), Emulator (the emulator player Start opens), Shared device (what happens when you play elsewhere or the game misbehaves) and Rest breaks (human-like pauses). Everything saves as you change it — there is no Save button.

NeedsAn instance A mapped city, for tasks that walk to buildings

Where: Instances ▸ open an instance ▸ Settings. These settings belong to this instance only and are not carried by profiles, except the City map.

The controls are the same in every theme; the page around them is not:

Aurora — four cards in one column you scroll.
Standing Watch — four plates in three columns that fit one screen: §1 INSTANCE over §2 EMULATOR, §3 SHARED DEVICE, and §4 REST BREAKS with the NEXT 24 H watch bill — the next day on one strip, NOW at its head, each coming break a block and quiet hours hatched. A group whose switch is off goes dashed, and its numbers say OFF.
Prism — four bands down the page, each with its title on the left and its fields on the right. Every switch is a light gate that prints ON or OFF and sends a beam into the fields it governs, solid while on and dashed while off; a field its gate has turned off is greyed with RETIRED WHILE OFF.

The Settings view: Instance and Emulator (Aurora shows the top of its column; Standing Watch and Prism show all four groups).

Set it up

Check Emulator holds the right address — the instance should read Ready on Instances once it does.
On Emulator, link the instance to its emulator player if you want Start to open the emulator for you.
Leave City map on Follows its emulator, or pick the map you made in City Mapper, if this account runs tasks that walk to buildings.
Leave Screen delay at its default unless the bot misreads screens.
Review Shared device. The defaults suit most accounts.
Switch Rest breaks on if the account runs for long stretches.

Instance

Name this account and bind it to an emulator.

Name

What this instance is called everywhere in the app. Saved when you press Enter or click out of the field. Renaming needs an internet connection; if it cannot be saved, Evonex keeps the old name, saves everything else, and tells you.

Emulator

The address this instance drives. Pick a detected emulator, or type an address such as 127.0.0.1:5555 or just the port. The circular-arrows button looks for emulators again; Evonex also looks each time you open the instance. Saved when you pick or finish typing. Placeholder: 127.0.0.1:5555. While the instance is linked to its emulator (the Emulator group below) the field is greyed: the port comes from the emulator each time it starts — unlink it to type one.

City map

The city map this instance uses to reach buildings inside the city. Default: Follows its emulator — the map linked to this instance’s emulator on the City Mapper page (or mapped on its port), the same map for every instance on that emulator. Pick a map by name to use that one whatever emulator it is on. A task's own form can pick a different map for that task. The list refreshes each time you open it, so a map you have just made appears. Saved as soon as you pick.

Screen delay

How long the bot waits after a tap for the game to finish drawing before it looks at the screen — the same wait for every such step in every task. 300 to 6000 ms in steps of 100. Default: 1800 ms. Saved a moment after you stop changing it, and used from the next step, even while running. Waits the game itself needs, such as a map animation or a cold start, are not changed by it.

Raise Screen delay when the bot skips steps for no reason, reports buttons as missing, or taps before a page has opened — that is what a PC that cannot keep up looks like. Lower it to make tasks quicker, but too low and the bot reads screens that have not finished drawing.

Emulator

Start opens this emulator when it's closed, then opens Evony. A linked instance needs no emulator open when you press Start; an unlinked one reads Not linked — Evonex can't start this emulator for you. Link it and Start opens it when it's closed.

Emulator · Player · Folder

Shown once linked: the emulator (MuMu, LDPlayer, MEmu or BlueStacks), the player inside it with the name its own manager shows (such as MuMu #0 · “Northwatch”), and the folder it is installed in.

On Start

What pressing Start does with it right now, such as Starts it if it's closed, then opens Evony, or why it will not.

Boot on Start

On: Start opens the emulator when it is closed. Off: Off = Evonex only connects to an emulator you opened. Default: on. Saved at once.

Restart the emulator every

On, with the hours beside it (1–24, default 6): after the bot has run that long, it finishes the task in hand at a safe point, closes the emulator, starts it again and reopens the game — a long-running emulator slowly uses more memory, and a restart frees it. The hours count from Start, and again from every time the emulator was started since (a rest break that closed it counts). Only for an emulator Evonex can close and start again: MuMu, LDPlayer or MEmu with Boot on Start on — otherwise it reads Not available and says why. If Map by hand or Auto map is using the emulator at that moment, it tries again 15 minutes later. Default: on, every 6 h. The switch saves at once.

Start emulator now

Opens the emulator now without starting the bot.

Show window

Brings the emulator’s window to the front.

Unlink

Forgets the emulator and its port. Greyed out while the instance runs.

Link an emulator… / Change…

Picks the emulator player this instance uses, from the players Evonex finds on this PC — the same picker as on Instances. Greyed out while the instance runs.

You never set the daily reset: every server resets at 00:00 US Pacific time, and daily tasks and daily limits roll over there. What you can choose is whether to reload the game after it — under Shared device.

Shared device

Hand the game back when you pick up your phone, and recover from a crash. Every switch and number saves as you change it and applies to a running instance straight away.

Reclaim when I play elsewhere

The game runs on one device at a time. When you open it on your phone, the emulator is kicked; with this on, the bot waits out the grace period, then reloads and carries on — which signs your phone out. With it off, the bot stays Yielded and does not take the game back on its own. Default: on.

Grace period first

How long the game is left to you before the bot takes it back. 1 to 240 min. Default: 5 min. Greyed out while reclaiming is off. If the instance is already kicked when you press Start, it takes the game back at once. It takes the game back at most 4 times an hour, then stays yielded until the hour has passed.

Relaunch if the game closes

Starts the game again if it has closed or crashed. Default: on.

Restart if the game stalls

Reopens the game when it stops responding — a lost connection, a frozen screen, or something else taking over the screen. After even a short connection loss the game can still draw your city while ignoring every tap, and reopening it is the only way back. A task that is working is never reopened for running long. Default: on.

Stuck for

How long the game must be stuck before it is reopened. It is also the shortest gap between two reopens, so a lasting problem is retried rather than hammered. 30 to 600 s in steps of 10. Default: 120 s. A game that leaves the screen is reopened without waiting. Greyed out while Restart if the game stalls is off.

Reload after the daily reset

Right after the server's daily reset, closes and reopens the game so events, the shop and daily limits are fresh before today's daily tasks run. Once a game day, and only if the bot was running at that time. A task that is running at that moment finishes at its next safe point first. Default: off.

Wait after reset

How long after the reset to wait before reloading. At 0 the game reloads the moment the reset passes; a few minutes lets the server settle first. 0 to 30 min. Default: 0 min. Greyed out while the reload is off.

Rest breaks

Pause on a human-like schedule so long, non-stop runs don't look automated. Every switch and number saves as you change it.

Rest breaks switch

In the group's header. Turns the whole group on or off; with it off, everything below is greyed out. Default: off.

Periodic breaks

Work for a while, then take a break, on repeat. Default: on (it takes effect once the group's switch is on).

Work for

How long to play before a break. 1 to 48 h. Default: 4 h.

Then rest for

How long each break lasts. 5 to 600 min. Default: 30 min.

Randomize by

Varies both lengths by up to this much each time, so the rhythm is not a fixed pattern. ± 0 to 50 %. Default: ± 20 %.

Periodic summary

A plain-language preview under the section: ≈ plays 4 h, then rests 30 min · ±20% each time, or Off — plays without periodic breaks.

Quiet hours

Go idle inside a window on the days you pick, like sleeping. Default: off.

Sleep from

When the window starts, 24-hour, in your PC's time. Default: 02:00.

Until

When the window ends. An end earlier than the start runs overnight, such as 22:00 to 06:00. Default: 08:00.

On these days

Seven day buttons, Monday first: the days the window may start on. All lit means every day, which is the default; at least one day always stays lit. A window that runs overnight belongs to the day it starts on, so with Wednesday lit, Wednesday's 22:00 to 06:00 sleeps on into Thursday morning whether or not Thursday is lit. A day saves the moment you click it.

Wake jitter

Moves the wake time earlier or later by up to this much. ± 0 to 120 min. Default: ± 5 min.

Quiet summary

Sleeps 02:00 → 08:00 every day · wakes ±5 min, Sleeps 22:00 → 06:00 (next morning) on Wed, Sat · wakes ±5 min, or Off — no quiet hours.

Close the emulator too

Closes the emulator itself for each break, not just the game, and starts it again when the break ends. Default: off. It is offered only when Evonex can start that emulator again afterwards: this instance is linked to its emulator in the Emulator group with Boot on Start on, and it is one Evonex can close — MuMu, LDPlayer or MEmu (an older MEmu only when Evonex runs as administrator; BlueStacks cannot be closed from Evonex). It also needs Periodic breaks or Quiet hours on. When it is not offered the switch is greyed out, your choice is kept, and the line under it says why; when it is, that line names the emulator it will close (Closes MuMu #0 for each break and starts it again when the break ends.). If another instance is running on the same emulator, or City Mapper is using it, that break closes only the game.

NEXT 24 H

Standing Watch only: the watch bill at the head of the group — the next 24 hours on one strip with NOW at its head, each coming break a block (REST) and quiet hours hatched. Its header says TIMES MOVE BY THEIR JITTER; with the group off it draws, dashed, what the breaks would do. Hover a block for its times.

Randomize by really does change each break: ± 20 % of a 30-minute break is anywhere from 24 to 36 minutes. A break shorter than the number you typed is the setting working. Set it to 0 for exact lengths.

How it runs

A break starts between runs; a long watcher such as Rally Joiner winds down at a safe point first. The bot closes the game (and the emulator, with Close the emulator too), Status reads Resting, and when the break ends the emulator is started again if it was closed, the game is reopened and the plan carries on. Quiet hours take priority over a periodic break due at the same time.
Breaks survive a restart. Close and reopen Evonex mid-break and the instance keeps sleeping for the time that was left; the countdown to the next break carries over too, so an account you restart often still gets its breaks. If the break had closed the emulator, Start opens it to connect and the resumed break closes it again.
Edits apply at once. Shorten Then rest for during a break and it ends sooner; switch the group off and the instance wakes, starting the emulator again if the break had closed it.
When you play elsewhere, Status reads Reclaim with a countdown, then Now running reads Reopening the game… while it takes the game back.
The daily-reset reload happens once a game day, at the reset plus Wait after reset (right at the reset by default), only if the bot was running (not paused) at that moment. A task still running then finishes at its next safe point first, and the game reloads after it. Starting or resuming the bot after that moment does not reload. A game the bot itself opened after that moment counts as fresh and is not reloaded again.

Examples

An overnight farm. On Ember Keep: Rest breaks on, Periodic breaks 5 h work, 25 min rest, ± 25 %; Quiet hours 01:30 until 07:00, wake ± 40 min; Reload after the daily reset on, Wait after reset 5 min.
Quiet hours on some days only. On Silverpine: Quiet hours 22:00 until 06:00, On these days Wed and Sat. A window belongs to the day it starts on, so Wednesday's sleep runs into Thursday morning, and Thursday evening plays straight through.
Breaks that rest the PC too. On Northwatch, linked to its MuMu player with Boot on Start on: Rest breaks on and Close the emulator too on. Each break closes the emulator and opens it again when the break ends.
A main you also play on your phone. On Northwatch: Reclaim when I play elsewhere on, Grace period first 45 min — long enough to finish what you are doing before the bot takes over again. Turn reclaiming off on days you want the account to stay yours.
A slower PC. Tasks report buttons missing that are plainly on screen. Raise Screen delay from 1800 ms to 2400 ms and watch the next few runs; go higher in steps of 300 ms only if it keeps happening.

Troubleshooting

The bot skips steps or says a button is missing when it isn't.

The screen had not finished drawing when the bot looked. Raise Screen delay a few hundred milliseconds at a time.

The bot keeps kicking me off my phone.

Reclaim when I play elsewhere is on. Lengthen Grace period first, or switch reclaiming off while you play.

The emulator closed and came back by itself after a few hours.

That is Restart the emulator every on the Emulator card — on by default, every 6 h — freeing the memory a long-running emulator builds up. The task in hand finishes at a safe point first. Change the hours or switch it off there.

The game restarts in the middle of a long task.

A task is never restarted for running long — only when the game itself gets stuck: it lost its connection, froze, or left the screen. Evonex reopens the game and picks the task up again. Stuck for sets how long a frozen or disconnected game is given first; a game that leaves the screen is reopened at once. Restart if the game stalls is the switch for all of it.

My breaks are shorter than I set.

That is Randomize by at work. Set it to 0 for exact lengths.

The game didn't reload after the reset.

It reloads only if the bot was running at the reset plus Wait after reset (0 by default). If you started it later, or it was paused then, there is no reload that day.

Quiet hours slept into a day I did not light.

A window belongs to the day it starts on. An overnight window that starts on a lit day sleeps on into the next morning, lit or not.

Close the emulator too is greyed out.

Evonex only closes an emulator it can start again. Check that this instance is linked to its emulator in the Emulator group with Boot on Start on, that Rest breaks is on with Periodic breaks or Quiet hours, and read the line under the switch — it says what is missing. BlueStacks cannot be closed from Evonex, and an older MEmu needs Evonex to run as administrator (MEmu 9.5.7 does not).

I cannot type in the Emulator field.

The instance is linked to its emulator, and its port comes from the emulator each time it starts. To type an address, press Unlink in the Emulator group first.

Which clock do Quiet hours use?

Your PC's own time, 24-hour; the days in On these days are your PC's days too.

My new name didn't stick.

Renaming needs an internet connection. Evonex keeps the old name and tells you when it can't save it; try again once you're online.

City map shows a map I deleted.

The instance still points at it, and tasks that need a city stop with a setup gap. Pick another map, or Follows its emulator.