Slay the Spire 2 thematic background
Back to News
UpdateSteam News2026-05-307 min

Slay the Spire 2 May Bug Fixes: Main Branch Stability Push After the Beta Cycle

Official May 30 bug-fix notes bring a large set of beta-branch fixes onto the main branch, with stability, controller, Linux, event, relic, and multiplayer corrections rather than a fresh balance reset.

One-line conclusion

May Bug Fixes is not a new balance patch. Mega Crit explicitly frames it as a main-branch bug-fix push that brings many beta fixes over to the live branch.

3 actions to do now

  • Branch meaning: main branch catches up on bug fixes from beta
  • Best use: troubleshooting, stability checks, and issue-status confirmation
  • Do not treat this page as a new balance headline by itself

Next questions to open

May Bug Fixes is not a new balance patch. Mega Crit explicitly frames it as a main-branch bug-fix push that brings many beta fixes over to the live branch.

That makes this page useful for troubleshooting and branch-status clarity: if a player is still on main branch, this is the note that tells you whether a crash, controller issue, Linux problem, or event bug may already be resolved.

Official source of truth: this is a stability pass, not a new meta pass

The main thing to get right is branch interpretation. These notes are about shipping fixes from beta into main, not announcing a fresh theorycrafting season.

That means the right use of this page is issue triage, branch clarity, and support routing before you start rewriting build advice.

  • Branch meaning: main branch catches up on bug fixes from beta
  • Best use: troubleshooting, stability checks, and issue-status confirmation
  • Do not treat this page as a new balance headline by itself

What players should check first

The official notes heavily emphasize general stability, controller behavior, Linux fixes, and navigation problems. There are also targeted corrections across Regent, Defect, relics, events, Ancients, and multiplayer.

For this site, the practical answer is to route affected players toward known-issues and patch pages before they assume an observed problem is still live.

  • General: crashes, input/navigation, settings saves, reward-flow issues
  • Regent: Summon Forth ordering fix is directly relevant to current play clarity
  • Multiplayer: multiple state and connection issues received follow-up fixes

This page is a quick-reference guide for players checking launch-week status, practical next steps, and the most useful follow-up links after release.