-
Notifications
You must be signed in to change notification settings - Fork 48
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
Symlink mods to output directories from a common mod storage #109
Comments
I really like this idea! It's basically how pnpm works actually. |
I got the idea from xmcl(x-minecraft-laucher)! |
You could probably have a hash in the mod's file name that is generated from the version of the mod, modloader, minecraft version and the ID or something like this. This is an awesome idea! |
Firstly this directly conflicts with #140, and it also provides no benefit over using the hash of the files' contents. |
If you regularly switch profiles then the mods could be stored in this store instead of constantly re-downloading possibly 100s of megabytes of mod files each and every time you want to switch profiles. |
I was referring to this in my comment. |
Profile 1 (quilt, 1.18.2):
Profile 2 (fabric, 1.18.2):
I hope that if the two profiles have identical mods, ferium will automatically symlink them from the same file.
Even if the
modloaderprofile settings are not the same, if the mod is the same they should be symlinked.The text was updated successfully, but these errors were encountered: