How to code a mod that's a dependency?

[thebest108]

So I'm separating the custom collision system from my mod so I can integrate it into other mods, but I'm having an issue with getting it to build separately and such.

 

The idea is that each mod will come with a copy of the custom collision, and using the library system only 1 version will load and all involved mods will run through that. Things get more complicated though because this library mod needs ASM (Invokestatic Override on moveEntity() and onUpdate(), so only 1 instance can be loaded), and needs to poll data from other mods somehow as well. On top of that, I want to keep it in the same development workspace as the mods that use it, yet still compile correctly with the build.gradle file. I need to define attributes like FMLCorePlugin "Location of Plugin" and FMLCorePluginContainsFMLMod, but these seem to apply to every file in the project, not to specific packages.

 

Anyway how can I structure such a library mod to accomplish all of this?

[Choonster]

Can't you just package it as a regular mod and have other mods add it as a dependency manually or through Maven?

 

I'd suggest using the new ContainedDep mechanic to package your mod inside other mods, but it doesn't look like contained mods can be coremods (at least not when they're first extracted).