saveData writes local state first for one-save games, so the game can continue through refreshes, tab closes, and short offline periods.
JavaScript Offline Sync
Keep browser saves local-first, then sync deliberately.
This JavaScript page keeps SDK navigation focused while linking to the shared offline sync model for deeper runtime behavior.
Browser Behavior
The JavaScript facade treats local state as the boot path and cloud sync as the safety path.
loadData returns the default local save for fast boot. Use forceSyncData or syncDue when the game reaches a safe network moment.
Use saveSlot/loadSlot instead when your game has manual saves, multiple campaigns, or slot slots.
The SDK keeps account/session identifiers and slot references in the configured browser storage.
If remote sync returns a conflict, show the player a recovery choice instead of silently overwriting cloud progress.
Go Deeper
Use the shared sync model when you need exact retry, backoff, and conflict rules.
Runtime-level guidance for local drafts, safe sync moments, 429 handling, and conflict recovery.
SDK-specific recovery pattern using exported statuses instead of raw strings.