Instances & workspace

The workspace

One account's control room: start, pause and stop it, fix what blocks it, and follow every run live.

Open Instances and click an instance to open its workspace. The header runs the account, five views hold everything about it, and the first view, Overview, is where you start it, see what it is doing, fix anything that stops it, and follow each run step by step in the Activity Monitor.

NeedsAn instance Tasks or duties switched on

Where: Instances ▸ click an instance. Reading the interface shows where each theme puts Instances. The workspace always opens on Overview. This page covers the header, the views and the Overview.

One workspace, three layouts

The five views are the same in every theme — Overview, Plan, Duties, Task setup and Settings — and so are the controls and readings in them. What the theme changes is where they stand:

Aurora puts the header across the top — Instances, the name, Start and Pause — and the views on a row of tabs under it. Overview opens with four cards: Status, Now running, Next break and Uptime.
Standing Watch puts everything on one header line: Instances, the instance's grid code (such as C-18), its name in capitals, the views as numbered tabs (1 Overview to 5 Settings), the reminder ALT 1–5 SWITCHES VIEW, then Stop and Pause. Overview sets the four readings in one strip — STATUS, NOW RUNNING, NEXT BREAK, UPTIME — and stands the instance scope, the day as a round dial, beside the Activity Monitor.
Prism puts the crown across the top of every view — the back arrow, a state gem, the name with its Status under it, NOW RUNNING, NEXT BREAK, UPTIME, and Start / Stop and Pause as icon buttons — and the spectrum rail down the right wall: five glass facets, one per view, each with a peek at what it holds. Overview lays the day’s runs on the session lane inside the Activity Monitor.

The Overview: the header, the five views, the four live readings and the Activity Monitor.

Set it up

Open the instance from Instances.
On Duties, switch on the tasks and duties you want. Set each task's options on Task setup.
Back on Overview, if a Needs setup card is showing, press Fix on each row until the card disappears.
Press Start. The first time, Evonex offers rest breaks — choose Add rest breaks or Not now.
Watch the Activity Monitor: the running task appears at the top, and ● Live shows beside the title.

The header

Instances

Goes back to the Instances page. The account keeps running. Prism draws it as a back arrow (tooltip: Back to Instances).

Grid code

Standing Watch only: the instance's code on the Instances page, such as C-18.

Instance name

The name set under Settings. Prism shows the Status under it, beside the state gem — a mark whose shape says the state (a square when stopped).

Start / Stop

Start runs the account on auto-pilot: the plan and the duties take turns on their own schedules, and there is no mode to choose. While the account runs or is paused the button is a red Stop, which ends the run. Tooltips: Start the plan — Evonex runs your tasks on auto-pilot and Stop the plan. Prism shows both as icon buttons with the same tooltips.

Pause / Resume

Pause holds the run at its next step and keeps it open; the button then reads Resume, which carries on from the same place. Greyed out while the account is stopped (tooltip: Start the instance first).

The views

Overview

This view: status, setup gaps and the Activity Monitor.

Plan

The game day at a glance — what is owed, what is next, what happened. See Plan.

Duties

Where tasks and duties are switched on, ordered and given their rhythms. See Duties.

Task setup

What each task does in the game: targets, tiers, counts. See Task setup.

Settings

Name, emulator, city map, Screen delay, Shared device and Rest breaks. See Instance settings.

Switching views

Aurora: click a tab. Standing Watch: click a numbered tab, or press Alt+1 to Alt+5. Prism: click a facet on the rail; with the rail focused, ↑ / ↓ move to the next view.

Peeks (Prism)

Each facet says what its view holds: 30 runs today (and ✕ 1 issue · 58m ago while there are issues) on Overview, Next reset 7h 28m on Plan, the Duties verdict on Duties, 10 tasks in the library and the profile chip's state on Task setup, and the Screen delay (with Needs setup · 2 while there are gaps) on Settings.

Narrow windows

Standing Watch drops the tabs under the name, and folds the instance scope into a small dial beside the name (click it to open Overview). Prism shrinks the rail to icons; hover a facet for its name and peek.

The four live readings

Status, Now running, Next break and Uptime read the same in every theme: four cards in Aurora, one strip in Standing Watch (each with a line under it, such as working since 04:20, breaks off or since 04:20 · one tick an hour, and ● Live beside Now running while a run is live), and the crown in Prism.

Status

Running, Resting · 1m 20s (time left in a break), Reclaim 45s or Yielded (the game was opened on another device), Recovering, Paused, Error, Needs setup or Stopped. For Error and Needs setup, hover the value to read the reason.

Now running

The task on screen, with its progress when it counts units (Troop Training · 2/4). Otherwise On break, Recovering the game…, Reopening the game…, Yielded to you, Idle (running, with nothing due this moment), Paused, or — when stopped.

Next break

When the next rest break starts, such as in 2h 14m, or in 2d 5h when quiet hours skip to a day you picked. Now · 25m left during a break, Off when rest breaks are off, and — while stopped.

Uptime

How long this run has been going, in hours and minutes, such as 0h 42m; — while stopped.

The day beside the feed (Standing Watch and Prism)

Instance scope (Standing Watch)

NORTHWATCH'S DAY: the game day as one ring, the reset at the top and NOW as the red sweep. Today's runs stand where they started — ● done, ○ nothing to do, ✕ failed, ⊘ stopped — with the run in flight as a red arc into the sweep, the stretch the bot has been on watch, and the next break. The middle counts today’s runs (29 RUNS · 24 OK · 1 FAILED). Hover a mark to name its run; click it to open the run in the Activity Monitor. A legend sits under the dial.

Session lane (Prism)

Inside the Activity Monitor, under its title: 30 runs since the reset, then the day from the reset on an hour grid — the stretch the bot has been up (on since 04:19), the next break hatched, one mark per run (a failure loud red, a stop never red, the live run an open diamond with its line to NOW). Hover a mark for its run; click it to open the run. The filters sit in the monitor’s title row.

Needs setup

A Needs setup card appears above the Activity Monitor only when something would stop a task, a duty, or the whole instance from running. Evonex checks again every few seconds, and at once after you save a change, so the card shrinks as you fix things and disappears when nothing is left.

Count

Beside the title: how many rows there are. Red when something stops the whole instance; orange otherwise.

Red mark

A blocker: what the row names cannot run until it is fixed. Blockers are listed first.

Orange mark

A warning: worth fixing, but it stops nothing from starting.

Message

One sentence saying what is wrong and where to fix it. A row about a duty starts with Duties ·, so it is not confused with the task of the same name in your plan.

Fix

Goes to the place that fixes the row: the Settings view, a task's form on Task setup, a duty's settings window on Duties, the Duties view itself, City Mapper, or Coordex. Hover it to see where it leads.

Scrolling

The card shows up to four rows; scroll inside it for the rest. The count is always the full total.

Typical rows:

“Northwatch” has no emulator / device address set — set one in Instance settings before it can start. Fix opens Settings.
“Northwatch” has nothing enabled to run — enable a task on Plan, or a duty on Duties, before starting. Tasks are switched on from Duties; Fix takes you there.
“Rally Setter” needs “Coordex board” set before it can run — pick it in the task's setup. A required field on the task's form is empty. Fix opens that form.
A building the task walks to is not mapped in the city this instance uses. Fix opens City Mapper.

Starting with gaps

Pressing Start checks once more. If anything is a blocker, the Needs setup before starting dialog lists it before the bot starts. Warnings on their own never interrupt a start.

The list

Every blocker, up to six (then …and N more.), each naming its task or duty.

Heads-up (won't stop the start):

Up to four warnings, listed after the blockers.

What will run:

Notes about what the start will do — for example, that only duties will run because no task is switched on.

Cancel

Closes the dialog; nothing starts. The ✕ does the same.

Start anyway

Starts with the gaps still there: whatever can run does, and the blocked tasks and duties are skipped until fixed. Not offered when the blocker is about the whole instance — no emulator, an emulator another running instance holds, or nothing switched on — because nothing could run.

Open setup

Does not start. Goes straight to the fix for the first blocker in the list.

The first-Start rest break offer

The first time you press Start on an instance whose rest breaks are off, Evonex asks Add human-like rest breaks? It asks once per instance.

Add rest breaks

Switches Rest breaks on with both Periodic breaks and Quiet hours at their defaults: work 4 h, rest 30 min, ± 20 %; sleep 02:00 to 08:00 every day, wake ± 5 min. Adjust them any time under Settings ▸ Rest breaks.

Not now

Leaves rest breaks off. The question is not asked again for this instance.

Activity Monitor

A live log of this instance's runs, newest first. Each run is a card that opens to one row per operation, and an operation can open its full step trail. Standing Watch also prints each run’s outcome as a word beside its glyph — LIVE, DONE, NOTHING, FAILED, STOPPED, PAUSED — and the count of runs in view before the tick strip (30 RUNS · OLDEST → NEWEST). Prism marks the live run LIVE and shows the session lane where the tick strip would be.

● Live

Beside the title while a run is in progress. Click it to scroll to the running task and open it. Tooltip: Jump to the running task.

Tick strip

Aurora and Standing Watch: one small tick per run in the list (the newest 40), oldest on the left, toned by outcome. Hover a tick for the task, its outcome and how long ago; click it to jump to that run. Hidden when fewer than two runs are shown. Prism shows the session lane instead.

Clear

Hides every run shown now; new activity still appears. The cleared point is kept for this instance, even after Evonex restarts. It hides runs here only — the Plan view and the Dashboard still count them. Tooltip: Hide the activity shown — new activity will reappear.

Trash

Permanently deletes this instance's run history and its log files, everywhere they are counted: this monitor, the Plan view and the Dashboard. It asks first (Clear history & logs, then Delete) and works only while the instance is stopped; otherwise it says Stop the instance first, then clear its history and logs.

All tasks

Shows every task, or only the one you pick. The list holds the tasks that appear in the runs loaded.

All / Done / Issues

All shows every run. Done shows finished runs that went fine. Issues shows runs with a genuine failure, and its label carries the count it would show (Issues · 2). A stop you asked for is never an issue.

Search activity…

Filters runs by any text in them: the task name, the run's headline, each operation, and every detailed step. The small ✕ clears it.

Each run card, left to right:

Chevron

Opens or closes the run. The running run and the newest failed run open by themselves once; after that your clicks decide.

Glyph

The run's overall outcome — see Glyphs below.

Task name

Which task or duty the run was.

Headline

While running, what it is doing now (In progress… or Paused when there is nothing more specific). When finished, its outcome, or a count such as 3 done, 1 skipped. A task that fires again each time a march returns is folded into one card ending · N passes.

Tally

While a counting run is live, its progress such as 2 / 4. When finished, a count per outcome such as 3 ✓ · 1 ○ · 1 ✕.

Time

How long the run took and how long ago it started, such as 1m12s · 5m ago.

Operation rows

Inside an open run: one line per thing it did — a glyph, what happened (updating live while it runs) and its clock time.

Details

On rows that recorded a step trail. Opens Activity steps, below.

Day labels

When the list spans more than one day, runs are grouped under TODAY, YESTERDAY and dates such as SAT 05 JUL.

Show earlier activity

At the bottom when older runs exist; loads 30 more each time.

Empty list

No activity recorded yet., with a hint to press Start while the instance is stopped — or, when filters hide everything, No activity matches these filters — clear them to see the full log.

Glyphs

●

Running.

✓

Finished fine.

Failed.

⊘

Stopped — by you, or by a start check. Never counted as a failure.

❙❙

Paused.

○

Skipped — passed over this time.

✗

Blocked — deliberately left out, for example by a skip list.

A warning worth reading.

⌛

Waiting, and will try again.

Activity steps

Headline

The operation's summary.

Task · time

Which task, and the operation's clock time.

Copy

Copies the whole trail, oldest first with its step numbers, ready to paste into a report. The icon turns to a tick for a moment. Tooltip: Copy the whole trail — pasteable into a report.

Steps

Numbered with 1 as the oldest, newest on top. While the operation is still running, new steps appear at the top as they happen.

Show 50 earlier · N more

Shown when there are older steps than the popup holds; each click adds up to 50 (fewer when fewer are left, such as Show 6 earlier · 6 more).

No detailed steps were recorded for this one.

Shown when the operation kept no trail.

Closes the popup.

Clicking a run anywhere else — a run on the Plan view, a done 13:58 receipt, a mark on the instance scope or the session lane — brings you to Overview and opens that run. If the run is too old for the live list, a Run report popup shows what it recorded instead.

How it runs

Start checks the setup (the dialog above appears only for blockers), makes the one-time rest break offer, then starts. The bot opens the game if it is not already open and takes due duties and plan tasks one at a time.
Pause stops at the next step and holds there with the game left open. Resume carries on. Settings you save while the account runs or is paused are picked up at its next step.
Stop ends the run. The run in progress is recorded with ⊘ — a neutral outcome, not a failure.
The view refreshes every 2 seconds, and the rows of a running run update as each step happens.
Going back to Instances or anywhere else in the app does not stop the account.

The trash icon in the Activity Monitor deletes this instance's run history for good — the Plan view and the Dashboard lose those runs too. To tidy the view only, use Clear.

Examples

First start of a new instance. Open Ember Keep, switch on the tasks you want on Duties and press Start. The dialog lists a task whose form still has an empty required field. Press Open setup, fill the field, press Save changes, and press Start again. Choose Add rest breaks when asked.
Finding out why a run failed. Click Issues · 1. The failed run is already open; press Details on the row marked ✕ and use Copy to paste its trail into a message.
Stepping in for a few minutes. Press Pause, do what you need in the emulator, then press Resume. The bot carries on from where it paused.

Troubleshooting

I pressed Start and “Needs setup before starting” appeared.

Something is a blocker. Press Open setup to jump to the first fix, or Start anyway to run what can run and skip the rest. Once every blocker is fixed, Start starts without asking.

There is no Start anyway button.

The problem is with the whole instance: no emulator set, its emulator held by another running instance, nothing switched on, or Solo on a task that is switched off. Nothing could run, so fix it first — Open setup goes there.

I cannot find the tabs.

Each theme switches views its own way: a row of tabs in Aurora, numbered tabs beside the name in Standing Watch (or Alt+1 to Alt+5), and the facets down the right wall in Prism.

Status still says Needs setup after I fixed it.

It clears on the next check, a few seconds after saving. If it stays, the Needs setup card lists what is still open.

Now running says Idle.

The account runs, but nothing is due this moment — a watcher is between checks, or every task is waiting on its schedule. UP NEXT on the Plan view says what comes next and why.

Status reads Reclaim 2m 10s.

The game was opened on another device and the bot stepped aside. It takes the game back when the countdown ends. Change the wait, or turn reclaiming off, under Settings ▸ Shared device.

A row has no Details button.

Only operations that recorded a step trail get one. The row's own line is everything that operation reported.

The Activity Monitor is empty, but the bot has run before.

Check the filters: All tasks, All and an empty search show everything. If you pressed Clear, earlier runs stay hidden here; the Dashboard still counts them.

The trash icon tells me to stop the instance first.

History can only be deleted while the instance is stopped. Press Stop, then try again.

Next break says Off.

Rest breaks are off for this instance. Turn them on under Settings ▸ Rest breaks.