Slay the Spire 2 Steam Workshop Mods and Save Guide

Current branch status: Steam Workshop support is available on the v0.107.1 main branch. The v0.108.0 beta improves first-time modded profile setup and multiplayer conflict messages, but those fixes are still beta-only.

Sources: official Major Update 2 / v0.107.1 announcement, official v0.108.0 beta notes, and the official Steam Workshop.

Slay the Spire 2 shipped with a mod loader, but Steam Workshop support turned mod installation from a folder-management task into a subscription workflow. The confusing part is no longer finding the files. It is understanding branches, profiles, and multiplayer compatibility well enough that a new character mod does not look like lost progress or a broken lobby.

How to install a Workshop mod

1. Open Slay the Spire 2 in your Steam Library.
2. Open the game's Workshop page.
3. Read the mod description, required dependencies, supported game version, and recent comments.
4. Select Subscribe. Steam downloads the mod automatically.
5. Launch the game and open the Mods area from the main menu.
6. Enable the mod and any required library mods.
7. Restart if the mod page or game asks for it.
8. Confirm the enabled list before starting a serious run or joining multiplayer.

Do not subscribe to twenty mods at once on your first attempt. Add one content mod and its dependencies, launch the game, and verify that a new run starts. A small test set makes conflicts much easier to identify.

Why your progress can look missing

Modded and unmodded play use separate progress. This is protective: a broken or removed mod should not corrupt the clean profile. Before v0.108 beta, opening the modded profile for the first time could look like a total reset because the new profile started empty.

The v0.108 beta changes that first-run experience. Existing unmodded progress is copied into the modded profile automatically, and a popup explains what happened. The two profiles remain separate afterward. Unlocking an Epoch, winning an Ascension level, or changing another progression value while modded does not update the unmodded profile.

Think of the first copy as a fork, not synchronization.

Main branch or beta branch for mods?

Main v0.107.1 is the safer default when a mod author lists main-branch support. Beta v0.108 is useful when you want the improved profile flow, new beta content, or a mod explicitly targets that version. It also carries higher compatibility risk because game code and data changed after the mod was published.

Check four places before changing branches: the mod description, pinned Workshop discussion, recent user comments, and dependency pages. “Updated recently” is less useful than a clear supported version.

Multiplayer setup checklist

Version conflicts are more common in modded co-op because four separate installations must agree. v0.108 adds more detailed mismatch errors and fixes intended to reduce conflicts, but Mega Crit still recommends using the same exact mods for gameplay-affecting content.

Before opening the lobby, compare:

• Main or beta branch.
• Game version shown on the menu.
• Enabled mod names.
• Mod versions and dependency versions.
• Load order if a mod author says order matters.
• Whether anyone has a local or manually installed copy in addition to the Workshop copy.

Cosmetic mods are less likely to affect simulation, but the safest troubleshooting step is still matching everything. If a lobby fails, disable all mods, confirm clean multiplayer works, then restore mods in small groups.

A safe troubleshooting order

1. Read the exact popup instead of repeatedly relaunching.
2. Confirm everyone uses the same branch.
3. Disable the most recently added mod.
4. Check whether every dependency is enabled.
5. Verify Workshop downloads have finished.
6. Test a solo run with the same mod set.
7. Test a clean multiplayer lobby.
8. Re-enable mods one at a time.

This sequence separates game-version problems from mod conflicts and network problems. Changing five things between attempts destroys the evidence that would identify the cause.

Backups are still worth doing

Separate profiles reduce risk but do not replace backups. Before switching branches or installing a large overhaul, close the game, let Steam finish syncing, and keep a dated copy of your save directory. Do not edit a save while the game is running or while Steam is actively syncing it.

If Steam Cloud reports a conflict, compare timestamps and file sizes before choosing a side. The newest timestamp is not automatically the correct state if a crash or empty profile was just written.

Which mods should a first-time player install?

Start with interface or information mods that do not rewrite balance. Learn the base card pool and enemy patterns before adding characters, relic packs, or large rule changes. Once you can explain why a run failed, content mods become much easier to evaluate.

The new Spire Builds database can cover many lookup needs without modifying the game. Use it for card text, relic effects, and monster patterns, then add an in-game overlay only if you genuinely prefer that workflow.

FAQ

Did mods delete my progress?

Usually no. You are likely looking at a separate modded profile. v0.108 beta copies clean progress into it on first use and explains the separation.

Do the profiles sync later?

No. Modded and unmodded progress continue independently after the initial copy.

Can friends use different mods?

Gameplay-affecting mod lists and versions should match. Use the same game branch as well.