phungus420
Deity
- Joined
- Mar 1, 2003
- Messages
- 6,296
I agree with keldath: Adding in AI logic for all terrain transports would be a good idea. keldath you should post your working code for this in the Specific Code Proposals thread in the RevDCM project form.
As a RevDCM user, and mod maker, I'm all for including components that do not harm or significantly alter RevDCM; so long as these components can easily be verified as stable. However one need only look at the Python Helpers thread to realize that easily verifiable stability is a big sticking point; at this point the Python Helpers mod component should not be added. The two main examples of components that are good to add are specific and useful XML tags and new stable AI logic (even for components not in base BtS so long as such components could be created using RevDCM XML --such as all terrain transports-- we should endeavor to support such modifications to RevDCM); such a development plan only helps out the mod makers who use a RevDCM core in their mods, and these mod's users. RevDCM has become the standard modding core for BtS, and it's good to support that role. However the line needs to be drawn sometimes. For a component to be included in the RevDCM core, that component must be simple and concise, or improve the functionality of a simple modification to RevDCM itself (XML mod). Again it's important to note RevDCM should not support all added components in other mods that use a RevDCM core; for instance, it would be foolish to have RevDCM try to support all the python components in Dune Wars; if a modpack team is modding complex things in their mod, they need to support it, this should not fall on glider and jdog. This line is important because of the stability issues which creep into projects like this if too many things are added; especially if they are added too quickly without enough assessment of their worth and stability.
@glider
I see this on the todo list:
WoC requires a file to be created/altered if any components are active. This file must be created/altered in the Program Files path. As such for Vistas Users they must launch as an admin, not doing so will cause a crash. The user can get around this by using launch as admin, and this is the defacto way all RevDCM mods are installed and used. However this is a poor work around, many users never bother, they simply see that the mod fails, and give up. To get around this I am working on an installer script so that the User Settings folder that BUG uses will be installed to a different path; users will no longer need to launch as an admin. However this fix will not work if any WoC components are active, the mod will always crash if not launched as an admin on Windows 7 and Vista. Forcing WoC on all heavy modpack makers is going to destroy this fix, and is not necessary. Keep all core RevDCM components in the core, if users want to use WoC, they may, but do not force us to use it.
For reference check here:
http://forums.civfanatics.com/showthread.php?t=341219
Edit, more Todo list stuff:
http://forums.civfanatics.com/showpost.php?p=8616533&postcount=34
It's all ready to merge, and has been checked. This is important code too as it eliminates all python callbacks.
Also MP compatibility is mysteriously absent from the current todo list
As a RevDCM user, and mod maker, I'm all for including components that do not harm or significantly alter RevDCM; so long as these components can easily be verified as stable. However one need only look at the Python Helpers thread to realize that easily verifiable stability is a big sticking point; at this point the Python Helpers mod component should not be added. The two main examples of components that are good to add are specific and useful XML tags and new stable AI logic (even for components not in base BtS so long as such components could be created using RevDCM XML --such as all terrain transports-- we should endeavor to support such modifications to RevDCM); such a development plan only helps out the mod makers who use a RevDCM core in their mods, and these mod's users. RevDCM has become the standard modding core for BtS, and it's good to support that role. However the line needs to be drawn sometimes. For a component to be included in the RevDCM core, that component must be simple and concise, or improve the functionality of a simple modification to RevDCM itself (XML mod). Again it's important to note RevDCM should not support all added components in other mods that use a RevDCM core; for instance, it would be foolish to have RevDCM try to support all the python components in Dune Wars; if a modpack team is modding complex things in their mod, they need to support it, this should not fall on glider and jdog. This line is important because of the stability issues which creep into projects like this if too many things are added; especially if they are added too quickly without enough assessment of their worth and stability.
@glider
I see this on the todo list:
It is absolutely imperative that you make it so that WoC is not required for core RevDCM components, such as super spies. WoCifying SS is a no go. And here is why:- Update RevDCM Super Spies to the WoC Super Spies BTS default format for promotions
WoC requires a file to be created/altered if any components are active. This file must be created/altered in the Program Files path. As such for Vistas Users they must launch as an admin, not doing so will cause a crash. The user can get around this by using launch as admin, and this is the defacto way all RevDCM mods are installed and used. However this is a poor work around, many users never bother, they simply see that the mod fails, and give up. To get around this I am working on an installer script so that the User Settings folder that BUG uses will be installed to a different path; users will no longer need to launch as an admin. However this fix will not work if any WoC components are active, the mod will always crash if not launched as an admin on Windows 7 and Vista. Forcing WoC on all heavy modpack makers is going to destroy this fix, and is not necessary. Keep all core RevDCM components in the core, if users want to use WoC, they may, but do not force us to use it.
For reference check here:
http://forums.civfanatics.com/showthread.php?t=341219
Edit, more Todo list stuff:
Done already see here:- Phungus says: Add civic required array to UnitInfos so the Inquisitor will no longer need to be hardcoded in the SDK, and the CannotTrain callback can be fully removed, also will add a modding tool. Add Gameoption tag in UnitInfos for unit trainability (reasons same as above, probably best to set it up so when selected a unit cannot be trained, this would mean Inquisitions would be on by default and the Inquistions gameoption would need to be No Inquistions)
- Phungus revdcm specific code proposals thread: changes to game options selections (inquisitor/espionage)
http://forums.civfanatics.com/showpost.php?p=8616533&postcount=34
It's all ready to merge, and has been checked. This is important code too as it eliminates all python callbacks.
Dom Pedro's Python helpers is not stable, multiple user reports of CTDs when using it.- glider: merge Dom Pedro's mod helper?
Also MP compatibility is mysteriously absent from the current todo list
