Preparing the interactive tool. Please wait; the guide and worked examples remain available below.
Check the save context before calling it a wipe
In the documented v0.108.0 beta behavior, unmodded and modded progress use separate save contexts. Mega Crit says the first launch with mods copies unmodded saves into modded saves and shows a notice; after that, progress in either context is not reflected in the other. This statement is tied to that beta note; later builds may change the workflow.
- Record whether the session you want is modded or unmodded and whether mods are currently enabled.
- Check the game's visible save/run list under that state before starting a new run or replacing anything.
- If the expected entry is absent, check the active Steam branch and consult later official notes; do not assume the other context has been overwritten.
- Avoid deleting files or repeatedly creating new runs as a troubleshooting experiment. This guide does not prescribe file-level edits or claim a recovery method.
References: Mega Crit: Slay the Spire 2 beta patch v0.108.0 · Mega Crit: October 2026 Neowsletter
Preflight a modded co-op session
The same official beta note says players had encountered version conflicts in modded multiplayer and recommends using the same exact mods as teammates, particularly when they change gameplay. It is a recommendation from that patch note, not a guarantee that matching names alone ensures compatibility.
| Before inviting | Compare | If different or unknown |
|---|---|---|
| Branch/build | Steam branch and in-game version for each player | Agree on a branch/build before starting; re-check after updates |
| Mod set | Exact enabled mod names, versions and load state | Align the set, especially gameplay-changing mods, or try an unmodded session |
| Save context | Whether each player is launching with mods | Check the intended save/run list; modded and unmodded contexts were separate in the cited beta note |
| Reported error | Exact message, step and whether all players can reproduce | Capture the context and report through the game feedback tool when available |
References: Mega Crit: Slay the Spire 2 beta patch v0.108.0 · Mega Crit: October 2026 Neowsletter
Use the local context checker
The checker below compares only the choices you select. It cannot see your save files, Steam branch, installed mods, online lobby, player identity or current game version. Its result is a prompt for what to verify, not a compatibility test.
- Select the save/run context you intend to resume and the launch mod state.
- Choose Solo or Co-op; if modded co-op, compare your exact gameplay mods with the group.
- Follow the result as a checklist and confirm the actual save entry and lobby in game.
- If current behavior differs from v0.108.0, check the latest official patch notes before changing files or removing mods.
References: Mega Crit: Slay the Spire 2 beta patch v0.108.0 · Mega Crit: October 2026 Neowsletter
Send a useful report without inventing a diagnosis
Mega Crit's October newsletter says the in-game feedback tool gives the team more useful context and lets them sort issues; it recommends continuing to use that tool. Community discussions can help compare reports, but replies are user-generated and are not verified fixes.
References: Mega Crit: October 2026 Neowsletter · Slay the Spire 2 player discussions
Before you play
- Compare intended save context with current mod state.
- Confirm the branch/build before relying on v0.108.0 behavior.
- For modded co-op, compare exact mod sets, especially gameplay-changing mods.
- Use the game's own feedback route for reproducible issues when available.
Frequently asked questions
Did enabling mods delete my unmodded progress?
The cited v0.108.0 beta note says the modded and unmodded contexts are separate and describes an initial copy prompt. Check the intended context and current build before concluding progress is gone.
Do teammates need identical mods?
Mega Crit recommends the same exact mods for modded multiplayer, especially gameplay-affecting mods; matching names alone is not a compatibility guarantee.
Can this checker recover or inspect a save?
No. It only compares choices in the open page; it does not read, change, back up or recover game files.
Sources & revision notes
Editorial revision: November 5, 2026; not a gameplay test date. The reference notes identify source limits and version differences.
- Mega Crit: Slay the Spire 2 beta patch v0.108.0 (Official)
Official beta patch note dated July 2, 2026. It says modded and unmodded saves are separate, the first modded launch copies unmodded saves and explains this, and the team recommends the same exact mods for multiplayer, particularly gameplay-changing mods. This is a version-specific note, not proof that every current branch behaves identically.
- Mega Crit: October 2026 Neowsletter (Official)
Official developer newsletter, checked November 5, 2026. It describes beta v0.111.0 and a planned November 12 update, with Main expected to catch up to that beta; schedules and branch contents may change, so check the latest in-client build and official notes.
- Slay the Spire 2 on Steam (Official)
Mega Crit's Steam product page identifies the title as Early Access and describes up-to-four-player co-op. Checked November 5, 2026; platform availability and Early Access content can change.
- Slay the Spire 2 player discussions (Community)
External, user-generated Steam discussions; not reviewed or verified by GamerWin. Include branch, in-game version, platform, enabled mod names/versions and the exact action before posting. Do not include account details or save files containing private information.
November 5, 2026: added a dated mod/save and multiplayer preflight based on Mega Crit's beta notes. No save, mod or co-op session was examined.
How we research and correct guidesNo affiliate links or paid placement. Commercial disclosure.