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

Suggestion: Move PortableMC files from work-dir to main-dir #234

Open
RuiNtD opened this issue Nov 13, 2024 · 3 comments
Open

Suggestion: Move PortableMC files from work-dir to main-dir #234

RuiNtD opened this issue Nov 13, 2024 · 3 comments

Comments

@RuiNtD
Copy link

RuiNtD commented Nov 13, 2024

In PortableMC's current state, it's hard to use it for multiple "instances", since every instance (every distinct --work-dir) has its own portablemc_auth.json, requiring the user to login to each instance. It would be nice if PortableMC put its own files (including portablemc_version_manifest.json) into main-dir, next to assets and libraries, which would be consistent with every other Minecraft launcher.

@mindstorm38
Copy link
Owner

mindstorm38 commented Nov 15, 2024

Thanks for the suggestion! This improvement will be definitely included in the next major version, which is the rewrite in Rust (see #196). The portablemc_version_manifest.json file will be removed definitely and replaced by a file cache in standard OS-specific user local cache directory, for the authentication database, it's not yet implemented in the rewrite, but we'll support an argument to specify the location of the database. By default, it will still be located in the work dir by default I think, because my idea is that the main directory should possibly be read-only to users (allowing shared main directory). But at the same time it's right, and I've been thinking about this for some time, that it can also be very practical to also share a common database to all users, I'm very interested in your opinion about that!

@RuiNtD
Copy link
Author

RuiNtD commented Nov 15, 2024

In my mind the main dir is meant for anything launcher related and the work dir should be strictly for the game itself. Minecraft Launcher, as well as every other launcher, make this distinction and put the auth files in a consistent location, along with assets and libraries. It might make sense with the rewrite to tweak these argument names. work-dir could probably be mc-dir and main-dir could probably stay as-is.

@mindstorm38
Copy link
Owner

I like this opinion, and the mc-dir arg is a great idea I never thought about, I'll consider implementing this! I'll also consider adding an argument for changing the database location manually if needed, and by the way there will be support for specifying these via env variables!

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