Difference between revisions of "Talk:OXP howto AI"
(→= checkForShips: type) |
|||
| Line 50: | Line 50: | ||
in a script or planetinfo, yes but does this work in AI? [[User: Murgh| Murgh]] |
in a script or planetinfo, yes but does this work in AI? [[User: Murgh| Murgh]] |
||
| + | |||
| + | Don't see why not. A_H |
||
Revision as of 22:28, 31 January 2006
running list of most lacking method descriptions..
- performLanding
- setDestinationToDockingAbort
- setPlanetPatrolCoordinates
- setDestinationWithinTarget
- patrolReportIn
- addFuel
- setDestinationToDockingAbort
--Murgh 20:11, 26 January 2006 (UTC)
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
Arexack's meddling
I just reorganised the entries into functional groups.
Should we keep this list format (for linking purposes) or replace the === with * for better overview?
Arexack1600 monday --Arexack 15:07, 23 January 2006 (UTC)
- I like it. it's better this way with the hypertext index than replacing them with * rows, I think. Murgh
this new line by 82.171.18.144..
= checkForShips: type
Returns with shipsFound_number = #.
in a script or planetinfo, yes but does this work in AI? Murgh
Don't see why not. A_H
