Dashboard — Evonex guide

Dashboard

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

The Dashboard is the landing page for your whole fleet, and it is built to answer one question: is my fleet working, and if not, which one and why. It says so three times over — what is true right now, what each instance did today, and what the day actually produced. It refreshes every 2 seconds while the page is open, and it isn't read-only: every row carries an inline Start / Stop, and a guarded Stop all can halt the fleet without opening a single workspace.

The muster

The strip at the top is the fleet in one line. The headline counts what is working (3 of 5 working), the bar under it shows how the fleet is made up, and each segment is one of four conditions: WORKING, WAITING (resting, yielded, recovering or paused — all fine, all temporary), ATTENTION (an error, or setup it is waiting on) and OFF.

Below the bar is the verdict — the single sentence on this page worth acting on. It names the one instance in the worst condition and gives the engine's own reason for it (Farm 2 — no emulator set), and clicking it opens that instance. When everything is fine it says so in three words; when some instances are simply switched off, it says nothing at all rather than nagging you about a choice you made.

The lanes

Every instance gets one row: a state lamp, its name, a status pill and what it is doing right now on the left — then its whole game day, drawn against a ruler shared by every other lane. The day runs reset to reset (the ruler names both ends), each finished run is a block toned by how it went, and one NOW cursor falls straight down through every lane.

That shared ruler is the point: an instance that went quiet at 3am is a gap sitting directly under the blocks its neighbours were still producing at the same minute. Hover any block to read the time, the task and how long it took; click one to open the instance that ran it. Nothing is ever drawn ahead of the cursor — the fleet keeps no forecast, and a plausible guess would still be a guess.

At the right of each row, last contact is the clock time that instance last finished anything, with a small triangle for how long ago: filled under 15 minutes, half under an hour, hollow under four, and a faint outline beyond. On a fleet left running overnight it is the fastest way to spot the one that stopped reporting.

A narrow window drops the lanes and leaves the plain instance list. A lane too short to separate one run from the next would be a smear, not an instrument.

Today's runs

The record, at run grain: every run since the game reset, newest first. Each line leads with a glyph — ✓ green (finished ok), ✕ red (failed), ⊘ blue (a manual or gate stop) or ○ grey (a run whose ending was never recorded, usually because the app was closed mid-run) — then the task, the instance, what it did, and how long ago.

The counts in the header describe the runs that have finished, so they always add up to the total beside them. A run still in flight is listed but counted by nothing, because it has no outcome to be counted as yet.

A stop is never a failure. Stopping a run yourself finalises it as stopped — the ⊘ blue glyph — so it is counted separately from real errors everywhere in Evonex.

Today's take

Beside the log is what the fleet actually earned today: every itemised achievement, summed across every instance and every task — Ymir Lv6 ×30. Only things that really happened are counted; a skipped or failed line never books as produce, and a day that made nothing shows nothing rather than a row of zeroes.

View full report opens the same data broken down per instance and per task, with proportional count bars and a Today / 7 days / 30 days range filter.

This PC

The line along the bottom is the host machine — live CPU, RAM and GPU load on the left, then what the machine is: CPU and core count, RAM, GPU, free disk, and a plain-language capacity hint for how many emulator windows it can comfortably drive before screen capture slows down.

Stop all

Stop all, on the right of the muster strip, halts every running instance at once. It sits behind a two-click guard — the first click lifts the guard, the second fires, and it re-closes itself if you leave it alone — so a stray click can't take down your whole fleet. It greys out when nothing is running.