Use the LoadBalancing API to match players to a shared game session (called "room") and transfer messages synchronously, in real-time, between connected players across platforms. All client SDKs can interact with each other, no matter if iOS, Android, web, console or standalone.
Simply set your AppId and pick a region to connect to. Click here for a list of available regions.
The LoadBalancing API is built to integrate well with your game logic.
You can fine-control when you want to handle incoming messages and how often you send anything.
Internally, both directions are buffered until your game calls
Games often use a game loop which calculates updates and then refreshes the screen.
Service() 10 to 50 times per second depending on your game and network usage.
If you don't call it, no "network progress" gets done at all.
Service covers two tasks:
- Received events and data gets executed.
This is done when you can handle the updates.
As a sequence order is always kept intact, everything that the client receives is queued and ordered.
DispatchIncomingCommandsto do this task.
- Outgoing data of your client is sent to the server.
This includes acknowledgments (created in the background) which are important to keep connection to the server.
SendOutgoingCommandsto do this task. Controlling the frequency of
SendOutgoingCommandscalls controls the number of packages you use to send a client's produced data.
When the application is quitting or when the user logs out do not forget to disconnect.
Create a Game
To create a new room, aka game, invoke "Create Room" operation on your connected LoadBalancing client.
This sets the room name and amount of players that are allowed in the room. The client will enter the new room automatically. When using the "Create Room" operation the room will be created before joining, if it doesn't exist. Rooms exist until the last player leaves.
You can define "Custom Room Properties" to set shared values for the room when you create it. The custom room properties can be used (e.g.) to store the map name, level or the round duration. The keys of Custom Properties have to be strings. Of course those values can be set and modified in the room as well.
You can select any of your custom properties to be shown also in the lobby, by setting the optional array with their names as "Custom Room Properties For Lobby". Properties showing in the lobby can be used for matchmaking and as filter for random matches.
Read more about matchmaking in our guide here.
Find a Game
Clients join games by name or ask Photon to find a perfect match.
Find rooms ...
- by Random: Matches players randomly. Optionally fills rooms or distributes players evenly.
- Use Filters in random matchmaking for better matching.
- by Listing: The lobby lists visible rooms to let players pick and join manually.
- that are Private: Join hidden rooms that you know the name of.
- or Parameterized: Customize random matching by defining expected properties.
With Photon Realtime, rooms' data can be saved and loaded easily. You need to setup webhooks to hook up Photon Cloud with an external web server.
Once setup, room states will be saved automatically for you. To rejoin rooms:
This feature makes asynchronous matchmaking and gameplay possible.
Read more about how to do this in our Persistence Guide.
Whatever happens on one client can be sent as event to update everyone in the same room.
Update your players with stats, positions or your current turn. Photon will send it as fast as possible (with optional reliability).
- Send messages/events: Send any type of data to other players.
- Player/Room properties: Photon updates and syncs these, even to players who join later.
Your event codes should stay below 200. Each code should define the type of event and the content it carries.
The event data in the example above is a
Hashtable. It can be a
byte or basically any data type supported by Photon's serialization (a
See Serialization in Photon for more information.
Whenever an event is dispatched a handler is called. An example is shown below.
Each event carries its code and data in the way your client sent them. Your application knows which content to expect by the code passed (see above).
For an up-to-date list of default event codes look for the event codes constants in your SDK, e.g. within
ExitGames.Client.Photon.LoadBalancing.EventCode for C#.
Custom or Authoritative Server Logic
As is, without authoritative logic, Photon Cloud products already allow for a broad range of game types.
- First Person Shooters
- Racing Games
- Minecraft type of games
- Casual real-time games
- Asynchronous and synchronous games