Which log messages reveal a corrupted persistent.renpy file during Ren'Py deployment?

Goal

Identify the specific log entries that indicate a corrupted persistent.renpy file when a Ren'Py build fails to start or load.

Constraints

Deployments often rely on the standard renpy.log and console output, which may not explicitly reference persistence. The persistence file is a binary pickle that can become unreadable if its schema changes or the file is truncated.

Unresolved Decision

It is unclear which log patterns reliably signal persistence corruption versus other load‑time errors, and how to programmatically detect and recover from such corruption during automated deployment pipelines.

Questions

• What specific entries in renpy.log or console output are most indicative of a corrupted persistent.renpy file?
• Can a pre‑load check be added to the deployment script to detect corruption before the main game loop starts?
• Which Ren'Py configuration options influence the robustness of persistence serialization during updates?