Read each game's cloud-save setting and warn only when it is on, with accurate advice #152

Closed
opened 2026-10-25 21:21:00 -05:00 by ethan-hann · 1 comment
Owner

The game editor always says to turn off the store's cloud saves, or the store can sync older saves over the ones SavePoint puts back (gameEditor.cloudSaves, README, user guide, D-entry near decisions.md line 177). A test on the Linux VM with Balatro and Steam Cloud on showed that advice is wrong for one PC: Steam does nothing while the game is closed, and at the next launch it compares each file's sha1 with its own cache, keeps the local files ("SHA mismatch with cache - setting local changes"), and uploads them when the game exits. No conflict dialog appeared and no local file was overwritten, for new content, older content, preserved old mtimes, and older content over a newer cloud copy. The remaining risk is a second PC (or a cleared Steam cache) holding a newer cloud change: then Steam may ask which copy to keep or download over the files SavePoint put back. That case was not reproduced.

What to build:

  • Steam: read userdata//7/remote/sharedconfig.vdf, UserRoamingConfigStore > Software > Valve > Steam > apps > > cloudenabled ("1" on, "0" off). Which account folder: the most recently used login. A missing key or missing file is "unknown", not on.
  • GOG Galaxy: read ProductSettings.cloudStorage for gameReleaseKey 'gog_' from a copy of %ProgramData%\GOG.com\Galaxy\storage\galaxy-2.0.db (plus its -wal), never the live file. No row means off. Galaxy's log shows this column, not CloudSavesConfiguration.enabled, decides whether sync runs. The global switch is featureCloudSaves in %LOCALAPPDATA%\GOG.com\Galaxy\Configuration\config.json; false means off for every game.
  • Never write any Steam or Galaxy file.
  • Editor: show the cloud note only when the game's store reports cloud on (or unknown, with softer wording), saying plainly that the store keeps what SavePoint puts back and uploads it when you quit, and that saves from another PC can replace them. Turning cloud off stays the advice for people who play on more than one PC.
  • README, user guide and decisions updated to match.

Tests use fixtures built from the real file layouts (vdf text, a SQLite file with the real table shapes), covering on, off, missing key, missing file, and no store installed.

The game editor always says to turn off the store's cloud saves, or the store can sync older saves over the ones SavePoint puts back (gameEditor.cloudSaves, README, user guide, D-entry near decisions.md line 177). A test on the Linux VM with Balatro and Steam Cloud on showed that advice is wrong for one PC: Steam does nothing while the game is closed, and at the next launch it compares each file's sha1 with its own cache, keeps the local files ("SHA mismatch with cache - setting local changes"), and uploads them when the game exits. No conflict dialog appeared and no local file was overwritten, for new content, older content, preserved old mtimes, and older content over a newer cloud copy. The remaining risk is a second PC (or a cleared Steam cache) holding a newer cloud change: then Steam may ask which copy to keep or download over the files SavePoint put back. That case was not reproduced. What to build: - Steam: read userdata/<accountid>/7/remote/sharedconfig.vdf, UserRoamingConfigStore > Software > Valve > Steam > apps > <appid> > cloudenabled ("1" on, "0" off). Which account folder: the most recently used login. A missing key or missing file is "unknown", not on. - GOG Galaxy: read ProductSettings.cloudStorage for gameReleaseKey 'gog_<productId>' from a copy of %ProgramData%\GOG.com\Galaxy\storage\galaxy-2.0.db (plus its -wal), never the live file. No row means off. Galaxy's log shows this column, not CloudSavesConfiguration.enabled, decides whether sync runs. The global switch is featureCloudSaves in %LOCALAPPDATA%\GOG.com\Galaxy\Configuration\config.json; false means off for every game. - Never write any Steam or Galaxy file. - Editor: show the cloud note only when the game's store reports cloud on (or unknown, with softer wording), saying plainly that the store keeps what SavePoint puts back and uploads it when you quit, and that saves from another PC can replace them. Turning cloud off stays the advice for people who play on more than one PC. - README, user guide and decisions updated to match. Tests use fixtures built from the real file layouts (vdf text, a SQLite file with the real table shapes), covering on, off, missing key, missing file, and no store installed.
ethan-hann added this to the 1.0 milestone 2026-10-25 21:53:00 -05:00
Author
Owner

Shipped in 0.9.14 (pull request 155).

Shipped in 0.9.14 (pull request 155).
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#152
No description provided.