#engine backups list
writtenengine backups list [--game <id>] | show <id> | restore <id|latest> [--game <id>] [--dry-run]Lists the backups JoyPro made of a game's control files before each export, shows one, or puts one back. The Export page's Undo last export and Game config backups use it.
engine backups list --game DCS --text
engine backups restore latest --game DCS --dry-run --text
list [--game <id>]: the backup sets.show <id>: the files of one set and their original paths.restore <id|latest> [--game <id>] [--dry-run]: puts the files back and removes files the export created;--dry-runshows what would happen and writes nothing.- Safety: a restore backs up the current files first (so it can be undone too) and is refused while the game runs or when the game is not installed. The newest 30 sets per game are kept.
- Sets live in
%LOCALAPPDATA%\JoyPro2\GameBackups\<date-time>_<game>\withmanifest.json(the original paths). - Output: JSON or text with
--text. Exit code1when the id is missing (needs a backup id (or latest)), unknown (No backup '<id>' ... See engine backups list.) or the restore reports errors. - See backups.
What it does The backup sets every export makes of the game files it changes (newest 30 per game): list them, show one, or restore one (latest = the newest of --game). A restore removes files the export created and backs up the current files first, so it can be undone; --dry-run shows what it would do.
| Option | Values | Meaning |
|---|---|---|
--game | <id> | Game filter value. Example: DCS or IL2Game. |
--dry-run | switch (no value) | Report what the command would do; nothing is written or changed. |
Used by the GUI Start: Export to games · Export: Undo last export · Export: Export now · Export: Refresh · Export: Restore · Settings: Detect again · Settings: Use detected · Profile bar: Export
Example
engine backups list --text