Difference between revisions of "Script.plist"
m (→Do: plural actions) |
(→Conditions: change description) |
||
| Line 2: | Line 2: | ||
== Conditions == | == Conditions == | ||
| − | Check whether the current status of | + | Check whether the current status of one of a number of queriable states are '''equal''', '''lessthan''', '''morethan''' a given value or state, or '''oneof''' a list of space separated states. |
example: | example: | ||
Revision as of 18:53, 20 January 2006
script.plist Used by missions and OXP's to check conditions and change scripted parameters accordingly. In OXP's it provides Oolite with additional information to generate and populate customised systems. Every condition is followed by a scripted action, a 'Do' or 'Else' entry, a 'do' entry can be nested (have conditions, followed by Do)
Conditions
Check whether the current status of one of a number of queriable states are equal, lessthan, morethan a given value or state, or oneof a list of space separated states.
example:
<key>conditions</key>
<dict>
<array>
<string>shipsFound_number equal 0</string>
</array>
</dict>
Do
The actions to perform when conditions are met.
Example:
<key>do</key>
<dict>
<array>
<string>addShips: asp-cloaked 1</string>
<string>addShips: pirate 12</string>
</array>
</dict>
Else
Actions performed when conditions are not met. Same as "Do".
Just a small start. probably better to list the condition parameters, methods in their own Omnibus. A_H
This is a stubby stub.
