GeekGravityGame saves, sync and troubleshooting
Public document · Updated
Where is progress stored?
Integrated games save in the current browser first. Signing in enables account synchronization; confirm successful sync before changing devices. Signed-out, offline or unavailable-host local saves are not proof of cloud persistence.
External games follow their original website's save rules. WeChat mini-game and browser progress are separate.
Two different saves
Signing in or changing devices can expose local/cloud conflicts. Compare the summaries and choose deliberately. The game must load the selected state immediately.
Troubleshooting
- Missing progress on another device: check the account, game integration and whether the original device completed synchronization.
- Only saved locally: check connection and sign-in state, then retry. Do not clear browser data before confirming synchronization.
- Private browsing or full storage: local writes can also fail; check save feedback.
- Upgrade cannot read progress: report the game, version, device and reproduction steps. Do not post credentials or full private saves publicly.
Developer contract
Keep a stable game ID and maintain a schemaVersion inside your data. Account save data is limited to 64 KiB and summary to 1 KiB. Use a small, meaningful summary such as the current level.
Revision checks detect conflicts. Do not blindly overwrite them. Handle the SDK save event by replacing the running game state, not merely localStorage. Network requests during page close are not guaranteed to finish; checkpoint at stable milestones.
The write result's saved field reports persistence; source equal to cloud confirms synchronization for that write. A local result does not mean upload success. Client saves must not be trusted for authoritative rankings or rewards.