docs(saves): the launcher's Linux backups are in ~/.local/share/longshot/save-backup #722
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: needs approval
beanstalk: running
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!722
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Longshot:docs/linux-save-backup-folder"
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?
Type: docs · Risk: low · Tested on: none (docs only) · Needs: none
Why
The launcher is moving its Linux save backups from
~/.local/share/oot-save-backupsto~/.local/share/longshot/save-backup/, beside the saves (LongshotLauncher#80). The saves guide, which the website shows, should say where to find them. No open issue fits (tracker searched).What changed
The Linux row of the saves guide's "Where Longshot keeps them" table names the new folder, and says that a launcher from before LongshotLauncher#80, and
scripts/longshot_saves.py, still use~/.local/share/oot-save-backups.docs/saves.md, one table row.Measurements
Nothing to measure: a line of the docs.
Flags and settings
None
Testing
Tested: read the rendered table row;
tests/run_all.pyis left to CI (no checks are run on this PC).Not tested: the website build with this page; CI's site checks cover it.
Must be tested: None
Risks
What could break: nothing in the game; until LongshotLauncher#80 is released, the newest launcher still writes to the old folder, which the row names.
Turning it off: revert the commit
Compatibility: Nothing changes
Checklist
Everyone
type(scope): description) of the status line's type.main.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named). (CI runs it on @e83e9182)third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.🤖 Generated with Claude Code
WIP: docs(saves): the launcher's Linux backups are in ~/.local/share/longshot/save-backupto docs(saves): the launcher's Linux backups are in ~/.local/share/longshot/save-backupdocs(saves): the launcher's Linux backups are in ~/.local/share/longshot/save-backupto WIP: docs: the game, not its title, and the launcher's new Linux save backup folderWIP: docs: the game, not its title, and the launcher's new Linux save backup folderto docs(saves): the launcher's Linux backups are in ~/.local/share/longshot/save-backup