Filtering Network Messages with Photon Engine Interest Groups in Unity PUN2
Learn how to use Photon Engine interest groups in Unity PUN2 to filter network messages, reducing bandwidth by ensuring only subscribed players receive specific events.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use Photon Engine interest groups in Unity PUN2 to filter network messages, reducing bandwidth by ensuring only subscribed players receive specific events.
Learn how to set up custom room properties, use Photon Realtime’s lobby system, and balance latency by selecting the nearest region. A step‑by‑step guide with Unity code snippets and trade‑off insights.
Learn how to use Photon Room Properties to synchronize persistent game state, manage trust boundaries via the Master Client, and avoid common bandwidth pitfalls.
Learn how Photon Realtime Interest Groups filter network traffic by subscribing clients to byte-coded channels, cutting bandwidth in scalable multiplayer games, with a C# example.
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
AutoReconnect behavior after a failed client upgrade Photon Realtime’s AutoReconnect feature is designed to restore a client’s connection to the same server and room following a transient network drop. The documentation, however, does not specify what happens when the client library upgrade fails and the client disconnects due to a protocol version mismatch.
Determine whether enabling Photon’s Async HTTP fallback or adjusting the server’s MaxCCU setting deterministically reduces the latency spikes observed when many clients issue OpCreateRoom or OpJoinRoom operations concurrently. Photon Realtime queues these operations on the game server’s per‑peer message dispatch queue, and the latency increase depends on an
Developers using Photon Realtime need to decide how to handle the room list cache that does not automatically expire entries based on time. The cache is refreshed only when the client calls OpGetRoomList or when the server pushes updates according to the lobby’s update interval, which can leave closed or full rooms visible longer than desired. The goal is to