If you've been wondering why Slay the Spire 2 patches feel a little slower than what you remember from the original, that's by design. Developer Mega Crit has officially confirmed it's moved to a fortnightly update schedule, cutting the patch frequency in half compared to the first game. The reason? Weekly updates were, in the studio's own words, "a lot of work so it really sucked."
Why the original's weekly grind wasn't sustainable
Mega Crit addressed the shift directly in a Steam blog post accompanying the latest beta branch patch. The studio acknowledged that players familiar with the first game's rhythm might notice the difference, but the explanation is straightforward: keeping up a weekly cadence for a small indie team is genuinely punishing.
"This may be a bit surprising as the first game patched weekly, but it was a lot of work so it really sucked," Mega Crit wrote. Refreshingly honest, and hard to argue with. Shipping a polished patch every seven days, responding to community feedback, testing changes, and avoiding regressions is a treadmill that doesn't stop.
The key here is that the decision isn't about doing less work overall. It's about doing better work with more breathing room.
What the two-week cadence actually changes for players
Mega Crit laid out the practical upside. A biweekly schedule means bigger, more considered changes per patch rather than a stream of small tweaks that can feel reactive and inconsistent. The studio also pointed out that beta players now get more time to actually absorb changes and form useful opinions before the next wave lands.
That last part matters more than it sounds. One of the recurring criticisms during Slay the Spire 2's early access period has been that changes moved from the Steam beta branch to the main build before the community had properly stress-tested them. The game's first major update triggered a spike of around 13,000 negative Steam reviews, with players frustrated by how difficult it had become to build satisfying combos. A slower patch loop gives feedback more time to breathe before anything gets locked in.
Slay the Spire 2 is currently in Steam Early Access. The biweekly patch schedule applies to beta branch updates, which eventually roll into the main branch.
The broader context: a rough start to early access patching
This schedule change doesn't exist in a vacuum. Slay the Spire 2's early access period has been eventful. The game's lifetime Steam review score dropped to 66% positive after that first major update, which pushed several weeks of beta changes into the main branch simultaneously. Players, particularly from the game's large Chinese audience, reacted strongly to how the difficulty had shifted.
Mega Crit has been transparent throughout, responding publicly to criticism and framing the situation as a learning process. The studio noted that progress "will not be linear" and that "no change is necessarily permanent." Slowing the patch cadence feels like a direct response to that turbulence, giving the team more control over what ships and when.
A small team making a deliberate call
It's worth remembering what Mega Crit actually is: a tiny studio. The kind of weekly patch output that the original Slay the Spire maintained during early access was impressive precisely because of that context. Sustaining it for a sequel with higher expectations and a more active community is a different proposition.
Slowing down to every two weeks is a practical call that most players should be fine with, especially if the tradeoff is patches that are more polished and less likely to trigger another review bomb. The Slay the Spire 2 guides community will have more time to actually document changes before the next set arrives, which is a net positive for everyone trying to keep up with how the meta shifts.
For players deep in builds right now, whether you're running Ironclad strategies or working through the spire with a different class, the biweekly rhythm means fewer surprise shake-ups to your go-to decks. Keep an eye on the Steam beta branch for what's coming next before it hits the main build.
