Trader Save Corruption and Backup Recovery

The percentage-based Trader save-corruption bug was fixed in v1.0.6. It could create a floating-point error while buying or selling with percentage buttons, leave the problem unnoticed during play, and reveal the unusable save only on the next load.

The same patch added automatic backup fallback. When the current save state is unusable, the game looks for a valid backup and reverts to it. That can cost some recent progress, but it is designed to avoid losing the entire save.

Current status

Use this recovery order

1. Confirm the installed version. Update to v1.0.6 or later before testing the old percentage-trading symptom. The current reviewed release is v1.0.8.
2. Close the old build completely. Let the game update before loading the affected save again.
3. Allow the automatic validation to run. If the current state is unusable and a valid backup exists, the game should select that backup without a manual file change.
4. Inspect the recovered point. Check recent Trader inventory, resources, tasks, and Map progress so you know what partial progress was rolled back.
5. Save the reproduction details. If the current build still cannot load, record the version, the last percentage buy/sell action, and what appears at load before trying anything destructive.

Distinguish fallback from a new regression

• The save opens at an older point: this is consistent with a valid backup replacing an unusable latest state. Verify the rollback and continue from the recovered state.
• The problem follows percentage trading on a build older than v1.0.6: update first; the identified source was fixed in v1.0.6.
• The same percentage sequence corrupts a current build: treat it as a new regression and report the exact sequence.
• The save problem follows an unrelated crash or shutdown: do not assume the Trader fix explains it. Use the broader launch troubleshooting checklist.

For the version timeline, read Updates and Patch Notes. If the recovered save has missing item or Trader discovery questions, continue with the Databank and Blueprint checks.