Skip to content

What's new ​

These docs track PlayerState V1 for the Creator Store model. Install or update the model there; this site documents behaviour and API surface.

Notable capabilities and recent additions. For how data is scoped and replicated, start with Concepts and the data visibility model.

Docs layout: The API reference is split into topic pages under Server, Client, and Typesβ€”bookmark deep links that used #sections may need updating.

Shared session and server-only data ​

Session (per-player, non-persistent) and migration ​

  • Session data β€” Runtime-only roots such as session replicate during play but do not persist. RuntimeNonPersistentRoots in config lists top-level keys stripped before save.

  • Legacy data migration β€” Opt-in import from an old DataStore during profile load (strategies include Auto, Overwrite, KeepNew, Manual, and related options). MigrationResult reports when migration finishes (applied, legacy data, strategy, metadata). Migration guide

Other API highlights ​

Server and client references cover the full surface area; these are commonly called out:

Lifecycle events: BeforeRelease, BeforeSave, ProfileLoaded, ProfileUnloaded, MigrationResult. Events

  • BeforeRelease β€” Fires before a player's profile session is released on leave or server shutdown. Intended for leave-only final data writes (e.g. persisting world state into the profile). Does not fire on SaveData(). On leave, runs before BeforeSave. BeforeRelease()

PlayerState - High-Performance Roblox Data Management