Talk:Route1patrolAI - Revision history

Aegidian at 10:51, 2 February 2006

2006-02-02T10:51:49Z

82.171.18.144: signed, forgot to logon

2006-02-02T00:16:27Z

signed, forgot to logon

82.171.18.144 at 00:09, 2 February 2006

2006-02-02T00:09:02Z

82.171.18.144: number2: undefined state

2006-02-02T00:07:27Z

number2: undefined state

82.171.18.144: Several errors in this one: 1Outboundloot

2006-02-02T00:05:20Z

Several errors in this one: 1Outboundloot

New page

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.

← Older revision		Revision as of 10:51, 2 February 2006
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)

← Older revision		Revision as of 00:16, 2 February 2006
Line 9:		Line 9:
	"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET");		"GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET");
	state 'ATTACK_TARGET' is undefined. Why not use 'setAIto: interceptAI.plist' like everywhere else?		state 'ATTACK_TARGET' is undefined. Why not use 'setAIto: interceptAI.plist' like everywhere else?
		+
		+	[[User:Araxack\|Arexack]]

@@ Line 1: / Line 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.
 DOCKING_WITCHPOINT:
  "GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setStateTo: ATTACK_TARGET");

← Older revision		Revision as of 00:07, 2 February 2006
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?