Skip to content

Releases: mtkennerly/ludusavi-playnite

v0.10.2 (2022-09-12)

12 Sep 02:29
9beeddb
Compare
Choose a tag to compare
  • Fixed:
    • The extension's context menu section did not appear when selecting a single game if the installed Ludusavi version did not support multi-backup.

v0.10.1 (2022-09-11)

11 Sep 00:43
9c98227
Compare
Choose a tag to compare
  • Added:
  • Fixed:
    • Some errors were logged at info level.

v0.10.0 (2022-09-01)

01 Sep 08:51
9c77779
Compare
Choose a tag to compare
  • Added:
    • Support for multiple backups per game. This requires Ludusavi 0.12.0 or newer. You can open Ludusavi to configure how many backups to keep. The feature will be disabled if an older version is detected.
    • Support for automatic backups on an interval while playing a game.
    • Translation for Italian. (Thanks to contributors on the Crowdin project)
  • Fixed:
    • Disabled fallback restoration by Steam ID for Ludusavi versions older than 0.12.0 to avoid a defect in those versions.
    • The plugin settings window now has a horizontal scroll bar when necessary.

v0.9.0 (2022-08-13)

12 Aug 22:30
75447f7
Compare
Choose a tag to compare
  • Added:
    • Completed the translation for Simplified Chinese. (Thanks to contributors on the Crowdin project)

v0.8.1 (2022-07-11)

11 Jul 15:34
e19b711
Compare
Choose a tag to compare
  • Fixed:
    • Handling of games whose name begins with a hyphen. Previously, the plugin would not have been able to run Ludusavi for such games.
    • Handling of games whose name contains quotation marks. Previously, depending on the quote placement, the plugin may not have found anything to back up for such games.

v0.8.0 (2022-07-07)

07 Jul 07:57
2d8ebd7
Compare
Choose a tag to compare
  • Added:
    • Translations for Simplified Chinese (partial), Polish, Brazilian Portuguese, and Spanish. (Thanks to contributors on the Crowdin project)
  • Changed:
    • The plugin can now recognize when a game is on PC or Steam in more situations. Specifically, it now checks the game's platform name and source plugin ID as well, instead of just the platform specification ID and source name.

v0.7.0 (2022-05-27)

27 May 11:00
a19ac1d
Compare
Choose a tag to compare
  • Changed:
    • Localization now uses Project Fluent instead of pure C# code internally. Although English currently remains the only language supported, this change should make it easier for other people to contribute. If you'd like to help, check out the new Crowdin project.
    • The ludusavi-skip tag is now [Ludusavi] Skip. If you were using the old tag, it will be automatically renamed for you.
    • Removed support for erri120's extension update notifier since Playnite now natively provides this functionality.
  • Added:
    • Game-specific context menu entries to add or remove Ludusavi-related tags.
    • Option to restore save data for a game before playing it.
    • Option to remember your choice when asked if you want to back up a game.
    • Several new tags to tweak behavior for individual games:
      • [Ludusavi] Game: backup
      • [Ludusavi] Game: backup and restore
      • [Ludusavi] Game: no backup
      • [Ludusavi] Game: no restore
      • [Ludusavi] Platform: backup
      • [Ludusavi] Platform: backup and restore
      • [Ludusavi] Platform: no backup
      • [Ludusavi] Platform: no restore
  • Fixed:
    • When doing a backup or restore of specific games via their context menu, the plugin did not check whether another backup/restore was already in progress.

v0.6.1 (2022-01-14)

15 Jan 02:23
Compare
Choose a tag to compare
  • Fixed:
    • Crash when a game in Playnite did not have any platforms set.

v0.6.0 (2021-10-08)

08 Oct 23:48
Compare
Choose a tag to compare

v0.5.1 (2020-11-16)

17 Nov 01:25
Compare
Choose a tag to compare
  • Fixed:
    • Unresponsiveness when backing up after playing a game if its total backup size was very large (multiple GiB). The backup would still complete, but Playnite would lock up until it finished.
    • Error message in any backup/restore when the total file size was very large. The backup/restore itself still worked, but it could not be reported properly.