Skip to content

v0.3.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Jul 17:05
· 161 commits to main since this release
v0.3.5
33ebadb

v0.3.5

Released 24 July 2026

Prevention and escalation for conflicts. If you are already caught in one, you can now keep both
saves rather than choosing. If no one acts, the console and your Windows tray will eventually say so.

Both the server and the agents need updating. Windows agents update themselves. On Steam Deck,
download the newer tarball and re-run install.sh.

New

  • Per-game conflict policy. In a game's detail card you can now set how conflicts are handled:

    • Manual (the default) — unchanged. Conflicts wait for you.
    • Newest wins — when two machines diverge, the server keeps the newer save automatically and
      notifies both machines to pull. No conflict row is ever written.
    • Prefer machine — one machine's saves go through auto-resolve; all other machines still
      produce a conflict.

  • Keep both. When resolving a conflict you can now choose to keep both saves. The one you select
    becomes the current Latest; both snapshots are protected from automatic retention so you can
    promote the other later if you change your mind. The Versions list labels protected rows and offers
    an Unprotect button for when you are done.

  • Stale conflict escalation. A conflict that has sat unresolved for more than six hours
    is now marked overdue. The console shows a persistent Overdue conflicts badge, and agents
    are told on their next heartbeat — so a connected Windows machine raises a notification even if
    you are away from the console.

  • Agent backoff. After three consecutive rejected saves for a game, the agent stops uploading
    new archives and instead reports the open conflict without adding to it. This is the behaviour that
    should have prevented 2.6 GB of redundant uploads in the Octopath incident. A clean pull followed
    by a normal save resets the counter; force-push bypasses it if you know what you are doing.

Fixed

  • Resolving to an older version. If a machine uploaded a save between when the conflict was
    opened and when you resolved it, the console would silently replace the newer Latest with the older
    conflict option. That is now refused: the conflict stays open, the current head is untouched, and
    the console explains what happened.

Upgrading

docker compose pull && docker compose up -d

The database updates itself on start. ⚠️ Rolling back to 0.3.4 or earlier is not supported after
the update — take a copy of the database first if you want the option.

Windows agents update themselves. On Steam Deck, download the newer tarball and re-run install.sh.

Known issues

  • Steam Deck: the D-pad does not work in the agent's folder browser. Use point-and-click, or
    arrow keys with a keyboard attached.
  • Linux and Steam Deck have no auto-update. Download the newer tarball and re-run install.sh.
Assets 4
Loading