[Feature Request] Add option to disable dependency management

[Cloudperry]

trafficstars

Sometimes the dependencies of mods are just wrong. For example the mod Syncmatica has Malilib and Litematica as dependencies, but both of those are not required on a server just like the setup instructions say. I'm sure there are many more cases of mods dependencies being wrong with mods that are for both the client and the server.

The optimal solution for this would be adding an option to disable dependency management per mod. Just having an option to disable dependency management completely would be a really good solution as well. I think that managing mods' dependencies manually is really easy, because most mods have 0-2 dependencies.

Edit: Removed paragraph about my dumb old way to manage server and client mods.

[jakobkmar]

Thank you for your suggestion! I will have a look into this and change the system so that it supports this use case.

However, please note that I don't have the time to implement this right away.

[Cloudperry]

Soon after posting this I thought of having the same mods folder for client and server and it seems that Fabric handles that really well. All the mods that are client only just don't get loaded on the server and vice versa. With that approach duplicate dependencies in client/server mods are not an issue anymore.

[JustCryen]

To be fair, at this point you probably could symlink the directory and manage everything from one archive

[Cloudperry]

Yeah thats exactly what I meant with my last comment. I meant that I will have one mods folder (archive) and symlink the server and client folders there. The reason I managed my mods separately before was that I didn't know Fabric would handle same mods folder for client/server that well.