[sivadaboi]

On top of #102. Since #102, device settings read the game database once per run, at start, without waiting for a rebuild, and a database update takes effect at the next start. That holds up after a weekly update, but not on a fresh install.

The problem. On a fresh install there is no downloaded catalogue yet at the first start, so the database read is the one built into the app. None of its 50,910 games has a settings entry (no c field in embedded/ludusavi-index.json.gz). So device settings stay off for the whole first run. Graphics and other settings files sync between devices until OpenSave happens to be restarted, which on a PC that sleeps rather than shuts down can be days.

Seen by hand. Two fresh scratch devices built from dev-public, both of which had played Balatro, each with its own settings.jkr. Balatro was tracked right after install, as people do, and the devices were paired once both downloads were indexed (plus a minute). The first sync was "both sides modified": the Deck opened on a save conflict whose only difference was its graphics file, and the save itself never arrived. Balatro's Configuration tab lists no device settings. With this change, the same steps sync the save, each device keeps its own settings.jkr, and Configuration lists it.

The change:

• presets.CatalogueGeneration() moves each time a new index is put in place: by a rebuild, or by the index built with the weekly download.
• The daemon's existing minute ticker (the one that runs ResyncWatchers) compares it with the generation it last read. When it has moved, the ticker:
  • reads the database again, outside the lock, and swaps it in, so settings are never empty in between;
  • runs adoptExclusionView over the games, as at start, so the watcher doesn't take the new view for a change.
• Start is untouched: it still never waits for a rebuild.

This sits in its own file, daemon/devicesettings_refresh.go, plus one line in the ticker and a field next to devMu, so that it doesn't touch the lines #118/#127/#128 rewrite. The reset sets loaded, db and patterns and leaves any other field zero, which works with today's devSettingsCache and with theirs (their verdicts map is created lazily).

Tests:

• daemon/devicesettings_refresh_test.go: a game's settings file is synced before the catalogue is indexed, and left out after one tick once it is, with the last snapshot's hash carried over. It fails without the refresh, without the generation bump on rebuild, and without the carry-over.
• presets/catalogue_generation_test.go: a downloaded index moves the generation. It fails without the bump.

Checks:

• With Games from your other devices set themselves up again; trust your own devices to choose folders #132, Device settings take the catalogue once it is indexed, without a restart #133 and Watcher: list a folder without blocking its removal (restores failing since #100) #134 merged onto dev-public (951cee6), the full Windows unit and e2e suites pass, with one exception: TestBuildManifest_SurvivesFilesVanishingDuringTheWalk (delta), which fails in over half of runs on this PC on dev-public and dev alike and isn't touched here. After Games from your other devices set themselves up again; trust your own devices to choose folders #132's last commit (a fix to how the catalogue check reads the index after a rebuild), presets, p2p, daemon and api and the folder, offer and rollback e2e tests were run again, and pass.
• -race on Linux (WSL Ubuntu) passes for presets, daemon, p2p/..., api, store, cliapp, fsx, watcher and snapshot, and for the folder, offer and rollback e2e tests. TestSignIn_AnOldAttemptsTimerLeavesTheNewListener once reported a data race in its cleanup; it does the same on plain dev-public.
• Merged one at a time with every open PR: no conflicts with any that merge cleanly into dev-public today, and no new file in the conflicts of those that don't (sync: batch small files, skip unchanged manifests, probe presence on its own #26, sync: closest devices first, by measured link speed #27, and the four against main).
• Merged with each of device settings: find a game's settings by what they hold, and give back what is a save #118, A game tracked without an App ID is offered its game database link #127 and sessions: see protected games and games installed anywhere; a safety net for the rest #128, the daemon and presets tests pass, including this test.

Changelog: left to your batch. Suggested wording:

• Device settings work from the first run. On a new install, OpenSave used to sync settings files such as graphics options between devices until it was restarted, and a weekly catalogue update took effect only at the next start. Both now take effect within a minute, without a restart.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
open-save	Ready	Preview	Oct 27, 2026 9:50pm UTC