ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Goal Determine how the documented 500 messages/second per‑room guideline in Photon Realtime 4.0 influences latency when many peers send events concurrently, and identify whether this behavior is consistent across Photon Cloud and self‑hosted Server deployments. Constraints & Uncertainty The 500 msg/s figure is documented as guidance; the actual server ma
Goal and Constraints Restore a binary snapshot of room and player state to a fresh Photon Server instance and confirm that the recovered data matches the original state exactly. The snapshot format is proprietary, and the Photon Admin API offers no automated restore or diff commands. Uncertainty Across Regions Documentation does not specify whether restoring
Photon Realtime employs a Concurrent User (CCU) licensing model where costs are tied to peak simultaneous connections. In low-traffic environments, maintaining an accurate CCU count is critical to staying within the limits of the Free or low-tier subscriptions and avoiding connection rejections. There is a technical distinction between a graceful shutdown an
When integrating Unity with Photon Realtime, developers must choose between the high-level PhotonView ObservedComponents for state synchronization and the lower-level RaiseEvent method for custom data transmission. The goal is to maintain consistent game state across clients while minimizing network congestion. While ObservedComponents automate property sync
Goal: determine whether enabling PhotonNetwork.OfflineMode in PUN reproduces the exact callback sequence and state changes that occur during a real connection to the Photon Cloud, allowing unit tests to run without credentials or network traffic. Constraints: the test must avoid any production AppId, must not generate external traffic, and must remain determ
This question examines the interoperability of Photon Server room persistence and client-side rejoining following a version upgrade. The LoadBalancing client API provides RejoinAndReconnect() methods intended to restore prior room context, while room persistence stores the latest room state on the server and cached events (lastN) are retained when RoomOption
I'm planning a zero-downtime migration for a small realtime app on Photon Engine. The current plan is to keep one Photon Cloud App ID so old and new client builds share the same rooms, and rely on PlayerTTL/EmptyRoomTTL plus rejoin with the same user ID so disconnected players resume their actor slot instead of re-entering as new actors. The uncertainty is t
photonengine