2 réponses à ce sujet

[TrixX]

Well just making a collated Chargenmorphcfg.xml to incorporate the largest and most used mods on Nexus/BSN at the moment.

 

Presets are being ignored for the most part as it's primarily for compatibility reasons. Has anyone got any tips for file structure/depth for the override folder setup?

 

Current layout is 3 folders deep with all files collated into their categories:

 

Chargenmods > [folder for file type] > [folder for pack details]

 

Presets go in the second level and the third level splits them into race (HM, HF, etc...)

 

Seeing as the Override folder can only see to a depth of 3 folders I've limited it this way. If this info is outdated or incorrect please let me know

 

So far I have around 40 different mods to compile in this way. I am also separating the Toolset items to their own directories for ease of finding/use.

[DarthParametric]

There is no need to manually compile it. Pretty much all mods that require custom entries in chargenmorphcfg.xml already direct users to Terra_Ex's CharGenMorph Compiler, which will produce a combined chargenmorphcfg.xml for all mods installed. There is little point in using one with entries for mods that are not present.

 

If you are talking about actually collating and redistributing other people's mods, that is a very big no no, unless you have explicit permission from the original mod authors.

[TrixX]

AH yes that's a good little tool, however from memory it hasn't the ability to work with just files and requires a correct base chargenmorph for each mod that is being added (unless I'm wrong!).

 

I have many mods that are required but have no chargenmorphcfg.xml file so need to add the entries manually. Even some of the more well known mods don't have all entries correct in their chargenmorph files. I made a compendium a while back basically so I could run the game with any of those mods hassle free.

 

I'm not looking to release a compilation mod or in any way redistributing others work, just looking for some advice on the mechanics of compiling them all into a single folder structure which is navigable and editable.