Choose the safe migration path
| Save origin | Working assumption | Recommended action |
|---|---|---|
| 0.9.9 stable or older pre-Unstable save | Official Unstable notes say old saves do not work after the configuration rework | Back up the old folder and start a new 1.0 campaign |
| Early Unstable beta save before its planned wipe | The beta announcement warned that at least one wipe was planned | Check the exact beta build and patch notes; do not assume compatibility |
| Post-wipe Unstable beta save | Developers expected beta saves to remain playable in full 1.0 if no urgent issue appeared | Back up, update, and verify the campaign before deleting the old copy |
| Fresh version 1.0 save | Uses the release data baseline | Continue normally and keep periodic backups |
| Modded or edited save | Mods can add an independent compatibility problem | Record the mod list, preserve the complete folder, and verify every required mod |
OFFICIAL GAMEPLAYBack up before opening the save in a new build
- 01
Close Quasimorph
Do not copy or replace campaign files while the game is writing to them.
- 02
Open the LocalLow save location
Start at %USERPROFILE%\AppData\LocalLow and find the Magnum Scriptum Quasimorph folder used by the installation.
- 03
Copy the complete folder
Use a dated backup outside LocalLow so saves, settings, and supporting files remain together.
- 04
Record branch and build
Note whether the save came from stable, Unstable beta, or release and record the visible version string.
- 05
Test a copy after updating
Load the campaign, inspect storage, ship upgrades, missions, and story state, then exit and reload once before trusting the migration.
What the Unstable beta announcement confirmed
The official announcement said the large configuration rework required a wipe and that old saves would not work. It also said saves started during the beta were expected to remain playable in the full 1.0 release if no urgent need appeared, but explicitly warned that at least one wipe during the beta was planned.
Those statements are not contradictory: an old stable save, an early beta save, and a later post-wipe beta save are three different migration cases. The branch and build that created the campaign matter more than the date on the file.
Do not continue when migration symptoms appear
Missing storage, reset ship upgrades, broken mission state, absent story messages, invalid items, or repeated load errors are reasons to stop. Repeatedly saving over the campaign can turn a reversible compatibility test into permanent data loss.
Restore the untouched backup, disable incompatible mods only according to their documentation, and compare the exact source and destination builds. A new 1.0 campaign is safer than forcing an unsupported old save through changed data tables.
Avoid these migration mistakes
- Assuming every file labeled beta was created after the final planned beta wipe.
- Deleting the old folder immediately after one successful load.
- Testing with mods enabled without recording their versions and dependencies.
- Copying only one visible save file instead of the complete game folder.
- Treating a community success report from another build as a guarantee for the current campaign.
FAQ
Frequently asked questions
Do I need a new save for Quasimorph 1.0?
Use a new campaign for old pre-Unstable stable saves. A post-wipe Unstable beta save may be compatible, but preserve a full backup and verify its exact build before relying on it.
Will an Unstable beta save work in 1.0?
The developers expected beta saves to remain playable at release if no urgent conflict appeared, but also planned at least one beta wipe. Compatibility depends on when the beta save was created.
Where should I back up the save?
Close the game, copy the complete Quasimorph folder under %USERPROFILE%\AppData\LocalLow\Magnum Scriptum or Magnum Scriptum Ltd, and store the dated copy outside LocalLow.
Is this save compatibility guide current for Quasimorph 1.0?
The page uses 1.0 as its baseline and labels older or uncertain details. Check the update line and linked sources before relying on exact numbers.
Does this site copy the official wiki?
No. It summarizes and organizes verified facts for specific search questions, then links the original sources so readers can audit details.
Research trail
Sources and further reading
Official mission progression, difficulty, economy, UI, class, mercenary, implant, and balance changes.
02 · OfficialQuasimorph on SteamOfficial game description, release details, features, controller support, and Steam Deck status.
03 · CommunityHow to Save Your GameCommunity-confirmed Windows LocalLow save directory and backup approach.
04 · CommunityQuasimorph 1.0 save questions — Reddit discussionLaunch-day questions about corrupted saves, whether a new save is required, and the need to separate old stable saves from the 1.0 release.