Post-incident wrap-up #35
Slay the Spire 2
The most recent tracked incident was a negative warning alert triggered by sustained conditions. Across the visible window, the game added 1,480 reviews, the current 1-hour directional delta sits at 53, and the incident peak reached 76 in 1 hour. 1 earlier incident have already resolved.
Incident opened Mar 23, 2026, 6:00 PM and resolved Mar 23, 2026, 7:46 PM.
Peak tier reached: WARNING.
Reported score change during incident window: 0.0%.
Estimated time to peak: -740 m.
Estimated time to resolve: 1 h 46 m.
Before / after
Window from Mar 23, 2026, 6:42 AM to Mar 23, 2026, 10:42 PM.
Score before
77.0%
Score now
77.0%
Change
0.0%
Reviews added
1,480
Peak velocity
240/h
Composite impact score
low (31)Tier severity
+14
Review volume delta
+12
Peak velocity
+5
Score movement
+0
Resolution duration
+0
Likely cause ranking
Probabilities are heuristic and derived from approved tag assignments, classifier confidence, and editorial overrides.
100%
Sustained negative flow indicates prolonged audience dissatisfaction.
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 warning incident with 1,480 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 31/100 (LOW).
What are the most likely causes?
Patch Backlash 100%
Is it resolving?
Resolved after 1 h 46 m with stabilized current sentiment state.
How far did sentiment move from normal?
Score moved by 0.0 points, from 77.0% to 77.0%. Peak velocity reached 240 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 23, 2026, 5:40 AM
Peak pressure window
Peak tier reached WARNING.
Mar 23, 2026, 8:44 AM
Baseline divergence
1h direction velocity ran at 1.86x slot baseline.
Mar 23, 2026, 6:00 PM
Incident opened
Model opened a negative warning incident via sustained trigger logic.
Mar 23, 2026, 6:00 PM
Likely cause: Patch Backlash
Sustained negative flow indicates prolonged audience dissatisfaction. (alerts.trigger_type)
Mar 23, 2026, 7:46 PM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Recovery tracking
Forecast ETA to normalize sentiment: Now (HIGH confidence)
Velocity is already within the stabilization band, so sentiment appears normalized.
Time to peak
-740 m
Time to resolve
1 h 46 m
Score at start
77.0%
Score at worst
77.0%
Score drop
0.0 pt
Recovered +24 h
n/a
Recovered +7 d
n/a
Recovered +30 d
n/a
Sentiment stabilised
Yes
Alert timeline
Escalation history across active and resolved incidents for this game.
Started Mar 23, 2026, 6:00 PM
Peaked at warning severity
Mar 23, 2026, 6:42 AM
Incident opened at warning severity
Mar 23, 2026, 6:00 PM
Trigger: sustained
Resolved
Mar 23, 2026, 7:46 PM