Global recourse packs - Githubissues

MultiMC / Launcher

A custom launcher for Minecraft that allows you to easily manage multiple installations of Minecraft at once

https://multimc.org/

Other

4.32k stars 883 forks source link

Global recourse packs #3861

Open Freddie-06 opened 3 years ago

Freddie-06 commented 3 years ago

Role

I play with many instances, all with the same recourse pack

Suggestion

I would like to have a folder, that automatically copies a file into every (new) instance, that is created.

Benefit

To make the time from clicking "new instance" to having a fully playable and personalized instance

This suggestion is unique

[X] I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.

Edit: spelling

bbb651 commented 3 years ago

Adding to this, instead of copying the file over it can use symlinks which will reduce redundant file size and disk usage for the copying operations.

spannerman79 commented 3 years ago

use symlinks

MultiMC is a portable application.

Furthermore on windows to create a symlink requires the use of elevated permissions on an OS where symlinking is known to be ...unstable at best.

No.

Freddie-06 commented 3 years ago

Furthermore on windows to create a symlink requires the use of elevated permissions Oof. That would not be good for a Minecraft launcher, and may take away potential users

bbb651 commented 3 years ago

You are right, I didn't take portability and other operating systems into account. I'm not sure how copying symlinks works but it would be nice if the end user could put a symlink instead resource pack and get the behavior I described, without drawbacks for other users.

glowiak commented 2 years ago

ln -s

LinkZeldasGuard commented 2 years ago

What about instead of using symlinks or copying the files over, could you not just redirect Minecraft to use a "global resoucepacks" folder outside of the "instances" folder? I mean like similar to the official Launcher where you can select your on repository for the installation. Wouldn't it be possible to do just that, but split it up into the seperate folders like "resourcepacks", "saves", etc, so you can assign one resourcepacks folder to all of your instances, that is, if you want of couse, I'd keep the current system and just make it optional.