Early Access patches move the mod API quickly. A Workshop item can still be installed and silently fail to load if its manifest was written for the previous build.
Fixing Disabled Workshop Mods After a Patch
Verified field fixThe shortest safe order for this issue:
- Unsubscribe and resubscribe to the mod only after reading its supported game build.
- Remove duplicate local copies of the same mod from the game folder.
- Launch a fresh run before loading a modded save to confirm the base build works.
Check the Workshop ID, not just the mod name
The same mod can exist as a local folder and a Workshop subscription. Two copies may confuse the loader or load an old manifest. Compare the workshop content folder with the local mods folder and keep one supported installation path.
$workshop = "<Steam>/steamapps/workshop/content/2868840"
Get-ChildItem $workshop |
Sort-Object LastWriteTime -Descending |
Select-Object Name, LastWriteTime Test on a new run, then a copied save
Launch the unmodded game once after an update. If a new run is stable, enable one mod at a time and check the character-select screen. A modded save can contain references to content that was removed in the update, so never use the only copy of a long-running run for this test.
Field notes before you change the build
A Slay the Spire 2 mod list is a dependency graph, not a popularity ranking. Confirm that the loader and shared frameworks match the current game build before sorting content mods. A missing dependency can look exactly like a bad load order.
Back up the active profile and a save before disabling anything. If the game starts cleanly with frameworks only, add content back in small batches and test the same menu, dialogue, or world load after each one.
- Do not mix two mod-manager deployments over the same game folder.
- Do not delete a content mod without testing a copied save first.
- Do not paste a load order from a different game build and expect it to be stable.
Check it before you keep it
Disable every mod and launch a fresh run
0 / 5 completeKeep a known-good profile
Export the working mod list before the next patch. A short, documented stack is easier to repair than a folder full of files whose versions nobody recorded.
The line to keep
For an Early Access roguelike, the safest load order is a short list of explicitly updated mods and a backup of every run you care about.
Did this fix work on Patch Early Access 0.104 — balance and saves?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against Early Access 0.104 — balance and saves. Votes are local-only telemetry.
Slay the Spire 2: bench questions
2 answersWhy does the Workshop show my mod as subscribed but the game ignores it?
Can a removed mod corrupt an existing save?
Modding & Load Order
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
Slay the Spire 2: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Slay the Spire 2 on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Custom.
Slay the Spire 2: Shader Stutter, Frame Pacing & Custom Config Tuning
A measured stutter-hunting routine for Slay the Spire 2: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Custom settings file to edit.
Slay the Spire 2: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Slay the Spire 2 without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.