feat: saves from the game's user/ folder, one backups folder, Linux build files in the cache, and release.py from Tooling #211

Merged
HumanBean merged 1 commit from HumanBean/LongshotLauncher:feat/paths-and-shared-release into main 2026-11-20 00:33:50 +00:00
Owner

Summary

Paths. The launcher's half of moving the player's files on Linux into ~/.local/share/longshot/user/ (the game side is a Longshot PR still to come):

  • Saves and options: read from user/ when that folder exists, otherwise from the old place. --user is passed unchanged, so every mix of old and new launcher and game finds the saves. The launcher never creates user/.
  • Backups: new backups go to one save-backups folder on Windows and Linux. The old folders (save-backup, oot-save-backups) are still listed and restorable, and are never moved.
  • Build files on Linux: work/ and the downloaded SDKs move to ~/.cache/longshot/launcher, renamed once at start-up while no build runs. A folder you chose is never moved. Windows is unchanged.
  • Safety: a game folder that holds the save folder can't be deleted or renamed.

Shared release.py. The launcher's copy of release.py and its test are removed. CI fetches Tooling at the commit in .tooling-rev (Tooling#24); the release workflow, title check, CircleCI jobs, mise.toml and docs follow.

Testing

Tested: not built or run on this PC; static review only. New C# checks are in SavesChecks, SaveBackupsChecks and InstallChecks.

Still to test:

  • CI's build and tests, by CI.
  • On Linux, by hand:
    • an existing install moves work/ to the cache and builds;
    • saves show before and after the game moves them to user/;
    • old backups are listed and restore.
  • On Windows, by hand: backups go to save-backups and old ones are still listed.

Risks

  • Tooling first: .tooling-rev is a placeholder. It needs Tooling#24's commit hash before this merges, or the release jobs fail at checkout.
  • Old launcher, new game: once the game has moved the saves into user/, an older launcher's Saves page looks in the old place. The links the game leaves there cover the save folder itself.

🤖 Generated with Claude Code

## Summary **Paths.** The launcher's half of moving the player's files on Linux into `~/.local/share/longshot/user/` (the game side is a Longshot PR still to come): - **Saves and options:** read from `user/` when that folder exists, otherwise from the old place. `--user` is passed unchanged, so every mix of old and new launcher and game finds the saves. The launcher never creates `user/`. - **Backups:** new backups go to one `save-backups` folder on Windows and Linux. The old folders (`save-backup`, `oot-save-backups`) are still listed and restorable, and are never moved. - **Build files on Linux:** `work/` and the downloaded SDKs move to `~/.cache/longshot/launcher`, renamed once at start-up while no build runs. A folder you chose is never moved. Windows is unchanged. - **Safety:** a game folder that holds the save folder can't be deleted or renamed. **Shared `release.py`.** The launcher's copy of `release.py` and its test are removed. CI fetches Tooling at the commit in `.tooling-rev` ([Tooling#24](https://git.magicbean.dev/MagicBeanDev/Tooling/pulls/24)); the release workflow, title check, CircleCI jobs, `mise.toml` and docs follow. ## Testing **Tested:** not built or run on this PC; static review only. New C# checks are in `SavesChecks`, `SaveBackupsChecks` and `InstallChecks`. **Still to test:** - CI's build and tests, by CI. - On Linux, by hand: - an existing install moves `work/` to the cache and builds; - saves show before and after the game moves them to `user/`; - old backups are listed and restore. - On Windows, by hand: backups go to `save-backups` and old ones are still listed. ## Risks - **Tooling first:** `.tooling-rev` is a placeholder. It needs Tooling#24's commit hash before this merges, or the release jobs fail at checkout. - **Old launcher, new game:** once the game has moved the saves into `user/`, an older launcher's Saves page looks in the old place. The links the game leaves there cover the save folder itself. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat: saves from the game's user/ folder, one save-backups folder, build files in the cache folder on Linux; release.py comes from Tooling
Some checks failed
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Failing after 4s
31c2fc654a
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Member

Possibly related, for context:

  • issue #188 Linux: save backups are split between two folders, and the launcher lists only one — Related backup-folder unification and legacy backup listing
  • issue MagicBeanDev/Longshot#913 Idea: Store save files per user account — Game-side per-user save-location change relevant to launcher paths
Possibly related, for context: - issue #188 Linux: save backups are split between two folders, and the launcher lists only one — Related backup-folder unification and legacy backup listing - issue MagicBeanDev/Longshot#913 Idea: Store save files per user account — Game-side per-user save-location change relevant to launcher paths
HumanBean changed title from WIP: feat: saves from the game's user/ folder, one backups folder, Linux build files in the cache, and release.py from Tooling to feat: saves from the game's user/ folder, one backups folder, Linux build files in the cache, and release.py from Tooling 2026-11-20 00:33:46 +00:00
HumanBean deleted branch feat/paths-and-shared-release 2026-11-20 00:33:50 +00:00
Sign in to join this conversation.
No reviewers
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!211
No description provided.