Instances & workspace

Instance settings

Identity, shared-device recovery, and human-like rest breaks.

The Settings tab holds three cards: Instance (who this account is and which emulator it drives), Shared device (handing the game back and recovering from trouble), and Rest breaks (human-like pacing).

Instance

Name

What this account is called on the grid and in the header.

Account type

main or farm — a label for organizing your accounts.

Emulator

The emulator this instance drives; pick a detected one or type a host:port address.

City map profile

The mapped city this account uses to reach in-city buildings. Create and map it in City Mapper; a task can still override it in its own settings.

Screen delay

How long Evonex waits after each tap for the game to redraw before it looks at the screen — the same wait for every step in every task.

Raise Screen delay if the bot is misreading screens: steps skipped for no reason, buttons reported as missing, or a tap landing before a page has finished opening. Those are what a PC too slow to keep up looks like. Lower it to make every task quicker — but too low and the bot starts reading screens that have not finished drawing. It starts at 1800 ms and applies straight away, with no need to stop the bot.

This card saves as you go — there is no Save button. The emulator, city profile and screen delay save the moment you set them; the name and account type save when you click out of the field.

You do not have to tell Evonex when the daily reset is: every game server resets at the same fixed moment (00:00 US Pacific time), and daily tasks and per-day quotas roll over there automatically — not at your PC's midnight. The one thing you can choose is whether to reload after it, which is on the Shared device card below.

Shared device

This game runs on one device at a time, so this card decides what happens when you pick the game up elsewhere or it runs into trouble. Changes here take effect immediately — no Save needed.

Reclaim when I play elsewhere — when another device logs in, wait out a grace window, then reload and resume (signing the other device out). Set the Grace period first.
Relaunch if the game closes — cold-start the game if its process is gone.
Restart if the game stalls — force-restart when the screen freezes and stops responding. Set how long it must stay Stuck for first.
Reload after the daily reset — a few minutes after the server resets, close and reopen the game so events, the shop and daily quotas are fresh before today's daily tasks run. Wait after reset is how long to give the server to settle first. It fires once a day, and it does not matter whether the bot was running when the reset went past: a start that finds the game still open from before the reset reloads it. What it never does is reload a game it opened itself after the wait — that one is fresh already.

Rest breaks

A round-the-clock run is itself a signal, so Rest breaks pauses the account on a human-like schedule. Switch the card on, then use periodic breaks, quiet hours, or both. A break closes the game and reopens it afterwards, and only ever starts between task runs — never mid-step. These settings also save instantly.

Periodic breaks — Work for a stretch, Then rest for a while, on repeat, with Randomize by a percentage so the rhythm isn't a fixed pattern.
Quiet hours — go idle inside a daily window: Sleep from a start time Until an end (it may cross midnight), with a Wake jitter that randomizes the wake time.

Randomize by means the break really is a different length each time — ±20% of a 30-minute break is anywhere from 24 to 36 minutes. That is the point of it, so a break that comes out shorter than the number you typed is the setting working. Set it to 0 if you want the exact figure.

A break survives closing Evonex. Stop and restart the app mid-break and the account stays asleep for the time that was left, rather than waking up the moment the window reopens; the countdown to the next break survives a restart too, so an account you restart often still gets its breaks.