Stacked AI - Revision history

Eric Walch: indexing

2007-12-23T12:30:15Z

indexing

Winston at 13:23, 12 July 2006

2006-07-12T13:23:27Z

Arexack: /* Example of a multi-layer stacked AI-system: */

2006-01-23T20:53:17Z

‎Example of a multi-layer stacked AI-system:

Arexack: /* RESTART */

2006-01-23T20:33:00Z

‎RESTART

Arexack: /* Example of a multi-layer stacked AI-system: */

2006-01-23T20:31:18Z

‎Example of a multi-layer stacked AI-system:

Arexack: rewritten stackingAI examples after accidental deletion.

2006-01-23T20:30:35Z

rewritten stackingAI examples after accidental deletion.

New page

The best way to avoid overly-complex AI's is to use 'stacked'AI's.

An AI(firstAI.plist) can stack another AI(secondAI.plist) on top of itself by calling the method 'setAITo: secondAI.plist'.

One could design a ''''scaffoldAI'''' that defines the entity's default behaviour, have this call for specialised jobAI's when such specific behaviour is called for.

Specialised '''JobAI''''s need to ''''exitAI'''' in order for the [[state machine]] to return to the previous AI.

('''! Warning:''' do not use another 'setAITo' action to return to a previous state unless there is a good reason for doing so. To do so could lead to recursive AI loops, resulting in memoryleaks and crashes.)

'''Alternatively:''' the completion of a job results in the ending of the entity (leaves system or destruction for example). Entity death should exit all AI's in the stack.

== Example of a multi-layer stacked AI-system: ==
'''defaultAI:'''
Jobdescription: Navigate from witchpoint to station,
ATTACKED = "setAITo: job1AI.plist"

'''job1AI:'''
*STATE1 Jobdescription: Combat, scan for hostiles, attack.
NO_TARGET = "set state to STATE2"
*STATE2 Jobdescription: scanforloot/Attacked setStateTo:State1
NOTARGET = "exitAI"
TARGETFOUND = "setAITo: job2AI.plist"

'''job2AI:'''
*STATE1 jobdescription: scanfor and collect loot.
NOTARGET = "exitAI"

== RESTART ==
Is the message recieved when a halted AI returns to the top of the stack.

So alternatively we could have organised the above system in a less complex way:

'''defaultAI:'''
*STATE1 Jobdescription: Navigate from witchpoint to station,
ATTACKED = ("setAITo: job1AI.plist");
RESTART = ("setStateTo: STATE2");
*STATE2 Jobdescription: scan for loot
TARGET_FOUND = (setAITo: job2.plist");
ATTACKED = ("setAITo: job1AI.plist");
NO_TARGET = ("setStateTo: STATE1");
UPDATE = (scanForLoot);

'''job1AI:'''
*STATE1 Jobdescription: combat; scanForHostiles,attack,etc.
NO_TARGET = "exitAI"

'''job2AI:'''
*STATE1 jobdescription: scanfor and collect loot.
NO_TARGET = "exitAI"

== Note ==
The above examles have highly simplified AI scripts, for complete AI structure go [[OXP_howto_AI|here]].

Working examples of JobAI are collectLootAI.plist and InterceptAI.plist.

A working example of a 'scaffold'AI is route1PatrollAI.plist.

== Links ==
[[OXP_howto]]
[[OXP_howto_AI]]
Back to: [[State_machine]]

← Older revision		Revision as of 12:30, 23 December 2007
Line 65:		Line 65:

	[[Category:Oolite]]		[[Category:Oolite]]
		+	[[Category:Oolite scripting]]

← Older revision		Revision as of 13:23, 12 July 2006
Line 62:		Line 62:
	[[OXP_howto_AI]]		[[OXP_howto_AI]]
	Back to: [[State_machine]]		Back to: [[State_machine]]
		+
		+
		+	[[Category:Oolite]]

@@ Line 24: / Line 24: @@
  '''job2AI:'''
- *STATE1 jobdescription: scanfor and collect loot.
+ *STATE1 jobdescription: performCollect (loot).
  NOTARGET = "exitAI"

@@ Line 44: / Line 44: @@
  '''job1AI:'''
  *STATE1 Jobdescription: combat; scanForHostiles,attack,etc.
-  NO_TARGET = "exitAI"
+  NO_TARGET = (exitAI)
  '''job2AI:'''
  *STATE1 jobdescription: scanfor and collect loot.
- NO_TARGET = "exitAI"
+ NO_TARGET = (exitAI)
 == Note ==

@@ Line 15: / Line 15: @@
  Jobdescription: Navigate from witchpoint to station,
  ATTACKED = "setAITo: job1AI.plist"
  '''job1AI:'''
  *STATE1 Jobdescription: Combat, scan for hostiles, attack.
@@ Line 26: / Line 26: @@
  *STATE1 jobdescription: scanfor and collect loot.
  NOTARGET = "exitAI"
 == RESTART ==