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

Search for mods recursively #81

Open
sargunv opened this issue Mar 30, 2019 · 10 comments · May be fixed by #994
Open

Search for mods recursively #81

sargunv opened this issue Mar 30, 2019 · 10 comments · May be fixed by #994

Comments

@sargunv
Copy link
Contributor

sargunv commented Mar 30, 2019

I'd love to be able to organize my mods however I like within the "mods/" folder, so for example I could maintain a structure like this:

minecraft/
| mods/
  | lib/
    | fabric.jar
    | fabric-language-kotlin.jar
    | cloth.jar
    | crochet.jar
  | core/
    | roughly-enough-items.jar
    | modmenu.jar
  | content/
    | level-up-hp.jar
    | some-really-cool-mod.jar
  | utility/
    | lead-villagers.jar
    | some-tweaks-here.jar
@liach
Copy link
Contributor

liach commented Mar 30, 2019

For now, you can use prefix in your mod jar names to serve this purpose while getting mods loaded by the loader.

@liach
Copy link
Contributor

liach commented Nov 24, 2019

We should have a vote on this. I disagree as people may actually use folders to put their disabled mods in.

@Pannoniae
Copy link

You can treat a folder named "disabled" as a special-case for disabled mods, and everything else as just a category.

@liach
Copy link
Contributor

liach commented Nov 24, 2019

Imo there are just too many "special cases" to consider, including version-specific folders, etc. maybe we can have a file that defines what folders to load from? (bad idea possibly, overcomplicated)

@Frontrider
Copy link

I'd say that if you want to remove a mod then actually remove that mod, or add a ".disabled" extension to the file like multimc does.

@Julienraptor01
Copy link

Julienraptor01 commented Jun 11, 2022

One idea could be that by default subfolders are loaded except :
If the name of the folder is a MC version that isn't the one used
If the name of the folder end by .disabled

If recursivity is added and a subfolder is in a subfolder, will it be loaded
Example of what i mean

mods
->1.16.5
-->libs
--->someLib+v1.0.0.jar
--->someOtherLib+v1.0.0.jar
-->mods
--->someMod+v1.0.0.jar
--->someOtherMod+v1.0.0.jar
-->notWorking.disabled
--->anotherMod+v1.0.0.jar
->1.18.2
-->libs
--->someLib+v2.0.0.jar
--->someOtherLib+v2.0.0.jar
-->mods
--->someMod+v2.0.0.jar
--->someOtherMod+v2.0.0.jar
-->notWorking.disabled
--->anotherMod+v2.0.0.jar

@sfPlayer1
Copy link
Contributor

Recursive loading is currently only available with some customization, e.g. -Dfabric.addMods=mods effectively makes the whole folder recursively available

@Julienraptor01
Copy link

Recursive loading is currently only available with some customization, e.g. -Dfabric.addMods=mods effectively makes the whole folder recursively available

Nice 👍
Having this feature toggleable is a really good idea.
Version sorting and folder disabling could be a great addition.

@MJRamon
Copy link

MJRamon commented Jul 2, 2024

Bumping this, as it is essential feature for server owners and modpack makers.

@claymorwan
Copy link

We need this feature fr, I have multiple mc instances, one being a vanilla with clients mods, but that means I have to manually add the client mod to every instance everytime I add one. It would be easier if I could just link my mod folder for the client only mods to my otehr instances so I just have to add it to 1 directory to get it sync

@notTamion notTamion linked a pull request Oct 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants