Post-incident wrap-up #8
Slay the Spire 2
The most recent tracked incident was a negative nuclear alert triggered by sustained conditions. Across the visible window, the game added 13,006 reviews, the current 1-hour directional delta sits at 229, and the incident peak reached 488 in 1 hour. 1 earlier incident have already resolved.
Incident opened Mar 20, 2026, 7:29 PM and resolved Mar 21, 2026, 3:19 AM.
Peak tier reached: NUCLEAR.
Reported score change during incident window: 0.0%.
Estimated time to peak: -131 m.
Estimated time to resolve: 7 h 50 m.
Before / after
Window from Mar 20, 2026, 10:06 AM to Mar 21, 2026, 3:07 PM.
Score before
89.0%
Score now
78.0%
Change
-11.0%
Reviews added
13,006
Peak velocity
1,188/h
Composite impact score
severe (88)Tier severity
+35
Review volume delta
+20
Peak velocity
+16
Score movement
+16
Resolution duration
+1
Likely cause ranking
Probabilities are heuristic and derived from approved tag assignments, classifier confidence, and editorial overrides.
Incident FAQ
Auto-generated summary designed for quick sharing, operations handoffs, and SEO-friendly incident context.
What happened?
Slay the Spire 2 entered a negative nuclear incident with 13,006 additional reviews in the tracked window.
How severe was it?
Incident reached nuclear severity, indicating maximum modeled pressure. Composite impact score is 88/100 (SEVERE).
What are the most likely causes?
Patch Backlash 100%
Is it resolving?
Resolved after 7 h 50 m with still elevated current sentiment state.
How far did sentiment move from normal?
Score moved by -11.0 points, from 89.0% to 78.0%. Peak velocity reached 1,188 reviews/hour.
Does it resemble a broader cluster?
No related incidents were detected across connected titles in the current comparison window.
External trigger timeline
Correlates model milestones with seasonal overlap and cause evidence to explain likely trigger context.
Mar 19, 2026, 12:00 AM
Seasonal overlap: Steam Spring Sale 2026
Official Steam seasonal sale.
Mar 20, 2026, 5:18 PM
Peak pressure window
Peak tier reached NUCLEAR.
Mar 20, 2026, 7:29 PM
Incident opened
Model opened a negative nuclear incident via sustained trigger logic.
Mar 21, 2026, 3:18 AM
Baseline divergence
1h direction velocity ran at 2.86x slot baseline.
Mar 21, 2026, 3:19 AM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Mar 21, 2026, 8:00 PM
Likely cause: Patch Backlash
Sustained negative flow pattern. (alerts + classifier v2 migration backfill)
Recovery tracking
Forecast ETA to normalize sentiment: Now (HIGH confidence)
Post-incident behaviour is close to expected baseline levels.
Time to peak
-131 m
Time to resolve
7 h 50 m
Score at start
81.0%
Score at worst
81.0%
Score drop
0.0 pt
Recovered +24 h
-3.0 pt
Recovered +7 d
n/a
Recovered +30 d
n/a
Sentiment stabilised
No
Alert timeline
Escalation history across active and resolved incidents for this game.
Started Mar 20, 2026, 7:29 PM
Incident opened at nuclear severity
Mar 20, 2026, 7:29 PM
Trigger: sustained
Peaked at nuclear severity
Mar 21, 2026, 2:54 AM
Resolved
Mar 21, 2026, 3:19 AM