Difference between revisions of "Shipdata structure"
From Elite Wiki
Cholmondely (talk | contribs) (Tagged as Legacy Scripting) |
Cholmondely (talk | contribs) (Added links to examples (I hope!)) |
||
| Line 29: | Line 29: | ||
* See [[Shipdata.plist]] for relevant properties. | * See [[Shipdata.plist]] for relevant properties. | ||
| + | |||
| + | * There are examples of subentities in [[Z GrOovy HPC pack]] (2014), [[Refugee Adder]] (2006, XML), [[Animated Ships]] (2010), [Oolite Stations|stations]] - the docking bay for one thing | ||
[[Category:Oolite]] [[Category:Legacy scripting]] | [[Category:Oolite]] [[Category:Legacy scripting]] | ||
Revision as of 06:00, 22 June 2022
Every entity is defined by a title-key, followed by a <dict>ionary of the object's properties. Do not use '-'(minus symbol) in the entity title.
The structure of the shipdata.plist is as follows:
XML:
***usual XML-Header info***
<plist>
<dict>
<key>my_object</key>
<dict>
(all relevant property entries)
</dict>
<!-- between these everything will be ignored, convenient for selfcomments -->
<key>my_second_object</key>
<dict>
(all relevant property entries)
</dict>
</dict>
</plist>
OpenStep:
{
// comment
"my_object" = {
(all relevant property entries)
};
}
- See Shipdata.plist for relevant properties.
- There are examples of subentities in Z GrOovy HPC pack (2014), Refugee Adder (2006, XML), Animated Ships (2010), [Oolite Stations|stations]] - the docking bay for one thing