Automatic game-save discovery Beta
Scan supported game-save locations, review paths and ranges before creating projects, and retain manual edits during rediscovery.
What discovery means
Definitions describe paths, not installation proof. Windows Steam/GOG/Epic supply evidence; Ludusavi primary, manually selected secondary manifests and local overrides describe resources. Registry resources can be unsupported; registry backup/Heroic/Lutris are outside current Windows Beta scope.
Opening the page makes no network request. Explicitly download/update inputs, select roots/stores/accounts and scan. Inspect per-root diagnostics; valid cache can survive network failures, but corrupt inputs must not appear as healthy empty output.
Review and create
A game can contain multiple provider Backup Sets. Selecting resources/presets creates drafts for review, not automatic persistent configs. MineRewind instances can become independent configs.
Steam defaults to the most recent account; other accounts/wildcard fallbacks remain visible but unselected. Check paths/resources/scope and broad-root warnings. Source/destination overlap blocks. Single-shot save failure preserves config/review baseline.
Source scope
All or validated relative Include globs define directory/file-set boundaries. Config filters/plugin policies can only narrow them. Complete capture within a source boundary does not mean the entire physical root.
Rediscovery
Three-way review compares last-reviewed upstream baseline, current user config and new candidates, preserving user changes by default. Identity is provider + DefinitionId + SetId, not display title. Upstream changes, narrowing and conflicts need review.
Acceptance
Exercise scan/account selection/create, scope edits, single-source backup, review conflicts/cancellation and attribution. Discovery knowledge does not elect runtime Kind ownership.
Staged confirmation in 1.9.3
After scanning, confirm configurations by game/backup set, then review individual sources and resources. Read full paths, edition, provider and scope; a game entry is not a saved configuration. Continue with names, backup destinations and final review. Selection is disabled while scanning; canceled or departed scans cannot update the current page later.
The Minecraft creation entrypoint can automatically discover saves without first selecting a directory or downloading Ludusavi. Automatic discovery includes known launcher locations and remembered roots. Selected-directory scans stay within the chosen scope; switching back to automatic discovery includes known locations again. Java and Bedrock use separate Kinds, matching each draft's edition. Discovery uses directory/level.dat evidence, not world-health or game-loading validation.