Elite Wiki - User contributions [en]

Oolite JavaScript Reference: Mission

2012-01-27T08:16:47Z

Frame: /* displayModel */

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

The '''mission''' global object is used to run mission screens, and perform other actions related to mission scripting.

== Properties ==

=== <code>displayModel</code> ===
'''displayModel''' : {{oojsclass|Ship}}
If currently running a mission screen with a <code>model</code>, the ship entity used to display the model. This can be animated by setting its position and orientation from a [[Oolite JavaScript Reference: Global#addFrameCallback|frame callback]]. Uses role to identify ship, so be sure to use a uniqe role if you want a specific ship to be showed.

== Methods ==

=== <code>addMessageText</code> ===
function '''addMessageText'''(message : String)

Appends text to the currently running mission screen. Can also be used to add text to other screens like the system data (F7) screen.

=== <code>addMessageTextKey</code> ===
function '''addMessageTextKey'''(messageKey : String)

Like <code>[[#addMessageText|addMessageText()]]</code>, but looks up the specified <code>messageKey</code> in [[missiontext.plist]].

=== <code>markSystem</code> ===
function '''markSystem'''(systemNumber : Number)

Mark a system on the long range chart. Multiple systems may be marked at once, as in <code>mission.markSystem(4, 54, 222)</code>.

'''See also:''' <code>[[#unmarkSystem|unmarkSystem()]]</code>

=== <code>runScreen</code> ===
'''runScreen(parameters : Object [, callback : Function [, this : Object]])'''
Present a mission screen.

The appearance of the mission screen is defined by the properties of the <code>parameters</code> object. The currently defined properties are:
* <code>title : String</code>
* <code>titleKey : String</code> (Key in [[missiontext.plist]])
* <code>music : String</code> (name of a music file)
* <code>overlay : ''guiTextureSpecifier''</code> (name of an image used as overlay)
* <code>background : ''guiTextureSpecifier''</code> (name of a picture used as background)
* <code>model : String</code> (Role of a ship that will be shown as rotating ship)
* <code>message : String</code>
* <code>messageKey : String</code> (Key in [[missiontext.plist]])
* <code>spinModel: Boolean</code> (If <code>false</code>, the model is shown from the top with no automatic animation.)
* <code>choicesKey : String</code> (Key in [[missiontext.plist]])

Some of these are mutually exclusive; for instance, “title” overrides “titleKey”. See [[Oolite JavaScript Reference: Global#setScreenBackground|setScreenBackground()]] for a discussion of ''guiTextureSpecifier''.

The callback function is a function that is called when the player makes a choice. Every runScreen can have its own specific callback function, or you can design a single function to handle multiple mission screens instead.

'''Example:''' 
A simple mission screen:
mission.runScreen({
title: "My first mission screen",
message: "This am a mission screen wot is good",
choicesKey: "me_firstmission_choices"
},
function (choice)
{
if (choice === "1_YES") player.commsMessage("Yay!");
else if (choice === "2_NO") player.commsMessage("Boo.");
else player.commsMessage("Whut?");
});
In [[missiontext.plist]], you’ll need the following. The numbers are used because choices are sorted by key.
{
"me_firstmission_choices" =
{
"1_YES" = "Yes.";
"2_NO" = "No.";
"3_MAYBE" = "Maybe.";
};
}

The call does not have to be laid out as above. The parameters object can be manipulated in any way you want beforehand, and the callback function can be written out of line. For example, the following is equivalent:
var parameters = new Object();
parameters.title = "My first mission screen";
parameters.message = "This am";
parameters.choicesKey = "me_firstmission_choices";
parameters.message += " a mission screen wot is good";

function callback(choice)
{
if (choice === "1_YES") player.commsMessage("Yay!");
else if (choice === "2_NO") player.commsMessage("Boo.");
else player.commsMessage("Whut?");
}

mission.runScreen(parameters, callback);

This form is more complicated, and the ordering is less intuitive. However, it does allow you to make complex decisions about the parameters in code, and writing the callback out of line can be preferable if it’s long. It is recommended that you start out with the first approach, but keep in mind that there are other options if it becomes too limiting.

One warning: <code>runScreen()</code> will overwrite any existing missionscreen. The only safe place is using it inside a <code>missionScreenOpportunity</code> handler, because that handler only fires when it is allowed to show such a screen. When using the command at other places, first make sure with <code>guiScreen != "GUI_SCREEN_MISSION"</code> that there is currently no missionscreen on display by another oxp.

=== <code>setInstructions</code> ===
function '''setInstructions(instructions : String, [worldScriptName : String])'''

Specify a message to put on the Manifest screen (usually short instructions for current mission), under the title “Missions”.

When not called from within a world script, the name of a world script must be specified so that Oolite knows which script the message belongs to. Clear the message by calling <code>setInstructions(null)</code>.

It is recommended that <code>setInstructions()</code> is used only when you need to customise the text for a specific scenario. For static text, use <code>[[#setInstructionsKey|setInstructionsKey()]]</code> instead.

'''See also:''' <code>[[#setInstructionsKey|setInstructionsKey()]]</code>

=== <code>setInstructionsKey</code> ===
function '''setInstructionsKey(messageKey : String, [worldScript : String])'''

Like <code>[[#setInstructions|setInstructions()]]</code>, but looks up the specified <code>messageKey</code> in [[missiontext.plist]].

'''See also:''' <code>[[#setInstructions|setInstructions()]]</code>

=== <code>unmarkSystem</code> ===
function '''unmarkSystem'''(systemNumbers : Number)

Remove a mark set with <code>[[#markSystem|markSystem()]]</code>. Multiple systems may be unmarked at once, as in <code>mission.unmarkSystem(4, 54, 222)</code>.

'''See also:''' <code>[[#markSystem|markSystem()]]</code>

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Quaternion

2011-08-30T20:02:33Z

Frame: /* rotateY */

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

The '''<code>Quaternion</code>''' class represents a [[quaternion]], a four-dimensional number, which is used to express rotations. Explaining quaternion mathematics is ''way'' beyond the scope of this document, but a quick overview is provided below.

=== Quaternions for Rotations ===
This is a very quick, pragmatic discussion of quaternions as they apply to rotating things in Oolite. If you’re interested in the theory, see:
* Wikipedia: [http://en.wikipedia.org/wiki/Quaternions_and_spatial_rotation Quaternions and spatial rotation]
* Wikipedia: [http://en.wikipedia.org/wiki/Quaternion Quaternion]
* MathWorld: [http://mathworld.wolfram.com/Quaternion.html Quaternion]

Consider a ship at point ''h'' oriented to face a station at point ''t''. This can be expressed as the vector from the ship to the station, ''v'' = ''t'' − ''h''. However, if the ship rolls, it is still heading along the same vector ''v'', so additional information is required: a twist angle, ''α''. A rotation quaternion is a tuple ''Q'' = (''w'', ''x'', ''y'', ''z''), such that
:''Qw'' = cos ''α''/2
:''Qx'' = ''vx'' sin ''α''/2
:''Qy'' = ''vy'' sin ''α''/2
:''Qz'' = ''vz'' sin ''α''/2
Additionally, a rotation quaternion must be normalized; that is, it must fulfill the '''normal invariant''' ''Qw''² + ''Qx''² + ''Qy''² + ''Qz''² = 1. Unlike with [[property list]] scripting and specifications, quaternions will not be automatically normalized for you except where specified, but a <code>[[#normalize|normalize]]()</code> method is provided.

An '''identity rotation''' – that is, one which, when applied, has no effect – is represented by the '''identity quaternion''' (1, 0, 0, 0).

The <code>Quaternion</code> class provides several methods to make construction of rotations easier: <code>[[#rotate|rotate]]()</code>, <code>[[#rotateX|rotateX]]()</code>, <code>[[#rotateY|rotateY]]()</code>, <code>[[#rotateZ|rotateZ]]()</code>.

Rotations can be combined by quaternion multiplication (see the <code>[[#multiply|multiply]]()</code> method). Note that quaternion multiplication is not commutative; that is, ''PQ'' is not the same as ''QP''. If this seems strange, take a box or book and assign it ''x'', ''y'' and ''z'' axes. Rotate it about the ''x'' axis and then the ''y'' axis. Then, rotate it about the ''y'' axis followed by the ''x'' axis. If the results of the two rotations are the same, you’re doing it wrong.

=== Quaternion Expressions ===
All Oolite-provided functions which take a quaternion as an argument may instead be passed an [[Oolite JavaScript Reference: Entity|Entity]] instead, in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used. In specifications, this is represented by arguments named <code>quaternionOrEntity</code>. (Is this actually useful? It seems less compellingly so than the [[Oolite JavaScript Reference: Vector#Vector Expressions|vector equivalent]]. -- [[User:Ahruman]])

Additionally, most <code>Quaternion</code> methods may be passed four numbers, or an array of four numbers, instead of a quaternion. In specifications, this is represented by arguments named <code>quaternionExpression</code>.

== Properties ==
=== <code>w</code> ===
'''w''' : Number (read/write)

The ''w'' component of the quaternion.

=== <code>x</code> ===
'''x''' : Number (read/write)
The ''x'' component of the quaternion.

=== <code>y</code> ===
'''y''' : Number (read/write)
The ''y'' component of the quaternion.

=== <code>z</code> ===
'''z''' : Number (read/write)
The ''z'' component of the quaternion.

== Methods ==
=== Constructor ===
'''new Quaternion'''([value : [[#Quaternion Expressions|quaternionExpression]]])
Create a new quaternion with the specified value. If no value is provided, the vector is initialized to the identity quaternion (1, 0, 0, 0).

=== <code>dot</code> ===
function '''dot'''(q : [[#Quaternion Expressions|quaternionExpression]]) : Number
Returns the quaternion dot product (inner product) of the target and <code>q</code>. (For two normalized quaternions, this will be 1 if they’re equal, -1 if they’re opposite and 0 if they’re perpendicular.)

=== <code>multiply</code> ===
function '''multiply'''(q : [[#Quaternion Expressions|quaternionExpression]]) : Quaternion
Returns the standard quaternion product (Grassmann product) of the target and <code>q</code>. This is used to concatenate rotations together.

=== <code>normalize</code> ===
function '''normalize'''() : Quaternion
Returns the quaternion adjusted to fulfill the [[#Quaternions for Rotations|normal invariant]]. Specifically, this divides each component by the square root of (''w''² + ''x''² + ''y''² + ''z''²).

=== <code>rotate</code> ===
function '''rotate'''(a : [[Oolite JavaScript Reference: Vector#Vector Expressions|vectorExpression]], angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the axis of <code>a</code>. (FIXME: clockwise or anticlockwise?)

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateX(angle)</code> is equivalent to <code>q.[[#rotate|rotate]]([1, 0, 0], angle)</code>.

=== <code>rotateY</code> ===
function '''rotateY'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''y'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateY(angle)</code> is equivalent to <code>q.[[#rotate|rotate]]([0, 1, 0], angle)</code>.

=== <code>rotateZ</code> ===
function '''rotateZ'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''z'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateZ(angle)</code> is equivalent to <code>q.[[#rotate|rotate]]([0, 0, 1], angle)</code>.

=== <code>toArray</code> ===
function '''toArray'''() : Array
Returns an array of the quaternion’s components, in the order <code>[w, x, y, z]</code>. <code>q.toArray()</code> is equivalent to <code>[q.w, q.x, q.y, q.z]</code>.

=== <code>vectorForward</code> ===
function '''vectorForward'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the forward vector from the quaternion.

To understand this, consider an entity which is aligned with the world co-ordinate system – that is, its <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is the identity quaternion (1, 0, 0, 0), and thus its ''x'' axis is aligned with the world ''x'' axis, its ''y'' axis is aligned with the world ''y'' axis and its ''z'' axis is aligned with the world ''z'' axis. If it is rotated by a quaternion ''Q'', <code>Q.vectorForward()</code> is the forward (''z'') axis after rotation. Similarly, <code>Q.[[#vectorUp|vectorUp]]()</code> is the up (''y'') axis after rotation, and <code>Q.[[#vectorRight|vectorRight]]()</code> is the right (''x'') axis after rotation.

=== <code>vectorRight</code> ===
function '''vectorRight'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the right vector from the quaternion. See <code>[[#vectorForward|vectorForward]]()</code> for a definition.

=== <code>vectorUp</code> ===
function '''vectorUp'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the up vector from the quaternion. See <code>[[#vectorForward|vectorForward]]()</code> for a definition.

== Static Methods ==

=== <code>random</code> ===
function '''random'''() : Quaternion
Returns a random normalized quaternion.

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Quaternion

2011-08-30T20:02:09Z

Frame: /* rotateZ */

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

The '''<code>Quaternion</code>''' class represents a [[quaternion]], a four-dimensional number, which is used to express rotations. Explaining quaternion mathematics is ''way'' beyond the scope of this document, but a quick overview is provided below.

=== Quaternions for Rotations ===
This is a very quick, pragmatic discussion of quaternions as they apply to rotating things in Oolite. If you’re interested in the theory, see:
* Wikipedia: [http://en.wikipedia.org/wiki/Quaternions_and_spatial_rotation Quaternions and spatial rotation]
* Wikipedia: [http://en.wikipedia.org/wiki/Quaternion Quaternion]
* MathWorld: [http://mathworld.wolfram.com/Quaternion.html Quaternion]

Consider a ship at point ''h'' oriented to face a station at point ''t''. This can be expressed as the vector from the ship to the station, ''v'' = ''t'' − ''h''. However, if the ship rolls, it is still heading along the same vector ''v'', so additional information is required: a twist angle, ''α''. A rotation quaternion is a tuple ''Q'' = (''w'', ''x'', ''y'', ''z''), such that
:''Qw'' = cos ''α''/2
:''Qx'' = ''vx'' sin ''α''/2
:''Qy'' = ''vy'' sin ''α''/2
:''Qz'' = ''vz'' sin ''α''/2
Additionally, a rotation quaternion must be normalized; that is, it must fulfill the '''normal invariant''' ''Qw''² + ''Qx''² + ''Qy''² + ''Qz''² = 1. Unlike with [[property list]] scripting and specifications, quaternions will not be automatically normalized for you except where specified, but a <code>[[#normalize|normalize]]()</code> method is provided.

An '''identity rotation''' – that is, one which, when applied, has no effect – is represented by the '''identity quaternion''' (1, 0, 0, 0).

The <code>Quaternion</code> class provides several methods to make construction of rotations easier: <code>[[#rotate|rotate]]()</code>, <code>[[#rotateX|rotateX]]()</code>, <code>[[#rotateY|rotateY]]()</code>, <code>[[#rotateZ|rotateZ]]()</code>.

Rotations can be combined by quaternion multiplication (see the <code>[[#multiply|multiply]]()</code> method). Note that quaternion multiplication is not commutative; that is, ''PQ'' is not the same as ''QP''. If this seems strange, take a box or book and assign it ''x'', ''y'' and ''z'' axes. Rotate it about the ''x'' axis and then the ''y'' axis. Then, rotate it about the ''y'' axis followed by the ''x'' axis. If the results of the two rotations are the same, you’re doing it wrong.

=== Quaternion Expressions ===
All Oolite-provided functions which take a quaternion as an argument may instead be passed an [[Oolite JavaScript Reference: Entity|Entity]] instead, in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used. In specifications, this is represented by arguments named <code>quaternionOrEntity</code>. (Is this actually useful? It seems less compellingly so than the [[Oolite JavaScript Reference: Vector#Vector Expressions|vector equivalent]]. -- [[User:Ahruman]])

Additionally, most <code>Quaternion</code> methods may be passed four numbers, or an array of four numbers, instead of a quaternion. In specifications, this is represented by arguments named <code>quaternionExpression</code>.

== Properties ==
=== <code>w</code> ===
'''w''' : Number (read/write)

The ''w'' component of the quaternion.

=== <code>x</code> ===
'''x''' : Number (read/write)
The ''x'' component of the quaternion.

=== <code>y</code> ===
'''y''' : Number (read/write)
The ''y'' component of the quaternion.

=== <code>z</code> ===
'''z''' : Number (read/write)
The ''z'' component of the quaternion.

== Methods ==
=== Constructor ===
'''new Quaternion'''([value : [[#Quaternion Expressions|quaternionExpression]]])
Create a new quaternion with the specified value. If no value is provided, the vector is initialized to the identity quaternion (1, 0, 0, 0).

=== <code>dot</code> ===
function '''dot'''(q : [[#Quaternion Expressions|quaternionExpression]]) : Number
Returns the quaternion dot product (inner product) of the target and <code>q</code>. (For two normalized quaternions, this will be 1 if they’re equal, -1 if they’re opposite and 0 if they’re perpendicular.)

=== <code>multiply</code> ===
function '''multiply'''(q : [[#Quaternion Expressions|quaternionExpression]]) : Quaternion
Returns the standard quaternion product (Grassmann product) of the target and <code>q</code>. This is used to concatenate rotations together.

=== <code>normalize</code> ===
function '''normalize'''() : Quaternion
Returns the quaternion adjusted to fulfill the [[#Quaternions for Rotations|normal invariant]]. Specifically, this divides each component by the square root of (''w''² + ''x''² + ''y''² + ''z''²).

=== <code>rotate</code> ===
function '''rotate'''(a : [[Oolite JavaScript Reference: Vector#Vector Expressions|vectorExpression]], angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the axis of <code>a</code>. (FIXME: clockwise or anticlockwise?)

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateX(angle)</code> is equivalent to <code>q.[[#rotate|rotate]]([1, 0, 0], angle)</code>.

=== <code>rotateY</code> ===
function '''rotateY'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''y'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateY(angle)</code> is equivalent to <code>q.[[#rotate|rotate]](0, 1, 0, angle)</code>.

=== <code>rotateZ</code> ===
function '''rotateZ'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''z'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateZ(angle)</code> is equivalent to <code>q.[[#rotate|rotate]]([0, 0, 1], angle)</code>.

=== <code>toArray</code> ===
function '''toArray'''() : Array
Returns an array of the quaternion’s components, in the order <code>[w, x, y, z]</code>. <code>q.toArray()</code> is equivalent to <code>[q.w, q.x, q.y, q.z]</code>.

=== <code>vectorForward</code> ===
function '''vectorForward'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the forward vector from the quaternion.

To understand this, consider an entity which is aligned with the world co-ordinate system – that is, its <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is the identity quaternion (1, 0, 0, 0), and thus its ''x'' axis is aligned with the world ''x'' axis, its ''y'' axis is aligned with the world ''y'' axis and its ''z'' axis is aligned with the world ''z'' axis. If it is rotated by a quaternion ''Q'', <code>Q.vectorForward()</code> is the forward (''z'') axis after rotation. Similarly, <code>Q.[[#vectorUp|vectorUp]]()</code> is the up (''y'') axis after rotation, and <code>Q.[[#vectorRight|vectorRight]]()</code> is the right (''x'') axis after rotation.

=== <code>vectorRight</code> ===
function '''vectorRight'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the right vector from the quaternion. See <code>[[#vectorForward|vectorForward]]()</code> for a definition.

=== <code>vectorUp</code> ===
function '''vectorUp'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the up vector from the quaternion. See <code>[[#vectorForward|vectorForward]]()</code> for a definition.

== Static Methods ==

=== <code>random</code> ===
function '''random'''() : Quaternion
Returns a random normalized quaternion.

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Quaternion

2011-08-30T20:01:51Z

Frame: /* rotateX */

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

The '''<code>Quaternion</code>''' class represents a [[quaternion]], a four-dimensional number, which is used to express rotations. Explaining quaternion mathematics is ''way'' beyond the scope of this document, but a quick overview is provided below.

=== Quaternions for Rotations ===
This is a very quick, pragmatic discussion of quaternions as they apply to rotating things in Oolite. If you’re interested in the theory, see:
* Wikipedia: [http://en.wikipedia.org/wiki/Quaternions_and_spatial_rotation Quaternions and spatial rotation]
* Wikipedia: [http://en.wikipedia.org/wiki/Quaternion Quaternion]
* MathWorld: [http://mathworld.wolfram.com/Quaternion.html Quaternion]

Consider a ship at point ''h'' oriented to face a station at point ''t''. This can be expressed as the vector from the ship to the station, ''v'' = ''t'' − ''h''. However, if the ship rolls, it is still heading along the same vector ''v'', so additional information is required: a twist angle, ''α''. A rotation quaternion is a tuple ''Q'' = (''w'', ''x'', ''y'', ''z''), such that
:''Qw'' = cos ''α''/2
:''Qx'' = ''vx'' sin ''α''/2
:''Qy'' = ''vy'' sin ''α''/2
:''Qz'' = ''vz'' sin ''α''/2
Additionally, a rotation quaternion must be normalized; that is, it must fulfill the '''normal invariant''' ''Qw''² + ''Qx''² + ''Qy''² + ''Qz''² = 1. Unlike with [[property list]] scripting and specifications, quaternions will not be automatically normalized for you except where specified, but a <code>[[#normalize|normalize]]()</code> method is provided.

An '''identity rotation''' – that is, one which, when applied, has no effect – is represented by the '''identity quaternion''' (1, 0, 0, 0).

The <code>Quaternion</code> class provides several methods to make construction of rotations easier: <code>[[#rotate|rotate]]()</code>, <code>[[#rotateX|rotateX]]()</code>, <code>[[#rotateY|rotateY]]()</code>, <code>[[#rotateZ|rotateZ]]()</code>.

Rotations can be combined by quaternion multiplication (see the <code>[[#multiply|multiply]]()</code> method). Note that quaternion multiplication is not commutative; that is, ''PQ'' is not the same as ''QP''. If this seems strange, take a box or book and assign it ''x'', ''y'' and ''z'' axes. Rotate it about the ''x'' axis and then the ''y'' axis. Then, rotate it about the ''y'' axis followed by the ''x'' axis. If the results of the two rotations are the same, you’re doing it wrong.

=== Quaternion Expressions ===
All Oolite-provided functions which take a quaternion as an argument may instead be passed an [[Oolite JavaScript Reference: Entity|Entity]] instead, in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used. In specifications, this is represented by arguments named <code>quaternionOrEntity</code>. (Is this actually useful? It seems less compellingly so than the [[Oolite JavaScript Reference: Vector#Vector Expressions|vector equivalent]]. -- [[User:Ahruman]])

Additionally, most <code>Quaternion</code> methods may be passed four numbers, or an array of four numbers, instead of a quaternion. In specifications, this is represented by arguments named <code>quaternionExpression</code>.

== Properties ==
=== <code>w</code> ===
'''w''' : Number (read/write)

The ''w'' component of the quaternion.

=== <code>x</code> ===
'''x''' : Number (read/write)
The ''x'' component of the quaternion.

=== <code>y</code> ===
'''y''' : Number (read/write)
The ''y'' component of the quaternion.

=== <code>z</code> ===
'''z''' : Number (read/write)
The ''z'' component of the quaternion.

== Methods ==
=== Constructor ===
'''new Quaternion'''([value : [[#Quaternion Expressions|quaternionExpression]]])
Create a new quaternion with the specified value. If no value is provided, the vector is initialized to the identity quaternion (1, 0, 0, 0).

=== <code>dot</code> ===
function '''dot'''(q : [[#Quaternion Expressions|quaternionExpression]]) : Number
Returns the quaternion dot product (inner product) of the target and <code>q</code>. (For two normalized quaternions, this will be 1 if they’re equal, -1 if they’re opposite and 0 if they’re perpendicular.)

=== <code>multiply</code> ===
function '''multiply'''(q : [[#Quaternion Expressions|quaternionExpression]]) : Quaternion
Returns the standard quaternion product (Grassmann product) of the target and <code>q</code>. This is used to concatenate rotations together.

=== <code>normalize</code> ===
function '''normalize'''() : Quaternion
Returns the quaternion adjusted to fulfill the [[#Quaternions for Rotations|normal invariant]]. Specifically, this divides each component by the square root of (''w''² + ''x''² + ''y''² + ''z''²).

=== <code>rotate</code> ===
function '''rotate'''(a : [[Oolite JavaScript Reference: Vector#Vector Expressions|vectorExpression]], angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the axis of <code>a</code>. (FIXME: clockwise or anticlockwise?)

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateX(angle)</code> is equivalent to <code>q.[[#rotate|rotate]]([1, 0, 0], angle)</code>.

=== <code>rotateY</code> ===
function '''rotateY'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''y'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateY(angle)</code> is equivalent to <code>q.[[#rotate|rotate]](0, 1, 0, angle)</code>.

=== <code>rotateZ</code> ===
function '''rotateZ'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''z'' axis. (FIXME: clockwise or anticlockwise?)

<code>q.rotateZ(angle)</code> is equivalent to <code>q.[[#rotate|rotate]](0, 0, 1, angle)</code>.

=== <code>toArray</code> ===
function '''toArray'''() : Array
Returns an array of the quaternion’s components, in the order <code>[w, x, y, z]</code>. <code>q.toArray()</code> is equivalent to <code>[q.w, q.x, q.y, q.z]</code>.

=== <code>vectorForward</code> ===
function '''vectorForward'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the forward vector from the quaternion.

To understand this, consider an entity which is aligned with the world co-ordinate system – that is, its <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is the identity quaternion (1, 0, 0, 0), and thus its ''x'' axis is aligned with the world ''x'' axis, its ''y'' axis is aligned with the world ''y'' axis and its ''z'' axis is aligned with the world ''z'' axis. If it is rotated by a quaternion ''Q'', <code>Q.vectorForward()</code> is the forward (''z'') axis after rotation. Similarly, <code>Q.[[#vectorUp|vectorUp]]()</code> is the up (''y'') axis after rotation, and <code>Q.[[#vectorRight|vectorRight]]()</code> is the right (''x'') axis after rotation.

=== <code>vectorRight</code> ===
function '''vectorRight'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the right vector from the quaternion. See <code>[[#vectorForward|vectorForward]]()</code> for a definition.

=== <code>vectorUp</code> ===
function '''vectorUp'''() : [[Oolite JavaScript Reference: Vector|Vector]]
Returns the up vector from the quaternion. See <code>[[#vectorForward|vectorForward]]()</code> for a definition.

== Static Methods ==

=== <code>random</code> ===
function '''random'''() : Quaternion
Returns a random normalized quaternion.

[[Category:Oolite JavaScript Reference]]

Shipdata.plist

2011-03-22T23:38:55Z

Frame: /* rotational_velocity */

'''shipdata.[[plist]]''' 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's sake, listed alphabetically:

= Ship keys=
The following keys are used by all ships
==accuracy==
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 assings to the missile the accuracy value of 0.0, which corresponds to the standard missile tracking behaviour.

Used with NPC ships it enlarges the chance of shooting at greater distances. Value with NPC ships is between -5 and 10.

Example:
"accuracy" = 8;

== aft_eject_position ==
Determines the XYZ point on the model from which cargo is ejected.

Example:
"aft_eject_position" = "0.0 -4.5 -23.0";

== aft_weapon_type ==
Assigns the ship's laser.
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE).

Example:
"aft_weapon_type" = "WEAPON_BEAM_LASER";

== ai_type ==
Assigns an AI to the entity. This may be a previously existing AI, or one custom made for the occasion.

Example:
"ai_type" = "pirateAI.plist";

== auto_ai ==
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.
Example:
"auto_ai" = yes;
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.

== beacon ==
A special feature for beacons and navigation aids.
The string can be anything - the first letter is what's displayed in the advanced space compass.

Example:
"beacon" = "X-code";

The following characters are known to be used as identifiers for '''stations and other fixed objects''' (listed with their respective OXPs):

A = Astromine (Commies)
B = Black Monk Monastery (Black Monks)
A Seedy Space Bar (Random Hits)
Nemeanian Military Base (Assassins)
C = CoachWhip hOopy Casino (Hoopy Casino)
Pi-42 Con Store (Your Ad Here)
F = Collective Zero-G Factory (Commies)
Collective SLAPU (Commies)
Imperial AstroFactory (Dictators)
G = Griff Research Ltd Orbital Base (Assassins)
GRS Buoy Factory (GRS Buoy Repair)
H = Hacker Outpost (Anarchies)
Deep Space Hoopy Hotel : Hades Branch (Assassins)
L = The Link Base (Ionics)
Deep Space Hoopy Hotel : Lernean Branch (Assassins)
N = Main Station Beacon
P = Tianve Pulsar Monitoring Station (Tianve)
R = Rock Hermit (Rock Hermit Locator)
Augeaian Orbital Repair Facility (Assassins)
Rebel Outpost (Assassins)
Q = Hesperides Wiseguy Way-Station (Assassins)
S = Navy SecCom Station (Galactic Navy)
Special Branch Orbital Headquarters (Assassins)
T = Taranis Corporation HQ (Taranis)
W = Witchpoint Buoy
Z = Free Trade Zone (Free Trade Zone)

The following characters are known to be used for '''non-station objects that may appear anywhere''':

H = Homing Beacon (ett Homing Beacon)

The following characters should not be assigned easily to stations or ships that are supposed to appear anywhere, because they are likely to be used for ships in other OXPs:

M = Mark
T = Target
V = Victim
X = general marker
+ = general marker

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) 
Example in shipdata:
"beacon" = "fuelStation_location";
Example in descriptions.plist
"fuelStation_location" = (1, 2, -3, 2, -3, -4, 3, -4, 3, 4, -3, 4, -3, 3, 2, 3, 2, -3, 1, -3 );
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.

== bounty ==
Sets a Cr. reward on the NPC'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.

Example:
"bounty" = 50;

== cargo_carried ==
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.

Example:
"cargo_carried" = "Gold";

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. 
It is possible to define a mix of random cargo for ships by using the string "SCARCE_GOODS" or "PLENTIFUL_GOODS", 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.) 
To make cargo_carried working for ships, the cargo_type must be "CARGO_NOT_CARGO" to define the ship not being cargo itself. (see below)

== [[cargo_type]] ==
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. Works since Oolite 1.71 also for pods spawn by a script. CARGO_CARRIED needs in addition an second key cargo_carried that specifies the cargo. (see below) 

Example:
"cargo_type" = "CARGO_RANDOM";

More control of contents of barrels is available through the CARGO_CARRIED string.

Example:
"cargo_type" = "CARGO_CARRIED";
"cargo_carried" = "4 Gold";

You can also specify the cargo of a ship. use "cargo_type" = CARGO_NOT_CARGO and define the contents of the barrels it will give with "cargo_carried". In that case there must be no quantity defined, only the type of [[commodity]].

Example:
"cargo_type" = "CARGO_NOT_CARGO";
"cargo_carried" = "Computers";

Another notable type of cargo is the scripted item CARGO_SCRIPTED_ITEM, as examplified by the cloacking device. When CARGO_SCRIPTED_ITEM is defined, the barrels will trigger scooping events for the ship-scripts. Other barrels don't trigger scooping events. 
The cargo barrels are stored in the ships hold like normal barrels when a cargo was defined for them with the JS method "setCargo". 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.

== cloak_automatic ==
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) Key added with Oolite 1.75

Example:
"cloak_automatic" = no;

== cloak_passive ==
When true, any firing of laser will deactivate the cloak. (False by default)

Example:
"cloak_passive" = yes;

==conditions==
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.

Example:
"conditions" = (
"systemGovernment_number equal 3",
"systemEconomy_number lessthan 4"
);

== counts_as_kill ==
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. Key is added with Oolite 1.75

Example:
"counts_as_kill" = no;

== custom_views==
Will add the ability to display custom POVs of the player ship, in game toggled by pressing '''v'''.

This is an array with any number of entries, one for each view, each with:
*a '''view_description''' - giving a textual description of the view.
*a '''view_position''' - relative to the origin of the ship model.
*a '''view_orientation''' - this is a [[Quaternions|quaternion]] expressing a rotation from directly forwards.
*a '''weapon_facing''' - FORWARD, AFT, PORT or STARBOARD. The weapon that will fire when that view is selected.

The view_position is best chosen by selecting a facet, line or point in Wings and copying down the coordinates.

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:

W = the cosine of half the angle rotated about the axis xyz 
X = the sine of half the angle rotated about xyz, multiplied by x 
Y = the sine of half the angle rotated about xyz, multiplied by y 
Z = the sine of half the angle rotated about xyz, multiplied by z 

Four decimal places are probably enough accuracy for these values.

Example:
custom_views =
(
{
view_description = "Front View";
view_orientation = "0.0 0.0 1.0 0.0";
view_position = "0.0 30.0 200.0";
weapon_facing = "FORWARD";
}
);

== death_actions ==
Gives an opportunity to have a ship's death trigger one or a set of [[Shipdata.plist#script_actions|script_actions]]. It contains an array of legacy script expressions.

Example:
"death_actions" = ("spawn: explosive_shrapnel 1");

== debris_role ==
Specifies the kind of debris an asteroid or boulder generates. When not defined they default to generating 'ships' with role "boulder" or "splinter". (Key added with Oolite 1.74)

Example:
"debris_role" = "my_boulder_foo";

== density ==
This real value is used to calculate a ships total mass. Default is 1.0

Example:
"density" = 1.5;

== display_name ==
States the model's name as it will be known to the ID computer. By default this is the same as "name". Added for multilingual oolite.

Example:
"display_name" = "ExampleShip Mark IX";

== energy_recharge_rate ==
The rate at which energy is replenished. Stations are at 100, Adders at 2. (Default value: 1)

Example:
"energy_recharge_rate" = "3.5";

== escape_pod_model ==
With this entry ships can have custom escape pods. (starting from version 1.65) You have to specify the '''role''' of your custom escape pod (not its entry-name).

Example:
"escape_pod_model" = "custom_pod";

== escorts ==
Determines how many escorts an NPC shall have. Maximum is 16.

Example:
"escorts" = 4;
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't escort a mother with CLASS_POLICE. 
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.

== escort_role ==
Assigns the specific ship type to be the escort, by the ship's role. (Before Oolite 1.74 only the name "escort-role" is accepted.)

Example:
"escort_role" = "my_custom_escort_role";
Escort ships will use the escortAI.plist unless "auto_ai" is set to false.

== escort_ship ==
Assigns the specific ship type to be the escort, by the ship's name. (Before Oolite 1.74 only the name "escort-ship" is accepted.)

Example:
"escort_ship" = "cobramk1";
Escort ships will use the escortAI.plist unless "auto_ai" is set to false.

== exhaust ==
The XYZ position(s) of exhaust plume(s), and the XYZ of the plume shape, ergo

x y z width height length

'''x y z''' is the position relative to the origin of the main model.

'''width''' in meters, how wide a plume is on x axis. (x radius)

'''height''' in meters, how tall a plume is on y axis. (y radius)

'''length''' 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)

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)

Example:
"exhaust" = (
"5 0.0 -25 6.0 4.0 10.0",
"-5 0.0 -25 6.0 4.0 10.0"
);

== extra_cargo ==
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.

Example:
"extra_cargo" = 25;

== forward_weapon_type ==
Assigns the ship's laser.
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE).

Example:
"forward_weapon_type" = "WEAPON_BEAM_LASER";

== frangible ==
Determines if eventual sub-entities are "loose". By default any given object is already frangible, so the use of this line must be to negate that.
If set to false, the object plus subentities will be regarded as a single object.
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.

Example:
"frangible" = no;

== fragment_chance ==
Determines if a ship breaks apart into fragments and generates parts with role "wreckage". By chance factor, or true/false. Default is 90% chance.
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 -> 1.25s)

Example:
"fragment_chance" = no;

== fuel ==
Determines an NPC ship's fuel storage, which will affect how it uses its Fuel Injectors.

Example:
"fuel" = 70;

== has_cloaking_device ==
Determines if a ship has a cloacking device installed. By chance factor, or true/false.

Example:
"has_cloaking_device" = 0.5;

== has_ecm ==
Determines if a ship has the E.C.M system installed. By chance factor, or true/false.

Example:
"has_ecm" = 0.5;
or
"has_ecm" = no;

== has_energy_bomb ==
Determines if a ship has an energy bomb. If it has one, it might launch a mine with role "energy_bomb" as part of his fleeing behavior. currently the only build-in mine with this role is the q-bomb. 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.

Example:
"has_energy_bomb" = yes;

== has_escape_pod ==
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, '''has_escape_pod''' must be set to a numeric value corresponding to the escape pods present on board.

Examples:
has_escape_pod = no;
has_escape_pod = 0.75;
has_escape_pod = 3;

== has_fuel_injection ==
Determines if a ship has the witchdrive fuel injector.

Example:
"has_fuel_injection" = 0.99;

==has_military_jammer==
Determines if a ship has a military jammer. Ships equipped with this item become invisible on the radar.
Example:
"has_military_jammer" = 0.75;

==has_military_scanner_filter==
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.
Example:
"has_military_scanner_filter" = 0.50;

== has_scoop ==
Determines if a ship has a fuel/cargo scoop.

Example:
"has_scoop" = no;

== has_scoop_message ==
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)

Example:
"has_scoop_message" = no;

== has_shield_booster==
Determines if a ship has the shield booster. (enlarges max energy with 256)

Example:
"has_shield_booster" = 0.80;

== has_shield_enhancer ==
Determines if a ship has the coveted shield enhancer. (enlarges max energy with 256 and raises energy recharge rate with 50%)

Example:
"has_shield_enhancer" = 0.45;

== heat_insulation ==
This real number gives the amount of heat insulation of a ship. Default is 1.0 Only for NPC ships. Playes ships can have the equipment EQ_HEAT_SHIELDING with gives the player than a heat_insulation of 2.0

Example:
"heat_insulation" = "2.0";

== hud ==
Used for a playership, to assign another HUD than the default one.

Example:
"hud" = "specialhud.plist";

== hyperspace_motor ==
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)

Examples:
"hyperspace_motor" = no;

hyperspace_motor=NO;

== hyperspace_motor_spin_time ==
Used to modify jump countdown time. Default = 15.

Examples:
"hyperspace_motor_spin_time" = "15";

==is_external_dependency==
This key should be added to ships that use like_ship references to ships in other oxps but don't depend on them. Normally will Oolite write errors in the log when it can't resolve a like_ship reference. When this key is set to YES, it will suppress the error generation. WARNING: only set this key to YES when the model won't get added to the system without the other oxp installed or you will miss a valuable warning.

Example:
"is_external_dependency" = yes;

==is_submunition==
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.

Example:
"is_submunition" = yes;

==is_template==
Set this to yes/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.

Example:
"is_template" = yes;

== laser_color ==
Determines a ship's laser colour.

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.

Example:
"laser_color" = "cyanColor"

== launch_actions ==
Triggers a script on the entity just after setup, also when called by spawn and addShip methods.
Can be used to change to a custom AI, when a ship is generated by standard role.
[[Shipdata.plist#script_actions|script_actions]]

Example:
"role = trader";
"launch_actions" = (
"setAITo: pirateAI.plist"
);

== like_ship ==
Allows a shipdata entry (of a ship with many matching characteristics to another) to be short and sweet. With '''like_ship''' you can reference to another existing shipdata entry, and then only specify the differences to the 'original'. It takes the unique '''entry-identifier''' as argument. Of course you have to make sure that the 'original' you are referring to actually exists, or Oolite won't be able to create your ship.

Works well together with the [[#is_template|is_template]]-key.

Example:
"my_ship" = {
"like_ship" = "adder";
"max_flight_speed" = "700";
"name" = "Freak Turbo Adder";
},

== likely_cargo ==
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.

Example:
"likely_cargo" = "2";

== materials ==
See [[Materials in Oolite]].

== max_cargo ==
Sets the ship'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.

Example:
"max_cargo" = "5";

== max_energy ==
Sets the ship's energy value. (Default value: 200)

Example:
"max_energy" = "300";

== max_flight_pitch ==
Sets pitch factor. Will usually range from a sluggish 0.6 to a very sensitive 3.0

Example:
"max_flight_pitch" = "2.2";

== max_flight_roll ==
Sets roll factor. Will usually range from 0.8 to 4.6.

Example:
"max_flight_roll" = "4.2";

== max_flight_speed ==
Sets the model's top speed. Interceptors fly at 520 (0.52 LM), Shuttles at 80.

Example:
"max_flight_speed" = "320";

== max_flight_yaw ==
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

Example:
"max_flight_yaw" = "2.2";

== max_missiles ==
Sets a ship's missile limit. Maximum allowable value for the player is 16 and for npc ships 32. When not defined, the value with "missiles" is used as max_missiles. When defining more than a few missiles, it could be wise to also define value for "missile_load_time" to avoid massive missile launches. npc ships are more likely to fire missiles the more they carry.

Example:
"max_missiles" = "1";

== missile_launch_position ==
Determines the XYZ point on the model from which a missile is launched.

Example:
"missile_launch_position" = "0.0 -2.25 10.0";

This position should lie outside the bounding box of the entity and not just outside of the ships mesh. If it does lie inside the bounding box, the launch position is shifted along its direction until the launched missile lies outside the bounding box. The collision radius of the launched missile is taken into account. The collision radius for a plain missile is 4.52 meter.

== missile_load_time ==
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.

Example:
"missile_load_time" = "2.1";

== missiles ==
Sets a ship's probable number of missiles.

Example:
"missiles" = "0";

== missile_role ==
Defines the entity that is launched as missile. Can specify a certain missile-type or any other ship-entity by role. Only applies to NPC's, player-ship dependacies must be defined in the [[shipyard.plist]]. If no missile_role is defined and a NPC ship launches a missile he most often chooses the default missile but sometimes chooses one at random from all ships with role missile inside one of the installed OXP's.

Example:
"missile_role" = "thargon";

== model ==
Assigns the entity's corresponding '''.dat''' file that will be found with the exact same name in the ''Models'' folder.

Example:
"model" = "example_ship.dat";

== name ==
States the model's name as it will be known to the ID computer.

Example:
"name" = "ExampleShip Mark IX";

== no_boulders ==
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.

Example:
"no_boulders" = yes;

== pilot ==
Gives the ship a predefined pilot, defined in [[characters.plist]]. Can eject in pod, if available, and be captured. 
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.

Example:
"pilot" = "constrictor-mission-thief";

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: "oolite-trader", "oolite-pirate", "oolite-hunter", "oolite-police", "oolite-miner", "oolite-passenger" and "oolite-slave". 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)

== roles ==
Assigns which [[role]](s) the entity should have, that can correspond to one specific, exclusive use, or several.

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.

'''NB:''' If the ship cannot be docked to, extra care should be taken to avoid using the words '''station''' or '''carrier''' as part of any of the ship'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.

Example:
"roles" = "hunter(0.25) trader(2.0) pirate";

or an exclusive role, simply:

"roles" = "uniquely_named_role";

This has the benefit of being the only ship to be selected when a [[Script.plist|script]] calls for the ''uniquely_named_role'' ship.

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.

Example:
"roles" = "Gold";

Some roles are used by the game engine to populate systems, detect and define properties. (see also the [[System Populator]])
Such roles include 'thargoid', 'missile' and 'energybomb'.
Externally used equipment also needs specific mention of role, for example EQ_*_MINE and EQ_*_MISSILE.

== rotational_velocity ==
May be applied to a sub-entity, like the following entry to the [[Shipdata.plist#subentities|subentity]] spines of the [[Weeviloid Hunter]].
Takes the form of [[Quaternions|quaternions]]. The following example enables rotation around the Z-axis.

Example:
"rotational_velocity" = "0.707 0.0 0.0 0.707";

An explaining example taken from the Oolite Bulletin board.

The rotational velocity key is rotation per second.

For instance, if you want to rotate once per 20 seconds around the Z axis:

a = 360 ° / 20 = 18 °

[x, y, z] = [0, 0, 1]

sin a ˜ 0.30902

cos a ˜ 0.95106

Q = (0.95106, 0, 0, 0.30902)

'''shipdata.plist entry:'''
"rotational_velocity"="0.95106 0.0 0.0 0.30902";

== scan_class ==
Will alter the model's appearance on the [[IFF system]]. If this line is omitted, it will become by default a standard ship entity, appearing as yellow flag on the radar. There are other options.
* CLASS_BUOY
* CLASS_CARGO
* CLASS_MILITARY
* CLASS_MISSILE
* CLASS_POLICE
* CLASS_ROCK
* CLASS_STATION
* CLASS_THARGOID
* CLASS_NO_DRAW
(Name is valid starting with Oolite 1.74. Before it was called "scanClass". Scripts can define custom colours for ships on the [[IFF system]] so ships might have an other scan_class as is seams.)

==== Developer Note ====
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't allocate CLASS_POLICE or CLASS_THARGOID to ships lightly!

Example:
"scan_class" = "CLASS_ROCK";

== scanner_range ==
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.

Example:
"scanner_range" = "25600";

== scoop_position ==
Determines the XYZ point on the model from which cargo is scooped. (default is 0,0,0)

Example:
"scoop_position" = "0.0 -4.5 -23.0"

== script ==
Specifies a [[Scripting Oolite with JavaScript|JavaScript script]] to attach to the ship. Ship scripts are the preferred approach for scripting ships in current Oolite.

== script_info ==
A property list whose contents are available to JavaScript scripts, for whatever use they desire. It is exposed to JavaScript as the <code>[[Oolite JavaScript Reference: Ship#scriptInfo|scriptInfo]]</code> property of <code>Ship</code> objects. 
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 "NO" string will be read as true. For all normal keys its Oolite that does the conversion for you.

== script_actions ==
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.

Example:
"script_actions" =
(
"testForEquipment: EQ_CLOAKING_DEVICE",
{
"conditions"
(
"foundEquipment_bool equal NO"
)
"do"
(
"awardEquipment: EQ_CLOAKING_DEVICE"
)
"else"
(
"awardCargo: 100 Gold"
)
}
);

== setup_actions ==
Arranges a process that may be necessary for some objects, like ball turrets.

Example:
"setup_actions" =
(
"initialiseTurret"
);

== shaders ==
The ''shaders'' dictionary has the same structure as the ''[[#materials|materials]]'' dictionary. When [[Shaders in Oolite|shaders]] are available, the contents of the ''shaders'' dictionary are used in preference to those in ''materials''. If shaders are not available, the ''shaders'' dictionary is ignored.

== smooth ==
Determines if the model will use glLightModel(GL_FLAT) or glLightModel(GL_SMOOTH).

If true, then lighting effects will be interpolated across the polygons of the model, giving a more 'rounded' effect.

Asteroids, Boulders and Splinters use this effect as do some other models.

Example:
"smooth" = yes;

== spawn ==
The spawn directory is only used when a ship is added with the command: "spawnShip: shipname". 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.

Example
"spawn"
{
"facing_position" = "spu 0 0 0";
"position" = "wpu 0 0 0.2";
}

== subentities ==
An array of ''subentity definitions''. A ''subentity'' is an object attached to your ship. There are several types of subentity:
* ''Static subentities'', 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.
* ''Docks'' 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 "dock" in lowercase must be part of the old style name in order to get recognised as the dock subEntity.
* 'Ball turrets'' 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, '''ballturret'''.
* ''Flashers'' 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.

=== New-style subentity definition ===
Oolite 1.73 introduced a more flexible, dictionary-based way of specifying subentities. A new-style subentity is a dictionary using the following keys:
{| class="wikitable" border="1" cellpadding="3" cellspacing="0"
|+ Subentity definition properties
! Name !! Type !! Description
|-
| '''type''' || string || One of: “'''standard'''”, “'''ball_turret'''”, “'''flasher'''”. If not specified, “standard” is assumed.
|-
| '''subentity_key''' || string || The key of a ''shipdata.plist'' entry. Required for '''standard''' and '''ball_turret''' subentities, ignored for flashers.
|-
| '''position''' || 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 '''x''', '''y''' and '''z''' entries.) Default: (0, 0, 0).
|-
| '''orientation''' || [[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 '''w''', '''x''', '''y''' and '''z''' entries.) Default: (1, 0, 0, 0), which corresponds to no rotation.
|-
| '''is_dock''' || boolean || True if the subentity is a dock; false by default. Only applies to '''standard''' subentities. '''Note:''' this is ''not'' implied by having “dock” in the '''subentity_key''', as it is for old-style subentity definitions.
|-
| '''fire_rate''' || number || Interval between shots in seconds, for '''ball_turret''' subentities. Default: 0.5; minimum: 0.25.
|-
| '''color''' || [[Materials in Oolite#Colour specifiers|colour specifier]] || Single colour for a flasher. Ignored for non-flashers. Default value: '''redColor'''.
|-
| '''colors''' || 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 '''color'''. '''Note:''' like [[#laser_color|laser_color]], flasher colours must be “reasonably bright”.
|-
| '''frequency''' || 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.
|-
| '''initially_on''' || boolean || Specifiers whether a flasher is turned on when created. Ignored for non-flashers. Default: yes.
|-
| '''phase''' || 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.
|-
| '''size''' || positive number || Diameter of a flasher in metres. Ignored for non-flashers. Default: 8. (Why 8? I don’t remember.)
|-
|}

=== Old-style subentity definition ===
Prior to Oolite 1.73, this was the the only way to specify a subentity.

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:

==== Flashers ====
For a flasher, the entry takes the form:
*FLASHER* x y z hue frequency phase size
''*FLASHER*'' must be precisely the string “*FLASHER*”, in capitals.

''x'', ''y'' and ''z'' form the '''position'''.

''hue'' specifies the [http://en.wikipedia.org/wiki/HSL_and_HSV HSV] hue component (in degrees) of '''color'''. Saturation and value are always 1.

'''frequency''', '''phase''' and '''size''' are the same as in the new-style format.

'''initially_on''' is false.

==== Other subentities ====
For a non-flasher, the entry takes the form:
key x y z qw qx qy qz
''key'' corresponds to '''subentity_key'''.

''x'', ''y'' and ''z'' form the '''position'''.

''qw'', ''qx'', ''qy'' and ''qz'' form the '''orientation'''.

'''type''' is ''standard'' unless the command ''initialiseTurret'' is present in the [[#setup_actions|setup_actions]] of the subentity, in which case it is ''ball_turret''. Note that the ''initialiseTurret'' no longer does anything when executed in a script; its presence is only used as an indicator to set the ''is_turret'' property when old-style definitions are translated. If ''initialiseTurret'' is inside a condition, it will be ignored. The ''initialiseTurret'' command is not required or useful for turrets which are only referenced using new-style subentity definitions.

'''is_dock''' is implied by having the string “dock” (in lowercase) in the ''key''.

== track_contacts ==
Tracks the movement of the ship and sends a "CLOSE CONTACT" message to other ship AI's. It uses a time consuming tracking, so only set to true when actually used.

Example:
"track_contacts" = yes;

== throw_sparks ==
Each new ship should start in seemingly good operating condition, unless specifically told not to. (Added with oolite 1.73, false by default)

Example:
"throw_sparks" = yes;

== thrust ==
Gives the entity an 'inertia' 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).

Example:
"thrust" = "25"

== unpiloted ==
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. 
It will not add a pilot when set to false, but will remove any existing pilot when set to true.
commsMessages can only be broadcasted by piloted ships. Ships are by default piloted. cargo , rocks, missiles etc. are not piloted by default.

Example:
"unpiloted" = yes;

== view_position_.. ==
Sets the ship's 4 point-of-view positions in XYZ relative to the model.

Example:
"view_position_aft" = "0.0 5.0 -20.0";
"view_position_forward" = "0.0 1.9375 5.0";
"view_position_port" = "-11.85 2.825 -3.5";
"view_position_starboard" = "11.85 2.825 -3.5";

== weapon_energy ==
This setting works differently depending on the type of entity it's used for: 

Missiles. Changes the damage inflicted by the missile. Any value accepted.

Example:
"weapon_energy" = "180";

NPC ships. Changes the forward weapon damage to a value different to the default one. Values higher than 50 will be ignored.

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

Example:
"weapon_energy" = "17";

N.B. It does not have any effect on player ships.

== weapon_offset ==
Removed after version 1.65 (it was used to change the offsetpoint of a plasma cannon.)

== weapon_position_.. ==
Plots the 'gunmouth' points of the model's 4 potential lasers.

Example:
"weapon_position_aft" = "0.0 -5.0 -20.0";
"weapon_position_forward" = "0.0 0.0417 16.6667";
"weapon_position_port" = "-13.75 -2.0625 -1.875";
"weapon_position_starboard" = "13.75 -2.0625 -1.875";

= Station keys=
The following keys are only used by stations or carriers.

== allows_auto_docking ==
When set false for a station, this station will not allow the use of a docking computer. Default value in "yes". (Planned for Oolite 1.75)

Example:
allows_auto_docking = "no";

== allows_fast_docking ==
When set true for a station, this station will allow fast docking with the docking computer. Default value in "no". (Planned for Oolite 1.75)

Example:
allows_fast_docking = "yes";

== defense_ship ==
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]]

Example:
defense_ship" = "my_defender";

== defense_ship_role ==
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 "police"/"interceptor" for normal stations and "hermit-ship" 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: "defense_ship"

Example:
"defense_ship_role" = " carrier_defenders";

== docking_pattern_model ==
The name of the .dat file that is used for displaying the docking pattern for this station only. Default is "ring.dat". (Introduced in version 1.74)

Example:
"docking_pattern_model" = "ring.dat";

== equipment_price_factor ==
Equipment price mask for dockables.

Example:
"equipment_price_factor" = "4.5";

== equivalent_tech_level ==
Sets shipyard tech level for dockables, different to the local system tech_level. Default value is the system tech_level.

Example:
"equivalent_tech_level" = 1;

== has_npc_traffic ==
Determines if a station has NPC traffic. Default is "yes". When set to "no the station will not launch random traders. Only rotating stations will launch traders when this is set to true.

Example:
"has_npc_traffic" = yes;

== has_patrol_ships ==
Determines if a station launches periodic patrol ships. Default is "no". Main stations always have patrol ships. (Planned for Oolite 1.75)

Example:
"has_patrol_ships" = yes;

== has_shipyard ==
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 "no", but for main stations has_shipyard is always "yes". (Name is valid starting with Oolite 1.74. Before it was called "hasShipyard".)

Example:
"has_shipyard" = "0.75";

or

"has_shipyard" = (
systemGovernment_number morethan 3,
systemEconomy_number lessthan 4
)

== interstellar_undocking ==
When set true for a station, this station will allow interstellar docking and undocking in interstellar space. When set to "no" the player docks in nearby normal space. Default value in "no". (Planned for Oolite 1.75)

Example:
interstellar_undocking = "yes";

==is_carrier==
Added as a tag for making the model be considered a carrier or station. An alternative to including ''carrier'' or ''station'' 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 "isCarrier".)

Example:
"is_carrier" = yes;

== market ==
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

Example:
"market" = "none";

== max_defense_ships ==
Designates how many ships a dockable entity (station, carrier) can launch in defense. Default value is 3. See also [[Station Ships]]

Example:
"max_defense_ships" = "10";

== max_police ==
Designates how many police or patrol ships a dockable entity (station, carrier) can launch. Default value is 8. See also [[Station Ships]]

Example:
"max_police " = "10";

== max_scavengers ==
Designates how many scavengers or miners a dockable entity (station, carrier) can launch. Default value is 3. See also [[Station Ships]]

Example:
"max_scavengers" = "10";

== port_dimensions ==
Defines the size of the docking port and takes 3 numbers, separated by "x". 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.

Example:
"port_dimensions" = "65x30x500";

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) 
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.

== port_radius ==
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.

Example:
"port_radius" = "500";

== requires_docking_clearance ==
Sets the requirement for docking clearance. Default is "no". See also [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|DockingClearance]]

Example:
"requires_docking_clearance" = yes;

==rotating==
Given to a station when rotation is desired. Default is "no".

Example:
"rotating" = yes;

== station_roll ==
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. (Key is added in Oolite 1.74.2)

Example:
"station_roll" = "-1.5"

--------------------------------------------------------------------------------
[[Category:Oolite]]
[[Category:Oolite scripting]]

Shipdata.plist

2011-03-22T23:35:32Z

Frame: /* rotational_velocity */

'''shipdata.[[plist]]''' 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's sake, listed alphabetically:

= Ship keys=
The following keys are used by all ships
==accuracy==
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 assings to the missile the accuracy value of 0.0, which corresponds to the standard missile tracking behaviour.

Used with NPC ships it enlarges the chance of shooting at greater distances. Value with NPC ships is between -5 and 10.

Example:
"accuracy" = 8;

== aft_eject_position ==
Determines the XYZ point on the model from which cargo is ejected.

Example:
"aft_eject_position" = "0.0 -4.5 -23.0";

== aft_weapon_type ==
Assigns the ship's laser.
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE).

Example:
"aft_weapon_type" = "WEAPON_BEAM_LASER";

== ai_type ==
Assigns an AI to the entity. This may be a previously existing AI, or one custom made for the occasion.

Example:
"ai_type" = "pirateAI.plist";

== auto_ai ==
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.
Example:
"auto_ai" = yes;
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.

== beacon ==
A special feature for beacons and navigation aids.
The string can be anything - the first letter is what's displayed in the advanced space compass.

Example:
"beacon" = "X-code";

The following characters are known to be used as identifiers for '''stations and other fixed objects''' (listed with their respective OXPs):

A = Astromine (Commies)
B = Black Monk Monastery (Black Monks)
A Seedy Space Bar (Random Hits)
Nemeanian Military Base (Assassins)
C = CoachWhip hOopy Casino (Hoopy Casino)
Pi-42 Con Store (Your Ad Here)
F = Collective Zero-G Factory (Commies)
Collective SLAPU (Commies)
Imperial AstroFactory (Dictators)
G = Griff Research Ltd Orbital Base (Assassins)
GRS Buoy Factory (GRS Buoy Repair)
H = Hacker Outpost (Anarchies)
Deep Space Hoopy Hotel : Hades Branch (Assassins)
L = The Link Base (Ionics)
Deep Space Hoopy Hotel : Lernean Branch (Assassins)
N = Main Station Beacon
P = Tianve Pulsar Monitoring Station (Tianve)
R = Rock Hermit (Rock Hermit Locator)
Augeaian Orbital Repair Facility (Assassins)
Rebel Outpost (Assassins)
Q = Hesperides Wiseguy Way-Station (Assassins)
S = Navy SecCom Station (Galactic Navy)
Special Branch Orbital Headquarters (Assassins)
T = Taranis Corporation HQ (Taranis)
W = Witchpoint Buoy
Z = Free Trade Zone (Free Trade Zone)

The following characters are known to be used for '''non-station objects that may appear anywhere''':

H = Homing Beacon (ett Homing Beacon)

The following characters should not be assigned easily to stations or ships that are supposed to appear anywhere, because they are likely to be used for ships in other OXPs:

M = Mark
T = Target
V = Victim
X = general marker
+ = general marker

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) 
Example in shipdata:
"beacon" = "fuelStation_location";
Example in descriptions.plist
"fuelStation_location" = (1, 2, -3, 2, -3, -4, 3, -4, 3, 4, -3, 4, -3, 3, 2, 3, 2, -3, 1, -3 );
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.

== bounty ==
Sets a Cr. reward on the NPC'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.

Example:
"bounty" = 50;

== cargo_carried ==
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.

Example:
"cargo_carried" = "Gold";

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. 
It is possible to define a mix of random cargo for ships by using the string "SCARCE_GOODS" or "PLENTIFUL_GOODS", 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.) 
To make cargo_carried working for ships, the cargo_type must be "CARGO_NOT_CARGO" to define the ship not being cargo itself. (see below)

== [[cargo_type]] ==
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. Works since Oolite 1.71 also for pods spawn by a script. CARGO_CARRIED needs in addition an second key cargo_carried that specifies the cargo. (see below) 

Example:
"cargo_type" = "CARGO_RANDOM";

More control of contents of barrels is available through the CARGO_CARRIED string.

Example:
"cargo_type" = "CARGO_CARRIED";
"cargo_carried" = "4 Gold";

You can also specify the cargo of a ship. use "cargo_type" = CARGO_NOT_CARGO and define the contents of the barrels it will give with "cargo_carried". In that case there must be no quantity defined, only the type of [[commodity]].

Example:
"cargo_type" = "CARGO_NOT_CARGO";
"cargo_carried" = "Computers";

Another notable type of cargo is the scripted item CARGO_SCRIPTED_ITEM, as examplified by the cloacking device. When CARGO_SCRIPTED_ITEM is defined, the barrels will trigger scooping events for the ship-scripts. Other barrels don't trigger scooping events. 
The cargo barrels are stored in the ships hold like normal barrels when a cargo was defined for them with the JS method "setCargo". 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.

== cloak_automatic ==
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) Key added with Oolite 1.75

Example:
"cloak_automatic" = no;

== cloak_passive ==
When true, any firing of laser will deactivate the cloak. (False by default)

Example:
"cloak_passive" = yes;

==conditions==
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.

Example:
"conditions" = (
"systemGovernment_number equal 3",
"systemEconomy_number lessthan 4"
);

== counts_as_kill ==
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. Key is added with Oolite 1.75

Example:
"counts_as_kill" = no;

== custom_views==
Will add the ability to display custom POVs of the player ship, in game toggled by pressing '''v'''.

This is an array with any number of entries, one for each view, each with:
*a '''view_description''' - giving a textual description of the view.
*a '''view_position''' - relative to the origin of the ship model.
*a '''view_orientation''' - this is a [[Quaternions|quaternion]] expressing a rotation from directly forwards.
*a '''weapon_facing''' - FORWARD, AFT, PORT or STARBOARD. The weapon that will fire when that view is selected.

The view_position is best chosen by selecting a facet, line or point in Wings and copying down the coordinates.

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:

W = the cosine of half the angle rotated about the axis xyz 
X = the sine of half the angle rotated about xyz, multiplied by x 
Y = the sine of half the angle rotated about xyz, multiplied by y 
Z = the sine of half the angle rotated about xyz, multiplied by z 

Four decimal places are probably enough accuracy for these values.

Example:
custom_views =
(
{
view_description = "Front View";
view_orientation = "0.0 0.0 1.0 0.0";
view_position = "0.0 30.0 200.0";
weapon_facing = "FORWARD";
}
);

== death_actions ==
Gives an opportunity to have a ship's death trigger one or a set of [[Shipdata.plist#script_actions|script_actions]]. It contains an array of legacy script expressions.

Example:
"death_actions" = ("spawn: explosive_shrapnel 1");

== debris_role ==
Specifies the kind of debris an asteroid or boulder generates. When not defined they default to generating 'ships' with role "boulder" or "splinter". (Key added with Oolite 1.74)

Example:
"debris_role" = "my_boulder_foo";

== density ==
This real value is used to calculate a ships total mass. Default is 1.0

Example:
"density" = 1.5;

== display_name ==
States the model's name as it will be known to the ID computer. By default this is the same as "name". Added for multilingual oolite.

Example:
"display_name" = "ExampleShip Mark IX";

== energy_recharge_rate ==
The rate at which energy is replenished. Stations are at 100, Adders at 2. (Default value: 1)

Example:
"energy_recharge_rate" = "3.5";

== escape_pod_model ==
With this entry ships can have custom escape pods. (starting from version 1.65) You have to specify the '''role''' of your custom escape pod (not its entry-name).

Example:
"escape_pod_model" = "custom_pod";

== escorts ==
Determines how many escorts an NPC shall have. Maximum is 16.

Example:
"escorts" = 4;
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't escort a mother with CLASS_POLICE. 
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.

== escort_role ==
Assigns the specific ship type to be the escort, by the ship's role. (Before Oolite 1.74 only the name "escort-role" is accepted.)

Example:
"escort_role" = "my_custom_escort_role";
Escort ships will use the escortAI.plist unless "auto_ai" is set to false.

== escort_ship ==
Assigns the specific ship type to be the escort, by the ship's name. (Before Oolite 1.74 only the name "escort-ship" is accepted.)

Example:
"escort_ship" = "cobramk1";
Escort ships will use the escortAI.plist unless "auto_ai" is set to false.

== exhaust ==
The XYZ position(s) of exhaust plume(s), and the XYZ of the plume shape, ergo

x y z width height length

'''x y z''' is the position relative to the origin of the main model.

'''width''' in meters, how wide a plume is on x axis. (x radius)

'''height''' in meters, how tall a plume is on y axis. (y radius)

'''length''' 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)

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)

Example:
"exhaust" = (
"5 0.0 -25 6.0 4.0 10.0",
"-5 0.0 -25 6.0 4.0 10.0"
);

== extra_cargo ==
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.

Example:
"extra_cargo" = 25;

== forward_weapon_type ==
Assigns the ship's laser.
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE).

Example:
"forward_weapon_type" = "WEAPON_BEAM_LASER";

== frangible ==
Determines if eventual sub-entities are "loose". By default any given object is already frangible, so the use of this line must be to negate that.
If set to false, the object plus subentities will be regarded as a single object.
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.

Example:
"frangible" = no;

== fragment_chance ==
Determines if a ship breaks apart into fragments and generates parts with role "wreckage". By chance factor, or true/false. Default is 90% chance.
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 -> 1.25s)

Example:
"fragment_chance" = no;

== fuel ==
Determines an NPC ship's fuel storage, which will affect how it uses its Fuel Injectors.

Example:
"fuel" = 70;

== has_cloaking_device ==
Determines if a ship has a cloacking device installed. By chance factor, or true/false.

Example:
"has_cloaking_device" = 0.5;

== has_ecm ==
Determines if a ship has the E.C.M system installed. By chance factor, or true/false.

Example:
"has_ecm" = 0.5;
or
"has_ecm" = no;

== has_energy_bomb ==
Determines if a ship has an energy bomb. If it has one, it might launch a mine with role "energy_bomb" as part of his fleeing behavior. currently the only build-in mine with this role is the q-bomb. 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.

Example:
"has_energy_bomb" = yes;

== has_escape_pod ==
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, '''has_escape_pod''' must be set to a numeric value corresponding to the escape pods present on board.

Examples:
has_escape_pod = no;
has_escape_pod = 0.75;
has_escape_pod = 3;

== has_fuel_injection ==
Determines if a ship has the witchdrive fuel injector.

Example:
"has_fuel_injection" = 0.99;

==has_military_jammer==
Determines if a ship has a military jammer. Ships equipped with this item become invisible on the radar.
Example:
"has_military_jammer" = 0.75;

==has_military_scanner_filter==
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.
Example:
"has_military_scanner_filter" = 0.50;

== has_scoop ==
Determines if a ship has a fuel/cargo scoop.

Example:
"has_scoop" = no;

== has_scoop_message ==
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)

Example:
"has_scoop_message" = no;

== has_shield_booster==
Determines if a ship has the shield booster. (enlarges max energy with 256)

Example:
"has_shield_booster" = 0.80;

== has_shield_enhancer ==
Determines if a ship has the coveted shield enhancer. (enlarges max energy with 256 and raises energy recharge rate with 50%)

Example:
"has_shield_enhancer" = 0.45;

== heat_insulation ==
This real number gives the amount of heat insulation of a ship. Default is 1.0 Only for NPC ships. Playes ships can have the equipment EQ_HEAT_SHIELDING with gives the player than a heat_insulation of 2.0

Example:
"heat_insulation" = "2.0";

== hud ==
Used for a playership, to assign another HUD than the default one.

Example:
"hud" = "specialhud.plist";

== hyperspace_motor ==
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)

Examples:
"hyperspace_motor" = no;

hyperspace_motor=NO;

== hyperspace_motor_spin_time ==
Used to modify jump countdown time. Default = 15.

Examples:
"hyperspace_motor_spin_time" = "15";

==is_external_dependency==
This key should be added to ships that use like_ship references to ships in other oxps but don't depend on them. Normally will Oolite write errors in the log when it can't resolve a like_ship reference. When this key is set to YES, it will suppress the error generation. WARNING: only set this key to YES when the model won't get added to the system without the other oxp installed or you will miss a valuable warning.

Example:
"is_external_dependency" = yes;

==is_submunition==
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.

Example:
"is_submunition" = yes;

==is_template==
Set this to yes/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.

Example:
"is_template" = yes;

== laser_color ==
Determines a ship's laser colour.

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.

Example:
"laser_color" = "cyanColor"

== launch_actions ==
Triggers a script on the entity just after setup, also when called by spawn and addShip methods.
Can be used to change to a custom AI, when a ship is generated by standard role.
[[Shipdata.plist#script_actions|script_actions]]

Example:
"role = trader";
"launch_actions" = (
"setAITo: pirateAI.plist"
);

== like_ship ==
Allows a shipdata entry (of a ship with many matching characteristics to another) to be short and sweet. With '''like_ship''' you can reference to another existing shipdata entry, and then only specify the differences to the 'original'. It takes the unique '''entry-identifier''' as argument. Of course you have to make sure that the 'original' you are referring to actually exists, or Oolite won't be able to create your ship.

Works well together with the [[#is_template|is_template]]-key.

Example:
"my_ship" = {
"like_ship" = "adder";
"max_flight_speed" = "700";
"name" = "Freak Turbo Adder";
},

== likely_cargo ==
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.

Example:
"likely_cargo" = "2";

== materials ==
See [[Materials in Oolite]].

== max_cargo ==
Sets the ship'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.

Example:
"max_cargo" = "5";

== max_energy ==
Sets the ship's energy value. (Default value: 200)

Example:
"max_energy" = "300";

== max_flight_pitch ==
Sets pitch factor. Will usually range from a sluggish 0.6 to a very sensitive 3.0

Example:
"max_flight_pitch" = "2.2";

== max_flight_roll ==
Sets roll factor. Will usually range from 0.8 to 4.6.

Example:
"max_flight_roll" = "4.2";

== max_flight_speed ==
Sets the model's top speed. Interceptors fly at 520 (0.52 LM), Shuttles at 80.

Example:
"max_flight_speed" = "320";

== max_flight_yaw ==
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

Example:
"max_flight_yaw" = "2.2";

== max_missiles ==
Sets a ship's missile limit. Maximum allowable value for the player is 16 and for npc ships 32. When not defined, the value with "missiles" is used as max_missiles. When defining more than a few missiles, it could be wise to also define value for "missile_load_time" to avoid massive missile launches. npc ships are more likely to fire missiles the more they carry.

Example:
"max_missiles" = "1";

== missile_launch_position ==
Determines the XYZ point on the model from which a missile is launched.

Example:
"missile_launch_position" = "0.0 -2.25 10.0";

This position should lie outside the bounding box of the entity and not just outside of the ships mesh. If it does lie inside the bounding box, the launch position is shifted along its direction until the launched missile lies outside the bounding box. The collision radius of the launched missile is taken into account. The collision radius for a plain missile is 4.52 meter.

== missile_load_time ==
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.

Example:
"missile_load_time" = "2.1";

== missiles ==
Sets a ship's probable number of missiles.

Example:
"missiles" = "0";

== missile_role ==
Defines the entity that is launched as missile. Can specify a certain missile-type or any other ship-entity by role. Only applies to NPC's, player-ship dependacies must be defined in the [[shipyard.plist]]. If no missile_role is defined and a NPC ship launches a missile he most often chooses the default missile but sometimes chooses one at random from all ships with role missile inside one of the installed OXP's.

Example:
"missile_role" = "thargon";

== model ==
Assigns the entity's corresponding '''.dat''' file that will be found with the exact same name in the ''Models'' folder.

Example:
"model" = "example_ship.dat";

== name ==
States the model's name as it will be known to the ID computer.

Example:
"name" = "ExampleShip Mark IX";

== no_boulders ==
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.

Example:
"no_boulders" = yes;

== pilot ==
Gives the ship a predefined pilot, defined in [[characters.plist]]. Can eject in pod, if available, and be captured. 
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.

Example:
"pilot" = "constrictor-mission-thief";

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: "oolite-trader", "oolite-pirate", "oolite-hunter", "oolite-police", "oolite-miner", "oolite-passenger" and "oolite-slave". 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)

== roles ==
Assigns which [[role]](s) the entity should have, that can correspond to one specific, exclusive use, or several.

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.

'''NB:''' If the ship cannot be docked to, extra care should be taken to avoid using the words '''station''' or '''carrier''' as part of any of the ship'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.

Example:
"roles" = "hunter(0.25) trader(2.0) pirate";

or an exclusive role, simply:

"roles" = "uniquely_named_role";

This has the benefit of being the only ship to be selected when a [[Script.plist|script]] calls for the ''uniquely_named_role'' ship.

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.

Example:
"roles" = "Gold";

Some roles are used by the game engine to populate systems, detect and define properties. (see also the [[System Populator]])
Such roles include 'thargoid', 'missile' and 'energybomb'.
Externally used equipment also needs specific mention of role, for example EQ_*_MINE and EQ_*_MISSILE.

== rotational_velocity ==
May be applied to a sub-entity, like the following entry to the [[Shipdata.plist#subentities|subentity]] spines of the [[Weeviloid Hunter]].
Takes the form of [[Quaternions|quaternions]]. The following example enables rotation around the Z-axis.

Example:
"rotational_velocity" = "0.707 0.0 0.0 0.707";

an explaining example taken from the Oolite Bulletin board.

The rotational velocity key is rotation per second.

For instance, if you want to rotate once per 20 seconds around the Z axis:

a = 360 ° / 20 = 18 °

[x, y, z] = [0, 0, 1]

sin a ˜ 0.30902

cos a ˜ 0.95106

Q = (0.95106, 0, 0, 0.30902)

"rotational_velocity"="0.95106 0.0 0.0 0.30902";

== scan_class ==
Will alter the model's appearance on the [[IFF system]]. If this line is omitted, it will become by default a standard ship entity, appearing as yellow flag on the radar. There are other options.
* CLASS_BUOY
* CLASS_CARGO
* CLASS_MILITARY
* CLASS_MISSILE
* CLASS_POLICE
* CLASS_ROCK
* CLASS_STATION
* CLASS_THARGOID
* CLASS_NO_DRAW
(Name is valid starting with Oolite 1.74. Before it was called "scanClass". Scripts can define custom colours for ships on the [[IFF system]] so ships might have an other scan_class as is seams.)

==== Developer Note ====
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't allocate CLASS_POLICE or CLASS_THARGOID to ships lightly!

Example:
"scan_class" = "CLASS_ROCK";

== scanner_range ==
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.

Example:
"scanner_range" = "25600";

== scoop_position ==
Determines the XYZ point on the model from which cargo is scooped. (default is 0,0,0)

Example:
"scoop_position" = "0.0 -4.5 -23.0"

== script ==
Specifies a [[Scripting Oolite with JavaScript|JavaScript script]] to attach to the ship. Ship scripts are the preferred approach for scripting ships in current Oolite.

== script_info ==
A property list whose contents are available to JavaScript scripts, for whatever use they desire. It is exposed to JavaScript as the <code>[[Oolite JavaScript Reference: Ship#scriptInfo|scriptInfo]]</code> property of <code>Ship</code> objects. 
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 "NO" string will be read as true. For all normal keys its Oolite that does the conversion for you.

== script_actions ==
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.

Example:
"script_actions" =
(
"testForEquipment: EQ_CLOAKING_DEVICE",
{
"conditions"
(
"foundEquipment_bool equal NO"
)
"do"
(
"awardEquipment: EQ_CLOAKING_DEVICE"
)
"else"
(
"awardCargo: 100 Gold"
)
}
);

== setup_actions ==
Arranges a process that may be necessary for some objects, like ball turrets.

Example:
"setup_actions" =
(
"initialiseTurret"
);

== shaders ==
The ''shaders'' dictionary has the same structure as the ''[[#materials|materials]]'' dictionary. When [[Shaders in Oolite|shaders]] are available, the contents of the ''shaders'' dictionary are used in preference to those in ''materials''. If shaders are not available, the ''shaders'' dictionary is ignored.

== smooth ==
Determines if the model will use glLightModel(GL_FLAT) or glLightModel(GL_SMOOTH).

If true, then lighting effects will be interpolated across the polygons of the model, giving a more 'rounded' effect.

Asteroids, Boulders and Splinters use this effect as do some other models.

Example:
"smooth" = yes;

== spawn ==
The spawn directory is only used when a ship is added with the command: "spawnShip: shipname". 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.

Example
"spawn"
{
"facing_position" = "spu 0 0 0";
"position" = "wpu 0 0 0.2";
}

== subentities ==
An array of ''subentity definitions''. A ''subentity'' is an object attached to your ship. There are several types of subentity:
* ''Static subentities'', 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.
* ''Docks'' 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 "dock" in lowercase must be part of the old style name in order to get recognised as the dock subEntity.
* 'Ball turrets'' 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, '''ballturret'''.
* ''Flashers'' 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.

=== New-style subentity definition ===
Oolite 1.73 introduced a more flexible, dictionary-based way of specifying subentities. A new-style subentity is a dictionary using the following keys:
{| class="wikitable" border="1" cellpadding="3" cellspacing="0"
|+ Subentity definition properties
! Name !! Type !! Description
|-
| '''type''' || string || One of: “'''standard'''”, “'''ball_turret'''”, “'''flasher'''”. If not specified, “standard” is assumed.
|-
| '''subentity_key''' || string || The key of a ''shipdata.plist'' entry. Required for '''standard''' and '''ball_turret''' subentities, ignored for flashers.
|-
| '''position''' || 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 '''x''', '''y''' and '''z''' entries.) Default: (0, 0, 0).
|-
| '''orientation''' || [[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 '''w''', '''x''', '''y''' and '''z''' entries.) Default: (1, 0, 0, 0), which corresponds to no rotation.
|-
| '''is_dock''' || boolean || True if the subentity is a dock; false by default. Only applies to '''standard''' subentities. '''Note:''' this is ''not'' implied by having “dock” in the '''subentity_key''', as it is for old-style subentity definitions.
|-
| '''fire_rate''' || number || Interval between shots in seconds, for '''ball_turret''' subentities. Default: 0.5; minimum: 0.25.
|-
| '''color''' || [[Materials in Oolite#Colour specifiers|colour specifier]] || Single colour for a flasher. Ignored for non-flashers. Default value: '''redColor'''.
|-
| '''colors''' || 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 '''color'''. '''Note:''' like [[#laser_color|laser_color]], flasher colours must be “reasonably bright”.
|-
| '''frequency''' || 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.
|-
| '''initially_on''' || boolean || Specifiers whether a flasher is turned on when created. Ignored for non-flashers. Default: yes.
|-
| '''phase''' || 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.
|-
| '''size''' || positive number || Diameter of a flasher in metres. Ignored for non-flashers. Default: 8. (Why 8? I don’t remember.)
|-
|}

=== Old-style subentity definition ===
Prior to Oolite 1.73, this was the the only way to specify a subentity.

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:

==== Flashers ====
For a flasher, the entry takes the form:
*FLASHER* x y z hue frequency phase size
''*FLASHER*'' must be precisely the string “*FLASHER*”, in capitals.

''x'', ''y'' and ''z'' form the '''position'''.

''hue'' specifies the [http://en.wikipedia.org/wiki/HSL_and_HSV HSV] hue component (in degrees) of '''color'''. Saturation and value are always 1.

'''frequency''', '''phase''' and '''size''' are the same as in the new-style format.

'''initially_on''' is false.

==== Other subentities ====
For a non-flasher, the entry takes the form:
key x y z qw qx qy qz
''key'' corresponds to '''subentity_key'''.

''x'', ''y'' and ''z'' form the '''position'''.

''qw'', ''qx'', ''qy'' and ''qz'' form the '''orientation'''.

'''type''' is ''standard'' unless the command ''initialiseTurret'' is present in the [[#setup_actions|setup_actions]] of the subentity, in which case it is ''ball_turret''. Note that the ''initialiseTurret'' no longer does anything when executed in a script; its presence is only used as an indicator to set the ''is_turret'' property when old-style definitions are translated. If ''initialiseTurret'' is inside a condition, it will be ignored. The ''initialiseTurret'' command is not required or useful for turrets which are only referenced using new-style subentity definitions.

'''is_dock''' is implied by having the string “dock” (in lowercase) in the ''key''.

== track_contacts ==
Tracks the movement of the ship and sends a "CLOSE CONTACT" message to other ship AI's. It uses a time consuming tracking, so only set to true when actually used.

Example:
"track_contacts" = yes;

== throw_sparks ==
Each new ship should start in seemingly good operating condition, unless specifically told not to. (Added with oolite 1.73, false by default)

Example:
"throw_sparks" = yes;

== thrust ==
Gives the entity an 'inertia' 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).

Example:
"thrust" = "25"

== unpiloted ==
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. 
It will not add a pilot when set to false, but will remove any existing pilot when set to true.
commsMessages can only be broadcasted by piloted ships. Ships are by default piloted. cargo , rocks, missiles etc. are not piloted by default.

Example:
"unpiloted" = yes;

== view_position_.. ==
Sets the ship's 4 point-of-view positions in XYZ relative to the model.

Example:
"view_position_aft" = "0.0 5.0 -20.0";
"view_position_forward" = "0.0 1.9375 5.0";
"view_position_port" = "-11.85 2.825 -3.5";
"view_position_starboard" = "11.85 2.825 -3.5";

== weapon_energy ==
This setting works differently depending on the type of entity it's used for: 

Missiles. Changes the damage inflicted by the missile. Any value accepted.

Example:
"weapon_energy" = "180";

NPC ships. Changes the forward weapon damage to a value different to the default one. Values higher than 50 will be ignored.

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

Example:
"weapon_energy" = "17";

N.B. It does not have any effect on player ships.

== weapon_offset ==
Removed after version 1.65 (it was used to change the offsetpoint of a plasma cannon.)

== weapon_position_.. ==
Plots the 'gunmouth' points of the model's 4 potential lasers.

Example:
"weapon_position_aft" = "0.0 -5.0 -20.0";
"weapon_position_forward" = "0.0 0.0417 16.6667";
"weapon_position_port" = "-13.75 -2.0625 -1.875";
"weapon_position_starboard" = "13.75 -2.0625 -1.875";

= Station keys=
The following keys are only used by stations or carriers.

== allows_auto_docking ==
When set false for a station, this station will not allow the use of a docking computer. Default value in "yes". (Planned for Oolite 1.75)

Example:
allows_auto_docking = "no";

== allows_fast_docking ==
When set true for a station, this station will allow fast docking with the docking computer. Default value in "no". (Planned for Oolite 1.75)

Example:
allows_fast_docking = "yes";

== defense_ship ==
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]]

Example:
defense_ship" = "my_defender";

== defense_ship_role ==
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 "police"/"interceptor" for normal stations and "hermit-ship" 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: "defense_ship"

Example:
"defense_ship_role" = " carrier_defenders";

== docking_pattern_model ==
The name of the .dat file that is used for displaying the docking pattern for this station only. Default is "ring.dat". (Introduced in version 1.74)

Example:
"docking_pattern_model" = "ring.dat";

== equipment_price_factor ==
Equipment price mask for dockables.

Example:
"equipment_price_factor" = "4.5";

== equivalent_tech_level ==
Sets shipyard tech level for dockables, different to the local system tech_level. Default value is the system tech_level.

Example:
"equivalent_tech_level" = 1;

== has_npc_traffic ==
Determines if a station has NPC traffic. Default is "yes". When set to "no the station will not launch random traders. Only rotating stations will launch traders when this is set to true.

Example:
"has_npc_traffic" = yes;

== has_patrol_ships ==
Determines if a station launches periodic patrol ships. Default is "no". Main stations always have patrol ships. (Planned for Oolite 1.75)

Example:
"has_patrol_ships" = yes;

== has_shipyard ==
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 "no", but for main stations has_shipyard is always "yes". (Name is valid starting with Oolite 1.74. Before it was called "hasShipyard".)

Example:
"has_shipyard" = "0.75";

or

"has_shipyard" = (
systemGovernment_number morethan 3,
systemEconomy_number lessthan 4
)

== interstellar_undocking ==
When set true for a station, this station will allow interstellar docking and undocking in interstellar space. When set to "no" the player docks in nearby normal space. Default value in "no". (Planned for Oolite 1.75)

Example:
interstellar_undocking = "yes";

==is_carrier==
Added as a tag for making the model be considered a carrier or station. An alternative to including ''carrier'' or ''station'' 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 "isCarrier".)

Example:
"is_carrier" = yes;

== market ==
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

Example:
"market" = "none";

== max_defense_ships ==
Designates how many ships a dockable entity (station, carrier) can launch in defense. Default value is 3. See also [[Station Ships]]

Example:
"max_defense_ships" = "10";

== max_police ==
Designates how many police or patrol ships a dockable entity (station, carrier) can launch. Default value is 8. See also [[Station Ships]]

Example:
"max_police " = "10";

== max_scavengers ==
Designates how many scavengers or miners a dockable entity (station, carrier) can launch. Default value is 3. See also [[Station Ships]]

Example:
"max_scavengers" = "10";

== port_dimensions ==
Defines the size of the docking port and takes 3 numbers, separated by "x". 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.

Example:
"port_dimensions" = "65x30x500";

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) 
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.

== port_radius ==
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.

Example:
"port_radius" = "500";

== requires_docking_clearance ==
Sets the requirement for docking clearance. Default is "no". See also [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|DockingClearance]]

Example:
"requires_docking_clearance" = yes;

==rotating==
Given to a station when rotation is desired. Default is "no".

Example:
"rotating" = yes;

== station_roll ==
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. (Key is added in Oolite 1.74.2)

Example:
"station_roll" = "-1.5"

--------------------------------------------------------------------------------
[[Category:Oolite]]
[[Category:Oolite scripting]]

Commodities.plist

2011-03-20T16:08:04Z

Frame: /* For Example: */

Commodities.[[plist]] is a dictionary with an entry for each type of market. Three are defined initially, 'default' containing the default (natch) information for each of the [[commodities]] in the universe, 'rockhermit' which has the prices and quantities available at a [[rock hermit]] and 'none' which has prices and price variation set to zero. If you create a commodities.plist for your own station, you have to put your station's '''primary role''' here. (Starting with Oolite 1.74 it will be possible to add a '''market''' key to the shipdata pointing to one of the defined markets in a commodities.plist)

Each market is an array of 17 commodities, each in itself an array of 10 items:
# The name of the commodity
# Units available at a market (this is calculated at each marketplace)
# Price per unit at a market (this is calculated at each marketplace)
# The base price per unit MARKET_BASE_PRICE
# An adjustment to price based on the economy MARKET_ECO_ADJUST_PRICE
# An adjustment to units availble based on the economy MARKET_ECO_ADJUST_QUANTITY
# The base quantity available to a market MARKET_BASE_QUANTITY
# A 'mask' which defines how the price varies MARKET_MASK_PRICE
# A 'mask' which defines how the quantity varies MARKET_MASK_QUANTITY
# The unit of quantity (0 == tons, 1 == kilos, 2 == grams)

At each market prices and quantities are calculated from values 4..9 and a random value from 0-255 (MARKET_RND) according to a complex series of steps:

 
<code>// calculate the local price </code> 
<code>price = (MARKET_BASE_PRICE + (MARKET_RND & MARKET_MASK_PRICE) + (economy * MARKET_ECO_ADJUST_PRICE)) & 255</code> 
 
<code>// calculate the local quantity available</code> 
<code>quantity = (MARKET_BASE_QUANTITY + (MARKET_RND & MARKET_MASK_QUANTITY) - (economy * MARKET_ECO_ADJUST_QUANTITY)) & 255</code> 
 
<code>// if the quantity gets too high it's zeroed</code> 
<code>if (quantity > 127) quantity = 0</code> 
 
<code>// limit the quantity to 0..63 units</code> 
<code>quantity &= 63</code> 
 
<code>// price in credits is the final price x 0.4</code> 
<code>price *= 0.4</code> 

Thus if you wish the price of a commodity to be higher in good economies you set MARKET_ECO_ADJUST_PRICE to a high positive value. If you require the price to vary less randomly you set MARKET_MASK_PRICE to a low value (1 or 0). You can work out the rest I'm sure!

== For Example: ==

* '''[[Commodities#Radioactives|Radioactives]]'''
* MARKET_BASE_PRICE = 65
* MARKET_ECO_ADJUST_PRICE = -3
* MARKET_ECO_ADJUST_QUANTITY = -3
* MARKET_BASE_QUANTITY = 2
* MARKET_MASK_PRICE = 7
* MARKET_MASK_QUANTITY = 7

If MARKET_RND is 133 and the economy is 3 ([[Planetinfo.plist#Economy|Mainly Industrial]]) then:

* price = (65 + (133 & 7) + (3 * -3)) & 255 = (65 + 5 - 9) & 255 = '''61'''
* quantity = (2 + (133 & 7) - (3 * -3)) & 255 = (2 + 5 + 9) & 255 = '''16'''

61 * 0.4 = '''24.4 credits per ton, 16 tons available.'''

Since (MARKET_RND & MARKET_MASK_PRICE) will always be a value between 0 and 7, this sets the minimum price per ton of [[Commodities#Radioactives|Radioactives]] at a [[Planetinfo.plist#Economy|Poor Agricultural]] economy at 17.6 Cr. and the maximum price per ton at a [[Planetinfo.plist#Economy|Rich Industrial]] economy at 28.8 Cr.

[[Category:Oolite]]
[[Category:Oolite_scripting]]

AFE FAQ8

2010-10-16T18:40:18Z

Frame: /* 98) Is that it? */

== 98) Is that it? ==

98.1) The Elite Project
* 98.1.1) What is it?
* 98.1.2) How can I keep tabs on it?

98.2) The Galileo Project
* 98.2.1) What is it?
* 98.2.2) How can I keep tabs on it?

98.3) X
* 98.3.1) What is it?
* 98.3.2) How can I keep tabs on it?

For the time being. According to recent press, David Braben is working on
Elite 4. Very little is known about this, not even the final intended name.
Ian Bell also reports an ongoing project on his homepage but gives no
details. Maybe it's another Elite. Maybe not. Who knows?

Vague details on:
Matt Dibb's page - http://www.hoopla.cwc.com/lotf/
Jades' Elite 4 page.

''above link is dead as tested at october 16th 2010''

These aren't your only hopes, though. There are other games in the pipeline:

----

=== 98.1) The Elite Project ===

'''98.1.1) What is it? '''

An attempt to write a single-player game with the feel and open-
endedness of Elite. As a result of a recent debate on the likely
stance of the original authors to copyright, no features
copyrightable to Elite are going to be included, including the
name. Provisional name: Stardreamer.

This game will be public domain.

'''98.1.2) How can I keep tabs on it?'''

See http://www.uni-leipzig.de/~troeger/tep/ for the most
comprehensive list of links about.

The latest code is available from
http://www-stu.cai.cam.ac.uk/~jaj22/tep/

=== 98.2) The Galileo Project ===

'''98.2.1) What is it?'''

An attempt to write a multiplayer game with the open-endedness of Elite
but the universe, scenario, technology and the like are all newly devised.
Will be playable over the internet.

'''98.2.2) How can I keep tabs on it?'''

Via their website:
http://www.galileo.base.org/

=== 98.3) X ===

'''98.3.1) What is it?'''

A commercial space flight and combat sim that I am told "looks everything
First Encounters could have been, brought up to date". I have yet to check
out the webpage though I hear a rolling demo is available.

'''98.3.2) How can I keep tabs on it?'''

From the link off http://www.egosoft.com/, the company which is developing it.

== Links ==
Back to: [[Alt_Fan_Elite_FAQ]]

[[Category:Classic]]
[[Category:FE2]]
[[Category:FFE]]

Oolite JavaScript Reference: World script event handlers

2010-09-22T16:05:05Z

Frame: /* startUp */

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. note that keystroke listening is not implemented. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

==== <code>playerWillSaveGame</code> ====
{{Oolite-prop-added|1.75}} 
The <code>playerWillSaveGame</code> handler is called whenever the player saves a game. The transferred message is one of the following strings: 'standardSave', 'autoSave' or 'quickSave'

this.playerWillSaveGame = function(message : String)
{
// Your code here
}

Using this event is useful for storing temporary variables in missionVariables, just before the game gets saved. missionVariables are slow in use compared to normal JS variables, therefor their use should be minimised for efficient code. The main benefit of using missionVariables is that they are saved in a saved game.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" 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.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event) 
playerWillEnterWitchspace (NPC ship event) 
playerEnteredNewGalaxy (world event) 
shipWillExitWitchspace (world event) 
shipExitedWitchspace (world event) 

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> 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't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite_JavaScript_Reference:_Player#alertCondition|player.alertCondition]]</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>guiScreenWillChange</code> ====
{{Oolite-prop-added|1.74}} 
The <code>guiScreenWillChange</code> handler is called when the guiScreen is about to change. It only fires for the screens: GUI_SCREEN_EQUIP_SHIP, GUI_SCREEN_MANIFEST, GUI_SCREEN_MARKET and GUI_SCREEN_SHIPYARD. On these screens a script could change the content of the page to be displayed. In Oolite 1.75 will 'GUI_SCREEN_SYSTEM_DATA' be added to this list. (world script only)

this.guiScreenWillChange = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called after a ship has been added to the system. After a witchspace jump it means that first all ships are added to the system, then all the relevant shipSpawned events are triggered. 
This handler for the woldScript is new since Oolite 1.74. After the event is sent to the shipScript, it is now also send to the worldScript with the added entity as argument.

this.shipSpawned = function(ship)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Missing Events ===

All the initially planned events have been implemented in 1.74.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite JavaScript Reference]]

Save Anywhere

2010-09-01T13:22:12Z

Frame:

Save Anywhere is a unique method whereby you can save your game at any OXP station, not only Main Planetary Orbital Stations, as in the standard game.

'''Requires:'''

It is recommended that you read the enclosed Instructions file ''carefully'' before using this OXP.

'''Downloads:'''

Current version:

* [http://www.box.net/shared/l6f4mdqvn9''Save Anywhere V3.1''] Current Release Version.

Older versions:

* [http://www.boxcn.net/shared/tnjt79pskb''Save Anywhere V0.2'']

[[Category:Oolite]] {{equipment-OXP}}

{{stub}}

Oolite JavaScript Reference: Mission

2010-08-26T19:32:11Z

Frame: /* runScreen */

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

The '''mission''' global object is used to run mission screens, and perform other actions related to mission scripting.

== Methods ==

=== <code>addMessageText</code> ===
function '''addMessageText'''(message : String)

Appends text to the currently running mission screen.

=== <code>markSystem</code> ===
function '''markSystem'''(systemNumber : Number)

Mark a system on the long range chart. (It is currently possible to mark multiple systems at once, as in <code>mission.markSystem(4, 54, 222)</code>, but this syntax ''may'' be deprecated for Oolite 1.75.)

'''See also:''' <code>[[#unmarkSystem|unmarkSystem()]]</code>

=== <code>runScreen</code> ===
{{Oolite-method-added|1.74}}
'''runScreen(parameters : Object [, callback : Function [, this : Object]])'''
Present a mission screen.

The appearance of the mission screen is defined by the properties of the <code>parameters</code> object. The currently defined properties are:
* <code>title : String</code>
* <code>titleKey : String</code> (Key in [[missiontext.plist]])
* <code>music : String</code> (name of a music file)
* <code>overlay : String</code> (name of an image used as overlay)
* <code>background : String</code> (name of a picture used as background)
* <code>model : String</code> (Role of a ship that will be shown as rotating ship)
* <code>message : String</code>
* <code>messageKey : String</code> (Key in [[missiontext.plist]])
* <code>choicesKey : String</code> (Key in [[missiontext.plist]])

Some of these are mutually exclusive; for instance, “title” overrides “titleKey”.

The callback function is a function that is called when the player makes a choice. Every runScreen can have its own specific callback function, or you can design a single function to handle multiple mission screens instead.

'''Example:''' 
A simple mission screen:
mission.runScreen({
title: "My first mission screen",
message: "This am a mission screen wot is good",
choicesKey: "me_firstmission_choices"
},
function (choice)
{
if (choice === "1_YES") player.commsMessage("Yay!");
else if (choice === "2_NO") player.commsMessage("Boo.");
else player.commsMessage("Whut?");
});
In [[missiontext.plist]], you’ll need the following. The numbers are used because choices are sorted by key.
{
"me_firstmission_choices" =
{
"1_YES" = "Yes.";
"2_NO" = "No.";
"3_MAYBE" = "Maybe.";
};
}

The call does not have to be laid out as above. The parameters object can be manipulated in any way you want beforehand, and the callback function can be written out of line. For example, the following is equivalent:
var parameters = new Object();
parameters.title = "My first mission screen";
parameters.message = "This am";
parameters.choicesKey = "me_firstmission_choices";
parameters.message += " a mission screen wot is good";

function callback(choice)
{
if (choice === "1_YES") player.commsMessage("Yay!");
else if (choice === "2_NO") player.commsMessage("Boo.");
else player.commsMessage("Whut?");
}

mission.runScreen(parameters, callback);

This form is more complicated, and the ordering is less intuitive. However, it does allow you to make complex decisions about the parameters in code, and writing the callback out of line can be preferable if it’s long. It is recommended that you start out with the first approach, but keep in mind that there are other options if it becomes too limiting.

=== <code>setInstructions</code> ===
function '''setInstructions(instructions : String, [worldScriptName : String])'''

Specify a message to put on the Manifest screen (usually short instructions for current mission), under the title “Missions”.

When not called from within a world script, the name of a world script must be specified so that Oolite knows which script the message belongs to. Clear the message by calling <code>setInstructions(null)</code>.

It is recommended that <code>setInstructions()</code> is used only when you need to customise the text for a specific scenario. For static text, use <code>[[#setInstructionsKey|setInstructionsKey()]]</code> instead.

'''See also:''' <code>[[#setInstructionsKey|setInstructionsKey()]]</code>

=== <code>setInstructionsKey</code> ===
{{Oolite-method-added|1.74}}
function '''setInstructionsKey(messageKey : String, [worldScript : String])'''

Like <code>[[#setInstructions|setInstructions()]]</code>, but looks up the specified <code>messageKey</code> in [[missiontext.plist]].

'''See also:''' <code>[[#setInstructions|setInstructions()]]</code>

=== <code>unmarkSystem</code> ===
function '''unmarkSystem'''(systemNumbers : Number)

Remove a mark set with <code>[[#markSystem|markSystem()]]</code>. (It is currently possible to mark multiple systems at once, as in <code>mission.unmarkSystem(4, 54, 222)</code>, but this syntax ''may'' be deprecated for Oolite 1.75.)

'''See also:''' <code>[[#markSystem|markSystem()]]</code>

[[Category:Oolite JavaScript Reference]]

Your Ad Here!

2010-03-10T13:34:47Z

Frame: /* Main Features */

===Intro===

It all started with the Budget Crisis of 3119, when the Co-operative finally realised the scale of the overspend on the project to upgrade the old Faraway wormhole navigation system to the new Witchspace Beacon network. Gross financial mismanagement is hardly new to the Co-operative, or even (sadly) uncommon, but the Faraway fiasco was of an entirely different order of magnitude. This hole wasn't going to be filled with some budgetary offset and a bit of creative accountancy; somehow, the Witchspace Beacon network would have to start generating income.

The idea of charging a levy on all ships using Witchspace was briefly considered, then discarded as a) unpopular and, sadly, b) impossible. Fortunately, a solution was found: the Ad-X Corporation was prepared to pay handsomely for the right to station giant TeraScreen advertisements at the Witchpoint (and, in some larger systems, outside the main station itself).

[[Image:My_favourites_ads_from_Your_Ad_Here!.jpg|thumb|450px|left|Just some of our favourite adverts!]]

It seemed like the problem had been solved. Unfortunately, the only systems prepared to accept unrestricted TeraScreen advertising were the Corporate States, the Democracies and the Confederacies. Dictatorships wanted to use the screens for their own purposes (usually, giant pictures of one Glorious Leader or another); the Communist worlds would have nothing but propaganda (and, indeed, have been working on a system of propaganda screens of their own); and the Multi-Government, Feudal and Anarchy worlds wanted a slice of the pie for themselves – one far bigger than their downmarket demographic warranted.

In desperation, the Co-operative cast around for other possible revenue streams. The various member worlds of the wealthy Corporate State voting bloc had always bridled at Co-op restrictions on the classes and quantities of commodities exchanged at main system stations, demanding "Free Trade" instead. Other planets in the Co-operative, fearful that their own domestic economies would be overwhelmed by an arrangement that inherently favoured the rich and powerful, had always resisted such demands. But faced with the possible bankruptcy of the entire stellar trading network, a compromise was reached: in return for a regular rent on the local Witchpoint volume, the Co-operative would allow a number of independent trading posts to be set up in systems with sufficiently high levels of economic, cultural and political cohesion – or, as some cynics have suggested, those systems with a big enough population to make the venture worthwhile.

Thus the Convenience Stores were born: franchise stations, based near the Witchpoint, offering goods and services to passing ships. Exempt from Co-op trade regulations, the Convenience Stores set about making money from every possible source. They are encrusted with advertising, and even the stations' defence craft – cheap ex-Navy Sidewinders – are plastered with logos and corporate sponsorship. Most controversially, controlled commodities – slaves, narcotics and firearms – are offered freely, and legally, for sale.

Within a Convenience Store, commerce moves at a rapid pace, and prices of even the most basic goods can fluctuate wildly. Some merchants, for commercial or ideological reasons, have abandoned the main system stations altogether; but cannier Commanders, balancing the reliable price index of the Co-operative against speculative capitalist bubble-blowing, can often exploit the feverish atmosphere of a Convenience Store to obtain impressive profits on relatively small quantities of goods.

--------------------------------------------------------------------

===Overview===

Do you want spam with that?

This OXP adds a lot of variety to the Universe. Witch-point and navigation beacons are replaced with giant bill boards displaying adverts.
Every set features 50 different adverts and also adds a different type of constore to the universe (Set A introduces the Pi-42 constore, Set B the Tescoo Ooxpress constore etc). A constore is a dockable commercial base which is added to the space lanes of most systems with a large population. Also from version 4 and above of this oxp each constore has its own security force, the ships of which are skinned in the colours of the store they protect, and billboards will occasionally appear in asteroid fields of Corporate Systems.

All ads made by different Oolite players for a more varied visual experience. You can contribute with your own ads on the ''[http://www.aegidian.org/bb/viewtopic.php?t=2588&start=1110 Oolite BB]''. Note that your ads must be relevant to the world of Oolite and submitted as 256x128 pixel images.
Also for ver 4 and above all the artwork on the constores is a contribution of different oolite players

--------------------------------------------------------------------

===Main Features===

Terascreen - 44,017" monster screens used as witchpoint buoys in highly policed systems.

Terascreen Junior - The 17k" Terascreen which works as navigational buoy in highly policed systems.

Constores - convenience stations that sell a little of everything present only in non Anarchy highly populated systems

Constore defenders - Constores security force (From ver 4 and above)

Asteroid rolling terascreen Junior - Ad terascreens inside asteroid fields only in corporate systems (From ver 4 and above)

--------------------------------------------------------------------

===Difficulty Rating===

No difficulty. It only adds ads and innocent constores to the universe.

--------------------------------------------------------------------

===Installing and Playing===

To play the OXP, unzip the download file. This will create a forlder "YOUR_AD_HERE.oxp" and also several folders named "YOUR_AD_HERE_SET_X.oxp". In order to have a functional installation of your ad here you need the primary folder ("YOUR_AD_HERE.oxp") and at least one set ("YOUR_AD_HERE_SET_A.oxp" for examble). The more folder sets you chose to install the more the variety of the ads, constores ect you introduce to the universe. Move the folders you want under the AddOns folder inside your oolite installation

--------------------------------------------------------------------

===Update Notes===

'''Changes in version 4:'''

1.All the native constores have been replaced with variants of Griff’s Trade outpost (The original one with the ads).

2.Every station has its own dedicated defenders (Pi-42 security, Tescoo security etc) and every defender ship is different for each station.

3.Increase the maximum energy and maximum defenders of the constores.

4.Replace the buggy AI of the constores with the one Eric gave me. It is not so wise to attack a constore anymore!

5.Improve and translate (into JS) the script of the oxp. Now the script has a second condition (if the player is launched from the station) and also checks before placing a constore if there is already one in the system.

6.Increase the appearance of billboard buoys in systems with government above 4.Now the billboard buoys almost always replace the original buoys in confederacies, democracies and corporate states and not half of the times like in the previous version.

7.Integrate Ahrumans shady billboards as a very rare encounter inside the asteroid fields of corporate states. Every set has only one asteroid billboard and it would be easily maintained for future sets with just the replacement of the png (with the same logic as the common billboards in every set)

'''Credits for version 4'''

1.All Constore brand name ads are made by DaddyHoggy and Pangloss.

2.All Constore Billboard ads are made by Griff, DaddyHoggy, Pangloos and Disembodied.

3.All Constore Adrings are made by Pangloss and Griff.

4.All Constore roof billboards are made by Griff and Pangloss.

5.All Constore GlowAds are made by Pangloss and Griff.

6.The sidewinder defenders artwork is Pangloss and DaddyHoggy’s job.

7.Eric made the new AI for the constores and also the small JS for the correct facing of the constores.

8.The station itself is a creation of (well who else) Griff. Also Griff with the new improved shaders gave us the possibility to have different stations in different colors.

9.Special thanks to Ahruman for allowing us to integrate its shader billboard demo oxp.

10.Special thanks to another_commander for all his help and support in the translation of the script.

--------------------------------------------------------------------

===Download Link===

'''VERSION 3'''

[http://sancho.dk/oolite/yaw.zip''Download Ver 3 (Basic package)''] Version for all oolite versions below 1.72.1. '''It includes sets A to D''' 
[http://sancho.dk/oolite/ya_set_E.zip''Download Set E for Ver 3''] You must first install the basic package of version 3 
[http://sancho.dk/oolite/ya_set_F.zip''Download Set F for Ver 3''] You must first install the basic package of version 3 

'''VERSION 4'''

This version has significant improvements and bug fixes from version 3. The most profound of the improvements is that the original box-style convenience store dockable bases have been replaced with variants of the original Griff trade outpost,but due to the use of JS and shaders for the new constores it is only compatible from version 1.72.1 and above.

[http://sancho.dk/oolite/Yaw_V4.zip''Download Ver 4.0''] Version for oolite 1.72.1 and above. '''It includes all sets from A to F''' 

'''VERSION 4.1.1'''

This version has minor changes over version 4.0. Version 4.0 will no longer be able to orient the con-stores correctly in space when used with Oolite 1.74. Not a big deal of course but users of Oolite 1.73 and above should use the new version 4.1.1 that contains the corrected main script. Sets A till F are unchanged.

[http://www.box.net/shared/x1idbg1vgs ''Download Ver 4.1.1''] Version for oolite 1.73 and above. '''It only contains the main oxp (1.7 MB) but none of the sets'''. You should also download above 4.0 package for obtaining the sets A to F when you not already have those.

{{ship-OXP}} {{station-OXP}}

Your Ad Here!

2010-03-10T13:32:53Z

Frame: /* Update Notes */

===Intro===

It all started with the Budget Crisis of 3119, when the Co-operative finally realised the scale of the overspend on the project to upgrade the old Faraway wormhole navigation system to the new Witchspace Beacon network. Gross financial mismanagement is hardly new to the Co-operative, or even (sadly) uncommon, but the Faraway fiasco was of an entirely different order of magnitude. This hole wasn't going to be filled with some budgetary offset and a bit of creative accountancy; somehow, the Witchspace Beacon network would have to start generating income.

The idea of charging a levy on all ships using Witchspace was briefly considered, then discarded as a) unpopular and, sadly, b) impossible. Fortunately, a solution was found: the Ad-X Corporation was prepared to pay handsomely for the right to station giant TeraScreen advertisements at the Witchpoint (and, in some larger systems, outside the main station itself).

[[Image:My_favourites_ads_from_Your_Ad_Here!.jpg|thumb|450px|left|Just some of our favourite adverts!]]

It seemed like the problem had been solved. Unfortunately, the only systems prepared to accept unrestricted TeraScreen advertising were the Corporate States, the Democracies and the Confederacies. Dictatorships wanted to use the screens for their own purposes (usually, giant pictures of one Glorious Leader or another); the Communist worlds would have nothing but propaganda (and, indeed, have been working on a system of propaganda screens of their own); and the Multi-Government, Feudal and Anarchy worlds wanted a slice of the pie for themselves – one far bigger than their downmarket demographic warranted.

In desperation, the Co-operative cast around for other possible revenue streams. The various member worlds of the wealthy Corporate State voting bloc had always bridled at Co-op restrictions on the classes and quantities of commodities exchanged at main system stations, demanding "Free Trade" instead. Other planets in the Co-operative, fearful that their own domestic economies would be overwhelmed by an arrangement that inherently favoured the rich and powerful, had always resisted such demands. But faced with the possible bankruptcy of the entire stellar trading network, a compromise was reached: in return for a regular rent on the local Witchpoint volume, the Co-operative would allow a number of independent trading posts to be set up in systems with sufficiently high levels of economic, cultural and political cohesion – or, as some cynics have suggested, those systems with a big enough population to make the venture worthwhile.

Thus the Convenience Stores were born: franchise stations, based near the Witchpoint, offering goods and services to passing ships. Exempt from Co-op trade regulations, the Convenience Stores set about making money from every possible source. They are encrusted with advertising, and even the stations' defence craft – cheap ex-Navy Sidewinders – are plastered with logos and corporate sponsorship. Most controversially, controlled commodities – slaves, narcotics and firearms – are offered freely, and legally, for sale.

Within a Convenience Store, commerce moves at a rapid pace, and prices of even the most basic goods can fluctuate wildly. Some merchants, for commercial or ideological reasons, have abandoned the main system stations altogether; but cannier Commanders, balancing the reliable price index of the Co-operative against speculative capitalist bubble-blowing, can often exploit the feverish atmosphere of a Convenience Store to obtain impressive profits on relatively small quantities of goods.

--------------------------------------------------------------------

===Overview===

Do you want spam with that?

This OXP adds a lot of variety to the Universe. Witch-point and navigation beacons are replaced with giant bill boards displaying adverts.
Every set features 50 different adverts and also adds a different type of constore to the universe (Set A introduces the Pi-42 constore, Set B the Tescoo Ooxpress constore etc). A constore is a dockable commercial base which is added to the space lanes of most systems with a large population. Also from version 4 and above of this oxp each constore has its own security force, the ships of which are skinned in the colours of the store they protect, and billboards will occasionally appear in asteroid fields of Corporate Systems.

All ads made by different Oolite players for a more varied visual experience. You can contribute with your own ads on the ''[http://www.aegidian.org/bb/viewtopic.php?t=2588&start=1110 Oolite BB]''. Note that your ads must be relevant to the world of Oolite and submitted as 256x128 pixel images.
Also for ver 4 and above all the artwork on the constores is a contribution of different oolite players

--------------------------------------------------------------------

===Main Features===

Terascreen - 44,017" monster screens used as witchpoint buoys in highly policed systems.

Terascreen Junior - The 17k" Terascreen which works as navigational buoy in highly policed systems.

Constores - convenience stations that sell a little of everything present only in non Anarchy highly populatated systems

Constore defenters - Constores security force (From ver 4 and above)

Asteroid rolling terascreen Junior - Ad terascreens inside asteroid fields only in corporate systems (From ver 4 and above)

--------------------------------------------------------------------

===Difficulty Rating===

No difficulty. It only adds ads and innocent constores to the universe.

--------------------------------------------------------------------

===Installing and Playing===

To play the OXP, unzip the download file. This will create a forlder "YOUR_AD_HERE.oxp" and also several folders named "YOUR_AD_HERE_SET_X.oxp". In order to have a functional installation of your ad here you need the primary folder ("YOUR_AD_HERE.oxp") and at least one set ("YOUR_AD_HERE_SET_A.oxp" for examble). The more folder sets you chose to install the more the variety of the ads, constores ect you introduce to the universe. Move the folders you want under the AddOns folder inside your oolite installation

--------------------------------------------------------------------

===Update Notes===

'''Changes in version 4:'''

1.All the native constores have been replaced with variants of Griff’s Trade outpost (The original one with the ads).

2.Every station has its own dedicated defenders (Pi-42 security, Tescoo security etc) and every defender ship is different for each station.

3.Increase the maximum energy and maximum defenders of the constores.

4.Replace the buggy AI of the constores with the one Eric gave me. It is not so wise to attack a constore anymore!

5.Improve and translate (into JS) the script of the oxp. Now the script has a second condition (if the player is launched from the station) and also checks before placing a constore if there is already one in the system.

6.Increase the appearance of billboard buoys in systems with government above 4.Now the billboard buoys almost always replace the original buoys in confederacies, democracies and corporate states and not half of the times like in the previous version.

7.Integrate Ahrumans shady billboards as a very rare encounter inside the asteroid fields of corporate states. Every set has only one asteroid billboard and it would be easily maintained for future sets with just the replacement of the png (with the same logic as the common billboards in every set)

'''Credits for version 4'''

1.All Constore brand name ads are made by DaddyHoggy and Pangloss.

2.All Constore Billboard ads are made by Griff, DaddyHoggy, Pangloos and Disembodied.

3.All Constore Adrings are made by Pangloss and Griff.

4.All Constore roof billboards are made by Griff and Pangloss.

5.All Constore GlowAds are made by Pangloss and Griff.

6.The sidewinder defenders artwork is Pangloss and DaddyHoggy’s job.

7.Eric made the new AI for the constores and also the small JS for the correct facing of the constores.

8.The station itself is a creation of (well who else) Griff. Also Griff with the new improved shaders gave us the possibility to have different stations in different colors.

9.Special thanks to Ahruman for allowing us to integrate its shader billboard demo oxp.

10.Special thanks to another_commander for all his help and support in the translation of the script.

--------------------------------------------------------------------

===Download Link===

'''VERSION 3'''

[http://sancho.dk/oolite/yaw.zip''Download Ver 3 (Basic package)''] Version for all oolite versions below 1.72.1. '''It includes sets A to D''' 
[http://sancho.dk/oolite/ya_set_E.zip''Download Set E for Ver 3''] You must first install the basic package of version 3 
[http://sancho.dk/oolite/ya_set_F.zip''Download Set F for Ver 3''] You must first install the basic package of version 3 

'''VERSION 4'''

This version has significant improvements and bug fixes from version 3. The most profound of the improvements is that the original box-style convenience store dockable bases have been replaced with variants of the original Griff trade outpost,but due to the use of JS and shaders for the new constores it is only compatible from version 1.72.1 and above.

[http://sancho.dk/oolite/Yaw_V4.zip''Download Ver 4.0''] Version for oolite 1.72.1 and above. '''It includes all sets from A to F''' 

'''VERSION 4.1.1'''

This version has minor changes over version 4.0. Version 4.0 will no longer be able to orient the con-stores correctly in space when used with Oolite 1.74. Not a big deal of course but users of Oolite 1.73 and above should use the new version 4.1.1 that contains the corrected main script. Sets A till F are unchanged.

[http://www.box.net/shared/x1idbg1vgs ''Download Ver 4.1.1''] Version for oolite 1.73 and above. '''It only contains the main oxp (1.7 MB) but none of the sets'''. You should also download above 4.0 package for obtaining the sets A to F when you not already have those.

{{ship-OXP}} {{station-OXP}}

RegistrationID

2010-02-28T19:47:00Z

Frame:

== '''Registration ID..''' ==
[[File:RegistrationOXPimage1.jpg]]

In an Effort to diminishing Piracy Gal Cop has recently started Demanding ID
tags on every ship in the galaxy. existing non ID ships, will acquire an ID
upon change of ownership.. For now this only applies to all the popular
brands of ships, those we have come to know since the dawn of interstellar space travel.

'''Protests'''

A lot of back yard ship factories have protested against this and refuses to
put ID tags on their custom or upgraded ships until legislation upon the matter
as been cleared about whether or not this violates the rights of the individual
trader..

'''flawed legislation'''

Independant Space Traders Union also known as ITU, has appealed Gal Cops current
practice as follows

''"it is obvious that the police now, as a matter of routine, demand the production of registration indemnity ID Tags whenever they stop or interrogate a spacer for whatever cause. Of course, if they are looking for a stolen ship or have reason to believe that a particular spacer is engaged in committing a crime, that is one thing, but to demand an ID tag from all and sundry, for instance, from a lady who may leave her mining ship in an asteroid field longer than her license allows her to, or some trivial matter of that sort, is wholly unreasonable. This Act was passed for security purposes, and not for the purposes for which, apparently, it is now sought to be used."
''

''' Decision Pending '''

The Board of Space Vessel Affairs(BSVA) have ruled that current practices must be followed until a decision has been made.. however the supplier of the photo chromatic paint embedded in the alloys of the ID tagged vessels, cannot be removed without removing the metal entirely... and changing the assembly lines again could lead to law suits against GAL COP and even GAL CORP, from the union of space vessel suppliers known as SVS.

'''What the Wise Men Say'''

Experts agree that the ID practice is here to stay: however those shops that exist on the fringe of law, should still be able to get away with not painting IDs on their ships... subsequently Prices on NON id ships, are higher than ID ships, and also acts as an additional reason, not to embed ID paint into the alloy of your Vessel.

These shops that are largely unknown to Gal Cop, also risks getting inspections from Gal Cop, if they registrar with Gal Cop to get an alloted series of ID tag numbers.

The Experts also agree that eventually even these will be forced to accept, they do however also agree that pirates will remove the ID tags soon, when some back yard ship repair shop starts removing the metal or the paint from the duranium alloys at an extremly high cost ofcourse...

finally ID tags may allow for Pirates to easier stalk and find their prey..

[http://www.box.net/shared/l0yu9ihdl2 Download version 0.12 here]

OXP

2010-02-28T19:45:55Z

Frame:

== What are OXPs? ==

[[Image:oolite-oxp-icon.png|128px|right|OXP icon]]
An '''OXP''' (Oolite eXpansion Pack) is an enhancement to the game [[Oolite]]. Typically, an OXP is downloaded as a ZIP file, which is expanded and placed in Oolite's AddOns folder. On the Mac the OXP is a shown as an application, which takes the form of the icon shown here. On Windows the OXP appears as a normal folder ending ".oxp". 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. Whatever your OS, you need to move the OXP into Oolite's AddOns folder. Oolite will only read an OXP if you move the .oxp folder (or Application on the Mac) into Oolite's AddOns folder.

== Downloading OXPs ==

On this page you will find download links to all the OXPs. The download will create a .ZIP file. Unzip it and a new folder will appear. Open this folder and you will see a folder ending .oxp and usually a README file. Move the folder ending .oxp into the Oolite AddOns folder. Next time you load up Oolite the new features added by the OXP will be added to the game. Be sure to read the README file, as this will tell you what the OXP does. If you are updating an old version of an OXP on Oolite 1.69.1 onwards, hold down the SHIFT key whilst Oolite loads up for the first time after installing in order to ensure the cache is updated.

Below you will see a table of all the OXPs set out in alphabetical order. The link in the first column will take you to a Wiki Page giving you information on the OXP and a download link. If no Wiki page is currently available for the OXP, the link will take you directly to a download link.

The links in the next column will take you to Wiki Pages giving information on ships or stations added by the OXP. Many of the [[Oolite_Missions|Mission OXPs]] will contain lots of other ships, stations or weapons that are not listed here. The Wiki only gives information on the Ships listed in the galaxy wide "Jane's Spacecraft". Many military, criminal and corporate powers do not make information on the craft they build or use available to the galactic public! Below the Main Table is a list of download links to all the OXPs broken down by category.

Most OXPs can also be found at [http://oosat.alioth.net The Oolite Satellite Resource Site] (Oosat2) or the older [http://capnhack.com/hosting/oolite/Oolite/OoSat.html Captain Hack OoSat Site] (Oosat1). Please note however that neither of these sites have been updated for a long time, nor will they be. All updating is now done on this page of the Wiki. You should use the link shown on this page to get the latest version of the OXP. For example, the versions of Assassins.oxp, Ionics.oxp, Thargoid Wars.oxp and Spyhunter.oxp on the Captain Hack site are old versions (and contain bugs). The links on this page will take you to the latest versions.

== Table of all OXPs ==

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top"
! Information / Download !! Ships !! Stations !! Short Description
|-valign="top"
| [[Aegidian's_Specials|Aegidian's Specials]]
| [[Mussurana]]
[[Asp_%28Oolite%29#Notable_features|Asp Mark II Special]]
|
|Ships. The powerful Mussurana and an improved Asp.
|-valign="top" bgcolor="#e7e7ff"
| [[Aegidian's_X-Ships|Aegidian's X-Ships]]
| [[Python_ET_Special|Python ET Special]]

[[Cobra_Mk.2_%28Oolite%29|Cobra Mk II]]

[[Asp_%28Oolite%29#Notable_features|Asp Mark II Special]]

[[Sidewinder_%28Oolite%29#Notable_featuresl|Sidewinder Special]]
|
|Ships. An improved Python, the experimental Cobra Mk II, the Asp Mark II Special and the Sidewinder Special.
|-valign="top"
| [http://www.box.net/shared/p9wjemvoc8 ''Amen Brick's Pirate Clan One: The Blitzspears (NEW 07/08)'']
| Assassin, Hoodlum, Mugger, Scoundrel and Spiv
|
|Ships. The first of the Pan-Galaxy Outlaw clans to rise through the leadership of some diabolical criminal genius. What are his, or indeed hers or, further indeed, its future plans? Will their nefarious example be followed by others? The answers are out there...
All ships in this version are playable. Future versions (probably modular for memory saving reasons) will have more clans, the ability to join clans (if I master the arcane art of programming), stations and missions. Stay untuned, folks.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/sm6fpqxsg4 ''Amen Brick's Megaships v1.2 (Amended 07/08)'']
| The Battleship, The Biodome, The Cruiseship, The Hospitalship, The Supercargo, The Superlifter and the Yacht:Amen Class
|
|Ships. Graceful giants cross the galaxies before our eyes. The forlorn Biodome, destined to forever wander the Ooniverse. The Cruiseship taking citizens to holiday planets. The Supercargo ferrying aid to the needy. The private Yacht filled with luxury and the prosaic Superlifter than helps giant ships get to their new homes or their final resting place. Now amended to make spectacular explosions as they try to dock less likely (sorry!)
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/E5Amigasoundpack01oxp.zip ''Amiga Replacement Sounds'']
|
|
| Sound Set, based on the sound set used in the Amiga version of the original Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Anarchies_OXP|''Anarchies.oxp'']]
| [[Hacker_Viper|Hacker Viper]]

[[Salvager_Phoenix|Salvager Phoenix]]

[[Salvager_Tugger|Salvager Tugger]]
| [[Hacker_Outpost|Hacker Outpost]]

[[Salvage_Gang|Salvage Gang]]

[[Sentinel_Station|Sentinel Station]]

[[Renegade_Station|Renegade Station]]
| Feature/Ships/Stations. Complete overhaul of Oolite's legal rating system. It gets harder to become clean again. But there are some new ways to achieve this as well: Hacker Outposts can be found in the higher tech [[Powers_and_Organisations#Anarchy_Worlds|Anarchy systems]], the criminals willing to clear a fugitive's legal record. For a price of course! Salvage Gangs are spread all over the Ooniverse, providing good equipment deals. Those in Anarchy systems offer a service similar to the Hacker Outposts as well. Sentinel Stations are placed in some of the worst Anarchies. But beware! Some of them have been overthrown by the pirates and are now Renegade Stations. Good news for the pirates among the players, because these are as close to a safe-haven for you as it gets! All of these also feature their own ships.
|-valign="top"
| [[AMS_OXP|Anti-Missile System]]
|
|
|Equipment. Adds the anti-missile system, designed to offer a defence against non-standard missiles via automatically firing interceptor darts (6 per launcher, replenishable). Requires [[Missile_Analyser|Missile Analyser OXP]] by Eric Walch.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/aphidv2.oxp_.zip ''Aphid Escort Service'']
|
|
|Ships. Adds the stylish Aphid escort service.
|-valign="top"
| [[Aquatics_OXP|Aquatics]]
| [[Manta_Ray|Manta Ray]], [[Shark|Shark]], [[Man_O%27_War|Man O' War]], [[Box_Escort|Box Escort]], [[Conger|Conger Cargo Hauler]], [[Hawksbill|Hawksbill Fuel Tanker]], [[HammerHead|HammerHead Hauler Carrier]], [[Barracuda|Barracuda]], [[LeviathanPlatform|Leviathan System Platform]], [[Orca|Orca Destroyer]]
|
|Ships/mission/station. Ships from the Aquarian Shipbuilding Corporation of Aqualina, G3. Also includes a brand new station (the Aquarian Shipbuilding Corp. HQ) plus a mission based out of it. And who knows, there may be a few more surprises in there too...
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/att1.zip ''Armoured Transport Type 1'']
| [[Gaundlet_Armoured_Transport_Type1|Gaundlet Armoured Transport Type 1]]

[[Gaundlet_Armoured_Escort_Viper|Gaundlet Armoured Escort Viper]]
|
|Ships. Convoys of well armed craft ferry gold and other valuables through the space lanes. Only a pirate with an Iron Ass would dream of attempting a robbery!
|-valign="top"
| [[The Assassins Guild OXP|Assassins Guild V1.3 (Updated)]]
| [[Deamon_Cruiser|Deamon Cruiser]]

[[Mongoose]]

[[Nemesis]]

[[Scorpion_Frigate|Scorpion Frigate]]
|[[Navy Station]]
| [[Oolite_Missions#The_Assassins_Guild|Missions]] / Ships / Stations / Planets. 21 missions involving murder to order in Galaxy 7, available to experienced Commanders amoral enough to gain admittance to the sinister [[Powers_and_Organisations#The_Assassins_Guild|Assassins Guild]]. Updated from the versions on Oosat1 & Oosat2.
|-valign="top" bgcolor="#e7e7ff"
|[[Asteroid_Storm|Asteroid Storm]]
|
|
| Feature / [[Oolite_Missions#Asteroid_Storm|Mission]]. Adds lots of different types of Asteroids to the Universe. A [[Oolite_Missions#Asteroid_Storm|Mission]] is also included, well suited to a novice Commander. A well known station in Galaxy 1 comes under threat from a large asteroid strike. The updated version fixes a bug that meant that only one new type of asteroid was being added. Now the intended twelve varieties appear in game. '''Note''': this OXP does not work in Oolite v.1.74+.
|-valign="top"
| [[Baakili_Far_Trader|Baakili Far Trader]]
| [[Baakili Far Trader]]
|
|Ships. Adds a dockable Alien ship.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/dropbox/bandersnatch_1_1.zip ''Bandersnatch v1.1'']
|[[Bandersnatch]]
|
|Ships. Adds a pirate capital vessel armed with plasma turrets. (Bugfixed at November 2009)
|-valign="top"
| [[Black_Monk_Monastery|Bank of the Black Monks]]
| [[Black_Monk_Gunship|Black Monk Gunship]]
| [[Black_Monk_Monastery|Black Monk Monastery]]
| Feature / [[Oolite_Missions#Bank_of_the_Black_Monks|Mission]]. Monks aboard well armed stations appear in advanced systems. Loans are offered, defaulters will be exterminated! Two versions of the OXP are available, the [http://www.box.net/public/z2ahfudnt3 Non-Shader Bank of the Black Monks OXP'] and the [http://http://www.box.net/shared/7twwbaelcc 'Shady Bank of the Black Monks OXP']. The Non-Shader Version will run on all versions of Oolite. The Shady version uses Shaders and requires Version 1.71 or higher of Oolite. Slow Systems will struggle to run the Shady Version, so if you find installing it is slowing your system down too much, then try the Non-Shady Version.
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth]]
| [[Behemoth]]
|
|Ships. Adds a dockable Navy Cruiser. Updated from the version on Oosat1.
|-valign="top"
| [[ADCK's_Behemoths|Behemoths - Shadered (By ADCK)]]
|
|
|Ships. Based on the above oxp, but with 2 new behemoths and shaders (Includes shaders which require Oolite 1.69 or later)
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth_Spacewar|''Behemoth Spacewar'']]
|
|
|Patch. Adds intelligence to the Behemoth and brings a combat with Thargoids
|-valign="top"
| [[BigShips_OXP|Big Ships]]
|
|
|Ships (ish). Adds the new role "bigTrader" to the game, designed for large ships which are unable to dock with stations due to their size. Also includes an AI which can be used for such ships, but DOES NOT include any ships of its own.
|-valign="top" bgcolor="#e7e7ff"
| [[Media:BoomslangWIP.zip|''Boomslang'']]
| [[Boomslang]]
|
|Ships. Adds a mid-range multi-role ship. Used by pirates and traders alike.
|-valign="top"
| [[Bounty_Scanner|Bounty Scanner]]
|
|
|Equipment. The Bounty Scanner adds bounty details (if any) to the targeting lock-box display when locked onto other ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Bulk_Haulers|Bulk Haulers by ADCK]]
|
|
|Ships. Adds many Bulk Haulers to the game, including a retextured version of Aegidians Bulk Hauler as seen in the Oolite video on YouTube, which until recently has not been available to the public. (Requires [[BigShips_OXP|Big Ships]] and Includes shaders which require Oolite 1.69 or later)
|-valign="top"
| [[BuoyRepair|BuoyRepair1.02.5]]
| Armadillo Controller Guanako
|[[Buoy Repair Facility|Buoy Repair Facility]]
|Feature. Repair company for defect or destroyed nav-beacons (Updated 7/10/2009).
|-valign="top" bgcolor="#e7e7ff"
| [http://www.crimsonforge.co.uk/cloister/neocaduceus.zip Caduceus]
| [[Caduceus|Caduceus]]
|
|Ships. Adds the very expensive (and deadly) Caduceus, which has six broadside-mounted auto-targeting plasma cannons.
|-valign="top"
| [http://oosat.alioth.net/files/seosu.zip ''Capisastra'']
| [[Capisastra_Defender|Capisastra Defender]]

[[Capisastra_Hauler|Capisastra Hauler]]

[[Capisastra_Warrior|Capisastra Warrior]]
|
|Ships. Capisatra pirates appear in Galaxy 4. [[Capisastra_OXP|More Information]].
|-valign="top" bgcolor="#e7e7ff"
| [[Captured_Thargons_OXP|Captured Thargons]]
|
|
|Equipment. Gives the possibility for player ships to carry and launch captured and reprogrammed Thargon robot fighters
|-valign="top"
| [[Cargo_Wreck_Teaser_OXP|''Cargo & Wrecks V1.4 (Updated April 2009)'']]
|
|
| Cargo. Adds lots of different types of cargo canisters.
|-valign="top" bgcolor="#e7e7ff"
| [[Cataclysm_OXP|''Cataclysm'']]
|
|
| Mission. "Cataclysm.oxp is a mission OXP that takes up the threads of the native Constrictor Hunt and Thargoid Plans missions, and sends you on a mission far bigger than anything you have done for the Navy so far. It gives you the opportunity to re-visit places you have visited before, and re-meet people you had contact with during these missions. And of course it will let you meet various other people, and lead you to a lot of new places, some of which you probably haven't visited before."
|-valign="top"
| [http://oosat.alioth.net/files/clearskies.oxp_.zip ''Clear Skies'']
|
|
| Utility. Reduces nebula effects. Handy if your system is finding it hard to run Oolite.
|-valign="top" bgcolor="#e7e7ff"
| [[Cobra_3.5|Chopped Cobra]]
| [[Cobra_3.5|Cobra Mk 3.5]]
|
|Ships. A slightly faster and tougher variation on the classic Cobra Mk III, at the price of a reduced cargo bay.
|-valign="top"
| [[Cobra_Clipper_SAR|Cobra Clipper SAR]]
| [[Cobra_Clipper_SAR|Cobra Clipper SAR]]
|
|Ships. A custom Cobra Mk III to rescue stranded Commanders.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/cobra3njx.zip ''Cobra Mk III Njx'']
| [[Cobra_III_NjX|Cobra III NjX]]
|
|Ships. A faster, tougher variation on the Classic Cobra Mk III.
|-valign="top"
| [[Commies|''Commies'']]
| [[Ray_Mk.I|Ray Mk I]]

[[Giant_Ray|Giant Ray]]

[[Astro_Mines|Mining Pods]]

[[Astro_Mines|Scavenger Rays]]

[[Sturgeon_Mk.I|Sturgeon Mk I]]

[[Worker%27s_Commuter|Worker's Commuter]]

| [[Astro_Mines|Astro Mines]]

[[CZGF|Collective Zero-G Factory]]

[[SLAPU|Solar Laboratory and Production Unit]]
|Ships / Stations. Commie systems have their own police forces, transports, stations and miners.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/pLists/hud.plist ''Compact HUD'']
|
|
|Alternative HUD.
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Condor'']
| [[Condor]]
|
| Ships. A very powerful police and Navy Cruiser.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/CustomSounds.zip ''Custom Sounds'']
|
|
| Sound Set. The largest of the currently available sound sets, this pack replaces or adds over 40 sounds, featuring additional music and extensive use of a calm female computer voice to warn the Commander of alarming events.
|-valign="top"
| [http://oosat.alioth.net/files/dwcobra3HiRes.zip ''Dark Wheel Cobra''] -
([http://oosat.alioth.net/files/dwcobra3.zip alternative lo-end version])
|[[DWCobra|Dark Wheel Cobra]]
|
|Ships. A custom Cobra Mk III model, as seen on the cover of the Elite Manual.
|-valign="top" bgcolor="#e7e7ff"
| [[Deep_Space_Dredger|''Deep Space Dredger 2.3'']]
| [[Sabre]]
| [[Deep_Space_Dredger|Deep Space Dredger]]
|Ships / Stations. Adds dockable Space Dredgers to the space lanes, defended by a squad of Saber fighters. Version 2.3 has new, improved textures.
|-valign="top"
| [[DeepSpacePirates|''Deep Space Pirates'']]
|
|
|Feature. Normally in Oolite ships do not appear outside the space lanes. This OXP adds ships outside the space lanes. As no police patrols extend this far out pirates and other unpleasant characters can be found in deep space.
|-valign="top"
|-valign="top" bgcolor="#e7e7ff"
| [[Deepspace_Ships|''Deepspace Ships'']]
|
|
|Oolite Ships replacement set. Replaces the default ships with new textures.
|-valign="top"
| [[Deposed_OXP|''Deposed 1.3.4'']]
|
|
| [[Oolite_Missions#Deposed|Mission]]. A series of missions set in Galaxy 4 for an experienced Commander. This version is now mission-offering. compatible with other OXPs.
|-valign="top" bgcolor="#e7e7ff"
|[http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Dictators'']
| [[Imperial_Censor|Imperial Censor]]

[[Imperial_Freighter|Imperial Freighter]]

[[Imperial_Lictor|Imperial Lictor]]

[[Imperial_Quaestor|Imperial Quaestor]]

[[Imperial_Tanker|Imperial Tanker]]

[[Junta_Enforcer|Junta Enforcer]]

[[Revolutionary_Guard|Revolutionary Guard]]
| [[Imperial_AstroFactory|Imperial AstroFactory]]
| Ships / Stations. Dictatorship systems gain their own police forces, supply craft and stations.
|-valign="top"
| [http://oosat.alioth.net/files/Diso.zip ''Diso'']
|
|[[Navy Station]]
| Planets / Stations. Extra planets and stations are added to the Diso system in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [[Display reputation OXP|''Display reputation'']]
|
|
| Feature. Displays your passenger and contract reputation in your ship's manifest.
|-valign="top"
| ''Dr HUD'' [http://sancho.dk/oolite/Dr_HUD_Cmk3.zip Cobra Mk III version], [http://sancho.dk/oolite/Dr_HUD.zip Custom version]
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|Docking Clearance]]
|
|
| Feature. Sets the docking clearance on for all stations in Oolite. Click on [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|this link]] for further explanation.
|-valign="top"
| ''Dr HUD'' [http://sancho.dk/oolite/Dr_HUD_Cmk3.zip Cobra Mk III version], [http://sancho.dk/oolite/Dr_HUD.zip Custom version]
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [[Dragon|Dragon Assault Craft (Updated 9/8/08)]]
| [[Dragon|Dragon Assault Craft]]
|
| Ships / Equipment. Adds the Dragon Assault Craft, a heavy combat ship available in several different paint-jobs. Also adds the Military Smart Missile, an improved Hard Head Missile with more bang for your Credit. Both the ship and missile are available to the player and NPCs alike.
|-valign="top"
| [http://www.mediafire.com/?sharekey=ca166c7e38ef78c6e7c82ed4b8f0c380e04e75f6e8ebb871 ''Dragonfly/Firefly S.T'']
| [[Dragonfly S.T /Firefly S.T]]
|
|Ships. Adds the Dragonfly S.T and also the much faster Firefly S.T variant. Small fast ideal ship for pirates or bounty hunters.
|-valign="top" bgcolor="#e7e7ff"
| [[Drones_OXP|Drones]]
|
|
|Weapons. Three new autonomous drones to help the player (and NPCs) in combat. Fire and forget, with targeting taken from the ships scanning computers. Variants are the combat drone (standard fighting drone), the kamikaze drone (upgraded with a low yield warhead) and anti-Thargoid drone (GalCop commission, with stronger lasers and better speed and manoeuvrability, plus battle computer optimisation to seek and destroy Thargoid vessels). All can be recovered and possibly re-used if they survive battle.
|-valign="top"
| [[Eagle Mk II]]
| [[Eagle Mk II]]
|
| Ships. Adds the cheap Eagle Mk II escort vessel in several different versions, including an enhanced SE.
|-valign="top" bgcolor="#e7e7ff"
| ''[http://www.box.net/shared/xkltqit3oj Eagles Mk's I to IV (By ADCK)]''
|
|
|Adds 4 Eagle Long Range Fighters to the game, There are 8 different colours to each Eagle, and 4 player versions. Made by ADCK. (Includes shaders which require Oolite 1.69 or later)

|-valign="top"
| [[Energy_Equipment_OXP|Energy Equipment]]
|
|
|Equipment. The emergency charge device - a pylon-mounted top-up for the ships systems, and the emergency energy unit - an internally fitted automatically triggered top-up when the juice runs low.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon]
|
|
| Equipment. Mark a position in space by deploying a pylon mounted beacon.
|-valign="top"
| [http://www.arcadia-digital.net/steve/Oolite/Ships/Executive%20SpaceWays%20v2.2.zip ''Executive Spaceways'']
| [[Delta_Long-Range_Escort|Delta Long-Range Escort]]

[[Gemini_Escort|Gemini Escort]]

[[Starseeker_Personal_Shuttle|Starseeker Personal Shuttle]]

[[Strelka_CruiseLiner|Strelka Cruise Liner]]

[[Trident_Executive_Shuttle|Trident Executive Shuttle]]
|
| Ships. Adds the Executive SpaceWays fleet of ships. Commanders may consult the [[Executive_SpaceWays|Executive SpaceWays Sales Brochure]] for further details.
|-valign="top" bgcolor="#e7e7ff"
| [[External Views OXP|External Views]]
|
|
| Utility. Adds better outside views to all the Classic Elite Ships. Warning: Do '''not''' use with Oolite 1.70 and above! From Oolite 1.70 onwards improved outside views have been added to the game itself, so you don't need this OXP anymore. Just throw it away.

|-valign="top"
| [[Far_Arm_ships|Far Arm ships]]
| [[Far_Arm_Sunracer|Sunracer]] 
[[Far_Arm_Scow|Scow]] 
[[Far_Arm_Tanker|Tanker]] 
[[Far_Arm_Corsair|Corsair]] 
[[Far_Arm_Dart|Dart]] 
[[Far_Arm_Hunter|Hunter]] 
[[Far_Arm_Cruiser|Cruiser]] 
[[Far_Arm_Titan|Titan]] 
[[Far_Arm_Manchi_Vulture|Manchi Vulture]] 
[[Far_Arm_Manchi_Wasp|Manchi Wasp]]
|
| Ships. This OXP adds 10 ships, inspired by [http://en.wikipedia.org/wiki/Space_Rogue Paul Neurath's Space Rogue] to the Ooniverse. There is also a new alien race called the Manchi, who pilot ships of bizarre design. Released under the [http://creativecommons.org/licenses/by-nc-sa/3.0/ Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported] License.

|-valign="top" bgcolor="#e7e7ff"
| [[Far Star OXP|Far Star]]
| [[Far_Star_Murderer|Far Star Murderer]]
|
| Ships. A mid-range fighter / trader, with a fair sized cargo bay.

|-valign="top"
| [[Media:Farsun1.03.zip|''Farsun v1.03'']]
|
|
| Utility. Places suns further away from the planet than standard Oolite. Now fully compatible with the Nova mission.

|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/ferdelance_ng.oxp.zip ''Fer de Lance NG'']
|
|
| Ships. Adds a more powerful version of the Fer de Lance with several custom paint jobs.

|-valign="top"
| [http://oosat.alioth.net/files/ferdepai.oxp_.zip ''Ferdepai'']
| [[Ferdepai]]
|
| Ships. Adds a new fighter / trader to Galaxy 2.

|-valign="top" bgcolor="#e7e7ff"
| [http://www.msdownload.co.uk/Oolite/FighterHud.zip ''Fighter HUD Mk. II'']
| [[Fighter_HUD_%28Oolite%29|Fighter HUD]]
|
| Alternative HUD.

|-valign="top"
| [http://oosat.alioth.net/files/Firewasp.zip ''Firewasp'']
| [[Firewasp]]
|
| Ships. A fast interceptor.

|-valign="top" bgcolor="#e7e7ff"
| ''[[Flying Dutchman OXP|Flying Dutchman]]''
| [[Griff Wireframe Cobra]]
|
| Feature / Ships. Adds the small chance to meet a ''Ghost Ship'' in the Ooniverse. What is it? Some claim that it's the ghost of Commander Peter Jameson, reported lost at the end of the last Thargoid War, others that it is simply a manifestation of all those lost souls who were trapped in the trackless depths of interstellar space. One common story is the trail of bad luck and hideous deaths that follow in the wake of the ship's sightings...

|-valign="top"
| ''[[Freaky Thargoids OXP|Freaky Thargoids]]''
|
|
| [[shaders in Oolite|Shader]] example, requires Oolite 1.69. With this OXP installed, Thargoids will use the new Shaders.

|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/e43ftmvqmr ''Free Trade Zone'']
|
| [[Free_Trade_Zone|Free Trade Zone]]
| Stations. Adds an independent trading post of dubious legality to Multi-Government systems.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/fsr.zip ''Frog Space Rickshaw'']
| [[Frog_Space_Rickshaw|Frog Space Rickshaw]]
|
| Ships. Adds a chatty space taxi service to the safer systems.

|-valign="top" bgcolor="#e7e7ff"
| [[Fuel_Collector_OXP|Fuel Collector]]
|
|
|Equipment. The Fuel Collector enables you to very slowly gather fuel whilst cruising in space, whether en-route to a station, or in interstellar space should a witch-jump malfunction occur. You can also gather any unburnt fuel from destroyed ships as well as tap fuel from derelict or abandoned ships.

|-valign="top"
| [[Fuel_Station_OXP|Fuel Station]]
|
|
|Station. Adds fly-thru Fuel Stations and Fuel Satellites near the witchpoint and along route one.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Fuel Tank'']
|[[Fuel Tank]]
|
| Equipment. Mounts in place of a missile, to top up 3 light years of fuel.

|-valign="top"
| [[Galactic_Navy_OXP | Galactic Navy]]
| [[Navy_Frigate|Navy Frigate]]

[[Navy_Medical_Ship|Navy Medical Ship]]

[[Navy_Minesweeper|Navy Minesweeper]]

[[Navy_Transport|Navy Transport]]
| [[Navy_SecCom_Station|Navy Sector Command Station]]
| Ships and Stations. A selection of ships and space stations that adds to the already formidable arsenal of the Galactic Navy. Allows commanders to join the Navy Reserves. Requires the Behemoth OXP.

|-valign="top" bgcolor="#e7e7ff"
| [[Gates_OXP|Gates]]
|
|
|Station. Adds short-cut jump gates to suitable systems, speeding journeys between the main station and witchpoint for a fee of only 250Cr.

|-valign="top"
| [[Generation_Ships_OXP|''Generation Ships'']]
| [[Generation_Ships_OXP|Generation Ships]]
|
| Ships. The mythical Generation Ships appear from time to time.

|-valign="top" bgcolor="#e7e7ff"
| [[Globe_station|Globe Station2.0]]
|
| [[Globe_station|Globe Station]]
| Stations. A new type of station appears at advanced systems. (Updated 22/10/2009)

|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/greekshipset1.zip ''Greek Ships'']
| [[Penelope_Class_Freighter|Penelope Class Freighter]]

[[Telemachus_Class_Escort|Telemachus Class Escort]]

[[Ulysses_Class_Interceptor|Ulysses Class Interceptor]]
|
|Ships. A large trade ship and escorts. Sometimes also used by pirates.

|-valign="top" bgcolor="#e7e7ff"
| [[Griff_ArcElite|Griff ArcElite]]
|
|
|Ships. New versions of the native Oolite ships textured & shaded to resemble how they originally appeared in the Acorn Archimedes version of Elite

|-valign="top"
| [[Griff_Industries|Griff's Normalmapped Ships]]
|
|
| This is where you can get your hands on some of the best looking ships for Oolite, using shaders and normal-mapping. See the OXP page for a gallery of all the ships. This OXP requires [http://developer.berlios.de/project/showfiles.php?group_id=3577&release_id=13778 Version 1.71 of Oolite] or higher.

|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/griffin2.oxp.zip ''Griffin Mk.II]
| [[Griffin_Two_%28Oolite%29|Griffin Two]]
|
|Ships. Adds the Griffin Mk II from Frontier.

|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/GrittyCoriolis.oxp.zip ''Gritty Coriolis'']
|
|
|Stations. The Corolis Station gets a more detailed texture.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip ''G-HUD Mk2'']
|
|
|Alternative HUD.
|-valign="top"
| [[Media:halsis.zip|''Hal's Hot Sister'']]
|
|
|Sound Set, featuring a female cockpit voice.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/boyracers.zip ''Hatchling Boyracers'']
| [[BoyRacer|Boy Racer]]
|
|Ships. The talkative (and often insulting) Boyracers appear in the more advanced systems.
|-valign="top"
| [http://www.mediafire.com/file/mm2ekntynom/Hawksound.zip ''Hawksound'']
|
|
|Sound Set. Clean sounds. Quality female computer voice, new weapon, damage and some station interface sounds.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/Herald.zip ''Herald'']
| [[Herald_Military_Gunboat|Herald Military Gunboat]]
|
|Ships. A powerful police and Navy interceptor.
|-valign="top"
| [[Hired_Guns_OXP|Hired Guns]]
|
|
| Weapons/Equipment. Gives the chance to agree a contract for a pair of ships to accompany you on your next journey and fight on your behalf alongside you.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/tugs.zip ''Hognose Tugships'']
| [[Hognose]]
|
|Ships. The chatty tug ships can be seen towing broken down ships.
|-valign="top"
|[[HoOpy Casino]]
|
|[[HoOpy Casino]]
|Stations. HoOpy Casinos appear near the station in advanced systems. Commanders who chose to dock can win or lose credits in games of chance.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.mediafire.com/?2vgjwpj6xdy ''Hotrods v0.52c''], [http://www.box.net/shared/j2r6frlvq1 ''Hotrods v0.52d'']
|
|
|Ships. Classic Elite Ships appear with custom paint jobs. Includes also a large number of custom and standard racing vehicles and a spacegang in tiger-getup that doesn't like the player. A rework, and a new name, for Custom Paints & Racers. Replaces [http://capnhack.com/hosting/oolite/Oolite/OXPs/custpaint1.zip ''Custom Paint Jobs'']
|-valign="top"
|[[Hyperradio_js_OXP | Hyperradio v1.17]]
|
|
|Equipment. This device gives you the ability to listen to your own music. It is expandable by musicpacks that can be separately installed and compatible to OXPConfig, RepairBots and Snoopers. (Updated 11/02/2010)
|-valign="top" bgcolor="#e7e7ff"
| [[Icarus (Oolite)|Icarus]]
| [[Icarus (Oolite)|Icarus]]
|
|Ships. Adds the Icarus Light Trader from [[Seldar Shipyards]]. A small fighter / trader based on blueprints from the lost Solice system.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/illicit_unlock.oxp.zip ''Illicit Unlock'']
|
|
|Utility. Allows the player to fly all the Classic Elite Ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Imperial_Courier_%28Oolite%29|Imperial Courier]]
| [[Imperial_Courier_%28Oolite%29|Imperial Courier]]
|
|Ships. The powerful Imperial Courier from Frontier, constructed by [[Seldar Shipyards]]. Updated from the version on Oosat1.
|-valign="top"
| [[Interstellar help OXP|''Interstellar help'']]
|
|
|Feature. Allows you to help out some traders who got stuck in interstellar space without fuel. You will be rewarded.
|-valign="top" bgcolor="#e7e7ff"
| [[ionics_OXP|Ionics 1.2.3]]
| [[Ionics_Funnelweb|Ionics Funnelweb]]

[[Ionics_Huntsman|Ionics Huntsman]]

[[Ionics_Redback|Ionics Redback]]

[[Ionics_Whitetail|Ionics Whitetail]]
|
| [[Oolite_Missions#Ionics|Mission]]. A series of missions set in Galaxy 2 featuring the Ionics Company of Zaria. [[Ionics_OXP|More Information here.]] Updated on 7-4-2009. This version is now compatible with multi-mission offering of other OXPs.
|-valign="top"
| [[Ixian_Ships|''Ixian Ships'']]
| [[Ixian_Battle_Cruiser|Ixian Battle Cruiser]]

[[Ixian_Bezerka|Ixian Bezerka]]

[[Ixian_Freighter_MK1|Ixian Freighter Mk I]]

[[Ixian_Gunship|Ixian Gunship]]

[[Ixian_No-Ship_Mark_I|Ixian No-Ship Mk I]]
|
|Ships. A set of ships from Dune. Used by pirates and traders alike.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/jabberwocky.zip ''Jabberwocky'']
|
|
|Ships. Adds the powerful Jabberwocky fighter / trader.
|-valign="top"
| ''[[JavaScript test OXP|JavaScript test]]''
|
|
| [[Scripting Oolite with JavaScript|JavaScript scripting]] example, requires Oolite 1.68.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/dropbox/kestrel_falcon1_71_0.zip ''Kestrel&Falcon v1.71.0'']
| [[Kestrel]]
[[Falcon_%28Oolite%29|Falcon]]
|
| Ships. Adds a powerful Star Wars style Falcon, used by pirates and traders alike, and an interceptor used by the Police and Navy. Both models are also available on the open market. Improved from the older Kestrel.oxp and Falcon.oxp models, still available from the [http://www.box.net/public/b2tic3tjsk#1:4083657 ''Benulobiweed''] main download area.
|-valign="top"
| [[Killit_OXP|''Killit'']]
|
|
| Weapons. Adds a bunch of insane super weapons.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.crimsonforge.co.uk/cloister/kirin.zip ''Kirin'']
| [[Kirin]]
|
| Ships. Adds a heavy military hauler, CV and XM versions used by both pirates and traders.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/kleptohud.oxp.zip ''Klepto-HUD'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://sancho.dk/oolite/lane_legal.zip ''Lane Legal Racers'']
| [[Krait]]

[[Mamba]]

[[Sidewinder]]
|
|Ships. Adds NPC versions of ships from different [[Racers#Listing_of_sponsored_teams|racing teams]].
|-valign="top"
| [http://capnhack.com/hosting/oolite/dropbox/Lave171.zip ''Lave v1.71'']
|
|
| Planets. Gives the Lave System a make-over adding all the features described in The Dark Wheel novella included with the original Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Lave_Academy_OXP|Lave Academy]]
|
|
| Station. Adds the Lave Academy Orbital station above Lave (and now other planets), with three new mini-game tests of the Commanders' ship skills.
|-valign="top"
| [[Media:Llama.zip|Llama]]
| [[Llama]]
|
|Ships. Adds the Llama fighter / trader. Updated from the version of Oosat1 to fix a small bug.
|-valign="top" bgcolor="#e7e7ff"
|[[Localhero_OXP|Localhero v1.05]]
|
|
|Mission. Adds a mission campaign in the first galaxies. (Updated 9.04.2008)
|-valign="top"
| [[LongWay_OXP| ''Long Way Around 1.1'']]
|
|
| [[Oolite_Missions#The_Longway_Mission|Mission]]. A transport mission well suited to the novice in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Longshot.zip ''Longshot'']
| [[Longshot]]
|
|Ships. Adds the Longshot fighter / trader, regarded by many as a cheaper alternative to the Cobra Mk III.
|-valign="top"
| [[Lovecats.oxp|''Lovecats 1.2'']]
|
|
| [[Oolite_Missions#Love_Cats|Mission]]. Love and betrayal amongst the feline races of Galaxy 4. A fast ship, fuel injectors, fuel scoops and a hard heart are advised before you tangle with these cats! Version 1.1 missionclash proof.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/mPakRedux.zip ''M-Pack (rusties)'']
|
|
| Ships. Adds rusty versions of all the Classic Elite ships. Bargain basement prices, although these old bangers are in a poor condition compared to a brand new model. Engines may be worn out reducing maximum speeds and shield generators are frequently held together with duck-tape. When you try to trade one of these old rust buckets in at the shipyards, you may also find that the trade-in value is reduced. None the less, they are cheap and can still haul cargo between the stars.
|-valign="top"
| [http://oosat.alioth.net/files/manta.oxp_.zip ''Manta'']
| [[Manta]]
|
|Ships. Adds the Manta light escort craft.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/marett_vol1.zip ''Marett Space Corporation'']
| [[Adder_Mk_II|Adder Mk II]]

[[Mosquito_Trader|Mosquito Trader]]

[[Mosquito_Sport|Mosquito Sport]]
|
|Ships. A collection of fighters and medium traders from Marett Space Corps.
|-valign="top"
| [http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip ''Medusa Hud'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/megawalnutdash.oxp.zip ''Mega-Walnut Dashboard'']
|
|
| Alternative HUD.
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Merlin'']
| [[Merlin_%28Oolite%29|Merlin]]
|
|Ships. An interceptor used by the Police and Navy, but also available on the open market.
|-valign="top" bgcolor="#e7e7ff"
| [[Media:MildAudio.oxp.zip|''MildAudio'']]
|
|
| Sound Set.
|-valign="top"
| [[Military_Fiasco|Military Fiasco]]
| [[Basilisk]]

[[Hydra]]

[[Leviathan]]

[[Rattle_Cutter|Rattle Cutter]]

[[Wolf_Mk.2_%28Oolite%29|Wolf Mk II Paragon]]
|
| [[Oolite_Missions#Military_Fiasco|Mission]]. A mission for the Navy available to a Commander with more than 1,000 kills. Also equips the Navy with powerful cruisers. Version 2.0 is updated version of the Military OXP over the version on Oosat2. Use this one, as the old version can clash with other Mission OXPs. You must also use the Updated version of [http://oosat.alioth.net/files/Murgh-Xships.zip ''Murgh's X-Ships''] to play this OXP.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/gwxstations.oxp.zip ''Military Station'']
|
| [[Military_station|Military Station]]
|Stations. Well armed Military Stations appear in the more advanced systems.
|-valign="top"
| [http://www.msdownload.co.uk/Oolite/stingray.zip ''Military Stingray'']
| [[Stingray_%28Oolite%29|Stingray]]
|
|Ships. Adds the Military Stingray to the GalCop Navy fleet. Second hand versions are sometimes available on the open market.
|-valign="top" bgcolor="#e7e7ff"
| [[Milspec HUD|Milspec HUD]]
|
|
| Alternative HUD. Adds targeting aids, emphasis on functionality.
|-valign="top"
| [[Missiles and Bombs|Missiles and Bombs]]
|
|
|Equipment. Adds the Cascade stand-off missile, Multiple-warhead anti-Thargoid missile, Frag Mine, Frag Missile, EMP Missile and short-range defence missile to the game. The new weapons are available to the player and NPCs alike.
|-valign="top" bgcolor="#e7e7ff"
| [[Missile_Rack_OXP|Missile Rack]]
|
|
|Weapons. Pylon mounted racks of three mini-missiles. Smaller and less powerful than standard missiles, but effectively triple the available armaments a ship can carry.
|-valign="top"
| [http://sancho.dk/oolite/missionaries.zip ''Missionaries v1.1'']
| [[Happy_Eye_Pulpit_Pod|Happy Eye Pulpit Pod]]
|
|Ships. Clerics of four faiths are added to the Universe, spamming Commanders with requests to worship their Gods.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/monument.zip ''Monument'']
|
|
|Feature. A monument to famous Commanders can sometimes be seen near the Sun.
|-valign="top"
| [http://capnhack.com/hosting/oolite/dropbox/morrigan101.zip ''Morrigan'']
|
|
|Ships. Adds a vast trade ship to the Universe. (v 1.0.1, Bugfixed december 2009)
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds2.zip ''Murgh's Replacement Sounds'']
|
|
| Sound Set.
|-valign="top"
| [[Murgh_Xships OXP|''Murgh's X-Ships'']]
| [[Bandy-Bandy]]

[[Chuckwalla]]

[[Eel_Rapier|Eel Rapier]]

[[Taipan]]
|
|Ships. A fast courier craft and two light escort ships are added. Updated from the version on Oosat1. You MUST use this version for the [[Military_Fiasco|Military Fiasco]] Mission to run properly!
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Navy Starships'']
|
|
|Ships. Arms the Navy with powerful cruisers including a docakable Star Trek style Starship.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/newships.oxp.zip ''New Ships'']
| [[Hamadryad]]

[[Josher]]

[[Naga]]

[[Ringhals]]
|
|Ships. Adds a variety of mining and trade ships seen in previous versions of Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Neolite Ships]]
|
|
| Oolite ships replacement set.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip ''NG HUD'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/nuvipers.zip ''Nu Vipers'']
| [[GalCop_Viper_Mark_II|GalCop Viper Mark II]]
[[GalCop_Viper_Cruiser|GalCop Viper Cruiser]]
|
|Ships. Increases the types of Viper patrol ships appearing in the space lanes and defending Stations.
|-valign="top"
| [[Nukes.oxp|Nuclear Torpedos]]
|
|
| Equipment. Adds some powerful, but slow moving, missiles.
|-valign="top" bgcolor="#e7e7ff"
| [[Old Ships]]
| [[Bushmaster_Miner|Bushmaster Miner]]

[[Cat_%28Oolite%29|Cat (Cougar)]]

[[Chameleon_%28Oolite%29|Chameleon]]

[[Ghavial_%28Oolite%29|Ghavial]]

[[Iguana_%28Oolite%29|Iguana]]

[[Monitor_%28Oolite%29|Monitor]]

[[Ophidian_%28Oolite%29|Ophidian]]

[[Salamander_%28Oolite%29|Salamander]]
|
|Ships. A collection of ships from ArcElite and Elite-A.
|-valign="top"
| [[Oo-Haul]]
| [[L-Crate_Hauler|L-Crate Hauler]]
|
|[[Oolite_Missions#Oo-haul_Escort_Missions|Mission]]. Vast corporate bulk haulers can be seen in the space lanes. Commanders with a respectable Elite rating who chose to dock with a [[Pi-42]] base may also be offered missions to escort one of these haulers safely to its destination. You must also install the [[Your Ad Here!|Your Ad Here!]] OXP for this OXP to work properly.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/index.php/Image:OoliteItaliano_v1.3.zip ''Oolite Italiano v1.3'']
|
|
|Miscellaneous. First ever Oolite localization OXP. Requires Oolite v1.73 or later.
|-valign="top"
| [http://www.box.net/shared/ch3lsepk9k ''Oolite Russian v1.0'']
|
|
|Miscellaneous. The second Oolite localization OXP. Requires Oolite v1.72 or later.
|-valign="top" bgcolor="#e7e7ff"
| [[Orb]]
| [[Orb]]
|
|Ships. Adds a new alien race, which may (or may not) help GalCop in the battle against the Thargoids.
|-valign="top"
| [[Media:Orbits.zip|''Orbits'']]
|
|
|Utility. Positions planets on orbits around the sun.
|-valign="top" bgcolor="#e7e7ff"
| [[Ore_Processor|''Ore Processor'']]
|
|
| [[Ore_Processor|Equipment]]. When mounted to a ships fuel scoop systems extracts valuable materials from asteroid fragments. A must for any Commander working as a miner.
|-valign="top"
| [http://oosat.alioth.net/files/outrider.zip ''Outrider'']
| [[Outrider_%28Oolite%29|Outrider]]
|
| Ships. A medium fighter produced by the [[Taranis Corporation HQ (Oolite)|Taranis Corporation]].
|-valign="top" bgcolor="#e7e7ff"
| [[OXPConfig|OXPConfig1.08]]
|
|
| Tools/Utility. This tool gives you the ability to configure several oxps. It changes internal (local) settings of the oxps to enable (or disable) logging or audio functions and special settings to recognize errors or to avoid clashes. (Updated 04/09/2009)
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Pallas'']
| [[Pallas]]
|
|Ships. A fast but lightly shielded fighter.
|-valign="top" bgcolor="#e7e7ff"
| [[P.A. Groove Stations OXP]]
|
|
|Stations. Adds lots of different types of Coriolis and Dodec Stations.
|-valign="top"
| [http://oosat.alioth.net/files/Pelamis.zip ''Pelamis'']
| [[Pelamis]]
|
|Ships. Adds the Pelamis trade ship.
|-valign="top" bgcolor="#e7e7ff"
| [[Personalities OXP|''Personalities'']]
|
|
| Ships. Adds a bunch of unique, well-known personalities to the Ooniverse. Keen to meet yourself in your game (or have others meet yourself in their game)? Submit your own personality in the OXP's thread on the Oolite BBs.
|-valign="top"
| [http://oosat.alioth.net/files/Phoenix.zip ''Phoenix'']
| [[Phoenix]]
|
|Ships. A strange ship, built from salvaged parts from various Serpent Class ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Pirate Coves OXP|Pirate Coves]]
|
| [[Pirate Coves OXP|Pirate Coves]]
| [[Oolite_Missions#Pirate_Coves|Mission]]. Some rock hermits in the more dangerous systems have been taken over by pirates. Traders coming too close are likely to be assaulted by scrambled pirates keen to relive them of their cargo.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip ''Pirate Traps'']
|
|
|Feature. To combat piracy GalCop sometimes deploys dummies of trade ships. Pirates who fire on them have their details transmitted to the police and face large fines.
|-valign="top" bgcolor="#e7e7ff"
| [[Planetfall_OXP|Planetfall]]
|
|
|System. Allows the player to land on and trade at the planets and moons of each system.
|-valign="top"
| [[Pods_OXP|Pods]]
|
|
|Cargo. Many new varieties of cargo pod, including fuel, missile, bulk, and empty, plus pods which take a couple of goes to scoop, jam in the fuel scoop, explode and even bring a trumble. Designed as a balanced OXP, to add some positives and some negatives to cargo scooping, to give more realism. Those of you who also use the [[UPS_Courier|UPS Courier]] OXP can also [http://www.box.net/shared/sytn2yhpu0 download a little add-on] to the OXP that applies some of the new pods to UPS ones too (UPS Courier needs to be installed for the add-on to work).

|-valign="top" bgcolor="#e7e7ff"
| [[Probe_OXP|Probe]]
|
|
|Equipment. A long-range probe missile, flies away from the ship and scans at ranges of 50km and 100km, reporting ships found back to the ship. It then turns around and comes back, ready for fuel scooping and re-use.
|-valign="top"
| [http://oosat.alioth.net/files/PTI.zip ''Pteradyne Technologies Ships''] - ([http://oosat.alioth.net/files/PTI_bugfix11.zip ''bug fix''])
| [[Excalibur]]
[[Paladin]]
|
|Ships. A powerful combat ship, the Excalibur is offered for sale on the open market. The Paladin is the even tougher Military version, although sometimes these ships fall into the wrong hands.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/pcc.oxp.zip ''Python Class Cruiser]
| [[Python_Class_Cruiser|Python Class Cruiser]]
|
|Ships. A large powerful trade ship, which can also hold its own in battle.
|-valign="top"
| ''[[Media:Python_Class_Cruiser.oxp.zip|Python Class Cruiser version 2.6]]''
|
|
| As above, but features [[shaders in Oolite|Shaders]]. Shaders require Oolite 1.69 or later.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/racers.oxp.zip ''Racers'']
|[[Chicaneer Mk II]]

[[Chicaneer Mk IV]]

[[Dragster Mk I]]

[[Dragster Mk II]]
|
|Ships. Adds dedicated racing ships to the Universe. Although very fast, these ships are pure racers with no cargo bays and light shields. The focus on pure speed makes them ill-suited to combat or trading roles.
|-valign="top"
| [[Ring_Racer_OXP|Ring Racer]]
|
|
| Mission. Corporate Systems Ring Racing League in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [[RingPod.oxp|''Racing Rings'']]
|
|
|Feature. Adds Racing Rings to the Galaxy 1 systems of Lave and Zanoce. Fly through the rings in order and completing the race circuit will transmit the competitors' time.

|-valign="top"
|[[Random Hits OXP|Random Hits Version 1.3.6 Beta (Updated 5/8/09)]]
|[[GalMine Hopper|GalMine Hopper]]

[[GalMine AutoMiner|GalMine AutoMiner]]

[[GalMine Cargo Drone|GalMine Cargo Drone]]
|[[Space Bar|Space Bar]]
|[[Oolite_Missions#Random_Hits|Missions]] / Ships / Stations / Feature. Adds [[Space Bar|Seedy Space Bars]] to the space lanes of all Anarchy Systems. Commanders who chose to dock with one can view a Bulletin Board displaying details of the local Galaxies Most Wanted Criminals. Large bounties are paid for killing or capturing one of these offenders. Missions are procedurally generated using a database of over 40,000 words creating over one trillion different Bulletin Board Advertisements. Missions are therefore effectively never-ending. This OXP requires [http://developer.berlios.de/project/showfiles.php?group_id=3577&release_id=13778 Version 1.72.2 of Oolite].

|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/RoC.oxp.zip ''Remorse of Conscience'']
| [[Remorse_Of_Conscience_v2|Remorse Of Conscience]]
|
|Ships. A trade ship with a large hold, that can hold its own in combat. A good upgrade from the Cobra Mk III.
|-valign="top"
|[[Renegade Pirates OXP|Renegade Pirates V3.0]]
|
|
|Ships / Feature. Adds rare very well armed pirate versions of Classic Elite ships to the more lawless systems. These pirates carry high bounties, but their multiple lasers and plasma cannons will make mince-meat of a young Jameson. Do not install this OXP until you have an Iron Ass!
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/RVandGS.zip ''Renegade Viper + Grass Snake'']
|[[Renegade Viper]]

[[Grass Snake]]
|
|Ships. Sometimes even GalCops are victims of crime, finding their Vipers stolen from the docking berth. The joy-rider gives the stolen Viper a new lick of paint and joins a pirate fleet. Large bounties are paid for ridding the space lanes of these thieves. The Grass Snake is a trade ship with a large hold, often used by pirates.
|-valign="top"
| [[Repair_Bots_OXP|Repair 'Bots]]
|
|
| Equipment. A pylon mounted canister of repair nanobots. These can be activated in-flight, when they scan your ship for damaged equipment and attempt to fix an item of it (a random one if multiple items are found). They are reliable for lower tech items, but as the equipment gets more complicated they sometimes struggle. But if all else fails, buy, try and fly again...
|-valign="top" bgcolor="#e7e7ff"
| [[RegistrationID|Registration ID]]
|
|
| Flavour. All Oolite standard ships now have ID tags.. You need at least Oolite 1.73 and a Graphics card capable of running shaders on a full setting..
|-valign="top"
| [[Rock Hermit Locator]]
|
|
|Equipment. The Rock Hermit Locator is a piece of equipment for your ship to locate Rock Hermits. Useful for miners and Traders.. You need to already have bought the advanced space compass that works in tandem with the RHL ("Rock Hermit Locator").
|-valign="top" bgcolor="#e7e7ff"
| [http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Saleza Aeronautics'']
| [[Bellatrix_Cruiser|Bellatrix Cruiser]]

[[Rigel_Bomber|Rigel Bomber]]

[[Saiph_Interceptor|Saiph Interceptor]]
|
|Ships / Feature. High Tech Corporate States gain their own patrol craft. Some of these ships are also available on the open market.
|-valign="top"
| [http://www.box.net/shared/mcmeur2axl''Santa''] - ([http://oosat.alioth.net/files/Santa.zip alternative lo-end version])
|
|
|Ships. Just for fun adds a (very rare) Santa Sledge to the space lanes escorted by plasma gun toting reindeer space bikers!
|-valign="top" bgcolor="#e7e7ff"
| [[Save_Anywhere|Save Anywhere]]
|
|
|Feature. Save Anywhere allows you to save your game at any OXP Station, instead of only at Main Stations, as in the standard game.
|-valign="top"
| [[Media:BlackBaron1.70.zip|''Scourge of the Black Baron v1.70'']]
|
|
| [[Oolite_Missions#The_Scourge_of_the_Black_Baron|Mission]]. A sequel to the [http://capnhack.com/hosting/oolite/Oolite/OXPs/longway.oxp.zip ''Long Way Around''] mission, featuring combat and transport missions. Well suited to a relative novice in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [[Second_Wave_OXP|Second Wave]]
| A variety of new alien ship variants.
|
| Ships. Some new variants on the standard Thargoid Warship and Thargon Robot Fighter.

|-valign="top"
| [http://oosat.alioth.net/files/s-ships1.zip ''Selezen's S-Ships'']
| [[GalCop_SWAT_Viper|GalCop SWAT Viper]]

[[Oresrian_Trader|Oresrian Trader]]
|
|Ships. In response to increasing piracy GalCop has introduced the SWAT Viper, a beefed up version of the standard Viper. Also adds the peaceful Oresrian Trader.
|-valign="top" bgcolor="#e7e7ff"
| [[Sell equipment OXP|''Sell Equipment'']]
|
|
| Feature / Equipment. Allows you to resell all equipment you bought at an equipment store of suitable techlevel. For a small fee you purchase the "Sell xyz"-option, and are refunded 60 per cent of the original price.
|-valign="top"
| ''[[Shady Cobra OXP|Shady Cobra]]''
|
|
| Ships. A [[shaders in Oolite|Shader]] example (requires Oolite 1.69 or later). Replaces the normal model for the Cobra Mk III with one featuring the new Shaders.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/All-Stars_0.zip ''Skrounk All-Stars Limited'']
| [[All_Stars_Large_Freighter|All Stars Large Freighter]]

[[Seymour_Class_Sled|Seymour Class Sled]]

[[Starbelly_Class_Sled|Starbelly Class Sled]]

[[Starhawk|Star Hawk]]

[[Starwolf_Mark_I|Starwolf Mk I]]
|
| Ships. A set of ships featuring a large trade ship and a variety of fighters and escorts.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/snark.zip ''Snark'']
|
|
|Ships. The Snark is a powerful fighter / trader, often used by pirates and bounty hunters.
|-valign="top"
| [[Snoopers|Snoopers2.0]]
|
|
| Feature. The galactic news network. Updated 05/02/2010
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Spearhead.zip ''Spearhead Interceptor Mk.I'']
|
|
|Ships. A pure fighter, fast and nippy but with a weak shield, no cargo bay and can be a twitchy bird to fly. Often used as an escort or part of a pirate fleet acting in a hit an run role.
|-valign="top"
| [[Spy_Hunter_OXP|''Spy Hunter'']]
|
|
| [[Oolite_Missions#Spyhunter|Mission]]. A mission for the Galactic Navy available to a Commander with a rating of 'Dangerous' or above. Spys from the Empire sometimes infiltrate GalCop space. Commanders wishing to volunteer for hunting duties should visit the Navy base at Inines in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/StarWars.zip ''Star Wars Ships'']
| [[A-Wing]]

[[B-Wing]]

[[Lambdashuttle|Lambda Shuttle]]

[[Tie-Fighter]]

[[Tie-Interceptor]]

[[X-Wing]]

[[Y-Wing]]
|
|Ships. Adds a set of ships from the Star Wars Universe to Oolite. Tie Fighters are occasionally used by GalCop to support Viper patrols, but all ships are available on the open market and may be used by traders, pirates and bounty hunters alike.
|-valign="top"
| [[Status Quo Q-bomb OXP|''Status Quo Q-bomb'']]
|
|
|Feature. Changes the behaviour of Q-bombs according to the [[Status Quo]] novel. They don't detonate in gravity wells, like close to planets or suns.
|-valign="top" bgcolor="#e7e7ff"
| ''[http://www.box.net/shared/static/9cwp2jk84o.zip Sung's Detailed Textures]''
|
|
|Replacement textures for all Classic Elite Ships. The author's web-site no longer has a link to his textures. The link will download them directly from Lestradae's hosting site.
|-valign="top"
| ''[http://www.box.net/shared/535vddgddh Sung's Detailed Textures (Shader Version)]''
|
|
|Same as the above oxp, only now with shader support. Normal maps & Effects maps by ADCK. (Includes shaders which require Oolite 1.69 or later)
|-valign="top" bgcolor="#e7e7ff"
| [http://sancho.dk/oolite/sunskimmers.zip ''Sunskimmers'']
|
|
|Feature. Normally in Oolite ships tend to stick to the space lanes and so are rarely encountered on the way to the Sun. This OXP adds ships to the sun / planet corridor increasing the chance of meeting other ships whilst sun-skimming.
|-valign="top"
| [http://www.mediafire.com/?sharekey=ca166c7e38ef78c6e7c82ed4b8f0c380e04e75f6e8ebb871 ''S.T.E'']
| [[S.T.E]]
|
|Ships. The S.T.E addon ship a step up from the Cobra III improved trading capabilities also has increased speed over Cobra, is also available in 3 colour options blue, red and yellow.
|-valign="top" bgcolor="#e7e7ff"
| [[SuperCobra]]
| [[SuperCobra]]
|
|Ships. The awesome Super Cobra. A beefed up version of the Cobra Mk III featuring larger engines, more cargo space and stronger shields.
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Swift'']
| [[Swift]]
|
|Ships. As the name implies, a very fast ship often used by pirates or bounty hunters. Although fast, cargo space is limited and the shield is nominal.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.msdownload.co.uk/Oolite/system_redux.zip ''System Redux'']
| [[System_Redux_%28Oolite%29|System Redux]]
|
|Texture the home planet, add a planet/moon combination to each system.
|-valign="top"
| [[Taranis_OXP|''Taranis Corporation HQ'']]
|
| [[Taranis_Corporation_HQ_%28Oolite%29|Taranis Corporation HQ]]
| [[Oolite_Missions#Taranis|Mission]]. Adds the vast orbital [[Taranis_Corporation_HQ_%28Oolite%29|Taranis Corporation HQ]] to the Lerelace system in Galaxy 1. A mission is also available for law abiding Commanders with a rating of Competent or better. You must also have the [http://oosat.alioth.net/files/outrider.zip ''Outrider''] OXP installed for this OXP to work properly.
|-valign="top" bgcolor="#e7e7ff"
| [[Target_Autolock_OXP|Target Autolock]]
|
|
| Equipment. A software update for the standard [[Scanner_Targeting_Enhancement|scanner targeting enhancement]] equipment that automatically locks onto attacking ships if you have no prior target selected.
|-valign="top"
| [http://sancho.dk/oolite/Shield-tail.zip ''Teretrurus Mk.I'']
| [[Teretrurus Mk.I|Teretrurus MK.I]]
|
|Ships. A medium fighter / trader somewhat faster and tougher than the Cobra Mk III, but with a smaller cargo bay.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Terrapin.zip ''Terrapin Trader'']
| [[Terrapin]]
|
|Ships. A medium fighter / trader. A good upgrade from the Cobra Mk III.
|-valign="top"
| [http://oosat.alioth.net/files/Tescoura.zip ''Tesoura'']
| [[Tesoura]]
|
|Ships. A slow, but well shielded trade ship.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Thargoid_CarrierV1.zip ''Thargoid Carrier'']
| [[Thargoid_Carrier|Thargoid Carrier]]
|
|Ships. Arms the Thargoids with a vast carrier capital vessel. Many OXPs increase the fire-power available to the GalCop Navy. If you chose to play with these OXPs installed, then you should really give the Bugs a chance and allow them access to this mighty craft!
|-valign="top"
| [[Thargoid_Wars|Thargoid Wars V4.4 (Updated)]]
|
|
| [[Oolite_Missions#ThargoidWars|Mission]]. War with the Thargoids intensifies featuring new attack and defense missions. To avoid young Jamesons being out-gunned, the OXP missions will run in all Galaxies except Galaxy 1. Updated from the version on Oosat1. It is important that you use the updated version as the old version will clash with many other missions.
|-valign="top" bgcolor="#e7e7ff"
| [[Thargorn_Threat_oxp|''Thargorn Threat v1.3 (updated)'']]
| [[Terroriser_Frigate|Terroriser Frigate]]

[[Thargoid_Thargorn_Battleship|Thargoid Thargorn Battleship]]

[[Thargoid_Thorgon_Cruiser|Thargoid Thorgon Cruiser]]
|
|Ships. Redresses the game imbalance caused by the number of OXPs arming the Navy with warships. These Thargoid craft are very powerful and re-establish the Thargoid's place as a threat to mankind. Best played with the Behemoth OXP installed, for epic space battles.
|-valign="top"
| [http://www.wagar.org.uk/downloads/software/oolite/Tianve1.3.zip''Tianve'']
|
|[[Navy Station]]
|Planets / Stations. Adds scenery, including a pulsar, to the Galaxy 1 system of Tianve. A Station orbits the pulsar and fleets of pleasure liners can be seen taking tourists on flights around the pulsar. There are various adverts in the system, along with two extra 'space lanes', one between the planet and the pulsar and another between the pulsar and the witchpoint.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Tiger.zip ''Tiger'']
| [[Tiger_Mark_I|Tiger Mark I]]
|
|Ships. A truly awesome (and very expensive) multi-role craft.
|-valign="top"
| [http://oosat.alioth.net/files/TGY.zip ''Tionisla Orbital Graveyard]
|
|
|Feature. Adds the graveyard to the Galaxy 1 system of Tionisla, as described in the Dark Wheel. Long dead Commanders are buried in their rusting ships amongst monuments, Stars of David, Crucifixes and other religious symbols. Security patrols will make short work of any Commander foolish enough to desecrate the tombs.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/tori.zip ''Torus Station'']
|
| [[Torus_station|Torus Station]]
|Stations. Adds a vast 2001 style space station to very high tech level systems.
|-valign="top"
| [[Total_patrol_OXP|''Total patrol'']]
|
|
|Feature. Replaces the default police AIs with a totalPatrolAI which lets police ships patrol between all three major points of the system: planet, witchpoint and sun.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/eil0djqhca ''Trade Outpost v1.1'']
|
| [[Trader_Outpost_%28Oolite%29|Trade Outpost]]
|Griff trade outpost without ads.
|-valign="top"
| [[Traffic_Control_OXP|Traffic Control]]
|
|
| Station upgrade. Adds traffic control personnel to each system main station. They are happy to talk new Commanders (and older ones who've got too reliant on Docking Computers and then lost them) through approaching and manual docking with the station. There's even a cheery goodbye when you leave, just don't dawdle and block the station approach lane!
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Trans-Hab.zip ''Trans-Hab Station'']
|
| [[Transhab_station|Transhab Station]]
|Stations. Adds a large station with rotating arms to some medium tech level systems.
|-valign="top"
| [[Transports]]
| [[CoachWhip]]

[[Coral]]

[[Woma]]
|
|Ships. Adds more variety to the game. Passenger liners can be seen in the space lanes of the safer systems transporting paying customers to their destinations. Also features Moray Transporters and Large Woma fuel tankers to bring much needed supplies and fuel to space stations.
|-valign="top" bgcolor="#e7e7ff"
| [[Trident_Down|Trident Down]]
|

|
| [[Oolite_Missions#Trident_Down|Mission]]. A series of missions set in Galaxy 4 involving the investigation of a vicious attack on an Trident Shuttle operated by [[Executive_SpaceWays|Executive SpaceWays]].

|-valign="top"
| [[UPS_Courier|U.P.S. Courier]]
|
|
|[[Oolite_Missions#UPS_Courier_Company|Mission]] / Feature. The UPS Courier service will randomly offer Commanders the option of taking goods or documents from system to system. Some say experienced Couriers may also be offered combat missions.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/UrutaMK3.zip ''Urutu Mk.III'']
| [[Urutu_Mk.III|Urutu Mk III]]
|
|Ships. A medium fighter / trader from Elite-A.
|-valign="top"
| [http://oosat.alioth.net/files/UrutaMK4.zip ''Urutu Mk.IV'']
| [[Urutu_Mk.IV|Urutu Mk IV]]
|
|Ships. A medium fighter / trader from Elite-A.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.purgatori.net/Isis_Interstellar.htm ''Vampire'']
| [http://www.purgatori.net/Isis_Interstellar.htm Vampire]
|
|Ships. Adds the Purgatori Vampire series of combat ships. A strong combat ship in numerous different versions and paint-jobs. A Military version is used by the police, but several civilian versions of the ship are also available on the open market. Clicking the download link will take you to the sales brochure, where you can inspect further particulars and download the OXP.
|-valign="top"
| [[Vector_OXP|Vector1.3]]
| Vector
|
|Mission/Ships. Fast, rare and expensive. And some small surprises - So dive in and have a good time (Updated 31.08.2009)
|-valign="top" bgcolor="#e7e7ff"
| [[Velocity_OXP|Velocity]]
|
|
|Ships. A fast fighter ship.
|-valign="top"
| [[Venom]]
| [[Venom]]
[[Venom|Venom Renegade]]
|
|Ships. From Isis Interstellar who previously also made the [http://www.purgatori.net/Isis_Interstellar.htm Vampire]. This ship also provides three extra HUDs.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/weeviloid2.zip ''Weeviloid'']
| [[Weeviloid_Hunter|Weeviloid Hunter]]
[[Weeviloid_Scoutship|Weeviloid Scoutship]]
|
|Ships. The scout-ship is a light trade ship. The hunter is a fearsome multi-gunned war ship. Little is known about the Weeviloids and many Commanders meeting them have found them hostile.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds.zip ''Wiggy's Replacement Sounds'']
|
|
| Sound Set.
|-valign="top" bgcolor="#e7e7ff"
| [[Welcome_Mat_OXP|Welcome Mat]]
|
|
| Misc. Software upgrade for the communications systems to expand the information given to the commander on arrival from witchspace into a new system. Augments the system name message with planetary biographical details via the buoy network, plus the latest safety and alien presence information from Galcop. Also fully compatible with [[OXPConfig|OXPConfig]].
|-valign="top"
| [http://www.box.net/shared/vhho2av2az ''Wolf Mk.II v3.3]
| [[Wolf_Mk.2_%28Oolite%29|Wolf Mk II]]
|
|Ships. Adds the powerful Wolf Mk II, as seen in Elite-A.
|-valign="top" bgcolor="#e7e7ff"
| [[Media:Wolfs_variants.zip|''Wolfwood's Variants v1.5'']]
| [[Asp_Mk.I|Asp Mk I]]

[[Cobra_Courier|Cobra Courier]]

[[Cobra_Rapier|Cobra Rapier]]

[[Drake]]

[[Drake_Mk_II|Drake Mk II]]

[[Wolf Mk I]]
|
|Ships. A large selection of traders and fighters based on models seen in Classic versions of Elite. The ships strive to be on the same level with original ships and not too powerful in comparison to them. Tested on Oolite v1.70.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds3.zip ''Xaotik's Replacement Sounds'']
|
|
| Sound Set.
|-valign="top" bgcolor="#e7e7ff"
| [[Your Ad Here!]]
| [[Pi-42 security|Sidewinder Pi-42 Security]]

[[Tescoo security|Sidewinder Tescoo Security]]

[[Star security|Sidewinder Star Security]]

[[Mall Wart security|Sidewinder Mall Wart Security]]

[[Sainsboory's security|Sidewinder Sainsboory's Security]]
| [[Pi-42]]

[[Tescoo_Oxpress|Tescoo Oxpress]]

[[Star]]

[[Mall Wart]]

[[Sainsboory's]]

|Feature. This OXP adds a lot of variety to the Universe. Witch-point and navigation beacons are replaced with giant bill boards displaying adverts.
Every set features 50 different adverts and also adds a different type of constore to the universe (Set A introduces the Pi-42 constore, Set B the Tescoo Ooxpress constore etc). A constore is a dockable commercial base which is added to the space lanes of most systems with a large population.
Also from version 4 and above of this oxp each constore has its own security force, the ships of which are skinned in the colours of the store they protect, and billboards will occasionally appear in asteroid fields of Corporate Systems.
|}

==All OXPs by Category==

===Sound Sets===
[http://capnhack.com/hosting/oolite/Oolite/OXPs/E5Amigasoundpack01oxp.zip ''Amiga Replament Sounds''] 
[http://oosat.alioth.net/files/CustomSounds.zip ''Custom Sounds''] 
[[Media:halsis.zip|Hal's Hot Sister]] (female cockpit voice) 
[http://www.mediafire.com/file/mm2ekntynom/Hawksound.zip ''Hawksound''] 
[http://capnhack.com/hosting/oolite/Oolite/extra/oosounds2.zip ''Murgh's Replacement Sounds''] 
[http://capnhack.com/hosting/oolite/Oolite/extra/oosounds.zip ''Wiggy's Replacement Sounds] 
[http://capnhack.com/hosting/oolite/Oolite/extra/oosounds3.zip ''Xaotik's Replacement Sounds''] (= [[Media:MildAudio.oxp.zip|MildAudio]]) 
[http://www.box.net/shared/edl1p4lm3o ''Combined Murgh, Wiggy & Xaotik's sounds''] (Needs oolite 1.73+)

===Alternative HUDs===
[http://capnhack.com/hosting/oolite/Oolite/pLists/hud.plist ''Compact HUD''] 
[http://www.jblythe.f9.co.uk/Deepspace/Download/DeepspaceHUD_OXP.zip ''Deepspace HUD''] 
[http://sancho.dk/oolite/Dr_HUD_Cmk3.zip Dr HUD Cobra Mk.III version], [http://sancho.dk/oolite/Dr_HUD.zip Custom version] 
[http://oosat.alioth.net/files/FighterHud.zip ''Fighter HUD''] 
[http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip ''G-HUD Mk2''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/kleptohud.oxp.zip ''Klepto-HUD''] 
[http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip ''Medusa HUD''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/megawalnutdash.oxp.zip ''Mega-Walnut Dashboard''] 
[http://oosat.alioth.net/files/MilHUDv2.zip ''Milspec HUD v2''] (1.65-1.72) |
[http://www.box.net/shared/hczsm8gyi0 ''Milspec HUD v3''] (for 1.73 onwards) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip ''NG HUD''] 
[http://wiki.alioth.net/images/d/d9/TrekHud.zip ''Trek HUD''] 
[[HUD images here]]

===Dockable Objects===
[[Anarchies OXP|Anarchies]] 
[[Aquatics_OXP|Aquatics]] 
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[[Baakili_Far_Trader|Baakili Far Trader]] 
[[Black_Monk_Monastary|Bank of the Black Monks]] 
[[BuoyRepair|BuoyRepair1.02.5]] - Updated (7/10/2009) 
[[Deep Space Dredger|Deep Space Dredger]] 
[http://www.mediafire.com/?dnzltr0cit5 ''Free Trade Zone''] 
[[Fuel_Station_OXP|Fuel Station]] 
[[Globe_station|Globestation2.0]] (Updated 22/10/2009) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/GrittyCoriolis.oxp.zip ''Gritty Coriolis''] 
[[HoOpy Casino]] 
[[Lave_Academy_OXP|Lave Academy]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/gwxstations.oxp.zip ''Military Station''] 
[[Planetfall_OXP|Planetfall]] 
[[Random Hits OXP|Random Hits]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/tori.zip ''Torus Station''] 
[http://oosat.alioth.net/files/Trans-Hab.zip ''Trans-Hab Station''] 
[http://www.box.net/shared/eil0djqhca ''Trade Outpost v1.1''] 
[http://oosat.alioth.net/files/Taranis.zip ''Taranis Corporation HQ''] 
[[P.A. Groove Stations OXP]] 
[[Your Ad Here!]] 
More information on the Station images appearing in Oolite can be found [[Oolite Stations|here]].

[[Dockable Object images here]]

===Customisations by Government (or Tech Level)===
[[Anarchies OXP|Anarchies]] 
[[BuoyRepair|BuoyRepair1.02.5]] 
[[Commies|Commies]] 
[[DeepSpacePirates|DeepSpacePirates]] 
[http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Dictators''] 
[[Feudal_States|The Feudal States]] 
[[Random Hits OXP|Random Hits]] 
[[Snoopers|Snoopers2.0]] (Updated 05/02/2010) 

===Other System Objects===
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[http://oosat.alioth.net/files/Diso.zip ''Diso''] 
[[Fuel_Station_OXP|Fuel Station]] 
[http://www.mediafire.com/?zahdnac0tj1 ''Lave v1.70''] 
[[Lave_Academy_OXP|Lave Academy]] 
[[Pirate Coves OXP|Pirate Coves]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip ''Pirate Traps''] 
[http://www.box.net/shared/b2tic3tjsk#1:3775170:31020120 ''Planets''] 
[[RingPod.oxp|Racing Rings]] 
[[Ring_Racer_OXP|Ring Racer]] 
[http://www.wagar.org.uk/downloads/software/oolite/Tianve1.3.zip''Tianve''] 
[http://oosat.alioth.net/files/TGY.zip ''Tionisla Orbital Graveyard] 
[[Traffic_Control_OXP|Traffic Control]] 
[[Your Ad Here!]] 

===Missions===
[[Aquatics_OXP|Aquatics]] 
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[[Asteroid_Storm|Asteroid Storm 1.52]] 
[[BlackjacksBullion_OXP|Blackjacks Bullion]] 
[[Cataclysm_OXP|Cataclysm]] 
[[Deposed_OXP|Deposed 1.3.4]] 
[[Ionics_OXP|Ionics v.1.2.3]] 
[[Lave_Academy_OXP|Lave Academy]] 
[[Localhero OXP|Localhero v1.05]]  (Updated 27.04.2008) 
[[LongWay_OXP|Long Way Around 1.1]] 
[[Lovecats.oxp|Lovecats 1.2]] 
[[Military_Fiasco|Military Fiasco V2.3]] 
[[Oo-Haul]] 
[[Random Hits OXP|Random Hits]] 
[[Media:BlackBaron1.70.zip| ''Scourge of the Black Baron v1.70'']] 
[[Spy_Hunter_OXP|Spy Hunter]] 
[[Taranis_OXP|Taranis Corporation HQ]] 
[[Thargoid_Wars|Thargoid Wars V4.4 (Updated)]] 
[[Trident_Down|Trident Down]] 
[[UPS_Courier|U.P.S. Courier]] 
[[Vector_OXP|Vector1.3]]  (Updated 31.08.2009) 

More information on the numerous Oolite Missions can be found [[Oolite Missions|here]].

===Ship Systems===
[[Anarchies OXP|Anarchies]] 
[[AMS_OXP|Anti-Missile System]] 
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[[Captured_Thargons_OXP|Captured Thargons]] 
[[Drones_OXP|Drones]] 
[http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon] 
[http://oosat.alioth.net/files/External%20Views.zip ''External Views''] 
[[Energy_Equipment_OXP|Energy Equipment]] 
[[Fuel Tank|Fuel Tank]] 
[[Hired_Guns_OXP|Hired Guns]] 
[[Hyperradio_js_OXP|Hyperradio v1.17]]  (Updated 11/02/2010) 
[[Killit_OXP|''Killit™'' insta-death super weapons]] 
[[Missile Analyser|Missile Analyser]] 
[[Misjump Analyser|Misjump Analyser]] 
[[Missiles and Bombs|Missiles and Bombs]] 
[[Missile_Rack_OXP|Missile Rack]] 
[[Nukes.oxp|Nuclear Torpedos]] 
[[Ore_Processor|Ore Processor]] 
[[Probe_OXP|Probe]] 
[[Repair_Bots_OXP|Repair 'Bots]] 
[[Rock_Hermit_Locator|Rock Hermit Locator]] 
[[Sell equipment OXP|Sell equipment]] 
[[Status Quo Q-bomb OXP|Status Quo Q-bomb]] 
[[Target_Autolock_OXP|Target Autolock]] 
[[Target Reticle|Target Reticle]] 
[[Welcome_Mat_OXP|Welcome Mat]] 

===Ships and Ship Variants===
See below for ship names and stats. 

[[Aegidian's_Specials|Aegidian's Specials]] 
[[Aegidian's_X-Ships|Aegidian's X-Ships]] 
[http://uploading.com/files/CTQ4YDB4/Blitzspear%20Clan.rar.html''Amen Brick's Pirate Clan One: The Blitzspears v1.0 (new 07/08)''] 
[http://www.uploading.com/files/QERHQBAE/Amen_Bricks_Megaships.oxp.zip.html''Amen Brick's Megaships v1.1 (new 07/08)''] 
[[Anarchies OXP|Anarchies]] 
[http://oosat.alioth.net/files/aphidv2.oxp_.zip ''Aphid Escort Service''] 
[[Aquatics_OXP|Aquatics]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/att1.zip ''Armoured Transport Type 1''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/bandersnatch.zip ''Bandersnatch''] 
[[Baakili_Far_Trader|Baakili Far Trader]] 
[[Behemoth]] 
''[http://www.box.net/shared/nv87fgfyf2 Behemoths - Shadered (By ADCK)]''(Includes shaders which require Oolite 1.69 or later) 
[[BigShips_OXP|Big Ships]] 
[[Media:BoomslangWIP.zip|''Boomslang'']] 
''[http://www.box.net/shared/sxcsfa47hf Bulk Haulers (By ADCK)]''(Requires [[BigShips_OXP|Big Ships]] and Includes shaders which require Oolite 1.69 or later) 
[[Caduceus]] 
[http://oosat.alioth.net/files/seosu.zip ''Capisastra''] 
[http://oosat.alioth.net/files/clearskies.oxp_.zip ''Clear Skies''] 
[http://oosat.alioth.net/files/ChoppedCobra.zip ''Cobra 3.5 (chopped Cobra)''] 
[[Cobra_Clipper_SAR|Cobra Clipper SAR]] 
[http://oosat.alioth.net/files/cobra3njx.zip ''Cobra Mk.III Njx''] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Condor''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/custpaint1.zip ''Custom Paint Jobs''] 
[http://oosat.alioth.net/files/dwcobra3HiRes.zip ''Dark Wheel Cobra''] - ([http://oosat.alioth.net/files/dwcobra3.zip alternative lo-end version]) 
[[DeepSpacePirates|DeepSpacePirates]] 
[[Deepspace_Ships|Deepspace Ships]] 
[[Dragon|Dragon Assault Craft (Updated 9/8/08)]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/eagle2.zip ''Eagle Mk.II''] 
''[http://www.box.net/shared/xkltqit3oj Eagles Mk's I to IV (by ADCK)]'' (Includes shaders which require Oolite 1.69 or later)
 
[http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon] 
[http://www.arcadia-digital.net/steve/Oolite/Ships/Executive%20SpaceWays%20v2.2.zip ''Executive Spaceways''] 
[[Far_Arm_ships|Far Arm ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/farstar.oxp.zip ''Far Star''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/ferdelance_ng.oxp.zip ''Fer de Lance NG''] 
[http://oosat.alioth.net/files/ferdepai.oxp_.zip ''Ferdepai''] 
[http://oosat.alioth.net/files/Firewasp.zip ''Firewasp''] 
[[Flying Dutchman OXP|Flying Dutchman]] 
[[Freaky Thargoids OXP|Freaky Thargoids]] ([[shaders in Oolite|shader]] example, requires Oolite 1.69 or later) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/fsr.zip ''Frog Space Rickshaw''] 
[[Galactic_Navy_OXP|Galactic Navy]] 
[[Generation_Ships_OXP|Generation Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/greekshipset1.zip ''Greek Ships''] 
[[Griff_ArcElite|Griff ArcElite Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/griffin2.oxp.zip ''Griffin Mk.II] 
[[Griff_Krait|Griff Krait]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/boyracers.zip ''Hatchling Boyracers''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/Herald.zip ''Herald''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/tugs.zip ''Hognose Tugships''] 
[http://www.mediafire.com/?2vgjwpj6xdy ''Hotrods v0.52c''], [http://www.box.net/shared/j2r6frlvq1 ''Hotrods v0.52d''] 
[http://wiki.alioth.net/index.php/Icarus_%28Oolite%29 ''Icarus''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/illicit_unlock.oxp.zip ''Illicit Unlock''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/impcourier.zip ''Imperial Courier''] 
[[Interstellar help OXP|Interstellar Help]] 
[[Ixian_Ships|Ixian Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/jabberwocky.zip ''Jabberwocky''] 
[http://capnhack.com/hosting/oolite/dropbox/kestrel_falcon1_71_0.zip ''Kestrel&Falcon v1.71.0''] 
[http://www.crimsonforge.co.uk/cloister/kirin.zip ''Kirin''] 
[http://sancho.dk/oolite/lane_legal.zip ''Lane Legal Racers''] 
[[Media:Llama.zip|''Llama'']] 
[http://oosat.alioth.net/files/Longshot.zip ''Longshot''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/mPakRedux.zip ''M-Pack (rusties)''] 
[http://oosat.alioth.net/files/manta.oxp_.zip ''Manta''] 
[http://oosat.alioth.net/files/marett_vol1.zip ''Marett Space Corporation''] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Merlin''] 
[http://sancho.dk/oolite/missionaries.zip ''Missionaries v1.1''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/monument.zip ''Monument''] 
[http://capnhack.com/hosting/oolite/dropbox/morrigan101.zip ''Morrigan''] 
[[Murgh_Xships OXP|Murgh's X-Ships]] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Navy Starships''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/newships.oxp.zip ''New Ships''] 
[[Neolite Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/nuvipers.zip ''Nu Vipers''] 
[[Old Ships]] 
[[Orb]] 
[http://oosat.alioth.net/files/outrider.zip ''Outrider''] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Pallas''] 
[http://oosat.alioth.net/files/Pelamis.zip ''Pelamis''] 
[[Personalities OXP|Personalities]] 
[http://oosat.alioth.net/files/Phoenix.zip ''Phoenix''] 
[http://oosat.alioth.net/files/PTI.zip ''Pteradyne Technologies Ships''] - ([http://oosat.alioth.net/files/PTI_bugfix11.zip ''bug fix'']) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/pcc.oxp.zip ''Python Class Cruiser] 
''[[Media:Python Class Cruiser.oxp.zip|Python Class Cruiser version 2.6]]'' (Includes shaders which require Oolite 1.69 or later) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/racers.oxp.zip ''Racers''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/RoC.oxp.zip ''Remorse of Conscience''] 
[http://oosat.alioth.net/files/RenegadesV3.zip ''Renegade Pirates''] (Wait until you have an Iron Ass before installing this OXP!) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/RVandGS.zip ''Renegade Viper + Grass Snake] 
[http://oosat.alioth.net/files/Saleza%20Aeronautics%20v2.0.zip ''Saleza Aeronautics''] 
[http://oosat.alioth.net/files/santa_v2.zip ''Santa''] - ([http://oosat.alioth.net/files/Santa.zip alternative lo-end version]) 
[[Second_Wave_OXP|Second Wave]] 
[http://oosat.alioth.net/files/s-ships1.zip ''Selezen's S-Ships''] 
[[Shady Cobra OXP|Shady Cobra]] 
[http://oosat.alioth.net/files/All-Stars_0.zip ''Skrounk All-Stars Limited''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/snark.zip ''Snark''] 
[http://oosat.alioth.net/files/Spearhead.zip ''Spearhead Interceptor Mk.I''] 
[http://oosat.alioth.net/files/StarWars.zip ''Star Wars Ships''] 
[http://www.box.net/shared/static/9cwp2jk84o.zip ''Sung's Detailed Texture''s] 
[http://www.box.net/shared/535vddgddh ''Sung's Detailed Textures (Shader Version)''] (Includes shaders which require Oolite 1.69 or later)
 
[http://sancho.dk/oolite/sunskimmers.zip ''Sunskimmers''] 
[[SuperCobra|Super Cobra]] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Swift''] 
[http://sancho.dk/oolite/Shield-tail.zip ''Teretrurus Mk.I''] 
[http://oosat.alioth.net/files/Terrapin.zip ''Terrapin Trader''] 
[http://oosat.alioth.net/files/Tescoura.zip ''Tesoura''] 
[http://oosat.alioth.net/files/Thargoid_CarrierV1.zip ''Thargoid Carrier''] 
[[Thargorn_Threat_oxp|Thargorn Threat v1.3 (updated)]] 
[http://oosat.alioth.net/files/Tiger.zip ''Tiger''] 
[[Transports|Transports]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/tugs.zip ''Tugs''] 
[http://oosat.alioth.net/files/UrutaMK3.zip ''Urutu Mk.III''] 
[http://oosat.alioth.net/files/UrutaMK4.zip ''Urutu Mk.IV''] 
[http://www.purgatori.net/Isis_Interstellar.htm ''Vampire''] 
[[Velocity_OXP|Velocity]] 
[[Vector_OXP|Vector1.3]]  (Updated 31.08.2009) 
[[Venom|Venom]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/weeviloid2.zip ''Weeviloid''] 
[http://www.box.net/shared/vhho2av2az ''Wolf Mk.II v3.3] 
[http://wiki.alioth.net/images/0/06/Wolfs_variants.zip ''Wolfwood's Variants v1.5''] 

[[Ship data table|Ship data table here]] 
More information on the Ships appearing in Oolite can be found [[Oolite Ships|here]].

[[Ships and Ship Variant images here]]

=== Other objects and miscellaneous eyecandy ===
[[Asteroid_Storm|Asteroid Storm]] 
[[Cargo_Wreck_Teaser_OXP|Cargo & Wrecks v1.4]] 
[[Famous Planets OXP|Famous_planets_oxp and FP Expansion packs]] 
[[Famous_Planets_2.0.OXP]] 
[[Media:Farsun1.03.zip|''Farsun v1.03'']] 
[[Hyperradio_js_OXP|Hyperradio v1.17]]  (Updated 11/02/2010) 
[http://marc-schaffer.ch/data/OoliteGerman_V0.3.zip Oolite German v0.3] 
[[Media:OoliteItaliano_v1.3.zip|''Oolite Italiano v1.3'']] 
[http://www.box.net/shared/ch3lsepk9k Oolite Russian v1.0] 
[http://www.box.net/shared/rrlm77ztzm Oolite en français] 
[[Media:Orbits.zip|''Orbits'']] 
[[OXPConfig|OXPConfig1.08]]  (Updated 04/09/2009) 
[[Pods_OXP|Pods]] 
[[Pods_OXP#UPS_PODS|Pods UPS Pack]] 
[[Snoopers|Snoopers2.0]] (Updated 05/02/2010) 
[[RegistrationID|Registration ID ]]

== Installing an OXP ==
Unzip the OXP and place it in the folder named '''AddOns'''. Sometimes the zipped files contain several folders, make sure you only copy the folder -or file for Macintoshes- ending with '''.oxp''' into the AddOns folder. This folder is found in different locations, depending on the platform:

=== Mac OS X ===
Found in the folder that contains the Oolite application.

'''Troubleshooting:''' If you get an error saying "The item could not be moved because "AddOns" cannot be modified", that can happen if you weren't the user that installed Oolite.
The solution is to put the OXP's of your choice in '''~/Library/Application Support/Oolite/AddOns/''' instead (you may need to create this folder).
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 & Permissions pane and check that it says You Can: Read & Write.

=== Linux ===
The OXP directory can be found in '''$HOME/.Oolite/AddOns.''' for all current versions of OOlite

=== Windows ===
If the installable package was used (post Jan 06) then the AddOns folder needs to be created in '''C:\Programs Files\Oolite'''. Note that this applies if the default installation location is used. If the install location is changed then use the path to the Oolite folder that corresponds to your installation.
If the GNUStep dedicated versions (pre-Jan 2006) is used, then the AddOns folder must be created in the oolite.app folder.

After unzipping the file, make sure that it is ''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 item with the '''.oxp''' extension into the AddOns folder.

== Caveats ==
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's not, Oolite will give you an error instead of trying to load the commander.

== Creating an OXP ==
It is intended to be easy to create expansion packs. With a few simple [[List_of_software|tools]], a player can make small or big changes, and customize the gaming experience.

* [[OXP howto|How to make OXPs]]

[[Category:Oolite]]
[[Category:Oolite expansion packs]]
[[Category:Factual]]

RegistrationID

2010-02-28T19:28:44Z

Frame:

RegistrationID

2010-02-28T19:28:19Z

Frame:

== '''Registration ID..''' ==
[[File:RegistrationOXPimage1.jpg]]
In an Effort to diminishing Piracy Gal Cop has recently started Demanding ID
tags on every ship in the galaxy. existing non ID ships, will acquire an ID
upon change of ownership.. For now this only applies to all the popular
brands of ships, those we have come to know since the dawn of interstellar space travel.

'''Protests'''

A lot of back yard ship factories have protested against this and refuses to
put ID tags on their custom or upgraded ships until legislation upon the matter
as been cleared about whether or not this violates the rights of the individual
trader..

'''flawed legislation'''

Independant Space Traders Union also known as ITU, has appealed Gal Cops current
practice as follows

''"it is obvious that the police now, as a matter of routine, demand the production of registration indemnity ID Tags whenever they stop or interrogate a spacer for whatever cause. Of course, if they are looking for a stolen ship or have reason to believe that a particular spacer is engaged in committing a crime, that is one thing, but to demand an ID tag from all and sundry, for instance, from a lady who may leave her mining ship in an asteroid field longer than her license allows her to, or some trivial matter of that sort, is wholly unreasonable. This Act was passed for security purposes, and not for the purposes for which, apparently, it is now sought to be used."
''

''' Decision Pending '''

The Board of Space Vessel Affairs(BSVA) have ruled that current practices must be followed until a decision has been made.. however the supplier of the photo chromatic paint embedded in the alloys of the ID tagged vessels, cannot be removed without removing the metal entirely... and changing the assembly lines again could lead to law suits against GAL COP and even GAL CORP, from the union of space vessel suppliers known as SVS.

'''What the Wise Men Say'''

Experts agree that the ID practice is here to stay: however those shops that exist on the fringe of law, should still be able to get away with not painting IDs on their ships... subsequently Prices on NON id ships, are higher than ID ships, and also acts as an additional reason, not to embed ID paint into the alloy of your Vessel.

These shops that are largely unknown to Gal Cop, also risks getting inspections from Gal Cop, if they registrar with Gal Cop to get an alloted series of ID tag numbers.

The Experts also agree that eventually even these will be forced to accept, they do however also agree that pirates will remove the ID tags soon, when some back yard ship repair shop starts removing the metal or the paint from the duranium alloys at an extremly high cost ofcourse...

finally ID tags may allow for Pirates to easier stalk and find their prey..

[http://www.box.net/shared/l0yu9ihdl2 Download version 0.12 here]
[[File:Example.jpg]]

RegistrationID

2010-02-28T19:27:58Z

Frame:

== '''Registration ID..''' ==

In an Effort to diminishing Piracy Gal Cop has recently started Demanding ID
tags on every ship in the galaxy. existing non ID ships, will acquire an ID
upon change of ownership.. For now this only applies to all the popular
brands of ships, those we have come to know since the dawn of interstellar space travel.

'''Protests'''

A lot of back yard ship factories have protested against this and refuses to
put ID tags on their custom or upgraded ships until legislation upon the matter
as been cleared about whether or not this violates the rights of the individual
trader..

'''flawed legislation'''

Independant Space Traders Union also known as ITU, has appealed Gal Cops current
practice as follows

''"it is obvious that the police now, as a matter of routine, demand the production of registration indemnity ID Tags whenever they stop or interrogate a spacer for whatever cause. Of course, if they are looking for a stolen ship or have reason to believe that a particular spacer is engaged in committing a crime, that is one thing, but to demand an ID tag from all and sundry, for instance, from a lady who may leave her mining ship in an asteroid field longer than her license allows her to, or some trivial matter of that sort, is wholly unreasonable. This Act was passed for security purposes, and not for the purposes for which, apparently, it is now sought to be used."
''

''' Decision Pending '''

The Board of Space Vessel Affairs(BSVA) have ruled that current practices must be followed until a decision has been made.. however the supplier of the photo chromatic paint embedded in the alloys of the ID tagged vessels, cannot be removed without removing the metal entirely... and changing the assembly lines again could lead to law suits against GAL COP and even GAL CORP, from the union of space vessel suppliers known as SVS.

'''What the Wise Men Say'''

Experts agree that the ID practice is here to stay: however those shops that exist on the fringe of law, should still be able to get away with not painting IDs on their ships... subsequently Prices on NON id ships, are higher than ID ships, and also acts as an additional reason, not to embed ID paint into the alloy of your Vessel.

These shops that are largely unknown to Gal Cop, also risks getting inspections from Gal Cop, if they registrar with Gal Cop to get an alloted series of ID tag numbers.

The Experts also agree that eventually even these will be forced to accept, they do however also agree that pirates will remove the ID tags soon, when some back yard ship repair shop starts removing the metal or the paint from the duranium alloys at an extremly high cost ofcourse...

finally ID tags may allow for Pirates to easier stalk and find their prey..

[http://www.box.net/shared/l0yu9ihdl2 Download version 0.12 here]

RegistrationID

2010-02-28T19:27:08Z

Frame:

== '''Registration ID..''' ==
[[File:120px-RegistrationOXPimage1.jpg]]

In an Effort to diminishing Piracy Gal Cop has recently started Demanding ID
tags on every ship in the galaxy. existing non ID ships, will acquire an ID
upon change of ownership.. For now this only applies to all the popular
brands of ships, those we have come to know since the dawn of interstellar space travel.

'''Protests'''

A lot of back yard ship factories have protested against this and refuses to
put ID tags on their custom or upgraded ships until legislation upon the matter
as been cleared about whether or not this violates the rights of the individual
trader..

'''flawed legislation'''

Independant Space Traders Union also known as ITU, has appealed Gal Cops current
practice as follows

''"it is obvious that the police now, as a matter of routine, demand the production of registration indemnity ID Tags whenever they stop or interrogate a spacer for whatever cause. Of course, if they are looking for a stolen ship or have reason to believe that a particular spacer is engaged in committing a crime, that is one thing, but to demand an ID tag from all and sundry, for instance, from a lady who may leave her mining ship in an asteroid field longer than her license allows her to, or some trivial matter of that sort, is wholly unreasonable. This Act was passed for security purposes, and not for the purposes for which, apparently, it is now sought to be used."
''

''' Decision Pending '''

The Board of Space Vessel Affairs(BSVA) have ruled that current practices must be followed until a decision has been made.. however the supplier of the photo chromatic paint embedded in the alloys of the ID tagged vessels, cannot be removed without removing the metal entirely... and changing the assembly lines again could lead to law suits against GAL COP and even GAL CORP, from the union of space vessel suppliers known as SVS.

'''What the Wise Men Say'''

Experts agree that the ID practice is here to stay: however those shops that exist on the fringe of law, should still be able to get away with not painting IDs on their ships... subsequently Prices on NON id ships, are higher than ID ships, and also acts as an additional reason, not to embed ID paint into the alloy of your Vessel.

These shops that are largely unknown to Gal Cop, also risks getting inspections from Gal Cop, if they registrar with Gal Cop to get an alloted series of ID tag numbers.

The Experts also agree that eventually even these will be forced to accept, they do however also agree that pirates will remove the ID tags soon, when some back yard ship repair shop starts removing the metal or the paint from the duranium alloys at an extremly high cost ofcourse...

finally ID tags may allow for Pirates to easier stalk and find their prey..

[http://www.box.net/shared/l0yu9ihdl2 Download version 0.12 here]

File:RegistrationOXPimage1.jpg

2010-02-28T19:25:16Z

Frame: Header for registration OXP image

Header for registration OXP image

RegistrationID

2010-02-28T19:23:53Z

Frame:

RegistrationID

2010-02-28T19:15:05Z

Frame:

== '''Registration ID..''' ==

In an Effort to diminishing Piracy Gal Cop has recently started Demanding ID
tags on every ship in the galaxy. existing non ID ships, will acquire an ID
upon change of ownership.. For now this only applies to all the popular
brands of ships, those we have come to know since the dawn of interstellar space travel.

'''Protests'''

A lot of back yard ship factories have protested against this and refuses to
put ID tags on their custom or upgraded ships until legislation upon the matter
as been cleared about whether or not this violates the rights of the individual
trader..

'''flawed legislation'''

Independant Space Traders Union also known as ITU, has appealed Gal Cops current
practice as follows

"it is obvious that the police now, as a matter of routine, demand the production of registration indemnity ID Tags whenever they stop or interrogate a spacer for whatever cause. Of course, if they are looking for a stolen ship or have reason to believe that a particular spacer is engaged in committing a crime, that is one thing, but to demand an ID tag from all and sundry, for instance, from a lady who may leave her mining ship in an asteroid field longer than her license allows her to, or some trivial matter of that sort, is wholly unreasonable. This Act was passed for security purposes, and not for the purposes for which, apparently, it is now sought to be used."

''' Decision Pending '''
The Board of Space Vessel Affairs(BSVA) have ruled that current practices must be followed until a decision has been made.. however the supplier of the photo chromatic paint embedded in the alloys of the ID tagged vessels, cannot be removed without removing the metal entirely... and changing the assembly lines again could lead to law suits against GAL COP and even GAL CORP.

Experts agree that the ID practice is here to stay: however those shops that exist on the fringe of law, should still be able to get away with not painting IDs on their ships... subsequently Prices on NON id ships, are higher than ID ships..

The Experts also agree that eventually even these will be forced to accept

[http://www.box.net/shared/l0yu9ihdl2 Download version 0.12 here]

RegistrationID

2010-02-28T18:46:25Z

Frame:

== '''Registration ID..''' ==

[http://www.box.net/shared/l0yu9ihdl2 Download here]

RegistrationID

2010-02-28T18:46:15Z

Frame: Created page with '== '''Registration ID..''' == [IMG]http://i304.photobucket.com/albums/nn180/Frame_2/Registration-1.jpg[/IMG] [http://www.box.net/shared/l0yu9ihdl2 Download here]'

== '''Registration ID..''' ==
[IMG]http://i304.photobucket.com/albums/nn180/Frame_2/Registration-1.jpg[/IMG]
[http://www.box.net/shared/l0yu9ihdl2 Download here]

Oolite JavaScript Reference: Ship

2010-02-23T21:35:12Z

Frame:

'''Prototype:''' <code>[[Oolite JavaScript Reference: Entity|Entity]]</code> 
'''Subtypes:''' <code>[[Oolite JavaScript Reference: Station|Station]]</code>, <code>[[Oolite JavaScript Reference: PlayerShip|PlayerShip]]</code>

{{Oolite-class-added|1.70}}

The '''<code>Ship</code>''' class is an <code>[[Oolite JavaScript Reference: Entity|Entity]]</code> representing a ship, station, missile, cargo pod or other flying item – anything that can be specified in [[shipdata.plist]]. A <code>Ship</code> has all the properties and methods of a <code>Entity</code>, and several others.

<code>[[Oolite JavaScript Reference: Station|Station]]</code>s and the <code>[[Oolite JavaScript Reference: Player|Player]]</code> are types of ship. Note that these more specific types have additional properties and methods.

== Properties ==
=== <code>aftWeapon</code> ===
{{Oolite-prop-added|1.74}}
'''aftWeapon''' : EquipmentType(read-only)
The currently equipped aft weapon, or null.
Identical to the equivalent [[Oolite JavaScript Reference: PlayerShip#aftWeapon|PlayerShip]] property.

'''See also''': <code>[[#forwardWeapon|forwardWeapon]]</code>

=== <code>AI</code> ===
'''AI''' : String (read-only)
The name of the ship’s current AI. (See also: <code>[[#AIState|AIState]]</code>, <code>[[#setAI|setAI()]]</code>, <code>[[#switchAI|switchAI()]]</code>, <code>[[#exitAI|exitAI()]]</code>)

=== <code>AIState</code> ===
'''AIState''' : String (read/write, read-only for player)
The ship’s AI’s current state. (See also: <code>[[#AI|AI]]</code>, <code>[[#reactToAIMessage|reactToAIMessage()]]</code>, <code>[[#hasSuspendedAI|hasSuspendedAI]]</code>)

=== <code>availableCargoSpace (deprecated)</code> ===
{{Oolite-prop-added|1.72}}
'''availableCargoSpace''': Number (read-only integer)
The ship’s free cargo space, in tons. Deprecated in favour of cargoSpaceAvailable.

=== <code>beaconCode</code> ===
'''beaconCode''' : String (read-only)
If the ship is a beacon, an identifying string. The first character is used for identification on the [[Advanced Space Compass]]. For non-beacons, this property is <code>null</code>. (See also: <code>[[#isBeacon|isBeacon]]</code>)

=== <code>bounty</code> ===
'''bounty''' : Number (read/write integer)
The bounty on the ship. In the case of the player, it is halved at each witchspace jump. 
It is actually the legal status of the ship that is shown here and not the bounty. For all ships both are the same but for anything with scan class Thargoid the legal status is only based on the ships mass and has no relation to its defined bounty.

=== <code>cargoCapacity (deprecated)</code> ===
'''cargoCapacity''': Number (read-only integer)
The ship’s cargo capacity, in tons. Name introduced with version 1.72. Old name was maxCargo. Deprecated in favour of '''cargoSpaceCapacity'''

=== <code>cargoSpaceAvailable</code> ===
{{Oolite-prop-added|1.74}}
'''cargoSpaceAvailable''' : Number (read-only integer)
The ship’s available cargo space, in tons. Name introduced with version 1.74. Replaces availableCargoSpace.

=== <code>cargoSpaceCapacity</code> ===
{{Oolite-prop-added|1.74}}
'''cargoSpaceCapacity''' : Number (read-only integer)
The ship’s cargo capacity, in tons. Name introduced with version 1.74. Old names were maxCargo, cargoCapacity.

=== <code>cargoSpaceUsed</code> ===
{{Oolite-prop-added|1.72}}
'''cargoSpaceUsed''' : Number (read-only integer)
The ship’s current cargo, in tons. Any ship carrying less than

=== <code>contracts</code> ===
{{Oolite-prop-added|1.74}}
'''contracts''' : Array (read-only NSDictionary)
The ship’s contracts. (For now only available for the player). Each contract contains the entries: <code>commodity: string, quantity: integer, description: string, start: integer, destination: integer, startName: string, destinationName: string, eta: integer, etaDescription: string, fee: Integer, premium: Integer</code> 

For example, the information of the first contract can be obtained by:
player.ship.contracts[0].commodity
player.ship.contracts[0].quantity
player.ship.contracts[0].description
player.ship.contracts[0].start
player.ship.contracts[0].destination
player.ship.contracts[0].startName
player.ship.contracts[0].destinationName
player.ship.contracts[0].eta // Estimated Time of Arrival.
player.ship.contracts[0].etaDescription
player.ship.contracts[0].fee // The profit of the contract, paid out on successful delivery.
player.ship.contracts[0].premium // The sum paid to obtain the goods and paid back on successful delivery.

start and destination contain system ID numbers for planets in the current galaxy chart, eta is in clock seconds, fee is the amount that the player will receive when delivering this contract, and premium was the amount the player had to pay to secure this contract.

=== <code>desiredSpeed</code> ===
{{Oolite-prop-added|1.72}}
'''desiredSpeed''' : Number (read/write nonnegative, read-only for player)
The speed the AI will attempt to maintain. The AI core and AI script may change this from time to time. The corresponding AI method is <code>setSpeedFactorTo:</code>; a speed factor of 1.0 corresponds to a <code>desiredSpeed</code> equal to <code>[[#maxSpeed|maxSpeed]]</code>.

=== <code>displayName</code> ===
'''displayName''' : String (read/write, read-only for player)
The name of the ship as seen by the player. By default it is the same as name(<code>name</code> key in [[shipdata.plist]]). This property is changed from '''shipDisplayName''' in 1.72

=== <code>entityPersonality</code> ===
'''entityPersonality''' : Number (read-only integer)
A random number in the range 0..32767 which is generated when the ship is created. Equivalent to the <code>entityPersonalityInt</code> [[Shaders in Oolite: uniforms#Ship|uniform binding]].

=== <code>equipment</code> ===
{{Oolite-prop-added|1.74}}
'''equipment''' : Array of [[Oolite_JavaScript_Reference:_EquipmentInfo|EquipmentInfo ]] (read-only)
The equipment a ship is carrying.

=== <code>escorts</code> ===
'''escorts''' : Array (read-only array of [[Oolite JavaScript Reference: Entity|Entity]]s)
The ship’s deployed escorts.

=== <code>escortGroup</code> ===
{{Oolite-prop-added|1.73}}
'''escortGroup''' : [[Oolite JavaScript Reference: ShipGroup|ShipGroup]] (Class added with Oolite 1.73)
The ship’s deployed escorts.

=== <code>forwardWeapon</code> ===
{{Oolite-prop-added|1.74}}
'''forwardWeapon''' : EquipmentType(read-only)
Identical to the equivalent [[Oolite JavaScript Reference: PlayerShip#forwardWeapon|PlayerShip]] property.

'''See also''': <code>[[#aftWeapon|aftWeapon]]</code>

=== <code>fuel</code> ===
'''fuel''' : Number (read/write)
The ship’s current fuel capacity, in LY. The game will limit this to the range 0..7, and round it off to the nearest tenth. (See also: <code>[[Oolite JavaScript Reference: Player#fuelLeakRate|Player.fuelLeakRate]]</code>)

=== <code>group</code> ===
{{Oolite-prop-added|1.73}}
'''group''' : [[Oolite JavaScript Reference: ShipGroup|ShipGroup]] (Class added with Oolite 1.73)
Contains ship’s belonging to each other. Added pirate groups are an example or a station with its launched defenders. 
A group is an individual object that can be linked to several ships belonging to the same group. When a ship dies and the group object has still owners, the group stays active as object. The group is only removed from memory after the last ship that had this group as property is removed. 
Adding a group to a ship does not automatic puts that ship in the group. For that to happen you need also use the addShip() command.
e.g.
this.ship.group = new ShipGroup();
this.ship.group.addShip(this.ship);

=== <code><del>groupID</del></code> ===
Removed in 1.73. Use <code>[[#group|group]]</code> instead.

=== <code>hasHostileTarget</code> ===
'''hasHostileTarget''' : Boolean (read-only)
<code>true</code> if the ship’s AI is trying to kill something, <code>false</code> otherwise. Always <code>false</code> for the player.

=== <code>hasSuspendedAI</code> ===
'''hasSuspendedAI''' : Boolean (read-only)
<code>true</code> if the ship has suspended AIs, <code>false</code> otherwise.

=== <code>heatInsulation</code> ===
'''heatInsulation''' : Number (read/write)
The ship’s heat insulation factor. 1.0 is normal, higher values mean more resistance to heat.

=== <code>isBeacon</code> ===
'''isBeacon''' : Boolean (read-only)
<code>true</code> if the ship is a beacon (i.e., can show up on the [[Advanced Space Compass]] with a character indicating its identity), <code>false</code> otherwise. (See also: <code>[[#beaconCode|beaconCode]]</code>)

=== <code>isCloaked</code> ===
'''isCloaked''' : Boolean (read-only)
<code>true</code> if the ship has a cloaking device which is currently active <code>false</code> otherwise. If the ship has a cloaking device and sufficient energy to use it, you can activate it by setting <code>isCloaked</code> to <code>true</code>.

=== <code>isFrangible</code> ===
'''isFrangible''' : Boolean (read-only)
<code>true</code> if the ship is frangible (i.e., its subentities can be destroyed separately from the main ship), <code>false</code> otherwise. (See also: <code>[[#subEntities|subEntities]]</code>)

=== <code>isJamming</code> ===
'''isJamming''' : Boolean (read-only)
<code>true</code> if the ship has a military scanner jammer which is currently active <code>false</code> otherwise.

=== <code>isMine</code> ===
{{Oolite-prop-added|1.73}}
'''isMine''' : Boolean (read-only)
<code>true</code> if the ship is a mine, <code>false</code> otherwise.

=== <code>isMissile</code> ===
{{Oolite-prop-added|1.73}}
'''isMissile''' : Boolean (read-only)
<code>true</code> if the ship is a missile, <code>false</code> otherwise.

=== <code>isPirate</code> ===
'''isPirate''' : Boolean (read-only)
<code>true</code> if the ship is a pirate vessel, <code>false</code> otherwise. Currently equivalent to <code>[[#primaryRole|primaryRole]] == "pirate"</code>.

=== <code>isPirateVictim</code> ===
'''isPirateVictim''' : Boolean (read-only)
<code>true</code> if the ship’s [[#primaryRole|primary role]] is listed in ''pirate-victim-roles.plist'', <code>false</code> otherwise. This is the same test used by the pirate AI to select victims.

=== <code>isPolice</code> ===
'''isPolice''' : Boolean (read-only)
<code>true</code> if the ship is a police vessel, <code>false</code> otherwise. Currently equivalent to <code>[[Oolite JavaScript Reference: Entity#scanClass|scanClass]] == "CLASS_POLICE"</code>.

=== <code>isThargoid</code> ===
'''isThargoid''' : Boolean (read-only)
<code>true</code> if the ship is a Thargoid vessel, <code>false</code> otherwise. Currently equivalent to <code>[[Oolite JavaScript Reference: Entity#scanClass|scanClass]] == "CLASS_THARGOID"</code>.

=== <code>isTrader</code> ===
'''isTrader''' : Boolean (read-only)
<code>true</code> if the ship is a merchant vessel, <code>false</code> otherwise. Currently equivalent to <code>[[#primaryRole|primaryRole]] == "trader" || isPlayer</code>. '''Note:''' <code>[[#isPirateVictim|isPirateVictim]]</code> may be a better choice in many cases.

=== <code>isWeapon</code> ===
{{Oolite-prop-added|1.73}}
'''isWeapon''' : Boolean (read-only)
<code>true</code> if the ship is a weapon, <code>false</code> otherwise. Currently equivalent to <code>[[#isMissile|isMissile]] || [[#isMine|isMine]] </code>, but new categories of weapon could be added in future.

=== <code>lightsActive</code> ===
{{Oolite-prop-added|1.74}}
'''lightsActive''' : Boolean (read-write)
Setting this property to <code>true</code> turns on all the entity’s flashers, and setting it to <code>false</code> turns them off. Setting it sets the <code>lightsActive</code> property for all subentities, but subentities’ setting can also be manipulated separately. In addition to affecting flashers, the value can be used by shaders.

Note: <code>lightsActive</code> is always <code>true</code> when a ship is spawned, although individual flashers may be off because they have <code>initially_on</code> set to false in their ''shipdata.plist'' declarations.

=== <code>maxCargo</code> ===
'''maxCargo''' : Number (read-only integer)
The ship’s cargo capacity. This property is renamed to '''cargoCapacity''' in 1.72.

=== <code>maxSpeed</code> ===
'''maxSpeed''' : Number (read-only)
The ship’s maximum speed under normal power. Note that <code>[[#speed|speed]]</code> may exceed this when [[witch fuel injectors]] or [[hyperspeed]] are in use. (See also: <code>[[#speed|speed]]</code>)

=== <code>maxThrust</code> ===
{{Oolite-prop-added|1.74}}
'''maxThrust''' : Number (read-only)
The ship’s maxThrust. This value is the one defined as thrust in shipdata.plist.

=== <code>missileCapacity</code> ===
{{Oolite-prop-added|1.74}}
'''missileCapacity''' : Number (read-only integer)
The ship’s maximum number of missiles it can carry.

=== <code>missiles</code> ===
{{Oolite-prop-added|1.74}}
'''missiles''' : Array (read-only array of [[Oolite JavaScript Reference: EquipmentInfo|EquipmentInfo's]])
The ship’s loaded missiles.

=== <code>name</code> ===
'''name''' : String (read/write, read-only for player)
The name of the ship type (<code>name</code> key in [[shipdata.plist]]). This property was changed from '''shipDescription''' in 1.72

=== <code>passengerCapacity</code> ===
{{Oolite-prop-added|1.72}}
'''passengerCapacity''' : Number (read-only integer)
The ship’s maximum passenger capacity.

=== <code>passengerCount</code> ===
{{Oolite-prop-added|1.72}}
'''passengerCount''' : Number (read-only integer)
The ship’s current number of passengers.

=== <code>passengers</code> ===
{{Oolite-prop-added|1.74}}
'''passengers''' : Array (read-only NSDictionary)
The ship’s passengers. (For now only available for the player). Each passengers list contains the entries: <code>name: String, start: integer, destination: integer, startName: string, destinationName: string, eta: integer, etaDescription: string, fee: Integer, premium: Integer</code> 
For example, the information of the first contract can be obtained by:
player.ship.passengers[0].name
player.ship.passengers[0].start
player.ship.passengers[0].destination
player.ship.passengers[0].startName
player.ship.passengers[0].destinationName
player.ship.passengers[0].eta
player.ship.passengers[0].etaDescription
player.ship.passengers[0].fee // The final fee, paid out on successful delivery.
player.ship.passengers[0].premium // The advance fee, already paid on acceptance of the contract.

start and destination contain system ID numbers for planets in the current galaxy chart, eta is in clock seconds, fee is the amount that the player will receive when delivering this passenger, and premium shows the amount the player received when the passenger boarded the ship.

=== <code>potentialCollider</code> ===
'''potentialCollider''' : [[Oolite JavaScript Reference: Entity|Entity]] (read-only)
The entity the ship is currently trying not to crash into, if any.

=== <code>primaryRole</code> ===
'''primaryRole''' : String (read/write, read-only for player)
The main role of the ship; the role for which it was created. For instance, if a ship’s ''shipdata.plist'' entry specifies the roles “pirate trader(0.5) escort”, and a ship of that type is spawned to be a trader, its <code>primaryRole</code> is <code>"trader"</code>, its <code>roles</code> is <code>["escort", "pirate", "trader"]</code> and its <code>roleProbabilities</code> is <code> { "escort":1, "pirate":1, "trader":0.5}</code>.

'''See also:''' <code>[[#roles|roles]]</code>, <code>[[#roleProbabilities|roleProbabilities]]</code>.

=== <code>reportAIMessages</code> ===
'''reportAIMessages''' : Boolean (read/write)
Debugging facility: set to <code>true</code> to dump information about AI activity to the log.

=== <code>roleProbabilities</code> ===
'''roles''' : Object (read-only)
The probabilities for each role in <code>[[#roles|roles]]</code>. Example:
this.pirateProb = ship.roleProbabilities["pirate"]
'''See also:''' <code>[[#primaryRole|primaryRole]]</code>, <code>[[#roles|roles]]</code>.

=== <code>roles</code> ===
'''roles''' : Array (read-only array of Strings)
The roles of the ship. This consists of the roles specified in the ship’s ''shipdata.plist'' entry, as well as the <code>[[#primaryRole|primaryRole]]</code> if it is not among those.

'''See also:''' <code>[[#primaryRole|primaryRole]]</code>, <code>[[#roleProbabilities|roleProbabilities]]</code>, <code>[[#hasRole|hasRole()]]</code>.

=== <code>savedCoordinates</code> ===
{{Oolite-prop-added|1.74}}
'''savedCoordinates''' : [[Oolite JavaScript Reference: Vector|Vector]] (read-write)
The savedCoordinates of the ship in system co-ordinates. The savedCoordinates vector is only used by AI scripting to store a coordinate that can be used by other AI commands like <code>setDestinationToCoordinates</code>. It are the same coordinates that are set by the AI command: <code>"setCoordinates: X Y Z"</code>

=== <code>scannerRange</code> ===
'''scannerRange''' : Number (read-only)
The range of the ship’s scanner.

=== <code>script</code> ===
'''script''' : [[Oolite JavaScript Reference: Script|Script]] (read-only)
The ship’s script.

=== <code>scriptInfo</code> ===
'''scriptInfo''' : Object (read-only)
The contents of the <code>script_info</code> key in the ship’s ''[[shipdata.plist]]'' entry, if any. This may be any [[property list]] object, but the reccomended approach is to use a dictionary whose keys have a unique prefix (such as you should be using for file names, ship names etc.). A property list dictionary is converted to a JavaScript object with properties corresponding to the dictionary’s keys. All other property list types used with Oolite have directly corresponding JavaScript types.

=== <code>shipDescription</code> ===
'''shipDescription''' : String (read/write, read-only for player)
The name of the ship type (<code>name</code> key in [[shipdata.plist]]). This property is changed into '''name''' in 1.72

=== <code>shipDisplayName</code> ===
'''shipDisplayName''' : String (read/write, read-only for player)
The name of the ship as seen by the player. By default it is the same as shipDescription(<code>name</code> key in [[shipdata.plist]]). This property is changed into '''displayName''' in 1.72

=== <code>speed</code> ===
'''speed''' : Number (read-only)
The ship’s current speed. (See also: <code>[[#maxSpeed|maxSpeed]]</code>)

=== <code>subEntities</code> ===
'''subEntities''' : Array (read-only array of Ships)
The ships subentities, or <code>null</code> if it has none. Special subentities such as flashers and exhaust plumes are not included. (See also: <code>[[#isFrangible|isFrangible]]</code>)

=== <code>target</code> ===
'''target''' : Ship (read-write)
The ship’s primary target, i.e. the entity it will attempt to shoot at. This value is automatically co-ordinated between a ship and its subentities. 
Starting with 1.74 a current target can be deselected by setting "target = null". (Before defining null resulted in an error)

=== <code>temperature</code> ===
'''temperature''' : Number (read/write)
The ship’s temperature, normalized such that a temperature of 1.0 is the level at which a ship starts taking heat damage.

=== <code>thrust</code> ===
{{Oolite-prop-added|1.74}}
'''thrust''' : Number (read/write (For player read-only))
The ship’s thrust. This value is maximised by maxThrust. This value determines how fast the ship accelerates or decelerates. Speed-change in m/ses per sec.

=== <code>weaponRange</code> ===
'''weaponRange''' : Number (read/write)
The maximum range of the ship’s primary weapon. For the player it is the range of the weapon that fired as last, even when the view direction changed.

=== <code>withinStationAegis</code> ===
'''withinStationAegis''' : Boolean (read-only)
<code>true</code> if the ship is within the aegis of the system’s main station (i.e., no more than 51 200 game metres from the station, or twice scanner range).

== Methods ==
=== <code>abandonShip</code> ===
{{oolite-method-added|1.74}}
function '''abandonShip'''() : Boolean
Returns <code>true</code> when the ship has an escapepod. It will launch all escapeposd on board leaving the ship behind as a empty hulk. (scanClass = CLASS_CARGO). This command does nothing when no escape-pod is present. 
Pressence of an escapepod can be tested with: <code>hasEquipment("EQ_ESCAPE_POD")</code>

=== <code>awardContract</code> ===
{{oolite-method-added|1.74}}
function '''awardContract'''(quantity: Integer, commodity: String, start: Integer, destination: Integer, eta: Integer, fee: Integer) : Boolean
Adds a contract to the ship. (''Currently only for the player''). <code>eta</code> is in seconds and must be greater than the current time. <code>start</code> and <code>destination</code> are the ID numbers of the system. 
It returns false when there is no room for the cargo or the eta is chosen wrong or there is not enough money to accept the contracts.
e.g.
player.ship.awardContract(12, "Food", 34, 67, clock.seconds+7*24*3600, 5000)

If successful - and in galaxy chart 1 - the player will have 12 more food containers on board, the manifest will show that the cargo was picked up at Inus, to be delivered at Cemave, within exactly 7 days from now, and the player will be given 5000 credits if the cargo is delivered on time (early or late delivery will affect the amount paid).
'''N.B.''' Normally to get a contract, the player will have to buy the cargo at the local market price. Using this method, no inital payment is made.

=== <code>awardEquipment</code> ===
{{oolite-method-added|1.74}}
function '''awardEquipment'''(equipmentKey : String)
Adds the given piece of equipment to the ship. Example: <code>ship.awardEquipment("EQ_ECM")</code> (before 1.74 this command was only available for the player's ship)

=== <code>awardPassenger</code> ===
{{oolite-method-added|1.74}}
function '''awardPassenger'''(name: String, start: Integer, destination: Integer, eta: Integer, fee: Integer) : Boolean
Adds a contract to the ship. (''Currently only for the player''). <code>eta</code> is in seconds and must be greater than the current time. <code>start</code> and <code>destination</code> are the ID numbers of the system. 
It returns false when there is no room for the passenger or the eta is chosen wrong.
e.g.
player.ship.awardPassenger("cmdr Jameson", 34, 67, clock.seconds+3*24*3600, 1500)

If successful - and in galaxy chart 1 - the player will have cmdr Jameson as a passenger, his documents will show that he boarded the ship at Inus, to go to Cemave, within exactly 3 days from now, and the player will be given 1500 credits if he gets there on time (early or late arrival will affect the amount paid).
'''N.B.''' Normally a passenger will pay the captain a small advance upon boarding. Using this method, no inital payment is made.

=== <code>commsMessage</code> ===
{{oolite-method-added|1.72}}
function '''commsMessage'''(message : String) : Ship
Make the ship type entity broadcast the specified message. Works on buoys and subentities as well as normal ships and stations.

=== <code>deployEscorts</code> ===
function '''deployEscorts'''()
Launch the ship’s escorts, if any.

=== <code>dockEscorts</code> ===
function '''dockEscorts'''()
Dock the ship’s deployed escorts, if any.

=== <code>dumpCargo</code> ===
{{oolite-method-added|1.71}}
function '''dumpCargo'''() : Ship
Ejects one item of cargo from the ship, and returns the cargo item. Returns <code>null</code> if the ship has no cargo, anything has been ejected in the last 0.5 seconds, or if sent to the player while docked.

'''See Also:''' <code>[[#dumpCargo|dumpCargo]]</code>, <code>[[#ejectSpecificItem|ejectSpecificItem]]</code>

=== <code>ejectItem</code> ===
{{oolite-method-added|1.71}}
function '''ejectItem'''(role : String) : Ship
Spawns a ship of role <code>role</code> immediately behind the ship, with a slight backwards velocity. (Note: an equal and opposite reaction is applied to the parent ship, so doing this with large ships is rarely useful. <code>player.ejectItem("station")</code> may seem funny, but don’t come running to me if you have someone’s eye out.) Returns the generated ship, or <code>null</code> if no ship is generated. The scanClass of the ejected item will always be CLASS_CARGO.

'''See Also:''' <code>[[#dumpCargo|dumpCargo]]</code>, <code>[[#ejectSpecificItem|ejectSpecificItem]]</code>

=== <code>ejectSpecificItem</code> ===
{{oolite-method-added|1.71}}
function '''ejectSpecificItem'''(itemKey : String) : Ship
Spawns a ship with the ''shipdata.plist'' key <code>itemKey</code> immediately behind the ship, with a slight backwards velocity. The scanClass of the ejected item will always be CLASS_CARGO.

'''See Also:''' <code>[[#dumpCargo|dumpCargo]]</code>, <code>[[#ejectItem|ejectItem]]</code>

=== <code>equipmentStatus</code> ===
{{oolite-method-added|1.74}}
function '''equipmentStatus'''(equipmentKey : String) : String
Tests whether the specified type of equipment is installed, and whether it is functioning. Returns one of the following strings: <code>"EQUIPMENT_OK"</code>, <code>"EQUIPMENT_DAMAGED"</code>, <code>"EQUIPMENT_UNAVAILABLE"</code>. (was before 1.74 only available to the player)

'''See also''': <code>[[#setEquipmentStatus|setEquipmentStatus()]]</code>

=== <code>explode</code> ===
function '''explode'''()
Like it says. Works on otherwise-indestructible main station, and everything else too.

=== <code>exitAI</code> ===
function '''exitAI'''()
Exit the current AI, restoring the previous one. Equivalent to the <code>[[AI_methods|exitAI]]:</code> AI method. May not be used on player. Will generate a warning if there are no suspended AI states.

'''See Also:''' <code>[[#AI|AI]]</code>, <code>[[#setAI|setAI()]]</code>, <code>[[#hasSuspendedAI|hasSuspendedAI]]</code>

=== <code>fireECM</code> ===
{{Oolite-method-added|1.73}}
function '''fireECM'''()
activates an ecm burst, identical as the AI command.

=== <code>fireMissile</code> ===
{{oolite-method-added|1.74}}
function '''fireMissile'''([missile]) : Ship
fireMissile() will try and fire the first available missile and will return the missile fired, or null if no missiles can be fired at this time. It can take the optional missile identifier parameter, to allow for a specific missile to be fired. Missiles cannot be fired if the NPC ship hasn't got a valid target, or if the previous missile was launched less than missile_load_time seconds before. If a missile type was specified, and not found on the ship, no missile will be fired.

=== <code>hasEquipment</code> ===
{{Oolite-method-added|1.73}} 
function '''hasEquipment'''(equipmentKey : String [, includeWeapons : Boolean]) : Boolean
Returns <code>true</code> if the given piece of equipment is present on/in the ship, <code>false</code> if it is not. If <code>includeWeapons</code> is false, primary weapons (lasers) and secondary weapons (missiles and mines) are excluded. If <code>includeWeapons</code> is not specified, <code>true</code> is assumed.

Prior to Oolite 1.73, <code>hasEquipment()</code> is only available for the player’s ship and <code>includeWeapons</code> is ignored (treated as always false).

Example: <code>if (player.hasEquipment("EQ_TRUMBLE")) log("Oh noes, I has a trumble!")</code>

=== <code>hasRole</code> ===
function '''hasRole'''(role : String)
Returns <code>true</code> if the ship has <code>role</code> among its roles, <code>false</code> otherwise.

'''See Also:''' <code>[[#roles|roles]]</code>

=== <code>reactToAIMessage</code> ===
function '''reactToAIMessage'''(AIState : String)
Immediately execute the ship’s AI in the specified state.

=== <code>remove</code> ===
{{Oolite-method-added|1.72}}
function '''remove'''()
Like it says. Works on otherwise-indestructible main station, and everything else too. Same as explode except for the explosion itself

=== <code>removeEquipment</code> ===
{{Oolite-method-added|1.74}}
function '''removeEquipment'''(equipmentKey : String)
Removes the given piece of equipment from the ship. Example: <code>ship.removeEquipment("EQ_ECM")</code>. (before 1.74 this command was only available to the player)
This function can also be used to remove missiles (and mines). If more than one missile of the same type is found on board, only one of them will be removed.

=== <code>selectNewMissile</code> ===
{{oolite-method-added|1.74}}
function '''selectNewMissile'''() : equipmentKey
selectNewMissile() will automatically select a missile for a specific ship. It uses the missile_role shipdata.plist key to find out which missiles to select. As with the system populator, there's a small chance that missiles other than the missile_role specified in shipdata will be selected.
e.g.
this.ship.awardEquipment(this.ship.selectNewMissile())
will automatically add the 'right type' of missile to a ship, i.e. one that its captain would normally choose.

=== <code>setAI</code> ===
function '''setAI'''(AIName : String)
Set the current AI, leaving the old one suspended. Equivalent to the <code>[[AI_methods|setAITo]]:</code> AI method. May not be used on player.

'''See Also:''' <code>[[#AI|AI]]</code>, <code>[[#switchAI|switchAI()]]</code>, <code>[[#exitAI|exitAI()]]</code>

=== <code>setEquipmentStatus</code> ===
{{Oolite-method-added|1.74}}
function '''setEquipmentStatus'''(equipmentKey : String, statusKey : String)
Changes the status of the given piece of equipment from the ship. The two only valid status keys are <code>"EQUIPMENT_OK"</code>, <code>"EQUIPMENT_DAMAGED"</code>. (was before 1.74 only available to the player)

'''See also''': <code>[[#equipmentStatus|equipmentStatus()]]</code>

=== <code>setScript</code> ===
{{oolite-method-added|1.71}}
function '''setScript'''(scriptName : String)
Set, or completely replace, the javascript code associated to a ship entity.

=== <code>spawn</code> ===
{{oolite-method-added|1.71}}
function '''spawn'''(role : String [, count : Number]) : Array
Attempts to create <code>count</code> (maximum: 64) ships of role <code>role</code> close to the ship – specifically, inside the ship’s collision radius. (Since creating ships may fail, the number created may be less than <code>count</code>). The created ships are returned in an array. If <code>count</code> is not specified, one will be assumed.

<code>spawn()</code> is intended for cases when a ship splits into multiple parts or drops parts. In particular, it has the following special behaviour:
* The spawned ships inherit most of the temperature of the parent.
* If the parent is a missile and a child has the <code>[[shipdata.plist#is_submunition|is_submunition]]</code> property, the child will be considered a missile, its target will be set to that of the parent and the child’s owner will be set to the parent.
* <code>spawn()</code> does not set up escorts for the new ships, or generate witchspace effects, or do any special AI handling.

spawn() has a bunch of special semantics. In particular:

* The generated ships have a random position inside the parent ship’s collision radius, and initially face outwards.
* The generated ships inherit 85 % of the parent’s temperature.
* If the parent is a missile and the spawned ship has the is_submunition property set, the spawned ship inherits the parent’s owner and target and is flagged as a missile. (Special case for smarter
cluster missiles)
* Unlike addShip family methods, spawn() does not set up escorts, and does not handle auto-selection of trade routes and witchspace jump effects when it happens near a wormhole.

In short, spawn() is the right thing if bits are falling off or out of a ship, and wrong for everything else.
=== <code>spawnOne</code> ===
{{oolite-method-added|1.71}}
function '''spawnOne'''(role : String) : Ship
Convenience method which calls <code>[[#spawn|spawn]](role)</code> and returns the first element of the resulting array, or <code>null</code> if <code>spawn()</code> fails.

=== <code>switchAI</code> ===
function '''switchAI'''(AIName : String)
Set the current AI, exiting the old one. Equivalent to the <code>[[AI_methods|switchAITo]]:</code> AI method. May not be used on player.

'''See Also:''' <code>[[#AI|AI]]</code>, <code>[[#setAI|setAI()]]</code>, <code>[[#exitAI|exitAI()]]</code>

[[Category:Oolite scripting]]

Oolite JavaScript Reference: System

2009-07-29T23:55:48Z

Frame: /* <code>pseudoRandom255</code> */

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

The '''<code>System</code>''' class represents the current system. There is always one <code>System</code> object, available through the global propery <code>system</code>.

Attempts to change system properties are ignored in interstellar space (i.e., the place you end up in after a witchspace malfunction).

== Properties ==
=== <code>allShips</code> ===
{{Oolite-prop-added|1.70}}
'''allShips''' : Array (read-only)
A list of the ships in the system. If there are none, an empty list.

'''See Also:''' <code>[[#shipsWithPrimaryRole|shipsWithPrimaryRole]]()</code>, <code>[[#shipsWithRole|shipsWithRole]]()</code>, <code>[[#entitiesWithScanClass|entitiesWithScanClass]]()</code>, <code>[[#filteredEntities|filteredEntities]]()</code>.

=== <code>description</code> ===
'''description''' : String (read/write)
The description of the current system, as seen on the planet info screen.

=== <code>economy</code> ===
'''economy''' : Number (integer, read/write)
The type of economy in the current system, ranging from 0 (Rich Industrial) to 7 (Poor Agricultural). (See also: <code>[[#economyDescription|economyDescription]]</code>)

=== <code>economyDescription</code> ===
'''economyDescription''' : String (read-only)
A description of the economy type, for example, “Mostly Industrial”. (See also: <code>[[#economy|economy]]</code>)

=== <code>goingNova</code> ===
'''goingNova''' : Boolean (read-only)
<code>true</code> if the system’s sun is in the process of going nova, <code>false</code> otherwise. ('''To do''': this should be a propery of the sun.) (See also: <code>[[#goneNova|goneNova]]</code>, <code>[[#setSunNova|setSunNova()]]</code>)

=== <code>goneNova</code> ===
'''goneNova''' : Boolean (read-only)
<code>true</code> if the system’s sun hase gone nova, <code>false</code> otherwise. ('''To do''': this should be a propery of the sun.) (See also: <code>[[#goingNova|goingNova]]</code>, <code>[[#setSunNova|setSunNova()]]</code>)

=== <code>government</code> ===
'''government''' : Number (read/write, integer)
The type of government in the current system, ranging from 0 (Anarchy) to 7 (Corporate State). (See also: <code>[[#governmentDescription|governmentDescription]]</code>)

=== <code>governmentDescription</code> ===
'''governmentDescription''' : String (read-only)
A description of the government type, for example, “Democracy”. (See also: <code>[[#government|government]]</code>)

=== <code>ID</code> ===
ID : Number (integer, read-only)
A number identifying the system. 0 to 255, or -1 for interstellar space. Equivalent to <code>planet_number</code> in plist scripts.

=== <code>info</code> ===
'''info''' : String (write-only)
Overwrites existing info of the current system the player is in. As properties it uses the [[planetinfo.plist]] keys. e.g.
<code>System.info.description = "This is a dull planet."</code>
sets the description of the current planet to "This is a dull planet." (added with Oolite 1.72)

=== <code>inhabitantsDescription</code> ===
'''inhabitantsDescription''' : String (read/write)
The description of the inhabitants of the current system, such as “Slimy Blue Frogs”.

=== <code>isInterstellarSpace</code> ===
{{Oolite-prop-added|1.70}}
'''isInterstellarSpace''' : Boolean (read-only)
<code>true</code> if the current system is in interstellar space, <code>false</code> otherwise.

=== <code>mainPlanet</code> ===
{{Oolite-prop-added|1.70}}
'''mainPlanet''' : [[Oolite JavaScript Reference: Planet|Planet]] (read-only)
The system’s main planet, or <code>null</code> if there is none.

=== <code>mainStation</code> ===
{{Oolite-prop-added|1.70}}
'''mainStation''' : [[Oolite JavaScript Reference: Station|Station]] (read-only)
The system’s main station, or <code>null</code> if there is none.

=== <code>planets</code> ===
{{Oolite-prop-added|1.70}}
'''planets''' : Array (read-only)
A list of the planets in the system. If there are none, an empty list.

=== <code>population</code> ===
'''population''' : Number (integer, read/write)
The population of the current system.

=== <code>productivity</code> ===
'''productivity''' : Number (integer, read/write)
The productivity of the current system.

=== <code>pseudoRandom100</code> ===
'''pseudoRandom100''' : Number (integer, read)
A random number between 0 and 99 that is always the same for a given system.

=== <code>pseudoRandom256</code> ===
'''pseudoRandom256''' : Number (integer, read)
A random number between 0 and 255 that is always the same for a given system.

=== <code>sun</code> ===
{{Oolite-prop-added|1.70}}
'''sun''' : [[Oolite JavaScript Reference: Sun|Sun]] (read-only)
The system’s sun, or <code>null</code> if there is none.

=== <code>techLevel</code> ===
'''techLevel''' : Number (integer, read/write)
The technology level of the current system, ranging from 0 to 15.

== Methods ==
=== <code>addMoon</code> ===
function '''addMoon'''(planetInfoKey : String)
Adds a moon to the system, using the specified entry in ''[[planetinfo.plist]]''. A moon is the same as a planet, except that it has no atmosphere. (See also: <code>[[#addPlanet|addPlanet()]]</code>)

=== <code>addPlanet</code> ===
function '''addPlanet'''(planetInfoKey : String)
Adds a planet to the system, using the specified entry in ''[[planetinfo.plist]]''. (See also: <code>[[#addMoon|addMoon()]]</code>)

=== <code>countShipsWithRole</code> ===
function '''countShipsWithRole'''(role : String) : Number (integer)
Returns the number of ships with the specified role in the system; Counts not only the primary role the ship is added with but all roles a ship can have. Specially useful for counting a group of ships linked together with a common but not used role.

=== <code>countShipsWithPrimaryRole</code> ===
function '''countShipsWithPrimaryRole'''(role : String) : Number (integer)
Returns the number of ships with the specified primary role in the system; equivalent to checkForShips: in plist scripts. (added with Oolite 1.72)

=== <code>entitiesWithScanClass</code> ===
{{Oolite-method-added|1.70}}
function '''entitiesWithScanClass'''(scanClass : String [, relativeTo : [[Oolite JavaScript Reference: Entity|Entity]] [, range : Number]]) : Array
A list of the entities in the system whose scan class is <code>scanClass</code>. If <code>relativeTo</code> is specified, the list will be sorted in order of proximity to <code>relativeTo</code> (i.e., the first element of the list is closest). If <code>range</code> is also specified, entities further than <code>range</code> metres from <code>relativeTo</code> will be excluded. If no matching entities are found, an empty array is returned.

'''See Also:''' <code>[[#shipsWithPrimaryRole|shipsWithPrimaryRole]]()</code>, <code>[[#shipsWithRole|shipsWithRole]]()</code>, <code>[[#filteredEntities|filteredEntities]]()</code>.

=== <code>filteredEntities</code> ===
{{Oolite-method-added|1.70}}
function '''filteredEntities'''(this : Object, predicate : Function [, relativeTo : [[Oolite JavaScript Reference: Entity|Entity]] [, range : Number]]) : Array
A list of the entities for which <code>predicate</code> returns <code>true</code>. If <code>relativeTo</code> is specified, the list will be sorted in order of proximity to <code>relativeTo</code> (i.e., the first element of the list is closest). If <code>range</code> is also specified, entities further than <code>range</code> metres from <code>relativeTo</code> will be excluded. If no matching entities are found, an empty array is returned.

'''Example:'''
this.findIdlePoliceInScannerRange = function()
{
function isIdlePolice(entity)
{
return entity.isShip && entity.isPolice && !entity.target
}

return system.filteredEntities(this, isIdlePolice, player, 25600)
}

'''See Also:''' <code>[[#shipsWithPrimaryRole|shipsWithPrimaryRole]]()</code>, <code>[[#shipsWithRole|shipsWithRole]]()</code>, <code>[[#entitiesWithScanClass|entitiesWithScanClass]]()</code>.

=== <code>infoForSystem</code> ===
function '''infoForSystem'''(galaxyNumber: Integer, systemID : Integer) (write-only)
Overwrites existing info of the given system. As properties it uses the [[planetinfo.plist]] keys. e.g.
System.infoForSystem(0, 55).description = "This is a dull planet."
sets the description of planet nr 55 in galaxy 0 to his is a dull planet." (added with Oolite 1.72.1)

=== <code>legacy_addShips etc.</code> ===
function '''legacy_addShips'''(role : String, count : Number)
function '''legacy_addSystemShips'''(role : String, count : Number, position : Number)
function '''legacy_addShipsAt'''(role : String, count : Number, coordscheme : String, where : [[Oolite JavaScript Reference: Vector#Vector Expressions|vectorExpression]])
function '''legacy_addShipsAtPrecisely'''(role : String, count : Number, coordscheme : String, where : [[Oolite JavaScript Reference: Vector#Vector Expressions|vectorExpression]])
function '''legacy_addShipsWithinRadius'''(role : String, count : Number, coordScheme : String, where : [[Oolite JavaScript Reference: Vector#Vector Expressions|vectorExpression]], radius : Number)
function '''legacy_spawnShip'''(shipDataKey : String)
Various ways of causing ships to appear. Each of these corresponds to a legacy scripting method. For more info about the coordscheme, look at [[oolite coordinate systems]]. A new, more flexible <code>addShips()</code> function will supersede all of them.

'''Important:''' <code>legacy_addShipsWithinRadius</code> does not work in Oolite 1.70, but has been fixed for Oolite 1.71. <code>legacy_spawn</code>, previously listed here, never worked as intended and has been replaced with <code>Ship.[[Oolite JavaScript Reference: Ship#spawn|spawn]]()</code>.

=== <code>sendAllShipsAway</code> ===
function '''sendAllShipsAway'''()
Makes all ships hyperspace out of the system.

=== <code>setSunNova</code> ===
function '''setSunNova'''(secondsUntilNova : Number)
Sets the system’s sun to go nova after the specified time interval. Time is specified in [[Time scales in Oolite#Game real time|game real time]].
Deprecated since 1.72 in favour of: system.sun.goNova()

=== <code>shipsWithPrimaryRole</code> ===
{{Oolite-method-added|1.70}}
function '''shipsWithPrimaryRole'''(role : String [, relativeTo : [[Oolite JavaScript Reference: Entity|Entity]] [, range : Number]]) : Array
A list of the entities in the system whose [[Oolite JavaScript Reference: Ship#primaryRole|primary role]] is <code>role</code>. If <code>relativeTo</code> is specified, the list will be sorted in order of proximity to <code>relativeTo</code> (i.e., the first element of the list is closest). If <code>range</code> is also specified, entities further than <code>range</code> metres from <code>relativeTo</code> will be excluded. If no matching entities are found, an empty array is returned.

'''See Also:''' <code>[[#shipsWithRole|shipsWithRole]]()</code>, <code>[[#entitiesWithScanClass|entitiesWithScanClass]]()</code>, <code>[[#filteredEntities|filteredEntities]]()</code>.

=== <code>shipsWithRole</code> ===
{{Oolite-method-added|1.70}}
function '''shipsWithRole'''(role : String [, relativeTo : [[Oolite JavaScript Reference: Entity|Entity]] [, range : Number]]) : Array
A list of the entities in the system whose [[Oolite JavaScript Reference: Ship#roles|role set]] contains <code>role</code>. If <code>relativeTo</code> is specified, the list will be sorted in order of proximity to <code>relativeTo</code> (i.e., the first element of the list is closest). If <code>range</code> is also specified, entities further than <code>range</code> metres from <code>relativeTo</code> will be excluded. If no matching entities are found, an empty array is returned.

'''See Also:''' <code>[[#shipsWithRole|shipsWithRole]]()</code>, <code>[[#entitiesWithScanClass|entitiesWithScanClass]]()</code>, <code>[[#filteredEntities|filteredEntities]]()</code>.

=== <code>systemIDForName</code> ===
function '''systemIDForName'''(systemName : String) : Integer
Returns the ID number of a system in the current galaxy based on the system name)

=== <code>systemNameForID</code> ===
function '''systemNameForID'''(systemID : Integer) : String
Returns the name of a system in the current galaxy based on the given ID number)

[[Category: Oolite scripting]]

Your Ad Here!

2009-06-27T08:45:19Z

Frame: /* Download Link */

===Download Link===

[http://sancho.dk/oolite/yaw.zip''Download Ver 3 (Basic package)''] Version for all oolite versions below 1.72.1. '''It includes set A to D''' 
[http://sancho.dk/oolite/ya_set_E.zip''Download Set E for Ver 3''] You must first install the basic package of version 3 
[http://sancho.dk/oolite/ya_set_F.zip''Download Set F for Ver 3''] You must first install the basic package of version 3 

[http://sancho.dk/oolite/Yaw_V4.zip''Download Ver 4''] Version for oolite 1.72.1 and above. This version has significant improvements and bug fixes from version 3. The most profound of the improvements is that the original box-style convenience store dockable bases have been replaced with variants of the original Griff trade outpost,but due to the use of JS and shaders for the new constores it is only compatible from version 1.72.1 and above '''It includes all sets from A to F'''

File:FuelCollectorV0.03oxp.zip

2008-08-19T20:46:40Z

Frame: Equipment, read readme file in umbrella map

Equipment, read readme file in umbrella map

File:BountyScannerV1.03.zip

2008-08-19T20:01:14Z

Frame: Equipment adds bounty information to missile target reticle

Equipment adds bounty information to missile target reticle

File:BountyScannerV1.02.zip

2008-08-17T12:20:12Z

Frame: Equipment for Oolite: adds bounty information to the target reticle

Equipment for Oolite: adds bounty information to the target reticle

File:FuelCollectorv0.02oxp.zip

2008-08-16T16:44:57Z

Frame: The Fuel Collector v0.2

The Fuel Collector v0.2

File:BountyScannerOXP 1.01.zip

2008-08-13T16:54:08Z

Frame: Equipment , adds bounty information to Players target missile box..

Equipment , adds bounty information to Players target missile box..

File:BountyScannerOXP.zip

2008-08-12T15:09:19Z

Frame: For Oolite 1.71, Equipment that adds Bounty information to that missile targetbox

For Oolite 1.71, Equipment that adds Bounty information to that missile targetbox

File:FuelCollector.oxp.zip

2008-07-25T12:39:09Z

Frame:

Rock Hermit Locator

2007-07-24T23:56:42Z

Frame:

The Rock Hermit Locator is an add on Equipement for your Vessel.. It is especially usefull for miners and Traders since Rock hermits are allways in an asteroid field, and Rock Hermits have good prices on certain commodities...

Download it here

[http://home20.inet.tele.dk/dp1974/Rock_Hermit_Locator1.1.oxp.zip ''Rock Hermit Locator'']

Rock Hermit Locator

2007-07-24T23:55:40Z

Frame:

The Rock Hermit Locator is an add on Equipement for your Vessel.. It is especially usefull for miners and Traders since Rock hermits are allways in an asteroid field, and Rock Hermits have good prices on certain items...

Download it here

[http://home20.inet.tele.dk/dp1974/Rock_Hermit_Locator1.1.oxp.zip ''Rock Hermit Locator'']

Rock Hermit Locator

2007-07-24T23:53:55Z

Frame: New page: The Rock Hermit Locator is an add on Equipement for your Vessel.. It is especially usefull for miners and Traders since Rock hermits are allways in an asteroid field, and Rock Hermits have...

OXP

2007-07-24T23:52:07Z

Frame: /* Table of all OXPs */

OXP

2007-07-24T23:22:17Z

Frame: /* Ship Systems */