Sessions and player context
What the launcher provides, what stays private, and what replay changes.
Configuration fields
| Field | Type / meaning |
|---|---|
| version | 1 or 2 in the type; current parent returns 2 |
| sessionId, gameId | Correlation identifiers, not authentication credentials |
| locale | en or he |
| reducedMotion | boolean preference |
| room | null or roomId, code, gameId, playerId, expiresAt, launchToken |
| personalBest | optional number; account best or zero |
| preferences | optional muted/reducedMotion booleans |
| dailyChallenge | optional/null seed, releaseId and date |
Daily seeds are tied to game slug, release and UTC date. Specific built-in games may transform the configuration seed; new games should not copy a specialized transform blindly.
Privacy and authentication
There is no general getPlayer(), getUser(), login() or getWallet() SDK method. Configuration does not include email, account password or parent play token. room.playerId, when present, is scoped room context; it is not a universal player identity response. Games must never read parent cookies or ask players for Play Island passwords. Room tickets have their own server validation and expiry. They do not supply a complete game networking or authoritative score protocol. Any external game-server integration needs its own authenticated and validated session association.
Session lifecycle
A launcher session starts before the game loads and expires after two hours. Terminal reports close it. The SDK can begin another run after a terminal; the parent creates a new server session on started. Wait for acknowledgement, and re-read configuration when you need the updated session/day/release context. Because configuration is a separate request channel, request it after the new started acknowledgement, not immediately after sending started. Changing the signed-in account requires reloading before saving. Guest browser saves, where enabled, do not automatically become account saves. General provider games do not have a save entitlement merely because loadSave appears on the SDK.