Why Slay the Spire 2 Steam reviews turned Mixed again
Slay the Spire 2 pushed Major Update 1 to the main Steam branch on April 17, 2026. Instead of resetting confidence, the update pulled the game back into the same balance argument that had already driven one of the year's loudest Steam backlash cycles.
By April 18, 2026, the recent-review window on Steam was sitting in Mixed territory at roughly 53% positive from more than 63,000 recent reviews, even while the English-language score remained far stronger. That split matters because it shows a game can keep deep long-term goodwill while still behaving like a live trust problem in the recent-review layer.
The permanent tracking surface for that volatility is the Slay the Spire 2 game page, where incident history and review movement matter more than a single lifetime label.
Why this belongs in the patch-backlash cluster
This is not a normal content-patch disagreement. It is a recurring patch backlash story, where the same design-direction dispute keeps repricing public sentiment whenever a major update lands.
Roguelikes are especially exposed to this pattern because players are not only reacting to bugs or performance failures. They are reacting to changes in mastery. When a patch alters combo potential, route planning, or difficulty expectations, players often treat the change as a direct attack on the version of the game they already learned.
That is why balance disputes in games like Slay the Spire 2 can create Steam-review behavior that looks closer to a storefront protest than normal feedback. The review box becomes a public pressure system, not just a place to log opinions.
Complaint classification: Balance. The dominant player complaints center on design changes that alter combo potential, route planning, and difficulty expectations -- not bugs, performance, or monetization.
Why recent Steam reviews matter more than the lifetime score
The most misleading read here is that Slay the Spire 2 still has enough overall goodwill to ignore the flare-up. That misses the structural point. On Steam, recent reviews are often the first trust signal a potential buyer sees. If that box moves into Mixed territory, it changes the purchase context immediately.
This is where the article also belongs in the Steam review analytics cluster. Review velocity, score direction, and repeat incidents matter more than one stable all-time average. A healthy lifetime score can coexist with a weak present-tense trust signal.
Slay the Spire 2 now illustrates a bigger PC pattern: once a game develops repeat update anxiety, every new patch arrives under suspicion. That makes the next 48 to 72 hours more important than the patch announcement itself.
For the evergreen framework behind that reading, pair this article with How ReviewBomb Detects Steam Review Surges, What Is a Steam Review Bomb?, and the broader reports archive.
What happens next
The next meaningful test is not whether Mega Crit survives this patch. It almost certainly will. The real question is whether the studio can stop this from hardening into a chronic repeat-volatility pattern.
That usually requires:
- tighter follow-up tuning
- clearer explanation of design intent
- visible willingness to adjust unpopular changes
- a stronger sense that community feedback affects patch direction
If recent sentiment stabilizes, this remains a sharp but temporary backlash. If it does not, Slay the Spire 2 becomes one of the clearest examples of how a major Steam success can still be trapped by recurring balance distrust.
ReviewBomb verdict
This is not just another rough update. It is a repeat patch-backlash case where recent Steam reviews matter more than the lifetime label because they show the trust problem is still active. The dominant complaint classification is Balance.
Related incident data: compare this coverage with the tracked Slay the Spire 2 incident, where ReviewBomb keeps the review velocity and severity context attached to the live dataset.