Disaster Response Systems
Salt dust storms, heatwaves, and system failures should teach resource redundancy rather than punish blindly. The briefing connects gameplay-facing systems to Mission Control language so future UI and game text can stay consistent.
System Role
This system should always explain what the player can do, what limit they are pushing against, what can fail, and how the result enters sector or planetary records. It should not read as an isolated stat.
Player-Facing Questions
- What resource or risk does the system expose?
- Which building, event, or technology changes it?
- What tradeoff appears when the value improves?
- Which global indicator or chronicle record should reference it later?
Writing Rule
Keep the text concrete: threshold, deficit, redundancy, maintenance, delay, and consequence. Avoid fantasy phrasing, pure upgrade language, or claims that one action solves a planet-scale problem.
