Hello,

is it possible to give the mcmod.info file another name? For example core_mod.info and if so where can I set it?

I would like to create a specific .info file for every child mod of my mod...

 

 

- Busti

 

How have you organized your development workspace for "child" mods?  Each mod, child or otherwise, should have its own project folder with its own mcmod.info. There shouldn't be any need to name them differently.

I guess an image is good for explanation here:

http://puu.sh/arW3I.png

I'm not sure that is the best way to organize mods that work together.  I think you should have them all at same level in the workspace (each with own /src folder).  Then to use them together they should have API that can be called from each other, and if any depend on others you should list them as dependencies (in the mcmod.info).

 

How are you building the directory structure you have currently?  It seems like it would be a problem to have the source all intermingled like that.

I'm orienting myself at Project Red... The different mods are not like "SubMods" but more like different Components...

I am just trying to find out how Project Red managed to create multiple .info files for every component.

https://github.com/MrTJP/ProjectRed/tree/master/resources

Okay, they are doing a kinda a complicated build.gradle that actually renames each one to mcmod.info during the build.  Look at their build.gradle file.  It has lines such as:

        rename ("lighting_mod.info", 'mcmod.info')

 

When building code, you can pretty much navigate all sorts of folder structures.  But I don't think doing it their way is necessary.  But yeah if you want to mess around with the build.gradle you can pick up the files you need from any folder structure.