OXP howto

Overview

An Oolite Expansion Pack can cause many big changes or additions to Oolite's gameplay, or it may represent just a small, subtle alteration. By appearances, there is no way to tell what is inside, as it's merely a folder with the added extention .oxp.

Inside, it will at least contain a folder (Config, AIs, Models, Textures, etc...) that holds scripts, plists or other things like textures or models. It is down to the goal of the OXP, which ways to combine elements to the OXP's contents. To get a feeling for it, simply take a look in other oxps.

AIs

The folder named AIs contains any AI.plist additions the OXP might use.

• Making Oolite AI

Config

All plist files except for those introducing new AIs, requires.plist or info.plist, belong in Config.

In its simplest form, an OXP could contain only a Config with an altering script.plist or planetinfo.plist. An OXP that adds a new ship needs a shipdata.plist entry, and unless it is based entirely on existing Oolite data, would include a model and texture.

• Making Oolite plists

This folder contains Property lists such as:

• characters.plist that adds non-player characters to Oolite.
• commodities.plist that contains information for each commodity in a market.
• crosshairs.plist that contains the look for your weapons (v1.73).
• customsounds.plist that contains references to ingame used sounds.
• demoships.plist that selects demoships to show on startup.
• descriptions.plist that adds vocabulary to Oolite texts.
• equipment.plist lists upgrades available from the Shipyard.
• hud.plist and hud-small.plist that allows for changes or a radically new Head-Up Display.
• illegal_goods.plist that contains a list of banned/forbidden items. GalCop has an eye on that.
• missiontext.plist contains texts for the mission screens.
• OXPMessages.plist adds warnings to testversions of an oxp.
• pirate-victim-roles.plist that defines which roles should act as traders.
• planetinfo.plist that plots system specific changes from the default. May also contain script actions.
• screenbackgrounds.plist that contains references to background images (v1.74).
• script.plist to handle conditional script actions. script.js will be loaded in preference to script.plist if both exist.
• shipdata.plist that introduces any new entity (ships, stations, objects etc.) to Oolite.
• shipdata-overrides.plist that selectively can replace shipentries in other shipdata.plists
• shipyard.plist that introduces new ships available for player purchase.
• shipyard-overrides.plist that selectively can replace shipentries in other shipyard.plists
• speech_pronunciation_guide.plist is another of the other custom methods.
• worldScripts.plist that contains a list of scripts (if more than one worldScript should be used).

Deprecated:

• script.oos was briefly introduced during 1.70 development but is now deprecated in favour of JS.)

Plist Verifier

Oolite has what amounts to a spell checker for shipdata.plist and other some plists, called the OXP verifier. The verifier detects unknown keys or wrong use of keys etc. It can currently only be invoked from the command line.

On Windows or Linux: Code: oolite.app/oolite --verify-oxp <path to OXP>

On Mac OS X: Code: Oolite.app/Contents/MacOS/Oolite --verify-oxp <path to OXP>

Most mac users will not be familiar to using the command line. Look inside your application folder for a utilities folder. Inside that you will find a program called terminal. Run it to open a terminal window. Now drop the oolite application on that window. That will generate the path to oolite on the command line. Delete the trailing space and paste the following text - including the trailing space- behind it: "/Contents/MacOS/Oolite --verify-oxp ". Now drop the oxp you want to verify on the window. That will again create the path to the oxp behind the last entry. When you select the window and hit the <return> key, the verification will start. It should now open the console program, showing the results.

Models

Oolite models need to be in the .dat format. There are utilities available that convert models made in Wings 3D (.obj) and Meshwork (.mesh) into this. A .dat file can be opened in a plain text editor to view the object's assigned texture names and see that they correspond with the actual file names in the Textures folder. The .dat file must be named exactly as it is referenced in the shipdata model entry - case sensitive!!!

• Making Oolite models

Textures

Oolite's textures are in the .png format, usually at a standard 512x512 size, and must be named exactly as they are named in the .dat file.

• Making Oolite textures

• Smivs' guide to making Oolite textures

Viewing a specific texture and / or model in Oolite. "I made one. How do I proof it?"

• Viewing a Texture or Model

Scripts

Scripts are in text format. In this folder you can put both js scripts as well as legacy scripts.

Requires

Every oxp should contain a Property lists with the name requires.plist that is placed at the main level of the oxp folder. It contains just a dictionary with two entries: version and max_version. version is the lowest Oolite version the code can run on. This ensures that older Oolite versions don't behave bad or crash because they load an oxp that does contain unknown stuff. The max_version is only needed when you want an oxp to not run with newer Oolite versions. Very useful for adding in test versions of an oxp to ensure this test version is not used forever.

The structure for OXPs:

AddOns (folder)
-.oxp (folder) - Holds requires.plist and info.plist and the other folders
--> AIs (folder) - Holds AI.plists
--> Config (folder) - Holds all other plists
--> Images (folder) - Holds background images
--> Models (folder) - Holds the .dat files
--> Music (folder) - Surprise - holds music files
--> Scripts (folder) - Holds scripts (worldScripts and shipScripts)
--> Shaders (folder) - Holds Vertex and Fragment shaders (v1.69)
--> Sounds (folder) - Holds sound files
--> Textures (folder) - Holds models textures

Unique names

On loading the oxps, Oolite will add all files in the AIs, Models, Sound and Scripts folders in one bug folder for its own use. That means that all files need unique names or one file will overwrite another with the same name. Files in Textures are not pre-loaded, but when looking for a specific texture Oolite looks in all Texture folders until it finds a texture file with a matching name. If another oxp contains a texture with identical name, Oolite could use that texture.

For the Config folder something similar happens. Here the plists all have the same name, but the content of all oxp plists is loaded per type in one big plist. e.g. all individual shipData.plist go in one big shipData.plist file. And within a single plist, all keys must be unique. When two plists use the same key, the later loading key will overwrite the former.

Generally it is a good habit to precede your chosen filenames and keys with the name of the oxp, or another unique prefix, to make sure the names stay unique and no other oxp will use the same names.

Scripting with JavaScript

For current test releases (Oolite 1.75.x and above) JavaScript is the preferred scripting interface for worldScripts and shipScripts. The legacy scripting interface (see script.plist) is still supported. See Scripting Oolite with JavaScript for more information.

See Also

• OXP Tutorial
• How to create dockable stations
• List of software that is helpful for creating OXPs
• OXP Distribution for best practices on OXP packaging and distribution

External links

• Oolite Tutorial-Meshwork Shipbuilding
• Oolite Tutorial-Wings 3D Shipbuilding