Ren'Py 7.4 Save‑File Encryption: Evaluating a Shift from Opt‑In to Default

Goal: Assess whether Ren'Py should change the default value of config.encrypt_save_data from false to true in upcoming releases.

Constraints and uncertainties include the risk of permanent save loss if the per‑project encryption key is misplaced, potential I/O overhead on low‑end devices, and compatibility issues when collaborators toggle the setting between plaintext and encrypted saves. Additionally, the current encryption only protects confidentiality and integrity, leaving replay attacks unaddressed.

Should the engine generate and manage a project‑specific key automatically to reduce key‑loss risk? Would a configurable fallback to plaintext saves mitigate compatibility concerns? Is the performance impact acceptable for the target hardware baseline?