Caution: Fraudulent or imitation websites may appear. Only this site is official. Report concerns on our Report Fraud page.
Player Data is one of the most important systems in any VR fangame.
It allows your game to save player progress, stats, cosmetics, settings, and anything else that needs to persist between sessions.
This page explains how Player Data works, what types of data PlayFab supports, and how it fits into your game’s backend
1. What Player Data Is Used For
Player Data stores information such as:
Player settings
Cosmetics owned
Unlocked badges
Progression
Stats (tags, wins, time played)
Tutorial completion
Age group (PAG)
Moderation flags (non‑sensitive only)
Anything that needs to be saved permanently belongs here.
2. Types of Player Data
PlayFab has three main data types you’ll use in a VR fangame:
A. Player Data (UserData)
Key/value pairs
Good for settings, flags, and simple values
Example: "HasCompletedTutorial": "true"
B. Player Statistics
Numeric values only
Automatically sorted for leaderboards
Example: "Tags": 42
C. Player Profile
Display name
Avatar URL
Created date
Bans
Country (if enabled)
This is read‑only and used for identification.
3. When to Use Each Type
Use Player Data for:
Cosmetics
Unlocks
Settings
Toggles
Player preferences
Use Player Statistics for:
Leaderboards
Tag counts
Wins
Time played
XP
Use Player Profile for:
Display name
Account creation date
Ban status
3. When to Use Each Type
Use Player Data for:
Cosmetics
Unlocks
Settings
Toggles
Player preferences
Use Player Statistics for:
Leaderboards
Tag counts
Wins
Time played
XP
Use Player Profile for:
Display name
Account creation date
Ban status
4. How Player Data Fits Into Your Game Flow
Typical VR fangame flow:
Player logs in
Game requests Player Data
Game loads:
Cosmetics
Stats
Settings
Player plays
Game updates Player Data
Game saves changes before quitting
This ensures progress is always stored.
5. Common Player Data Keys in Gtag‑Style Games
Here are typical keys used in VR fangames:
"CosmeticsOwned"
"Badge"
"Color"
"NameColor"
"HasCompletedTutorial"
"PAG" (Player Age Group)
"BannedUntil" (if using custom moderation)
"RoomJoinCount"
"LastLogin"
These are stored as simple strings.6. Common Player Statistics
Stats are numeric and great for leaderboards:
"Tags"
"Tagged"
"Wins"
"Losses"
"TimePlayed"
"RoomsJoined"
"EventsCompleted"
Stats update automatically and can be displayed publicly.
7. Best Practices
Keep Player Data small and simple
Use Statistics for anything numeric
Never store sensitive data
Use CloudScript for secure updates
Validate data before saving
Avoid storing large JSON blobs