Slay the Spire 2 developers explain how its patching methods work to new players

Slay the Spire 2 has leapt out of the gate in Early Access, drawing big player numbers and plenty of attention—both cheering and jeering. Its first big balance pass, which targeted some runaway “endless combo” setups, sparked heated debate and a surge of negative user reviews. In response, the studio laid out a clear roadmap for how updates will roll out and why the process can feel bumpy from the outside.

For many, this is their first time seeing a live, evolving build of a Slay the Spire game. The team emphasized that Early Access is a collaborative workshop, not a straight line to 1.0. Here’s the gist of how they’ll operate while Slay the Spire 2 is in development:

• Changes are driven by three inputs: community feedback, in-game and backend data, and the designers’ long-term vision for how runs should feel.
• Player reports sent through the in-game tool are especially valuable, since they capture reactions from people actively testing the latest changes.
• The “beta” branch is where the wild experiments live. It will receive frequent, sometimes dramatic shifts. Once those settle, updates migrate to the main branch.
• Nothing is sacred. Numbers, cards, relics, encounters—any of it can change, and sometimes be changed back. Expect iteration, not finality.
• This cycle will continue for the next year or two, with the aim of reaching a refined balance on par with the original Slay the Spire at its best.

One sticking point has been the removal or weakening of certain degenerate loops. The studio’s stance is that leaving a single solved path to victory undermines the entire roguelike deckbuilding arc. Variety and discovery beat a one-click win, even if that means some beloved power plays get trimmed along the way. In exchange, other strategies should rise as tuning continues.

If you’re worried about waking up to a different game every week, you don’t have to participate in the betas. The main branch remains the steadier option. Opting into the beta requires switching branches via your platform’s settings for the game, and doing so is entirely optional. Those who enjoy chasing the meta and providing feedback can jump in early; those who prefer a more settled experience can wait for changes to filter into the primary build.

The developers also cautioned newcomers not to treat any single patch as the final word. Balance work in a system as interlocked as Slay the Spire is a push-and-pull: you adjust one outlier, a new one emerges; you buff a weak archetype, an unforeseen combo appears. That ebb and flow is part of the process, and community testing helps surface edge cases quickly.

Practically speaking, here’s what that means for players right now:

• If you love stability, stay on the main branch. You’ll see fewer surprises and more polished updates.
• If you want to help shape the game, try the beta branch and use the in-game report feature to highlight bugs, balance issues, and confusing interactions.
• Don’t get too attached to a single powerhouse deck. Today’s nerf might be tomorrow’s rework, and today’s underdog could be next week’s standout.

Slay the Spire 2 is still early in its lifecycle, and the team clearly wants to preserve the thrill of experimentation rather than let the community solve the meta months before launch. That means some patches will feel great, others might sting—but the goal is a healthier, more varied climb in the long run.

For players who were around during the first game’s Early Access era, much of this will sound familiar. For everyone else, consider this a peek behind the curtain: a living, breathing deckbuilder only reaches its final form through a lot of iteration, a lot of data, and a lot of candid feedback from the people playing it. If you’re along for the ride, buckle up—and if you’re not, the main branch will be there when you’re ready.