Export to a folder with no save yet is refused, though the picker says 'any folder' #165

Closed
opened 2026-11-17 09:08:46 +00:00 by riqmarmes · 1 comment
Contributor

What happened?

Saves → Export saves… → Another folder… → pick an empty/new folder → the confirm page cannot run the export:

No save of the game under (a folder with account.sav and slot_*, or 0400486024DEC000 under an emulator's nand/user/save): start the game there once and save.

and Export stays disabled. Exporting works only when the folder already holds a save (or an emulator's empty title folder), i.e. exactly when there is something to overwrite.

Launcher version

v1.0.0-rc.10 (676e300e), installed, Windows 11 (10.0.22631).

Steps / frequency

  1. Open Saves.
  2. Export saves… → the last option, Another folder… → pick an empty folder (e.g. on another drive).
  3. Press Continue: the confirm page says "No save of the game under …" and Export is disabled.

Every time. A folder that already holds a save works.

What I expected

The export to write the save there (account.sav, option.sav, slot_*), so I can keep a backup on another drive, or point a portable emulator at a folder before its first run. The picker says "A portable emulator's user folder, or any folder", and docs/saves.md says "into any folder you pick with Choose a folder".

Where it comes from

SavesConfirmViewModel.Refresh and Saves.ImportExport resolve the destination with Saves.Locate, which requires an existing save. Saves.Copy already knows how to create a target that is not there yet (it is how the first import works), and the confirm page already has the empty-target words ("nothing saved yet", "Nothing there yet to back up.").

scripts/longshot_saves.py refuses it too (its side() calls locate() on the destination, and new_save_folder() returns nothing for FOLDER; only a Hookshot/Longshot destination may be created), and the launcher's Core/Saves.cs is a rule-for-rule port of it.

Question

Should the launcher allow it — a folder with no save is made into the save folder — or should the picker/docs wording change to say the folder must already hold a save? If the answer is "allow it", I would send the launcher change (and the script change too if you want one rule across both).

### What happened? Saves → **Export saves…** → **Another folder…** → pick an empty/new folder → the confirm page cannot run the export: > No save of the game under *<folder>* (a folder with account.sav and slot_*, or 0400486024DEC000 under an emulator's nand/user/save): start the game there once and save. and **Export** stays disabled. Exporting works only when the folder already holds a save (or an emulator's empty title folder), i.e. exactly when there is something to overwrite. ### Launcher version v1.0.0-rc.10 (`676e300e`), installed, Windows 11 (10.0.22631). ### Steps / frequency 1. Open **Saves**. 2. **Export saves…** → the last option, **Another folder…** → pick an empty folder (e.g. on another drive). 3. Press Continue: the confirm page says "No save of the game under …" and Export is disabled. Every time. A folder that already holds a save works. ### What I expected The export to write the save there (`account.sav`, `option.sav`, `slot_*`), so I can keep a backup on another drive, or point a portable emulator at a folder before its first run. The picker says "A portable emulator's user folder, or any folder", and `docs/saves.md` says "into any folder you pick with *Choose a folder*". ### Where it comes from `SavesConfirmViewModel.Refresh` and `Saves.ImportExport` resolve the destination with `Saves.Locate`, which requires an existing save. `Saves.Copy` already knows how to create a target that is not there yet (it is how the first import works), and the confirm page already has the empty-target words ("nothing saved yet", "Nothing there yet to back up."). `scripts/longshot_saves.py` refuses it too (its `side()` calls `locate()` on the destination, and `new_save_folder()` returns nothing for `FOLDER`; only a Hookshot/Longshot destination may be created), and the launcher's `Core/Saves.cs` is a rule-for-rule port of it. ### Question Should the launcher allow it — a folder with no save is made into the save folder — or should the picker/docs wording change to say the folder must already hold a save? If the answer is "allow it", I would send the launcher change (and the script change too if you want one rule across both).
Collaborator

Possibly related, for context:

  • PR #26 feat: redesign save management around slots and transfers — Merged save-management redesign deliberately disabled export for empty saves
Possibly related, for context: - PR #26 feat: redesign save management around slots and transfers — Merged save-management redesign deliberately disabled export for empty saves
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/LongshotLauncher#165
No description provided.