Difference between revisions of "Talk:Route1patrolAI"

From Elite Wiki
(Several errors in this one: 1Outboundloot)
 
(number2: undefined state)
Line 1: Line 1:
  +
OUTBOUND_LOOT:
 
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.
  +
  +
DOCKING_WITCHPOINT:
  +
"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET");
  +
state 'ATTACK_TARGET' is undefined. Why not use 'setAIto: interceptAI.plist' like everywhere else?

Revision as of 01:07, 2 February 2006

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.

DOCKING_WITCHPOINT:

"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET"); 

state 'ATTACK_TARGET' is undefined. Why not use 'setAIto: interceptAI.plist' like everywhere else?