01
Create a project and copy a ps_test_ runtime key.
AI Guide
Use this checklist when a coding agent is wiring Persistly into a game.
The checklist keeps AI integrations narrow and correct: create the project, use ps_test_ keys first, create an account, store accountId and accountSessionToken locally, autosave local drafts, and handle 409 conflicts explicitly.
Checklist
This should be followed in order.
02
Initialize the SDK with a runtimeKey and create an account.
03
Persist accountId and accountSessionToken locally immediately after account creation.
04
Use the first slot for simple games; add more named slots later only if the game needs them.
05
Store gameplay data locally first and let autosave sync remotely on the runtime sync policy.
06
For no-login cross-device demos, use createTransferCode on the device that already has the account and attachWithTransferCode on the new device.
07
Handle 409 conflict by accepting the cloud conflict branch and reconciling local edits.
08
Switch from ps_test_ to ps_live_ only in production builds.