Help Index → When something does not behave as expected → Use case 57
Distinguish a wrong folder, unreadable metadata and a failed load before attempting recovery. The picker’s display is not proof that a new save has successfully replaced the app’s existing context.
Before you start
- Keep NMS closed while investigating. Preserve an independent copy of the existing save folder before any manual file replacement.
- Before accepting Load Slot’s replacement warning, copy EACH pending Raw JSON pane to its own external file and preserve other useful app work. Loading replaces views; never save old context over another slot to test loading.
Steps
- Inspect Save Path in the save picker. First use or a missing remembered path starts blank. Pick Folder starts at an already selected existing path, otherwise suggests the newest valid embedded-metadata account among Steam st_* and GOG DefaultUser folders under %APPDATA%\HelloGames\NMS. Confirm or browse to the intended folder; then separately consent to the preference write. Cancel preserves the previous selection. (control reference)
- Inspect Game Slot and Save File metadata. Description can explain an unreadable entry. An empty list can indicate an incorrect folder or scan failure, not necessarily deleted saves. (control reference)
- Select the intended slot and choose Load Slot only when ready to replace app data. The Save File field is display-only: selection follows readable Auto/Manual metadata timestamps. If equal, OK selects Manual and Cancel abandons loading. (control reference)
- Wait until loading finishes. On failure, retain the exact error and check the folder’s availability and complete save/metadata files without renaming or manufacturing them. If you cannot establish a trustworthy source, stop and use an independent known-good folder backup for manual recovery. (control reference)
Expected result
- Only a successfully decoded context with all views populated becomes the new loaded source. A failed load is reported rather than silently accepted.
- Metadata can be readable while later decoding or view population still fails; slot labels alone cannot establish successful loading.
- Discovery is a picker suggestion only: strictly newer positive embedded save timestamps win, ties keep the first encountered account; no folder is automatically loaded or persisted. A matching data file is required beside readable metadata. If no valid candidate exists, manual browsing remains available.
What changes, and when to save
Scanning and loading do not write the live save. Choosing a remembered folder writes preferences only after confirmation; this does not authorize editing or restoring game files. Folder discovery itself only suggests a picker start path; it does not select a loaded save or authorize preference persistence.
Check the result
- After success, confirm loaded slot, Main or Expedition context and recognizable records. After failure, check that you are still viewing the prior data before taking any edit or save action.
Important details and recovery
- Do not pair a data file with unrelated metadata or assume choosing another displayed file overrides timestamp policy.
- There is no promised automatic repair for corrupt or unsupported saves. Preserve originals and report the exact error before further changes.
- Storage is dynamic: Steam for st_* folders, GOG for DefaultUser, Steam/GOG for other selected folder names, and blank with no folder. Neither that caption nor filesystem Date modified proves which save should be loaded.