Launcher: portable Windows build disables Play after renaming a parent folder #140
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher#140
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Reported on Discord
What happened
The reporter's portable launcher was placed in
D:/CGames/Zelda OOT/. Renaming eitherCGamesorZelda OOTcauses Play to become disabled; restoring the folder names makes Play work again. The screenshot shows launcher v1.0.0-rc.9 and Longshot v3.0.0-rc.5, with “not built: its game is missing.”Expected behavior
Play should remain available when a parent folder of the portable launcher and its game data is renamed.
Steps to reproduce
D:/CGames/Zelda OOT/.CGamesorZelda OOTfolder.System / versions
Windows (indicated by the drive path); portable Longshot Launcher v1.0.0-rc.9; Longshot v3.0.0-rc.5 (release candidate).
Log
The supplied
longshot_log.txtidentifies the game/options and mounted content underD:\CGames\Zelda OOT\LongshotLauncher-data\.... It is a game log, not a launcher log, and does not include launcher behavior during the rename. The screenshot is attached separately.Still unknown
Exact launcher executable and build folder layout, whether the launcher was restarted after renaming, Windows version, and the launcher log captured after the rename. The supplied game log was produced when Longshot ran, so it does not explain why the launcher disables Play after the parent path changes.
Related but different: Launcher #125 fixes relisting a moved game build after an update; this report reproduces by renaming a parent folder and is not the same scenario.
Files from the Discord report: