Concepts
PlayerState persists data with ProfileStore, replicates a filtered view to clients with Replica, and separates per-player versus server-wide and temporary versus saved concerns. You do not need a new mental model for ordinary fields: top-level profile keys still behave as replicated, saved player data.
Start here for visibility: Data visibility model — normal data, session, SharedSession, and Server / ServerOnlyRoots.
Guides hub
Task-based shortcuts (install, hide data from clients, migration, listeners, and more) live on the Guides hub.
Lifecycle at a glance
| Phase | Signal / API |
|---|---|
| Profile ready after join | ProfileLoaded |
| Manual save during play | BeforeSave |
| Player leave / shutdown | BeforeRelease → BeforeSave → save → ProfileUnloaded |
BeforeRelease does not run on SaveData()
After concepts
- API overview, server and client references, types
- What's new for recent capabilities