Quick answer
📈 Chaos monitor
Pressure state board
Use the board to practise one short status call: rising, pressing, stable.
Pressure 45 · rising · press centre.
📈 Watch cue: assign one monitor → 🛑 lower the needle before danger → ✅ call “stable” → return to the main task.
Pressure is a Medium Chaos module. Its needle rises continuously; lower it by repeatedly pressing the centre button, then keep managing it until the bomb is defused. The reference lists a 4 × 2 footprint and a first fixed appearance at Level 6.
Assign one monitor
Choose one player to watch Pressure and announce only meaningful changes. Deaf can call the visible state, Mute can verify the manual instruction, and Blind can make the physical adjustment when the call is confirmed. Do not rotate this job every few seconds: continuity is more valuable than a second opinion.
When Pressure moves toward an unsafe state, pause the normal module callout and press the centre button repeatedly until the needle is back under control. Report “stable” or “still rising” so the rest of the team knows whether to resume.
Pressure priority calls
| Call | Meaning | Next action |
|---|---|---|
| Stable | The needle is controlled for the moment | Resume the normal module |
| Rising | The correction is not finished | Keep the monitor assigned and delay the next input |
| Critical | The team is close to losing the state | Stop all other calls and correct Pressure first |
| Unknown | Nobody can confirm the current state | Reread the panel before pressing again |
Do not invent a numeric threshold from a remembered run. The useful answer is the observed state and the next safe action; the current panel decides when the correction is complete.
Combine it with campaign planning
Pressure becomes much easier when the team knows the likely module mix. Use Level Lookup before a run, then review Alarm and Slider because they use the same priority rule: manage the interruption without losing the main bomb state. The role guide explains how to keep one caller responsible for the current hazard.
Common mistakes
- Waiting until the state is critical before calling it.
- Treating every small movement as an emergency and creating callout noise.
- Solving a normal module while nobody watches the Chaos panel.
- Making a correction without repeating the resulting state.
The reference lists 15 fixed appearances. Exact thresholds may be adjusted in later versions; use the live panel and current manual for final decisions.