Allow sub-folders within /mods (not version folders) for better organization

[elonhusk]

Hello,

 

Organizing mods is a nightmare and I've always wished I could use subfolders named with categories to place different types of mods into in my /mods directory but Forge doesn't like when I try it.

 

This would be easy to implement with dir.listFiles()

 

https://www.baeldung.com/java-list-directory-files

https://www.technicalkeeda.com/java-tutorials/java-file-listfiles-method-example

 

Example

/mods/

folder-named-worldgen/mods-about-worldgen

folder-named-mobs/mods-about-mobs

folder-named-biomes/mods-about-biomes

etc.

Edited March 2, 2020 by elonhusk

[LexManos]

I think he is asking for us to still load all of the mods, just to make us scan subfolders as well.

This is already possible with the mod discovery API we have.

I don't think we'll add this to Forge by default because it'd just be to prone to user errors. Duplicate mods, different versions, and the like.

I'm not seeing the benefit of something like this.

[Alpvax]

One case I can think of would be to have a folder of optional mods (renamed with .disabled after the extension to prevent loading). When modpacks get large it can become more difficult to find the ones you are looking for, and I don't see how more organisation can hurt. You can search if you know what mod you are looking for but you can't search for "optional mods". Duplicates/different versions would get flagged up on launch.

It could be put behind a config option.

Edited March 2, 2020 by Alpvax