EmperorFool
Deity
I'm considering merging the SDK portion of this into BULL and wanted to check that I'm doing it for the correct reason.
The BULL SDK code has several compile-time features which you enable by setting preprocessor flags. These are features which require changing constants or other core game info that would break saved game compatibility. For example, Sentry Actions require new Missions and Activity Types.
BULL puts the XML required for these features into the Optional folder. Some XML changes require inserting a block of XML into an existing file. Others require replacing a file entirely because one or two values are changed in many elements. I think this is where WoC Lite could really come in handy.
My hope is that I could change these XML files into modules that only changed the necessary data. The user would copy them into their Assets folder (or wherever they go) based on the BULL DLL version they chose. Is that correct?
Also, if two features add new Actions, they must line up exactly with the C++ constants in CvEnums.h. Thus, it is imperative that the user be able to specify module loading order. Is this where MLF files come into play?
The BULL SDK code has several compile-time features which you enable by setting preprocessor flags. These are features which require changing constants or other core game info that would break saved game compatibility. For example, Sentry Actions require new Missions and Activity Types.
BULL puts the XML required for these features into the Optional folder. Some XML changes require inserting a block of XML into an existing file. Others require replacing a file entirely because one or two values are changed in many elements. I think this is where WoC Lite could really come in handy.
My hope is that I could change these XML files into modules that only changed the necessary data. The user would copy them into their Assets folder (or wherever they go) based on the BULL DLL version they chose. Is that correct?
Also, if two features add new Actions, they must line up exactly with the C++ constants in CvEnums.h. Thus, it is imperative that the user be able to specify module loading order. Is this where MLF files come into play?