Slay the Spire 2 Beta Patch v0.108.0: Modding Fixes, Multiplayer Cards, and the New Current Beta Anchor
Official v0.108.0 beta notes are now the active patch anchor, adding a large round of fixes, multiplayer card support, modding cleanup, and enough balance movement that older v0.107 build assumptions should be treated as retest material rather than current truth.
One-line conclusion
v0.108.0 is now the current beta anchor. Mega Crit uses this patch to push a broader package than v0.107.0: bug fixes, multiplayer additions, modding support cleanup, UX improvements, and targeted balance changes across multiple characters.
3 actions to do now
- Current beta scope: v0.108.0
- Patch posture: multiplayer additions, modding fixes, UX cleanup, performance work, and targeted balance changes
- Site action: move current-version routing first, then retest specific build assumptions second
Next questions to open
v0.108.0 is now the current beta anchor. Mega Crit uses this patch to push a broader package than v0.107.0: bug fixes, multiplayer additions, modding support cleanup, UX improvements, and targeted balance changes across multiple characters.
That is enough to trigger another freshness sync across the site. The safest move is to shift homepage, builds, patch hub, tier framing, and sitemap priority language onto v0.108.0 first, then keep deeper meta claims conservative until repeated runs confirm what the new multiplayer and balance layer actually changes.
Official source of truth: v0.108.0 replaces v0.107.0 as the current beta anchor
The operational fact is simple: the active official beta scope is no longer v0.107.0. It is now v0.108.0.
That matters because every patch hub, build summary, and tier framing page should begin from the newest official beta notes, especially when the patch includes both systems changes and fresh card content.
- Current beta scope: v0.108.0
- Patch posture: multiplayer additions, modding fixes, UX cleanup, performance work, and targeted balance changes
- Site action: move current-version routing first, then retest specific build assumptions second
What changed enough to matter in v0.108.0
The notes are not just another small balance nudge. Mega Crit adds a new batch of multiplayer cards across multiple classes, continues cleanup around modded saves and multiplayer version conflicts, and moves several cards, relics, enemies, and Doom interactions enough that old patch language should not stay frozen on v0.107.0.
That does not mean every build and tier page needs a hard rewrite today, but it does mean any page still presenting v0.107.0 as the current decision layer is now factually stale.
- General follow-up: end-of-turn/Doom ordering and Regen Potion interactions change edge-case outcomes
- Character touchpoints: Ironclad, Silent, Regent, Necrobinder, and Defect all receive concrete retest hooks
- Multiplayer touchpoints: new cards and co-op fixes justify keeping patch guidance adjacent to issue triage
Why the modding and multiplayer layer matters anyway
A big share of the notes is about modding, multiplayer state correctness, save behavior, and user-facing error handling. That matters because a lot of “did this patch change my run?” questions are really version-conflict, co-op, or mod-state questions in disguise rather than pure balance questions.
For the site, that means patch coverage should keep separating strategy changes from issue and environment changes instead of flattening everything into one generic patch recap.
- Use v0.108.0 as a version and retest update, not as proof that every tier call is settled
- Keep known-issues, patch notes, and build retest paths adjacent
- Treat multiplayer and modding notes as player-facing decision support, not just developer trivia
What this site should update now
The right minimum action is to publish one v0.108.0 current-patch analysis page and move homepage, builds hub, tier list hub, patch hub, and sitemap priority language onto the new version anchor.
That keeps the site current without pretending we already have enough run-proof to make sweeping new tier claims.
- Publish one current v0.108.0 patch analysis page
- Update homepage, builds, tier lists, patch hub, and news priority links to v0.108.0
- Keep deeper build and tier takeaways watchlist-first until more run evidence lands
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.