Messages - Revision history

Cholmondely: Tweaks! Added links, some explanations

2024-07-24T07:41:08Z

Tweaks! Added links, some explanations

SandJ: Just typos

2012-05-21T22:58:51Z

Just typos

Aegidian: /* Game defined states and messages */ better title of section

2006-01-23T17:26:45Z

‎Game defined states and messages: better title of section

Aegidian: /* Game defined states and messages */ more detail on how AI's process messages

2006-01-23T17:26:01Z

‎Game defined states and messages: more detail on how AI's process messages

Arexack: /* Links */ fixed link

2006-01-23T17:01:09Z

‎Links: fixed link

Arexack: new!

2006-01-23T16:57:51Z

new!

New page

== Game defined states and messages ==
When an AI [[state machine]] is started it is always put into the state GLOBAL, and the ENTER message will be sent.

The following table describes each '''message''' the game engine may send to an AI state machine.

These '''messages''' may be sent while processing commands executed by the AI state machine, or while the AI's controlled entity is performing it's current task.

ACCEPT_DISTRESS_CALL
AEGIS_CLOSE_TO_PLANET
AEGIS_IN_DOCKING_RANGE
AEGIS_LEAVING_DOCKING_RANGE
AEGIS_NONE
APPROACH_COORDINATES
APPROACH_START
APPROACH_STATION
ATTACKED
CARGO_SCOOPED
COLLISION
CONDITION_GREEN
// Lowest alert status of station entity, next level: Condition_Yellow.
CONDITION_YELLOW
// Second level of station entity alert status, next level: Red_Alert.
COURSE_OK
DEPLOYING_ESCORTS
DESIRED_RANGE_ACHIEVED
DOCKED
DOCKING_ABORTED
DOCKING_COMPLETE
DOCKING_REFUSED
DOCKING_REQUESTED
ECM
ENERGY_FULL
ENERGY_LOW
ENTER
// Always sent to the new (now current) state of the AI state machine
// after switching to a new state.
ENTERED_WITCHSPACE
ESCORTING
EXIT
// Always sent to the current state of the AI state machine before switching to a new state.
EXITED_WITCHSPACE
FACING_DESTINATION
FIGHTING
FLEEING
FRUSTRATED
GONE_BEYOND_RANGE
GROUP_ATTACK_TARGET
HOLD_FULL
HOLD_POSITION
INCOMING_MISSILE
LANDED_ON_PLANET
LAUNCHED
MOTHER_LOST
// sent if an escorting ship, or a group of ships loses it's Leader.
NO_STATION_FOUND
NO_TARGET
NOT_ESCORTING
NOTHING_FOUND
ODDS_BAD
ODDS_GOOD
ODDS_LEVEL
// Odds determined by CheckGroupOdds method.
REACHED_SAFETY
// Sent when the ship controlled by the AI is fleeing it's primary_target
// and is at least desired_range kms from it.
RED_ALERT
// Entity attacked.
RESTARTED
// Sent when an AI state machine is made the current AI state machine by
// becoming the top of the AI state machine stack for a particular entity.
STATION_FOUND
TARGET_CLEAN
TARGET_DESTROYED
TARGET_FOUND
// Sent when searching for a target and something suitable is found.
// The found_target can be made the primary target by calling setTargetToFoundTarget
// in response to this message.
TARGET_FUGITIVE
TARGET_LOST
TARGET_MARKED
TARGET_MINOR_OFFENDER
TARGET_OFFENDER
THARGOID_DESTROYED
TRY_AGAIN_LATER
UPDATE
// This message is sent to the current state each time the AI gets a chance to "think".
WAIT_FOR_SUN
WAYPOINT_SET
YELLOW_ALERT
// Hostile craft in scannerrange.

== Notes ==
{{Stub}}

== Links ==
[[OXP_Howto_AI]]
[[Category:Oolite]]

← Older revision		Revision as of 17:26, 23 January 2006
Line 1:		Line 1:
−	== ~~Game defined states~~ and ~~messages~~ ==	+	== AI States and Messages ==
	When an AI [[state machine]] is started it is always put into the state GLOBAL, and it will be sent an ''ENTER'' message.		When an AI [[state machine]] is started it is always put into the state GLOBAL, and it will be sent an ''ENTER'' message.

@@ Line 2: / Line 2: @@
 When an AI [[state machine]] is started it is always put into the state GLOBAL, and it will be sent an ''ENTER'' message.
-The following table describes some of the '''message'''s the game engine might send to an AI state machine.
+The following table describes some of the '''messages''' the game engine might send to an AI state machine.
-AIs might be passed these message as a matter of routine, in which case the AI will wait until its next cycle before reacting, or it might be asked to react to the given message immediately.
+AIs might be passed these messages as a matter of routine, in which case the AI will wait until its next cycle before reacting, or it might be asked to react to the given message immediately.
 When an AI reacts to a message it examines the state it is currently in: if the state has an entry for a given message it responds by performing the corresponding list of actions, if it has no corresponding entry the message is discarded and ignored.
@@ Line 21: / Line 21: @@
   COLLISION
   CONDITION_GREEN
- //  Lowest alert status of station entity, next level: Condition_Yellow.
+    Lowest alert status of station entity, next level: Condition_Yellow.
   CONDITION_YELLOW
- //  Second level of station entity alert status, next level: Red_Alert.
+    Second level of station entity alert status, next level: Red_Alert.
   COURSE_OK
   DEPLOYING_ESCORTS
@@ Line 36: / Line 36: @@
   ENERGY_LOW
   ENTER
- //  Always sent to the new (now current) state of the AI state machine
+    Always sent to the new (now current) state of the AI state machine after switching to a new state.
- //  after switching to a new state.
+    See [[State machine]] - "Program flow" for more detail
   ENTERED_WITCHSPACE
   ESCORTING
   EXIT
- //  Always sent to the current state of the AI state machine before switching to a new state.
+    Always sent to the current state of the AI state machine before switching to a new state.
   EXITED_WITCHSPACE
   FACING_DESTINATION
@@ Line 55: / Line 56: @@
   LAUNCHED
   MOTHER_LOST
- //  sent if an escorting ship, or a group of ships, loses its Leader.
+    sent if an escorting ship, or a group of ships, loses its Leader.
   NO_STATION_FOUND
   NO_TARGET
   NOT_ESCORTING
   NOTHING_FOUND
-  ODDS_BAD
+  ODDS_BAD   }
-  ODDS_GOOD
+  ODDS_GOOD  }    Odds determined by CheckGroupOdds method (see NOTES below)
- ODDS_LEVEL
+ ODDS_LEVEL }
   REACHED_SAFETY
- //  Sent when the ship controlled by the AI is fleeing its primary_target
+    Sent when the ship controlled by the AI is fleeing its primary_target and is at least desired_range kms from it.
   RED_ALERT
- //  Entity attacked.
+    Entity attacked.
   RESTARTED
- //  Sent when an AI state machine is made the current AI state machine by
+    Sent when an AI state machine is made the current AI state machine by becoming the top of the AI state machine stack for a particular entity.
   STATION_FOUND
   TARGET_CLEAN
   TARGET_DESTROYED
   TARGET_FOUND
- //  Sent when searching for a target and something suitable is found.
+    Sent when searching for a target and something suitable is found.
- //  The found_target can be made the primary target by calling setTargetToFoundTarget
+    The found_target can be made the primary target by calling setTargetToFoundTarget in response to this message.
   TARGET_FUGITIVE
   TARGET_LOST
@@ Line 87: / Line 84: @@
   TRY_AGAIN_LATER
   UPDATE
- //  This message is sent to the current state each time the AI gets a chance to "think".
+    This message is sent to the current state each time the AI gets a chance to "think".
   WAIT_FOR_SUN
   WAYPOINT_SET
   YELLOW_ALERT
- //  Hostile craft in scanner range.
+    Hostile craft in scanner range.
 == Notes ==
-  {{Stub}}
+=== Meta-Messages ===
 == Links ==
- [[OXP_howto_AI]]
+*[[OXP howto AI]] (.plist AI's)
 [[Category:Oolite]]

@@ Line 1: / Line 1: @@
 == Game defined states and messages ==
-When an AI [[state machine]] is started it is always put into the state GLOBAL, and the ENTER message will be sent.
+When an AI [[state machine]] is started it is always put into the state GLOBAL, and it will be sent an ''ENTER'' message.
-The following table describes each '''message''' the game engine may send to an AI state machine.
+The following table describes some of the '''message'''s the game engine might send to an AI state machine.
   ACCEPT_DISTRESS_CALL
@@ Line 88: / Line 91: @@
   WAYPOINT_SET
   YELLOW_ALERT
   //  Hostile craft in scannerrange.
 == Notes ==