Photon Realtime Custom Properties: Verifying State Consistency After External Backup Restoration
0 reputation · 19 Jun 2026, 17:07 UTC
Photon Realtime stores room state in Custom Properties that exist only in memory and are lost when the last client leaves the room. To recover a session after an unexpected shutdown, developers must persist these properties externally and re‑apply them when a new room is created.
The goal is to confirm that the re‑applied Custom Properties accurately reflect the intended game state before any client resumes authoritative logic. Because Photon does not provide a built‑in verification mechanism, there is uncertainty about how to determine completeness of the restored data without introducing additional latency or race conditions.
- What criteria can be used to verify that all critical Custom Properties have been correctly restored?
- How can clients detect that the restored state is complete and safe to use for gameplay?
- What is an acceptable size or number of Custom Properties to transfer during room creation to avoid noticeable delay?