Slay the Spire 2 progress missing? Check before replacing a save

Rule out a different profile or modded save first

Write down the installed version and branch, Steam account, selected in-game profile, and whether mods loaded when the missing progress was earned. Compare those against the current session before touching a file. Mega Crit's beta notes describe separate modded and unmodded progress; an empty-looking modded profile can be a mode mismatch rather than corruption.

If the progress appears in the original mode or profile, stop here. Do not use the cloud-reset procedure to make two different progress tracks synchronize.

A missing Timeline Epoch has a separate Beta repair

Mega Crit’s July 30 Beta v0.110.0 notes identify an end-of-run Epoch that could disappear and block the Timeline. The developer says affected saves repair when loaded. This claim applies to that specific fault; it does not establish recovery for every locked node.

The repair is documented for Beta. This wiki’s Main v0.107.1 baseline does not establish that it includes the fix. Keep your branch recorded and preserve the affected save before testing; changing branches is a separate decision.

1. On an affected Beta profile, confirm the installed version includes v0.110.0 or later, then load that profile and inspect the missing Epoch.
2. Kingy recommends comparing a screenshot before and after loading, then restarting once to check that the result persists.
3. If it remains blocked, record the Timeline node, completed run, version, profile and mods for an F2 report. Continue to file recovery only if the separate corruption case below applies.

On Windows, make an untouched copy before recovery

If the same account, branch, mode and profile still shows lost or corrupt progress, locate the affected Steam account and profile under `%APPDATA%\SlayTheSpire2\steam\<Steam ID>\profile1\saves`. The developer post uses `profile1`; choose the actual affected profile rather than assuming every player uses that folder. Copy its entire `saves` directory to a separate safe location and keep the original `progress.save`, `progress.save.backup` and `progress.save.corrupt` files unchanged in that copy.

Confirm that a backup or corrupt file actually exists for the affected profile before proceeding. Its contents and age are not verified by the filename. If no candidate exists, preserve what you have and use the in-game F2 report instead of substituting another profile's file.

Follow the developer's order only for an applicable corrupt save

Mega Crit's Windows procedure is: open the game console with `~`, enter `cloud delete` twice (the first entry asks for confirmation; the second closes the game), and do not reopen the game yet. This deliberately deletes the Steam Cloud copy, so keep the separate file backup before running it.

In the affected profile's `saves` folder, move or rename the active `progress.save`; then rename either `progress.save.backup` or `progress.save.corrupt` to `progress.save`. Relaunch the game and inspect the progress before discarding any preserved files. Mega Crit says this order should keep Steam Cloud from overwriting the replacement, but it cannot guarantee the backup contains the progress you want.

The pinned post also links a third-party rebuild script but explicitly does not guarantee its safety. Kingy has not tested or endorsed it. The pinned post provides no equivalent save-replacement procedure for macOS, Linux or Steam Deck; use the in-game F2 report for those cases rather than guessing a path or transferring these Windows steps.