Launcher Bug: Client Directory Resets to Default After Saving and Restarting on Windows 10/11 #1203
Labels
No labels
area
blabot
area
client
area
encounters
area
launcher
area
missions
area
npc-behavior
area
performance
area
portal
area
quests
area
rdb
area
teams
area
trading
area
zone
priority
1
priority
2
priority
3
priority
4
shadowlands
state
cant-reproduce
state
duplicate
state
fixed
state
new
state
unrefined
state
verified
state
wontfix
type
bug
type
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: prk/issues#1203
Loading…
Add table
Add a link
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?
Describe the bug
When changing the client directory from the default (
C:\prk\client\client
) to a custom folder, the launcher appears to save the change successfully. However, upon reopening the settings or relaunching the game, the client directory resets back to the default path, causing the launcher to prompt for a re-download of the client files.Additionally, if you change the client directory but switch to another tab (e.g., Display or GUI) before clicking Save, only the settings of the active tab are saved. The changes made in the previous tab (e.g., the client directory) are not saved. This behavior is confusing because clicking Save causes the settings modal to close, giving the impression that all changes across all tabs have been saved.
If you click Save while still on the Launcher tab (without switching tabs), the client directory will be saved correctly.
To Reproduce
Steps to reproduce the behavior:
C:\prk\client\client
) to a different folder.C:\prk\client\client
.Expected behavior
When the user clicks Save, all settings across all tabs should be saved, not just the active tab. Alternatively, the system should warn the user that unsaved changes exist before allowing them to switch tabs. This would prevent confusion and ensure that users understand their changes are not being saved.
Screenshots
If applicable, add screenshots to help explain your problem.