Launcher: portable Windows build disables Play after renaming a parent folder #140

Open
opened 2026-11-16 07:27:52 +00:00 by BeanIssues · 1 comment
Collaborator

Reported on Discord

What happened

The reporter's portable launcher was placed in D:/CGames/Zelda OOT/. Renaming either CGames or Zelda OOT causes 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

  1. Place/use the portable launcher at D:/CGames/Zelda OOT/.
  2. Rename either the CGames or Zelda OOT folder.
  3. Observe that Play is disabled; restore the original name and Play works again.

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.txt identifies the game/options and mounted content under D:\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.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1571786169434378320/1571786169434378320) ## What happened The reporter's portable launcher was placed in `D:/CGames/Zelda OOT/`. Renaming either `CGames` or `Zelda OOT` causes 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 1. Place/use the portable launcher at `D:/CGames/Zelda OOT/`. 2. Rename either the `CGames` or `Zelda OOT` folder. 3. Observe that Play is disabled; restore the original name and Play works again. ## 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.txt` identifies the game/options and mounted content under `D:\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.
Author
Collaborator

Files from the Discord report:

Files from the Discord report: - [image.png](https://git.magicbean.dev/attachments/68bd0cb9-1b59-438b-9628-5ed61fc0167e) - [longshot_log.txt](https://git.magicbean.dev/attachments/1e100926-ffa7-4c00-b33a-82ef16790e40)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#140
No description provided.