Skip to main content
Cloud Sync
- Game-state backups
- Custom content backups (Custom quests, items, and processes)
- Upload/download operations tied to your configured gist
- Create a GitHub personal access token with
gistscope. - Create or choose a private gist.
- Open
/cloudsync(or Settings cloud-sync controls). - Save token and Gist ID.
- Run an upload, then verify a download from another profile/device.
- Token and gist ID are stored locally in IndexedDB.
- Credentials stay on your device except for authenticated requests to GitHub APIs.
- In Settings, use Clear / Log out actions to remove them from the device.
- Keep manual exports from
/gamesavesand/contentbackupas a fallback. - Rotate tokens if a device is lost or shared.
- Use separate tokens for Cloud Sync and contribution actions if you want tighter least-privilege.
- 401/403: token scope invalid or token revoked.
- 404 gist: incorrect gist ID or missing access rights.
- Sync appears stale: verify current profile writes before uploading and reload after download.
Cloud Sync
Cloud Sync stores sanitized backups in a private GitHub gist so you can recover across browsers or devices.
