Unity Offline Sync

Use Unity lifecycle moments as safe sync points.

Unity docs stay inside the SDK flow while linking to the shared Persistly offline sync model.

Unity Behavior

Persist locally first, then sync at lifecycle boundaries.

SaveSlotAsync writes local progress before remote sync, so pause/quit events can preserve player state.

Use ForceSyncAsync at safe lifecycle moments: manual save, checkpoint, app pause, app quit, or foreground resume.

Keep autosave cadence predictable. Do not sync every frame or every tiny state mutation.

Handle conflicts explicitly so players can choose local or cloud progress when both changed.

Go Deeper

Use the shared model for runtime-level retry and conflict behavior.