On this page
No verified redemption system or active code is published.
Published data-folder paths
The developer’s bug-report instructions publish operating-system data-folder locations for ReStory. The practical answer is to back up the complete relevant folder before you rename, remove, or replace anything. Those instructions do not establish one universal filename that is safe to edit on every platform. Treat the path as a place to inspect and preserve, not as an instruction to edit a file immediately.
- Windows: %UserProfile%\AppData\LocalLow\Mandragora\
- macOS: ~/Library/Application Support/Mandragora/Restory/
- Linux / Steam Deck: ~/.local/share/Steam/steamapps/compatdata/3812600/pfx/drive_c/users/steamuser/AppData/LocalLow/Mandragora/
Folder capitalization and the exact files inside can vary. The developer post is the authority for these paths.
Safe backup procedure
A backup is most useful when it is made before the problem is changed. Close the game, let Steam finish any visible cloud synchronization, and copy the whole folder to a dated location that is easy to identify. Keep the original untouched so you can compare timestamps and restore it if a test makes the situation worse. Make a second copy before each separate experiment if the first test changes the folder, and write down which copy was active when you saw the symptom.
- 01
Close ReStory and wait for Steam Cloud synchronization to finish.
- 02
Copy the entire relevant folder to a new, dated backup directory.
- 03
Keep the original untouched; test a restore only with the game closed.
- 04
If Steam reports a cloud conflict, compare timestamps before choosing a copy.
Windows and macOS checks
On Windows, paste the published LocalLow path into File Explorer after closing ReStory. On macOS, use Finder’s Go to Folder command for the Application Support path, remembering that the Library folder may not be visible in the normal sidebar. Do not create a second folder with a guessed spelling if the expected directory is absent; record what you actually found and report it with the platform and version. Check that the folder’s modified time matches the session you are investigating, but do not delete older files merely because their names look unfamiliar.
Steam Deck and Proton checks
On Steam Deck, the published path sits inside the game’s Steam compatdata prefix and uses the Windows-style LocalLow location shown above. The path is tied to App ID 3812600, so do not substitute a different app ID from a similarly named game. Proton, Steam Cloud, and future updates can change what is present, so treat the live folder and the developer’s current instructions as the authority. If you move between desktop mode and another computer, close the game on both sides and wait for Steam to finish synchronization before comparing folders.
Cloud saves are not a replacement for backups
Steam lists Steam Cloud support for ReStory, but cloud synchronization is not the same as a manually dated backup. A cloud conflict can present two different timestamps, and choosing the wrong side can overwrite the state you wanted to preserve. Compare copies before launching again and make the decision with the game closed. A backup folder should remain outside the live save location so the game cannot mistake it for active data, and it should be named with the date and platform you used.
A reversible restore test
When you need to test a restore, keep the current folder as a second dated copy before putting an older copy in its place. Launch only after the replacement is complete, verify the expected save in-game, and close the game again before deciding whether the test helped. If the result is worse, restore the untouched current copy and report the original and test states separately; do not keep overwriting the same folder while troubleshooting.
Do not guess at filenames
The published locations answer where ReStory data is stored, not which file a player should rename. A folder can contain more than one kind of game data, and an unfamiliar filename may be part of the game’s normal operation. If the developer has not documented a specific file-level action for your issue, preserve the folder and include its relevant metadata in the report instead of deleting candidates.
What this does not prove
These paths locate game data. They do not prove that a particular filename is the only save, that manual edits are supported, or that moving files between Windows, macOS, and Steam Deck is safe. Exact filenames, cross-platform transfer behavior, and recovery after a corrupted cloud conflict are pending confirmation. If the issue is reproducible, use the developer’s report format instead of experimenting on the only copy.
Sources and references
Open the original pages below to re-check prices, patches, platform support, or other details that may change after this guide was updated.
