: On the new device, select "Download Sync" and enter that code to transfer both saves and persistent data securely. Why this happens
In your Steamworks dashboard, set up a cloud path pointing to your config.save_directory On Windows, this is usually %APPDATA%/RenPy/
If you're a game developer or technically advanced user with legitimate game files, you can disable the save protection mechanism by modifying the game's source code: renpy this save was created on a different device link
: Ren'Py Sync is designed with security in mind. The 10-character code is generated on your computer and used as a key to encrypt your data before it is sent to the server. The Ren'Py developers have no way of decrypting your data. Server logs only keep the code's hash, the game's name hash, and your IP address to prevent abuse.
Open your project's screens.rpy file and locate your screen confirm(message, yes_action, no_action): block. Ensure it accommodates unknown message configurations properly. You need to make sure the interface handles the following variables safely: : On the new device, select "Download Sync"
Ensure your screens.rpy has the proper, up-to-date screen that includes the gui.UNKNOWN_TOKEN check.
Ren’Py then refuses to load the save. But why? And more importantly, how do you bypass it? The Ren'Py developers have no way of decrypting your data
To prevent "spiked" save files from running unauthorized scripts, Ren'Py now tracks where a save was created.
If you manually downloaded a save or used an online editor, you can force Ren'Py to bypass the token check by standardizing your local key file. On Windows: Press Win + R , type %appdata% , and hit Enter. Navigate to the RenPy/tokens/ sub-folder. Open security-keys.txt with a text editor.
Because you are including the persistent data, you are often copying the security key along with the saves. This can effectively "authorize" the new device, preventing the error message from appearing.
How to Fix "This Save Was Created on a Different Device" (User Guide)