Use PersistlyGameSaves for normal Unity game code.
Unity Advanced Runtime
Use direct Unity client calls only for lower-level control.
Most Unity games should stay on PersistlyGameSaves. Advanced pages exist for custom wrappers and exact runtime debugging.
Boundary
Keep the facade as the default public integration.
Use PersistlyClient when you need direct account/session control or custom serialization around the runtime contract.
Persist accountId, accountSessionToken, and stable slotId values if you bypass the facade.
Do not build custom HTTP paths that bypass runtime limits, conflict checks, or account-session scoping.
References
Use these shared pages for exact runtime behavior.
Direct HTTP contract for account sessions, slot sync, account/slot sync, and errors.
Exact request and response shapes for lower-level integrations.