Photon Integration: Room Properties

Room Properties are global values stored on a Photon room.
They define the rules, settings, and metadata for the entire multiplayer session.
While Custom Player Properties store data for individual players, Room Properties store data that applies to everyone in the room.

Room Properties are essential for game modes, map selection, room codes, region logic, and any system where all players must share the same information.

1. What Room Properties Are

Room Properties are key–value pairs stored on the room itself.

Examples:

• "map": "FOREST"

• "mode": "CASUAL"

• "maxPlayers": 10

• "eventActive": true

• "version": "1.2.0"

• "staffOnly": false

These values are synced automatically to all players.

2. Why VR Fangames Use Room Properties

Room Properties allow you to:

• Define the map

• Define the game mode

• Control max players

• Enable/disable events

• Restrict rooms to staff

• Sync room settings to all players

• Display room info on join

• Validate room compatibility

They are the backbone of multiplayer logic.

3. How Room Properties Work

A. Setting Room Properties

The host (or master client) sets the properties when creating the room.

Photon then:

• Stores the values

• Broadcasts them to all players

• Updates them in real time

B. Updating Room Properties

Room Properties can be updated mid‑game.

Example:

• Changing the map

• Switching game modes

• Enabling an event

• Locking the room

Photon automatically syncs the changes.

4. Recommended Room Property Structure

Use simple, readable keys:

map "FOREST" Current map

mode "CASUAL" Game mode

maxPlayers 10 Player limit

eventActive true Event toggle

version "1.2.0" Required game version

staffOnly false Restrict room access

roomCode "ABCD" Room code identifier

These values should be strings, ints, or booleans.

5. When to Use Room Properties

Use Room Properties when:

• The value affects the entire room

• All players need to know the value

• The value rarely changes

• The value defines gameplay rules

Examples:

• Map name

• Game mode

• Event status

• Room code

• Version requirement

• Staff‑only flag

6. When NOT to Use Room Properties

Do NOT use Room Properties for:

• Player cosmetics

• Player identity

• Player stats

• Movement data

• Physics data

• Anything that updates every frame

Those belong in Custom Player Properties or local scripts.

7. Room Properties vs. Custom Player Properties

Feature Room Properties Player Properties

Applies to Entire room One player

Used for Map, mode, settings Cosmetics, identity

Updates Global Per player

Syncs Automatically Automatically

Best for Game mode logic Appearance & identity

They serve different purposes and should not be mixed.

8. Room Property Visibility

Room Properties can be:

A. Visible in the lobby

Used for:

• Room lists

• Matchmaking

• Public room browsing

B. Hidden (internal use only)

Used for:

• Staff flags

• Version checks

• Event toggles

You choose which properties are visible.

9. Best Practices

• Keep property keys short and consistent

• Use strings for map/mode names

• Use booleans for toggles

• Use integers for numeric values

• Update properties only when needed

• Validate room settings using PlayFab

• Store room codes as properties

• Use version checks to prevent mismatched players