Inside an instance

Overview

Start, pause and stop one instance, and follow everything it does.

Where

Instances ▸ click an instance. On the Dashboard, a click on an instance’s row opens it too.

Use it to

Start, pause and stop the instance, fix what blocks it, and read what it did.

Good to know

An instance always opens on Overview. Leaving it never stops the instance.

Overview is the control room of one instance. Press Start and Evonex plays this game for you. The tasks on your plan and your duties take turns by themselves, so there is no mode to choose. Every run lands in the Activity Monitor, newest first.

Your plan is the list of tasks you add on Duties. Duties are the daily care Evonex fits in around it.

123456781234567812345678

1. 1Start / Stop Starts the instance. While it runs, the same button reads Stop and ends the run.
2. 2Pause Holds the run at its next step and keeps the game open. The button then reads Resume.
3. 3The five views Switch between Overview, Plan, Duties, Task setup and Settings.
4. 4Status Shows whether the instance is running, resting, paused or stopped.
5. 5Now running Names the task that has the screen.
6. 6Next break Counts down to the next rest break.
7. 7Uptime Shows how long the instance has run since you pressed Start.
8. 8Activity Monitor Lists every run of this instance, newest first.

1. 1Start / Stop Starts the instance. While it runs, the same button reads Stop and ends the run.
2. 2Pause Holds the run at its next step and keeps the game open. The button then reads Resume.
3. 3The five views Switch between Overview, Plan, Duties, Task setup and Settings.
4. 4Status Shows whether the instance is running, resting, paused or stopped.
5. 5Now running Names the task that has the screen.
6. 6Next break Counts down to the next rest break.
7. 7Uptime Shows how long the instance has run since you pressed Start.
8. 8Activity Monitor Lists every run of this instance, newest first.

1. 1Start / Stop Starts the instance. While it runs, the same button reads Stop and ends the run.
2. 2Pause Holds the run at its next step and keeps the game open. The button then reads Resume.
3. 3The five views Switch between Overview, Plan, Duties, Task setup and Settings.
4. 4Status Shows whether the instance is running, resting, paused or stopped.
5. 5Now running Names the task that has the screen.
6. 6Uptime Shows how long the instance has run since you pressed Start.
7. 7Protection Shows whether the keep’s bubble is up and until when. Press it to open the Protection duty.
8. 8Activity Monitor Lists every run of this instance, newest first.

Your first run

1. 1Link the emulatorOn Settings, link the emulator this instance plays on, or type its address.
2. 2Pick what runsOn Duties, add tasks to your plan and switch on the duties you want.
3. 3Set up the tasksOn Task setup, fill in each task that has a form and press Save changes.
4. 4Fix what is flaggedBack on Overview, press Fix on each row of the Needs setup card until the card is gone.
5. 5Press StartAnswer the rest-break question the first time. Then watch the first run appear in the Activity Monitor.

Start, pause and stop

• Start checks your setup, then starts. If the instance is linked to an emulator that is closed, Evonex opens the emulator first (while Boot on Start is on) and then opens the game.
• Pause holds the run at its next step and keeps the game open. The button turns into Resume: press it to carry on from the same place. Pause is greyed out while the instance is stopped.
• Stop ends the run. The task in progress is recorded as stopped, not as a failure, and the Activity Monitor keeps its history.
• Leaving this page never stops anything. Instances takes you back to the list while the instance keeps running.
• A change you save in Settings, Duties or Task setup while the instance runs is picked up at its next step. You do not need to restart.
• Some themes print ALT 1–5 SWITCHES VIEW. Press Alt+1 to Alt+5 to jump between the five views.

The four readings

Four live readings tell you how the instance is doing. They refresh every two seconds. Where they sit depends on your theme; their words are the same.

In the Prism theme they ride the top bar, which stays in view on every view: Status under the instance’s name, then three facts — Now running, Protection and Uptime unless you change them. Next break then sits on Plan, where Arrange facts lets you choose which facts the top bar shows.

The Needs setup card

When something would stop a task, a duty or the whole instance, a Needs setup card appears above the Activity Monitor. It is hidden when everything is in order.

123412341234

1. 1Count Counts every row. It is red when a row stops the whole instance and orange when none does.
2. 2Red dot Marks a blocker: this task or duty cannot run until you fix it.
3. 3Orange dot Marks a warning. The instance can still start.
4. 4Fix Jumps to the place that solves the row.

• Each row is one problem in plain words. Problems that stop work come first.
• Fix takes you to the place that solves the row: Settings, a task’s form on Task setup, a duty’s settings window on Duties, City Mapper or Coordex. Hover Fix to see where it leads.
• The card shows four rows and scrolls for more. It updates a few seconds after you save a fix.

Typical rows:

• “Northwatch” has no emulator / device address set — set one in Instance settings before it can start. Link the emulator or type its address.
• Duties · “Material composing” needs at least one of “compose count” set before it can run — pick one in this duty’s settings. A required setting is empty.
• “Northwatch” shares device 127.0.0.1:5555 with “Silverpine”, which is already running — two instances can’t drive one emulator. Give each instance its own emulator.
• A task that walks to buildings has no city map: the row ends with Open City Mapper to finish the map.
• “Northwatch” is on Office PC — move it to this PC to run it here. Move the instance on the Instances page; see Your PCs.
• Last start failed: the emulator closed before the game finished loading. The last Start stopped on the way, and the row says why. It is only a warning: fix the cause, such as opening the emulator, and press Start again. The row goes away after a start that works.

When you press Start with a gap

If a blocker is open, Start opens Needs setup before starting instead of starting. It lists each blocker. A warning never stops a start: warnings appear under Heads-up (won't stop the start):. Evonex checks again every time you press Start.

123412341234

1. 1The list Names each blocker, then the warnings that will not stop the start.
2. 2Cancel Closes the window. Nothing starts.
3. 3Start anyway Starts with the gaps still open. Whatever can run does run; blocked tasks and duties are skipped until you fix them.
4. 4Open setup Does not start. Takes you straight to the fix for the first blocker.

The first Start: rest breaks

The first time you press Start inside an instance, Evonex asks Add human-like rest breaks? Running non-stop around the clock is the least human-like pattern, so Evonex offers short breaks.

121212

1. 1Add rest breaks Turns rest breaks on, with a break every few hours and quiet hours overnight.
2. 2Not now Keeps rest breaks off. Evonex does not ask again for this instance.

• Add rest breaks turns on two parts: a rest of 30 minutes after about 4 hours of play, each varying by up to 20 %, and quiet hours from 02:00 to 08:00 every day. During a break Evonex closes the game, not the emulator.
• Not now keeps rest breaks off.
• Evonex asks once per instance, only when you press Start inside the instance (not Start on the Instances page), and only while rest breaks are off.
• Fine-tune or turn breaks off any time in Instance settings ▸ Rest breaks.

The Activity Monitor

The Activity Monitor is a live log of this instance. Each run of a task or duty is one card, newest first. The run in progress sits on top.

123456712345671234567

1. 1Runs at a glance Shows one mark per run, oldest first. Hover a mark to see which task it was; click it to jump to the run.
2. 2All tasks Limits the list to one task or duty.
3. 3All · Done · Issues Shows every run, only runs that went fine, or only real failures.
4. 4Search activity… Finds any text: a task name, a headline, a step.
5. 5Clear Hides every run logged so far. New activity still appears.
6. 6Trash Deletes this instance’s history and logs for good.
7. 7A run card Opens and closes one run. It shows the task, what happened and how long ago.

1. 1Runs at a glance Shows one mark per run, oldest first. Hover a mark to see which task it was; click it to jump to the run.
2. 2All tasks Limits the list to one task or duty.
3. 3All · Done · Issues Shows every run, only runs that went fine, or only real failures.
4. 4Search activity… Finds any text: a task name, a headline, a step.
5. 5Clear Hides every run logged so far. New activity still appears.
6. 6Trash Deletes this instance’s history and logs for good.
7. 7A run card Opens and closes one run. It shows the task, what happened and how long ago.

1. 1All tasks Limits the list to one task or duty.
2. 2All · Done · Issues Shows every run, only runs that went fine, or only real failures.
3. 3Search activity… Finds any text: a task name, a headline, a step.
4. 4Clear Hides every run logged so far. New activity still appears.
5. 5Trash Deletes this instance’s history and logs for good.
6. 6Runs at a glance Shows one mark per run on a timeline of the day. Hover a mark to see which task it was; click it to jump to the run.
7. 7A run card Opens and closes one run. It shows the task, what happened and how long ago.

Read a run card

A card shows an arrow, a status symbol, the task’s name, what happened, a small tally, and the run’s length and age, such as 1m12s · 5m ago. Open it to see one row per operation, newest on top.

• The tally reads 2 / 4 while a counted run is live. Afterwards it lists the results that are not zero, such as 28 ✓ · 1 ○ · 7 ! · 15 ⌛.
• The running card and the newest failed card open by themselves once. After that, your clicks decide.
• A row that repeats on purpose folds into one row marked ×4. Repeated passes of a march task fold into one card that ends · 3 passes.
• A card draws its newest 50 rows. Show 50 earlier · N more at its foot draws the next 50. Show earlier activity at the very bottom loads 30 more runs. The list opens with the newest 30.
• Day labels such as TODAY, YESTERDAY and a date split the list when it spans more than one day.

Find a run

• All tasks limits the list to one task or duty.
• All, Done and Issues show every run, only the runs that went fine, or only the runs with a real failure. A stop you asked for is never an issue. The label carries a count, such as Issues · 2.
• Search activity… looks through task names, headlines and every step.
• ● Live appears only while a run is open. Click it to jump to that run.
• Some themes add a timeline or a day dial beside the list. It plots the same runs against the clock: hover a mark to name the run, click it to open the run.

Details: every step of one row

A row that recorded steps has a Details button. It opens Activity steps: numbered lines, newest on top, so line 1 is the first thing the bot did. Open a row that is still running and new steps appear at the top while you watch.

123451234512345

1. 1What it did Names the operation these steps belong to.
2. 2Copy Copies the whole trail, ready to paste into a report.
3. 3Numbered steps Lists what the bot did, newest on top.
4. 4Show earlier Loads up to 50 older steps at a time.
5. 5Close Closes the window.

A row without steps says No detailed steps were recorded for this one. When you report a problem, a copied trail helps; see Report a bug.

Clear, delete and how long history is kept

• Clear hides everything logged so far. New activity still appears. Evonex remembers it for each instance, even after a restart. It hides only here: the Plan’s reports and the Dashboard still count those runs.
• The trash icon deletes this instance’s activity history and its log files for good. That also removes its Plan reports and Dashboard history. It works only while the instance is stopped; otherwise it says Stop the instance first, then clear its history and logs. Evonex asks you to confirm first.
• Evonex keeps each run for 90 days. The steps behind Details are kept for 14 days; after that the run’s card stays, but its steps are gone. A run in progress and anything from the last day are never trimmed.

When the game loses its connection

If the game shows its no-connection sign during a task, the task waits. One row named Connection appears in that run: The game lost its connection — waiting for it to come back. When the game returns, the same row changes to The game is back online — carrying on. Drops that follow each other share the row and show ×2 instead of adding lines.

The row can also end like this:

• The game is still offline — carrying on: Evonex waited 120 seconds, then went on, because Restart if the game stalls is off.
• Stopped waiting for the game to come back: you stopped or paused the instance.
• The game did not come back while the bot waited: Evonex reopened the game. See Instance settings ▸ Shared device.

Problems?