Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Custom save file directory #6806

Open
deusnovus opened this issue May 15, 2024 · 2 comments
Open

[Feature Request] Custom save file directory #6806

deusnovus opened this issue May 15, 2024 · 2 comments

Comments

@deusnovus
Copy link

Overview

Allow the user to maintain a save file folder externally, at a custom folder path of the user's choice.

Smaller details

Possibly a duplicate of #4638 , but I think the original post's request was rather unreasonable. However, it would be beneficial to provide the option to maintain a save file folder externally for all users, including those who have an existing cloud storage plan, like myself.

Nature of request

N/A

Why would this feature be useful?

I personally use 3 different emulators that allow external save folder paths, automatically sync every file in Dropbox and use them throughout all my computers. I have never experienced corruption issues from incomplete synchronizations, but just in case, I also manually maintain offline backups.

@SiTWulf
Copy link

SiTWulf commented May 17, 2024

A problem exist.
Every savegame uses a ramdom Save Folder.
For example, same game in PC uses 0000000000000026 save folder but in Steam Deck uses 0000000000000003
You not get a working Cloud Sync with ramdom save folders.

@deusnovus
Copy link
Author

deusnovus commented May 18, 2024

I am only using Linux in all my machines and I haven't encountered any problems transferring my entire "bis" folder from one computer to another via Dropbox; saves work as intended, though it would have been nice to have some semblance of what these random folders are. (like using a game's titleID for a folder name)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants