Godot Advanced Runtime

Use direct Godot client calls only for lower-level control.

Most Godot 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 PersistlyGameSaves for normal Godot game code.

Use PersistlyClient when you need direct account/session control or custom addon behavior around the runtime contract.

Persist account_id, account_session_token, and stable slot_id 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.

Runtime/API reference

Direct HTTP contract for account sessions, slot sync, account/slot sync, and errors.

API examples

Exact request and response shapes for lower-level integrations.