Mechanics

The loop, the fleet, the resources and how a night is scored.

Articles in this section

• The game loopThe thirty-to-ninety-second loop behind every SysAdmin Crisis night: watch, diagnose, act and confirm. Learn the four movements repeated until sunrise.
• Servers and the fleetThe five server roles in SysAdmin Crisis, the processes they run, the thresholds that colour their status and how the rack grows over the campaign.
• ResourcesThe four resources in SysAdmin Crisis: budget, bandwidth, uptime and reputation. See what each is for, how it is spent and which one survives the night.
• Incidents at a glanceHow SysAdmin Crisis picks incidents: seven types plus one variant, when they arrive and how many can run at once, each with a log signature.
• Escalation and SLA debtHow ignoring an incident costs uptime in SysAdmin Crisis: escalation, SLA debt and a grace window that shrinks with every night of the campaign.
• Scoring and gradesHow SysAdmin Crisis scores a shift: the formula, the five grade thresholds and where the points come from. A lost shift is not graded at all.
• DifficultyWhat the easy, normal and hard levels change in SysAdmin Crisis, and what they deliberately leave alone. Each one adjusts a few specific things.
• Determinism and seedsWhy the same seed gives the same night on every device in SysAdmin Crisis: how the simulation stays deterministic and what that buys you as a player.