Difference between revisions of "Script.plist"
From Elite Wiki
(→Conditions) |
(→Conditions: formatting example) |
||
| Line 4: | Line 4: | ||
Check whether the current status of the player are equal, lessthan or morethan a given value or state. | Check whether the current status of the player are equal, lessthan or morethan a given value or state. | ||
| − | + | example: | |
| − | + | <key>conditions</key> | |
| − | + | <dict> | |
| − | + | <array> | |
| − | + | <string>shipsFound_number equal 0</string> | |
| − | + | </array> | |
| − | + | </dict> | |
== Do == | == Do == | ||
Revision as of 18:48, 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 the player are equal, lessthan or morethan a given value or state.
example:
<key>conditions</key>
<dict>
<array>
<string>shipsFound_number equal 0</string>
</array>
</dict>
Do
The action to perform when conditions are met.
Example:
- <key>do</key>
- <dict>
- <array>
- <string>addShips: asp-cloaked 1</string>
- </array>
- <array>
- </dict>
- <dict>
- </key>
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.
