Search for mods recursively

[fabricmc]

Search for mods recursively

[Pannoniae]

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

[sfPlayer1]

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

[liach]

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

[Julienraptor01]

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

[Frontrider]

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.

[liach]

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

[liach]

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)

[Julienraptor01]

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.