Difference between revisions of "OXP howto"

From Elite Wiki
m (Linked to shipyard.plist)
m (add link)
Line 10: Line 10:
 
=== Config===
 
=== Config===
  
This folder contains Property Lists such as:
+
This folder contains [[Property lists]] such as:
  
 
* ''[[shipdata.plist]]'' that introduces any new entity (ships, stations, objects etc.) to Oolite.
 
* ''[[shipdata.plist]]'' that introduces any new entity (ships, stations, objects etc.) to Oolite.

Revision as of 00:36, 4 July 2006

OXP icon

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 named Config, and possibly other folders such as AIs, Models, Textures, Sounds, etc. It is down to the goal of the OXP, which ways to combine elements to the OXP's contents.

AIs

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

Config

This folder contains Property lists such as:

All plist files except for those introducing new AI, 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.

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.

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.

External links