Saving progress without losing your fallback

A useful save routine gives you a way back when a session, setting change or device move goes wrong.

Keep more than one checkpoint

If your edition provides multiple manual slots, rotate between at least two. Save normal progress in one and keep another as a known working checkpoint. Before a major change, avoid overwriting every slot in the same session.

Confirm before you close

Wait for any save indicator to finish, then check the load menu for the expected slot. When testing a new setup, load the save once before relying on it. Do not force the game to close while it is writing data.

Back up files carefully

On a platform that allows save-file access, close the game first. Locate the save directory using documentation for your exact edition rather than guessing a path. Copy it to a separate folder with a date and edition label. Preserve the original files until you have confirmed the backup is readable.

Cloud synchronization needs a check

If your platform supports cloud saves, allow synchronization to finish before switching devices. A cloud copy is convenient, but it can also synchronize an unwanted change. Keep an independent backup where the platform allows it.

Do not assume editions share save formats

Before moving a save, check whether the source and destination editions are compatible. Make a copy of both sets before any replacement. If the game rejects a save, restore the known working files instead of repeatedly overwriting them.

A simple session checklist

• Save after meaningful progress.
• Keep one older slot that loads correctly.
• Back up before modifying files or changing devices.
• Confirm synchronization or copying has finished.

See getting started for initial setup and the FAQ for edition questions.