Difference between revisions of "Talk:OXP howto AI"
(Giles's thoughts) |
m |
||
Line 33: | Line 33: | ||
--[[User:Aegidian|Aegidian]] 11:22, 22 January 2006 (UTC) | --[[User:Aegidian|Aegidian]] 11:22, 22 January 2006 (UTC) | ||
+ | |||
+ | Hmm.. I did refer somewhere to '''AIreference.htm''' residing in the oolite folder, that file contains a reasonably coherent explanation on AI-states and messages. | ||
+ | |||
+ | 'AddFuel #' ... is it not 'awardFuel #'? | ||
+ | [[Arexack|Arexack]] Mo1:52AM 23jan06 |
Revision as of 00:56, 23 January 2006
list of lacking method descriptions..
- addFuel
- recallDockingInstructions
- setDestinationToDockingAbort
- markTargetForFines
- patrolReportIn
- messageMother
- groupAttackTarget
- commsMessage
- wormholeEntireGroup
- setDestinationWithinTarget
- setAITo
- findNearestPlanet
- setDestinationFromCoordinates
- setTargetToFoundTarget
- setSpeedFactorTo <-> setSpeedTo
- setDestinationToCurrentLocation
OK updated and added various entries. Arexack
Giles's thoughts
Needs an introduction explaining what a state-machine is and how Oolite uses them in its AI.
Also how AI receive messages (in the form of strings) and processes messages about every five seconds (depending on the pauseAI set), except when asked to react to a certain message.
A simple state machine should be given as an example and then shown as a property list.
Note that I'm likely to expand the use of AI in Oolite:- ship pilots will also have AI which will receive copies of messages sent to the ship's AI, but pilots AI's will perform a more 'strategic' role.
--Aegidian 11:22, 22 January 2006 (UTC)
Hmm.. I did refer somewhere to AIreference.htm residing in the oolite folder, that file contains a reasonably coherent explanation on AI-states and messages.
'AddFuel #' ... is it not 'awardFuel #'? Arexack Mo1:52AM 23jan06