The backup structure has changed! Read below for more detail.
- Added:
- Backup option to exclude save locations that are only confirmed for another operating system.
- Backup option to exclude store screenshots.
--try-updateflag for backups via CLI.
- Fixed:
- When starting the GUI, if Ludusavi could not check for a manifest update (e.g., because your Internet is down), then it would default to an empty manifest even if you already had a local copy that was downloaded before. Now, it will use the local copy even if it can't check for updates.
- Changed:
- Backup structure is now human-readable.
- App window now has a minimum size, 640x480. (Note: For now, the crates.io release will not have a minimum size.)
- File size units are now adjusted based on the size, rather than always using MiB. (contributed by wtjones)
(See also: experimental variant with OpenGL)
New backup structure
Click to expand full details
Previously, Ludusavi used Base64 to encode game names and original paths when organizing backups. There were some technical advantages of that approach, but it was not easy to understand, and there was a technical flaw because Base64 output can include /, which isn't safe for folder or file names.
Therefore, Ludusavi now organizes backups like this, in a way that is easier to read and understand:
C:/somewhere/the-backup-folder/
Game 1 Name/
mapping.yaml
registry.yaml
drive-C/ # drive-0 on Linux and Mac
Users/
...
Program Files/
Steam/
...
The name of each game's folder is as close to the real title as possible, except for replacing some special characters with _. Ultimately, Ludusavi doesn't care much about the folder name and mainly looks for mapping.yaml, which contains some metadata that Ludusavi needs. If a game has any Windows registry data to back up, then there will also be a registry.yaml file. Within each drive folder, everything is simply organized exactly like it already is on your computer.
If you need to restore a previous backup, then please use Ludusavi v0.6.0 to do the restoration first, then migrate to Ludusavi v0.7.0 and create a new backup.
You can read more here about the background of this change. Be assured that this sort of disruptive change is not taken lightly, but may happen in some cases until Ludusavi reaches version 1.0.0.