Prevent Riots and Breaches

What Causes Class-D Riots

Riots erupt when Class-D happiness collapses—usually from ignored hunger, energy, and bathroom needs, but also from witnessing repeated deaths, overcrowded housing, and lack of Security visibility. The riot meter fills gradually, giving attentive directors time to intervene if they monitor alerts.

Overloading Class-D with back-to-back high-risk tests without breaks accelerates unhappiness faster than Safe-class routines. Balance dangerous assignments with downtime near amenities. Doctors and Medbay access reduce riot spikes after containment injuries.

Understaffed Security guarantees riots spread. One guard cannot cover multiple wings. Scale Security headcount with Class-D population, not only with SCP danger rating.

Security Stations and Task Force Response

Security personnel patrol between Security Stations you place near Class-D blocks and containment corridors. Stations expand coverage radius and shorten response times. Position them at choke points so rioters cannot reach Euclid wings unchecked.

Task Force units handle active riots and serious breaches when standard Security is overwhelmed. They cost more to maintain but end incidents faster, preserving research lines and preventing chain breaches. Deploy Task Force before riots fully ignite during yellow alert phases for best results.

Maintenance keeps doors and containment systems functional. Broken heavy doors during an Euclid test invite escapes that Security alone cannot plug.

Rotate Security patrol paths through amenity zones—not only cell blocks—so staff see guards during meals and breaks, a hidden morale stabilizer in beta builds.

Containment Breaches vs Riots

Breaches originate from SCP behavior, failed tests, or insufficient chamber tier. Riots originate from personnel revolt. Both can coincide—a riot during an active breach is the nightmare scenario Task Force exists to solve.

Upgrade chambers before upgrading test frequency. Euclid anomalies need researched containment options, not improvised Safe cells. Keter containment remains end-game for good reason; premature Keter testing wipes facilities.

After breaches, audit triangle connections and Scientist survival. Reconnect SCPs quickly to restore income without letting adrenaline rush you into skipping security reviews.

Containment foam and heavy door tiers vary by SCP entry—read each anomaly card before assuming one chamber template fits all Euclid captures imported from the wilderness.

Staff Happiness as Security Policy

Treat happiness metrics as security infrastructure. Cafeterias, restrooms, fair shift pacing, and visible Security presence cost Money upfront but prevent exponential losses from full-facility shutdowns. Beta NPC needs make this literal—not metaphorical.

Cross-train with our manage NPC needs beta guide for fixture placement and pod layout doctrine. Directors who master needs and connections first rarely need emergency Task Force spam.

Incident Response Playbook

When breach alarms sound, pause non-essential tests immediately to free Security pathing. Task Force deploys to the nearest choke point between breach origin and Class-D housing. Scientists not essential to suppression should shelter—losing senior research staff sets unlock timelines back days.

After incidents, run a post-mortem: Was breach caused by under-tier containment, overstressed Class-D, or missing Maintenance on doors? Fix root cause before resuming income pushes. Repeated identical breaches signal layout failure, not bad luck.

Public servers add chaos from unrelated player events near your wing. Single-player or private sessions help practice response drills without cross-traffic interference during beta learning.

Keep spare cash unallocated during Euclid weeks equal to one full Security payroll—emergency Task Force hires during double incidents drain budgets faster than most directors expect.

Schedule weekly layout audits even when no alarms fire—latent happiness decay accumulates invisibly until a single failed test triggers cascading riots.

Document which Security Station covers which wing in a notebook—beta expansions often outpace memory when floors multiply.