Looking for some advice on making a ModuleConfig.xml

[InfamousNate]

I'm making some installers for a few of my mods and I've run into something that's not really covered in the NMM Installer Tutorial.

 

I've gotten the basic "Do you have (DLC Name)? yes/no" option down, but I'm not sure how to add branches to this. Say I have 4 variations of the same mod. 2 that require DG and two that don't, but within each of those two options I have a red option and a blue option. What would I need to add to the xml to allow the fomod to recognize this process?

 

Would the folder structure be like this?

00 - Dawnguard (only contains an esp and meshes)

01 - Vanilla (only contains an esp and meshes)

02 - Red Option (only contains red textures)

03 - Blue Option (only contains blue textures)

 

Or since the meshes are the same for all versions should I just add a core folder at 00 with only the meshes inside?

 

00 - Core (meshes)

01 - Dawnguard (esp)

02 - Vanilla (esp)

03 - Red Option (red textures)

04 - Blue Option (blue textures)

 

Any advice would be greatly appreciated. :sweat:

[blattgeist]

1. split the config into 2 parts, one that defines the options that are displayed to the user and also sets condition flags, another one that installs the files based on specific conditions. This way you can say in part 2 I want to install the Red Dawnguard version of my mod if the following conditions are met: DG flag=yes/on, core flag=yes/on, red flag=yes/on.

 

I've struggled a whole day to get this right in my own mod. If you want you can check my mod's xml file out, there are even some explanations inside the file (green text).

 

Please note "on" and "off" have to be specified. The installer won't know that there is an "off" just because you have defined an "on" for a flag. You have to set the flag to "off" somewhere in the installer if you want an "off" flag as a condition.

Edited July 29, 2015 by blattgeist