glider1
Deity
As of RevolutionDCM 2.0 onwards, we have basic WoC Lite compatibility. This forum is for discussing all aspects of WoC included in RevolutionDCM, including WoC modules and any problems or thoughts about RevolutionDCM with WoC.
The basic philosophy with RevolutionDCM 2.0 is hybridization. This means a standard modding design combined with a WoC design. The most fundamental mods that add functionality to BTS, are hard coded into the core but controllable through the interface, while extra "clothing" is added to RevolutionDCM via WoC and is controllable simply by adding and removing modules.
Therefore the proposed direction for RevolutionDCM WoC development is this:
1) That the core mod components that are in RevDCM now be continually improved within the hardcoded core as it is now so that very high standards of quality and familiarity remain, and always ensuring that the code can be controlled via the interface.
2) That any WoC additions in the future that require modification to the core itself should be very easy to merge and maintain and be of exceptional quality. The WoC core code that is inserted, we must ensure at all times does not execute when the WoC module is removed.
3) That the RevolutionDCM core AI with any future WoC in it, should not diminish the cohesive and coherent partnership with the Better BTS AI and the two should remain cleanly tracked with each other.
4) That RevolutionDCM always remains compatible with the heavy weight mods that currently use RevolutionDCM as their backbone. These mods are specifically maintained and improved by dedicated modders and this model of design is known to work well.
Thoughts and discussions about all aspects of WoC with RevolutionDCM are welcome.
Cheers.
The definition of "easy merge" means:
The WoC SDK code is excellently commented
The definition of "easy maintenance" means:
The WoC SDK code is compact and concise and preferably is not so complex as be deeply distributed throughout the entire SDK. This greatly puts more weight on smaller WoC modules that are relevant to RevolutionDCM with only a small footprint in the SDK.
The basic philosophy with RevolutionDCM 2.0 is hybridization. This means a standard modding design combined with a WoC design. The most fundamental mods that add functionality to BTS, are hard coded into the core but controllable through the interface, while extra "clothing" is added to RevolutionDCM via WoC and is controllable simply by adding and removing modules.
Therefore the proposed direction for RevolutionDCM WoC development is this:
1) That the core mod components that are in RevDCM now be continually improved within the hardcoded core as it is now so that very high standards of quality and familiarity remain, and always ensuring that the code can be controlled via the interface.
2) That any WoC additions in the future that require modification to the core itself should be very easy to merge and maintain and be of exceptional quality. The WoC core code that is inserted, we must ensure at all times does not execute when the WoC module is removed.
3) That the RevolutionDCM core AI with any future WoC in it, should not diminish the cohesive and coherent partnership with the Better BTS AI and the two should remain cleanly tracked with each other.
4) That RevolutionDCM always remains compatible with the heavy weight mods that currently use RevolutionDCM as their backbone. These mods are specifically maintained and improved by dedicated modders and this model of design is known to work well.
Thoughts and discussions about all aspects of WoC with RevolutionDCM are welcome.
Cheers.
The definition of "easy merge" means:
The WoC SDK code is excellently commented
The definition of "easy maintenance" means:
The WoC SDK code is compact and concise and preferably is not so complex as be deeply distributed throughout the entire SDK. This greatly puts more weight on smaller WoC modules that are relevant to RevolutionDCM with only a small footprint in the SDK.
Wonders compilation (compiled by Johny Smith)
