Like ship shipdata.plist example

The following is an example of a simple shipdata.plist that aims to introduce an entity into Oolite that shares many/most characteristics with another entity already present in an Oolite shipdata.plist.

Code in XML:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>my_custom_adder</key>
  <dict>
    <key>like_ship</key>
    <string>adder</string>
    <key>name</key>
    <string>Freak Adder</string>
    <key>model</key>
    <string>custom_adder.dat</string>
    <key>roles</key>
    <string>trader my_freaky_adder</string>
  </dict>
</dict>
</plist>

Code in OpenStep:

{
  my_custom_adder = {
    like_ship = "adder";
    name = "Freak Adder";
    model = "custom_adder.dat";
    roles = "trader my_freaky_adder";
  };
}

Note:

What is crucial here, is that the like_ship entry corresponds with a known ship name, and that the model referred to is correctly spelled. With the other entries (or any other desired changed from the original reference) one is free to choose personal preference. The roles entry above includes the unique entry 'my_freaky_adder' because this could later be used in a script.plist to summon this specific model.

Recap

As with all such files, the above shipdata will be placed in a folder named Config, and the models it refers to placed within a folder named Models and its textures placed in Textures. These folders would again be placed in a top level folder to be named, for instance, MyLike_ship.oxp, ready to be placed in your AddOns.

Another example

• 2007

BACK