Difference between revisions of "Talk:OXP howto AI"
m |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | list of lacking method descriptions.. |
+ | running list of most lacking method descriptions.. |
| − | + | ||
| − | * |
+ | *performLanding |
*setDestinationToDockingAbort |
*setDestinationToDockingAbort |
||
| − | *markTargetForFines |
||
| + | *setPlanetPatrolCoordinates |
||
| − | *patrolReportIn |
||
| − | *messageMother |
||
| − | *groupAttackTarget |
||
| − | *commsMessage |
||
| − | *wormholeEntireGroup |
||
*setDestinationWithinTarget |
*setDestinationWithinTarget |
||
| − | *setAITo |
||
| + | *patrolReportIn |
||
| − | *findNearestPlanet |
||
| + | *addFuel |
||
| − | *setDestinationFromCoordinates |
||
| + | *setDestinationToDockingAbort |
||
| − | *setTargetToFoundTarget |
||
| + | --[[User:Murgh|Murgh]] 20:11, 26 January 2006 (UTC) |
||
| − | *setSpeedFactorTo <-> setSpeedTo |
||
| + | |||
| − | *setDestinationToCurrentLocation |
||
| − | [[User: Murgh| Murgh]] |
||
OK updated and added various entries. |
OK updated and added various entries. |
||
[[User: Arexack|Arexack]] |
[[User: Arexack|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. |
||
| + | |||
| + | --[[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 |
||
| + | |||
| + | == 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? |
||
| + | |||
| + | [[User:Arexack|Arexack]]1600 monday |
||
| + | --[[User:Arexack|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. [[User: Murgh| Murgh]] |
||
| + | |||
| + | |||
| + | this new line by [[User: 82.171.18.144|82.171.18.144]].. |
||
| + | ==== checkForShips: type === |
||
| + | Returns with shipsFound_number = #. |
||
| + | |||
| + | in a script or planetinfo, yes but does this work in AI? [[User: Murgh| Murgh]] |
||
| + | |||
| + | Don't see why not. A_H |
||
| + | : |
||
| + | Now I find myself asking: why is this method included in the AI-methodlist? A_H |
||
| + | |||
| + | : |
||
| + | Other scripting question: |
||
| + | condition = (A , B , C) |
||
| + | do = action |
||
| + | is this an AND or an OR function? |
||
| + | |||
| + | An AND fuction could be built like: |
||
| + | condition = A |
||
| + | do = condition B |
||
| + | do = condition C |
||
| + | do = action |
||
| + | A_H |
||
Latest revision as of 00:11, 17 March 2007
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
Now I find myself asking: why is this method included in the AI-methodlist? A_H
Other scripting question: condition = (A , B , C) do = action is this an AND or an OR function?
An AND fuction could be built like:
condition = A
do = condition B
do = condition C
do = action
A_H
