Skip to content

Unofficial fork test build v2.4.1-fixes.8

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Oct 18:25
· 0 commits to main since this release
v2.4.1-fixes.8
8631705

Warning

Unofficial test build from the fork ChakraFusion/OpenSave, branch fixes-2.4.1. It is not a release of Liquid-co/OpenSave. Please don't report problems with it to the OpenSave project or its Discord.

OpenSave 2.4.1 with the fixes and features proposed upstream: data-safety fixes in sync, save versions, play sessions, per-device settings, snapshot integrity, network-aware sync, and faster sync and restore of large saves. The full list, with one pull request per topic, is in the overview issue on Liquid-co/OpenSave.

Tested: fixes.7 was tried by hand on Windows, on four PCs over LAN and VPN. The changes since (below) are covered by the automated unit and end-to-end tests only. Linux, macOS, Flatpak and the Decky plugin are built by the same workflow and pass the unit and end-to-end tests on Linux, but haven't been tried by hand.

Updates: the built-in update check still points at Liquid-co/OpenSave. This build calls itself v2.4.1-fixes.8, a pre-release, so an official release can be offered as an update, which returns you to the official build.

Before trying it: OpenSave keeps a snapshot before replacing any save, but back up saves you care about all the same. Devices on this build and on official 2.4.1 can be paired; nothing is taken from a device without save versions, and its deletions are refused.

Changes since v2.4.1: v2.4.1...v2.4.1-fixes.8

New since fixes.7 (the first five are fixes merged upstream into dev-public today, ported to this build; the last is new here and will be proposed upstream):

  • A new database applies its migrations in one step, so a failed start can't leave it half-migrated.
  • A save emptied while a sync was starting is still held back and asked about.
  • A file deleted right after a sync no longer comes back when the sync's completion report is lost, also for a game synced by hand.
  • An extra save location put back after being emptied stays put back.
  • In an extra save location, edits made on both devices while a slow sync check was running are asked about, instead of one silently replacing the other.
  • The game database is prepared in the background after its weekly download: the first snapshot afterwards no longer pauses for about 25 seconds.

Changes since fixes.7: v2.4.1-fixes.7...v2.4.1-fixes.8

Assets 16
Loading