Difference between revisions of "AI SW Targeting"
| Line 8: | Line 8: | ||
:Super weapons with {{TTL|AITargetingType|1}} set. | :Super weapons with {{TTL|AITargetingType|1}} set. | ||
| − | See [[:Category:AIIonCannon_Flags|here]] for a list of such flags. If one of these flags is missing but the relevant object exists on the map, it can cause an [[Internal Error]]. | + | See [[:Category:AIIonCannon_Flags|here]] for a list of such flags. If one of these flags is missing but the relevant object exists on the map, it can cause an [[Internal Error]]. All flags have three values for hard, medium and easy difficulty, in this order. In at least RA2, the only difference between medium and hard is that on the latter, the AI checks if a possible target is in production; if it is and it has higher priority, then the AI will wait until production is complete then strike (according to Rules.ini comments). |
{{SourceCode|http://dc.strategy-x.com/src2/HouseClass/PickIonCannonTarget.cpp|tr=yes}} | {{SourceCode|http://dc.strategy-x.com/src2/HouseClass/PickIonCannonTarget.cpp|tr=yes}} | ||
[[Category:AIIonCannon_Flags| ]] | [[Category:AIIonCannon_Flags| ]] | ||
Revision as of 21:14, 21 August 2009
The [[[:Template:TTL]]] section has several flags relating to AI offensive Super Weapon targeting. They all share the same behaviour - they state the "priority" or "importance" of certain object types when evaluating the best target. This targeting model applies to super weapons with the following settings:
- TS
- Template:TTL
- Template:TTL
- RA2/YR
- Template:TTL
- Template:TTL
- Super weapons with Template:TTL set.
See here for a list of such flags. If one of these flags is missing but the relevant object exists on the map, it can cause an Internal Error. All flags have three values for hard, medium and easy difficulty, in this order. In at least RA2, the only difference between medium and hard is that on the latter, the AI checks if a possible target is in production; if it is and it has higher priority, then the AI will wait until production is complete then strike (according to Rules.ini comments).
