Separate Encrypted Persistent File vs Embedded Persistent Data in Ren'Py Saves

Answer

In Ren'Py 8.x the config.encrypted_persistent flag controls encryption of the dedicated persistent file (persistent with no extension) that lives in the save directory. It does **not** affect any persistent data that might be stored inside individual save files (.save). When the flag is True the engine writes all persistent variables to that separate file and stores them in an encrypted form; the .save files contain only the game state snapshot and no readable persistent data.

How the Flag Works

• Default storage: Unless you change config.persistent_storage, Ren'Py keeps persistent data in a file named persistent (no extension) alongside the .save files.
• Effect of the flag: Setting config.encrypted_persistent = True causes that persistent file to be written with encryption derived from the game title and a seed. The flag does not encrypt data stored inside .save files.
• Automatic creation: When the flag is enabled and there is any persistent data to write, Ren'Py automatically creates (or updates) the persistent file; no extra configuration is required.

Verification Steps

1. Add init python: config.encrypted_persistent = True to your game.rpy.
2. Launch the game, reach a point where you set or modify a persistent variable, and create a save.
3. In the save directory look for a file named exactly persistent (no extension). Its size should be non‑zero and its contents should appear as binary data when viewed with a hex editor.
4. Open any recent .save file with a hex editor or a tool like renpy.unpickle; you should not see the plain‑text names or values of persistent variables.
5. Open the Ren'Py debug console (Shift+O) and run persistent to verify that the variables load correctly.
6. Repeat the test with config.encrypted_persistent = False; the persistent file will now contain readable plain‑text data, while the .save files remain unchanged.

Trade‑offs for a Small Project

• Separate encrypted file (flag on):
  • Adds a second file (persistent) to each save folder.
  • Persistent data is protected from casual inspection.
  • Backups must copy both the .save files and the persistent file.
• Embedded or unencrypted persistent data (flag off or custom storage):
  • If you keep the default separate file but leave it unencrypted, you still have only one extra file, but the data is readable.
  • If you set config.persistent_storage = 'saves', persistent data is stored inside each .save file, eliminating the extra file but making the data visible inside the save container.

For a small project that values simplicity and portability, keeping persistent data in the default unencrypted persistent file is often sufficient. If you need to hide unlock flags, gallery progress, or preference data from players or modders, enabling config.encrypted_persistent provides that protection at the cost of managing an additional file.

Missing Diagnostic Detail

Does your project use a custom config.persistent_storage setting or a Ren'Py version older than 8.0? Those details could change how the flag behaves.