Elite Wiki - User contributions [en]

Oolite planet list

2017-06-16T18:17:34Z

PG1: changed link to Interactive Map to insecure one (http instead of https)

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

The format of the entries is:

: # {system ID}. '''{name}''' ({coordinates}), { {IDs of nearby systems} } within 7.0 LY. Radius {radius of main planet} km.
:: {government}, {economy}. Pop. {population} B, Prod. {productivity} MCr. HC: {hub count}, TL: {tech level}, {inhabitant description}.
:: ''{system comments}''

for example

: # 7. '''Lave''' (20,173), {39,46,55,129,147,255} within 7.0 LY. Radius 4116 km.
:: Dictatorship, Rich Agri. Pop. 2.5 B, Prod. 7000 MCr. HC: 6, TL: 5, Human Colonials.
:: ''Lave is most famous for its vast rain forests and the Laveian tree grub. ''

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

* Online interactive maps.
** [http://bit.ly/OoliteInteractiveMap2 OOlite Interactive Map] courtesy of PhantorGorth. It does 2D & 3D modes for displaying the planet map and the planet data. Also there is a superb jump route calculator.
** [http://theramist.co.uk/ooliteinfo/oo.php OOliteInfo] from Maaarcooose is also available which not only displays the galaxy maps and all planet data, but also allows modification of the seed numbers used to generate the galaxy data. '''Note: The economy descriptions for a lot of planets are not accurately described on this resource.'''

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

=== Notes on values ===

* For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. The Technology Level numbers shown in the lists are the numbers displayed to the player (range 1-15), and again ''subtract 1 from this number'' (range 0-14) to get the value entered into planetinfo.plist.

* The "hub count" is the number of systems reachable from this system in a single jump: it will always match the number of systems in the "IDs of nearby systems" list.

* The radius of the main planet as an in-game object is 1/100th of that listed by the system description.

* The coordinates are in X, Y format, ranging from 0,0 (top left corner) to 255,255 (bottom right corner). When translated to the galactic maps, because they are rectangular rather than square, this means that an X coordinate step is 0.4 LY, but a Y coordinate step is only 0.2 LY

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/OoliteGalaxiesSpreadsheet spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* There is also an [http://bit.ly/OoliteInteractiveMap2 interactive map] of the Oolite Galaxies including route finding (by PhantorGorth). Also includes a 3D option. Works in Firefox, Chrome, IE9+, Safari (but not v6 on a Mac), Opera (the quick zoom has a side effects caused by Opera).

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror] -- [[Sector3/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror] -- [[Sector4/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror] -- [[Sector5/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror] -- [[Sector6/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror] -- [[Sector7/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror] -- [[Sector8/Index|The New Galaxy Guide]]

[https://www.box.com/s/ex98vikozd2gm2vsztme Zipped set of all 8 Vector Maps]

[https://www.box.com/s/sy991cllk135hqvewpnm Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Oolite planet list

2017-04-25T21:01:02Z

PG1: Fixed link for Oolite Interactive Map

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

The format of the entries is:

: # {system ID}. '''{name}''' ({coordinates}), { {IDs of nearby systems} } within 7.0 LY. Radius {radius of main planet} km.
:: {government}, {economy}. Pop. {population} B, Prod. {productivity} MCr. HC: {hub count}, TL: {tech level}, {inhabitant description}.
:: ''{system comments}''

for example

: # 7. '''Lave''' (20,173), {39,46,55,129,147,255} within 7.0 LY. Radius 4116 km.
:: Dictatorship, Rich Agri. Pop. 2.5 B, Prod. 7000 MCr. HC: 6, TL: 5, Human Colonials.
:: ''Lave is most famous for its vast rain forests and the Laveian tree grub. ''

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

* Online interactive maps.
** [http://bit.ly/OoliteInteractiveMap OOlite Interactive Map] courtesy of PhantorGorth. It does 2D & 3D modes for displaying the planet map and the planet data. Also there is a superb jump route calculator.
** [http://theramist.co.uk/ooliteinfo/oo.php OOliteInfo] from Maaarcooose is also available which not only displays the galaxy maps and all planet data, but also allows modification of the seed numbers used to generate the galaxy data. '''Note: The economy descriptions for a lot of planets are not accurately described on this resource.'''

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

=== Notes on values ===

* For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. The Technology Level numbers shown in the lists are the numbers displayed to the player (range 1-15), and again ''subtract 1 from this number'' (range 0-14) to get the value entered into planetinfo.plist.

* The "hub count" is the number of systems reachable from this system in a single jump: it will always match the number of systems in the "IDs of nearby systems" list.

* The radius of the main planet as an in-game object is 1/100th of that listed by the system description.

* The coordinates are in X, Y format, ranging from 0,0 (top left corner) to 255,255 (bottom right corner). When translated to the galactic maps, because they are rectangular rather than square, this means that an X coordinate step is 0.4 LY, but a Y coordinate step is only 0.2 LY

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/OoliteGalaxiesSpreadsheet spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* There is also an [http://bit.ly/Oolite2DMap interactive map] of the Oolite Galaxies including route finding (by PhantorGorth). Also includes a 3D option. Works in Firefox, Chrome, IE9+, Safari (but not v6 on a Mac), Opera (the quick zoom has a side effects caused by Opera).

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror] -- [[Sector3/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror] -- [[Sector4/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror] -- [[Sector5/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror] -- [[Sector6/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror] -- [[Sector7/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror] -- [[Sector8/Index|The New Galaxy Guide]]

[https://www.box.com/s/ex98vikozd2gm2vsztme Zipped set of all 8 Vector Maps]

[https://www.box.com/s/sy991cllk135hqvewpnm Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Oolite planet list

2017-04-25T17:47:59Z

PG1: /* Where do these crazy names come from? */ fixed the link for the spreadsheet as a zip file now points to my website (via bit.ly) rather than Dropbox.

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

The format of the entries is:

: # {system ID}. '''{name}''' ({coordinates}), { {IDs of nearby systems} } within 7.0 LY. Radius {radius of main planet} km.
:: {government}, {economy}. Pop. {population} B, Prod. {productivity} MCr. HC: {hub count}, TL: {tech level}, {inhabitant description}.
:: ''{system comments}''

for example

: # 7. '''Lave''' (20,173), {39,46,55,129,147,255} within 7.0 LY. Radius 4116 km.
:: Dictatorship, Rich Agri. Pop. 2.5 B, Prod. 7000 MCr. HC: 6, TL: 5, Human Colonials.
:: ''Lave is most famous for its vast rain forests and the Laveian tree grub. ''

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

* Online interactive maps.
** [http://bit.ly/Oolite2DMap OOlite Interactive Map] courtesy of PhantorGorth. It does 2D & 3D modes for displaying the planet map and the planet data. Also there is a superb jump route calculator.
** [http://theramist.co.uk/ooliteinfo/oo.php OOliteInfo] from Maaarcooose is also available which not only displays the galaxy maps and all planet data, but also allows modification of the seed numbers used to generate the galaxy data. '''Note: The economy descriptions for a lot of planets are not accurately described on this resource.'''

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

=== Notes on values ===

* For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. The Technology Level numbers shown in the lists are the numbers displayed to the player (range 1-15), and again ''subtract 1 from this number'' (range 0-14) to get the value entered into planetinfo.plist.

* The "hub count" is the number of systems reachable from this system in a single jump: it will always match the number of systems in the "IDs of nearby systems" list.

* The radius of the main planet as an in-game object is 1/100th of that listed by the system description.

* The coordinates are in X, Y format, ranging from 0,0 (top left corner) to 255,255 (bottom right corner). When translated to the galactic maps, because they are rectangular rather than square, this means that an X coordinate step is 0.4 LY, but a Y coordinate step is only 0.2 LY

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/OoliteGalaxiesSpreadsheet spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* There is also an [http://bit.ly/Oolite2DMap interactive map] of the Oolite Galaxies including route finding (by PhantorGorth). Also includes a 3D option. Works in Firefox, Chrome, IE9+, Safari (but not v6 on a Mac), Opera (the quick zoom has a side effects caused by Opera).

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror] -- [[Sector3/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror] -- [[Sector4/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror] -- [[Sector5/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror] -- [[Sector6/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror] -- [[Sector7/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror] -- [[Sector8/Index|The New Galaxy Guide]]

[https://www.box.com/s/ex98vikozd2gm2vsztme Zipped set of all 8 Vector Maps]

[https://www.box.com/s/sy991cllk135hqvewpnm Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Deep Horizons Gas Giant Skimming OXP

2015-06-11T22:07:24Z

PG1: /* Authors */

==Background==
[[File:Gas_giant_skimming_header.jpg‎|thumb|left]]
Gravity compensators bucking like a Taargian Mule, enough atmospheric friction your hull could fry a Hoggian egg, and all for a chance to sift some quirium from a hydrogen stream. 'Ass draggin' a gas giant ain't for the weak-bladdered. And mining one?!? Leave that to the corporate 'wire-flies' if you know what's good for you. I worked on an 'Ass-Dragger' for a while. Why do you think I stay station-side now?!?" - Icosahedron Station Dock Worker in orbit of a gas giant

==Overview==
''The Road to Riches or the Elevator to Hell''

Skimming gas giants to refuel a ship or mining one for rare minerals is not an easy task. But it is one that some pilots utilize to reduce their fuel costs, and a lucky (or foolhardy) few fill their holds with compressed exotic gases and other rarities. Any ship with a fuel scoop can attempt to refuel from a gas giant planet. Just get low enough in orbit and be going fast enough, and you can skim the atmosphere for Quirium ions. Or if you want to try mining, equip yourself with the necessary gas compressors and refining equipment and do the same. Keep in mind, mining requires a lower orbit than refueling. Heh... If it was easy, everyone would do it...

== Description ==
{{OXPLevel|0|3}}
Once the OXP is installed you can immediately start gas skimming. No extra equipment is required to the fuel scoop. The extra skimming possibility is provided by Deep Horizons Industries to all Fuel Scoop Manufacturers for low licensing costs (the scoop is a mass product after all).

== Requirements ==
Unknown, but should still work with older releases (2011).
The License.txt states that v1.0.7 works with Oolite v1.75.

== License ==
Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States license (Modified)
This is the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States license as detailed at
http://creativecommons.org/licenses/by-nc-nd/3.0/us/ with the additional terms and conditions as found in the License.txt file in the OXP package. By installing the OXP you agree to these terms and conditions.

== Downloads ==
The [http://deephorizonindustries.com/Gas_Giant_Skimming.html latest version] is always available on the [http://deephorizonindustries.com/default.html Deep Horizons homepage]

== About ==
Founded on the planet Teriar in Galaxy 3 originally, Deep Horizon Industries started as a planet-side manufacturer of large-scale farming equipment. It later expanded into early environmental modification systems to be utilized on agricultural worlds to expand growth seasons. Throughout its 200 year history, DHI has constantly expanded its product and service offerings to its consumers. Now offering State-of-the-Art optical sensors, gas refining equipment, and its traditional farming equipment to name but a few, Deep Horizon Industries is now a pan-galactic company catering to a wide array of customer needs...

Read the [http://deephorizonindustries.com/about_company.html complete background story here].
== Authors ==
* Cmd. Cheyd
* Code optimizations provided by PhantorGorth

[http://deephorizonindustries.com/contact.html Contact]
 

[[Category:Oolite]][[Category:Activities_OXPs]][[Category:Mechanics_OXPs]][[Category:Oolite expansion packs]]

Oolite planet list

2014-01-11T09:44:27Z

PG1: Changed the link back to the bit.ly address. (I do not want direct linking. DO NOT change back)

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. The Technology Level numbers shown in the lists are the numbers displayed to the player (range 1-15), and again ''subtract 1 from this number'' (range 0-14) to get the value entered into planetinfo.plist.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

* Online interactive maps.
** [http://bit.ly/Oolite2DMap OOlite Interactive Map] courtesy of PhantorGorth. It does 2D & 3D modes for displaying the planet map and the planet data. Also there is a superb jump route calculator.
** [http://theramist.co.uk/ooliteinfo/oo.php OOliteInfo] from Maaarcooose is also available which not only displays the galaxy maps and all planet data, but also allows modification of the seed numbers used to generate the galaxy data.

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/HYuwRq spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* There is also an [http://bit.ly/Oolite2DMap interactive map] of the Oolite Galaxies including route finding (by PhantorGorth). Also includes a 3D option. Works in Firefox, Chrome, IE9+, Safari (but not v6 on a Mac), Opera (the quick zoom has a side effects caused by Opera).

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[https://www.box.com/s/ex98vikozd2gm2vsztme Zipped set of all 8 Vector Maps]

[https://www.box.com/s/sy991cllk135hqvewpnm Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Oolite planet list

2014-01-11T09:40:17Z

PG1: Fixed the spellings and mentioned the planet data available from my interactive map.

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. The Technology Level numbers shown in the lists are the numbers displayed to the player (range 1-15), and again ''subtract 1 from this number'' (range 0-14) to get the value entered into planetinfo.plist.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

* Online interactive maps.
** [https://dl.dropbox.com/u/1380916/WebPages/2D%20Oolite%20Galaxy.html OOlite Interactive Map] courtesy of PhantorGorth. It does 2D & 3D modes for displaying the planet map and the planet data. Also there is a superb jump route calculator.
** [http://theramist.co.uk/ooliteinfo/oo.php OOliteInfo] from Maaarcooose is also available which not only displays the galaxy maps and all planet data, but also allows modification of the seed numbers used to generate the galaxy data.

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/HYuwRq spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* There is also an [http://bit.ly/Oolite2DMap interactive map] of the Oolite Galaxies including route finding (by PhantorGorth). Also includes a 3D option. Works in Firefox, Chrome, IE9+, Safari (but not v6 on a Mac), Opera (the quick zoom has a side effects caused by Opera).

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[https://www.box.com/s/ex98vikozd2gm2vsztme Zipped set of all 8 Vector Maps]

[https://www.box.com/s/sy991cllk135hqvewpnm Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

GalCop Rewards

2013-02-25T21:07:41Z

PG1: Updated revision and link

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. '''You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].'''

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/Wn3d8T GalCop_Rewards.1.0.2.oxp.zip]

==Fast Facts==
{{OXPLevel|0|0}}
{{Infobox OXPb| title = GalCop Rewards
|version = 1.0.2
|release = 2012-06-18
|license = CC-by-nc-sa-3.0
|features = Adds GalCop Reward Points
|category = Mechanics OXPs
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12061 BB-Link]
}}

Oolite planet list

2013-01-20T16:11:50Z

PG1: /* Where do these crazy names come from? */ Added link to my Interactive Map

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. The Technology Level numbers shown in the lists are the numbers displayed to the player (range 1-15), and again ''subtract 1 from this number'' (range 0-14) to get the value entered into planetinfo.plist.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/HYuwRq spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* There is also an [http://bit.ly/Oolite2DMap interactive map] of the Oolite Galaxies including route finding (by PhantorGorth). Also includes a 3D option. Works in Firefox, Chrome, IE9+, Safari (but not v6 on a Mac), Opera (the quick zoom has a side effects caused by Opera).

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The new Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[https://www.box.com/s/ex98vikozd2gm2vsztme Zipped set of all 8 Vector Maps]

[https://www.box.com/s/sy991cllk135hqvewpnm Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Safe Docking

2013-01-15T00:17:15Z

PG1: /* Fast Facts */

==Introduction==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born. See [[GalCop Rewards|GalCop Rewards OXP]] for details. Well, you may be wondering what this has to do with this Safe Docking OXP. Poor docking was one of the main issues GalCop had with bad piloting. Safe Docking is GalCop's attempt for rewarding pilots for docking at participating stations in a safe manner and makes use of GalCop Rewards to do this.

==Overview==

With Safe Docking OXP how fast and carefully you dock now determines whether you get rewarded or receive a penalty. Dock too fast and you will be get a penalty (and may be an insult). Dock at an acceptable speed and you may get rewarded with GalCop Reward Points. Generally the slower the better, but be warned, go too slowly or scrape your ship's hull and the station's Dockmaster will not be pleased. If you only docked in an "Ok" fashion you may not get a message at all.

Only manual docking counts. If you dock using a Docking Computer (both automatic or Instant docking) you will not be rewarded. Also cheating by using the Docking Computer to get you almost there and turning it off and finishing docking manually is also detected and will not count as manual docking.

'''The following table shows the speeds and their results:'''
{| class="wikitable"
!Speed Range
!Rating
!Reward
!Penalty
|-
|>=0m/s and <25m/s
|Too Slow
|
|Lose 5 Credits
|-
|>=25m/s and <50m/s
|Excellent
|10 Reward Points
|
|-
|>=50m/s and <75m/s
|Very Good
|5 Reward Points
|
|-
|>=75m/s and <100m/s
|Good
|1 Reward Points
|
|-
|>=100m/s and <125m/s
|Ok
|
|
|-
|>=125m/s and <225m/s
|Poor
|
|Lose 1 Reward Points and fined 20 Credits
|-
|>=225m/s and <300m/s
|Reckless
|
|Lose 5 Reward Points and fined 40 Credits
|-
|>=300m/s and <400m/s
|Dangerous
|
|Lose all Reward Points and fined 100 Credits
|-
|>=400m/s and <550m/s
|Very Dangerous
|
|Lose all Reward Points and fined 500 Credits
|-
|>=550m/s
|Criminal
|
|Lose all Reward Points, fined 1000 Credits and gain 5 Credits bounty
|-
|<225m/s and scraped ship during docking
|Collided
|
|Lose 2 Reward Points and fined 25 Credits
|}

The only variation from the above is if you are under attack '''AND''' at low energy. In this situation you will let off any penalty. Being under attack is defined by being attacked by at least one non-police ship (by laser or missile) and each attacking ship still has you as its target. (Still targeted is checked every 2 seconds.) If you have been attacked by a cloaked ship within the last 10 seconds then this also counts as under attack. Low Energy is when your energy is less than 128 which is less than 2 full bars on a ship's HUD.

All fines are reduced not take you below 100 credits. So if you are below 100 credits you won't be fined.

If you re-visit the same station in the scheme within the last hour (in-game hours) then you do not get any Rewards Points. The Dockmaster will let you know if this is the case. Penalties for bad docking will still apply though.

==Participating Stations==

All system Main Stations are in the scheme but also when you enter the station aegis you will get a message telling you that the station is in the scheme e.g. “The Dockmaster would like to let you know that Lave Orbital Station is a participant in the Safe Docking Rewards Scheme.”

Any other station or carrier you will receive an equivalent message if you enter the region within the aegis distance around them (2x scanner radius). In Oolite aegis only normally applies to the main station but it is “reproduced” for these other stations.

==My Speed==

If you install OXPConfig OXP version 2.0.10 or higher then you can use that to modify the OXP parameter that adds to a station's arrival message a notification of your arrival speed. This parameter is off by default.

==Docking Clearance==

If docking clearance requirement is turned on (usually by installing the Docking Clearance OXP) then docking without clearance means you get no Reward Points added for good docking. Penalties for bad docking will still apply though.

==Dependencies==

{{OXPConfig-small}}
[[GalCop Rewards|GalCop Rewards OXP]]

Optional: [[OXPConfig|OXPConfig OXP version 2.0.10 or higher]]

Optional: [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance]]

==Download==
[http://bit.ly/VGCs2m Safe_Docking.1.0.1.oxp.zip]

==Fast Facts==
{{OXPLevel|0|1}}
{{Infobox OXPb| title = Safe Docking
|version = 1.0.1
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Manual Docking Behaviour
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12062 BB-Link]
}}

{{mechanics-OXP}}

Safe Docking

2013-01-15T00:16:44Z

PG1: /* Download */

==Introduction==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born. See [[GalCop Rewards|GalCop Rewards OXP]] for details. Well, you may be wondering what this has to do with this Safe Docking OXP. Poor docking was one of the main issues GalCop had with bad piloting. Safe Docking is GalCop's attempt for rewarding pilots for docking at participating stations in a safe manner and makes use of GalCop Rewards to do this.

==Overview==

With Safe Docking OXP how fast and carefully you dock now determines whether you get rewarded or receive a penalty. Dock too fast and you will be get a penalty (and may be an insult). Dock at an acceptable speed and you may get rewarded with GalCop Reward Points. Generally the slower the better, but be warned, go too slowly or scrape your ship's hull and the station's Dockmaster will not be pleased. If you only docked in an "Ok" fashion you may not get a message at all.

Only manual docking counts. If you dock using a Docking Computer (both automatic or Instant docking) you will not be rewarded. Also cheating by using the Docking Computer to get you almost there and turning it off and finishing docking manually is also detected and will not count as manual docking.

'''The following table shows the speeds and their results:'''
{| class="wikitable"
!Speed Range
!Rating
!Reward
!Penalty
|-
|>=0m/s and <25m/s
|Too Slow
|
|Lose 5 Credits
|-
|>=25m/s and <50m/s
|Excellent
|10 Reward Points
|
|-
|>=50m/s and <75m/s
|Very Good
|5 Reward Points
|
|-
|>=75m/s and <100m/s
|Good
|1 Reward Points
|
|-
|>=100m/s and <125m/s
|Ok
|
|
|-
|>=125m/s and <225m/s
|Poor
|
|Lose 1 Reward Points and fined 20 Credits
|-
|>=225m/s and <300m/s
|Reckless
|
|Lose 5 Reward Points and fined 40 Credits
|-
|>=300m/s and <400m/s
|Dangerous
|
|Lose all Reward Points and fined 100 Credits
|-
|>=400m/s and <550m/s
|Very Dangerous
|
|Lose all Reward Points and fined 500 Credits
|-
|>=550m/s
|Criminal
|
|Lose all Reward Points, fined 1000 Credits and gain 5 Credits bounty
|-
|<225m/s and scraped ship during docking
|Collided
|
|Lose 2 Reward Points and fined 25 Credits
|}

The only variation from the above is if you are under attack '''AND''' at low energy. In this situation you will let off any penalty. Being under attack is defined by being attacked by at least one non-police ship (by laser or missile) and each attacking ship still has you as its target. (Still targeted is checked every 2 seconds.) If you have been attacked by a cloaked ship within the last 10 seconds then this also counts as under attack. Low Energy is when your energy is less than 128 which is less than 2 full bars on a ship's HUD.

All fines are reduced not take you below 100 credits. So if you are below 100 credits you won't be fined.

If you re-visit the same station in the scheme within the last hour (in-game hours) then you do not get any Rewards Points. The Dockmaster will let you know if this is the case. Penalties for bad docking will still apply though.

==Participating Stations==

All system Main Stations are in the scheme but also when you enter the station aegis you will get a message telling you that the station is in the scheme e.g. “The Dockmaster would like to let you know that Lave Orbital Station is a participant in the Safe Docking Rewards Scheme.”

Any other station or carrier you will receive an equivalent message if you enter the region within the aegis distance around them (2x scanner radius). In Oolite aegis only normally applies to the main station but it is “reproduced” for these other stations.

==My Speed==

If you install OXPConfig OXP version 2.0.10 or higher then you can use that to modify the OXP parameter that adds to a station's arrival message a notification of your arrival speed. This parameter is off by default.

==Docking Clearance==

If docking clearance requirement is turned on (usually by installing the Docking Clearance OXP) then docking without clearance means you get no Reward Points added for good docking. Penalties for bad docking will still apply though.

==Dependencies==

{{OXPConfig-small}}
[[GalCop Rewards|GalCop Rewards OXP]]

Optional: [[OXPConfig|OXPConfig OXP version 2.0.10 or higher]]

Optional: [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance]]

==Download==
[http://bit.ly/VGCs2m Safe_Docking.1.0.1.oxp.zip]

==Fast Facts==
{{OXPLevel|0|1}}
{{Infobox OXPb| title = Safe Docking
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Manual Docking Behaviour
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12062 BB-Link]
}}

{{mechanics-OXP}}

Oolite JavaScript Reference: Quaternion

2013-01-10T23:14:23Z

PG1: /* Quaternions for Rotations */

'''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). Often you will want to start with this identity quaternion before applying the methods '''rotate''', '''rotateX''', '''rotateY''' or '''rotateZ'''.

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 array of four numbers, or an [[Oolite JavaScript Reference: Entity|Entity]] (in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used). In specifications, this is represented by arguments typed <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>conjugate</code> ===
{{oolite-method-added|1.77}}
function '''conjugate'''() : Quaternion
Return the conjugate of the quaternion (i.e. the quaternion which when multiplied by the original quaternion returns the identity quaternion). The input quaternion must be normalized.

=== <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>. The vector <code>a</code> must be a normalized vector. A positive angle is anti-clockwise if the vector is pointing towards you.

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. A positive angle is anti-clockwise if the ''x'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''y'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''z'' axis is pointing towards you.

<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

2013-01-10T23:10:12Z

PG1: /* rotate */

'''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 array of four numbers, or an [[Oolite JavaScript Reference: Entity|Entity]] (in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used). In specifications, this is represented by arguments typed <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>conjugate</code> ===
{{oolite-method-added|1.77}}
function '''conjugate'''() : Quaternion
Return the conjugate of the quaternion (i.e. the quaternion which when multiplied by the original quaternion returns the identity quaternion). The input quaternion must be normalized.

=== <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>. The vector <code>a</code> must be a normalized vector. A positive angle is anti-clockwise if the vector is pointing towards you.

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. A positive angle is anti-clockwise if the ''x'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''y'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''z'' axis is pointing towards you.

<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

2013-01-10T23:09:20Z

PG1: /* 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 array of four numbers, or an [[Oolite JavaScript Reference: Entity|Entity]] (in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used). In specifications, this is represented by arguments typed <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>conjugate</code> ===
{{oolite-method-added|1.77}}
function '''conjugate'''() : Quaternion
Return the conjugate of the quaternion (i.e. the quaternion which when multiplied by the original quaternion returns the identity quaternion). The input quaternion must be normalized.

=== <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>. The vector <code>a</code> must be a normalized vector. (FIXME: clockwise or anticlockwise?)

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. A positive angle is anti-clockwise if the ''x'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''y'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''z'' axis is pointing towards you.

<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

2013-01-10T23:08:56Z

PG1: /* 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 array of four numbers, or an [[Oolite JavaScript Reference: Entity|Entity]] (in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used). In specifications, this is represented by arguments typed <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>conjugate</code> ===
{{oolite-method-added|1.77}}
function '''conjugate'''() : Quaternion
Return the conjugate of the quaternion (i.e. the quaternion which when multiplied by the original quaternion returns the identity quaternion). The input quaternion must be normalized.

=== <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>. The vector <code>a</code> must be a normalized vector. (FIXME: clockwise or anticlockwise?)

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. A positive angle is anti-clockwise if the ''x'' axis is pointing towards you.

<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. A positive angle is anti-clockwise if the ''y'' axis is pointing towards you.

<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

2013-01-10T23:08:30Z

PG1: /* 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 array of four numbers, or an [[Oolite JavaScript Reference: Entity|Entity]] (in which case the entity’s <code>[[Oolite JavaScript Reference: Entity#orientation|orientation]]</code> is used). In specifications, this is represented by arguments typed <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>conjugate</code> ===
{{oolite-method-added|1.77}}
function '''conjugate'''() : Quaternion
Return the conjugate of the quaternion (i.e. the quaternion which when multiplied by the original quaternion returns the identity quaternion). The input quaternion must be normalized.

=== <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>. The vector <code>a</code> must be a normalized vector. (FIXME: clockwise or anticlockwise?)

=== <code>rotateX</code> ===
function '''rotateX'''(angle : Number) : Quaternion
Returns a quaternion rotated <code>angle</code> radians about the ''x'' axis. A positive angle is anti-clockwise if the ''x'' axis is pointing towards you.

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

Quaternion

2013-01-10T22:29:58Z

PG1: Undo revision 35431 by PG1 (talk)

== Overview ==

A quaternion is a set of four values (W X Y Z) that are used in Oolite to specify a rotation in 3D space. To specify a particular rotation you need to think about the axis about which the rotation is made and the angle or amount by which the model is to be rotated.

For a given axis (x y z) and angle (α), the quaternion representing a rotation of a degrees around the axis from the origin (0,0,0) to (x,y,z) is:

W = cos (0.5 × α)

X = x × sin (0.5 × α)

Y = y × sin (0.5 × α)

Z = z × sin (0.5 × α)

So a rotation of 90 degrees about the z axis (0 0 1) would be:

W = cos 45 ° = 0.707…

X = 0 × sin 45 ° = 0

Y = 0 × sin 45 ° = 0

Z = 1 × sin 45 ° = 0.707…

Now because quaternions are normalised (adjusted so that W × W + X × X + Y × Y + Z × Z = 1) when Oolite reads them in, you can multiply each part of a quaternion by the same value and still have it represent the same angle. So this rotation can also be represented as W = 1, X = 0, Y = 0, Z = 1 (let's use [1 0 0 1] as shorthand).

== Examples ==

=== 90 ° turns about the z-axis ===

Oolite uses quaternions to specify rotations in some parts of [[shipdata.plist]], most notably in the subentities part of an entry, like here in the relevant sub-entity entry for the [[Coriolis station (Oolite)|Coriolis station]]:

Code:
subentities =
(
"arc-detail 0 0 0 1 0 0 0",
"arc-detail 0 0 0 1 0 0 1",
"arc-detail 0 0 0 0 0 0 1"
"arc-detail 0 0 0 1 0 0 -1"
)

The last four numbers after the four 'arc-detail' lines are the W X Y and Z of quaternions representing rotations about the z-axis of 0 degrees, 90 degrees, 180 degrees, and 270 degrees (the first three numbers are the subentity's position relative to the station, in this case all are at the same place at the station's origin).

=== 120 ° turns about the z-axis ===

Similarly, the shipdata of the [[Weeviloid_Hunter|Weeviloid 2]] illustrates how to place sub-entities at 3 equilateral points:

Code:
subentities =
(
"weeviloid2-spine 0 0 0 1 0 0 0",
"weeviloid2-spine 0 0 0 0.5 0 0 0.8660254",
"weeviloid2-spine 0 0 0 0.5 0 0 -0.8660254"
)

Given that the first entry (0 0 0 1 0 0 0) will place the sub-entity at the exact place that the model is situated (0 degrees), the next two lines reproduce it at 120 degrees and 240 degrees.

=== 22.5 ° turns about the z-axis ===

To display 16 sub-entities that join to make a ring, as done in the [[Ringpod]] and [[Torus station|Torus]] shipdata, these are the relevant lines:

Code:
subentities =
(
"torus_pod 0 0 0 1 0 0 0", // 0 degree
"torus_pod 0 0 0 0.9808 0.0 0.0 0.1951", // 22.5 degrees
"torus_pod 0 0 0 0.9239 0.0 0.0 0.3827", // 45 degrees
"torus_pod 0 0 0 0.8315 0.0 0.0 0.5556", / /67.5 degrees
"torus_pod 0 0 0 0.7071 0.0 0.0 0.7071", // 90 degrees
"torus_pod 0 0 0 0.5556 0.0 0.0 0.83110", //112.5 degrees
"torus_pod 0 0 0 0.3827 0.0 0.0 0.9239", // 135 degrees
"torus_pod 0 0 0 0.1951 0.0 0.0 0.9808", // 157.5 degrees
"torus_pod 0 0 0 0 0 0 1", // 180 degrees
"torus_pod 0 0 0 -0.1951 0.0 0.0 0.9808", // 202.5 degrees
"torus_pod 0 0 0 -0.3827 0.0 0.0 0.9239", // 225 degrees
"torus_pod 0 0 0 -0.5556 0.0 0.0 0.83110", // 247.5 degrees
"torus_pod 0 0 0 -0.7071 0.0 0.0 0.7071", // 270 degrees
"torus_pod 0 0 0 -0.8315 0.0 0.0 0.5556", // 292.5 degrees
"torus_pod 0 0 0 -0.9239 0.0 0.0 0.3827", // 315 degrees
"torus_pod 0 0 0 -0.9808 0.0 0.0 0.1951" // 337.5 degrees
)

Again the 0 ° sub-entity will appear with the 0 0 0 1 0 0 0, and the next 15 lines place it at 22.5 °, 45 °, 67.5 °, 90 °, 112.5 °, 135 °, 157.5 °, 180 ° (with 0 0 0 0 0 0 1), 202.5 °, 225 °, 247.5 °, 270 °, 292.5 °, 315 ° and 337.5 °.

=== using Java Script to calculate quaternions ===

Oolite contains a whole set of vector and quaternion methods than can be used for easy manipulating quaternions. To generate a quaternion for a certain rotation around the z-axis we can rotate the identity quaternion around the z-axis with the command:
new Quaternion(1,0,0,0).rotate(new Vector3D(0,0,1), angle)
With this command we can calculate our own quaternion for any rotation around the z-axis, or any other axis when desired. Angle is not in degree but in Math.PI

=== Quaternion calculus ===

To perform one rotation, and then another, one needs to multiply two quaternions together.

Multiplying quaternions isn't commutative: Qa × Qb does not equal Qb × Qa

To multiply Q₁ (w₁ , x₁ , y₁ , z₁ ) by Q₂ (w₂, x₂, y₂, z₂):

W = w₁ × w₂ - x₁ × x₂ - y₁ × y₂ - z₁ × z₂

X = w₁ × x₂ + x₁ × w₂ + y₁ × z₂ - z₁ × y₂

Y = w₁ × y₂ + y₁ × w₂ + z₁ × x₂ - x₁ × z₂

Z = w₁ × z₂ + z₁ × w₂ + x₁ × y₂ - y₁ × x₂

To determine the quaternion for a rotation of α degrees/radians around an axis defined by a vector (x, y, z):

W = cos (0.5 × α)

X = x × sin (0.5 × α)

Y = y × sin (0.5 × α)

Z = z × sin (0.5 × α)

''or'':

W = 1 / tan (0.5 × α)

X = x

Y = y

Z = z

These are equivalent because of the trigonometric identity sin x/cos x = tan x, and the fact that quaternion normalization means that multiplying each component by the same value (in this case, 1 / sin (0.5 × α)) does not affect the resulting orientation.

=== Oolite Specifics ===

Although Quaternions are coordinate system indifferent, Oolite, because it makes use of OpenGL, uses a [http://en.wikipedia.org/wiki/Left-handed_coordinate_system#Orientation_and_handedness left-handed coordinate system]. This means that all positive quaternion rotations about an axis, as discussed in the [[#Overview|Overview]] section above, are anti-clockwise (counter-clockwise) when the axis of rotation is pointing towards you (clockwise if pointing away from you).

Also all Oolite ships and other entities have to be designed with forwards pointing along the z-axis, up along the y-axis and right along the x-axis. These entities have an orientation in space is given by a quaternion (the [[Oolite_JavaScript_Reference:_Entity#orientation|.orientation]] JavaScript property) that describes the transformation from this initial design orientation to the required final orientation.

== See Also ==

* [[Oolite JavaScript Reference: Quaternion]]
* [http://en.wikipedia.org/wiki/Quaternion Wikipedia page on quaternions]
* [http://en.wikipedia.org/wiki/Quaternions_and_spatial_rotation Wikipedia page on quaternions and spatial rotation]
* [http://skal.planet-d.net/demo/matrixfaq.htm The Matrix and Quaternion FAQ]

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

Quaternion

2013-01-10T21:32:50Z

PG1: /* Oolite Specifics */

== Overview ==

A quaternion is a set of four values (W X Y Z) that are used in Oolite to specify a rotation in 3D space. To specify a particular rotation you need to think about the axis about which the rotation is made and the angle or amount by which the model is to be rotated.

For a given axis (x y z) and angle (α), the quaternion representing a rotation of a degrees around the axis from the origin (0,0,0) to (x,y,z) is:

W = cos (0.5 × α)

X = x × sin (0.5 × α)

Y = y × sin (0.5 × α)

Z = z × sin (0.5 × α)

So a rotation of 90 degrees about the z axis (0 0 1) would be:

W = cos 45 ° = 0.707…

X = 0 × sin 45 ° = 0

Y = 0 × sin 45 ° = 0

Z = 1 × sin 45 ° = 0.707…

Now because quaternions are normalised (adjusted so that W × W + X × X + Y × Y + Z × Z = 1) when Oolite reads them in, you can multiply each part of a quaternion by the same value and still have it represent the same angle. So this rotation can also be represented as W = 1, X = 0, Y = 0, Z = 1 (let's use [1 0 0 1] as shorthand).

== Examples ==

=== 90 ° turns about the z-axis ===

Oolite uses quaternions to specify rotations in some parts of [[shipdata.plist]], most notably in the subentities part of an entry, like here in the relevant sub-entity entry for the [[Coriolis station (Oolite)|Coriolis station]]:

Code:
subentities =
(
"arc-detail 0 0 0 1 0 0 0",
"arc-detail 0 0 0 1 0 0 1",
"arc-detail 0 0 0 0 0 0 1"
"arc-detail 0 0 0 1 0 0 -1"
)

The last four numbers after the four 'arc-detail' lines are the W X Y and Z of quaternions representing rotations about the z-axis of 0 degrees, 90 degrees, 180 degrees, and 270 degrees (the first three numbers are the subentity's position relative to the station, in this case all are at the same place at the station's origin).

=== 120 ° turns about the z-axis ===

Similarly, the shipdata of the [[Weeviloid_Hunter|Weeviloid 2]] illustrates how to place sub-entities at 3 equilateral points:

Code:
subentities =
(
"weeviloid2-spine 0 0 0 1 0 0 0",
"weeviloid2-spine 0 0 0 0.5 0 0 0.8660254",
"weeviloid2-spine 0 0 0 0.5 0 0 -0.8660254"
)

Given that the first entry (0 0 0 1 0 0 0) will place the sub-entity at the exact place that the model is situated (0 degrees), the next two lines reproduce it at 120 degrees and 240 degrees.

=== 22.5 ° turns about the z-axis ===

To display 16 sub-entities that join to make a ring, as done in the [[Ringpod]] and [[Torus station|Torus]] shipdata, these are the relevant lines:

Code:
subentities =
(
"torus_pod 0 0 0 1 0 0 0", // 0 degree
"torus_pod 0 0 0 0.9808 0.0 0.0 0.1951", // 22.5 degrees
"torus_pod 0 0 0 0.9239 0.0 0.0 0.3827", // 45 degrees
"torus_pod 0 0 0 0.8315 0.0 0.0 0.5556", / /67.5 degrees
"torus_pod 0 0 0 0.7071 0.0 0.0 0.7071", // 90 degrees
"torus_pod 0 0 0 0.5556 0.0 0.0 0.83110", //112.5 degrees
"torus_pod 0 0 0 0.3827 0.0 0.0 0.9239", // 135 degrees
"torus_pod 0 0 0 0.1951 0.0 0.0 0.9808", // 157.5 degrees
"torus_pod 0 0 0 0 0 0 1", // 180 degrees
"torus_pod 0 0 0 -0.1951 0.0 0.0 0.9808", // 202.5 degrees
"torus_pod 0 0 0 -0.3827 0.0 0.0 0.9239", // 225 degrees
"torus_pod 0 0 0 -0.5556 0.0 0.0 0.83110", // 247.5 degrees
"torus_pod 0 0 0 -0.7071 0.0 0.0 0.7071", // 270 degrees
"torus_pod 0 0 0 -0.8315 0.0 0.0 0.5556", // 292.5 degrees
"torus_pod 0 0 0 -0.9239 0.0 0.0 0.3827", // 315 degrees
"torus_pod 0 0 0 -0.9808 0.0 0.0 0.1951" // 337.5 degrees
)

Again the 0 ° sub-entity will appear with the 0 0 0 1 0 0 0, and the next 15 lines place it at 22.5 °, 45 °, 67.5 °, 90 °, 112.5 °, 135 °, 157.5 °, 180 ° (with 0 0 0 0 0 0 1), 202.5 °, 225 °, 247.5 °, 270 °, 292.5 °, 315 ° and 337.5 °.

=== using Java Script to calculate quaternions ===

Oolite contains a whole set of vector and quaternion methods than can be used for easy manipulating quaternions. To generate a quaternion for a certain rotation around the z-axis we can rotate the identity quaternion around the z-axis with the command:
new Quaternion(1,0,0,0).rotate(new Vector3D(0,0,1), angle)
With this command we can calculate our own quaternion for any rotation around the z-axis, or any other axis when desired. Angle is not in degree but in Math.PI

=== Quaternion calculus ===

To perform one rotation, and then another, one needs to multiply two quaternions together.

Multiplying quaternions isn't commutative: Qa × Qb does not equal Qb × Qa

To multiply Q₁ (w₁ , x₁ , y₁ , z₁ ) by Q₂ (w₂, x₂, y₂, z₂):

W = w₁ × w₂ - x₁ × x₂ - y₁ × y₂ - z₁ × z₂

X = w₁ × x₂ + x₁ × w₂ + y₁ × z₂ - z₁ × y₂

Y = w₁ × y₂ + y₁ × w₂ + z₁ × x₂ - x₁ × z₂

Z = w₁ × z₂ + z₁ × w₂ + x₁ × y₂ - y₁ × x₂

To determine the quaternion for a rotation of α degrees/radians around an axis defined by a vector (x, y, z):

W = cos (0.5 × α)

X = x × sin (0.5 × α)

Y = y × sin (0.5 × α)

Z = z × sin (0.5 × α)

''or'':

W = 1 / tan (0.5 × α)

X = x

Y = y

Z = z

These are equivalent because of the trigonometric identity sin x/cos x = tan x, and the fact that quaternion normalization means that multiplying each component by the same value (in this case, 1 / sin (0.5 × α)) does not affect the resulting orientation.

=== Oolite Specifics ===

Although Quaternions are coordinate system indifferent, Oolite, because it makes use of OpenGL, uses a [http://en.wikipedia.org/wiki/Left-handed_coordinate_system#Orientation_and_handedness left-handed coordinate system]. This means that all positive quaternion rotations about an axis, as discussed in the [[#Overview|Overview]] section above, are clockwise when the axis of rotation is pointing towards you (anti-clockwise if pointing away from you).

Also all Oolite ships and other entities have to be designed with forwards pointing along the z-axis, up along the y-axis and right along the x-axis. These entities have an orientation in space is given by a quaternion (the [[Oolite_JavaScript_Reference:_Entity#orientation|.orientation]] JavaScript property) that describes the transformation from this initial design orientation to the required final orientation.

== See Also ==

* [[Oolite JavaScript Reference: Quaternion]]
* [http://en.wikipedia.org/wiki/Quaternion Wikipedia page on quaternions]
* [http://en.wikipedia.org/wiki/Quaternions_and_spatial_rotation Wikipedia page on quaternions and spatial rotation]
* [http://skal.planet-d.net/demo/matrixfaq.htm The Matrix and Quaternion FAQ]

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

Quaternion

2013-01-10T19:12:12Z

PG1: /* Oolite Specifics */

Quaternion

2013-01-10T19:08:03Z

PG1: Added Oolite Specifics section

== Overview ==

A quaternion is a set of four values (W X Y Z) that are used in Oolite to specify a rotation in 3D space. To specify a particular rotation you need to think about the axis about which the rotation is made and the angle or amount by which the model is to be rotated.

For a given axis (x y z) and angle (α), the quaternion representing a rotation of a degrees around the axis from the origin (0,0,0) to (x,y,z) is:

W = cos (0.5 × α)

X = x × sin (0.5 × α)

Y = y × sin (0.5 × α)

Z = z × sin (0.5 × α)

So a rotation of 90 degrees about the z axis (0 0 1) would be:

W = cos 45 ° = 0.707…

X = 0 × sin 45 ° = 0

Y = 0 × sin 45 ° = 0

Z = 1 × sin 45 ° = 0.707…

Now because quaternions are normalised (adjusted so that W × W + X × X + Y × Y + Z × Z = 1) when Oolite reads them in, you can multiply each part of a quaternion by the same value and still have it represent the same angle. So this rotation can also be represented as W = 1, X = 0, Y = 0, Z = 1 (let's use [1 0 0 1] as shorthand).

== Examples ==

=== 90 ° turns about the z-axis ===

Oolite uses quaternions to specify rotations in some parts of [[shipdata.plist]], most notably in the subentities part of an entry, like here in the relevant sub-entity entry for the [[Coriolis station (Oolite)|Coriolis station]]:

Code:
subentities =
(
"arc-detail 0 0 0 1 0 0 0",
"arc-detail 0 0 0 1 0 0 1",
"arc-detail 0 0 0 0 0 0 1"
"arc-detail 0 0 0 1 0 0 -1"
)

The last four numbers after the four 'arc-detail' lines are the W X Y and Z of quaternions representing rotations about the z-axis of 0 degrees, 90 degrees, 180 degrees, and 270 degrees (the first three numbers are the subentity's position relative to the station, in this case all are at the same place at the station's origin).

=== 120 ° turns about the z-axis ===

Similarly, the shipdata of the [[Weeviloid_Hunter|Weeviloid 2]] illustrates how to place sub-entities at 3 equilateral points:

Code:
subentities =
(
"weeviloid2-spine 0 0 0 1 0 0 0",
"weeviloid2-spine 0 0 0 0.5 0 0 0.8660254",
"weeviloid2-spine 0 0 0 0.5 0 0 -0.8660254"
)

Given that the first entry (0 0 0 1 0 0 0) will place the sub-entity at the exact place that the model is situated (0 degrees), the next two lines reproduce it at 120 degrees and 240 degrees.

=== 22.5 ° turns about the z-axis ===

To display 16 sub-entities that join to make a ring, as done in the [[Ringpod]] and [[Torus station|Torus]] shipdata, these are the relevant lines:

Code:
subentities =
(
"torus_pod 0 0 0 1 0 0 0", // 0 degree
"torus_pod 0 0 0 0.9808 0.0 0.0 0.1951", // 22.5 degrees
"torus_pod 0 0 0 0.9239 0.0 0.0 0.3827", // 45 degrees
"torus_pod 0 0 0 0.8315 0.0 0.0 0.5556", / /67.5 degrees
"torus_pod 0 0 0 0.7071 0.0 0.0 0.7071", // 90 degrees
"torus_pod 0 0 0 0.5556 0.0 0.0 0.83110", //112.5 degrees
"torus_pod 0 0 0 0.3827 0.0 0.0 0.9239", // 135 degrees
"torus_pod 0 0 0 0.1951 0.0 0.0 0.9808", // 157.5 degrees
"torus_pod 0 0 0 0 0 0 1", // 180 degrees
"torus_pod 0 0 0 -0.1951 0.0 0.0 0.9808", // 202.5 degrees
"torus_pod 0 0 0 -0.3827 0.0 0.0 0.9239", // 225 degrees
"torus_pod 0 0 0 -0.5556 0.0 0.0 0.83110", // 247.5 degrees
"torus_pod 0 0 0 -0.7071 0.0 0.0 0.7071", // 270 degrees
"torus_pod 0 0 0 -0.8315 0.0 0.0 0.5556", // 292.5 degrees
"torus_pod 0 0 0 -0.9239 0.0 0.0 0.3827", // 315 degrees
"torus_pod 0 0 0 -0.9808 0.0 0.0 0.1951" // 337.5 degrees
)

Again the 0 ° sub-entity will appear with the 0 0 0 1 0 0 0, and the next 15 lines place it at 22.5 °, 45 °, 67.5 °, 90 °, 112.5 °, 135 °, 157.5 °, 180 ° (with 0 0 0 0 0 0 1), 202.5 °, 225 °, 247.5 °, 270 °, 292.5 °, 315 ° and 337.5 °.

=== using Java Script to calculate quaternions ===

Oolite contains a whole set of vector and quaternion methods than can be used for easy manipulating quaternions. To generate a quaternion for a certain rotation around the z-axis we can rotate the identity quaternion around the z-axis with the command:
new Quaternion(1,0,0,0).rotate(new Vector3D(0,0,1), angle)
With this command we can calculate our own quaternion for any rotation around the z-axis, or any other axis when desired. Angle is not in degree but in Math.PI

=== Quaternion calculus ===

To perform one rotation, and then another, one needs to multiply two quaternions together.

Multiplying quaternions isn't commutative: Qa × Qb does not equal Qb × Qa

To multiply Q₁ (w₁ , x₁ , y₁ , z₁ ) by Q₂ (w₂, x₂, y₂, z₂):

W = w₁ × w₂ - x₁ × x₂ - y₁ × y₂ - z₁ × z₂

X = w₁ × x₂ + x₁ × w₂ + y₁ × z₂ - z₁ × y₂

Y = w₁ × y₂ + y₁ × w₂ + z₁ × x₂ - x₁ × z₂

Z = w₁ × z₂ + z₁ × w₂ + x₁ × y₂ - y₁ × x₂

To determine the quaternion for a rotation of α degrees/radians around an axis defined by a vector (x, y, z):

W = cos (0.5 × α)

X = x × sin (0.5 × α)

Y = y × sin (0.5 × α)

Z = z × sin (0.5 × α)

''or'':

W = 1 / tan (0.5 × α)

X = x

Y = y

Z = z

These are equivalent because of the trigonometric identity sin x/cos x = tan x, and the fact that quaternion normalization means that multiplying each component by the same value (in this case, 1 / sin (0.5 × α)) does not affect the resulting orientation.

=== Oolite Specifics ===

Although Quaternions are coordinate system indifferent, Oolite, because it makes use of OpenGL, uses a [http://en.wikipedia.org/wiki/Left-handed_coordinate_system#Orientation_and_handedness left-handed coordinate system]. This means that all positive quaternion rotations about an axis, as discussed in the [[#Overview|Overview]] section above, are anti-clockwise (counter-clockwise) when the axis of rotation is pointing towards you (clockwise if pointing away from you).

Also all Oolite ships and other entities have to be designed with the forward points along the z-axis, up along the y-axis and right along the x-axis. These entities have an orientation in space is given by a quaternion (the [[Oolite_JavaScript_Reference:_Entity#orientation|.orientation]] Javascript property) that describes the transformation from this initial design orientation to the required final orientation.

== See Also ==

* [[Oolite JavaScript Reference: Quaternion]]
* [http://en.wikipedia.org/wiki/Quaternion Wikipedia page on quaternions]
* [http://en.wikipedia.org/wiki/Quaternions_and_spatial_rotation Wikipedia page on quaternions and spatial rotation]
* [http://skal.planet-d.net/demo/matrixfaq.htm The Matrix and Quaternion FAQ]

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

GalCop Rewards

2012-07-09T23:16:47Z

PG1: Adding emphasis on requirement for other OXP that rewards points in "Earning Reward Points" section.

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. '''You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].'''

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/KvrXtU GalCop_Rewards.1.0.1.oxp.zip]

==Fast Facts==
{{OXPLevel|0|0}}
{{Infobox OXPb| title = GalCop Rewards
|version = 1.0.1
|release = 2012-06-18
|license = CC-by-nc-sa-3.0
|features = Adds GalCop Reward Points
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12061 BB-Link]
}}

{{mechanics-OXP}}

GalCop Rewards

2012-06-18T11:24:52Z

PG1:

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/KvrXtU GalCop_Rewards.1.0.1.oxp.zip]

==Fast Facts==
{{OXPLevel|0|0}}
{{Infobox OXPb| title = GalCop Rewards
|version = 1.0.1
|release = 2012-06-18
|license = CC-by-nc-sa-3.0
|features = Adds GalCop Reward Points
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12061 BB-Link]
}}

{{mechanics-OXP}}

GalCop Rewards

2012-06-18T11:19:54Z

PG1:

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/KvrXtU GalCop_Rewards.1.0.1.oxp.zip]

==Fast Facts==
{{OXPLevel|0|0}}
{{Infobox OXPb| title = GalCop Rewards
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Adds GalCop Reward Points
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12061 BB-Link]
}}

{{mechanics-OXP}}

Safe Docking

2012-06-18T00:15:16Z

PG1:

==Introduction==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born. See [[GalCop Rewards|GalCop Rewards OXP]] for details. Well, you may be wondering what this has to do with this Safe Docking OXP. Poor docking was one of the main issues GalCop had with bad piloting. Safe Docking is GalCop's attempt for rewarding pilots for docking at participating stations in a safe manner and makes use of GalCop Rewards to do this.

==Overview==

With Safe Docking OXP how fast and carefully you dock now determines whether you get rewarded or receive a penalty. Dock too fast and you will be get a penalty (and may be an insult). Dock at an acceptable speed and you may get rewarded with GalCop Reward Points. Generally the slower the better, but be warned, go too slowly or scrape your ship's hull and the station's Dockmaster will not be pleased. If you only docked in an "Ok" fashion you may not get a message at all.

Only manual docking counts. If you dock using a Docking Computer (both automatic or Instant docking) you will not be rewarded. Also cheating by using the Docking Computer to get you almost there and turning it off and finishing docking manually is also detected and will not count as manual docking.

'''The following table shows the speeds and their results:'''
{| class="wikitable"
!Speed Range
!Rating
!Reward
!Penalty
|-
|>=0m/s and <25m/s
|Too Slow
|
|Lose 5 Credits
|-
|>=25m/s and <50m/s
|Excellent
|10 Reward Points
|
|-
|>=50m/s and <75m/s
|Very Good
|5 Reward Points
|
|-
|>=75m/s and <100m/s
|Good
|1 Reward Points
|
|-
|>=100m/s and <125m/s
|Ok
|
|
|-
|>=125m/s and <225m/s
|Poor
|
|Lose 1 Reward Points and fined 20 Credits
|-
|>=225m/s and <300m/s
|Reckless
|
|Lose 5 Reward Points and fined 40 Credits
|-
|>=300m/s and <400m/s
|Dangerous
|
|Lose all Reward Points and fined 100 Credits
|-
|>=400m/s and <550m/s
|Very Dangerous
|
|Lose all Reward Points and fined 500 Credits
|-
|>=550m/s
|Criminal
|
|Lose all Reward Points, fined 1000 Credits and gain 5 Credits bounty
|-
|<225m/s and scraped ship during docking
|Collided
|
|Lose 2 Reward Points and fined 25 Credits
|}

The only variation from the above is if you are under attack '''AND''' at low energy. In this situation you will let off any penalty. Being under attack is defined by being attacked by at least one non-police ship (by laser or missile) and each attacking ship still has you as its target. (Still targeted is checked every 2 seconds.) If you have been attacked by a cloaked ship within the last 10 seconds then this also counts as under attack. Low Energy is when your energy is less than 128 which is less than 2 full bars on a ship's HUD.

All fines are reduced not take you below 100 credits. So if you are below 100 credits you won't be fined.

If you re-visit the same station in the scheme within the last hour (in-game hours) then you do not get any Rewards Points. The Dockmaster will let you know if this is the case. Penalties for bad docking will still apply though.

==Participating Stations==

All system Main Stations are in the scheme but also when you enter the station aegis you will get a message telling you that the station is in the scheme e.g. “The Dockmaster would like to let you know that Lave Orbital Station is a participant in the Safe Docking Rewards Scheme.”

Any other station or carrier you will receive an equivalent message if you enter the region within the aegis distance around them (2x scanner radius). In Oolite aegis only normally applies to the main station but it is “reproduced” for these other stations.

==My Speed==

If you install OXPConfig OXP version 2.0.10 or higher then you can use that to modify the OXP parameter that adds to a station's arrival message a notification of your arrival speed. This parameter is off by default.

==Docking Clearance==

If docking clearance requirement is turned on (usually by installing the Docking Clearance OXP) then docking without clearance means you get no Reward Points added for good docking. Penalties for bad docking will still apply though.

==Dependencies==

{{OXPConfig-small}}
[[GalCop Rewards|GalCop Rewards OXP]]

Optional: [[OXPConfig|OXPConfig OXP version 2.0.10 or higher]]

Optional: [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance]]

==Download==
[http://bit.ly/M9ZDfu Safe_Docking.1.0.0.oxp.zip]

==Fast Facts==
{{OXPLevel|0|1}}
{{Infobox OXPb| title = Safe Docking
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Manual Docking Behaviour
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12062 BB-Link]
}}

{{mechanics-OXP}}

GalCop Rewards

2012-06-18T00:08:10Z

PG1:

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/LsHkkq GalCop_Rewards.1.0.0.oxp.zip]

==Fast Facts==
{{OXPLevel|0|0}}
{{Infobox OXPb| title = GalCop Rewards
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Adds GalCop Reward Points
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12061 BB-Link]
}}

{{mechanics-OXP}}

Safe Docking

2012-06-18T00:07:48Z

PG1:

==Introduction==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born. See [[GalCop Rewards|GalCop Rewards OXP]] for details. Well, you may be wondering what this has to do with this Safe Docking OXP. Poor docking was one of the main issues GalCop had with bad piloting. Safe Docking is GalCop's attempt for rewarding pilots for docking at participating stations in a safe manner and makes use of GalCop Rewards to do this.

==Overview==

With Safe Docking OXP how fast and carefully you dock now determines whether you get rewarded or receive a penalty. Dock too fast and you will be get a penalty (and may be an insult). Dock at an acceptable speed and you may get rewarded with GalCop Reward Points. Generally the slower the better, but be warned, go too slowly or scrape your ship's hull and the station's Dockmaster will not be pleased. If you only docked in an "Ok" fashion you may not get a message at all.

Only manual docking counts. If you dock using a Docking Computer (both automatic or Instant docking) you will not be rewarded. Also cheating by using the Docking Computer to get you almost there and turning it off and finishing docking manually is also detected and will not count as manual docking.

'''The following table shows the speeds and their results:'''
{| class="wikitable"
!Speed Range
!Rating
!Reward
!Penalty
|-
|>=0m/s and <25m/s
|Too Slow
|
|Lose 5 Credits
|-
|>=25m/s and <50m/s
|Excellent
|10 Reward Points
|
|-
|>=50m/s and <75m/s
|Very Good
|5 Reward Points
|
|-
|>=75m/s and <100m/s
|Good
|1 Reward Points
|
|-
|>=100m/s and <125m/s
|Ok
|
|
|-
|>=125m/s and <225m/s
|Poor
|
|Lose 1 Reward Points and fined 20 Credits
|-
|>=225m/s and <300m/s
|Reckless
|
|Lose 5 Reward Points and fined 40 Credits
|-
|>=300m/s and <400m/s
|Dangerous
|
|Lose all Reward Points and fined 100 Credits
|-
|>=400m/s and <550m/s
|Very Dangerous
|
|Lose all Reward Points and fined 500 Credits
|-
|>=550m/s
|Criminal
|
|Lose all Reward Points, fined 1000 Credits and gain 5 Credits bounty
|-
|<225m/s and scraped ship during docking
|Collided
|
|Lose 2 Reward Points and fined 25 Credits
|}

The only variation from the above is if you are under attack '''AND''' at low energy. In this situation you will let off any penalty. Being under attack is defined by being attacked by at least one non-police ship (by laser or missile) and each attacking ship still has you as its target. (Still targeted is checked every 2 seconds.) If you have been attacked by a cloaked ship within the last 10 seconds then this also counts as under attack. Low Energy is when your energy is less than 128 which is less than 2 full bars on a ship's HUD.

All fines are reduced not take you below 100 credits. So if you are below 100 credits you won't be fined.

If you re-visit the same station in the scheme within the last hour (in-game hours) then you do not get any Rewards Points. The Dockmaster will let you know if this is the case. Penalties for bad docking will still apply though.

==Participating Stations==

All system Main Stations are in the scheme but also when you enter the station aegis you will get a message telling you that the station is in the scheme e.g. “The Dockmaster would like to let you know that Lave Orbital Station is a participant in the Safe Docking Rewards Scheme.”

Any other station or carrier you will receive an equivalent message if you enter the region within the aegis distance around them (2x scanner radius). In Oolite aegis only normally applies to the main station but it is “reproduced” for these other stations.

==My Speed==

If you install OXPConfig OXP version 2.0.10 or higher then you can use that to modify the OXP parameter that adds to a station's arrival message a notification of your arrival speed. This parameter is off by default.

==Docking Clearance==

If docking clearance requirement is turned on (usually by installing the Docking Clearance OXP) then docking without clearance means you get no Reward Points added for good docking. Penalties for bad docking will still apply though.

==Dependencies==

{{OXPConfig-small}}
[[GalCop Rewards|GalCop Rewards OXP]]

Optional: [[OXPConfig|OXPConfig OXP version 2.0.10 or higher]]

==Download==
[http://bit.ly/M9ZDfu Safe_Docking.1.0.0.oxp.zip]

==Fast Facts==
{{OXPLevel|0|1}}
{{Infobox OXPb| title = Safe Docking
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Manual Docking Behaviour
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12062 BB-Link]
}}

{{mechanics-OXP}}

OXP List

2012-06-18T00:01:24Z

PG1:

__NOTOC__
== OXP Categories ==
{| class="wikitable" width="100%" style="border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #ffffff; table-layout: fixed; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"
|-
! scope="col" width="70px" style="margin: 0px; padding: 0px; border-width: 1px; border-style: solid; border-color: #ffffff; background-color: #e7e7ff; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;" |Category
! scope="col" style="margin: 0px; padding: 0px; border-width: 1px; border-style: solid; border-color: #ffffff; background-color: #e7e7ff; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;" |Description of OXP Category
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Activities_OXPs|Activities]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Allow Commanders to carry out a new activity or task eg. racing, gas giant skimming, taking out loans
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Dockables_OXPs|Dockables]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Add new objects that the player can dock with eg. carriers, space bars, casinos, fuel stations. Also, see [[Oolite Stations]]
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Ambience_OXPs|Ambience]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Change or add to the scenery, visuals or sound effects eg. planet skins, add new planets/moons to systems, move suns further away, dim nebulae, add monuments
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Equipment_OXPs|Equipment]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Buy upgrades for your ship excluding weapons
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Mechanics_OXPs|Mechanics]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Change the game play in a specific way eg. alter market mechanics, add more pirates
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:HUDs_OXPs|HUDs]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Modifications of your dials, gauges and other read-outs
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Missions_OXPs|Missions]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|New missions for Commanders to undertake. For more information, see [[Oolite Missions]]
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Retextures_OXPs|Retextures]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Retexture existing objects, either by replacing or adding variations, but without adding objects that did not exist before
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Ships_OXPs|Ships]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|New ships, except dockable ships. Also, see [[Oolite Ships]]
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Systems_OXPs|Systems]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Alter multiple star systems in a number of ways eg. combinations of changing main station and local police ships, adding new stations, ships, activities, missions
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Weapons_OXPs|Weapons]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|Addons for your ship for blowing up the baddies
|-
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"|[[:Category:Misc_OXPs|Misc]]
|style="margin: 0px; padding: 0px; border-style: solid; border-width: 1px; border-color: #ffffff; background-color:#f0f0ff; font-size: 12px; vertical-align: top; text-align: left; white-space:normal; word-wrap: break-word;"|OXPs that don't fit into the other categories eg. debug consoles, internationalisations, config mechanisms, demo OXPs
|}
OXP authors: if you are unsure how to categorise your OXP or if you wish to update the details of an OXP for an author who has disappeared, please seek advice on the [http://www.aegidian.org/bb/viewforum.php?f=4 Expansion Pack Forum] before proceeding. Please put your OXP in one category only. You can edit the section below to add your OXP. 

== Sortable Table of OXPs ==
The following table is optimized for a horizontal screen resolution of at least 1280px so that all OXP descriptions fit on one line.
{| class="wikitable" width="100%" style="border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #ffffff; table-layout: fixed; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;"
|-
! scope="col" style="border-width: 1px; border-style: solid; border-color: #ffffff; background-color: #e7e7ff; vertical-align: top; text-align: left; overflow: hidden; white-space: nowrap;" |The "C" column indicates compatibility with Oolite 1.76.1:

"Y"=compatible, "Y*"=compatible (with caveats), "N"=incompatible, "N*"=incompatible (but a fix is described), blank=unknown/untested.
|}


{{OXPListTableHeader}}

{{OXPSortableTableRow
|cat=Retextures
|desc=[[Accessories OXP|Accessories]] replaces the textures of all Stations and non-ship objects in Oolite with a more detailed and realistic look
|aut=[[User:Smivs|Smivs]]
|date=2012-03-05
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Accipiter]] is the market entry from Xeceesian shipyards, a strong & fast all purpose vessel for experienced commanders
|aut=[[User:CaptSolo|CaptSolo]]
|con=Staer9, Griff
|date=2011-05-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Aegidian%27s Specials]] adds the powerful [[Mussurana]], the [[Asp (Oolite)#Notable features|Asp Mark II Special]], and a new cargo canister
|aut=[[User:Aegidian|Aegidian]]
|date=2009-07-27
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Aegidian%27s X-Ships]] adds [[Python ET Special]]s, [[Cobra Mk.2 (Oolite)|Cobra Mk II]]s, [[Taipan]]s, [[Asp (Oolite)#Notable features|Asp Mark II Special]]s, and [[Sidewinder (Oolite)#Notable features|Sidewinder Special]]s
|aut=[[User:Aegidian|Aegidian]]
|date=2009-04-29
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[AI Trading Assistant]] monitors cargo trading, and immediately warns of unprofitable mistakes
|aut=Wildeblood
|con=Capt. Murphy
|date=2012-05-17
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Pirate Clan Blitzspears|Amen Brick's Pirate Clan One: The Blitzspears]] adds the [[Assassin Blitzspear|Assassin]], the [[Hoodlum]], the [[Scoundrel]], and the [[Spiv]]
|aut=[[User:Amen Brick|Amen Brick]]
|date=2008-06-30}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Amiga Replacement Sounds]] is based on the sound set used in the Amiga version of the original Elite
|aut=EAGLE 5
|date=2006-03-22
|work=Y}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[Anarchies OXP|Anarchies]] overhauls legal ratings and spices up anarchies with [[Hacker Outpost]]s, [[Salvage Gang]]s, special stations & ships
|aut=[[User:Commander McLane|Commander McLane]]
|con=Killer Wolf, Griff, Cdr. Wyvern, Murgh, Aegidian, 8-Bit Apocalypse
|date=2012-04-02
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9462 Another HUD] is based on Killer Wolf's Generic HUD
|aut=NorthenderPNE
|date=2011-03-18
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Aphid]] adds the stylish Aphid Escort Service
|aut=8-Bit Apocalypse
|date=2005-01-02
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[APRIL OXP|APRIL]] is an expandable in-flight pylon reloading piece of equipment.
|aut=[[User:Thargoid|Thargoid]]
|date=2012-04-19
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Aquatics OXP|Aquatics]] adds the Aquarian Shipbuilding Corporation of Aqualina, G3 along with its ships and a mission
|aut=[[User:Thargoid|Thargoid]]
|date=2012-01-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Armoured Transport Type 1]] adds Gaundlet's [[Gaundlet Armoured Transport Type1|Armoured Transport Type 1]] and [[Gaundlet Armoured Escort Viper|Armoured Escort Viper]] that ferry valuables
|aut=[[User:Arexack|Arexack Heretic]]
|date=2005-12-28
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Armoury OXP|Armoury]] adds AMS, captured Thargons, drones, probes, a missile rack, some bombs, and the missile machine
|aut=[[User:Thargoid|Thargoid]]
|date=2012-03-16
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[The Assassins Guild OXP|Assassins Guild]] adds 21 missions involving murder to order in Galaxy 7
|aut=[[User:LittleBear|Littlebear]]
|date=2012-04-02
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Asteroid Storm]] adds different types of asteroids & a mission where a station in G1 is threatened by a large asteroid strike
|aut=[[User:LittleBear|Littlebear]], Charlie
|date=2012-05-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Aurora]] adds huge passenger ships for the wealthiest in society
|aut=[[User:Pagroove|pagroove]]
|con=Griff, Thargoid
|date=2010-11-10
|work=Y*}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=12008 Autodock] allows the player to authorise the main station to pilot his ship into the hangar on remote control for a fee when no docking computer is installed.
|aut=CommonSenseOTB
|date=2012-06-02
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://www.mediafire.com/?fnc65em7uh5un1d Auto ECM] fires the ECM once when a missile is fired at the player's ship. See the [http://aegidian.org/bb/viewtopic.php?p=138124#p138124 BB] for more info
|aut=Switeck
|date=2011-05-01
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Auto eject OXP|Auto Eject]] ejects your escape pod automatically when your energy becomes too low
|aut=[[User:Commander McLane|Commander McLane]]
|date=2010-06-16
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Automatic Chaff System]] provides an enhanced chaff-based missile countermeasure system
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2010-06-21
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Auto_Skim_OXP|Auto Skim]] gives the player ship an AI to automatically sun skim.
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=3171 Okti]
|date=2011-07-31
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Baakili Far Trader]] adds a dockable alien ship
|aut=[[User:Zieman|Zieman]]
|date=2010-09-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Bandersnatch]] adds a pirate capital vessel armed with 4 x fore lasers
|aut=[[User:Flying Circus|Flying_Circus]]
|date=2009-11-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11857 Battle Damage] Improved immersive experience by adding hull damage when you take un-shielded laser fire.
|aut=[[User:Smivs|Smivs]]
|date=2012-04-30
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Beer Cooler]] allows you to fit your ship with a beer cooler
|aut=[[User:Maik|Maik]]
|date=2010-08-11
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Behemoth]] adds a dockable Navy cruiser carrying [[Navy Asp]]s and [[Navy Viper]]s
|aut=[[User:Aegidian|Aegidian]]
|con=Eric Walch
|date=2011-01-10
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Behemoth Spacewar]] adds intelligence to the Behemoth and brings a combat with Thargoids
|aut=[[User:Eric Walch|Eric Walch]]
|date=2012-03-31
|work=}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[BGS|BGS - Background Set]] framework for images, sounds and ambient music
|aut=[[User:Svengali|Svengali]]
|con=Pagroove, PhantorGorth
|date=2012-05-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11890 BigBlimpy] It's a big balloon. Carries big cargo, or display signs.
|aut=mandoman
|date=2012-04-28
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[BigShips OXP|Big Ships]] ensures that large ships do not dock and controls population of systems with them
|aut=[[User:Thargoid|Thargoid]]
|con=Eric Walch
|date=2009-11-24
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Black Monk Monastery]] offers loans in advanced systems and adds the [[Black Monk Gunship]] to persecute defaulters
|aut=[[User:LittleBear|Littlebear]]
|date=2010-06-14
|work=}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[BlackjacksBullion OXP|Blackjack's Bullion]] starts in galaxy 2 at Telace as Commander Blackjack arrives via escape pod
|aut=[[User:Rustybolts|Rustybolts]]
|date=2012-06-09
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[BlOomberg Markets]] varies the in-game economy by generating random events that affect commodity prices
|aut=[[User:Ramirez|Ramirez]]
|date=2011-10-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Boomslang]] adds a mid-range multi-role ship. Used by pirates and traders alike
|aut=milinks, [[User:Jar|Jar]]
|date=2008-09-07
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Bounty Scanner]] adds bounty details (if any) to the targeting lock-box display when locked onto other ships
|aut=[[User:Frame|Frame]]
|date=2010-07-02
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[BountyStatus OXP|Bounty Status]] displays your current bounty (and your legal status) on the F5 manifest screen
|aut=[[User:Thargoid|Thargoid]]
|date=2011-05-08
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Breakable_'Standard'_Equipment_OXPs|Breakable 'Standard' Equipment]] can make standard equipment like Shields, HUD, Engines etc damageable in combat
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2012-05-05
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Bulk Haulers]] adds the [[Lynx Bulk Carrier (Oolite)|Lynx Bulk Carrier]], the [[Long Range Cruiser (Oolite)|Long Range Cruiser]], the [[Bulk Hauler]], and the [[Super Bulk Hauler]]
|aut=[[User:ADCK|ADCK]]
|con=Aegidian, pagroove
|date=2010-04-07
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[BuoyRepair|Buoy Repair]] adds a [[Buoy Repair Facility]] and related ships to repair defect or destroyed nav-beacons
|aut=[[User:Eric Walch|Eric Walch]]
|con=Svengali, Murgh, Zieman
|date=2012-03-19
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[[Cabal Common Library]] is a collection of snippets and helpers for OXPs
|aut=[[User:Svengali|Svengali]]
|con=Cdr. Cheyd, PhantorGorth
|date=2012-05-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Caduceus]] adds the very expensive (and deadly) Caduceus
|aut=[[User:ClymAngus|ClymAngus]]
|con=Cdr. Wyvern, another_commander, Eric Walch, Thargoid
|date=2010-12-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Capisastra]] adds [[Capisastra Defender]]s, [[Capisastra Hauler]]s, and [[Capisastra Warrior]]s
|aut=[[User:Selezen|Selezen]]
|date=2006-01-12}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Captain Berf Engineer]] adds a voice for crew members
|aut=[[User:Captain Berf|Captain Berf]]
|date=2009-12-26
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Captain Berf Pilot]] adds a voice for crew members
|aut=[[User:Captain Berf|Captain Berf]]
|date=2009-12-26
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Captain Berf Pilot Alien]] adds a voice for crew members
|aut=[[User:Captain Berf|Captain Berf]]
|date=2009-12-26
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Captain Berf Tactical Officer]] adds a voice for crew members
|aut=[[User:Captain Berf|Captain Berf]]
|date=2009-12-26
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Cargo Shepherd OXP|Cargo Shepherd]] attracts cargo pods and holds them until you can scoop them, also includes a beacon
|aut=[[User:Thargoid|Thargoid]]
|date=2011-04-07
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Cargo_Wreck_Teaser_OXP|Cargo Wreck Teaser]] adds alternative cargo pods to the system.
|aut=[[User:Arexack|Arexack Heretic]]
|date=2012-02-11
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[CB-HUD Mark II]] features a HUD that changes based on installed equipment. See the [http://aegidian.org/bb/viewtopic.php?p=141035#p141035 BB post] for more information
|aut=Captain Beatnik
|date=2011-09-25
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11502 CCR-HUD] is the stand-alone version of the Coluber Red Racer HUD
|aut=Captain Beatnik
|date=2012-01-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Chopped Cobra]] adds a chopped version of Griff's Cobra and also includes Enforcer and S9 variants by Smivs.
|aut=[[User:Staer9|Staer9]]
|con=Smivs
|date=2011-07-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Chupacabra]] is a bird-like ship featuring the ChupaCabraHUD
|aut=[[User:Staer9|Staer9]]
|date=2011-11-17
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[ChupacabraHUD]] has central curved bar gauges, custom missile displays and shield capacitor gauges
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-10-26
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Clippers]] Long-legged variants of the Python and Boa 2, with new features! Replaces Boa Clipper OXP.
|aut=[[User:Smivs|Smivs]]
|date=2012-06-09
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11678 Cloak Repair] Allows a damaged Cloaking Device to be replaced at TL15 systems.
|aut=[[User:Smivs|Smivs]]
|date=2012-02-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9157 Cobra AC] is a faithful reproduction of the Cobra on the cover of the Dark Wheel novella with improved specs
|aut=dertien
|date=2011-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Cobra Clipper SAR]] adds a custom Cobra Mk III to rescue stranded Commanders
|aut=[[User:Murgh|Murgh]]
|date=2010-04-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Cobra III NjX]] adds a faster, tougher variation on the Classic Cobra Mk III
|aut=[[User:Selezen|Selezen]]
|date=2006-08-10
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Cobra 3.5]] adds the Cobra Mk 3.5, a slightly faster and tougher variant with a reduced cargo bay
|aut=[[User:Aegidian|Aegidian]]
|date=2006-12-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Cobra Mark III-XT]] Cobra3 with revamped architecture and upgraded systems to boost performance
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-07-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.purgatori.net/cobra4.htm Cobra MkIV] is [[Isis Interstellar]]'s successor to the Cobra MkIII, available in trader and fighter variants
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2010-11-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11974 Colonial Viper Mark 1] adds a single seater fighter from GalTech Industries Corporation
|aut=[[User:Shipbuilder|Shipbuilder]]
|date=2012-05-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11206 Coluber Ships] adds the [[Coluber Blue Racer|Blue Racer]], a medium cargo ship, and the Red Racer, a fast, heavy, long-range fighter
|aut=Captain Beatnik
|date=2011-12-17
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[CombatHUD|Combat HUD]] A stylish, logically arranged HUD designed to give clear information during combat.
|aut=[[User:Smivs|Smivs]]
|date=2012-01-10
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[OosoundsCombined OXP|Combined Murgh, Wiggy & xaotik's sounds]] combines the 3 available packs from Murgh, Wiggy and xaotik
|aut=[[User:Eric Walch|Eric Walch]]
|con=Murgh, Wiggy, xaotik
|date=2009-09-13
|work=Y}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[Commies]] Adds [[Astro Mines]], [[CZGF|Factories]], [[SLAPU|Production Units]], [[Worker%27s Commuter|Commuters]] & special police ships to Communist systems
|aut=[[User:Dr. Nil|Dr. Nil]]
|con=Ramirez, Murgh, johnsmith, HueijRevisited
|date=2010-05-22
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[CompactHUD|Compact HUD]] provides an alternative HUD with a clean look
|aut=[[User:Aegidian|Aegidian]]
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Condor]] adds a very powerful police and Navy Cruiser
|aut=Charlie
|con=Eric Walch
|date=2010-10-24
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Console HUD]] Azure themed semi-transparent HUD with balanced array of indicators
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-12-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Contractor ZZ1 | Contractor Mk II]] Very fast combat 'stealth' ship. Appears in-game as a Bounty-hunter and rarely as Pirate. Buyable
|aut=[[User:Smivs|Smivs]]
|date=2012-01-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Copperhead]] Redux of core ship in Archimedes Elite slightly modified. NPC and player buyable
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-05-05
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Coyote's_Run|Coyote's Run]] brings [[:User:El Viejo|El Viejo]]'s novella [[:Category:Oolite stories#El Viejo|Coyote]] to life as an exciting mission OXP
|aut=Okti
|con=El Viejo, Smivs, Wyvern
|date=2011-12-16
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Croydon Starsoarer]] adds a ship that is similar to the Asp in specification
|aut=[[User:Simon B|SimonB]]
|con=pagroove
|date=2010-05-08
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11129 Cruzer] adds ace's Cruzer
|aut=ace\56
|con=Staer9
|date=2011-11-08
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[CustomSounds OXP|CustomSounds]] replaces/adds 40+ sounds, featuring music & extensive use of calm female computer voice for warnings
|aut=milinks
|date=2006-12-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10842 Dark Rainbow] is an 'uberfied' and tweaked version of the [[Caduceus]] with more turrets, pylons, and cargo
|aut=sdrubble
|date=2011-09-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[DWCobra|Dark Wheel Cobra]] is a custom Cobra Mk III model, as seen on the cover of the Elite Manual
|aut=[[User:Ramon|Ramon]]
|date=2006-11-23
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Darkspace]] removes the nebula from the sky and limits the number of stars visible to improve game performance
|aut=[[User:Gimi|Gimi]]
|date=2011-12-07
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[[Debug OXP]] is a special OXP that enables JavaScript console support in test releases of Oolite (1.70 and later)
|aut=[[User:Ahruman|Ahruman]]
|date=2011-12-16
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[http://deephorizonindustries.com/Gas_Giant_Skimming.html Deep Horizon - Gas Giants Skimming] allows to skim gas giants to refuel a ship or mine them for rare minerals
|aut=[[User:Cmd. Cheyd|Cdr. Cheyd]]
|date=2010-07-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://deephorizonindustries.com/Lights_Down.html Deep Horizon - Lights Down] lowers ambient light within system to give more natural feel to planets and ships
|aut=[[User:Cmd. Cheyd|Cdr. Cheyd]]
|date=2010-07-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://deephorizonindustries.com/Nav_Buoy.html Deep Horizon - Nav Buoy 1.0] replaces Witchpoint, Station, and other Nav Buoys with a new model
|aut=[[User:Cmd. Cheyd|Cdr. Cheyd]]
|date=2011-07-04
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://deephorizonindustries.com/Pirate_Ambushes.html Deep Horizon - Pirate Ambushes] adds pirates that ambush the player upon exit from witchspace
|aut=[[User:Cmd. Cheyd|Cdr. Cheyd]]
|date=2010-07-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://deephorizonindustries.com/DH-Systems.html Deep Horizon - Systems] textures the main planet of a system as well as adding moons and additional planets
|aut=[[User:Cmd. Cheyd|Cdr. Cheyd]]
|date=2010-07-06
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Deep Space Dredger]] adds dockable Space Dredgers, defended by [[Sabre]] fighters, and a missile to salvage derelict ships
|aut=[[User:Sabre|Sabre]]
|date=2011-01-10
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[DeepSpacePirates|Deep Space Pirates]] adds pirates and asteroids outside the space lanes
|aut=[[User:Eric Walch|Eric Walch]]
|date=2010-01-04
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Deepspace Ships#Deepspace HUDs|Deepspace HUD]] is an alternative HUD with two versions
|aut=DeepSpace
|date=2010-02-14
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Deepspace Ships]] replaces the default ships with new textures
|aut=DeepSpace
|date=2010-02-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Delightful Docking]] Improved docking experience. Slower stations. View the station when queueing. Better music.
|aut=[[User:Smivs|Smivs]]
|date=2012-02-20
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Deposed OXP|Deposed]] is a series of missions set in Galaxy 4 for an experienced Commander
|aut=[[User:Cmdr. Wombat|Cdr. Wombat]]
|con=Commander McLane, Eric Walch
|date=2009-03-28
|work=Y}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[Dictators OXP|Dictators]] adds a range of ships and stations to each dictatorship and offers new trading opportunities to players
|aut=[[User:Ramirez|Ramirez]]
|date=2011-07-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Diso OXP|Diso]] adds extra planets and stations to the Diso system in Galaxy 1
|aut=[[User:Murgh|Murgh]]
|con=Eric Walch
|date=2010-11-02
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Display reputation OXP|Display Reputation]] lets you know your current reputations in the passenger ferrying and the cargo contract market
|aut=[[User:Commander McLane|Commander McLane]]
|date=2010-03-27
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance]] enables the docking clearance protocol for all stations
|aut=[[User:Eric Walch|Eric Walch]]
|date=2008-12-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Docklights OXP|Docklights]] adds a trail of green docking lights to tech 3+ main stations, which turn red on station launches
|aut=[[User:Thargoid|Thargoid]]
|date=2012-06-05
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Griff Industries|Dodo Stations]] adds new textures for Dodecahedron stations
|aut=[[User:Griff|Griff]], [[User:CaptKev|CaptKev]]
|date=2010-05-18
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Dr HUD OXP|Dr HUD]] is an alternative HUD
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2006-12-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Dragon|Dragon Assault Craft]] adds a heavy combat ship, and the Military Smart Missile, an improved hard head
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2008-11-26
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Dragon#Download|Dragon Military Missile]] adds an enhanced hardhead, seeks priority targets when ECM'd
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2008-11-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.mediafire.com/?rllzzcbkwgm Dragonfly/Firefly S.T] adds [[Dragonfly S.T]] & much faster [[Firefly S.T]]. Ideal small fast ships for pirates or bounty hunters
|aut=[[User:Rustybolts|Rustybolts]]
|date=2009-10-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Eagle Mk II]] adds the cheap Eagle Mk II escort vessel in several different versions, including an enhanced SE
|aut=[[User:Selezen|Selezen]]
|date=2006-03-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[ADCK%27s Eagles|Eagles Mk I to IV]] adds four Eagle Long Range Fighters to the game
|aut=[[User:ADCK|ADCK]]
|date=2010-04-07
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11935 Elbereth] Large, unusual cargo hauler. Lights up pretty.
|aut=mandoman
|date=2012-05-10
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[https://www.box.com/s/6470a1bcc4fce34919db EnergyBombfor1.77.oxp] makes the Energy Bomb available on 'unrestricted play' mode in Oolite 1.77+ (Trunk/Nightly)
|aut=[[User:Capt. Murphy|Capt. Murphy]]
|date=2012-04-24
|work=N*}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Energy Equipment OXP|Energy Equipment]] adds a pylon-mounted automatically triggered top-up for when the juice runs low
|aut=[[User:Thargoid|Thargoid]]
|date=2010-03-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Enhanced_Misjump_OXP|Enhanced Misjump]] changes the effect of the jump tunnel when having a misjump
|aut=[[User:cim|cim]]
|date=2011-12-18
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Escape Pod Locator OXP|Escape Pod Locator v1.4.1]] is a piece of equipment to allow tracking of escape pods in system
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2012-06-05
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Escort Contracts OXP|Escort Contracts v1.5.6]] allows players to enter into short-term escort contracts with NPC lone wolf traders
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2012-05-07
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[ETT Homing Beacon]] marks a position in space by deploying a pylon-mounted beacon
|aut=Twisted
|con=Lone_Wolf
|date=2011-04-04
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Executive SpaceWays]] adds [[Delta Long-Range Escort|Delta]]/[[Gemini Escort|Gemini]] Escorts, [[Starseeker Personal Shuttle|Starseeker]]/[[Trident Executive Shuttle|Trident Exec]] Shuttles, [[Strelka Cruise Liner]]s
|aut=[[User:Ramirez|Ramirez]]
|date=2010-06-19
|work=}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Explorers' Club OXP|Explorers' Club]] v1.3.2 keeps a record of the systems you have visited and gives you an explorer rank
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2012-03-05
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[ExtraFuelTanks]] Re-fillable extra fuel tanks fitted inside your ship. 1LY Reserve or 3LY Auxiliary tanks available.
|aut=[[User:Smivs|Smivs]]
|date=2012-04-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.box.net/shared/moreq536ht#/shared/moreq536ht/1/71484311/786362645/1 Extra Thargoids] adds some types of Thargoid ship, each of which packs surprises.
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=2628 UK_Eliter]
|date=2012-06-01
|work=Y}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[Factions OXP|Factions]] from anarchy, feudal, dictatorship & communist systems meet in multi-government systems and start fighting
|aut= m4r35n357
|date=2012-04-05
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Famous Planets OXP|Famous Planets]] adds unique textures, new descriptions, and theme tunes for many planets in G1 and G2
|aut=[[User:Pagroove|pagroove]]
|con=Cdr. Cheyd, Stromboli, Pangloss, CaptKev, Drew Wagar, Thargoid, Svengali, Lestradae, UK Eliter
|date=2010-09-30
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Famous Planets Liners OXP|Famous Planets Liners]] adds Spaceway Liners on the 4 spaceways from Lave to Zadies
|aut=[[User:Pagroove|pagroove]]
|con=Ramirez, Presti70, Thargoid
|date=2009-03-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Far Arm ships|Far Arm Ships]] adds [[Far Arm Sunracer|Sunracer]]s, [[Far Arm Scow|Scow]]s, [[Far Arm Tanker|Tanker]]s, [[Far Arm Corsair|Corsair]]s, [[Far Arm Dart|Dart]]s, [[Far Arm Hunter|Hunter]]s, [[Far Arm Cruiser|Cruiser]]s, [[Far Arm Titan|Titan]]s, [[Far Arm Manchi Vulture|Vulture]]s, and [[Far Arm Manchi Wasp|Wasp]]s
|aut=[[User:Zieman|Zieman]]
|date=2010-10-02
|work=Y*}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Far Star Murderer]] adds a mid-range fighter / trader, with a fair sized cargo bay
|aut=8-Bit Apocalypse
|con=Svengali
|date=2011-11-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Far Sun OXP|Far Sun]] places suns further away from the planet than standard Oolite
|aut=[[User:Kaks|Kaks]]
|date=2010-05-05
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.box.net/shared/moreq536ht Fer de Lance 3G] adds player & NPC Fer de Lance versions with custom paint jobs & altered specs
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=2628 UK_Eliter]
|date=2012-06-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Fer de Lance NG]] adds a more powerful version of the Fer de Lance with several custom paint jobs
|aut=alien
|date=2005-03-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11626 Feramborini] Fast, unarmed, and fast. For Rich folk.
|aut=mandoman
|date=2012-02-13
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Ferdepai]] adds a new fighter / trader to Galaxy 2
|aut=[[User:Johnsmith|johnsmith]]
|date=2006-12-17
|work=Y*}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[Feudal States]] adds the [[Jäger]], the [[Korvette]], the [[Zerstörer]], a [[Royal Hunting Lodge]] and other elements to feudal systems
|aut=[[User:Ramirez|Ramirez]]
|date=2011-12-15
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Fighter HUD (Oolite)|Fighter HUD]] is an alternative HUD
|aut=[[User:CaptKev|CaptKev]]
|date=2008-05-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11933 FireAnt] Killer bug series. Tiny fighter, with tiny ball turrets, and above average speed.
|aut=mandoman
|date=2012-05-10
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11437 Firebird] adds a ship inspired by an early 70s Pontiac Firebird
|aut=mandoman
|date=2012-01-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11642 Firefly (Serenity)] adds the Firefly from Serenity
|aut=[[User:Staer9|Staer9]]
|date=2012-02-17
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Firewasp]] adds a fast interceptor
|aut=[[User:Draco Caeles|Draco_Caeles]]
|date=2006-05-10
|work=}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Fireworks OXP|Fireworks]] allows you a joyful celebration of whatever it is you want to celebrate
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-05-12
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Flight Log OXP|Flight Log]] adds a log of the last 10 systems visited
|aut=[[User:Thargoid|Thargoid]]
|date=2011-01-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Flying Dutchman OXP|Flying Dutchman]] adds the small chance to meet a Ghost Ship in the Ooniverse
|aut=[[User:Commander McLane|Commander McLane]]
|con=Griff
|date=2011-04-14
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[[Freaky Thargoids OXP|Freaky Thargoids]] is a shader demonstration for Oolite
|aut=[[User:Ahruman|Ahruman]]
|con=Eric Walch
|date=2011-02-03
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Free Trade Zone]] adds an independent trading post of dubious legality to Multi-Government systems
|aut=[[User:Disembodied|Disembodied]]
|con=Commander McLane
|date=2010-10-08
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Frog Space Rickshaw]] adds a chatty space taxi service to the safer systems
|aut=[[User:Murgh|Murgh]]
|date=2006-01-12
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Fuel Collector OXP|Fuel Collector]] scoops fuel from killed ships and collects fuel while cruising, even in witch space
|aut=[[User:Frame|Frame]]
|con=Commander McLane
|date=2011-07-05
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Fuel Station OXP|Fuel Station]] adds fly-thru Fuel Stations and Fuel Satellites near the witchpoint and along route one
|aut=[[User:Thargoid|Thargoid]]
|date=2012-01-24
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Fuel Tank]] mounts in place of a missile, to top up 3 light years of fuel
|aut=[[User:Ramirez|Ramirez]]
|date=2008-05-31
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Furball OXP|Furball]] adds barroom brawls that've got out of hand. Furious fugitives flee from pissed off police on the station's doorstep
|aut=Caracal
|con=m4r35n357
|date=2012-04-25
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Galactic Hyperdrive OXP|Galactic Hyperdrive]] is a free upgrade to the core game's equipment. Improves usability, costs nothing
|aut=Wildeblood
|date=2012-06-10
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Galactic_Misjump_OXP|Galactic Misjump]] allows intergalactic space to be reached by the brave
|aut=[[User:cim|cim]]
|date=2012-06-14
|work=Y}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[Galactic Navy OXP|Galactic Navy]] adds more ships and stations to the arsenal of the Galactic Navy. Allows to join the Navy Reserves
|aut=[[User:Nemoricus|Nemoricus]]
|date=2011-10-18
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9530 Galaxy Info] helps you search for systems by criteria you select and will try to locate the nearest one
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=3171 Okti]
|date=2012-01-10
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[GalCop Rewards]] adds a loyalty reward scheme with a lottery.
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=2456 PhantorGorth]
|date=2012-06-16
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[GalDrivePod]] A portable Galactic Hyperdrive unit, allowing you to complete the "Lost Worlds Grand Tour"
|aut=[[User:Smivs|Smivs]]
|date=2011-03-24
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Gates OXP|Gates]] adds short-cut jump gates to suitable systems, speeding journeys between the main station and witchpoint
|aut=[[User:Thargoid|Thargoid]]
|date=2011-10-23
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Generation Ships OXP|Generation Ships]] adds encounters with the mythical Generation Ships from time to time
|aut=[[User:Draco Caeles|Draco_Caeles]]
|con=Commander McLane
|date=2011-04-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11438 Genesis] adds a huge player-flyable trader with 8 ball-turrets. The NPC version comes with 6 SunBat Mk II escorts
|aut=mandoman
|date=2011-01-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[GHOST Gunship]] is GHOST's entry into the ship market, a good value for money ship with multiple front lasers
|aut=[[User:Staer9|Staer9]]
|date=2011-10-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11135 GHOST Raptor] is a very light dog-fighter with high speed capabilities and decent shielding and energy banks
|aut=[[User:Staer9|Staer9]]
|date=2011-11-10
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Globe station|Globe Station]] is a new type of stations that appears in advanced systems
|aut=[[User:Murgh|Murgh]]
|con=Svengali
|date=2009-10-22
|work=}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10073 Graffiti Asteroids] add asteroids with graffitis
|aut=[[User:Staer9|Staer9]]
|date=2011-06-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Greek Ships OXP|Greek Ships]] adds [[Penelope Class Freighter]]s, [[Telemachus Class Escort]]s, and [[Ulysses Class Interceptor]]s
|aut=8-Bit Apocalypse
|date=2005-07-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.box.net/shared/oqpkkzbl30jmm14vj2bo Green Gecko] features the Green Knights of Lago in their awesome twin-laser Geckos
|aut=[[User:El Viejo|El Viejo]]
|date=2011-09-07
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11960 GreenHornet] Largest in the Killer Insect series. Good for hauling, or mauling.
|date=2012-05-10
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Griff ArcElite|Griff's ArcElite]] adds versions of native Oolite ships textured & shaded to resemble the Acorn Archimedes version of Elite
|aut=[[User:Griff|Griff]]
|date=2008-09-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Griff Boa]] contains the famous Griff Boa
|aut=[[User:Griff|Griff]]
|date=2011-10-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://www.box.com/shared/k2lvh3enuy Griff's Explosion Debris] adds new alloy & debris models to exploding ships
|aut=[[User:Griff|Griff]]
|con=Thargoid
|date=2009-02-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Griff Krait]] adds a heavily modified Krait, similar in design to the Griff Boa
|aut=[[User:Griff|Griff]]
|date=2010-06-17
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Griff Industries|Griff's Normalmapped Ships]] adds some of the best looking ships, stations, and flotsam available in Oolite
|aut=[[User:Griff|Griff]]
|date=2012-02-29
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Griff's No Shaders Shipset|Griff's No Shaders Shipset]] Texture mod of Griff's normalmapped ships
|aut=[[User:Griff|Griff]]
|con=CaptSolo
|date=2012-05-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Griffin Two (Oolite)|Griffin Two]] adds the Griffin Mk II from Frontier
|aut=[[User:Aegidian|Aegidian]]
|date=2005-10-11
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Gritty Coriolis OXP|Gritty Coriolis]] alternates the Coriolis stations with two elaborate gritty Corioli
|aut=xaotik
|date=2006-02-27
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip G-HUD Mk2] adds an alternative HUD
|aut=[[User:Gunney Plym|Gunney Plym]]
|date=2008-07-08
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11050 Halloween Witch] adds a witch that fires pumpkins at the player
|aut=[[User:Griff|Griff]]
|con=CommonSenseOTB, Eric Walch
|date=2011-10-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Halsis]] features a female cockpit voice, sometimes called Hal's Hot Sister
|aut=[[User:Ovvldc|Ovvldc]]
|date=2006-08-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[BoyRacer|Hatchling BoyRacers]] adds the talkative (and often insulting) [[BoyRacer]]s to more advanced systems
|date=2006-01-13
|aut=[[User:Murgh|Murgh]]
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Staer9 haulerp30|Hauler P30]] is a very large cargo ship made by Staer9 Industries
|date=2011-07-15
|aut=[[User:Staer9|Staer9]]
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Hawksound]] features a quality female computer voice, new weapon, damage and some station interface sounds
|aut=[[User:Hawkstrom|Hawkstrom]]
|date=2008-11-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Herald Military Gunboat|Herald]] adds the [[Herald Military Gunboat]], a powerful police and Navy interceptor
||aut=[[User:Flying Circus|Flying_Circus]]
|date=2005-01-07
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Hired Guns OXP|Hired Guns]] adds escort ships that can be contracted to accompany you on your next journey
|aut=[[User:Thargoid|Thargoid]]
|date=2012-01-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Hognose|Hognose Tugships]] adds the [[Hognose]], a chatty tug ship that can be seen towing broken down ships
|aut=[[User:Murgh|Murgh]]
|con=Jonnycuba
|date=2006-03-01
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[HoOpy Casino]]s appear near the station in advanced systems. You can win or lose credits in games of chance
|aut=[[User:Murgh|Murgh]]
|con=Eric Walch
|date=2012-04-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11106 Hornet] adds ace's Hornet
|aut=ace\56
|con=Staer9
|date=2011-11-07
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Hotrods OXP|Hotrods]] adds custom paint jobs to classic Elite ships, racing vehicles, and a space gang that doesn't like the player
|aut=[[User:Kaks|Kaks]]
|con=Arexack_Heretic, Murgh
|date=2011-12-05
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[HyperCargo OXP|HyperCargo]] adds an extended and expanded cargo handling system
|aut=[[User:Thargoid|Thargoid]]
|date=2012-04-22
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Hyperradio js OXP|Hyperradio]] is an expandable music-player
|aut=[[User:Svengali|Svengali]]
|date=2011-12-17
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[I_Missile |I-Missile OXP]] Adds a very fast "interceptor" missile to the players arsenal
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-10-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Icarus (Oolite)|Icarus]] adds a small fighter / trader based on blueprints from the lost Solice system
|aut=[[User:Selezen|Selezen]]
|date=2007-07-13
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Icesteroids]] are like normal asteroids but are frozen lumps of water instead
|aut=[[User:Staer9|Staer9]]
|con=Griff
|date=2011-10-31
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Illegal_Goods_Tweak_OXP|Illegal Goods Tweak v1.7.3]] adds interactions with Galcop customs on docking at a main station with Contraband in the hold
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2012-05-30
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Illicit Unlock OXP|Illicit Unlock]] allows the player to fly all the classic Elite ships
|aut=tgape
|date=2005-10-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Griff_Industries#Related_OXP's_by_Other_Authors|Illicit Unlock - Griff Version]] allows the player to fly [[Griff Industries#Griff's Normalmapped Ships OXP|Griff's]] pirate/viper Ships
|aut=[[User:ADCK|ADCK]]
|con=dertien
|date=2011-02-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Imperial Courier (Oolite)|Imperial Courier]] adds the powerful Imperial Courier from Frontier, constructed by [[Seldar Shipyards]]
|aut=[[User:Selezen|Selezen]]
|con=Commander McLane
|date=2007-06-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Imperial_Star_Destroyer|Imperial Star Destroyer]] adds a battleship
|aut=[[User:Staer9|Staer9]]
|date=2011-06-05
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Imperial Trader (Oolite)|Imperial Trader]] adds the powerful Imperial Trader from Frontier
|aut=[[User:ADCK|ADCK]]
|date=2010-06-14
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Interstellar help OXP|Interstellar Help]] allows you to help out traders who got stuck in interstellar space without fuel
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-03-02
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://www.box.com/shared/moreq536ht Interstellar Tweaks] modifies what happens in interstellar space.
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=2628 UK_Eliter]
|date=2012-06-01
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Ionics OXP|Ionics]] adds a series of missions featuring the Ionics Company of Zaria, the Ramaza Liberation Front and The Link
|aut=[[User:Galileo|Galileo]]
|con=Eric Walch
|date=2010-08-10
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[IronHide OXP|IronHide]] introduces the new range of IronHide ship armour from the Aquarian Shipbuilding Corporation
|aut=[[User:Thargoid|Thargoid]]
|date=2011-02-19
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Iron Raven]] is a multi-stage mission to investigate a dangerous conspiracy on behalf of GalCop High Command
|aut=[[User:Ramirez|Ramirez]]
|date=2011-11-17
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Ixian Ships|Ixian Military Ships]] adds Ixian [[Ixian Battle Cruiser|Battle Cruiser]]s, [[Ixian Bezerka|Bezerka]]s, [[Ixian Gunship|Gunship]]s and [[Ixian No-Ship Mark I|No-Ship]]s from Dune
|aut=8-Bit Apocalypse
|con=Eric Walch
|date=2009-03-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Ixian Ships#Ixian Freighter|Ixian Freighter]] adds a civilian freighter to the universe
|aut=8-Bit Apocalypse
|date=2005-01-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Jabberwocky]] adds the powerful Jabberwocky fighter / trader
|aut=[[User:Flying Circus|Flying_Circus]]
|date=2006-03-12
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[JellyBaby Dispenser]] adds a handy Jellybaby Dispenser for your cockpit
|aut=[[User:Smivs|Smivs]]
|date=2011-03-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Kestrel & Falcon OXP|Kestrel & Falcon]] adds buyable Star Wars style [[Falcon_%28Oolite%29|Falcon]] for pirates/traders and the [[Kestrel]], a police/navy interceptor
|aut=Charlie
|con=Kaks
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Kestros Mk4]] is a medium-sized fighter, the result of the Kestros project.
|aut=[[Ryan Hoots]]
|date=2011-12-18
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Killer_Wolf's_Dynamic_HUD|Killer Wolf's Dynamic HUD]] adds a version of the dynamic HUD first seen in Killer Wolf's Werewolf ships, to all ships
|aut=[[User:Killer Wolf|Killer Wolf]]
|con=Thargoid
|date=2010-07-08
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Killit_OXP|Killit]] adds a bunch of insane super weapons
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-05-07
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://purgatori.net/kingcobra.htm King Cobra] is [[Isis Interstellar]]'s Cobra MkVI, with new missiles and a custom HUD
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2012-01-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Kirin]] adds a heavy military hauler, CV & XM versions used by both pirates & traders
|aut=[[User:ClymAngus|ClymAngus]]
|con=Cdr. Wyvern
|date=2009-09-09
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Klepto-HUD OXP|Klepto-HUD]] is a different take on a HUD with precise crosshairs
|aut=Kleptoid
|date=2006-03-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Koneko Kobra]] is [[Koneko Industries | Koneko Industries's]] variant of the Cobra Mk3.
|aut=[[Ryan Hoots]]
|date=2011-12-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://sancho.dk/oolite/lane_legal.zip ''Lane Legal Racers''] adds NPC versions of [[Krait]]s, [[Mamba]]s, and [[Sidewinder]]s from different [[Racers#Listing_of_sponsored_teams|racing teams]]
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-09-27
|work=Y*}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Lave OXP|Lave]] is a system make-over for Lave, adding all features described in The Dark Wheel novella included with original Elite
|aut=[[User:Murgh|Murgh]]
|date=2009-12-31
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Lave Academy OXP|Lave Academy]] adds Lave Academy Station above Lave & other planets, with 3 mini-games to test Commanders' skills
|aut=[[User:Thargoid|Thargoid]]
|date=2011-12-31
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[http://aegidian.org/bb/viewtopic.php?p=130015#p130015 LinkG7] is a mission in Galaxy 7
|aut=Okti
|date=2011-02-16
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Liners]] adds some beautiful and very large vessels to the spacelanes.
|aut=[[User:Smivs|Smivs]]
|con=pagroove, Thargoid, Griff, Eric Walch
|date=2012-05-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Llama]] adds the Llama fighter / trader. Updated from the version of Oosat1 to fix a small bug
|aut=[[User:Flying Circus|Flying_Circus]]
|date=2006-02-28
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://www.boxcn.net/shared/bpl582x1hu Long Range Target Scanner] shows all ships currently in your system and allows to target them
|aut=Okti
|date=2011-05-27
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[LongWay_OXP|Long Way Around]] adds a transport mission well suited to the novice in Galaxy 1
|aut=[[User:Aegidian|Aegidian]]
|date=2009-04-11
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Lovecats.oxp|Lovecats]] is a mission about love & betrayal amongst the feline races of Galaxy 4. Fast ship & hard heart required!
|aut=[[User:Johnsmith|johnsmith]]
|date=2011-07-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Second-hand ships|M-Pack (rusties)]] adds rusty banger versions of all Classic Elite ships in poor condition but still can haul cargo
|aut=[[User:Murgh|Murgh]]
|date=2006-01-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Manta]] adds the Manta light escort craft
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11290 Marauder] is a small ship with huge engines, intended to be an escort, or a speed mission runner.
|aut=Mandoman
|date=2011-12-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Marett Space Corporation OXP|Marett Space Corporation]] releases [[Adder Mk II]], [[Mosquito Trader]], [[Mosquito Sport]], new fighters / medium traders
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip Medusa HUD] is an alternative HUD
|aut=[[User:ClymAngus|ClymAngus]]
|date=2009-01-18
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Mega-Walnut Dashboard OXP|Mega-Walnut Dashboard]] is a generic version of the fabled Fer de Lance HUD
|aut=[[User:Aegidian|Aegidian]]
|date=2005-07-05
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11959 Megaladon] It's a huge shark ship. Nasty looking, but really just a cargo ship.
|aut=Mandoman
|date=2012-05-17
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Merlin_(Oolite)|Merlin]] Ships are interceptors used by the Police & Navy, but also available on the open market
|aut=Charlie
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[MFLPS]] introduces player flyable versions of NPC ships with multiple forward lasers
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-10-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[MildAudio]] Sound Set
|aut=xaotik
|date=2006-02-15
|work=}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Military_Fiasco|Military Fiasco]] adds a navy mission for Commanders with > 1,000 kills. Also equips Navy with powerful cruisers
|aut=[[User:Murgh|Murgh]]
|con=Eric Walch
|date=2011-01-20
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Military Fuel Injectors OXP|Military Fuel Injectors]] is an upgrade to the vanilla injectors that gives a velocity boost and recaptures unburnt fuel
|aut=[[User:Thargoid|Thargoid]]
|date=2011-07-25
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Military station|Military Station]] adds well armed Military Stations to the more advanced systems
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-02-24
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Military Stingray Mk. II|Military Stingray]] adds an ex-military ship that may show up in pirate hands or for the player to buy
|aut=[[User:CaptKev|CaptKev]]
|date=2007-03-24
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=12050 Military Targetting System] is a modern up to date style of targetting for oolite aquiring up to 16 targets of a particular type simultaneously at the push of a button.
|aut=CommonSenseOTB
|date=2012-06-13
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[MilHUD 4000]] is a fork of Milspec HUD with updated script and new features
|aut=Wildeblood
|date=2012-04-09
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Milspec HUD]] is an alternative HUD with targeting aids and an emphasis on functionality
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2011-12-16
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Misjump Analyser]] scans witchspace & on detection of disturbances sounds an alarm & logs location of disturbance
|aut=[[User:Eric Walch|Eric Walch]]
|date=2010-05-25
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?p=135619#p135619 Misjump Inducer] can turn on/off misjumps on demand
|aut=Switeck
|date=2011-04-02
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Missile_Analyser|Missile Analyser]] scans incoming missiles & sets target to incoming missile when it is no standard missile
|aut=[[User:Eric Walch|Eric Walch]]
|date=2010-05-25
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10151 Missile Spoof] is an ECM system that employs flares to deter hardened missiles
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2011-12-04
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Missiles_and_Bombs|Missiles & Bombs]] adds a wide variety of missiles & bombs that are are available to player & NPCs alike
|aut=[[User:Ramirez|Ramirez]]
|date=2011-12-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Missionaries OXP|Missionaries]] adds clerics of four faiths who spam Commanders with requests to worship their Gods
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Moccasin]] adds light escort craft from Xeceesian Shipyards modeled after ArcElite core ship
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-06-07
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Mod-HUD]] is a slight modification / re-organization of the standard Oolite HUD without surround boxes
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-05-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/monument.zip Monument] sometimes adds a monument to famous Commanders close to the Sun
|aut=[[User:Dajt|dajt]]
|date=2005-05-28
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Morrigan]] adds a vast trade ship to the Universe
|aut=[[User:Flying Circus|Flying_Circus]]
|date=2009-12-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Oosounds2_OXP|Murgh's Replacement Sounds]] contains 10 new sounds
|aut=[[User:Murgh|Murgh]]
|date=2005-08-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Murgh_Xships OXP|Murgh's X-Ships]] adds [[Bandy-Bandy]], [[Chuckwalla]], [[Eel Rapier]], [[Taipan]] (fast courier craft & 2 light escort ships)
|aut=[[User:Murgh|Murgh]]
|date=2009-09-12
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[NavalGrid OXP|Naval Grid]] enhances recharging rates by linking the naval energy unit to military-boosted shields
|aut=[[User:Thargoid|Thargoid]]
|date=2011-03-09
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Naval Torpedo]] is slower and less maneuverable but is more destructive than standard missiles
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-07-04
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Neolite Ships]] is an Oolite ships replacement set. Version 1.1.1 is available.
|aut=[[User:Simon B|SimonB]]
|date=2012-06-05
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[New_Cargoes|New Cargoes]] adds special cargoes and markets for them with high risk high profit trading opportunities
|aut=[[User:cim|cim]]
|date=2012-05-17
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/newships.oxp.zip ''New Ships''] adds [[Hamadryad]], [[Josher]], [[Naga]], [[Ringhals]] (mining and trade ships from previous versions of Elite)
|aut=[[User:Murgh|Murgh]]
|date=2006-05-15
|work=}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[http://www.box.net/shared/moreq536ht Nexus missile] adds multiple versions of a multi-warhead, 'anti-hostile' (or, in one case, anti-thargoid) missile
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=2628 UK_Eliter]
|date=2012-06-01
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip NG HUD] is an alternate HUD. All standard functions, but with a personal view
|aut=alien
|date=2005-03-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11075 Night Adder] adds ace's Night Adder, a fully shadered, light escort player ship
|aut=ace\56
|con=Staer9
|date=2011-11-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11142 NovaBat] is a 3x enlarged version of the SunBat with larger cargo capacity, higher speed, and better weapons
|aut=mandoman
|date=2011-11-11
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[NPC-shields OXP|NPC-shields]] gives shields to NPCs, together with a nice glow effect
|aut=[[User:Commander McLane|Commander McLane]]
|date=2012-01-05
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Numeric_Style_HUDs|Numeric Style HUDs]] numeric gauges, now version 3.
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2012-04-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/nuvipers.zip Nu Vipers] increases the types of Viper patrol ships with [[GalCop Viper Mark II]], [[GalCop Viper Cruiser]]
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Nukes.oxp|Nuclear Torpedos]] adds some powerful, but slow moving, missiles
|aut=[[User:Eric Walch|E. Walch]], [[User:Wyvern|Cdr. Wyvern]]
|date=2012-01-29
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Offender traders OXP|Offender Traders]] makes some traders into offenders/fugitives
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-04-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Old Ships]] adds Elite-A [[Bushmaster Miner]]s, [[Cat (Oolite)|Cat]]s, [[Chameleon (Oolite)|Chameleon]]s, [[Ghavial (Oolite)|Ghavial]]s, [[Iguana (Oolite)|Iguana]]s, [[Monitor (Oolite)|Monitor]]s, [[Ophidian (Oolite)|Ophidian]]s, [[Salamander (Oolite)|Salamander]]s
|aut=[[User:Murgh|Murgh]]
|date=2006-08-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Old Ships 2010]] is a retextured version of [[Old Ships]], adding the bonus Monitor 2 ship
|aut=[[User:Pagroove|pagroove]]
|con=Murgh, ADCK, Simon B, Lestradae
|date=2011-02-10
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Oo-Haul]] adds vast bulk [[L-Crate Hauler]]s to the space lanes and offers missions at [[Your Ad Here!|constores]] to safely escort them
|aut=[[User:Dr. Nil|Dr. Nil]]
|con=Eric Walch, Ark
|date=2009-02-21
|work=}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[ooCheat_OXP|ooCheat]] adds a cheat menu to the game
|aut=[[User:Thargoid|Thargoid]]
|date=2011-02-19
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[http://marc-schaffer.ch/data/OoliteGerman_V0.3.zip Oolite auf Deutsch] is a German Oolite localization
|aut=[[User:SwissMÃ¤c|SwissMäc]]
|date=2009-06-02
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=4490 Oolite Italiano] is an Italian Oolite localization
|aut=[[User:Another commander|another_commander]]
|date=2012-01-06
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=Oolite in Russian: [http://www.roolite.org Roolite.org] provides localizations of Oolite 1.74.2 and some OXPs. Also check [http://www.elite-games.ru/conference/viewtopic.php?t=48476&start=0 Elite Games]
|aut=Seventh
|date=2009-03-26
|work=}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=8216 Orbits] positions planets on orbits around the sun
|date=2012-04-21
|aut=[[User:Ebi|Ebi]]
|con=Kaks, Wildeblood
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Ore Processor]] extracts valuable materials from asteroid fragments when mounted to a ship's fuel scoop
|aut=[[User:Dr. Nil|Dr. Nil]]
|con=Ark, Kaks, Eric Walch
|date=2012-02-10
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Orisis]] BigTraders are new passenger liners that ferry passengers around
|aut=[[User:Pagroove|pagroove]]
|con=ADCK, Thargoid
|date=2010-01-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Outrider (Oolite)|Outrider]] is a medium fighter produced by the [[Taranis Corporation HQ (Oolite)|Taranis Corporation]]
|aut=[[User:Roberto|Roberto]]
|date=2006-08-14
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[[OXPConfig]] provides menus to configure supported OXPs, to recognize errors, or to avoid clashes
|aut=[[User:Svengali|Svengali]]
|date=2012-05-21
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[P.A. Groove Stations OXP|P.A. Groove Stations]] adds lots of different types of Coriolis and Dodec Stations
|aut=[[User:Pagroove|pagroove]]
|con=Griff, Commander McLane
|date=2010-04-16
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Pallas]] adds a fast but lightly shielded fighter.
|aut=Charlie
|con=Svengali
|date=2011-10-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Pelamis]] adds the Pelamis trade ship
|aut=[[User:Aegidian|Aegidian]]
|date=2006-04-24
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Phoenix]] is a strange ship, built from salvaged parts from various Serpent Class ships
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2007-01-17
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Pie_Chart_Style_HUDs|Pie Chart Style HUDs]] New invention=>pie gauges.
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-05-20
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Pirate Coves OXP|Pirate Coves]] adds rock hermits that have been taken over by pirates in more dangerous systems
|aut=lazygun
|date=2012-04-23
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip Pirate Traps] are dummy traders which transmit details of pirates firing on them to the police
|aut=popsch
|date=2006-01-04
|work=}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Planetfall_OXP|Planetfall]] allows the player to land on and trade at the planets and moons of each system
|aut=[[User:Thargoid|Thargoid]]
|date=2010-04-15
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Pods_OXP|Pods]] adds fuel, missile, bulk & empty cargo pods and pods which jam, explode, have trumbles or take a few scoops
|aut=[[User:Thargoid|Thargoid]]
|date=2010-03-18
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Police_IFF_Scanner_Upgrade|Police IFF Scanner Upgrade v 1.3.1]] highlights offender and fugitive ships with custom IFF scanner colours
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-12-18
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[PovrayPlanets OXP|Povray Planets]] adds procedurally generated textures to planets in galaxies 1, 2, 4 and 5
|aut=submersible
|date=2012-02-28
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11338 Primable Laser] adds a secondary forward laser
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=3171 Okti]
|date=2011-12-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Pteradyne Technologies Ships OXP|Pteradyne Technologies Ships]] adds the [[Excalibur]], a buyable combat ship and the [[Paladin]], a military version
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2006-12-27
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://www.boxcn.net/shared/bpl582x1hu Pylon Based Equipment Remover] allows to remove a selected piece of equipment from your pylons
|aut=Okti
|date=2011-04-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Python Class Cruiser]] is a large powerful trade ship, which can also hold its own in battle
|aut=[[User:Aegidian|Aegidian]]
|date=2007-07-11
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Q-Charger]] is a Quirium supercharger which promises a 100% speed gain with twice the fuel efficiency of fuel injectors
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-08-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/racers.oxp.zip Racers] adds [[Chicaneer Mk II]], [[Chicaneer Mk IV]], [[Dragster Mk I]], and [[Dragster Mk II]] racing ships
|aut=[[User:Murgh|Murgh]]
|date=2006-01-02
|work=Y}}
{{OXPSortableTableRow
|cat=Weapons
|desc=[[Railgun OXP|Railgun]] introduces a revolutionary new weapons system to the Ooniverse
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-05-13
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Ramon's Anaconda]] is a fantastic re-imagining of the Anaconda freighter. Check out its special features
|aut=[[User:Ramon|Ramon]]
|con=Griff
|date=2009-04-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Random_Docking_Music_OXP|Random Docking Music]] plays a random music track from a pre-set list on activating docking computers
|aut=[[User:Frame|Frame]]
|date=2010-05-12
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Random Hits OXP|Random Hits]] adds [[Space Bar|seedy space bars]] to anarchy systems that offer large bounties on the galaxy's Most Wanted Criminals
|aut=[[User:LittleBear|Littlebear]]
|con=Eric Walch
|date=2011-11-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Randomshipnames OXP|Random Ship Names]] adds randomly generated names to all normal ship classes
|aut=[[User:Commander McLane|Commander McLane]]
|con=Disembodied
|date=2012-04-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://terrastorage.ath.cx/Marmagka/e8e9ce360da6bb40f5952cbe00f02501/RedSet.zip RedSet] contains red-themed backgrounds for the UI screens
|aut=[[User:Another commander|another_commander]]
|date=2010-06-18
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.purgatori.net/reduxedvamps.htm Reduxed Vampires] adds reworked versions of the Vampire Mk I and Mk II and a Reaper "Gold Edition"
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2010-10-10
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[RegistrationID|Registration ID]] adds ID tags to all Oolite standard ships
|aut=[[User:Frame|Frame]]
|date=2010-02-28
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Remorse_Of_Conscience_v2|Remorse Of Conscience]] is a trade ship with a large hold, that can hold its own in combat
|aut=8-bit Apocalypse
|con=Svengali
|date=2011-11-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Renegade Pirates OXP|Renegade Pirates]] adds rare, very well-armed, high bounty pirate versions of Classic Elite ships
|aut=[[User:LittleBear|Littlebear]]
|con=Aegidian, Griff
|date=2006-12-03
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[RVandGS|Renegade Viper + Grass Snake]] adds [[Renegade Viper|stolen Vipers]] which earn large bounties & [[Grass Snake]], a large pirate trade ship
|aut=8-bit Apocalypse
|con=Svengali
|date=2011-10-29
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Repair_Bots_OXP|Repair 'Bots]] adds a pylon mounted canister of repair nanobots which attempt to fix damaged equipment in mid-flight
|aut=[[User:Thargoid|Thargoid]]
|date=2012-03-19
|work=Y}}
{{OXPSortableTableRow
|cat=Systems
|desc=[[RRS Group|Rescue Stations]] adds Rescue Stations to stable systems, for rescue and recovery.
|aut=[[User:cim|cim]]
|date=2012-03-24
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Resistance Commander]] gives players a chance to command a squadron in combat
|aut=[[User:Ramirez|Ramirez]]
|date=2012-02-20
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Retro Rockets OXP|Retro Rockets]] are a handy little piece of equipment which gives your ship a backwards boost out of trouble
|aut=[[User:Thargoid|Thargoid]]
|date=2011-07-04
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Ringpod|Ring Pod]] adds a series of racing rings to the Galaxy 1 systems of Lave and Zaonce
|aut=[[User:Aegidian|Aegidian]]
|con=Eric Walch
|date=2011-10-11
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Ring_Racer_OXP|Ring Racer]] adds the Corporate Systems Ring Racing League to Galaxy 1
|aut=[[User:Thargoid|Thargoid]]
|date=2010-04-14
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Rock Hermit Locator]] adds equipment to locate Rock Hermits
|aut=[[User:Frame|Frame]]
|date=2011-03-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11791 Romulan Bird of Prey] is a rendition of the ship from the first Star Trek series
|aut=mandoman
|date=2012-03-30
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10869 RXSoftware Shipset] is a remake of all standard player ships plus 18 new ships, most of them player useable
|aut=commanderxairon
|date=2011-10-12
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Safe Docking]] allows you to earn GalCop Reward Points for safe manual docking.
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=2456 PhantorGorth]
|date=2012-06-16
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11921 SafeJumps] Warns the player if they are about to jump to a Nova system
|aut=Okti
|date=2012-05-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Saleza Aeronautics]] adds [[Bellatrix Cruiser]]s, [[Rigel Bomber|Rigel Tactical Bomber]]s, and [[Saiph Interceptor]]s to high tech corporate systems
|aut=[[User:Ramirez|Ramirez]]
|date=2010-10-24
|work=Y*}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Santa]] adds very rare Santa Sledge to space lanes escorted by plasma gun toting reindeer space bikers!
|aut=[[User:Griff|Griff]]
|con=Eric Walch
|date=2010-05-26
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[[Save Anywhere]] allows you to save your game at any OXP Station
|aut=[[User:Frame|Frame]]
|date=2011-12-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Scimitar]] Adds a fast and nimble ship well kitted out for the serious bounty hunter
|aut=[[User:CaptSolo|CaptSolo]]
|date=2012-01-10
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.purgatori.net/scorpius.htm Scorpius] adds a heavily armoured private trading and transport vessel, protected by Vampire escorts
|aut=[[User:Killer Wolf|Killer Wolf]]
|con=Griff
|date=2011-08-14
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Scourge of the Black Baron]] features combat & transport Galaxy 1 missions
|aut=[[User:Rxke|Rxke]]
|con=Kaks, Thargoid
|date=2010-08-07
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Scout]] is a cheap but good looking ship from Staer9 that shares a lot of technology with the [[Xeikil]]
|aut=[[User:Staer9|Staer9]]
|date=2011-05-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Second Wave OXP|Second Wave]] adds variants of Thargoid Warship, Thargon Robot Fighter and alien ships
|aut=[[User:Thargoid|Thargoid]]
|date=2011-12-18
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Selezen's S-Ships]] adds [[GalCop SWAT Viper]]s and [[Oresrian Trader]]s
|aut=[[User:Selezen|Selezen]]
|date=2007-07-12
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Sell equipment OXP|Sell Equipment]] allows, for a small fee, resale of equipment at 60% price at suitable tech level world
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-02-28
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11123 Sensible Lasers] allows to sell a laser weapon and leave the weapon mounting point empty
|aut=Wildeblood
|date=2011-11-07
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Sensible Sun|Sensible Sun]] creates suns 2.75 times further from the planet than the default configuration
|aut=Wildeblood
|date=2011-11-07
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[[Shady Cobra OXP|Shady Cobra]] adds shader effects to Cobra Mk III
|aut=[[User:Ahruman|Ahruman]]
|date=2007-07-11
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Shady Sungs]] adds replacement textures for all Classic Elite Ships
|aut=[[User:Sung|Sung]], [[User:ADCK|ADCK]]
|con=Micha
|date=2012-01-22
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Shield_Equalizer_%26_Capacitors_OXP|Shield Equalizer & Capacitors]] balances shield energy and stores unused shield energy
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-07-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Skrounk All-Stars Limited]] adds [[All Stars Large Freighter|Large Freighter]], [[Seymour Class Sled]], [[Starbelly Class Sled]], [[Starhawk]] & [[Starwolf_Mark_I|Starwolf Mk I]]
|aut=goji62
|date=2007-02-24
|work=N}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11890 SmallBlimpy] Smaller than BigBlimpy, but looks just as silly.
|aut=mandoman
|date=2011-12-28
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Smivs%27_ShipSet|Smivs' Shipset v4.1.3]] re-textures all the core ships, with non-shader lighting effects and stunning visual SFX.
|aut=[[User:Smivs|Smivs]]
|date=2012-06-08
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11387 Snapper] is a VERY large ship, able to move at 250LM, while hauling around 760 tons of cargo
|aut=mandoman
|date=2011-12-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Snark]] is a powerful fighter/trader, often used by pirates and bounty hunters
|aut=[[User:Flying Circus|Flying_Circus]]
|date=2006-06-21
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Sniper Camera System HUD|Sniper Camera System]] Zoomable camera for surveillance and long-range sniping.
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-08-04
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[SniperLock]] More accurate targeting by automatically keeping ship's aim on target longer.
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-12-17
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11542 Sniper Sight] is the Ooniverse's most customizable precision gun sight. (A variant is included in [[MilHUD 4000]])
|aut=Wildeblood
|date=2012-04-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Snoopers]] adds the galactic news network channels
|aut=[[User:Daddyhoggy|DaddyHoggy]]
|con=Disembodied, Drew, Svengali
|date=2012-01-04
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Solid Gold Cobra Mk.3]] is a limited edition Cobra Mk3 to celebrate its 25 years anniversary
|aut=[[User:ADCK|ADCK]]
|date=2010-06-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Solo's Silver Ships]] Adds three ships with silver themed textures
|aut=[[User:CaptSolo|CaptSolo]]
|date=2011-08-19
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://www.purgatori.net/Sothis.htm Sothis Space Station] is a station from [[Isis Interstellar]] with a compact design of comparable size to a standard Coriolis
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2010-08-08
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Spearhead Interceptor Mk.I]] is a pure fighter, fast and nippy but with weak shields and without cargo bay
|aut=Rendell
|date=2011-11-15
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[S.I.R.F.|Special Interstellar Repair Facilities]] offer different trading strategies & repair facilities on uncommon trading routes
|aut=Tinker
|date=2010-07-02
|work=Y*}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.purgatori.net/spectres.htm Spectre] adds [[Isis Interstellar]]'s Vampire Mk V, a secret military vessel fighting Thargoids in witch space
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2011-01-16
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Spy Hunter OXP|Spy Hunter]] is a mission for Galactic Navy for Commander with rating of 'Dangerous' or above
|aut=[[User:Selezen|Selezen]]
|date=2009-04-11
|work=}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[[Staer9's Shipset]] replaces the same ships as [[Neolite Ships]] using a style similar to Griff's to be used alongside his shipset
|aut=[[User:Staer9|Staer9]]
|con=Griff
|date=2012-05-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Staer9 Spectre]] is a cheap small fighter with high maneuverability that flopped in the market
|aut=[[User:Staer9|Staer9]]
|date=2011-05-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Star-Jelly]] Beautiful translucent organisms sometimes found in Asteroid fields
|aut=[[User:Smivs|Smivs]],[[User:Staer9|Staer9]]
|date=2012-03-16
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11963 StarMoth] Colorful trader ship for brightening your Ooniverse.
|aut=mandoman
|date=2012-05-18
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Star Wars Ships]] adds [[A-Wing]], [[B-Wing]], [[Lambda Shuttle]], [[Tie-Fighter]], [[Tie-Interceptor]], [[X-Wing]], [[Y-Wing]]
|aut=Azzameen
|date=2006-05-31
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Status Quo Q-bomb OXP|Status Quo Q-bomb]] changes the behaviour of Q-bombs according to the [[Status Quo]] novel
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-02-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[S.T.E]] is a step up from the Cobra III with improved trading capabilities and increased speed
|aut=[[User:Rustybolts|Rustybolts]]
|date=2009-07-13
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Stealth OXP|Stealth]] is a small G3 mission showcasing new scanner capabilities & introducing stealth ships
|aut=[[User:Thargoid|Thargoid]]
|date=2011-07-13
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://www.purgatori.net/Steampunk%20HUD.htm Steampunk HUD] adds a steampunk style HUD by [[Isis Interstellar]]
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2010-01-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Stellar Serpents OXP|Stellar Serpents]] adds huge space-born serpent monsters which move from system to system and are good hunting prey
|aut=[[User:Thargoid|Thargoid]]
|date=2012-02-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11373 Submersible Nebulae] replaces the traditional four nebulae textures
|aut=submersible
|date=2011-12-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11054 SunBat] is a black, fast fighter, now packing aft laser.
|aut=mandoman
|date=2011-10-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11305&hilit=SunBatMkII SunBat MkII] is a black, faster than SunBat fighter, and very hard to kill.
|aut=mandoman
|date=2011-12-06
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://sancho.dk/oolite/sunskimmers.zip Sunskimmers] adds ships to the sun/planet corridor
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-08-09
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[SuperCobra]] is larger, faster with stronger hull than Cobra Mk III
|aut=8-Bit Apocalypse
|con=Eric Walch
|date=2010-10-12
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Superhub]] from GASEC is the first station that is capable of transporting itself to its destination
|aut=[[User:Pagroove|pagroove]]
|date=2012-03-13
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Swarm OXP|Swarm]] adds a new swarming variant on the Thargoid mothership and thargons.
|aut=[[User:Thargoid|Thargoid]]
|date=2012-02-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Swift]] is a very fast ship often used by pirates or bounty hunters with limited cargo space & nominal shields
|aut=Charlie
|date=2007-02-24
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Switeck's Shipping OXP|Switeck's Shipping]] tweaks ships, market prices and NPC behavior. Adds Medium, Hard, and Harder Jameson saves
|aut=Switeck
|date=2011-07-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[System Demux (Oolite)|System Demux]] textures home planet, adds planet/moon combination to systems
|aut=[[User:DrBeeb|DrBeeb]]
|date=2010-07-18
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[System Redux (Oolite)|System Redux]] textures home planet, adds planet/moon combination to systems
|aut=[[User:CaptKev|CaptKev]]
|date=2011-12-03
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://www.box.net/shared/r05ub873b5 TAF Reset] resets the Time Acceleration Factor (TAF) to 1.0 upon docking
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2009-09-15
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[[Talkative_Space_Compass|Talkative Space Compass]] is an upgrade to the advanced space compass that shows the name of the current target
|aut=[[User:cim|cim]]
|date=2011-11-12
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Taranis OXP|Taranis]] is a mission for law abiding Commanders with rating of Competent+. Adds [[Taranis Corporation HQ (Oolite)|Taranis Corporation HQ]]
|aut=[[User:Roberto|Roberto]]
|con=Eric Walch
|date=2012-05-20
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Target_Autolock_OXP|Target Autolock]] updates [[Scanner Targeting Enhancement]] to auto-lock onto attacking ships
|aut=[[User:Thargoid|Thargoid]]
|date=2011-02-13
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[[Target Range OXP|Target Range]] is found in all rich systems with stable governments
|aut=Caracal
|date=2010-07-24
|work=Y*}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Target Reticle]] updates [[Scanner Targeting Enhancement]] to turn reticle red when target centred
|aut=[[User:Eric Walch|Eric Walch]]
|date=2010-05-31
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Taxi Galactica]] adds a Taxi Service and a non player flyable taxi cab ship to systems
|aut=[[User:Pleb87|pleb87]]
|date=2012-05-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Teretrurus Mk.I]] is a medium fighter/trader somewhat faster & tougher than Cobra Mk III, but with smaller cargo bay
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2008-02-01
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Terrapin|Terrapin Trader]] is a medium fighter/trader. A good upgrade from Cobra Mk III
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2008-02-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Tesoura]] is a slow, but well shielded trade ship
|aut=[[User:Randall|Randall]], [[User:Dr. Nil|Dr. Nil]]
|date=2008-02-01
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Thargoid Carrier]] arms Thargoids with capital carrier
|aut=[[User:Selezen|Selezen]]
|con=Commander McLane
|date=2012-03-10
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Thargorn_Threat_oxp|Thargoid Threat]] adds [[Thargoid Terrorizer Frigate]], [[Thargoid Thargorn Battleship]], [[Thargoid Thorgon Cruiser]]
|aut=[[User:Arexack|Arexack Heretic]]
|con=Eric Walch
|date=2012-04-15
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Thargoid Wars]] intensifies war with the Thargoids, featuring new attack and defense missions
|aut=[[User:Cmdr. Wombat|Cdr. Wombat]]
|date=2011-11-07
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Thargoid Witchspace Drive]] v0.9.4 adds a rare equipment item allowing long range jumps > 7 light years
|aut=[[User:Capt. Murphy|Capt.Murphy]]
|date=2012-04-20
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Tianve OXP|Tianve]] adds [[Navy Station]], as well as Visuals, including a pulsar, to the Galaxy 1 system of Tianve
|aut=[[User:Drew|Drew]]
|date=2009-12-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Tiger Mark I]] is a truly awesome (and very expensive) multi-role craft
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2006-05-14
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11760 Tionisla Chronicle Array] adds the huge transmitter, serving newsfeeds across the galaxy
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=18304 Storm]
|date=2012-03-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Tionisla Orbital Graveyard]] adds the famed graveyard to Tionisla, G1, as described in “The Dark Wheel” novella
|aut=[[User:Selezen|Selezen]]
|con=Eric Walch
|date=2011-02-14
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Tionisla Reporter]] adds a mission for a starting commander
|aut=[[User:Eric Walch|Eric Walch]]
|date=2011-07-24
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[TCAT OXP|To Catch a Thargoid]] is a G3 follow-up mission to Thargoid Plans, for Dangerous or Elite rank Commanders
|aut=[[User:Thargoid|Thargoid]]
|date=2012-04-18
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Torus station|Torus Station]] adds a vast 2001 style space station to very high tech level systems
|aut=[[User:Murgh|Murgh]]
|con=Svengali
|date=2010-10-15
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Total patrol OXP|Total Patrol]] makes police ships patrol between planet, witchpoint & sun
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-03-01
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[ToughGuys|ToughGuys]] Adds increased toughness of 'Baddies' for everyday use or as a backdrop for an immersive storyline.
|aut=[[User:Smivs|Smivs]]
|date=2012-05-18
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Tracker OXP|Tracker]] gives the capability to track up to 6 targets per system via the ASC
|aut=[[User:Thargoid|Thargoid]]
|date=2012-03-16
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Trader Outpost (Oolite)|Trade Outpost]] adds Griff's trade outpost without ads
|aut=[[User:CaptKev|CaptKev]], [[User:Griff|Griff]], [[User:Ark|Ark]]
|date=2009-02-21
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Traffic_Control_OXP|Traffic Control]] personnel gives help with approach to and manual docking at all main stations
|aut=[[User:Thargoid|Thargoid]]
|date=2010-06-20
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Transhab station|Transhab Station]] adds a large station with rotating arms to some medium tech level systems
|aut=[[User:Draco Caeles|Draco_Caeles]]
|date=2006-06-18
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Transports]] adds [[CoachWhip]], [[Coral]], [[Woma]]
|aut=[[User:Murgh|Murgh]]
|con=Eric Walch, Kaks
|date=2010-12-04
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://wiki.alioth.net/images/d/d9/TrekHud.zip Trek HUD] replaces your HUD with a Star Trek NG LCARS-style HUD
|aut=[[User:Barabis|barabis]]
|date=2008-11-11
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Trident Down]] contains a series of Galaxy 4 missions investigating a vicious attack on a [[Executive SpaceWays|Trident Shuttle]]
|aut=[[User:Ramirez|Ramirez]]
|date=2012-04-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://www.box.net/shared/ghkefshhib tty] replaces the standard Oolite font with a typewriter-like font
|aut=[[User:Kaks|Kaks]]
|date=2009-02-28
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11004 Turbo Anaconda] is a faster Anaconda with reduced manoeuvrability, thrust, and combat abilities
|aut=Cdr. MacSeumas
|date=2011-10-21
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11685 UHU] is a new fast ship from Mandoman Technologies'
|aut=mandoman
|date=2012-02-28
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[UPS Courier]] offers Commanders transport of goods/documents & occasional combat missions
|aut=[[User:Eric Walch|Eric Walch]]
|date=2012-02-05
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Urutu Mark III & Urutu Mark IV]] are medium fighters/traders from Elite-A
|aut=milinks
|date=2006-09-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Vampire]] adds the Purgatori Vampire series of combat ships
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2007-01-29
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Vampire - Diamondback]] adds the Diamondback Vampire series of combat ships
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2010-04-04
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Vampire - Dominatrix]] adds the Dominatrix Vampire series of combat ships
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2009-12-13
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Vector OXP|Vector]] is a unusual mission type - fast money, slavers, tricks and GalCop is watching you...
|aut=[[User:Svengali|Svengali]]
|date=2011-12-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Velocity_OXP|Velocity]] is a fast fighter ship
|aut=[[User:Sabre|Sabre]]
|date=2009-09-11
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11300 Vendetta] is a heavy attack fighter with bounty hunters in mind
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2011-12-19
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.purgatori.net/Venom.oxp.zip Venom] adds [[Venom]]s in normal and renegade versions from [[Isis Interstellar]]
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2009-12-25
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11801 Ventura] adds a trader, the NPC version comes with 3 Yellow Jacket escorts
|aut=mandoman
|date=2012-04-27
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Victim 11]] extends the [[The Assassins Guild OXP|Assassins Guild]] mission with an additional target
|aut=[[User:Fatleaf|Fatleaf]]
|con=Okti, Smivs, El Viejo, Switeck
|date=2011-12-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Vortex OXP|Vortex]] A new ex-military player ship. Rare, expensive and powerful - kitted out with advanced and unique features
|aut=[[User:Thargoid|Thargoid]]
|date=2012-04-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.purgatori.net/wasps.htm Wasps] adds formation flying wasps, queen wasps, and wasp nests
|aut=[[User:Killer Wolf|Killer Wolf]]
|con=Thargoid, Ahruman, Eric Walch
|date=2010-08-04
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://capnhack.com/hosting/oolite/Oolite/OXPs/weeviloid2.zip ''Weeviloid''] adds [[Weeviloid Hunter]]s, fearsome multi-gunned war ships and [[Weeviloid Scoutship]]s, light trade ships
|aut=[[User:Aegidian|Aegidian]]
|date=2006-05-11
|work=}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Welcome_Mat_OXP|Welcome Mat]] upgrades the comms systems to expand the information that is given on arrival in new system
|aut=[[User:Thargoid|Thargoid]]
|date=2012-04-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Werewolf]] from [[Isis Interstellar]] has 3 variants: [[Werewolf|Werewolf ~ Damage Inc.]], [[Werewolf|Werewolf (Civilian)]] & [[Werewolf|Werewolf (Purgatori Model)]]
|aut=[[User:Killer Wolf|Killer Wolf]]
|date=2011-12-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[WildShips OXP|WildShips]] adds Kiota stations plus four other ships to the game
|aut=[[User:Thargoid|Thargoid]]
|date=2012-05-27
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Wolf_Mk.2_%28Oolite%29|Wolf Mk II]] adds the powerful Wolf Mk II, as seen in Elite-A
|aut=[[User:Ark|Ark]]
|date=2009-07-07
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://wiki.alioth.net/images/0/06/Wolfs_variants.zip Wolfwood's Variants] adds [[Asp_Mk.I|Asp Mk I]], [[Cobra Courier]], [[Cobra Rapier]], [[Drake]], [[Drake Mk II]] & [[Wolf Mk I]]
|aut=Wolfwood
|date=2008-02-02
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[WonderWorm]] adds 'Time Raiders' and a buyable version of their uber-ships. Not to be taken seriously!
|aut=[[User:Smivs|Smivs]]
|date=2012-01-03
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Wormhole restoration OXP|Wormhole Restoration]] adds a new way to leave interstellar space without using fuel, expanding on Thargoid backstory
|aut=[[User:Commander McLane|Commander McLane]]
|date=2011-05-12
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[WPB_OXP|WPB]] adds a different witchpoint beacon in some systems
|aut=[[User:Murgh|Murgh]]
|con=Svengali
|date=2011-10-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.box.net/shared/n9xla832xbccuk7yuzrf Wyvern Ladies] adds armed long-range transports Wyvern Empress & Wyvern Queen, and the Wyvern Princess escort
|aut=Wyvern
|date=2011-08-04
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Xarik]] is an advanced aircraft, last creation of the late Prof. Eisel Xarik. Used by pirates, traders, and hunters
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2010-02-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Xeikil]] adds a player, a GalCop interceptor, and 24 pirate variants of Staer9 Industries' current top fighter
|aut=[[User:Staer9|Staer9]]
|date=2011-05-16
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Xeikil MK2]] adds a player, a GalCop interceptor, and 24 pirate variants of Staer9 Industries' replacement [[Xeikil]]
|aut=[[User:Staer9|Staer9]]
|date=2011-05-22
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Xeptatl's Sword]] An epic mission to thwart the Thargoids, spanning all eight galaxies.
|aut=[[User:Smivs|Smivs]]
|con=Okti, El Viejo, Fatleaf
|date=2011-12-17
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[YellOo Cabs]] adds YellOo Cab Co taxis to the Ooniverse. NPC and Buyable
|aut=[[User:Smivs|Smivs]]
|date=2011-12-23
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11800 Yellow Jacket] is an escort ship from the Killer Insects series
|aut=mandoman
|date=2012-04-01
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Your Ad Here!]] adds Convenience Stores [[Pi-42]], [[Tescoo Oxpress]], [[Star]], [[Mall Wart]], [[Sainsboory's]] & [[Security Sidewinder|security sidewinders]]
|aut=[[User:Griff|Griff]]
|con=DaddyHoggy, Pangloss, Disembodied, Eric Walch
|date=2011-02-20
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[YAHMobile OXP|Your Ad Here Mobile Billboards]] introduces ship-towed mobile ad billboards to route one of most systems
|aut=[[User:Thargoid|Thargoid]]
|date=2012-03-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11384 Zeke Mining Transporter] introduces a cheap, playable ship, and a save file to start as miner
|aut=Captain Patrick
|date=2012-05-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Z-ships]] adds [[Z-ships_Asp_Explorer|Asp Explorer]], [[Z-ships_Cobra_Commodore|Cobra Commodore]], [[Z-ships_Porcupine|Porcupine]] & [[Z-ships_Python_Courier|Python Courier]]
|aut=[[User:Zieman|Zieman]]
|date=2010-03-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9056 Z-GrOovY Griff's Cobra Mk3 Variety Pack] adds multiple Griff's Cobra Mk3 with alternate hull paintings
|aut=dertien
|date=2011-01-27
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11745 Z-GrOovY SML System Stations] adds Griff-based small/medium/large Coriolis, Tetrahedron, and Octahedron stations
|aut=dertien
|date=2012-03-17
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9306 Z-GrOovY System Stations] adds Griff-based Tetrahedron, Octahedron, Coriolis, Dodecahedron, Icosahederon stations
|aut=dertien
|date=2011-03-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9146 Z-GrOovY Viper Raider] adds a new player ship based on the police Viper
|aut=dertien
|date=2011-02-13
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9056 Z-GrOovY YAH Sidewinder Variety Pack] adds multiple Your Ad Here! Constore defenders with alternate hull paintings
|aut=dertien
|date=2011-01-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9056 Z-GrOovY YellOo Cab Variety Pack] adds the Moray Starboat with taxi hull painting
|aut=dertien
|date=2011-01-27
|work=Y}}
|}

== Work in Progress OXPs ==
The following table contains OXPs that either have not yet been released by their authors but are already being discussed on the [http://www.aegidian.org/bb/viewforum.php?f=4 Expansion Pack Forum], or released OXPs that still have WIP status. Links get you either to the respective discussion or the Wiki page if it already exists.
{{OXPListTableHeader}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11817 Amaranth Eagles] mixes ADCK's and Selezen's Eagles and adds new textures
|aut=Amaranth
|con=ADCK, Selezen
|date=2012-04-06
|work=Y}}
{{OXPSortableTableRow
|cat=Misc
|desc=[http://aegidian.org/bb/viewtopic.php?t=8341 Animated Ships] adds animated butterflies flapping their wings as a demo
|aut=[[User:Thargoid|Thargoid]]
|date=2010-08-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11835 Beatnik's Shipset] adds new versions of the core ships with individual HUDs and cross hairs
|aut=Captain Beatnik
|date=2012-04-06
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11282 Borg] adds the Borg cube from Star Trek
|aut=[[User:RyanHoots|RyanHoots]]
|date=2011-12-03
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9864 Cargo Scanner] scans targeted cargo containers to find out what they contain
|aut=Okti
|date=2011-05-17
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11726 Colonization] sets up colonies, huge structures that you can fly into and dock inside
|aut=Okti
|date=2012-03-13
|work=}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[http://aegidian.org/bb/viewtopic.php?p=154365#p154365 Commies Retexture] gives the Commies a new face
|aut=Amaranth
|date=2012-04-06
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11837 Criminal Record] introduces GalCrim and changes the way Oolite remembers criminal records
|aut=Wildeblood
|date=2012-04-12
|work=}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Docking Computers OXP|Docking Computers]] equips new commanders with fee-per-use docking computers while they learn to dock
|aut=Wildeblood
|date=2012-06-03
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://aegidian.org/bb/viewtopic.php?p=156153#p156153 Draven Ships] adds the Oodulldoff station, and Draven Carriers, Gunships, Raiders, Traders, Shuttles, and Krackens
|aut=Ironfist
|date=2011-11-10
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11971 Extended Shipyards v0.1] offers additional options at the shipyard including test-flights, hire, and ship storage. Requires Oolite 1.77(trunk/nightly)
|aut=[[User:Capt. Murphy|Capt. Murphy]]
|date=2012-05-20
|work=N*}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10794 External Missiles HUD] allows control over external missile pylons
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-09-04
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11787 FE2 Imperial Courier] will be a new version of the ship from Frontier Elite 2
|aut=dertien
|date=2012-03-29
|work=}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?p=160986#p160986 Hornet] adds a ship that looks like a hornet
|aut=mandoman
|date=2012-01-02
|work=}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11775 Ico Station V2] adds a new Icosahedron station based on Griff's textures
|aut=dertien
|date=2012-03-24
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[[Jaguar_Company|Jaguar Company]] adds in an Elite group of pilots to patrol the space lanes in Anarchy, Feudal and Multi-Government systems
|aut=[[User:Tricky|Tricky]]
|date=2012-06-13
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.box.net/shared/0i2fnrc175t Katipo] adds a very fast, moderate maneuverability, low cargo ship with low thrust
|aut=[[User:Simon_B|SimonB]]
|date=2011-03-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Koneko Industries OXP]] adds several new ships by [[Koneko Industries]] to the Ooniverse.
|aut=[[User:RyanHoots|Ryan Hoots]]
|date=2012-01-11
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9441 Miner Pod] breaks up asteroids and collects the splinters
|aut=Okti
|date=2011-03-23
|work=Y}}
{{OXPSortableTableRow
|cat=Activities
|desc=[http://aegidian.org/bb/viewtopic.php?t=8275 Mining] adds mines to protect and provide resources for to get gold
|aut=docwild
|date=2010-07-28
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[More Core Player Ships OXP]] adds more player buyable ships.
|aut=[[Ryan Hoots]]
|date=2011-12-02
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[[Nuit Space Station OXP|Nuit Space Station]] is the newest creation of [[Isis Interstellar]]
|aut=[[User:Killer_Wolf|Killer Wolf]]
|date=2009-11-11
|work=Y}}
{{OXPSortableTableRow
|cat=Dockables
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11711 Oolific Princess] adds a dockable starliner
|aut=SimonB
|date=2012-03-15
|work=}}
{{OXPSortableTableRow
|cat=Missions
|desc=[http://aegidian.org/bb/viewtopic.php?p=130221#p130221 Oresrati Challenge] adds a fun mission to the loneliest system of the Ooniverse, Oresrati
|aut=Okti
|date=2011-04-26
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10820 Peregrine Fighter] is a very small stand-alone ship in its early design stages
|aut=Wyvern
|date=2011-09-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9946 Phantom] is a trader/fighter from [[Isis Interstellar]] with external missiles
|aut=[[User:Killer_Wolf|Killer Wolf]]
|date=2011-05-27
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.aegidian.org/bb/viewtopic.php?p=158934#p158934 Red Racer] is a heavy long range fighter or escort ship from the coluber shipyard in the Riredi system
|aut=Captain Beatnik
|date=2011-12-03
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?p=138226#p138226 Shield Cycler] distributes shield energy between fore and aft shields
|aut=Lone_Wolf
|date=2011-05-18
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11892 Ship_Storage_Helper v0.15] is a helper OXP with functions to store/restore current ship info. Requires Oolite 1.77(trunk/nightly)
|aut=[[User:Capt. Murphy|Capt. Murphy]]
|date=2012-05-20
|work=N*}}
{{OXPSortableTableRow
|cat=Activities
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=5484 Solar System] adds extra planets and jump gates to a system
|aut=[[User:Frame|Frame]]
|date=2009-01-11
|work=}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11619 Storm Shipyards] work on alternative versions of the core ship set
|aut=[http://aegidian.org/bb/memberlist.php?mode=viewprofile&u=18304 Storm]
|date=2012-02-12
|work=}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9472 Sun Skimmer Pod] adds a pod that goes sun skimming and returns full of fuel
|aut=Okti
|date=2011-03-21
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9488 Target Tracker] aligns your ship on your target
|aut=Okti
|date=2011-03-23
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9353 Thor Class Supercarrier] adds a Navy Carrier as a replacement pack for the Behemoth and the Galactic Navy
|aut=dertien
|date=2011-03-03
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10809 Trident Shipyard Corp] adds the Trident Privateer Mark II in trader, hunter, pirate, and police versions
|aut=Cmdr Vault
|date=2012-04-05
|work=Y}}
{{OXPSortableTableRow
|cat=Mechanics
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=8254 Trumble Treats] makes Trumbles sellable, and turn to fur when dead. Bought ships have an infection risk
|aut=[[User:Arexack|Arexack_Heretic]]
|date=2010-08-04
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=9242 Wormhole Drones] creates a path of worm holes to lead you to your destination system
|aut=Mauiby de Fug
|date=2011-02-22
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?p=161606#p161606 RL] adds the Yasen-N, a heavy courier-trader with good storage capabilities, and the Skat, a very fast courier
|aut=MiMoriarty
|date=2012-01-09
|work=Y}}
{{OXPSortableTableRow
|cat=Retextures
|desc=[http://www.aegidian.org/bb/viewtopic.php?t=8541 Zygoroids] add new beautifully textured asteroid models to the Ooniverse
|aut=ZygoUgo
|date=2010-10-05
|work=Y}}
|}

== OXPs with Problems ==
The following table contains OXPs that have problems eg. broken download, or have been written for versions of Oolite earlier than the current 1.76
{{OXPListTableHeader}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Amen Bricks Megaships|Amen Brick's Megaships]] adds [[Battleship]]s, [[Biodome]]s, [[Cruiseship]]s, [[Hospitalship]]s, [[Supercargo]]s, [[Superlifter]]s, and [[Yacht - Amen Class|Yacht]]s
|aut=[[User:Amen_Brick|Amen Brick]]
|date=2008-07-11
|work=N}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[ADCK%27s Behemoths]] adds shadered versions of the [[Behemoth]], [[Galactic Navy OXP|Galactic Navy]] ships and stations, and then some
|aut=[[User:ADCK|ADCK]]
|con=Aegidian, pagroove, Nemoricus, Selezen, Simon B
|date=2010-04-20
|work=N}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Cataclysm OXP|Cataclysm]] takes up the threads of Constrictor Hunt and Thargoid Plans, and sends you on your biggest Navy mission yet
|aut=[[User:Commander_McLane|Commander McLane]]
|date=2009-01-06
|work=N}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Clear Skies OXP|Clear Skies]] reduces nebula effects and dims stars. (OXP is an un-installable mess!)
|aut=[[User:Johnsmith|johnsmith]]
|date=2006-11-12
|work=N*}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://www.aegidian.org/bb/viewtopic.php?t=8526 Comms Demo] provides a way to communicate with NPC ships
|aut=[[User:Kaks|Kaks]]
|date=2009-10-26
|work=N}}
{{OXPSortableTableRow
|cat=Missions
|desc=[http://www.box.net/shared/mq1mzoc79t Constrictor Mission Hints] adds more hints for those doing the native Constrictor Mission
|aut=[[User:Arexack|Arexack Heretic]]
|date=2010-08-04
|work=N}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Kirin#Download|Kirin Sport]] adds a a smaller, faster, more agile - and less well armed - civilian variant of the [[Kirin]]
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2009-07-22
|work=N}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Localhero_OXP|Localhero]] adds a mission campaign in the first galaxies
|aut=[[User:Svengali|Svengali]]
|date=2008-04-09
|work=N}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Longshot]] adds the Longshot fighter / trader, regarded by many as a cheaper alternative to the Cobra Mk III
|aut=[[User:Dr. Nil|Dr. Nil]]
|date=2007-02-24
|work=N}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Orb]] adds a new alien race, which might help GalCop in the battle against the Thargoids.
|aut=Charlie
|date=2007-02-13
|work=N}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Personalities OXP|Personalities]] adds a bunch of unique, well-known personalities from the Bulletin Board to the Ooniverse
|aut=[[User:Commander_McLane|Commander McLane]]
|date=2009-11-05
|work=N}}
|}
[[Category:Oolite expansion packs]]
[[Category:OXP Lists]]
[[Category:Factual]]

GalCop Rewards

2012-06-17T23:52:08Z

PG1:

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/LsHkkq GalCop_Rewards.1.0.0.oxp.zip]

==Fast Facts==
{{OXPLevel|0|0}}
{{Infobox OXPb| title = GalCop Rewards
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Adds GalCop Reward Points
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12061 BB-Link]
}}

Safe Docking

2012-06-17T23:49:58Z

PG1:

==Introduction==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born. See [[GalCop Rewards|GalCop Rewards OXP]] for details. Well, you may be wondering what this has to do with this Safe Docking OXP. Poor docking was one of the main issues GalCop had with bad piloting. Safe Docking is GalCop's attempt for rewarding pilots for docking at participating stations in a safe manner and makes use of GalCop Rewards to do this.

==Overview==

With Safe Docking OXP how fast and carefully you dock now determines whether you get rewarded or receive a penalty. Dock too fast and you will be get a penalty (and may be an insult). Dock at an acceptable speed and you may get rewarded with GalCop Reward Points. Generally the slower the better, but be warned, go too slowly or scrape your ship's hull and the station's Dockmaster will not be pleased. If you only docked in an "Ok" fashion you may not get a message at all.

Only manual docking counts. If you dock using a Docking Computer (both automatic or Instant docking) you will not be rewarded. Also cheating by using the Docking Computer to get you almost there and turning it off and finishing docking manually is also detected and will not count as manual docking.

'''The following table shows the speeds and their results:'''
{| class="wikitable"
!Speed Range
!Rating
!Reward
!Penalty
|-
|>=0m/s and <25m/s
|Too Slow
|
|Lose 5 Credits
|-
|>=25m/s and <50m/s
|Excellent
|10 Reward Points
|
|-
|>=50m/s and <75m/s
|Very Good
|5 Reward Points
|
|-
|>=75m/s and <100m/s
|Good
|1 Reward Points
|
|-
|>=100m/s and <125m/s
|Ok
|
|
|-
|>=125m/s and <225m/s
|Poor
|
|Lose 1 Reward Points and fined 20 Credits
|-
|>=225m/s and <300m/s
|Reckless
|
|Lose 5 Reward Points and fined 40 Credits
|-
|>=300m/s and <400m/s
|Dangerous
|
|Lose all Reward Points and fined 100 Credits
|-
|>=400m/s and <550m/s
|Very Dangerous
|
|Lose all Reward Points and fined 500 Credits
|-
|>=550m/s
|Criminal
|
|Lose all Reward Points, fined 1000 Credits and gain 5 Credits bounty
|-
|<225m/s and scraped ship during docking
|Collided
|
|Lose 2 Reward Points and fined 25 Credits
|}

The only variation from the above is if you are under attack '''AND''' at low energy. In this situation you will let off any penalty. Being under attack is defined by being attacked by at least one non-police ship (by laser or missile) and each attacking ship still has you as its target. (Still targeted is checked every 2 seconds.) If you have been attacked by a cloaked ship within the last 10 seconds then this also counts as under attack. Low Energy is when your energy is less than 128 which is less than 2 full bars on a ship's HUD.

All fines are reduced not take you below 100 credits. So if you are below 100 credits you won't be fined.

If you re-visit the same station in the scheme within the last hour (in-game hours) then you do not get any Rewards Points. The Dockmaster will let you know if this is the case. Penalties for bad docking will still apply though.

==Participating Stations==

All system Main Stations are in the scheme but also when you enter the station aegis you will get a message telling you that the station is in the scheme e.g. “The Dockmaster would like to let you know that Lave Orbital Station is a participant in the Safe Docking Rewards Scheme.”

Any other station or carrier you will receive an equivalent message if you enter the region within the aegis distance around them (2x scanner radius). In Oolite aegis only normally applies to the main station but it is “reproduced” for these other stations.

==My Speed==

If you install OXPConfig OXP version 2.0.10 or higher then you can use that to modify the OXP parameter that adds to a station's arrival message a notification of your arrival speed. This parameter is off by default.

==Docking Clearance==

If docking clearance requirement is turned on (usually by installing the Docking Clearance OXP) then docking without clearance means you get no Reward Points added for good docking. Penalties for bad docking will still apply though.

==Dependencies==

{{OXPConfig-small}}
[[GalCop Rewards|GalCop Rewards OXP]]

Optional: [[OXPConfig|OXPConfig OXP version 2.0.10 or higher]]

==Download==
[http://bit.ly/M9ZDfu Safe_Docking.1.0.0.oxp.zip]

==Fast Facts==
{{OXPLevel|0|1}}
{{Infobox OXPb| title = Safe Docking
|version = 1.0.0
|release = 2012-06-16
|license = CC-by-nc-sa-3.0
|features = Manual Docking Behaviour
|category = Mechanics
|author = Phantor Gorth
|download = [[#Download|See Download]]
|feedback = [http://aegidian.org/bb/viewtopic.php?f=4&t=12062 BB-Link]
}}

GalCop Rewards

2012-06-17T23:34:58Z

PG1: GalCop Rewards OXP

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. You will normally need to install another OXP that rewards points. E.g. [[Safe Docking]].

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/LsHkkq GalCop_Rewards.1.0.0.oxp.zip]

Safe Docking

2012-06-17T23:34:38Z

PG1: Safe Docking OXP

==Introduction==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born. See [[GalCop Rewards|GalCop Rewards OXP]] for details. Well, you may be wondering what this has to do with this Safe Docking OXP. Poor docking was one of the main issues GalCop had with bad piloting. Safe Docking is GalCop's attempt for rewarding pilots for docking at participating stations in a safe manner and makes use of GalCop Rewards to do this.

==Overview==

With Safe Docking OXP how fast and carefully you dock now determines whether you get rewarded or receive a penalty. Dock too fast and you will be get a penalty (and may be an insult). Dock at an acceptable speed and you may get rewarded with GalCop Reward Points. Generally the slower the better, but be warned, go too slowly or scrape your ship's hull and the station's Dockmaster will not be pleased. If you only docked in an "Ok" fashion you may not get a message at all.

Only manual docking counts. If you dock using a Docking Computer (both automatic or Instant docking) you will not be rewarded. Also cheating by using the Docking Computer to get you almost there and turning it off and finishing docking manually is also detected and will not count as manual docking.

'''The following table shows the speeds and their results:'''
{| class="wikitable"
!Speed Range
!Rating
!Reward
!Penalty
|-
|>=0m/s and <25m/s
|Too Slow
|
|Lose 5 Credits
|-
|>=25m/s and <50m/s
|Excellent
|10 Reward Points
|
|-
|>=50m/s and <75m/s
|Very Good
|5 Reward Points
|
|-
|>=75m/s and <100m/s
|Good
|1 Reward Points
|
|-
|>=100m/s and <125m/s
|Ok
|
|
|-
|>=125m/s and <225m/s
|Poor
|
|Lose 1 Reward Points and fined 20 Credits
|-
|>=225m/s and <300m/s
|Reckless
|
|Lose 5 Reward Points and fined 40 Credits
|-
|>=300m/s and <400m/s
|Dangerous
|
|Lose all Reward Points and fined 100 Credits
|-
|>=400m/s and <550m/s
|Very Dangerous
|
|Lose all Reward Points and fined 500 Credits
|-
|>=550m/s
|Criminal
|
|Lose all Reward Points, fined 1000 Credits and gain 5 Credits bounty
|-
|<225m/s and scraped ship during docking
|Collided
|
|Lose 2 Reward Points and fined 25 Credits
|}

The only variation from the above is if you are under attack '''AND''' at low energy. In this situation you will let off any penalty. Being under attack is defined by being attacked by at least one non-police ship (by laser or missile) and each attacking ship still has you as its target. (Still targeted is checked every 2 seconds.) If you have been attacked by a cloaked ship within the last 10 seconds then this also counts as under attack. Low Energy is when your energy is less than 128 which is less than 2 full bars on a ship's HUD.

All fines are reduced not take you below 100 credits. So if you are below 100 credits you won't be fined.

If you re-visit the same station in the scheme within the last hour (in-game hours) then you do not get any Rewards Points. The Dockmaster will let you know if this is the case. Penalties for bad docking will still apply though.

==Participating Stations==

All system Main Stations are in the scheme but also when you enter the station aegis you will get a message telling you that the station is in the scheme e.g. “The Dockmaster would like to let you know that Lave Orbital Station is a participant in the Safe Docking Rewards Scheme.”

Any other station or carrier you will receive an equivalent message if you enter the region within the aegis distance around them (2x scanner radius). In Oolite aegis only normally applies to the main station but it is “reproduced” for these other stations.

==My Speed==

If you install OXPConfig OXP version 2.0.10 or higher then you can use that to modify the OXP parameter that adds to a station's arrival message a notification of your arrival speed. This parameter is off by default.

==Docking Clearance==

If docking clearance requirement is turned on (usually by installing the Docking Clearance OXP) then docking without clearance means you get no Reward Points added for good docking. Penalties for bad docking will still apply though.

==Dependencies==

[[GalCop Rewards|GalCop Rewards OXP]]

Optional: [[OXPConfig|OXPConfig OXP version 2.0.10 or higher]]

==Download==
[http://bit.ly/M9ZDfu Safe_Docking.1.0.0.oxp.zip]

GalCop Rewards

2012-06-17T23:06:47Z

PG1: Created page with "== Introduction == By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limit..."

== Introduction ==

By the year 3136 GalCop had reached a point where too many pilots were committing lots of minor misdemeanours… docking whilst drunk, breaking speed limits in reduced speed zones, docking without permission, etc. Trying to set fines and penalties hadn’t reduced this ever growing problem. Their latest solution was to replace or augment the stick with a carrot, and so they took the lottery concept as used by the government of Riveis, and the concept of a loyalty reward card system, and merged them together and GalCop Rewards was born.

== Overview ==

GalCop Rewards is a points-based lottery and rewards system. The aim is to gain reward points. If you have rewards points you get entered into the lottery that happens every 50 hours*. Playing the lottery costs 1 reward point. If you have 5 reward points then you get entered in the next 5 lotteries and then it will stop. If you win the lottery you win vouchers as prizes●. The more points you have the better the type of voucher you can win. These vouchers can be anything like “percentage savings on fuel”, “free repairs”, “Get 1t of a commodity when you purchase Xt of the same commodity†”, “Percentage saving on equipment”. Also this voucher can be valid for a number of redeems. You do not have to do anything to redeem your voucher. If you buy the relevant equipment or commodities at a participating station▲ the voucher will be automatically redeemed‡.

'''Please Note:'''

All vouchers cost reward points so you can not redeem your voucher if you do not have enough reward points.

As GalCop can not know where you are in space when the lottery is played you will be informed of any voucher, or vouchers, you win when you arrive or whilst at a participating station.

Any financial savings a voucher gives are rewarded back to you after a purchase so you still need enough money to make the purchase without the voucher.

You only get awarded equipment based vouchers for equipment which are referenced with wildcards (usually missiles) or specific equipment that your ship can take and you don't already have.

<nowiki>*</nowiki>The higher the number of points you have the less likely you are to win the lottery. Though this plateaus. This is because the vouchers you can win with high points get so much better. Also this is to encourage new pilots with initial easier wins. (Starts at 1 in 5 and reduces to 1 in 15 by 500 points or higher.)

●You only get one voucher at any time. If more than one lottery was played since it was last checked you may win more than one voucher. If you win more than one or you have an existing voucher you will get to choose which voucher you want to keep, whether that be one of the new ones or the existing one. If you choose a new one that voucher will replace the existing one.

†Only normally legal, non-precious, commodities will be included in the vouchers. GalCop purchases some tonnes of these commodities from the market for these rewards in advance, so don't be worried if there doesn't appear to be enough at the station's market.

▲By default only the main station of each system is participating in this scheme. Other stations may be added by other OXPs.

‡With commodity based vouchers you may not have room in your cargo bay for all the additional tonnes so you only get what you have room for. As vouchers are for one off purchases partial rewards are considered as a full redeem and you will still reduce the remaining number of redeems or lose the voucher. You may not collect the missing commodities later. Only if you have no room at all will the voucher not be redeemed.

==Earning Reward Points==

Generally this isn't part of this OXP. You will normally need to install another OXP that rewards points. E.g. Safe Docking.

But there is one inbuilt way to earn points though and that is to purchase equipment (standard equipment by default) without redeeming a voucher when doing so.

==Manifest Screen==

To see how many Reward Points you have and what voucher you have go to the Manifest screen (F5-F5). The line in the Manifest screen with your remaing Reward Points also tells you approximately when the next lottery will be. Also if you are in space it will tell you how many lotteries have passed.

==Download==
[http://bit.ly/LsHkkq GalCop_Rewards.1.0.0.oxp.zip]

Oolite planet list

2012-04-22T10:36:51Z

PG1:

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. In the original planet lists posted, references to a planet must subtract 1 from the planet number. The Technology Levels in the ''original'' planet lists posted already have the 1 subtracted as required by the '' plist '', whereas that displayed to the player has 1 added. In the ''revised'' planet lists and ''table summaries'' posted the Technology Level has the 1 added that the player sees; whereas the planet numbering starts at zero (indicated by the # symbol) to agree with the charts posted.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/HYuwRq spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions and there is now a statistics sheet.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The new Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[http://s248731467.onlinehome.us/Oolite_Maps_-_Full_Set.zip Zipped set of all 8 Vector Maps]

[http://s248731467.onlinehome.us/Oolite_Maps_-_Full_Set_-_Printer_Friendly.zip Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Oolite planet list

2012-04-20T21:33:38Z

PG1:

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. In the original planet lists posted, references to a planet must subtract 1 from the planet number. The Technology Levels in the ''original'' planet lists posted already have the 1 subtracted as required by the '' plist '', whereas that displayed to the player has 1 added. In the ''revised'' planet lists and ''table summaries'' posted the Technology Level has the 1 added that the player sees; whereas the planet numbering starts at zero (indicated by the # symbol) to agree with the charts posted.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://bit.ly/HYuwRq spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The new Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[http://s248731467.onlinehome.us/Oolite_Maps_-_Full_Set.zip Zipped set of all 8 Vector Maps]

[http://s248731467.onlinehome.us/Oolite_Maps_-_Full_Set_-_Printer_Friendly.zip Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Oolite planet list

2012-04-20T19:59:22Z

PG1:

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. In the original planet lists posted, references to a planet must subtract 1 from the planet number. The Technology Levels in the ''original'' planet lists posted already have the 1 subtracted as required by the '' plist '', whereas that displayed to the player has 1 added. In the ''revised'' planet lists and ''table summaries'' posted the Technology Level has the 1 added that the player sees; whereas the planet numbering starts at zero (indicated by the # symbol) to agree with the charts posted.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [http://dl.dropbox.com/u/1380916/Oolite/Oolite_galaxies.zip spreadsheet] (please note that this spreadsheet is in OpenDocument format) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies. UPDATE: It now calculates the planet descriptions.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The new Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[http://s248731467.onlinehome.us/Oolite_Maps_-_Full_Set.zip Zipped set of all 8 Vector Maps]

[http://s248731467.onlinehome.us/Oolite_Maps_-_Full_Set_-_Printer_Friendly.zip Zipped set of all 8 Vector Maps (print versions)]

[[Category:Oolite]][[Category:Classic]]

Factions OXP

2012-04-13T18:54:45Z

PG1: New Version. New Download Link. On Behalf of m4r35n357 (Ian Smith)

__NOTOC__
Factions adds a point of interest to multi-government systems:

* Teams from anarchy, feudal, dictatorship, and communist systems approach the midpoint of the space lane and start fighting, They only fight with ships of opposing factions. Team members call for assistance when their energy is low. Whether they are being helped depends on how occupied the other team members are at the time.
* The player may opt to express his political views by attacking ships from one or more of the factions, they will remember this for the duration of the run only. Whether you pay the ultimate price depends again on how busy the particular faction member are. If you kill one of them, prepare to die!
* Your scanner differentiates between factions by color to help you sort out who is who.

==Danger Level==
{{OXPLevel|0}}
This OXP does not in itself add to the danger level, that is purely up to the player.

==Other Uses==
During play testing it also occurred to me that this code would be useful for ship combat/uberness testing too, eg. a team of stock NPC cobras vs your brand spanking new ship. There are lots of good stats available from the extensive debugging I've built in too. Anyway, here's the code, you need the systems dependencies (or you can edit shipdata.plist to taste) and CCL. I use colour coding for the scanner so I know what's going one, see script.js for colours. Logging is enabled, and script.js has some other config points to look at.

==Dependencies==
* Oolite 1.75 or later
* [[Cabal Common Library]] v1.2 or later (for random integer fuction)
* [[Anarchies OXP|Anarchies]], [[Commies]], [[Dictators OXP|Dictators]], [[Feudal States]], [[Galactic Navy OXP|Galactic Navy]], and your choice of either [[Behemoth]] or [[ADCK's Behemoths]]

==Copyright & License==
Factions is © 2011 m4r35n357 (Ian Smith)

This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

==Revision History==
Version 1.11 (05.04.2012): Mercenary immersion enhancement: the various participants might just recognize you in future battles if you annoy them enough. Reduced the default odds of a battle to 25%, tune to taste.

Version 1.10 (29.07.2011): Even better confinement of combatants, more ship types for commies & dictators, fixed bug where player enemy status was remembered until game exit, fairer starting conditions, dictators can't race to start & ambush everyone now

Version 1.9 (22.07.2011): Better confinement of combatants, easier to use uber mode

Version 1.8 (04.07.2011): Fix obscure escort bug, remove automatic flee response, but let non-ecm ships still flee

Version 1.7 (27.06.2011): Various AI tweaks, add a GalCop task force

Version 1.6 (13.06.2011): Comms messages between faction members, plasma-equipped NPCs avoid friendly fire, number of factions dependent on tech level, others

Version 1.5 (31.05.2011): Removed unused shipdata entries

Version 1.4 (30.05.2011): Commies now have Giant Rays available, GalCop can now have a Transport or Behemoth instead of the Frigate

Version 1.3 (25.05.2011): Start factions further away from battle site to allow player more time to see the early stages

Version 1.2 (24.05.2011): Add licence to README, add danger level to README

Version 1.1 (24.05.2011): Raise faction membership to 16 (+ any escorts), make it more dangerous to kill a faction member

Version 1.0 (24.05.2011): Botched first release

==Download==
[http://www.box.com/s/5649f8449570ee392b3c Version 1.11] from box.com

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

Oolite planet list

2011-11-07T06:54:46Z

PG1:

== Overview ==

Although this list was taken from Oolite the data applies well to the [[BBC_Micro|BBC Micro]] version of Classic Elite, and some other versions.

Each entry shows the system number, name, coordinates, tech level, inhabitants, government and a comment on the system.

For OXP writers, note that references to a particular galaxy in [[Oolite]] (in a [[Planetinfo.plist]] entry for example), should ''subtract 1 from the galaxy number'' – Galaxy 1 is referred to as 0, etc. In the original planet lists posted, references to a planet must subtract 1 from the planet number. The Technology Levels in the ''original'' planet lists posted already have the 1 subtracted as required by the '' plist '', whereas that displayed to the player has 1 added. In the ''revised'' planet lists and ''table summaries'' posted the Technology Level has the 1 added that the player sees; whereas the planet numbering starts at zero (indicated by the # symbol) to agree with the charts posted.

* A spreadsheet of all galaxies can be downloaded in [[Media:Galaxies.zip|Excel format]] or [[Media:Galaxies_Ods.zip|Open Document format]].

* Downloadable vector graphic PDF's of the 8 charts have also been created and can be downloaded from the [[#Galaxies | ''links below'']].

=== Where do these crazy names come from? ===

If you read through the source code and/or binary for either Elite or Oolite, you will not find any text containing the list of planets and their properties. The entire universe (including the famous [http://www.frontier.co.uk/games/older/elite/faq.html edible poet]) is constructed programmatically (using a truncated Fibonacci function) from a handful of seed numbers and the strings "ABOUSEITILETSTONLONUTHNOAL" (used by the planet description string) and " ' 'LEXEGEZACEBISOUSESARMAINDIREA'ERATENBERALAVETIEDORQUANTEISRION" which is used both by the planet description string and to generate all the system names in the 8 Galaxies (the single quotes indicate placeholders where the planet name generation can be terminated early). The algorithm was reverse-engineered from the original BBC disk by [[ Christian Pinder]], and implemented in Objective-C for Oolite. Further details are given in the discussion of Elite's [[Random_number_generator|random number generators]].

* In this [[Media:Oolite_galaxies.zip|spreadsheet]] ('''There is a bug in this spreadsheet I wrote. I am waiting on the uploading of my fixed version which I can not do myself. To fix it yourself change cell AG5 to read "=((AF5-1)*4+AA5+AD5+1)/10" without quotes and copy down. - PhantorGorth''') (please note that this spreadsheet is in OpenDocument format and can be read by OpenOffice.org and many others applications including Microsoft Excel with the appropriate plug-in) you can see some of the algorithms in action where they are used to calculate the names, positions, inhabitants and other parameters for all 256 planets for a selected Galaxy plus a plot of the Galaxy (Sorry, but no links between worlds are plotted). You can also use this to view what could have been if a different seed number was used for the Galaxies.

* A related spreadsheet showing useful trading routes is also available for [http://www.box.net/shared/bchkkloi32 download].

* The files used to build the vector maps are all available online for download [http://www.crimsonforge.co.uk/cloister/OOmap_toolkit.zip HERE]. These require adobe Illistrator 10 to open.

== Galaxies ==
# [[Image:StarChart-Galaxy-000.png|50px|Jump route chart of galaxy 1]] [[Oolite planet list/Galaxy 1|Galaxy 1]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G1.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G1.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G1.pdf US Mirror] -- [[Sector1/Index|The new Galaxy Guide]]
# [[Image:StarChart-Galaxy-001.png|50px|Jump route chart of galaxy 2]] [[Oolite planet list/Galaxy 2|Galaxy 2]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G2.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G2.pdf print version] --[http://s248731467.onlinehome.us/OOmap_G2.pdf US Mirror; Update needed] -- [[Sector2/Index|The New Galaxy Guide]]
# [[Image:StarChart-Galaxy-002.png|50px|Jump route chart of galaxy 3]] [[Oolite planet list/Galaxy 3|Galaxy 3]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G3.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G3.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G3.pdf US Mirror]
# [[Image:StarChart-Galaxy-003.png|50px|Jump route chart of galaxy 4]] [[Oolite planet list/Galaxy 4|Galaxy 4]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G4.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G4.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G4.pdf US Mirror]
# [[Image:StarChart-Galaxy-004.png|50px|Jump route chart of galaxy 5]] [[Oolite planet list/Galaxy 5|Galaxy 5]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G5.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G5.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G5.pdf US Mirror; Update needed]
# [[Image:StarChart-Galaxy-005.png|50px|Jump route chart of galaxy 6]] [[Oolite planet list/Galaxy 6|Galaxy 6]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G6.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G6.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G6.pdf US Mirror]
# [[Image:StarChart-Galaxy-006.png|50px|Jump route chart of galaxy 7]] [[Oolite planet list/Galaxy 7|Galaxy 7]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G7.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G7.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G7.pdf US Mirror]
# [[Image:StarChart-Galaxy-007.png|50px|Jump route chart of galaxy 8]] [[Oolite planet list/Galaxy 8|Galaxy 8]] -- [http://www.crimsonforge.co.uk/cloister/OOmap_G8.pdf Vector Map] -- [http://www.crimsonforge.co.uk/cloister/gOOmap_G8.pdf print version] -- [http://s248731467.onlinehome.us/OOmap_G8.pdf US Mirror]

[[Category:Oolite]][[Category:Classic]]

Handling OXP Dependencies with JavaScript

2010-12-03T08:39:59Z

PG1:

==Loading/Initialisation Dependencies==

=== The Issue ===

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency chain issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

=== Solution ===

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A_Script";
this.author = "Author";
this.copyright = "Copyright Info"
this.licence = "License";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// function to handle the initialising of other scripts
function runOtherStartUp(s) {
if (worldScripts[s].startUp) worldScripts[s].startUp(); // Call the other startUp.
if (worldScripts[s].startUp) delete worldScripts[s].startUp; // Make sure the other startUp is deleted as it may not be written using
// this template.
};

// calling each dependency:
runOtherStartUp("Oxp_B_Script") // Repeat for each OXP script that this OXP script depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
this.Oxp_X_Script_Exists = !!worldScripts["Oxp_X_Script"]; // Repeat for other similar OXP script checks.
// Please note that the two not (!) operators here work by have one convert the existence of the script object into a boolean which has
// its true/false status the wrong way round for our needs and then the other swaps the boolean's status to way we need it.

// Do Oxp_A_Script's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP script goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

==Event Dependencies==

===The Issue===

There are also times when you will want for a particular event the code from your OXP to run after the code from another OXP. The method chosen above for loading can not be used for events as deleting the function will mean the event code will work once and the next time the event is triggered there is no code to call. This issue therefore requires another solution.

===Solution===

The current solution for this is to use the timer mechanism. In essence this involves using a timer started from your script's event to trigger code to be called later after the code from the dependency OXP's event. This method does suffer from the fact that you can not handle dependency chains very well (if at all) and you have to set the timer to trigger long enough afterwards to guarantee that the code your code depends on has already been run.

This could be done using this code:

<pre>this.eventName = function {
this.eventTimer = new Timer(this, this.funcToRun, secondsToWait);
}

this.funcToRun = function {
// Put your event code here.
}</pre>

Choose the appropriate names for the eventName (see [[Oolite_JavaScript_Reference:_ship_script_event_handlers|Ship Script Event Handlers]] or [[Oolite_JavaScript_Reference:_world_script_event_handlers|World Script Event Handlers]]), eventTimer and funcToRun, and now many seconds to wait (secondsToWait) before it launches (usually about 1 second).

== See Also ==
* [[Scripting Oolite with JavaScript]]

[[Category:Oolite scripting]]

Handling OXP Dependencies with JavaScript

2010-11-07T16:47:53Z

PG1:

==Loading/Initialisation Dependencies==

=== The Issue ===

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency chain issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

=== Solution ===

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A_Script";
this.author = "Author";
this.copyright = "Copyright Info"
this.licence = "License";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// function to handle the initialising of other scripts
function runOtherStartUp(s) {
if (worldScripts[s].startUp) worldScripts[s].startUp(); // Call the other startUp.
if (worldScripts[s].startUp) delete worldScripts[s].startUp; // Make sure the other startUp is deleted as it may not be written using
// this template.
};

// calling each dependency:
runOtherStartUp("Oxp_B_Script") // Repeat for each OXP script that this OXP script depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
this.Oxp_X_Script_Exists = !!worldScripts["Oxp_X_Script"]; // Repeat for other similar OXP script checks.
// Please note that the two not (!) operators here work by have one convert the existence of the script object into a boolean which has
// its true/false status the wrong way round for our needs and then the other swaps the boolean's status to way we need it.

// Do Oxp_A_Script's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP script goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

==Event Dependencies==

===The Issue===

There are also times when you will want for a particular event the code from your OXP to run after the code from another OXP. The method chosen aboved for loading can not be used for events as deleting the function will mean the event code will work once and the next time the event is triggered there is no code to call. This issue therefore requires another solution.

===Solution===

The current solution for this is to use the timer mechanism. In essence this involves using a timer started from your script's event to trigger code to be called later after the code from the dependency OXP's event. This method does suffer from the fact that you can not handle dependency chains very well (if at all) and you have to set the timer to trigger long enough afterwards to guarantee that the code your code depends on has already been run.

This could be done using this code:

<pre>this.eventName = function {
this.eventTimer = new Timer(this, this.funcToRun, secondsToWait);
}

this.funcToRun = function {
// Put your event code here.
}</pre>

Choose the appropriate names for the eventName (see [[Oolite_JavaScript_Reference:_ship_script_event_handlers|Ship Script Event Handlers]] or [[Oolite_JavaScript_Reference:_world_script_event_handlers|World Script Event Handlers]]), eventTimer and funcToRun, and now many seconds to wait (secondsToWait) before it launches (usually about 1 second).

== See Also ==
* [[Scripting Oolite with JavaScript]]

[[Category:Oolite scripting]]

Handling OXP Dependencies with JavaScript

2010-11-07T16:44:32Z

PG1:

==Loading/Initialisation Dependencies==

=== The Issue ===

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency chain issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

=== Solution ===

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A_Script";
this.author = "Author";
this.copyright = "Copyright Info"
this.licence = "License";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// function to handle the initialising of other scripts
function runOtherStartUp(s) {
if (worldScripts[s].startUp) worldScripts[s].startUp(); // Call the other startUp.
if (worldScripts[s].startUp) delete worldScripts[s].startUp; // Make sure the other startUp is deleted as it may not be written using this template.
};

// calling each dependency:
runOtherStartUp("Oxp_B_Script") // Repeat for each OXP script that this OXP script depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
this.Oxp_X_Script_Exists = !!worldScripts["Oxp_X_Script"]; // Repeat for other similar OXP script checks.
// Please note that the two not (!) operators here work by have one convert the existence of the script object into a boolean which has its true/false status the wrong way round for our needs and then the other swaps the boolean's status to way we need it.

// Do Oxp_A_Script's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP script goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

==Event Dependencies==

===The Issue===

There are also times when you will want for a particular event the code from your OXP to run after the code from another OXP. The method chosen aboved for loading can not be used for events as deleting the function will mean the event code will work once and the next time the event is triggered there is no code to call. This issue therefore requires another solution.

===Solution===

The current solution for this is to use the timer mechanism. In essence this involves using a timer started from your script's event to trigger code to be called later after the code from the dependency OXP's event. This method does suffer from the fact that you can not handle dependency chains very well (if at all) and you have to set the timer to trigger long enough afterwards to guarantee that the code your code depends on has already been run.

This could be done using this code:

<pre>this.eventName = function {
this.eventTimer = new Timer(this, this.funcToRun, secondsToWait);
}

this.funcToRun = function {
// Put your event code here.
}</pre>

Choose the appropriate names for the eventName (see [[Oolite_JavaScript_Reference:_ship_script_event_handlers|Ship Script Event Handlers]] or [[Oolite_JavaScript_Reference:_world_script_event_handlers|World Script Event Handlers]]), eventTimer and funcToRun, and now many seconds to wait (secondsToWait) before it launches (usually about 1 second).

== See Also ==
* [[Scripting Oolite with JavaScript]]

[[Category:Oolite scripting]]

Handling OXP Dependencies with JavaScript

2010-11-07T11:18:13Z

PG1:

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency chain issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "Copyright Info"
this.licence = "License";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do Oxp_A's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

== See Also ==
* [[Scripting Oolite with JavaScript]]

[[Category:Oolite scripting]]

Handling OXP Dependencies with JavaScript

2010-11-07T01:11:50Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "Copyright Info"
this.licence = "License";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do Oxp_A's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

== See Also ==
* [[Scripting Oolite with JavaScript]]

[[Category:Oolite scripting]]

Handling OXP Dependencies with JavaScript

2010-11-07T00:59:47Z

PG1:

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do Oxp_A's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

== See Also ==
* [[Scripting Oolite with JavaScript]]

[[Category:Oolite scripting]]

Scripting Oolite with JavaScript

2010-11-07T00:55:59Z

PG1: /* See Also */

[[Oolite]] 1.68 and later supports scripts written in [http://en.wikipedia.org/wiki/ECMAScript ECMAScript] (more commonly known as [http://en.wikipedia.org/wiki/JavaScript JavaScript]) in addition to its traditional model based on [[property lists]]. This page provides an overview of how JavaScript is used in Oolite. The page [[Oolite JavaScript Reference: object model]] provides reference for Oolite-specific objects and methods. The page [[Oolite JavaScript Reference: world script event handlers]] provides reference for the event handlers Oolite supports. The language standards and some tutorials can be found through the Wiki links provided above.

== Using JavaScript ==

Currently, JavaScript is supported for “worldScripts”, that is, as a replacement for scripts in ''script.plist'' and shipScripts, that acts as expansion for the ships AI. While a ''script.plist'' file may contain any number of separate scripts, a single JavaScript file may contain only one script.

If your OXP only uses one script, place a JavaScript file named ''script.js'' (or ''script.es'') in the OXP’s ''Config'' directory. If you wish to use multiple scripts, you may instead create file named ''world-scripts.plist'' in the ''Config'' directory. This [[property list]] file should consist of an array of worldScript names; the named scripts should exist in a directory named ''Scripts'' inside your OXP. As with most “atomic” files (files which cannot be merged), such script files must have a unique name to avoid conflicts with other OXPs. Using the ''world-scripts.plist'' method, you can combine JavaScript, plist and OOS scripts however you wish.

Whereas plist scripts are based on polling – all scripts are run at semi-regular intervals, whether they need to be or not – scripts written in JavaScript are “event driven” – different functions, or ''event handlers'', in the script are called in response to state changes in the game, or when other events of interest happen. For instance, <code>willExitWitchSpace</code> is called just before player exits witchspace, and <code>alertConditionChanged</code> is called whenever the alert condition changes. See the [[Oolite JavaScript event handler reference|event handler reference]] for a full list of handlers and when Oolite will call them.

The <code>tickle</code> handler is similar to event handlers, but is called periodically at the same times as plist scripts are run – about every 10 seconds, and when certain state changes occur. For efficiency, however, it is best to avoid using <code>tickle</code> if possible.

=== script.js File Template ===

Copy and paste this template into a file called script.js in the OXP Config directory. Ensure you change at least the Name value. '''Every script must have a unique name.''' If multiple scripts with the same name are encountered, Oolite will arbitrary select one and discard the others.

<pre>this.name = "My OXP Script"
this.author = "Your Name Here"
this.copyright = "(C) 2009 Me."
this.licence = "CC-NC-by-SA 2.0"
this.description = "This OXP doesn't do very much yet.";
this.version = "1.0 alpha 1"

/* You can copy and paste this function and just change the "startUp"
to another event name to handle other OXP events (eg "STATUS_DOCKED",
"alertConditionChanged", etc).
*/
this.startUp = function()
{
Log("Initialising OXP " + name)
}</pre>

== See Also ==
* [[Oolite JavaScript event handler reference]]
* [[Oolite JavaScript object model]]
* [[JavaScript test OXP]]
* [[Javascript Operators]]
* [[Handling OXP Dependencies with JavaScript]]

[[Category:Oolite scripting]]

Handling OXP Dependencies with JavaScript

2010-11-07T00:52:44Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do Oxp_A's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

Handling OXP Dependencies with JavaScript

2010-11-06T22:38:33Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0 alpha 1";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do Oxp_A's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear in a sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

Handling OXP Dependencies with JavaScript

2010-11-06T22:37:28Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0 alpha 1";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do Oxp_A's initialisation stuff here as required.

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear the sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

Handling OXP Dependencies with JavaScript

2010-11-06T22:34:30Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case you may find that you need to include those additional OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0 alpha 1";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do initialisation stuff here as required

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear the sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

Handling OXP Dependencies with JavaScript

2010-11-06T22:31:57Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists it is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case may find that you need to include those OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0 alpha 1";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do initialisation stuff here as required

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear the sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

Handling OXP Dependencies with JavaScript

2010-11-06T22:29:02Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Load Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists and it in turn is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case may find that you need to include those OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0 alpha 1";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do initialisation stuff here as required

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear the sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.

Handling OXP Dependencies with JavaScript

2010-11-06T22:28:08Z

PG1: /* Solution */

== The Issue ==

One of the common issues with OXP development is that many OXPs are dependent on the existence of other OXPs. If they only need to exist side by side this isn't a big problem and the player only has to make sure all necessary OXPs are installed. If you need another OXP to be initialised first (have it's startUp function called first) you will run into a problem. An example of this would be if say your OXP added a station above some moons in a range of systems. If your OXP ran before the OXP(s) that created the moons then it may place the stations differently or not at all compared to if it ran later or last.

This problem arises because Oolite does not guarantee the order in which the OXPs are loaded. Some version do load in alphabetical order but that isn't true across the board. There have been solutions to this problem by either running the initialisation code from a timer or from a screen change event instead of the startUp function but these methods are not good for multiple dependency issues and in the case of screen change events do not always trigger. Since version 1.74 of Oolite there has been a much simpler solution.

== Solution ==

Oolite 1.74 removed the automatic calling of OXPs' reset functions (making this.reset redundant) and reloads all functions from the cache when the player dies before calling all the OXPs' startUp functions.

This allows for an OXP to call a dependency OXP's startUp function before it does its own initialising, provided it hasn't been run yet. Then have that startUp function deleted so it can't be called again until the player dies. (Please note that a JavaScript function deleted whilst it is in the middle of being called, that includes subfunctions, will still be fully executed.) This method then works through the dependency chain until all dependencies are initialised.

As an example if OXP_A depends on OXP_B which depends on OXP_C with this method it doesn't matter what order the OXPs get called in:

Oolite's Calling Order: OXP_A, OXP_C, OXP_B. 
*OXP_A's startUp is called first.
*It deletes itself and then looks for the existence of OXP_B's startUp function and as it exists calls it.
*OXP_B's startUp first deletes itself and then looks for the existence of OXP_C's startUp. As it exists and it in turn is called.
*OXP_C startUp first deletes itself and as it doesn't have any dependencies then executes its initialisation code and returns execution back to OXP_B's startUp.
*OXP_B startUp now executes its initialisation code and returns execution back to OXP_A's startUp where it gets to execute its initialisation code.
All the above was within the initial call to OXP_A's startUp.
*Now Oolite will want to call OXP_C's startUp as it is next in its list. As it has already been called and deleted it won't find it and will skip it.
*Finally Oolite will try to call OXP_B's startUp function which also has been deleted and will also therefore be skipped.

The result is that the three OXP's have been initialised in the right order. If you tried this with a different OXP load order the results will be the same.

If the dependency OXP is not using this method you must delete that's startUp function yourself after you have called its startUp function. This may have a subtle knock on effect if that dependency OXP has it own dependencies that are handled in some other way. If that is the case may find that you need to include those OXPs as dependencies of your OXP and call them first.

Well that's the theory, so here is what a OXP template using this idea should look like in practice:

<pre>this.name = "Oxp_A";
this.author = "Author";
this.copyright = "license";
this.description = "Some Description";
this.version = "1.0 alpha 1";

this.startUp = function()
{

delete this.startUp; // Must be done straight away to prevent loops. It doesn't stop this function from working.

// For handling oxps that are written using this template:
if (worldScripts.Oxp_B.startUp) worldScripts.Oxp_B.startUp(); // Calls Oxp_B.startUp as it is required to load before your Oxp_A.
// Repeat above for each OXP that this OXP depends on.

// For handling old oxps that are NOT written using this template:
if (worldScripts.Oxp_Old.startUp)
{
worldScripts.Oxp_Old.startUp(); // Calls Oxp_Old.startUp as it is required to load before your Oxp_A.
delete worldScripts.Oxp_Old.startUp; // You do this as Oxp_Old can't.
}
// Repeat above for each old OXP that this OXP depends on.

// Test for existence of an OXP that isn't required but effects the way this OXP works.
if (worldScripts["Oxp_X"])
{
this.Oxp_X_Exists = true;
}
else
{
this.Oxp_X_Exists = false;
}
// Repeat above for other similar OXP checks.

// Do initialisation stuff here as required

log(this.name + " " + this.version +" loaded."); // This goes last so the load messages appear the sensible order.

}

// The rest of OXP goes here</pre>

Replace the OXP names, repeat the sections and fill the rest of the code as needed.