feat: saves from the game's user/ folder, one backups folder, Linux build files in the cache, and release.py from Tooling #211
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!211
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:feat/paths-and-shared-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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):user/when that folder exists, otherwise from the old place.--useris passed unchanged, so every mix of old and new launcher and game finds the saves. The launcher never createsuser/.save-backupsfolder on Windows and Linux. The old folders (save-backup,oot-save-backups) are still listed and restorable, and are never moved.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.Shared
release.py. The launcher's copy ofrelease.pyand its test are removed. CI fetches Tooling at the commit in.tooling-rev(Tooling#24); the release workflow, title check, CircleCI jobs,mise.tomland docs follow.Testing
Tested: not built or run on this PC; static review only. New C# checks are in
SavesChecks,SaveBackupsChecksandInstallChecks.Still to test:
work/to the cache and builds;user/;save-backupsand old ones are still listed.Risks
.tooling-revis a placeholder. It needs Tooling#24's commit hash before this merges, or the release jobs fail at checkout.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
Possibly related, for context:
WIP: feat: saves from the game's user/ folder, one backups folder, Linux build files in the cache, and release.py from Toolingto feat: saves from the game's user/ folder, one backups folder, Linux build files in the cache, and release.py from Tooling