Playfab Intergration: Title Data

Title Data is PlayFab’s system for storing global, game‑wide configuration values.
Unlike Player Data (which is unique per player), Title Data is shared across every player and every device.

VR fangames use Title Data to control global settings, announcements, shop prices, event data, and anything that needs to update instantly without releasing a new game build.

1. What Title Data Is Used For

Title Data is perfect for storing:

• Global announcements

• Shop prices

• Event start/end dates

• Map rotation

• Daily reward settings

• Version requirements

• Maintenance messages

• Word filters

• Moderation rules

• CloudScript configuration

• Seasonal cosmetic lists

Anything that should update without updating the game belongs in Title Data.

2. Why VR Fangames Use Title Data

VR fangames rely on Title Data because:

• You can update it instantly

• It syncs to all players

• It works with CloudScript

• It prevents hard‑coding values in Unity

• It allows live balancing

• It keeps your game flexible

For example, you can change shop prices or event rewards without pushing a new update.

3. How Title Data Works

A. You store key/value pairs in PlayFab

Example:

• "ShopPrice_HAT_RED": "250"

• "EventActive": "true"

• "DailyRewardAmount": "50"

B. Your game downloads Title Data on startup

This ensures all players use the same global settings.

C. CloudScript uses Title Data for secure logic

Example:

• Checking event status

• Validating shop prices

• Enforcing version requirements

D. You can update Title Data anytime

Changes apply instantly to all players.

4. Common Title Data Keys in VR Fangames

Shop & Economy

• "ShopPrice_HAT_RED"

• "ShopPrice_BADGE_MOD"

• "DailyRewardAmount"

• "EventCurrencyMultiplier"

Events

• "EventActive"

• "EventStart"

• "EventEnd"

• "EventRewardItem"

Gameplay

• "MapRotation"

• "RoomCodeLength"

• "MaxPlayers"

Moderation

• "WordFilter"

• "AutoBanThreshold"

• "StaffList"

Version Control

• "RequiredVersion"

• "UpdateMessage"

5. Title Data vs. Player Data (Important)

Feature Title Data Player Data

Appies to Everyone One player

Editable by Devs only Game/CloudScript

Use Case Global settings Player progress

Updates Instantly Per player

Security High Medium

They serve completely different purposes

6. Best Practices

• Keep keys short and consistent

• Use prefixes (ShopPrice_, Event_, Config_)

• Store only global values

• Avoid storing large JSON blobs

• Use Title Data for anything CloudScript needs

• Never store sensitive data

• Update Title Data before events go live

7. Title Data + CloudScript

CloudScript often reads Title Data to:

• Validate shop prices

• Check if events are active

• Enforce version requirements

• Load moderation rules

• Load staff permissions

• Control daily rewards

This keeps your backend secure and flexible.

8. Title Data + Photon

Photon can use Title Data for:

• Room settings

• Map rotation

• Region restrictions

• Max player limits

This ensures all rooms follow the same global rules.