Guía de la rama beta: cómo unirse, parches quincenales, quién debería cambiar

Starting with v0.105.0 on May 7, 2026, Mega Crit officially moved Slay the Spire 2 from a weekly patch cadence to a bi-weekly one. The team's reasoning was simple: the first game patched weekly, but it was a lot of work and left little room for bigger changes or polish.

In practice this means three things. First, each beta drop will be larger and contain more substantial reworks. Second, the gap between a beta build and the main-branch rollup will be more predictable. Third, hotfixes (like v0.105.1) will still happen quickly when something is genuinely broken — the cadence change applies to feature drops, not emergencies.

As of this writing, the beta branch is running v0.105.1 (May 8, 2026), which includes v0.105.0 plus the same-day hotfix. The main branch is still on the post-v0.104.0 live build from late April.

The headline differences if you switch to beta: Doormaker is gone and Aeonglass is the new Act 3 boss; the Bestiary screen exists in the Compendium; Defect is meaningfully buffed across Lightning Orb cards; Regent's Sword Sage now grants Sovereign Blade Replay 1; three new Neow relics are in the pool; and several enemy and multiplayer bugs are fixed.

On Steam, right-click Slay the Spire 2 in your library, choose Properties, switch to the "Betas" tab (sometimes labeled "Game versions and betas"), and select the beta branch from the dropdown. No password is required. Steam will download a small delta and put you on the beta build the next time you launch.

To opt back out, return to the same tab and select "None" or the default branch from the dropdown. Steam will revert your installation to the main branch on next launch. Saves are generally compatible, but Mega Crit recommends not running the same save back and forth between branches mid-run — finish or abandon current runs before switching.

Mega Crit explicitly recommends that controller and Steam Deck users switch to the beta branch right now. The team is actively chasing crashes around selection screens that show up almost exclusively on controller / Deck input, and having more players on beta makes those crashes reproducible and fixable. If you primarily play on controller or on a Steam Deck, you are exactly the audience the studio is asking for help from.

Beyond that, switch if you want the latest content (Aeonglass, Bestiary, the Defect buffs) and you are comfortable with the trade-offs: less stable, occasional new bugs, and intent or icon issues that get hotfixed within days. Stay on main if you are running streams, contributing to leaderboards on the stable build, or you simply prefer a less churn-heavy experience.

The biggest practical risk is bugs that survive a beta drop's first day. v0.105.0 launched with a wrong Aeonglass intent icon and broken boss music; v0.105.1 fixed those within 24 hours. That pattern is typical — expect at least one hotfix per major beta drop, usually within the first few days.

Save compatibility is generally fine. The studio supports moving between branches at the meta level (between runs). Mid-run switching can produce edge-case desyncs, especially in multiplayer where host and client must be on the same build. If you co-op, coordinate with your group so everyone is on the same branch.

Under the new cadence, the next beta drop should land roughly two weeks after May 7 — that is around May 21, 2026, give or take a few days. After it stabilizes, expect a main-branch rollup that combines v0.105.x with whatever ships in the next beta cycle, similar to how April's v0.103.2 rolled up all the v0.100–v0.103.1 beta work at once.

Practically: if you switch to beta now, you ride one or two beta cycles ahead of main. If you stay on main, you will probably get this content as a single, larger update sometime in early June 2026.