Difference between revisions of "Talk:Route1patrolAI"
From Elite Wiki
(number2: undefined state) |
|||
| Line 1: | Line 1: | ||
| − | OUTBOUND_LOOT: |
||
| + | 1) |
||
INCOMING_MISSILE" = (fightOrFleeMissile, setTargetToPrimaryAggressor, deployEscorts, groupAttackTarget, "setAITo: interceptAI.plist", "setStateTo: OUTBOUND_LOOT"); |
INCOMING_MISSILE" = (fightOrFleeMissile, setTargetToPrimaryAggressor, deployEscorts, groupAttackTarget, "setAITo: interceptAI.plist", "setStateTo: OUTBOUND_LOOT"); |
||
'setStateTo: OUTBOUND_LOOT' makes no sense here, put it in a RESTART message response. |
'setStateTo: OUTBOUND_LOOT' makes no sense here, put it in a RESTART message response. |
||
| + | |||
| + | 2) |
||
DOCKING_WITCHPOINT: |
DOCKING_WITCHPOINT: |
||
"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET"); |
"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET"); |
||
Revision as of 01:09, 2 February 2006
1)
INCOMING_MISSILE" = (fightOrFleeMissile, setTargetToPrimaryAggressor, deployEscorts, groupAttackTarget, "setAITo: interceptAI.plist", "setStateTo: OUTBOUND_LOOT");
'setStateTo: OUTBOUND_LOOT' makes no sense here, put it in a RESTART message response.
2)
DOCKING_WITCHPOINT:
"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET");
state 'ATTACK_TARGET' is undefined. Why not use 'setAIto: interceptAI.plist' like everywhere else?
