Post-incident wrap-up #40
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,012 reviews, the current 1-hour directional delta sits at 32, and the incident peak reached 32 in 1 hour. 1 earlier incident have already resolved.
Incident opened Apr 4, 2026, 3:03 PM and resolved Apr 4, 2026, 3:47 PM.
Peak tier reached: WARNING.
Reported score change during incident window: 0.0%.
Estimated time to peak: -61 m.
Estimated time to resolve: 44 m.
Before / after
Window from Apr 4, 2026, 4:02 AM to Apr 4, 2026, 8:28 PM.
Score before
81.0%
Score now
81.0%
Change
0.0%
Reviews added
1,012
Peak velocity
147/h
Composite impact score
low (25)Tier severity
+14
Review volume delta
+8
Peak velocity
+3
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,012 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 25/100 (LOW).
What are the most likely causes?
Patch Backlash 100%
Is it resolving?
Resolved after 44 m with stabilized current sentiment state.
How far did sentiment move from normal?
Score moved by 0.0 points, from 81.0% to 81.0%. Peak velocity reached 147 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 30, 2026, 12:00 AM
Seasonal overlap: Steam House & Home Fest 2026
Official Steam themed fest.
Apr 4, 2026, 2:02 PM
Peak pressure window
Peak tier reached WARNING.
Apr 4, 2026, 3:03 PM
Incident opened
Model opened a negative warning incident via sustained trigger logic.
Apr 4, 2026, 3:03 PM
Likely cause: Patch Backlash
Sustained negative flow indicates prolonged audience dissatisfaction. (alerts.trigger_type)
Apr 4, 2026, 3:46 PM
Baseline divergence
1h direction velocity ran at 12.80x slot baseline.
Apr 4, 2026, 3:47 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
-61 m
Time to resolve
44 m
Score at start
81.0%
Score at worst
81.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 Apr 4, 2026, 3:03 PM
Opened at warning severity
Apr 4, 2026, 3:02 PM
Trigger: sustained
Peaked at warning severity
Apr 4, 2026, 3:24 PM
Resolved from warning severity
Apr 4, 2026, 3:46 PM