Dashboard — Evonex guide (Evony bot)

Dashboard

The watch floor — every instance and its game day in one place, and the one sentence worth acting on.

The Dashboard answers one question: is my fleet working, and if not, which instance and why. It says so three ways — what is true right now, what each instance did today, and what the day produced — and it isn't read-only: every instance has its own Start / Stop, and a guarded Stop all halts the whole fleet.

Evonex opens on the Dashboard, and it refreshes every two seconds while it is on screen. Each theme lays it out its own way over the same facts: Aurora stacks cards, Prism sets a three-column deck, and Standing Watch plots the fleet's day on a radar beside a ledger.

The Dashboard: the fleet right now, every instance's game day, today's runs and take, and This PC.

Set it up

Create at least one instance — see Create your first instance.
Press Start on an instance's row, or start it from its workspace.
Read the verdict; click it, or any instance, to open that instance.

What every Dashboard shows

The three layouts read the same facts, word for word. What they say:

Headline

3 of 5 working — how many instances are running out of how many exist. With none yet: No instances yet.

Conditions

Every instance counted into one of four: WORKING (green) — running; WAITING (blue) — resting, yielded, recovering, paused, or waiting for another instance to free its emulator, all temporary; ATTENTION (red) — an error or a refused Start; OFF (grey) — stopped.

Verdict

The one sentence worth acting on. It names the first instance in the worst state — an error first, then a setup gap, then a pause — with the reason, such as Ember Keep — has no emulator / device address set — set one in Instance settings before it can start. or Silverpine is paused; click it to open that instance. When all are running it reads All 5 working (or Working for one); with nothing running, Nothing is running — start an instance to begin; with no instances, Create an instance on the Instances page to get started. When some are working and the rest are simply switched off, it says nothing.

Stop all

Stops every live instance. Greyed, never hidden, while no instance is working. How it guards against a stray click is the theme's — see each layout below.

Each instance

Its state, what it is doing now — the task it is on (with a count such as · 2/5 when it works through several items), Waiting — … with the reason, On an anti-flag break, Yielded to you, Recovering the game…, Paused, Idle, or the reason it stopped — its runs since the reset, its last contact, and its own Start / Stop. Click anywhere on it except the Start / Stop to open the instance. The Dashboard does not knock on emulators, so a stopped instance reads Stopped here rather than Ready or Offline.

Last contact

The time the instance last finished anything, with a mark for how long ago: filled under 15 minutes, half under an hour, hollow under four hours, faint beyond that. On a fleet left running overnight it is the quickest way to spot the one that stopped reporting.

The game day

Every run since the daily reset (00:00 Pacific time), at the time it started, on one clock all instances share — so a quiet instance shows as a gap beside the runs its neighbours made at the same time. Runs are coloured by how they went: green fine, orange with a warning, grey skipped, blue stopped, red failed, hollow when the ending was never recorded. Hover a run for its start time, task and length; click it to open that instance. Nothing is drawn ahead of now — the Dashboard shows what happened, never a forecast.

Today's runs

Every run since the reset, newest first, with its counts — 12 runs · 10 ok · 1 issue · 1 stopped. Only finished runs are counted, so the parts add up to the total; a run still going is listed but not counted. Each row has a mark (● running, ✓ fine, ✕ failed, ⊘ stopped, ○ never recorded), the time it started, the task, the instance, what it did, and how long ago. No runs yet this game day. before anything has run.

View full report

Opens the Report window — see below.

Today's take

What the fleet actually produced today, added up across every instance and task — for example Ymir Lv6 ×30. Only things that happened count; skipped or failed lines never do. +N more kinds opens the full report; Nothing itemised yet this game day. is shown instead of a row of zeroes.

This PC

How hard this PC is working — CPU, RAM and, when it can be read, GPU — judged by the busier of CPU and GPU: green normally, orange from 60%, red from 85%. Then the machine — processor, memory, graphics card, free disk — and a rough estimate of how many emulator windows it drives comfortably, such as ≈ 6 emulator instances comfortably (limited by RAM). The estimate keeps about 4 GB of memory for Windows and Evonex, then allows about 2 GB and two processor threads per emulator. Other readings: This PC is below the comfortable minimum for an emulator. and Capacity unknown — couldn't read system memory.

Aurora: stacked cards

Aurora stacks the Dashboard in four cards: the muster on top, one lane per instance across the game day, today's runs beside today's take, and This PC along the bottom.

Muster

The headline, the count in each condition present beside it — for example 3 WORKING 1 WAITING 1 OFF — a bar with one segment per condition, as wide as its share of the fleet, and the verdict under it.

⚑ GUARD / ▶ Stop all

Stop all in two clicks. The first click on ⚑ GUARD lifts the guard and shows ▶ Stop all; a second click within four seconds fires it. Left alone, it closes itself again.

INSTANCES

One lane per instance: a state lamp (it pulses while running), the name, the status pill and what it is doing on the left; the game day across the middle; the run count, the last-contact time with its triangle, Start / Stop and a chevron on the right. since … reset beside the heading says when this game day began, on your PC's clock.

Ruler

The day's start time at the left edge, RESET at the right, and clock times every six hours between (every twelve on a narrow window). A small accent mark shows now.

TODAY'S RUNS

The counts, View full report and the run rows; Showing the 80 most recent of today's runs. when there are more.

TODAY'S TAKE

The seven biggest results, and +N more kinds.

This PC

Everything on one line: the live load, the machine and the estimate.

Up to twelve lanes show at once; more scroll. On a narrow window the lanes, ruler, run counts and chevrons are hidden and the rows become a plain list — last contact and Start / Stop stay.

Prism: the deck

Prism sets the Dashboard as three columns: the fleet right now on the left, the day's lanes in the middle, and the record — today's runs over today's take — on the right.

Fleet · right now

A ring with one arc per instance, coloured by its condition (an attention arc drawn thicker), the headline in its centre — 3 over of 10 working — and the four counts under it as chips. Past sixteen instances the ring shows one arc per condition instead.

Verdict card

An error is a red card headed NEEDS YOU · WORST FIRST; a setup gap or a pause is an amber card headed WAITING ON. Click the card to open the instance. A calm verdict is a plain line under the chips.

Stop all

In the Fleet panel's header. It asks first: Stop every live instance? names each live instance, and offers Keep running (the default — Enter and Esc both keep the fleet running) or Stop all N.

This PC · live · 2 s

Three arcs — CPU, RAM, GPU — each with its value, a word (easy, busy, strained) and its hardware; free disk in the header; the estimate under them.

Instances

since … reset and a legend (ok · issue · stopped · unknown · in flight) in the header; the ruler with its start time, RESET and a NOW tag whose beam falls through every lane. Each row has the state mark, the name, the state in capitals with what it is doing, the lane, the run count over the last-contact time and its mark, then Start / Stop and open ›. A faulted row carries a red edge.

Today's runs

The settled count in large type with ✓ ok · ✕ issue · ■ stopped and a bar split between them, then the runs on a thread, newest first. View full report › in the header; N more today › opens the report when the list is cut.

Today's take · fleet-wide, summed

Up to six tiles, each a result over its count, and +N more kinds ›.

On a narrower window the right-hand column folds into tabs on the middle panel — Lanes · Runs · Take — and on a narrow one the left column narrows and the ring gets smaller.

Standing Watch: the watch plot

Standing Watch sets the Dashboard as a plotting room: the headline, the fleet as a ruled ledger and the day's record on the left, and THE WATCH PLOT — the whole fleet's game day on one radar — on the right.

Head

A1 · DASHBOARD, the headline as a sentence — 3 OF 10 WORKING. — and four condition plates: the count, a mark and WORKING, WAITING, ATTENTION or OFF. The attention plate is hatched red while it counts anything.

Verdict chit

An error is a card cocked at a slight angle with a red edge and an ATTENTION stamp: the instance's grid code and last contact (C-05 · LAST 20:14), the verdict, Open … › and WORST WINS. A setup gap or a pause is the same card, straight, stamped WAITING ON. Click anywhere on it to open the instance. A calm verdict is a quiet line.

FLEET

One ruled line per instance: SEEN (the last-contact mark), GRID (its code, C-01 and on), INSTANCE, STATE, RUNS, LAST, DOING NOW, then Start / Stop and open ›. Hovering a row lights its ring on the plot, and hovering a ring lights its row.

■ Stop all

In the FLEET header, beside ASKS FIRST: it opens the same question as Prism's — Keep running holds the default, Esc keeps running, and only Stop all N stops.

TODAY'S RUNS

The counts, View full report and ruled rows, newest first; N more today › when the list is cut.

TODAY'S TAKE · FLEET-WIDE · SUMMED

Up to six chips and +N more kinds ›.

THIS PC · LIVE · 2 S

A ticked meter per reading with its value and a word (calm, busy, strained), the hardware line and the estimate.

THE WATCH PLOT

One ring per instance, C-01 outermost, around a game day that starts at the reset at twelve o'clock and runs clockwise. The red sweep stands at now, and the swept part of the day is lit; nothing is painted ahead of the sweep. Every run is a contact at its start: a dot when fine, an orange dot with a warning, a red ✕ for an issue, a square when stopped, a hollow ring when its ending is unknown. A run in flight is a red arc into the sweep; a faulted instance's ring is struck through in red, and a waiting one carries a dashed orange arc. The hub shows the time TO RESET; the head names the game day; the legend sits under the radar. Hover a contact for its time, length and task; click it to open the instance. With more than twelve instances the rings become four condition bands.

On a narrower window the plot folds to a small scope beside the verdict, today's runs, take and This PC become three tabs, and the ledger lets its DOING NOW column give way first.

The Report window

Today / 7 days / 30 days

The window to report on. Default: Today, which here starts at midnight on your PC's clock; the others cover the last 7 or 30 days.

Instance cards

One card per instance, busiest first, headed with its name and 24 runs · 20 ok · 1 stopped · 3 issues.

Task blocks

Inside each card, each task with its run count and what it produced: a label, a count such as ×12 and a bar scaled to the task's biggest line — green for results, orange for warnings or skips, red for failures, and the theme's accent for a line with no outcome of its own. ran, nothing itemised when the task produced nothing to list; +3 more when more lines exist.

Empty window

No tracked activity in this window yet — once your instances run tasks, their achievements roll up here.

Closes the report.

How it runs

The page reads the fleet every two seconds while it is visible and stops when you leave it. It shows what happened — never a forecast. Start on an instance starts it straight away; if something is missing, a Needs setup message names it, the instance turns orange and the verdict repeats it. Stop — on an instance or through Stop all — ends each instance at its next step, and the runs it cuts are recorded as stopped (⊘), counted apart from real failures.

Examples

The morning check. Read the verdict first. Then run your eye down the last-contact marks: a hollow or faint one beside neighbours with filled ones is the instance that went quiet overnight, and its day shows the gap. Click it to open the instance and read its Activity Monitor.
Taking the game back for an hour. Use Stop all — in Aurora click ⚑ GUARD then ▶ Stop all within four seconds; in Prism and Standing Watch click Stop all and confirm Stop all N. Every instance stops at its next step. When you are done, press Start on each one.
Was the night worth it? Look at Today's take for the fleet total, then View full report ▸ 7 days to compare instances.

Stop all cuts any task in progress at its next step. Rallies or marches already sent in the game carry on; the bot simply stops tending them.

Troubleshooting

An instance reads Stopped although its emulator is open.

The Dashboard doesn't check emulators. Open Instances to see Ready or Offline there.

Stop all is greyed out, but an instance is paused or resting.

Stop all only arms while at least one instance is working. Stop a paused or resting instance with its own Stop.

An instance is running but nothing is drawn for it.

Runs appear when they finish. Check what it is doing, and open the instance to read the Activity Monitor.

There are grey ○ runs in the list.

Those runs never recorded an ending — usually Evonex was closed or the PC slept mid-run. They are not failures.

The Report's Today doesn't match Today's runs.

Today's runs start at the game's daily reset; the Report's Today starts at midnight on your PC. Around the reset they cover different hours.

My Dashboard looks different from the screenshots.

Each theme lays the Dashboard out its own way — pick yours with the guide's Screenshots picker. The words and numbers are the same in all three.

The capacity hint says Capacity unknown.

Evonex couldn't read this PC's memory. It is only an estimate — the live load is still accurate.