Installer ludusavi avec Homebrew, Nix, scoop, winget

Liens du projet

• Page d'accueil
• Page du gestionnaire de paquets

Commandes et alias

• ludusavi

Historique du projet

The project was created on GitHub in June 2020 to solve a practical PC-gaming problem: game save files are scattered across launcher folders, user profiles, Wine and Proton prefixes, and sometimes the Windows registry. Ludusavi's README describes support for backup and restore across Steam, GOG, Epic, Heroic, Lutris, and other game libraries, plus Steam screenshots and Steam Deck workflows.

Ludusavi separates the application from its game-location knowledge. The README states that it uses the Ludusavi Manifest for backup metadata and that the data is primarily sourced from PCGamingWiki, asking contributors to improve the wiki so those fixes flow back into Ludusavi's data.

Historique d'adoption

By 2026 the repository had thousands of GitHub stars and regular releases, and upstream documentation listed Windows, Linux, and macOS downloads plus Winget, Scoop, Flatpak, Cargo, and package-manager distribution. Homebrew, Nix, Scoop, and Winget packaging make it easy to install in both desktop and automation-oriented environments.

Its adoption is tied to Steam Deck and Proton growth: Ludusavi explicitly documents Proton saves, works on Steam Deck, and provides command-line behavior that fits backup scripts and game-launch wrappers.

Modes d'utilisation

Users can run Ludusavi interactively to preview, back up, and restore detected saves, or use the CLI for scheduled backups. Official docs cover backup automation, retention, validation, cloud backup, custom games, launch wrapping, root directories, and transferring saves between operating systems.

The documented application folder stores `config.yaml`, logs, and `manifest.yaml`; the docs warn that the manifest is managed by Ludusavi and should not be edited manually.

Pourquoi les passionnés de paquets s'y intéressent

Ludusavi is the kind of package that earns its place in multi-platform package indexes because it bridges desktop gaming and reproducible backup culture. Package maintainers care about it because it is a Rust desktop app with GUI and CLI surfaces, release assets for several operating systems, and data-driven behavior that depends on external manifest updates.

Chronologie

• 2020: Public GitHub repository created.
• 2020s: Rust GUI and CLI mature around a shared game-save manifest.
• 2025: v0.28 and v0.29 releases continue the regular release stream.
• 2026: v0.31.0 published, with upstream docs still listing broad package-manager availability.

Related projects

• Ludusavi Manifest provides the game save metadata consumed by the application.
• PCGamingWiki is the primary source for the save-location data.
• A Playnite extension is linked from the README for users of that launcher.

Sources

• https://api.github.com/repos/mtkennerly/ludusavi
• https://api.github.com/repos/mtkennerly/ludusavi/releases
• https://github.com/mtkennerly/ludusavi
• https://github.com/mtkennerly/ludusavi/blob/master/docs/help/application-folder.md
• https://github.com/mtkennerly/ludusavi/blob/master/docs/help/configuration-file.md
• https://github.com/mtkennerly/ludusavi/tree/master/docs