<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.alioth.net/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cholmondely</id>
	<title>Elite Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.alioth.net/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cholmondely"/>
	<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php/Special:Contributions/Cholmondely"/>
	<updated>2026-11-19T23:44:44Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.12</generator>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Gravitation_OXP&amp;diff=90373</id>
		<title>Gravitation OXP</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Gravitation_OXP&amp;diff=90373"/>
		<updated>2026-11-16T22:36:58Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added a little&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Tch&amp;#039;s Gravitation.png|right|thumb|From Tch_Gravitation_RUS_opisanie_3.0.2_2013-12-31.pdf]]&lt;br /&gt;
Tch&amp;#039;s OXP created &amp;quot;Gravity&amp;quot; effects back in 2013 - it is not known if it works with the newer versions of Oolite.&lt;br /&gt;
&lt;br /&gt;
== Tch_Gravitation_3.0.2_2013-12-31.oxp ==&lt;br /&gt;
&lt;br /&gt;
This package creates a simplified model of gravity in the game. It manifests itself as follows:&lt;br /&gt;
&lt;br /&gt;
1. If you turn off the engines (ship speed 0) at an altitude of more than 450 astronomical kilometers above the planetoid surface, the player&amp;#039;s ship goes into the &amp;quot;Round Orbit&amp;quot; flight mode around the most influential planetoid at the moment. The display display displays information: &amp;quot;height, km&amp;quot;; &amp;quot;the angle of rotation from the starting point, hail&amp;quot;; &amp;quot;orbital speed, km / s&amp;quot;; &amp;quot;period of circulation, min&amp;quot;. However, if the calculated orbital speed exceeds the maximum speed of the player&amp;#039;s ship on normal thrust, then the transition to the orbital mode is impossible. This situation, as a rule, occurs near the Gas giants.&lt;br /&gt;
&lt;br /&gt;
The display shows the calculated orbital period, but the flight time around the planetoid is actually reduced several times using a time acceleration coefficient, so as not to delay the gameplay process (this coefficient affects only orbital time, but not game!).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2. If there are packages that create satellite objects near planetoids, calculate the characteristics of their orbits and transmit data on the established exchange protocol, the package calculates the new positions of these satellites and moves satellite objects in their orbits.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3. If the player ship is in the zone of gravity of the planetoid, and the engines are turned on (speed more than 0), then there is an additional factor of the displacement of the player ship, directed strictly to the center of the planetoid. This factor imitates the force of attraction near the planets and moons, which rejects the player ship from the intended course, attracting him to an influential planetoid. At the same time, information is displayed on the display about the height above the surface of the planet, km; about the force of attraction (in the form of a displacement factor from the intended course under the influence of gravity, km / s), and the current speed of the ship, km / s. The radar is automatically turned on in the zone of gravity and automatically disconnected when the ship moves away from the planet and exits its gravity zone.&lt;br /&gt;
&lt;br /&gt;
The force of attraction has the maximum value near the surface of the planet (and there the ship shifts the most strongly from the course) and decreases when it is removed from the planet until it disappears at all. As in reality, the force of attraction depends on the average density of the planets and on their radius - the main planets and additional planets have the greatest density, the moons have an average density, and the Gas giants have the lowest density. However, thanks to the high radius of the Gas giants, the gravitational force near them is the largest, and can pull the player’s ship into a gravitational trap, from which you can only get out with a hyper jump. This happens when the total additional displacement factor in 1 second exceeds the maximum speed of the player’s ship on normal thrust.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4. At an altitude of less than 450 astronomical kilometers does not matter whether the engines work or not: the ship cannot go into the Circular orbit flight mode, and the force of attraction attracts the ship to the planetoid.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
5. Outside the zone of gravity, with the engines on, the flight takes place as usual; with the engines turned off, the ship passes into a circular orbital flight.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
Visit Tch&amp;#039;s box: https://app.box.com/s/dyo1vedrxuyeyum3atci and poke about inside his &amp;quot;Game Environment&amp;quot; folder. The &amp;quot;opisanie&amp;quot; file is a .pdf with more detail than above and pretty pictures.&lt;br /&gt;
&lt;br /&gt;
== Note ==&lt;br /&gt;
*The above was translated from the Roolite page [https://oolite.ru/coriolis/viewtopic.php?f=11&amp;amp;t=569&amp;amp;sid=d082f02aebe6f9cbac0cefac921e34d3 Tch. Личная рубрика.]&lt;br /&gt;
*&amp;quot;Opisanie&amp;quot; is the Russian for &amp;quot;description&amp;quot;&lt;br /&gt;
*Tch also wrote a &amp;quot;Ships Orbits&amp;quot; OXP and a &amp;quot;Landing module&amp;quot; OXP.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Realism]]&lt;br /&gt;
&lt;br /&gt;
== Issues ==&lt;br /&gt;
*This OXP may be broken by the newer versions of Oolite!&lt;br /&gt;
&lt;br /&gt;
{{mechanics-OXP}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=File:Oolite.oxp.cim.extracts-tre-clan.oxz&amp;diff=90372</id>
		<title>File:Oolite.oxp.cim.extracts-tre-clan.oxz</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=File:Oolite.oxp.cim.extracts-tre-clan.oxz&amp;diff=90372"/>
		<updated>2026-11-14T17:50:09Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Response to https://bb.oolite.space/viewtopic.php?p=307422#p307422&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=File:Oolite.oxp.cim.extracts-tre-clan.oxz&amp;diff=90371</id>
		<title>File:Oolite.oxp.cim.extracts-tre-clan.oxz</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=File:Oolite.oxp.cim.extracts-tre-clan.oxz&amp;diff=90371"/>
		<updated>2026-11-14T17:44:45Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Planetinfo.plist&amp;diff=90365</id>
		<title>Planetinfo.plist</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Planetinfo.plist&amp;diff=90365"/>
		<updated>2026-11-11T12:52:55Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* OXP Property: Gas Giants */ Added more&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;planetinfo.[[plist]]&amp;#039;&amp;#039;&amp;#039; in &amp;#039;AddOns/Config&amp;#039; contains a dictionary for each of systems for which you wish to set custom data. A list of all galaxies and planets can be found [[Oolite planet list|here]]. Each of the properties mentioned below can be set (but, notably, not the location of the main planet, which is hard coded into the system seed value):&lt;br /&gt;
&lt;br /&gt;
The planetinfo.plist in cim&amp;#039;s [[SOTL Exploration]] OXP contains more properties such as &amp;quot;coordinates&amp;quot; (the position of the system in the galaxy), &amp;quot;random_seed&amp;quot; (this dumb pilot has no idea!), and possibly others. Cim &amp;#039;&amp;#039;did&amp;#039;&amp;#039; say that not all the new properties in the planetinfo.plist for [[SOTL Altmap]] actually did anything! (Altmap new properties include: &amp;quot;founded&amp;quot;, planet_seismic_instability&amp;quot;, &amp;quot;planet_surface_gravity&amp;quot;, &amp;quot;undist&amp;quot;, &amp;quot;planet_wind_speeds&amp;quot; &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.)&lt;br /&gt;
&lt;br /&gt;
[[File:BellScrib goatsoup1.JPG|thumb|right|Ian Bell worksheet for the goatsoup recipe from his vanished archives&amp;lt;br&amp;gt;See [[Oolite_planet_list#Where_do_these_crazy_names_come_from|Where do these crazy names come from?]] ]]&lt;br /&gt;
&lt;br /&gt;
=== Colour Specifiers ===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Colour specifiers&amp;#039;&amp;#039;&amp;#039; are used to declare colours in material attribute dictionaries, and in other contexts such as lasers in &amp;#039;&amp;#039;[[shipdata.plist]]&amp;#039;&amp;#039;. Colour specifiers take any of several forms:&lt;br /&gt;
Named colours, RGB / RGBA tuples, RGB / RGBA dictionaries or HSBA dictionaries. &lt;br /&gt;
&lt;br /&gt;
Colours can be viewed at https://rgbcolorpicker.com/0-1 and many other websites&lt;br /&gt;
&lt;br /&gt;
Click on the &amp;quot;gory details&amp;quot; for more: ---&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-collapsible mw-collapsed&amp;quot;  data-expandtext=&amp;quot;Show gory details&amp;quot; data-collapsetext=&amp;quot;Hide gory details&amp;quot; style=&amp;quot;overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
==== Named colours ====&lt;br /&gt;
The simplest form of colour specifier is a string containing a colour name. The following names are supported:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
|+ Colour names&lt;br /&gt;
! Name !! RGBA value&lt;br /&gt;
|-&lt;br /&gt;
|  blackColor || 0, 0, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| darkGrayColor || 1/3, 1/3, 1/3, 1&lt;br /&gt;
|-&lt;br /&gt;
| lightGrayColor || 2/3, 2/3, 2/3, 1&lt;br /&gt;
|-&lt;br /&gt;
| whiteColor || 1, 1, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
| grayColor || 1/2, 1/2, 1/2, 1&lt;br /&gt;
|-&lt;br /&gt;
| redColor || 1, 0, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| greenColor || 0, 1, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| blueColor || 0, 0, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
| cyanColor || 0, 1, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
| yellowColor || 1, 1, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| magentaColor || 1, 0, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
|  orangeColor || 1, 1/2, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| purpleColor || 1/2, 0, 1/2, 1&lt;br /&gt;
|-&lt;br /&gt;
| brownColor || 0.6, 0.4, 0.2, 1&lt;br /&gt;
|-&lt;br /&gt;
| clearColor || 0, 0, 0, 0&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== RGBA tuples ====&lt;br /&gt;
Colours may also be specified in RGB or RGBA (red, green, blue, alpha [transparency]). RGB or RGBA tuples may be specified as arrays or as strings separated by spaces. The values may range from 0 to 1 or 0 to 255. (If no value is greater than 1, 0–1 is assumed, otherwise 0–255.) Examples:&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;quot;1 1 0&amp;quot;&amp;lt;/code&amp;gt; — yellow&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;quot;0 128 0 128&amp;quot;&amp;lt;/code&amp;gt; — medium green at 50% opacity&lt;br /&gt;
* &amp;lt;code&amp;gt;(1, 0, 0)&amp;lt;/code&amp;gt; – red&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== RGBA dictionaries ====&lt;br /&gt;
Just in case you’re unsure of the order the RGB[A] components come in, you can use a dictionary:&lt;br /&gt;
 {&lt;br /&gt;
    blue = 0.8;&lt;br /&gt;
    green = 0.8;&lt;br /&gt;
 }&lt;br /&gt;
Accepted keys are &amp;#039;&amp;#039;&amp;#039;red&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;green&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;blue&amp;#039;&amp;#039;&amp;#039; and &amp;#039;&amp;#039;&amp;#039;alpha&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;opacity&amp;#039;&amp;#039;&amp;#039;), all optional (default: 0.0 for red, green and blue, 1.0 for alpha).&lt;br /&gt;
&lt;br /&gt;
==== HSBA dictionaries ====&lt;br /&gt;
But wait, there’s more! Colours may also be specified as dictionaries in the [http://en.wikipedia.org/wiki/HSB_colour_space HSB colour space]. Accepted keys are &amp;#039;&amp;#039;&amp;#039;hue&amp;#039;&amp;#039;&amp;#039; (hue angle in degrees, required), &amp;#039;&amp;#039;&amp;#039;saturation&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;brightness&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;value&amp;#039;&amp;#039;&amp;#039;) and &amp;#039;&amp;#039;&amp;#039;alpha&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;opacity&amp;#039;&amp;#039;&amp;#039;). The default for the optional keys is 1.0.&lt;br /&gt;
 {&lt;br /&gt;
    // Pale magenta&lt;br /&gt;
    hue = 300;&lt;br /&gt;
    saturation = 0.3;&lt;br /&gt;
 }&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Added for Oolite v.1.91 ===&lt;br /&gt;
*air_density / or the Javascript planet entity airDensity - see below (pretty picture!) &lt;br /&gt;
&lt;br /&gt;
=== Added for Oolite v.1.89 ===&lt;br /&gt;
 This needs editing by somebody who understands it! Snatched from the Progress thread&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=270737#p270737 air_color] now produces the right color for the sky. Not only that, it is now used as the atmosphere scatter color when the planet is viewed from space. Non-blue atmospheres are finally possible!&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=270771#p270771 air_color_mix_ratio]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=271058#p271058 terminator_threshold_vector shipdata key]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=271058#p271058 JSPlanet terminatorThresholdVector property]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=269833#p269833 MULTIPLIER_LIGHTSRCRADIANCE and MULITPLIER_EXPOSURE]: Planet, ships and atmosphere shaders can now define lightsource radiance and scene exposure multipliers&lt;br /&gt;
*Also stuff about city lights&lt;br /&gt;
*And probably other stuff I missed!&lt;br /&gt;
&lt;br /&gt;
==Where Settings Apply==&lt;br /&gt;
&lt;br /&gt;
===Universal Settings===&lt;br /&gt;
&lt;br /&gt;
Universal options are applied to all 2048 solar systems, this is useful for settings such as ambient lighting levels, eg.&lt;br /&gt;
 &amp;quot;universal&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
Universal options can be over-ridden by specifying the same option for a specific system or. Obviously, not all options make sense to apply to the whole universe.&lt;br /&gt;
&lt;br /&gt;
===Interstellar Space===&lt;br /&gt;
&lt;br /&gt;
Conditions for interstellar space in general can be set with the “interstellar space” key.&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=17191 Procedure to find all interstellar spaces] (2015)&lt;br /&gt;
&lt;br /&gt;
===Specific Systems===&lt;br /&gt;
&lt;br /&gt;
Each system is keyed by a string consisting of the galaxy number (0..7) followed by a space and then the planet number (0..255), eg.&lt;br /&gt;
 &amp;quot;0 7&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
specifies system 7, in galaxy 0, &amp;#039;&amp;#039;Lave&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
===Specific Interstellar Spaces===&lt;br /&gt;
&lt;br /&gt;
You can also specify a position in interstellar space, eg.&lt;br /&gt;
 &amp;quot;interstellar: 0 7 129&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
specifies the space in galaxy 0 between systems 7 and 129, &amp;#039;&amp;#039;Lave&amp;#039;&amp;#039; and &amp;#039;&amp;#039;Zaonce&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
Note that&lt;br /&gt;
 &amp;quot;interstellar: 0 7 129&amp;quot; = // jumping from Lave towards Zaonce&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
and&lt;br /&gt;
 &amp;quot;interstellar: 0 129 7&amp;quot; = // jumping from Zaonce towards Lave&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
are distinct locations and if they both need the same properties this must be explicitly set for both.&lt;br /&gt;
&lt;br /&gt;
In 1.81 the property &amp;quot;link_color&amp;quot; when set on a specific interstellar space changes the colour of the link between the two systems in the advanced navigation array (assuming no route is in place above it). When setting link_color, the lower system ID must be placed first, because of how the chart is drawn.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039; that [[User:Switeck|Switeck]] has done a lot of work on this - there are intermediate spots in the interstellar spaces - but only on the line between two systems. See the OXPs on his User: page&lt;br /&gt;
&lt;br /&gt;
==Layers==&lt;br /&gt;
&lt;br /&gt;
Settings other than &amp;quot;universal&amp;quot; in Oolite 1.81 or later have a &amp;#039;layer&amp;#039; property from 0 to 3. The default value for planetinfo.plist files is 1. If multiple OXPs specify a setting for a particular property, the order they will be checked in is:&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 3 settings&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 2 settings&amp;#039;&amp;#039;&amp;#039; (default for Javascript changes to data)&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 1 settings&amp;#039;&amp;#039;&amp;#039; (default for planetinfo.plist)&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Universal settings&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 0 settings&amp;#039;&amp;#039;&amp;#039; (value for core game settings)&lt;br /&gt;
&lt;br /&gt;
This allows OXPs to safely override each other&amp;#039;s changes if necessary, and for OXPs which really need a specific setting in a particular system to set it at layer 3&lt;br /&gt;
&lt;br /&gt;
Example&lt;br /&gt;
 &amp;quot;layer&amp;quot; = 2;&lt;br /&gt;
&lt;br /&gt;
==Terraforming Example==&lt;br /&gt;
   &lt;br /&gt;
For the planet Lave, you would use the key &amp;#039;0 7&amp;#039; (planet 7 in galaxy 0) Then you set the values. The following example sets Lave&amp;#039;s sea to blue, land to green, and land to sea ratio to 75%. &lt;br /&gt;
 &lt;br /&gt;
Code:&lt;br /&gt;
 { &lt;br /&gt;
    &amp;quot;0 7&amp;quot; = &lt;br /&gt;
    { &lt;br /&gt;
       &amp;quot;percent_land&amp;quot; = &amp;quot;75&amp;quot;;&lt;br /&gt;
       &amp;quot;land_color&amp;quot; = &amp;quot;0.5 1.0 0.5&amp;quot;;&lt;br /&gt;
       &amp;quot;sea_color&amp;quot; =  &amp;quot;0.3 0.7 1.0&amp;quot;;&lt;br /&gt;
    } &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
Then you can override any of the settings listed above, for example to change Zaatxe&amp;#039;s (Galaxy 0 Planet 8) inhabitants into blue frogs you&amp;#039;d enter &lt;br /&gt;
 &lt;br /&gt;
Code:&lt;br /&gt;
     &amp;quot;0 8&amp;quot; =  &lt;br /&gt;
    { &lt;br /&gt;
         &amp;quot;inhabitants&amp;quot; = &amp;quot;Blue Frogs&amp;quot;;&lt;br /&gt;
    } &lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
You can use any or all of the keys in each of the entries. It&amp;#039;s probably best to only use the key&amp;#039;s you want to change. So, another example, to change the sky_blur_xxx settings for Zaonce (Galaxy 0 Planet 129) to big, heavily clustered, but pale blurs - you&amp;#039;d enter &lt;br /&gt;
 &lt;br /&gt;
Code:&lt;br /&gt;
     &amp;quot;0 129&amp;quot; = &lt;br /&gt;
    { &lt;br /&gt;
         &amp;quot;sky_blur_cluster_chance&amp;quot; =  &amp;quot;0.9&amp;quot;;&lt;br /&gt;
         &amp;quot;sky_blur_alpha&amp;quot; = &amp;quot;0.1&amp;quot;;&lt;br /&gt;
         &amp;quot;sky_blur_scale&amp;quot; = &amp;quot;32.0&amp;quot;;&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==About the Inhabitants==&lt;br /&gt;
&lt;br /&gt;
===Concealment===&lt;br /&gt;
{{oolite-prop-added|1.83}}&lt;br /&gt;
&lt;br /&gt;
An integer that determines how much information about the system is unknown.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;concealment&amp;quot; = &amp;quot;300&amp;quot;;&lt;br /&gt;
The following values are recognised:&lt;br /&gt;
* 0: default, all information visible&lt;br /&gt;
* 100 or more: F7 screen shows no information, economy/government/TL/star colour not visible on chart&lt;br /&gt;
* 200 or more: system name is not shown&lt;br /&gt;
* 300 or more: system vanishes entirely from chart, will not be used in route plotting, cannot be targeted by player (NPCs can still jump to it, though)&lt;br /&gt;
&lt;br /&gt;
===Government===&lt;br /&gt;
&lt;br /&gt;
An integer between 0 and 7 indicating the government type of the system.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;government&amp;quot; = &amp;quot;7&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Possible values:&lt;br /&gt;
: 0: Anarchy&lt;br /&gt;
: 1: Feudal&lt;br /&gt;
: 2: Multi-Governmental&lt;br /&gt;
: 3: Dictatorship&lt;br /&gt;
: 4: Communist&lt;br /&gt;
: 5: Confederacy&lt;br /&gt;
: 6: Democracy&lt;br /&gt;
: 7: Corporate State&lt;br /&gt;
&lt;br /&gt;
===Economy===&lt;br /&gt;
An integer between 0 and 7 indicating the economy type of the system.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;economy&amp;quot; = &amp;quot;5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Possible values:&lt;br /&gt;
: 0: Rich Industrial&lt;br /&gt;
: 1: Average Industrial&lt;br /&gt;
: 2: Poor Industrial&lt;br /&gt;
: 3: Mainly Industrial&lt;br /&gt;
: 4: Mainly Agricultural&lt;br /&gt;
: 5: Rich Agricultural&lt;br /&gt;
: 6: Average Agricultural&lt;br /&gt;
: 7: Poor Agricultural&lt;br /&gt;
 &lt;br /&gt;
===Tech Level===&lt;br /&gt;
&lt;br /&gt;
An integer between 0 and 14 indicating the sophistication of the planets technology. The tech level displayed on the system data screens in game is one higher than this number (range 1 to 15).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;techlevel&amp;quot; = &amp;quot;13&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?p=113258#p113258 Episodic minor variations in TL (2010)]&lt;br /&gt;
&lt;br /&gt;
Further Note: The [[Famous Planets]] OXP transmogrifies [[Sector1/Sori]] into the Anarchy &amp;quot;Ascension&amp;quot; with a TL of 16! This is virtually no different to Ceesxe&amp;#039;s TL 15.&lt;br /&gt;
&lt;br /&gt;
===Population===&lt;br /&gt;
&lt;br /&gt;
An integer between 0 and 67 indicating the number of inhabitants of a planet in hundreds of millions&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;population&amp;quot; = &amp;quot;23&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
See Wildeblood&amp;#039;s note on no upper limit [https://bb.oolite.space/viewtopic.php?p=299408#p299408 here] (2025)&lt;br /&gt;
&lt;br /&gt;
===Productivity===&lt;br /&gt;
&lt;br /&gt;
An integer indicating the productivity of a planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;productivity&amp;quot; = &amp;quot;1000&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Name===&lt;br /&gt;
&lt;br /&gt;
The name of the planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;name&amp;quot; = &amp;quot;The planet&amp;#039;s name&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;: See the [https://bb.oolite.space/viewtopic.php?t=12131 Pronounceable Planets Project] thread on the forum for some ideas!&lt;br /&gt;
&lt;br /&gt;
===Inhabitant===&lt;br /&gt;
&lt;br /&gt;
The name for one of the inhabitants of the main planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;inhabitant&amp;quot; = &amp;quot;Green Platypus&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Inhabitants===&lt;br /&gt;
&lt;br /&gt;
The name of the inhabitants of the main planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;inhabitants&amp;quot; = &amp;quot;Green Platypi&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Description===&lt;br /&gt;
&lt;br /&gt;
A short description of the planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;description&amp;quot; = &amp;quot;Really, anything you want to say about the place!&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;: For more than 1 oxp describing a system see [https://bb.oolite.space/viewtopic.php?p=165471#p165471 here] (2012) - and elsewhere. Note that &amp;#039;&amp;#039;eg&amp;#039;&amp;#039;. [[System Features Rings]] does this through Javascript. rather than a .plist.&lt;br /&gt;
&lt;br /&gt;
===Government Description===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Overrides the default text used to describe the government.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;government_description&amp;quot; = &amp;quot;Dictatorship (Monarchy)&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Economy Description===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Overrides the default text used to describe the economy.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;economy_description&amp;quot; = &amp;quot;Mainly Industrial (Machine Tools)&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Population Description===&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
Overrides the default text used to describe the population.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;population_description&amp;quot; = &amp;quot;13 Billion&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Random Seed===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
A seed for a random number generator used in Oolite 1.81 to generate system properties impractical to store in this file (e.g. the positions of each star on the background starfield)&lt;br /&gt;
&lt;br /&gt;
For historical reasons, this is a string of 6 integers between 0 and 255, for example:&lt;br /&gt;
 random_seed = &amp;quot;74 90 72 2 83 183&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==System population==&lt;br /&gt;
These properties are only used in Oolite 1.79 or later.&lt;br /&gt;
&lt;br /&gt;
===Populator===&lt;br /&gt;
&lt;br /&gt;
The name of the worldscript function which will be used to [[Oolite_System_Populator|populate the system]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;populator&amp;quot; = &amp;quot;systemWillPopulate&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Repopulator===&lt;br /&gt;
&lt;br /&gt;
The name of the worldscript function which will be used to [[Oolite_System_Populator|repopulate the system]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;repopulator&amp;quot; = &amp;quot;systemWillRepopulate&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==Properties of the Planet==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Most of these properties are ignored if a planet texture is set.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Note that the available planet texture generator properties changed in places between Oolite 1.77 and Oolite 1.80&lt;br /&gt;
&lt;br /&gt;
And note the 2016 introduction of the shader uniform [[Shaders in Oolite: uniforms|fogUniform]] (a Javascript method for adding fog to planet atmospheres)&lt;br /&gt;
&lt;br /&gt;
===Air Color===&lt;br /&gt;
A colour specifier determining the color of the planet&amp;#039;s sky, as well as the atmosphere scatter color.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;air_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Air Color Mix Ratio===&lt;br /&gt;
{{oolite-prop-added|1.89}}&lt;br /&gt;
&lt;br /&gt;
The amount of air color that be mixed in the overall atmosphere color. A number from 0.0 to 1.0 (default 0.5).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;air_color_mix_ratio&amp;quot; = &amp;quot;0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Atmosphere Rotational Velocity===&lt;br /&gt;
&lt;br /&gt;
Sets how fast the atmosphere is rotating. (A random value between 0.0 to 0.03 is the default).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;atmosphere_rotational_velocity&amp;quot; = &amp;quot;0.1&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Cloud Alpha===&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The transparency level of the cloud layer, relative to the standard transparency. 1.0 is the default. Texture packs which include clouds on the planetary texture may wish to reduce this.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cloud_alpha&amp;quot; = &amp;quot;0.2&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Has Atmosphere===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
This boolean property is used for the main planet only. If it is unset or true, the main planet has an atmosphere, as is always the case in 1.80 and before. If it is set to be false, then the planet will not have an atmosphere.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_atmosphere&amp;quot; = 0;&lt;br /&gt;
&lt;br /&gt;
This has no effect on secondary planets - their atmosphere is determined by whether addition uses &amp;lt;code&amp;gt;addPlanet&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;addMoon&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
[[File:AtmDensityExample.png|thumb|320px|right|Atmosphere Density examples: Stranger&amp;#039;s &amp;#039;&amp;#039;FPO Lave&amp;#039;&amp;#039; in four increasing atmosphere densities: 0.2, 0.5, 0.75 and 1.0. Every other parameter in the planet definition is the same in all pictures.]]&lt;br /&gt;
=== Air Density ===&lt;br /&gt;
{{oolite-prop-added|1.91}}&lt;br /&gt;
&lt;br /&gt;
A number clamped in range from 0.0 to 1.0 describing the density of the planet&amp;#039;s atmosphere. All planets in the core use 0.75 as default.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;air_density&amp;quot; = &amp;quot;0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Illumination Color===&lt;br /&gt;
{{oolite-prop-added|1.91}}&lt;br /&gt;
&lt;br /&gt;
A colour specifier determining the colour of the planet&amp;#039;s illumination such as cities light. Illumination is inserted as a grayscale map in the alpha channel of the planet&amp;#039;s diffuse texture. You can specify this key even if no illumination map is defined, but it won&amp;#039;t have any effect - without an illumination map the dark side of the planet remains dark in all cases.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;illumination_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Land Color===&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;land_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Percent Cloud===&lt;br /&gt;
The percentage of the planet&amp;#039;s atmosphere occupied by clouds.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;percent_cloud&amp;quot; = &amp;quot;0..100&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note that with a low cloud_alpha setting not all of the clouds defined here may actually be visible&lt;br /&gt;
&lt;br /&gt;
===Percent Ice===&lt;br /&gt;
The percentage of the planet occupied by the polar ice caps. Oolite 1.81 or later.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;percent_ice&amp;quot; = &amp;quot;0..100&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Percent Land===&lt;br /&gt;
The percentage of the planet occupied by land.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;percent_land&amp;quot; = &amp;quot;0..100&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Planet Distance===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The distance from the centre of the planet to the witchpoint. Only used for the system main planet - secondary planets are positioned separately.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;planet_distance&amp;quot; = &amp;quot;410000&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
The main planet is always positioned on the z-axis.&lt;br /&gt;
&lt;br /&gt;
===Planet Distance Multiplier===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Multiplies the distance from the centre of the main planet to the witchpoint.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;planet_distance_multiplier&amp;quot; = &amp;quot;1.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Planet Name===&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The planet&amp;#039;s name. For the main planet, this defaults to being the same as the system name - the property is mainly intended for secondary planets.&lt;br /&gt;
&lt;br /&gt;
Example&lt;br /&gt;
  &amp;quot;planet_name&amp;quot; = &amp;quot;Earth&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Polar Land Color===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Sets the land colour in polar regions.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;land_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Polar Sea Color===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Sets the sea colour in polar regions.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sea_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Radius===&lt;br /&gt;
An integer between 3000 and 7000 indicating the radius of the main planet. On the F7 screen, this is measured in kilometres. The radius in game is 1/100th of this.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;radius&amp;quot; = &amp;quot;5500&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Rotational Velocity===&lt;br /&gt;
A number describing the rotational velocity of the planet in radians per second. Overrides rotation_speed if both are set.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;rotational_velocity&amp;quot; = 0.0015;&lt;br /&gt;
&lt;br /&gt;
===Rotation Speed===&lt;br /&gt;
A number describing the rotational velocity of the planet in radians per second. Unlike rotational_velocity, this is affected by rotation_speed_factor.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;rotation_speed&amp;quot; = 0.0015;&lt;br /&gt;
&lt;br /&gt;
===Rotation Speed Factor===&lt;br /&gt;
The rotational speed of all planets whose rotational speed was set by rotation_speed and not by rotational_velocity will be multiplied by this number.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;rotation_speed_factor&amp;quot; = 1.0;&lt;br /&gt;
&lt;br /&gt;
(Intended more for the universal section as a &amp;quot;personal taste&amp;quot; option than for individual planets)&lt;br /&gt;
&lt;br /&gt;
===Sea Color===&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sea_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Terminator Threshold Vector===&lt;br /&gt;
{{oolite-prop-added|1.89}}&lt;br /&gt;
&lt;br /&gt;
This property gives control over the color of the planet&amp;#039;s terminator. The way the property works is not entirely straightforward, so see [https://bb.oolite.space/viewtopic.php?p=271058#p271058 this post on BB] for more information.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;terminator_threshold_vector&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
By default the terminator vector is &amp;quot;0.105 0.18 0.28&amp;quot; - which results in a reddish orange colour.&lt;br /&gt;
&lt;br /&gt;
===Texture===&lt;br /&gt;
The replacement texture to be used by a system&amp;#039;s main planet.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For textures you can use lat-long maps (twice as wide as high) with a special elongation at the poles, or cube maps. Other maps will also be wrapped around planets, but will always give distortions.&amp;lt;br&amp;gt;&lt;br /&gt;
Since Oolite 1.74 you can also use cube maps for planets. Cube maps are 6 times higher than wide and will be recognised automatically by Oolite, based on the dimensions. Cube maps are the preferred method, because lat-long give some distortion and have the poles improperly placed in Oolite&amp;#039;s implementation. See also [[Planettool]] for conversion from lat-long into cube maps.&lt;br /&gt;
&lt;br /&gt;
From Oolite 1.89 onwards, illumination mapping on custom planets is supported. The illumination map goes in the diffuse map&amp;#039;s alpha channel. Low alpha values translate to high illumination. This allows for effects like city lights on a planet&amp;#039;s dark side.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;texture&amp;quot; =  &amp;quot;newPlanetTexture.png&amp;quot;;&lt;br /&gt;
:N.B.&lt;br /&gt;
The illumination mapping feature is disabled by setting &amp;#039;&amp;#039;Graphics Detail: Shaders Enabled&amp;#039;&amp;#039; or lower in the game setting menu. &amp;#039;&amp;#039;Enabled&amp;#039;&amp;#039; at &amp;#039;&amp;#039;Graphics Detail: Extra Detail&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
===Texture HSB Color===&lt;br /&gt;
This changes the overall hue of the replacement texture.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;texture_hsb_color&amp;quot; =  &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Texture NormSpec===&lt;br /&gt;
{{oolite-prop-added|1.89}}&lt;br /&gt;
&lt;br /&gt;
The external texture that will be used as a normal and specular map for the given planet. Colorspace should be linear, with the normal map in the r,g and b and the specular map in the a channel. The texture can be of either equirectangular or cubemap formats. This feature is available at the Extra Detail setting only. To set:&lt;br /&gt;
 &amp;quot;texture_normspec&amp;quot; = &amp;quot;planetNormalAndSpecularMap.png&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
=== OXP Property: Gas Giants ===&lt;br /&gt;
Several OXPs introduce gas giants and assign them characteristics (the [[Stranger&amp;#039;s World]] suite of OXPs, the [[Additional Planets]] OXP suite, and the vintage [[Deep Horizon]] suite). Deep Horizon adds an extra OXP allowing one to skim fuel from DH&amp;#039;s gas giants. The most recent version of [[Cloud City OXP]] places cloud cities at gas giants.&lt;br /&gt;
&lt;br /&gt;
These three OXP suites all use different keys to identify their gas giants.&lt;br /&gt;
:Planetary Systems uses {{CodeEx|codeex=.solarGasGiant}}&lt;br /&gt;
:Deep Horizons uses {{CodeEx|codeex=.isGasGiant}}&lt;br /&gt;
:Stranger&amp;#039;s World has two versions of Gas Giant (Saturn &amp;amp; Zeus/Jupiter) which seem to be defined by planetary radius (150,000 &amp;lt; 175000 and 125,000 &amp;lt; 150,000). The following tags are also used, {{CodeEx|codeex=planetDataTag = 5}} &amp;amp; {{CodeEx|codeex=planetDataTag = 6}} See inside Stranger&amp;#039;s [https://ooliteproject.github.io/oolite-expansion-catalog/expansions/oolite.oxp.stranger.SunGear/oolite.oxp.stranger.SunGear.html Sun Gear OXP] &amp;amp; [https://ooliteproject.github.io/oolite-expansion-catalog/expansions/oolite.oxp.stranger.PlanetarySystems/oolite.oxp.stranger.PlanetarySystems.html Planetary Systems OXP] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There is a 2026 BB discussion starting [https://bb.oolite.space/viewtopic.php?p=305866#p305866 here]. More realistic gas giants require a &amp;#039;&amp;#039;deep&amp;#039;&amp;#039; atmosphere which is currently not available in the vanilla game code. [[Planetfall]]&amp;#039;s heat/turbulence is not yet an atmosphere, although it mimics elements of it!&lt;br /&gt;
&lt;br /&gt;
=== OXP Property: Atmospheric turbulence ===&lt;br /&gt;
This is introduced by [[Planetfall2 OXP]] - look at the &amp;quot;planetFall2_turbulence.js&amp;quot; file inside the scripts folder in the OXP.&lt;br /&gt;
&lt;br /&gt;
=== OXP Property: Landing sites ===&lt;br /&gt;
These are introduced by [[Planetfall2 OXP]] - see the [[Planetfall2_OXP#The_Dark_Side|copious material]] which [[User:Phkb|Phkb]] has produced explaining how to do this.&lt;br /&gt;
&lt;br /&gt;
==Properties of the Sky==&lt;br /&gt;
&lt;br /&gt;
===Ambient Level===&lt;br /&gt;
&lt;br /&gt;
Sets how much ambient light (shed by stars and nebulae) illuminates the dark side of objects like planets and ships. Values should typically be between 0.0 and 1.0 (1.0 is the default) but can be higher for a flat lit, cartoon-like effect.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;ambient_level&amp;quot; = &amp;quot;0.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Nebula Count Multiplier===&lt;br /&gt;
This is used for defining the number of nebulas. Default is 1.0. Number can be greater or less than default and is also randomised a bit. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;nebula_count_multiplier&amp;quot; = &amp;quot;1.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky Blur Alpha===&lt;br /&gt;
Default 0.1&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_blur_alpha&amp;quot; = &amp;quot;0.0 .. 1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky Blur Cluster Chance===&lt;br /&gt;
This is used for creating nebulae (typically 0.80)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_blur_cluster_chance&amp;quot; = &amp;quot;0.85&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky Blur Scale===&lt;br /&gt;
Default 10. Larger numbers generate bigger nebula, but slow down the game considerable on slower machines.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_blur_scale&amp;quot; = &amp;quot;0.0 .. 128.0 or more&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky N Blurs===&lt;br /&gt;
This is used for defining the number of nebulas (typical is 80, maximum is 1280). This key is multiplied by a &amp;quot;nebula_count_multiplier&amp;quot; definition in Oolite 1.81 or later.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_n_blurs&amp;quot; = &amp;quot;800&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky N Stars===&lt;br /&gt;
This is used for defining the number of stars (typical = 600, maximum in 1.76 or earlier is 4800). This key is multiplied by a &amp;quot;star_count_multiplier&amp;quot; definition in Oolite 1.81 or later. In reduced detail mode, this number will be capped to 2400.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_n_stars&amp;quot; = &amp;quot;1200&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky and Nebula RGB Colors===&lt;br /&gt;
&lt;br /&gt;
These are rgb values (from 0.0 to 1.0) for the two colours between which the colour of the stars (and nebulaesque blurs) vary, ordered r1 g1 b1 r2 g2 b2 where (r1 g1 b1) defines the first colour and (r2 g2 b2) the second.&amp;lt;br&amp;gt;&lt;br /&gt;
(Default values are &amp;quot;0.75 0.8 1.0 1.0 0.85 0.6&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_rgb_colors&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0 0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Alternatively, two [[Materials in Oolite#Colour specifiers|colour specifiers]] may be used:&lt;br /&gt;
 &amp;quot;sky_color_1&amp;quot; = &amp;quot;redColor&amp;quot;;&lt;br /&gt;
 &amp;quot;sky_color_2&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
     &amp;quot;hue&amp;quot; = &amp;quot;60&amp;quot;;&lt;br /&gt;
     &amp;quot;brightness&amp;quot; = &amp;quot;0.8&amp;quot;;&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 &amp;quot;nebula_color_1&amp;quot; = &amp;quot;greenColor&amp;quot;;&lt;br /&gt;
 &amp;quot;nebula_color_2&amp;quot; = &amp;quot;blueColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Star Count Multiplier===&lt;br /&gt;
This is used for defining the number of stars. Default is 1.0. Number can be greater or less than default and is also randomised a bit. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;star_count_multiplier&amp;quot; = &amp;quot;0.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Properties of the Station==&lt;br /&gt;
&lt;br /&gt;
===Market Script===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
A Javascript file used to load a [[Oolite Market Scripts|market script]] for global system price and quantity modifications.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;market_script&amp;quot; = &amp;quot;myoxp_newsystemmarket.js&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; [https://bb.oolite.space/viewtopic.php?p=235837#p235837 What&amp;#039;s the difference between the market script specified in planetinfo.plist and the one called for by trade-goods.plist?] (2015)&lt;br /&gt;
&lt;br /&gt;
===Station===&lt;br /&gt;
The type of station orbiting the main planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station&amp;quot; = &amp;quot;coriolis..dodec..special&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Station Roll===&lt;br /&gt;
The speed at which the station rotates (as with all rotational velocities this is in radians per second) and affects all rotating stations in a system. For a specific station you can use the key [[Shipdata.plist#station_roll | station_roll]] in shipdata.plist.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station_roll&amp;quot; = &amp;quot;0.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Station Vector===&lt;br /&gt;
The direction of the main station from the main planet&lt;br /&gt;
 &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station_vector&amp;quot; = &amp;quot;-0.717 -0.668 0.201&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Stations Require Docking Clearance===&lt;br /&gt;
&lt;br /&gt;
Specifies if a player has to explicit ask docking permission. See also [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|Oolite Docking Clearance]]&lt;br /&gt;
&lt;br /&gt;
===Market (defunct)===&lt;br /&gt;
The market to be used in this system as the default market. It points to a key in commodities.plist&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;market&amp;quot; = &amp;quot;rockhermit&amp;quot;;&lt;br /&gt;
Will use the rockhermit market as default for for all stations in the system. When no market is defined a key in commodities.plist is used that matches the role of the main station. Than that is not defined, the default market is used in this system.&lt;br /&gt;
&lt;br /&gt;
In 1.81 and later, this is replaced by market_script&lt;br /&gt;
&lt;br /&gt;
==Properties of the Sun==&lt;br /&gt;
;N.B.&lt;br /&gt;
The corona effect, modified by the first three properties mentioned below, is disabled by setting &amp;#039;&amp;#039;Reduced Detail:On&amp;#039;&amp;#039; in the game setting menu. &amp;#039;&amp;#039;Enabled&amp;#039;&amp;#039; by default (&amp;#039;&amp;#039;Reduced Detail:Off&amp;#039;&amp;#039;).&lt;br /&gt;
&lt;br /&gt;
===Corona Flare===&lt;br /&gt;
&lt;br /&gt;
Sets the overall size of the corona in proportion to its sun. (See note above.)&lt;br /&gt;
&lt;br /&gt;
A number from 0.0 (invisibly small) to 1.0 (huge)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;corona_flare&amp;quot; = &amp;quot;0.075&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Corona Hues===&lt;br /&gt;
&lt;br /&gt;
Specifies whether the corona should have visible bands of colours within the corona. (See note above.)&lt;br /&gt;
&lt;br /&gt;
A number from 0.0 (monochromatic) to 1.0 (vivid alternating colours).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;corona_hues&amp;quot; = &amp;quot;0.6&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Corona Shimmer===&lt;br /&gt;
&lt;br /&gt;
Specifies how quickly the corona colours change. (See note above.)&lt;br /&gt;
&lt;br /&gt;
A number from 0.0 (very slow) to 1.0 (very fast).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;corona_shimmer&amp;quot; = &amp;quot;0.4&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Color===&lt;br /&gt;
&lt;br /&gt;
Sets the colour of a system&amp;#039;s sun.&lt;br /&gt;
&lt;br /&gt;
Can be any [[Materials in Oolite#Colour specifiers|colour specifier]] or [[Materials in Oolite#Named colours|named colour]]. The specified colour is blended with 50% white so it will never be a saturated colour.  Dark colours will be brightened by this blending.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_color&amp;quot; = &amp;quot;blueColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Distance===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Sets the distance between the sun and the main planet in metres.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_distance&amp;quot; = 924122;&lt;br /&gt;
&lt;br /&gt;
Ignored if sun_distance_modifier is set.&lt;br /&gt;
&lt;br /&gt;
===Sun Distance Multiplier===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Multiplies the distance between the sun and the main planet by this factor.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_distance_multiplier&amp;quot; = 2;&lt;br /&gt;
&lt;br /&gt;
Ignored if sun_distance_modifier is set.&lt;br /&gt;
&lt;br /&gt;
===Sun Distance Modifier===&lt;br /&gt;
&lt;br /&gt;
Sets the approximate distance between a system sun and its main planet. The standard distance is 20 planetary radii. Setting it much lower (10, or even less) will cause delays when generating systems, as Oolite compensates for possible collisions between the sun and other system objects.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_distance_modifier&amp;quot; = &amp;quot;15.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.81 or later, sun_distance_multiplier is more useful.&lt;br /&gt;
&lt;br /&gt;
=== Sun Gone Nova ===&lt;br /&gt;
&lt;br /&gt;
Sets a nova sun in the system.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_gone_nova&amp;quot; = &amp;quot;YES&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Name===&lt;br /&gt;
&lt;br /&gt;
Stores the name of a system&amp;#039;s sun. This is only implemented in Oolite from version 1.79 onwards, though was used by OXPs before then.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_name&amp;quot; = &amp;quot;Alpha Centauri&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Radius===&lt;br /&gt;
&lt;br /&gt;
Sets the radius of a system&amp;#039;s sun. A number between 1000 and 1000000.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_radius&amp;quot; = &amp;quot;100000&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Vector===&lt;br /&gt;
The direction of the sun from the main planet&lt;br /&gt;
 &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_vector&amp;quot; = &amp;quot;-0.717 -0.668 0.201&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==Additional Planets==&lt;br /&gt;
&lt;br /&gt;
Finally you can also define your own custom planets and moons:&lt;br /&gt;
 &amp;quot;LavesPurpleMoon&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--They also can be added through script_actions, but it&amp;#039;s deprecated and even commented out on this page--&amp;gt;&lt;br /&gt;
To add them to the system, use JS methods &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_System#addPlanet|system.addPlanet]]&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_System#addPlanet|system.addMoon]]&amp;lt;/code&amp;gt;. For the example above, the &amp;lt;code&amp;gt;planetInfoKey&amp;lt;/code&amp;gt; will be &amp;lt;code&amp;gt;&amp;quot;LavesPurpleMoon&amp;quot;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Position===&lt;br /&gt;
Position of the planet in space. The first parameter is 3-character code of the coordinate system, other three is x, y and z components of position vector.&lt;br /&gt;
 &amp;quot;position&amp;quot; = &amp;quot;pwm 0 -50000 0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
You can omit the coordinate system parameter, then the absolute coordinate system will be used:&lt;br /&gt;
 &amp;quot;position&amp;quot; = &amp;quot;0 -50000 0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See [[Oolite coordinate systems]] for more info about it.&lt;br /&gt;
&lt;br /&gt;
===Orientation===&lt;br /&gt;
Orientation of the planet in space (seems not to be working correctly).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;orientation&amp;quot; = &amp;quot;0.0 1.0 0.0 0.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Other keys===&lt;br /&gt;
&lt;br /&gt;
You can use other keys from the [[#Properties_of_the_Planet| Properties of the Planet]] section for your planets and moons.&lt;br /&gt;
&lt;br /&gt;
Here are some of the keys you may want to use:&lt;br /&gt;
* &amp;quot;radius&amp;quot;: Radius of the planet in km. e.g. a value of 500 is drawn with a radius of 5000 meters but in player dialogues this value is presented as 500 km.&lt;br /&gt;
* &amp;quot;rotational_velocity&amp;quot;: Rotation of the planet in rotations per second.&lt;br /&gt;
* &amp;quot;texture&amp;quot;: The name of the texture file that is used to wrap around the surface.&lt;br /&gt;
* &amp;quot;seed&amp;quot;: Seed value used to create the planet&amp;#039;s surface features. If no seed is defined it uses the same seed as the main planet, and will create a copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:Ico-Glow.png|thumb|right|300px|Click for more detail (eg the Ico station)]]&lt;br /&gt;
== Experimentation ==&lt;br /&gt;
The effect to the right was created by [[User:Cody|Cody]]. &amp;quot;OXPs were a Griff Icosahedron station, a [[Deep Horizon Nav Buoy]], a core planet (I think - if not, [[Povray Planets]]), a mix of [[KeeperSky]] &amp;amp; [[Zygo Cinematic Sky &amp;amp; Nebulas]], plus &amp;#039;&amp;#039;&amp;#039;star_count_multiplier&amp;#039;&amp;#039;&amp;#039; = 56; &amp;#039;&amp;#039;&amp;#039;sun_distance_multiplier&amp;#039;&amp;#039;&amp;#039; = 5; and &amp;#039;&amp;#039;&amp;#039;ambient_level&amp;#039;&amp;#039;&amp;#039; = 0.15;&lt;br /&gt;
&lt;br /&gt;
For a similar &amp;quot;lights down&amp;quot; look, you&amp;#039;d have to tweak &amp;#039;&amp;#039;&amp;#039;oolite-default-shader.fragment&amp;#039;&amp;#039;&amp;#039; thusly:&lt;br /&gt;
:#define MULTIPLIER_LIGHTSRCRADIANCE	2.0&lt;br /&gt;
:#define MULITPLIER_EXPOSURE		1.0&lt;br /&gt;
&lt;br /&gt;
*For another example see cbr&amp;#039;s modifed &amp;quot;Tionisla is Mars&amp;quot; texture [https://bb.oolite.space/viewtopic.php?p=306156#p306156 here] (2026)&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Random number generator]] - original method for creating planet descriptions (before Oolite v.1.80 back in 2014).&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3860 seed = &amp;quot;1 2 3 4 5 6&amp;quot;;]: Psuedo-random number generation &amp;amp; planet descriptions (2007)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3808 position = &amp;quot;x y z&amp;quot; in planetinfo.plist] (2007)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=17678 How to regenerate planetinfo?] (cim, 2015) Replacing the current 7Mb .plist with the original goatsoup recipe.&lt;br /&gt;
&lt;br /&gt;
*Wildeblood&amp;#039;s [[World Builder]] allows you to experiment with these settings in-game.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Assorted Tweaks ===&lt;br /&gt;
*[[User:Submersible|Submersible]]&amp;#039;s collection of [https://www.youtube.com/user/submersibletoaster YouTube videos] of planet textures (2012)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=5044 Question: How to add custom planet descriptions] (2008)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=217053#p217053 Tweaking your skies] (Tricky, 2014)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20959 Empty system] Removing the stations (and presumably inhabitants) from a system (2021)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=17191 Programming for Interstellar Space] (2015)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]]&lt;br /&gt;
[[Category:Oolite scripting]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Sector1/Onrira&amp;diff=90364</id>
		<title>Sector1/Onrira</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Sector1/Onrira&amp;diff=90364"/>
		<updated>2026-11-11T00:19:46Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Torus station */ Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{System|Name=Onrira|Sector=1|System=23|XPos=22|YPos=232|Location=in the eight o&amp;#039;clock corner|Government=7|Economy=0|Techlevel=14|Population=6|Inhabitants=Blue Frogs|Productivity=52800|PlanetRadius=6678|MapX=22|MapY=116}}&lt;br /&gt;
&amp;lt;!-- Copy and edit the following box for a smaller &amp;quot;System Box&amp;quot; for fictions or OXPs&lt;br /&gt;
{{SmallSystem|Name=Onrira|Sector=1|System=23|XPos=22|YPos=232|Location=in the eight o&amp;#039;clock corner|Government=7|Economy=0|Techlevel=14|Population=6|Inhabitants=Blue Frogs|Productivity=52800|PlanetRadius=6678}}&lt;br /&gt;
End of the small system box --&amp;gt;&lt;br /&gt;
{{GalacticCatalogueEntry|Name=Onrira|Sector=1|System=23|Description=The world Onrira is mildly noted for the Onriraian deadly Esonatoid but plagued by lethal spotted yaks.}}&lt;br /&gt;
== Witchspace Routes ==&lt;br /&gt;
There are 4 direct Witchspace Routes from/to Onrira:&lt;br /&gt;
{{WitchspaceHeader}}&lt;br /&gt;
{{WitchspaceEntry|Name=Erlaza|Sector=1|System=113|Distance=3.2|Government=3|Economy=6|Techlevel=6|Population=3.0|Productivity=6720|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Larais|Sector=1|System=177|Distance=1.2|Government=3|Economy=4|Techlevel=9|Population=4.0|Productivity=13440|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Oresqu|Sector=1|System=204|Distance=2.8|Government=2|Economy=1|Techlevel=10|Population=4.0|Productivity=17280|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Orerve|Sector=1|System=255|Distance=6.8|Government=1|Economy=3|Techlevel=6|Population=2.5|Productivity=7000|Routes=}}&lt;br /&gt;
{{WitchspaceFooter}}&lt;br /&gt;
{{LocalAreaMapHeader|Name=Onrira|Sector=1|X=22|Y=232|Radius=5}}{{LocalAreaMapEntry|Name=Erlaza|RX=8|RY=-2|Radius=3}}{{LocalAreaMapEntry|Name=Larais|RX=-3|RY=4|Radius=4}}{{LocalAreaMapEntry|Name=Oresqu|RX=0|RY=-15|Radius=4}}{{LocalAreaMapEntry|Name=Orerve|RX=-10|RY=-29|Radius=4}}{{LocalAreaMapFooter}}&lt;br /&gt;
== Trade ==&lt;br /&gt;
{{PricelistEconomy0}}&lt;br /&gt;
== OXPs ==&lt;br /&gt;
&lt;br /&gt;
=== Famous Planets ===&lt;br /&gt;
[[image:Onrira (Animation).gif|right]]The planet Onrira is famous for its Torus station. When the first Torus station was unveiled in orbit around Onrira in 3129 (eighteen years ago), it was an event full of political promise. Both [[GASEC]] and GalCop had relied heavily on the services of [[Obnoxicorp]] in both the political lobbying and execution of the project. At the time Onrira was an unstable multi-government system, but the Torus station helped unify the planet&amp;#039;s inhabitants. It was a technological marvel at the time and Onrira became the first tech 14 planet in galaxy 1. ([[Famous Planets OXP]]) [[Category:Famous Planets|Onrira]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Torus station ===&lt;br /&gt;
Adds the famous [[Torus station]] to Onrira (and other systems too). Note: this is suppressed in the [[Stranger&amp;#039;s World]] suite of OXPs.&lt;br /&gt;
&lt;br /&gt;
=== Galactic Navy ===&lt;br /&gt;
[[Image:Sector1 Navy Sector Command 3 SmallNavySectorMap.png|right]]This system falls under the responsibility of the [[Sector1/Navy Command Station 3|Navy Command Station 3]] in [[Sector1/Isinor|Isinor]]. ([[Galactic Navy OXP]])&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Onrira Tori.png|thumb|right|320px|The renowned Onrira Torus station]]&lt;br /&gt;
== History ==&lt;br /&gt;
The [[Sidewinder (Oolite)|Sidewinder]] and [[Sidewinder NG]] are built here in the [[Onrira Orbital Shipyards]] by [[Spalder and Starblaze Inc]]. for [[Faulcon de Lacy]]. The Sidewinder Scout was originally built to Navy specifications for a multi-purpose support craft and the ship began rolling off production lines over a hundred and fifty years ago. It was replaced by the [[Sidewinder NG]] (Next Generation), a more compact, modern and hyperspace-capable version.&lt;br /&gt;
&lt;br /&gt;
== Fiction ==&lt;br /&gt;
&lt;br /&gt;
=== Status Quo ===&lt;br /&gt;
The novella [[Status Quo]] by [[Drew Wagar]] mentions Onrira as the birthplace of [[James Feynman]] and as the location of a top secret [[Faulcon de Lacy]] research laboratory.&lt;br /&gt;
{{QuoteText|Text=James Feynman was from the planet Onrira, thirty-something, tall, thin and dark–haired, with a hint of premature grey around the temples.&lt;br /&gt;
&lt;br /&gt;
[...]&lt;br /&gt;
&lt;br /&gt;
Of course, the engine design was beyond secret: this newly-built Faulcon de Lacy lab at Onrira dealt in technology way beyond state of the art: there was stuff here that wouldn’t be mainstream until long after he was dead.|Source=(Status Quo, Chapter 1)}}&lt;br /&gt;
[[Category:Status Quo]]&lt;br /&gt;
&lt;br /&gt;
=== Frog Space Rickshaw ===&lt;br /&gt;
Onrira is where Jaswindar Singh and his descendants established the Space Rickshaw Co. ([[Frog Space Rickshaw]])&lt;br /&gt;
&lt;br /&gt;
[[File:Alliances Bank.png|right|200px]]&lt;br /&gt;
=== Alliances ===&lt;br /&gt;
In the SW corner of Chart One - Two Corporate State Rich Industrial Systems have formed what have some considered to be an unnatural alliance. After a failed attempt to form this partnership nineteen Galactic Standard Years ago, where, during the final, delicate negotiations, the felines of [[Sector1/Ensoreus|Ensoreus]] finally lost control of their instinctive urges and began to knock the Blue Frog delegates of Onrira around the table covering them in fluff in the process.&lt;br /&gt;
&lt;br /&gt;
Both sides have denied that all of the most recent negotiations have been undertaken via Holo-3D Vid-Conferencing to avoid a repeat of the embarrassing incident.&lt;br /&gt;
&lt;br /&gt;
In the short period since this financial product from &amp;quot;Alliances&amp;quot; hit the market the number of Commanders visiting these two systems has increased by 32.8% (the only requirement to hold an &amp;quot;Alliances&amp;quot; account is that new account holders must spend at least 21 standard days at one of the systems main stations).&lt;br /&gt;
&lt;br /&gt;
It is said that the logo for &amp;quot;Alliances&amp;quot; harks back to the days when both systems had access to only the ageing Coriolis Stations and, as their Marketing Department points out, the logo also imitates the compass directions of North, South, East and West - clearly showing their intentions to spread the benefits of an Alliances account to the four corners of Chart One.&lt;br /&gt;
:[https://bb.oolite.space/viewtopic.php?p=69424#p69424 From &amp;quot;more competition in the banking sector&amp;quot; (2009)]&lt;br /&gt;
&lt;br /&gt;
=== The Traders Almanach ===&lt;br /&gt;
{{QuoteText|Text=If every Credit counts, try this: Best would be to buy computers or excavators and haul them to Erlaza. They give you about 49 to 58%, at least in Erlaza. Besides, the computers can also be sold well enough in Larais. What&amp;#039;s more, in the Onrira system, you can see the first torus station ever built and the Faulcon de Lacy laboratories. In this high-tech system you can purchase almost everything you need to improve and harden your ship.|Source=(Excerpt from: [[The Traders Almanach]] entry for 1:23)}}&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Planetinfo.plist&amp;diff=90363</id>
		<title>Planetinfo.plist</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Planetinfo.plist&amp;diff=90363"/>
		<updated>2026-11-10T13:27:33Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added OXP properties - Gas Giants, Turbulence, Landing sites&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;planetinfo.[[plist]]&amp;#039;&amp;#039;&amp;#039; in &amp;#039;AddOns/Config&amp;#039; contains a dictionary for each of systems for which you wish to set custom data. A list of all galaxies and planets can be found [[Oolite planet list|here]]. Each of the properties mentioned below can be set (but, notably, not the location of the main planet, which is hard coded into the system seed value):&lt;br /&gt;
&lt;br /&gt;
The planetinfo.plist in cim&amp;#039;s [[SOTL Exploration]] OXP contains more properties such as &amp;quot;coordinates&amp;quot; (the position of the system in the galaxy), &amp;quot;random_seed&amp;quot; (this dumb pilot has no idea!), and possibly others. Cim &amp;#039;&amp;#039;did&amp;#039;&amp;#039; say that not all the new properties in the planetinfo.plist for [[SOTL Altmap]] actually did anything! (Altmap new properties include: &amp;quot;founded&amp;quot;, planet_seismic_instability&amp;quot;, &amp;quot;planet_surface_gravity&amp;quot;, &amp;quot;undist&amp;quot;, &amp;quot;planet_wind_speeds&amp;quot; &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.)&lt;br /&gt;
&lt;br /&gt;
[[File:BellScrib goatsoup1.JPG|thumb|right|Ian Bell worksheet for the goatsoup recipe from his vanished archives&amp;lt;br&amp;gt;See [[Oolite_planet_list#Where_do_these_crazy_names_come_from|Where do these crazy names come from?]] ]]&lt;br /&gt;
&lt;br /&gt;
=== Colour Specifiers ===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Colour specifiers&amp;#039;&amp;#039;&amp;#039; are used to declare colours in material attribute dictionaries, and in other contexts such as lasers in &amp;#039;&amp;#039;[[shipdata.plist]]&amp;#039;&amp;#039;. Colour specifiers take any of several forms:&lt;br /&gt;
Named colours, RGB / RGBA tuples, RGB / RGBA dictionaries or HSBA dictionaries. &lt;br /&gt;
&lt;br /&gt;
Colours can be viewed at https://rgbcolorpicker.com/0-1 and many other websites&lt;br /&gt;
&lt;br /&gt;
Click on the &amp;quot;gory details&amp;quot; for more: ---&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-collapsible mw-collapsed&amp;quot;  data-expandtext=&amp;quot;Show gory details&amp;quot; data-collapsetext=&amp;quot;Hide gory details&amp;quot; style=&amp;quot;overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
==== Named colours ====&lt;br /&gt;
The simplest form of colour specifier is a string containing a colour name. The following names are supported:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
|+ Colour names&lt;br /&gt;
! Name !! RGBA value&lt;br /&gt;
|-&lt;br /&gt;
|  blackColor || 0, 0, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| darkGrayColor || 1/3, 1/3, 1/3, 1&lt;br /&gt;
|-&lt;br /&gt;
| lightGrayColor || 2/3, 2/3, 2/3, 1&lt;br /&gt;
|-&lt;br /&gt;
| whiteColor || 1, 1, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
| grayColor || 1/2, 1/2, 1/2, 1&lt;br /&gt;
|-&lt;br /&gt;
| redColor || 1, 0, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| greenColor || 0, 1, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| blueColor || 0, 0, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
| cyanColor || 0, 1, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
| yellowColor || 1, 1, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| magentaColor || 1, 0, 1, 1&lt;br /&gt;
|-&lt;br /&gt;
|  orangeColor || 1, 1/2, 0, 1&lt;br /&gt;
|-&lt;br /&gt;
| purpleColor || 1/2, 0, 1/2, 1&lt;br /&gt;
|-&lt;br /&gt;
| brownColor || 0.6, 0.4, 0.2, 1&lt;br /&gt;
|-&lt;br /&gt;
| clearColor || 0, 0, 0, 0&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== RGBA tuples ====&lt;br /&gt;
Colours may also be specified in RGB or RGBA (red, green, blue, alpha [transparency]). RGB or RGBA tuples may be specified as arrays or as strings separated by spaces. The values may range from 0 to 1 or 0 to 255. (If no value is greater than 1, 0–1 is assumed, otherwise 0–255.) Examples:&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;quot;1 1 0&amp;quot;&amp;lt;/code&amp;gt; — yellow&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;quot;0 128 0 128&amp;quot;&amp;lt;/code&amp;gt; — medium green at 50% opacity&lt;br /&gt;
* &amp;lt;code&amp;gt;(1, 0, 0)&amp;lt;/code&amp;gt; – red&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== RGBA dictionaries ====&lt;br /&gt;
Just in case you’re unsure of the order the RGB[A] components come in, you can use a dictionary:&lt;br /&gt;
 {&lt;br /&gt;
    blue = 0.8;&lt;br /&gt;
    green = 0.8;&lt;br /&gt;
 }&lt;br /&gt;
Accepted keys are &amp;#039;&amp;#039;&amp;#039;red&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;green&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;blue&amp;#039;&amp;#039;&amp;#039; and &amp;#039;&amp;#039;&amp;#039;alpha&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;opacity&amp;#039;&amp;#039;&amp;#039;), all optional (default: 0.0 for red, green and blue, 1.0 for alpha).&lt;br /&gt;
&lt;br /&gt;
==== HSBA dictionaries ====&lt;br /&gt;
But wait, there’s more! Colours may also be specified as dictionaries in the [http://en.wikipedia.org/wiki/HSB_colour_space HSB colour space]. Accepted keys are &amp;#039;&amp;#039;&amp;#039;hue&amp;#039;&amp;#039;&amp;#039; (hue angle in degrees, required), &amp;#039;&amp;#039;&amp;#039;saturation&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;brightness&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;value&amp;#039;&amp;#039;&amp;#039;) and &amp;#039;&amp;#039;&amp;#039;alpha&amp;#039;&amp;#039;&amp;#039; (or &amp;#039;&amp;#039;&amp;#039;opacity&amp;#039;&amp;#039;&amp;#039;). The default for the optional keys is 1.0.&lt;br /&gt;
 {&lt;br /&gt;
    // Pale magenta&lt;br /&gt;
    hue = 300;&lt;br /&gt;
    saturation = 0.3;&lt;br /&gt;
 }&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Added for Oolite v.1.91 ===&lt;br /&gt;
*air_density / or the Javascript planet entity airDensity - see below (pretty picture!) &lt;br /&gt;
&lt;br /&gt;
=== Added for Oolite v.1.89 ===&lt;br /&gt;
 This needs editing by somebody who understands it! Snatched from the Progress thread&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=270737#p270737 air_color] now produces the right color for the sky. Not only that, it is now used as the atmosphere scatter color when the planet is viewed from space. Non-blue atmospheres are finally possible!&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=270771#p270771 air_color_mix_ratio]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=271058#p271058 terminator_threshold_vector shipdata key]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=271058#p271058 JSPlanet terminatorThresholdVector property]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=269833#p269833 MULTIPLIER_LIGHTSRCRADIANCE and MULITPLIER_EXPOSURE]: Planet, ships and atmosphere shaders can now define lightsource radiance and scene exposure multipliers&lt;br /&gt;
*Also stuff about city lights&lt;br /&gt;
*And probably other stuff I missed!&lt;br /&gt;
&lt;br /&gt;
==Where Settings Apply==&lt;br /&gt;
&lt;br /&gt;
===Universal Settings===&lt;br /&gt;
&lt;br /&gt;
Universal options are applied to all 2048 solar systems, this is useful for settings such as ambient lighting levels, eg.&lt;br /&gt;
 &amp;quot;universal&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
Universal options can be over-ridden by specifying the same option for a specific system or. Obviously, not all options make sense to apply to the whole universe.&lt;br /&gt;
&lt;br /&gt;
===Interstellar Space===&lt;br /&gt;
&lt;br /&gt;
Conditions for interstellar space in general can be set with the “interstellar space” key.&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=17191 Procedure to find all interstellar spaces] (2015)&lt;br /&gt;
&lt;br /&gt;
===Specific Systems===&lt;br /&gt;
&lt;br /&gt;
Each system is keyed by a string consisting of the galaxy number (0..7) followed by a space and then the planet number (0..255), eg.&lt;br /&gt;
 &amp;quot;0 7&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
specifies system 7, in galaxy 0, &amp;#039;&amp;#039;Lave&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
===Specific Interstellar Spaces===&lt;br /&gt;
&lt;br /&gt;
You can also specify a position in interstellar space, eg.&lt;br /&gt;
 &amp;quot;interstellar: 0 7 129&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
specifies the space in galaxy 0 between systems 7 and 129, &amp;#039;&amp;#039;Lave&amp;#039;&amp;#039; and &amp;#039;&amp;#039;Zaonce&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
Note that&lt;br /&gt;
 &amp;quot;interstellar: 0 7 129&amp;quot; = // jumping from Lave towards Zaonce&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
and&lt;br /&gt;
 &amp;quot;interstellar: 0 129 7&amp;quot; = // jumping from Zaonce towards Lave&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
are distinct locations and if they both need the same properties this must be explicitly set for both.&lt;br /&gt;
&lt;br /&gt;
In 1.81 the property &amp;quot;link_color&amp;quot; when set on a specific interstellar space changes the colour of the link between the two systems in the advanced navigation array (assuming no route is in place above it). When setting link_color, the lower system ID must be placed first, because of how the chart is drawn.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039; that [[User:Switeck|Switeck]] has done a lot of work on this - there are intermediate spots in the interstellar spaces - but only on the line between two systems. See the OXPs on his User: page&lt;br /&gt;
&lt;br /&gt;
==Layers==&lt;br /&gt;
&lt;br /&gt;
Settings other than &amp;quot;universal&amp;quot; in Oolite 1.81 or later have a &amp;#039;layer&amp;#039; property from 0 to 3. The default value for planetinfo.plist files is 1. If multiple OXPs specify a setting for a particular property, the order they will be checked in is:&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 3 settings&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 2 settings&amp;#039;&amp;#039;&amp;#039; (default for Javascript changes to data)&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 1 settings&amp;#039;&amp;#039;&amp;#039; (default for planetinfo.plist)&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Universal settings&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;* Layer 0 settings&amp;#039;&amp;#039;&amp;#039; (value for core game settings)&lt;br /&gt;
&lt;br /&gt;
This allows OXPs to safely override each other&amp;#039;s changes if necessary, and for OXPs which really need a specific setting in a particular system to set it at layer 3&lt;br /&gt;
&lt;br /&gt;
Example&lt;br /&gt;
 &amp;quot;layer&amp;quot; = 2;&lt;br /&gt;
&lt;br /&gt;
==Terraforming Example==&lt;br /&gt;
   &lt;br /&gt;
For the planet Lave, you would use the key &amp;#039;0 7&amp;#039; (planet 7 in galaxy 0) Then you set the values. The following example sets Lave&amp;#039;s sea to blue, land to green, and land to sea ratio to 75%. &lt;br /&gt;
 &lt;br /&gt;
Code:&lt;br /&gt;
 { &lt;br /&gt;
    &amp;quot;0 7&amp;quot; = &lt;br /&gt;
    { &lt;br /&gt;
       &amp;quot;percent_land&amp;quot; = &amp;quot;75&amp;quot;;&lt;br /&gt;
       &amp;quot;land_color&amp;quot; = &amp;quot;0.5 1.0 0.5&amp;quot;;&lt;br /&gt;
       &amp;quot;sea_color&amp;quot; =  &amp;quot;0.3 0.7 1.0&amp;quot;;&lt;br /&gt;
    } &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
Then you can override any of the settings listed above, for example to change Zaatxe&amp;#039;s (Galaxy 0 Planet 8) inhabitants into blue frogs you&amp;#039;d enter &lt;br /&gt;
 &lt;br /&gt;
Code:&lt;br /&gt;
     &amp;quot;0 8&amp;quot; =  &lt;br /&gt;
    { &lt;br /&gt;
         &amp;quot;inhabitants&amp;quot; = &amp;quot;Blue Frogs&amp;quot;;&lt;br /&gt;
    } &lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
You can use any or all of the keys in each of the entries. It&amp;#039;s probably best to only use the key&amp;#039;s you want to change. So, another example, to change the sky_blur_xxx settings for Zaonce (Galaxy 0 Planet 129) to big, heavily clustered, but pale blurs - you&amp;#039;d enter &lt;br /&gt;
 &lt;br /&gt;
Code:&lt;br /&gt;
     &amp;quot;0 129&amp;quot; = &lt;br /&gt;
    { &lt;br /&gt;
         &amp;quot;sky_blur_cluster_chance&amp;quot; =  &amp;quot;0.9&amp;quot;;&lt;br /&gt;
         &amp;quot;sky_blur_alpha&amp;quot; = &amp;quot;0.1&amp;quot;;&lt;br /&gt;
         &amp;quot;sky_blur_scale&amp;quot; = &amp;quot;32.0&amp;quot;;&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==About the Inhabitants==&lt;br /&gt;
&lt;br /&gt;
===Concealment===&lt;br /&gt;
{{oolite-prop-added|1.83}}&lt;br /&gt;
&lt;br /&gt;
An integer that determines how much information about the system is unknown.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;concealment&amp;quot; = &amp;quot;300&amp;quot;;&lt;br /&gt;
The following values are recognised:&lt;br /&gt;
* 0: default, all information visible&lt;br /&gt;
* 100 or more: F7 screen shows no information, economy/government/TL/star colour not visible on chart&lt;br /&gt;
* 200 or more: system name is not shown&lt;br /&gt;
* 300 or more: system vanishes entirely from chart, will not be used in route plotting, cannot be targeted by player (NPCs can still jump to it, though)&lt;br /&gt;
&lt;br /&gt;
===Government===&lt;br /&gt;
&lt;br /&gt;
An integer between 0 and 7 indicating the government type of the system.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;government&amp;quot; = &amp;quot;7&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Possible values:&lt;br /&gt;
: 0: Anarchy&lt;br /&gt;
: 1: Feudal&lt;br /&gt;
: 2: Multi-Governmental&lt;br /&gt;
: 3: Dictatorship&lt;br /&gt;
: 4: Communist&lt;br /&gt;
: 5: Confederacy&lt;br /&gt;
: 6: Democracy&lt;br /&gt;
: 7: Corporate State&lt;br /&gt;
&lt;br /&gt;
===Economy===&lt;br /&gt;
An integer between 0 and 7 indicating the economy type of the system.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;economy&amp;quot; = &amp;quot;5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Possible values:&lt;br /&gt;
: 0: Rich Industrial&lt;br /&gt;
: 1: Average Industrial&lt;br /&gt;
: 2: Poor Industrial&lt;br /&gt;
: 3: Mainly Industrial&lt;br /&gt;
: 4: Mainly Agricultural&lt;br /&gt;
: 5: Rich Agricultural&lt;br /&gt;
: 6: Average Agricultural&lt;br /&gt;
: 7: Poor Agricultural&lt;br /&gt;
 &lt;br /&gt;
===Tech Level===&lt;br /&gt;
&lt;br /&gt;
An integer between 0 and 14 indicating the sophistication of the planets technology. The tech level displayed on the system data screens in game is one higher than this number (range 1 to 15).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;techlevel&amp;quot; = &amp;quot;13&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?p=113258#p113258 Episodic minor variations in TL (2010)]&lt;br /&gt;
&lt;br /&gt;
Further Note: The [[Famous Planets]] OXP transmogrifies [[Sector1/Sori]] into the Anarchy &amp;quot;Ascension&amp;quot; with a TL of 16! This is virtually no different to Ceesxe&amp;#039;s TL 15.&lt;br /&gt;
&lt;br /&gt;
===Population===&lt;br /&gt;
&lt;br /&gt;
An integer between 0 and 67 indicating the number of inhabitants of a planet in hundreds of millions&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;population&amp;quot; = &amp;quot;23&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
See Wildeblood&amp;#039;s note on no upper limit [https://bb.oolite.space/viewtopic.php?p=299408#p299408 here] (2025)&lt;br /&gt;
&lt;br /&gt;
===Productivity===&lt;br /&gt;
&lt;br /&gt;
An integer indicating the productivity of a planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;productivity&amp;quot; = &amp;quot;1000&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Name===&lt;br /&gt;
&lt;br /&gt;
The name of the planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;name&amp;quot; = &amp;quot;The planet&amp;#039;s name&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;: See the [https://bb.oolite.space/viewtopic.php?t=12131 Pronounceable Planets Project] thread on the forum for some ideas!&lt;br /&gt;
&lt;br /&gt;
===Inhabitant===&lt;br /&gt;
&lt;br /&gt;
The name for one of the inhabitants of the main planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;inhabitant&amp;quot; = &amp;quot;Green Platypus&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Inhabitants===&lt;br /&gt;
&lt;br /&gt;
The name of the inhabitants of the main planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;inhabitants&amp;quot; = &amp;quot;Green Platypi&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Description===&lt;br /&gt;
&lt;br /&gt;
A short description of the planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;description&amp;quot; = &amp;quot;Really, anything you want to say about the place!&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;: For more than 1 oxp describing a system see [https://bb.oolite.space/viewtopic.php?p=165471#p165471 here] (2012) - and elsewhere. Note that &amp;#039;&amp;#039;eg&amp;#039;&amp;#039;. [[System Features Rings]] does this through Javascript. rather than a .plist.&lt;br /&gt;
&lt;br /&gt;
===Government Description===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Overrides the default text used to describe the government.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;government_description&amp;quot; = &amp;quot;Dictatorship (Monarchy)&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Economy Description===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Overrides the default text used to describe the economy.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;economy_description&amp;quot; = &amp;quot;Mainly Industrial (Machine Tools)&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Population Description===&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
Overrides the default text used to describe the population.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;population_description&amp;quot; = &amp;quot;13 Billion&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Random Seed===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
A seed for a random number generator used in Oolite 1.81 to generate system properties impractical to store in this file (e.g. the positions of each star on the background starfield)&lt;br /&gt;
&lt;br /&gt;
For historical reasons, this is a string of 6 integers between 0 and 255, for example:&lt;br /&gt;
 random_seed = &amp;quot;74 90 72 2 83 183&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==System population==&lt;br /&gt;
These properties are only used in Oolite 1.79 or later.&lt;br /&gt;
&lt;br /&gt;
===Populator===&lt;br /&gt;
&lt;br /&gt;
The name of the worldscript function which will be used to [[Oolite_System_Populator|populate the system]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;populator&amp;quot; = &amp;quot;systemWillPopulate&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Repopulator===&lt;br /&gt;
&lt;br /&gt;
The name of the worldscript function which will be used to [[Oolite_System_Populator|repopulate the system]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;repopulator&amp;quot; = &amp;quot;systemWillRepopulate&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==Properties of the Planet==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Most of these properties are ignored if a planet texture is set.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Note that the available planet texture generator properties changed in places between Oolite 1.77 and Oolite 1.80&lt;br /&gt;
&lt;br /&gt;
And note the 2016 introduction of the shader uniform [[Shaders in Oolite: uniforms|fogUniform]] (a Javascript method for adding fog to planet atmospheres)&lt;br /&gt;
&lt;br /&gt;
===Air Color===&lt;br /&gt;
A colour specifier determining the color of the planet&amp;#039;s sky, as well as the atmosphere scatter color.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;air_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Air Color Mix Ratio===&lt;br /&gt;
{{oolite-prop-added|1.89}}&lt;br /&gt;
&lt;br /&gt;
The amount of air color that be mixed in the overall atmosphere color. A number from 0.0 to 1.0 (default 0.5).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;air_color_mix_ratio&amp;quot; = &amp;quot;0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Atmosphere Rotational Velocity===&lt;br /&gt;
&lt;br /&gt;
Sets how fast the atmosphere is rotating. (A random value between 0.0 to 0.03 is the default).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;atmosphere_rotational_velocity&amp;quot; = &amp;quot;0.1&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Cloud Alpha===&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The transparency level of the cloud layer, relative to the standard transparency. 1.0 is the default. Texture packs which include clouds on the planetary texture may wish to reduce this.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cloud_alpha&amp;quot; = &amp;quot;0.2&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Has Atmosphere===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
This boolean property is used for the main planet only. If it is unset or true, the main planet has an atmosphere, as is always the case in 1.80 and before. If it is set to be false, then the planet will not have an atmosphere.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_atmosphere&amp;quot; = 0;&lt;br /&gt;
&lt;br /&gt;
This has no effect on secondary planets - their atmosphere is determined by whether addition uses &amp;lt;code&amp;gt;addPlanet&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;addMoon&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
[[File:AtmDensityExample.png|thumb|320px|right|Atmosphere Density examples: Stranger&amp;#039;s &amp;#039;&amp;#039;FPO Lave&amp;#039;&amp;#039; in four increasing atmosphere densities: 0.2, 0.5, 0.75 and 1.0. Every other parameter in the planet definition is the same in all pictures.]]&lt;br /&gt;
=== Air Density ===&lt;br /&gt;
{{oolite-prop-added|1.91}}&lt;br /&gt;
&lt;br /&gt;
A number clamped in range from 0.0 to 1.0 describing the density of the planet&amp;#039;s atmosphere. All planets in the core use 0.75 as default.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;air_density&amp;quot; = &amp;quot;0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Illumination Color===&lt;br /&gt;
{{oolite-prop-added|1.91}}&lt;br /&gt;
&lt;br /&gt;
A colour specifier determining the colour of the planet&amp;#039;s illumination such as cities light. Illumination is inserted as a grayscale map in the alpha channel of the planet&amp;#039;s diffuse texture. You can specify this key even if no illumination map is defined, but it won&amp;#039;t have any effect - without an illumination map the dark side of the planet remains dark in all cases.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;illumination_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Land Color===&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;land_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Percent Cloud===&lt;br /&gt;
The percentage of the planet&amp;#039;s atmosphere occupied by clouds.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;percent_cloud&amp;quot; = &amp;quot;0..100&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note that with a low cloud_alpha setting not all of the clouds defined here may actually be visible&lt;br /&gt;
&lt;br /&gt;
===Percent Ice===&lt;br /&gt;
The percentage of the planet occupied by the polar ice caps. Oolite 1.81 or later.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;percent_ice&amp;quot; = &amp;quot;0..100&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Percent Land===&lt;br /&gt;
The percentage of the planet occupied by land.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;percent_land&amp;quot; = &amp;quot;0..100&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Planet Distance===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The distance from the centre of the planet to the witchpoint. Only used for the system main planet - secondary planets are positioned separately.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;planet_distance&amp;quot; = &amp;quot;410000&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
The main planet is always positioned on the z-axis.&lt;br /&gt;
&lt;br /&gt;
===Planet Distance Multiplier===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Multiplies the distance from the centre of the main planet to the witchpoint.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;planet_distance_multiplier&amp;quot; = &amp;quot;1.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Planet Name===&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The planet&amp;#039;s name. For the main planet, this defaults to being the same as the system name - the property is mainly intended for secondary planets.&lt;br /&gt;
&lt;br /&gt;
Example&lt;br /&gt;
  &amp;quot;planet_name&amp;quot; = &amp;quot;Earth&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Polar Land Color===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Sets the land colour in polar regions.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;land_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Polar Sea Color===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Sets the sea colour in polar regions.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sea_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Radius===&lt;br /&gt;
An integer between 3000 and 7000 indicating the radius of the main planet. On the F7 screen, this is measured in kilometres. The radius in game is 1/100th of this.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;radius&amp;quot; = &amp;quot;5500&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Rotational Velocity===&lt;br /&gt;
A number describing the rotational velocity of the planet in radians per second. Overrides rotation_speed if both are set.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;rotational_velocity&amp;quot; = 0.0015;&lt;br /&gt;
&lt;br /&gt;
===Rotation Speed===&lt;br /&gt;
A number describing the rotational velocity of the planet in radians per second. Unlike rotational_velocity, this is affected by rotation_speed_factor.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;rotation_speed&amp;quot; = 0.0015;&lt;br /&gt;
&lt;br /&gt;
===Rotation Speed Factor===&lt;br /&gt;
The rotational speed of all planets whose rotational speed was set by rotation_speed and not by rotational_velocity will be multiplied by this number.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  &amp;quot;rotation_speed_factor&amp;quot; = 1.0;&lt;br /&gt;
&lt;br /&gt;
(Intended more for the universal section as a &amp;quot;personal taste&amp;quot; option than for individual planets)&lt;br /&gt;
&lt;br /&gt;
===Sea Color===&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sea_color&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Terminator Threshold Vector===&lt;br /&gt;
{{oolite-prop-added|1.89}}&lt;br /&gt;
&lt;br /&gt;
This property gives control over the color of the planet&amp;#039;s terminator. The way the property works is not entirely straightforward, so see [https://bb.oolite.space/viewtopic.php?p=271058#p271058 this post on BB] for more information.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;terminator_threshold_vector&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
By default the terminator vector is &amp;quot;0.105 0.18 0.28&amp;quot; - which results in a reddish orange colour.&lt;br /&gt;
&lt;br /&gt;
===Texture===&lt;br /&gt;
The replacement texture to be used by a system&amp;#039;s main planet.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For textures you can use lat-long maps (twice as wide as high) with a special elongation at the poles, or cube maps. Other maps will also be wrapped around planets, but will always give distortions.&amp;lt;br&amp;gt;&lt;br /&gt;
Since Oolite 1.74 you can also use cube maps for planets. Cube maps are 6 times higher than wide and will be recognised automatically by Oolite, based on the dimensions. Cube maps are the preferred method, because lat-long give some distortion and have the poles improperly placed in Oolite&amp;#039;s implementation. See also [[Planettool]] for conversion from lat-long into cube maps.&lt;br /&gt;
&lt;br /&gt;
From Oolite 1.89 onwards, illumination mapping on custom planets is supported. The illumination map goes in the diffuse map&amp;#039;s alpha channel. Low alpha values translate to high illumination. This allows for effects like city lights on a planet&amp;#039;s dark side.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;texture&amp;quot; =  &amp;quot;newPlanetTexture.png&amp;quot;;&lt;br /&gt;
:N.B.&lt;br /&gt;
The illumination mapping feature is disabled by setting &amp;#039;&amp;#039;Graphics Detail: Shaders Enabled&amp;#039;&amp;#039; or lower in the game setting menu. &amp;#039;&amp;#039;Enabled&amp;#039;&amp;#039; at &amp;#039;&amp;#039;Graphics Detail: Extra Detail&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
===Texture HSB Color===&lt;br /&gt;
This changes the overall hue of the replacement texture.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;texture_hsb_color&amp;quot; =  &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Texture NormSpec===&lt;br /&gt;
{{oolite-prop-added|1.89}}&lt;br /&gt;
&lt;br /&gt;
The external texture that will be used as a normal and specular map for the given planet. Colorspace should be linear, with the normal map in the r,g and b and the specular map in the a channel. The texture can be of either equirectangular or cubemap formats. This feature is available at the Extra Detail setting only. To set:&lt;br /&gt;
 &amp;quot;texture_normspec&amp;quot; = &amp;quot;planetNormalAndSpecularMap.png&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
=== OXP Property: Gas Giants ===&lt;br /&gt;
Several OXPs introduce gas giants and assign them characteristics (the [[Stranger&amp;#039;s World]] suite of OXPs, the [[Additional Planets]] OXP suite, and the vintage [[DeepHorizon]] suite). Deep Horizon adds an extra OXP allowing one to skim fuel from gas giants. The most recent version of [[Cloud City OXP]] places cloud cities at gas giants.&lt;br /&gt;
&lt;br /&gt;
These three OXP suites probably all use different keys to identify their gas giants. Not being a programmer, this editor has no idea as to what they are!&lt;br /&gt;
&lt;br /&gt;
See the 2026 discussion starting [https://bb.oolite.space/viewtopic.php?p=305866#p305866 here]. More realistic gas giants require a &amp;#039;&amp;#039;deep&amp;#039;&amp;#039; atmosphere which is currently not available in the vanilla game code. [[Planetfall]]&amp;#039;s heat/turbulence is not yet an atmosphere, although it mimics elements of it!&lt;br /&gt;
&lt;br /&gt;
=== OXP Property: Atmospheric turbulence ===&lt;br /&gt;
This is introduced by [[Planetfall2 OXP]] - look at the &amp;quot;planetFall2_turbulence.js&amp;quot; file inside the scripts folder in the OXP.&lt;br /&gt;
&lt;br /&gt;
=== OXP Property: Landing sites ===&lt;br /&gt;
These are introduced by [[Planetfall2 OXP]] - see the [[Planetfall2_OXP#The_Dark_Side|copious material]] which [[User:Phkb|Phkb]] has produced explaining how to do this.&lt;br /&gt;
&lt;br /&gt;
==Properties of the Sky==&lt;br /&gt;
&lt;br /&gt;
===Ambient Level===&lt;br /&gt;
&lt;br /&gt;
Sets how much ambient light (shed by stars and nebulae) illuminates the dark side of objects like planets and ships. Values should typically be between 0.0 and 1.0 (1.0 is the default) but can be higher for a flat lit, cartoon-like effect.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;ambient_level&amp;quot; = &amp;quot;0.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Nebula Count Multiplier===&lt;br /&gt;
This is used for defining the number of nebulas. Default is 1.0. Number can be greater or less than default and is also randomised a bit. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;nebula_count_multiplier&amp;quot; = &amp;quot;1.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky Blur Alpha===&lt;br /&gt;
Default 0.1&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_blur_alpha&amp;quot; = &amp;quot;0.0 .. 1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky Blur Cluster Chance===&lt;br /&gt;
This is used for creating nebulae (typically 0.80)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_blur_cluster_chance&amp;quot; = &amp;quot;0.85&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky Blur Scale===&lt;br /&gt;
Default 10. Larger numbers generate bigger nebula, but slow down the game considerable on slower machines.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_blur_scale&amp;quot; = &amp;quot;0.0 .. 128.0 or more&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky N Blurs===&lt;br /&gt;
This is used for defining the number of nebulas (typical is 80, maximum is 1280). This key is multiplied by a &amp;quot;nebula_count_multiplier&amp;quot; definition in Oolite 1.81 or later.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_n_blurs&amp;quot; = &amp;quot;800&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky N Stars===&lt;br /&gt;
This is used for defining the number of stars (typical = 600, maximum in 1.76 or earlier is 4800). This key is multiplied by a &amp;quot;star_count_multiplier&amp;quot; definition in Oolite 1.81 or later. In reduced detail mode, this number will be capped to 2400.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_n_stars&amp;quot; = &amp;quot;1200&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sky and Nebula RGB Colors===&lt;br /&gt;
&lt;br /&gt;
These are rgb values (from 0.0 to 1.0) for the two colours between which the colour of the stars (and nebulaesque blurs) vary, ordered r1 g1 b1 r2 g2 b2 where (r1 g1 b1) defines the first colour and (r2 g2 b2) the second.&amp;lt;br&amp;gt;&lt;br /&gt;
(Default values are &amp;quot;0.75 0.8 1.0 1.0 0.85 0.6&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sky_rgb_colors&amp;quot; = &amp;quot;0.0..1.0 0.0..1.0 0.0..1.0 0.0..1.0 0.0..1.0 0.0..1.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Alternatively, two [[Materials in Oolite#Colour specifiers|colour specifiers]] may be used:&lt;br /&gt;
 &amp;quot;sky_color_1&amp;quot; = &amp;quot;redColor&amp;quot;;&lt;br /&gt;
 &amp;quot;sky_color_2&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
     &amp;quot;hue&amp;quot; = &amp;quot;60&amp;quot;;&lt;br /&gt;
     &amp;quot;brightness&amp;quot; = &amp;quot;0.8&amp;quot;;&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 &amp;quot;nebula_color_1&amp;quot; = &amp;quot;greenColor&amp;quot;;&lt;br /&gt;
 &amp;quot;nebula_color_2&amp;quot; = &amp;quot;blueColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Star Count Multiplier===&lt;br /&gt;
This is used for defining the number of stars. Default is 1.0. Number can be greater or less than default and is also randomised a bit. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;star_count_multiplier&amp;quot; = &amp;quot;0.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Properties of the Station==&lt;br /&gt;
&lt;br /&gt;
===Market Script===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
A Javascript file used to load a [[Oolite Market Scripts|market script]] for global system price and quantity modifications.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;market_script&amp;quot; = &amp;quot;myoxp_newsystemmarket.js&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; [https://bb.oolite.space/viewtopic.php?p=235837#p235837 What&amp;#039;s the difference between the market script specified in planetinfo.plist and the one called for by trade-goods.plist?] (2015)&lt;br /&gt;
&lt;br /&gt;
===Station===&lt;br /&gt;
The type of station orbiting the main planet.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station&amp;quot; = &amp;quot;coriolis..dodec..special&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Station Roll===&lt;br /&gt;
The speed at which the station rotates (as with all rotational velocities this is in radians per second) and affects all rotating stations in a system. For a specific station you can use the key [[Shipdata.plist#station_roll | station_roll]] in shipdata.plist.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station_roll&amp;quot; = &amp;quot;0.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Station Vector===&lt;br /&gt;
The direction of the main station from the main planet&lt;br /&gt;
 &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station_vector&amp;quot; = &amp;quot;-0.717 -0.668 0.201&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Stations Require Docking Clearance===&lt;br /&gt;
&lt;br /&gt;
Specifies if a player has to explicit ask docking permission. See also [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|Oolite Docking Clearance]]&lt;br /&gt;
&lt;br /&gt;
===Market (defunct)===&lt;br /&gt;
The market to be used in this system as the default market. It points to a key in commodities.plist&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;market&amp;quot; = &amp;quot;rockhermit&amp;quot;;&lt;br /&gt;
Will use the rockhermit market as default for for all stations in the system. When no market is defined a key in commodities.plist is used that matches the role of the main station. Than that is not defined, the default market is used in this system.&lt;br /&gt;
&lt;br /&gt;
In 1.81 and later, this is replaced by market_script&lt;br /&gt;
&lt;br /&gt;
==Properties of the Sun==&lt;br /&gt;
;N.B.&lt;br /&gt;
The corona effect, modified by the first three properties mentioned below, is disabled by setting &amp;#039;&amp;#039;Reduced Detail:On&amp;#039;&amp;#039; in the game setting menu. &amp;#039;&amp;#039;Enabled&amp;#039;&amp;#039; by default (&amp;#039;&amp;#039;Reduced Detail:Off&amp;#039;&amp;#039;).&lt;br /&gt;
&lt;br /&gt;
===Corona Flare===&lt;br /&gt;
&lt;br /&gt;
Sets the overall size of the corona in proportion to its sun. (See note above.)&lt;br /&gt;
&lt;br /&gt;
A number from 0.0 (invisibly small) to 1.0 (huge)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;corona_flare&amp;quot; = &amp;quot;0.075&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Corona Hues===&lt;br /&gt;
&lt;br /&gt;
Specifies whether the corona should have visible bands of colours within the corona. (See note above.)&lt;br /&gt;
&lt;br /&gt;
A number from 0.0 (monochromatic) to 1.0 (vivid alternating colours).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;corona_hues&amp;quot; = &amp;quot;0.6&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Corona Shimmer===&lt;br /&gt;
&lt;br /&gt;
Specifies how quickly the corona colours change. (See note above.)&lt;br /&gt;
&lt;br /&gt;
A number from 0.0 (very slow) to 1.0 (very fast).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;corona_shimmer&amp;quot; = &amp;quot;0.4&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Color===&lt;br /&gt;
&lt;br /&gt;
Sets the colour of a system&amp;#039;s sun.&lt;br /&gt;
&lt;br /&gt;
Can be any [[Materials in Oolite#Colour specifiers|colour specifier]] or [[Materials in Oolite#Named colours|named colour]]. The specified colour is blended with 50% white so it will never be a saturated colour.  Dark colours will be brightened by this blending.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_color&amp;quot; = &amp;quot;blueColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Distance===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Sets the distance between the sun and the main planet in metres.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_distance&amp;quot; = 924122;&lt;br /&gt;
&lt;br /&gt;
Ignored if sun_distance_modifier is set.&lt;br /&gt;
&lt;br /&gt;
===Sun Distance Multiplier===&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Multiplies the distance between the sun and the main planet by this factor.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_distance_multiplier&amp;quot; = 2;&lt;br /&gt;
&lt;br /&gt;
Ignored if sun_distance_modifier is set.&lt;br /&gt;
&lt;br /&gt;
===Sun Distance Modifier===&lt;br /&gt;
&lt;br /&gt;
Sets the approximate distance between a system sun and its main planet. The standard distance is 20 planetary radii. Setting it much lower (10, or even less) will cause delays when generating systems, as Oolite compensates for possible collisions between the sun and other system objects.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_distance_modifier&amp;quot; = &amp;quot;15.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.81 or later, sun_distance_multiplier is more useful.&lt;br /&gt;
&lt;br /&gt;
=== Sun Gone Nova ===&lt;br /&gt;
&lt;br /&gt;
Sets a nova sun in the system.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_gone_nova&amp;quot; = &amp;quot;YES&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Name===&lt;br /&gt;
&lt;br /&gt;
Stores the name of a system&amp;#039;s sun. This is only implemented in Oolite from version 1.79 onwards, though was used by OXPs before then.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_name&amp;quot; = &amp;quot;Alpha Centauri&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Radius===&lt;br /&gt;
&lt;br /&gt;
Sets the radius of a system&amp;#039;s sun. A number between 1000 and 1000000.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_radius&amp;quot; = &amp;quot;100000&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Sun Vector===&lt;br /&gt;
The direction of the sun from the main planet&lt;br /&gt;
 &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;sun_vector&amp;quot; = &amp;quot;-0.717 -0.668 0.201&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==Additional Planets==&lt;br /&gt;
&lt;br /&gt;
Finally you can also define your own custom planets and moons:&lt;br /&gt;
 &amp;quot;LavesPurpleMoon&amp;quot; =&lt;br /&gt;
 {&lt;br /&gt;
 ...&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--They also can be added through script_actions, but it&amp;#039;s deprecated and even commented out on this page--&amp;gt;&lt;br /&gt;
To add them to the system, use JS methods &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_System#addPlanet|system.addPlanet]]&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_System#addPlanet|system.addMoon]]&amp;lt;/code&amp;gt;. For the example above, the &amp;lt;code&amp;gt;planetInfoKey&amp;lt;/code&amp;gt; will be &amp;lt;code&amp;gt;&amp;quot;LavesPurpleMoon&amp;quot;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
===Position===&lt;br /&gt;
Position of the planet in space. The first parameter is 3-character code of the coordinate system, other three is x, y and z components of position vector.&lt;br /&gt;
 &amp;quot;position&amp;quot; = &amp;quot;pwm 0 -50000 0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
You can omit the coordinate system parameter, then the absolute coordinate system will be used:&lt;br /&gt;
 &amp;quot;position&amp;quot; = &amp;quot;0 -50000 0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See [[Oolite coordinate systems]] for more info about it.&lt;br /&gt;
&lt;br /&gt;
===Orientation===&lt;br /&gt;
Orientation of the planet in space (seems not to be working correctly).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;orientation&amp;quot; = &amp;quot;0.0 1.0 0.0 0.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
===Other keys===&lt;br /&gt;
&lt;br /&gt;
You can use other keys from the [[#Properties_of_the_Planet| Properties of the Planet]] section for your planets and moons.&lt;br /&gt;
&lt;br /&gt;
Here are some of the keys you may want to use:&lt;br /&gt;
* &amp;quot;radius&amp;quot;: Radius of the planet in km. e.g. a value of 500 is drawn with a radius of 5000 meters but in player dialogues this value is presented as 500 km.&lt;br /&gt;
* &amp;quot;rotational_velocity&amp;quot;: Rotation of the planet in rotations per second.&lt;br /&gt;
* &amp;quot;texture&amp;quot;: The name of the texture file that is used to wrap around the surface.&lt;br /&gt;
* &amp;quot;seed&amp;quot;: Seed value used to create the planet&amp;#039;s surface features. If no seed is defined it uses the same seed as the main planet, and will create a copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:Ico-Glow.png|thumb|right|300px|Click for more detail (eg the Ico station)]]&lt;br /&gt;
== Experimentation ==&lt;br /&gt;
The effect to the right was created by [[User:Cody|Cody]]. &amp;quot;OXPs were a Griff Icosahedron station, a [[Deep Horizon Nav Buoy]], a core planet (I think - if not, [[Povray Planets]]), a mix of [[KeeperSky]] &amp;amp; [[Zygo Cinematic Sky &amp;amp; Nebulas]], plus &amp;#039;&amp;#039;&amp;#039;star_count_multiplier&amp;#039;&amp;#039;&amp;#039; = 56; &amp;#039;&amp;#039;&amp;#039;sun_distance_multiplier&amp;#039;&amp;#039;&amp;#039; = 5; and &amp;#039;&amp;#039;&amp;#039;ambient_level&amp;#039;&amp;#039;&amp;#039; = 0.15;&lt;br /&gt;
&lt;br /&gt;
For a similar &amp;quot;lights down&amp;quot; look, you&amp;#039;d have to tweak &amp;#039;&amp;#039;&amp;#039;oolite-default-shader.fragment&amp;#039;&amp;#039;&amp;#039; thusly:&lt;br /&gt;
:#define MULTIPLIER_LIGHTSRCRADIANCE	2.0&lt;br /&gt;
:#define MULITPLIER_EXPOSURE		1.0&lt;br /&gt;
&lt;br /&gt;
*For another example see cbr&amp;#039;s modifed &amp;quot;Tionisla is Mars&amp;quot; texture [https://bb.oolite.space/viewtopic.php?p=306156#p306156 here] (2026)&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Random number generator]] - original method for creating planet descriptions (before Oolite v.1.80 back in 2014).&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3860 seed = &amp;quot;1 2 3 4 5 6&amp;quot;;]: Psuedo-random number generation &amp;amp; planet descriptions (2007)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3808 position = &amp;quot;x y z&amp;quot; in planetinfo.plist] (2007)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=17678 How to regenerate planetinfo?] (cim, 2015) Replacing the current 7Mb .plist with the original goatsoup recipe.&lt;br /&gt;
&lt;br /&gt;
*Wildeblood&amp;#039;s [[World Builder]] allows you to experiment with these settings in-game.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Assorted Tweaks ===&lt;br /&gt;
*[[User:Submersible|Submersible]]&amp;#039;s collection of [https://www.youtube.com/user/submersibletoaster YouTube videos] of planet textures (2012)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=5044 Question: How to add custom planet descriptions] (2008)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=217053#p217053 Tweaking your skies] (Tricky, 2014)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20959 Empty system] Removing the stations (and presumably inhabitants) from a system (2021)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=17191 Programming for Interstellar Space] (2015)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]]&lt;br /&gt;
[[Category:Oolite scripting]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Property_list&amp;diff=90362</id>
		<title>Property list</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Property_list&amp;diff=90362"/>
		<updated>2026-11-10T12:53:57Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:plist-XML-ASCII-ill.png|thumb|right|300px|the plist formats, XML and OpenStep]]&lt;br /&gt;
A &amp;#039;&amp;#039;&amp;#039;property list&amp;#039;&amp;#039;&amp;#039;, or &amp;#039;&amp;#039;&amp;#039;plist&amp;#039;&amp;#039;&amp;#039; for short, is data structured in a standardized way, used by Oolite for a wide variety of configuration files. 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. &lt;br /&gt;
&lt;br /&gt;
== Context ==&lt;br /&gt;
See [[OXP howto]] (structure) for the list of current and deprecated .plists. And also for which .plist goes into which folder inside an OXP.&lt;br /&gt;
&lt;br /&gt;
The concept originates with [http://en.wikipedia.org/wiki/OpenStep OpenStep], the specification on which the Cocoa and GNUstep programming libraries Oolite uses are based.&lt;br /&gt;
&lt;br /&gt;
Property Lists (descriptions) contrast with Scripts (instructions).&lt;br /&gt;
&lt;br /&gt;
== Formats ==&lt;br /&gt;
A property list is an abstract structure which can be represented files using at least five different formats. Since Oolite uses two different implementations of property list support, one on Mac&amp;amp;nbsp;OS&amp;amp;nbsp;X and another on other platforms, it can’t consistently read all these formats.&lt;br /&gt;
&lt;br /&gt;
Two formats are recommended for Oolite: the traditional [http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/PropertyLists/Introduction/Introduction.htmll  OpenStep format], which is easy to read, and the [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Articles/XMLPListsConcept.html XML format], which is more flexible. The other formats are Apple binary format (which can be read by both implementations, but is not human-readable), and the GNUstep text and binary formats, which are not supported under Mac&amp;amp;nbsp;OS&amp;amp;nbsp;X.&lt;br /&gt;
&lt;br /&gt;
While the OpenStep format does not support all the data types used by Oolite – specifically, it does not support [[#integer|integers]], [[#real|reals]] or [[#boolean|booleans]] – Oolite can in most cases automatically convert [[#string|strings]] to these types starting with Oolite 1.69. (If you find an exception, please report it.) As such, the types can be used interchangeably. In prior versions of Oolite, some types, especially booleans, could not be converted automatically, so XML format was required for some property lists.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Data types ==&lt;br /&gt;
The rest of this page describes the types of property list element used by Oolite, and how they are represented in OpenStep and XML format property lists. It does not cover all property list content types or file formats and is not a general-purpose reference to property lists.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== string ===&lt;br /&gt;
A string is a block of text. In OpenStep format plists, this is surrounded by straight double quotation marks, with “&amp;lt;code&amp;gt;\&amp;lt;/code&amp;gt;” being used to escape quotation marks within the string: &amp;lt;code&amp;gt;&amp;quot;a string with a \&amp;quot;quotation\&amp;quot; and a &amp;amp;lt;tag&amp;amp;gt;&amp;quot;&amp;lt;/code&amp;gt;. OpenStep format plists also allow single-word strings to be used without quotation marks when this is unambiguous. However, the definition of “unambiguous” differs between Mac&amp;amp;nbsp;OS&amp;amp;nbsp;X and GNUstep, so this usage is not recommended except for numbers. In XML format, it is surrounded by &amp;lt;code&amp;gt;&amp;amp;lt;string&amp;amp;gt;&amp;lt;/code&amp;gt; tags, escaping contents with XML entities: &amp;lt;code&amp;gt;&amp;amp;lt;string&amp;amp;gt;a string with a &amp;amp;amp;quot;quotation&amp;amp;amp;quot; and a &amp;amp;amp;lt;tag&amp;amp;amp;gt;&amp;amp;lt;/string&amp;amp;gt;&amp;lt;/code&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== integer ===&lt;br /&gt;
An integer is a whole number. In OpenStep format plists, an integer is a string whose contents happen to be digits (and optionally a minus sign), and may be unquoted: &amp;lt;code&amp;gt;-12345&amp;lt;/code&amp;gt;. In XML format, it is surrounded by &amp;lt;code&amp;gt;&amp;amp;lt;integer&amp;amp;gt;&amp;lt;/code&amp;gt; tags: &amp;lt;code&amp;gt;&amp;amp;lt;integer&amp;amp;gt;-12345&amp;amp;lt;/integer&amp;amp;gt;&amp;lt;/code&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== real ===&lt;br /&gt;
A real is a number with a fractional part. In OpenStep format plists, reals are again written as unquoted strings: &amp;lt;code&amp;gt;42.123&amp;lt;/code&amp;gt;. In XML format, reals are surrounded by &amp;amp;lt;real&amp;amp;gt; tags: &amp;lt;code&amp;gt;&amp;amp;lt;real&amp;amp;gt;42.123&amp;amp;lt;/real&amp;amp;gt;&amp;lt;/code&amp;gt;. Large reals can be expressed in scientific notation: &amp;lt;code&amp;gt;1.35e+20&amp;lt;/code&amp;gt; means 1.35 × 10&amp;lt;small&amp;gt;&amp;lt;sup&amp;gt;20&amp;lt;/sup&amp;gt;&amp;lt;/small&amp;gt;. Integers and reals are mostly interchangeable in Oolite. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== boolean ===&lt;br /&gt;
A boolean is either of the values &amp;#039;&amp;#039;true&amp;#039;&amp;#039; or &amp;#039;&amp;#039;false&amp;#039;&amp;#039;. In XML format, the tags &amp;lt;code&amp;gt;&amp;amp;lt;true/&amp;amp;gt;&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;amp;lt;false/&amp;amp;gt;&amp;lt;/code&amp;gt; can be used. OpenStep format does not support booleans. However, as of Oolite 1.69, a number of different methods can be used to represent them: any of the strings &amp;lt;code&amp;gt;&amp;quot;true&amp;quot;&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;&amp;quot;yes&amp;quot;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;quot;on&amp;quot;&amp;lt;/code&amp;gt; may be used to represent &amp;#039;&amp;#039;true&amp;#039;&amp;#039;, and any of the strings &amp;lt;code&amp;gt;&amp;quot;false&amp;quot;&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;&amp;quot;no&amp;quot;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;quot;off&amp;quot;&amp;lt;/code&amp;gt; may be used to represent &amp;#039;&amp;#039;false&amp;#039;&amp;#039;. Also the uppercase variants of these keywords can be used as casing is ignored for these booleans.  Additionally, the number 0 is interpreted as &amp;#039;&amp;#039;false&amp;#039;&amp;#039; and any other number as &amp;#039;&amp;#039;true&amp;#039;&amp;#039; (but see [[#fuzzy boolean|fuzzy boolean]] below). The recommended form is to use &amp;lt;code&amp;gt;&amp;quot;yes&amp;quot;&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;&amp;quot;no&amp;quot;&amp;lt;/code&amp;gt; to keep a consistent syntax that is not confusing.&lt;br /&gt;
&lt;br /&gt;
Previous versions of this page indicated that numbers could be used as booleans in OpenStep-format property lists in any version of Oolite. This is incorrect and such usage will not work with versions prior to 1.69.&lt;br /&gt;
&lt;br /&gt;
=== fuzzy boolean ===&lt;br /&gt;
A fuzzy boolean isn&amp;#039;t really a property list type; rather, it&amp;#039;s a special usage defined by Oolite. If a fuzzy boolean is expected, and a number is encountered, it is treated as a probability between 0 and 1. For instance, if a value of 0.5 is used, it will be treated as &amp;#039;&amp;#039;true&amp;#039;&amp;#039; half the time, and &amp;#039;&amp;#039;false&amp;#039;&amp;#039; the other half. Values other than numbers are treated like [[#boolean|booleans]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== array ===&lt;br /&gt;
An array is an ordered list of objects. &lt;br /&gt;
&lt;br /&gt;
In &amp;#039;&amp;#039;&amp;#039;OpenStep format&amp;#039;&amp;#039;&amp;#039;, an array is contained in parentheses, with items separated by commas: &amp;lt;code&amp;gt;(0, two, &amp;quot;three and a half&amp;quot;, yes)&amp;lt;/code&amp;gt;.&lt;br /&gt;
You can have several values without name, and they are grouped using round brackets:&lt;br /&gt;
&lt;br /&gt;
 (&lt;br /&gt;
 value1,&lt;br /&gt;
 value2,&lt;br /&gt;
 value3&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;Note that between two values there is a comma.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In &amp;#039;&amp;#039;&amp;#039;XML format&amp;#039;&amp;#039;&amp;#039;, it is contained in &amp;lt;code&amp;gt;&amp;amp;lt;array&amp;amp;gt;&amp;lt;/code&amp;gt; tags: &amp;lt;code&amp;gt;&amp;amp;lt;array&amp;amp;gt;&amp;amp;lt;integer&amp;amp;gt;0&amp;amp;lt;/integer&amp;amp;gt; &amp;amp;lt;string&amp;amp;gt;two&amp;amp;lt;/string&amp;amp;gt; &amp;amp;lt;string&amp;amp;gt;three and a half&amp;amp;lt;/string&amp;amp;gt; &amp;amp;lt;true/&amp;amp;gt;&amp;amp;lt;/array&amp;amp;gt;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Later the values are just accessed by numbers: The first, the second, the next, the last, ...&lt;br /&gt;
&lt;br /&gt;
Now the part that can make plist files really complex: Wherever you place a value, it can be a primitive one (a number, a string, a boolean value like true/false) or a complex value such as an array or a dictionary. And with this you can create all the complex structures you perceive when looking at Oolite&amp;#039;s plist files.&lt;br /&gt;
&lt;br /&gt;
=== dictionary ===&lt;br /&gt;
Dictionaries are the most complex type. They consist of key/value pairs – each pair consists of a key, which is always a string, and a value, which can be any type, including other dictionaries. Each key must be unique, and the order of pairs is not significant. Again, every value has a name or a key.&lt;br /&gt;
&lt;br /&gt;
In &amp;#039;&amp;#039;&amp;#039;OpenStep format&amp;#039;&amp;#039;&amp;#039;, dictionaries are contained in braces, with key and value separated by &amp;lt;code&amp;gt;=&amp;lt;/code&amp;gt; signs and each pair followed by a semicolon: &lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   &amp;quot;name1&amp;quot; = &amp;quot;value1&amp;quot;;&lt;br /&gt;
   &amp;quot;name2&amp;quot; = &amp;quot;value2&amp;quot;;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Not all names have to go into quotes, and not all values require them. But you need to watch out where you place them and where not.&lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   length = 42;&lt;br /&gt;
   width = 36.5;&lt;br /&gt;
   &amp;quot;long name&amp;quot; = &amp;quot;this is a thing with a really quite long name&amp;quot;; // &amp;#039;&amp;#039;note: quotes for a key with spaces are required&amp;#039;&amp;#039;&lt;br /&gt;
   attributes = (&amp;quot;hairy&amp;quot;, &amp;quot;muscular&amp;quot;); // &amp;#039;&amp;#039;note: this is actually an &amp;#039;&amp;#039;&amp;#039;array&amp;#039;&amp;#039;&amp;#039; of string values following the key&amp;#039;&amp;#039;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
Use &amp;lt;code&amp;gt; tag if you need to mark elements of code/markup within plain text, such as function or variable names, types, literals, tags etc.&lt;br /&gt;
and &amp;lt;pre&amp;gt; tag or space at the beginning of the line (which also results in an implicit &amp;lt;pre&amp;gt; tag) if you need to mark block of code/markup - &lt;br /&gt;
several or even one line of code that &amp;quot;do something&amp;quot; beside &amp;quot;exist&amp;quot;: declare some object (equipment, function, missiontext entry), specify some value for the property, call js function etc.&lt;br /&gt;
&lt;br /&gt;
Note: This, of course, is a general recommendation, not a rule - if you know that in this particular case is better to do differently - go for it.&lt;br /&gt;
Also, it would probably be better to put it somewhere else, but I&amp;#039;m not sure where it would fit.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
In &amp;#039;&amp;#039;&amp;#039;XML format&amp;#039;&amp;#039;&amp;#039;, dictionaries are contained in &lt;br /&gt;
&amp;lt;code&amp;gt;&amp;amp;lt;dict&amp;amp;gt;&amp;lt;/code&amp;gt; tags,&amp;lt;/br&amp;gt;&lt;br /&gt;
with keys specified by &amp;lt;code&amp;gt;&amp;amp;lt;key&amp;amp;gt;&amp;lt;/code&amp;gt; tags &amp;lt;/br&amp;gt;&lt;br /&gt;
and immediately followed by values with whatever tag is appropriate for the value type: &lt;br /&gt;
 &amp;amp;lt;dict&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;key&amp;amp;gt;length&amp;amp;lt;/key&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;integer&amp;amp;gt;42&amp;amp;lt;/integer&amp;amp;gt; &lt;br /&gt;
   &amp;amp;lt;key&amp;amp;gt;width&amp;amp;lt;/key&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;real&amp;amp;gt;36.5&amp;amp;lt;/real&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;key&amp;amp;gt;long name&amp;amp;lt;/key&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;string&amp;amp;gt;this is a thing with a really quite long name&amp;amp;lt;/string&amp;amp;gt;  &lt;br /&gt;
   &amp;amp;lt;key&amp;amp;gt;attributes&amp;amp;lt;/key&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;array&amp;amp;gt;&lt;br /&gt;
     &amp;amp;lt;string&amp;amp;gt;hairy&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
     &amp;amp;lt;string&amp;amp;gt;muscular&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
   &amp;amp;lt;/array&amp;amp;gt;  &lt;br /&gt;
 &amp;amp;lt;/dict&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Root element ==&lt;br /&gt;
Every property list has a single value as its root. Typically this is a dictionary. In XML format, the root value must be surrounded by &amp;lt;code&amp;gt;&amp;amp;lt;plist&amp;amp;gt;&amp;lt;/code&amp;gt; tags in addition to its normal type tag: &amp;lt;code&amp;gt;&amp;amp;lt;plist&amp;amp;gt; &amp;amp;lt;dictionary&amp;amp;gt; &amp;amp;lt;key&amp;amp;gt;green&amp;amp;lt;/key&amp;amp;gt; &amp;amp;lt;array&amp;amp;gt; &amp;amp;lt;integer&amp;amp;gt;0&amp;amp;lt;/integer&amp;amp;gt; &amp;amp;lt;integer&amp;amp;gt;1&amp;amp;lt;/integer&amp;amp;gt; &amp;amp;lt;integer&amp;amp;gt;0&amp;amp;lt;/integer&amp;amp;gt; &amp;amp;lt;/array&amp;amp;gt; &amp;amp;lt;/dictionary&amp;amp;gt; &amp;amp;lt;/plist&amp;amp;gt;&amp;lt;/code&amp;gt; (OpenStep equivalent: &amp;lt;code&amp;gt;{ green = (0, 1, 0); }&amp;lt;/code&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
Under Mac&amp;amp;nbsp;OS&amp;amp;nbsp;X, if the root element of an OpenStep-format property list is a dictionary, it does not have to be surrounded by braces. However, &amp;#039;&amp;#039;this does not work under GNUstep&amp;#039;&amp;#039;, so those creating property lists on Macs must be careful. In particular, OpenStep-format property lists exported by Property List Editor may not work under GNUstep.&lt;br /&gt;
&lt;br /&gt;
== Comments ==&lt;br /&gt;
Both formats can also contain comments, which are ignored by the program but are useful to human readers. In OpenStep format, these can either start with “&amp;lt;code&amp;gt;//&amp;lt;/code&amp;gt;” and continue to the end of the line, or start with “&amp;lt;code&amp;gt;/*&amp;lt;/code&amp;gt;” and end with “&amp;lt;code&amp;gt;*/&amp;lt;/code&amp;gt;”. In XML, they start with “&amp;lt;code&amp;gt;&amp;amp;lt;!--&amp;lt;/code&amp;gt;” and end with “&amp;lt;code&amp;gt;--&amp;amp;gt;&amp;lt;/code&amp;gt;” (and must not contain “&amp;lt;code&amp;gt;--&amp;lt;/code&amp;gt;” anywhere else in the comment). &lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
 /* this line is a comment in OpenStep format */&lt;br /&gt;
 // this line is also a comment in OpenStep format&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;amp;lt;!-- this line is a comment in XML --&amp;amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== XML Preamble ==&lt;br /&gt;
XML plists also need a standard header, which looks like this:&lt;br /&gt;
 &amp;amp;lt;?xml version=&amp;quot;1.0&amp;quot; encoding=&amp;quot;UTF-8&amp;quot;?&amp;amp;gt; &lt;br /&gt;
 &amp;amp;lt;!DOCTYPE plist PUBLIC &amp;quot;-//Apple Computer//DTD PLIST 1.0//EN&amp;quot; &amp;quot;&amp;lt;nowiki&amp;gt;http://www.apple.com/DTDs/PropertyList-1.0.dtd&amp;lt;/nowiki&amp;gt;&amp;quot;&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Real-world Example ==&lt;br /&gt;
The following is a shortened version of Oolite’s built-in &amp;#039;&amp;#039;[[equipment.plist]]&amp;#039;&amp;#039;, in both OpenStep and XML formats.&lt;br /&gt;
&lt;br /&gt;
=== OpenStep ===&lt;br /&gt;
 (&lt;br /&gt;
     (&lt;br /&gt;
         1, 300, &amp;quot;Missile&amp;quot;, &amp;quot;EQ_MISSILE&amp;quot;,&lt;br /&gt;
         &amp;quot;Faulcon de Lacy HM3 homing missile, fast and accurate when used in conjunction with standard targetting scanners.&amp;quot;,&lt;br /&gt;
         {&lt;br /&gt;
             available_to_all = &amp;quot;yes&amp;quot;;&lt;br /&gt;
         }&lt;br /&gt;
     ),&lt;br /&gt;
     (&lt;br /&gt;
         7, 9000, &amp;quot;Energy Bomb&amp;quot;, &amp;quot;EQ_ENERGY_BOMB&amp;quot;,&lt;br /&gt;
         &amp;quot;A one-shot super-weapon capable of destroying all small craft within range.&amp;quot;&lt;br /&gt;
     )&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
The round brackets are arrays in OpenStep, and are used to group information for a given key. Examples are the exhaust (if one has multiple ones for a given ship), the individual custom views and sub-entities...&lt;br /&gt;
&lt;br /&gt;
The curly brackets make up dictionaries, which tie together different keys on the same subject. The two main examples there are the overall entries themselves (each ship is made up of a dictionary of keys describing it) and the external views (a dictionary of individual views, each of which is defined as an array of keys describing that given view).&lt;br /&gt;
&lt;br /&gt;
One would recommend using a programmer-friendly editor like notepad++ or an equivalent. On N++ if you select an open or closing bracket (of whichever flavour) it will automatically highlight the other part of the pair and link them. It&amp;#039;s useful for quickly checking that you have your pairs correct - a good habit to get into. And in many cases the kind of log error one sees is indicative of missing brackets. Those and missing quotes and semi-colons are arguably the three most common errors in openStep plists if one excludes typo&amp;#039;s. [https://bb.oolite.space/viewtopic.php?p=153556#p153556 Thargoid] (2011)&lt;br /&gt;
&lt;br /&gt;
=== XML ===&lt;br /&gt;
 &amp;amp;lt;?xml version=&amp;quot;1.0&amp;quot; encoding=&amp;quot;UTF-8&amp;quot;?&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!DOCTYPE plist PUBLIC &amp;quot;-//Apple Computer//DTD PLIST 1.0//EN&amp;quot; &amp;lt;nowiki&amp;gt;&amp;quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&amp;quot;&amp;lt;/nowiki&amp;gt;&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;plist version=&amp;quot;1.0&amp;quot;&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;array&amp;amp;gt;&lt;br /&gt;
     &amp;amp;lt;array&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;integer&amp;amp;gt;1&amp;amp;lt;/integer&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;integer&amp;amp;gt;300&amp;amp;lt;/integer&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;string&amp;amp;gt;Missile&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;string&amp;amp;gt;EQ_MISSILE&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;string&amp;amp;gt;Faulcon de Lacy HM3 homing missile, fast and accurate when used in conjunction with&lt;br /&gt;
                 standard targetting scanners.&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;dict&amp;amp;gt;&lt;br /&gt;
             &amp;amp;lt;key&amp;amp;gt;available_to_all&amp;amp;lt;/key&amp;amp;gt;&lt;br /&gt;
             &amp;amp;lt;true/&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;/dict&amp;amp;gt;&lt;br /&gt;
     &amp;amp;lt;/array&amp;amp;gt;&lt;br /&gt;
     &amp;amp;lt;array&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;integer&amp;amp;gt;7&amp;amp;lt;/integer&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;integer&amp;amp;gt;9000&amp;amp;lt;/integer&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;string&amp;amp;gt;Energy Bomb&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;string&amp;amp;gt;EQ_ENERGY_BOMB&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
         &amp;amp;lt;string&amp;amp;gt;A one-shot super-weapon capable of destroying all small craft within range.&amp;amp;lt;/string&amp;amp;gt;&lt;br /&gt;
     &amp;amp;lt;/array&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;/array&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;/plist&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conversion ==&lt;br /&gt;
Technically the XML plists are the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. However, those editors are only easily available for the Mac. Windows and Linux users will have to rely on text editors to edit those plists. Therefore it is advised to write everything in open step format.&lt;br /&gt;
&lt;br /&gt;
Converting xml to open step can be done by a python script, written by Cdr. Jettison: [http://www.box.net/shared/g79rnfx4jcp1do35liin download python conversion script] (&amp;#039;&amp;#039; xml plist must be free of comment for the script to work&amp;#039;&amp;#039;)&lt;br /&gt;
&lt;br /&gt;
Note that this conversion script contains CR/LF (carriage return/linefeed) end-of-lines, as used on Windows computers. This will cause &amp;#039;&amp;#039;&amp;quot;bad interpreter: No such file or directory&amp;quot;&amp;#039;&amp;#039; errors if run on Linux. You can strip out the CR characters yourself, or download this [https://www.box.com/s/n06cixgjxsxmph2drucz copy of the script which has already had the CRs removed]. (you will also need to make the script executable)&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=10039 BB discussion] about converting plists (2011-21)&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=6836 earlier conversion discussion] (2009)&lt;br /&gt;
* [[OXP howto]]&lt;br /&gt;
* [[OXP howto plist]] has a section on finding and fixing errors&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?t=6301 Oolite in French] (2009) - handling diacritical signs on letters&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=10949 Property List problems] (2011) - mostly XML, some OpenStep&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=13442 Clobbering order for AddOns .plist keys] (2013: Is there a defined or predictable order in which plists &amp;#039;&amp;#039;eg&amp;#039;&amp;#039; planetinfo.plist are applied and hence can be clobbered by another plist?)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]]&lt;br /&gt;
[[Category:Legacy scripting]]&lt;br /&gt;
[[Category:Oolite scripting]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Cloud_City_OXP&amp;diff=90361</id>
		<title>Cloud City OXP</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Cloud_City_OXP&amp;diff=90361"/>
		<updated>2026-11-09T18:15:51Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note at top- and then download details for Krager&amp;#039;s 2026 version&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Cloud Cities.png|right|800px]]&lt;br /&gt;
[[File:Cloud City close-up.png|right|800px]]&lt;br /&gt;
This OXP has been recently updated by Krager (June 2026).&lt;br /&gt;
== Overview ==&lt;br /&gt;
Some eye-candy showing Cloud cities at each main planet (eventually) destined for some future gas giants, Population of each one a few million.&lt;br /&gt;
It is possible to fly under a Cloud city without blowing up, but not easy. Also they are (fairly) easy to destroy (immoral but fun).&lt;br /&gt;
There is even a black-coloured Cloud city at each home planet to give a visual throw-back to how Cloud Cities could have looked like in original Elite.&lt;br /&gt;
&lt;br /&gt;
Note: No docking nor landing capability exists, your ship will be destroyed if you approach too close!&lt;br /&gt;
&lt;br /&gt;
 &amp;#039;&amp;#039;&amp;#039;Disclaimer, wish-list:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 This is a work in progress with coding help needed (landing, docking &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.), or is its present state a &amp;#039;feature&amp;#039; ... &lt;br /&gt;
 &amp;quot;Cloud cities not visitable unless visitor registered&amp;quot; ?&lt;br /&gt;
 Fix some issues like why subentities on cloud cities (flashers &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.) sometimes don&amp;#039;t appear?&lt;br /&gt;
 Improvements to textures, model, invited. The OXP models folder also contains the wings3D raw model file.&lt;br /&gt;
 Atmosphere of main planets not thick enough to encapsulate whole city, but not really a problem.&lt;br /&gt;
 Hope to have some exhaust plumes firing out of the bottom to levitate the city, but the &amp;#039;craft&amp;#039; is not moving.&lt;br /&gt;
 The craft are following a local latitude, longitude placement scheme, but not rotating with planet yet.&lt;br /&gt;
&lt;br /&gt;
See BB Thread: [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=5932 Cloud City OXP] (2009)&lt;br /&gt;
&lt;br /&gt;
=== Musings ===&lt;br /&gt;
*1) The aesthetics no longer work with modern Oolite - either the Griffian version in the Vanilla Game or Murgh&amp;#039;s [[Iron Ass OXP|Low Poly alternatives]]. There is a free model at [https://www.solcommand.com/ SolCommand] of a &amp;quot;Venusian Aerostat&amp;quot; - but it might not have a dock - and might need resizing due to Oolite&amp;#039;s planets being [[Distance (Oolite)|too small]].&lt;br /&gt;
*2) The docking needs work. It can be solved either by adding a dock to the model [[OXP howto dockable stations|along the z-axis]] or by adding [[External Docking System|external docking]]. Docking will be made more interesting by [[Planetfall2 OXP]] if below 5km altitude!&lt;br /&gt;
*3) With Oolite v.1.92, we can now define [https://oolite.space/#v192sub2 atmosphere colour/density] &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. to add to the immersion.&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
* [http://app.box.net/shared/exyinqm9me Download] (Dr Beeb&amp;#039;s original - wonky markets, appears at &amp;#039;&amp;#039;all&amp;#039;&amp;#039; main planets, especially non-gas giants!&lt;br /&gt;
* Krager&amp;#039;s update: [https://cloud.mail.ru/public/Twxm/MQpTpiBck/ОБМЕННИК/RUS_CloudCity%20v0.5%20mod.oxz RUS_CloudCity] (13th June, 2026)&lt;br /&gt;
:What has been done (translated from Krager&amp;#039;s Russian):&lt;br /&gt;
::1. Docking now works at all cloud cities.&lt;br /&gt;
::2. The airlock is turned towards space.&lt;br /&gt;
::3. Added marketplaces with a range of prices (requires [[Market Script Interface]] OXP).&lt;br /&gt;
::4. Added patrols and strong defenders (optionally - [[Snark]] is needed).&lt;br /&gt;
::5. Added trade in equipment and ships.&lt;br /&gt;
::6. Added reaction to nearby battle, should save the player (did not check).&lt;br /&gt;
::7. Shifted from the station by 180 degrees. &lt;br /&gt;
::8. Appears at the gas giants from the [[Additional Planets]] OXP suite&lt;br /&gt;
* Note: this is an OXP not an OXZ. It needs to go in your AddOns folder (See [[OXP]] for details).&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
There seems to be no license in the package.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
* [[User:DrBeeb|DrBeeb]] (Author)&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=5932 BB Thread] (2009)&lt;br /&gt;
* [[Zarece (Rough Guide)]] has a description of cloud cities&lt;br /&gt;
&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?p=275950#p275950 Half-a-dozen stunning screen shots] by cbr (2021)&lt;br /&gt;
[[File:Tag-colour-green.png]]{{OXPLevel|0}}&lt;br /&gt;
&lt;br /&gt;
{{Ambience-OXP}}&lt;br /&gt;
{{demo-OXP}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=OXP_howto&amp;diff=90360</id>
		<title>OXP howto</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=OXP_howto&amp;diff=90360"/>
		<updated>2026-11-09T11:17:13Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note on using AI&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:&amp;#039;&amp;#039;Shortcut: EW:OXP and EW:HOWDS redirect here&amp;#039;&amp;#039;&amp;lt;/br&amp;gt;&lt;br /&gt;
[[Image:oolite-oxp-icon.png|100px|thumb|right|OXP icon]]&lt;br /&gt;
[[File:Oolite-debug-menu.png|thumb|right|Debug Menu  (From the AppleMac variety of the &amp;quot;Oolite TR&amp;quot; version)]]&lt;br /&gt;
==Overview==&lt;br /&gt;
An &amp;#039;&amp;#039;&amp;#039;Oolite Expansion Pack&amp;#039;&amp;#039;&amp;#039; can cause many big changes or additions to Oolite&amp;#039;s gameplay, or it may represent just a small, subtle alteration. By first appearances, there is no way to tell what is inside, as it&amp;#039;s merely a &amp;#039;&amp;#039;folder&amp;#039;&amp;#039; with the added extension &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
Oolite Version 1.79 onwards supports also compressed files in ZIP format with extension &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039;. &lt;br /&gt;
&lt;br /&gt;
To learn starting with a non-compressed version have a look at [[OXP_tutorial]].&lt;br /&gt;
&lt;br /&gt;
{{QuoteText|Text=It&amp;#039;s worth saying I think that compared with a lot of game addon architectures, the OXP architecture as designed by Giles is already very good at avoiding conflicts compared with a lot of other games&lt;br /&gt;
- you can save your game, add, remove and upgrade lots of OXPs, load your game, and have it work&lt;br /&gt;
- you can do this repeatedly, while incrementally upgrading the core game, for years&lt;br /&gt;
- as a player you basically never have to care about load order; as an OXP developer, rarely&lt;br /&gt;
&lt;br /&gt;
It&amp;#039;s also worth noting that a lot of types of OXP conflicts are inevitable due to resource conflicts - a planet can only have one diffuse map, a ship can only have one AI - or due to conceptual conflicts - OXP A removes all stations from a system; OXP B expects the player to dock there.|Source=([https://bb.oolite.space/viewtopic.php?p=241733#p241733 Cim (3rd Lead Developer)])}}&lt;br /&gt;
&lt;br /&gt;
=== Oolite TR version ===&lt;br /&gt;
The Oolite Developer Release/Test Release version is specially developed for testing out OXPs. It comes with a [[Debug OXP]]/Debug Console allowing one to spawn ships/station on demand, award oneself a test ship, detect the mass of another ship &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
It is downloaded from the main Oolite website - currently http://www.oolite.space/download/&lt;br /&gt;
&lt;br /&gt;
== OXZ ==&lt;br /&gt;
The new OXZ distribution format is strongly recommended. It makes version control and distribution just so much easier.&lt;br /&gt;
&lt;br /&gt;
To make an OXZ file, use a ZIP program to compress the contents of the OXP folder, so that the [[manifest.plist]] file is in the root of the ZIP file, and the folders (AI, Config, etc) are folders in the ZIP file. Then, rename the ZIP file so that its extension is &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039;. To inspect an OXZ file, open it with your ZIP program.&lt;br /&gt;
&lt;br /&gt;
Here is a sample: [[Media:X.0.1.oxz]] - just rename all &amp;quot;X&amp;quot; within to the title of your idea and put your name into the author fields. &lt;br /&gt;
&lt;br /&gt;
You can use [http://www.ghisler.com/download.htm Total Commander] or [http://en.wikipedia.org/wiki/Krusader Krusader] to edit files within &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039; directly, without unpacking.&lt;br /&gt;
&lt;br /&gt;
For more details read [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16688 The All-in-One Guide to OXZ Packaging and Distribution].&lt;br /&gt;
&lt;br /&gt;
=== Creating an .oxz on an AppleMac ===&lt;br /&gt;
When you compress the files/folders on the AppleMac to create the .oxz &amp;#039;&amp;#039;do not&amp;#039;&amp;#039; select them with your mouse! This way lies misery!&lt;br /&gt;
&lt;br /&gt;
Rather, ensure the relevant files/folders are inside one overall folder. Then, use &amp;#039;&amp;#039;&amp;#039;command-a&amp;#039;&amp;#039;&amp;#039; to select all the &amp;#039;&amp;#039;contents&amp;#039;&amp;#039; of this overall folder and then select &amp;#039;&amp;#039;&amp;#039;compress&amp;#039;&amp;#039;&amp;#039; from the file menu on the finder&amp;#039;s menu bar. Finally, rename your newly-created .zip file as an .oxz&lt;br /&gt;
&lt;br /&gt;
==Structure==&lt;br /&gt;
Inside the &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039; folder, or the &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039; file, 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&amp;#039;s contents. To get a feeling for it, simply take a look in other oxps. (If they are in .oxz format, any normal unzip program can inspect their contents - many will even let you edit the contents without having to unzip and rezip the file)&lt;br /&gt;
&lt;br /&gt;
The structure for OXPs:&lt;br /&gt;
 AddOns (folder)&lt;br /&gt;
 ~.oxp (really just another folder!) - Holds manifest.plist and the other folders:&lt;br /&gt;
 &lt;br /&gt;
 --&amp;gt; AIs (folder) - Holds AI plists&lt;br /&gt;
 --&amp;gt; Config (folder) - Holds all other plists (and possibly an anonymous &amp;quot;Script.js&amp;quot;)&lt;br /&gt;
 --&amp;gt; Images (folder) - Holds background images&lt;br /&gt;
 --&amp;gt; Models (folder) - Holds the .dat files (special Oolite format)&lt;br /&gt;
 --&amp;gt; Music (folder) - Surprise - holds .ogg music files&lt;br /&gt;
 --&amp;gt; Scenarios (folder) - Holds new game scenarios (v1.79)&lt;br /&gt;
 --&amp;gt; Scripts (folder) - Holds scripts (worldScripts and shipScripts)&lt;br /&gt;
 --&amp;gt; Shaders (folder) - Holds Vertex and Fragment shaders (v1.69)&lt;br /&gt;
 --&amp;gt; Sounds (folder) - Holds sound files&lt;br /&gt;
 --&amp;gt; Textures (folder) - Holds models textures (can be planets, too!)&lt;br /&gt;
 --&amp;gt; [[manifest.plist]] (file) &lt;br /&gt;
     &amp;#039;&amp;#039;the following might also be found in here:&amp;#039;&amp;#039;&lt;br /&gt;
 --&amp;gt; [[Misc plists|info.plist]] (file, seems to be a poor duplicate of the Manifest.plist)&lt;br /&gt;
 --&amp;gt; [[Requires.plist]] (file: deprecated - replaced by Manifest.plist)&lt;br /&gt;
&lt;br /&gt;
*If the OXP is in the uncompressed OXP folder format, the .oxp folder must contain a [[requires.plist]] file. If it is in the compressed OXZ single-file format, it must contain a [[manifest.plist]] file.&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=13134 Nested OXPs in AddOns folder] (2012) - some OXZ&amp;#039;s do this (Station spotter oxp inside [[Stations for Extra Planets]]) &lt;br /&gt;
&lt;br /&gt;
===AIs folder===&lt;br /&gt;
The folder named AIs contains any AI.plist additions the OXP might use. &lt;br /&gt;
&lt;br /&gt;
* [[OXP howto AI|Making Oolite AI]]&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.79 AIs may be written in Javascript using .js files in this folder. A helper library is provided to make writing complex JS AIs simpler.&lt;br /&gt;
&lt;br /&gt;
* [[Oolite PriorityAI Documentation]]&lt;br /&gt;
* [[Oolite PriorityAI Tutorial]]&lt;br /&gt;
&lt;br /&gt;
===Config folder===&lt;br /&gt;
All plist files except for those introducing new AIs, &amp;#039;&amp;#039;[[requires.plist]]&amp;#039;&amp;#039;, &amp;#039;&amp;#039;[[manifest.plist]]&amp;#039;&amp;#039; or &amp;#039;&amp;#039;[[Misc plists|info.plist]]&amp;#039;&amp;#039;, belong in Config.&lt;br /&gt;
&lt;br /&gt;
In its simplest form, an OXP could contain only a Config with an altering &amp;#039;&amp;#039;script.plist&amp;#039;&amp;#039; or &amp;#039;&amp;#039;planetinfo.plist&amp;#039;&amp;#039;.  An OXP that adds a new ship needs a &amp;#039;&amp;#039;shipdata.plist&amp;#039;&amp;#039; entry, and unless it is based entirely on existing Oolite data, would include a model and texture. &lt;br /&gt;
&lt;br /&gt;
* [[OXP howto plist|Making Oolite plists]]&lt;br /&gt;
* Usually irrelevant: The Config folder isn&amp;#039;t cached in the same way as the rest of an oxp because usually its contents merge rather than overwriting (See [https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=16927 here])&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This folder contains [[Property lists]] such as:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;[[characters.plist]]&amp;#039;&amp;#039; that adds non-player characters to Oolite.&lt;br /&gt;
* &amp;#039;&amp;#039;[[crosshairs.plist]]&amp;#039;&amp;#039; that contains the look for your weapons (v1.73).&lt;br /&gt;
* &amp;#039;&amp;#039;[[customsounds.plist]]&amp;#039;&amp;#039; that contains references to ingame used sounds.&lt;br /&gt;
* &amp;#039;&amp;#039;[[descriptions.plist]]&amp;#039;&amp;#039; that adds vocabulary to Oolite texts.&lt;br /&gt;
* &amp;#039;&amp;#039;[[effectdata.plist]]&amp;#039;&amp;#039; defines custom visual effects (v1.77).&lt;br /&gt;
* &amp;#039;&amp;#039;[[equipment.plist]]&amp;#039;&amp;#039; lists upgrades available from the Shipyard.&lt;br /&gt;
* &amp;#039;&amp;#039;[[explosions.plist]]&amp;#039;&amp;#039; customises things blowing up (v1.81)&lt;br /&gt;
* &amp;#039;&amp;#039;[[global-settings.plist]]&amp;#039;&amp;#039; sets a few miscellaneous universal settings (v1.81)&lt;br /&gt;
* &amp;#039;&amp;#039;[[gui-settings.plist]]&amp;#039;&amp;#039; settings for reformatting the GUI screens (v1.81)&lt;br /&gt;
* &amp;#039;&amp;#039;[[hud.plist]]&amp;#039;&amp;#039; and &amp;#039;&amp;#039;[[hud.plist|hud-small.plist]]&amp;#039;&amp;#039; that allows for changes or a radically new &amp;#039;&amp;#039;Head-Up Display&amp;#039;&amp;#039;.&lt;br /&gt;
* &amp;#039;&amp;#039;[[Oolite_Keyboard_Controls|keyconfig2.plist]]&amp;#039;&amp;#039; that allows for changes of the keymapping.&lt;br /&gt;
* &amp;#039;&amp;#039;[[missiontext.plist]]&amp;#039;&amp;#039; contains texts for the mission screens.&lt;br /&gt;
* &amp;#039;&amp;#039;[[OXPMessages.plist]]&amp;#039;&amp;#039; adds warnings to testversions of an oxp.&lt;br /&gt;
* &amp;#039;&amp;#039;[[planetinfo.plist]]&amp;#039;&amp;#039; that plots system specific changes from the default. May also contain &amp;#039;&amp;#039;script actions&amp;#039;&amp;#039;.&lt;br /&gt;
* &amp;#039;&amp;#039;[[role-categories.plist]]&amp;#039;&amp;#039; for specifying groups of roles (&amp;#039;&amp;#039;eg&amp;#039;&amp;#039;.: trader, Miner, pirate &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.) with similar properties (v1.79)&lt;br /&gt;
* &amp;#039;&amp;#039;[[scenarios.plist]]&amp;#039;&amp;#039; lists the starting scenarios in the Scenarios folder (v1.79).&lt;br /&gt;
* &amp;#039;&amp;#039;[[screenbackgrounds.plist]]&amp;#039;&amp;#039; that contains references to background images (v1.74).&lt;br /&gt;
* &amp;#039;&amp;#039;[[Scripting Oolite with JavaScript|script.js]]&amp;#039;&amp;#039; is the successor of [[script.plist]] in JavaScript.It will be loaded in preference to script.plist if both exist.&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipdata.plist]]&amp;#039;&amp;#039; that introduces any new entity (ships, stations, objects etc.) to Oolite.&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipdata-overrides.plist]]&amp;#039;&amp;#039; that selectively can replace shipentries in other shipdata.plists&lt;br /&gt;
* &amp;#039;&amp;#039;[[shiplibrary.plist]]&amp;#039;&amp;#039; that gives information for the ship description library viewable from the startup screen (v1.79)&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipyard.plist]]&amp;#039;&amp;#039; that introduces new ships available for player purchase.&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipyard-overrides.plist]]&amp;#039;&amp;#039; that selectively can replace shipentries in other shipyard.plists&lt;br /&gt;
* &amp;#039;&amp;#039;[[speech_pronunciation_guide.plist]]&amp;#039;&amp;#039; is another of the other custom methods.&lt;br /&gt;
* &amp;#039;&amp;#039;[[trade-goods.plist]]&amp;#039;&amp;#039; defines trade goods in 1.81 and later&lt;br /&gt;
* &amp;#039;&amp;#039;[[world-scripts.plist]]&amp;#039;&amp;#039; that contains a list of scripts (if more than one worldScript should be used).&lt;br /&gt;
&lt;br /&gt;
Deprecated:&lt;br /&gt;
* &amp;#039;&amp;#039;[[commodities.plist]]&amp;#039;&amp;#039; that contains information for each commodity in a market in 1.80 or earlier&lt;br /&gt;
* &amp;#039;&amp;#039;[[demoships.plist]]&amp;#039;&amp;#039; that selects demoships to show on startup (replaced - approximately - by shiplibrary.plist in 1.79 and later)&lt;br /&gt;
* &amp;#039;&amp;#039;[[illegal_goods.plist]]&amp;#039;&amp;#039; that contains a list of banned/forbidden items in 1.80 or earlier. GalCop has an eye on that.&lt;br /&gt;
* &amp;#039;&amp;#039;[[Oolite_Keyboard_Controls|keyconfig.plist]]&amp;#039;&amp;#039; that allows for changes of the keymapping. (deprecated in v1.92)&lt;br /&gt;
* &amp;#039;&amp;#039;[[pirate-victim-roles.plist]]&amp;#039;&amp;#039; that defines which roles should act as traders. (deprecated in v1.79)&lt;br /&gt;
* &amp;#039;&amp;#039;[[script.plist]]&amp;#039;&amp;#039; to handle conditional &amp;#039;&amp;#039;script actions&amp;#039;&amp;#039;. (deprecated)&lt;br /&gt;
* &amp;#039;&amp;#039;[[script.oos]]&amp;#039;&amp;#039; was briefly introduced during 1.70 development but is now deprecated in favour of JS.)&lt;br /&gt;
&lt;br /&gt;
=== Models folder===&lt;br /&gt;
Oolite models need to be in an Oolite specific format using the the &amp;#039;&amp;#039;&amp;#039;.dat&amp;#039;&amp;#039;&amp;#039; file extension. 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&amp;#039;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 &amp;#039;&amp;#039;model&amp;#039;&amp;#039; entry - case sensitive!!!&lt;br /&gt;
&lt;br /&gt;
* [[OXP howto model|Making Oolite models]] - tutorials for Wings3D &amp;amp; Blender, notes on sub-entities, links &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12165 Model Converter utilities] (2012-17)&lt;br /&gt;
* Video: [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16123 From scratch to Mamba in under an hour] ([[Dertien]], 2013)&lt;br /&gt;
&lt;br /&gt;
===Scripts folder===&lt;br /&gt;
Scripts are in text format. In this folder you can put both JavaScript scripts as well as legacy scripts. New OXPs should only use JavaScript here.&lt;br /&gt;
* [[Scripting_Oolite_with_JavaScript|Scripting Oolite with Javascript]]&lt;br /&gt;
* [[Oolite_JavaScript_object_model|Scripting reference]]&lt;br /&gt;
&lt;br /&gt;
===Textures folder===&lt;br /&gt;
&lt;br /&gt;
Oolite&amp;#039;s textures are in the &amp;#039;&amp;#039;&amp;#039;.png&amp;#039;&amp;#039;&amp;#039; format, usually at a standard 512x512 size, and must be named exactly as they are named in the .dat file. &lt;br /&gt;
&lt;br /&gt;
* [[OXP howto texture|Making Oolite textures]]&lt;br /&gt;
&lt;br /&gt;
* [[Smivs&amp;#039;_texture_tutorial|Smivs&amp;#039; guide to making Oolite textures]]&lt;br /&gt;
&lt;br /&gt;
* [[Texturing tips and tricks by Theta Seven]]&lt;br /&gt;
&lt;br /&gt;
Viewing a specific texture and / or model in Oolite.&lt;br /&gt;
&amp;quot;I made one. How do I proof it?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
* [[Viewing a Texture or Model]]&lt;br /&gt;
&lt;br /&gt;
==Tool: OXP Verifier==&lt;br /&gt;
&lt;br /&gt;
Oolite has what amounts to a spell checker for shipdata.plist and some other plists, called the OXP verifier. &lt;br /&gt;
&lt;br /&gt;
*It does not work with OXZ&amp;#039;s (so convert your OXP&amp;#039;s to OXZ&amp;#039;s later!).&lt;br /&gt;
*Nor does it work on the standard game release version of Oolite (v.1.90, v.1.92 &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;). Only on the Test Release/Developer&amp;#039;s Release version &amp;#039;&amp;#039;and&amp;#039;&amp;#039; on the Nightlies/Pre-Releases (v.1.91, v.1.93 &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.)&lt;br /&gt;
&lt;br /&gt;
The verifier detects unknown keys or wrong use of keys &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. It can currently only be invoked from the command line. &lt;br /&gt;
&lt;br /&gt;
On Windows or Linux: &lt;br /&gt;
Code: &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;oolite.app/oolite --verify-oxp &amp;lt;path to OXP&amp;gt; &amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
On Mac OS X: &lt;br /&gt;
Code: &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Oolite.app/Contents/MacOS/Oolite --verify-oxp &amp;lt;path to OXP&amp;gt;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Most Mac users will not be familiar with using the command line. Look inside your application folder for a &amp;#039;&amp;#039;&amp;#039;utilities folder&amp;#039;&amp;#039;&amp;#039;. Inside that you will find a program called [https://en.wikipedia.org/wiki/Terminal_(macOS) Terminal]. &amp;lt;br&amp;gt;&lt;br /&gt;
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: &amp;quot;/Contents/MacOS/Oolite --verify-oxp &amp;quot;.  Now drop the oxp you want to verify on the window. That will again create the path to the oxp behind the last entry. &amp;lt;br&amp;gt;&lt;br /&gt;
When you select the window and hit the &amp;lt;return&amp;gt; key, the verification will start. It should now open the Console program, showing the results. &amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Console&amp;#039;&amp;#039;&amp;#039; is a log viewer developed by Apple Inc. and included with macOS, also in the utilities folder. It allows users to search through all of the system&amp;#039;s logged messages, and can alert the user when certain types of messages are logged. The Console is generally used for troubleshooting when there is a problem with the computer. MacOS itself, as well as any applications that are used, send a constant stream of messages to the system in the form of log files. The console allows you to read the system logs, help find certain ones, monitor them, and filter their contents. See [[Debug OXP]] for more information.&lt;br /&gt;
&lt;br /&gt;
There is a lengthy file - &amp;#039;&amp;#039;&amp;#039;OXP verifier design.txt&amp;#039;&amp;#039;&amp;#039; tucked inside your Oolite installation with more information about it&lt;br /&gt;
&lt;br /&gt;
Note that it is possible to [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=21443 obtain graphical output] from Graphviz for OXP Verifier.&lt;br /&gt;
&lt;br /&gt;
=== Verifier BB threads ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=8&amp;amp;t=13400 plist Editor Pro for Windows] (2013 - full of relevant Red Herrings)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=16865 lite --verify-oxp fails when path has spaces in it] (2014)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=21359 OXP Develoopment and Plist files] (2023 - quick introduction)&lt;br /&gt;
&lt;br /&gt;
=== Correcting with plutil (Apple Macintosh Terminal utility) ===&lt;br /&gt;
Since a very small mistake is enough to stop a .plist from being accepted, it&amp;#039;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 &amp;#039;address&amp;#039; of the plist to be shown. Hit return, and Terminal will reveal whether or not the plist is OK. If it&amp;#039;s not, you might be given a clue to what is wrong, and the line number of the error - or just a general note that &amp;quot;Unexpected character { at line 1&amp;quot;!&lt;br /&gt;
&lt;br /&gt;
==Need for unique names==&lt;br /&gt;
On loading the oxps, Oolite will add all files in the AIs, Models, Sound and Scripts folders in one big 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Scripting with JavaScript==&lt;br /&gt;
Older OXPs (from [[User:Aegidian|Aegidian]]&amp;#039;s day were written in Legacy Script: see [[Methods]]. Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of &amp;#039;&amp;#039;&amp;#039;ECMAv5&amp;#039;&amp;#039;&amp;#039;. It is the same Spidermonkey version that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. [https://bb.oolite.space/viewtopic.php?p=256623#p256623 It is unlikely to change] in the future.&lt;br /&gt;
&lt;br /&gt;
JavaScript is the preferred scripting interface for worldScripts and shipScripts. The legacy scripting interface (see [[script.plist]]) still works, but is not supported. See [[Scripting Oolite with JavaScript]] for more information.&lt;br /&gt;
&lt;br /&gt;
Note that most of the [[Legacy Scripting]] still works perfectly well (XML &amp;amp; OpenStep)!&lt;br /&gt;
&lt;br /&gt;
==Hidden settings==&lt;br /&gt;
There are several [[Hidden_Settings_in_Oolite]] that make life for an oxp creator easier. One of them is the setting &amp;#039;&amp;#039;&amp;#039;always-flush-cache&amp;#039;&amp;#039;&amp;#039;. It makes every startup a bit slower, but it prevents Oolite working with cached data instead of your newly changed file. For someone that only does occasional oxp changes it will be enough to flush the cache by holding the shift key when starting Oolite but if you are writing oxps, this is the way to prevent frustrations.&lt;br /&gt;
&lt;br /&gt;
==Cookbook==&lt;br /&gt;
* How to add dials to a HUD: https://bb.oolite.space/viewtopic.php?p=290352#p290352&lt;br /&gt;
* How to limit a station&amp;#039;s shipyard to only offer a defined set of ships: https://bb.oolite.space/viewtopic.php?p=293174#p293174&lt;br /&gt;
* Ship/Station design with external docking ports: https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=21574&amp;amp;p=293777&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Context&amp;#039;&amp;#039;&amp;#039;: [https://bb.oolite.space/viewtopic.php?p=275434#p275434 What can OXP&amp;#039;s &amp;#039;&amp;#039;not&amp;#039;&amp;#039; change?] (2021)&lt;br /&gt;
*It is often helpful to dip one&amp;#039;s toes (claws?) in the water by experimenting with tweaking oxp&amp;#039;s first: see [[How to tweak OXZ&amp;#039;s]]&lt;br /&gt;
*[[:Category:Oolite scripting]]&lt;br /&gt;
*[[Javascript Operators]]&lt;br /&gt;
*[[:Category:Oolite JavaScript Reference‎]]&lt;br /&gt;
*[[:Category:Oolite Development]]&lt;br /&gt;
*[[User:Montana05|Montana05]] recommends https://www.w3schools.com/js/js_array_sort.asp for better knowledge of the js on Oolite.&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12149 OXP Development Best Practices] (2012-7)&lt;br /&gt;
*Some older oxp&amp;#039;s are written in [[Legacy Scripting]]&lt;br /&gt;
*[https://github.com/OoliteProject/oolite/find/master Github] vanilla game code repository - the resources section at the bottom of the page contains possibly useful parts of vanilla game coding, with occasional annotations.&lt;br /&gt;
=== Tools ===&lt;br /&gt;
*[[List of software]] that is helpful for creating OXPs (eg. editorial packages for javascript or 3D model creators)&lt;br /&gt;
*[[List of Planets used in OXPs]] for planets already used by other OXPs. Helps authors avoid overlapping with or breaking other OXPs.&lt;br /&gt;
*[[OXP_howto_Game_Balance|OXP howto Game Balance]] to avoid conflicts from accidental gameplay changes.&lt;br /&gt;
*[[Long Range Scanner]] is an OXP which allows you to jump around the star system to objects you have placed there - or to jump around within the galaxy. A &amp;quot;cheat&amp;quot; for players, but a useful tool for some OXP designers.&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=13422 What Tools Are Good For Windows OXP Programming?] (2013)&lt;br /&gt;
&lt;br /&gt;
==== Tutorials for Tools ====&lt;br /&gt;
*[https://web.archive.org/web/20050317033938/http://oolite.aegidian.org/cyoship/ Oolite Tutorial - Meshwork Shipbuilding (OSX only)] via WayBack Machine&lt;br /&gt;
*[https://web.archive.org/web/20060621211940/http://oolite.aegidian.org/cyoship2/ Oolite Tutorial - Wings 3D Shipbuilding (Cross-platform)] via WayBack Machine&lt;br /&gt;
&lt;br /&gt;
=== OXP tutorials ===&lt;br /&gt;
Oolite changes affecting different varieties of OXPs happened with v.1.76 (2011), v.1.80 (2014) &amp;amp; v1.82 (2015).&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20937 MasterClass: How to OXP (updating SoThisTC)] by [[User:Spara|Spara]] who teaches computing in Helsinki! (2021)&lt;br /&gt;
*[https://archive.org/details/GettingStartedWithOoliteOXZDevelopment Getting started with OXZ Development] &amp;#039;&amp;#039;An .odt for Open Office&amp;#039;&amp;#039;: By Bugbear (2012). 2 example OXPs: a pirate-ridden solar systems warning tool &amp;amp; Witchspace Blockades [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17731 BB Thread (2015)]&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18837 OXP Performance] BB thread (mostly 2017-8): improving your OXP (speed, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;)&lt;br /&gt;
==== Tutorials: Ships, Retextures &amp;amp; Dockables OXPs ====&lt;br /&gt;
*[[OXP howto model]]&lt;br /&gt;
*[[OXP howto texture]] - also covers planet textures&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18284 The bare minimum for a game-recognizable ship OXP] (thread: 2016)&lt;br /&gt;
*[[OXP_tutorial|OXP Tutorial]] creating a new spaceship - and then tweaking it in different ways (2007-13)&lt;br /&gt;
*[[OXP howto dockable stations]] (2009-10)&lt;br /&gt;
*[[User:Shipbuilder|Shipbuilder]] wrote a Shaders tutorial with resource packs (2013)&lt;br /&gt;
==== Tutorials: HUD OXPs ====&lt;br /&gt;
*[[OXP howto HUD]]&lt;br /&gt;
*[[Guide to HUDs]] - table comparing features&lt;br /&gt;
*[[HUD Customisation Guide‎‎]]&lt;br /&gt;
*[[Fully Annotated HUD Configuration (hud.plist) File‎]]&lt;br /&gt;
==== Tutorials: Missions OXPs ====&lt;br /&gt;
*[[OXP mission offering]]&lt;br /&gt;
*[[GalCop Missions]] has a wide variety of over 80 javascripted mini-missions - see the list behind the &amp;quot;Spoilers&amp;quot; button&lt;br /&gt;
==== Tutorials: Other ====&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=14135 How to make a simple OXP?] (thread: 2013) 3 OXPs - pop-up message at docking, set only Pythons for sale at Lave shipyard, create a new ship. &lt;br /&gt;
*[[Escape Pod Locator OXP]] has notes on programming on the bottom of the page regarding beacon transmission &amp;amp; location&lt;br /&gt;
&lt;br /&gt;
=== Helpful OXPs for your OXP===&lt;br /&gt;
There are a number of OXPs which have been specifically written to allow your OXP to use them:&lt;br /&gt;
*[[Library OXP|Library]]: a collection of useful snippets and helpers. Its main purpose is to simplify or unify some common tasks used by OXPers. &lt;br /&gt;
:*It can add dynamic maps, music &amp;amp; animation. &lt;br /&gt;
:*It adds a Personal Assistant Device for the player with details of people met, medals awarded, Guild rankings, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
:*It allows in-game configuration of an oxp by the player.&lt;br /&gt;
:*Add-on modules allows inspection of models and materials for creation of ship &amp;amp; station oxps.&lt;br /&gt;
*[[GalCop Missions]] introduces many new pieces of equipment with wide varieties of use (Cargo Stoppers, Ejection Dampers, Range Finders, Solar Radiation Disrupter Missiles, Seismic Resonance Scanners, Patient Transport Modules &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;). It can also help with creating missions (it contains over 80 varieties - see the spoiler button on that wiki page).&lt;br /&gt;
*[[Diplomancy]] can be used to make states of war impact personally on the player&lt;br /&gt;
*[[System Data Config]] helps re-organise the F7 screen to squeeze more information onto it&lt;br /&gt;
&lt;br /&gt;
==== While docked/stations ====&lt;br /&gt;
*[[HD Backgrounds]] can provide a High Definition screenshot of a station lobby or other such for interaction with the player&lt;br /&gt;
*[[BGS]] can help organise a customised docking or launching sequence (see the [[Riredi OXP]] or the [[Kiota Stations]]).&lt;br /&gt;
*[[GNN]] can broadcast your news alerts (see how [[Diplomancy]] uses it for war &amp;amp; peace declarations). GNN also contains &amp;#039;&amp;#039;&amp;#039;PhraseGen&amp;#039;&amp;#039;&amp;#039; which can be used for randomizing text descriptions.&lt;br /&gt;
*[[Station Validator]] will remember that a station has been destroyed and stop Oolite automatically replacing it on the next visit to the system&lt;br /&gt;
*[[Station Dock Control]] can help interraction with other ships docked at the station&lt;br /&gt;
*[[Bulletin Board System]] can help manage interractions at the station&lt;br /&gt;
*[[Email System OXP]] can also help manage interractions at the station&lt;br /&gt;
*[[Ship Storage Helper]] allows storage of the player&amp;#039;s ship whilst doing other things (such as flying another ship!)&lt;br /&gt;
*[[Equipment Storage OXP]]  allows storage of equipment/goods whilst doing other things&lt;br /&gt;
*[[Ship&amp;#039;s Library]] allows reading documents with illustrations while docked (see the included Ship&amp;#039;s Manual)&lt;br /&gt;
*[[Station Options]] allows complex configurations of equipment, but could potentially also be used for managing dialogue with NPCs&lt;br /&gt;
*[[Life in the Frontier]] was being expanded to cover more stations (Dodo/Ico/Rock Hermits and potentially OXP stations), but is currently mothballed. &lt;br /&gt;
&lt;br /&gt;
==== In-flight ====&lt;br /&gt;
*[[MFD - Broadcast Comms]] can be used for in-flight interaction with NPC&amp;#039;s&lt;br /&gt;
*[[Bigships]] can be used to help with the AI for massive space ships which cannot dock at orbital stations&lt;br /&gt;
*[[Montanas Resource Pack 01]] contains a number of resources for use (treasures, containers, escape/survival equipment)&lt;br /&gt;
*[[Star System Lane Indicator]] - the older version contains a very graphical dynamic display (does not function properly, but boy! does it look good!)&lt;br /&gt;
*[[SOTL Exploration]] contains exploration equipment and a non-automatic hyperspace jump&lt;br /&gt;
*[[SOTL Altmap]] contains different politics, markets and NPCs with Torus Drives.&lt;br /&gt;
*[[Resistance Commander]] &amp;amp; [[EscortDeck]] contain mechanisms for &amp;quot;managing&amp;quot; allied ships.&lt;br /&gt;
&lt;br /&gt;
==== Planet Surfaces ====&lt;br /&gt;
*[[Planetfall OXP]] allows landing on the planet (used by [[Feudal States]] for access to the Royal Court, and by [[Astronaut]] for space-jumping)&lt;br /&gt;
*[[Lave is Earth 8k]] contains night-time city lighting&lt;br /&gt;
&lt;br /&gt;
=== Packaging and distribution ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16688 The All-in-One Guide to OXZ Packaging and Distribution].&lt;br /&gt;
::And see [https://bb.oolite.space/viewtopic.php?p=279034#p279034 this post] for AppleMac issues with the above.&lt;br /&gt;
* Cim created [https://github.com/cim--/oxp-build-scripts some scripts to ease packaging] a project.&lt;br /&gt;
*[[OXP Distribution]] The All-in-One Guide to OXP Packaging and Distribution (and [[OXP_standards]] for advice on which ways of doing things are supported and which are not).&lt;br /&gt;
* Since the domain change to [https://oolite.space] the distribution of expansions has changed slightly. The new version is still subject to discussions and might change again. Here is a [[Publishing Procedure Comparison]].&lt;br /&gt;
*[[Gameplay_and_Balance_Indicator|Gameplay Balance Indicator]] and [[OXP_Levelindicators|Difficulty Indicator]]. Add these to your wiki page to show effects on Game Balance and the Difficulty Level of your OXP/OXZ. The &amp;#039;&amp;#039;&amp;#039;first&amp;#039;&amp;#039;&amp;#039; indicates the impact on play (equipment making the game easier/more difficult), the &amp;#039;&amp;#039;&amp;#039;second&amp;#039;&amp;#039;&amp;#039; indicates the suggested [[Elite Rating]] needed to attempt the mission/defeat the ship &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:World Builder cover art.png|200px|right|thumb|One of Wildeblood&amp;#039;s many AI-created OXP icons (for his [[World Builder]] OXP)]].&lt;br /&gt;
== Note on using AI to write your OXP ==&lt;br /&gt;
Since 2025 [[User:Wildeblood|Wildeblood]], [[User:Captain Beatnik|Captain Beatnik]] &amp;amp; [[User:Various Interest|Various Interest]] have used AI to write OXPs. And Krager has been using AI to improve some older OXPs.&lt;br /&gt;
&lt;br /&gt;
:Wildeblood has also used AI to produce OXP &amp;quot;icons&amp;quot; as well as a dozen or so of his most recent OXPs. &lt;br /&gt;
&lt;br /&gt;
:Captain Beatnik used it to produce [[CB-HUD Mark IV]] as well as the javascript and the new planet texture in [[Riredi OXP]].  &lt;br /&gt;
&lt;br /&gt;
:Various Interest used it for the sounds in his [[Better Damage Sounds OXP]]. &lt;br /&gt;
&lt;br /&gt;
:And Krager used it for the dated [[Cloud City OXP]], fixing the markets and placing the stations at Gas Giants - see the end of the BB thread [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=5932 here].&lt;br /&gt;
&lt;br /&gt;
There are more details about all of this on our BB in the appropriate threads which include some of the difficulties encountered as well as the AI engines used.&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite| ]]&lt;br /&gt;
[[Category:Oolite scripting| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Developer%27s_Corner&amp;diff=90359</id>
		<title>Developer&#039;s Corner</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Developer%27s_Corner&amp;diff=90359"/>
		<updated>2026-11-09T10:48:23Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note on using AI&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Here you will find information that helps understanding the Oolite source code, build and test the project.&lt;br /&gt;
&lt;br /&gt;
* [[Contributing to the project]]&lt;br /&gt;
* [[Release Process]]&lt;br /&gt;
* [[Branding]], [[Branding History]]&lt;br /&gt;
* [https://ooliteproject.github.io/oolite/ Oolite API documentation]&lt;br /&gt;
* [https://ooliteproject.github.io/oolite/ Doxygen Documentation]&lt;br /&gt;
* [https://ooliteproject.github.io/oolite/coverage/index.html Code Coverage Report]&lt;br /&gt;
* [[Cross Platform IDEs]]&lt;br /&gt;
* [[Compiling with Clang instead of gcc]] (Windows/Linux)&lt;br /&gt;
* [[Oolite build system]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OS Specific parts ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin:auto&amp;quot;&lt;br /&gt;
|+ Operating System dependent stuff&lt;br /&gt;
|-&lt;br /&gt;
! Procedure !! Apple Mac !! Linux !! Windows&lt;br /&gt;
|-&lt;br /&gt;
| Setting up a development environment || [[Development on Apple Mac]], [[Cross Platform IDEs]] || [[Development on Linux]], [[Cross Platform IDEs]] || [[Development on Windows]], [[Cross Platform IDEs]]&lt;br /&gt;
|-&lt;br /&gt;
| Compiling || [[Compiling on Apple Mac]] || [[Compiling on Linux]] || [[Developing Oolite#On_Windows_2 | Compiling on Windows]]&lt;br /&gt;
|-&lt;br /&gt;
| Testing || [[Testing on Apple Mac]], [[Common Testing]] || [[Testing on Linux]], [[Common Testing]] || [[Testing on Windows]], [[Common Testing]]&lt;br /&gt;
|-&lt;br /&gt;
| Packaging into Installer || [[Installer on Apple Mac]] || [[Installer on Linux]] || [[Installer on Windows]]&lt;br /&gt;
|-&lt;br /&gt;
| Running                  || [[Running Oolite-Mac]] || ||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Releasing the code ==&lt;br /&gt;
&lt;br /&gt;
Once you developed a while you might no longer be happy that all you have created is called &amp;#039;nightly&amp;#039; or &amp;#039;prerelease&amp;#039; or &amp;#039;unstable&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
If you are convinced the current status should be published as &amp;#039;stable&amp;#039; or &amp;#039;release&amp;#039;, follow the [[Oolite Release Process]].&lt;br /&gt;
&lt;br /&gt;
== Hints ==&lt;br /&gt;
&lt;br /&gt;
The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.&lt;br /&gt;
&lt;br /&gt;
If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=21470&lt;br /&gt;
&lt;br /&gt;
To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules&lt;br /&gt;
&lt;br /&gt;
=== Note on using AI ===&lt;br /&gt;
The lack of AppleMac developers prevented the successful updating of Oolite v.1.90 (between 2020-26). v.1.93 for the AppleMac was produced by David Hobley using AI and [https://bb.oolite.space/viewtopic.php?p=307341#p307341 published] at the end of October 2026 . See [https://github.com/OoliteProject/oolite Github] for details.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite Development| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Smugglers_-_The_Galactic_Underworld&amp;diff=90358</id>
		<title>Smugglers - The Galactic Underworld</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Smugglers_-_The_Galactic_Underworld&amp;diff=90358"/>
		<updated>2026-11-01T17:22:44Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Tips */ Added note on CB-HUD Mark IV&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Smugglers&amp;#039; News Flash.png|right|500px]]&lt;br /&gt;
Makes any commodity potentially illegal to import in various systems, and adds equipment and contracts for those interested in smuggling goods outside normal legal channels.&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
Historically, in both the original Elite and therefore in Oolite, there were three illegal goods: slaves, narcotics and firearms. These were illegal to export from all GalCop stations, and there was no variation or flexibility in those items. This OXP aims to expand what goods are illegal, making it far more variable. There are new interface screens to show what items are illegal and where, a new Black Market available from Rock Hermits and other stations, and new equipment items to aid in smuggling cargo.&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
It started with a single system.&lt;br /&gt;
&lt;br /&gt;
[[Sector1/Ceedra|Ceedra]], an insignificant confederacy in an unfrequented arm of galactic sector 1. They had been receiving some contaminated imported food from the nearby Anarchy system [[Sector1/Isdibi|Isdibi]], possibly random or possibly intentional as a way to destabilise the government, it was difficult to tell. But a request was made to [[GalCop]] to put an import ban on food and force any traders that bring food to the station to hand it over for destruction.&lt;br /&gt;
&lt;br /&gt;
The impact was almost immediate. Traders were outraged that their harmless cargo of wheat and grains were being taken away, which had never before happened in GalCop history, plus they received a bounty for doing so, doubling the pain. Messages were sent, trade delegations made an outward show of force, but GalCop&amp;#039;s hands were tied. This was the decision of the planet in question, and under GalCop law they were perfectly entitled to impose import restrictions, beyond the export restrictions that had long been in place for slaves or narcotics. &lt;br /&gt;
&lt;br /&gt;
Suddenly the floodgates were opened. System after system found reason to ban goods, from basic staples like food or textiles, up to the traders standard fare of computers, furs and liquor. Even precious metals were banned in some systems, often for rather obscure reasons. And always, once a ban was in place, the price would hit the roof.&lt;br /&gt;
&lt;br /&gt;
Some commentators have suggested there is evidence that certain systems were requesting a good to be made illegal purely for the jump in price that naturally follows and the bump in traffic that accompanies extra profits. While GalCop have been sought for comment, none has been forthcoming, and nothing appears to be able to bring a halt to the practice. If systems are indeed creating spurious trade legalities, GalCop is not preventing them.&lt;br /&gt;
&lt;br /&gt;
Somewhat inevitably, at almost the same time, an entirely new market emerged, beneath the radar of GalCop&amp;#039;s far-seeing eyes. As soon as a good was declared illegal to import the price of that good sky-rocketed, and the temptation to circumvent the restrictions GalCop was forced to impose was too great. Dock masters became a particular target, being offered high sums to fiddle manifest registries. Shadier stations began to offer customised smuggling compartments that provided a way to hide cargo from the customs scanning equipment. Contracts to move illicit cargo were also available from these locations.&lt;br /&gt;
&lt;br /&gt;
While it was always present in some form or another, now the Galactic Underworld became almost mainstream. The galaxy had changed.&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
This OXP aims to broaden the scope and appeal of illegal goods in a number of ways.&lt;br /&gt;
&lt;br /&gt;
===1. Illegal goods===&lt;br /&gt;
Illegal goods can now be any of the 17 different commodity types. So food might be declared illegal on one planet, computers on another. These things might change as well, so computers might be illegal for a few months, and then conditions are lifted and they are back to normal again.&lt;br /&gt;
&lt;br /&gt;
Also, illegal trade goods will now be illegal to import(*). If you arrive at a GalCop station with visible illegal goods in your hold, you will be fined and your cargo will be confiscated. See also the section below on &amp;#039;&amp;#039;Bribing Officials&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
Even if you plan to stay on the right side to the law, this OXP can add variety to the way illegal goods are handled by the game, and make the process of shipping cargo across the galaxy more interesting.&lt;br /&gt;
&lt;br /&gt;
Illegal goods notifications can be viewed on the F7 System Data screen, as well as via the F4 interface screen (see below). The F6 Galactic Chart will highlight systems within 7 LY that have illegal goods. Systems with just &amp;#039;&amp;#039;&amp;#039;firearms&amp;#039;&amp;#039;&amp;#039; as illegal will be shown with an &amp;#039;&amp;#039;&amp;#039;orange diamond&amp;#039;&amp;#039;&amp;#039;. Systems with other commodities, or with multiple commodities, will be shown with a &amp;#039;&amp;#039;&amp;#039;yellow diamond&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
(*) &amp;#039;&amp;#039;&amp;#039;Slaves&amp;#039;&amp;#039;&amp;#039; remain illegal to export, and they are the only commodity that is illegal to export. The reason for this is that some escape capsules end up being transported as slaves, and it&amp;#039;s unfair to penalise the player for potentially rescuing downed pilots. It is recommended the [[Illegal_Goods_Tweak_OXP|Illegal Goods Tweak OXP]] be installed so that captured slaves can be released. For other fixes see [[Escape Pod]].&lt;br /&gt;
&lt;br /&gt;
===2. Smuggling Compartment===&lt;br /&gt;
To help traders to work around these import restrictions a new piece of equipment, the smuggling compartment, can be purchased at non-GalCop stations (Rock Hermits in particular, but also other docking ports) in TL4 or greater systems. &lt;br /&gt;
&lt;br /&gt;
Cargo can be moved into and out of the smuggling compartment via an F4 Interface screen &amp;quot;Smuggling Compartment Configuration&amp;quot;. During flight, the &amp;quot;Smuggling Compartment Storage&amp;quot; primable equipment item allows for the transfer of cargo from the standard hold to the smuggling compartment. Cargo cannot be transferred out of the smuggling compartment during flight.&lt;br /&gt;
&lt;br /&gt;
The smuggling compartment has, in most circumstances, around a 25-40% chance of being detected, based on tech level. GalCop is always improving their detection equipment, which means that the scanner resistant technology of the smuggling compartment needs to be updated regularly to cope. About every 30 days a &amp;quot;Version Upgrade&amp;quot; should be purchased (at TL5 or greater systems) for your smuggling compartment, which will install the latest scanner resistant technology and keep the chance of detection as good as it possibly can be.&lt;br /&gt;
&lt;br /&gt;
This chance improves slightly once the &amp;quot;Phase Adjustment&amp;quot; equipment (available at TL7 or greater systems) is installed. With the phase adjustment equipment installed the phase setting of the hold can be adjusted, which can reduce the chance of being detected considerably. Phase settings can be picked up at Black Market noticeboard (which might be unreliable), or they can be purchased for a considerable cost. See also the Phase Scanner (below).&lt;br /&gt;
&lt;br /&gt;
If your compartment is damaged during a battle, cargo may be lost, the same as with normal cargo. You will need to find a non-GalCop station to repair the damage, otherwise the entire compartment will be discovered and removed, and you will receive a bounty. If you have a ship overhaul performed at a GalCop station with the smuggling compartment, it will be discovered and removed, and you will receive a bounty. See also the section below on Bribing Officials.&lt;br /&gt;
&lt;br /&gt;
===3. New equipment===&lt;br /&gt;
Apart from the smuggling compartment and phase adjustment tool, this OXP also introduces the following equipment items.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;** Phase Scanner **&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
TL8 or greater Anarchy systems will sometimes have a Phase Scanner available for purchase. The scanner can, when aimed at GalCop main stations, detect what phase setting the manifest scanners will be susceptible to. Once you know what the phase setting is for a particular government and tech level they can set the phase of their smuggling compartment and it will be almost undetectable to GalCop manifest scanners.&lt;br /&gt;
&lt;br /&gt;
The Phase scanner is used by targeting the main station, priming the equipment and then activating it. It will take a few seconds to perform its job, and will consume a large amount of energy in the process - a naval energy unit is required. If you are too close to the station, or you are moving too slowly, the station will detect the scan and a bounty will be placed on you. If you then dock at the station the scanner will be removed. If you are too far away from the main station the scanner will not operate. If a police vessel catches you performing a scan you will receive a bounty and may find yourself under fire.&lt;br /&gt;
&lt;br /&gt;
If your scanner is damaged you must get it repaired at a non-GalCop station, otherwise the equipment will be confiscated and you will receive a bounty. If you have a ship overhaul performed at a GalCop station while the equipment is on board, it will be removed as part of the overhaul and you will receive a bounty. But see also &amp;quot;Bribing Officials&amp;quot; below.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;** Tech version upgrades **&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
Technology improves every day, and the scanner resistant technology used in the smuggling compartment needs to be updated to keep in step with the times. So, the tech version upgrade will keep your smuggling compartment up-to-date. Available at TL5 or greater systems.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;** Import Permits **&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
While some goods might be declared illegal, you can still purchase a permit to import that good from the planet in question. Usually these permits are quite expensive. &lt;br /&gt;
&lt;br /&gt;
Permits can only be used once, and will automatically be removed after use.&lt;br /&gt;
&lt;br /&gt;
===4. Bribing Officials===&lt;br /&gt;
If your smuggling compartment is discovered during a renovation or when damaged, or you dock with illegal cargo in your hold, you can attempt to bribe the station officials. You will be asked to enter the amount of the bribe. If you pay attention to what the official says you can get an idea on whether a smaller amount will be required, but larger amounts will have a greater chance of being successful. If you are successful you will be able to keep all your cargo and equipment. If you are unsuccessful you will lose all smuggling-related equipment and may end up increasing the bounty on your head.&lt;br /&gt;
&lt;br /&gt;
The Black Market noticeboard (see below) can be useful in finding systems where the dock master and other customs officials can be bribed for a reasonable amount.&lt;br /&gt;
&lt;br /&gt;
===5. New Interfaces screens===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;** Black market **&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
See the [[Black Market]] page for more information about the Black Market.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;** Dock master **&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
When docked at a main station, and when the dock master is available (he doesn&amp;#039;t work 24/7!) from this interface you can ask him about any good milk runs he/she is aware of, or you can try to bribe them into changing your cargo manifest for you.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;** Illegal goods information **&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
Illegal goods are changing all the time. To try to keep track of the potential chaos, this interface screen will initially show you the latest changes to illegal goods in the sector, plus it offers the following options:&amp;lt;br/&amp;gt;&lt;br /&gt;
a. List of all illegal goods in the galaxy. Here you can see it all.&amp;lt;br/&amp;gt;&lt;br /&gt;
b. List of all illegal goods within 7LY of your current system.&amp;lt;br/&amp;gt;&lt;br /&gt;
c. List of illegal goods on your current course. If you have a long, cross-chart trip planned, this option will tell you what&amp;#039;s illegal on the way, and flagging which ones you have a permit for (if any).&amp;lt;br/&amp;gt;&lt;br /&gt;
d. List of all import permits. This is what you are authorised (legally or not) to import.&amp;lt;br/&amp;gt;&lt;br /&gt;
e. List of all Rock Hermit waypoints purchased.&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
One now needs to keep abreast of developments in the systems one is about to visit. This &amp;#039;&amp;#039;can&amp;#039;&amp;#039; be done using the new F4 choices. And it can &amp;#039;&amp;#039;also&amp;#039;&amp;#039; be done using the F7 screen - and if one&amp;#039;s route has been plotted using the [[ANA]], one can view the different systems along the route in F7 using the left/right arrow keys.&lt;br /&gt;
&lt;br /&gt;
=== Other OXPs ===&lt;br /&gt;
*[[CB-HUD Mark IV]] warns you if some of your cargo is contraband in the current system you are in.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==Adding additional commodities==&lt;br /&gt;
Additional commodities can be added to the system by doing the following:&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Adding the commodity permit cost, and price factors.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
  var sbi = worldScripts.Smugglers_Illegal;&amp;lt;br/&amp;gt;&lt;br /&gt;
  sbi._commodityInfo[&amp;quot;my_commodity_key&amp;quot;] = [permitCost, factorIncIllegal, factorIncBM];&lt;br /&gt;
  // permitCost        = How much an import permit will cost for this commodity (eg 2000)&lt;br /&gt;
  // factorIncIllegal  = The factor to increase this commodity by when it is flagged as illegal (eg 2.5 = 2.5 times original price)&lt;br /&gt;
  // factorIncBM       = The factor to increase this commodity by at a black market &lt;br /&gt;
  //                         when it is flagged illegal at the main station (eg 1.4 = 1.4 times standard price)&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Adding illegal possibilities for this commodity to the pool&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
  var sbi = worldScripts.Smugglers_Illegal;&lt;br /&gt;
  sbi._possibilities.push({&lt;br /&gt;
    govTypes:&amp;quot;0,3&amp;quot;, &lt;br /&gt;
    commodity:&amp;quot;my_commodity_key&amp;quot;, &lt;br /&gt;
    properties:&amp;quot;&amp;quot;, &lt;br /&gt;
    permit:1, &lt;br /&gt;
    scale:1, &lt;br /&gt;
    period:30, &lt;br /&gt;
    chance:0.5, &lt;br /&gt;
    description:&amp;quot;A brief description of the in-game reason for making this commodity illegal.&amp;quot;});&lt;br /&gt;
  /* &lt;br /&gt;
    govTypes:     Comma-separated list of government types (0-7) this definition can apply to eg (&amp;quot;0,1,2&amp;quot;)&lt;br /&gt;
    commodity:    Comma-separated list of commodity names this definition will apply to (eg &amp;quot;food,my_commodity_key&amp;quot;).&lt;br /&gt;
    properties:   Comma-separated list of text search strings to use against the planetary description.&lt;br /&gt;
                        For instance, &amp;quot;civil war&amp;quot; would only select planets that have &amp;quot;civil war&amp;quot; in their description.&lt;br /&gt;
                        &amp;quot;drink|brew&amp;quot; would only select planets that have &amp;quot;drink&amp;quot; or &amp;quot;brew&amp;quot; in their description.&lt;br /&gt;
    permit:       Boolean value (0 or 1) indicating whether a permit can be purchased for this commodity&lt;br /&gt;
    scale:        The legality scale to apply to this commodity. &lt;br /&gt;
                        The scale will apply when calculating the bounty to apply to a player caught smuggling &lt;br /&gt;
                        illegal goods as a multiplier. Most illegal goods have a scale of 1. Slaves have 2.&lt;br /&gt;
    period:       The period (in days) this definition will be active for.&lt;br /&gt;
    chance:       A chance factor, between 0 (never) and 1 (very often), to apply when selecting this definition&lt;br /&gt;
    description:  The description to display for this definition.&lt;br /&gt;
  */&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Add the [[Market Script Interface]] market script to your commodity.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
The [[Market Script Interface]] OXP enables multi-OXP interfaces to the same market script, and is how Smugglers enables the legal/illegal flags to be set for each commodity.&lt;br /&gt;
&lt;br /&gt;
In the commodity definition in your &amp;quot;trade-goods.plist&amp;quot; file, add the following line:&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;market_script&amp;quot; = &amp;quot;msi_tradegoods_market.js&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note: If your commodity definition already has a &amp;quot;market_script&amp;quot; defined, you will need to interface your code with [[Market Script Interface]], to enable it to work with the Smugglers version.&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
* This OXP updates the &amp;quot;oolite-contracts-cargo.js&amp;quot; file with a new version of the _initialiseCargoContractsForSystem function that excludes illegal goods from being selected for standard cargo contracts.&lt;br /&gt;
* Related to the previous note, this OXP also updates the _initialiseCargoContractsForSystem function of Switech&amp;#039;s Cargo-Contract-Mod, to exclcude illegal goods from being selected for standard cargo contracts.&lt;br /&gt;
* This OXP also changes the logic of the &amp;quot;Legal&amp;quot; column on the F8 Market screen. Previously, goods that were illegal to export were marked with &amp;quot;Im&amp;quot;, and goods illegal to import were marked with &amp;quot;Ex&amp;quot;. This logic has been reversed, and the column relabelled as &amp;quot;Ban&amp;quot; to indicate what type of ban is in place.&lt;br /&gt;
&lt;br /&gt;
==Special Note==&lt;br /&gt;
Because of the complex nature of this OXP, the possibility for conflicts is great, so please report any bugs or unexpected outcomes. Don&amp;#039;t assume someone else has noticed it - if two people report a bug it makes tracking the bug down so much easier!&lt;br /&gt;
&lt;br /&gt;
And it goes without saying that I&amp;#039;d like to hear from you if you have any suggestions on how the OXP could be improved. &lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
The [[Market Script Interface]] OXP is a requirement for this pack.&amp;lt;br/&amp;gt;&lt;br /&gt;
The [[Black Market]] OXP is a requirement for this pack.&amp;lt;br/&amp;gt;&lt;br /&gt;
The [[System Data Config|Compressed F7 Layout]] OXP is a requirement for this pack.&lt;br /&gt;
&lt;br /&gt;
==Incompatible OXP&amp;#039;s==&lt;br /&gt;
At present, this OXP is incompatible with the following OXPs:&lt;br /&gt;
* [[New_Cargoes|New Cargoes]] v1.2.3: The system of permits, how it stores cargo, and how it controls illegal goods are all potentially conflicting. See New Cargoes for a link to a detailed analysis. &lt;br /&gt;
However, version 2 of New Cargoes is compatible with Smugglers.&lt;br /&gt;
&lt;br /&gt;
This conflict has been recorded in the manifest file, so if you have New Cargoes installed the &amp;quot;Smugglers&amp;quot; OXP will not load.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
Place the &amp;#039;Smugglers_2.13.oxz&amp;#039; or &amp;#039;Smugglers.oxp&amp;#039; (extracted from the ZIP file download) into your &amp;#039;AddOns&amp;#039; folder and when you start the game, hold down &amp;#039;Shift&amp;#039; until you see the spinning Cobra.&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download [[Media:Smugglers_2.13.oxz|Smugglers_2.13.oxz]] v2.13 (downloaded {{#downloads:Smugglers_2.13.oxz}} times).&amp;lt;br/&amp;gt;&lt;br /&gt;
Download [https://app.box.com/s/9zwazfe98cg2z89bmpn7mmhypm24d3zj Smugglers.zip] v2.13 (extract OXP folder to AddOns)&lt;br /&gt;
&lt;br /&gt;
==License==&lt;br /&gt;
This OXP is released under the Creative Commons Attribution - Non-Commercial - Share Alike 3.0 license. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/&lt;br /&gt;
&lt;br /&gt;
Skull and crossbones image from https://commons.wikimedia.org/wiki/File:Skull_and_crossbones.png.&amp;lt;br/&amp;gt;&lt;br /&gt;
Warning image from http://simpleicon.com/warning-3.html.&amp;lt;br/&amp;gt;&lt;br /&gt;
Chat image from http://simpleicon.com/chat-2.html.&amp;lt;br/&amp;gt;&lt;br /&gt;
ID image from http://simpleicon.com/id_card.html.&amp;lt;br/&amp;gt;&lt;br /&gt;
Lock image from http://simpleicon.com/lock-2.html.&amp;lt;br/&amp;gt;&lt;br /&gt;
Cupboard image from http://simpleicon.com/cupboard_4.html&amp;lt;br/&amp;gt;&lt;br /&gt;
Candle image from http://simpleicon.com/candle-2.html.&amp;lt;br/&amp;gt;&lt;br /&gt;
Form image from http://simpleicon.com/admite_form_1.html.&amp;lt;br/&amp;gt;&lt;br /&gt;
Map marker image from http://simpleicon.com/map_marker.html.&lt;br /&gt;
&lt;br /&gt;
With the help of:&amp;lt;br/&amp;gt;&lt;br /&gt;
Layne, Stormrider, Norby, cim, Diziet Sma, Cody, and all the people on the BB who offered suggestions and ideas to make this OXP as good as it could be. If the OXP fails in any way, is it because of my limitations as a programmer, not because of the paucity of your ideas and contributions!&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
2.13&lt;br /&gt;
* Updates for Station Dock Control 2.0.&lt;br /&gt;
* Put the illegal goods information shown on the F7 screen into the top part of the screen, freeing up space for other OXP&amp;#039;s to use the lower half.&lt;br /&gt;
* Stopped hiding the HUD on the F7 screen.&lt;br /&gt;
&lt;br /&gt;
2.12&lt;br /&gt;
* Smugglers Guidebook now only purchasable through the Black Market.&lt;br /&gt;
&lt;br /&gt;
2.11&lt;br /&gt;
* Added Smuggler&amp;#039;s Guidebook to the Ship&amp;#039;s Library (if installed).&lt;br /&gt;
* Added check for the Market Screen Legal Column mod.&lt;br /&gt;
* Tweaked some mission screens for better positioning.&lt;br /&gt;
* The initial entry point to &amp;quot;Import Permits&amp;quot; and &amp;quot;Smuggling Compartments&amp;quot; is now free, so you no longer need a minimum cash balance to see what permits are available or what the Smuggling Compartment options are. If using Oolite 1.92, the amount and install time columns will also be suppressed for these items.&lt;br /&gt;
&lt;br /&gt;
2.10&lt;br /&gt;
* Fixed issue with inverted logic check in monkey-patch for Switech&amp;#039;s cargo contract mod.&lt;br /&gt;
&lt;br /&gt;
2.9&lt;br /&gt;
* Updated monkey-patch for Switech&amp;#039;s cargo contract mod.&lt;br /&gt;
&lt;br /&gt;
2.8&lt;br /&gt;
* Fixed issue with cargo storage when New Cargoes not installed.&lt;br /&gt;
&lt;br /&gt;
2.7&lt;br /&gt;
* Darkened overlay images for better compatibility with Oolite 1.92.&lt;br /&gt;
&lt;br /&gt;
2.6&lt;br /&gt;
* Moved all text into descriptions.plist or missiontext.plist for easier localisation.&lt;br /&gt;
* Corrected information in readme.txt.&lt;br /&gt;
* Pushed out tech upgrades to every 60 days (rather than every 30).&lt;br /&gt;
* When asked about milkruns, the Dock Master will now show a short range chart or the run, rather than a long range chart.&lt;br /&gt;
&lt;br /&gt;
2.5&lt;br /&gt;
* Tokenised descriptions to reduce size of save file.&lt;br /&gt;
* Added shortcut keys to short &amp;amp; long range charts.&lt;br /&gt;
* Added text to Contextual Help.&lt;br /&gt;
&lt;br /&gt;
2.4&lt;br /&gt;
* Bug Fixes.&lt;br /&gt;
&lt;br /&gt;
2.3&lt;br /&gt;
* Fixed bug introduced when changing over to use the Market Script Interface.&lt;br /&gt;
* Fixed syntax error in Dock Master script.&lt;br /&gt;
&lt;br /&gt;
2.2&lt;br /&gt;
* Allows color and shape of chart markers for illegal goods to be changed via Library Config.&lt;br /&gt;
* Tweaked the returns and time frames for gold, platinum and gem stones, to not be quite so generous or easy to exploit.&lt;br /&gt;
* Fixed issue where illegal goods were not being created if starting a new game with the &amp;quot;Easy Start&amp;quot; option.&lt;br /&gt;
* Code refactoring.&lt;br /&gt;
&lt;br /&gt;
2.1.1&lt;br /&gt;
* Removed reference to blackmarket script from world-scripts.plist.&lt;br /&gt;
&lt;br /&gt;
2.1&lt;br /&gt;
* Enabled equipment conditions, which had been turned off for testing.&lt;br /&gt;
&lt;br /&gt;
2.0&lt;br /&gt;
* Updated market script process to use new [[Market Script Interface]] OXP.&lt;br /&gt;
* Switched pricing change to be inside market script callbacks (so they will now show up on sample price calculations).&lt;br /&gt;
* Made compatible with [[New Cargoes]] OXP (version 2.0)&lt;br /&gt;
* Split off [[Black Market]] into its own OXP, and made it a requirement of this OXP.&lt;br /&gt;
&lt;br /&gt;
1.5.8&lt;br /&gt;
* Fixed some potential referencing errors with mission screens.&lt;br /&gt;
&lt;br /&gt;
1.5.7&lt;br /&gt;
* Added extra facility for removing the Black Market on stations.&lt;br /&gt;
&lt;br /&gt;
1.5.6&lt;br /&gt;
* Better use of new functions available in later versions of Oolite.&lt;br /&gt;
* Removed code that was deleting TL1 phase scan settings.&lt;br /&gt;
* Bug fixes.&lt;br /&gt;
&lt;br /&gt;
1.5.5&lt;br /&gt;
* List of illegal goods displayed on F7 system data screen will now be shown inflight, but without reasons (ie just a list of illegal goods).&lt;br /&gt;
* Additional checking types added to ship condition checking routine.&lt;br /&gt;
* Bug fixes.&lt;br /&gt;
&lt;br /&gt;
1.5.4&lt;br /&gt;
* Moving kg or g type commodities will now force the Manifest MFD to update.&lt;br /&gt;
* Better integration with Escape Pod Tweaks. Scooped escape pods can no longer be transferred to the smuggling compartment.&lt;br /&gt;
* Equipment.plist corrections. &lt;br /&gt;
* Updates to readme.txt file.&lt;br /&gt;
&lt;br /&gt;
1.5.3&lt;br /&gt;
* Removed 1t cargo space requirement for in-flight storage equipment, to ensure it is always available when a smuggling compartment is installed.&lt;br /&gt;
* Removed incorrect Naval Energy Unit requirement for in-flight storage equipment.&lt;br /&gt;
* Code refactoring.&lt;br /&gt;
&lt;br /&gt;
1.5.2&lt;br /&gt;
* Fixed issue with the in-flight storage function not handling all conditions when checking scooped cargo.&lt;br /&gt;
&amp;lt;div class=&amp;quot;mw-collapsible mw-collapsed&amp;quot;  data-expandtext=&amp;quot;Show older&amp;quot; data-collapsetext=&amp;quot;Hide older&amp;quot; style=&amp;quot;overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
1.5.1&lt;br /&gt;
* Fixed broken integration with &amp;quot;Escape Pod Tweaks&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
1.5.0&lt;br /&gt;
* Added new options for when player is caught in a sting operation: pay a fine amount, accept a legal penalty, or attempt to bribe their way out of trouble.&lt;br /&gt;
* System productivity now has an influence on the amount you need to offer when bribing officials.&lt;br /&gt;
* Calculation of the maximum smuggling compartment size now factors in current smuggling compartment size so all downgrade options are available (not just the ones that would fix in the current available space).&lt;br /&gt;
* Fixed damage/repair process.&lt;br /&gt;
* Fixed issue with smuggling compartment damage resetting the tech level of the compartment.&lt;br /&gt;
* Fixed incorrect description lookup key.&lt;br /&gt;
* Improved integration with the &amp;quot;Escape Pod Tweaks&amp;quot; OXP.&lt;br /&gt;
* Code cleanup.&lt;br /&gt;
&lt;br /&gt;
1.4.2&lt;br /&gt;
* Systems with illegal goods marked on the map will now have their marks removed after loading the game if the setting switch is turned off via Library Config.&lt;br /&gt;
&lt;br /&gt;
1.4.1&lt;br /&gt;
* Primable equipment now given to player who already had a smuggling compartment installed.&lt;br /&gt;
&lt;br /&gt;
1.4.0&lt;br /&gt;
* Added primable equipment which allows cargo to be moved to the smuggling compartment during flight.&lt;br /&gt;
* Fixed issue on &amp;quot;Move cargo out&amp;quot; screen, showing &amp;quot;[avail]&amp;quot; instead of available compartment space.&lt;br /&gt;
* Removed decimal point values from showing for available compartment space.&lt;br /&gt;
* Better handling of kg and g commodities.&lt;br /&gt;
* Fixed issue with outrageous amounts being offered for narcotics and slaves on the Black Market.&lt;br /&gt;
&lt;br /&gt;
1.3.2&lt;br /&gt;
* Better handling of interstellar space conditions.&lt;br /&gt;
&lt;br /&gt;
1.3.1&lt;br /&gt;
* Added options to [[Library OXP|Library]] Config to control whether systems with illegal goods are marked on the galaxy map.&lt;br /&gt;
&lt;br /&gt;
1.3.0&lt;br /&gt;
* It is now possible to add new commodities to the list of illegal goods possibilities.&lt;br /&gt;
* The dock master can now relabel cargo as new (ie. non-core) commodities.&lt;br /&gt;
* System map will now be shown when the dock master informs player of a milk run, highlighting the two systems.&lt;br /&gt;
* Illegal goods on route will now handle not having the Advanced Navigation Array correctly.&lt;br /&gt;
* Cleaned up overlay images.&lt;br /&gt;
&lt;br /&gt;
1.2.2&lt;br /&gt;
* Added &amp;quot;display_color&amp;quot; property to some equipment items (Oolite v1.85/86 only).&lt;br /&gt;
* Added integration options for &amp;quot;Bounty System - Most Wanted&amp;quot; OXP.&lt;br /&gt;
* Better handling of interstellar space.&lt;br /&gt;
* Code refactoring.&lt;br /&gt;
&lt;br /&gt;
1.2.1&lt;br /&gt;
* Fix for crazy prices being applied after a saved game is reloaded.&lt;br /&gt;
&lt;br /&gt;
1.2.0&lt;br /&gt;
* Changed method of adjusting prices to work better with other OXP&amp;#039;s that adjust prices.&lt;br /&gt;
* Fixed Javascript error when attempting to sell illegal cargo through the Black Market.&lt;br /&gt;
* Added console message confirming sale of illegal cargo through the Black Market.&lt;br /&gt;
* Code cleanup.&lt;br /&gt;
&lt;br /&gt;
1.1.4&lt;br /&gt;
* Arranged data on illegal goods lists to be in columns.&lt;br /&gt;
* Removed hard-coded scanner range values.&lt;br /&gt;
&lt;br /&gt;
1.1.3&lt;br /&gt;
* Fixed error where function to remove sting ship monkey patches wasn&amp;#039;t being passed the correct parameter.&lt;br /&gt;
&lt;br /&gt;
1.1.2&lt;br /&gt;
* Added code for putting smuggling contracts on the Bulletin board system if the Contracts On BB OXP is also installed.&lt;br /&gt;
* Code refactoring.&lt;br /&gt;
&lt;br /&gt;
1.1.1&lt;br /&gt;
* Fixed some spelling mistakes.&lt;br /&gt;
* Added &amp;quot;machinery&amp;quot; to list of commodities the &amp;quot;Visible As&amp;quot; property of a smuggling compartment can be set to.&lt;br /&gt;
* Fixed issue with not being able to move machinery into or out of the smuggling compartment.&lt;br /&gt;
* Fixed issue with not being able to purchase or sell machinery directly from the smuggling compartment.&lt;br /&gt;
&lt;br /&gt;
1.1.0&lt;br /&gt;
* Additional info on F7 screen is now only available when docked to stop the information from overrunning the HUD.&lt;br /&gt;
* Corrected use of &amp;quot;techLevel&amp;quot;/&amp;quot;techlevel&amp;quot; on systemInfo objects.&lt;br /&gt;
* Re-fixed issue with amount of gold, platinum and gemstones taking up the same amount of smuggling cargo space as normal cargo space.&lt;br /&gt;
&lt;br /&gt;
1.0.0&lt;br /&gt;
* Bug fixes.&lt;br /&gt;
&lt;br /&gt;
0.9.0&lt;br /&gt;
* Added new Black Market option, enabling the sale of rare or expensive equipment items (eg naval-sourced equipment)&lt;br /&gt;
* Added ability for 3rd party OXP&amp;#039;s to add items for sale to the Black Market.&lt;br /&gt;
* Fixed incorrect label in descriptions.plist.&lt;br /&gt;
* Fixed issue where a smuggling compartment repair item was being displayed when the unit wasn&amp;#039;t damaged.&lt;br /&gt;
* Add ability for sting ship to respond to cloaked attacks.&lt;br /&gt;
* Better handling of interstellar space conditions.&lt;br /&gt;
* Some values were not being reset correctly after a galactic jump.&lt;br /&gt;
* Police ship model used on all police-related screens displayed at that station will now be the same model.&lt;br /&gt;
* Sound effects added for mode/activate functions of phase scanner.&lt;br /&gt;
&lt;br /&gt;
0.8.1&lt;br /&gt;
* Fixed issue where opening the &amp;quot;Purchase Smuggling Compartment&amp;quot; screen was turning off the HUD and not turning it back on again.&lt;br /&gt;
&lt;br /&gt;
0.8.0&lt;br /&gt;
* Fixed Javascript error when opening the market info details screen for a commodity in interstellar space.&lt;br /&gt;
* Added $isGoodIllegal function to Smugglers_Illegal.&lt;br /&gt;
&lt;br /&gt;
0.7.9&lt;br /&gt;
* Fixed issue where docking will illegal goods and rescued escape pods was not allowing the player to bribe the station officials.&lt;br /&gt;
&lt;br /&gt;
0.7.8&lt;br /&gt;
* Fixed issue where illegal good definitions were not being applied correctly in every situation.&lt;br /&gt;
&lt;br /&gt;
0.7.7&lt;br /&gt;
* Fixed issue with smuggling compartments of various sizes appearing on the equipment screen.&lt;br /&gt;
&lt;br /&gt;
0.7.6&lt;br /&gt;
* Better handling of situation where another OXP removes the smuggling compartment.&lt;br /&gt;
* Fixed issue with contracts where a Javascript error could occur in rare circumstances.&lt;br /&gt;
* Fixed Javascript error with script attached to police sting ship.&lt;br /&gt;
* Improved sting ship compatibility with other worldScripts.&lt;br /&gt;
* Really (hopefully, maybe) fixed vector error in Blackmarket script.&lt;br /&gt;
* Changed &amp;quot;==&amp;quot; comparisons to &amp;quot;===&amp;quot; for performance improvements.&lt;br /&gt;
&lt;br /&gt;
0.7.5&lt;br /&gt;
* Fixed Javascript vector error in Blackmarket script.&lt;br /&gt;
* Added code to make use of enhanced F7 screen features in Oolite 1.83/4.&lt;br /&gt;
&lt;br /&gt;
0.7.4&lt;br /&gt;
* Reconfigured the cargo contracts fixes to work with the default contract code and with Switech&amp;#039;s cargo contract mod OXP.&lt;br /&gt;
* Removed unnecessary &amp;quot;requires.plist&amp;quot; file.&lt;br /&gt;
* Extra checking for the presence of the sting ship to prevent null errors.&lt;br /&gt;
* Fixed issue where smuggling equipment was not being offered for sale anywhere.&lt;br /&gt;
* Fixed issue where the phase scanner was not being offered for sale at any time.&lt;br /&gt;
* Fixed issue where going into the smuggling compartment purchase page multiple times without actually purchasing something was deducting money anyway.&lt;br /&gt;
* Adjusted the price of the phase scanner.&lt;br /&gt;
* Tidying up of some equipment installation rules.&lt;br /&gt;
* F7 screen was turning off HUD when in flight in some circumstances.&lt;br /&gt;
&lt;br /&gt;
0.7.3&lt;br /&gt;
* Fixed issue with incorrect text showing on F8F8 commodity info screen.&lt;br /&gt;
* Included current system in list of planets shown on &amp;quot;Illegal imports on current course&amp;quot; option.&lt;br /&gt;
* Fixed issue with the Black Market welcome text, which was not being correctly reset upon docking.&lt;br /&gt;
&lt;br /&gt;
0.7.2&lt;br /&gt;
* Fixed loop variable pointer error in Black Market script.&lt;br /&gt;
&lt;br /&gt;
0.7.1&lt;br /&gt;
* Fixed timer setup bug in Black Market script.&lt;br /&gt;
&lt;br /&gt;
0.7.0&lt;br /&gt;
* Updated all bounty changes to use &amp;quot;setBounty&amp;quot;, rather than just updating the bounty directly, so a description can be passed to other OXP&amp;#039;s.&lt;br /&gt;
* Expanded the use of the &amp;quot;properties&amp;quot; element of illegal definitions, so that multiple options can be entered (eg &amp;quot;cuisine,meat,steak&amp;quot;).&lt;br /&gt;
* Added a couple of extra illegal goods definitions.&lt;br /&gt;
* Added the ability to sell illegal cargo on the Black Market, for a reduced price. Plus some extra things...&lt;br /&gt;
* Added Seedy Space Bars to list of stations that have a Black Market.&lt;br /&gt;
* Moved a lot of static text into descriptions.plist and missiontext.plist.&lt;br /&gt;
* Fixed issue with only 500kg of gold or platinum taking up 1t of smuggling cargo space, and 500000g of gemstones.&lt;br /&gt;
* Removed redundant items from equipment.plist.&lt;br /&gt;
* Fixed bug when using a HUD that doesn&amp;#039;t implement the &amp;quot;Big GUI&amp;quot; option, where the HUD was being turned off when displaying some mission screens, but wasn&amp;#039;t being turned back on again.&lt;br /&gt;
* In Oolite 1.83 the bugfix relating to damaged equipment items that take up cargo space is resolved, so code has been added to switch to using the in-built repair methods, rather than keeping a long list of &amp;quot;Repair&amp;quot; equipment items. For backwards compatibility with 1.82, however, those items are still present.&lt;br /&gt;
* Adjusted the costs of repair items to be more in-line with how the core system handles repair costs.&lt;br /&gt;
* Improved integration with Illegal Goods Tweak. When docking with slaves, IGT will always run first, and Smugglers will be called afterwards.&lt;br /&gt;
* Updated screenID&amp;#039;s to enable BGS background sounds.&lt;br /&gt;
* Renamed background overlay images to prevent possibility of future duplication.&lt;br /&gt;
* Added checks for null value in station allegiance.&lt;br /&gt;
* Updated the check for &amp;quot;Allow Big GUI&amp;quot;.&lt;br /&gt;
* Cleaned up sound function to avoid the need to check for BGS.&lt;br /&gt;
* Toned down overlay images.&lt;br /&gt;
* Code refactoring.&lt;br /&gt;
&lt;br /&gt;
0.6.2&lt;br /&gt;
* Fixed bug with checking for and removing used permits.&lt;br /&gt;
* Fixed issue where Constrictor hunt mission hints were being pushed off the System Data screen by all the illegal goods notifications.&lt;br /&gt;
* Added extra overlay image for purchasing Permits.&lt;br /&gt;
* Added extra overlay image for Rock Hermit waypoint list.&lt;br /&gt;
&lt;br /&gt;
0.6.1&lt;br /&gt;
* Using escape pod will now empty smuggler&amp;#039;s compartment.&lt;br /&gt;
* Pared down &amp;quot;trade-goods.plist&amp;quot; to only contain required information, hopefully making it compatible with &amp;quot;Risk based economy&amp;quot; v2 OXP and BlOomberg Markets OXP.&lt;br /&gt;
* Removing the smuggling compartment or phase scanner at a Rock Hermit (or other non-GalCop station) will now refund the full cost, rather than just 70%.&lt;br /&gt;
* Changing the size of the smuggling compartment will refund the full price of the old size first, before purchasing the new size.&lt;br /&gt;
* Fixed bug when starting new game.&lt;br /&gt;
* Fixed issue where the message about delivering illegal goods via a cargo contract was appearing incorrectly.&lt;br /&gt;
&lt;br /&gt;
0.6.0&lt;br /&gt;
* Fixed issue where illegal flags were not appearing on secondary stations, removed need to have planetinfo.plist.&lt;br /&gt;
* Removed log file debug code.&lt;br /&gt;
&lt;br /&gt;
0.5.0&lt;br /&gt;
* Fixed bug with selling relabelled cargo.&lt;br /&gt;
* Fixed issue with delivering a standard cargo contract to a system where the cargo has become illegal after accepting the contract. The player was not being given the opportunity to bribe a docking official to clear their bounty.&lt;br /&gt;
* Fixed issue where, after using the phase scanner and being discovered using it, and then docking, the player was not being given the opportunity to bribe their way out of trouble.&lt;br /&gt;
* Added emails for various actions, when the Email System OXP is in use.&lt;br /&gt;
* Changed skull and crossbones background image for Black Market.&lt;br /&gt;
* Improved integration with [[Illegal_Goods_Tweak_OXP|Illegal Goods Tweak OXP]] (v2.2.0). The inital screen IGT displays will now look like an Amnesty Intergalactic screen, rather than a GalCop one, and the player has only two choices: hand over the slaves, or work with GalCop. If they choose the latter, Smugglers will include slaves as part of its import restrictions and the player can bribe as normal if they choose to.&lt;br /&gt;
&lt;br /&gt;
0.4.0&lt;br /&gt;
* Fixed issue where you could purchase any smuggling compartment, regardless of how much credit you have.&lt;br /&gt;
* Added player credit balance to smuggling compartment purchase screen.&lt;br /&gt;
* Added player credit balance to Black Market purchasing screens.&lt;br /&gt;
* Tightened up which stations will have a Black Market.&lt;br /&gt;
* Added government icon and TL to all purchase screens in Black Market.&lt;br /&gt;
* Tweaks to the calculation of phase scan noticeboard items.&lt;br /&gt;
* Improvements to the page handling for illegal goods.&lt;br /&gt;
&lt;br /&gt;
0.3.1&lt;br /&gt;
* Fixed mangled manifest.plist file.&lt;br /&gt;
&lt;br /&gt;
0.3.0&lt;br /&gt;
* Tweaks to the minimum tech level for purchasing smuggling equipment items.&lt;br /&gt;
* Further adjustments to precious metals and gem stones illegal notifications for better economic balance.&lt;br /&gt;
* Added overlay background images to various interface screens.&lt;br /&gt;
* Smuggling compartment repair costs now linked to size of compartment.&lt;br /&gt;
* Arriving in a system where you have a permit but no cargo for that permit will no longer remove the permit.&lt;br /&gt;
* Routine to create new illegal goods will now exclude the current system, to prevent the issue where the engine understands a good is illegal, but the game interface doesn&amp;#039;t.&lt;br /&gt;
* Added extra checks to the docking process to ensure a good that the engine understands is illegal is also marked as illegal on the market screen before penalising the player.&lt;br /&gt;
* Added police ship models to all the after-dock screens.&lt;br /&gt;
&lt;br /&gt;
0.2.0 &lt;br /&gt;
* Made the price of RH waypoints, fake permits and phase scans related to the station price factor.&lt;br /&gt;
* Bribing the same station multiple times will increase the required amount of the bribe (by 10 or 20 percent each time).&lt;br /&gt;
* Added the last successful bribe amount to the screen where you enter a bribe amount.&lt;br /&gt;
* Reduced the police vessel detection range for the phase scanner, as their ships wouldn&amp;#039;t have the same range as the main station.&lt;br /&gt;
* Main station market quantity of illegal goods under contract now set to zero (so, when arriving short, the player can&amp;#039;t just buy the difference, launch and redock to complete the contract).&lt;br /&gt;
* Fixed issue where you could purchase anything from the Black Market, regardless of how much credit you have.&lt;br /&gt;
* Limited smuggling compartment options to standard commodities only.&lt;br /&gt;
* Fixed issue where wrong illegal goods were being picked up if the player followed another ship through a wormhole.&lt;br /&gt;
* Rebalanced prices for precious metals and gem stones.&lt;br /&gt;
* Damaged smuggling compartments and phase scanners can now be repaired, and better handling of damaged equipment in general.&lt;br /&gt;
* Fixed issue where phase scanner would not show up for purchase anywhere.&lt;br /&gt;
* Fixed issue where having 0t available space would not allow transfer of precious metals from smuggling compartment to standard hold.&lt;br /&gt;
* Added a new item to the Illegal Goods interface screen that lists all purchased Rock Hermit waypoints.&lt;br /&gt;
* Fixed issue with tech upgrades, where the option to purchase new ones was always available, no matter how many times you purchased it.&lt;br /&gt;
* Adjusted the price of the tech upgrade.&lt;br /&gt;
* Bug fixes.&lt;br /&gt;
&lt;br /&gt;
0.1.2&lt;br /&gt;
* Added missing semi-colon to planetinfo.plist.&lt;br /&gt;
* Found additional spot where techlevel was showing 1 lower than actual.&lt;br /&gt;
* Fixed issue where phase scans for TL 1 systems would not show up in the list of discovered phase scans.&lt;br /&gt;
&lt;br /&gt;
0.1.1&lt;br /&gt;
* Tech levels on all displays were showing 1 lower than actual.&lt;br /&gt;
* Attempting to bribe a dock master to relabel cargo when you don&amp;#039;t have any cargo that can be relabeled would put the game into a locked state.&lt;br /&gt;
* Spelling corrections.&lt;br /&gt;
&lt;br /&gt;
0.1.0&lt;br /&gt;
* Initial public release&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17723 BB Thread for this OXP] &lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17179 Idea for Smugglers OXP] (2015) Fons et origo of this OXP&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=17675 Legal column on Market screen] (2015) related discussion of the confusions inherent in the Legal column.&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=204379#p204379 Expanded version of the smuggling proposal] (Elite: Dangerous - Design Decision Forum: 2013)&lt;br /&gt;
&lt;br /&gt;
==Quick Facts==&lt;br /&gt;
{{OXPLevel|2}}{{IconOXP|ooVersion=&amp;quot;1.82&amp;quot;|oxpCPU=&amp;quot;Average&amp;quot;|oxpMEM=&amp;quot;Average&amp;quot;|oxpGPU=&amp;quot;Low&amp;quot;|oxpIsAPI=true|oxpIsDocumented=true|oxpIsConfigurable=true}}&lt;br /&gt;
[[Image:IconLib.png|48px|right|link=Library OXP|alt=Config options available through &amp;#039;Library&amp;#039;]]&lt;br /&gt;
{{Infobox OXPb| title = Smugglers.oxz&lt;br /&gt;
|version = 2.13&lt;br /&gt;
|release = 2026-06-21&lt;br /&gt;
|license = CC BY-NC-SA 3.0&lt;br /&gt;
|features = Equipment, Commodities&lt;br /&gt;
|category = Mechanics OXPs&lt;br /&gt;
|author = [[User:phkb|phkb]]&lt;br /&gt;
|feedback = [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17723 Oolite BB]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Gameplay and Balance indicator==&lt;br /&gt;
[[Image:tag-colour-orange.png]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=GalCops&amp;diff=90355</id>
		<title>GalCops</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=GalCops&amp;diff=90355"/>
		<updated>2026-10-24T21:08:39Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Page created (redirect)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[GalCop (Police)]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Pilot%27s_Reference_Manual&amp;diff=90354</id>
		<title>Pilot&#039;s Reference Manual</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Pilot%27s_Reference_Manual&amp;diff=90354"/>
		<updated>2026-10-24T21:07:35Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Minor tweaks&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;font size=&amp;quot;4&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;Pilot’s Reference Manual to the Cobra Mk III&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
(revision 3.1.57a)&amp;lt;br/&amp;gt;&lt;br /&gt;
Published by [[Faulcon de Lacy|Faulcon deLacy]]&amp;lt;br/&amp;gt;&lt;br /&gt;
Written by Lt. D Hughes (Test Pilot, Cowell &amp;amp; MgRath Shipyards, Lave)&amp;lt;br/&amp;gt;&lt;br /&gt;
[[File:Oolite-543.png|right|800px]]&lt;br /&gt;
[[File:Oolite-954.png|right|800px]]&lt;br /&gt;
Engineering Team:&amp;lt;br/&amp;gt;&lt;br /&gt;
Prof. I. Bell, Prof. D. Braben&amp;lt;br/&amp;gt;&lt;br /&gt;
Avionics &amp;amp; Navigation Team:&amp;lt;br/&amp;gt;&lt;br /&gt;
Cdr. G. Williams, Cdr. D Smith, Cdr. D. Taylor&amp;lt;br/&amp;gt;&lt;br /&gt;
==Introduction to the Cobra Mk III==&lt;br /&gt;
===Timeline ([[Lore|syncretist]])===&lt;br /&gt;
2972 - 	[[Paynou, Prossett and Salem]] proposal for a successor to the [[Cobra Mk.1 (Oolite)|Cobra Mk I]] receives green light by [[GalCop|Galactic Co-operative]] and [[GASEC]] officials. Financing is arranged.&amp;lt;br/&amp;gt;&lt;br /&gt;
2974 - 	[[Cobra_Mk.2_(Oolite)|Cobra Mk II]] designs authorised – construction of 2 prototype shells begins.&amp;lt;br/&amp;gt;&lt;br /&gt;
2982 - 	First prototype explodes on launch due to shearing stress on hull.&amp;lt;br/&amp;gt;&lt;br /&gt;
2983 - 	Second prototype scrapped due to malformed alloys.&amp;lt;br/&amp;gt;&lt;br /&gt;
2985 - 	Third prototype commissioned following acquisition of further funding from [[Faulcon de Lacy|Faulcon deLacy]].&amp;lt;br/&amp;gt;&lt;br /&gt;
2988 - 	Third prototype launched. Initial trials successful.&amp;lt;br/&amp;gt;&lt;br /&gt;
2990 - 	Following exhaustive tests, metal stress fractures found in key areas of hull. Cobra Mk II design scrapped.&amp;lt;br/&amp;gt;&lt;br /&gt;
2994 - 	PPS fail to repay loans and are incorporated into Faulcon deLacy. FdL refurbish Cobra Mk I design using some elements of suggested Mk II systems.&amp;lt;br/&amp;gt;&lt;br /&gt;
3069 - 	FdL begin design tests on [[Cobra Mk.3 (Oolite)|Cobra Mk III]] designs, following on from suggestions made by the original Mk II design team.&amp;lt;br/&amp;gt;&lt;br /&gt;
3073 - 	Cobra Mk III design specification is agreed, including the landmark modular construction strategy, allowing for high levels of customisability.&amp;lt;br/&amp;gt;&lt;br /&gt;
3079 - 	Two prototypes built at [[Cowell &amp;amp; MgRath]] shipyards on [[Lave]]. Testing is scheduled to be based on Lave Coriolis 1.&amp;lt;br/&amp;gt;&lt;br /&gt;
3083 -	First prototype returns after extensive tests. Second prototype is launched and returns successfully.&amp;lt;br/&amp;gt;&lt;br /&gt;
3084 - 	Tests reveal minor stressing. Small redesigns are authorised and carried out.&amp;lt;br/&amp;gt;&lt;br /&gt;
3085 - 	Second wave of testing on both prototypes reveals no problems with spaceframe.&amp;lt;br/&amp;gt;&lt;br /&gt;
3088 - 	Avionics and engineering options are developed for the frame.&amp;lt;br/&amp;gt;&lt;br /&gt;
3092 - 	Bridge and control modules are finalised.&amp;lt;br/&amp;gt;&lt;br /&gt;
3094 - 	Cargo bay design is finalised, including options for refitting and expansion.&amp;lt;br/&amp;gt;&lt;br /&gt;
3098 - 	Cobra Mk III is cleared by GASEC and GalCop for commercial sales.&amp;lt;br/&amp;gt;&lt;br /&gt;
3100 - 	First production Cobra Mk III is purchased by GalCop and tested. GalCop begins negotiations for Cobra Mk III to be supplied to all successful pilot academy graduates as part of financial and insurance package.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Design Features===&lt;br /&gt;
The Cobra Mk III has attained a highly popular customer base due to the innovations in design within the spaceframe.&amp;lt;br/&amp;gt;These include:&lt;br /&gt;
*Revolutionary modular design of the internal workspace, since replicated out on license to other manufacturers.&lt;br /&gt;
*Superior structural integrity and inertial stability, even at high velocities.&lt;br /&gt;
*Comfort and luxury throughout the living area, with the new holoStim facilities fitted as standard.&lt;br /&gt;
&lt;br /&gt;
==Ship’s Systems==&lt;br /&gt;
===Bridge Systems===&lt;br /&gt;
====Astrogation Console====&lt;br /&gt;
::::::[[Image:Astro-console-gray.png|300px]]&lt;br /&gt;
The DL-A396 Astrogator Console is a fully integrated unit, and was retrofitted to most spaceframes between 3155 and 3159.  It is now the standard console type used by GalCop vessels, including those of the [[Galactic Navy]].&lt;br /&gt;
&lt;br /&gt;
The console features several multifunction displays (MFDs) and customisable controls.  The manufacturer, [[Aegidian Industries|Williams Avionics]], supplies the console with a default layout template, but users can customise the controls and displays as necessary.  The only display that retains a definite style is the local space scanner.&lt;br /&gt;
&lt;br /&gt;
The astrogator console is the interface to the astrogation computer that takes over the majority of the ship&amp;#039;s navigation controls. The most recent unit, introduced in 3170, is the Socam 103, which includes all the standard controls along with advanced thruster control, a more advanced AI and a newly updated personality interface. &lt;br /&gt;
&lt;br /&gt;
Standard responsibilities of the astrogation system are:&lt;br /&gt;
* Handling of relativistic space flight: advanced routines &amp;#039;hide&amp;#039; the relativistic aspect of real space flight from the pilot, presenting a simple dive/climb/roll control method and a simplified acceleration and deceleration control related to the primary stellar body in the vicinity of the ship.&lt;br /&gt;
* Docking procedures once within a space station.&lt;br /&gt;
* Basic IFF interrogation with nearby vessels.&lt;br /&gt;
* Tracking of stellar objects.&lt;br /&gt;
* Orientation and positioning for witchspace transit (formerly handled by the Orbitspace Authority on a manual basis).&lt;br /&gt;
&lt;br /&gt;
Note that any references to controls within this manual will refer to the default layout of the console controls as supplied by Williams Avionics. Also note that each control has been assigned a verbal command through the AI, and unless you have disabled this option you may use the appropriately assigned command.&lt;br /&gt;
&lt;br /&gt;
====Viewscreen====&lt;br /&gt;
:::[[Image:Viewscreen sample.png|800px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The view screen shows several items.  The HUD, at the bottom of the screen, is detailed in the next section. The central cross-hairs are used for accurate orientation of the ship during navigation and docking manoeuvres, as well as having obvious functions in combat. &lt;br /&gt;
&lt;br /&gt;
The Sanya Amiya TLF glare-reducing view screen shows a processed view of the exterior of the ship using feed from four digiFeed cameras mounted on the contours of the hull. The views are displayed at 4 terapixel resolution and are intelligently processed before being displayed to reduce glare from solar objects and to enhance the available light, allowing greater clarity.  During flight, the four available cameras are quickly selected:&lt;br /&gt;
*&amp;#039;&amp;#039;Forward View&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f1&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;1&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
*&amp;#039;&amp;#039;Aft View&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f2&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;2&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
*&amp;#039;&amp;#039;Port View&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f3&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;3&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
*&amp;#039;&amp;#039;Starboard View&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f4&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;4&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
Other view functions may also be called upon at any time, using the console:&lt;br /&gt;
*&amp;#039;&amp;#039;Status screen&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f5&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;5&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Displays present location and condition, fuel, economic and legal status, and lists the installed equipment.&lt;br /&gt;
*&amp;#039;&amp;#039;Manifest screen&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f5&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;5&amp;#039;&amp;#039;&amp;#039; twice&amp;lt;br/&amp;gt;Displays the contents of the hold, and any eventual contract commitments.&lt;br /&gt;
*&amp;#039;&amp;#039;Short Range Chart&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f6&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;6&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Shows a proximate [[Short Range Chart|system chart]] with quick-info and current hyperjump range perimeter with the available fuel.&lt;br /&gt;
*&amp;#039;&amp;#039;Galactic Chart&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f6&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;6&amp;#039;&amp;#039;&amp;#039; twice&amp;lt;br/&amp;gt;Shows the entire galactic sector and enables planet name-search.&lt;br /&gt;
*&amp;#039;&amp;#039;System Data screen&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f7&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;7&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Displays essential information on the present nearby system.&lt;br /&gt;
*&amp;#039;&amp;#039;Local Commodity Market&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f8&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;8&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Displays local market prices, although no interaction is possible unless docked.&lt;br /&gt;
&lt;br /&gt;
=====ID system=====&lt;br /&gt;
When engaged, the ship&amp;#039;s supplied ID system will select the first object to pass through the centre of the cross-hairs. If the selected object is a space vessel the computer will interrogate the vessel&amp;#039;s transponder and show the class of the ship. With a [[Scanner Targeting Enhancement]] installed, more information is available.&lt;br /&gt;
&lt;br /&gt;
The ID computer can be enabled by pressing &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;r&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; on the astrogation console. To deactivate, press &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;u&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;. To transfer an ID query to [[Pilot%27s_Reference_Manual#Pylon_weapon_indicators|Missile Target mode]], press &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;t&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=====Comms log=====&lt;br /&gt;
The view screen can also show communication logs as well as incoming communications. This is provided for pilots or crews who are hard of hearing or whose audio range is not supported by the standard audio set-up. An additional add-on is available from [[Aegidian Industries|Williams Avionics]] allowing system messages from throughout the ship to be displayed on-screen, and this is now being supplied as standard by [[Cowell &amp;amp; MgRath]].&lt;br /&gt;
&lt;br /&gt;
Incoming communiques are displayed forthcoming, but log transcripts may be recalled by pressing the button marked &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;&amp;amp;#126;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;, which will also indicate the transmission source on the [[IFF system]], if available within scanner range.&lt;br /&gt;
&lt;br /&gt;
===== Console messages log =====&lt;br /&gt;
These are messages from your ship&amp;#039;s computer concerning such things as missile locks, losing missile targets (due to extreme ranges), engaging fuel injectors &amp;#039;&amp;#039;et cetera&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=====Ship Camera=====&lt;br /&gt;
At any point, the selected video feed may be linked to an on-board photographic recorder which will preserve the momentary point of view for posterity. To engage the camera, press the default command &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;&amp;amp;#42;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
====In-dock services====&lt;br /&gt;
When docked, the computer connects to the local markets, making business transactions possible:&lt;br /&gt;
*&amp;#039;&amp;#039;Ship outfitting&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f3&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Lists equipment and services available for purchase and installment.&lt;br /&gt;
*&amp;#039;&amp;#039;Shipyard&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f3&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;3&amp;#039;&amp;#039;&amp;#039; twice&amp;lt;br/&amp;gt; Displays what vessels are for sale at the local dealership.&lt;br /&gt;
*&amp;#039;&amp;#039;Interfaces&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f4&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Shows all ship interfaces available, including access to all [[Contracts|carrier contracts]], for parcels, passengers and cargo. Select the type of contract you want to browse from the list, then use the menu to navigate the options. A system map will be displayed when each contract is viewed, revealing the destination of the contract.&lt;br /&gt;
*&amp;#039;&amp;#039;Local Commodity Market&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Press &amp;#039;&amp;#039;&amp;#039;f8&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;8&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;Shows local market prices of available goods, and offers the opportunity to buy and sell.&lt;br /&gt;
&lt;br /&gt;
====Heads-up Display (HUD)====&lt;br /&gt;
::[[Image:Oolite-numbered-hud.png|580px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The HUD uses holographic litePixel overlay to project essential details onto the main viewscreen, allowing the pilot the maximum available information with minimum eye movement (note that a [[Viewscreen vs Window debate]] exists!).&lt;br /&gt;
&lt;br /&gt;
Information shown on the standard HUD layout (pictured above) are outlined below:&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(1) Shield Strength&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
Shows  the effective charge in the twin Zieman deflector shields. These shields absorb energy by reflecting it with an equivalent charge of inverse energy. There are two generators for these shields, one forward and aft.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(2) Level indicators&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
From top to bottom:&lt;br /&gt;
*&amp;#039;&amp;#039;Witchspace Fuel&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Indicates how much [[Quirium]] fuel is left in the tanks. Using the [[Pilot%27s_Reference_Manual#Hyperdrive|Hyperdrive]] or the [[Witch_fuel_injectors |Fuel Injectors]] will decrease the amount of fuel on board. If a hyperjump destination is plotted on the [[Short Range Chart]], a needle will indicate how much of the available fuel will be required.&lt;br /&gt;
*&amp;#039;&amp;#039;Cabin Temperature&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;This scale reports the cabin temperature. This will rise when a ship nears the corona of a star or encounters too much atmospheric friction near the surface of a planet. If the temperature gets too high, the structure of the ship will begin to break down as the plating melts. If this begins to happen, the ship will explode.&lt;br /&gt;
*&amp;#039;&amp;#039;Laser Temperature&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Although ships do have a laser cooling system on board, coupled with the cooling matrix of each type of laser, rapid firing will still generate more heat than either system is capable of handling. This gauge will report how hot the laser is getting, and if the indicator reaches the top the laser will shut down until it cools.&lt;br /&gt;
*&amp;#039;&amp;#039;Altitude&amp;#039;&amp;#039; &amp;lt;br/&amp;gt;Indicates the height of a ship from a planetary body. The drive matrices in most ships are not usually sensitive enough to deal with atmospheric entry. As a result, ships may suffer catastrophic hull failure when coming into contact with a planet&amp;#039;s atmosphere. The altitude meter will indicate when the ship is becoming dangerously close to a planet&amp;#039;s surface. If the bar reaches the top, the ship&amp;#039;s structural integrity will be compromised. Some HUDs ([[Vimana HUD]], [[Vimana-X HUD]] &amp;amp; [[CB-HUD Mark IV]] include warning signs for low altitude - planets &amp;#039;&amp;#039;etc&amp;#039;&amp;#039; do not show up on your scanner, so if they are not visible in your viewscreen...).&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(3) Pylon weapon indicators&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
These indicators show the type and status of weapons attached to the external pylons of your ship. There are three types of armament that can be mounted, and these are distinguished by different icons on the HUD:&lt;br /&gt;
&lt;br /&gt;
*[[Image:Oolite-missile-icon.png|14px]] [[Missile]]&lt;br /&gt;
*[[Image:Oolite-ecmh-icon.png|14px]] [[ECM Hardened Missile]]&lt;br /&gt;
*[[Image:Oolite-mine-icon.png|14px]] [[Q bomb]]&lt;br /&gt;
&lt;br /&gt;
When shown with a yellow outline, the highlighted weapon is armed and ready to launch.&lt;br /&gt;
&lt;br /&gt;
To arm a missile, hit &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;t&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; on your console. To disarm, press &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;u&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;, or switch back to [[Pilot%27s_Reference_Manual#ID_system|ID mode]] by pressing &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;r&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;.  To fire, press &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;m&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
A [[Multi-Targeting System]] may be purchased and installed, to select several simultaneous targets.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(4) Aegis&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
When this &amp;#039;&amp;#039;S&amp;#039;&amp;#039; is displayed, the ship is within the control zone of a space station, inside its protective &amp;#039;&amp;#039;Aegis&amp;#039;&amp;#039;. Any pirate activity detected within this zone will be met by immediate response from members of the Galactic Police. Crimes committed in the aegis are more likely to be registered by the [[GalCops]].&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(5) Mass Lock/Status indicator&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
This pulsating lamp shows the status of your ship. If it is green, the radar is clear, and the [[Torus Drive|Torus Jump Drive]] may be activated. If it is yellow, there are other vessels or powered objects in the nearby vicinity, and the Jump Drive is inhibited. If it is red, there is a danger to your ship: a hostile may have target-locked your ship, your energy reserves may be very low, you may be at too low an altitude, or your cabin temperature may be approaching a dangerous level.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(6) Short-range Scanner&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
The scanner is the pilot’s overview of the world outside, and is a protected design, patented by Brell and Baben in 3084, running the [[IFF system]] on a 3D representation of space in a 30 km radius of the ship.&lt;br /&gt;
&lt;br /&gt;
The three dimensions are represented via an elliptical display showing the horizontal plane plus the use of ‘tails’ on each scanner blip to indicate the vertical position in relation to the scanning ship’s position. To make further use of this tool, see 8, [[Pilot%27s_Reference_Manual#Scanner_Zoom_Factor|Scanner Zoom Factor]].&lt;br /&gt;
&lt;br /&gt;
Note that suns, planets &amp;amp; moons do not register on your scanner (remember to keep an eye on your altitude gauge is this is the case!).&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(7) Galactic Standard Time indicator&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
Displays the current date and time in galactic [[Time|meanTime]], the standard notation for recording time in space. It is used because it does not rely on point of reference like planetary rotations.  Upon exiting witchspace, the clock will temporarily enter update mode to synchronise with the local time signal as broadcast by all witchspace beacons. This is necessary due to the small amount of relative time distortion experienced during witchspace transit.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(8) Scanner Zoom Factor&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
This shows the zoom factor of the scanner, from 1:1 (normal scale) to 1:5 (macro scale). The key marked &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;z&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; on your console will toggle through the zoom factors.&lt;br /&gt;
&lt;br /&gt;
Note that an optional ultrazoom 1:1 &amp;lt;&amp;gt; 1:16 scale is also possible (as is a non-linear logarithmic scaling) - see [[HUDSelector]] for more detail.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(9) Space Compass&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
There are two space compasses available for your HUD. Your ship is fitted with the basic version. It tracks a single object, intelligently choosing which would be the more relevant. Upon entry to a system it will automatically track the location of the nearby planet.  &lt;br /&gt;
* [[Image:OoASC-plr.png|50px|]] nearby planet directly ahead. &lt;br /&gt;
* [[Image:OoASC-plf.png|50px|]] nearby planet directly aft. &lt;br /&gt;
When the world&amp;#039;s space station is detected, the compass will track that instead. The [[Advanced Space Compass]] may be purchased to offer further options (registering other beacons).&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(10) Relative Speed indicator&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
The speed indicator show s the ship&amp;#039;s relative velocity through space using the [[Pilot%27s_Reference_Manual#System_drive|System drive]]. Through advanced AI and engineering technology, much of the hard work of space flight has been removed from the pilot and made the speciality of the flight computers on board the ship. This means that a simple relative speed indicator is all that is needed to calculate the ship&amp;#039;s speed in relation to the major bodies of the system.&lt;br /&gt;
&lt;br /&gt;
A simple control method will increase and decrease the ship&amp;#039;s movement from a standstill to speeds in excess of 0.3 light Mach. Use the &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;w&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; and &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;s&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; controls on your console to increase or decrease your speed respectively. &lt;br /&gt;
&lt;br /&gt;
To further enhance your ship&amp;#039;s speed performance, consider installing [[Witch fuel injectors]].&lt;br /&gt;
&lt;br /&gt;
There are some HUDs which give an absolute scale for speed - see the speed column on the [[Guide to HUDs]] wiki page.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(11) Roll/Pitch indicators&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
These scales show the ship&amp;#039;s roll rate about the axis of travel (the central dot will move to the right of centre when the ship is rolling clockwise, to the left if counterclockwise), and the thrust levels in the vertical axis (the central dot will move left when in a dive attitude, and right when climbing). These are useful when calibrating directional controls following a systems upgrade or an avionics failure. &lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;(12) Energy Level Indicators&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
These bars show the amount of energy stored in the solar capacitors. They are used primarily to power the ship&amp;#039;s systems, including the structural integrity field, life support system and lasers, as well as auxiliary systems such as cargo loading systems and communications.  Ships can have between 2 and 7 capacitors, and energy will drain from them in numerical order as the ship takes damage. Hull damage will reduce these levels as the autoRepair systems seal hull breaches. If the last energy cell is depleted, the hull&amp;#039;s damage will cease to be sealed and the structural integrity field will collapse, normally resulting in explosion with the final laser hit.&lt;br /&gt;
&lt;br /&gt;
These cells will recharge using solar energy when the ship is in cruise mode.&lt;br /&gt;
&lt;br /&gt;
An [[Extra Energy Unit]] is available for purchase which will improve the recharge rate of the energy cells.&lt;br /&gt;
&lt;br /&gt;
=====&amp;#039;&amp;#039;&amp;#039;Fuel Scoop Status Indicator&amp;#039;&amp;#039;&amp;#039;=====&lt;br /&gt;
This icon, only visible when [[Fuel Scoops]] are fitted, is located between the Forward Shield Strength indicator and the Short-range Scanner on the Cobra Mark III. The Fuel Scoops Status Indicator has the twin function of indicating when the Fuel Scoops are in operation and also when the Cargo Bay is filled to capacity.&lt;br /&gt;
&lt;br /&gt;
* [[Image:Fuel_Scoops_Icon.png|50px|]] The Fuel Scoop Icon.&lt;br /&gt;
&lt;br /&gt;
====mediStim Bay====&lt;br /&gt;
The mediStim system, provided by Synapse Biotech, provides emergency medical treatment for the commander and crew of a ship. The system can often be the difference between life and death for an injured crew member, and provides first aid and basic life-support until the patient can reach a fully equipped hospital ship or medical centre.&lt;br /&gt;
&lt;br /&gt;
The system is normally stowed against a bulkhead, but will open out into a padded treatment table with standard medical supplies and a medical reference commPad. For lone pilots, a medical servitor droid can be purchased as an upgrade, and is capable of performing many forms of treatment depending on the AI package purchased with the unit.&lt;br /&gt;
&lt;br /&gt;
See the speculation at [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=21325 Using the ship&amp;#039;s mediStim Bay]&lt;br /&gt;
&lt;br /&gt;
=====Equipment Locker=====&lt;br /&gt;
The equipment locker contains many items of personal equipment essential for the space traveller.  The following are supplied as standard:&lt;br /&gt;
&lt;br /&gt;
=====commPads=====&lt;br /&gt;
These are personal communications devices that contain a library system. A standard commPad can uplink to most communications mediums, including holoNets, hyperNets and thruSpace comms grids. They can be customised for particular functions and contain 3.1 terabytes of storage space.  Specialised variants are available, including the medical commPad mentioned above, and a galactic trader&amp;#039;s variant which incorporates a neural link translation program and catalogued trade routes, amongst other things.&lt;br /&gt;
&lt;br /&gt;
=====remLock masks=====&lt;br /&gt;
The last line of defence against pirates is often the remLock mask. When one of these is worn, in the event of the wearer being cast into the vacuum of space, the mask shoots a polyfibre cocoon around the wearer and begins a life support cycle. The latest version, upgraded after a decade, contains memnSomn software, placing the wearer into a state of suspended awareness to avoid the discomforting experience of being exposed to vacuum.&lt;br /&gt;
&lt;br /&gt;
=====Maintenance Tools=====&lt;br /&gt;
Essential tools for performing repairs or adjustments on ship&amp;#039;s systems.&lt;br /&gt;
&lt;br /&gt;
=====Manuals=====&lt;br /&gt;
This manual, plus other essential operating or cultural manuals, with room for many more in a customised expandable file.&lt;br /&gt;
&lt;br /&gt;
In addition to the standard equipment outlined above, the locker has room for many other things, including personal weaponry, clothing and spare parts.&lt;br /&gt;
&lt;br /&gt;
===Living Section===&lt;br /&gt;
Located just below the bridge and accessible via a gravity well, the living section is where the pilot and co-pilot will spend their time when not in command of the vessel.&lt;br /&gt;
&lt;br /&gt;
The living quarters were designed for comfort and maximum relaxation, and contain equipment intended to provide all the comforts of a planetside environment.&lt;br /&gt;
&lt;br /&gt;
The sleeping area is towards the fore of the living section, and contains a gravSomn flotation sleep field to provide maximum support and comfort as the field contours to the body no matter what the sleeping position.  Bedding is supplied, and the autoHygiene units within the frame will launder and sterilise all fabrics.&lt;br /&gt;
&lt;br /&gt;
The relaxation area contains a full synPleasure facility, including relaxaPads and sensory immersion suite, providing a homesick commander with all the sights, sounds and smells of home.&lt;br /&gt;
&lt;br /&gt;
The hygiene facilities are tailored for all species, providing washroom and waste management of any variety. Water and sonic showers are both fitted as standard, and optional extras include sulphuric showers and decontamination facilities.&lt;br /&gt;
&lt;br /&gt;
The atmospheric processors tied to the living quarters can be set independently of those for the rest of the ship, allowing the pilot to transfer passengers from alternate atmospheric conditions with ease. There is a double airlock door fitted to the rear of the living section, joining directly to the cargo bay.&lt;br /&gt;
&lt;br /&gt;
===Cargo Bay===&lt;br /&gt;
The Cobra Mk III cargo hold offers room to support freight of 20t of standard [[Cargo_Container_(Oolite)|cargo cannisters]]. Should this prove to be insufficient, there exists a solution in undertaking a [[Cargo Bay expansion]], which is not terribly expensive or technologically advanced, but does take some time. &lt;br /&gt;
&lt;br /&gt;
From the bridge, all Cargo Bay functions are controlled by the Tichy CargoMate, often informally referred to as &amp;quot;the Librarian&amp;quot;, as it is relied upon to keep all cargo indexed and updated to the ship&amp;#039;s manifest, and using its C-claws, keep all cargo stacked and organized in the most practical manner possible. &lt;br /&gt;
&lt;br /&gt;
Should the need arise to jettison cargo mid-flight, this action is prompted by pressing &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;shift-d&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;. It is always advisable, however, to toggle through the Tichy&amp;#039;s register first, by pressing &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;shift-r&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;, to be certain it is the desired cargo that is next in line for ejection.&lt;br /&gt;
&lt;br /&gt;
===Engineering===&lt;br /&gt;
====Engines====&lt;br /&gt;
=====System drive=====&lt;br /&gt;
The ionic repulsion drive is the standard mode of conveyance for most space vessels. The Cobra Mk III is fitted with two Kruger “lightfast” motors, each capable of 1.21 gigawatts power. This provides a top speed of just over 30% light speed.&lt;br /&gt;
&lt;br /&gt;
The motors are mounted either side of the ship&amp;#039;s centreline in approximately the centre of the engineering section at the rear of the ship. The large plasma vents allow maximum yield of charged particles from the motors.&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;w&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; and &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;s&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; controls on your console will increase or decrease the velocity. &lt;br /&gt;
&lt;br /&gt;
=====Hyperdrive=====&lt;br /&gt;
The Irrikan Thruspace drive is one of the smallest and most efficient hyperdrives on the market. The twin generators take up only 15 cubic metres of space onboard, and the quirium matrix reactor is one of the most efficient on the market today. Recent upgrades in the reactant injector assemblies have meant that the drive is less prone to misjumps: welcome news for those battle-scarred pilots who have been dumped in the middle of a [[Thargoids|Thargoid]] war zone far too often.&lt;br /&gt;
&lt;br /&gt;
The standard control for initiating a hyperjump is marked &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;h&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; on the astrogation console, once a destination is plotted on the [[Short Range Chart]]. The same command may be used to abort a hyperjump during the countdown. Note that a hyperjump may fail if attempted too close to a large body.&lt;br /&gt;
&lt;br /&gt;
=====Torus Jump Drive=====&lt;br /&gt;
The so-called [[Torus Drive]], also known as a flux distortion drive or simply a Jump drive, physically changes the inertial mass of an object by projecting a gravitic field around it. This means that any vessel fitted with one can achieve approximately three times the speed normally achievable with the system drive.  The downside of this is that the ship is vulnerable to collision with asteroidal bodies that penetrate the gravitic field. The field itself is disrupted by the passage of other system drives within the field, resulting in the vessel being &amp;#039;dumped&amp;#039; back into normal space.&lt;br /&gt;
&lt;br /&gt;
The standard control for activating or deactivating this drive is marked &amp;lt;font size=&amp;quot;3&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;j&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; on the astrogation console.&lt;br /&gt;
&lt;br /&gt;
====Computers====&lt;br /&gt;
The Cobra Mk III is fitted as standard with a Rackham Pell NT901 System and Flight Control computer with a level 3 dynamic artificial intelligence system.  This provides complete peace of mind to the pilot as the system can control most aspects of the ship&amp;#039;s performance.  The computer has a fully featured navigation and flight logic system installed, and has the latest version of the Lind M4 hyperspace transit control software, which allows the ship to handle the complex calculations needed for hyperspace trajectories.&lt;br /&gt;
&lt;br /&gt;
The NT901 has a Humanised personality program, providing the owner with a unique companion during each trip. The program learns how to behave based on the personality and responses of the pilot, and can be an invaluable companion to lone pilots during long-haul flights.  Many pilots retain the personality program (usually backing it up to a commPad) and install it on any ship they own.&lt;br /&gt;
&lt;br /&gt;
The Engineering system is tied into the NT901, but also has an independent monitoring system to provide a fail-safe in case of catastrophic incidents.  The system handles damage control, thruster control and monitoring of the drives and their fuel.&lt;br /&gt;
&lt;br /&gt;
====Life Support====&lt;br /&gt;
Life Support systems comprise of the atmospheric processing systems, the waste management systems and the recycling plant. These systems are all tied together through a central core system containing a molecular resequencer that purifies and cleans the matter that is passed through it.&lt;br /&gt;
&lt;br /&gt;
The atmospheric system is the most advanced part of the system, including complex monitoring and control routines that constantly sample the air quality. It immediately isolates foreign bodies, including viruses, bacteria and other non-standard particles, then filters them out to the resequencer.&lt;br /&gt;
&lt;br /&gt;
Likewise, waste matter is passed to the resequencer and recycled through the system to wherever it is needed. It is this system that powers the food processors onboard the ship.&lt;br /&gt;
&lt;br /&gt;
The life support system fitted to Cobras, and indeed most other ships, operates at a tenth of its maximum capacity. This allows for power outages and permits the addition of additional passenger berths without the need to upgrade the life support systems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Shipboard Upgrades==&lt;br /&gt;
*For a full list of available upgrades, see the [[Oolite Equipment]] section of the Wiki.&lt;br /&gt;
*For notes on priming optional OXP equipment see [[Priming Equipment]]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=9756 Oolite Manual] (BB Thread for this wiki page - 2005-6 with much later suggestions)&lt;br /&gt;
*[[User:Selezen|Selezen]] - primary author&lt;br /&gt;
*[[Ship&amp;#039;s Library OXP]] contains an in-game dynamic Ship&amp;#039;s Manual (2013)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]][[Category:Help pages]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=CB-HUD_Mark_IV&amp;diff=90353</id>
		<title>CB-HUD Mark IV</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=CB-HUD_Mark_IV&amp;diff=90353"/>
		<updated>2026-10-24T18:20:50Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added pretty picture&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A clean, balanced HUD featuring detailed flight instruments, equipment indicators, combat warnings and compact target information. It requires no other OXPs.&lt;br /&gt;
[[File:Cb68-CB-HUD-Mark-IV.jpg|right|900px]]&lt;br /&gt;
==Overview==&lt;br /&gt;
The CB-HUD Mark IV is developed and produced by the [[Crab Boolean Corporation|Crab-Boolean Corporation]] located on [[Sector1/Riredi|Riredi]] in galaxy 1.  &lt;br /&gt;
&lt;br /&gt;
=== Features ===&lt;br /&gt;
A station-aware docking clearance light keeps your docking status visible, while a dedicated docked layout shows the information you need during your station visit.&lt;br /&gt;
&lt;br /&gt;
Compact flight instruments, adaptive energy divisions, absolute shield percentages, speed/altitude/cabin/weapon-temperature readouts, fuel and jump destination, basic/advanced compass and native joystick sensitivity indicator.&lt;br /&gt;
&lt;br /&gt;
Equipment indicators cover docking computer, escape pod, ECM and injectors.&lt;br /&gt;
&lt;br /&gt;
Master alert and rotating Alerts cover equipment damage, maintenance, contraband and legal warnings. Cargo and relevant station information remain visible docked; missile pylons remain visible there even with weapons offline.&lt;br /&gt;
&lt;br /&gt;
Four warning rows left of the crosshair show incoming missiles, forward/aft shield warnings and low/critical energy. Lamps blink; text stays steady.&lt;br /&gt;
&lt;br /&gt;
Four target rows on the right show unique name (if available), type/legal state, distance with Closing/Opening/Steady, and Condition: Good, Weak or Crit.&lt;br /&gt;
&lt;br /&gt;
Both blocks use 10x10 text with a fixed edge facing the crosshair.&lt;br /&gt;
&lt;br /&gt;
*10 [[MFD]]s&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
*The layout is designed for 16:10; other aspect ratios may leave less room for side MFDs.&lt;br /&gt;
&lt;br /&gt;
[[File:Cb68ch-CB-HUD-Mark IV.png|right|thumb|600px|Screenshot showing 10 [[MFD]]s (configured for [[Stranger&amp;#039;s World]]). Click to enlarge.&amp;lt;br&amp;gt;Note that the yellow fuel gauge includes the Fuel Tank&amp;#039;s added 3LY, that the green cabin temperature gauge mentions the included heat shields and that the light blue shield gauges include the effects of the Military Shield Enhancement]] &lt;br /&gt;
=== Warning thresholds ===&lt;br /&gt;
*Own shield percentages always use 128 energy points as 100%, regardless of shield upgrades. Weak below 40%, clears at 50%; down at zero, back to weak at 10%.&lt;br /&gt;
*Own energy: low below 25%, clears at 30%; critical below 15%, back to low at 20%.&lt;br /&gt;
*Target condition uses that target&amp;#039;s maximum: Weak below 40%, Good at 45%;&lt;br /&gt;
*Crit below 15%, back to Weak at 20%. Target condition is energy, not OXP shields.&lt;br /&gt;
&lt;br /&gt;
=== Docking light (D) ===&lt;br /&gt;
:Orange: no known clearance. &lt;br /&gt;
::Blinking orange: requested, waiting.&lt;br /&gt;
:Green: clearance granted or this station explicitly requires none.&lt;br /&gt;
::Blinking green: clearance expires soon. The white D and outline stay steady.&lt;br /&gt;
&lt;br /&gt;
The selected station takes priority. Selecting another station does not inherit the first station&amp;#039;s clearance. With no station selected, an active request is retained; otherwise the main station is used while within its [[aegis]].&lt;br /&gt;
&lt;br /&gt;
Green is about clearance, not collision avoidance, traffic or dock size.&lt;br /&gt;
&lt;br /&gt;
=== Optional OXP support ===&lt;br /&gt;
*[[HUDSelector]], Smivs&amp;#039; [[Extra Fuel Tanks]] and [[Shield Equalizer And Capacitors OXP]] are optional.&lt;br /&gt;
*[[CombatMFD]] is &amp;#039;&amp;#039;not&amp;#039;&amp;#039; required; its data sources and other OXP scripts are untouched.&lt;br /&gt;
*[[Shield Cycler]] 1.12 and Shield Cycler Next 2.1/2.1.1 can show their live mode: the upper former Equalized label says Cycler mode:, the lower shows the mode. &amp;quot;Disabled&amp;quot; is shown when switched off. Reduced functionality can still operate.&lt;br /&gt;
:Only install one Cycler branch. Unknown versions/data omit the mode display. The adapter reads the internal state defensively; it never controls shield transfer.&lt;br /&gt;
&lt;br /&gt;
==Minimum requirements==&lt;br /&gt;
*Oolite 1.86+&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
&lt;br /&gt;
=== Monitor Resolution ===&lt;br /&gt;
This HUD works best 16:10. Other resolutions work, but little space may be left for left and right MFD´s.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
Place CB-HUD-Mark-IV-1.0.0.oxz in the normal Oolite AddOns location. Keep only one Mark-IV version active. Mark III may remain installed. Select Mark IV through HUDSelector if it is installed. Without HUDSelector, Mark IV activates automatically. The original Mark III uses the Default HUD entry rather than a separate named entry; another default-HUD replacement can affect that selection. Reload Oolite&amp;#039;s configuration (rebuild its cache when necessary). This package does not install itself.&lt;br /&gt;
=== Compatibility and Testing ===&lt;br /&gt;
Automated tests cover warning thresholds, docking state, text configuration, optional integrations and HUD lifecycle. Standalone startup, HUD selection,&lt;br /&gt;
selection preservation and ship purchase were checked in a simulated Oolite JavaScript environment, also using the unmodified HUDSelector 1.28 package&amp;#039;s script. These checks supplement in-game testing; they do not emulate rendering.&lt;br /&gt;
&lt;br /&gt;
The minimum Oolite version 1.86 is based on a native source/API audit. In-game 1.86 testing and in-game Shield Cycler testing have not been performed. Standard incoming missile events/scan class are supported; unusual script-only missile behaviour may differ.&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
=== Current version ===&lt;br /&gt;
* Version 1.0 [https://app.box.com/s/0fxma53oqutfkjli7zq25kf8hno6gicz oolite.oxp.captain_beatnik.CB-HUD_mark_iv.oxz]&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
*License: CC-BY-NC-SA 4.0&lt;br /&gt;
=== Attribution and Thanks ===&lt;br /&gt;
CB-HUD Mark IV by Captain Beatnik is derived from CB-HUD Mark III and the original configuration files supplied with Oolite.&lt;br /&gt;
&lt;br /&gt;
Many thanks to Giles C Williams (aegidian) and all contributors for developing Oolite.&lt;br /&gt;
&lt;br /&gt;
Thanks to Mazur, Thargoid, Killer Wolf, JeffBTX, Wyvern, Smivs and CommonSenseOTB.&lt;br /&gt;
I learned a great deal by studying their work.&lt;br /&gt;
&lt;br /&gt;
Special thanks to Norby, Phkb, Cag and Neelix. Their work made the additional functions of this HUD possible.&lt;br /&gt;
&lt;br /&gt;
Finally, many thanks to Cholmondely and Maik for their work on the wiki and documentation.&lt;br /&gt;
&lt;br /&gt;
These acknowledgements are also retained in Config/cb68_cbhudIV_main.plist.&lt;br /&gt;
&lt;br /&gt;
=== Development Assistance ===&lt;br /&gt;
OpenAI Codex, an AI coding assistant, assisted with JavaScript, configuration, code review and documentation. The HUD concept, design decisions and in-game testing are by Captain Beatnik.&lt;br /&gt;
&lt;br /&gt;
== The [[Dark Side]] ==&lt;br /&gt;
Everything is drawn using scripts and configuration — there are no additional image files!&lt;br /&gt;
=== Text Customisation ===&lt;br /&gt;
All own visible text, units and templates are in the Config folder&amp;#039;s [[Descriptions.plist]].&lt;br /&gt;
&lt;br /&gt;
Edit quoted values while retaining the namespaced keys and placeholders needed.&lt;br /&gt;
&lt;br /&gt;
Empty strings and leading/trailing spaces are valid; blanking text does not disable warnings, lamps or equipment. Longer translations need visual testing.&lt;br /&gt;
&lt;br /&gt;
Target text has a width limit; type shortening preserves the default bounty Cr suffix. Dock system/station names share a 36-character budget including dots.&lt;br /&gt;
&lt;br /&gt;
=== How the HUD is built ===&lt;br /&gt;
The HUD needs no additional image files or textures. Its layout, instruments, scale marks and crosshairs are defined through JavaScript and the .plist configuration, using Oolite&amp;#039;s built-in drawing functions and font. No Images or Textures folder is included in the package.&lt;br /&gt;
&lt;br /&gt;
Config/cb68_cbhudIV_main.plist has no legends section. All Mark-IV-defined labels and readouts use &amp;lt;tt&amp;gt;drawCustomText&amp;lt;/tt&amp;gt;: dials, with their text supplied from Config/descriptions.plist through the script. Native displays such as the clock and equipment carousel continue to draw their own text.&lt;br /&gt;
&lt;br /&gt;
Oolite draws legends before dials, then processes the dials in their listed order. Placing custom text and scale elements later in that list lets them appear in front of the filled instrument bars. A legend cannot provide that foreground layer over a dial. Scale lines are drawn as narrow custom bars, not as images.&lt;br /&gt;
&lt;br /&gt;
The left-hand shield, energy and weapon-temperature bars fill from right to left. This uses a negative width in the relevant dial definition, for example&lt;br /&gt;
&amp;lt;tt&amp;gt;width = -98;&amp;lt;/tt&amp;gt; for the shield bars. The magnitude specifies the bar width and the negative sign reverses its fill direction. Optional capacitor bars use the same technique. This makes the left and right instrument groups visually mirror one another without needing separate artwork.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*Author: [[User:Captain Beatnik|Captain Beatnik]] (page has links to his other HUDs)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=307272#p307272 BB Release Note for Mark IV] (2026)&lt;br /&gt;
:Feedback is always welcome if something doesn&amp;#039;t work or where something could or should be improved or done differently.&lt;br /&gt;
*[[CB-HUD Mark III]] (2025-6) previous version!&lt;br /&gt;
*[[CB-HUD Mark II]] (2011) popular precursor (includes notes on CB-HUD Mark I).&lt;br /&gt;
*[[HUD]]&lt;br /&gt;
*[[hud.plist]]&lt;br /&gt;
&lt;br /&gt;
{{HUD-OXP}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=File:Cb68ch-CB-HUD-Mark_IV.png&amp;diff=90352</id>
		<title>File:Cb68ch-CB-HUD-Mark IV.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=File:Cb68ch-CB-HUD-Mark_IV.png&amp;diff=90352"/>
		<updated>2026-10-24T18:11:45Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Another crummy Cholmondeley Screen Shot&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Another crummy Cholmondeley Screen Shot&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Oolite_JavaScript_Reference:_Ship_script_event_handlers&amp;diff=90349</id>
		<title>Oolite JavaScript Reference: Ship script event handlers</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Oolite_JavaScript_Reference:_Ship_script_event_handlers&amp;diff=90349"/>
		<updated>2026-10-17T21:36:06Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* shipTakingDamage */ Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].&lt;br /&gt;
&lt;br /&gt;
Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.&lt;br /&gt;
&lt;br /&gt;
The list of event handlers will change from version to version (usually additions of extra handlers). For this reason, any variables or functions you create as &amp;lt;code&amp;gt;this.variable&amp;lt;/code&amp;gt; should have a name beginning with &amp;#039;_&amp;#039; or &amp;#039;$&amp;#039; - e.g. &amp;lt;code&amp;gt;this._variable&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;this.$variable&amp;lt;/code&amp;gt; - to avoid potential conflicts with future event handlers.&lt;br /&gt;
&lt;br /&gt;
Note that a ship script event which affects the player ship (therefore not those marked NPC only, station only, etc.) will also appear as a [[Oolite JavaScript Reference: World script event handlers|world script event]].&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.79 onwards, each ship has two scripts: the &amp;quot;ship script&amp;quot; as in previous versions (&amp;lt;code&amp;gt;ship.script&amp;lt;/code&amp;gt;) and an AI script (&amp;lt;code&amp;gt;ship.AIScript&amp;lt;/code&amp;gt;) which manages [[Oolite Javascript Reference: PriorityAI Documentation|Javascript-based AI]]. The former is intended for constant events related to the ship itself, and the latter is intended for event handling which varies based on what the ship is currently doing. Both scripts receive all events which do not expect a return value. Events expecting a return value are sent to the ship script &amp;#039;&amp;#039;only&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Docking ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWillDockWithStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWillDockWithStation&amp;lt;/code&amp;gt; handler is called at the beginning of the docking tunnel effect.&lt;br /&gt;
&lt;br /&gt;
 this.shipWillDockWithStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
At this moment &amp;quot;ship.dockedStation == nil&amp;quot;, &amp;quot;ship.status == STATUS_DOCKING&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipDockedWithStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipDockedWithStation&amp;lt;/code&amp;gt; handler is called at the end of the docking tunnel effect.&lt;br /&gt;
&lt;br /&gt;
 this.shipDockedWithStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
At this moment &amp;quot;ship.dockedStation == the station&amp;quot;, &amp;quot;ship.status == STATUS_DOCKED&amp;quot; and &amp;quot;gui_screen&amp;quot; is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWillLaunchFromStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
This handler was added for npc ships with test release 1.75, before it was a worldScript only handler.&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWillLaunchFromStation&amp;lt;/code&amp;gt; handler is called for ship scripts on ship creation, before the shipSpawned event. &lt;br /&gt;
&lt;br /&gt;
 this.shipWillLaunchFromStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLaunchedFromStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLaunchedFromStation&amp;lt;/code&amp;gt; handler is called at the end of the launch tract, when the ship has clearly left the station and AI updating begins.&lt;br /&gt;
&lt;br /&gt;
 this.shipLaunchedFromStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationWithdrewDockingClearance&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationWithdrewDockingClearance&amp;lt;/code&amp;gt; handler is received when the station the ship is trying to dock with unexpectedly withdraws clearance (e.g. if &amp;lt;code&amp;gt;station.abortAllDockings&amp;lt;/code&amp;gt; is called).&lt;br /&gt;
&lt;br /&gt;
 this.stationWithdrewDockingClearance = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Witchspace Jumps ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;playerWillEnterWitchspace&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;playerWillEnterWitchspace&amp;lt;/code&amp;gt; handler is called just before a witchspace jump starts and after the &amp;lt;code&amp;gt;shipWillEnterWitchspace&amp;lt;/code&amp;gt; handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)&lt;br /&gt;
&lt;br /&gt;
 this.playerWillEnterWitchspace = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipExitedWormhole&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipExitedWormhole&amp;lt;/code&amp;gt; handler is called when a ship exits a wormhole.&lt;br /&gt;
&lt;br /&gt;
 this.shipExitedWormhole = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWillEnterWormhole&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWillEnterWormhole&amp;lt;/code&amp;gt; handler is called when a ship enters a wormhole. only&lt;br /&gt;
&lt;br /&gt;
 this.shipWillEnterWormhole = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWitchspaceBlocked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWitchspaceBlocked&amp;lt;/code&amp;gt; handler is called when a ship is prevented from entering witchspace by the presence of a nearby large mass. The blocking object is passed as a parameter&lt;br /&gt;
&lt;br /&gt;
 this.shipWitchspaceBlocked = function(blocker)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;wormholeSuggested&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;wormholeSuggested&amp;lt;/code&amp;gt; handler is called when another ship enters witchspace and suggests that this ship follows. The wormhole used is passed as a parameter. This is most commonly called when a group leader enters witchspace and wishes to take its escorts with it.&lt;br /&gt;
&lt;br /&gt;
 this.wormholeSuggested = function(wormhole)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Enter/Exit Aegis ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnteredStationAegis&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnteredStationAegis&amp;lt;/code&amp;gt; handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don&amp;#039;t give aegis messages.&lt;br /&gt;
&lt;br /&gt;
 this.shipEnteredStationAegis = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipExitedStationAegis&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipExitedStationAegis&amp;lt;/code&amp;gt; handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).&lt;br /&gt;
&lt;br /&gt;
 this.shipExitedStationAegis = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnteredPlanetaryVicinity&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnteredPlanetaryVicinity&amp;lt;/code&amp;gt; handler is called when the player enters the planet aegis (3x planet radius).&lt;br /&gt;
&lt;br /&gt;
 this.shipEnteredPlanetaryVicinity = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipExitedPlanetaryVicinity&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipExitedPlanetaryVicinity&amp;lt;/code&amp;gt; handler is called when the player leaves the planet aegis (3x planet radius).&lt;br /&gt;
&lt;br /&gt;
 this.shipExitedPlanetaryVicinity = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipApproachingPlanetSurface&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipApproachingPlanetSurface&amp;lt;/code&amp;gt; handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).&lt;br /&gt;
&lt;br /&gt;
 this.shipApproachingPlanetSurface = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLeavingPlanetSurface&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLeavingPlanetSurface&amp;lt;/code&amp;gt; handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).&lt;br /&gt;
&lt;br /&gt;
 this.shipLeavingPlanetSurface = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Combat ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;cascadeWeaponDetected&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;cascadeWeaponDetected&amp;lt;/code&amp;gt; handler fires when a Q-bomb (or equivalent device) detonates within scanner range of the player. The stock Q-mine (and potentially OXP equivalents) will also send this handler at the start of the countdown, giving ships more time to react. The weapon entity will be passed as a parameter.&lt;br /&gt;
&lt;br /&gt;
 this.cascadeWeaponDetected = function(weapon)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;defenseTargetDestroyed&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;defenseTargetDestroyed&amp;lt;/code&amp;gt; handler is sent when a defense (i.e. secondary) target is destroyed. A reference to the destroyed ship (which will become invalid shortly) is passed as a parameter.&lt;br /&gt;
&lt;br /&gt;
 this.defenseTargetDestroyed = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortAttack&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortAttack&amp;lt;/code&amp;gt; handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.&lt;br /&gt;
&lt;br /&gt;
 this.escortAttack = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;helpRequestReceived&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;helpRequestReceived&amp;lt;/code&amp;gt; handler is sent when an ally of this ship is being attacked and requires help. There are two parameters, the ally and the enemy.&lt;br /&gt;
&lt;br /&gt;
 this.helpRequestReceived = function(ally, enemy)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAttackedOther&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74.2}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAttackedOther&amp;lt;/code&amp;gt; handler is called when this ship hits another with a laser shot. &amp;lt;code&amp;gt;other&amp;lt;/code&amp;gt; is the identity of the ship being hit.&lt;br /&gt;
&lt;br /&gt;
 this.shipAttackedOther = function(other)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAttackedWithMissile&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAttackedWithMissile&amp;lt;/code&amp;gt; handler is called when a missile is fired. &amp;lt;code&amp;gt;missile&amp;lt;/code&amp;gt; contains the missile entity and &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that launched the missile.&lt;br /&gt;
&lt;br /&gt;
 this.shipAttackedWithMissile = function(missile, whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAttackerDistracted&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAttackerDistracted&amp;lt;/code&amp;gt; handler is called when the ship&amp;#039;s current attacker is distracted by another ship. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; contains the ship which is doing the distracting.&lt;br /&gt;
&lt;br /&gt;
 this.shipAttackerDistracted = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBeingAttacked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBeingAttacked&amp;lt;/code&amp;gt; handler is called when a laser shot  hits. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that attacked.&lt;br /&gt;
&lt;br /&gt;
 this.shipBeingAttacked = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?t=18607 Monitoring attacks with more detail than just &amp;quot;shipTakingDamage&amp;quot;/&amp;quot;shipBeingAttacked&amp;quot;] (2017)&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBeingAttackedByCloaked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBeingAttackedByCloaked&amp;lt;/code&amp;gt; handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.&lt;br /&gt;
&lt;br /&gt;
 this.shipBeingAttackedByCloaked = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBeingAttackedUnsuccessfully&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBeingAttackedUnsuccessfully&amp;lt;/code&amp;gt; handler is called when a laser shot narrowly misses the ship, when fired by an uncloaked ship intending to hit. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that attacked.&lt;br /&gt;
&lt;br /&gt;
 this.shipBeingAttackedUnsuccessfully = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCloakActivated&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCloakActivated&amp;lt;/code&amp;gt; handler is called whenever the script&amp;#039;s target ship activates its cloaking device. No parameters are required for this handler.&lt;br /&gt;
&lt;br /&gt;
  this.shipCloakActivated = function()&lt;br /&gt;
  {&lt;br /&gt;
     // Your code here&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCloakDeactivated&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCloakDeactivated&amp;lt;/code&amp;gt; handler is called whenever the script&amp;#039;s target ship deactivates its cloaking device. No parameters are required for this handler.&lt;br /&gt;
&lt;br /&gt;
  this.shipCloakDeactivated = function()&lt;br /&gt;
  {&lt;br /&gt;
     // Your code here&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetDestroyed&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetDestroyed&amp;lt;/code&amp;gt; handler is called when the target gets destroyed by this ship. &amp;lt;code&amp;gt;target&amp;lt;/code&amp;gt; contains the destroyed target entity. This command is always preceded by the &amp;lt;code&amp;gt;shipTargetLost&amp;lt;/code&amp;gt; handler.&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetDestroyed = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipDied&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipDied&amp;lt;/code&amp;gt; handler is called when the ship or player dies.&lt;br /&gt;
&lt;br /&gt;
 this.shipDied = function(whom, why)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;whom&amp;#039;&amp;#039;&amp;#039; contains the entity that caused the kill. &amp;#039;&amp;#039;&amp;#039;why&amp;#039;&amp;#039;&amp;#039; is the cause written as string and is one of: &amp;quot;removed&amp;quot;, &amp;quot;hit a planet&amp;quot;, &amp;quot;energy damage&amp;quot;, &amp;quot;scrape damage&amp;quot;, &amp;quot;heat damage&amp;quot;, &amp;quot;cascade weapon&amp;quot;.&amp;lt;br&amp;gt;&lt;br /&gt;
(&amp;quot;cascade weapon&amp;quot; is new in 1.74 and  &amp;quot;removed&amp;quot; / &amp;quot;energy damage&amp;quot; were accidentally switched in 1.73)&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnergyBecameFull &amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnergyBecameFull &amp;lt;/code&amp;gt; handler is called when the energy level reaches its maximum value again. &lt;br /&gt;
&lt;br /&gt;
 this.shipEnergyBecameFull = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnergyIsLow&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnergyIsLow&amp;lt;/code&amp;gt; handler is called every time when a ship gets energy damage while the energy level lies below 25% of its maximum value.&lt;br /&gt;
&lt;br /&gt;
 this.shipEnergyIsLow = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipHitByECM&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.71}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipHitByECM&amp;lt;/code&amp;gt; handler is called when a ship receives a ECM pulse. &amp;lt;code&amp;gt;pulsesRemaining&amp;lt;/code&amp;gt; contains the number of pulses that still have to be send by the sending ship. When a ship activates his ecm, he will send 4 pulses with 0.5 seconds interval and increasing range.: 6400 --&amp;gt; 12800 --&amp;gt; 19200 --&amp;gt; 25600.&lt;br /&gt;
&lt;br /&gt;
 this.shipHitByECM = function(pulsesRemaining)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipFiredMissile&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipFiredMissile&amp;lt;/code&amp;gt; handler is called when a missile is fired. &amp;lt;code&amp;gt;missile&amp;lt;/code&amp;gt; contains the missile entity and &amp;lt;code&amp;gt;target&amp;lt;/code&amp;gt; the identity of the target. The handler is send to the ship that launched the missile.&lt;br /&gt;
&lt;br /&gt;
 this.shipFiredMissile = function(missile, target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipKilledOther&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipKilledOther&amp;lt;/code&amp;gt; handler is called when a ship kills an other ship. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that was killed. &amp;lt;code&amp;gt;damageType&amp;lt;/code&amp;gt; is the type of damage.&lt;br /&gt;
&lt;br /&gt;
 this.shipKilledOther = function(whom,damageType)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipReleasedEquipment&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipReleasedEquipment&amp;lt;/code&amp;gt; handler is called when a ship launches a mine (a pylon-mounted equipment item whose key ends with &amp;quot;_MINE&amp;quot;). &amp;lt;code&amp;gt;mine&amp;lt;/code&amp;gt; contains the launched mine entity.&lt;br /&gt;
&lt;br /&gt;
 this.shipReleasedEquipment = function(mine)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetAcquired&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetAcquired&amp;lt;/code&amp;gt; handler is called whenever a new target is selected.&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetAcquired = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetCloaked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetCloaked&amp;lt;/code&amp;gt; handler is called when the target cloakes.&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetCloaked = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetLost&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetLost&amp;lt;/code&amp;gt; handler is called when the target gets lost. &amp;lt;code&amp;gt;target&amp;lt;/code&amp;gt; contains the lost target entity.&amp;lt;br&amp;gt;(Handler introduced in 1.74 as replacement with consistent name for the old handler: &amp;#039;shipLostTarget&amp;#039;.)&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetLost = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTakingDamage&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTakingDamage&amp;lt;/code&amp;gt; handler is called when a ship sustains damage.&amp;lt;br&amp;gt;&lt;br /&gt;
It transfers the &amp;lt;code&amp;gt;amount&amp;lt;/code&amp;gt; of damage, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; caused the damage and a string indicating the &amp;lt;code&amp;gt;type&amp;lt;/code&amp;gt; of damage:&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;scrape damage&amp;quot; (collisions with other entities, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be other entity involved)&lt;br /&gt;
* &amp;quot;heat damage&amp;quot; (see [[Shipdata.plist#heat_insulation]] for more information about this, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be nil in this case)&lt;br /&gt;
* &amp;quot;energy damage&amp;quot; (default / catch-all including weapons damage and missile detonations, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be nil if the entity causing the damage is cloaked, and if the damage is caused by a missile then &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be the entity that launched the missile, if it is damage from a direct laser or from a sub-entity weapon, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be the ship or station mounting the weapon, etc.)&lt;br /&gt;
* &amp;quot;cascade weapon&amp;quot; (caught in Quirium Cascade Mine effect, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be the entity that launched the weapon)&lt;br /&gt;
* &amp;quot;hit a planet&amp;quot;&lt;br /&gt;
* &amp;quot;hit a sun&amp;quot;&lt;br /&gt;
* &amp;quot;removed&amp;quot; (corresponds to the &amp;lt;code&amp;gt;Ship.remove()&amp;lt;/code&amp;gt; method, regardless of the suppressDeathEvent parameter)&lt;br /&gt;
&lt;br /&gt;
For the player ship, only damage not absorbed by the shields will appear in &amp;lt;code&amp;gt;amount&amp;lt;/code&amp;gt;, but the handler will be called anyway with zero as the amount if the shields absorb all the damage.&lt;br /&gt;
&lt;br /&gt;
 this.shipTakingDamage = function(amount, whom, type)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?t=18607 Monitoring attacks with more detail than just &amp;quot;shipTakingDamage&amp;quot;/&amp;quot;shipBeingAttacked&amp;quot;] (2017)&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;cargoDumpedNearby&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;cargoDumpedNearby&amp;lt;/code&amp;gt; handler is sent when a nearby ship - not this ship - dumps a cargo pod.&lt;br /&gt;
&lt;br /&gt;
 this.cargoDumpedNearby = function(cargo: ship, releasedBy: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;commsMessageReceived&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;commsMessageReceived&amp;lt;/code&amp;gt; handler is sent when receiving a message from other ships.&lt;br /&gt;
&lt;br /&gt;
 this.commsMessageReceived = function(message: string, sender: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;distressMessageReceived&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;distressMessageReceived&amp;lt;/code&amp;gt; handler is sent when receiving a distress message from other ships. Distress messages can only be &amp;quot;sent&amp;quot; to ships which have an &amp;quot;ACCEPT_DISTRESS_CALL&amp;quot; reaction in their AI.&lt;br /&gt;
&lt;br /&gt;
 this.distressMessageReceived = function(aggressor: ship, sender: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;equipmentAdded&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;equipmentAdded&amp;lt;/code&amp;gt; handler is called whenever a ship gains an item of equipment. This includes &amp;quot;gaining&amp;quot; of &amp;lt;code&amp;gt;EQ_SOMETHING_DAMAGED&amp;lt;/code&amp;gt; when an &amp;lt;code&amp;gt;EQ_SOMETHING&amp;lt;/code&amp;gt; is damaged. This event will fire regardless of the reason for the equipment being added to the ship.&lt;br /&gt;
&lt;br /&gt;
 this.equipmentAdded = function(equipmentKey)&lt;br /&gt;
 {&lt;br /&gt;
       // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;equipmentRemoved&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;equipmentRemoved&amp;lt;/code&amp;gt; handler is called whenever a ship loses an item of equipment. This includes &amp;quot;losing&amp;quot; of &amp;lt;code&amp;gt;EQ_SOMETHING_DAMAGED&amp;lt;/code&amp;gt; when an &amp;lt;code&amp;gt;EQ_SOMETHING&amp;lt;/code&amp;gt; is repaired This event will fire regardless of the reason for the equipment being removed from the ship.&lt;br /&gt;
&lt;br /&gt;
 this.equipmentRemoved = function(equipmentKey)&lt;br /&gt;
 {&lt;br /&gt;
       // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAchievedDesiredRange&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAchievedDesiredRange&amp;lt;/code&amp;gt; handler is called when the ship reaches the desired range from its destination during certain flight behaviours.&lt;br /&gt;
&lt;br /&gt;
 this.shipAchievedDesiredRange = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAIFrustrated&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAIFrustrated&amp;lt;/code&amp;gt; handler is called when the ship&amp;#039;s low-level behaviour is unable to achieve the desired result (e.g. a &amp;lt;code&amp;gt;performFlee&amp;lt;/code&amp;gt; request is not getting further from the target). A short string describing the context of the frustration is passed as a parameter.&lt;br /&gt;
&lt;br /&gt;
 this.shipAIFrustrated = function(context)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Frustration&amp;#039;&amp;#039;&amp;#039; itself was added to the Vanilla game code on or before 23rd January 2006. It appears quite a lot in the ShipEntity.m &amp;amp; ShipEntityAI.m files in the Vanilla game code. There seems to be no documentation about it (lost in the [[Great Deletion]]?).&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBountyChanged&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBountyChanged&amp;lt;/code&amp;gt; handler is sent when an event tries to change the bounty level of the ship. &amp;lt;code&amp;gt;delta&amp;lt;/code&amp;gt; may be zero, positive or negative. &amp;lt;code&amp;gt;reason&amp;lt;/code&amp;gt; is a string that may either contain a standard value or a custom value set by an OXP. The standard values are:&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;setup actions&amp;#039;&amp;#039;&amp;#039;: Bounty level settings in the system populator or as a side effect of launching a ship from a station with a particular role.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;scripted&amp;#039;&amp;#039;&amp;#039;: OXP scripted changes to bounties, with no specified cause.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;attacked police&amp;#039;&amp;#039;&amp;#039;: The ship attacked a police ship&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;attacked main station&amp;#039;&amp;#039;&amp;#039;: The ship attacked the main station&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;attacked innocent&amp;#039;&amp;#039;&amp;#039;: The ship attacked a Clean ship and was seen doing so&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;seen by police&amp;#039;&amp;#039;&amp;#039;: The ship was seen by police committing a crime&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;distress call&amp;#039;&amp;#039;&amp;#039;: A police ship responded to a distress call from a ship that this ship is attacking&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;illegal exports&amp;#039;&amp;#039;&amp;#039;: The ship launched from a main station while carrying illegal goods (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;assisting offenders&amp;#039;&amp;#039;&amp;#039;: The bounty adjustment applied when a clean ship escorts an offender, or vice versa (NPC only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;new galaxy&amp;#039;&amp;#039;&amp;#039;: The ship entered a new galaxy (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;new system&amp;#039;&amp;#039;&amp;#039;: The ship entered a new system&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;paid fine&amp;#039;&amp;#039;&amp;#039;: The ship was marked for fines by police, and then paid them on docking (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;escape pod&amp;#039;&amp;#039;&amp;#039;: The ship is a replacement ship from escape pod insurance (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;assisting police&amp;#039;&amp;#039;&amp;#039;: The ship helped out a police ship in combat&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;unknown&amp;#039;&amp;#039;&amp;#039;: The bounty changed for an unknown reason. This should not occur.&lt;br /&gt;
&lt;br /&gt;
 this.shipBountyChanged = function(delta,reason)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCloseContact&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCloseContact&amp;lt;/code&amp;gt; handler is sent when approaching otherShip and when &amp;quot;track_contacts&amp;quot; in shipData is &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 this.shipCloseContact = function(otherShip)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCollided&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCollided&amp;lt;/code&amp;gt; handler is sent after a collision with otherShip.&lt;br /&gt;
&lt;br /&gt;
 this.shipCollided = function(otherShip)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipDumpedCargo&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.83}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipDumpedCargo&amp;lt;/code&amp;gt; handler is sent when this ship dumps a cargo pod.&lt;br /&gt;
&lt;br /&gt;
 this.shipDumpedCargo = function(cargo: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipNowFacingDestination&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipNowFacingDestination&amp;lt;/code&amp;gt; handler is called when the ship is facing its destination during certain flight behaviours.&lt;br /&gt;
&lt;br /&gt;
 this.shipNowFacingDestination = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipReachedEndPoint&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipReachedEndPoint&amp;lt;/code&amp;gt; handler is sent after reaching the last navigation point when in mode &amp;lt;code&amp;gt;performFlyRacepoints&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 shipReachedEndPoint = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipReachedNavPoint&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipReachedNavPoint&amp;lt;/code&amp;gt; handler is sent after reaching a navigation point when in mode &amp;lt;code&amp;gt;performFlyRacepoints&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 this.shipReachedNavPoint = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipScoopedOther&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipScoopedOther&amp;lt;/code&amp;gt; handler is called when a ship scoops scripted_cargo. (&amp;quot;cargo_type&amp;quot; = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn&amp;#039;t trigger a handler.&amp;lt;br&amp;gt;The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: &amp;lt;code&amp;gt;shipWasScooped&amp;lt;/code&amp;gt; with the scooper as argument. Starting with Oolite 1.77 this handler will fire on every scooped object.&lt;br /&gt;
&lt;br /&gt;
 this.shipScoopedOther = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLaunchedEscapePod&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLaunchedEscapePod&amp;lt;/code&amp;gt; handler is called when the pilot bails out. This will be followed by a &amp;lt;code&amp;gt;shipWillDockWithStation()&amp;lt;/code&amp;gt;/&amp;lt;code&amp;gt;shipDockedWithStation()&amp;lt;/code&amp;gt; pair after a few seconds when it is the player that is ejecting.&lt;br /&gt;
&lt;br /&gt;
 this.shipLaunchedEscapePod = function(escapepod, passengers)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;escapepod&amp;lt;/code&amp;gt; contains the main pod with the pilot. &amp;lt;code&amp;gt;passengers&amp;lt;/code&amp;gt; will be added with Oolite 1.77 and is an array with passenger pods for those ships that have more than one escape-capsule defined.&lt;br /&gt;
&lt;br /&gt;
=== NPC only ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;aiAwoken&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
This is sent to the ship periodically when &amp;lt;code&amp;gt;ship.AIScriptWakeTime&amp;lt;/code&amp;gt; passes. One of the actions of this handler should be to cause a new wake time to be set. It is received by both the ship script and the AI script but usually only of interest to the latter.&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;aiStarted&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
This is sent to the ship when a new Javascript-based AI is loaded. The AI Script should then use it to do initialisation. The ship script can usually ignore it.&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;coordinatesForEscortPosition&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;coordinatesForEscortPosition&amp;lt;/code&amp;gt; handler fires whenever the game engine wishes to know the positions of escorts relative to their group leader, and fires in the group leader&amp;#039;s ship script at that time. It is given two parameters: the number of the escort, and the maximum number of escorts the group leader might have (which is not necessarily the number of escorts it currently has, of course). Unlike most ship script handlers, which return void, &amp;#039;&amp;#039;this handler is required to return a Vector&amp;#039;&amp;#039; (or a value equivalent to a Vector) describing the relative position of the escort to the mothership.&lt;br /&gt;
&lt;br /&gt;
 coordinatesForEscortPosition = function(num,max)&lt;br /&gt;
 {&lt;br /&gt;
    // Your code here&lt;br /&gt;
    return escort_position;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
The escort position is relative to the mothership, and in the mothership&amp;#039;s coordinate system. For example, to place an escort 500m to the right of the mothership, return &amp;lt;code&amp;gt;new Vector(500, 0, 0);&amp;lt;/code&amp;gt;. You are responsible for ensuring that there is sufficient space between the escorts and the mothership, and between any pair of escorts, or they will spend most of their time trying to avoid collisions with each other. If you intend to use the same ship script on several ships of varying sizes, you may wish to include the mothership&amp;#039;s [[Oolite_JavaScript_Reference:_Entity#collisionRadius|collisionRadius]] in the calculations.&lt;br /&gt;
&lt;br /&gt;
Placing escorts directly ahead of the mothership (e.g. &amp;lt;code&amp;gt;new Vector(0, 0, 500);&amp;lt;/code&amp;gt;) or too close to the mothership will trigger collision warnings for the mothership, making it difficult to maintain level flight for any significant time.&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;entityDestroyed&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75.1}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;entityDestroyed&amp;lt;/code&amp;gt; handler fires immediately &amp;#039;&amp;#039;after&amp;#039;&amp;#039; the ship becomes invalid, regardless of the reason, except when the game restarts. This is the best place for all kind of &amp;#039;clean-up&amp;#039; code, for example stopping [[Oolite_JavaScript_Reference:_Timer|Timers]] associated with the ship script.&lt;br /&gt;
&lt;br /&gt;
 entityDestroyed = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortAccepted&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortAccepted&amp;lt;/code&amp;gt; handler is called when a mother ship accepts this ship as an escort. The mothership simultaneously gets a &amp;lt;code&amp;gt;shipAcceptedEscort&amp;lt;/code&amp;gt; event.&lt;br /&gt;
&lt;br /&gt;
 this.escortAccepted = function(mothership)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortDock&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortDock&amp;lt;/code&amp;gt; handler is called by a mother ships that uses the AI command: &amp;lt;code&amp;gt;dockEscorts&amp;lt;/code&amp;gt;.  Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.&lt;br /&gt;
&lt;br /&gt;
 this.escortDock = function(delay)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortRejected&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortRejected&amp;lt;/code&amp;gt; handler is called when a mother ship rejects this ship as an escort.&lt;br /&gt;
&lt;br /&gt;
 this.escortRejected = function(mothership)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;offenceCommittedNearby&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;offenceCommittedNearby&amp;lt;/code&amp;gt; handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.&lt;br /&gt;
&lt;br /&gt;
 this.offenceCommittedNearby = function(attacker, victim)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;scriptedAI&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;scriptedAI&amp;lt;/code&amp;gt; handler is called each frame while the ship&amp;#039;s AI is in &amp;quot;performScriptedAI&amp;quot; or &amp;quot;performScriptedAttackAI&amp;quot; mode. It must return an object defining the ship&amp;#039;s flight parameters. The &amp;lt;code&amp;gt;delta&amp;lt;/code&amp;gt; parameter is the length of the current frame in seconds. [[OXP_Scripted_AI|More information on using this functionality]]&lt;br /&gt;
&lt;br /&gt;
 this.scriptedAI = function(delta)&lt;br /&gt;
 {&lt;br /&gt;
   // Your code here&lt;br /&gt;
   return flightParameters;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAcceptedEscort&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAcceptedEscort&amp;lt;/code&amp;gt; handler is called when this ship accepts a new ship as an escort. The escort simultaneously gets a &amp;lt;code&amp;gt;escortAccepted&amp;lt;/code&amp;gt; event. &lt;br /&gt;
&lt;br /&gt;
 this.shipAcceptedEscort = function(newEscort)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLandedOnPlanet&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLandedOnPlanet&amp;lt;/code&amp;gt; handler is called for ships landing on a planet. It transfers the &amp;lt;code&amp;gt;planet&amp;lt;/code&amp;gt; parameter.&lt;br /&gt;
&lt;br /&gt;
 shipLandedOnPlanet = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipRemoved&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipRemoved&amp;lt;/code&amp;gt; handler is called for ships removed by script. It transfers the &amp;lt;code&amp;gt;suppressDeathEvent&amp;lt;/code&amp;gt; parameter so the script knows if there will also follow a shipDied() event.&lt;br /&gt;
&lt;br /&gt;
 shipRemoved = function(suppressDeathEvent)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipSpawned&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipSpawned&amp;lt;/code&amp;gt; handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered. Note that this is not called for subentities - if subentities need specific set up running, this must be called from the main ship&amp;#039;s handler.&lt;br /&gt;
&lt;br /&gt;
 this.shipSpawned = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;spawnedAsEscort&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;spawnedAsEscort&amp;lt;/code&amp;gt; handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument. &lt;br /&gt;
&lt;br /&gt;
 this.spawnedAsEscort = function(mother)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWasDumped&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWasDumped&amp;lt;/code&amp;gt; handler is sent to the cargopod when a ship jettisons it. The dumping ship is transferred as the argument. &lt;br /&gt;
&lt;br /&gt;
 this.shipWasDumped = function(dumper)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWasScooped&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWasScooped&amp;lt;/code&amp;gt; handler is send to the cargopod when a ship scoops scripted_cargo. (&amp;quot;cargo_type&amp;quot; = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on  the handler &amp;lt;code&amp;gt;shipScoopedOther&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 this.shipWasScooped = function(scooper)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Stations only ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;alertConditionChanged&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;alertConditionChanged&amp;lt;/code&amp;gt; handler is called when a station&amp;#039;s alert status ([[Oolite JavaScript Reference: Station#alertCondition|Station.alertCondition]]) changes. Only the player and stations have an alert condition. The equivalent player event is handled inside [[Oolite JavaScript Reference: World script event handlers|world scripts]].&lt;br /&gt;
&lt;br /&gt;
 this.alertConditionChanged = function(newCondition, oldCondition)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;otherShipDocked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;otherShipDocked&amp;lt;/code&amp;gt; handler is called with a station script only, when an ship docks. It has the docked ship as argument.&lt;br /&gt;
&lt;br /&gt;
 this.otherShipDocked = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationDockingQueuesAreEmpty&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationDockingQueuesAreEmpty&amp;lt;/code&amp;gt; handler is called when the last ship in the queues docks with the station (or gives up docking and leaves).&lt;br /&gt;
&lt;br /&gt;
 this.stationDockingQueuesAreEmpty = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationLaunchedShip&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationLaunchedShip&amp;lt;/code&amp;gt; handler is called with a station script only, when a ship launches. It has the launched ship as argument.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 this.stationLaunchedShip = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationAcceptedDockingRequest&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationAcceptedDockingRequest&amp;lt;/code&amp;gt; handler is called when a ship has requested docking clearance and has been allocated a dock. Due to the way in which docking clearance works, this is likely to be called several times for the same ship as it moves through the docking sequence.&lt;br /&gt;
&lt;br /&gt;
 this.stationAcceptedDockingRequest = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationReceivedDockingRequest&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationReceivedDockingRequest&amp;lt;/code&amp;gt; handler is called when a ship requests docking clearance. The ship requesting is passed as a parameter. This is often necessary for carriers which will need to come to a stop before ships can dock with them. Due to the way in which docking clearance works, this is likely to be called several times for the same ship as it moves through the docking sequence.&lt;br /&gt;
&lt;br /&gt;
 this.stationReceivedDockingRequest = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
(note: a handler by this name was present in 1.79 and 1.80, but was called at the wrong time and should not be used. Set a minimum version of 1.81 if you use this event handler)&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;willOpenDockingPortFor&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;willOpenDockingPortFor&amp;lt;/code&amp;gt; handler is called with a station script only, when a ship requests docking, in cases where a dock is set to generally disallow docking (i.e. [[Oolite_JavaScript_Reference:_Dock#allowsDocking|allowsDocking]] is &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;). It returns a boolean:&lt;br /&gt;
* if it returns &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; (or this handler isn&amp;#039;t defined), this dock will not be opened later for the requesting ship, and it should not try again.&lt;br /&gt;
* if it returns &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, this dock will be opened later for the requesting ship, and it should try again later if it cannot find another suitable dock on this station.&lt;br /&gt;
The handler is passed the identity of the dock and the requesting ship&lt;br /&gt;
&lt;br /&gt;
 this.willOpenDockingPortFor = function(dock, ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
      return allow;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Docks Only ===&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
==== acceptDockingRequestFrom ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;acceptDockingRequestFrom&amp;lt;/code&amp;gt; handler is called when a ship is looking for docking clearance from the station, and is considering this dock. To get as far as calling this handler, the dock must have &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_Dock#allowsDocking|allowsDocking]] = true&amp;lt;/code&amp;gt; and be large enough to physically fit the ship.&lt;br /&gt;
&lt;br /&gt;
It returns a boolean: &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; to accept the request (which, depending on docking queue lengths will not necessarily mean that this dock is the one that the ship heads for) or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; to reject the request.  &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; is assumed if this handler is not defined.&lt;br /&gt;
&lt;br /&gt;
This handler may be called multiple times for the same ship if the ship is having difficulty finding a suitable docking queue.&lt;br /&gt;
&lt;br /&gt;
 this.acceptDockingRequestFrom = function(ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
      return allow;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== acceptLaunchingRequestFrom ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;acceptLaunchingRequestFrom&amp;lt;/code&amp;gt; handler is called when a ship is looking for launching clearance from the station, and is considering this dock. To get as far as calling this handler, the dock must have &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_Dock#allowsLaunching|allowsLaunching]] = true&amp;lt;/code&amp;gt; and be large enough to physically fit the ship (unless the ship is the player).&lt;br /&gt;
&lt;br /&gt;
It returns a boolean: &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; to accept the request (which, depending on launching queue lengths will not necessarily mean that this dock is the one that the ship uses) or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; to reject the request.  &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; is assumed if this handler is not defined.&lt;br /&gt;
&lt;br /&gt;
 this.acceptLaunchingRequestFrom = function(ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
      return allow;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Missing Events ===&lt;br /&gt;
&lt;br /&gt;
All initially planned events have a corresponding event handler in v1.74.&lt;br /&gt;
&lt;br /&gt;
If there are other events you would like to be able to respond to, please write a request [https://bb.oolite.space/viewtopic.php?t=3296 on the forum].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;See also:&amp;#039;&amp;#039;&amp;#039; [[Oolite JavaScript Reference: World script event handlers|world script event handlers]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3865 distant effects of a ship&amp;#039;s mass or energy?] - analysis of &amp;#039;&amp;#039;&amp;#039;collisions&amp;#039;&amp;#039;&amp;#039; at vast distance back in 2007.&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite JavaScript Reference]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Oolite_JavaScript_Reference:_Ship_script_event_handlers&amp;diff=90348</id>
		<title>Oolite JavaScript Reference: Ship script event handlers</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Oolite_JavaScript_Reference:_Ship_script_event_handlers&amp;diff=90348"/>
		<updated>2026-10-17T21:35:16Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* shipBeingAttacked */ Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].&lt;br /&gt;
&lt;br /&gt;
Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.&lt;br /&gt;
&lt;br /&gt;
The list of event handlers will change from version to version (usually additions of extra handlers). For this reason, any variables or functions you create as &amp;lt;code&amp;gt;this.variable&amp;lt;/code&amp;gt; should have a name beginning with &amp;#039;_&amp;#039; or &amp;#039;$&amp;#039; - e.g. &amp;lt;code&amp;gt;this._variable&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;this.$variable&amp;lt;/code&amp;gt; - to avoid potential conflicts with future event handlers.&lt;br /&gt;
&lt;br /&gt;
Note that a ship script event which affects the player ship (therefore not those marked NPC only, station only, etc.) will also appear as a [[Oolite JavaScript Reference: World script event handlers|world script event]].&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.79 onwards, each ship has two scripts: the &amp;quot;ship script&amp;quot; as in previous versions (&amp;lt;code&amp;gt;ship.script&amp;lt;/code&amp;gt;) and an AI script (&amp;lt;code&amp;gt;ship.AIScript&amp;lt;/code&amp;gt;) which manages [[Oolite Javascript Reference: PriorityAI Documentation|Javascript-based AI]]. The former is intended for constant events related to the ship itself, and the latter is intended for event handling which varies based on what the ship is currently doing. Both scripts receive all events which do not expect a return value. Events expecting a return value are sent to the ship script &amp;#039;&amp;#039;only&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Docking ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWillDockWithStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWillDockWithStation&amp;lt;/code&amp;gt; handler is called at the beginning of the docking tunnel effect.&lt;br /&gt;
&lt;br /&gt;
 this.shipWillDockWithStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
At this moment &amp;quot;ship.dockedStation == nil&amp;quot;, &amp;quot;ship.status == STATUS_DOCKING&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipDockedWithStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipDockedWithStation&amp;lt;/code&amp;gt; handler is called at the end of the docking tunnel effect.&lt;br /&gt;
&lt;br /&gt;
 this.shipDockedWithStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
At this moment &amp;quot;ship.dockedStation == the station&amp;quot;, &amp;quot;ship.status == STATUS_DOCKED&amp;quot; and &amp;quot;gui_screen&amp;quot; is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWillLaunchFromStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
This handler was added for npc ships with test release 1.75, before it was a worldScript only handler.&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWillLaunchFromStation&amp;lt;/code&amp;gt; handler is called for ship scripts on ship creation, before the shipSpawned event. &lt;br /&gt;
&lt;br /&gt;
 this.shipWillLaunchFromStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLaunchedFromStation&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLaunchedFromStation&amp;lt;/code&amp;gt; handler is called at the end of the launch tract, when the ship has clearly left the station and AI updating begins.&lt;br /&gt;
&lt;br /&gt;
 this.shipLaunchedFromStation = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationWithdrewDockingClearance&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationWithdrewDockingClearance&amp;lt;/code&amp;gt; handler is received when the station the ship is trying to dock with unexpectedly withdraws clearance (e.g. if &amp;lt;code&amp;gt;station.abortAllDockings&amp;lt;/code&amp;gt; is called).&lt;br /&gt;
&lt;br /&gt;
 this.stationWithdrewDockingClearance = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Witchspace Jumps ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;playerWillEnterWitchspace&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;playerWillEnterWitchspace&amp;lt;/code&amp;gt; handler is called just before a witchspace jump starts and after the &amp;lt;code&amp;gt;shipWillEnterWitchspace&amp;lt;/code&amp;gt; handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)&lt;br /&gt;
&lt;br /&gt;
 this.playerWillEnterWitchspace = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipExitedWormhole&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipExitedWormhole&amp;lt;/code&amp;gt; handler is called when a ship exits a wormhole.&lt;br /&gt;
&lt;br /&gt;
 this.shipExitedWormhole = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWillEnterWormhole&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWillEnterWormhole&amp;lt;/code&amp;gt; handler is called when a ship enters a wormhole. only&lt;br /&gt;
&lt;br /&gt;
 this.shipWillEnterWormhole = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWitchspaceBlocked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWitchspaceBlocked&amp;lt;/code&amp;gt; handler is called when a ship is prevented from entering witchspace by the presence of a nearby large mass. The blocking object is passed as a parameter&lt;br /&gt;
&lt;br /&gt;
 this.shipWitchspaceBlocked = function(blocker)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;wormholeSuggested&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;wormholeSuggested&amp;lt;/code&amp;gt; handler is called when another ship enters witchspace and suggests that this ship follows. The wormhole used is passed as a parameter. This is most commonly called when a group leader enters witchspace and wishes to take its escorts with it.&lt;br /&gt;
&lt;br /&gt;
 this.wormholeSuggested = function(wormhole)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Enter/Exit Aegis ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnteredStationAegis&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnteredStationAegis&amp;lt;/code&amp;gt; handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don&amp;#039;t give aegis messages.&lt;br /&gt;
&lt;br /&gt;
 this.shipEnteredStationAegis = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipExitedStationAegis&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipExitedStationAegis&amp;lt;/code&amp;gt; handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).&lt;br /&gt;
&lt;br /&gt;
 this.shipExitedStationAegis = function(station)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnteredPlanetaryVicinity&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnteredPlanetaryVicinity&amp;lt;/code&amp;gt; handler is called when the player enters the planet aegis (3x planet radius).&lt;br /&gt;
&lt;br /&gt;
 this.shipEnteredPlanetaryVicinity = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipExitedPlanetaryVicinity&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipExitedPlanetaryVicinity&amp;lt;/code&amp;gt; handler is called when the player leaves the planet aegis (3x planet radius).&lt;br /&gt;
&lt;br /&gt;
 this.shipExitedPlanetaryVicinity = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipApproachingPlanetSurface&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipApproachingPlanetSurface&amp;lt;/code&amp;gt; handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).&lt;br /&gt;
&lt;br /&gt;
 this.shipApproachingPlanetSurface = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLeavingPlanetSurface&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLeavingPlanetSurface&amp;lt;/code&amp;gt; handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).&lt;br /&gt;
&lt;br /&gt;
 this.shipLeavingPlanetSurface = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Combat ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;cascadeWeaponDetected&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;cascadeWeaponDetected&amp;lt;/code&amp;gt; handler fires when a Q-bomb (or equivalent device) detonates within scanner range of the player. The stock Q-mine (and potentially OXP equivalents) will also send this handler at the start of the countdown, giving ships more time to react. The weapon entity will be passed as a parameter.&lt;br /&gt;
&lt;br /&gt;
 this.cascadeWeaponDetected = function(weapon)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;defenseTargetDestroyed&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;defenseTargetDestroyed&amp;lt;/code&amp;gt; handler is sent when a defense (i.e. secondary) target is destroyed. A reference to the destroyed ship (which will become invalid shortly) is passed as a parameter.&lt;br /&gt;
&lt;br /&gt;
 this.defenseTargetDestroyed = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortAttack&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortAttack&amp;lt;/code&amp;gt; handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.&lt;br /&gt;
&lt;br /&gt;
 this.escortAttack = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;helpRequestReceived&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;helpRequestReceived&amp;lt;/code&amp;gt; handler is sent when an ally of this ship is being attacked and requires help. There are two parameters, the ally and the enemy.&lt;br /&gt;
&lt;br /&gt;
 this.helpRequestReceived = function(ally, enemy)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAttackedOther&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74.2}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAttackedOther&amp;lt;/code&amp;gt; handler is called when this ship hits another with a laser shot. &amp;lt;code&amp;gt;other&amp;lt;/code&amp;gt; is the identity of the ship being hit.&lt;br /&gt;
&lt;br /&gt;
 this.shipAttackedOther = function(other)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAttackedWithMissile&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAttackedWithMissile&amp;lt;/code&amp;gt; handler is called when a missile is fired. &amp;lt;code&amp;gt;missile&amp;lt;/code&amp;gt; contains the missile entity and &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that launched the missile.&lt;br /&gt;
&lt;br /&gt;
 this.shipAttackedWithMissile = function(missile, whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAttackerDistracted&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAttackerDistracted&amp;lt;/code&amp;gt; handler is called when the ship&amp;#039;s current attacker is distracted by another ship. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; contains the ship which is doing the distracting.&lt;br /&gt;
&lt;br /&gt;
 this.shipAttackerDistracted = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBeingAttacked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBeingAttacked&amp;lt;/code&amp;gt; handler is called when a laser shot  hits. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that attacked.&lt;br /&gt;
&lt;br /&gt;
 this.shipBeingAttacked = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?t=18607 Monitoring attacks with more detail than just &amp;quot;shipTakingDamage&amp;quot;/&amp;quot;shipBeingAttacked&amp;quot;] (2017)&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBeingAttackedByCloaked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBeingAttackedByCloaked&amp;lt;/code&amp;gt; handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.&lt;br /&gt;
&lt;br /&gt;
 this.shipBeingAttackedByCloaked = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBeingAttackedUnsuccessfully&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBeingAttackedUnsuccessfully&amp;lt;/code&amp;gt; handler is called when a laser shot narrowly misses the ship, when fired by an uncloaked ship intending to hit. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that attacked.&lt;br /&gt;
&lt;br /&gt;
 this.shipBeingAttackedUnsuccessfully = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCloakActivated&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCloakActivated&amp;lt;/code&amp;gt; handler is called whenever the script&amp;#039;s target ship activates its cloaking device. No parameters are required for this handler.&lt;br /&gt;
&lt;br /&gt;
  this.shipCloakActivated = function()&lt;br /&gt;
  {&lt;br /&gt;
     // Your code here&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCloakDeactivated&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCloakDeactivated&amp;lt;/code&amp;gt; handler is called whenever the script&amp;#039;s target ship deactivates its cloaking device. No parameters are required for this handler.&lt;br /&gt;
&lt;br /&gt;
  this.shipCloakDeactivated = function()&lt;br /&gt;
  {&lt;br /&gt;
     // Your code here&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetDestroyed&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetDestroyed&amp;lt;/code&amp;gt; handler is called when the target gets destroyed by this ship. &amp;lt;code&amp;gt;target&amp;lt;/code&amp;gt; contains the destroyed target entity. This command is always preceded by the &amp;lt;code&amp;gt;shipTargetLost&amp;lt;/code&amp;gt; handler.&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetDestroyed = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipDied&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipDied&amp;lt;/code&amp;gt; handler is called when the ship or player dies.&lt;br /&gt;
&lt;br /&gt;
 this.shipDied = function(whom, why)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;whom&amp;#039;&amp;#039;&amp;#039; contains the entity that caused the kill. &amp;#039;&amp;#039;&amp;#039;why&amp;#039;&amp;#039;&amp;#039; is the cause written as string and is one of: &amp;quot;removed&amp;quot;, &amp;quot;hit a planet&amp;quot;, &amp;quot;energy damage&amp;quot;, &amp;quot;scrape damage&amp;quot;, &amp;quot;heat damage&amp;quot;, &amp;quot;cascade weapon&amp;quot;.&amp;lt;br&amp;gt;&lt;br /&gt;
(&amp;quot;cascade weapon&amp;quot; is new in 1.74 and  &amp;quot;removed&amp;quot; / &amp;quot;energy damage&amp;quot; were accidentally switched in 1.73)&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnergyBecameFull &amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnergyBecameFull &amp;lt;/code&amp;gt; handler is called when the energy level reaches its maximum value again. &lt;br /&gt;
&lt;br /&gt;
 this.shipEnergyBecameFull = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipEnergyIsLow&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipEnergyIsLow&amp;lt;/code&amp;gt; handler is called every time when a ship gets energy damage while the energy level lies below 25% of its maximum value.&lt;br /&gt;
&lt;br /&gt;
 this.shipEnergyIsLow = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipHitByECM&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.71}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipHitByECM&amp;lt;/code&amp;gt; handler is called when a ship receives a ECM pulse. &amp;lt;code&amp;gt;pulsesRemaining&amp;lt;/code&amp;gt; contains the number of pulses that still have to be send by the sending ship. When a ship activates his ecm, he will send 4 pulses with 0.5 seconds interval and increasing range.: 6400 --&amp;gt; 12800 --&amp;gt; 19200 --&amp;gt; 25600.&lt;br /&gt;
&lt;br /&gt;
 this.shipHitByECM = function(pulsesRemaining)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipFiredMissile&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipFiredMissile&amp;lt;/code&amp;gt; handler is called when a missile is fired. &amp;lt;code&amp;gt;missile&amp;lt;/code&amp;gt; contains the missile entity and &amp;lt;code&amp;gt;target&amp;lt;/code&amp;gt; the identity of the target. The handler is send to the ship that launched the missile.&lt;br /&gt;
&lt;br /&gt;
 this.shipFiredMissile = function(missile, target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipKilledOther&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipKilledOther&amp;lt;/code&amp;gt; handler is called when a ship kills an other ship. &amp;lt;code&amp;gt;whom&amp;lt;/code&amp;gt; the identity of the ship that was killed. &amp;lt;code&amp;gt;damageType&amp;lt;/code&amp;gt; is the type of damage.&lt;br /&gt;
&lt;br /&gt;
 this.shipKilledOther = function(whom,damageType)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipReleasedEquipment&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipReleasedEquipment&amp;lt;/code&amp;gt; handler is called when a ship launches a mine (a pylon-mounted equipment item whose key ends with &amp;quot;_MINE&amp;quot;). &amp;lt;code&amp;gt;mine&amp;lt;/code&amp;gt; contains the launched mine entity.&lt;br /&gt;
&lt;br /&gt;
 this.shipReleasedEquipment = function(mine)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetAcquired&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetAcquired&amp;lt;/code&amp;gt; handler is called whenever a new target is selected.&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetAcquired = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetCloaked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetCloaked&amp;lt;/code&amp;gt; handler is called when the target cloakes.&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetCloaked = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTargetLost&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTargetLost&amp;lt;/code&amp;gt; handler is called when the target gets lost. &amp;lt;code&amp;gt;target&amp;lt;/code&amp;gt; contains the lost target entity.&amp;lt;br&amp;gt;(Handler introduced in 1.74 as replacement with consistent name for the old handler: &amp;#039;shipLostTarget&amp;#039;.)&lt;br /&gt;
&lt;br /&gt;
 this.shipTargetLost = function(target)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipTakingDamage&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipTakingDamage&amp;lt;/code&amp;gt; handler is called when a ship sustains damage.&amp;lt;br&amp;gt;&lt;br /&gt;
It transfers the &amp;lt;code&amp;gt;amount&amp;lt;/code&amp;gt; of damage, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; caused the damage and a string indicating the &amp;lt;code&amp;gt;type&amp;lt;/code&amp;gt; of damage:&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;scrape damage&amp;quot; (collisions with other entities, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be other entity involved)&lt;br /&gt;
* &amp;quot;heat damage&amp;quot; (see [[Shipdata.plist#heat_insulation]] for more information about this, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be nil in this case)&lt;br /&gt;
* &amp;quot;energy damage&amp;quot; (default / catch-all including weapons damage and missile detonations, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be nil if the entity causing the damage is cloaked, and if the damage is caused by a missile then &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be the entity that launched the missile, if it is damage from a direct laser or from a sub-entity weapon, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be the ship or station mounting the weapon, etc.)&lt;br /&gt;
* &amp;quot;cascade weapon&amp;quot; (caught in Quirium Cascade Mine effect, &amp;lt;code&amp;gt;who&amp;lt;/code&amp;gt; will be the entity that launched the weapon)&lt;br /&gt;
* &amp;quot;hit a planet&amp;quot;&lt;br /&gt;
* &amp;quot;hit a sun&amp;quot;&lt;br /&gt;
* &amp;quot;removed&amp;quot; (corresponds to the &amp;lt;code&amp;gt;Ship.remove()&amp;lt;/code&amp;gt; method, regardless of the suppressDeathEvent parameter)&lt;br /&gt;
&lt;br /&gt;
For the player ship, only damage not absorbed by the shields will appear in &amp;lt;code&amp;gt;amount&amp;lt;/code&amp;gt;, but the handler will be called anyway with zero as the amount if the shields absorb all the damage.&lt;br /&gt;
&lt;br /&gt;
 this.shipTakingDamage = function(amount, whom, type)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;cargoDumpedNearby&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;cargoDumpedNearby&amp;lt;/code&amp;gt; handler is sent when a nearby ship - not this ship - dumps a cargo pod.&lt;br /&gt;
&lt;br /&gt;
 this.cargoDumpedNearby = function(cargo: ship, releasedBy: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;commsMessageReceived&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;commsMessageReceived&amp;lt;/code&amp;gt; handler is sent when receiving a message from other ships.&lt;br /&gt;
&lt;br /&gt;
 this.commsMessageReceived = function(message: string, sender: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;distressMessageReceived&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;distressMessageReceived&amp;lt;/code&amp;gt; handler is sent when receiving a distress message from other ships. Distress messages can only be &amp;quot;sent&amp;quot; to ships which have an &amp;quot;ACCEPT_DISTRESS_CALL&amp;quot; reaction in their AI.&lt;br /&gt;
&lt;br /&gt;
 this.distressMessageReceived = function(aggressor: ship, sender: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;equipmentAdded&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;equipmentAdded&amp;lt;/code&amp;gt; handler is called whenever a ship gains an item of equipment. This includes &amp;quot;gaining&amp;quot; of &amp;lt;code&amp;gt;EQ_SOMETHING_DAMAGED&amp;lt;/code&amp;gt; when an &amp;lt;code&amp;gt;EQ_SOMETHING&amp;lt;/code&amp;gt; is damaged. This event will fire regardless of the reason for the equipment being added to the ship.&lt;br /&gt;
&lt;br /&gt;
 this.equipmentAdded = function(equipmentKey)&lt;br /&gt;
 {&lt;br /&gt;
       // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;equipmentRemoved&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;equipmentRemoved&amp;lt;/code&amp;gt; handler is called whenever a ship loses an item of equipment. This includes &amp;quot;losing&amp;quot; of &amp;lt;code&amp;gt;EQ_SOMETHING_DAMAGED&amp;lt;/code&amp;gt; when an &amp;lt;code&amp;gt;EQ_SOMETHING&amp;lt;/code&amp;gt; is repaired This event will fire regardless of the reason for the equipment being removed from the ship.&lt;br /&gt;
&lt;br /&gt;
 this.equipmentRemoved = function(equipmentKey)&lt;br /&gt;
 {&lt;br /&gt;
       // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAchievedDesiredRange&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAchievedDesiredRange&amp;lt;/code&amp;gt; handler is called when the ship reaches the desired range from its destination during certain flight behaviours.&lt;br /&gt;
&lt;br /&gt;
 this.shipAchievedDesiredRange = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAIFrustrated&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAIFrustrated&amp;lt;/code&amp;gt; handler is called when the ship&amp;#039;s low-level behaviour is unable to achieve the desired result (e.g. a &amp;lt;code&amp;gt;performFlee&amp;lt;/code&amp;gt; request is not getting further from the target). A short string describing the context of the frustration is passed as a parameter.&lt;br /&gt;
&lt;br /&gt;
 this.shipAIFrustrated = function(context)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Frustration&amp;#039;&amp;#039;&amp;#039; itself was added to the Vanilla game code on or before 23rd January 2006. It appears quite a lot in the ShipEntity.m &amp;amp; ShipEntityAI.m files in the Vanilla game code. There seems to be no documentation about it (lost in the [[Great Deletion]]?).&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipBountyChanged&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipBountyChanged&amp;lt;/code&amp;gt; handler is sent when an event tries to change the bounty level of the ship. &amp;lt;code&amp;gt;delta&amp;lt;/code&amp;gt; may be zero, positive or negative. &amp;lt;code&amp;gt;reason&amp;lt;/code&amp;gt; is a string that may either contain a standard value or a custom value set by an OXP. The standard values are:&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;setup actions&amp;#039;&amp;#039;&amp;#039;: Bounty level settings in the system populator or as a side effect of launching a ship from a station with a particular role.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;scripted&amp;#039;&amp;#039;&amp;#039;: OXP scripted changes to bounties, with no specified cause.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;attacked police&amp;#039;&amp;#039;&amp;#039;: The ship attacked a police ship&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;attacked main station&amp;#039;&amp;#039;&amp;#039;: The ship attacked the main station&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;attacked innocent&amp;#039;&amp;#039;&amp;#039;: The ship attacked a Clean ship and was seen doing so&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;seen by police&amp;#039;&amp;#039;&amp;#039;: The ship was seen by police committing a crime&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;distress call&amp;#039;&amp;#039;&amp;#039;: A police ship responded to a distress call from a ship that this ship is attacking&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;illegal exports&amp;#039;&amp;#039;&amp;#039;: The ship launched from a main station while carrying illegal goods (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;assisting offenders&amp;#039;&amp;#039;&amp;#039;: The bounty adjustment applied when a clean ship escorts an offender, or vice versa (NPC only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;new galaxy&amp;#039;&amp;#039;&amp;#039;: The ship entered a new galaxy (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;new system&amp;#039;&amp;#039;&amp;#039;: The ship entered a new system&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;paid fine&amp;#039;&amp;#039;&amp;#039;: The ship was marked for fines by police, and then paid them on docking (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;escape pod&amp;#039;&amp;#039;&amp;#039;: The ship is a replacement ship from escape pod insurance (player only)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;assisting police&amp;#039;&amp;#039;&amp;#039;: The ship helped out a police ship in combat&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;unknown&amp;#039;&amp;#039;&amp;#039;: The bounty changed for an unknown reason. This should not occur.&lt;br /&gt;
&lt;br /&gt;
 this.shipBountyChanged = function(delta,reason)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCloseContact&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCloseContact&amp;lt;/code&amp;gt; handler is sent when approaching otherShip and when &amp;quot;track_contacts&amp;quot; in shipData is &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 this.shipCloseContact = function(otherShip)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipCollided&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipCollided&amp;lt;/code&amp;gt; handler is sent after a collision with otherShip.&lt;br /&gt;
&lt;br /&gt;
 this.shipCollided = function(otherShip)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipDumpedCargo&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.83}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipDumpedCargo&amp;lt;/code&amp;gt; handler is sent when this ship dumps a cargo pod.&lt;br /&gt;
&lt;br /&gt;
 this.shipDumpedCargo = function(cargo: ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipNowFacingDestination&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{Oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipNowFacingDestination&amp;lt;/code&amp;gt; handler is called when the ship is facing its destination during certain flight behaviours.&lt;br /&gt;
&lt;br /&gt;
 this.shipNowFacingDestination = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipReachedEndPoint&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipReachedEndPoint&amp;lt;/code&amp;gt; handler is sent after reaching the last navigation point when in mode &amp;lt;code&amp;gt;performFlyRacepoints&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 shipReachedEndPoint = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipReachedNavPoint&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipReachedNavPoint&amp;lt;/code&amp;gt; handler is sent after reaching a navigation point when in mode &amp;lt;code&amp;gt;performFlyRacepoints&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 this.shipReachedNavPoint = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipScoopedOther&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipScoopedOther&amp;lt;/code&amp;gt; handler is called when a ship scoops scripted_cargo. (&amp;quot;cargo_type&amp;quot; = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn&amp;#039;t trigger a handler.&amp;lt;br&amp;gt;The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: &amp;lt;code&amp;gt;shipWasScooped&amp;lt;/code&amp;gt; with the scooper as argument. Starting with Oolite 1.77 this handler will fire on every scooped object.&lt;br /&gt;
&lt;br /&gt;
 this.shipScoopedOther = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLaunchedEscapePod&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLaunchedEscapePod&amp;lt;/code&amp;gt; handler is called when the pilot bails out. This will be followed by a &amp;lt;code&amp;gt;shipWillDockWithStation()&amp;lt;/code&amp;gt;/&amp;lt;code&amp;gt;shipDockedWithStation()&amp;lt;/code&amp;gt; pair after a few seconds when it is the player that is ejecting.&lt;br /&gt;
&lt;br /&gt;
 this.shipLaunchedEscapePod = function(escapepod, passengers)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;escapepod&amp;lt;/code&amp;gt; contains the main pod with the pilot. &amp;lt;code&amp;gt;passengers&amp;lt;/code&amp;gt; will be added with Oolite 1.77 and is an array with passenger pods for those ships that have more than one escape-capsule defined.&lt;br /&gt;
&lt;br /&gt;
=== NPC only ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;aiAwoken&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
This is sent to the ship periodically when &amp;lt;code&amp;gt;ship.AIScriptWakeTime&amp;lt;/code&amp;gt; passes. One of the actions of this handler should be to cause a new wake time to be set. It is received by both the ship script and the AI script but usually only of interest to the latter.&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;aiStarted&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
This is sent to the ship when a new Javascript-based AI is loaded. The AI Script should then use it to do initialisation. The ship script can usually ignore it.&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;coordinatesForEscortPosition&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;coordinatesForEscortPosition&amp;lt;/code&amp;gt; handler fires whenever the game engine wishes to know the positions of escorts relative to their group leader, and fires in the group leader&amp;#039;s ship script at that time. It is given two parameters: the number of the escort, and the maximum number of escorts the group leader might have (which is not necessarily the number of escorts it currently has, of course). Unlike most ship script handlers, which return void, &amp;#039;&amp;#039;this handler is required to return a Vector&amp;#039;&amp;#039; (or a value equivalent to a Vector) describing the relative position of the escort to the mothership.&lt;br /&gt;
&lt;br /&gt;
 coordinatesForEscortPosition = function(num,max)&lt;br /&gt;
 {&lt;br /&gt;
    // Your code here&lt;br /&gt;
    return escort_position;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
The escort position is relative to the mothership, and in the mothership&amp;#039;s coordinate system. For example, to place an escort 500m to the right of the mothership, return &amp;lt;code&amp;gt;new Vector(500, 0, 0);&amp;lt;/code&amp;gt;. You are responsible for ensuring that there is sufficient space between the escorts and the mothership, and between any pair of escorts, or they will spend most of their time trying to avoid collisions with each other. If you intend to use the same ship script on several ships of varying sizes, you may wish to include the mothership&amp;#039;s [[Oolite_JavaScript_Reference:_Entity#collisionRadius|collisionRadius]] in the calculations.&lt;br /&gt;
&lt;br /&gt;
Placing escorts directly ahead of the mothership (e.g. &amp;lt;code&amp;gt;new Vector(0, 0, 500);&amp;lt;/code&amp;gt;) or too close to the mothership will trigger collision warnings for the mothership, making it difficult to maintain level flight for any significant time.&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;entityDestroyed&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.75.1}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;entityDestroyed&amp;lt;/code&amp;gt; handler fires immediately &amp;#039;&amp;#039;after&amp;#039;&amp;#039; the ship becomes invalid, regardless of the reason, except when the game restarts. This is the best place for all kind of &amp;#039;clean-up&amp;#039; code, for example stopping [[Oolite_JavaScript_Reference:_Timer|Timers]] associated with the ship script.&lt;br /&gt;
&lt;br /&gt;
 entityDestroyed = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortAccepted&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortAccepted&amp;lt;/code&amp;gt; handler is called when a mother ship accepts this ship as an escort. The mothership simultaneously gets a &amp;lt;code&amp;gt;shipAcceptedEscort&amp;lt;/code&amp;gt; event.&lt;br /&gt;
&lt;br /&gt;
 this.escortAccepted = function(mothership)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortDock&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortDock&amp;lt;/code&amp;gt; handler is called by a mother ships that uses the AI command: &amp;lt;code&amp;gt;dockEscorts&amp;lt;/code&amp;gt;.  Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.&lt;br /&gt;
&lt;br /&gt;
 this.escortDock = function(delay)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;escortRejected&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;escortRejected&amp;lt;/code&amp;gt; handler is called when a mother ship rejects this ship as an escort.&lt;br /&gt;
&lt;br /&gt;
 this.escortRejected = function(mothership)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;offenceCommittedNearby&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;offenceCommittedNearby&amp;lt;/code&amp;gt; handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.&lt;br /&gt;
&lt;br /&gt;
 this.offenceCommittedNearby = function(attacker, victim)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;scriptedAI&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;scriptedAI&amp;lt;/code&amp;gt; handler is called each frame while the ship&amp;#039;s AI is in &amp;quot;performScriptedAI&amp;quot; or &amp;quot;performScriptedAttackAI&amp;quot; mode. It must return an object defining the ship&amp;#039;s flight parameters. The &amp;lt;code&amp;gt;delta&amp;lt;/code&amp;gt; parameter is the length of the current frame in seconds. [[OXP_Scripted_AI|More information on using this functionality]]&lt;br /&gt;
&lt;br /&gt;
 this.scriptedAI = function(delta)&lt;br /&gt;
 {&lt;br /&gt;
   // Your code here&lt;br /&gt;
   return flightParameters;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipAcceptedEscort&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipAcceptedEscort&amp;lt;/code&amp;gt; handler is called when this ship accepts a new ship as an escort. The escort simultaneously gets a &amp;lt;code&amp;gt;escortAccepted&amp;lt;/code&amp;gt; event. &lt;br /&gt;
&lt;br /&gt;
 this.shipAcceptedEscort = function(newEscort)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipLandedOnPlanet&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipLandedOnPlanet&amp;lt;/code&amp;gt; handler is called for ships landing on a planet. It transfers the &amp;lt;code&amp;gt;planet&amp;lt;/code&amp;gt; parameter.&lt;br /&gt;
&lt;br /&gt;
 shipLandedOnPlanet = function(planet)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipRemoved&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipRemoved&amp;lt;/code&amp;gt; handler is called for ships removed by script. It transfers the &amp;lt;code&amp;gt;suppressDeathEvent&amp;lt;/code&amp;gt; parameter so the script knows if there will also follow a shipDied() event.&lt;br /&gt;
&lt;br /&gt;
 shipRemoved = function(suppressDeathEvent)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipSpawned&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipSpawned&amp;lt;/code&amp;gt; handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered. Note that this is not called for subentities - if subentities need specific set up running, this must be called from the main ship&amp;#039;s handler.&lt;br /&gt;
&lt;br /&gt;
 this.shipSpawned = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;spawnedAsEscort&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;spawnedAsEscort&amp;lt;/code&amp;gt; handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument. &lt;br /&gt;
&lt;br /&gt;
 this.spawnedAsEscort = function(mother)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWasDumped&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWasDumped&amp;lt;/code&amp;gt; handler is sent to the cargopod when a ship jettisons it. The dumping ship is transferred as the argument. &lt;br /&gt;
&lt;br /&gt;
 this.shipWasDumped = function(dumper)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;shipWasScooped&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;shipWasScooped&amp;lt;/code&amp;gt; handler is send to the cargopod when a ship scoops scripted_cargo. (&amp;quot;cargo_type&amp;quot; = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on  the handler &amp;lt;code&amp;gt;shipScoopedOther&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
 this.shipWasScooped = function(scooper)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Stations only ===&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;alertConditionChanged&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;alertConditionChanged&amp;lt;/code&amp;gt; handler is called when a station&amp;#039;s alert status ([[Oolite JavaScript Reference: Station#alertCondition|Station.alertCondition]]) changes. Only the player and stations have an alert condition. The equivalent player event is handled inside [[Oolite JavaScript Reference: World script event handlers|world scripts]].&lt;br /&gt;
&lt;br /&gt;
 this.alertConditionChanged = function(newCondition, oldCondition)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;otherShipDocked&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;otherShipDocked&amp;lt;/code&amp;gt; handler is called with a station script only, when an ship docks. It has the docked ship as argument.&lt;br /&gt;
&lt;br /&gt;
 this.otherShipDocked = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationDockingQueuesAreEmpty&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationDockingQueuesAreEmpty&amp;lt;/code&amp;gt; handler is called when the last ship in the queues docks with the station (or gives up docking and leaves).&lt;br /&gt;
&lt;br /&gt;
 this.stationDockingQueuesAreEmpty = function()&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationLaunchedShip&amp;lt;/code&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationLaunchedShip&amp;lt;/code&amp;gt; handler is called with a station script only, when a ship launches. It has the launched ship as argument.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 this.stationLaunchedShip = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationAcceptedDockingRequest&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationAcceptedDockingRequest&amp;lt;/code&amp;gt; handler is called when a ship has requested docking clearance and has been allocated a dock. Due to the way in which docking clearance works, this is likely to be called several times for the same ship as it moves through the docking sequence.&lt;br /&gt;
&lt;br /&gt;
 this.stationAcceptedDockingRequest = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;stationReceivedDockingRequest&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;stationReceivedDockingRequest&amp;lt;/code&amp;gt; handler is called when a ship requests docking clearance. The ship requesting is passed as a parameter. This is often necessary for carriers which will need to come to a stop before ships can dock with them. Due to the way in which docking clearance works, this is likely to be called several times for the same ship as it moves through the docking sequence.&lt;br /&gt;
&lt;br /&gt;
 this.stationReceivedDockingRequest = function(whom)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
(note: a handler by this name was present in 1.79 and 1.80, but was called at the wrong time and should not be used. Set a minimum version of 1.81 if you use this event handler)&lt;br /&gt;
&lt;br /&gt;
==== &amp;lt;code&amp;gt;willOpenDockingPortFor&amp;lt;/code&amp;gt; ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;willOpenDockingPortFor&amp;lt;/code&amp;gt; handler is called with a station script only, when a ship requests docking, in cases where a dock is set to generally disallow docking (i.e. [[Oolite_JavaScript_Reference:_Dock#allowsDocking|allowsDocking]] is &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;). It returns a boolean:&lt;br /&gt;
* if it returns &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; (or this handler isn&amp;#039;t defined), this dock will not be opened later for the requesting ship, and it should not try again.&lt;br /&gt;
* if it returns &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, this dock will be opened later for the requesting ship, and it should try again later if it cannot find another suitable dock on this station.&lt;br /&gt;
The handler is passed the identity of the dock and the requesting ship&lt;br /&gt;
&lt;br /&gt;
 this.willOpenDockingPortFor = function(dock, ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
      return allow;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Docks Only ===&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
==== acceptDockingRequestFrom ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;acceptDockingRequestFrom&amp;lt;/code&amp;gt; handler is called when a ship is looking for docking clearance from the station, and is considering this dock. To get as far as calling this handler, the dock must have &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_Dock#allowsDocking|allowsDocking]] = true&amp;lt;/code&amp;gt; and be large enough to physically fit the ship.&lt;br /&gt;
&lt;br /&gt;
It returns a boolean: &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; to accept the request (which, depending on docking queue lengths will not necessarily mean that this dock is the one that the ship heads for) or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; to reject the request.  &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; is assumed if this handler is not defined.&lt;br /&gt;
&lt;br /&gt;
This handler may be called multiple times for the same ship if the ship is having difficulty finding a suitable docking queue.&lt;br /&gt;
&lt;br /&gt;
 this.acceptDockingRequestFrom = function(ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
      return allow;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
==== acceptLaunchingRequestFrom ====&lt;br /&gt;
{{oolite-method-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;acceptLaunchingRequestFrom&amp;lt;/code&amp;gt; handler is called when a ship is looking for launching clearance from the station, and is considering this dock. To get as far as calling this handler, the dock must have &amp;lt;code&amp;gt;[[Oolite_JavaScript_Reference:_Dock#allowsLaunching|allowsLaunching]] = true&amp;lt;/code&amp;gt; and be large enough to physically fit the ship (unless the ship is the player).&lt;br /&gt;
&lt;br /&gt;
It returns a boolean: &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; to accept the request (which, depending on launching queue lengths will not necessarily mean that this dock is the one that the ship uses) or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; to reject the request.  &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; is assumed if this handler is not defined.&lt;br /&gt;
&lt;br /&gt;
 this.acceptLaunchingRequestFrom = function(ship)&lt;br /&gt;
 {&lt;br /&gt;
      // Your code here&lt;br /&gt;
      return allow;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
=== Missing Events ===&lt;br /&gt;
&lt;br /&gt;
All initially planned events have a corresponding event handler in v1.74.&lt;br /&gt;
&lt;br /&gt;
If there are other events you would like to be able to respond to, please write a request [https://bb.oolite.space/viewtopic.php?t=3296 on the forum].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;See also:&amp;#039;&amp;#039;&amp;#039; [[Oolite JavaScript Reference: World script event handlers|world script event handlers]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3865 distant effects of a ship&amp;#039;s mass or energy?] - analysis of &amp;#039;&amp;#039;&amp;#039;collisions&amp;#039;&amp;#039;&amp;#039; at vast distance back in 2007.&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite JavaScript Reference]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Priming_Equipment&amp;diff=90347</id>
		<title>Priming Equipment</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Priming_Equipment&amp;diff=90347"/>
		<updated>2026-10-17T21:31:30Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Links */ Added another&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Vimana Hud info.png|right|thumb|1000px|Some HUDS display the current selected equipment. The [[Vimana HUD]] (shown here) displays it at #2, together with the next primable equipment)]]&lt;br /&gt;
There is a wide range of additional less-standard equipment available – new inventions, prototypes, specialist items, military technology, scientific research kit, and so forth. As the standard equipment almost fills a typical instrument panel, the following keys can be used to activate extra equipment.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;N&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;: &amp;#039;&amp;#039;&amp;#039;cycle&amp;#039;&amp;#039;&amp;#039; selected equipment (hold Ctrl to reverse cycle direction)&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;n&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;: &amp;#039;&amp;#039;&amp;#039;activate&amp;#039;&amp;#039;&amp;#039; selected equipment (primary activation) - makes it happen!&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;b&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;: activate selected equipment (secondary activation - usually affects the effect of the &amp;#039;n&amp;#039; key, &amp;#039;&amp;#039;ie&amp;#039;&amp;#039; sets the &amp;#039;&amp;#039;&amp;#039;Equipment Mode&amp;#039;&amp;#039;&amp;#039;)&lt;br /&gt;
:The exact meanings of the &amp;#039;n&amp;#039; and &amp;#039;b&amp;#039; keys vary considerably between equipment (“&amp;#039;&amp;#039;&amp;#039;activate&amp;#039;&amp;#039;&amp;#039;” and “&amp;#039;&amp;#039;&amp;#039;change equipment mode&amp;#039;&amp;#039;&amp;#039;” is common) and you should consult the equipment&amp;#039;s manual when it is installed.&lt;br /&gt;
&lt;br /&gt;
=== Fast Activation Keys ===&lt;br /&gt;
For &amp;#039;&amp;#039;&amp;#039;fast activation&amp;#039;&amp;#039;&amp;#039; of particularly useful extra equipment, the  &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;0&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; and  &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Tab&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; keys may be set to send the primary activation signal to an installed piece of equipment without needing to select it first. You may configure which equipment items use these keys, once you have such equipment installed while docked, through an interface on the [[F4 screen (ship and system interfaces)]] (&amp;#039;&amp;#039;&amp;#039;Manage primable equipment&amp;#039;&amp;#039;&amp;#039; under the &amp;quot;Ship Systems&amp;quot; category).&lt;br /&gt;
&lt;br /&gt;
If you do not configure it yourself, convention is that a &amp;#039;&amp;#039;&amp;#039;defensive&amp;#039;&amp;#039;&amp;#039; item will be assigned to the &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;0&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; key, and an &amp;#039;&amp;#039;&amp;#039;offensive&amp;#039;&amp;#039;&amp;#039; item will be assigned to the &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Tab&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; key.&lt;br /&gt;
&lt;br /&gt;
== Extra Equipment HUD displays (MFDs) ==&lt;br /&gt;
To allow additional fitted equipment to display information to your [[HUD]], it is fitted with a number (depending on layout) of multi-function displays ([[MFD]]s). If equipment is providing MFD content, you can cycle the display between the various options with the &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; key. If your HUD has more than one MFD, you can switch between the MFDs with the &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;:&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; key.&lt;br /&gt;
&lt;br /&gt;
The manuals provided with the additional equipment will tell you if it uses MFDs or not.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;:&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; select next MFD - &amp;#039;&amp;#039;ie&amp;#039;&amp;#039; move from MFD slot 3 to MFD slot 4 on your viewscreen&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;ctrl&amp;#039;&amp;#039;&amp;#039; &amp;#039;&amp;#039;&amp;#039;:&amp;#039;&amp;#039;&amp;#039; &amp;lt;/font&amp;gt; select previous MFD  - &amp;#039;&amp;#039;ie&amp;#039;&amp;#039; move from MFD slot 4 to MFD slot 3 on your viewscreen&lt;br /&gt;
&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039; &amp;lt;/font&amp;gt; cycle current MFD forwards - &amp;#039;&amp;#039;ie&amp;#039;&amp;#039; choose which of your possible MFDs you want in slot 3 on your viewscreen - or if you want to leave that slot blank&lt;br /&gt;
: &amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;ctrl&amp;#039;&amp;#039;&amp;#039; &amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039; &amp;lt;/font&amp;gt; cycle current MFD backwards&lt;br /&gt;
&lt;br /&gt;
== Tweaks ==&lt;br /&gt;
{{QuoteText|Text=Have a look through the [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16337 TINKERER&amp;#039;S WORKSHOP] thread. Yes - it is many pages long but is well worth the time spent. In that thread you will find code that allows many OXPs/OXZs to be &amp;quot;turned on&amp;quot; every time you launch from a station or make a jump. What you would normally spend time doing with the Shift+N, N, and B keys upon each launch or jump can be automated. My Special Equipment list is at least 20 items long and none of them need activation upon each launch or jump. In order to do this you would have to be comfortable with editing plists and JavaScripts. Give it a shot as it is well worth the time and effort if you want to automate this process.|Source=([https://bb.oolite.space/viewtopic.php?p=276125#p276125 Nite Owl])}}&lt;br /&gt;
:You may wish to look at [[How to tweak OXZ&amp;#039;s]] if you have not tweaked before.&lt;br /&gt;
&lt;br /&gt;
*This facility was introduced into Oolite with v.1.75 back in 2011&lt;br /&gt;
&lt;br /&gt;
[[File:Primeable Equipment MFD.png|right|thumb|500px|The primable equipment MFD lists all primable equipment with a &amp;quot;&amp;gt;&amp;quot; showing that selected]]&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=6&amp;amp;t=17800 Assign function keys to prime equipment] (2015-date)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18437 How to change/keep Order of Primable Equipment?] (2016)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=18609 Do NPCs use primable equipment?] (2017)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=278126#p278126 In-game keyboard configuration] (2021)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=20685 Markt, zusätzliche Verkaufswarenanzeigen] (2020-date) Milo&amp;#039;s code for introducing another 2 fast activation keys (needs compilation or some such).&lt;br /&gt;
&lt;br /&gt;
=== OXPs ===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Recommended&amp;#039;&amp;#039;&amp;#039; if you have several items of primable equipment:&lt;br /&gt;
*[[Primeable Equipment MFD]] allows you to prime equipment through an MFD, but allowing a look at the current first eight pieces of primeable equipment (the others move up as you toggle through them...). This is the best way of handling a selection of primable equipment, as we currently only have the two fast activation buttons for game use.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Help pages]] [[Category:Equipment| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Shipdata.plist&amp;diff=90346</id>
		<title>Shipdata.plist</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Shipdata.plist&amp;diff=90346"/>
		<updated>2026-10-17T21:29:07Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* equipment_price_factor */ Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{QuoteText|Text=The shipdata.plist would be more accurately called objectdata nowadays - a &amp;quot;ship&amp;quot; in Oolite might be a ship, a station, a rock, basically any solid object smaller than a planet (or moon)|Source=([https://bb.oolite.space/viewtopic.php?p=275475#p275475 Cim])}}&lt;br /&gt;
&lt;br /&gt;
= Format =&lt;br /&gt;
Shipdata.plist is in [[Property list]] format.&lt;br /&gt;
The shipdata document is a dictionary of ships. Example:&lt;br /&gt;
&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;rsvh_adder&amp;quot; = {&lt;br /&gt;
        like_ship = &amp;quot;adder&amp;quot;;&lt;br /&gt;
        is_external_dependency = yes;&lt;br /&gt;
        pilot = &amp;quot;oolite-hunter&amp;quot;;&lt;br /&gt;
        roles = &amp;quot;rrs-vicious-hunter(1)&amp;quot;;&lt;br /&gt;
        &amp;quot;missile_role&amp;quot; = &amp;quot;EQ_HARDENED_MISSILE&amp;quot;;&lt;br /&gt;
    	&amp;quot;script_info&amp;quot; = {&lt;br /&gt;
    		&amp;quot;randomshipnames&amp;quot; = &amp;quot;hunter&amp;quot;;&lt;br /&gt;
    		&amp;quot;skilled_npc_role&amp;quot; = &amp;quot;hunter&amp;quot;;&lt;br /&gt;
    	};&lt;br /&gt;
      };&lt;br /&gt;
    &lt;br /&gt;
      &amp;quot;rsvh_asp&amp;quot; = {&lt;br /&gt;
        like_ship = &amp;quot;asp&amp;quot;;&lt;br /&gt;
        is_external_dependency = yes;&lt;br /&gt;
        pilot = &amp;quot;oolite-hunter&amp;quot;;&lt;br /&gt;
        roles = &amp;quot;rrs-vicious-hunter(1)&amp;quot;;&lt;br /&gt;
        &amp;quot;aft_weapon_type&amp;quot; = &amp;quot;WEAPON_BEAM_LASER&amp;quot;;&lt;br /&gt;
    	&amp;quot;script_info&amp;quot; = {&lt;br /&gt;
    		&amp;quot;randomshipnames&amp;quot; = &amp;quot;hunter&amp;quot;;&lt;br /&gt;
    		&amp;quot;skilled_npc_role&amp;quot; = &amp;quot;hunter&amp;quot;;&lt;br /&gt;
    	};&lt;br /&gt;
      };&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;shipdata.[[plist]]&amp;#039;&amp;#039;&amp;#039; will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure|(extra)]]. The following (property) entries are, for order&amp;#039;s sake, listed alphabetically:&lt;br /&gt;
&lt;br /&gt;
= Ship keys=&lt;br /&gt;
The following keys are used by all ships&lt;br /&gt;
==accuracy==&lt;br /&gt;
Used with missiles it has influence on tracking of target. Allowed values with missiles are between 0.0 and 10.0. When not defined, the system assigns to the missile the accuracy value of 0.0, which corresponds to the standard missile tracking behaviour.&lt;br /&gt;
&lt;br /&gt;
In 1.76 or earlier, when used with NPC ships it slightly enlarges the chance of shooting at greater distances, and makes a small improvement to their aim. Value with NPC ships is between -5 and 10 though all values between -5 and +1 will be increased to +1. When not defined, NPCs will be assigned a random value in the range +1 to +10.&lt;br /&gt;
&lt;br /&gt;
In 1.77 or later, when used with NPC ships it affects various aspects of the ship AI. Values can be assigned between -5 and +10. When not defined, a random value between -5 and +5 will be used. [[OXP_NPC_Combat_AI|NPC accuracy]] significantly affects the quality of the AI in combat.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;accuracy&amp;quot; = 8.3;&lt;br /&gt;
&lt;br /&gt;
In detail, and so far, and none of this applies to Thargoids:&lt;br /&gt;
* in general, accuracy affects aim more than it used to (low accuracy are worse than before, high are better)&lt;br /&gt;
* accuracy &amp;gt;= 0 removes some bad combat tactics from consideration, deals with laser overheating more usefully, sets a minimum missile_load_time (if none was given in shipdata), and makes token efforts to dodge your lasers while fleeing&lt;br /&gt;
* accuracy &amp;gt;= 5 is the threshold for advanced combat tactics and must be explicitly applied to a ship.&lt;br /&gt;
* accuracy &amp;gt;= 5 takes evasive action if hit, and will try to keep you off their six at close range much more&lt;br /&gt;
* accuracy &amp;gt;= 6 applies a larger &amp;quot;jink&amp;quot; at long range while fleeing or retreating, to make a harder target&lt;br /&gt;
* accuracy &amp;gt;= 7.5 gives much closer target tracking. They will miss much less than before.&lt;br /&gt;
* accuracy &amp;gt;= 8.5 enables &amp;quot;sniper&amp;quot; AI. It&amp;#039;s not much use without a forward military laser, but is deadly with one&lt;br /&gt;
* accuracy &amp;gt;= 9 significantly increases the size of the &amp;quot;jink&amp;quot; for fleeing and retreating&lt;br /&gt;
:See Cim&amp;#039;s detailed explanation [https://bb.oolite.space/viewtopic.php?p=173293#p173293 here] (2012) - and over several posts the simple schema above is added to.&lt;br /&gt;
:Compare with [[Shipdata.plist#reaction_time|reaction_time]]&lt;br /&gt;
&lt;br /&gt;
== aft_eject_position ==&lt;br /&gt;
Determines the XYZ point on the model from which cargo is ejected.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;aft_eject_position&amp;quot; = &amp;quot;0.0 -4.5 -23.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== aft_weapon_type ==&lt;br /&gt;
Assigns the ship&amp;#039;s aft laser. &lt;br /&gt;
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE). &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;aft_weapon_type&amp;quot; = &amp;quot;WEAPON_BEAM_LASER&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== ai_type ==&lt;br /&gt;
Assigns an AI to the entity. This may be a previously existing AI, or one custom made for the occasion.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;ai_type&amp;quot; = &amp;quot;pirateAI.plist&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== auto_ai ==&lt;br /&gt;
This will autoswitch the ai to the appropriate one if a ship was added in one of its standard roles like trader or pirate. (true by default). See also the comment in the autoAIMap.plist inside Oolite. Defining auto_ai is only necessary when using one of the standard roles mentioned in the autoAIMap.plist for your ship. auto_ai does nothing for ships with custom roles.&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;auto_ai&amp;quot; = yes;&lt;br /&gt;
This auto_ai switch is also used for bounties. When auto_ai is false the ship will keep the bounty as defined for the ship but, when true and the ship is added in one of the populator roles, the ship will get the default bounty for that role.&lt;br /&gt;
&lt;br /&gt;
== auto_weapons ==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
This parameter if true (the default is false) indicates to the Oolite system populator (and potentially to OXPs) that they may change the weapons, missile load, equipment and other such parameters of this ship to make it better fit its role. This allows you to specify a single hull for multiple roles, and have the ship re-equipped to suit those roles. Ships intended for general addition to the spacelanes in standard roles and not intended to be significantly different in difficulty to the core ships should probably turn this on. OXPs: For example, [[Skilled NPCs]] only affects those ships with this parameter set to true.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;auto_weapons&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
See [https://bb.oolite.space/viewtopic.php?p=235800#p235800 here] for more detail&lt;br /&gt;
&lt;br /&gt;
== beacon ==&lt;br /&gt;
A special feature for beacons and navigation aids.&lt;br /&gt;
The string can be anything - the first letter was what was displayed in the advanced space compass before Oolite v.1.79. It is still the only display for the older [[HUD]]&amp;#039;s.&lt;br /&gt;
&lt;br /&gt;
Example: &lt;br /&gt;
 &amp;quot;beacon&amp;quot; = &amp;quot;X&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Characters that are known to be used as identifiers for &amp;#039;&amp;#039;&amp;#039;stations and other fixed objects&amp;#039;&amp;#039;&amp;#039; are found on the page for the [[Advanced_Space_Compass#List_of_Navigational_Buoys|Advanced Space Compass]]. Most letters have been used multiple times in various OXPs. &lt;br /&gt;
&lt;br /&gt;
Since v.1.79 the HUD also displays a longer label; before that several HUD OXPs were available to do something similar (see [[Advanced Space Compass]]).&lt;br /&gt;
&lt;br /&gt;
We can also use custom icons with the compass. For that you must define a key in descriptions.plist with the same name as the beacon definition.  Than define the icon in the same way as missile icons. (An array of x/y-coordinates that will be connected by lines). You can find more info at [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=9529 the Oolite BB].&amp;lt;br&amp;gt;&lt;br /&gt;
Example in shipdata:&lt;br /&gt;
 &amp;quot;beacon&amp;quot; = &amp;quot;fuelStation_location&amp;quot;;&lt;br /&gt;
Example in descriptions.plist&lt;br /&gt;
 &amp;quot;fuelStation_location&amp;quot; =  (1, 2, -3, 2, -3, -4, 3, -4, 3, 4,  -3, 4, -3, 3, 2, 3, 2, -3, 1, -3 );&lt;br /&gt;
Before 1.75 the ships primary role was used for defining the icon name in descriptions.plist, but since 1.75 the beacon name itself is used.&lt;br /&gt;
&lt;br /&gt;
There are several devices which detect things from great distance: the Vanilla game&amp;#039;s [[Advanced Space Compass]], [[The Galactic Almanac OXZ]], [[Telescope]] and the [[Long Range Scanner]]. The last is a cheat OXP useful for programmers. See the [https://bb.oolite.space/viewtopic.php?p=281279#p281279 HIMSN thread] for details of making things invisible to them.&lt;br /&gt;
&lt;br /&gt;
== beacon_label ==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
A full label for the beacon. If this is not set, it will default to be the same as &amp;lt;code&amp;gt;beacon&amp;lt;/code&amp;gt;, but it may be useful to have a beacon with a full label starting with a different letter than its code. The beacon label text will be expanded using the standard description rules&lt;br /&gt;
 &amp;quot;beacon_label&amp;quot; = &amp;quot;%H Station&amp;quot;; // Lave Station, Diso Station, etc.&lt;br /&gt;
&lt;br /&gt;
== bounty ==&lt;br /&gt;
Sets a Cr. reward on the NPC&amp;#039;s head, and is bound to give it trouble with the law . This bounty setting is overruled when adding ships in one of the populator roles like pirate, trader etc. Pirates are default added with a small bounty and traders are added clean. However, like the player, also the npc bounty can raise when attacking other clean ships or police vessels.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;bounty&amp;quot; = 50;&lt;br /&gt;
&lt;br /&gt;
== cargo_carried ==&lt;br /&gt;
Determines the type of cargo carried as described in [[commodities]] and [[commodities.plist]].  Only one type can be specified. This key can be used for both ships and barrels.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cargo_carried&amp;quot; = &amp;quot;Gold&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
When used for barrels, it is also possible to add several units in a pod by preceding the commodity name with a space separated number. Adding more than a ton in a pod is not possible. Defining a quantity for ships is not possible this way.&amp;lt;br&amp;gt;&lt;br /&gt;
It is possible to define a mix of random cargo for ships by using the string &amp;quot;SCARCE_GOODS&amp;quot; or &amp;quot;PLENTIFUL_GOODS&amp;quot;, instead of a commodity name. The first selects random goods that are scarce at the main station, the second selects goods that are plentiful present at the main station. (Populator added traders heading toward the station always have scarce goods while traders heading from the main station always have plentiful goods on board. It would be wise to stick to this rule with custom ships.)&amp;lt;br&amp;gt;&lt;br /&gt;
To make cargo_carried working for ships, the cargo_type must be &amp;quot;CARGO_NOT_CARGO&amp;quot; to define the ship not being cargo itself. (see below)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;: A bug introduced in 1.82 means that only commodity keys from the [[Trade-goods.plist]] are recognised here. That is &amp;quot;gold&amp;quot; will be recognised, whereas &amp;quot;Gold&amp;quot; will not. This bug is fixed in the 1.83/1.84 release.&lt;br /&gt;
&lt;br /&gt;
== [[cargo_type]] ==&lt;br /&gt;
Determines if object is indeed cargo (CARGO_RANDOM, CARGO_SLAVES, CARGO_THARGOID, CARGO_ALLOY, CARGO_MINERALS, CARGO_CARRIED) or a ship, as below, which is not cargo.  (CARGO_RANDOM is not fully random but means that a container can hold any kind of commodity.)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cargo_type&amp;quot; = &amp;quot;CARGO_RANDOM&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Will create random cargo, often based on availability in the system. When you want fixed cargo you can use:&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cargo_type&amp;quot; = &amp;quot;CARGO_CARRIED&amp;quot;;&lt;br /&gt;
 &amp;quot;cargo_carried&amp;quot; = &amp;quot;4 Gold&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
You can also specify the cargo of a ship. use &amp;quot;cargo_type&amp;quot; = CARGO_NOT_CARGO  and define the contents of the barrels it will give with &amp;quot;cargo_carried&amp;quot;. In that case there must be no quantity defined, only the type of [[commodity]].&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cargo_type&amp;quot; =  &amp;quot;CARGO_NOT_CARGO&amp;quot;;&lt;br /&gt;
 &amp;quot;cargo_carried&amp;quot; = &amp;quot;Computers&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Another notable type of cargo is the scripted item CARGO_SCRIPTED_ITEM, as exemplified by the cloaking device. When CARGO_SCRIPTED_ITEM is defined, the barrels will trigger scooping events for the ship-scripts. Other barrels don&amp;#039;t trigger scooping events.&amp;lt;br&amp;gt;&lt;br /&gt;
The cargo barrels are stored in the ships hold like normal barrels when a cargo was defined for them with the JS method &amp;quot;setCargo&amp;quot;. Without defined content, scripted barrels are removed after scooping. Scripted cargo works with any object that can be scooped. When you have scripted escape pods that must be preserved after scooping, fill it with one ton of Slaves.&lt;br /&gt;
&lt;br /&gt;
== cloak_automatic ==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
When false, the cloak of npc ships will never get activate automatic during combat, but is only activated by JS script commands. (True by default)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cloak_automatic&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
== cloak_passive ==&lt;br /&gt;
When true, any firing of laser will deactivate the cloak. (False by default in 1.76 or earlier, true by default in 1.77 or later) &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;cloak_passive&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
==conditions==&lt;br /&gt;
With this option you can include an array of extra conditions when to add a ship. When the conditions are not met, the ship does not appear in a selection list by role. Useful when you have a standard ship like a trader that should only be added in certain systems.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;conditions&amp;quot; = (&lt;br /&gt;
                 &amp;quot;systemGovernment_number equal 3&amp;quot;,&lt;br /&gt;
                 &amp;quot;systemEconomy_number lessthan 4&amp;quot;&lt;br /&gt;
                );&lt;br /&gt;
&lt;br /&gt;
==condition_script==&lt;br /&gt;
&amp;#039;&amp;#039;Available from Oolite 1.77 onwards&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
This option specifies a Javascript file which controls the addition of this ship. The &amp;lt;code&amp;gt;allowSpawnShip&amp;lt;/code&amp;gt; function in that [[Oolite_JavaScript_Reference:_Condition_scripts|condition script]] will then be tested before the ship is added. Several ships can share a condition script.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;condition_script&amp;quot; = &amp;quot;myoxp_conditions.js&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== counts_as_kill ==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
Killing this ship will not count as a kill by the player when set to false. (Default is true). Using this key prevents awarding kills to all kind of cargo, debris etc.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;counts_as_kill&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
== custom_views==&lt;br /&gt;
Will add the ability to display custom POVs of the player ship, in game toggled by pressing &amp;#039;&amp;#039;&amp;#039;v&amp;#039;&amp;#039;&amp;#039;.  &lt;br /&gt;
&lt;br /&gt;
This is an array with any number of entries, one for each view, each with:&lt;br /&gt;
*a &amp;#039;&amp;#039;&amp;#039;view_description&amp;#039;&amp;#039;&amp;#039; - giving a textual description of the view. &lt;br /&gt;
*a &amp;#039;&amp;#039;&amp;#039;view_position&amp;#039;&amp;#039;&amp;#039; - relative to the origin of the ship model. &lt;br /&gt;
*a &amp;#039;&amp;#039;&amp;#039;view_orientation&amp;#039;&amp;#039;&amp;#039; - this is a [[Quaternions|quaternion]] expressing a rotation from directly forwards. &lt;br /&gt;
*a &amp;#039;&amp;#039;&amp;#039;weapon_facing&amp;#039;&amp;#039;&amp;#039; - FORWARD, AFT, PORT or STARBOARD. The weapon that will fire when that view is selected.&lt;br /&gt;
&lt;br /&gt;
The view_position is best chosen by selecting a facet, line or point in Wings and copying down the coordinates. &lt;br /&gt;
&lt;br /&gt;
For the view_orientation you will probably need a calculator but the basic method is to choose a unit vector (x y z) as the axis for a rotation then calculate the four values W X Y and Z for the quaternion as follows: &lt;br /&gt;
&lt;br /&gt;
W = the cosine of half the angle rotated about the axis xyz&amp;lt;br /&amp;gt;&lt;br /&gt;
X = the sine of half the angle rotated about xyz, multiplied by x&amp;lt;br /&amp;gt;&lt;br /&gt;
Y = the sine of half the angle rotated about xyz, multiplied by y &amp;lt;br /&amp;gt;&lt;br /&gt;
Z = the sine of half the angle rotated about xyz, multiplied by z &amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Four decimal places are probably enough accuracy for these values.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
  custom_views =&lt;br /&gt;
 (&lt;br /&gt;
     {&lt;br /&gt;
         view_description = &amp;quot;Front View&amp;quot;;&lt;br /&gt;
         view_orientation = &amp;quot;0.0 0.0 1.0 0.0&amp;quot;;&lt;br /&gt;
         view_position = &amp;quot;0.0 30.0 200.0&amp;quot;;&lt;br /&gt;
         weapon_facing = &amp;quot;FORWARD&amp;quot;;&lt;br /&gt;
     }&lt;br /&gt;
 );&lt;br /&gt;
&lt;br /&gt;
== death_actions ==&lt;br /&gt;
Gives an opportunity to have a ship&amp;#039;s death trigger one or a set of [[Shipdata.plist#script_actions|script_actions]]. It contains an array of legacy script expressions.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;death_actions&amp;quot; = (&amp;quot;spawn: explosive_shrapnel 1&amp;quot;);&lt;br /&gt;
 &lt;br /&gt;
== debris_role ==&lt;br /&gt;
{{oolite-prop-added|1.74}}&lt;br /&gt;
&lt;br /&gt;
Specifies the kind of debris an asteroid or boulder generates. When not defined they default to generating &amp;#039;ships&amp;#039; with role &amp;quot;boulder&amp;quot; or &amp;quot;splinter&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;debris_role&amp;quot; = &amp;quot;my_boulder_foo&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
See the discussion here: [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=10061 (RELEASE) Icesteroids V2] (2011-12) - about role circularity and about the vanilla game code creating alloys whenever anything big explodes!&lt;br /&gt;
&lt;br /&gt;
== density ==&lt;br /&gt;
This real value is used to calculate a ships total mass. Default is 1.0. The mass of the ship is then 20 * density * volume.&lt;br /&gt;
&lt;br /&gt;
Ship&amp;#039;s mass does not affect its flight under the non-inertial engines - see [[#thrust|thrust]]. It does affect:&lt;br /&gt;
* changes in momentum, and damage done, in a collision&lt;br /&gt;
* the minimum distance needed from this ship for another ship to open a witchspace wormhole (the blocking radius is the square root of a tenth of the mass)&lt;br /&gt;
* the length of time a witchspace wormhole opened by this ship will remain open, and the radius of that wormhole.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;density&amp;quot; = 1.5;&lt;br /&gt;
&lt;br /&gt;
* See Eric Walch&amp;#039;s comment on vanilla-game Coriolis stations [https://bb.oolite.space/viewtopic.php?p=118196#p118196 here] (2010)&lt;br /&gt;
* See Captain Beatnik&amp;#039;s note on ramming [https://bb.oolite.space/viewtopic.php?p=296569#p296569 here] (2024)&lt;br /&gt;
&lt;br /&gt;
== display_name ==&lt;br /&gt;
States the model&amp;#039;s name as it will be known to the ID computer. By default this is the same as &amp;quot;name&amp;quot;. Added for multilingual oolite.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;display_name&amp;quot; = &amp;quot;ExampleShip Mark IX&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== energy_recharge_rate ==&lt;br /&gt;
The rate at which energy is replenished.  Stations are at 100, Adders at 2. (Default value: 1)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;energy_recharge_rate&amp;quot; = &amp;quot;3.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
See [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12152 Energy rates and recharge] for more detail (2012)&lt;br /&gt;
&lt;br /&gt;
== escape_pod_model ==&lt;br /&gt;
With this entry ships can have custom escape pods. Defaults to &amp;quot;escape-capsule&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Since v1.65:&amp;#039;&amp;#039;&amp;#039; You have to specify the &amp;#039;&amp;#039;&amp;#039;role&amp;#039;&amp;#039;&amp;#039; of your custom escape pod (not its entry-name).&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Since v1.77:&amp;#039;&amp;#039;&amp;#039; Deprecated in favour of &amp;lt;code&amp;gt;escape_pod_role&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;escape_pod_model&amp;quot; = &amp;quot;custom_pod_role&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; Each shipdata entry has an implicit unique role in the form of a shipdata key enclosed in square brackets - e.g. &amp;quot;[entry-name]&amp;quot;. It might be useful if you want to use a specific escape pod that has no unique role.&lt;br /&gt;
&lt;br /&gt;
== escape_pod_role ==&lt;br /&gt;
With this entry ships can have custom escape pods. It&amp;#039;s almost the same as &amp;lt;code&amp;gt;escape_pod_model&amp;lt;/code&amp;gt;, but has a less ambiguous name. Added in v1.77.&lt;br /&gt;
&lt;br /&gt;
The game first tries to spawn a pod using &amp;lt;code&amp;gt;escape_pod_role&amp;lt;/code&amp;gt;, but if the property isn&amp;#039;t set or a spawn fails, the game uses &amp;lt;code&amp;gt;escape_pod_model&amp;lt;/code&amp;gt;. If the latter fails too, the game tries the &amp;quot;escape-capsule&amp;quot; role.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;escape_pod_model&amp;quot; = &amp;quot;custom_pod_role&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== escorts ==&lt;br /&gt;
Determines how many escorts an NPC shall have. Maximum is 16.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;escorts&amp;quot; = 4;&lt;br /&gt;
Warning: Ships with scanClass = CLASS_POLICE should always have escorts set to zero. Oolite will set this value here and add wingmans instead of escorts. Without special scripting escorts won&amp;#039;t escort a mother with CLASS_POLICE.&amp;lt;br&amp;gt;&lt;br /&gt;
For ships that are added in a trader role, the populator can decide to subtract escorts from the defined value when the system is estimated as safe. &lt;br /&gt;
&lt;br /&gt;
== escort_role ==&lt;br /&gt;
Assigns the specific ship type to be the escort, by the ship&amp;#039;s role. (Before Oolite 1.74 only the name &amp;quot;escort-role&amp;quot; is accepted.)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;escort_role&amp;quot; = &amp;quot;my_custom_escort_role&amp;quot;;&lt;br /&gt;
Escort ships will use the escortAI.plist unless &amp;quot;auto_ai&amp;quot; is set to false.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==escort_roles==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
This property overrules &amp;lt;code&amp;gt;escorts&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;escort_role&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;escort_ship&amp;lt;/code&amp;gt; to allow more flexible specification of a ship&amp;#039;s escorts. It takes the form of a list of dictionaries, each containing a &amp;quot;role&amp;quot;, &amp;quot;min&amp;quot; and &amp;quot;max&amp;quot; key. The ship will then get between &amp;quot;min&amp;quot; and &amp;quot;max&amp;quot; of that role of escort ship (specific ships can be added using the &amp;quot;[dataKey]&amp;quot; style of role), with &amp;quot;max&amp;quot; more likely in Anarchy systems and &amp;quot;min&amp;quot; more likely in Corporate States.&lt;br /&gt;
&lt;br /&gt;
   escort_roles = (&lt;br /&gt;
      { role = &amp;quot;escort&amp;quot;; min = -2; max = 2; },&lt;br /&gt;
      { role = &amp;quot;escort-medium&amp;quot;; min = 0; max = 4; },&lt;br /&gt;
      { role = &amp;quot;escort-heavy&amp;quot;; min = -4; max = 2; },&lt;br /&gt;
      { role = &amp;quot;&amp;quot;; min = 0; max = 2; } // spare slots for wandering escorts&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
A negative number can be used for &amp;quot;min&amp;quot; - this makes it more likely that none of this type of escort will be used in safer systems, and makes the maximum number less likely in the more dangerous systems. In the example above, the ship will mainly be escorted by &amp;quot;escort-medium&amp;quot; ships, with a couple of &amp;quot;escort&amp;quot; ships likely in unsafe systems, and a small chance of &amp;quot;escort-heavy&amp;quot; ships also appearing in more dangerous systems.&lt;br /&gt;
&lt;br /&gt;
Leaving the role key blank allows the ship to have spare slots for escorts which are left unfilled when the ship is spawned. This can be used to simulate a willingness to hire additional escorts, or to indicate that the ship has already lost some of its escorts.&lt;br /&gt;
&lt;br /&gt;
The maximum number of escorts remains 16, and the list will be processed from top to bottom. Once 16 escorts are added no further entries will be considered.&lt;br /&gt;
&lt;br /&gt;
== escort_ship ==&lt;br /&gt;
Assigns the specific ship type to be the escort, by the ship&amp;#039;s name. (Before Oolite 1.74 only the name &amp;quot;escort-ship&amp;quot; is accepted.)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;escort_ship&amp;quot; = &amp;quot;cobramk1&amp;quot;;&lt;br /&gt;
Escort ships will use the escortAI.plist unless &amp;quot;auto_ai&amp;quot; is set to false.&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.77 and later it is also possible to use &amp;lt;code&amp;gt;&amp;quot;escort_role&amp;quot; = &amp;quot;[cobramk1]&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== exhaust ==&lt;br /&gt;
The XYZ position(s) of exhaust plume(s), and the XYZ of the plume shape, ergo&lt;br /&gt;
&lt;br /&gt;
 x y z width height length&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;x y z&amp;#039;&amp;#039;&amp;#039; is the position relative to the origin of the main model. &lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;width&amp;#039;&amp;#039;&amp;#039; in meters, how far a plume extends on x axis, on each side of plume position. (x radius)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;height&amp;#039;&amp;#039;&amp;#039; in meters, how far a plume extends on y axis, above and below of plume position. (y radius)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;length&amp;#039;&amp;#039;&amp;#039; in meters, how long a plume is on z axis. (This value is in current Oolite versions ignored. Length is now derived from the ships speed)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Below are 2 assigned plumes at coords 5, 0, -25 and -5, 0, -25, and each plume is 6 m wide and 4 m tall. (length info is ignored)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;exhaust&amp;quot; = (&lt;br /&gt;
     &amp;quot;5 0.0 -25 3.0 2.0 10.0&amp;quot;,&lt;br /&gt;
     &amp;quot;-5 0.0 -25 3.0 2.0 10.0&amp;quot;&lt;br /&gt;
 );&lt;br /&gt;
&lt;br /&gt;
== exhaust_emissive_color ==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
Determines the colour of the exhausts.&lt;br /&gt;
&lt;br /&gt;
For the colour you can use either a [[Materials in Oolite#Colour specifiers|colour specifier]] or a [[Materials in Oolite#Named colours|named colour]]. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;exhaust_emissive_color&amp;quot; = &amp;quot;redColor&amp;quot;;&lt;br /&gt;
or&lt;br /&gt;
 &amp;quot;exhaust_emissive_color&amp;quot; = &amp;quot;1 0 0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== explosion_type ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
A list of [[explosions.plist]] entries describing how the ship explodes if destroyed.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;explosion_type&amp;quot; = (&amp;quot;oolite-default-asteroid-explosion&amp;quot;);&lt;br /&gt;
&lt;br /&gt;
== extra_cargo ==&lt;br /&gt;
Cargobay extension size can be customised. This is the amount the cargo capacity increases when an extra cargobay is installed. Default value is 15. It is only used with player ships.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;extra_cargo&amp;quot; = 25;&lt;br /&gt;
&lt;br /&gt;
== forward_weapon_type ==&lt;br /&gt;
Assigns the ship&amp;#039;s forward laser. &lt;br /&gt;
Any weapon type from the [[equipment.plist]] can be used.&amp;lt;br&amp;gt; e.g.: WEAPON_PULSE_LASER, WEAPON_BEAM_LASER, WEAPON_MILITARY_LASER, WEAPON_MINING_LASER, WEAPON_PLASMA_CANNON, WEAPON_THARGOID_LASER and WEAPON_NONE. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;forward_weapon_type&amp;quot; = &amp;quot;WEAPON_BEAM_LASER&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== frangible ==&lt;br /&gt;
Determines if eventual sub-entities are &amp;quot;loose&amp;quot;. By default any given object is already frangible, so the use of this line must be to negate that. &lt;br /&gt;
If set to false, the object plus subentities will be regarded as a single object.&lt;br /&gt;
If set to true, sub entities can be destroyed seperately from the main object. Frangible sub-entities can have a max_energy and an energy_recharge_rate that is independently set from the main entity.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;frangible&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
See the discussion here: [https://bb.oolite.space/viewtopic.php?t=15823 NPCs with frangible guns (2013)] - about how NPC AI should react when frangibles are franged!&lt;br /&gt;
&lt;br /&gt;
== fragment_chance ==&lt;br /&gt;
Determines if a ship breaks apart into fragments and generates parts with role &amp;quot;wreckage&amp;quot;. By chance factor, or true/false. Default is 90% chance.&lt;br /&gt;
The amount of wreckage is based on the ships mass with a maximum of 3. Wreckage is scaled to match the ships size but is very short living. (0.25s -&amp;gt; 1.25s)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;fragment_chance&amp;quot; = no;&lt;br /&gt;
 &lt;br /&gt;
== fuel ==&lt;br /&gt;
Determines an NPC ship&amp;#039;s fuel storage, which will affect how it uses its Fuel Injectors and how far it can jump. If unspecified the default is zero (though ships added via the system populator will often be given some fuel anyway)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;fuel&amp;quot; = 70;&lt;br /&gt;
&lt;br /&gt;
== has_cloaking_device ==&lt;br /&gt;
Determines if a ship has a cloacking device installed. By chance factor, or true/false.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_cloaking_device&amp;quot; = 0.5;&lt;br /&gt;
&lt;br /&gt;
== has_ecm ==&lt;br /&gt;
Determines if a ship has the E.C.M system installed. By chance factor, or true/false.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_ecm&amp;quot; = 0.5;&lt;br /&gt;
or&lt;br /&gt;
 &amp;quot;has_ecm&amp;quot; = no;&lt;br /&gt;
 &lt;br /&gt;
== has_energy_bomb ==&lt;br /&gt;
Determines if a ship has an energy bomb. If it has one, it might launch a mine with role &amp;quot;energy_bomb&amp;quot; as part of his fleeing behavior. currently the only build-in mine with this role is the q-bomb.&amp;lt;br&amp;gt;A ship will only deploy the bomb when it has also fuel-injectors and some fuel left to avoid getting killed by its own bomb. On average it will try to deploy the bomb once every 100 seconds during fleeing.&lt;br /&gt;
&lt;br /&gt;
Example:		&lt;br /&gt;
 &amp;quot;has_energy_bomb&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== has_escape_pod ==&lt;br /&gt;
Determines if a ship has an escape pod. Can be either a boolean value, or a number from 0 to 1 expressing the likelihood of the equipment being present. Starting with version 1.65 ships can have multiple escape pods. To specify more than one escape pod, &amp;#039;&amp;#039;&amp;#039;has_escape_pod&amp;#039;&amp;#039;&amp;#039; must be set to a numeric value corresponding to the escape pods present on board.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
 has_escape_pod = no;&lt;br /&gt;
 has_escape_pod = 0.75;&lt;br /&gt;
 has_escape_pod = 3;&lt;br /&gt;
&lt;br /&gt;
== has_fuel_injection ==&lt;br /&gt;
Determines if a ship has the witchdrive fuel injector.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_fuel_injection&amp;quot; = 0.99;&lt;br /&gt;
&lt;br /&gt;
==has_military_jammer==&lt;br /&gt;
Determines if a ship has a military jammer. Ships equipped with this item become invisible on the radar. &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_military_jammer&amp;quot; = 0.75;&lt;br /&gt;
&lt;br /&gt;
==has_military_scanner_filter==&lt;br /&gt;
Determines if a ship has a military jammer filter. Ships equipped with this item can see ships equipped with a military jammer on the radar. &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_military_scanner_filter&amp;quot; = 0.50;&lt;br /&gt;
&lt;br /&gt;
== has_scoop ==&lt;br /&gt;
Determines if a ship has a fuel/cargo scoop.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_scoop&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
== has_scoop_message ==&lt;br /&gt;
A key for cargo. Determines if a barrel generates a default scoop message when scooped. Default is true, but setting it to false suppresses any messages, so a scripts can generate its custom messages on scooping. (Added with Oolite 1.74)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_scoop_message&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
== has_shield_booster==&lt;br /&gt;
Determines if a ship has the shield booster. (enlarges max energy with 256)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_shield_booster&amp;quot; = 0.80;&lt;br /&gt;
&lt;br /&gt;
== has_shield_enhancer ==&lt;br /&gt;
Determines if a ship has the coveted shield enhancer. (enlarges max energy with 256 and raises energy recharge rate with 50%)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_shield_enhancer&amp;quot; = 0.45;&lt;br /&gt;
&lt;br /&gt;
== heat_insulation ==&lt;br /&gt;
This real number gives the amount of heat insulation of a ship. Default is 1.0 (2.0 for ships equipped with EQ_HEAT_SHIELD). Values below 0.125 will be increased to that minimum. This parameter is only for NPC ships and stations. Player ships ignore this and always start with 1.0 heat insulation and can add an additional 1.0 (for a total of 2.0) with the ship equipment EQ_HEAT_SHIELD. Heat insulation for NPCs is only a factor when close to the sun. Energy damage does not cause overheating (because otherwise it would be too easy to overheat NPC ships with missiles or lasers), but it can raise ships&amp;#039; temperature to the maximum safe level. Overheating occurs when a ship&amp;#039;s temperature exceeds the safe level, which is determined by the heat insulation level. External temperature is determined by distance from the sun. Larger suns are hotter. Suns that are going nova are, unsurprisingly, even warmer. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;heat_insulation&amp;quot; = &amp;quot;2.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
NPC ships launched from stations are given the same heat insulation as the station if the station&amp;#039;s is greater than the ship&amp;#039;s. Courier ships generated by the core system populator are given a heat insulation level of 6.0. Escort ships (if any) receive at least the same heat insulation as the ship they are escorting. See [https://bb.oolite.space/viewtopic.php?p=177357#p177357 BB Thread] (2012)&lt;br /&gt;
&lt;br /&gt;
Player ships use the same model as NPC ships for external temperature from the sun, but additionally simulate heat from air friction when inside planetary atmospheres, which is a factor that NPC ships ignore.&lt;br /&gt;
&lt;br /&gt;
== hud ==&lt;br /&gt;
Used for a playership, to assign another HUD than the default one. Note that small ships get the second default - the hud-small.plist&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;hud&amp;quot; = &amp;quot;specialhud.plist&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== hyperspace_motor ==&lt;br /&gt;
If set to false / NO, it will stop ships from executing normal hyperspace jump (player ships will still be able to execute galactic jumps). Default = true / YES. (Planned for Oolite 1.75)&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
 &amp;quot;hyperspace_motor&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
 hyperspace_motor=NO;&lt;br /&gt;
&lt;br /&gt;
== hyperspace_motor_spin_time ==&lt;br /&gt;
Used to modify jump countdown time. Default = 15.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
 &amp;quot;hyperspace_motor_spin_time&amp;quot; = &amp;quot;15&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==injector_burn_rate==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The default fuel burn rate of injectors on this ship, in deci-LY per second. The default is 0.25.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;injector_burn_rate&amp;quot; = 0.25;&lt;br /&gt;
&lt;br /&gt;
==injector_speed_factor==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The multiplier applied to the ship&amp;#039;s maximum speed when it is using injectors. The default is 7.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;injector_speed_factor&amp;quot; = 7;&lt;br /&gt;
&lt;br /&gt;
==is_external_dependency==&lt;br /&gt;
This key should be added to ships that use like_ship references to ships in other oxps but don&amp;#039;t depend on them. Normally will Oolite write errors in the log when it can&amp;#039;t resolve a like_ship reference. When this key is set to YES, it will suppress the error generation.&amp;lt;br&amp;gt;WARNING: only set this key to YES when the model won&amp;#039;t get added to the system without the other oxp installed or you will miss a valuable warning.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;is_external_dependency&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
==is_hulk==&lt;br /&gt;
Boolean value to indicate that this ship will be spawned as &amp;quot;Derelict&amp;quot;, as if the pilot had ejected and left the floating hulk behind.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;is_hulk&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
==is_submunition==&lt;br /&gt;
Key added for missiles with multiple warheads. When this key is set and the entity is spawn or fired by a missile, it inherits its parent as owner. This key must be set so the player will be awarded for a kill by submunition.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;is_submunition&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
==is_template==&lt;br /&gt;
Set this to yes for ships which are only used through like_ships and are not intended to be used directly. If your (otherwise working) OXP generates warnings about ships with no roles or model attribute, you probably need this.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;is_template&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== laser_color ==&lt;br /&gt;
Determines a ship&amp;#039;s laser colour.&lt;br /&gt;
&lt;br /&gt;
As colour you can use a [[Materials in Oolite#Colour specifiers|colour specifier]] or a [[Materials in Oolite#Named colours|named colour]]. The game requires laser colours to be reasonably bright; if the brightest colour component is less than 0.5, the colour will be brightened.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;laser_color&amp;quot; = &amp;quot;cyanColor&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== launch_actions ==&lt;br /&gt;
Triggers a script on the entity just after setup, also when called by spawn and addShip methods.&lt;br /&gt;
Can be used to change to a custom AI, when a ship is generated by standard role. &lt;br /&gt;
[[Shipdata.plist#script_actions|script_actions]]&lt;br /&gt;
&lt;br /&gt;
 Example:&lt;br /&gt;
 &amp;quot;role = trader&amp;quot;;&lt;br /&gt;
 &amp;quot;launch_actions&amp;quot; = (&lt;br /&gt;
   &amp;quot;setAITo: pirateAI.plist&amp;quot;&lt;br /&gt;
  );&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== like_ship ==&lt;br /&gt;
Allows a shipdata entry (of a ship with many matching characteristics to another) to be short and sweet. With &amp;#039;&amp;#039;&amp;#039;like_ship&amp;#039;&amp;#039;&amp;#039; you can reference to another existing shipdata entry, and then only specify the differences to the &amp;#039;original&amp;#039;. It takes the unique &amp;#039;&amp;#039;&amp;#039;entry-identifier&amp;#039;&amp;#039;&amp;#039; as argument. Of course you have to make sure that the &amp;#039;original&amp;#039; you are referring to actually exists, or Oolite won&amp;#039;t be able to create your ship.&lt;br /&gt;
&lt;br /&gt;
Works well together with the [[#is_template|is_template]]-key.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;my_ship&amp;quot; = {&lt;br /&gt;
 &amp;quot;like_ship&amp;quot; = &amp;quot;adder&amp;quot;;&lt;br /&gt;
 &amp;quot;max_flight_speed&amp;quot; = &amp;quot;700&amp;quot;;&lt;br /&gt;
 &amp;quot;name&amp;quot; = &amp;quot;Freak Turbo Adder&amp;quot;;&lt;br /&gt;
 },&lt;br /&gt;
&lt;br /&gt;
== likely_cargo ==&lt;br /&gt;
This is only used for ships with role asteroid and pirate. With asteroids it gives the likely number of boulders it breaks into. With pirates added by the [[System Populator]]: when lower than 16 it is the cargo, when higher than 15, it is changed in a random value between 0 and 15. This value is overridden by the actual scooped cargo if the pirate had scooped something.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;likely_cargo&amp;quot; = &amp;quot;2&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== materials ==&lt;br /&gt;
See [[Materials in Oolite]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== max_cargo ==&lt;br /&gt;
Sets the ship&amp;#039;s cargo limit. On explosion of trader ships added by the [[System Populator]], 10% of this value is used as likely cargo. When the result is lower than 16 it is the cargo, when higher than 15, it is changed in a random value between 0 and 15.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_cargo&amp;quot; = &amp;quot;5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== max_energy ==&lt;br /&gt;
Sets the ship&amp;#039;s energy value. (Default value: 200)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_energy&amp;quot; = &amp;quot;300&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
See [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12152 Energy rates and recharge] for more detail (2012). Divide by 64 to get the rough number of energy banks.&lt;br /&gt;
&lt;br /&gt;
== max_flight_pitch ==&lt;br /&gt;
Sets pitch factor. Will usually range from a sluggish 0.6 to a very sensitive 3.0&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_flight_pitch&amp;quot; = &amp;quot;2.2&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== max_flight_roll ==&lt;br /&gt;
Sets roll factor. Will usually range from 0.8 to 4.6.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_flight_roll&amp;quot; = &amp;quot;4.2&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== max_flight_speed ==&lt;br /&gt;
Sets the model&amp;#039;s top speed. Interceptors fly at 520 (0.52 LM), Shuttles at 80.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_flight_speed&amp;quot; = &amp;quot;320&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== max_flight_yaw ==&lt;br /&gt;
Sets yaw factor. Will usually range from a sluggish 0.6 to a very sensitive 3.0 When no value is defined it will use the same value as max_flight_pitch&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_flight_yaw&amp;quot; = &amp;quot;2.2&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== max_missiles ==&lt;br /&gt;
Sets a ship&amp;#039;s missile limit. Maximum allowable value for the player is 16 and for npc ships 32. When not defined, the value with &amp;quot;missiles&amp;quot; is used as max_missiles. When defining more than a few missiles, it could be wise to also define value for &amp;quot;missile_load_time&amp;quot; to avoid massive missile launches. npc ships are more likely to fire missiles the more they carry.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_missiles&amp;quot; = &amp;quot;1&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== missile_launch_position ==&lt;br /&gt;
Determines the XYZ point on the model from which a missile is launched.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;missile_launch_position&amp;quot; = &amp;quot;0.0 -2.25 10.0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
This position should lie outside the bounding box of the core entity and not just outside of the ships mesh.  Default value: (0, -4, 1)&amp;lt;br&amp;gt;&lt;br /&gt;
If the position does lie inside the bounding box, the launch position is shifted along its direction until the launched missile lies outside the bounding box of the central entity. (Bounding boxes of subentities are ignored) The collision radius of the launched missile is taken into account. The collision radius for a plain missile is 4.52 meter.&lt;br /&gt;
&lt;br /&gt;
== missile_load_time ==&lt;br /&gt;
Defines the time in seconds before a new missile is ready to fire after one is fired. Mainly useful for npc ships that have many missiles.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;missile_load_time&amp;quot; = &amp;quot;2.1&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== missiles ==&lt;br /&gt;
Sets the number of missiles the ship is equipped with on ship creation. e.g. you can set this at zero and than use a dedicated script to fill up the bay with specific missiles.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;missiles&amp;quot; = &amp;quot;0&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== missile_role ==&lt;br /&gt;
Defines the type of missiles (or mines) an NPC ship is provided with. Default is &amp;quot;EQ_MISSILE&amp;quot;. When missiles are loaded on ship creation, 90% will be of this type and 10% will be random, chosen from all possible NPC missiles and mines. Also affects the javascript [[Oolite_JavaScript_Reference:_Ship#selectNewMissile|selectNewMissile()]] command.&lt;br /&gt;
The string defined inside missile_role needs both to be defined inside [[equipment.plist]], and be inside the &amp;#039;&amp;#039;&amp;#039;roles&amp;#039;&amp;#039;&amp;#039; property of the missile/mine shipdata entry. &lt;br /&gt;
&lt;br /&gt;
To assign a specific missile type to a newly bought player ship, its dependancies must be defined inside [[shipyard.plist]].&lt;br /&gt;
&lt;br /&gt;
Example: &lt;br /&gt;
 &amp;quot;missile_role&amp;quot; = &amp;quot;EQ_THARGON&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Missiles&amp;quot; of course include bombs and other pylon-mounted equipment. See [https://bb.oolite.space/viewtopic.php?t=21923 Quirium Cascade Bomb] (2025) for a discussion of some of the issues.&lt;br /&gt;
&lt;br /&gt;
== model ==&lt;br /&gt;
Assigns the entity&amp;#039;s corresponding &amp;#039;&amp;#039;&amp;#039;.dat&amp;#039;&amp;#039;&amp;#039; file that will be found with the exact same name in the &amp;#039;&amp;#039;Models&amp;#039;&amp;#039; folder.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;model&amp;quot; = &amp;quot;example_ship.dat&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== model_scale_factor ==&lt;br /&gt;
1.81 or later only.&lt;br /&gt;
&lt;br /&gt;
If this is set, the model specified in the &amp;lt;code&amp;gt;model&amp;lt;/code&amp;gt; property will be scaled by this factor (the default is 1.0, of course). Additionally, all subentities will have both their positions and sizes scaled (recursively if necessary), and the weapon positions will also be multiplied by the scale factor.&lt;br /&gt;
&lt;br /&gt;
Player ships will also have their internal and external view positions multiplied by the scale factor.&lt;br /&gt;
&lt;br /&gt;
model_scale_factors on subentities will be ignored - the value for the main entity will be used instead.&lt;br /&gt;
&lt;br /&gt;
Note: is the [[Oolite_JavaScript_Reference:_Ship#setMaterials|ship.setMaterials]] method is used, the model_scale_factor will be reset on that ship instance.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;model_scale_factor&amp;quot; = 2.0;&lt;br /&gt;
&lt;br /&gt;
== name ==&lt;br /&gt;
States the model&amp;#039;s name as it will be known to the ID computer.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;name&amp;quot; = &amp;quot;ExampleShip Mark IX&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
See also [[Shipdata.plist#display_name|display name]], [[Shipdata.plist#ship_name|ship_name]] &amp;amp; [[Shipdata.plist#ship_class_name|ship_class_name]]&lt;br /&gt;
&lt;br /&gt;
== no_boulders ==&lt;br /&gt;
With older versions, scripted asteroids had no boulders by default. Starting with 1.70 all asteroids produce boulders when hit by a mining laser. no_boulders can overwrite this to emulate the old situation. By chance factor, or true/false.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;no_boulders&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== pilot ==&lt;br /&gt;
Gives the ship a predefined pilot, defined in [[characters.plist]]. Can eject in pod, if available, and be captured.&amp;lt;BR&amp;gt;&lt;br /&gt;
By default every object starts with a pilot except buoys, missiles, cargo and rocks. By defining a specific pilot,  any default pilot is replaced or a pilot is added to previously unpiloted objects.&lt;br /&gt;
  &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;pilot&amp;quot; = &amp;quot;constrictor-mission-thief&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
When no pilot is defined, Oolite will create a random pilot based on the ships role. For custom roles this means that Oolite has no clue and the pilot might have other bounties/insurances than desired. For this reason contains Oolite, starting with v 1.75, some predefined pilots: &amp;quot;oolite-trader&amp;quot;, &amp;quot;oolite-pirate&amp;quot;, &amp;quot;oolite-hunter&amp;quot;, &amp;quot;oolite-police&amp;quot;, &amp;quot;oolite-miner&amp;quot;, &amp;quot;oolite-passenger&amp;quot; and &amp;quot;oolite-slave&amp;quot;. When using one of these pilots, a random bounty/insurance will be set appropriate for this pilot role. Pilot bounty is different as ship bounty but on ejecting the pilot inherits the highest of both values. (actually a bitwise OR of both values)&lt;br /&gt;
&lt;br /&gt;
== port_weapon_type ==&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
Assigns the ship&amp;#039;s port laser. &lt;br /&gt;
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE). &lt;br /&gt;
&lt;br /&gt;
While not essential, you should generally assign the same weapon to [[#starboard_weapon_type|starboard_weapon_type]].&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;port_weapon_type&amp;quot; = &amp;quot;WEAPON_BEAM_LASER&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
No vanilla game NPCs have side lasers. OXP ships who do have side lasers will also use yaw to line up their shots. ([https://bb.oolite.space/viewtopic.php?p=234057#p234057 Cim, 2015]). Some earlier OXPs &amp;#039;&amp;#039;did&amp;#039;&amp;#039; add side lasers, but the then vanilla game code could do nothing with them!&lt;br /&gt;
&lt;br /&gt;
== reaction_time ==&lt;br /&gt;
Sets the reaction time of the pilot of this ship. The default is 1.5 seconds.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;reaction_time&amp;quot; = 1.0; // this pilot is superhuman! or a cat&lt;br /&gt;
&lt;br /&gt;
== roles ==&lt;br /&gt;
Assigns which [[role]](s) the entity should have, that can correspond to one specific, exclusive use, or several.&lt;br /&gt;
&lt;br /&gt;
The game engine constantly calls for generic roles to populate the universe.  In the example below the ship in question will be considered twice as often (2.0) when a trader is called for, only one quarter as often (0.25) when looking for a hunter, and as often as any other pirate ships when looking for a pirate. Multiple roles are space separated. An explanation of the generic roles available in Oolite 1.79 or later is at [[Oolite_Ship_Roles]].&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;NB:&amp;#039;&amp;#039;&amp;#039; If the ship cannot be docked to, extra care should be taken to avoid using the words &amp;#039;&amp;#039;&amp;#039;station&amp;#039;&amp;#039;&amp;#039; or &amp;#039;&amp;#039;&amp;#039;carrier&amp;#039;&amp;#039;&amp;#039; as part of any of the ship&amp;#039;s role names. When either of these words are inside the roles key, the ship is automatically given station attributes. Other ships might even fruitless try to dock with it, and it will affect how some ships / entities are shown on the scanner.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;roles&amp;quot; = &amp;quot;hunter(0.25) trader(2.0) pirate&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
or an exclusive role, simply:&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;roles&amp;quot; = &amp;quot;uniquely_named_role&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
This has the benefit of being the only ship to be selected when a [[Script.plist|script]] calls for the &amp;#039;&amp;#039;uniquely_named_role&amp;#039;&amp;#039; ship.&lt;br /&gt;
&lt;br /&gt;
An item from the [[commodities]] can also be named as a role, for when that commodity is floating in space and called upon, to be represented by a particular model.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;roles&amp;quot; = &amp;quot;Gold&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Some roles are used by the game engine to populate systems, detect and define properties. (see also the [[System Populator]])&lt;br /&gt;
Such roles include &amp;#039;thargoid&amp;#039;, &amp;#039;missile&amp;#039; and &amp;#039;energybomb&amp;#039;.&lt;br /&gt;
Externally used equipment also needs specific mention of role, for example EQ_*_MINE and EQ_*_MISSILE.&lt;br /&gt;
&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?p=98050#p98050 1 1/2 pages of discussion of station population percentages] (2010)&lt;br /&gt;
&lt;br /&gt;
== rotational_velocity ==&lt;br /&gt;
May be applied to a sub-entity, like the following entry to the [[Shipdata.plist#subentities|subentity]] spines of the [[Weeviloid Hunter]].&lt;br /&gt;
Takes the form of [[Quaternions|quaternions]]. The following example enables rotation around the Z-axis.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;rotational_velocity&amp;quot; = &amp;quot;0.707 0.0 0.0 0.707&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
An explaining example taken from the Oolite Bulletin board.&lt;br /&gt;
&lt;br /&gt;
The rotational velocity key is rotation per second. For instance, if you want to rotate once per 20 seconds around the Z axis:&lt;br /&gt;
 &lt;br /&gt;
a = 360 ° / 20 = 18 °&lt;br /&gt;
&lt;br /&gt;
[x, y, z] = [0, 0, 1]&lt;br /&gt;
 &lt;br /&gt;
sin a ˜ 0.30902&lt;br /&gt;
 &lt;br /&gt;
cos a ˜ 0.95106&lt;br /&gt;
 &lt;br /&gt;
Q = (0.95106, 0, 0, 0.30902)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;shipdata.plist entry:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
 &amp;quot;rotational_velocity&amp;quot;=&amp;quot;0.95106 0.0 0.0 0.30902&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
In practical terms, one can therefore use &lt;br /&gt;
 &amp;quot;rotational_velocity&amp;quot;=&amp;quot;3 0 0 1&amp;quot;&lt;br /&gt;
To alter the speed of rotation increase number 3, for slower rotations, decrease for higher speed. For opposite rotational direction, change 1 to -1.[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=6899&amp;amp;p=93038&amp;amp;hilit=rotational+velocity+key#p93038 (ref: Arhuman BB 1/11-09)]&lt;br /&gt;
&lt;br /&gt;
== scan_class ==&lt;br /&gt;
Will alter the model&amp;#039;s appearance on the [[IFF system]].  If this line is omitted, it will usually become by default a standard ship entity (CLASS_NEUTRAL), appearing as a yellow flag on the radar (red if hostile to the player), but may be given a different scan class if added with other roles.  There are other options.&lt;br /&gt;
* CLASS_BUOY - green/yellow on scanner, will rotate in idle state, does not masslock&lt;br /&gt;
* CLASS_CARGO - white on scanner, can be scooped, does not masslock&lt;br /&gt;
* CLASS_MILITARY - purple on scanner, better pilots, will not attack other military ships, flashes purple/magenta if hostile to player&lt;br /&gt;
* CLASS_MISSILE - cyan on scanner, will not avoid collisions&lt;br /&gt;
* CLASS_POLICE - purple on scanner, will not attack other police ships, legal penalties for attacking, never has bounty, flashes purple/magenta if hostile to player&lt;br /&gt;
* CLASS_ROCK - white on scanner, launched defense ships do not inherit scan class, does not masslock&lt;br /&gt;
* CLASS_STATION - green on scanner, launched defense ships do not inherit scan class&lt;br /&gt;
* CLASS_THARGOID - green/red on scanner, considered hostile to any non-thargoid ship&lt;br /&gt;
* CLASS_NO_DRAW - invisible on scanner, cannot be targeted by missiles, does not masslock&lt;br /&gt;
* CLASS_MINE - red/yellow on scanner, automatically set on mines launched by player to override existing scan class, does not masslock&lt;br /&gt;
(This property was called &amp;quot;scanClass&amp;quot; before Oolite 1.74.)&lt;br /&gt;
Scan classes marked as &amp;quot;does not masslock&amp;quot; will masslock the player anyway if they are hostile to the player (as condition will be Red)&lt;br /&gt;
&lt;br /&gt;
Scripts can define custom colours for ships on the [[IFF system]] so ships may have a scanner appearance different to the default for their scan class.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scan_class&amp;quot; = &amp;quot;CLASS_ROCK&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
==== Developer Note ====&lt;br /&gt;
*Oolite uses scan_class internally to determine the behaviour of some ships (particularly with regard to who may shoot whom without incurring legal penalties). Bear this in mind and don&amp;#039;t allocate CLASS_POLICE or CLASS_THARGOID to ships lightly!&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=4585 More cops for your money?] scan-class vs Role (2008)&lt;br /&gt;
&lt;br /&gt;
== scan_description ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The description of the ship&amp;#039;s legal status on the [[Scanner Targeting Enhancement]]. If this is absent, the default text for the scan class will be used.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;scan_description&amp;quot; = &amp;quot;Unclaimed rock&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note: There was a bug in version 1.90 where setting this property in shipdata.plist would cause a game fault. The issue was fixed in 1.92. To set the property in versions prior to 1.92, use the [[Oolite_JavaScript_Reference:_Ship#scanDescription|scanDescription]] property of the ship object.&lt;br /&gt;
&lt;br /&gt;
== scanner_display_color1 ==&lt;br /&gt;
Overrides the color that would normally be set by scanClass.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scanner_display_color1&amp;quot; = &amp;quot;greenColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== scanner_display_color2 ==&lt;br /&gt;
Overrides the color that would normally be set by scanClass. If this is set, the ship will flash between the two colours.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scanner_display_color2&amp;quot; = &amp;quot;redColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== scanner_hostile_display_color1 ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Overrides the color that would normally be set by scanClass when the ship is hostile and targeting the player.&lt;br /&gt;
&lt;br /&gt;
If no hostile colours are set, but normal colours are set, then the normal colours, not the scan class colours, will be used for a hostile ship.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scanner_hostile_display_color1&amp;quot; = &amp;quot;greenColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== scanner_hostile_display_color2 ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Overrides the color that would normally be set by scanClass when the ship is hostile and targeting the player. If this is set, the ship will flash between the two colours.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scanner_hostile_display_color2&amp;quot; = &amp;quot;redColor&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== scanner_range ==&lt;br /&gt;
Sets a custom scanner range. Standard is 25.6 km, thargoids have 50 km. Only applies to NPCs. However, at least since oolite 1.65 all defined scanner ranges are limited to 25.6 km, even for thargoids. This means it only makes sense defining shorter ranges than the maximum range.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scanner_range&amp;quot; = &amp;quot;25600&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== scoop_position ==&lt;br /&gt;
Determines the XYZ point on the model from which cargo is scooped. (default is 0,0,0)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;scoop_position&amp;quot; = &amp;quot;0.0 -4.5 -23.0&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Scooping for a player ship starts when the cargo collides with the front half of the bottom of the ship. Any other place of first contact leads to smashing the cargo in pieces. A good y-value for the position would therefor be half the size of the lowest body part of this area of the ship. For the z-value a point in the back side would be better.&lt;br /&gt;
&lt;br /&gt;
[https://bb.oolite.space/viewtopic.php?p=55413#p55413 2008 note] by Eric Walsh on what this &amp;#039;&amp;#039;does&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
== script ==&lt;br /&gt;
Specifies a [[Oolite_JavaScript_Reference:_Ship_script_event_handlers |Ship Script]] (through it&amp;#039;s filename) to attach to the ship. Ship scripts written in [[Scripting Oolite with JavaScript|JavaScript]] are the preferred approach for scripting ships in current Oolite.&lt;br /&gt;
&lt;br /&gt;
== script_info ==&lt;br /&gt;
A property list whose contents are available to JavaScript scripts, for whatever use they desire. It is exposed to JavaScript as the &amp;lt;code&amp;gt;[[Oolite JavaScript Reference: Ship#scriptInfo|scriptInfo]]&amp;lt;/code&amp;gt; property of &amp;lt;code&amp;gt;Ship&amp;lt;/code&amp;gt; objects.&amp;lt;br&amp;gt;&lt;br /&gt;
Take note that when using an ascii plist, the JS engine will read in all entries as strings. When you need an entry as number, you might need to explicit convert it to a number. This is specially true for booleans as a &amp;quot;NO&amp;quot; string will be read as true. For all normal keys its Oolite that does the conversion for you.&lt;br /&gt;
&lt;br /&gt;
A short overview about used [[OXP_scriptInfo|script_info keys in OXPs]].&lt;br /&gt;
&lt;br /&gt;
== script_actions ==&lt;br /&gt;
Gives an oportunity to insert events such as in [[script.plist]], to involve a specific shipdata entity.  As seen in the following example, this particular object checks if Player has a cloaking device, and if not, will award it.  Should Player already have it, the gift will be in gold. See also [[scripts within shipdata]] for more detailled info.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;script_actions&amp;quot; =&lt;br /&gt;
 (&lt;br /&gt;
     &amp;quot;testForEquipment: EQ_CLOAKING_DEVICE&amp;quot;,&lt;br /&gt;
     {&lt;br /&gt;
        &amp;quot;conditions&amp;quot;&lt;br /&gt;
        (&lt;br /&gt;
           &amp;quot;foundEquipment_bool equal NO&amp;quot;&lt;br /&gt;
        )&lt;br /&gt;
        &amp;quot;do&amp;quot;&lt;br /&gt;
        (&lt;br /&gt;
           &amp;quot;awardEquipment: EQ_CLOAKING_DEVICE&amp;quot;&lt;br /&gt;
        )&lt;br /&gt;
        &amp;quot;else&amp;quot;&lt;br /&gt;
        (&lt;br /&gt;
           &amp;quot;awardCargo: 100 Gold&amp;quot;&lt;br /&gt;
        )&lt;br /&gt;
     }&lt;br /&gt;
 );&lt;br /&gt;
&lt;br /&gt;
== setup_actions ==&lt;br /&gt;
Arranges a process that may be necessary for some objects, like ball turrets.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;setup_actions&amp;quot; =&lt;br /&gt;
 (&lt;br /&gt;
    &amp;quot;initialiseTurret&amp;quot;&lt;br /&gt;
 );&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== shaders ==&lt;br /&gt;
The &amp;#039;&amp;#039;shaders&amp;#039;&amp;#039; dictionary has the same structure as the &amp;#039;&amp;#039;[[#materials|materials]]&amp;#039;&amp;#039; dictionary. When [[Shaders in Oolite|shaders]] are available, the contents of the &amp;#039;&amp;#039;shaders&amp;#039;&amp;#039; dictionary are used in preference to those in &amp;#039;&amp;#039;materials&amp;#039;&amp;#039;. If shaders are not available, the &amp;#039;&amp;#039;shaders&amp;#039;&amp;#039; dictionary is ignored.&lt;br /&gt;
&lt;br /&gt;
== ship_name ==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The name of this individual ship (e.g. Pride of Lave), which is placed in [[Oolite_JavaScript_Reference:_Ship#shipUniqueName|ship.shipUniqueName]]. It rarely makes sense to set this property in &amp;lt;code&amp;gt;shipdata.plist&amp;lt;/code&amp;gt;, except perhaps for a unique mission ship.&lt;br /&gt;
&lt;br /&gt;
== ship_class_name ==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The name of this ship&amp;#039;s class (e.g. Sidewinder), which is placed in [[Oolite_JavaScript_Reference:_Ship#shipClassName|ship.shipClassName]]. If this is not set, it will default to [[#name|name]], which is usually suitable.&lt;br /&gt;
&lt;br /&gt;
== show_damage ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Whether to show sparks and other damage effects when this ship is hit.&lt;br /&gt;
&lt;br /&gt;
Defaults to on if energy recharge rate is greater than zero, off otherwise, for compatibility with previous hard-coded behaviour.&lt;br /&gt;
&lt;br /&gt;
== smooth ==&lt;br /&gt;
Determines if the model will use glLightModel(GL_FLAT) or glLightModel(GL_SMOOTH).&lt;br /&gt;
&lt;br /&gt;
If true, then lighting effects will be interpolated across the polygons of the model, giving a more &amp;#039;rounded&amp;#039; effect.&lt;br /&gt;
&lt;br /&gt;
Asteroids, Boulders and Splinters use this effect as do some other models.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;smooth&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== spawn ==&lt;br /&gt;
The spawn directory is only used when a ship is added with the command: &amp;quot;spawnShip: shipname&amp;quot;.  This command only allows to add one ship by name (not role!). The position and orientation are taken from a spawn directory that describes the position it is placed and the position it is looking at.&lt;br /&gt;
&lt;br /&gt;
Example&lt;br /&gt;
 &amp;quot;spawn&amp;quot;&lt;br /&gt;
 {&lt;br /&gt;
       &amp;quot;facing_position&amp;quot; = &amp;quot;spu 0 0 0&amp;quot;;&lt;br /&gt;
       &amp;quot;position&amp;quot; = &amp;quot;wpu 0 0 0.2&amp;quot;;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== starboard_weapon_type ==&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
Assigns the ship&amp;#039;s starboard laser. &lt;br /&gt;
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE). &lt;br /&gt;
&lt;br /&gt;
While not essential, you should generally assign the same weapon to [[#port_weapon_type|port_weapon_type]].&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;starboard_weapon_type&amp;quot; = &amp;quot;WEAPON_BEAM_LASER&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
No vanilla game NPCs have side lasers. OXP ships who do have side lasers will also use yaw to line up their shots. ([https://bb.oolite.space/viewtopic.php?p=234057#p234057 Cim, 2015]). Some earlier OXPs &amp;#039;&amp;#039;did&amp;#039;&amp;#039; add side lasers, but the then vanilla game code could do nothing with them!&lt;br /&gt;
&lt;br /&gt;
== subentities ==&lt;br /&gt;
An array of &amp;#039;&amp;#039;subentity definitions&amp;#039;&amp;#039;. A &amp;#039;&amp;#039;subentity&amp;#039;&amp;#039; is an object attached to your ship. There are several types of subentity:&lt;br /&gt;
* &amp;#039;&amp;#039;Static subentities&amp;#039;&amp;#039;, the default type, are simply extra models. They are defined as separate shipdata.plist entries, so technically they’re ships, but they don’t have a mind of their own. If the main ship is [[#frangible|frangible]], static subentities can take damage and blow up separately from the main ship. They can also be individually exploded or removed by scripts. See for example the shuttles in the four docks at the front of the Emerald [[liners]].&lt;br /&gt;
* &amp;#039;&amp;#039;Docks&amp;#039;&amp;#039; are recognized when setting up a station or carrier, and used to determine the station’s docking port parameters. After set-up, they work just like normal static subentities. The string &amp;quot;dock&amp;quot; in lowercase must be part of the old style name in order to get recognised as the dock subEntity. &lt;br /&gt;
* &amp;#039;&amp;#039;Ball turrets&amp;#039;&amp;#039; turn to track the ship’s current target, and shoot plasma balls if the target is within range (6000 metres). A ball turret’s field of fire is a 157 ° cone centred on its original facing. Currently, ball turrets make no effort not to shoot their own ship, so it is up to the designer to ensure this field of fire is clear. Like a static subentity, a ball turret is based on a shipdata.plist entry so its appearance can be customized. Oolite provides a built-in shipdata entry for ball turrets called, imaginatively, &amp;#039;&amp;#039;&amp;#039;ballturret&amp;#039;&amp;#039;&amp;#039;. &lt;br /&gt;
: For discussion on the effective range (before the reduction from the original 7500 to 7200) see [https://bb.oolite.space/viewtopic.php?p=198854#p198854 here].&lt;br /&gt;
:Note that the [[Vortex]] turrets can be switched off. This involved special scripting (basically removing and restoring the turrets by script). Needs a little fancy footwork when docked though or else if you dock with removed sub-entities (even deliberately removed ones) you&amp;#039;ll get a maintenance overhaul offered which will put them back if purchased.&lt;br /&gt;
* &amp;#039;&amp;#039;Flashers&amp;#039;&amp;#039; are blobs which glow with a pulsating light. From Oolite 1.74 onwards, constant light will also be an option. Note that while flashers appear luminous – they are unaffected by shadows – they do not cast light on other objects. See Phkb&amp;#039;s revamp of the Pulsar in [[Tianve OXP]].&lt;br /&gt;
* Random number of Subentities (&amp;#039;&amp;#039;eg&amp;#039;&amp;#039; Cargo pods): see [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18743 Can the number of entities a ship be randomized?] (2017)&lt;br /&gt;
&lt;br /&gt;
=== New-style subentity definition ===&lt;br /&gt;
Oolite 1.73 introduced a more flexible, dictionary-based way of specifying subentities. A new-style subentity is a dictionary using the following keys:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width:100%&amp;quot;&lt;br /&gt;
|+ Subentity definition properties&lt;br /&gt;
! Name !! Type !! Description&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;type&amp;#039;&amp;#039;&amp;#039; || string || One of: “&amp;#039;&amp;#039;&amp;#039;standard&amp;#039;&amp;#039;&amp;#039;”, “&amp;#039;&amp;#039;&amp;#039;ball_turret&amp;#039;&amp;#039;&amp;#039;”, “&amp;#039;&amp;#039;&amp;#039;flasher&amp;#039;&amp;#039;&amp;#039;”. If not specified, “standard” is assumed.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;subentity_key&amp;#039;&amp;#039;&amp;#039; || string || The key of a &amp;#039;&amp;#039;shipdata.plist&amp;#039;&amp;#039; entry. Required for &amp;#039;&amp;#039;&amp;#039;standard&amp;#039;&amp;#039;&amp;#039; and &amp;#039;&amp;#039;&amp;#039;ball_turret&amp;#039;&amp;#039;&amp;#039; subentities, ignored for flashers.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;position&amp;#039;&amp;#039;&amp;#039; || vector || The position of the subentity relative to its parent. (This can be specified as a string with three numbers in it, or an array of three numbers, or a dictionary with &amp;#039;&amp;#039;&amp;#039;x&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;y&amp;#039;&amp;#039;&amp;#039; and &amp;#039;&amp;#039;&amp;#039;z&amp;#039;&amp;#039;&amp;#039; entries.) Default: (0, 0, 0).&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;orientation&amp;#039;&amp;#039;&amp;#039; || [[quaternion]] || The orientation of the subentity. Ignored for flashers. (This can be specified as a string with four numbers in it, or an array of four numbers, or a dictionary with &amp;#039;&amp;#039;&amp;#039;w&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;x&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;y&amp;#039;&amp;#039;&amp;#039; and &amp;#039;&amp;#039;&amp;#039;z&amp;#039;&amp;#039;&amp;#039; entries.) Default: (1, 0, 0, 0), which corresponds to no rotation.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;is_dock&amp;#039;&amp;#039;&amp;#039; || boolean || True if the subentity is a dock; false by default. Only applies to &amp;#039;&amp;#039;&amp;#039;standard&amp;#039;&amp;#039;&amp;#039; subentities. &amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; this is &amp;#039;&amp;#039;not&amp;#039;&amp;#039; implied by having “dock” in the &amp;#039;&amp;#039;&amp;#039;subentity_key&amp;#039;&amp;#039;&amp;#039;, as it is for old-style subentity definitions. In Oolite 1.76 or earlier a station may only have at most one dock subentity.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width:100%&amp;quot;&lt;br /&gt;
|+ Subentity definition properties for dock subentities (1.77 or later)&lt;br /&gt;
! Name !! Type !! Description&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;allow_docking&amp;#039;&amp;#039;&amp;#039; || boolean || &amp;#039;&amp;#039;In Oolite 1.77 or later&amp;#039;&amp;#039;, whether the dock allows docking. Defaults to true. (and always true in 1.76). Ignored for non-docks.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;allow_launching&amp;#039;&amp;#039;&amp;#039; || boolean || &amp;#039;&amp;#039;In Oolite 1.77 or later&amp;#039;&amp;#039;, whether the dock allows launching. Defaults to true. (and always true in 1.76).  Ignored for non-docks.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;disallowed_docking_collides&amp;#039;&amp;#039;&amp;#039; || boolean || &amp;#039;&amp;#039;In Oolite 1.77 or later&amp;#039;&amp;#039;, if this is true, ships attempting to dock here will collide with the dock if &amp;lt;code&amp;gt;allow_docking&amp;lt;/code&amp;gt; is false. If it is false, ships attempting to dock here will be docked with the station anyway. Defaults to false. (and always false in 1.76).  Ignored for non-docks.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;dock_label&amp;#039;&amp;#039;&amp;#039; || string || &amp;#039;&amp;#039;In Oolite 1.77 or later&amp;#039;&amp;#039;, the name given to the dock by traffic control (overrides the display_name of the dock subentity). Defaults to &amp;quot;the docking bay&amp;quot;, and ignored for non-docks. In Oolite 1.76 or earlier the concept of dock names is meaningless.&lt;br /&gt;
|}&lt;br /&gt;
See [[Multiple Docks]] for more information on dock subentities and stations with more than one dock in Oolite 1.77 or later.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width:100%&amp;quot;&lt;br /&gt;
|+ Subentity definition properties for ball turrets&lt;br /&gt;
! Name !! Type !! Description&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;fire_rate&amp;#039;&amp;#039;&amp;#039; || number || Interval between shots in seconds, for &amp;#039;&amp;#039;&amp;#039;ball_turret&amp;#039;&amp;#039;&amp;#039; subentities. Default: 0.5; minimum: 0.25.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;weapon_range&amp;#039;&amp;#039;&amp;#039; || number || Range for &amp;#039;&amp;#039;&amp;#039;ball_turret&amp;#039;&amp;#039;&amp;#039; subentities. Default: 6000; maximum 7200.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;weapon_energy&amp;#039;&amp;#039;&amp;#039; || number || Weapon energy for &amp;#039;&amp;#039;&amp;#039;ball_turret&amp;#039;&amp;#039;&amp;#039; subentities. Default: 25; maximum 100.&lt;br /&gt;
|}&lt;br /&gt;
See [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12085 New range of turrets] for more information on turret subentities (2012 discussion about modelling, quaternions, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;). &amp;lt;br&amp;gt;&lt;br /&gt;
See [https://bb.oolite.space/viewtopic.php?p=300891#p300891 here] for a note on how turret weapon range has changed over the years&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width:100%&amp;quot;&lt;br /&gt;
|+ Subentity definition properties for flashers&lt;br /&gt;
! Name !! Type !! Description&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;color&amp;#039;&amp;#039;&amp;#039; || [[Materials in Oolite#Colour specifiers|colour specifier]] || Single colour for a flasher. Ignored for non-flashers. Default value: &amp;#039;&amp;#039;&amp;#039;redColor&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;colors&amp;#039;&amp;#039;&amp;#039; || array || Array of colour specifiers for a flasher. Ignored for non-flashers. Before 1.74, only the first entry was used. If not present, see &amp;#039;&amp;#039;&amp;#039;color&amp;#039;&amp;#039;&amp;#039;. &amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; like [[#laser_color|laser_color]], flasher colours must be “reasonably bright”.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;frequency&amp;#039;&amp;#039;&amp;#039; || number || Pulse rate for flashers, in cycles per second. Ignored for non-flashers. If 0, the flasher will have full intensity all the time in Oolite 1.74 and later, but half intensity in earlier releases. Default: 2.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;initially_on&amp;#039;&amp;#039;&amp;#039; || boolean || Specifiers whether a flasher is turned on when created. Ignored for non-flashers. Default: yes.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;phase&amp;#039;&amp;#039;&amp;#039; || number || Pulse phase offset for flashers, in seconds. Ignored for non-flashers. (This value is simply added to the time to get the pulse parameter.) Default: 0.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;size&amp;#039;&amp;#039;&amp;#039; || positive number || Diameter of a flasher in metres. Ignored for non-flashers. Default: 8. (Why 8? I don’t remember.)&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;bright_fraction&amp;#039;&amp;#039;&amp;#039; || number || &amp;#039;&amp;#039;In Oolite 1.77 or later&amp;#039;&amp;#039;, a number between 0 and 1 defining the proportion of the flasher&amp;#039;s cycle that the flasher is bright for. Ignored for non-flashers. The default (which mimics the behaviour of all flashers in 1.76 or earlier) is 0.5.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Old-style subentity definition ===&lt;br /&gt;
Prior to Oolite 1.73, this was the the only way to specify a subentity.&lt;br /&gt;
&lt;br /&gt;
An old-style subentity definition is a string with eight items separated by spaces. In the description below, words in bold correspond to keys in [[#New-style subentity definition|new-style definitions]]. There are two variants:&lt;br /&gt;
&lt;br /&gt;
==== Flashers ====&lt;br /&gt;
For a flasher, the entry takes the form:&lt;br /&gt;
 *FLASHER* x y z hue frequency phase size&lt;br /&gt;
&amp;#039;&amp;#039;*FLASHER*&amp;#039;&amp;#039; must be precisely the string “*FLASHER*”, in capitals.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;x&amp;#039;&amp;#039;, &amp;#039;&amp;#039;y&amp;#039;&amp;#039; and &amp;#039;&amp;#039;z&amp;#039;&amp;#039; form the &amp;#039;&amp;#039;&amp;#039;position&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;hue&amp;#039;&amp;#039; specifies the [http://en.wikipedia.org/wiki/HSL_and_HSV HSV] hue component (in degrees) of &amp;#039;&amp;#039;&amp;#039;color&amp;#039;&amp;#039;&amp;#039;. Saturation and value are always 1.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;frequency&amp;#039;&amp;#039;&amp;#039;, &amp;#039;&amp;#039;&amp;#039;phase&amp;#039;&amp;#039;&amp;#039; and &amp;#039;&amp;#039;&amp;#039;size&amp;#039;&amp;#039;&amp;#039; are the same as in the new-style format.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;initially_on&amp;#039;&amp;#039;&amp;#039; is false.&lt;br /&gt;
&lt;br /&gt;
==== Other subentities ====&lt;br /&gt;
For a non-flasher, the entry takes the form:&lt;br /&gt;
 key x y z qw qx qy qz&lt;br /&gt;
&amp;#039;&amp;#039;key&amp;#039;&amp;#039; corresponds to &amp;#039;&amp;#039;&amp;#039;subentity_key&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;x&amp;#039;&amp;#039;, &amp;#039;&amp;#039;y&amp;#039;&amp;#039; and &amp;#039;&amp;#039;z&amp;#039;&amp;#039; form the &amp;#039;&amp;#039;&amp;#039;position&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;qw&amp;#039;&amp;#039;, &amp;#039;&amp;#039;qx&amp;#039;&amp;#039;, &amp;#039;&amp;#039;qy&amp;#039;&amp;#039; and &amp;#039;&amp;#039;qz&amp;#039;&amp;#039; form the &amp;#039;&amp;#039;&amp;#039;orientation&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;type&amp;#039;&amp;#039;&amp;#039; is &amp;#039;&amp;#039;standard&amp;#039;&amp;#039; unless the command &amp;#039;&amp;#039;initialiseTurret&amp;#039;&amp;#039; is present in the [[#setup_actions|setup_actions]] of the subentity, in which case it is &amp;#039;&amp;#039;ball_turret&amp;#039;&amp;#039;. Note that the &amp;#039;&amp;#039;initialiseTurret&amp;#039;&amp;#039; no longer does anything when executed in a script; its presence is only used as an indicator to set the &amp;#039;&amp;#039;is_turret&amp;#039;&amp;#039; property when old-style definitions are translated. If &amp;#039;&amp;#039;initialiseTurret&amp;#039;&amp;#039; is inside a condition, it will be ignored. The &amp;#039;&amp;#039;initialiseTurret&amp;#039;&amp;#039; command is not required or useful for turrets which are only referenced using new-style subentity definitions.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;is_dock&amp;#039;&amp;#039;&amp;#039; is implied by having the string “dock” (in lowercase) in the &amp;#039;&amp;#039;key&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Links ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=19091 How are subentity scripts supposed to work ?] (2017)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=11716 Ball turrets] (2012)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=7222 Docking bay problems] (2009) - covers a range of issues&lt;br /&gt;
*Some OXP&amp;#039;s with subentities: &lt;br /&gt;
:Thargoids: [[Stellar Serpents OXP]] (2010), [[Animated Ships]]/Butterflies (2011), [[Aquatics]] (2011: Hammerhead bulk carrier &amp;amp; the Aqualina stations), [[WildShips OXP]] (2012-14: moving elevators inside station struts)&lt;br /&gt;
:[[Z GrOovy HPC pack]] (2014 - bought equipment is visible on ship!); [[Scrub]] (2022 - rotating rings)&lt;br /&gt;
&lt;br /&gt;
== sun_glare_filter ==&lt;br /&gt;
{{oolite-prop-added|1.79}}&lt;br /&gt;
&lt;br /&gt;
The default strength of the sun glare filter on this ship. A number between 0 and 1, with the default being 0 (no filter)&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;sun_glare_filter&amp;quot; = 0.3;&lt;br /&gt;
&lt;br /&gt;
== track_contacts ==&lt;br /&gt;
Tracks the movement of the ship and sends a &amp;quot;CLOSE CONTACT&amp;quot; message to other ship AI&amp;#039;s. It uses a time consuming tracking, so only set to true when actually used.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;track_contacts&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== throw_sparks ==&lt;br /&gt;
{{oolite-prop-added|1.73}}&lt;br /&gt;
&lt;br /&gt;
Each new ship should start in seemingly good operating condition, unless specifically told not to. (false by default)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;throw_sparks&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== thrust ==&lt;br /&gt;
Gives the entity an &amp;#039;inertia&amp;#039; value, telling how fast it can increase or reduce speed (in m/s^2). 0 for rocks and cargo, 50 for a very fast ship, 100 for a station. When used with turrets it defines the turn rate in revolutions per second (with 1 being an average value). &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;thrust&amp;quot; = &amp;quot;25&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== unpiloted ==&lt;br /&gt;
Used to designate items that will never have a pilot, thus never turn aggressive and never eject a pod. By chance factor, or true/false.&amp;lt;br&amp;gt;&lt;br /&gt;
It will not add a pilot when set to false, but will remove any existing pilot when set to true.&lt;br /&gt;
commsMessages can only be broadcasted by piloted ships. Ships are by default piloted.  cargo , rocks, missiles etc. are not piloted by default.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;unpiloted&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== view_position_.. ==&lt;br /&gt;
Sets the ship&amp;#039;s 4 point-of-view positions in XYZ relative to the model.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;view_position_aft&amp;quot; = &amp;quot;0.0 5.0 -20.0&amp;quot;;&lt;br /&gt;
 &amp;quot;view_position_forward&amp;quot; = &amp;quot;0.0 1.9375 5.0&amp;quot;;&lt;br /&gt;
 &amp;quot;view_position_port&amp;quot; = &amp;quot;-11.85 2.825 -3.5&amp;quot;;&lt;br /&gt;
 &amp;quot;view_position_starboard&amp;quot; = &amp;quot;11.85 2.825 -3.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== weapon_energy ==&lt;br /&gt;
This setting works differently depending on the type of entity it&amp;#039;s used for:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Missiles.&amp;lt;/b&amp;gt; Changes the damage inflicted by the missile. Any value accepted.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;NPC ships.&amp;lt;/b&amp;gt; Changes the forward weapon damage to a value different to the default one. Values higher than 50 will be clamped to 50. Does not change the value for aft weapons or subEntity weapons.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;N.B.&amp;lt;/b&amp;gt; It does not have any effect on player ships.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;turrets.&amp;lt;/b&amp;gt; Unused for turrets. Set the turret weapon_energy in its [[Shipdata.plist#New-style_subentity_definition|subEntity directory]].&lt;br /&gt;
&lt;br /&gt;
Default values are: WEAPON_PLASMA_CANNON = 6.0; WEAPON_PULSE_LASER = 15.0; WEAPON_BEAM_LASER = 15.0; WEAPON_MINING_LASER = 50.0; WEAPON_THARGOID_LASER = 12.5; WEAPON_MILITARY_LASER = 23.0&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;weapon_energy&amp;quot; = &amp;quot;17&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== weapon_facings ==&lt;br /&gt;
{{oolite-prop-added|1.77}}&lt;br /&gt;
&lt;br /&gt;
What weapon mounts are available on the ship. This is a bit-mask, so pick the mounts and add the numbers:&lt;br /&gt;
&lt;br /&gt;
1 - Forward&amp;lt;br /&amp;gt;&lt;br /&gt;
2 - Aft&amp;lt;br /&amp;gt;&lt;br /&gt;
4 - Port&amp;lt;br /&amp;gt;&lt;br /&gt;
8 - Starboard&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;br /&amp;gt;&lt;br /&gt;
Fore and aft weapon mounts only.&lt;br /&gt;
  &amp;lt;key&amp;gt;weapon_facings&amp;lt;/key&amp;gt;&lt;br /&gt;
  &amp;lt;integer&amp;gt;3&amp;lt;/integer&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If omitted, defaults to 15 (all mounts). If a player ship has this specified, and the same property specified in shipyard.plist, the shipyard.plist property takes precedence.&lt;br /&gt;
&lt;br /&gt;
Weapons assigned to a mount that the ship does not have will be ignored. Scripting cannot be used to add weapons to these mounts later, either.&lt;br /&gt;
&lt;br /&gt;
== weapon_mount_mode ==&lt;br /&gt;
{{oolite-prop-added|1.83}}&lt;br /&gt;
&lt;br /&gt;
This controls how multiple weapon mount points work. It has three possible values:&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;&amp;quot;single&amp;quot;&amp;#039;&amp;#039;&amp;#039;: this is the default, and replicates 1.82 and previous behaviour. In this mode, &amp;lt;code&amp;gt;weapon_position_*&amp;lt;/code&amp;gt; properties are simple vector expressions, and there is exactly one mount per facing.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;&amp;quot;split&amp;quot;&amp;#039;&amp;#039;&amp;#039;: In this mode, &amp;lt;code&amp;gt;weapon_position_*&amp;lt;/code&amp;gt; properties are an array of vector expressions. A weapon fitted to this facing has the same heat and energy cost as a single standard weapon, and the damage output is divided equally between all mount points. (in other words, the distinction is mainly cosmetic)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;&amp;quot;multiply&amp;quot;&amp;#039;&amp;#039;&amp;#039;: In this mode, &amp;lt;code&amp;gt;weapon_position_*&amp;lt;/code&amp;gt; properties are an array of vector expressions. A weapon fitted to this facing has N times the heat and energy cost as a single standard weapon, and each mount point does normal damage. (in other words, the weapon is fitted N times at once)&lt;br /&gt;
&lt;br /&gt;
For best results with AI and the &amp;quot;target reticle sensitive&amp;quot; feature, if there are several weapon positions in a (rough) line, the middle one should be listed first.&lt;br /&gt;
&lt;br /&gt;
See [https://github.com/OoliteProject/oolite/pull/161 this comment] or [[Multiple Lasers]] for examples.&lt;br /&gt;
&lt;br /&gt;
== weapon_offset ==&lt;br /&gt;
Removed after version 1.65 (it was used to change the offsetpoint of a plasma cannon.)&lt;br /&gt;
&lt;br /&gt;
== weapon_position_.. ==&lt;br /&gt;
Plots the &amp;#039;gunmouth&amp;#039; points of the model&amp;#039;s 4 potential lasers.&lt;br /&gt;
&lt;br /&gt;
In 1.82 and earlier, and in 1.83 and later in the &amp;quot;single&amp;quot; &amp;lt;code&amp;gt;weapon_mount_mode&amp;lt;/code&amp;gt;, these are vector expressions.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;weapon_position_aft&amp;quot; = &amp;quot;0.0 -5.0 -20.0&amp;quot;;&lt;br /&gt;
 &amp;quot;weapon_position_forward&amp;quot; = &amp;quot;0.0 0.0417 16.6667&amp;quot;;&lt;br /&gt;
 &amp;quot;weapon_position_port&amp;quot; = &amp;quot;-13.75 -2.0625 -1.875&amp;quot;;&lt;br /&gt;
 &amp;quot;weapon_position_starboard&amp;quot; = &amp;quot;13.75 -2.0625 -1.875&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
In 1.83 and later, with &amp;quot;split&amp;quot; or &amp;quot;multiply&amp;quot; &amp;lt;code&amp;gt;weapon_mount_mode&amp;lt;/code&amp;gt;, these values are specified as arrays of vector expressions. For example:&lt;br /&gt;
 &amp;quot;weapon_position_forward&amp;quot; = ( &amp;quot;0.0 3.0 32.0&amp;quot; , &amp;quot;-15.0 0.0 32.0&amp;quot; , &amp;quot;15.0 0.0 32.0&amp;quot; )&lt;br /&gt;
&lt;br /&gt;
= Station keys=&lt;br /&gt;
The following keys are only used by stations or carriers.&lt;br /&gt;
&lt;br /&gt;
== allegiance ==&lt;br /&gt;
An advisory flag that informs AIs how they should expect to be treated near or when attempting to dock with this station. See [[Oolite_JavaScript_Reference:_Station#allegiance|station.allegiance]] for the allowable values. If this is not set, the game will guess based on other station properties.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 allegiance = &amp;quot;neutral&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== allows_auto_docking ==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
When set false for a station, this station will not allow the use of a docking computer. Default value in &amp;quot;yes&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 allows_auto_docking = &amp;quot;no&amp;quot;;&lt;br /&gt;
 &lt;br /&gt;
== allows_fast_docking ==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
When set true for a station, this station will allow fast docking with the docking computer. Default value in &amp;quot;no&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 allows_fast_docking = &amp;quot;yes&amp;quot;;&lt;br /&gt;
 &lt;br /&gt;
== defense_ship ==&lt;br /&gt;
Gives an oportunity to designate a particular ship by name that will defend a station/carrier. See also [[Shipdata.plist#defense_ship_role|defense_ship_role]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 defense_ship&amp;quot; = &amp;quot;my_defender&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== defense_ship_role ==&lt;br /&gt;
Gives an oportunity to designate a particular (group of) ships that will defend a station/carrier. This has to be specified in the [[Shipdata.plist#roles|roles]] of the ship(s) that are assigned to defend. When launched from a carrier the scan_class becomes that of the carrier. Default role is &amp;quot;police&amp;quot;/&amp;quot;interceptor&amp;quot; for normal stations and &amp;quot;hermit-ship&amp;quot; for stations of CLASS_ROCK. Defense ships with scanclass police or with a hermit-ship role launch with a policeInterceptAI.plist. All other ships use the ai_type as defined in shipdata.plist. After launch, all primary roles are changed into: &amp;quot;defense_ship&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;defense_ship_role&amp;quot; = &amp;quot; carrier_defenders&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== equipment_price_factor ==&lt;br /&gt;
Equipment price mask for dockables.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;equipment_price_factor&amp;quot; = &amp;quot;4.5&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Note: [https://bb.oolite.space/viewtopic.php?t=18692 Possible to abuse equipment_price_factor &amp;lt; 1] (2017)&lt;br /&gt;
&lt;br /&gt;
== equivalent_tech_level ==&lt;br /&gt;
Sets shipyard tech level for dockables, different to the local system tech_level. Default value is the system tech_level.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;equivalent_tech_level&amp;quot; = 1;&lt;br /&gt;
&lt;br /&gt;
== has_npc_traffic ==&lt;br /&gt;
Determines if a station launches NPC traffic. Default is &amp;quot;yes&amp;quot; for stationary stations, and &amp;quot;no&amp;quot; for stations with a non-zero maximum speed. When set to &amp;quot;no&amp;quot; the station will not launch random ships as part of the main Oolite system repopulator (though OXP scripts may still launch ships from it).&lt;br /&gt;
&lt;br /&gt;
The type of traffic launched depends on the [[#allegiance|allegiance]] property of the station (which also determines what, if any, ships may try to dock at it).&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_npc_traffic&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== has_patrol_ships ==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
Determines if a station launches periodic patrol ships. Default is &amp;quot;no&amp;quot;. Main stations always have patrol ships.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_patrol_ships&amp;quot; = yes;&lt;br /&gt;
 &lt;br /&gt;
== has_shipyard ==&lt;br /&gt;
Determines if a station or carrier has a shipyard. By chance factor as number between 0 and 1, but it can also be an array of conditions. Default is &amp;quot;no&amp;quot;, but for main stations has_shipyard is always &amp;quot;yes&amp;quot;. (Name is valid starting with Oolite 1.74. Before it was called &amp;quot;hasShipyard&amp;quot;.)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;has_shipyard&amp;quot; = &amp;quot;0.75&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;has_shipyard&amp;quot; = (&lt;br /&gt;
                   &amp;quot;systemGovernment_number morethan 3&amp;quot;,&lt;br /&gt;
                   &amp;quot;systemEconomy_number lessthan 4&amp;quot;&lt;br /&gt;
                  )&lt;br /&gt;
&lt;br /&gt;
== interstellar_undocking ==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
When set true for a station, this station will allow interstellar docking and undocking in interstellar space. When set to &amp;quot;no&amp;quot; the player docks in nearby normal space. Default value in &amp;quot;no&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 interstellar_undocking = &amp;quot;yes&amp;quot;;&lt;br /&gt;
 &lt;br /&gt;
==is_carrier==&lt;br /&gt;
Added as a tag for making the model be considered a carrier or station.  An alternative to including &amp;#039;&amp;#039;carrier&amp;#039;&amp;#039; or &amp;#039;&amp;#039;station&amp;#039;&amp;#039; among the [[Shipdata.plist#roles|roles]]. When present this key even overrules station/carrier settings with roles. (Name is valid starting with Oolite 1.74. Before it was called &amp;quot;isCarrier&amp;quot;.)&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;is_carrier&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== market ==&lt;br /&gt;
Key that sets the market for stations and carriers. The name defines the key in [[commodities.plist]] that will be used as local market. Without a market key, the stations primaryRole is used as market.  Added with test release 1.74 and no longer used in 1.81 or later, where it is replaced by the market_* properties below.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;market&amp;quot; = &amp;quot;none&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== market_broadcast ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
If this is enabled the station&amp;#039;s market will appear on the F8 screen if the player is in flight and has the station targeted. The default is enabled. This is ignored (and always true) if the station is the main station.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;market_broadcast&amp;quot; = no;&lt;br /&gt;
&lt;br /&gt;
== market_capacity ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
The capacity in units per trade good of the station market. If omitted, the default market capacity of 127 units will be used. This is ignored if the station is the main station as it will use the system market, not its own.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;market_capacity&amp;quot; = 31;&lt;br /&gt;
&lt;br /&gt;
== market_definition ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
An array of [[trade-goods.plist#Secondary_Market_Definitions|secondary market rules]] which modify some or all of the price, quantity, capacity and legal status of a good relative to the primary system market. This is ignored if the station is the main station as it will use the system market, not its own.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;market_definition&amp;quot; = (&lt;br /&gt;
 	{&lt;br /&gt;
 		// export cheap clothes&lt;br /&gt;
 		&amp;quot;type&amp;quot; = &amp;quot;class&amp;quot;;&lt;br /&gt;
 		&amp;quot;name&amp;quot; = &amp;quot;oolite-wearable&amp;quot;;&lt;br /&gt;
 		&amp;quot;price_multiplier&amp;quot; = 0.8;&lt;br /&gt;
 		&amp;quot;price_randomiser&amp;quot; = 0.1;&lt;br /&gt;
 		&amp;quot;quantity_multiplier&amp;quot; = 3.5;&lt;br /&gt;
 		&amp;quot;quantity_randomiser&amp;quot; = 3.0;&lt;br /&gt;
 	}, 			&lt;br /&gt;
 	{&lt;br /&gt;
 		// not really interested in other goods&lt;br /&gt;
 		&amp;quot;type&amp;quot; = &amp;quot;default&amp;quot;;&lt;br /&gt;
 		&amp;quot;price_multiplier&amp;quot; = 0.55;&lt;br /&gt;
 		&amp;quot;price_randomiser&amp;quot; = 0.25;&lt;br /&gt;
 		&amp;quot;quantity_multiplier&amp;quot; = 0.0;&lt;br /&gt;
 		&amp;quot;capacity&amp;quot; = 3;&lt;br /&gt;
 	}&lt;br /&gt;
 );&lt;br /&gt;
&lt;br /&gt;
If the capacity set by a rule is larger than the market_capacity of the station, the market_capacity of the station is used instead.&lt;br /&gt;
&lt;br /&gt;
A blank array&lt;br /&gt;
 &amp;quot;market_definition&amp;quot; = ();&lt;br /&gt;
will give a market identical to the primary system market.&lt;br /&gt;
&lt;br /&gt;
If this key is omitted, the station will have no market. This is roughly equivalent to&lt;br /&gt;
 &amp;quot;market_definition&amp;quot; = (&lt;br /&gt;
 	{&lt;br /&gt;
 		&amp;quot;type&amp;quot; = &amp;quot;default&amp;quot;;&lt;br /&gt;
 		&amp;quot;price_multiplier&amp;quot; = 0;&lt;br /&gt;
 		&amp;quot;quantity_multiplier&amp;quot; = 0;&lt;br /&gt;
 		&amp;quot;capacity&amp;quot; = 0;&lt;br /&gt;
 	}&lt;br /&gt;
 );&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; There is some discussion about this at [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=21512 Secondary Market Definitions Defined] (2023)&lt;br /&gt;
&lt;br /&gt;
== market_monitored ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
If this is true, the market is subject to Cooperative law for the import and export of trade goods, and the player will gain the usual bounties for smuggling contraband. The default value is no. This is ignored (and effectively always true) if the station is the main station.&lt;br /&gt;
&lt;br /&gt;
 market_monitored = yes;&lt;br /&gt;
&lt;br /&gt;
== market_script ==&lt;br /&gt;
{{oolite-prop-added|1.81}}&lt;br /&gt;
&lt;br /&gt;
Allows a [[Oolite Market Scripts|market script]] to be used to modify trade prices. This overrides market_definition, if it is present.&lt;br /&gt;
&lt;br /&gt;
 market_script = &amp;quot;myoxp_marketchanges.js&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note:&amp;#039;&amp;#039;&amp;#039; [https://bb.oolite.space/viewtopic.php?p=235837#p235837 What&amp;#039;s the difference between the market script specified in planetinfo.plist and the one called for by trade-goods.plist?] (2015)&lt;br /&gt;
&lt;br /&gt;
== max_defense_ships ==&lt;br /&gt;
Designates how many ships a dockable entity (station, carrier) can launch in defense. Default value is 3. See also [[Station Ships]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_defense_ships&amp;quot; = &amp;quot;10&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== max_police ==&lt;br /&gt;
Designates how many police or patrol ships a dockable entity (station, carrier) can launch.  Default value is 8. See also [[Station Ships]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_police &amp;quot; = &amp;quot;10&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== max_scavengers ==&lt;br /&gt;
Designates how many scavengers or miners a dockable entity (station, carrier) can launch. Default value is 3. See also [[Station Ships]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;max_scavengers&amp;quot; = &amp;quot;10&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
== port_dimensions ==&lt;br /&gt;
Defines the size of the docking port and takes 3 numbers, separated by &amp;quot;x&amp;quot;. This key is generally of little use and can be skipped as it becomes overwritten by the actual size of the bounding box of the dock subentity when a correct dock subentity is defined.&lt;br /&gt;
  &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;port_dimensions&amp;quot; = &amp;quot;65x30x500&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
Size of Oolites main-station dock is: 64.00 x 192.00 x 250.00  while the dimension of a rock-hermit dock is: 138.001 x 138.001 x 250.12 (W x H x L)&amp;lt;br&amp;gt;&lt;br /&gt;
These sizes may be relevant for ship dimensions as since Oolite 1.75 ships must fit in these docks to be allowed docking or launching.&lt;br /&gt;
&lt;br /&gt;
== port_radius ==&lt;br /&gt;
Defines the size of the docking port radius. Or more precise, this is the distance from the station centre to the port location. Default value is 500. This key is generally of little use and can be skipped as it will be overwritten by the real position of the dock subentity.&lt;br /&gt;
  &lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;port_radius&amp;quot; = &amp;quot;500&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
If it is a &amp;#039;&amp;#039;really&amp;#039;&amp;#039; big number, then one auto-docks when one gets near to the station, well before entering the dock [https://bb.oolite.space/viewtopic.php?p=306549#p306549 Wildeblood (2026)].&lt;br /&gt;
&lt;br /&gt;
== requires_docking_clearance ==&lt;br /&gt;
Sets the requirement for docking clearance. Default is &amp;quot;no&amp;quot;. See also [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|DockingClearance]]&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;requires_docking_clearance&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
==rotating==&lt;br /&gt;
Given to a station when rotation is desired. Default is &amp;quot;no&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;rotating&amp;quot; = yes;&lt;br /&gt;
&lt;br /&gt;
== station_roll ==&lt;br /&gt;
{{oolite-prop-added|1.74.2}}&lt;br /&gt;
&lt;br /&gt;
Determines the rotation speed of a station. Default value is determined by the systemwide station_roll in planetInfo.plist. If that is not defined, the default is 0.4. Negative values are also possible for a rotation in the other direction.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note&amp;#039;&amp;#039;&amp;#039;: unlike the other turn rate properties, for historical reasons &amp;lt;code&amp;gt;station_roll&amp;lt;/code&amp;gt; is measured in right-angles/second, &amp;#039;&amp;#039;not&amp;#039;&amp;#039; radians/second.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;station_roll&amp;quot; = &amp;quot;-1.5&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==tunnel_corners==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
Defines the number of corners in the docking tunnel. Ranges from 4 to 128. Default is &amp;quot;4&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;tunnel_corners&amp;quot; = 6;&lt;br /&gt;
&lt;br /&gt;
==tunnel_start_angle==&lt;br /&gt;
{{oolite-prop-added|1.75}}&lt;br /&gt;
&lt;br /&gt;
Defines the position of the first corner of the docking tunnel in degrees. 0 means the first corner is straight up. Default is &amp;quot;45&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;tunnel_start_angle&amp;quot; = 0;&lt;br /&gt;
&lt;br /&gt;
==tunnel_aspect_ratio==&lt;br /&gt;
Defines the proportion of the tunnel’s width to its height. Default is &amp;quot;2.67&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;quot;tunnel_aspect_ratio&amp;quot; = 1;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Shipdata structure]] (for XML)&lt;br /&gt;
*[[Shipdata-overrides.plist]]&lt;br /&gt;
*[[Like ship shipdata.plist example]]&lt;br /&gt;
*[[Oolite JavaScript Reference: Condition scripts]] used to set conditions on the appearance of ships &amp;amp; equipment beyond the basics possible in [[shipdata.plist]], [[shipyard.plist]], [[shiplibrary.plist]] and equipment.plist&lt;br /&gt;
&lt;br /&gt;
=== Forum discussions ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=6232 Understanding the shipdata.plist] (2009)&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3355 Orientation Issues] (Asteroid turns 180°, and want it to face planet, 2007)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20959 Empty System] (Removing stations and rock hermits from a system, 2021)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=6&amp;amp;t=4729 Changing compass values of ships (from white to red)] (Hiding ships on the scanner, 2008)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=15831&amp;amp;start=735#p247369 Problems with Explosions] - metal plates birthing bigger plates when exploded (2016) -as [https://bb.oolite.space/viewtopic.php?p=247280#p247280 here].&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=10446 Top/down instead of side lasers] (2011)&lt;br /&gt;
&lt;br /&gt;
== Utilities ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=19514 A Parser for shipdata]: a python script to sort out spelling mistakes &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. By [[User:Cag|Cag]] (2018)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]]&lt;br /&gt;
[[Category:Oolite scripting]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Vanilla_game&amp;diff=90345</id>
		<title>Vanilla game</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Vanilla_game&amp;diff=90345"/>
		<updated>2026-10-15T10:52:54Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added more detail&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Oolite ad1 .jpg|thumb|right|500px]]&lt;br /&gt;
[[File:Start Choices.png|thumb|right|500px|Starting the game. &amp;lt;br&amp;gt; The list of options has been added to by the [[Start Choices]] .oxp]]&lt;br /&gt;
This is the &amp;#039;&amp;#039;basic game&amp;#039;&amp;#039; without any added [[OXP]]s. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you choose &amp;#039;&amp;#039;&amp;#039;Strict Mode&amp;#039;&amp;#039;&amp;#039; (Strict Game) when you start up Oolite, this will constrain you to the &amp;#039;&amp;#039;basic vanilla game&amp;#039;&amp;#039;, excluding whatever OXP/OXZs you may have loaded.&lt;br /&gt;
&lt;br /&gt;
It is identical to the normal game as played without any oxp&amp;#039;s loaded.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Note that the up-to-date vanilla game code currently comes designed for &amp;#039;&amp;#039;&amp;#039;Windows&amp;#039;&amp;#039;&amp;#039; &amp;amp; &amp;#039;&amp;#039;&amp;#039;Linux&amp;#039;&amp;#039;&amp;#039; (&amp;#039;&amp;#039;&amp;#039;AppleMac&amp;#039;&amp;#039;&amp;#039; only goes up to v.1.90 and Intel-chip Macs, &amp;#039;&amp;#039;&amp;#039;Pandora&amp;#039;&amp;#039;&amp;#039; only goes up to v.1.86). &lt;br /&gt;
&lt;br /&gt;
2) There are 3 flavours of each version: the &amp;quot;Last Stable Version&amp;quot;, the &amp;quot;Developer Release&amp;quot; (includes extras for OXP developers) and the &amp;quot;nightlies&amp;quot;/&amp;quot;pre-Releases&amp;quot;. These are all available here: https://oolite.space/#download&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Rescaling Experiment ==&lt;br /&gt;
This is a different vanilla code version (Windows only) of Oolite with larger solar systems and a faster Torus Drive to retain playability. See [[Rescaling experiment]] for more detail and download links.&lt;br /&gt;
&lt;br /&gt;
== Older Versions of Oolite ==&lt;br /&gt;
The Vanilla game used to be &amp;#039;&amp;#039;much more&amp;#039;&amp;#039; different from the oxp&amp;#039;d game.&lt;br /&gt;
&lt;br /&gt;
The strict game &amp;#039;&amp;#039;before&amp;#039;&amp;#039; Oolite v.1.80 was not just an oxp-less version of Oolite. It was actually a mildly modified version of the original [[Classic Elite]]. In those days, the &amp;quot;Vanilla game&amp;quot; was not the strict game, but was just a (regular) oxp-able game - but before adding in any oxp&amp;#039;s.&lt;br /&gt;
&lt;br /&gt;
Optional vanilla-game equipment (added-in to Elite) lost in the &amp;#039;&amp;#039;original&amp;#039;&amp;#039; strict game:&lt;br /&gt;
*Fuel Injectors&lt;br /&gt;
*anti-ECM missiles (&amp;quot;hard heads&amp;quot;)&lt;br /&gt;
*shield boosters&lt;br /&gt;
*scanner targeting enhancements&lt;br /&gt;
*ANA&lt;br /&gt;
*wormhole scanner&lt;br /&gt;
&lt;br /&gt;
Game options lost:&lt;br /&gt;
*targeting in-coming missiles&lt;br /&gt;
*contract hauling&lt;br /&gt;
*the F5F5 cargo-hold manifest screen&lt;br /&gt;
*the F3F3 shipyard for buying/selling ships&lt;br /&gt;
&lt;br /&gt;
Other losses:&lt;br /&gt;
*no navigation beacons&lt;br /&gt;
*no stopping at a standstill&lt;br /&gt;
&lt;br /&gt;
Gains:&lt;br /&gt;
Kills from shooting asteroids!&lt;br /&gt;
&lt;br /&gt;
But it did have the [[Energy Bomb]] - which has since been replaced with the [[Quirium Cascade Mine]]! But then so did the regular Oolite game!&lt;br /&gt;
&lt;br /&gt;
[[User:Cim|Cim]] started the process of changing the strict game away from this. See the discussion [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=14619 here].&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Oolite]] for the History of the development of Oolite&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3442 Strict/Unstrict Gameplay] (2007)&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=12191 New Commander] Playing an almost Vanilla game (2012)&lt;br /&gt;
*[https://www.youtube.com/watch?v=yngSxZXPqGA&amp;amp;list=PLsYaAtYv_5eUpD3FBWQk7XQuKQQsrVhNV&amp;amp;index=9 Arqubus&amp;#039;s YouTube critique of the Vanilla game] (2021, v.1.90)&lt;br /&gt;
&lt;br /&gt;
=== The Dark Arts ===&lt;br /&gt;
*[[:Category:Oolite Development]] for the Oolite Vanilla game code&lt;br /&gt;
[[Category:Oolite]][[Category:Factual]][[Category:Help pages]][[Category:Concepts]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Rescaling_experiment&amp;diff=90344</id>
		<title>Rescaling experiment</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Rescaling_experiment&amp;diff=90344"/>
		<updated>2026-10-15T10:41:28Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added more detail&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A different vanilla-code version of Oolite (just for Windows).&lt;br /&gt;
[[File:Scale Oolite-011.jpg|left]]&lt;br /&gt;
[[File:Rescaling (Arrival at Leesti - Vanilla).png|thumb|right|400px|Vanilla game &amp;#039;&amp;#039;&amp;#039;Arrival at Leesti&amp;#039;&amp;#039;&amp;#039;]]&lt;br /&gt;
[[File:Rescaling (Arrival at Leesti - Rescaled).png|thumb|right|400px|Rescaled &amp;#039;&amp;#039;&amp;#039;Arrival at Leesti&amp;#039;&amp;#039;&amp;#039; &amp;lt;br&amp;gt;•space lane 6 times longer&amp;lt;br&amp;gt;•planet 3 times larger&amp;lt;br&amp;gt;•sun distance 81 times further&amp;lt;br&amp;gt;•sun 27 times larger]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:left&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
 The goal is not to make a different game but rather to present the solar systems in which it takes place as a much larger arena.&lt;br /&gt;
 &lt;br /&gt;
 You haven&amp;#039;t got a hope in hell of spotting any orbital station from the witchpoint in this variant and that was one of the chief motivations for making it. &lt;br /&gt;
 &lt;br /&gt;
 Consider that there is the game as it takes place within your scanner range and the system that extends beyond your scanner. All of the really significant changes this project makes are to change the latter.&lt;br /&gt;
 In order to ease the transition between these two gameplay states (essentially : mass-locked and otherwise), the torus drive has been granted both a higher base speed and a sharper deceleration.&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 Sun collision radius x14&lt;br /&gt;
 Corona multiplier x112 (instead of 8 )&lt;br /&gt;
 &lt;br /&gt;
 Torus/Hyperspeed factor x512&lt;br /&gt;
 Deceleration x60&lt;br /&gt;
 &lt;br /&gt;
 Planet collision radius x35 (instead of 10)&lt;br /&gt;
 Planet distance x4&lt;br /&gt;
 &lt;br /&gt;
 So, relative to the standard game:&lt;br /&gt;
 &lt;br /&gt;
 * planets would be 3.5 times bigger&lt;br /&gt;
 * suns would be 49 times bigger&lt;br /&gt;
 * the spacelane would be 140 times longer&lt;br /&gt;
 * travel time from WitchPoint to planet would be approximately the same&lt;br /&gt;
&lt;br /&gt;
== Historical synopsis ==&lt;br /&gt;
Almost for as long as [[oolite]] has existed, various discussions have arisen concerning the issue of scale. There have been two main points of contention:&lt;br /&gt;
&lt;br /&gt;
::1. Planets, suns (stars), distances are all rather small&lt;br /&gt;
&lt;br /&gt;
::2. Ships are rather big (roughly three times bigger than in the [[The Space Traders Flight Training Manual|manual]] which came with [[Classic Elite|Elite]] - the game that oolite draws heavily from)&lt;br /&gt;
&lt;br /&gt;
By no means was there a consensus that these issues were worth bothering about, or even that they could be improved upon without &amp;#039;breaking the game&amp;#039;. Then in late 2013/early 2014 it was argued that both issues could be addressed without major upheaval and a basic plan was proposed with which to do so.&lt;br /&gt;
&lt;br /&gt;
A third issue was also highlighted:&lt;br /&gt;
&lt;br /&gt;
::3. The ships are all rather similar in size. The biggest freighter is only a few times bigger than the smallest fighter.&lt;br /&gt;
&lt;br /&gt;
Again, some didn&amp;#039;t see this as a problem. However, with a lot of help, and quite a bit of experimentation, the necessary source code alterations for a rescaled oolite were presented in late 2014. In early 2016 an updated version for Oolite 1.83 was released and feedback is very much welcome.&lt;br /&gt;
&lt;br /&gt;
The relevant thread on the bulletin boards (2013-date) can be found [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=16159&amp;amp;sid=e96495afedfdd1147935d575112103bf here].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Why bother? ==&lt;br /&gt;
&lt;br /&gt;
The goal is not for a &amp;#039;realistic&amp;#039; scaling of everything in the game, rather it is for the scaling to be a little less &amp;#039;immersion breaking&amp;#039; than that of the standard game.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
:Stations that don&amp;#039;t make the planets look really small&lt;br /&gt;
:Fighters that don&amp;#039;t make freighters look small&lt;br /&gt;
:Stations and &amp;#039;big ships&amp;#039; that don&amp;#039;t make the system look small (by being visible almost the entire trip from witchpoint to main station)&lt;br /&gt;
:Suns that don&amp;#039;t look utterly tiny (but admittedly, still look small...)&lt;br /&gt;
&lt;br /&gt;
So scaling is not truly &amp;#039;fixed&amp;#039; or &amp;#039;corrected&amp;#039;, instead some of its edges are smoothed in order to make its inaccuracies less glaring.&lt;br /&gt;
&lt;br /&gt;
[[File:Anaconda size vs 750 cargo cannisters.png|thumb|right|320px|Captain Beatnik&amp;#039;s analysis of [[Anaconda (Oolite)|Anaconda]] size &amp;#039;&amp;#039;vs&amp;#039;&amp;#039; 750 cargo cannisters]]&lt;br /&gt;
[[File:Cobrafootball.png|thumb|right|320px|Norby&amp;#039;s comparison of the Cobra Mk.3 size &amp;#039;&amp;#039;vs&amp;#039;&amp;#039; a football field]]&lt;br /&gt;
== How does it work? ==&lt;br /&gt;
&lt;br /&gt;
Essentially the experiment functions by recognising two different arenas in which the player operates (where issues of scale are apparent):&lt;br /&gt;
&lt;br /&gt;
::1. Space or the &amp;#039;system&amp;#039; in which the player is currently operating - The travel arena (enlarged by a factor of 3.3 for this experiment).&lt;br /&gt;
&lt;br /&gt;
::2. The range of the player-ship scanner - The combat arena (reduced to 0.5 of its normal size).&lt;br /&gt;
&lt;br /&gt;
So, planets, suns and distances are all bigger. For that to remain interesting, the torus drive has been made considerably more powerful.&lt;br /&gt;
&lt;br /&gt;
Some ships (but not all) have been made smaller. For combat to remain similar to the standard game, ship speed, scanner range and laser ranges have also been reduced.&lt;br /&gt;
&lt;br /&gt;
So, ships (generally) are smaller but they must come closer to engage in combat. The scanner range is smaller but takes just as long to cross as before (reduced speeds).&lt;br /&gt;
Space is bigger with greater travel distances but the torus drive is significantly more powerful to compensate for that.&lt;br /&gt;
&lt;br /&gt;
There are also a few cosmetic changes to exploit the possibilities of a rescaled oolite:&lt;br /&gt;
&lt;br /&gt;
:Greater distance from witchpoint to planet&lt;br /&gt;
&lt;br /&gt;
:Reduced distance (proportionally speaking) from planet to main station&lt;br /&gt;
&lt;br /&gt;
:Some of the larger ships remain at their original size (but not speed) to spread out the range of ship sizes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Like to try it for yourself? ==&lt;br /&gt;
&lt;br /&gt;
Some things that can be fixed by OXP have not yet been addressed in the code (e.g. sun to planet distances) but testers are very welcome to try it out and hopefully report their experience of using it on the relevant thread: https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=16159&amp;amp;sid=e96495afedfdd1147935d575112103bf&lt;br /&gt;
&lt;br /&gt;
A link to the build for &amp;#039;&amp;#039;&amp;#039;windows&amp;#039;&amp;#039;&amp;#039; computers can be found [https://bb.oolite.space/viewtopic.php?p=269850#p269850 here] (2020).&lt;br /&gt;
&lt;br /&gt;
Some of the leading researchers are [[User:Redspear|Redspear]] and [[User:Diziet Sma|Diziet Sma]].&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Jane&amp;#039;s Galactic Shipset‎]] - the first OXP to be produced, rescaling the [[Shipset]] of the [[Vanilla game]]&lt;br /&gt;
&lt;br /&gt;
*[[Distance (Oolite)]]&lt;br /&gt;
&lt;br /&gt;
*[[Guide to Ambience OXPs]] - compares the various OXPs which tweak the sun-planet distances (&amp;#039;&amp;#039;not&amp;#039;&amp;#039; part of this project)&lt;br /&gt;
:[[FarPlanets]] has realistic planet distances (it can take 130 years to get to some of them!), others compromise.&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=13343 Sizes and scale in Oolite (again)] (2013) Inside of a Coriolis Station&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=5872 Oolite ships dimensions... feet or meters?] (2009)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=2796 Size is everything!] (2007): an early grumble about scale&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*[https://www.deviantart.com/dirkloechel/art/Size-Comparison-Science-Fiction-Spaceships-398790051 Size Comparison] - Science Fiction Spaceships By DirkLoechel (Deviantart, 2013)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]] [[Category:Concepts]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Oolite_Tactics&amp;diff=90343</id>
		<title>Oolite Tactics</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Oolite_Tactics&amp;diff=90343"/>
		<updated>2026-10-07T16:47:18Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Tactics for particular scenarios */ Added small targets&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Combat!&amp;#039;&amp;#039;&amp;#039; (For trading, docking &amp;#039;&amp;#039;etc&amp;#039;&amp;#039; see [[:Category:Help pages]])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Life in space is not easy. It doesn&amp;#039;t matter what your occupation is - sooner or later, someone will shoot at you (or you will shoot at someone else). Blundering headlong into a dangerous situation without preparation is a certain way to end up dead, or at the very least, as petfood in orbit around Isveve.&lt;br /&gt;
&lt;br /&gt;
This essay is designed to combine most of the hints and tips given to players on the [https://bb.oolite.space/index.php Oolite Bulletin Board] over time. Hopefully some of this information is useful to you in your journeys across the Eight.&lt;br /&gt;
&lt;br /&gt;
There are some OXP tools and additions that can make combat easier. We&amp;#039;ll look at some OXP solutions and options at the end. What follows just covers the core equipment and scenarios.&lt;br /&gt;
[[File:Oolite-037.png|right|800px]]&lt;br /&gt;
==Starting out==&lt;br /&gt;
The early game can be quite a daunting affair - you have a great ship in the Cobra Mark III, but it is woefully under-equipped at the beginning. Make sure you read [[Mr_Gimlet|Mr Gimlet&amp;#039;s]] advice. The information it contains can help make your first decisions in the game to be wise ones. Other general advice and tactics for the start of the game:&lt;br /&gt;
* Be careful of quick money. Some parcel and passenger contracts can seem like an easy way to make money fast, but check the route to the destination. Are there any dangerous systems you have to pass through? What type of parcel is being carried? Could it attract unwanted attention?&lt;br /&gt;
* Look for &amp;quot;milk runs&amp;quot;, two systems located close together that have opposite economies. A rich industrial next to a poor agricultural is the best combination, but anything close to this can be good. On the F6 Galactic chart, use the &amp;quot;?&amp;quot; key to change the colour coding for the planets. There are four different colour ranges the key press will cycle through: government, tech level, sun colour, and economic level. The economic colour range runs from a deep green to yellow. You can change from showing the planet name to some icons showing you tech level, government and economic level by pressing &amp;quot;i&amp;quot;. Once you have purchased the [[Advanced_Navigational_Array|Advanced Navigational Array]] you can also see the route you are taking to your destination system, and by using the &amp;quot;^&amp;quot; key (shift+&amp;quot;6&amp;quot;) you can cycle between showing the fastest route (which may have more jumps), to the shortest route (which may take longer to travel). &lt;br /&gt;
* Remember to keep your cargo hold full (or at least as full as you can make it). While it can be tempting to buy a longed-for piece of kit as soon as you have the money for it, if you empty your bank balance and have nothing to buy new cargo with, you can be in a worse position than before.&lt;br /&gt;
* It is highly recommended that the first thing you purchase are [[witch fuel injectors|injectors]] - they can get you out of lots of different types of trouble, so they are definitely worth the money. While it might seem odd to even suggest this, selling your pulse laser to fund the purchase of injectors can actually be of some benefit, but you need to change your mindset when you do - with no offensive weapons you &amp;#039;&amp;#039;must&amp;#039;&amp;#039; flee dangerous situations. But with injectors at least you can.&lt;br /&gt;
* After injectors you have some options. Some commanders suggest an [[ECM]] system is the next best choice, to give you better defensive options. A beam laser will give you a much more formidable attack option, although there is value in mounting it in the aft position, so it can be more useful in defence.&lt;br /&gt;
&lt;br /&gt;
==Combat tactics==&lt;br /&gt;
Tactics for combat are tricky, as every player has different styles they prefer, and much of it depends on what equipment you have and the type of battles you’re  facing. To try to make this guide as useful as possible, we&amp;#039;ll look at three different stages for the player: A beginner, who has almost no equipment; a player with some equipment, considered a medium-level player; and a player with a fully-kitted out ship. A Cobra Mark III will be assumed for most of this guide, but many of the tactics will be applicable to any combat ship. Trade-focused vessels (eg [[Boa_(Oolite)|Boa&amp;#039;s]] and [[Anaconda_(Oolite)|Anaconda&amp;#039;s]]) will be considered separately [[#Tactics for cargo ship|later in the document]].&lt;br /&gt;
&lt;br /&gt;
Note: If you don&amp;#039;t fancy your prospects in the standard [[Cobra_Mk.3_(Oolite)|Cobra Mark III]] (the default starting ship), you could trade it in for a smaller ship (say, a [[Cobra_Mk.1_(Oolite)|Cobra Mark I]]), which will give you a bunch of credits to get you some essential kit as early as possible. However, there are downsides to down-sizing: smaller energy banks, slower speeds, smaller cargo capacity, some limitations on equipment. Make sure you understand the specifications of the ship you switch to.&lt;br /&gt;
&lt;br /&gt;
=== Precision Flying ===&lt;br /&gt;
You can fly more accurately by using &amp;quot;Precision Flying&amp;quot; for more precise pitching/yawing/rolling (this is very useful for aiming at distant or small targets!). &lt;br /&gt;
There are 4 options. &amp;lt;br&amp;gt;&lt;br /&gt;
1) Flying on Keyboard: hold down the &amp;quot;control&amp;quot; button. This stops when the button is released. (See [[AppleMac]] for bypassing interference by &amp;quot;Mission Control&amp;quot;). &amp;lt;br&amp;gt;&lt;br /&gt;
1) Flying on Keyboard: install the [[Keyboard Cobra]] OXP. This ensures that all flying is &amp;quot;precision flying&amp;quot; - but permanently inhibits fast turning.&amp;lt;br&amp;gt;&lt;br /&gt;
3) Flying on Controller/Joystick: the control button toggles between &amp;quot;precision&amp;quot; and &amp;quot;normal&amp;quot; flight. An indicator on some HUDs shows which is enabled (See [[Joysticks and Gamepads]]). One can also assign a controller/joystick button to this function. &amp;lt;br&amp;gt;&lt;br /&gt;
4) Flying on Controller/Joystick: precision flying can be incorporated into joystick axis [[Dizzy&amp;#039;s guide to Setting up Joystick Axis Profiles|&amp;quot;splines&amp;quot;]] which alter the response to joystick movements.&lt;br /&gt;
&lt;br /&gt;
===Beginner tactics===&lt;br /&gt;
If all you have is a [[Pulse_Laser|pulse laser]], with no [[ECM]] or [[witch fuel injectors|injectors]], your options are limited. The first tactic is to [[#Escaping tactics|avoid combat wherever you can]]. This is a tactic, although it can seem counter-intuitive given you&amp;#039;re in a space ship with lasers. But at this stage of the game, it&amp;#039;s all about survival. The longer you survive, the more money you can earn, and the faster you can upgrade your ship. You might consider entering battle if there are just one or at most two opponents, and if you do, these things are worth remembering:&lt;br /&gt;
* Don&amp;#039;t go &amp;quot;head-to-head&amp;quot; with another ship. That is, fly directly towards them as they&amp;#039;re flying directly towards you. Yes, it makes them much easier to line up, but other ships have a tendency to fire missiles at the last moment if they&amp;#039;re being attacked, which gives you no chance to avoid them. &lt;br /&gt;
* Playing chicken with ships the size of a 747 is not advisable. If you dodge the wrong way on the pass, you might end up with another ship buried in your cockpit.&lt;br /&gt;
* Don&amp;#039;t fly in a straight line - this makes you too easy a target for enemy ships. Move your ship around to make yourself a harder target.&lt;br /&gt;
* Get in close. Shooting at long distance might seem like a good idea, but the down side is that it&amp;#039;s much easier to miss your target. A pulse laser only has a range of 12.5km, so can&amp;#039;t hit anything outside that distance. And every miss adds heat to your laser, with no gain at all. If your laser overheats, you become much less of a threat to your targets. So reduce the distance to your targets as fast as you can, and get onto the tail of ships. &amp;#039;&amp;#039;&amp;#039;Use your throttle to reduce speed&amp;#039;&amp;#039;&amp;#039; and stay inside the turn of enemies, which can give you more opportunities to hit them with your laser.&lt;br /&gt;
* Make use of your missiles. The [[Missile|standard missiles]] can seem like a waste of money in the early game, but they can be useful for two things: (a) As a form of ECM. If an enemy ship fires a missile at you, fire one back at him. It&amp;#039;s quite likely they will have an ECM system and they will use it to destroy your missile, and in doing so destroy the one coming at you. (b) Fire them in close. If you can get close in behind another ship, they won&amp;#039;t be able to react in time to a missile fired at close range.&lt;br /&gt;
* Keep some &amp;quot;pirate kibble&amp;quot; handy. Pirate&amp;#039;s are desperate, and need all the funding they can get to keep their ships in space. They will demand cargo from you when they first start their attack. So, keep a few tons of food (the cheapest of all the commodities) on hand. When the demand is made, eject some of this food. The pirates will break off their attack to scoop the cargo, giving you time to get out of range. But when you eject the cargo, make sure you eject it in a direction away from the pirates. That will force them to travel further in order to scoop it, and every second they spend chasing is another moment you have to escape. The longer the better.&lt;br /&gt;
* Try to keep all jumps short, to leave fuel in your tank. Even if you don&amp;#039;t have injectors, having enough fuel to make an emergency jump to another system if things get out of hand can be life-saving.&lt;br /&gt;
* As soon as you arrive in a new system, set a course to your next one. Do this before any action starts, so you can be ready with an emergency jump.&lt;br /&gt;
* Make use of convoys. Quite often there will be other ships heading to the station from the witchpoint. Look in particular for large trading ships with escorts. Tag along with the group, even though the journey might be a bit on the slow side. If trouble starts, endeavour to put the traders between you and the pirates. In the event that a stray shot from the pirates hits one of the trader ships you&amp;#039;ll get some very welcome allies in the battle. Following an Anaconda to the station might seem tedious, but it only takes a couple of runs to start gaining enough credits to equip your ship, after which you can switch to other tactics.&lt;br /&gt;
&lt;br /&gt;
===Medium-level tactics===&lt;br /&gt;
You reach this stage when you have upgraded your laser to a beam or military level, and you have ECM&amp;#039;s and [[witch fuel injectors]]. You may not yet have shield boosters or extra energy units. At this stage you could probably take on battles against 2 to 3 opponents, or even 4 if you&amp;#039;re feeling confidant and your aim is good.&lt;br /&gt;
&lt;br /&gt;
* Most of the rules from the beginner apply here as well, and indeed apply to any player interested in combat. Don&amp;#039;t go head-to-head, don&amp;#039;t play chicken, get in close. The final tactic, of getting in close, is particularly important with the beam and military lasers. While they both have an increased range (15km for the [[Beam_Laser|beam laser]], and 30km for the [[Military_Laser|military]]), they also fire and heat up faster. Being able to fire fast is pointless if all your shots miss. So get in close, and make use of the increased rate of firing by hitting your targets with every bolt.&lt;br /&gt;
&lt;br /&gt;
* Avoid situations where there are opponents spread out across your scanner. It may seem counter-intuitive, but the closer your opponents are, the less likely you are to be hit. Once they&amp;#039;re all close, the only thing you need to be concerned about is running into them.&lt;br /&gt;
&lt;br /&gt;
* Make use of the different zoom settings of your scanner. Use &amp;quot;z&amp;quot; and &amp;quot;Z&amp;quot; (shift-z) to adjust the zoom and make it easier to see where other ships are.&lt;br /&gt;
&lt;br /&gt;
* ECM-hardened missiles can be very useful as a tactic, as well as for their destructive force. Many opponents will have injectors (you might see them rushing ahead of their comrades when battles start), and will outrun even a close-fired missile. A standard missile will likely be ECMed before it gets too far, and you don&amp;#039;t gain very much. An ECM-hardened missile, though, will force the opponent to flee much further, often completely off your scanner, which can help reduce the size of the opposing force and increase your chances of survival. Doing this before the battle is joined, before you&amp;#039;ve gotten in close, can be a good way of removing a target you think might be harder to kill (ships like an [[Asp_(Oolite)|Asp]] or a [[Fer-de-Lance_(Oolite)|Fer-de-Lance]]), allowing you to concentrate on the easier ships.&lt;br /&gt;
&lt;br /&gt;
* Try to target the weaker ships is a pirate group (eg [[Mamba_(Oolite)|Mambas]], [[Gecko_(Oolite)|Geckos]], [[Krait_(Oolite)|Kraits]]) before attempting the stronger ones (eg [[Asp_(Oolite)|Asps]] or [[Fer-de-Lance_(Oolite)|Fer-de-Lances]]).&lt;br /&gt;
&lt;br /&gt;
===Fully equipped ship===&lt;br /&gt;
When you reach this stage, you can effectively go up against much larger groups. Experienced players have often fought alone against groups of 12 or more. You&amp;#039;ll quite likely have a tail gun by this stage, and increased energy and shield strength. &lt;br /&gt;
&lt;br /&gt;
Some rules always apply: head-to-head is still never a good idea, and getting in close is the best way to deal with opponents. With a tail gun, though, especially if it&amp;#039;s a military laser, you have the option of sniping - that is, of heading away from the opposing force and using the rear laser to pick-off targets. You need to have a good eye for long distance shooting, as your laser will heat up quickly. You can snipe with the front laser as well, but be careful of the golden rule - don&amp;#039;t go head to head. If you plan on sniping with your front laser, bring your ship to a halt first, at the limit of the range of your laser, and snipe from there. The enemy ships will continue to fly towards you, but now the closing speed is halved, giving you more reaction time for when missiles are fired. As your targets get within range to use their own lasers, turn away and use injectors to get out of range, then stop at your laser range, rinse and repeat.&lt;br /&gt;
&lt;br /&gt;
Injectors are a great tool for combat, both in the pre-combat stage, where it allows you to get in close faster, but also in escape, when things aren&amp;#039;t going well, in getting you out of range faster. The key for injectors is fuel; no fuel means no injectors. Keep watch of your fuel use, and be careful when planning your jump routes. Wherever possible choose a route that will leave you with at least 1 or 2ly of fuel at your destination, particularly when your destination is a dangerous system. But also stay aware of your remaining fuel at all times - it can be disastrous to get into trouble in a battle, decide to turn and flee, and waste precious seconds hitting the injectors with no result. In that &amp;quot;Why aren&amp;#039;t my injectors working?&amp;quot; moment you could find yourself floating free in space.&lt;br /&gt;
&lt;br /&gt;
{{:Combat Manoeuvers}}&lt;br /&gt;
&lt;br /&gt;
==Tactics for cargo ships==&lt;br /&gt;
For a combat player making the decision to switch to a non-combat-focused ship, the greatest difficulty you will face is your own instinct to fight every fight. Cargo ships are slow and very non-agile. They can sport some reasonable defences, but often the best tactic is to avoid combat wherever possible. Use the tools provided by the [[Advanced_Navigational_Array|Advanced Navigational Array]] to plot safer routes and avoid dangerous systems as much as you can.&lt;br /&gt;
&lt;br /&gt;
If you&amp;#039;re starting the game in a bulk hauler, consider moving the standard-fitted front-mounted laser to the rear position. You might find this is a more advantageous position.&lt;br /&gt;
&lt;br /&gt;
Sometimes, though, you can&amp;#039;t avoid dangerous systems, because that&amp;#039;s often where the best profits can be found, and bulk haulers are looking for those big profits. Apart from using injectors and keeping some &amp;quot;pirate kibble&amp;quot; on hand (and on a big hauler, there should always be a bit of room for it), rear lasers and ECM-hardened missiles are your friends here. Turn away from any approaching pirate pack, and snipe them with your rear military laser. Your manoeuvrability is a bit restricted in a large ship, so this is your best chance of hitting anything. As they get in range, use injectors to get back out of range, or fire an ECM-hardened missile to make them run.&lt;br /&gt;
&lt;br /&gt;
==Tactics for particular scenarios==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Piracy&amp;#039;&amp;#039;&amp;#039;: See this article for details on [[Dealing with piracy (Oolite)|dealing with piracy]].&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Thargoids&amp;#039;&amp;#039;&amp;#039;: See this article for details on [[Dealing with Thargoids|dealing with Thargoids]], but in short, target the motherships first and ignore the Thargons as much as possible. If you can disable and destroy the motherships, the Thargons will shut down anyway.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Assassins&amp;#039;&amp;#039;&amp;#039;: If you pursue a career as a courier or passenger ferry, you will more than likely experience the situation where you arrive at a witchpoint and are jumped on by one or more assassins. In this situation be careful: assassins have a &amp;quot;Clean&amp;quot; record - if you are also clean, and a police vessel sees you in a fight with an assassin, you might suddenly find you&amp;#039;ve got a bounty on your head and you&amp;#039;re fighting the police as well.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Small targets&amp;#039;&amp;#039;&amp;#039;: note that there are particular problems with hitting very small targets - see [https://bb.oolite.space/viewtopic.php?t=22191 here]!&lt;br /&gt;
&lt;br /&gt;
==Who&amp;#039;s Who==&lt;br /&gt;
There are many different people in space, all doing different things.&lt;br /&gt;
&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Traders&amp;#039;&amp;#039;&amp;#039;: They have some guts to dare the dangerous business of galactic freight hauling. Yet, tend to cut and run at the first sign of trouble; few will stand their ground, and only when they have some backup, be it escorts, police, or hunters willing to cover their asses.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Escorts&amp;#039;&amp;#039;&amp;#039;: Paid mercenary pilots, hired to cover the big long-haul freighters.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Police&amp;#039;&amp;#039;&amp;#039;: Gatekeepers of law and order... Usually. Not so much in the anarchic frontiers though.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Couriers&amp;#039;&amp;#039;&amp;#039;: Freelance post runners, operating outside the regular postal services. Like traders will also break for it when shot at.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Hunters&amp;#039;&amp;#039;&amp;#039;: Ranging from paramilitary squadrons, to lone wolf vigilantes. Former traders perhaps, who made their bank grinding the long hauls, and now seek to inflict the same misery on pirates as pirates inflicted on them as traders. Usually fly very well kitted combat ships, and will be relentless in battle.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Pirates&amp;#039;&amp;#039;&amp;#039;: Whether natural psychopaths or too stupid to succeed at honest work, these are the scum of the universe who adopted a criminal lifestyle. Despite an outwardly bravado, many will scatter if they find themselves outclassed, thus why they tend to attack in packs, flying ships in varying states of repair. They will often move from their anarchies and such-like to raid neighbouring safer systems.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Assassins&amp;#039;&amp;#039;&amp;#039;: these don&amp;#039;t back down, and a top-rated heavy assassin (they fly Asps) can be a challenge. See [https://bb.oolite.space/viewtopic.php?p=241810#p241810 here] and following for more.&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Aegis Raiders&amp;#039;&amp;#039;&amp;#039;: pirates or assassins who raid the station [[Aegis|aegis]] for prey. See [https://bb.oolite.space/viewtopic.php?p=241810#p241810 here] and following for more.&lt;br /&gt;
&lt;br /&gt;
==Escaping tactics==&lt;br /&gt;
Running away can be the better part of valour during the early game. However, there are some things to remember even in this situation.&lt;br /&gt;
* Don&amp;#039;t fly straight. Flying in a straight line makes you a very predictable target. Without injectors to outrun other ships, you have to jink your ship around as much as you can.&lt;br /&gt;
* Head towards safety. Even while you&amp;#039;re bobbing and weaving to throw off the aim of the ships, you still have to maintain a general line of flight towards safety. Safety could mean a group of police ships, or a station. Don&amp;#039;t discount hiding in a Rock Hermit either. If nothing else it gives you a break and lets you refuel (which, if you have fuel injectors, could be critical) and lets your shields and energy banks recharge.&lt;br /&gt;
* If you have an aft laser, don&amp;#039;t forget about it. Ships trying to line you up in their sights will often fly straight, making themselves much easier to target. A few hits with a laser may completely dissuade them from chasing you.&lt;br /&gt;
&lt;br /&gt;
==Tactics for specific equipment==&lt;br /&gt;
&amp;#039;&amp;#039;Note: For rather more detail look at [[Laser tactics]].&amp;#039;&amp;#039;&lt;br /&gt;
===Pulse lasers===&lt;br /&gt;
With a range limited to 12.5km, these are a short range weapon. You have to get in close for these to have any impact at all.&lt;br /&gt;
&lt;br /&gt;
===Beam lasers===&lt;br /&gt;
The range is slightly improved over a pulse laser, at 15km, and they fire much faster. But they also heat up faster. These are still considered a close-range weapon, and not suitable for longer range targets (except perhaps larger ships that are slower and therefore easier to target)&lt;br /&gt;
&lt;br /&gt;
===Mining lasers===&lt;br /&gt;
These aren&amp;#039;t usually considered a combat weapon, but if used carefully they can pack quite a wallop. Sometimes, though, you will find yourself in combat, so it&amp;#039;s worth considering how these should be used. Because of the slow rate of fire, careful aiming is crucial. Mining lasers have the same range as a pulse laser (12.5km), so get in close before you fire.&lt;br /&gt;
&lt;br /&gt;
===Military lasers===&lt;br /&gt;
These are perfect for sniping, because of their extreme range (30km). However, heat management is critical as these lasers get hot fast. They make good short range weapons, because of the power in each shot and how fast those shots can be delivered, but you will find you need to spend some time in dodge-mode while you wait for your lasers to cool enough to deliver the kill shot.&lt;br /&gt;
&lt;br /&gt;
===Fuel Injectors===&lt;br /&gt;
Fuel Injectors are an essential part of any pilot&amp;#039;s ideal ship configuration. They can be used in attack (to close the distance to approaching enemy ships) or in defence (in escaping overwhelming situations), but it should be noted that they are not a &amp;quot;get out of jail free&amp;quot; card. Firstly, they use fuel, and lots of it. Using injectors indiscriminately can leave a pilot short for essential jumps. But also, not all enemies can be escaped just by using injectors. Some pirates will chase players with their own injectors, and quite often their injector speed is greater than that of the player (eg an [[Asp_(Oolite)|Asp]]). Injectors alone cannot be the only weapon in a pilot&amp;#039;s arsenal. &lt;br /&gt;
&lt;br /&gt;
That being said, even if the player is chased by a pirate with injectors, it can still be useful to employ the tactic in order to reduce the number of pirates being fought with.&lt;br /&gt;
&lt;br /&gt;
===Missiles===&lt;br /&gt;
&amp;#039;&amp;#039;Note: For rather more detail look at [[Missile tactics]] and [[Using weapons of mass destruction]].&amp;#039;&amp;#039;&lt;br /&gt;
* [[Missile|Standard missiles]] should be shot at close range, and the less the target is moving the more likely it will arrive before it&amp;#039;s hit by an ECM blast. &lt;br /&gt;
* [[ECM_Hardened_Missile|ECM-hardened missiles]] can be shot at long range, and are useful for thinning out an attacking group. &lt;br /&gt;
* [[Quirium_Cascade_Mine|Quirium Cascade Mines]] are truly a weapon of last resort. They are indiscriminate in their destructive power, and you will likely need injectors to escape the deadly wall of blue energy. However, they can be very effective in the right situations (eg against a large group of [[Thargoid_Warship_(Oolite)|Thargoids]]). Setting off a mine near a main station is not a good idea.&lt;br /&gt;
&lt;br /&gt;
Make note of the keys that control what missile/bomb will be fired next. The &amp;quot;y&amp;quot; key will cycle through your available missiles to let you select the next to be fired. If you carry a Quirium Cascade mine, this key can save you from an embarrassing (and potentially lethal) mistake.&lt;br /&gt;
&lt;br /&gt;
===Incoming missiles and ECM===&lt;br /&gt;
When a missile is fired at you, hit the ECM system straight away and &amp;#039;&amp;#039;keep&amp;#039;&amp;#039; hitting it until the missile is destroyed. Even with ECM-hardened missiles, keep hitting the ECM, as there is still a chance the counter-measure will be effective. &lt;br /&gt;
&lt;br /&gt;
You can also target the nearest incoming missile with one of your own by pressing T (shift-t) and then by firing it.&lt;br /&gt;
&lt;br /&gt;
Using the ECM will use energy - lots of it, actually. In a ship like a Cobra Mark III you have quite a bit of energy to spare, but in smaller ships your energy reserves are limited. You may find your ECM won&amp;#039;t fire because there is insufficient energy to run it. Keep an eye on your energy during battles to make sure you know if you need to run away from an incoming missile.&lt;br /&gt;
&lt;br /&gt;
If you don&amp;#039;t have an ECM system, or the missile is resistant to the counter-measures, you may not be able to avoid the blast. In that case, turn your ship around and run away from the missile. If you have injectors, great! Use them to escape. If you don&amp;#039;t have injectors, you can still survive the impact if you’re travelling away from the missile when it hits you. This reduces the impact somewhat. A fully shielded ship should be able to withstand a missile in this way.&lt;br /&gt;
&lt;br /&gt;
==OXP options==&lt;br /&gt;
There are a &amp;#039;&amp;#039;lot&amp;#039;&amp;#039; of OXP options for making combat easier. However, please make sure you read all the information about these OXP&amp;#039;s before you install them. There may be unexpected consequences from adding them. For instance, adding missiles and/or bombs also makes them available to NPC ships, meaning some of these items may be fired at you.&lt;br /&gt;
&lt;br /&gt;
This list is not to be considered as some form of recommendation, or even a complete list of OXP&amp;#039;s designed to help with combat, but merely as a starting point for finding OXP additions that might be suitable in your play experience. The links will take you to the page that describes the equipment. Read this information carefully before installing the OXP.&lt;br /&gt;
&lt;br /&gt;
For a full list of OXP&amp;#039;s you can visit [https://www.oolite.space/oxps/ oolite.space/oxps], which lists all OXP&amp;#039;s that can be downloaded directly from within the game, or go to [[OXP_List|the OXP List]] which lists pretty much everything else that&amp;#039;s available.&lt;br /&gt;
&lt;br /&gt;
=== Cheap and useful options for new players ===&lt;br /&gt;
*[[Military Targeting System]] - basic system is free! Automatically targets what you are looking at (you might wish to keep your weapons systems off-line to prevent hitting the wrong key!). &amp;#039;&amp;#039;Not&amp;#039;&amp;#039; on the in-game [[Expansions Manager]].&lt;br /&gt;
*[[Barrel Roll OXP]] - launch into a defensive barrel roll to prevent lasers hitting you (30₢, from TL6 and up)&lt;br /&gt;
*[[Fast Target Selector OXP]] - Scrolls between possible targets (all or just hostile: 10₢, from TL5 and up). This conflicts with the expensive part of the Military Targeting System (2,500₢).&lt;br /&gt;
*A HUD whose reticle lights up when you are on-target and have bought the [[STE]] (&amp;#039;&amp;#039;eg&amp;#039;&amp;#039; [[Vimana HUD]], [[CombatHUD]]). The HUDs are free, but STE costs 450₢ (TL12+).&lt;br /&gt;
*[[HUD Selector]] allows you to reset your Scanner and use the NonLinear setting where close-up matters are magnified and distant objects still visible (useful for dogfights with more than one participant). Free, unless you want to buy the in-flight selector.&lt;br /&gt;
&lt;br /&gt;
Some of these are included again below.&lt;br /&gt;
&lt;br /&gt;
===Targeting options===&lt;br /&gt;
* [[Guide to Accuracy OXPs]] has a fulsome analysis of what is available (and some notes on the Vanilla game options).&lt;br /&gt;
&lt;br /&gt;
=== Defensive Options ===&lt;br /&gt;
* [[Barrel Roll OXP]]&lt;br /&gt;
* [[Auto-ECM]] - automatically fires your ECM - this may not be ideal!&lt;br /&gt;
* Chaff Dispenser (part of [[Missiles and Bombs]] OXP)&lt;br /&gt;
* Anti-Missile System (part of [[Armoury OXP]])&lt;br /&gt;
&lt;br /&gt;
===Laser options===&lt;br /&gt;
* [[Laser Arrangement]] makes it much easier to switch lasers (&amp;#039;&amp;#039;eg&amp;#039;&amp;#039; from your front mount to the aft mount) while docked.&lt;br /&gt;
* [[Multiple Lasers]] mounts multiple lasers facing in the same direction enabling one to fire a broadside at the foe!&lt;br /&gt;
* The [[Laser_Mount_Switching_System_OXP|Laser Mount Switching System]] can also help by allowing two lasers to be installed in one position and then switched in flight.&lt;br /&gt;
* The [[Laser_Booster_OXP|Laser Booster]] can give your existing laser a boost, making it give more damage.&lt;br /&gt;
* The [[Laser_Cooler|Laser Cooler]] can help bring the heat down on your laser quickly.&lt;br /&gt;
* [[LaserCannons|Laser Cannons]], [[New lasers]], [[Gatling Laser]], [[Separated Lasers]] &amp;amp; [[Sniper Gun]] provide new laser options that increase your fire-power.&lt;br /&gt;
&lt;br /&gt;
===Missile options===&lt;br /&gt;
* [[Missiles_and_Bombs|Missiles and Bombs]] and [[Armoury_OXP|Armoury]] provides more missile and bomb options for the player, which can sometimes particularly help with larger targets (like Thargoid motherships). Be aware, some of these missiles may be used against the player.&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18705 Missile beep] adds an audible notification that a missile is inbound.&lt;br /&gt;
* [[I_Missile|I Missile]] is another missile option, with high speed and high impact.&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=14420 Nexus Missiles] provide various multi-warhead, semi-automatically-targeting, missiles.&lt;br /&gt;
* If you&amp;#039;re missing the Energy Bomb from the original Elite, you can add it back in with the [[Energy_Bomb|Energy Bomb OXP]].&lt;br /&gt;
&lt;br /&gt;
===Escort options===&lt;br /&gt;
* [[Hired_Guns_OXP|Hired Guns]] gives the player the opportunity to hire a pair of escorts for a single trip.&lt;br /&gt;
* [[EscortDeck|Escort Deck]] allows the player to fly with several escort ships attached via an external deck, while [[Carriers]] lets you fly with a big ship, and then switch into one of your escort ships to perform defensive actions. The [[EscortPack|Escort Pack]] expands the types of ships that can be added to either of these options.&lt;br /&gt;
* [[Fighters]] allows larger ships to launch small fighters to attack targets, and then the fighters can be scooped up afterwards.&lt;br /&gt;
&lt;br /&gt;
===Energy options===&lt;br /&gt;
* [[Energy_Equipment_OXP|Energy Equipment]] can help quickly recharge a depleted energy bank.&lt;br /&gt;
* [[Shield_Equalizer_%26_Capacitors_OXP|Shield Equalizer &amp;amp; Capacitors]] will equalise shields if one is higher than the other, as well as storing energy and passing it back into the shields when they are reduced.&lt;br /&gt;
* [[ShieldCycler|Shield Cycler]] allows pilots to configure how shields are to be configured: all forward, all aft, or both. This can really help if your default method of dealing with enemy ships is to turn away and snipe with a tail laser.&lt;br /&gt;
&lt;br /&gt;
===HUDs===&lt;br /&gt;
Many of the newer HUDs reconfigure themselves for combat to move needed information closer to the crosshairs. Some include sensitive reticles showing when your lasers are on target, some include glare protection, some include missile identifiers, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. See [[HUD images here]] &amp;lt;br&amp;gt;&lt;br /&gt;
Worth mentioning are [[CombatHUD]] (reticles), [[Vimana HUD]] (warnings &amp;amp; reticles), [[Xenon HUD]] (glare), [[ChupacabraHUD]] (missiles).&lt;br /&gt;
&lt;br /&gt;
===Other options===&lt;br /&gt;
* [[BroadcastComms_MFD|BroadcastComms MFD]] (Multi-Function Display) gives you the chance to attempt to bribe an attacker with some credits. If the bribe fails, you can try offering them even more credits.&lt;br /&gt;
* [[GalCop_Galactic_Registry|GalCop Galactic Registry]] can help you examine the make-up of the galaxy by highlighting specific elements of the sector (economies, techlevel, government, etc).&lt;br /&gt;
* [[Fuel_Tank|Fuel Tank]] is a disposable, pylon-mounted accessory that allows for an additional 3ly of fuel to be carried, to top up fuel tanks when required.&lt;br /&gt;
* [[Military_Fuel_Injectors_OXP|Military Fuel Injectors]] will reduce the fuel consumption of your fuel injectors.&lt;br /&gt;
* [[Ship_Configuration|Ship Configuration]] has options for increasing the speed of fuel injectors, adding extra energy banks, increasing the base speed of your ship. However, this OXP also limits the amount of equipment that can be installed on your ship, so make sure you understand what the OXP will do by reading the documentation carefully.&lt;br /&gt;
[[Category:Oolite]]&lt;br /&gt;
&lt;br /&gt;
==Mechanical Tweaks==&lt;br /&gt;
*You might find it helpful to reconfigure your keyboard.&lt;br /&gt;
**[[Keyboard Cobra]] OXP retunes the navigation keys to be more precise helping accuracy with your laser.&lt;br /&gt;
**TSOJ [https://bb.oolite.space/viewtopic.php?p=270930#p270930 suggests] rebinding the navigation keys in a more easy-to-use manner&lt;br /&gt;
**Linux keyboards (non-US) can be a major problem: see [https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=20822 here].&lt;br /&gt;
*** Non-English Language Keyboards can be [https://bb.oolite.space/viewtopic.php?f=8&amp;amp;t=20638 problematic].&lt;br /&gt;
*OR you could try using something other than just your keyboard!&lt;br /&gt;
**Use your mouse! &amp;#039;&amp;#039;&amp;#039;Shift-M&amp;#039;&amp;#039;&amp;#039; (for roll on x-axis) &amp;amp; &amp;#039;&amp;#039;&amp;#039;Shift-Control-M&amp;#039;&amp;#039;&amp;#039; (for yaw on x-axis) toggle flight control for your mouse in full-screen playing mode.&lt;br /&gt;
**Add a game controller! Look [[Dizzy&amp;#039;s guide to Setting up Joystick Axis Profiles|here]] &amp;amp; also at [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=18855 this] discussion.&lt;br /&gt;
**Or add a speedpad&lt;br /&gt;
**Or add a joystick. Ideally one compatible with your computer! Tips [[Dizzy&amp;#039;s guide to Setting up Joystick Axis Profiles|here]]&lt;br /&gt;
**Or a joystick &amp;amp; throttle set (HOTAS: Hands-On Throttle And Stick). Tips [[Dizzy&amp;#039;s guide to Setting up Joystick Axis Profiles|here]]&lt;br /&gt;
**Or two joysticks (HOSAS: Hands-On Stick And Stick). Tips [[Dizzy&amp;#039;s guide to Setting up Joystick Axis Profiles|here]]&lt;br /&gt;
**Or even a [[Buttonboxes|Buttonbox]]!&lt;br /&gt;
&lt;br /&gt;
Different things work for different people. Some people swear by the keyboard. Other people swear &amp;#039;&amp;#039;at&amp;#039;&amp;#039; the keyboard! HOTAS &amp;amp; HOSAS are also superb for the immersion factor. If you are interested in the joystick route try searching for &amp;#039;&amp;#039;joystick&amp;#039;&amp;#039; or &amp;#039;&amp;#039;hotas&amp;#039;&amp;#039; in the bulletin board!  &amp;#039;&amp;#039;&amp;#039;Warning&amp;#039;&amp;#039;&amp;#039;: most models do not work fully with &amp;#039;&amp;#039;AppleMacs&amp;#039;&amp;#039; or &amp;#039;&amp;#039;Linux&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
== Oolite combat vs Elite combat ==&lt;br /&gt;
&amp;#039;&amp;#039;Comments of Another_Commander, one of the Oolite Developers (see his combat style [https://www.youtube.com/watch?v=IHnjUjZVtgk here])&amp;#039;&amp;#039;&lt;br /&gt;
   The first thing one needs to do when starting fresh in Oolite is forget the combat play style of the old Elite 8-bit versions. Back in the old days, screen resolutions were much lower as you have correctly mentioned, frames per second were in the single digits for the fastest computers of the time, memory available for AI routines &amp;#039;&amp;#039;etc&amp;#039;&amp;#039; was much much lower and so on. This resulted in combat tactics that were fit for purpose for the available spec. An example of this is the &amp;#039;&amp;#039;&amp;#039;fat pixel&amp;#039;&amp;#039;&amp;#039; that represented any ship at large distances. Back then, the standard combat tactic I was using on the Spectrum was to shoot that fat pixel as much as I could before the ship it represented approached to a distance where the switch to proper vector graphics was made. Battles could finish in a few seconds like this before they even had a chance to properly start. And of course, it meant that I kept my ship moving steady forward while doing all this.&amp;lt;br/&amp;gt;&lt;br /&gt;
   The above example will not work in [[Oolite]]. Nowadays we have high resolution graphics and better artificial intelligence. There is no fat pixel anymore and ships are drawn as textured meshes regardless of distance, often with shaders running on top of them. So, there is no easy targeting at the start of combat and the AI is using predictive routines to try to judge where it should fire the next shot. Someone engaging in a fight while carrying the mindset of 8-bit computers will see the &amp;#039;&amp;#039;game over&amp;#039;&amp;#039; screen very quickly indeed.&amp;lt;br/&amp;gt;&lt;br /&gt;
   On top of this, there is one more detail that I need to bring to everyone&amp;#039;s attention: Most of us (and, from what I understand reading your first post, you too) have memories of how Elite used to be when we had a fully equipped ship. I remember Elite being really easy once I had an iron-ass ready. I, just like you, was hunting Thargoids in witchspace for that extra bit of challenge and I still could eliminate hordes of them in one little single ship. That, looking back at it many years after, seems wrong, no? But the question here is, does anyone remember how it was when they were starting? Was it not hard back then? Did you not lose one battle after another? I remember I did, and I remember being frustrated. But the feeling of achievement when I won my first encounter against a pack of three using a pulse laser (even though I had to bring a half-destroyed ship to the station) was so intense that it made all worth it at the end. And the rewarding feeling of adding one more piece of equipment to the ship as I was progressing was enhanced by the fact that I knew that next time I was going to be in combat I would have slightly better odds. And because of this, I wanted to continue playing (you know, that &amp;quot;one more flight and I&amp;#039;m done&amp;quot; thing... ;-))&amp;lt;br/&amp;gt;&lt;br /&gt;
   We are trying to capture this in Oolite. Yes, it is very difficult. It used to be even more difficult in the previous version. We had players coming here to complain about it but, guess what, the very same players who persisted and did not give up told us a few months down the line that the game was perfectly balanced after all and we really did not have to do any changes (but we did, because v1.80 was really, seriously difficult). To be able to capture this, some base design decisions had to be made and they have been with us almost since the beginning.&amp;lt;br/&amp;gt;&lt;br /&gt;
   The philosophy here is two-fold: 1. The player ship is just another ship in the universe, no special treatment is reserved for it (the polar opposite of the 8-bit Elites) and 2. The player must be able to be challenged even at higher ranks, but still be able to survive at start up.&amp;lt;br/&amp;gt;&lt;br /&gt;
   The immediate implication of this is that there are no skill levels. The game will not give you easy opponents in the beginning and harder ones when you are rated Deadly. The universe will always be the same. Bad things may and will happen to the player regardless of rank. Battle against a small group of pirates when armed only with what our &amp;#039;&amp;#039;&amp;#039;Advice For New Commanders document&amp;#039;&amp;#039;&amp;#039;, distributed with the game, refers to as &amp;quot;penlight&amp;quot;, should not be easy. Sometimes the Brave Sir Robin tactic may be a really good option and part of the strategy of this game is exactly this kind of decision making, knowing when it&amp;#039;s ok to flee and when it is worth facing the opposition. Getting surrounded by a wolfpack of 8 should be barely survivable even for an iron-ass Cobra.&amp;lt;br/&amp;gt;&lt;br /&gt;
   Having said that, I get the impression from your posts that you believe the enemies are unbeatable. They are not. You &amp;#039;&amp;#039;can&amp;#039;&amp;#039; win against them. NPCs do not have shields (one of the very few occasions where the player is given an advantage free of charge), only energy banks and those are exactly the same as yours. One of the things we did when we adjusted the balance for 1.82, was a survey amongst players. Part of the data collected was input from a few experienced players who started as brand fresh commanders at Lave when we asked for their help. And their input was that, with the balance changes in 1.82, it was definitely doable. Not easy, mind you, but doable. I expect that fresh players will obviously not find it doable immediately, but I believe that it is just a matter of persistence and developing some skill that was simply not applicable in the 8-bit versions, before they get to the level where they can make it. You already seem to be getting there; remember that ship that run away on injectors after having begged for mercy? You almost had him there and if he used injectors to flee, it was because he had already lost the battle. Without injectors, you would have finished it really soon.&amp;lt;br/&amp;gt;&lt;br /&gt;
   In any case, ships with injectors in the core game are mostly Asps, Kraits or Fer-de-Lances, so it was not exactly an easy-peasy fight you had there to begin with. So you are already progressing, but you seem to be quite unlucky too (bumping on tough opponents, having your Energy Unit being picked as the first equipment to be damaged in combat etc), but I am sure you are getting there.&amp;lt;br/&amp;gt;&lt;br /&gt;
   Some tips have already been given and there are other combat tactics that you can find out as you play the game too. For example, did you know that if you put your ship between the sun and your enemies, the sun glare will blind them and cause them to miss a lot? Also, fly unpredictably. The enemies are programmed to simulate human behaviour and they try to predict where you will go next based on your current heading and maneuvering. Surprise them. If you have one ship in your sights and another starts hitting you, do not be afraid to break lock on your current target and evade. Be on the move at all times. I&amp;#039;m sure you will find other tactics yourself if you don&amp;#039;t give up. And yes, get a military laser, it makes life so much easier. And quirium bombs, they are good for cleaning up a mess, provided you can run fast. [https://bb.oolite.space/viewtopic.php?p=239479#p239479 another_commander (2015)]&lt;br /&gt;
&lt;br /&gt;
== BB threads ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=495 Favourite Combat Tactics] (2005-16)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=7053 Stalemate frustration] (2009)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=6214 is there a such thing as evasive maneuvers?] (2009)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=8686 Combat] (2010)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=8189 Group dogfight tactics] (2010)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=6&amp;amp;t=8283 Player not the fastest ship...] (2010) - use of speed in combat&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=7992 Important Rules for Space Combat &amp;amp; Flight] (2010) - mix of humour and serious&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=257726#p257726 Any combat tips?] (2017)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=19285 Oolite tactics] (2017-18)&lt;br /&gt;
&lt;br /&gt;
Note that the NPC&amp;#039;s tactics were beefed up in 2014 (v.1.80) and then weakened slightly in 2015 (v.1.82).&lt;br /&gt;
&lt;br /&gt;
== Other advice pages ==&lt;br /&gt;
*[[How do I ...]] dock / succeed in trading / win a fight / configure my controller/joystick &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;&lt;br /&gt;
*See also the &amp;#039;&amp;#039;&amp;#039;OoliteRS&amp;#039;&amp;#039;&amp;#039; (Reference Sheets) and &amp;#039;&amp;#039;&amp;#039;AdviceforNewCommanders&amp;#039;&amp;#039;&amp;#039; which came as .pdfs in your original game download. Probably worth printing out!&lt;br /&gt;
&lt;br /&gt;
[[Category:Help pages]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Worm_(Oolite)&amp;diff=90341</id>
		<title>Worm (Oolite)</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Worm_(Oolite)&amp;diff=90341"/>
		<updated>2026-09-30T22:22:46Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added Redspear&amp;#039;s tupenny bit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Semantic Infobox ShipStats Oolite| title=Worm (Oolite)&lt;br /&gt;
|image = [[Image:Worm.png|300px]]&lt;br /&gt;
|dimensions = 35 x 25 x 39&lt;br /&gt;
|width = 35m&lt;br /&gt;
|height = 25m&lt;br /&gt;
|length = 39m&lt;br /&gt;
|capacity = 2&lt;br /&gt;
|capacityext = N/A&lt;br /&gt;
|maxspeed = 0.11 LM&lt;br /&gt;
|maneuverability = Pitch: 1.0 &amp;lt;br/&amp;gt; Roll: 2.0 &amp;lt;br/&amp;gt; Yaw: 1.0 &amp;lt;br/&amp;gt; Trust: 12&lt;br /&gt;
|energybanks = 1&lt;br /&gt;
|energyrecharge = 2.0&lt;br /&gt;
|gunmounts = Forward&lt;br /&gt;
|missileslots = N/A&lt;br /&gt;
|shieldboost = N/A&lt;br /&gt;
|milshields = N/A&lt;br /&gt;
|hyperspace = N/A&lt;br /&gt;
|isoxp = Standard&lt;br /&gt;
|isplayer = No&lt;br /&gt;
|baseprice = N/A&lt;br /&gt;
}}&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
The Worm is a short-range craft. It is mainly seen travelling between the planet and an orbital space station, and only occasionally seen outside of the space station&amp;#039;s orbit. The Worm can also be carried by other craft, such as the giant [[Anaconda (Oolite)|Anaconda]] or [[Boa (Oolite)|Boa]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Notable features ==&lt;br /&gt;
&lt;br /&gt;
The Worm is an inexpensive and adaptable craft - it can be outfitted for passenger transport, mining or as a lifeboat. It is usually unarmed and has only the shields necessary to protect it from minor collisions with micrometeorites. It can be modified to carry a small pulse (or mining) laser, but this option is rarely exercised as the ship simply isn&amp;#039;t built for combat, and the laser would not be much help against even the most feeble attack.&lt;br /&gt;
&lt;br /&gt;
It is rumoured that the thieves of the prototype [[Constrictor (Oolite)|Constrictor]] used a Worm disguised as a naval executive shuttle to sneak into a military compound on Reesdice. The Constrictor hasn&amp;#039;t been seen since.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Variants ==&lt;br /&gt;
The most common variants of this craft are the [[Worm Miner (Oolite)|Worm Miner]], the [[Worm Prospector]] and the to a shuttle converted [[Navy Shuttle]] (Neolite Worm).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Custom paintjobs ==&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:classicWorm-A.png|[[The Classic Ships OXP|Classic Worm]]&lt;br /&gt;
Image:classicWorm-B.png|[[The Classic Ships OXP|Classic Worm Miner]]&lt;br /&gt;
Image:Deepspace_Worm.jpg|[[Deepspace_Ships|Deepspace Worm]]&lt;br /&gt;
Image:Griff_worm.jpg|[[Griff_Industries|Griff&amp;#039;s Worm]]&lt;br /&gt;
Image:Neolite_worm.jpg|[[Neolite_Ships|Neolite Worm]]&lt;br /&gt;
Image:SungsWorm.jpg|[[Shady Sungs|Sung&amp;#039;s Worm]]&lt;br /&gt;
Image:IA_worm.jpg|[[Iron Ass OXP|Iron Ass Worm]]&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Lore ==&lt;br /&gt;
Once heard this asked in a (space) bar. Everyone was arguing until this old guy started to speak...&lt;br /&gt;
&lt;br /&gt;
 See, when folks ask ya that question, ya gotta ask yerself what they&amp;#039;re really asking ya, if ya see what I mean. But anyway, yer asking me so maybe you want me to tell ya the answer or maybe it&amp;#039;s you that wants to tell me. All academic ya might say :wink:&lt;br /&gt;
 &lt;br /&gt;
 For me, and I&amp;#039;ve no doubt on this having been in all of &amp;#039;em and flown most of &amp;#039;em, it&amp;#039;s simple. The worm is the best ship in [[The Eight|the eight]].&lt;br /&gt;
 &lt;br /&gt;
 Now I know that some folks will pick a &amp;#039;classic&amp;#039; like the [[Python (Oolite)|python]], as if the backstory&amp;#039;s part of the attraction; others favour new-fangled technology, the kind you&amp;#039;ll find in a [[Fer-de-Lance (Oolite)|fer-de-lance]] or [[Cobra Mk.3 (Oolite)|cobra three]]. Then there&amp;#039;s the &amp;#039;best of&amp;#039; bunch who&amp;#039;ll pick the fastest or the biggest or the toughest; and we&amp;#039;ve all met that guy who&amp;#039;ll surprise ya, with somethin&amp;#039; sounds crazy, just waitin&amp;#039; to tell ya why :wink:&lt;br /&gt;
 &lt;br /&gt;
 It&amp;#039;s cos in the worm there&amp;#039;s me and no other... or maybe one other, all the mod-cons I could wish for and nothin&amp;#039; else save for privacy: rarest comodity there is outside of an escape pod but who wants to be in one of those any more than bein&amp;#039; in stasis? See, the worm&amp;#039;s too slow to even knock a hair out of place, too small for worrying about cargo or crew and too vulnerable to travel alone - so it doesn&amp;#039;t.&lt;br /&gt;
 &lt;br /&gt;
 Luxury ain&amp;#039;t the usual word most folks think of when considerin&amp;#039; the worm but then most folks never flew in one. The most luxurious vessels imaginable will still equip a small fleet of worms. When ya next visit the observation deck on that [[Liners|fancy cruise ship]], imagine having it all to yerself: drifting safely and securely, free for yer mind to wander where it will while the folks elsewhere see to everything for ya. Can&amp;#039;t do that in a cobra, my friend.&lt;br /&gt;
 &lt;br /&gt;
 Sure, you can turn on the auto-pilot in yer fer-de-fancy-pants but you&amp;#039;ve still got to worry about everything else because it&amp;#039;s all on you. Most of them guys can&amp;#039;t even bear the thought of scratching the paintwork, never mind losing a shield. Fact is, in a worm, whatever it is, chances are someone else is doin&amp;#039; it for ya, all discreet mind, in some other ship, not bothering ya across the coms all the time. Even them miner&amp;#039;s have the cobras do the scoopin&amp;#039; while they stick to the shootin&amp;#039;.&lt;br /&gt;
 &lt;br /&gt;
 Besides, ain&amp;#039;t no paint job to speak of on a worm: that thing looks like a bashed up cargo pod to begin with and that&amp;#039;s exactly as it should be. Privacy doesn&amp;#039;t draw attention to itself unnessarily: tinted viewscreens that run the length of your ship will tend to do that [[Zorgon Petterson Group|Mr. Zorgan Petterson]]; twelve rules for ship design indeed...&lt;br /&gt;
 &lt;br /&gt;
 I&amp;#039;ve heard so many folks tell me that ya ain&amp;#039;t lived until you&amp;#039;ve flown a this, that or the other (and some of &amp;#039;em may even have a point) but I&amp;#039;ll tell ya what little I do know. When ya really have lived then you&amp;#039;ll appreciate bein&amp;#039; in a worm. Nothin&amp;#039; better my friend, nothin&amp;#039; better... [https://bb.oolite.space/viewtopic.php?p=280595#p280595 Redspear (2021)]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=HUD_images_here&amp;diff=90340</id>
		<title>HUD images here</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=HUD_images_here&amp;diff=90340"/>
		<updated>2026-09-30T15:27:52Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added CB-HUD Mark IV &amp;amp; Mark III&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Images are &amp;#039;&amp;#039;below&amp;#039;&amp;#039; their captions.&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
&lt;br /&gt;
 A HUD is a Heads-Up Display: &amp;#039;&amp;#039;a transparent display that presents data without requiring users to look away from their usual viewpoints. The origin of the name stems from a pilot being able to view information with the head positioned &amp;quot;up&amp;quot; and looking forward, instead of angled down looking at lower instruments. A HUD also has the advantage that the pilot&amp;#039;s eyes do not need to refocus to view the outside after looking at the optically nearer instruments First developed in the 1940s for military aircraft (from Wikipedia).&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
As the newer versions of Oolite have allowed more flexibility with modifying HUD elements since the early days of Oolite v.1.20 in 2004! From the halcyon days of Aegidian&amp;#039;s Mega-Walnut dashboard (for the Fer-de-Lance), the HUD designers have risen to the challenge. There was a quantum leap under [[User:Cim|Cim]]&amp;#039;s tenure as lead designer, when it was made easier to code new HUDs and the range of possibilities was greatly increased. This extended to [[MFD]]s. This happened with the release of Oolite v.1.79 in 2013/4.&lt;br /&gt;
&lt;br /&gt;
The most striking versions here include the Coluber, Dangerous &amp;amp; Vimana HUDs.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Ships with custom HUDs&amp;#039;&amp;#039;&amp;#039;: Note also that some ships come with their own HUD versions! &amp;#039;&amp;#039;Eg.&amp;#039;&amp;#039;: [[Coluber Blue Racer|Coluber Racers]] - Blue, Red, Yellowbelly &amp;amp; Black; also [[Isis Interstellar]] ships, all of [[Simon B&amp;#039;s Ships OXP|Simon B&amp;#039;s ships]] in Neolite-Wolfies and some of his Waka series, some of Wolfwood&amp;#039;s ships such as his [[Asp Explorer (Oolite)]], &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;HUDs not shown here&amp;#039;&amp;#039;&amp;#039;: Note also that some HUDs are not shown here: [[Killer Wolf&amp;#039;s Dynamic HUD]], [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16686 Cyan HUD], [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12476 Clear HUD], &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. See the [[OXP List]] and its links for more.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Experimenting with new HUDs&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
The easiest way into all this is probably using [[HUDSelector]] which comes with 3 more HUDs to try out (extra-large, large &amp;amp; small). It will then help manage most others you download.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Four points&amp;#039;&amp;#039;&amp;#039;: &amp;lt;br&amp;gt;&lt;br /&gt;
1) The game specifies 2 types of HUD: &amp;#039;&amp;#039;small&amp;#039;&amp;#039; (for the [[Adder (Oolite)|Adder]], the [[Cobra Mk.1 (Oolite)|Cobra Mk.1]], &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;) and &amp;#039;&amp;#039;regular&amp;#039;&amp;#039;. Most of these below do not have a small variant, so you will find that your small ship defaults to the Vanilla game&amp;#039;s small ship HUD! &amp;lt;br&amp;gt;&lt;br /&gt;
2) The number of MFDs varies with the HUD (from 0 to 15)! MFDs were introduced in 2013/14&amp;lt;br&amp;gt;&lt;br /&gt;
3) HUD designers often include icons for their favourite oxp equipments. See Coluber (&amp;amp; Deeper Space), CB (&amp;amp; CRR), Vimana &amp;amp; Z-GrOovY MiLHUD below for examples. &amp;lt;br&amp;gt;&lt;br /&gt;
4) A number of HUDS have special features&lt;br /&gt;
:* Choice of layouts/colour - Dangerous HUD (fighter cockpit view, hauler cockpit view and glass only view, 6 colours) &amp;amp; Xenon HUD (2 colours)&lt;br /&gt;
:* HUD changes with alert level (green/yellow/red) emphasising either astrogatory or combat elements (many HUDS do this - but see [[MilHUD 4000]] which only changes for combat - not low altitude &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.)&lt;br /&gt;
:* Current Location Display (with Current Risk Notifier) - see Deeper Space HUD&lt;br /&gt;
:* Weapon Bays Missile Identifier - see ChupacabraHUD&lt;br /&gt;
:* Warning signs for low altitude/energy/shields/high temperature - see Vimana HUD&lt;br /&gt;
:* Jump stability meter (counts down to jump) - see Wide-Screen HUD&lt;br /&gt;
:* Different compasses for celestial bodies (gravimeter) and for beacons (transponder) - see Wide-Screen HUD&lt;br /&gt;
:* Detection of the Police IFF Scanner Upgrade, changing to a special police scanner colour that de-emphasises police vessels and maximizes visibility of civilian vessels on the scanner.&lt;br /&gt;
:* Ship&amp;#039;s clock emphasised/de-emphasised depending on need  - see Wide-Screen HUD&lt;br /&gt;
:* Extra add-on modules (purchasable) with some of the functions of the Combat &amp;amp; Navigation MFD&amp;#039;s - see Vimana HUD&lt;br /&gt;
:* Sun glare contrast - see Xenon HUD&lt;br /&gt;
:* Variable brightness high-contrast centre patch (adjustable on the fly) - see [[MilHUD 4000]]&lt;br /&gt;
:* A Sniper Sight- see [[MilHUD 4000]] &lt;br /&gt;
:* Sound effects - see Dangerous HUD&lt;br /&gt;
:* Listings of present equipment - see Z-GrOovY MiLHUD, Vimana HUD, Deeper Space HUD &amp;amp; the Coluber HUDs (these lists are inevitably partial - there is &amp;#039;&amp;#039;so&amp;#039;&amp;#039; much equipment)&lt;br /&gt;
:*[[Shield Equalizer And Capacitors OXP|Shield Capacitors gauges]] - see [[ChupacabraHUD]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Oolite-numbered-hud.png|800px|thumb|right|&amp;#039;&amp;#039;&amp;#039;&amp;quot;Vanilla game&amp;quot; HUD&amp;#039;&amp;#039;&amp;#039; &amp;lt;br&amp;gt;&lt;br /&gt;
1 Shield Strength (Fore &amp;amp; Aft shields) &amp;lt;br&amp;gt;&lt;br /&gt;
2 Level Indicators: Fuel, Cabin Temperature, Laser Temperature &amp;amp; Altitude &amp;lt;br&amp;gt;&lt;br /&gt;
3 Pylon Weapon Indicators: Missile (selected), Missile, ECM-Hardened Missile, Quirium Cascade Bomb &amp;lt;br&amp;gt;&lt;br /&gt;
4 Aegis Indicator (for aegis of main orbital station) &amp;lt;br&amp;gt;&lt;br /&gt;
5 Mass-Lock/Status Indicator (Green, Yellow or Red) &amp;lt;br&amp;gt;&lt;br /&gt;
6 Short-Range Scanner &amp;lt;br&amp;gt;&lt;br /&gt;
7 Clock &amp;lt;br&amp;gt;&lt;br /&gt;
8 Scanner zoom factor &amp;lt;br&amp;gt;&lt;br /&gt;
9 Compass &amp;lt;br&amp;gt;&lt;br /&gt;
10 Speed Indicator (relative) &amp;lt;br&amp;gt;&lt;br /&gt;
11 Roll/Pitch Indicators &amp;lt;br&amp;gt;&lt;br /&gt;
12 Energy Banks &amp;lt;br&amp;gt;&lt;br /&gt;
Since a joystick is not plugged in, the [[Joysticks and Gamepads|Joystick precision indicator]] is not shown]]&lt;br /&gt;
&lt;br /&gt;
[[File:Simon B&amp;#039;s Wolf HUD template.png|thumb|right|800px|An Example of a Ship OXP custom HUD: Simon B&amp;#039;s Arachnid OXP &amp;quot;Wolf&amp;quot; HUD (2009)]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
=== Aad HUD ===&lt;br /&gt;
[[Aad-HUD|Almost Almost Default HUD!]] by [[User:Spara|Spara]] (2016)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:Aad-hud_normal.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Another HUD ===&lt;br /&gt;
[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=9462 Another HUD] by NorthenderPNE (2011)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:AnotherHUD.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== CB-HUD Mark II ===&lt;br /&gt;
[[CB-HUD Mark II]] by [[User:Captain Beatnik|Captain Beatnik]] (2011)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:CB-HUD_2011-09-25.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== CB-HUD Mark III ===&lt;br /&gt;
[[CB-HUD Mark III]] by [[User:Captain Beatnik|Captain Beatnik]] (2025)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:CB-HUD 2025-03-29.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== CB-HUD Mark IV ===&lt;br /&gt;
[[CB-HUD Mark IV]] by [[User:Captain Beatnik|Captain Beatnik]] (2026)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:Cb68-CB-HUD-Mark-IV.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== ChupacabraHUD ===&lt;br /&gt;
[[ChupacabraHUD]] by [[User:CommonSenseOTB|CommonSenseOTB]] (2011)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:ChupacabraHUD1.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Coluber HUD CH01 ===&lt;br /&gt;
[[Coluber HUD CH01]] by [[User:Captain Beatnik|Captain Beatnik]] (2014) &amp;amp; improved by [[User:Norby|Norby]] (2020)&amp;lt;br/&amp;gt;&lt;br /&gt;
Screenshot showing the Coluber HUD CH01 on a 2560x1440 pixel (16:9) monitor scaled-down to 1000x563 &amp;lt;br&amp;gt;&lt;br /&gt;
[[File:15wo9_coluber_hud_ch01.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== CombatHUD ===&lt;br /&gt;
[[CombatHUD]] - widescreen version (standard version has Comms and Console messages above the dials on either side). By [[User:Smivs|Smivs]] (2014) &amp;lt;br&amp;gt;&lt;br /&gt;
Combat HUD (Red Alert mode) &amp;lt;br&amp;gt;&lt;br /&gt;
[[File:chRedAlert.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Compact HUD ===&lt;br /&gt;
[[CompactHUD]] by [[User:Aegidian|Aegidian]] (by 2006), updated by [[User:Diziet Sma|Diziet Sma]] (2014)&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:Chws2.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== CRR-HUD ===&lt;br /&gt;
[[Coluber_Red_Racer#Coluber_Red_Racer_.28CRR.29_HUD|CRR-HUD BB]] An adaptation of the &amp;#039;&amp;#039;&amp;#039;Coluber Red Racer HUD&amp;#039;&amp;#039;&amp;#039;: see also [[Coluber Blue Racer]]. By [[User:Captain Beatnik|Captain Beatnik]] (2012) - there are separate HUDs for each of the 4 racers&amp;lt;br/&amp;gt;&lt;br /&gt;
[[Image:Crr_hud_pic_001.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Dangerous HUD ===&lt;br /&gt;
[[Dangerous HUD]] showing just the &amp;#039;&amp;#039;&amp;#039;green&amp;#039;&amp;#039;&amp;#039; &amp;amp; &amp;#039;&amp;#039;&amp;#039;blue&amp;#039;&amp;#039;&amp;#039; variants (not Orange, Pink, Purple &amp;amp; White). by Gsagostinho (2017-8)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:Gsagostinho-dangeroushud-blue.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== DeeperSpace HUD ===&lt;br /&gt;
[[Deeper Space HUD]] by Pleiadian (2017)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:DeeperSpaceHUD.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Deepspace HUD ===&lt;br /&gt;
[[Deepspace_Ships|Deepspace HUD]] by DeepSpace (2009)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:Deepspacehud.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Deepspace Retro HUD ===&lt;br /&gt;
[[Deepspace_Ships|Deepspace HUD]] by DeepSpace (2010)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:RetroHUD.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Dr HUD ===&lt;br /&gt;
[[Dr HUD OXP|Dr HUD]] by [[User:Dr. Nil|Dr. Nil]] (2010)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:huddrhud.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== ExtraLarge HUD ===&lt;br /&gt;
[[HUDSelector#ExtraLarge_HUD|ExtraLarge HUD]] provide a very large, alert sensitive scanner and custom dials with [[CombatMFD]] but no 16:10 support due to not enough room for the bottom two MFDs. By [[User:Norby|Norby]] (2015)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:XLHUD4r.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Fighter HUD ===&lt;br /&gt;
[[Fighter HUD (Oolite)|Fighter HUD Mk2]] by [[User:CaptKev|CaptKev]] (2008-9)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:hudfighter.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== G-HUD ===&lt;br /&gt;
[https://bb.oolite.space/viewtopic.php?t=4757 &amp;#039;&amp;#039;G-HUD Mk2&amp;#039;&amp;#039;] by [[User:Gunney Plym|Gunney Plym]] (2008)&amp;lt;br  /&amp;gt;&lt;br /&gt;
[http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip  Download]&lt;br /&gt;
[http://wiki.alioth.net/images/7/76/G-HUD_Mk2.png  &amp;#039;&amp;#039;Large version of screenshot&amp;#039;&amp;#039;]&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:G-HUD_Mk2_resize.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Isis HUD ===&lt;br /&gt;
[[Isis HUD]] by [[Killer Wolf]] (2013) &amp;lt;br&amp;gt;&lt;br /&gt;
Comes separately or included (as an option) with some Killer Wolf ships (Dominatrix, Werewolf, his newer Venom oxp&amp;#039;s).&amp;lt;br&amp;gt;&lt;br /&gt;
An old HUD: no MFD&amp;#039;s, no [[HUDSelector]] compliance.&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Isis HUD (Killer Wolf).png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== KeeperHUD ===&lt;br /&gt;
[[KeeperHUD]] by [[Keeper]] (2016) &amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:KeeperHUD mfds.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Killer Wolf&amp;#039;s Dynamic HUD ===&lt;br /&gt;
[[Killer Wolf&amp;#039;s Dynamic HUD]] by [[Killer Wolf]] (2010) &amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:KW Hud trading.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Klepto HUD ===&lt;br /&gt;
[[Klepto-HUD OXP]] by Kleptoid (2006)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:hudKleptoHUD.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Large HUD ===&lt;br /&gt;
[[HUDSelector#Large_HUD|Large HUD]] looks like the default HUD but with 10 MFDs, custom dials with [[CombatMFD]] and a large alert sensitively colored scanner. By [[User:Norby|Norby]] (2015).&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:LargeHUD9g.png|600px]] &amp;lt;br&amp;gt;&lt;br /&gt;
Both 4:3, 16:9 and 16:10 displays are supported, but in 4:3 &amp;quot;only&amp;quot; 8 MFDs are usable.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Medusa HUD ===&lt;br /&gt;
[https://bb.oolite.space/viewtopic.php?p=54886#p54886  &amp;#039;&amp;#039;Medusa HUD&amp;#039;&amp;#039;] by ClymAngus (2009)&amp;lt;br  /&amp;gt;&lt;br /&gt;
[[Image:Medusa_Hud.gif|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Mega Walnut Dash HUD ===&lt;br /&gt;
[[Mega-Walnut Dashboard OXP|Mega-Walnut Dashboard]]&lt;br /&gt;
Based on the original Fer de Lance HUD of the legendary [[User:Aegidian|Aegidian]] (2005)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:hudMegaWalnutDashHUD.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== MilHUD 4000 ===&lt;br /&gt;
[[MilHUD 4000]] by [[User: Wildeblood| Wildeblood]] (2012)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:M4000_police.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== MilHUD (Military Specification HUD) ===&lt;br /&gt;
[[MilSpec HUD OXP|MilSpec HUD]] by [[User:Wyvern|Wyvern]] (2006-11)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:hudmilspec.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== MillHUD Refit ===&lt;br /&gt;
[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17258 MillHUD Refit] by Wolfsstar BH (2015) &amp;lt;br&amp;gt;&lt;br /&gt;
Based on Wyvern&amp;#039;s MilSpec HUD: HUD Selector compatible, five alert condition colours, 10 MFD&amp;#039;s... &amp;lt;br&amp;gt;&lt;br /&gt;
[[File:MillHUD refit.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Mod HUD ===&lt;br /&gt;
[[Mod-HUD]] by [[User:CaptSolo|CaptSolo]] (2011-2)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:ModHUD-v1.0.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Nova Lux HUD ===&lt;br /&gt;
[[Nova Lux HUD]] by Vincentz (2015)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[File:NovaLux HUD (1).png|600px]]&amp;lt;br /&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Numeric Style HUDs ===&lt;br /&gt;
[[Numeric Style HUDs]] or browse viewtopic for current [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=9977 information]. By [[User:CommonSenseOTB|CommonSenseOTB]] (2011), updated by [[User:Diziet Sma|Diziet Sma]], [[User:Spara]], [[User:Norby|Norby]] (2015) &amp;lt;br /&amp;gt;&lt;br /&gt;
Version 3&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:NumericHUDv3 1.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== OrangED HUD ===&lt;br /&gt;
[[OrangED HUD]] has up to 4 MFDs. By [[User:Zireael|Zireael]] (2014) &amp;lt;br&amp;gt;&lt;br /&gt;
[[File:OrangED HUD.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Pie Chart Style HUDs ===&lt;br /&gt;
[[Pie Chart Style HUDs]] or browse viewtopic for current [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=9788 information]. By [[User:CommonSenseOTB|CommonSenseOTB]] (2011)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:PCS_HUDv2-3.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Small HUD ===&lt;br /&gt;
[[HUDSelector#Small_HUD|Small HUD]] like the default small HUD but with 10 MFDs. By [[User:Norby|Norby]] (2014)&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:SmallHUD.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Smart HUD===&lt;br /&gt;
[[SmartHUD]]-widescreen version (standard version has Comms and Console messages above the dials on either side). By [[User:Smivs|Smivs]] (2014). &amp;lt;br&amp;gt;&lt;br /&gt;
[[image:Chws2.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Sniper Camera System HUD ===&lt;br /&gt;
[[Sniper Camera System HUD]] or browse viewtopic for current [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=10461 information]. By [[User:CommonSenseOTB|CommonSenseOTB]] (2011) &amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:SniperCameraSystemv1.1-3.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Steampunk HUD ===&lt;br /&gt;
[[Steampunk HUD]] by [[Killer Wolf]] (2010).&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:Steamhud.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== SW (CAI/DAI) HUD ===&lt;br /&gt;
[[SWHUDDAI]] by [[User:Stranger|Stranger]] (2018-9)&lt;br /&gt;
:Stranger&amp;#039;s World &amp;#039;&amp;#039;Default&amp;#039;&amp;#039; Altimeter HUD for the vanilla game &amp;lt;br /&amp;gt;&lt;br /&gt;
:Stranger&amp;#039;s World &amp;#039;&amp;#039;Customised&amp;#039;&amp;#039; Altimeter HUD for &amp;quot;Stranger&amp;#039;s World&amp;quot; games &amp;lt;br /&amp;gt;&lt;br /&gt;
[[File:SW HUD.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Trek HUD ===&lt;br /&gt;
[[Trek HUD]] by Barabis (2008)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:hud.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Venom Cockpit HUD ===&lt;br /&gt;
[[Isis Interstellar]]&amp;#039;s HUD for their [[Venom]] line of ships.&amp;lt;br&amp;gt;&lt;br /&gt;
Three versions are supplied: standard (as below), mahogany &amp;amp; walnut burr &amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Venomcockpit.jpg|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vimana HUD ===&lt;br /&gt;
[[Vimana HUD]] by Gnievmir (2019)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[File:Vimana Hud info.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vimana-X HUD ===&lt;br /&gt;
[[Vimana HUD]] by [[User:Phkb|Phkb]] (2023)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[File:Vimanax hud.png|600px]]&lt;br /&gt;
&lt;br /&gt;
Modifiable from the [[F4 screen (ship and system interfaces)|Docked F4 Screen]] (Vimana-X Settings)&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wide-Screen HUD ===&lt;br /&gt;
[[Wide-Screen HUD]] by [[User:Wildeblood|Wildeblood]] (2013)&amp;lt;br /&amp;gt;&lt;br /&gt;
[[File:Wide-Screen-HUD.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wolfwood HUD ===&lt;br /&gt;
[http://wiki.alioth.net/images/0/06/Wolfs_variants.zip &amp;#039;&amp;#039;Wolfwood HUD&amp;#039;&amp;#039;] by [[Wolfwood Interstellar Technologies|Wolfwood]] (2006)&amp;lt;br /&amp;gt;&lt;br /&gt;
Note: the image shows an Imperial Cruiser even though at bottom right it says &amp;quot;Cobra Mk III&amp;quot;. Note the Imperial Cruiser has increased energy banks and missiles. But this gives you an idea of what it looks like. &lt;br /&gt;
[[Image:hudwolfwood2.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===Xenon HUD===&lt;br /&gt;
[[Xenon_HUD|Xenon HUD]] by [[User:Phkb|Phkb]] (2015-9)&amp;lt;br/&amp;gt;&lt;br /&gt;
[[Image:XenonHUD_Sample.png|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Yet Another HUD (Plagiarism HUD) ===&lt;br /&gt;
[[Plagiarism HUD|Yet Another HUD]]&lt;br /&gt;
Also known as the Plagiarism HUD, due to shamefully stealing parts from Trek HUD, MilHUD and Killer Wolf&amp;#039;s Dynamic HUD. By Palmski (2010)&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;Condition Critical:&amp;lt;br /&amp;gt;&lt;br /&gt;
[[Image:Yet_another_hud_crit.gif|600px]]&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Z-GrOovY MiLHUD ===&lt;br /&gt;
[[Z-GrOovY MiLHUD]] by Dertien (2013) &amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:Dertien Explanation.png|thumb|left|600px|Yellow condition displayed, showing legend]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Tweaks ==&lt;br /&gt;
&lt;br /&gt;
*Tweak to &amp;#039;dock&amp;#039; an older HUD so that it does not overlap the bottom of the F2-F8 screens while docked [https://bb.oolite.space/viewtopic.php?p=231730#p231730 see here]. By phkb (2014)&lt;br /&gt;
*Tweak to customise a HUD&amp;#039;s altimeter to allow for the [[Strangers World]] gravity wells. See code at the bottom of the first post [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20047 here]. By &amp;#039;&amp;#039;&amp;#039;Stranger&amp;#039;&amp;#039;&amp;#039; (2018)&lt;br /&gt;
*[[How to tweak OXZ&amp;#039;s]]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[HUD]]&lt;br /&gt;
*[[MFD]]&lt;br /&gt;
*[[Guide to HUDs]] compares the features of the various HUDs&lt;br /&gt;
*[[HUDSelector]] - a HUD manager&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=5724 The HUD-shop] (2009-10)&lt;br /&gt;
*[https://iandigaming.blogspot.com/2024/03/oolite-hud-display-showcase.html I and I&amp;#039;s HUD display showcase] (2024)&lt;br /&gt;
&lt;br /&gt;
[[Category:HUDs OXPs| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=CB-HUD_Mark_IV&amp;diff=90339</id>
		<title>CB-HUD Mark IV</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=CB-HUD_Mark_IV&amp;diff=90339"/>
		<updated>2026-09-30T15:15:56Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Tweaks.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A clean, balanced HUD featuring detailed flight instruments, equipment indicators, combat warnings and compact target information. It requires no other OXPs.&lt;br /&gt;
[[File:Cb68-CB-HUD-Mark-IV.jpg|right|900px]]&lt;br /&gt;
==Overview==&lt;br /&gt;
The CB-HUD Mark IV is developed and produced by the [[Crab Boolean Corporation|Crab-Boolean Corporation]] located on [[Sector1/Riredi|Riredi]] in galaxy 1.  &lt;br /&gt;
&lt;br /&gt;
=== Features ===&lt;br /&gt;
A station-aware docking clearance light keeps your docking status visible, while a dedicated docked layout shows the information you need during your station visit.&lt;br /&gt;
&lt;br /&gt;
Compact flight instruments, adaptive energy divisions, absolute shield percentages, speed/altitude/cabin/weapon-temperature readouts, fuel and jump destination, basic/advanced compass and native joystick sensitivity indicator.&lt;br /&gt;
&lt;br /&gt;
Equipment indicators cover docking computer, escape pod, ECM and injectors.&lt;br /&gt;
&lt;br /&gt;
Master alert and rotating Alerts cover equipment damage, maintenance, contraband and legal warnings. Cargo and relevant station information remain visible docked; missile pylons remain visible there even with weapons offline.&lt;br /&gt;
&lt;br /&gt;
Four warning rows left of the crosshair show incoming missiles, forward/aft shield warnings and low/critical energy. Lamps blink; text stays steady.&lt;br /&gt;
&lt;br /&gt;
Four target rows on the right show unique name (if available), type/legal state, distance with Closing/Opening/Steady, and Condition: Good, Weak or Crit.&lt;br /&gt;
&lt;br /&gt;
Both blocks use 10x10 text with a fixed edge facing the crosshair.&lt;br /&gt;
&lt;br /&gt;
*10 [[MFD]]s&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
*The layout is designed for 16:10; other aspect ratios may leave less room for side MFDs.&lt;br /&gt;
&lt;br /&gt;
=== Warning thresholds ===&lt;br /&gt;
*Own shield percentages always use 128 energy points as 100%, regardless of shield upgrades. Weak below 40%, clears at 50%; down at zero, back to weak at 10%.&lt;br /&gt;
*Own energy: low below 25%, clears at 30%; critical below 15%, back to low at 20%.&lt;br /&gt;
*Target condition uses that target&amp;#039;s maximum: Weak below 40%, Good at 45%;&lt;br /&gt;
*Crit below 15%, back to Weak at 20%. Target condition is energy, not OXP shields.&lt;br /&gt;
&lt;br /&gt;
=== Docking light (D) ===&lt;br /&gt;
:Orange: no known clearance. &lt;br /&gt;
::Blinking orange: requested, waiting.&lt;br /&gt;
:Green: clearance granted or this station explicitly requires none.&lt;br /&gt;
::Blinking green: clearance expires soon. The white D and outline stay steady.&lt;br /&gt;
&lt;br /&gt;
The selected station takes priority. Selecting another station does not inherit the first station&amp;#039;s clearance. With no station selected, an active request is retained; otherwise the main station is used while within its [[aegis]].&lt;br /&gt;
&lt;br /&gt;
Green is about clearance, not collision avoidance, traffic or dock size.&lt;br /&gt;
&lt;br /&gt;
=== Optional OXP support ===&lt;br /&gt;
*[[HUDSelector]], Smivs&amp;#039; [[Extra Fuel Tanks]] and [[Shield Equalizer And Capacitors OXP]] are optional.&lt;br /&gt;
*[[CombatMFD]] is &amp;#039;&amp;#039;not&amp;#039;&amp;#039; required; its data sources and other OXP scripts are untouched.&lt;br /&gt;
*[[Shield Cycler]] 1.12 and Shield Cycler Next 2.1/2.1.1 can show their live mode: the upper former Equalized label says Cycler mode:, the lower shows the mode. &amp;quot;Disabled&amp;quot; is shown when switched off. Reduced functionality can still operate.&lt;br /&gt;
:Only install one Cycler branch. Unknown versions/data omit the mode display. The adapter reads the internal state defensively; it never controls shield transfer.&lt;br /&gt;
&lt;br /&gt;
==Minimum requirements==&lt;br /&gt;
*Oolite 1.86+&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
&lt;br /&gt;
=== Monitor Resolution ===&lt;br /&gt;
This HUD works best 16:10. Other resolutions work, but little space may be left for left and right MFD´s.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
Place CB-HUD-Mark-IV-1.0.0.oxz in the normal Oolite AddOns location. Keep only one Mark-IV version active. Mark III may remain installed. Select Mark IV through HUDSelector if it is installed. Without HUDSelector, Mark IV activates automatically. The original Mark III uses the Default HUD entry rather than a separate named entry; another default-HUD replacement can affect that selection. Reload Oolite&amp;#039;s configuration (rebuild its cache when necessary). This package does not install itself.&lt;br /&gt;
=== Compatibility and Testing ===&lt;br /&gt;
Automated tests cover warning thresholds, docking state, text configuration, optional integrations and HUD lifecycle. Standalone startup, HUD selection,&lt;br /&gt;
selection preservation and ship purchase were checked in a simulated Oolite JavaScript environment, also using the unmodified HUDSelector 1.28 package&amp;#039;s script. These checks supplement in-game testing; they do not emulate rendering.&lt;br /&gt;
&lt;br /&gt;
The minimum Oolite version 1.86 is based on a native source/API audit. In-game 1.86 testing and in-game Shield Cycler testing have not been performed. Standard incoming missile events/scan class are supported; unusual script-only missile behaviour may differ.&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
=== Current version ===&lt;br /&gt;
* Version 1.0 [https://app.box.com/s/0fxma53oqutfkjli7zq25kf8hno6gicz oolite.oxp.captain_beatnik.CB-HUD_mark_iv.oxz]&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
*License: CC-BY-NC-SA 4.0&lt;br /&gt;
=== Attribution and Thanks ===&lt;br /&gt;
CB-HUD Mark IV by Captain Beatnik is derived from CB-HUD Mark III and the original configuration files supplied with Oolite.&lt;br /&gt;
&lt;br /&gt;
Many thanks to Giles C Williams (aegidian) and all contributors for developing Oolite.&lt;br /&gt;
&lt;br /&gt;
Thanks to Mazur, Thargoid, Killer Wolf, JeffBTX, Wyvern, Smivs and CommonSenseOTB.&lt;br /&gt;
I learned a great deal by studying their work.&lt;br /&gt;
&lt;br /&gt;
Special thanks to Norby, Phkb, Cag and Neelix. Their work made the additional functions of this HUD possible.&lt;br /&gt;
&lt;br /&gt;
Finally, many thanks to Cholmondely and Maik for their work on the wiki and documentation.&lt;br /&gt;
&lt;br /&gt;
These acknowledgements are also retained in Config/cb68_cbhudIV_main.plist.&lt;br /&gt;
&lt;br /&gt;
=== Development Assistance ===&lt;br /&gt;
OpenAI Codex, an AI coding assistant, assisted with JavaScript, configuration, code review and documentation. The HUD concept, design decisions and in-game testing are by Captain Beatnik.&lt;br /&gt;
&lt;br /&gt;
== The [[Dark Side]] ==&lt;br /&gt;
Everything is drawn using scripts and configuration — there are no additional image files!&lt;br /&gt;
=== Text Customisation ===&lt;br /&gt;
All own visible text, units and templates are in the Config folder&amp;#039;s [[Descriptions.plist]].&lt;br /&gt;
&lt;br /&gt;
Edit quoted values while retaining the namespaced keys and placeholders needed.&lt;br /&gt;
&lt;br /&gt;
Empty strings and leading/trailing spaces are valid; blanking text does not disable warnings, lamps or equipment. Longer translations need visual testing.&lt;br /&gt;
&lt;br /&gt;
Target text has a width limit; type shortening preserves the default bounty Cr suffix. Dock system/station names share a 36-character budget including dots.&lt;br /&gt;
&lt;br /&gt;
=== How the HUD is built ===&lt;br /&gt;
The HUD needs no additional image files or textures. Its layout, instruments, scale marks and crosshairs are defined through JavaScript and the .plist configuration, using Oolite&amp;#039;s built-in drawing functions and font. No Images or Textures folder is included in the package.&lt;br /&gt;
&lt;br /&gt;
Config/cb68_cbhudIV_main.plist has no legends section. All Mark-IV-defined labels and readouts use &amp;lt;tt&amp;gt;drawCustomText&amp;lt;/tt&amp;gt;: dials, with their text supplied from Config/descriptions.plist through the script. Native displays such as the clock and equipment carousel continue to draw their own text.&lt;br /&gt;
&lt;br /&gt;
Oolite draws legends before dials, then processes the dials in their listed order. Placing custom text and scale elements later in that list lets them appear in front of the filled instrument bars. A legend cannot provide that foreground layer over a dial. Scale lines are drawn as narrow custom bars, not as images.&lt;br /&gt;
&lt;br /&gt;
The left-hand shield, energy and weapon-temperature bars fill from right to left. This uses a negative width in the relevant dial definition, for example&lt;br /&gt;
&amp;lt;tt&amp;gt;width = -98;&amp;lt;/tt&amp;gt; for the shield bars. The magnitude specifies the bar width and the negative sign reverses its fill direction. Optional capacitor bars use the same technique. This makes the left and right instrument groups visually mirror one another without needing separate artwork.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*Author: [[User:Captain Beatnik|Captain Beatnik]] (page has links to his other HUDs)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=307272#p307272 BB Release Note for Mark IV] (2026)&lt;br /&gt;
:Feedback is always welcome if something doesn&amp;#039;t work or where something could or should be improved or done differently.&lt;br /&gt;
*[[CB-HUD Mark III]] (2025-6) previous version!&lt;br /&gt;
*[[CB-HUD Mark II]] (2011) popular precursor (includes notes on CB-HUD Mark I).&lt;br /&gt;
*[[HUD]]&lt;br /&gt;
*[[hud.plist]]&lt;br /&gt;
&lt;br /&gt;
{{HUD-OXP}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Crab_Boolean_Corporation&amp;diff=90338</id>
		<title>Crab Boolean Corporation</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Crab_Boolean_Corporation&amp;diff=90338"/>
		<updated>2026-09-30T15:09:50Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added CB-HUD Mark IV&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Crab Boolean Corporation are based on G1 [[Sector1/Riredi|Riredi]]&lt;br /&gt;
[[File:Riredi OXP-nightside (CB&amp;#039;s new texture).jpg|right|thumb|300px|Captain Beatnik&amp;#039;s newest Riredi OXP&amp;#039;s Riredi]]&lt;br /&gt;
== Overview ==&lt;br /&gt;
Crab Boolean (also Crab-Boolean) specialise in HUDs - especially for spaceships. Their [[CB-HUD Mark II]] used to account for 40% of their sales. Their new HUD, the [[CB-HUD Mark III]] was only recently launched to great acclaim.&lt;br /&gt;
&lt;br /&gt;
They have also developed a number of specialised HUDs for the various Coluber ships (often anonymously), as well as a specialised reconstruction of an ancient exploration HUD (see [[Tales from Riredi]] for more on this).&lt;br /&gt;
&lt;br /&gt;
Their offices and laboratories are located at Apex Mons (a gigantic, extinct shield volcano with two other military research facilities on its crater rim, faintly visible at night).&lt;br /&gt;
&lt;br /&gt;
== Gallery ==&lt;br /&gt;
Click on thumbnail to enlarge&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Image:CB-HUD.png  | An early Crab-Boolean HUD&lt;br /&gt;
&lt;br /&gt;
Image:CB-HUD 2011-09-25.jpg | [[CB-HUD Mark II]] - the best seller&lt;br /&gt;
&lt;br /&gt;
Image:CB-HUD 2025-03-29.png | [[CB-HUD Mark III]]&lt;br /&gt;
&lt;br /&gt;
Image:Cb68-CB-HUD-Mark-IV.jpg | [[CB-HUD Mark IV]]&lt;br /&gt;
&lt;br /&gt;
Image:15wo9 coluber hud ch01.png | [[Coluber HUD CH01]]&lt;br /&gt;
&lt;br /&gt;
Image:Crr hud pic 001.png | [[Coluber Red Racer]] HUD&lt;br /&gt;
&lt;br /&gt;
Image:Blueracer hud.png | [[Coluber Blue Racer]] HUD&lt;br /&gt;
&lt;br /&gt;
Image:CYR HUD.png | [[Coluber Blue Racer|Coluber Yellowbelly Racer]] HUD&lt;br /&gt;
&lt;br /&gt;
Image:CBL HUD.png | [[Coluber Blue Racer|Coluber Black Racer]] HUD&lt;br /&gt;
&lt;br /&gt;
Image:Pitviper2 HUD.png| [[Coluber Pitviper]] HUD&lt;br /&gt;
&lt;br /&gt;
Image:CB&amp;#039;s SOTL HUD (Spectroscopic).png | Reconstruction of an [[SOTL Exploration|ancient exploration HUD]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Tales from Riredi]] - short story focused on the Crab Boolean Corporation&lt;br /&gt;
*[[Riredi OXP]] - the newest version of this has the planet texture where the offices are located&lt;br /&gt;
*[[User:Captain Beatnik|Captain Beatnik]] - fons et origo of all this lore (and of the OXPs!).&lt;br /&gt;
&lt;br /&gt;
[[Category:Fictional organisations]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Guide_to_HUDs&amp;diff=90337</id>
		<title>Guide to HUDs</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Guide_to_HUDs&amp;diff=90337"/>
		<updated>2026-09-30T15:04:27Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added CB-HUD Mark IV&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Viewscreen sample.png|thumb|right|300px|The Vanilla game HUD]]&lt;br /&gt;
== Considerations for choosing a HUD ==&lt;br /&gt;
The most sophisticated HUDs &amp;#039;&amp;#039;seem&amp;#039;&amp;#039; to be CB-HUD Mark III, Dangerous HUD, Vimana, Vimana-X, Xenon &amp;amp; Z-GrOovY MiLHUD‎.&lt;br /&gt;
&lt;br /&gt;
=== Clutter ===&lt;br /&gt;
Do you want a good view of everything in space around you? Or do you want lots of dials/MFDs giving you information about the space around you?&lt;br /&gt;
&lt;br /&gt;
=== Viewscreens vs Windows, Consoles ===&lt;br /&gt;
Do you envisage yourself as looking out a window with a HUD projected onto it? Or as gazing at a viewscreen? &amp;lt;br&amp;gt;&lt;br /&gt;
And do you want to see a control console in front of you?&lt;br /&gt;
&lt;br /&gt;
If you prefer windows, the Dangerous HUD is the most extreme example.&lt;br /&gt;
If you prefer viewscreens, try the Plagiarism HUD.&lt;br /&gt;
&lt;br /&gt;
Consoles are available from the Deepspace HUD, Deeper Space HUD, Fighter HUD, Isis HUD, MegaWalnut Dash, NovaLux, Steampunk, Trek, Venom, Plagiarism &amp;amp; Z-GrOovY MiLHUD. See [[HUD images here]] for more information.&lt;br /&gt;
&lt;br /&gt;
=== Size ===&lt;br /&gt;
There are two considerations here.&lt;br /&gt;
:1) The size of your ship. Oolite defines a smaller HUD for a small ship such as an [[adder]], but only a handful of HUD OXPs include these small sizes.&lt;br /&gt;
:2) The size of your monitor. Some HUDs allow for a rather larger computer screen.&lt;br /&gt;
&lt;br /&gt;
=== Large Scanners ===&lt;br /&gt;
Do you want a large scanner? See [[HUD images here]] for options.&lt;br /&gt;
&lt;br /&gt;
=== Cheating ===&lt;br /&gt;
Do you think that the HUD is a cheat? Gnievmir&amp;#039;s original Vimana HUD also improves your ship (adds speed, energy, missile slots &amp;amp; cargo capacity, and allows purchase of a super-laser), Deeperspace HUD warns about danger based on the ratio of pirates/Thargoids to police in the entire solar system.&lt;br /&gt;
&lt;br /&gt;
== HUDs ==&lt;br /&gt;
The following table is optimized for a horizontal screen resolution of at least 1280px so that all OXP descriptions fit on one line.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- The &amp;quot;Z&amp;quot; column indicates that an OXZ version is available in the [http://www.oolite.org/oxps/ OXZ list] and downloadable within the [[Expansions Manager|Expansion Pack Manager]] in Oolite. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- KEEP DESCRIPTIONS (desc=...) ALPHABETICAL --&amp;gt;&lt;br /&gt;
&amp;lt;!-- KEEP LENGTHS OF DESCRIPTIONS TO THAT OF EXISTING ENTRIES OR LESS --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Guide to HUDs TableHeader}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Aad-HUD]] enhances and rearranges the default HUD&lt;br /&gt;
|date=2015-05-03&lt;br /&gt;
|aut=[[User:Spara|Spara]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=4&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=2 versions (small ships, widescreen)&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=9462 Another HUD] is based on Killer Wolf&amp;#039;s Generic HUD&lt;br /&gt;
|date=2011-03-18&lt;br /&gt;
|aut=NorthenderPNE&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[CB-HUD Mark IV]]  is a fully featured HUD, displaying numeric values, equipment lights and some additional gauges &lt;br /&gt;
|date=2026-09-25&lt;br /&gt;
|aut=[[User:Captain Beatnik|Captain Beatnik]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=10&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Extra gauges, Docking light&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[CB-HUD Mark III]]  is a fully featured HUD and uses data from [[CombatMFD]] to display numeric values and some additional gauges &lt;br /&gt;
|date=2025-03-30&lt;br /&gt;
|aut=[[User:Captain Beatnik|Captain Beatnik]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=Y&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=10&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Extra gauges&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[CB-HUD Mark II]] features a HUD that changes based on installed equipment. See the [https://bb.oolite.space/viewtopic.php?p=141035#p141035 BB post] for more information&lt;br /&gt;
|date=2011-09-25&lt;br /&gt;
|aut=[[User:Captain Beatnik|Captain Beatnik]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Equipment icons, large scanner.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[ChupacabraHUD]] has central curved bar gauges, custom missile displays and shield capacitor gauges&lt;br /&gt;
|date=2011-10-26&lt;br /&gt;
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Missile identifier, Curved Bar Gauges&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[ClearHUD]] is a minimalist HUD suitable for playing on large, wide screens&lt;br /&gt;
|date=2012-09-15&lt;br /&gt;
|aut=Tichy&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Widescreens &amp;#039;&amp;#039;only&amp;#039;&amp;#039;. Docked HUD. &amp;lt;br&amp;gt;Sniper-sight addon.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Coluber HUD CH01|Coluber HUD CH01]] A fully featured HUD with individual scales for each gauge and additional control lights for important equipment.&lt;br /&gt;
|date=2014-09-15&lt;br /&gt;
|aut=[[User:Captain Beatnik|Captain Beatnik]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=7&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Equipment lights, large scanner.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[CombatHUD|Combat HUD]] A stylish, logically arranged HUD designed to give clear information during combat.&lt;br /&gt;
|date=2013-01-24&lt;br /&gt;
|aut=[[User:Smivs|Smivs]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Can take 8 energy banks &amp;amp; 16 pylons. &amp;lt;br&amp;gt;Widescreen version.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[CompactHUD|Compact HUD]] provides an alternative HUD with a clean look&lt;br /&gt;
|date=2010-10-17&lt;br /&gt;
|aut=[[User:Aegidian|Aegidian]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=For small ships only&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Coluber_Red_Racer#Coluber_Red_Racer_.28CRR.29_HUD|CRR-HUD BB]] is the stand-alone version of the Coluber Red Racer HUD&lt;br /&gt;
|date=2012-01-19&lt;br /&gt;
|aut=[[User:Captain Beatnik|Captain Beatnik]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Equipment lights&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Cyan HUD]] Big scanner &amp;amp; partially &amp;lt;br&amp;gt;numeric dials around crosshairs.&lt;br /&gt;
|date=2014-07-17&lt;br /&gt;
|aut=[[User:Zireael|Zireael]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=16&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Large scanner&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Dangerous HUD]]&lt;br /&gt;
|date=2018-08-12&lt;br /&gt;
|aut=[[User:gsagostinho|GSAgostinho]]&lt;br /&gt;
|biggui=Y&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=7&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=3 versions, sounds, pulsating scanner&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Deeper Space HUD]]&lt;br /&gt;
|date=2018-04-22&lt;br /&gt;
|aut=Pleiadian&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Current Risk notifier, Equipment lights, &amp;lt;br&amp;gt;Navigation data&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Deepspace Ships#Deepspace HUDs|Deepspace HUD]] is an alternative HUD with two versions&lt;br /&gt;
|date=2010-02-14&lt;br /&gt;
|aut=DeepSpace&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Deepspace HUD OXP, Deepspace Retro HUD OXP.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Dr HUD OXP|Dr HUD]] is an alternative HUD&lt;br /&gt;
|date=2006-12-22&lt;br /&gt;
|aut=[[User:Dr. Nil|Dr. Nil]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Old HUD - no extras&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[HUDSelector|ExtraLarge HUD]]&lt;br /&gt;
|date=2028-03-28&lt;br /&gt;
|aut=[[User:Norby|Norby]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=Y&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=10&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Extra dials, large scanner, small ship HUD.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Fighter HUD (Oolite)|Fighter HUD]] is an alternative HUD&lt;br /&gt;
|date=2008-05-21&lt;br /&gt;
|aut=[[User:CaptKev|CaptKev]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=4&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Polarized glass laser sight&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[G-HUD]] adds an alternative HUD&lt;br /&gt;
|date=2008-07-08&lt;br /&gt;
|aut=[[User:Gunney Plym|Gunney Plym]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Old HUD - no extras&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[GETter_HUD_OXZ|GETter HUD]]&lt;br /&gt;
|date=2022-12-18&lt;br /&gt;
|aut=[[User:Reval|Reval]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Lists hold contents&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Isis HUD]]&lt;br /&gt;
|date=2022&lt;br /&gt;
|aut=[[Killer Wolf]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Immersive Docked HUDs&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[KeeperHUD|Keeper HUD]]&lt;br /&gt;
|date=2016-08-14&lt;br /&gt;
|aut=[[Keeper]]&lt;br /&gt;
|biggui=Y&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=15&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=opacity varies with need, docked HUD.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Killer_Wolf&amp;#039;s_Dynamic_HUD|Killer Wolf&amp;#039;s Dynamic HUD]] adds a version of the dynamic HUD first seen in Killer Wolf&amp;#039;s Werewolf ships, to all ships&lt;br /&gt;
|date=2010-07-08&lt;br /&gt;
|aut=[[Killer Wolf]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Special damaged version, immersive docked HUDs&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Klepto-HUD OXP|Klepto-HUD]] is a different &amp;#039;take&amp;#039; on a HUD with precise crosshairs&lt;br /&gt;
|date=2006-03-09&lt;br /&gt;
|aut=Kleptoid&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Very compact HUD&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[HUDSelector|Large HUD]]&lt;br /&gt;
|date=2028-03-28&lt;br /&gt;
|aut=[[User:Norby|Norby]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=Y&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=10&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Extra dials, large scanner.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip Medusa HUD] is an alternative HUD&lt;br /&gt;
|date=2009-01-18&lt;br /&gt;
|aut=[[User:ClymAngus|ClymAngus]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Old HUD - no extras&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Mega-Walnut Dashboard OXP|Mega-Walnut Dashboard]] is an elderly version of the fabled Fer de Lance HUD&lt;br /&gt;
|date=2005-07-05&lt;br /&gt;
|aut=[[User:Aegidian|Aegidian]]&lt;br /&gt;
|biggui=&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Old HUD - no extras&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[MilHUD 4000]] is a fork of Milspec HUD with updated script and new features&lt;br /&gt;
|date=2013-03-05&lt;br /&gt;
|aut=[[User:Wildeblood|Wildeblood]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=variable brightness/contrast centre patch, Sniper Sight, etc.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Milspec HUD]] is an alternative HUD with targeting aids and an emphasis on functionality&lt;br /&gt;
|date=2011-12-16&lt;br /&gt;
|aut=[[User:Wyvern|Cdr. Wyvern]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Sniper sight, docked HUD.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip NG HUD] is an alternate HUD with a personal view&lt;br /&gt;
|date=2005-03-06&lt;br /&gt;
|aut=alien&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Old HUD - no extras&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Nova Lux HUD]]&lt;br /&gt;
|date=2023-08-23&lt;br /&gt;
|aut=[[User:Vincentz|Vincentz]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=6&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Small ship HUD, Widescreen HUD.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Numeric_Style_HUDs|Numeric Style HUDs]] numeric gauges, now version 3.&lt;br /&gt;
|date=2015-01-10&lt;br /&gt;
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=8&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Unneeded dials fade out, Widescreen HUD.&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[OrangED HUD]] Big scanner, partially numeric dials and more!&lt;br /&gt;
|date=2014-07-17&lt;br /&gt;
|aut=[[User:Zireael|Zireael]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=4&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Pie_Chart_Style_HUDs|Pie Chart Style HUDs]] New invention! Pie-chart gauges.&lt;br /&gt;
|date=2011-05-20&lt;br /&gt;
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[HUDSelector|Small HUD]] for small ships&lt;br /&gt;
|date=2028-03-28&lt;br /&gt;
|aut=[[User:Norby|Norby]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=10&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[SmartHUD|SmartHUD]] &lt;br /&gt;
|date=2023-08-23&lt;br /&gt;
|aut=[[User:smivs|smivs]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Widescreen, immersive messages&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[SWHUDDAI|SW HUD CAI]] a modernised [[CB-HUD_Mark_II|CB HUD]] with customised SW altimeter&lt;br /&gt;
|date=2019-02-23&lt;br /&gt;
|aut=[[User:Stranger|Stranger]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Altimeter designed for Stranger&amp;#039;s World, Tweaked Scanner&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[SWHUDDAI|SW HUD DAI]] a modernised [[CB-HUD_Mark_II|CB HUD]] with default vanilla game altimeter&lt;br /&gt;
|date=2019-02-23&lt;br /&gt;
|aut=[[User:Stranger|Stranger]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=2&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Tweaked scanner&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Steampunk HUD]]&lt;br /&gt;
|date=2019-02-23&lt;br /&gt;
|aut=[[Killer Wolf]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Old HUD, immersive Docked HUD&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Trek HUD]]Star Trek NG LCARS-style (Library Computer Access &amp;amp; Retrieval System) HUD.&lt;br /&gt;
|date=2008-11-11&lt;br /&gt;
|aut=Barabis&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Old HUD - no extras&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Vimana HUD]] a complex HUD with many warnings and also lights for much additional equipment&lt;br /&gt;
|date=2019-09-12&lt;br /&gt;
|aut=[[Gnievmir]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=Y&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=6/12&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Too much to fit in here!&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Vimana-X HUD]] a full-spectrum update to Vimana HUD, with lots of additional features.&lt;br /&gt;
|date=2025-12-29&lt;br /&gt;
|aut=[[User:Phkb|phkb]]&lt;br /&gt;
|con=Gnievmir&lt;br /&gt;
|biggui=Y&lt;br /&gt;
|hull=Y&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=6/10/12&lt;br /&gt;
|speed=Y&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Far too much to fit in here!&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Wide-Screen HUD]] is the first Oolite HUD designed specifically for wide screens with 8:5 and 16:9 aspect ratios.&lt;br /&gt;
|date=2013-05-15&lt;br /&gt;
|aut=[[User:Wildeblood|Wildeblood]]&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Jump stability monitor, Target Radar, &amp;lt;br&amp;gt;gravimeter &amp;amp; transponder. Tweaks for &amp;lt;br&amp;gt;Police IFF Scanner, &amp;quot;fading&amp;quot; clock &lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Xenon_HUD|Xenon HUD]] groups important gauges around the crosshairs - and uses custom crosshair images.&lt;br /&gt;
|date=2018-08-19&lt;br /&gt;
|aut=[[User:Phkb|phkb]]&lt;br /&gt;
|biggui=Y&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=9&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=Y&lt;br /&gt;
|joystick=N&lt;br /&gt;
|hud_selector=Y&lt;br /&gt;
|extras=Hi-contrast mode,&amp;lt;br&amp;gt;amber or cyan colors&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=Yet Another HUD aka [[Plagiarism HUD]]&lt;br /&gt;
|date=2010-08-26&lt;br /&gt;
|aut=Palmski&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=N&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Special damaged version&lt;br /&gt;
}}&lt;br /&gt;
{{HUDSortableTableRow&lt;br /&gt;
|desc=[[Z-GrOovY_MiLHUD|Z-GrOovY MilHUD]]&lt;br /&gt;
|date=2013-12-27&lt;br /&gt;
|aut=Dertien&lt;br /&gt;
|biggui=N&lt;br /&gt;
|hull=N&lt;br /&gt;
|reticle=Y&lt;br /&gt;
|mfds=0&lt;br /&gt;
|speed=N&lt;br /&gt;
|distance=N&lt;br /&gt;
|joystick=Y&lt;br /&gt;
|hud_selector=N&lt;br /&gt;
|extras=Many equipment lights, special damaged version&lt;br /&gt;
}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Appendices ==&lt;br /&gt;
=== Key to Table ===&lt;br /&gt;
 Aut          OXP Author&lt;br /&gt;
               [[File:Oolite-gov-multigov.png|10px]] indicates one or more &amp;#039;&amp;#039;additional&amp;#039;&amp;#039; authors of the .oxp&amp;lt;br&amp;gt;&lt;br /&gt;
 Date         Date of latest version of OX - this helps date the generation of the HUD&lt;br /&gt;
               2010 - Dynamic HUDs appear, switching between Green, Yellow, Red Alert and docked HUDs&lt;br /&gt;
               2014 - MFDs appear&lt;br /&gt;
                    - HUD Selector published (breaking automatic link with HUD inside a ship.oxp)&lt;br /&gt;
 Big GUI      This allows more information to appear on mission screens or Docked screens (&amp;quot;GUIs&amp;quot;)&lt;br /&gt;
 Hull         The state of the ship (how urgent is [[maintenance]]?)&lt;br /&gt;
 Reticle      A targeting reticle showing when you are on target? (usually needs the purchase of an [[STE]])&lt;br /&gt;
 MFDs         How many MFDs does the HUD support?&lt;br /&gt;
 Speed        Is the speed also given numerically?&lt;br /&gt;
 Distance     Is the distance to the [[Compass]] target given numerically?&lt;br /&gt;
 Joystick     Is there an indicator for [[Oolite_Tactics#Precision_Flying|precision flying]] with a joystick/controller?&lt;br /&gt;
 HUD Selector Is this OXP compatible with the [[HUD Selector]] OXP?&lt;br /&gt;
&lt;br /&gt;
=== List of HUDs ===&lt;br /&gt;
*1 Aad HUD&lt;br /&gt;
*2 Another HUD&lt;br /&gt;
*3 CB-HUD Mark II&lt;br /&gt;
*4 CB-HUD Mark III&lt;br /&gt;
*5 ChupacabraHUD&lt;br /&gt;
*6 Coluber HUD CH01&lt;br /&gt;
*7 CombatHUD&lt;br /&gt;
*8 Compact HUD&lt;br /&gt;
*9 CRR-HUD&lt;br /&gt;
*10 Dangerous HUD&lt;br /&gt;
*11 DeeperSpace HUD&lt;br /&gt;
*12 Deepspace HUD&lt;br /&gt;
*13 Deepspace Retro HUD&lt;br /&gt;
*14 Dr HUD&lt;br /&gt;
*15 ExtraLarge HUD&lt;br /&gt;
*16 Fighter HUD&lt;br /&gt;
*17 G-HUD&lt;br /&gt;
*18 Isis HUD&lt;br /&gt;
*19 KeeperHUD&lt;br /&gt;
*20 Klepto HUD&lt;br /&gt;
*21 Large HUD&lt;br /&gt;
*22 Medusa HUD&lt;br /&gt;
*23 Mega Walnut Dash HUD&lt;br /&gt;
*24 MilHUD 4000&lt;br /&gt;
*25 MilHUD (Military Specification HUD)&lt;br /&gt;
*26 MillHUD Refit&lt;br /&gt;
*27 Mod HUD&lt;br /&gt;
*28 Nova Lux HUD&lt;br /&gt;
*29 Numeric Style HUDs&lt;br /&gt;
*30 OrangED HUD&lt;br /&gt;
*31 Pie Chart Style HUDs&lt;br /&gt;
*32 Small HUD&lt;br /&gt;
*33 Smart HUD&lt;br /&gt;
*35 Sniper Camera System HUD&lt;br /&gt;
*36 Steampunk HUD&lt;br /&gt;
*37 SW (CAI/DAI) HUD&lt;br /&gt;
*38 Trek HUD&lt;br /&gt;
*39 Venom Cockpit HUD&lt;br /&gt;
*40 Vimana HUD&lt;br /&gt;
*41 Vimana-X HUD&lt;br /&gt;
*42 Wide-Screen HUD&lt;br /&gt;
*43 Wolfwood HUD&lt;br /&gt;
*44 Xenon HUD&lt;br /&gt;
*45 Yet Another HUD&lt;br /&gt;
*46 Z-GrOovY MiLHUD&lt;br /&gt;
&lt;br /&gt;
== Considerations/Still to sort out for this wiki page ==&lt;br /&gt;
*Date (and explanation of importance re Vanilla Game Code development &amp;lt;-&amp;gt; HUD development)&lt;br /&gt;
*Different HUDs for different green/yellow/red conditions/alerts? / Range of alerts shown / Docked HUD?&lt;br /&gt;
*Cargo Hold indicator?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Extras? (&amp;#039;&amp;#039;eg&amp;#039;&amp;#039; Vimana HUD&amp;#039;s cornucopia of goodies, DeeperSpace&amp;#039;s Risk Assessment, Xenon HUD&amp;#039;s sights, Dangerous HUD&amp;#039;s noises).&lt;br /&gt;
:Current Location Display &amp;amp; Current Risk Notifier (Deeper Space HUD)&lt;br /&gt;
:Weapons Bay Missile identifier? (ChupacabraHUD)&lt;br /&gt;
:Extra reticles for other lasers (Xenon)&lt;br /&gt;
:Glare filter? / Glare contrast? (for reading HUD in Glare - cf Xenon HUD)&lt;br /&gt;
:Explicit warnings: missile approach/temp/altitude/shields/energy banks?&lt;br /&gt;
:Equipment Lights?&lt;br /&gt;
::Vanilla Optional Equipment lights?&lt;br /&gt;
::OXP Equipment lights?&lt;br /&gt;
:Customisation: &lt;br /&gt;
::Choice of Colours? (Dangerous HUD &amp;amp; Xenon HUD)&lt;br /&gt;
::Choice of Cockpits? (Dangerous HUD)&lt;br /&gt;
::Natural materials? (Mega Walnut Dash)&lt;br /&gt;
::Large screen variant? &lt;br /&gt;
::Large Scanner? - see image!&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[HUD images here]]&lt;br /&gt;
=== Faffing about with HUDs ===&lt;br /&gt;
*[[Hud.plist]] - has many more links at the bottom of the page&lt;br /&gt;
*[[HUD Customisation Guide]]&lt;br /&gt;
*[[Fully Annotated HUD Configuration (hud.plist) File‎]]&lt;br /&gt;
*[[Oolite Custom HUD Dials]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]] [[Category:HUDs OXPs| ]] [[Category:Factual]] [[Category:OXP Lists]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=User:Captain_Beatnik&amp;diff=90336</id>
		<title>User:Captain Beatnik</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=User:Captain_Beatnik&amp;diff=90336"/>
		<updated>2026-09-30T14:57:42Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added CB-HUD Mark IV, tweaks&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Pitviper 250x167 001.png|250px|thumb|right|Pitviper]]&lt;br /&gt;
[[File:CB-HUD 2025-03-29.png|250px|thumb|right|CB-HUD Mark III with 10 MFDs]]&lt;br /&gt;
[[File:15wo9 coluber hud ch01.png|250px|thumb|right|CH01 HUD with 7 MFD&amp;#039;s]]&lt;br /&gt;
[[File:Beatniks shipset pic 002.png|250px|thumb|right|Cobra Mk3 with new HUD]]&lt;br /&gt;
[[File:Riredi sodalite orbital station.png|250px|thumb|right|Riredi OXP]]&lt;br /&gt;
&lt;br /&gt;
Robert Triflinger from Bavaria.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;Responsible for the CB and Coluber OXPs.&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The HUDs are very striking - and not surprisingly, have inspired others to take them and tweak away with abandon!&lt;br /&gt;
&lt;br /&gt;
Riredi OXP is quite beautiful. The station is gorgeous and a wonderfully unique oddity! Both his HUDs and the Pitvipers proved very popular when they debuted back around 2012.&lt;br /&gt;
&lt;br /&gt;
== OXPs ==&lt;br /&gt;
Captain Beatnik&amp;#039;s OXPs include:&lt;br /&gt;
=== HUDs ===&lt;br /&gt;
*[[CB-HUD Mark IV]] - a 2026 HUD with extra dials which does not need the [[Combat MFD]]&lt;br /&gt;
*[[CB-HUD Mark III]] - a 2025 HUD incorporating extra dials from the [[Combat MFD]]&lt;br /&gt;
*[[CB-HUD Mark II‎]] - the number one HUD produced by the Crab-Boolean Corporation&lt;br /&gt;
*[[Coluber HUD CH01]] - the number one HUD produced by Coluber Inc.&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18335 (Release) Coluber HUD CH02] - a 2016 update by Nomad&lt;br /&gt;
::[[SWHUDDAI|SW HUD]] - a 2019 update of Coluber HUD CH01 by [[User:Stranger|Stranger]]&lt;br /&gt;
*[[HUD_images_here#CRR-HUD|CRR-HUD]] - for the Coluber Red Racer&lt;br /&gt;
*Other HUDs exist for the other Coluber racers, the Pitviper and his standalone Cobra Mk III&lt;br /&gt;
&lt;br /&gt;
=== Ships ===&lt;br /&gt;
*[[Coluber Blue Racer|Coluber Racers]] Blue, Red, Yellowbelly and Black - each with their own HUD&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=11206 (UPDATED RELEASE) Coluber ships] 20/11/2011, but last updated 28/10/2013&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12928 (UPDATED RELEASE) Coluber CRR-5375 Red Racer heavy fighter] 11/11/2012&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12725 (Release) Coluber Yellowbelly racer] 23/10/2012&lt;br /&gt;
*[[Coluber Pitviper]]&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12526 (RELEASE) Coluber CPV-9333 Pitviper] 15/9/2012&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=15069 (RELEASE) Coluber CPV-12375 Pitviper Mk. II] 27/7/2013&lt;br /&gt;
*Cobra Mk3&lt;br /&gt;
::[[Beatnik&amp;#039;s Cobra]] 11/4/2012 - New texture with new HUD&lt;br /&gt;
&lt;br /&gt;
=== System ===&lt;br /&gt;
*[[Riredi OXP]] remodels the system of Riredi in the first galaxy with a customised planet texture, orbital station and station defenders.&lt;br /&gt;
:Phkb&amp;#039;s 2024 update adds a [[New Cargoes]] commodity and updated retextures (including city night-lights) and planet landing sites for [[Planetfall2 OXP|PlanetFall2]].&lt;br /&gt;
&lt;br /&gt;
CB&amp;#039;s fiction also adds lore to Atriso &amp;amp; Aronar.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Fiction ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=21659 Nothing but trouble, annoyance and losses] (2024) - Felines living at Riredi&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=21666 6 + 9 = 13] (2024) - Fulfilling a contract for Riredesic on Riredi&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=21660 Been on a short trip to Aronar] (2024)&lt;br /&gt;
&lt;br /&gt;
[[Category:OXP authors]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=CB-HUD_Mark_IV&amp;diff=90335</id>
		<title>CB-HUD Mark IV</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=CB-HUD_Mark_IV&amp;diff=90335"/>
		<updated>2026-09-30T14:53:25Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Page created&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The CB-HUD Mark IV is a fully featured HUD requiring no other OXPs.&lt;br /&gt;
[[File:Cb68-CB-HUD-Mark-IV.jpg|right|900px]]&lt;br /&gt;
==Overview==&lt;br /&gt;
The CB-HUD Mark IV is developed and produced by the [[Crab Boolean Corporation|Crab-Boolean Corporation]] located on [[Sector1/Riredi|Riredi]] in galaxy 1.  &lt;br /&gt;
&lt;br /&gt;
=== Features ===&lt;br /&gt;
Compact flight instruments, adaptive energy divisions, absolute shield percentages, speed/altitude/cabin/weapon-temperature readouts, fuel and jump destination, basic/advanced compass and native joystick sensitivity indicator.&lt;br /&gt;
&lt;br /&gt;
Equipment indicators cover docking computer, escape pod, ECM and injectors.&lt;br /&gt;
&lt;br /&gt;
Master alert and rotating Alerts cover equipment damage, maintenance, contraband and legal warnings. Cargo and relevant station information remain visible docked; missile pylons remain visible there even with weapons offline.&lt;br /&gt;
&lt;br /&gt;
Four warning rows left of the crosshair show incoming missiles, forward/aft shield warnings and low/critical energy. Lamps blink; text stays steady.&lt;br /&gt;
&lt;br /&gt;
Four target rows on the right show unique name (if available), type/legal state, distance with Closing/Opening/Steady, and Condition: Good, Weak or Crit.&lt;br /&gt;
&lt;br /&gt;
Both blocks use 10x10 text with a fixed edge facing the crosshair.&lt;br /&gt;
&lt;br /&gt;
*10 [[MFD]]s&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
*The layout is designed for 16:10; other aspect ratios may leave less room for side MFDs.&lt;br /&gt;
&lt;br /&gt;
=== Warning thresholds ===&lt;br /&gt;
*Own shield percentages always use 128 energy points as 100%, regardless of shield upgrades. Weak below 40%, clears at 50%; down at zero, back to weak at 10%.&lt;br /&gt;
*Own energy: low below 25%, clears at 30%; critical below 15%, back to low at 20%.&lt;br /&gt;
*Target condition uses that target&amp;#039;s maximum: Weak below 40%, Good at 45%;&lt;br /&gt;
*Crit below 15%, back to Weak at 20%. Target condition is energy, not OXP shields.&lt;br /&gt;
&lt;br /&gt;
=== Docking light (D) ===&lt;br /&gt;
:Orange: no known clearance. &lt;br /&gt;
::Blinking orange: requested, waiting.&lt;br /&gt;
:Green: clearance granted or this station explicitly requires none.&lt;br /&gt;
::Blinking green: clearance expires soon. The white D and outline stay steady.&lt;br /&gt;
&lt;br /&gt;
The selected station takes priority. Selecting another station does not inherit the first station&amp;#039;s clearance. With no station selected, an active request is retained; otherwise the main station is used while within its [[aegis]].&lt;br /&gt;
&lt;br /&gt;
Green is about clearance, not collision avoidance, traffic or dock size.&lt;br /&gt;
&lt;br /&gt;
=== Optional OXP support ===&lt;br /&gt;
*[[HUDSelector]], Smivs&amp;#039; [[Extra Fuel Tanks]] and [[Shield Equalizer And Capacitors OXP]] are optional.&lt;br /&gt;
*[[CombatMFD]] is &amp;#039;&amp;#039;not&amp;#039;&amp;#039; required; its data sources and other OXP scripts are untouched.&lt;br /&gt;
*[[Shield Cycler]] 1.12 and Shield Cycler Next 2.1/2.1.1 can show their live mode: the upper former Equalized label says Cycler mode:, the lower shows the mode. &amp;quot;Disabled&amp;quot; is shown when switched off. Reduced functionality can still operate.&lt;br /&gt;
:Only install one Cycler branch. Unknown versions/data omit the mode display. The adapter reads the internal state defensively; it never controls shield transfer.&lt;br /&gt;
&lt;br /&gt;
==Minimum requirements==&lt;br /&gt;
*Oolite 1.86+&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
&lt;br /&gt;
=== Monitor Resolution ===&lt;br /&gt;
This HUD works best 16:10. Other resolutions work, but little space may be left for left and right MFD´s.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
Place CB-HUD-Mark-IV-1.0.0.oxz in the normal Oolite AddOns location. Keep only one Mark-IV version active. Mark III may remain installed. Select Mark IV through HUDSelector if it is installed. Without HUDSelector, Mark IV activates automatically. The original Mark III uses the Default HUD entry rather than a separate named entry; another default-HUD replacement can affect that selection. Reload Oolite&amp;#039;s configuration (rebuild its cache when necessary). This package does not install itself.&lt;br /&gt;
=== Compatibility and Testing ===&lt;br /&gt;
Automated tests cover warning thresholds, docking state, text configuration, optional integrations and HUD lifecycle. Standalone startup, HUD selection,&lt;br /&gt;
selection preservation and ship purchase were checked in a simulated Oolite JavaScript environment, also using the unmodified HUDSelector 1.28 package&amp;#039;s script. These checks supplement in-game testing; they do not emulate rendering.&lt;br /&gt;
&lt;br /&gt;
The minimum Oolite version 1.86 is based on a native source/API audit. In-game 1.86 testing and in-game Shield Cycler testing have not been performed. Standard incoming missile events/scan class are supported; unusual script-only missile behaviour may differ.&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
=== Current version ===&lt;br /&gt;
* Version 1.0 [https://app.box.com/s/0fxma53oqutfkjli7zq25kf8hno6gicz oolite.oxp.captain_beatnik.CB-HUD_mark_iv.oxz]&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
*License: CC-BY-NC-SA 4.0&lt;br /&gt;
=== Attribution and Thanks ===&lt;br /&gt;
CB-HUD Mark IV by Captain Beatnik is derived from CB-HUD Mark III and the original configuration files supplied with Oolite.&lt;br /&gt;
&lt;br /&gt;
Many thanks to Giles C Williams (aegidian) and all contributors for developing Oolite.&lt;br /&gt;
&lt;br /&gt;
Thanks to Mazur, Thargoid, Killer Wolf, JeffBTX, Wyvern, Smivs and CommonSenseOTB.&lt;br /&gt;
I learned a great deal by studying their work.&lt;br /&gt;
&lt;br /&gt;
Special thanks to Norby, Phkb, Cag and Neelix. Their work made the additional functions of this HUD possible.&lt;br /&gt;
&lt;br /&gt;
Finally, many thanks to Cholmondely and Maik for their work on the wiki and documentation.&lt;br /&gt;
&lt;br /&gt;
These acknowledgements are also retained in Config/cb68_cbhudIV_main.plist.&lt;br /&gt;
&lt;br /&gt;
=== Development Assistance ===&lt;br /&gt;
OpenAI Codex, an AI coding assistant, assisted with JavaScript, configuration, code review and documentation. The HUD concept, design decisions and in-game testing are by Captain Beatnik.&lt;br /&gt;
&lt;br /&gt;
== The [[Dark Side]] ==&lt;br /&gt;
=== Text Customisation ===&lt;br /&gt;
All own visible text, units and templates are in the Config folder&amp;#039;s [[Descriptions.plist]].&lt;br /&gt;
&lt;br /&gt;
Edit quoted values while retaining the namespaced keys and placeholders needed.&lt;br /&gt;
&lt;br /&gt;
Empty strings and leading/trailing spaces are valid; blanking text does not disable warnings, lamps or equipment. Longer translations need visual testing.&lt;br /&gt;
&lt;br /&gt;
Target text has a width limit; type shortening preserves the default bounty Cr suffix. Dock system/station names share a 36-character budget including dots.&lt;br /&gt;
&lt;br /&gt;
=== How the HUD is built ===&lt;br /&gt;
The HUD needs no additional image files or textures. Its layout, instruments, scale marks and crosshairs are defined through JavaScript and the .plist configuration, using Oolite&amp;#039;s built-in drawing functions and font. No Images or Textures folder is included in the package.&lt;br /&gt;
&lt;br /&gt;
Config/cb68_cbhudIV_main.plist has no legends section. All Mark-IV-defined labels and readouts use &amp;lt;tt&amp;gt;drawCustomText&amp;lt;/tt&amp;gt;: dials, with their text supplied from Config/descriptions.plist through the script. Native displays such as the clock and equipment carousel continue to draw their own text.&lt;br /&gt;
&lt;br /&gt;
Oolite draws legends before dials, then processes the dials in their listed order. Placing custom text and scale elements later in that list lets them appear in front of the filled instrument bars. A legend cannot provide that foreground layer over a dial. Scale lines are drawn as narrow custom bars, not as images.&lt;br /&gt;
&lt;br /&gt;
The left-hand shield, energy and weapon-temperature bars fill from right to left. This uses a negative width in the relevant dial definition, for example&lt;br /&gt;
&amp;lt;tt&amp;gt;width = -98;&amp;lt;/tt&amp;gt; for the shield bars. The magnitude specifies the bar width and the negative sign reverses its fill direction. Optional capacitor bars use the same technique. This makes the left and right instrument groups visually mirror one another without needing separate artwork.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*Author: [[User:Captain Beatnik|Captain Beatnik]] (page has links to his other HUDs)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=307272#p307272 BB Release Note for Mark IV] (2026)&lt;br /&gt;
:Feedback is always welcome if something doesn&amp;#039;t work or where something could or should be improved or done differently.&lt;br /&gt;
*[[CB-HUD Mark III]] (2025-6) previous version!&lt;br /&gt;
*[[CB-HUD Mark II]] (2011) popular precursor (includes notes on CB-HUD Mark I).&lt;br /&gt;
*[[HUD]]&lt;br /&gt;
*[[hud.plist]]&lt;br /&gt;
&lt;br /&gt;
{{HUD-OXP}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=File:Cb68-CB-HUD-Mark-IV.jpg&amp;diff=90334</id>
		<title>File:Cb68-CB-HUD-Mark-IV.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=File:Cb68-CB-HUD-Mark-IV.jpg&amp;diff=90334"/>
		<updated>2026-09-30T14:37:16Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: From https://bb.oolite.space/viewtopic.php?p=307272#p307272&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
From https://bb.oolite.space/viewtopic.php?p=307272#p307272&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=CB-HUD_Mark_III&amp;diff=90333</id>
		<title>CB-HUD Mark III</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=CB-HUD_Mark_III&amp;diff=90333"/>
		<updated>2026-09-30T14:11:06Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added CB-HUD Mark IV&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The CB-HUD Mark III is a fully featured HUD and uses data from CombatMFD to display numeric values and some additional gauges&lt;br /&gt;
[[File:CB-HUD 2025-03-29.png|right|900px]]&lt;br /&gt;
==Overview==&lt;br /&gt;
The CB-HUD Mark III is developed and produced by the [[Crab Boolean Corporation|Crab-Boolean Corporation]] located on [[Sector1/Riredi|Riredi]] in galaxy 1.  &lt;br /&gt;
&lt;br /&gt;
=== Features ===&lt;br /&gt;
*New Gauges&lt;br /&gt;
*10 [[MFD]]s&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
=== Why this new HUD? ===&lt;br /&gt;
 A while ago, I read on the CombatMFD wiki page that currently (July 2023) only [[Vimana HUD]] uses the additional displays and values ​​that CombatMFD provides for custom dials in HUDs. I thought that&amp;#039;s a real shame, because with the help of CombatMFD and the new keys for custom dials in the hud.plist, completely new possibilities open up, even without any knowledge of JavaScript, allowing you to create a custom HUD and then adapt it to your own needs and personal preferences.&lt;br /&gt;
 &lt;br /&gt;
 To showcase at least a few of the new features available since Oolite version 1.81, I created a new HUD and can now present to our community: - - - tadaaa! - - - The Crab-Boolean CB-HUD Mark III.&lt;br /&gt;
 &lt;br /&gt;
 As of today, the CB-HUD Mark III is designed as a pure hud.plist HUD and thus uses neither any JavaScript nor external images. (I only renamed the hud.plist and included the small script provided by Norby to make the HUD compatible with HUDSelector.oxz.)&lt;br /&gt;
 &lt;br /&gt;
 I hope the new possibilities may encourage some players to do a first step into [[the Dark Side]] of the game. Customizing the HUD to your own ideas and preferences is a good way to start, I can say that from my own experience.&lt;br /&gt;
&lt;br /&gt;
==Minimum requirements==&lt;br /&gt;
*Oolite 1.81+&lt;br /&gt;
*[[Combat MFD]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*[[HUD Selector]] compliant&lt;br /&gt;
&lt;br /&gt;
=== Monitor Resolution ===&lt;br /&gt;
This HUD works best 16:10. Other resolutions work, but little space may be left for left and right MFD´s.&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
This .oxz is not compatible with the Target Reticle.oxp as it already has this feature.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
After downloading, move or copy the .OXZ file into the AddOns folder of your oolite installation.&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
=== Current version ===&lt;br /&gt;
* Version 1.0 [https://app.box.com/s/dbgw6qhq4tgfym8p2nope4y9vanw1joe oolite.oxp.captain_beatnik.cb-hud_mark_iii.oxz]&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
*License: CC-BY-NC-SA 4.0&lt;br /&gt;
=== Attributions ===&lt;br /&gt;
:This work is derived from the original configuration files that come with the Oolite program package.&lt;br /&gt;
::Thanks a lot to Giles C Williams (aegidian) and all contributors for developing Oolite.&lt;br /&gt;
:Thanks to Mazur, Thargoid, Killer Wolf, JeffBTX, Wyvern, Smivs and CommonSenseOTB.&lt;br /&gt;
::I have learned very much by studying their work.&lt;br /&gt;
:Special thanks go to Norby, Phkb, Cag and Neelix.&lt;br /&gt;
::Because of their work the additional functions of this HUD have become possible.&lt;br /&gt;
:Last but not least many thanks to Cholmondely and Maik for their great work on the wiki and the documentation.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*Author: [[User:Captain Beatnik|Captain Beatnik]] (page has links to his other HUDs)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=299393#p299393 BB Release Note for Mark III] (2025)&lt;br /&gt;
:Feedback is always welcome if something doesn&amp;#039;t work or where something could or should be improved or done differently.&lt;br /&gt;
*[[CB-HUD Mark IV]] (2026) new version!&lt;br /&gt;
*[[CB-HUD Mark II]] (2011) popular precursor (includes notes on CB-HUD Mark I).&lt;br /&gt;
*[[HUD]]&lt;br /&gt;
*[[hud.plist]]&lt;br /&gt;
&lt;br /&gt;
{{HUD-OXP}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=User:Various_Interest&amp;diff=90329</id>
		<title>User:Various Interest</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=User:Various_Interest&amp;diff=90329"/>
		<updated>2026-09-23T11:22:27Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Creator of the [[Better Damage Sounds OXP]]&lt;br /&gt;
&lt;br /&gt;
See also his [https://bb.oolite.space/viewtopic.php?t=22196 OXP idea list] (2026)&lt;br /&gt;
&lt;br /&gt;
[[Category:OXP authors]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Better_Damage_Sounds_OXP&amp;diff=90328</id>
		<title>Better Damage Sounds OXP</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Better_Damage_Sounds_OXP&amp;diff=90328"/>
		<updated>2026-09-23T11:21:17Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Tweaks&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Replaces the vanilla shield and hull hit sounds with more immersive custom ones. &lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The author was bored of the uninspired bonks of the vanilla hit sounds and made his own, better ones. &lt;br /&gt;
&lt;br /&gt;
The OXP was peer reviewed by a staggering two people. This extensive review proved that it was indeed an improvement.&lt;br /&gt;
&lt;br /&gt;
== Compatibility with BGS and other sound OXPs ==&lt;br /&gt;
To make sure compatibility with BGS and other OXPs, make sure to download and install Better Damage Sounds AFTER them. Oolite code makes sure that the last OXP loaded would trump every other before them.&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
[[File:Better_Damage_Sounds_OXP.zip]] - unzip and place in your AddOns folder&lt;br /&gt;
&lt;br /&gt;
=== Licence ===&lt;br /&gt;
*Author: [[User:Various Interest|Various Interest]]&lt;br /&gt;
*License: CC-BY-NC-SA 4.0&lt;br /&gt;
*Required Oolite version: 1.80 or better&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?t=22193 BB thread]&lt;br /&gt;
&lt;br /&gt;
== Gameplay and Balance Indicator ==&lt;br /&gt;
[[File:Tag-colour-green.png|right]]&lt;br /&gt;
Sounds don&amp;#039;t usually make the game more or less difficult!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{ambience-OXP}} [[Category:Sound Sets OXPs]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=User:Various_Interest&amp;diff=90318</id>
		<title>User:Various Interest</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=User:Various_Interest&amp;diff=90318"/>
		<updated>2026-09-17T19:34:05Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Page created&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Creator of the [[Better Damage Sounds OXP]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:OXP authors]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Talk:OXP_howto_AI&amp;diff=90307</id>
		<title>Talk:OXP howto AI</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Talk:OXP_howto_AI&amp;diff=90307"/>
		<updated>2026-09-10T19:32:45Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* UK_Eliter */ Response (of sorts) and tidy-up&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;running list of most lacking method descriptions..&lt;br /&gt;
&lt;br /&gt;
*performLanding&lt;br /&gt;
*setDestinationToDockingAbort&lt;br /&gt;
*setPlanetPatrolCoordinates&lt;br /&gt;
*setDestinationWithinTarget&lt;br /&gt;
*patrolReportIn&lt;br /&gt;
*addFuel &lt;br /&gt;
*setDestinationToDockingAbort&lt;br /&gt;
--[[User:Murgh|Murgh]] 20:11, 26 January 2006 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OK updated and added various entries.&lt;br /&gt;
[[User: Arexack|Arexack]]&lt;br /&gt;
&lt;br /&gt;
== Giles&amp;#039;s thoughts ==&lt;br /&gt;
&lt;br /&gt;
Needs an introduction explaining what a state-machine is and how Oolite uses them in its AI.&lt;br /&gt;
&lt;br /&gt;
Also how AI receive messages (in the form of strings) and processes messages about every five seconds (depending on the pauseAI set), except when asked to &amp;#039;&amp;#039;react&amp;#039;&amp;#039; to a certain message.&lt;br /&gt;
&lt;br /&gt;
A simple state machine should be given as an example and then shown as a property list.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that I&amp;#039;m likely to expand the use of AI in Oolite:- ship pilots will also have AI which will receive copies of messages sent to the ship&amp;#039;s AI, but pilots AI&amp;#039;s will perform a more &amp;#039;strategic&amp;#039; role.&lt;br /&gt;
&lt;br /&gt;
--[[User:Aegidian|Aegidian]] 11:22, 22 January 2006 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Hmm.. I did refer somewhere to &amp;#039;&amp;#039;&amp;#039;AIreference.htm&amp;#039;&amp;#039;&amp;#039; residing in the oolite folder, that file contains a reasonably coherent explanation on AI-states and messages.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;AddFuel #&amp;#039; ... is it not &amp;#039;awardFuel #&amp;#039;?&lt;br /&gt;
[[Arexack|Arexack]] Mo1:52AM 23jan06&lt;br /&gt;
&lt;br /&gt;
== Arexack&amp;#039;s meddling ==&lt;br /&gt;
&lt;br /&gt;
I just reorganised the entries into functional groups. &lt;br /&gt;
&lt;br /&gt;
Should we keep this list format (for linking purposes) or replace the === with &amp;#039;&amp;#039;&amp;#039;* for better overview?&lt;br /&gt;
&lt;br /&gt;
[[User:Arexack|Arexack]]1600 monday&lt;br /&gt;
--[[User:Arexack|Arexack]] 15:07, 23 January 2006 (UTC)&lt;br /&gt;
&lt;br /&gt;
: I like it. it&amp;#039;s better this way with the hypertext index than replacing them with * rows, I think. [[User: Murgh| Murgh]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
this new line by [[User: 82.171.18.144|82.171.18.144]]..&lt;br /&gt;
==== checkForShips: type ===&lt;br /&gt;
Returns with shipsFound_number = #.&lt;br /&gt;
&lt;br /&gt;
in a script or planetinfo, yes but does this work in AI?  [[User: Murgh| Murgh]]&lt;br /&gt;
 &lt;br /&gt;
 Don&amp;#039;t see why not. A_H&lt;br /&gt;
:&lt;br /&gt;
Now I find myself asking: why is this method included in the AI-methodlist? A_H&lt;br /&gt;
&lt;br /&gt;
:&lt;br /&gt;
Other scripting question: &lt;br /&gt;
condition = (A , B , C)&lt;br /&gt;
do = action&lt;br /&gt;
is this an AND or an OR function? &lt;br /&gt;
&lt;br /&gt;
An AND fuction could be built like:&lt;br /&gt;
 condition = A&lt;br /&gt;
 do = condition B&lt;br /&gt;
      do = condition C&lt;br /&gt;
           do = action &lt;br /&gt;
A_H&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== UK_Eliter ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;scanforThargoid&amp;#039;: &amp;#039;Locates all the ships with primaryRole &amp;quot;thargoid&amp;quot; in range and chooses the nearest. Returns: &amp;quot;TARGET_FOUND&amp;quot; or &amp;quot;NOTHING_FOUND&amp;quot;&amp;#039;. Is that correct? Only the _primary_ role? That is not how the Javascript method `isThargoid` works. (On that latter, see [[Oolite_JavaScript_Reference:_Ship#isThargoid]].)&lt;br /&gt;
&lt;br /&gt;
Humph! It will be interesting to see if you get a response to this! Stuff is occasionally added to these wiki programming pages, but I&amp;#039;m unsure if anybody bothers keeping much of a watch on them. &amp;#039;&amp;#039;Cholmondeley 20:32, 10 September 2026 (BST)&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Category:Oolite_Development&amp;diff=90305</id>
		<title>Category:Oolite Development</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Category:Oolite_Development&amp;diff=90305"/>
		<updated>2026-09-06T07:22:24Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Oops!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== See also ==&lt;br /&gt;
=== OXPs ===&lt;br /&gt;
*[[:Category:Oolite scripting]]&lt;br /&gt;
*https://www.w3schools.com/js/js_array_sort.asp for better knowledge of the js on Oolite. &lt;br /&gt;
*For older oxp&amp;#039;s not written in Javascript, see [[Legacy Scripting]]&lt;br /&gt;
&lt;br /&gt;
=== Vanilla game code ===&lt;br /&gt;
If you’re familiar with OO design concepts, learning Objective-C is about half a day’s work. If not, maybe a few days. Objective-C is a much, much smaller extension to C than C++ is. Take your choice of introductory documents:&lt;br /&gt;
*[http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/index.html The Objective-C Programming Language] – covers OO basics, just about the entire language (including bits not used in Oolite – the Exception Handling and Thread Synchronization chapter in particular) and the runtime library used in Apple’s implementation.&lt;br /&gt;
*[http://www.gnustep.org/resources/ObjCFun.html Objective-C is Fun] – covers most of the language in about three pages. (Assumes a knowledge of C.)&lt;br /&gt;
*[http://www.otierney.net/objective-c.html Objective-C Beginner’s Guide] – a more hands-on tutorial.&lt;br /&gt;
&lt;br /&gt;
The biggest roadblock to most people seems to be [http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/index.html the memory management model]. (The chapter “Implementing Object Copy” can be considered an advanced topic in the context of Oolite, and the Core Foundation and Zones bit are of no interest.) The section [http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/MemoryManagementRules.html Memory Management Rules] is the really important bit.&lt;br /&gt;
&lt;br /&gt;
That said, Oolite is not necessarily the best project to start with; taking a look at [http://developer.apple.com/documentation/Cocoa/Conceptual/ObjCTutorial/index.html Apple’s] or [http://www.gnustep.it/pierre-yves/index.html GNUstep’s] tutorials. (The latter appears to be a rip-off– er, adaptation of the former.) These are geared towards GUI apps, though.&lt;br /&gt;
&lt;br /&gt;
[[User:Ahruman|Ahruman]], 2007&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== This category page ==&lt;br /&gt;
This category is a bit of a dog&amp;#039;s dinner.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1) &amp;quot;Developing Oolite&amp;quot; deals with modding the vanilla game code&lt;br /&gt;
&lt;br /&gt;
2) The various pages beginning &amp;quot;:&amp;quot; - :Class DOOFetch / :Class DOOUnzip / :Dynamic Oolite &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. are mistaken creations, do not function, and seem to be undeletable!&lt;br /&gt;
&lt;br /&gt;
3) The rest of the category (with the possible exception of Galaxy Seeds) are all about OXPs and should be classified accordingly.&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Vanilla_game&amp;diff=90304</id>
		<title>Vanilla game</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Vanilla_game&amp;diff=90304"/>
		<updated>2026-09-06T07:20:59Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Links */ Added another&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Oolite ad1 .jpg|thumb|right|500px]]&lt;br /&gt;
[[File:Start Choices.png|thumb|right|500px|Starting the game. &amp;lt;br&amp;gt; The list of options has been added to by the [[Start Choices]] .oxp]]&lt;br /&gt;
This is the &amp;#039;&amp;#039;basic game&amp;#039;&amp;#039; without any added [[OXP]]s. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you choose &amp;#039;&amp;#039;&amp;#039;Strict Mode&amp;#039;&amp;#039;&amp;#039; (Strict Game) when you start up Oolite, this will constrain you to the &amp;#039;&amp;#039;basic vanilla game&amp;#039;&amp;#039;, excluding whatever OXP/OXZs you may have loaded.&lt;br /&gt;
&lt;br /&gt;
It is identical to the normal game as played without any oxp&amp;#039;s loaded.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Older Versions of Oolite ==&lt;br /&gt;
The Vanilla game used to be &amp;#039;&amp;#039;much more&amp;#039;&amp;#039; different from the oxp&amp;#039;d game.&lt;br /&gt;
&lt;br /&gt;
The strict game &amp;#039;&amp;#039;before&amp;#039;&amp;#039; Oolite v.1.80 was not just an oxp-less version of Oolite. It was actually a mildly modified version of the original [[Classic Elite]]. In those days, the &amp;quot;Vanilla game&amp;quot; was not the strict game, but was just a (regular) oxp-able game - but before adding in any oxp&amp;#039;s.&lt;br /&gt;
&lt;br /&gt;
Optional vanilla-game equipment (added-in to Elite) lost in the &amp;#039;&amp;#039;original&amp;#039;&amp;#039; strict game:&lt;br /&gt;
*Fuel Injectors&lt;br /&gt;
*anti-ECM missiles (&amp;quot;hard heads&amp;quot;)&lt;br /&gt;
*shield boosters&lt;br /&gt;
*scanner targeting enhancements&lt;br /&gt;
*ANA&lt;br /&gt;
*wormhole scanner&lt;br /&gt;
&lt;br /&gt;
Game options lost:&lt;br /&gt;
*targeting in-coming missiles&lt;br /&gt;
*contract hauling&lt;br /&gt;
*the F5F5 cargo-hold manifest screen&lt;br /&gt;
*the F3F3 shipyard for buying/selling ships&lt;br /&gt;
&lt;br /&gt;
Other losses:&lt;br /&gt;
*no navigation beacons&lt;br /&gt;
*no stopping at a standstill&lt;br /&gt;
&lt;br /&gt;
Gains:&lt;br /&gt;
Kills from shooting asteroids!&lt;br /&gt;
&lt;br /&gt;
But it did have the [[Energy Bomb]] - which has since been replaced with the [[Quirium Cascade Mine]]! But then so did the regular Oolite game!&lt;br /&gt;
&lt;br /&gt;
[[User:Cim|Cim]] started the process of changing the strict game away from this. See the discussion [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=14619 here].&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Oolite]] for the History of the development of Oolite&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3442 Strict/Unstrict Gameplay] (2007)&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=12191 New Commander] Playing an almost Vanilla game (2012)&lt;br /&gt;
*[https://www.youtube.com/watch?v=yngSxZXPqGA&amp;amp;list=PLsYaAtYv_5eUpD3FBWQk7XQuKQQsrVhNV&amp;amp;index=9 Arqubus&amp;#039;s YouTube critique of the Vanilla game] (2021, v.1.90)&lt;br /&gt;
&lt;br /&gt;
=== The Dark Arts ===&lt;br /&gt;
*[[:Category:Oolite Development]] for the Oolite Vanilla game code&lt;br /&gt;
[[Category:Oolite]][[Category:Factual]][[Category:Help pages]][[Category:Concepts]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Category:Oolite_scripting&amp;diff=90303</id>
		<title>Category:Oolite scripting</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Category:Oolite_scripting&amp;diff=90303"/>
		<updated>2026-09-06T07:19:44Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Oolite]] scripting topics (mostly focused on OXPs).&lt;br /&gt;
*See also [[:Category:Oolite Development]] for the Oolite [[Vanilla game]] code&lt;br /&gt;
&lt;br /&gt;
== Introductions ==&lt;br /&gt;
*[[Oolite Javascript basics]] - 2022 essay by [[User:Massively Locked|Massively Locked]]&lt;br /&gt;
*[[Scripting Oolite with JavaScript]] contains JenAyton&amp;#039;s essays on what your computer does with Javascript (2008) and his own introduction to Oolite&amp;#039;s Javascript (2011)&lt;br /&gt;
=== Other References ===&lt;br /&gt;
*https://www.w3schools.com/js/js_array_sort.asp is a valuable resource for better knowledge of Javascript.&lt;br /&gt;
*https://developer.mozilla.org/en-US/docs/Web/JavaScript is also good&lt;br /&gt;
&lt;br /&gt;
*Hiran&amp;#039;s [https://ooliteproject.github.io/oolite-expansion-catalog/index.html OXP Index] updated weekly - includes&amp;#039;&amp;#039; all&amp;#039;&amp;#039; Javascript files in the officially published OXZs.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== OXP&amp;#039;s ==&lt;br /&gt;
Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of &amp;#039;&amp;#039;&amp;#039;ECMAv5&amp;#039;&amp;#039;&amp;#039; (2009). It is the same Spidermonkey version (1.8.5 - March 2011) that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. It is unlikely to change in the future (due to the [https://bb.oolite.space/viewtopic.php?p=256623#p256623 immense amount of work] involved in tampering with it!).&lt;br /&gt;
&lt;br /&gt;
*[[Legacy Scripting]] gives an introduction to javascript&amp;#039;s precursor languages (for earlier oxp&amp;#039;s)&lt;br /&gt;
&lt;br /&gt;
*[[:Category:OXPDoc]]: contains relevant documentation for some of the more complex oxp&amp;#039;s&lt;br /&gt;
*[[:Category:Oolite utilities]]: links to utilities (including some oxp&amp;#039;s) &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Links ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=3243 Scripters cove] (2007-date) is a general Q&amp;amp;A thread for programming issues, brimming with advice and suggestions. Be warned! The version of Javascript used in 2007 is earlier than that canonised for Oolite in 2011 - and which is still used. And there are over 100 pages of it!&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=13235 Just a comment on a line of code] (2012-13) contains some useful general comments on Javascript programing for Oolite&lt;br /&gt;
*[[User:Wildeblood]] - see &amp;quot;My &amp;quot;How-to&amp;quot; OXPs&amp;quot; - A collection of micro-OXPs, each demonstrating a particular Oolite JavaScript technique, which might be helpful to others seeking an example to copy. &lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite| Oolite scripting]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Display_Current_Course&amp;diff=90302</id>
		<title>Display Current Course</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Display_Current_Course&amp;diff=90302"/>
		<updated>2026-09-06T00:17:33Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added clarifications&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:Displaycurrentcourse.png|right|400px|thumb|The current course is shown in green (starts from the far right). &amp;lt;br&amp;gt;The course for &amp;#039;&amp;#039;this&amp;#039;&amp;#039; particular contract is in yellow]]&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
This OXP aims to improve the usefulness of the Advanced Navigational Array by adding the player&amp;#039;s current plotted course to all contract detail pages, enabling them to see if the contract is on a similar path to what they are currently traveling along.&lt;br /&gt;
&lt;br /&gt;
==Installation and use==&lt;br /&gt;
In order to get the benefits of this enhancement, the [[Advanced Navigational Array]] must be installed and functional. Once installed, and you have a course plotted on the F6 galactic chart, you will then see your current course plotted in green whenever you examine the details of a contract.&lt;br /&gt;
&lt;br /&gt;
==Link Color Variation==&lt;br /&gt;
It is possible to switch the color of the current course on the map, if the [[Library OXP]] is installed. You can switch between the default green, red, blue, orange, purple, white and magenta.&lt;br /&gt;
&lt;br /&gt;
==Third Party OXP&amp;#039;s==&lt;br /&gt;
If a third party OXP would like to have their mission screen included in those screens which get the current course plotted, all they need to do is:&amp;lt;br/&amp;gt;&lt;br /&gt;
1. Make sure their mission screen has a &amp;quot;screenID&amp;quot; property set.&amp;lt;br/&amp;gt;&lt;br /&gt;
2. Add the following code to their worldScript (usually in the startUpComplete function):&lt;br /&gt;
&lt;br /&gt;
  var dcc = worldScripts.DisplayCurrentCourse;&lt;br /&gt;
  if (dcc) dcc._screenIDList.push(&amp;quot;my_screen_id&amp;quot;);&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
Place the &amp;#039;DisplayCurrentCourse.oxz&amp;#039; into your &amp;#039;AddOns&amp;#039; folder and when you start the game, hold down &amp;#039;Shift&amp;#039; until you see the spinning Cobra.&lt;br /&gt;
&amp;lt;br/&amp;gt;Alternatively, you can download the expansion using the expansion pack manager in the game itself.&lt;br /&gt;
&lt;br /&gt;
==Download==&lt;br /&gt;
Download [[Media:DisplayCurrentCourse.oxz|DisplayCurrentCourse.oxz]] v1.10 (downloaded {{#downloads:DisplayCurrentCourse.oxz}} times).&lt;br /&gt;
&lt;br /&gt;
==License==&lt;br /&gt;
This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 4.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/4.0/&lt;br /&gt;
&lt;br /&gt;
==Version History==&lt;br /&gt;
1.10&lt;br /&gt;
* Moved all text into descriptions.plist for easier localisation.&lt;br /&gt;
&lt;br /&gt;
1.9&lt;br /&gt;
* Version number change to try and fix some download issues, no functional changes.&lt;br /&gt;
&lt;br /&gt;
1.8&lt;br /&gt;
* Added ability to change the link color (via Library Config).&lt;br /&gt;
&lt;br /&gt;
1.7&lt;br /&gt;
* Better handling of Galactic jumps.&lt;br /&gt;
* Code refactoring.&lt;br /&gt;
&lt;br /&gt;
1.6&lt;br /&gt;
* Updated list of known screenID&amp;#039;s.&lt;br /&gt;
* Fixed issue where viewing Escort Contracts would potentially stop the current route from showing.&lt;br /&gt;
* Added Random Hits screen ID inclusion.&lt;br /&gt;
&lt;br /&gt;
1.5&lt;br /&gt;
* Fixed the issue with the course being reset to the contract destination if only 1 contract was available.&lt;br /&gt;
&lt;br /&gt;
1.4&lt;br /&gt;
* Changed assumptions about &amp;quot;Route Mode - None&amp;quot; - this mode will now turn off the display of your current course on contract screens, rather than default to a &amp;quot;fewest jumps&amp;quot; route.&lt;br /&gt;
&lt;br /&gt;
1.3&lt;br /&gt;
* Added contract summary pages to the list of screen ID&amp;#039;s to monitor to fix issue where player&amp;#039;s current course is sometimes not displayed.&lt;br /&gt;
&lt;br /&gt;
1.2&lt;br /&gt;
* Attempts to fix issue where player&amp;#039;s true current course is sometimes not displayed.&lt;br /&gt;
&lt;br /&gt;
1.1&lt;br /&gt;
* Small improvements to marking logic, so only one link is required.&lt;br /&gt;
&lt;br /&gt;
1.0&lt;br /&gt;
* Initial release.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Contracts]]&lt;br /&gt;
&lt;br /&gt;
==Quick Facts==&lt;br /&gt;
{{OXPLevel|0}}{{IconOXP|ooVersion=&amp;quot;1.80&amp;quot;|oxpCPU=&amp;quot;Low&amp;quot;|oxpMEM=&amp;quot;Low&amp;quot;|oxpGPU=&amp;quot;Low&amp;quot;|oxpIsAPI=true|oxpIsDocumented=true}}&lt;br /&gt;
{|class=&amp;quot;floatright&amp;quot; style=&amp;quot;alignment:right;margin: 0 auto;&amp;quot;&lt;br /&gt;
|[[Image:IconLib.png|48px|right|link=Library OXP|alt=Config options available through &amp;#039;Library&amp;#039;]]&lt;br /&gt;
|}&lt;br /&gt;
{{Infobox OXPb| title = DisplayCurrentCourse.oxz&lt;br /&gt;
|version = 1.10&lt;br /&gt;
|release = 2025-07-23&lt;br /&gt;
|license = CC BY-NC-SA 4.0&lt;br /&gt;
|features = Route planning&lt;br /&gt;
|category = Mechanics OXPs‏‎&lt;br /&gt;
|author = [[User:phkb|phkb]]&lt;br /&gt;
|feedback = [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17892 Oolite BB]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Gameplay and Balance indicator==&lt;br /&gt;
[[Image:tag-colour-blue.png]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Equipment]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=OXP_howto&amp;diff=90301</id>
		<title>OXP howto</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=OXP_howto&amp;diff=90301"/>
		<updated>2026-09-04T06:05:48Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Tags&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:&amp;#039;&amp;#039;Shortcut: EW:OXP and EW:HOWDS redirect here&amp;#039;&amp;#039;&amp;lt;/br&amp;gt;&lt;br /&gt;
[[Image:oolite-oxp-icon.png|100px|thumb|right|OXP icon]]&lt;br /&gt;
[[File:Oolite-debug-menu.png|thumb|right|Debug Menu  (From the AppleMac variety of the &amp;quot;Oolite TR&amp;quot; version)]]&lt;br /&gt;
==Overview==&lt;br /&gt;
An &amp;#039;&amp;#039;&amp;#039;Oolite Expansion Pack&amp;#039;&amp;#039;&amp;#039; can cause many big changes or additions to Oolite&amp;#039;s gameplay, or it may represent just a small, subtle alteration. By first appearances, there is no way to tell what is inside, as it&amp;#039;s merely a &amp;#039;&amp;#039;folder&amp;#039;&amp;#039; with the added extension &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
Oolite Version 1.79 onwards supports also compressed files in ZIP format with extension &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039;. &lt;br /&gt;
&lt;br /&gt;
To learn starting with a non-compressed version have a look at [[OXP_tutorial]].&lt;br /&gt;
&lt;br /&gt;
{{QuoteText|Text=It&amp;#039;s worth saying I think that compared with a lot of game addon architectures, the OXP architecture as designed by Giles is already very good at avoiding conflicts compared with a lot of other games&lt;br /&gt;
- you can save your game, add, remove and upgrade lots of OXPs, load your game, and have it work&lt;br /&gt;
- you can do this repeatedly, while incrementally upgrading the core game, for years&lt;br /&gt;
- as a player you basically never have to care about load order; as an OXP developer, rarely&lt;br /&gt;
&lt;br /&gt;
It&amp;#039;s also worth noting that a lot of types of OXP conflicts are inevitable due to resource conflicts - a planet can only have one diffuse map, a ship can only have one AI - or due to conceptual conflicts - OXP A removes all stations from a system; OXP B expects the player to dock there.|Source=([https://bb.oolite.space/viewtopic.php?p=241733#p241733 Cim (3rd Lead Developer)])}}&lt;br /&gt;
&lt;br /&gt;
=== Oolite TR version ===&lt;br /&gt;
The Oolite Developer Release/Test Release version is specially developed for testing out OXPs. It comes with a [[Debug OXP]]/Debug Console allowing one to spawn ships/station on demand, award oneself a test ship, detect the mass of another ship &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
It is downloaded from the main Oolite website - currently http://www.oolite.space/download/&lt;br /&gt;
&lt;br /&gt;
== OXZ ==&lt;br /&gt;
The new OXZ distribution format is strongly recommended. It makes version control and distribution just so much easier.&lt;br /&gt;
&lt;br /&gt;
To make an OXZ file, use a ZIP program to compress the contents of the OXP folder, so that the [[manifest.plist]] file is in the root of the ZIP file, and the folders (AI, Config, etc) are folders in the ZIP file. Then, rename the ZIP file so that its extension is &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039;. To inspect an OXZ file, open it with your ZIP program.&lt;br /&gt;
&lt;br /&gt;
Here is a sample: [[Media:X.0.1.oxz]] - just rename all &amp;quot;X&amp;quot; within to the title of your idea and put your name into the author fields. &lt;br /&gt;
&lt;br /&gt;
You can use [http://www.ghisler.com/download.htm Total Commander] or [http://en.wikipedia.org/wiki/Krusader Krusader] to edit files within &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039; directly, without unpacking.&lt;br /&gt;
&lt;br /&gt;
For more details read [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16688 The All-in-One Guide to OXZ Packaging and Distribution].&lt;br /&gt;
&lt;br /&gt;
=== Creating an .oxz on an AppleMac ===&lt;br /&gt;
When you compress the files/folders on the AppleMac to create the .oxz &amp;#039;&amp;#039;do not&amp;#039;&amp;#039; select them with your mouse! This way lies misery!&lt;br /&gt;
&lt;br /&gt;
Rather, ensure the relevant files/folders are inside one overall folder. Then, use &amp;#039;&amp;#039;&amp;#039;command-a&amp;#039;&amp;#039;&amp;#039; to select all the &amp;#039;&amp;#039;contents&amp;#039;&amp;#039; of this overall folder and then select &amp;#039;&amp;#039;&amp;#039;compress&amp;#039;&amp;#039;&amp;#039; from the file menu on the finder&amp;#039;s menu bar. Finally, rename your newly-created .zip file as an .oxz&lt;br /&gt;
&lt;br /&gt;
==Structure==&lt;br /&gt;
Inside the &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039; folder, or the &amp;#039;&amp;#039;&amp;#039;.oxz&amp;#039;&amp;#039;&amp;#039; file, 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&amp;#039;s contents. To get a feeling for it, simply take a look in other oxps. (If they are in .oxz format, any normal unzip program can inspect their contents - many will even let you edit the contents without having to unzip and rezip the file)&lt;br /&gt;
&lt;br /&gt;
The structure for OXPs:&lt;br /&gt;
 AddOns (folder)&lt;br /&gt;
 ~.oxp (really just another folder!) - Holds manifest.plist and the other folders:&lt;br /&gt;
 &lt;br /&gt;
 --&amp;gt; AIs (folder) - Holds AI plists&lt;br /&gt;
 --&amp;gt; Config (folder) - Holds all other plists (and possibly an anonymous &amp;quot;Script.js&amp;quot;)&lt;br /&gt;
 --&amp;gt; Images (folder) - Holds background images&lt;br /&gt;
 --&amp;gt; Models (folder) - Holds the .dat files (special Oolite format)&lt;br /&gt;
 --&amp;gt; Music (folder) - Surprise - holds .ogg music files&lt;br /&gt;
 --&amp;gt; Scenarios (folder) - Holds new game scenarios (v1.79)&lt;br /&gt;
 --&amp;gt; Scripts (folder) - Holds scripts (worldScripts and shipScripts)&lt;br /&gt;
 --&amp;gt; Shaders (folder) - Holds Vertex and Fragment shaders (v1.69)&lt;br /&gt;
 --&amp;gt; Sounds (folder) - Holds sound files&lt;br /&gt;
 --&amp;gt; Textures (folder) - Holds models textures (can be planets, too!)&lt;br /&gt;
 --&amp;gt; [[manifest.plist]] (file) &lt;br /&gt;
     &amp;#039;&amp;#039;the following might also be found in here:&amp;#039;&amp;#039;&lt;br /&gt;
 --&amp;gt; [[Misc plists|info.plist]] (file, seems to be a poor duplicate of the Manifest.plist)&lt;br /&gt;
 --&amp;gt; [[Requires.plist]] (file: deprecated - replaced by Manifest.plist)&lt;br /&gt;
&lt;br /&gt;
*If the OXP is in the uncompressed OXP folder format, the .oxp folder must contain a [[requires.plist]] file. If it is in the compressed OXZ single-file format, it must contain a [[manifest.plist]] file.&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=13134 Nested OXPs in AddOns folder] (2012) - some OXZ&amp;#039;s do this (Station spotter oxp inside [[Stations for Extra Planets]]) &lt;br /&gt;
&lt;br /&gt;
===AIs folder===&lt;br /&gt;
The folder named AIs contains any AI.plist additions the OXP might use. &lt;br /&gt;
&lt;br /&gt;
* [[OXP howto AI|Making Oolite AI]]&lt;br /&gt;
&lt;br /&gt;
In Oolite 1.79 AIs may be written in Javascript using .js files in this folder. A helper library is provided to make writing complex JS AIs simpler.&lt;br /&gt;
&lt;br /&gt;
* [[Oolite PriorityAI Documentation]]&lt;br /&gt;
* [[Oolite PriorityAI Tutorial]]&lt;br /&gt;
&lt;br /&gt;
===Config folder===&lt;br /&gt;
All plist files except for those introducing new AIs, &amp;#039;&amp;#039;[[requires.plist]]&amp;#039;&amp;#039;, &amp;#039;&amp;#039;[[manifest.plist]]&amp;#039;&amp;#039; or &amp;#039;&amp;#039;[[Misc plists|info.plist]]&amp;#039;&amp;#039;, belong in Config.&lt;br /&gt;
&lt;br /&gt;
In its simplest form, an OXP could contain only a Config with an altering &amp;#039;&amp;#039;script.plist&amp;#039;&amp;#039; or &amp;#039;&amp;#039;planetinfo.plist&amp;#039;&amp;#039;.  An OXP that adds a new ship needs a &amp;#039;&amp;#039;shipdata.plist&amp;#039;&amp;#039; entry, and unless it is based entirely on existing Oolite data, would include a model and texture. &lt;br /&gt;
&lt;br /&gt;
* [[OXP howto plist|Making Oolite plists]]&lt;br /&gt;
* Usually irrelevant: The Config folder isn&amp;#039;t cached in the same way as the rest of an oxp because usually its contents merge rather than overwriting (See [https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=16927 here])&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
This folder contains [[Property lists]] such as:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;[[characters.plist]]&amp;#039;&amp;#039; that adds non-player characters to Oolite.&lt;br /&gt;
* &amp;#039;&amp;#039;[[crosshairs.plist]]&amp;#039;&amp;#039; that contains the look for your weapons (v1.73).&lt;br /&gt;
* &amp;#039;&amp;#039;[[customsounds.plist]]&amp;#039;&amp;#039; that contains references to ingame used sounds.&lt;br /&gt;
* &amp;#039;&amp;#039;[[descriptions.plist]]&amp;#039;&amp;#039; that adds vocabulary to Oolite texts.&lt;br /&gt;
* &amp;#039;&amp;#039;[[effectdata.plist]]&amp;#039;&amp;#039; defines custom visual effects (v1.77).&lt;br /&gt;
* &amp;#039;&amp;#039;[[equipment.plist]]&amp;#039;&amp;#039; lists upgrades available from the Shipyard.&lt;br /&gt;
* &amp;#039;&amp;#039;[[explosions.plist]]&amp;#039;&amp;#039; customises things blowing up (v1.81)&lt;br /&gt;
* &amp;#039;&amp;#039;[[global-settings.plist]]&amp;#039;&amp;#039; sets a few miscellaneous universal settings (v1.81)&lt;br /&gt;
* &amp;#039;&amp;#039;[[gui-settings.plist]]&amp;#039;&amp;#039; settings for reformatting the GUI screens (v1.81)&lt;br /&gt;
* &amp;#039;&amp;#039;[[hud.plist]]&amp;#039;&amp;#039; and &amp;#039;&amp;#039;[[hud.plist|hud-small.plist]]&amp;#039;&amp;#039; that allows for changes or a radically new &amp;#039;&amp;#039;Head-Up Display&amp;#039;&amp;#039;.&lt;br /&gt;
* &amp;#039;&amp;#039;[[Oolite_Keyboard_Controls|keyconfig2.plist]]&amp;#039;&amp;#039; that allows for changes of the keymapping.&lt;br /&gt;
* &amp;#039;&amp;#039;[[missiontext.plist]]&amp;#039;&amp;#039; contains texts for the mission screens.&lt;br /&gt;
* &amp;#039;&amp;#039;[[OXPMessages.plist]]&amp;#039;&amp;#039; adds warnings to testversions of an oxp.&lt;br /&gt;
* &amp;#039;&amp;#039;[[planetinfo.plist]]&amp;#039;&amp;#039; that plots system specific changes from the default. May also contain &amp;#039;&amp;#039;script actions&amp;#039;&amp;#039;.&lt;br /&gt;
* &amp;#039;&amp;#039;[[role-categories.plist]]&amp;#039;&amp;#039; for specifying groups of roles (&amp;#039;&amp;#039;eg&amp;#039;&amp;#039;.: trader, Miner, pirate &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.) with similar properties (v1.79)&lt;br /&gt;
* &amp;#039;&amp;#039;[[scenarios.plist]]&amp;#039;&amp;#039; lists the starting scenarios in the Scenarios folder (v1.79).&lt;br /&gt;
* &amp;#039;&amp;#039;[[screenbackgrounds.plist]]&amp;#039;&amp;#039; that contains references to background images (v1.74).&lt;br /&gt;
* &amp;#039;&amp;#039;[[Scripting Oolite with JavaScript|script.js]]&amp;#039;&amp;#039; is the successor of [[script.plist]] in JavaScript.It will be loaded in preference to script.plist if both exist.&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipdata.plist]]&amp;#039;&amp;#039; that introduces any new entity (ships, stations, objects etc.) to Oolite.&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipdata-overrides.plist]]&amp;#039;&amp;#039; that selectively can replace shipentries in other shipdata.plists&lt;br /&gt;
* &amp;#039;&amp;#039;[[shiplibrary.plist]]&amp;#039;&amp;#039; that gives information for the ship description library viewable from the startup screen (v1.79)&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipyard.plist]]&amp;#039;&amp;#039; that introduces new ships available for player purchase.&lt;br /&gt;
* &amp;#039;&amp;#039;[[shipyard-overrides.plist]]&amp;#039;&amp;#039; that selectively can replace shipentries in other shipyard.plists&lt;br /&gt;
* &amp;#039;&amp;#039;[[speech_pronunciation_guide.plist]]&amp;#039;&amp;#039; is another of the other custom methods.&lt;br /&gt;
* &amp;#039;&amp;#039;[[trade-goods.plist]]&amp;#039;&amp;#039; defines trade goods in 1.81 and later&lt;br /&gt;
* &amp;#039;&amp;#039;[[world-scripts.plist]]&amp;#039;&amp;#039; that contains a list of scripts (if more than one worldScript should be used).&lt;br /&gt;
&lt;br /&gt;
Deprecated:&lt;br /&gt;
* &amp;#039;&amp;#039;[[commodities.plist]]&amp;#039;&amp;#039; that contains information for each commodity in a market in 1.80 or earlier&lt;br /&gt;
* &amp;#039;&amp;#039;[[demoships.plist]]&amp;#039;&amp;#039; that selects demoships to show on startup (replaced - approximately - by shiplibrary.plist in 1.79 and later)&lt;br /&gt;
* &amp;#039;&amp;#039;[[illegal_goods.plist]]&amp;#039;&amp;#039; that contains a list of banned/forbidden items in 1.80 or earlier. GalCop has an eye on that.&lt;br /&gt;
* &amp;#039;&amp;#039;[[Oolite_Keyboard_Controls|keyconfig.plist]]&amp;#039;&amp;#039; that allows for changes of the keymapping. (deprecated in v1.92)&lt;br /&gt;
* &amp;#039;&amp;#039;[[pirate-victim-roles.plist]]&amp;#039;&amp;#039; that defines which roles should act as traders. (deprecated in v1.79)&lt;br /&gt;
* &amp;#039;&amp;#039;[[script.plist]]&amp;#039;&amp;#039; to handle conditional &amp;#039;&amp;#039;script actions&amp;#039;&amp;#039;. (deprecated)&lt;br /&gt;
* &amp;#039;&amp;#039;[[script.oos]]&amp;#039;&amp;#039; was briefly introduced during 1.70 development but is now deprecated in favour of JS.)&lt;br /&gt;
&lt;br /&gt;
=== Models folder===&lt;br /&gt;
Oolite models need to be in an Oolite specific format using the the &amp;#039;&amp;#039;&amp;#039;.dat&amp;#039;&amp;#039;&amp;#039; file extension. 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&amp;#039;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 &amp;#039;&amp;#039;model&amp;#039;&amp;#039; entry - case sensitive!!!&lt;br /&gt;
&lt;br /&gt;
* [[OXP howto model|Making Oolite models]] - tutorials for Wings3D &amp;amp; Blender, notes on sub-entities, links &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
* [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12165 Model Converter utilities] (2012-17)&lt;br /&gt;
* Video: [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16123 From scratch to Mamba in under an hour] ([[Dertien]], 2013)&lt;br /&gt;
&lt;br /&gt;
===Scripts folder===&lt;br /&gt;
Scripts are in text format. In this folder you can put both JavaScript scripts as well as legacy scripts. New OXPs should only use JavaScript here.&lt;br /&gt;
* [[Scripting_Oolite_with_JavaScript|Scripting Oolite with Javascript]]&lt;br /&gt;
* [[Oolite_JavaScript_object_model|Scripting reference]]&lt;br /&gt;
&lt;br /&gt;
===Textures folder===&lt;br /&gt;
&lt;br /&gt;
Oolite&amp;#039;s textures are in the &amp;#039;&amp;#039;&amp;#039;.png&amp;#039;&amp;#039;&amp;#039; format, usually at a standard 512x512 size, and must be named exactly as they are named in the .dat file. &lt;br /&gt;
&lt;br /&gt;
* [[OXP howto texture|Making Oolite textures]]&lt;br /&gt;
&lt;br /&gt;
* [[Smivs&amp;#039;_texture_tutorial|Smivs&amp;#039; guide to making Oolite textures]]&lt;br /&gt;
&lt;br /&gt;
* [[Texturing tips and tricks by Theta Seven]]&lt;br /&gt;
&lt;br /&gt;
Viewing a specific texture and / or model in Oolite.&lt;br /&gt;
&amp;quot;I made one. How do I proof it?&amp;quot;&lt;br /&gt;
&lt;br /&gt;
* [[Viewing a Texture or Model]]&lt;br /&gt;
&lt;br /&gt;
==Tool: OXP Verifier==&lt;br /&gt;
&lt;br /&gt;
Oolite has what amounts to a spell checker for shipdata.plist and some other plists, called the OXP verifier. &lt;br /&gt;
&lt;br /&gt;
*It does not work with OXZ&amp;#039;s (so convert your OXP&amp;#039;s to OXZ&amp;#039;s later!).&lt;br /&gt;
*Nor does it work on the standard game release version of Oolite (v.1.90, v.1.92 &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;). Only on the Test Release/Developer&amp;#039;s Release version &amp;#039;&amp;#039;and&amp;#039;&amp;#039; on the Nightlies/Pre-Releases (v.1.91, v.1.93 &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.)&lt;br /&gt;
&lt;br /&gt;
The verifier detects unknown keys or wrong use of keys &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;. It can currently only be invoked from the command line. &lt;br /&gt;
&lt;br /&gt;
On Windows or Linux: &lt;br /&gt;
Code: &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;oolite.app/oolite --verify-oxp &amp;lt;path to OXP&amp;gt; &amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
On Mac OS X: &lt;br /&gt;
Code: &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Oolite.app/Contents/MacOS/Oolite --verify-oxp &amp;lt;path to OXP&amp;gt;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Most Mac users will not be familiar with using the command line. Look inside your application folder for a &amp;#039;&amp;#039;&amp;#039;utilities folder&amp;#039;&amp;#039;&amp;#039;. Inside that you will find a program called [https://en.wikipedia.org/wiki/Terminal_(macOS) Terminal]. &amp;lt;br&amp;gt;&lt;br /&gt;
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: &amp;quot;/Contents/MacOS/Oolite --verify-oxp &amp;quot;.  Now drop the oxp you want to verify on the window. That will again create the path to the oxp behind the last entry. &amp;lt;br&amp;gt;&lt;br /&gt;
When you select the window and hit the &amp;lt;return&amp;gt; key, the verification will start. It should now open the Console program, showing the results. &amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Console&amp;#039;&amp;#039;&amp;#039; is a log viewer developed by Apple Inc. and included with macOS, also in the utilities folder. It allows users to search through all of the system&amp;#039;s logged messages, and can alert the user when certain types of messages are logged. The Console is generally used for troubleshooting when there is a problem with the computer. MacOS itself, as well as any applications that are used, send a constant stream of messages to the system in the form of log files. The console allows you to read the system logs, help find certain ones, monitor them, and filter their contents. See [[Debug OXP]] for more information.&lt;br /&gt;
&lt;br /&gt;
There is a lengthy file - &amp;#039;&amp;#039;&amp;#039;OXP verifier design.txt&amp;#039;&amp;#039;&amp;#039; tucked inside your Oolite installation with more information about it&lt;br /&gt;
&lt;br /&gt;
Note that it is possible to [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=21443 obtain graphical output] from Graphviz for OXP Verifier.&lt;br /&gt;
&lt;br /&gt;
=== Verifier BB threads ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=8&amp;amp;t=13400 plist Editor Pro for Windows] (2013 - full of relevant Red Herrings)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=3&amp;amp;t=16865 lite --verify-oxp fails when path has spaces in it] (2014)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=21359 OXP Develoopment and Plist files] (2023 - quick introduction)&lt;br /&gt;
&lt;br /&gt;
=== Correcting with plutil (Apple Macintosh Terminal utility) ===&lt;br /&gt;
Since a very small mistake is enough to stop a .plist from being accepted, it&amp;#039;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 &amp;#039;address&amp;#039; of the plist to be shown. Hit return, and Terminal will reveal whether or not the plist is OK. If it&amp;#039;s not, you might be given a clue to what is wrong, and the line number of the error - or just a general note that &amp;quot;Unexpected character { at line 1&amp;quot;!&lt;br /&gt;
&lt;br /&gt;
==Need for unique names==&lt;br /&gt;
On loading the oxps, Oolite will add all files in the AIs, Models, Sound and Scripts folders in one big 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Scripting with JavaScript==&lt;br /&gt;
Older OXPs (from [[User:Aegidian|Aegidian]]&amp;#039;s day were written in Legacy Script: see [[Methods]]. Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of &amp;#039;&amp;#039;&amp;#039;ECMAv5&amp;#039;&amp;#039;&amp;#039;. It is the same Spidermonkey version that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. [https://bb.oolite.space/viewtopic.php?p=256623#p256623 It is unlikely to change] in the future.&lt;br /&gt;
&lt;br /&gt;
JavaScript is the preferred scripting interface for worldScripts and shipScripts. The legacy scripting interface (see [[script.plist]]) still works, but is not supported. See [[Scripting Oolite with JavaScript]] for more information.&lt;br /&gt;
&lt;br /&gt;
Note that most of the [[Legacy Scripting]] still works perfectly well (XML &amp;amp; OpenStep)!&lt;br /&gt;
&lt;br /&gt;
==Hidden settings==&lt;br /&gt;
There are several [[Hidden_Settings_in_Oolite]] that make life for an oxp creator easier. One of them is the setting &amp;#039;&amp;#039;&amp;#039;always-flush-cache&amp;#039;&amp;#039;&amp;#039;. It makes every startup a bit slower, but it prevents Oolite working with cached data instead of your newly changed file. For someone that only does occasional oxp changes it will be enough to flush the cache by holding the shift key when starting Oolite but if you are writing oxps, this is the way to prevent frustrations.&lt;br /&gt;
&lt;br /&gt;
==Cookbook==&lt;br /&gt;
* How to add dials to a HUD: https://bb.oolite.space/viewtopic.php?p=290352#p290352&lt;br /&gt;
* How to limit a station&amp;#039;s shipyard to only offer a defined set of ships: https://bb.oolite.space/viewtopic.php?p=293174#p293174&lt;br /&gt;
* Ship/Station design with external docking ports: https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=21574&amp;amp;p=293777&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Context&amp;#039;&amp;#039;&amp;#039;: [https://bb.oolite.space/viewtopic.php?p=275434#p275434 What can OXP&amp;#039;s &amp;#039;&amp;#039;not&amp;#039;&amp;#039; change?] (2021)&lt;br /&gt;
*It is often helpful to dip one&amp;#039;s toes (claws?) in the water by experimenting with tweaking oxp&amp;#039;s first: see [[How to tweak OXZ&amp;#039;s]]&lt;br /&gt;
*[[:Category:Oolite scripting]]&lt;br /&gt;
*[[Javascript Operators]]&lt;br /&gt;
*[[:Category:Oolite JavaScript Reference‎]]&lt;br /&gt;
*[[:Category:Oolite Development]]&lt;br /&gt;
*[[User:Montana05|Montana05]] recommends https://www.w3schools.com/js/js_array_sort.asp for better knowledge of the js on Oolite.&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=12149 OXP Development Best Practices] (2012-7)&lt;br /&gt;
*Some older oxp&amp;#039;s are written in [[Legacy Scripting]]&lt;br /&gt;
*[https://github.com/OoliteProject/oolite/find/master Github] vanilla game code repository - the resources section at the bottom of the page contains possibly useful parts of vanilla game coding, with occasional annotations.&lt;br /&gt;
=== Tools ===&lt;br /&gt;
*[[List of software]] that is helpful for creating OXPs (eg. editorial packages for javascript or 3D model creators)&lt;br /&gt;
*[[List of Planets used in OXPs]] for planets already used by other OXPs. Helps authors avoid overlapping with or breaking other OXPs.&lt;br /&gt;
*[[OXP_howto_Game_Balance|OXP howto Game Balance]] to avoid conflicts from accidental gameplay changes.&lt;br /&gt;
*[[Long Range Scanner]] is an OXP which allows you to jump around the star system to objects you have placed there - or to jump around within the galaxy. A &amp;quot;cheat&amp;quot; for players, but a useful tool for some OXP designers.&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=13422 What Tools Are Good For Windows OXP Programming?] (2013)&lt;br /&gt;
&lt;br /&gt;
==== Tutorials for Tools ====&lt;br /&gt;
*[https://web.archive.org/web/20050317033938/http://oolite.aegidian.org/cyoship/ Oolite Tutorial - Meshwork Shipbuilding (OSX only)] via WayBack Machine&lt;br /&gt;
*[https://web.archive.org/web/20060621211940/http://oolite.aegidian.org/cyoship2/ Oolite Tutorial - Wings 3D Shipbuilding (Cross-platform)] via WayBack Machine&lt;br /&gt;
&lt;br /&gt;
=== OXP tutorials ===&lt;br /&gt;
Oolite changes affecting different varieties of OXPs happened with v.1.76 (2011), v.1.80 (2014) &amp;amp; v1.82 (2015).&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20937 MasterClass: How to OXP (updating SoThisTC)] by [[User:Spara|Spara]] who teaches computing in Helsinki! (2021)&lt;br /&gt;
*[https://archive.org/details/GettingStartedWithOoliteOXZDevelopment Getting started with OXZ Development] &amp;#039;&amp;#039;An .odt for Open Office&amp;#039;&amp;#039;: By Bugbear (2012). 2 example OXPs: a pirate-ridden solar systems warning tool &amp;amp; Witchspace Blockades [https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=17731 BB Thread (2015)]&lt;br /&gt;
&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18837 OXP Performance] BB thread (mostly 2017-8): improving your OXP (speed, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;)&lt;br /&gt;
==== Tutorials: Ships, Retextures &amp;amp; Dockables OXPs ====&lt;br /&gt;
*[[OXP howto model]]&lt;br /&gt;
*[[OXP howto texture]] - also covers planet textures&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=18284 The bare minimum for a game-recognizable ship OXP] (thread: 2016)&lt;br /&gt;
*[[OXP_tutorial|OXP Tutorial]] creating a new spaceship - and then tweaking it in different ways (2007-13)&lt;br /&gt;
*[[OXP howto dockable stations]] (2009-10)&lt;br /&gt;
*[[User:Shipbuilder|Shipbuilder]] wrote a Shaders tutorial with resource packs (2013)&lt;br /&gt;
==== Tutorials: HUD OXPs ====&lt;br /&gt;
*[[OXP howto HUD]]&lt;br /&gt;
*[[Guide to HUDs]] - table comparing features&lt;br /&gt;
*[[HUD Customisation Guide‎‎]]&lt;br /&gt;
*[[Fully Annotated HUD Configuration (hud.plist) File‎]]&lt;br /&gt;
==== Tutorials: Missions OXPs ====&lt;br /&gt;
*[[OXP mission offering]]&lt;br /&gt;
*[[GalCop Missions]] has a wide variety of over 80 javascripted mini-missions - see the list behind the &amp;quot;Spoilers&amp;quot; button&lt;br /&gt;
==== Tutorials: Other ====&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=14135 How to make a simple OXP?] (thread: 2013) 3 OXPs - pop-up message at docking, set only Pythons for sale at Lave shipyard, create a new ship. &lt;br /&gt;
*[[Escape Pod Locator OXP]] has notes on programming on the bottom of the page regarding beacon transmission &amp;amp; location&lt;br /&gt;
&lt;br /&gt;
=== Helpful OXPs for your OXP===&lt;br /&gt;
There are a number of OXPs which have been specifically written to allow your OXP to use them:&lt;br /&gt;
*[[Library OXP|Library]]: a collection of useful snippets and helpers. Its main purpose is to simplify or unify some common tasks used by OXPers. &lt;br /&gt;
:*It can add dynamic maps, music &amp;amp; animation. &lt;br /&gt;
:*It adds a Personal Assistant Device for the player with details of people met, medals awarded, Guild rankings, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
:*It allows in-game configuration of an oxp by the player.&lt;br /&gt;
:*Add-on modules allows inspection of models and materials for creation of ship &amp;amp; station oxps.&lt;br /&gt;
*[[GalCop Missions]] introduces many new pieces of equipment with wide varieties of use (Cargo Stoppers, Ejection Dampers, Range Finders, Solar Radiation Disrupter Missiles, Seismic Resonance Scanners, Patient Transport Modules &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;). It can also help with creating missions (it contains over 80 varieties - see the spoiler button on that wiki page).&lt;br /&gt;
*[[Diplomancy]] can be used to make states of war impact personally on the player&lt;br /&gt;
*[[System Data Config]] helps re-organise the F7 screen to squeeze more information onto it&lt;br /&gt;
&lt;br /&gt;
==== While docked/stations ====&lt;br /&gt;
*[[HD Backgrounds]] can provide a High Definition screenshot of a station lobby or other such for interaction with the player&lt;br /&gt;
*[[BGS]] can help organise a customised docking or launching sequence (see the [[Riredi OXP]] or the [[Kiota Stations]]).&lt;br /&gt;
*[[GNN]] can broadcast your news alerts (see how [[Diplomancy]] uses it for war &amp;amp; peace declarations). GNN also contains &amp;#039;&amp;#039;&amp;#039;PhraseGen&amp;#039;&amp;#039;&amp;#039; which can be used for randomizing text descriptions.&lt;br /&gt;
*[[Station Validator]] will remember that a station has been destroyed and stop Oolite automatically replacing it on the next visit to the system&lt;br /&gt;
*[[Station Dock Control]] can help interraction with other ships docked at the station&lt;br /&gt;
*[[Bulletin Board System]] can help manage interractions at the station&lt;br /&gt;
*[[Email System OXP]] can also help manage interractions at the station&lt;br /&gt;
*[[Ship Storage Helper]] allows storage of the player&amp;#039;s ship whilst doing other things (such as flying another ship!)&lt;br /&gt;
*[[Equipment Storage OXP]]  allows storage of equipment/goods whilst doing other things&lt;br /&gt;
*[[Ship&amp;#039;s Library]] allows reading documents with illustrations while docked (see the included Ship&amp;#039;s Manual)&lt;br /&gt;
*[[Station Options]] allows complex configurations of equipment, but could potentially also be used for managing dialogue with NPCs&lt;br /&gt;
*[[Life in the Frontier]] was being expanded to cover more stations (Dodo/Ico/Rock Hermits and potentially OXP stations), but is currently mothballed. &lt;br /&gt;
&lt;br /&gt;
==== In-flight ====&lt;br /&gt;
*[[MFD - Broadcast Comms]] can be used for in-flight interaction with NPC&amp;#039;s&lt;br /&gt;
*[[Bigships]] can be used to help with the AI for massive space ships which cannot dock at orbital stations&lt;br /&gt;
*[[Montanas Resource Pack 01]] contains a number of resources for use (treasures, containers, escape/survival equipment)&lt;br /&gt;
*[[Star System Lane Indicator]] - the older version contains a very graphical dynamic display (does not function properly, but boy! does it look good!)&lt;br /&gt;
*[[SOTL Exploration]] contains exploration equipment and a non-automatic hyperspace jump&lt;br /&gt;
*[[SOTL Altmap]] contains different politics, markets and NPCs with Torus Drives.&lt;br /&gt;
*[[Resistance Commander]] &amp;amp; [[EscortDeck]] contain mechanisms for &amp;quot;managing&amp;quot; allied ships.&lt;br /&gt;
&lt;br /&gt;
==== Planet Surfaces ====&lt;br /&gt;
*[[Planetfall OXP]] allows landing on the planet (used by [[Feudal States]] for access to the Royal Court, and by [[Astronaut]] for space-jumping)&lt;br /&gt;
*[[Lave is Earth 8k]] contains night-time city lighting&lt;br /&gt;
&lt;br /&gt;
=== Packaging and distribution ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=16688 The All-in-One Guide to OXZ Packaging and Distribution].&lt;br /&gt;
::And see [https://bb.oolite.space/viewtopic.php?p=279034#p279034 this post] for AppleMac issues with the above.&lt;br /&gt;
* Cim created [https://github.com/cim--/oxp-build-scripts some scripts to ease packaging] a project.&lt;br /&gt;
*[[OXP Distribution]] The All-in-One Guide to OXP Packaging and Distribution (and [[OXP_standards]] for advice on which ways of doing things are supported and which are not).&lt;br /&gt;
* Since the domain change to [https://oolite.space] the distribution of expansions has changed slightly. The new version is still subject to discussions and might change again. Here is a [[Publishing Procedure Comparison]].&lt;br /&gt;
*[[Gameplay_and_Balance_Indicator|Gameplay Balance Indicator]] and [[OXP_Levelindicators|Difficulty Indicator]]. Add these to your wiki page to show effects on Game Balance and the Difficulty Level of your OXP/OXZ. The &amp;#039;&amp;#039;&amp;#039;first&amp;#039;&amp;#039;&amp;#039; indicates the impact on play (equipment making the game easier/more difficult), the &amp;#039;&amp;#039;&amp;#039;second&amp;#039;&amp;#039;&amp;#039; indicates the suggested [[Elite Rating]] needed to attempt the mission/defeat the ship &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite| ]]&lt;br /&gt;
[[Category:Oolite scripting| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=OXP&amp;diff=90300</id>
		<title>OXP</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=OXP&amp;diff=90300"/>
		<updated>2026-09-04T06:04:45Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Oops!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:oolite-oxp-icon.png|128px|right|OXP icon]]&lt;br /&gt;
An &amp;#039;&amp;#039;&amp;#039;OXP&amp;#039;&amp;#039;&amp;#039; (&amp;#039;&amp;#039;&amp;#039;O&amp;#039;&amp;#039;&amp;#039;olite e&amp;#039;&amp;#039;&amp;#039;X&amp;#039;&amp;#039;&amp;#039;pansion &amp;#039;&amp;#039;&amp;#039;P&amp;#039;&amp;#039;&amp;#039;ack) is an enhancement to the game [[Oolite]]. An OXP could be a new game object (such as a ship, space station or a moon), a mission, or a combination of several elements. OXPs can use all of the facilities of Oolite, including some that are not used in the standard, unexpanded game. Please note that if you run Oolite in &amp;#039;Strict Play&amp;#039; mode (set via pressing F2 when docked or paused and then selecting &amp;#039;Reset to Strict play&amp;#039;), OXPs are not loaded.&lt;br /&gt;
&lt;br /&gt;
An &amp;#039;&amp;#039;&amp;#039;OXZ&amp;#039;&amp;#039;&amp;#039; is an OXP in a particular &amp;#039;&amp;#039;&amp;#039;Z&amp;#039;&amp;#039;&amp;#039;ipped format to make it easier for Oolite to process and for players to install - to find out what&amp;#039;s inside one, use your unzipping tool of choice on it.&lt;br /&gt;
&lt;br /&gt;
== Finding OXPs ==&lt;br /&gt;
=== OXPs ===&lt;br /&gt;
*The &amp;#039;&amp;#039;&amp;#039;[[OXP List]]&amp;#039;&amp;#039;&amp;#039; provides the most comprehensive list of Oolite OXP expansion packs.&lt;br /&gt;
*[[Guide to Unlisted OXPs]] has another 200 or so (which are not listed elsewhere).&lt;br /&gt;
&lt;br /&gt;
These have to go into your AddOns folder (see below).&lt;br /&gt;
=== OXZs ===&lt;br /&gt;
*The [http://www.oolite.space/oxps/#oxp &amp;#039;&amp;#039;&amp;#039;OXZ List&amp;#039;&amp;#039;&amp;#039;] provides the most comprehensive list of Oolite OXZ expansion packs (but only those uploaded to the in-game Expansions Manager).&lt;br /&gt;
*Just for fun, the [[Index of artefacts]] provides the most comprehensive analysis of these Oolite OXZ expansion packs...&lt;br /&gt;
*there are just a handful of OXZs (mostly experimental, but including some excellent ones by phkb) not listed on the Expansions Manager/OXZ List. They are mostly in the [[Guide to Unlisted OXPs]] mixed in with everything else.&lt;br /&gt;
*Check out the [[Oolite Starter]] which makes management of the expansions in your Ooniverse refeshing like a sip of properly chilled gin and tonic.&lt;br /&gt;
&lt;br /&gt;
Those in the in-game Expansions Manager should go in your Managed AddOns folder. Those which are not should go in your AddOns folder. See below.&lt;br /&gt;
&lt;br /&gt;
=== Old versions ===&lt;br /&gt;
For purely historical purposes (or a touch of nostalgia if you&amp;#039;ve been around Oolite for a long time) you might want to look at [http://oosat.alioth.net The Oolite Satellite Resource Site] (&amp;#039;&amp;#039;&amp;#039;Oosat2&amp;#039;&amp;#039;&amp;#039;, quite broken but still accessible, 2006-11-04 until 2007-03-03) or the even older [http://capnhack.com/hosting/oolite/Oolite/OoSat.html Captain Hack OoSat Site] (&amp;#039;&amp;#039;&amp;#039;Oosat1&amp;#039;&amp;#039;&amp;#039;, beginning until 2006-10-14). Oosat may have originally been hosted here on Alioth.net, as was &amp;#039;&amp;#039;&amp;#039;Oldsat&amp;#039;&amp;#039;&amp;#039;. They had a tendency to go off-line or to crash, losing all information. Search on the BB if you are curious!&lt;br /&gt;
&lt;br /&gt;
For your curiosity and maybe one or the other odd find there is also the [[OXP Attic]] which houses derelict OXPs from times long past. Also see [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=20721 Recovering Lost Oxp&amp;#039;s].&lt;br /&gt;
&lt;br /&gt;
== OXPs suitable for new players ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
It is suggested that players new to the game should be careful when choosing OXPs. The basic game is extremely well-balanced and has stood the test of time, but many OXPs change the balance and dynamics of the game.&lt;br /&gt;
&lt;br /&gt;
To make an informed choice as to what OXPs you might want, you do need to understand the way the standard game works first, so it is recommended that new players should consider playing Oolite without game-changing OXPs for a while.&lt;br /&gt;
&lt;br /&gt;
However, many OXPs will just enhance eye-candy and ambience - they make the game look better, or add features which make the Oolite experience more enjoyable without affecting the way the game plays.&lt;br /&gt;
&lt;br /&gt;
To help, a [[OXP_List_for_New_Players| list of suitable OXPs for newcomers]] has been compiled. These are OXPs that will not affect gameplay but are worthwhile additions for the new player who wants a diverse and visually exciting Ooniverse. &lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
Everyone has their own idea of what OXPs should be in a starter pack, or which are just best. There are several threads on the Forum on this topic, perhaps the best-balanced and most useful for newcomers being [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=11885 this one]. &lt;br /&gt;
&lt;br /&gt;
== Suitability for simpler or for more difficult/advanced gaming ==&lt;br /&gt;
There exists a way of marking an OXP&amp;#039;s difficulty level according to the author&amp;#039;s belief. You can find the [[OXP_Levelindicators|level indicators]] on the wiki.&lt;br /&gt;
&lt;br /&gt;
Another system in progress is [[Template:IconOXP]].&lt;br /&gt;
&lt;br /&gt;
==Player recommendations==&lt;br /&gt;
These commanders have put together lists of their personal favourites:&lt;br /&gt;
*[[User:Cpt|Cpt]] (2013)&lt;br /&gt;
*[[User:JazHaz|JazHaz]] (2013)&lt;br /&gt;
*[[User:Zireael|Zireael]] (2014)&lt;br /&gt;
*[[User:Norby#Recommended_OXPs|Norby]] (2015-7): includes packages of recommended OXPs for new players, the more experienced &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
*[[User:CaptSolo|CaptSolo]] (2020)&lt;br /&gt;
&lt;br /&gt;
== Help with OXPs ==&lt;br /&gt;
&lt;br /&gt;
Information on OXPs can also be found on the [https://bb.oolite.space/viewforum.php?f=4 Expansion Pack Forum], the Friendliest Board This Side of Riedquat. The helpful people there will be happy to assist you with any questions you have about OXPs.&lt;br /&gt;
&lt;br /&gt;
== Tweaking your OXPs ==&lt;br /&gt;
Do you prefer a louder &amp;#039;&amp;#039;beep&amp;#039;&amp;#039; for audible docking clearance? Would you rather your Commander&amp;#039;s Log also recorded purchases &amp;amp; repairs? Do you want your Laser Booster to activate automatically upon launch? &lt;br /&gt;
&lt;br /&gt;
You will find recipes for modifying some of the OXPs [https://bb.oolite.space/viewtopic.php?p=216177#p216177 here].&lt;br /&gt;
&lt;br /&gt;
== Installing an OXP ==&lt;br /&gt;
&lt;br /&gt;
OXPs are installed to the folder or directory (&amp;#039;folder&amp;#039; and &amp;#039;directory&amp;#039; are synonyms) named &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039;. Read on, we will also tell you where to find that folder.&lt;br /&gt;
&lt;br /&gt;
=== In OXZ format ===&lt;br /&gt;
Download the OXZ file, and save it to your AddOns folder. &lt;br /&gt;
&lt;br /&gt;
Many OXZ format expansion packs can also be downloaded and installed for you from the [[Expansions Manager]] in Oolite. These will be placed in a separate folder which Oolite manages (&amp;#039;&amp;#039;&amp;#039;ManagedAddOns&amp;#039;&amp;#039;&amp;#039;) - any you download yourself should go in the &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039; folder so that Oolite doesn&amp;#039;t accidentally overwrite them.&lt;br /&gt;
&lt;br /&gt;
If you want to inspect an OXZ you&amp;#039;ve downloaded with the expansion pack manager, copy it out of the &amp;#039;&amp;#039;&amp;#039;ManagedAddOns&amp;#039;&amp;#039;&amp;#039; folder first, then open it with your unzipping program. Some versions of the Expansions Manager can do this for you when you press the &amp;#039;&amp;#039;x&amp;#039;&amp;#039; key.&lt;br /&gt;
&lt;br /&gt;
=== In OXP format ===&lt;br /&gt;
Typically, an OXP is downloaded as a ZIP file though occasionally other compression tools such as 7z or rar have been used. Unzip it to find a folder with a name ending .oxp&lt;br /&gt;
&lt;br /&gt;
After unzipping the file, make sure that it is &amp;#039;&amp;#039;only&amp;#039;&amp;#039; the OXP folder that put into the AddOns directory - some zipped OXPs can contain a top level folder with a readMe file, and the actual OXP folder is a level further down. If this is the case, move the folder with the &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039; extension into the AddOns folder.&lt;br /&gt;
&lt;br /&gt;
Sometimes the zipped files contain several folders, make sure you only copy the folder -or file for Macintoshes- ending with &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039; into the AddOns folder. This folder is found in different locations, depending on the platform.&lt;br /&gt;
&lt;br /&gt;
If you have followed these instructions and OXPs are not being recognised by the game make sure that your commander is a normal game. If you started your commander using the &amp;quot;Strict Mode&amp;quot; starting option, no OXPs will ever be used.&lt;br /&gt;
&lt;br /&gt;
== Locating your AddOns folder ==&lt;br /&gt;
&lt;br /&gt;
=== Mac OS X ===&lt;br /&gt;
Found in the folder that contains the Oolite application.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively you can also have the &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039; folder in your user area at &amp;#039;&amp;#039;&amp;#039;~/Library/Application&amp;amp;nbsp;Support/Oolite/AddOns/&amp;#039;&amp;#039;&amp;#039;. When both places contain an &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039; folder, both contents are read with the content in the user libraries loading last.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Troubleshooting:&amp;#039;&amp;#039;&amp;#039; If you get an error saying &amp;quot;The item could not be moved because &amp;quot;AddOns&amp;quot; cannot be modified&amp;quot;, that can happen if you weren&amp;#039;t the user that installed Oolite.&lt;br /&gt;
The solution is to put the OXPs of your choice in &amp;#039;&amp;#039;&amp;#039;~/Library/Application&amp;amp;nbsp;Support/Oolite/AddOns/&amp;#039;&amp;#039;&amp;#039; instead (you may need to create this folder).&lt;br /&gt;
The error could also be triggered because you’re running from the disk image, you’ll need to copy the game somewhere else. Having done so, if you still get the error, use the Get Info command on the AddOns folder, open the Ownership &amp;amp; Permissions pane and check that it says You Can: Read &amp;amp; Write.&lt;br /&gt;
&lt;br /&gt;
=== Linux ===&lt;br /&gt;
The location of the AddOns folder will depend on whether you chose to install Oolite to &amp;#039;Home&amp;#039; or &amp;#039;System&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
If you chose the &amp;#039;Home&amp;#039; installation, the AddOns directory is located in &amp;#039;&amp;#039;&amp;#039;~/GNUstep/Applications/Oolite/AddOns&amp;#039;&amp;#039;&amp;#039;.  The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder)  You may have to create it.&lt;br /&gt;
&lt;br /&gt;
If you chose the &amp;#039;System&amp;#039; installation, the AddOns directory will be &amp;#039;&amp;#039;&amp;#039;~/.Oolite/Add-ons&amp;#039;&amp;#039;&amp;#039;. You may have to create it. Note that this is a &amp;#039;hidden&amp;#039; directory, and so you may have to turn on &amp;#039;Show hidden files&amp;#039; in your file manager before you can see it.&lt;br /&gt;
&lt;br /&gt;
An alternative location for a &amp;#039;System&amp;#039; installation is the &amp;#039;&amp;#039;&amp;#039;/opt/Oolite/AddOns&amp;#039;&amp;#039;&amp;#039; directory, but most users find this less convenient than &amp;#039;&amp;#039;&amp;#039;~/.Oolite/Add-ons&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder). Historical: if you are using the GNUStep dedicated versions (pre-Jan 2006), then the AddOns folder must be created inside the oolite.app folder.&lt;br /&gt;
&lt;br /&gt;
== Caveats ==&lt;br /&gt;
If you purchase a ship that is an OXP ship and save the game, you will only be able to load that commander as long as this OXP is installed in AddOns. If it&amp;#039;s not, Oolite will give you an error instead of trying to load the commander.&lt;br /&gt;
&lt;br /&gt;
== Managing a stable of OXPs ==&lt;br /&gt;
Nowadays we download OXZs through the in-game Expansions Manager - and it manages them for us. But if we tweak one, it usually becomes an OXP and must then be kept in the AddOns folder. Some older oxps have yet to be turned into OXZs and some experimental OXPs are in a similar position.&lt;br /&gt;
&lt;br /&gt;
So, if you have large numbers of these oxps, see the following threads from the BB.&lt;br /&gt;
*Issues with multiple expansions? [[Find the culprit]]&lt;br /&gt;
*Issues with [https://bb.oolite.space/viewtopic.php?p=273473#p273473 single OXPs]&lt;br /&gt;
*Issues with [https://bb.oolite.space/viewtopic.php?p=273490#p273490 multiple OXPs]&lt;br /&gt;
*Issues with different copies of the game on the [https://bb.oolite.space/viewtopic.php?p=272073#p272073 same hard drive]&lt;br /&gt;
*If you found a nice set of expansions and want to share that with others, consider using the [[Oolite Starter]]. It allows you to export and send expansion sets to other players, who then can activate it on their side.&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
With some OXPs installed, the directory structure will look something like this:&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Basic-debug.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Cabal_Common_Library1.5.1.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Explorers&amp;#039;_Club_1.3.1_2012-01-21.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\halsis.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Material Test Suite v1.2.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
with other directories and files under each of the .oxp directories.  You should only find .oxp directories immediately under a \AddOns directory.&lt;br /&gt;
&lt;br /&gt;
If none of your OXPs are working, are you playing in Strict Mode? Try starting a new commander from the Normal Start and see if the OXPs work then.&lt;br /&gt;
&lt;br /&gt;
If you edit the contents of one of your OXPs and cannot see the change, restart Oolite holding down &amp;lt;Shift&amp;gt; to force Oolite to re-read all the OXP files.&lt;br /&gt;
&lt;br /&gt;
If an OXP you installed is not working or is misbehaving, check the [[Latest.log]] file - you should see a list of the OXPs you have installed.  You should see a trend in the names which will tell you if you have installed an OXP within another OXP (move it) or two versions of an OXP (remove the older one) or it is absent suggesting you put it in the wrong place or did not get the .oxp directory extension correct (did you unzip the OXP?).&lt;br /&gt;
&lt;br /&gt;
If you know how, a system-wide search for any directory ending in &amp;quot;.oxp&amp;quot; should pull up the OXPs you have installed and they should only appear immediately beneath a &amp;#039;&amp;#039;&amp;#039;\AddOns&amp;#039;&amp;#039;&amp;#039; directory and never inside another .oxp directory (this is an easily-done error when extracting a zip file).&lt;br /&gt;
&lt;br /&gt;
Note that an OXP in the AddOns folder &amp;#039;&amp;#039;trumps&amp;#039;&amp;#039; an &amp;#039;identical&amp;#039; OXZ in the ManagedAddOns folder. So if the OXP is an older version, it will [https://bb.oolite.space/viewtopic.php?p=218632#p218632 disable] the newer OXZ.&lt;br /&gt;
&lt;br /&gt;
=== AppleMacs ===&lt;br /&gt;
... Strict semicolon parsing is a Mac thing. Windows and Linux use GNUstep to parse plists and that apparently is more relaxed syntax-wise than whatever it is that the Mac uses. &lt;br /&gt;
::[[User:Another_commander|Another_commander]] from [https://bb.oolite.space/viewtopic.php?p=262814#p262814 A possible solution?] (2018).&lt;br /&gt;
&lt;br /&gt;
... the libraries in the Mac seems to be less tolerant of some things than the GNUStep libraries on Linux:&lt;br /&gt;
:*lists are enclosed in &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;(&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;)&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; with items separated by &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;,&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; and there must &amp;#039;&amp;#039;not&amp;#039;&amp;#039; be a comma after the last item in the list.&lt;br /&gt;
:*objects are enclosed in &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;{&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;}&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; and consist of pairs: &amp;lt;key&amp;gt; = &amp;lt;value&amp;gt;.&lt;br /&gt;
:*Each key/value pair must have a &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; at the end, even the last pair in the object&lt;br /&gt;
:*&amp;#039;&amp;#039;if&amp;#039;&amp;#039; the object is a value in a key/value pair in another object, it&amp;#039;s closing &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;}&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; must be followed by a &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039;.&lt;br /&gt;
::lifted from a PM from [[User:Dybal|Dybal]] (2020)&lt;br /&gt;
&lt;br /&gt;
== Creating an OXP (Notes) ==&lt;br /&gt;
[[File:Plist-XML-ASCII-ill.png|thumb|right|702px|XML (left) &amp;amp; OpenStep (right)]]&lt;br /&gt;
Legacy script comes in two versions: XML &amp;amp; OpenStep. And then there is the much more complex Javascript.&lt;br /&gt;
&lt;br /&gt;
It is intended to be easy to create expansion packs. OpenStep is relatively easy - XML and Javascript less so.&lt;br /&gt;
&lt;br /&gt;
=== Start your own OXP ===&lt;br /&gt;
&lt;br /&gt;
There are two quite extreme ways to go, and a compromise:&lt;br /&gt;
&lt;br /&gt;
* OXZs are just renamed zipped OXPs. You can decompress any existing OXZ, look inside and start tweaking.&lt;br /&gt;
* And you can start from scratch by creating everything yourself - this will take some advanced knowledge.&lt;br /&gt;
* There also is the middle path - to follow our predefined paths and use a bunch of templates.&lt;br /&gt;
&lt;br /&gt;
We have provided three varieties which your OXP can be. Advanced OXP creators can also combine them into a single OXP, while even more advanced creators keep them separate and then link them using dependencies. We&amp;#039;ll cover that later.&lt;br /&gt;
&lt;br /&gt;
So what style of OXP is on your mind? Take one of the guided tours:&lt;br /&gt;
&lt;br /&gt;
*[[Create_Ship_OXP|Ship]]&lt;br /&gt;
*[[Create_Equipment_OXP|Equipment]]&lt;br /&gt;
*[[Create_Mission_OXP|Mission]]&lt;br /&gt;
&lt;br /&gt;
Alternatively, or when curious take a look at the [[OXP howto|OXP Howto]] page for full background information. It includes a full schema of an OXP&amp;#039;s possible contents as well as links to relevant wiki pages.&lt;br /&gt;
&lt;br /&gt;
=== OXP resources ===&lt;br /&gt;
*Here is an [[index of artefacts]] already created in OXPs.&lt;br /&gt;
*[[Documenting your artefacts]] (OXP, ships and equipment)&lt;br /&gt;
*[[OXP howto]] (as mentioned above)&lt;br /&gt;
*[[Publishing your OXP]]&lt;br /&gt;
*[[:Category:Oolite scripting]]&lt;br /&gt;
*[[:Category:Oolite JavaScript Reference]]&lt;br /&gt;
&lt;br /&gt;
*[https://github.com/cim--/oxp-build-scripts OXP Packaging Scripts] Cim&amp;#039;s collection for Linux (2015)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=275434#p275434 What can OXP&amp;#039;s &amp;#039;&amp;#039;not&amp;#039;&amp;#039; change?] (2021)&lt;br /&gt;
&lt;br /&gt;
Older OXPs (from [[User:Aegidian|Aegidian]]&amp;#039;s day were written in [[Legacy Scripting]]. Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of &amp;#039;&amp;#039;&amp;#039;ECMAv5&amp;#039;&amp;#039;&amp;#039;. It is the same Spidermonkey version (1.8.5 - March 2011) that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. It is unlikely to change in the future (due to the [https://bb.oolite.space/viewtopic.php?p=256623#p256623 immense amount of work] involved in tampering with it!).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshooting ===&lt;br /&gt;
&lt;br /&gt;
Regularly check the Oolite logfile. There are two such files in your filesystem: Latest.log and Previous.log. &lt;br /&gt;
TODO: Where exactly to find them?&lt;br /&gt;
&lt;br /&gt;
In case you see Oolite complaining about parsing problems on plist files, this usually raises the question which file Oolite was parsing at that moment. There are lots of such files, and to keep logs short that information is not printed. But you can change the logging configuration. Put a logcontrol.plist file straight into your AddOns folder and Oolite will pick it up. It can be as simple as&lt;br /&gt;
&lt;br /&gt;
    {&lt;br /&gt;
        plist.information = yes;&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
== Loading Order of OXPs ==&lt;br /&gt;
OXPs loaded after other OXPs will &amp;quot;trump&amp;quot; the earlier OXPs in terms of their effects on the game. It is a similar situation with the vanilla game code, where the OXPs trump or overwrite the relevant sections of the basic oolite game. &amp;lt;br&amp;gt;&lt;br /&gt;
The loading order under Macs and Windows is alphabetical, while Linux is unpredictable. There is no solution for Linux load ordering as yet ([https://bb.oolite.space/viewtopic.php?p=261821#p261821 Svengali 2018]).&lt;br /&gt;
&lt;br /&gt;
*[[Handling OXP Dependencies with JavaScript]] - how to determine the loading order&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=189416#p189416 Nested OXP&amp;#039;s in AddOns folder] (2012)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=231750#p231750 Cim on the subject] (2015)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=8928 OXP loading order] discussion, including Ahruman on the subject (2011)&lt;br /&gt;
&lt;br /&gt;
== AddOns and Managed AddOns folders ==&lt;br /&gt;
All versions of Oolite have an AddOns folder. Only versions 1.79 (2013) and onwards have the Managed AddOns folder.&lt;br /&gt;
&lt;br /&gt;
The contents of the &amp;#039;&amp;#039;&amp;#039;AddOns folder&amp;#039;&amp;#039;&amp;#039; must &amp;#039;&amp;#039;not&amp;#039;&amp;#039; be zipped if they are to be recognised by Oolite - so OXZs will not work if they are in there.&lt;br /&gt;
&lt;br /&gt;
The contents of the &amp;#039;&amp;#039;&amp;#039;Managed AddOns&amp;#039;&amp;#039;&amp;#039; folder must contain a [[Manifest.plist]] if they are to be recognised by your [[Expansions Manager]] (or by [[Oolite Starter]]). The Expansions Manager only checks &amp;#039;&amp;#039;this&amp;#039;&amp;#039; folder, not the AddOns folder.&lt;br /&gt;
&lt;br /&gt;
== OXP Lists ==&lt;br /&gt;
*[http://www.oolite.org/oxps/ Expansion Manager OXZ list] - orderable&lt;br /&gt;
*[[OXP List]] - orderable&lt;br /&gt;
*[[Guide to Unlisted OXPs]] - with links at the bottom to older lists&lt;br /&gt;
&lt;br /&gt;
*[[Brilliant but broken...]] great oxp&amp;#039;s that need updating/fixing... (do you have the skills?)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite expansion packs]]&lt;br /&gt;
[[Category:Factual]]&lt;br /&gt;
[[Category:Oolite scripting| ]]&lt;br /&gt;
[[Category:Oolite JavaScript Reference| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=OXP&amp;diff=90299</id>
		<title>OXP</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=OXP&amp;diff=90299"/>
		<updated>2026-09-04T06:03:07Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Creating an OXP */ Added a little more&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:oolite-oxp-icon.png|128px|right|OXP icon]]&lt;br /&gt;
An &amp;#039;&amp;#039;&amp;#039;OXP&amp;#039;&amp;#039;&amp;#039; (&amp;#039;&amp;#039;&amp;#039;O&amp;#039;&amp;#039;&amp;#039;olite e&amp;#039;&amp;#039;&amp;#039;X&amp;#039;&amp;#039;&amp;#039;pansion &amp;#039;&amp;#039;&amp;#039;P&amp;#039;&amp;#039;&amp;#039;ack) is an enhancement to the game [[Oolite]]. An OXP could be a new game object (such as a ship, space station or a moon), a mission, or a combination of several elements. OXPs can use all of the facilities of Oolite, including some that are not used in the standard, unexpanded game. Please note that if you run Oolite in &amp;#039;Strict Play&amp;#039; mode (set via pressing F2 when docked or paused and then selecting &amp;#039;Reset to Strict play&amp;#039;), OXPs are not loaded.&lt;br /&gt;
&lt;br /&gt;
An &amp;#039;&amp;#039;&amp;#039;OXZ&amp;#039;&amp;#039;&amp;#039; is an OXP in a particular &amp;#039;&amp;#039;&amp;#039;Z&amp;#039;&amp;#039;&amp;#039;ipped format to make it easier for Oolite to process and for players to install - to find out what&amp;#039;s inside one, use your unzipping tool of choice on it.&lt;br /&gt;
&lt;br /&gt;
== Finding OXPs ==&lt;br /&gt;
=== OXPs ===&lt;br /&gt;
*The &amp;#039;&amp;#039;&amp;#039;[[OXP List]]&amp;#039;&amp;#039;&amp;#039; provides the most comprehensive list of Oolite OXP expansion packs.&lt;br /&gt;
*[[Guide to Unlisted OXPs]] has another 200 or so (which are not listed elsewhere).&lt;br /&gt;
&lt;br /&gt;
These have to go into your AddOns folder (see below).&lt;br /&gt;
=== OXZs ===&lt;br /&gt;
*The [http://www.oolite.space/oxps/#oxp &amp;#039;&amp;#039;&amp;#039;OXZ List&amp;#039;&amp;#039;&amp;#039;] provides the most comprehensive list of Oolite OXZ expansion packs (but only those uploaded to the in-game Expansions Manager).&lt;br /&gt;
*Just for fun, the [[Index of artefacts]] provides the most comprehensive analysis of these Oolite OXZ expansion packs...&lt;br /&gt;
*there are just a handful of OXZs (mostly experimental, but including some excellent ones by phkb) not listed on the Expansions Manager/OXZ List. They are mostly in the [[Guide to Unlisted OXPs]] mixed in with everything else.&lt;br /&gt;
*Check out the [[Oolite Starter]] which makes management of the expansions in your Ooniverse refeshing like a sip of properly chilled gin and tonic.&lt;br /&gt;
&lt;br /&gt;
Those in the in-game Expansions Manager should go in your Managed AddOns folder. Those which are not should go in your AddOns folder. See below.&lt;br /&gt;
&lt;br /&gt;
=== Old versions ===&lt;br /&gt;
For purely historical purposes (or a touch of nostalgia if you&amp;#039;ve been around Oolite for a long time) you might want to look at [http://oosat.alioth.net The Oolite Satellite Resource Site] (&amp;#039;&amp;#039;&amp;#039;Oosat2&amp;#039;&amp;#039;&amp;#039;, quite broken but still accessible, 2006-11-04 until 2007-03-03) or the even older [http://capnhack.com/hosting/oolite/Oolite/OoSat.html Captain Hack OoSat Site] (&amp;#039;&amp;#039;&amp;#039;Oosat1&amp;#039;&amp;#039;&amp;#039;, beginning until 2006-10-14). Oosat may have originally been hosted here on Alioth.net, as was &amp;#039;&amp;#039;&amp;#039;Oldsat&amp;#039;&amp;#039;&amp;#039;. They had a tendency to go off-line or to crash, losing all information. Search on the BB if you are curious!&lt;br /&gt;
&lt;br /&gt;
For your curiosity and maybe one or the other odd find there is also the [[OXP Attic]] which houses derelict OXPs from times long past. Also see [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=20721 Recovering Lost Oxp&amp;#039;s].&lt;br /&gt;
&lt;br /&gt;
== OXPs suitable for new players ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
It is suggested that players new to the game should be careful when choosing OXPs. The basic game is extremely well-balanced and has stood the test of time, but many OXPs change the balance and dynamics of the game.&lt;br /&gt;
&lt;br /&gt;
To make an informed choice as to what OXPs you might want, you do need to understand the way the standard game works first, so it is recommended that new players should consider playing Oolite without game-changing OXPs for a while.&lt;br /&gt;
&lt;br /&gt;
However, many OXPs will just enhance eye-candy and ambience - they make the game look better, or add features which make the Oolite experience more enjoyable without affecting the way the game plays.&lt;br /&gt;
&lt;br /&gt;
To help, a [[OXP_List_for_New_Players| list of suitable OXPs for newcomers]] has been compiled. These are OXPs that will not affect gameplay but are worthwhile additions for the new player who wants a diverse and visually exciting Ooniverse. &lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
Everyone has their own idea of what OXPs should be in a starter pack, or which are just best. There are several threads on the Forum on this topic, perhaps the best-balanced and most useful for newcomers being [https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=11885 this one]. &lt;br /&gt;
&lt;br /&gt;
== Suitability for simpler or for more difficult/advanced gaming ==&lt;br /&gt;
There exists a way of marking an OXP&amp;#039;s difficulty level according to the author&amp;#039;s belief. You can find the [[OXP_Levelindicators|level indicators]] on the wiki.&lt;br /&gt;
&lt;br /&gt;
Another system in progress is [[Template:IconOXP]].&lt;br /&gt;
&lt;br /&gt;
==Player recommendations==&lt;br /&gt;
These commanders have put together lists of their personal favourites:&lt;br /&gt;
*[[User:Cpt|Cpt]] (2013)&lt;br /&gt;
*[[User:JazHaz|JazHaz]] (2013)&lt;br /&gt;
*[[User:Zireael|Zireael]] (2014)&lt;br /&gt;
*[[User:Norby#Recommended_OXPs|Norby]] (2015-7): includes packages of recommended OXPs for new players, the more experienced &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
*[[User:CaptSolo|CaptSolo]] (2020)&lt;br /&gt;
&lt;br /&gt;
== Help with OXPs ==&lt;br /&gt;
&lt;br /&gt;
Information on OXPs can also be found on the [https://bb.oolite.space/viewforum.php?f=4 Expansion Pack Forum], the Friendliest Board This Side of Riedquat. The helpful people there will be happy to assist you with any questions you have about OXPs.&lt;br /&gt;
&lt;br /&gt;
== Tweaking your OXPs ==&lt;br /&gt;
Do you prefer a louder &amp;#039;&amp;#039;beep&amp;#039;&amp;#039; for audible docking clearance? Would you rather your Commander&amp;#039;s Log also recorded purchases &amp;amp; repairs? Do you want your Laser Booster to activate automatically upon launch? &lt;br /&gt;
&lt;br /&gt;
You will find recipes for modifying some of the OXPs [https://bb.oolite.space/viewtopic.php?p=216177#p216177 here].&lt;br /&gt;
&lt;br /&gt;
== Installing an OXP ==&lt;br /&gt;
&lt;br /&gt;
OXPs are installed to the folder or directory (&amp;#039;folder&amp;#039; and &amp;#039;directory&amp;#039; are synonyms) named &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039;. Read on, we will also tell you where to find that folder.&lt;br /&gt;
&lt;br /&gt;
=== In OXZ format ===&lt;br /&gt;
Download the OXZ file, and save it to your AddOns folder. &lt;br /&gt;
&lt;br /&gt;
Many OXZ format expansion packs can also be downloaded and installed for you from the [[Expansions Manager]] in Oolite. These will be placed in a separate folder which Oolite manages (&amp;#039;&amp;#039;&amp;#039;ManagedAddOns&amp;#039;&amp;#039;&amp;#039;) - any you download yourself should go in the &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039; folder so that Oolite doesn&amp;#039;t accidentally overwrite them.&lt;br /&gt;
&lt;br /&gt;
If you want to inspect an OXZ you&amp;#039;ve downloaded with the expansion pack manager, copy it out of the &amp;#039;&amp;#039;&amp;#039;ManagedAddOns&amp;#039;&amp;#039;&amp;#039; folder first, then open it with your unzipping program. Some versions of the Expansions Manager can do this for you when you press the &amp;#039;&amp;#039;x&amp;#039;&amp;#039; key.&lt;br /&gt;
&lt;br /&gt;
=== In OXP format ===&lt;br /&gt;
Typically, an OXP is downloaded as a ZIP file though occasionally other compression tools such as 7z or rar have been used. Unzip it to find a folder with a name ending .oxp&lt;br /&gt;
&lt;br /&gt;
After unzipping the file, make sure that it is &amp;#039;&amp;#039;only&amp;#039;&amp;#039; the OXP folder that put into the AddOns directory - some zipped OXPs can contain a top level folder with a readMe file, and the actual OXP folder is a level further down. If this is the case, move the folder with the &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039; extension into the AddOns folder.&lt;br /&gt;
&lt;br /&gt;
Sometimes the zipped files contain several folders, make sure you only copy the folder -or file for Macintoshes- ending with &amp;#039;&amp;#039;&amp;#039;.oxp&amp;#039;&amp;#039;&amp;#039; into the AddOns folder. This folder is found in different locations, depending on the platform.&lt;br /&gt;
&lt;br /&gt;
If you have followed these instructions and OXPs are not being recognised by the game make sure that your commander is a normal game. If you started your commander using the &amp;quot;Strict Mode&amp;quot; starting option, no OXPs will ever be used.&lt;br /&gt;
&lt;br /&gt;
== Locating your AddOns folder ==&lt;br /&gt;
&lt;br /&gt;
=== Mac OS X ===&lt;br /&gt;
Found in the folder that contains the Oolite application.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively you can also have the &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039; folder in your user area at &amp;#039;&amp;#039;&amp;#039;~/Library/Application&amp;amp;nbsp;Support/Oolite/AddOns/&amp;#039;&amp;#039;&amp;#039;. When both places contain an &amp;#039;&amp;#039;&amp;#039;AddOns&amp;#039;&amp;#039;&amp;#039; folder, both contents are read with the content in the user libraries loading last.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Troubleshooting:&amp;#039;&amp;#039;&amp;#039; If you get an error saying &amp;quot;The item could not be moved because &amp;quot;AddOns&amp;quot; cannot be modified&amp;quot;, that can happen if you weren&amp;#039;t the user that installed Oolite.&lt;br /&gt;
The solution is to put the OXPs of your choice in &amp;#039;&amp;#039;&amp;#039;~/Library/Application&amp;amp;nbsp;Support/Oolite/AddOns/&amp;#039;&amp;#039;&amp;#039; instead (you may need to create this folder).&lt;br /&gt;
The error could also be triggered because you’re running from the disk image, you’ll need to copy the game somewhere else. Having done so, if you still get the error, use the Get Info command on the AddOns folder, open the Ownership &amp;amp; Permissions pane and check that it says You Can: Read &amp;amp; Write.&lt;br /&gt;
&lt;br /&gt;
=== Linux ===&lt;br /&gt;
The location of the AddOns folder will depend on whether you chose to install Oolite to &amp;#039;Home&amp;#039; or &amp;#039;System&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
If you chose the &amp;#039;Home&amp;#039; installation, the AddOns directory is located in &amp;#039;&amp;#039;&amp;#039;~/GNUstep/Applications/Oolite/AddOns&amp;#039;&amp;#039;&amp;#039;.  The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder)  You may have to create it.&lt;br /&gt;
&lt;br /&gt;
If you chose the &amp;#039;System&amp;#039; installation, the AddOns directory will be &amp;#039;&amp;#039;&amp;#039;~/.Oolite/Add-ons&amp;#039;&amp;#039;&amp;#039;. You may have to create it. Note that this is a &amp;#039;hidden&amp;#039; directory, and so you may have to turn on &amp;#039;Show hidden files&amp;#039; in your file manager before you can see it.&lt;br /&gt;
&lt;br /&gt;
An alternative location for a &amp;#039;System&amp;#039; installation is the &amp;#039;&amp;#039;&amp;#039;/opt/Oolite/AddOns&amp;#039;&amp;#039;&amp;#039; directory, but most users find this less convenient than &amp;#039;&amp;#039;&amp;#039;~/.Oolite/Add-ons&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
The AddOns folder should be in the top level of the Oolite install directory (at the same level as the oolite.app folder). Historical: if you are using the GNUStep dedicated versions (pre-Jan 2006), then the AddOns folder must be created inside the oolite.app folder.&lt;br /&gt;
&lt;br /&gt;
== Caveats ==&lt;br /&gt;
If you purchase a ship that is an OXP ship and save the game, you will only be able to load that commander as long as this OXP is installed in AddOns. If it&amp;#039;s not, Oolite will give you an error instead of trying to load the commander.&lt;br /&gt;
&lt;br /&gt;
== Managing a stable of OXPs ==&lt;br /&gt;
Nowadays we download OXZs through the in-game Expansions Manager - and it manages them for us. But if we tweak one, it usually becomes an OXP and must then be kept in the AddOns folder. Some older oxps have yet to be turned into OXZs and some experimental OXPs are in a similar position.&lt;br /&gt;
&lt;br /&gt;
So, if you have large numbers of these oxps, see the following threads from the BB.&lt;br /&gt;
*Issues with multiple expansions? [[Find the culprit]]&lt;br /&gt;
*Issues with [https://bb.oolite.space/viewtopic.php?p=273473#p273473 single OXPs]&lt;br /&gt;
*Issues with [https://bb.oolite.space/viewtopic.php?p=273490#p273490 multiple OXPs]&lt;br /&gt;
*Issues with different copies of the game on the [https://bb.oolite.space/viewtopic.php?p=272073#p272073 same hard drive]&lt;br /&gt;
*If you found a nice set of expansions and want to share that with others, consider using the [[Oolite Starter]]. It allows you to export and send expansion sets to other players, who then can activate it on their side.&lt;br /&gt;
&lt;br /&gt;
== Diagnostics ==&lt;br /&gt;
With some OXPs installed, the directory structure will look something like this:&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Basic-debug.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Cabal_Common_Library1.5.1.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Explorers&amp;#039;_Club_1.3.1_2012-01-21.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\halsis.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
:&amp;#039;&amp;#039;&amp;#039;...\AddOns\Material Test Suite v1.2.oxp&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
with other directories and files under each of the .oxp directories.  You should only find .oxp directories immediately under a \AddOns directory.&lt;br /&gt;
&lt;br /&gt;
If none of your OXPs are working, are you playing in Strict Mode? Try starting a new commander from the Normal Start and see if the OXPs work then.&lt;br /&gt;
&lt;br /&gt;
If you edit the contents of one of your OXPs and cannot see the change, restart Oolite holding down &amp;lt;Shift&amp;gt; to force Oolite to re-read all the OXP files.&lt;br /&gt;
&lt;br /&gt;
If an OXP you installed is not working or is misbehaving, check the [[Latest.log]] file - you should see a list of the OXPs you have installed.  You should see a trend in the names which will tell you if you have installed an OXP within another OXP (move it) or two versions of an OXP (remove the older one) or it is absent suggesting you put it in the wrong place or did not get the .oxp directory extension correct (did you unzip the OXP?).&lt;br /&gt;
&lt;br /&gt;
If you know how, a system-wide search for any directory ending in &amp;quot;.oxp&amp;quot; should pull up the OXPs you have installed and they should only appear immediately beneath a &amp;#039;&amp;#039;&amp;#039;\AddOns&amp;#039;&amp;#039;&amp;#039; directory and never inside another .oxp directory (this is an easily-done error when extracting a zip file).&lt;br /&gt;
&lt;br /&gt;
Note that an OXP in the AddOns folder &amp;#039;&amp;#039;trumps&amp;#039;&amp;#039; an &amp;#039;identical&amp;#039; OXZ in the ManagedAddOns folder. So if the OXP is an older version, it will [https://bb.oolite.space/viewtopic.php?p=218632#p218632 disable] the newer OXZ.&lt;br /&gt;
&lt;br /&gt;
=== AppleMacs ===&lt;br /&gt;
... Strict semicolon parsing is a Mac thing. Windows and Linux use GNUstep to parse plists and that apparently is more relaxed syntax-wise than whatever it is that the Mac uses. &lt;br /&gt;
::[[User:Another_commander|Another_commander]] from [https://bb.oolite.space/viewtopic.php?p=262814#p262814 A possible solution?] (2018).&lt;br /&gt;
&lt;br /&gt;
... the libraries in the Mac seems to be less tolerant of some things than the GNUStep libraries on Linux:&lt;br /&gt;
:*lists are enclosed in &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;(&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;)&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; with items separated by &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;,&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; and there must &amp;#039;&amp;#039;not&amp;#039;&amp;#039; be a comma after the last item in the list.&lt;br /&gt;
:*objects are enclosed in &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;{&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;}&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; and consist of pairs: &amp;lt;key&amp;gt; = &amp;lt;value&amp;gt;.&lt;br /&gt;
:*Each key/value pair must have a &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; at the end, even the last pair in the object&lt;br /&gt;
:*&amp;#039;&amp;#039;if&amp;#039;&amp;#039; the object is a value in a key/value pair in another object, it&amp;#039;s closing &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;}&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039; must be followed by a &amp;#039;&amp;lt;font color=&amp;quot;Red&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;;&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt;&amp;#039;.&lt;br /&gt;
::lifted from a PM from [[User:Dybal|Dybal]] (2020)&lt;br /&gt;
&lt;br /&gt;
== Creating an OXP (Notes) ==&lt;br /&gt;
[[File:Plist-XML-ASCII-ill.png|thumb|right|702px|XML (left) &amp;amp; OpenStep (right)]]&lt;br /&gt;
Legacy script comes in two versions: XML &amp;amp; OpenStep. And then there is the much more complex Javascript.&lt;br /&gt;
&lt;br /&gt;
It is intended to be easy to create expansion packs. OpenStep is relatively easy - XML and Javascript less so.&lt;br /&gt;
&lt;br /&gt;
=== Start your own OXP ===&lt;br /&gt;
&lt;br /&gt;
There are two quite extreme ways to go, and a compromise:&lt;br /&gt;
&lt;br /&gt;
* OXZs are just renamed zipped OXPs. You can decompress any existing OXZ, look inside and start tweaking.&lt;br /&gt;
* And you can start from scratch by creating everything yourself - this will take some advanced knowledge.&lt;br /&gt;
* There also is the middle path - to follow our predefined paths and use a bunch of templates.&lt;br /&gt;
&lt;br /&gt;
We have provided three varieties which your OXP can be. Advanced OXP creators can also combine them into a single OXP, while even more advanced creators keep them separate and then link them using dependencies. We&amp;#039;ll cover that later.&lt;br /&gt;
&lt;br /&gt;
So what style of OXP is on your mind? Take one of the guided tours:&lt;br /&gt;
&lt;br /&gt;
*[[Create_Ship_OXP|Ship]]&lt;br /&gt;
*[[Create_Equipment_OXP|Equipment]]&lt;br /&gt;
*[[Create_Mission_OXP|Mission]]&lt;br /&gt;
&lt;br /&gt;
Alternatively, or when curious take a look at the [[OXP howto|OXP Howto]] page for full background information. It includes a full schema of an OXP&amp;#039;s possible contents as well as links to relevant wiki pages.&lt;br /&gt;
&lt;br /&gt;
=== OXP resources ===&lt;br /&gt;
*Here is an [[index of artefacts]] already created in OXPs.&lt;br /&gt;
*[[Documenting your artefacts]] (OXP, ships and equipment)&lt;br /&gt;
*[[OXP howto]] (as mentioned above)&lt;br /&gt;
*[[Publishing your OXP]]&lt;br /&gt;
*[[Category:Oolite scripting]]&lt;br /&gt;
*[[Category:Oolite JavaScript Reference]]&lt;br /&gt;
&lt;br /&gt;
*[https://github.com/cim--/oxp-build-scripts OXP Packaging Scripts] Cim&amp;#039;s collection for Linux (2015)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=275434#p275434 What can OXP&amp;#039;s &amp;#039;&amp;#039;not&amp;#039;&amp;#039; change?] (2021)&lt;br /&gt;
&lt;br /&gt;
Older OXPs (from [[User:Aegidian|Aegidian]]&amp;#039;s day were written in [[Legacy Scripting]]. Modern OXPs are written in JavaScript. Specifically oolite.jsVersion 185, an Oolite specific variant of &amp;#039;&amp;#039;&amp;#039;ECMAv5&amp;#039;&amp;#039;&amp;#039;. It is the same Spidermonkey version (1.8.5 - March 2011) that Firefox 4 shipped with many years ago, but it is a special build for Oolite. This is the version that we have almost always had and it has not changed between versions of the game. It is unlikely to change in the future (due to the [https://bb.oolite.space/viewtopic.php?p=256623#p256623 immense amount of work] involved in tampering with it!).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshooting ===&lt;br /&gt;
&lt;br /&gt;
Regularly check the Oolite logfile. There are two such files in your filesystem: Latest.log and Previous.log. &lt;br /&gt;
TODO: Where exactly to find them?&lt;br /&gt;
&lt;br /&gt;
In case you see Oolite complaining about parsing problems on plist files, this usually raises the question which file Oolite was parsing at that moment. There are lots of such files, and to keep logs short that information is not printed. But you can change the logging configuration. Put a logcontrol.plist file straight into your AddOns folder and Oolite will pick it up. It can be as simple as&lt;br /&gt;
&lt;br /&gt;
    {&lt;br /&gt;
        plist.information = yes;&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
== Loading Order of OXPs ==&lt;br /&gt;
OXPs loaded after other OXPs will &amp;quot;trump&amp;quot; the earlier OXPs in terms of their effects on the game. It is a similar situation with the vanilla game code, where the OXPs trump or overwrite the relevant sections of the basic oolite game. &amp;lt;br&amp;gt;&lt;br /&gt;
The loading order under Macs and Windows is alphabetical, while Linux is unpredictable. There is no solution for Linux load ordering as yet ([https://bb.oolite.space/viewtopic.php?p=261821#p261821 Svengali 2018]).&lt;br /&gt;
&lt;br /&gt;
*[[Handling OXP Dependencies with JavaScript]] - how to determine the loading order&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=189416#p189416 Nested OXP&amp;#039;s in AddOns folder] (2012)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=231750#p231750 Cim on the subject] (2015)&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=8928 OXP loading order] discussion, including Ahruman on the subject (2011)&lt;br /&gt;
&lt;br /&gt;
== AddOns and Managed AddOns folders ==&lt;br /&gt;
All versions of Oolite have an AddOns folder. Only versions 1.79 (2013) and onwards have the Managed AddOns folder.&lt;br /&gt;
&lt;br /&gt;
The contents of the &amp;#039;&amp;#039;&amp;#039;AddOns folder&amp;#039;&amp;#039;&amp;#039; must &amp;#039;&amp;#039;not&amp;#039;&amp;#039; be zipped if they are to be recognised by Oolite - so OXZs will not work if they are in there.&lt;br /&gt;
&lt;br /&gt;
The contents of the &amp;#039;&amp;#039;&amp;#039;Managed AddOns&amp;#039;&amp;#039;&amp;#039; folder must contain a [[Manifest.plist]] if they are to be recognised by your [[Expansions Manager]] (or by [[Oolite Starter]]). The Expansions Manager only checks &amp;#039;&amp;#039;this&amp;#039;&amp;#039; folder, not the AddOns folder.&lt;br /&gt;
&lt;br /&gt;
== OXP Lists ==&lt;br /&gt;
*[http://www.oolite.org/oxps/ Expansion Manager OXZ list] - orderable&lt;br /&gt;
*[[OXP List]] - orderable&lt;br /&gt;
*[[Guide to Unlisted OXPs]] - with links at the bottom to older lists&lt;br /&gt;
&lt;br /&gt;
*[[Brilliant but broken...]] great oxp&amp;#039;s that need updating/fixing... (do you have the skills?)&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite expansion packs]]&lt;br /&gt;
[[Category:Factual]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Category:Oolite_JavaScript_Reference_Templates&amp;diff=90298</id>
		<title>Category:Oolite JavaScript Reference Templates</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Category:Oolite_JavaScript_Reference_Templates&amp;diff=90298"/>
		<updated>2026-09-04T06:02:03Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Tagged as Oolite JavaScript Reference&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Templates to simplify linking to [[:Category:Oolite JavaScript Reference|Oolite JavaScript Reference]] pages.&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite JavaScript Reference| ]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Simon_Challands&amp;diff=90297</id>
		<title>Simon Challands</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Simon_Challands&amp;diff=90297"/>
		<updated>2026-09-03T10:05:08Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added more detail&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Simon Challands has written several stories set in the [[Classic Elite]] universe. He is the author of the [http://elite.acornarcade.com/index.htm Acorn Elite website] (Last update - 2009).&lt;br /&gt;
&lt;br /&gt;
== Stories ==&lt;br /&gt;
* [[Aftermath]] - the result of the theft of the Constrictor (taken from http://elite.acornarcade.com/archive/aftall.htm which includes occasional footnotes)&lt;br /&gt;
* [http://elite.acornarcade.com/archive/calmcha.htm Calm and Chaos] - a very short piece following a journey&lt;br /&gt;
* [http://elite.acornarcade.com/archive/price/priceall.htm The Price of the Elite] - the discovery of a disk in the desert of Qudira&lt;br /&gt;
&lt;br /&gt;
[[Category:Authors]]&lt;br /&gt;
[[Category:Elite stories]]&lt;br /&gt;
&lt;br /&gt;
{{Stub}}&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Sector2/Orarra&amp;diff=90296</id>
		<title>Sector2/Orarra</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Sector2/Orarra&amp;diff=90296"/>
		<updated>2026-09-03T09:35:41Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Fiction */ Added a quote&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{System|Name=Orarra|Sector=2|System=193|XPos=144|YPos=33|Location=in the medium twelve o&amp;#039;clock direction|Government=6|Economy=1|Techlevel=10|Population=4.4|Inhabitants=Human Colonials|Productivity=31680|PlanetRadius=5264|MapX=144|MapY=16}}&lt;br /&gt;
&amp;lt;!-- Copy and edit the following box for a smaller &amp;quot;System Box&amp;quot; for fictions or OXPs&lt;br /&gt;
{{SmallSystem|Name=Orarra|Sector=2|System=193|XPos=144|YPos=33|Location=in the medium twelve o&amp;#039;clock direction|Government=6|Economy=1|Techlevel=10|Population=4.4|Inhabitants=Human Colonials|Productivity=31680|PlanetRadius=5264}}&lt;br /&gt;
End of the small system box --&amp;gt;&lt;br /&gt;
{{GalacticCatalogueEntry|Name=Orarra|Sector=2|System=193|Description=This planet is very well known for vicious Zast brew and its exotic goat soup.}}&lt;br /&gt;
== Witchspace Routes ==&lt;br /&gt;
There are 8 direct Witchspace Routes from/to Orarra:&lt;br /&gt;
{{WitchspaceHeader}}&lt;br /&gt;
{{WitchspaceEntry|Name=Tezaeded|Sector=2|System=39|Distance=4.0|Government=7|Economy=0|Techlevel=15|Population=6.4|Productivity=56320|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Esdi|Sector=2|System=67|Distance=5.2|Government=5|Economy=3|Techlevel=8|Population=3.7|Productivity=18648|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Usleri|Sector=2|System=118|Distance=6.8|Government=5|Economy=4|Techlevel=7|Population=3.4|Productivity=14688|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Tiriusri|Sector=2|System=126|Distance=2.4|Government=1|Economy=6|Techlevel=5|Population=2.4|Productivity=3840|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Zatebiso|Sector=2|System=204|Distance=5.6|Government=4|Economy=3|Techlevel=8|Population=3.6|Productivity=16128|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Abege|Sector=2|System=221|Distance=6.4|Government=4|Economy=3|Techlevel=7|Population=3.2|Productivity=14336|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Zageuser|Sector=2|System=236|Distance=6.4|Government=4|Economy=6|Techlevel=4|Population=2.3|Productivity=5888|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Esgebi|Sector=2|System=240|Distance=3.2|Government=2|Economy=1|Techlevel=8|Population=3.2|Productivity=13824|Routes=}}&lt;br /&gt;
{{WitchspaceFooter}}&lt;br /&gt;
{{LocalAreaMapHeader|Name=Orarra|Sector=2|X=144|Y=33|Radius=4}}{{LocalAreaMapEntry|Name=Tezaeded|RX=7|RY=-17|Radius=5}}{{LocalAreaMapEntry|Name=Esdi|RX=-12|RY=-14|Radius=4}}{{LocalAreaMapEntry|Name=Usleri|RX=4|RY=35|Radius=4}}{{LocalAreaMapEntry|Name=Tiriusri|RX=2|RY=-13|Radius=4}}{{LocalAreaMapEntry|Name=Zatebiso|RX=-11|RY=18|Radius=4}}{{LocalAreaMapEntry|Name=Abege|RX=16|RY=2|Radius=5}}{{LocalAreaMapEntry|Name=Zageuser|RX=16|RY=-3|Radius=4}}{{LocalAreaMapEntry|Name=Esgebi|RX=8|RY=0|Radius=4}}{{LocalAreaMapFooter}}&lt;br /&gt;
== Trade ==&lt;br /&gt;
{{PricelistEconomy1}}&lt;br /&gt;
== OXPs ==&lt;br /&gt;
=== Famous Planets 2.5 ===&lt;br /&gt;
[[image:Orarra (Animation).gif|right]]This planet is very well known for vicious Zast brew and its exotic goat soup. Zast brew is number seventy five on the list of the Ooniverse&amp;#039;s top one hundred list of dangerous narcotics as compiled by the [[Tionisla Chronicle Array|Tionisla Chronicle]]. By drinking it people think they can step into other parallel worlds. This mental state can last days and is considered highly dangerous. The goat soup, by comparison, is very innocent. When you make planetfall in one of the cities along the beautiful blue oceans you are recommended to try this before the main dinner. ([[Famous Planets OXP]])[[Category:Famous Planets|Orarra]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Galactic Navy ===&lt;br /&gt;
[[Image:Sector2 Navy Sector Command 8 SmallNavySectorMap.png|right]]The Orarra system falls under the responsibility of the [[Sector2/Navy Command Station 8|Navy Command Station 8]] in [[Sector2/Atzaxe|Atzaxe]], two hops away. The shortest witchspace path to ComSec Station 8 in Atzaxe is Orarra -(5.6LY)-&amp;gt; [[Sector2/Zatebiso|Zatebiso]] -(4.4LY)-&amp;gt; Atzaxe. ([[Galactic Navy OXP]])&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Fiction ==&lt;br /&gt;
=== Aftermath ===&lt;br /&gt;
Orrara features in [[Simon Challands]]&amp;#039; novel [[Aftermath]] which is set in the universe of [[Classic Elite]]. The planet and several orbital stations are described therein:&lt;br /&gt;
&lt;br /&gt;
  The planet Orarra was a scorched red-brown disc in the distance, burnt by its distant and hot sun...&lt;br /&gt;
  ...&lt;br /&gt;
  The planet was reached without incident, and before long the task group was sitting in the quiet bar of the hotel where accommodation had been provided for them in the station Dodec Four. There were four stations orbiting the planet...&lt;br /&gt;
  Emily Barbeth was the member of the team to visit Orarra Station Three. Early next morning a shuttle flew her over. Moving away from the landing platform towards the information displays lining the walls at its back was a map of the station. The stations were built as a standard shell with the essential facilities included but the rest of the interior differed depending upon the local needs and resources. The headquarters of the Orarra Corporation, who controlled all interstellar trade at the planet, were located some distance away at the address of Carrock House, Sarros Square, Facet 4. Outside the spaceport and its jostling crowds of humans and aliens Barbeth found a taxi to take her there. The small autonomous vessel lifted off into the central void of the station. The walls and ceiling of the taxi were transparent and through them the interior of the station was an impressive, if dizzying sight. Straight above, three quarters of a mile distant the interior of the opposite face was a blaze of light in the sky. Curving around to meet it were walls no less impressive. The pentagonal facets of the station were difficult to discern under their covering of buildings, parks and farmland and the appearance was more of the interior of a sphere. The Dodo and Coriolis space stations found in orbit around all planets of the Galactic Co-Operative were more than just trading posts, they were small worlds in their own right.&lt;br /&gt;
  The taxi was heading towards one of the &amp;quot;walls&amp;quot;. Since it was station daytime the whole interior was well illuminated, but the dense network of lighting still made the area ahead show up as being a largely built-up area. Numerous other taxi craft darted to and fro from the complex to the rest of the station, amidst them was the occasional larger bus or supply van.&lt;br /&gt;
  The taxi landed in a square in front of Carrock House. It was an imposing building as befitted the importance of the organisation it housed. Flags from poles jutting out the front proudly displayed the Corporation logo and its name was emblazoned above the doorway.&lt;br /&gt;
  Inside the building Barbeth was greeted with the usual unimaginative &amp;quot;How can I help you?&amp;quot; from the receptionist in the foyer...&lt;br /&gt;
&lt;br /&gt;
=== Routes and Regions ===&lt;br /&gt;
==== Spaceway L2 ====&lt;br /&gt;
The [[Sector2/Spaceway L2 (Route)|Spaceway L2]] passes through this system, coming from [[Sector2/Zatebiso|Zatebiso]] and going to [[Sector2/Esgebi|Esgebi]].&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== The Traders Almanach ===&lt;br /&gt;
{{QuoteText|Text=If the limiting factor is the size of the cargo bay, you&amp;#039;ve got to get the best gain per unit, so buy memory banks or hand-made Orarran sculptures and ship them to Tiriusri or Zageuser. And those memory banks are quite nice, giving you a rake-off of 28 Credits per unit. Besides, those memory banks can also be sold well enough in Usleri. For bounty and glory try Tiriusri, where dreadful brigands have been reported.|Source=(Excerpt from: [[The Traders Almanach]] entry for 2:193)}}&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Sector1/Xeer&amp;diff=90295</id>
		<title>Sector1/Xeer</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Sector1/Xeer&amp;diff=90295"/>
		<updated>2026-09-03T09:29:59Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Aftermath (Simon Challands) */ Added quote&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{System|Name=Xeer|Sector=1|System=150|XPos=141|YPos=116|Location=in the center|Government=6|Economy=4|Techlevel=8|Population=3.9|Inhabitants=Large Yellow Bug-eyed Frogs|Productivity=18720|PlanetRadius=2957|MapX=141|MapY=58}}&lt;br /&gt;
&amp;lt;!-- Copy and edit the following box for a smaller &amp;quot;System Box&amp;quot; for fictions or OXPs&lt;br /&gt;
{{SmallSystem|Name=Xeer|Sector=1|System=150|XPos=141|YPos=116|Location=in the center|Government=6|Economy=4|Techlevel=8|Population=3.9|Inhabitants=Large Yellow Bug-eyed Frogs|Productivity=18720|PlanetRadius=2957}}&lt;br /&gt;
End of the small system box --&amp;gt;&lt;br /&gt;
{{GalacticCatalogueEntry|Name=Xeer|Sector=1|System=150|Description=This world is very well known for Xeerian wolf meat and its fabulous cuisine.}}&lt;br /&gt;
Not to be confused with [[Sector7/Xeer]]!&lt;br /&gt;
== Witchspace Routes ==&lt;br /&gt;
There are 7 direct Witchspace Routes from/to Xeer:&lt;br /&gt;
{{WitchspaceHeader}}&lt;br /&gt;
{{WitchspaceEntry|Name=Reesdice|Sector=1|System=36|Distance=4.0|Government=4|Economy=5|Techlevel=6|Population=3.0|Productivity=9600|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Esusti|Sector=1|System=62|Distance=3.2|Government=4|Economy=1|Techlevel=10|Population=4.2|Productivity=24192|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Erbiti|Sector=1|System=110|Distance=2.8|Government=0|Economy=2|Techlevel=6|Population=2.3|Productivity=5888|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Xezaor|Sector=1|System=198|Distance=2.0|Government=2|Economy=0|Techlevel=11|Population=4.3|Productivity=20640|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Edorte|Sector=1|System=200|Distance=6.0|Government=7|Economy=5|Techlevel=10|Population=4.9|Productivity=21560|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Solageon|Sector=1|System=230|Distance=4.0|Government=2|Economy=6|Techlevel=6|Population=2.9|Productivity=5568|Routes=}}&lt;br /&gt;
{{WitchspaceEntry|Name=Aruszati|Sector=1|System=237|Distance=4.8|Government=6|Economy=3|Techlevel=10|Population=4.6|Productivity=25760|Routes=}}&lt;br /&gt;
{{WitchspaceFooter}}&lt;br /&gt;
{{LocalAreaMapHeader|Name=Xeer|Sector=1|X=141|Y=116|Radius=3}}{{LocalAreaMapEntry|Name=Reesdice|RX=8|RY=-15|Radius=5}}{{LocalAreaMapEntry|Name=Esusti|RX=-8|RY=5|Radius=4}}{{LocalAreaMapEntry|Name=Erbiti|RX=7|RY=6|Radius=3}}{{LocalAreaMapEntry|Name=Xezaor|RX=5|RY=-4|Radius=4}}{{LocalAreaMapEntry|Name=Edorte|RX=-2|RY=-31|Radius=4}}{{LocalAreaMapEntry|Name=Solageon|RX=-6|RY=18|Radius=4}}{{LocalAreaMapEntry|Name=Aruszati|RX=5|RY=23|Radius=4}}{{LocalAreaMapFooter}}&lt;br /&gt;
== Trade ==&lt;br /&gt;
{{PricelistEconomy4|FoodNote=Xeerian wolf meat}}&lt;br /&gt;
&lt;br /&gt;
== OXPs ==&lt;br /&gt;
&lt;br /&gt;
=== Famous Planets ===&lt;br /&gt;
[[image:Xeer (Animation).gif|right]]The planet Xeer is completely covered with ice. Like [[Sector1/Beusrior|Beusrior]], surface tempratures range between -20C and -60C. Every year Xeer hosts an ice-sports festival. This world is very well known for Xeerian Wolf meat and its fabulous cuisine. ([[Famous Planets OXP]]) [[Category:Famous Planets|Xeer]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Galactic Navy ===&lt;br /&gt;
{{GalacticNavySecComSign|Name=Xeer|Sector=1|NavySector=8}}&lt;br /&gt;
{{GalacticNavySecComMap|Name=Xeer|Sector=1|NavySector=8}}&lt;br /&gt;
Xeer is home to the [[Sector1/Navy Command Station 8|Navy Command Station 8]]. It controls a part of the center of the Galaxy Sector 1. ([[Galactic Navy OXP]])&lt;br /&gt;
[[Category:Galactic Navy|Xeer]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Her Imperial Majesty&amp;#039;s Space Navy ==&lt;br /&gt;
[[Her Imperial Majesty&amp;#039;s Space Navy|HIMSN]] maintains a somewhat secret shipyard here, doing important naval research.&lt;br /&gt;
&lt;br /&gt;
== Fiction ==&lt;br /&gt;
*[[Rattle Cutter|Xeer Citizens Concern Over Weapons Proliferation]]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=296979#p296979 Xeerian Wolf meat] (Captain Beatnik, 2024)&lt;br /&gt;
=== Aftermath (Simon Challands) ===&lt;br /&gt;
[[Aftermath]] features a short description of the Xeer naval dockyards. It is [[Classic Elite]] Fiction by [[Simon Challands]].&lt;br /&gt;
&lt;br /&gt;
  The giant gantries and arms of the Xeer New Devonport Naval Docks were seen drifting by as the the craft was slowly manoeuvered towards clear space. Xeer was a major naval base and shipyard and was bustling with more activity than would usually be seen outside the busiest civilian space station. To the left the skeletons of three half-completed Asp MkIIs lay enclosed by a web of metal. Small points of light showed where robotic construction equipment worked on the ships. On the opposite side was a squadron of new Sidewinder Scout craft that had just arrived from Onrira Orbital. Alongside them was one of the Sidewinder&amp;#039;s heavier squadron leader ships, the Bushmaster (an oversight in its naming resulted in it being given the identical designation to the common mining vessel).&lt;br /&gt;
  The transport cleared the structure of the central shipyard station, bringing into view the planet of Xeer itself, a huge crescent below. On the visible slice grey cloud covered the plains from which most of the planet&amp;#039;s agricultural wealth was obtained. A few concentrations of light could be seen in the dark area, mostly cities but two of the odder-appearing ones were the result of huge numbers of luminescent marine creatures that accumulated at two nights of every year making one of the more impressive natural sights in the galaxy. Up in space a Coriolis station span near to the main yard. This was where some of the more secret construction projects took place. It was rumoured that the Navy were developing their remote- controlled fighter in there, and other secret ships had certainly been built within it...&lt;br /&gt;
&lt;br /&gt;
=== Routes and Regions ===&lt;br /&gt;
==== Spaceway L3 ====&lt;br /&gt;
[[Image:Sector1 Spaceway L3 SmallRouteMap.png|right|Spaceway L3]]The [[Sector1/Spaceway L3 (Route)|Spaceway L3]] passes through this system, coming from [[Sector1/Esusti|Esusti]] and going to [[Sector1/Xezaor|Xezaor]]. [[Category:Sector1/Spaceway L3|Xeer]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== GalCenter G1 ====&lt;br /&gt;
Xeer is a member of the [[Sector1/GalCenter G1 (Region)|GalCenter G1]] region. [[Category:Sector1/GalCenter G1|Xeer]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== The Traders Almanach ===&lt;br /&gt;
{{QuoteText|Text=When cash matters more than cargo capacity, I give you this advice: You can&amp;#039;t make a mistake with buying Xeerian sushi dinners here. You&amp;#039;ve got the choice to move them to Xezaor with a plus of 70 to 80%, with Esusti being the second choice in destinations and Erbiti last. You see, wherever you go to from here, there is money to be made. Of lately, there have been piracy reports from Erbiti.|Source=(Excerpt from: [[The Traders Almanach]] entry for 1:150)}}&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Bushmaster_(disambiguation)&amp;diff=90294</id>
		<title>Bushmaster (disambiguation)</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Bushmaster_(disambiguation)&amp;diff=90294"/>
		<updated>2026-09-03T09:26:10Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:IA bushmaster3.jpg|thumb|200px|right|Iron Ass Bushmaster]]&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;Bushmaster&amp;#039;&amp;#039;&amp;#039; is a classic ship (usually a mining ship) that first appeared in Archimedes Elite&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Bushmaster&amp;#039;&amp;#039;&amp;#039; may refer to:&lt;br /&gt;
&lt;br /&gt;
* [[Bushmaster (classic)]], the Bushmaster from Elite 2&lt;br /&gt;
* [[Bushmaster (ArcElite)]], the Bushmaster Miner from ArcElite&lt;br /&gt;
* [[Bushmaster (Oolite)]], the various renditions that appear in Oolite&lt;br /&gt;
* Bushmaster as it appears in [[Griff ArcElite]]&lt;br /&gt;
* Bushmaster as it appears in the OXPs [[Old Ships OXP|Old Ships]] and [[Old Ships 2010]]&lt;br /&gt;
* Neolite Bushmaster, as found among the [[Neolite Ships]]&lt;br /&gt;
* Iron Ass Bushmaster, as found in the [[Iron Ass OXP]] Vol.2&lt;br /&gt;
&lt;br /&gt;
Note that [[Simon Challands]]&amp;#039; novel [[Aftermath]] adds an additional &amp;#039;&amp;#039;navy&amp;#039;&amp;#039; &amp;quot;Bushmaster&amp;quot;, a heavier squadron leader ship.&lt;br /&gt;
&lt;br /&gt;
[[Category:Disambiguation pages]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Astrogation_Console&amp;diff=90293</id>
		<title>Astrogation Console</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Astrogation_Console&amp;diff=90293"/>
		<updated>2026-09-02T08:14:56Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Links */ Added another&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Astrogation Console====&lt;br /&gt;
[[Image:Astro-console-gray.png|300px|right]]&lt;br /&gt;
The DL-A396 Astrogator Console is a fully integrated unit, and was retrofitted to most spaceframes between 3155 and 3159.  It is now the standard console type used by [[GalCop]] vessels, including those of the [[Galactic Navy]].&lt;br /&gt;
&lt;br /&gt;
The console features several multifunction displays [[MFD]]s and customisable controls.  The manufacturer, [[Aegidian Industries|Williams Avionics]], supplies the console with a default layout template, but users can customise the controls and displays as necessary.  The only display that retains a definite style is the local space scanner.&lt;br /&gt;
&lt;br /&gt;
The astrogator console is the interface to the astrogation computer that takes over the majority of the ship&amp;#039;s navigation controls. The most recent unit, introduced in 3170, is the Socam 103, which includes all the standard controls along with advanced thruster control, a more advanced AI and a newly updated personality interface. &lt;br /&gt;
&lt;br /&gt;
Standard responsibilities of the astrogation system are:&lt;br /&gt;
* Handling of relativistic space flight: advanced routines &amp;#039;hide&amp;#039; the relativistic aspect of real space flight from the pilot, presenting a simple dive/climb/roll control method and a simplified acceleration and deceleration control related to the primary stellar body in the vicinity of the ship.&lt;br /&gt;
* Docking procedures once within a space station.&lt;br /&gt;
* Basic IFF interrogation with nearby vessels.&lt;br /&gt;
* Tracking of stellar objects.&lt;br /&gt;
* Orientation and positioning for witchspace transit (formerly handled by the Orbitspace Authority on a manual basis).&lt;br /&gt;
&lt;br /&gt;
Note that any references to controls within this manual will refer to the default layout of the console controls as supplied by Williams Avionics. Also note that each control has been assigned a verbal command through the AI, and unless you have disabled this option you may use the appropriately assigned command.&lt;br /&gt;
&lt;br /&gt;
[[File:Streamdeck Regular Combat.png|thumb|right|320px|a buttonbox]]&lt;br /&gt;
[[File:Arquebus&amp;#039;s Touch Portal.png|thumb|right|320px|TouchPortal customised for Oolite]]&lt;br /&gt;
[[File:Roolite HUD 1.jpg|thumb|right|320px|Presti70&amp;#039;s Steel Battalion VT Controller]]&lt;br /&gt;
[[File:Roolite HUD.jpg|thumb|right|320px|Special cardboard print-out for Roolite]]&lt;br /&gt;
&lt;br /&gt;
=== Alterations ===&lt;br /&gt;
Note that it is possible to alter the key-bindings on your console. See [[Keyboard Issues]] for more detail.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
*[[Pilot&amp;#039;s Reference Manual]]&lt;br /&gt;
*[[Ship&amp;#039;s Library OXP]] (itself optional optional equipment!) contains Cim&amp;#039;s in-game &amp;#039;&amp;#039;&amp;#039;Ship&amp;#039;s Manual&amp;#039;&amp;#039;&amp;#039; readable on an [[MFD]] in-flight&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
*[[Keyboard Issues]] - problems with using your astrogation console&lt;br /&gt;
*[[Priming Equipment]] - operating optional OXP equipment&lt;br /&gt;
*[[Joysticks and Gamepads]]&lt;br /&gt;
*[[Buttonboxes]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
[[File:One armed man-0990.jpg|320px]][[File:One armed man-0999.jpg|320px]][[File:One armed man-0988.jpg|320px]]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=19423 Any luck with multiple (viewport) monitors?] (2018-21) Building a Cobra&amp;#039;s astrogation console for the younger generation&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
[[File:Maik&amp;#039;s Second Monitor.png|320px]]&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=4&amp;amp;t=20899 External Dashboards] (2021) Maik&amp;#039;s creation of a second dashboard using raspberry pi&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
*Musings on adding more consoles:&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?p=274564#p274564 uses for a second monitor] (2021)&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?p=275198#p275198 things to do en-route from Witchpoint to Station] (2021)&lt;br /&gt;
::[https://bb.oolite.space/viewtopic.php?t=1444 OT? Oolite simpit] (2006)&lt;br /&gt;
&lt;br /&gt;
*Vaguely related&lt;br /&gt;
::[[Oolite Voice Control]] - For Windows only (uses glovePIE)&lt;br /&gt;
&lt;br /&gt;
{{NavBox - Oolite Equipment}}[[Category:Equipment]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Category:Help_pages&amp;diff=90292</id>
		<title>Category:Help pages</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Category:Help_pages&amp;diff=90292"/>
		<updated>2026-08-31T13:10:46Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: /* Immersive Help */ Added Mr Gimlet&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;font size=&amp;quot;5&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;Collection of Help pages for playing [[Oolite]]&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Oolite-336.png|600px|right]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
 *For playing [[:Category:Classic|Classic Elite]], [[:Category:FE2|FE2]] &amp;amp; [[:Category:FFE|FFE]] see those respective categories for &amp;#039;&amp;#039;their&amp;#039;&amp;#039; help pages.&lt;br /&gt;
 *For help with [[The Dark Side]] - see [[:Category:Oolite scripting]] for more information.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;Note that three different Ship&amp;#039;s Manuals are on offer&amp;#039;&amp;#039; &lt;br /&gt;
:The Ship&amp;#039;s Manual in the [[Ship&amp;#039;s Library OXP]] is the most recent &lt;br /&gt;
::(&amp;#039;&amp;#039;and&amp;#039;&amp;#039; is readable in-game - &amp;#039;&amp;#039;and&amp;#039;&amp;#039; is adjusted to your ship &amp;#039;&amp;#039;and&amp;#039;&amp;#039; to your keyboard!)&lt;br /&gt;
:The [[Pilot&amp;#039;s Reference Manual]] was written for the Oolite Cobra  MkIII&lt;br /&gt;
:[[The Space Traders Flight Training Manual]] was written for the Classic Elite Cobra MkIII but is still good.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
The in-game [[Tutorial]] &amp;amp; the in-game [[Expansions Manager]] have their own explanatory wiki pages.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;Please note that your game download includes [[Mr Gimlet]]&amp;#039;s advice to new pilots and the RS Reference Sheet&amp;#039;&amp;#039;: (search for &amp;#039;&amp;#039;&amp;#039;OoliteRS&amp;#039;&amp;#039;&amp;#039; - stashed away in the entrails of your computer - or 2008 version - [[File:OoliteRS rev1.8.zip]]): it is well worth printing out.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
== Old Help ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=56825#p56825 Manual for Oolite v.1.65] (polyh, 2008): the major changes in Oolite game-play since 2008 involve tougher combat and more pirates in the safer systems which close to pirate dens in anarchies and such.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Videos ==&lt;br /&gt;
&lt;br /&gt;
=== Oolite v.1.90 ===&lt;br /&gt;
*[https://www.youtube.com/watch?v=yaoU-8jwsF0&amp;amp;list=PLsYaAtYv_5eWQDkMVZ9EPK5TGdzIkVse3 Oolite 1.90 - Let&amp;#039;s Play Poorly - Season 1]&lt;br /&gt;
*[https://www.youtube.com/watch?v=PxQFUETEQqk&amp;amp;list=PLsYaAtYv_5eUpD3FBWQk7XQuKQQsrVhNV Oolite unmodded - Let&amp;#039;s Play Poorly] (demonstrating the [[Strict Game]])&lt;br /&gt;
*[https://www.youtube.com/watch?v=iKrvCMK306U&amp;amp;list=PLsYaAtYv_5eW0rdcLg5foPSMk5an1-e8i Oolite 1.90 - Let&amp;#039;s Play Poorly - Season 2]&lt;br /&gt;
=== Oolite v.1.76 ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=10454 Links to 12 videos featuring oxp-laden Oolite] (2012/3) Flying a python.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Helpful OXPs for new pilots ==&lt;br /&gt;
There is a &amp;#039;&amp;#039;lot&amp;#039;&amp;#039; of information in Oolite. These vital OXPs help give you access to the information you need to play/enjoy the game&lt;br /&gt;
&lt;br /&gt;
*[[Hints]] allows you to eavesdrop on more experienced pilots in the station bars. Tips on combat tactics, trade, buying equipment, fighting off Thargoids or pirates, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
*[[Contextual Help]]&lt;br /&gt;
&lt;br /&gt;
*[[Addons for Beginners (Vital Statistics)]] will download the following&lt;br /&gt;
:*[[Ship&amp;#039;s Library]] (with ship&amp;#039;s manual)&lt;br /&gt;
:*[[XenonUI]] (handy guide to the buttons on your astrogation console)&lt;br /&gt;
:*[[Technical Reference Library]] identifies ships when you target them (just ships) &lt;br /&gt;
:*[[GalCop Galactic Registry]] - searchable guide to the galaxy you are in&lt;br /&gt;
:*[[Market Observer]] - useful statistics for analysing the F8 markets page (with immersive Market Ads at the bottom)&lt;br /&gt;
:*[[Vimana HUD]] (flashes warnings for High Temperature, Low Altitude, Low Energy &amp;amp; Low Shields)&lt;br /&gt;
:*[[HUD Selector]] - optional extra (for selecting HUDs)!&lt;br /&gt;
&lt;br /&gt;
You might also care to add [[The Galactic Almanac OXZ]] - a guide to everything in your current solar system - stations, planetary bodies, rock hermits, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
---- &lt;br /&gt;
== Immersive Help ==&lt;br /&gt;
Try out the following!&lt;br /&gt;
&lt;br /&gt;
*The OXPs listed just above&lt;br /&gt;
*[[Mr Gimlet]] - a short read&lt;br /&gt;
*[[Malacandra]]&amp;#039;s novella: [https://bb.oolite.space/viewtopic.php?t=16729 Sidewinder Precision Pro] - Adventures of a Sidewinder pilot (2014).&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.alioth.net/index.php?title=Category:Help_pages&amp;diff=90291</id>
		<title>Category:Help pages</title>
		<link rel="alternate" type="text/html" href="https://wiki.alioth.net/index.php?title=Category:Help_pages&amp;diff=90291"/>
		<updated>2026-08-31T01:33:04Z</updated>

		<summary type="html">&lt;p&gt;Cholmondely: Added &amp;quot;Immersive Help&amp;quot; ideas.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;font size=&amp;quot;5&amp;quot;&amp;gt;&amp;#039;&amp;#039;&amp;#039;Collection of Help pages for playing [[Oolite]]&amp;#039;&amp;#039;&amp;#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:Oolite-336.png|600px|right]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
 *For playing [[:Category:Classic|Classic Elite]], [[:Category:FE2|FE2]] &amp;amp; [[:Category:FFE|FFE]] see those respective categories for &amp;#039;&amp;#039;their&amp;#039;&amp;#039; help pages.&lt;br /&gt;
 *For help with [[The Dark Side]] - see [[:Category:Oolite scripting]] for more information.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;Note that three different Ship&amp;#039;s Manuals are on offer&amp;#039;&amp;#039; &lt;br /&gt;
:The Ship&amp;#039;s Manual in the [[Ship&amp;#039;s Library OXP]] is the most recent &lt;br /&gt;
::(&amp;#039;&amp;#039;and&amp;#039;&amp;#039; is readable in-game - &amp;#039;&amp;#039;and&amp;#039;&amp;#039; is adjusted to your ship &amp;#039;&amp;#039;and&amp;#039;&amp;#039; to your keyboard!)&lt;br /&gt;
:The [[Pilot&amp;#039;s Reference Manual]] was written for the Oolite Cobra  MkIII&lt;br /&gt;
:[[The Space Traders Flight Training Manual]] was written for the Classic Elite Cobra MkIII but is still good.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
The in-game [[Tutorial]] &amp;amp; the in-game [[Expansions Manager]] have their own explanatory wiki pages.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;Please note that your game download includes [[Mr Gimlet]]&amp;#039;s advice to new pilots and the RS Reference Sheet&amp;#039;&amp;#039;: (search for &amp;#039;&amp;#039;&amp;#039;OoliteRS&amp;#039;&amp;#039;&amp;#039; - stashed away in the entrails of your computer - or 2008 version - [[File:OoliteRS rev1.8.zip]]): it is well worth printing out.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
== Old Help ==&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?p=56825#p56825 Manual for Oolite v.1.65] (polyh, 2008): the major changes in Oolite game-play since 2008 involve tougher combat and more pirates in the safer systems which close to pirate dens in anarchies and such.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Videos ==&lt;br /&gt;
&lt;br /&gt;
=== Oolite v.1.90 ===&lt;br /&gt;
*[https://www.youtube.com/watch?v=yaoU-8jwsF0&amp;amp;list=PLsYaAtYv_5eWQDkMVZ9EPK5TGdzIkVse3 Oolite 1.90 - Let&amp;#039;s Play Poorly - Season 1]&lt;br /&gt;
*[https://www.youtube.com/watch?v=PxQFUETEQqk&amp;amp;list=PLsYaAtYv_5eUpD3FBWQk7XQuKQQsrVhNV Oolite unmodded - Let&amp;#039;s Play Poorly] (demonstrating the [[Strict Game]])&lt;br /&gt;
*[https://www.youtube.com/watch?v=iKrvCMK306U&amp;amp;list=PLsYaAtYv_5eW0rdcLg5foPSMk5an1-e8i Oolite 1.90 - Let&amp;#039;s Play Poorly - Season 2]&lt;br /&gt;
=== Oolite v.1.76 ===&lt;br /&gt;
*[https://bb.oolite.space/viewtopic.php?f=2&amp;amp;t=10454 Links to 12 videos featuring oxp-laden Oolite] (2012/3) Flying a python.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
== Helpful OXPs for new pilots ==&lt;br /&gt;
There is a &amp;#039;&amp;#039;lot&amp;#039;&amp;#039; of information in Oolite. These vital OXPs help give you access to the information you need to play/enjoy the game&lt;br /&gt;
&lt;br /&gt;
*[[Hints]] allows you to eavesdrop on more experienced pilots in the station bars. Tips on combat tactics, trade, buying equipment, fighting off Thargoids or pirates, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
*[[Contextual Help]]&lt;br /&gt;
&lt;br /&gt;
*[[Addons for Beginners (Vital Statistics)]] will download the following&lt;br /&gt;
:*[[Ship&amp;#039;s Library]] (with ship&amp;#039;s manual)&lt;br /&gt;
:*[[XenonUI]] (handy guide to the buttons on your astrogation console)&lt;br /&gt;
:*[[Technical Reference Library]] identifies ships when you target them (just ships) &lt;br /&gt;
:*[[GalCop Galactic Registry]] - searchable guide to the galaxy you are in&lt;br /&gt;
:*[[Market Observer]] - useful statistics for analysing the F8 markets page (with immersive Market Ads at the bottom)&lt;br /&gt;
:*[[Vimana HUD]] (flashes warnings for High Temperature, Low Altitude, Low Energy &amp;amp; Low Shields)&lt;br /&gt;
:*[[HUD Selector]] - optional extra (for selecting HUDs)!&lt;br /&gt;
&lt;br /&gt;
You might also care to add [[The Galactic Almanac OXZ]] - a guide to everything in your current solar system - stations, planetary bodies, rock hermits, &amp;#039;&amp;#039;etc&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
---- &lt;br /&gt;
== Immersive Help ==&lt;br /&gt;
Try out the following!&lt;br /&gt;
&lt;br /&gt;
*The OXPs listed just above&lt;br /&gt;
*[[Malacandra]]&amp;#039;s novella: [https://bb.oolite.space/viewtopic.php?t=16729 Sidewinder Precision Pro] - Adventures of a Sidewinder pilot (2014).&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Oolite]]&lt;/div&gt;</summary>
		<author><name>Cholmondely</name></author>
		
	</entry>
</feed>