OXP howto plist - Revision history

Cholmondely: /* Comments */ Oops!

2026-07-13T14:03:56Z

‎Comments: Oops!

2026-07-13T14:00:28Z

Added note on commenting out

2026-05-17T07:41:35Z

Added summary at the top

2024-02-29T02:17:11Z

Updating BB links

2023-03-16T11:44:58Z

Added Links

2023-03-06T12:59:16Z

‎Finding mistakes: Added note

2021-10-06T17:49:35Z

Added link to OXP Verifier, structure

2021-08-09T09:47:00Z

Tagged as Legacy scripting

2010-05-21T05:20:04Z

‎shipdata.plist: fixed link

2009-09-08T12:39:29Z

added category Oolite scripting

@@ Line 13: / Line 13: @@
 Adding comments, or commenting out unwanted code
 === OpenStep ===
 // comment runs from here to the return character at the end of the line ...    <br>
 /* comment text */
 === XML ===
-<!-- comment text -->
+''This is also true for this Wikipedia!'' <br>
 == Finding mistakes ==

← Older revision		Revision as of 14:00, 13 July 2026
Line 9:		Line 9:

	A good way to learn the correct way to make plists, is to examine the ones found within Oolite and working OXPs. The format is ideal to freely copy/paste items between various lists, and alter them as desired. This also minimizes the chance of little parser errors.		A good way to learn the correct way to make plists, is to examine the ones found within Oolite and working OXPs. The format is ideal to freely copy/paste items between various lists, and alter them as desired. This also minimizes the chance of little parser errors.
		+
		+	== Comments ==
		+	Adding comments, or commenting out unwanted code
		+	=== OpenStep ===
		+	// comment runs from here to the return character at the end of the line ... <br>
		+	/* comment text */
		+	=== XML ===
		+	<!-- comment text -->

	== Finding mistakes ==		== Finding mistakes ==

← Older revision		Revision as of 07:41, 17 May 2026
Line 1:		Line 1:
		+	There are 32 different possible .plists in Oolite OXPs - each adding to/overriding the vanilla game code. They need to go in specific folders in the OXPs. <br> See [[OXP howto]] (structure) for the list.
	[[Image:plist-XML-ASCII-ill.png\|thumb\|right\|300px\|the plist formats, XML and ASCII]]		[[Image:plist-XML-ASCII-ill.png\|thumb\|right\|300px\|the plist formats, XML and ASCII]]
	== plist ==		== plist ==

@@ Line 10: / Line 10: @@
 == Finding mistakes ==
-[http://aegidian.org/bb/viewtopic.php?p=69589#p69589 Macs use Cocoa to parse property lists, while other platforms use GNUstep. Their parsers work differently and are sensitive to different errors.] - see post above, too!
+[https://bb.oolite.space/viewtopic.php?p=69589#p69589 Macs use Cocoa to parse property lists, while other platforms use GNUstep. Their parsers work differently and are sensitive to different errors.] - see post above, too!
 === OXP Verifier ===
 A cross-platform utility for finding errors in some of the plists.

@@ Line 217: / Line 217: @@
 Place your shipdata and your script or planetinfo into the ''Config'' folder which, along with ''Textures'' and ''Models'', is placed in a folder to be named '''billboard.oxp'''. These are just a very few of the plist options for a model OXP, but enough to introduce an entity into the game universe.
 [[Category:Oolite]]
 [[Category:Oolite scripting]] [[Category:Legacy scripting]]

@@ Line 9: / Line 9: @@
 A good way to learn the correct way to make plists, is to examine the ones found within Oolite and working OXPs. The format is ideal to freely copy/paste items between various lists, and alter them as desired.  This also minimizes the chance of little parser errors.
-== Correcting with '''plutil''' (Macintosh Terminal) ==
+== Finding mistakes ==
 Since a very small mistake is enough to stop a plist from being accepted, it's important to be exact about every letter and sign. The Mac Terminal utility has a very practical tool for catching parser errors. After opening Terminal, simply type '''plutil''', add one space, and drag and drop the plist in question onto the Terminal window. This will cause the 'address' of the plist to be shown.  Hit return, and Terminal will reveal whether or not the plist is OK.  If it's not, you will be given a clue to what is wrong, and the line number of the error.
-== Basic Examples  ==
+== Basic Examples of plists ==
 The plists for a very simple OXP, for instance one containing a space advertising billboard, could contain this:

← Older revision		Revision as of 09:47, 9 August 2021
Line 215:		Line 215:

	[[Category:Oolite]]		[[Category:Oolite]]
−	[[Category:Oolite scripting]]	+	[[Category:Oolite scripting]] [[Category:Legacy scripting]]

@@ Line 74: / Line 74: @@
 This is the only mandatory plist inside folder ''Config'', to accompany the model named billboard1.dat in ''Models'', and billboard1_texture.png in ''Textures'', which would complete the minimal billboard.oxp, placing a slow spinning, lifeless object into the game.
-Because ''roles'' contains asteroid(0.05), this should cause our billboard to have a rare (and weird) appearance in the middle of an [[asteroid]] field.  This is a little awkward and not much chance of seeing our model frequently, so we would make a small addition to ''roles''.
+Because ''roles'' contains asteroid(0.05), this should cause our billboard to have a rare (and weird) appearance in the middle of an [[Asteroid_(Oolite)|asteroid]] field.  This is a little awkward and not much chance of seeing our model frequently, so we would make a small addition to ''roles''.
         <key>roles</key>
@@ Line 80: / Line 80: @@
 and include another plist in order to force an appearance of our model.  This by either a [[script.plist]] or [[planetinfo.plist]].
 === ''[[script.plist]]'' ===