Idea: Make direct game launches use shared saves on Windows #760
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
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
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#760
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 by truekry on Discord
The idea
When the game is started directly from its executable, make it use the same shared save folder as when it is started through the launcher. This would let players use the launcher only to check for updates, then start the game directly without losing access to their saves. The player also asks for this to be opt-in; clarify the intended scope of that opt-in during implementation.
What is missing
The exact opt-in behavior requested is unclear: whether it should control using the shared save folder or avoid the launcher's update check. The original report is from Windows, but no OS was explicitly stated.