Evonexv0.1.0
Sign in Download

Pick the theme you use in the app (Settings ▸ Theme). Light or dark follows the switch at the top of this page.

Inside an instance

Instance settings

Name the instance, link its emulator and tune how it behaves around you.

Where
Instances ▸ open an instance ▸ Settings. A Fix button for the emulator on the Needs setup card lands here.
Use it to
Name the instance, link its emulator, set the screen delay, decide what happens when you play elsewhere and add rest breaks.
Saves
Everything saves as you change it. There is no Save button.

Settings has four groups for this one instance: Instance, Emulator, Shared device and Rest breaks. Switches save at once, numbers about a second after you stop typing, and the name when you press Enter or leave the field. A running instance picks a change up at its next step.

These settings belong to this instance. Profiles do not carry them, except the City map; see Profiles.

The Settings of Northwatch.
  1. 1Instance Names the instance and points it at its emulator.
  2. 2Emulator Links the emulator that Start opens.
  1. 1Instance Names the instance and points it at its emulator.
  2. 2Emulator Links the emulator that Start opens.
  3. 3Shared device Decides what happens when you play elsewhere or the game misbehaves.
  4. 4Rest breaks Adds human-like pauses so long runs do not look automated.
  1. 1Instance Names the instance and points it at its emulator.
  2. 2Emulator Links the emulator that Start opens.
  3. 3Shared device Decides what happens when you play elsewhere or the game misbehaves.
  4. 4Rest breaks Adds human-like pauses so long runs do not look automated.

Instance

The Instance group.
  1. 1Name Renames the instance everywhere in Evonex.
  2. 2Emulator Holds the address of the emulator this instance drives.
  3. 3Re-scan Looks for emulators again, for example one you just opened.
  4. 4City map Chooses the city map the bot uses to reach buildings.
  5. 5Screen delay Sets how long the bot waits for the screen to redraw after each tap.
  1. 1Name Renames the instance everywhere in Evonex.
  2. 2Emulator Holds the address of the emulator this instance drives.
  3. 3Re-scan Looks for emulators again, for example one you just opened.
  4. 4City map Chooses the city map the bot uses to reach buildings.
  5. 5Screen delay Sets how long the bot waits for the screen to redraw after each tap.
  1. 1Name Renames the instance everywhere in Evonex.
  2. 2Emulator Holds the address of the emulator this instance drives.
  3. 3Re-scan Looks for emulators again, for example one you just opened.
  4. 4City map Chooses the city map the bot uses to reach buildings.
  5. 5Screen delay Sets how long the bot waits for the screen to redraw after each tap.
Name
What this instance is called everywhere in Evonex. It saves when you press Enter or leave the field. Renaming needs you to be online. If it cannot update, the old name stays, everything else is saved and a message tells you.
Emulator
The address of the emulator this instance drives. Pick a detected emulator from the list or type an address such as 127.0.0.1:5555. A bare port works too: type 5555 and it becomes 127.0.0.1:5555 when you finish. The circular arrows scan again; Evonex also scans each time you open the instance. The box is greyed out while the instance is linked to an emulator, because the port then comes from the emulator each time it starts. Press Unlink on the Emulator group to type a port yourself.
City map
The map of your city the bot uses to reach buildings. Follows its emulator uses the map linked to this instance’s emulator on the City Mapper page, the same map for every instance on that emulator. Pick a map by name to use that one instead. A task’s own form can pick a different map for that task. If you delete a map an instance uses, city tasks stop with a row on the Needs setup card until you pick another. Default: Follows its emulator.
Screen delay
How long the bot waits after each tap for the game to redraw before it looks at the screen. The same wait applies to every step of every task. Raise it if steps are skipped for no reason, buttons are reported missing or taps land before a page has finished opening: that is what a PC too slow to keep up looks like. Lower it to make every task quicker; too low and the bot reads screens that have not finished drawing. Waits the game itself needs, such as a map animation or a cold start, do not change. From 300 to 6000 ms in steps of 100. It applies from the next step, even while the instance runs, and profiles do not carry it. Default: 1800 ms.

Emulator

Start opens this emulator when it is closed, then opens the game. Until you link one, the group reads Not linked — Evonex can't start this emulator for you. Link it and Start opens it when it's closed. and offers Link an emulator….

The Emulator group of a linked instance.
  1. 1Read-outs Show the emulator, the player, its folder and what Start does with it.
  2. 2Boot on Start Lets Start open the emulator when it is closed.
  3. 3Restart the emulator every Restarts the emulator after this many hours of running.
  4. 4Start emulator now Opens the emulator without starting the bot.
  5. 5Show window Brings the emulator’s window to the front.
  6. 6Unlink Forgets the emulator and its port.
  7. 7Change… Picks another player from the ones Evonex finds on this PC.
  1. 1Read-outs Show the emulator, the player, its folder and what Start does with it.
  2. 2Boot on Start Lets Start open the emulator when it is closed.
  3. 3Restart the emulator every Restarts the emulator after this many hours of running.
  4. 4Start emulator now Opens the emulator without starting the bot.
  5. 5Show window Brings the emulator’s window to the front.
  6. 6Unlink Forgets the emulator and its port.
  7. 7Change… Picks another player from the ones Evonex finds on this PC.
  1. 1Read-outs Show the emulator, the player, its folder and what Start does with it.
  2. 2Boot on Start Lets Start open the emulator when it is closed.
  3. 3Restart the emulator every Restarts the emulator after this many hours of running.
  4. 4Start emulator now Opens the emulator without starting the bot.
  5. 5Show window Brings the emulator’s window to the front.
  6. 6Unlink Forgets the emulator and its port.
  7. 7Change… Picks another player from the ones Evonex finds on this PC.
Emulator
Read-out: the program, such as MuMu, LDPlayer, MEmu or BlueStacks.
Player
Read-out: the player that is linked, such as MuMu #0 · “Northwatch”.
Folder
Read-out: where the emulator is installed.
On Start
Read-out: what pressing Start does with this emulator at this moment, 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. It saves at once and applies to the next Start. Default: ON once the emulator is linked.
Restart the emulator every
Closes the emulator and starts it again after this long running, because a long-running emulator slowly uses more memory. From 1 to 24 hours. The hours count from Start and again from each time the emulator started since; a pause does not stop the count. The first restart after a Start can wait up to 20 percent longer, so instances started together do not restart in the same minute. At most two emulators restart at once. A running task is never cut in the middle of an action: it winds down at its next safe moment first. If something else is using that emulator, the restart is tried again 15 minutes later. Status reads Recovering meanwhile. This works only for an emulator Evonex can close and start again (MuMu, LDPlayer or MEmu; an older MEmu needs Evonex to run as administrator) with Boot on Start on. Otherwise the row is greyed out and says Not available — … with the reason. Default: OFF; every 6 h once you switch it on.
Start emulator now
Opens the emulator without starting the bot.
Show window
Brings the emulator’s window to the front.
Unlink
Forgets the emulator and its port. It is greyed out while the instance runs.
Link an emulator… / Change…
Picks the player from the ones Evonex finds on this PC. It is the same picker as on the Instances page, and it is greyed out while the instance runs. See Emulator setup.

Shared device

The game runs on one device at a time. These settings say what Evonex does when you pick up your phone, and how it recovers when the game closes or freezes.

The Shared device group.
  1. 1Reclaim when I play elsewhere Takes the game back after you played on another device.
  2. 2Grace period first Sets how long the game stays yours before Evonex takes it back.
  3. 3Relaunch if the game closes Starts the game again when it closes.
  4. 4Restart if the game stalls Reopens the game when it stops responding.
  5. 5Stuck for Sets how long the game must be stuck before it is reopened.
  6. 6Reload after the daily reset Reopens the game after the reset so it starts fresh.
  7. 7Wait after reset Waits a few minutes after the reset before the reload.
  1. 1Reclaim when I play elsewhere Takes the game back after you played on another device.
  2. 2Grace period first Sets how long the game stays yours before Evonex takes it back.
  3. 3Relaunch if the game closes Starts the game again when it closes.
  4. 4Restart if the game stalls Reopens the game when it stops responding.
  5. 5Stuck for Sets how long the game must be stuck before it is reopened.
  6. 6Reload after the daily reset Reopens the game after the reset so it starts fresh.
  7. 7Wait after reset Waits a few minutes after the reset before the reload.
  1. 1Reclaim when I play elsewhere Takes the game back after you played on another device.
  2. 2Grace period first Sets how long the game stays yours before Evonex takes it back.
  3. 3Relaunch if the game closes Starts the game again when it closes.
  4. 4Restart if the game stalls Reopens the game when it stops responding.
  5. 5Stuck for Sets how long the game must be stuck before it is reopened.
  6. 6Reload after the daily reset Reopens the game after the reset so it starts fresh.
  7. 7Wait after reset Waits a few minutes after the reset before the reload.
Reclaim when I play elsewhere
This game runs on one device at a time. Open it on your phone and the emulator is kicked. The bot waits out a grace window, then reloads and resumes, which signs your phone out. Switch it off and the bot stays Yielded: it does not take the game back on its own. Default: ON.
Grace period first
How long to leave the game to you before the bot reloads and resumes. From 1 to 240 minutes. It is greyed out while reclaiming is off. If the instance is already kicked when you press Start, it takes the game back at once. It reclaims at most four times an hour, then stays yielded until the hour has passed. Default: 5 min.
Relaunch if the game closes
When the game has closed, starts it again from scratch, waits for a screen it knows and clears the load pop-ups and ads. Default: ON.
Restart if the game stalls
Reopens the game when it stops responding: a lost connection, a frozen screen, or something else covering the screen. Losing the connection for even a moment leaves the game out of sync: it still draws your city, but nothing you press works, and reopening it is the only way back. Default: ON.
Stuck for
How long the game has to be stuck before it is reopened, whether it says it lost the connection or just stopped answering. It is also the shortest gap between two reopens. A task that is working is never reopened just for running long. From 30 to 600 seconds in steps of 10. It is greyed out while the switch above is off. Default: 120 s.
Reload after the daily reset
Right after the server’s daily reset, closes and reopens the game so events, the shop and daily quotas are fresh before today’s daily tasks run. It happens only while the bot is running at that time. Starting it later does not reload. A task running at the reset finishes at its next safe moment first. Default: OFF.
Wait after reset
How long to wait after the reset before the reload. 0 reloads the moment the reset passes; a few minutes give the server time to settle. From 0 to 30 minutes. It is greyed out while the reload is off. Default: 0 min.
Reclaiming signs your phone out. The reload after the reset closes the game. Restarting the emulator, and closing it for a break, close the whole emulator, so anything else running on that emulator is disturbed too.

Rest breaks

Rest breaks pause the instance on a human-like schedule, so long non-stop runs do not look automated. The switch in the group’s header turns the whole group on. With it off, everything below is greyed out.

The Rest breaks group with rest breaks on.
  1. 1Rest breaks Turns the whole group on or off.
  2. 2Periodic breaks Plays for a while, then rests, again and again.
  3. 3Work for Sets how long to play before a break.
  4. 4Then rest for Sets how long each break lasts.
  5. 5Randomize by Varies both lengths so the rhythm is not fixed.
  6. 6Quiet hours Goes idle inside a window, like sleeping.
  7. 7Sleep from Sets when the quiet window starts.
  8. 8On these days Lights the days quiet hours run.
  9. 9Wake jitter Varies the wake time by a few minutes.
  10. 10Close the emulator too Closes the emulator for each break, not only the game.
  1. 1Rest breaks Turns the whole group on or off.
  2. 2Periodic breaks Plays for a while, then rests, again and again.
  3. 3Work for Sets how long to play before a break.
  4. 4Then rest for Sets how long each break lasts.
  5. 5Randomize by Varies both lengths so the rhythm is not fixed.
  6. 6Quiet hours Goes idle inside a window, like sleeping.
  7. 7Sleep from Sets when the quiet window starts.
  8. 8On these days Lights the days quiet hours run.
  9. 9Wake jitter Varies the wake time by a few minutes.
  10. 10Close the emulator too Closes the emulator for each break, not only the game.
  1. 1Rest breaks Turns the whole group on or off.
  2. 2Periodic breaks Plays for a while, then rests, again and again.
  3. 3Work for Sets how long to play before a break.
  4. 4Then rest for Sets how long each break lasts.
  5. 5Randomize by Varies both lengths so the rhythm is not fixed.
  6. 6Quiet hours Goes idle inside a window, like sleeping.
  7. 7Sleep from Sets when the quiet window starts.
  8. 8On these days Lights the days quiet hours run.
  9. 9Wake jitter Varies the wake time by a few minutes.
  10. 10Close the emulator too Closes the emulator for each break, not only the game.
Rest breaks
The master switch. With it off, no break ever happens. Default: OFF.
Periodic breaks
Work for a while, then take a break, on repeat. It takes effect once the master switch is on. Default: ON. A line under the group sums it up: ≈ plays 4 h, then rests 30 min · ±20% each time.
Work for
How long to keep playing before a break. From 1 to 48 hours. Default: 4 h.
Then rest for
How long each break lasts. From 5 to 600 minutes. Default: 30 min.
Randomize by
Varies both lengths by this much, so the rhythm is not a fixed pattern. With ± 20 % a 30-minute rest lasts 24 to 36 minutes. 0 is exact. From 0 to 50 %. Default: ± 20 %.
Quiet hours
Go idle inside a window on the days you pick, like a person sleeping. Default: OFF. A line under the group sums it up: Sleeps 02:00 → 08:00 every day · wakes ±5 min.
Sleep from
When the window starts, in 24-hour time on your PC’s clock. Default: 02:00.
Until
When the window ends. An end before the start runs overnight, such as 22:00 to 06:00. Default: 08:00.
On these days
Seven buttons, Monday first. Lit days are the days quiet hours run, and at least one stays lit. A window belongs to the day it starts on: a window that starts on Wednesday evening sleeps on into Thursday morning whether or not Thursday is lit. Default: every day.
Wake jitter
Varies the wake time by this much. From 0 to 120 minutes. Default: ± 5 min.
Close the emulator too
Closes the whole emulator for each break, not only the game, and starts it again when the break ends. It is offered only when periodic breaks or quiet hours are on, the instance is linked to an emulator that Evonex can close and start again, and Boot on Start is on. MuMu, LDPlayer and MEmu qualify (an older MEmu needs Evonex to run as administrator); BlueStacks never does. When it is not offered, a line under the switch says why, and the break closes only the game. A break also closes only the game while another running instance, City Mapper or Auto map uses that emulator. Default: OFF.

Problems?

The bot skips steps or says a button is missing when it is not.
Raise Screen delay by a few hundred milliseconds at a time, for example from 1800 to 2400, and go higher only if it keeps happening.
The bot takes the game back while I still play on my phone.
Reclaim when I play elsewhere is on. Lengthen Grace period first, or switch it off while you play.
The emulator closed and came back by itself after a few hours.
Restart the emulator every is on for this instance: it restarts the emulator after that many hours, to free memory. The task in hand finishes at a safe moment first. Change the hours, or switch it off.
The game restarts in the middle of a long task.
Evonex never restarts the game because a task runs long. It reopens it only when the game itself is stuck: a lost connection, a frozen screen. Stuck for sets how long; Restart if the game stalls is the switch.
My breaks are shorter than I set.
Randomize by varies each break. Set it to 0 for exact lengths.
The game did not reload after the reset.
It reloads only if the bot was running, not paused, at the reset plus Wait after reset. If you started later that day, there is no reload.
Quiet hours slept into a day I did not light.
A window belongs to the day it starts on, so it can run on into the next morning.
Close the emulator too is greyed out.
Read the line under the switch. It needs a linked emulator that Evonex can close and start, Boot on Start on, and periodic breaks or quiet hours on. BlueStacks cannot be closed from Evonex.
Restart the emulator every says Not available.
The instance is not linked, Boot on Start is off, the emulator is BlueStacks, or an older MEmu runs without Evonex as administrator. Your choice is kept.
I cannot type in the Emulator box.
The instance is linked to an emulator. Press Unlink first.

Read next

OverviewSet up your emulatorCity MapperProfilesInstancesWhen something’s off