Difference between revisions of "Talk:Route1patrolAI"
(signed, forgot to logon) |
|||
| Line 11: | Line 11: | ||
[[User:Araxack|Arexack]] | [[User:Araxack|Arexack]] | ||
| + | |||
| + | 2) Actually in the docking states it's better that the carrier makes no response personally. So setting these non-existant states does no harm. I've fixed the AI so it doesn't do this from now on (v1.63). | ||
| + | |||
| + | WRT checkCourseToDestination and WAYPOINT_SET | ||
| + | |||
| + | This is a nasty hack really, it's how the AI manages to avoid hazards like planets and space-stations along the route chosen. But it doesn't easily preserve the 'final' destination or a 'final' state. | ||
| + | |||
| + | It's had to think of a better way to implement this ATM. --[[User:Aegidian|Aegidian]] 10:51, 2 February 2006 (UTC) | ||
Latest revision as of 11:51, 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?
2) Actually in the docking states it's better that the carrier makes no response personally. So setting these non-existant states does no harm. I've fixed the AI so it doesn't do this from now on (v1.63).
WRT checkCourseToDestination and WAYPOINT_SET
This is a nasty hack really, it's how the AI manages to avoid hazards like planets and space-stations along the route chosen. But it doesn't easily preserve the 'final' destination or a 'final' state.
It's had to think of a better way to implement this ATM. --Aegidian 10:51, 2 February 2006 (UTC)
