Elite Wiki - User contributions [en]

Oolite FAQ

2011-12-22T04:06:55Z

Kaks: /* System Requirements */

== Getting Started ==

{{FAQ|question=Where do I get the program? And what about the different versions that exist?|answer= The latest 'official' stable release is version 1.76, and is available on the [http://oolite.org/download.shtml oolite.org download page] for OS X, Windows, and Linux(x86). The last stable release made by the original programmer, Giles Williams (a.k.a. Aegidian) was 1.65 and is best available from his website [http://oolite.aegidian.org/ oolite.aegidian.org]. The latest test releases/development versions can be [http://developer.berlios.de/project/showfiles.php?group_id=3577 downloaded from BerliOS] with installers also available for OS X, Windows and Linux. More detailed information can be found on the [http://aegidian.org/bb/index.php Oolite Bulletin Board], in the respective sections for [http://aegidian.org/bb/viewforum.php?f=10 Oolite-Mac], [http://aegidian.org/bb/viewforum.php?f=9 Oolite-Linux] and [http://aegidian.org/bb/viewforum.php?f=8 Oolite-PC].}}

{{FAQ|question=What's the point of the game?|answer=To fly from planet to planet, buying and selling goods, shooting pirates or committing acts of piracy. There's no goal other than perhaps to achieve the rank of ELITE.}}

{{FAQ|question=I'm still confused, how do I play?|answer=It's a good idea to start with the [http://wiki.alioth.net/images/0/0d/Oolite_1.65_ReadMe.pdf.zip Oolite ReadMe] file for some basic information. For further information you may wish to consult the [http://wiki.alioth.net/index.php/Oolite_Instruction_Manual Oolite Instruction Manual] here on the wiki. A load of helpful information can be obtained from [http://wiki.alioth.net/index.php/Mr_Gimlet Mr Gimlet], the quite talkative dockmaster on Lave Station. If you're a fresh graduate from the Flight Academy on the way to your first ship, you should see him. It's also a good idea to have a look at Ian Bell's [http://www.iancgbell.clara.net/elite/manual.htm Flight Training Manual] for the original BBC Elite, although some of Oolite's control keys are different from the original, so be careful.}}

{{FAQ|question=How do I configure my joystick or gamepad for Oolite in Linux?|answer=See [[Linux Joysticks and Gamepads]].}}

== Gameplay ==

{{FAQ|question=What do the various colors represent on the radar?|answer=White - unpowered items that can't mass-lock the in-system drive (jumpdrive). Green/Yellow - navigation buoys. Yellow - powered craft. Red - powered craft identified as hostile. Green - space stations. Green/Red - thargoids. Purple - police. Blue/Red - police on intercept. Red/Yellow - active mine (about to detonate). Blue/Cyan - witchspace wormhole.}}

{{FAQ|question=I keep crashing when trying to dock. How do I dock manually?|answer=Many young Jamesons have met a sticky end and had to be scraped from the docking port of Lave Station whilst attempting docking. Its fairly easy once you get the hang of it. Check the [[How_to_Dock|How to Dock]] guide from the Galactic Navy Flight Manual. Or you can get the [[Traffic_Control_OXP|Traffic Control OXP]] for friendly instructions given by the station crew as you try to dock.}}

{{FAQ|question=How do I make decent profits?|answer=Trade between a Poor or Average Agricultural and a Rich or Average Industrial planet. Write down the prices for everything on both planets and find out where you make the most profit per ton. You can also download the [http://wiki.alioth.net/images/d/df/OoliteRS_rev1.8.zip Oolite Reference Sheet], which features a table with the average prices. From there you can figure out whether you're on a buyers' or a sellers' market. The [http://wiki.alioth.net/images/9/9e/OoliteTradingChart2.zip Trading Chart] allows you to create your own statistics along your way. [http://www.box.net/shared/bchkkloi32 This spreadsheet] highlights Poor Agricultural and Rich Industrial planets on a star chart (the spreadsheet is in .xls format and needs the Analysis Toolpak installed). You can also earn credits by taking cargo contracts - courier goods of varied type and volume between planets near and far. The spreadsheet helps assess whether you will be be able to complete the contract on time, and so build your reputation as an outstanding courier. Another option is to fit one or more [http://wiki.alioth.net/index.php/Passenger_Berth Passenger Berths] in your ship and earn credits by transporting individuals who, for one reason or another, prefer not to use the commercial Passenger Liners to reach their destination. As with cargo contracts, you can build your reputation up, which will result in your being offered more lucrative fares.}}

{{FAQ|question=It takes so long to get to the station after each jump. Can I do anything to speed the trip up?|answer=Well, space is huge. It is vast. I mean, have you ever imagined a football-field with an orange in one of the goals and a walnut in the other goal? If you haven't, then don't. It takes you nowhere. As will your ship's engine at normal speed. But then that's what your jumpdrive is for. Hit '''J''', and your journey speeds up. Unfortunately your jumpdrive doesn't work when other masses, like ships or planets, are nearby. They will 'lock' it. And in the 'corridor' between the witchpoint and the planet you are very likely to meet other ships. On the other hand there is no rule that you have to stick to the corridor. Just leave it sideways in any direction with your jumpdrive engaged for about 10-15 seconds, and head for the planet then. Makes your voyage much smoother. If you're a bounty-hunter and eager to meet lots of pirates, however, this is not your method of choice.}}

{{FAQ|question=I have already made my first intergalactic jump to Galaxy 2, but now I remember that I forgot my Zero-G cricket set/food blender/deadly lobstoid/edible arts graduate on Lave/Tionisla/Xeesle/Reesdice! Or I just found out that there are some more missions I'd like to do in the first galaxy. So how can I jump back to Galaxy 1?|answer=You can't. Unfortunately due to their very physical nature intergalactic wormholes allow for one-way travel only. Fortunately, though, the intergalactic wormhole in Galaxy 8 connects back to Galaxy 1. So you can go full circle. And you have to, if you want to return to the first galaxy. Of course that will cost you another 5000 credits for each galactic hyperjump. So the complete 8-Galaxies-Sightseeing-Tour has a pricetag of a total 40000 credits.}}

{{FAQ|question=I've got a trumble! First it was cute and fluffy. But then it started to multiply. Even worse, they started to eat everything on board and they are confusing my sights. I don't want them anymore! How can I get rid of them? Help!|answer=First of all, don't feel embarrassed. It happens to all commanders sooner or later. I mean, they're really cute and fluffy, aren't they? But seriously, there are several things you could try. E.g. sell them to other unsuspecting noobs. If you don't find enough willing buyers, you could use your escape capsule and abandon your infested ship, hoping that they haven't yet made it into the escape pod, of course. I mean, you can always hope, can't you? If that all doesn't work for you, just remember the old Klingon saying: 'Revenge is a dish that is best served cold.' Now consider that for trumbles it's just the opposite. Want some BBQ-sauce?}}

{{FAQ|question=My keyboard doesn't have a particular key used by Oolite, or I even want to change the keyboard layout completely to my liking. What can I do to change the keys?|answer=Oolite reads a key configuration file called keyconfig.plist that you can find at /AddOns/Config/keyconfig.plist; that is the Config-folder that you find inside your AddOns-folder; which is where you put your OXPs. (PC-users have to create the folder /AddOns/Config/ first and then drop a copy of the keyconfig.plist found in /Oolite.app/Contents/Resources/Config/ to this folder.) You can open this file in any text editor and change the ASCII values of the keys used to suit your own preferences. Information on the default keys is also found in the [http://wiki.alioth.net/index.php/Oolite_Keyboard_Controls Oolite Keybord Controls-documentation] here on the wiki.}}

{{FAQ|question=I've completed a number of native and OXP missions and my [http://wiki.alioth.net/index.php/Cobra_Mk.3_%28Oolite%29 Cobra Mk. III] has a number of new and funky pieces of equipment. However, I'm planning a change of ship, what pieces of equipment will I lose as a result?|answer=Many missions award equipment as a result of either accepting or completing them. For the majority of ship equipment, trading ships will result in the equipment being sold as well, with a few exceptions. The '''Cloaking Device''' and the '''Mark Transponder Scanner''', available from the (native) Cloaking Device and (OXP) Assassins missions respectively are transferred to your new ship. The '''Naval Energy Unit''', although awarded with the completion of the (native) Thargoid Plans mission, will be sold when you trade ships. However, completing the mission allows you to buy these units from high TL systems.}}

{{FAQ|question=I’m using ECM-hardened missiles, but enemies are still able to destroy them! I never seem to be able to destroy enemy hardheads, though. What gives?|answer=ECM-hardened missiles are not ECM-proof. The probability of a hardened missile being destroyed by ECM is 10%–34% depending on range, and if it is destroyed, there’s a 50% chance that it will detonate. This applies equally to hardened missiles fired by computer-controlled ships and those fired by the player. The most effective use of hardened missiles is to use them against relatively slow targets at moderate range, and only use them on nimble ships if you desperately need to force them to break of an attack. Also, don’t use your ECM until a missile is close to blast range (250 metres).

Specifically, the ECM sends out four pulses with different ranges, at half-second intervals. Each pulse has a 10% chance of destroying each hardhead it encounters. For a missile fired at close range, that’s 1 - 0.94 = 34.39% chance of being destroyed within two seconds.}}

{{FAQ|question=If I believe that sizes and distances in Oolite are given in meters, it is so ''unrealistic''. The planets have a diameter of only 30–50 kilometers, and the suns are only 1000 kilometers away. Can't we get a little more realism in space, please?|answer=First of all, remember that Oolite is a ''game'', not a ''space simulation''. This is because it ''wants to'' be a game, not a sim. So yes, sizes and distances are all messed up. Ships and stations are too big, planets and suns are too small, and too close to each other. But this is ''deliberately'' so, and we are not going to change it.

The reason is simple: Realistic sizes and distances don't make a good game. In reality space is so huge that you never would meet anybody else on your journey. Imagine the dozen or so ships you meet in the 500 or so kilometers between witchpoint and planet spread over the realistic 150 '''million''' kilometers between Sun and Earth. Even if your direction is only one degree off the perfect line, you would miss them all. And how interesting would that be for the gameplay? And finally, if you had a realistically sized station in front of a realistically sized planet, how would you ever even notice it? A grain of sand in front of a, well, '''planet'''. The result would be players in complete loneliness and virtually no interaction with NPCs. An utterly, utterly boring game. Therefore it was the right decision to screw realism in the layout of the planetary systems in Elite and Oolite.}}

== Expanding the Game ==

{{FAQ|question=Speaking of OXPs, I've heard a lot about them. What are they? And where do I find them?|answer=OXP stands for 'Oolite eXpansion Pack'. As the name suggests, an OXP is an expansion to the game. It can contain virtually everything: new graphics for your ship, new ships for the player and/or the NPCs, new stations, new missions, new fun. To install an OXP you simply have to drag it into your AddOns-folder (only the OXP itself, not the folder it probably comes in). And as for finding them, you're already at the right place. All OXPs are now (or will become) accessible through the [[OXP|OXP-page of the wiki]]. Just follow the link. And if you fancy trying to create an OXP, the modifying Oolite FAQ can be found [[Modifying Oolite Informal FAQ|here]].}}

{{FAQ|question=Are there any OXPs that are highly recommended? Or can I get a list of 'must-have' OXPs?|answer=This is a difficult one to answer, because it depends so much on personal taste. There is no list of 'must-have' or necessary OXPs that could be agreed upon by all—or even most—players or contributers. But if you have a look at the [http://aegidian.org/bb/index.php Oolite Bulletin Board], especially the [http://aegidian.org/bb/viewforum.php?f=2 Discussion]- and the [http://aegidian.org/bb/viewforum.php?f=4 Expansion Pack]-forums, you will surely find some topics about this question, and the personal answers of a couple of board members.}}

== Why does this and that not exist? ==

{{FAQ|question=Will there ever be an Oolite Massive Multi-player Online Role-Play Game (MMORPG)?|answer=At present Ahruman and Co. (the developers) have no plans to develop either Oolite or a separate branch to accommodate either an MMORPG or an MOG (Multi-player Online Game). This, however, doesn't mean one of you clever bods out there can't try ;-) We suggest you read [http://aegidian.org/bb/viewtopic.php?t=6173 this Bulletin Board thread] before you commence though, it may save you a lot of hair-tearing!}}

{{FAQ|question=Can the range of hyperspace jumps/my fuelcapacity be increased?|answer=No. Jumprange in Oolite is hardcoded for a reason. The game would become less challenging and thus less fun. (Although I can imagine hacks that give unlimited fuel.) And don't forget that there are already various ways of refueling while you are in flight.}}

{{FAQ|question=I want Laser Cooling Boosters!|answer=There are none at the moment and the reason is simple. It would unbalance the game too much. If they were available for the player only, things would get too easy. And if the NPCs could get them, too, things would get too hard. It's all about maintaining a reasonable balance. So the ultimate advice on this is: Aim carefully. Don't waste your laser fire. Prevent overheating.}}

{{FAQ|question=The other day I got killed when I launched from a Rock Hermit/Behemoth/whatever, and all the profits/kills that I made before were gone. Why couldn't I save there? Why only on main stations?|answer=First of all, congratulations to you for having internalized the ''Golden Rule'': save early, save often! Unfortunately in Oolite you can save and load a commander only on main stations. That's because they are the only 'fixed' objects in space. The rest of the system is populated anew each time you load a game and is not saved in your savefile. So chances are that the Rock Hermit or Behemoth you docked with when saving simply wouldn't exist when you load again, and you would find yourself in nirvana instead of in a safe haven. To prevent odd behavior like this saving and loading is prohibited anywhere else than in a main station. Alternatively you could install [http://wiki.alioth.net/index.php/Save_Anywhere Save Anywhere.oxp], which does exactly what it says on the tin. Note, however, that it is still in beta state. Read the documentation first.}}

{{FAQ|question=I would like to switch between different ships of mine, e.g. have a nice racer for the weekends, meanwhile leave my freighter docked somewhere and take it back on Monday. Why can't I do this?|answer=What else do you want? Custom paintjobs and interiors? A millionaire's spaceship-flotilla, one for every occasion? Who do you think you are? Jay Leno??? (Apologies if you ''are'' Jay Leno, but then you should have something else to do than playing computer games.) Let me tell you something: Space stations are no garages. Docking bays are limited, and the 'garage'-fees would be prohibitive. Imagine everybody else out there would want the same parking facilities!—Having said that, there is also a technical reason: A player can't have two ships and switch between them, because for the game the player ''is'' his ship, and you can ''be'' only one ship at a time. There is no way of storing a ship in your savefile and retrieving it later.}}

== Known Issues / Bugs ==

{{FAQ|question=Every so often some of the messages (either from other ships or from my ship) on the bottom of the screen remain and end up 'scrolling' up the screen to cover my gunsights. What's up with that?|answer=The 'sticky messages' bug is, unfortunately, a long standing issue in Oolite, still present in 1.65 and a few releases since. Starting with Oolite 1.71.1 this problem has been eliminated. If you prefer an older version of Oolite, flicking between views (either internal or external) is probably the quickest way to clear the messages.}}

{{FAQ|question=Every so often I meet a ship or a cargopod that I can't lock on. My laser fire goes right through it. Sometimes it happens with a ship I have just killed. Sometimes after a while it even starts again firing at me, but I can't harm it anymore.|answer=The 'ghost ship' bug is another very old acquaintance in Oolite, and again the tireless developers are trying to rectify this. In the meantime, ignoring the ghost ships (or cargo pods) is the best thing you can do.}}

== System Requirements ==

{{FAQ|question=Does it work on Mac OS X 10.2 (Jaguar) & 10.3 (Panther)?|answer=Sadly, no. The minimum OS requirement for Oolite on the Mac is now Mac OS X 10.4. The previous stable version (1.65) is however compatible with Mac OS X 10.3.9}}

{{FAQ|question=Does it work on both Intel and PPC Macs?|answer=Yes, since 1.65 Oolite has been Universal Binary. It was PPC only in previous versions.}}

{{FAQ|question=What's the latest version?|answer=The last stable release is 1.76. The last stable and latest test versions can be downloaded from [http://oolite.org/download.shtml Oolite's homepage]. More information can be found through the [http://aegidian.org/bb/viewforum.php?f=10 Oolite forums].}}

{{FAQ|question=Is there a port for the PC or Linux?|answer=Yes. Both ports are stable and are at the same level of development as Oolite for the Mac. You can download Oolite for Windows and for Linux PCs from [http://oolite.org/download.shtml Oolite's homepage] (click on "show all platforms" if you can't see the version you're looking for). Information on test releases can be found through the Oolite forums, for the [http://aegidian.org/bb/viewforum.php?f=9 Linux version], and for the [http://aegidian.org/bb/viewforum.php?f=8 Windows version].}}

== Writing OXPs ==

{{FAQ|question=I would like to contribute to Oolite and write my own OXP, but unfortunately my knowledge in scripting/programming is limited. How can I get started?|answer=First of all the Oolite community welcomes all efforts to enhance and enrich their favorite game, so be our guest! Many of us have started with very little knowledge, but over time were able to write and release astonishing OXPs, so why shouldn't you? Anyway, scripting can be learned. Currently there are two scripting languages in use for Oolite, plist-scripting (sometimes referred to as legacy-scripting) and JavaScript. For any serious OXP-plans you will have to learn them. A general starting point is the [http://wiki.alioth.net/index.php/OXP_howto OXP howto]-page, which will link you to further documentation. For plist-scripting you should read the [http://wiki.alioth.net/index.php/OXP_howto_plist OXP howto plist]-page, and also the [http://wiki.alioth.net/index.php/Property_list Property list]-intro. Information on the ongoing implementation of scripting with JavaScript can be found in the [http://wiki.alioth.net/index.php/Category:Oolite_scripting Category page for scripting] (work in progress). If you want to design a new ship, you should have a look at the [http://wiki.alioth.net/index.php/OXP_howto_model OXP howto model]-page and the [http://wiki.alioth.net/index.php/OXP_howto_texture OXP howto texture]-page. And if you want to give it a behavior of its own, you should consult the [http://wiki.alioth.net/index.php/OXP_howto_AI OXP howto AI]-page. I suggest you try to read and understand these first. If you still have questions afterwards, there is always the [http://aegidian.org/bb/index.php Oolite Bulletin Board], where lots of friendly people usually are very willing to lend a helping hand and to answer lots of questions.}}

{{FAQ|question=I want to write an OXP or add content to the Wiki, but some (or all) of the content was written by another author. What copyright issues do I face?|answer=Anything submitted to the Wiki is on the basis that anyone else may edit or fiddle with it. OXPs are submitted under the creative commons licence. The author (stricty speaking) owns the copyright, but licences users to use or distribute the OXP as long as they don't sell or charge for it. In practice virtually all OXP authors don't assert copyright and are pleased and flattered that somebody thinks their stuff is worth writing about or pinching to use in another OXP (its good manners to credit the orginal author in the readme though). I expect the author will be pleased if you want to add some background, but if you are in doubt, send him a PM asking him for permission. At the end of the day, Oolite is a fun project and everbody is doing stuff for it on that basis. (nicked wholesale from [http://aegidian.org/bb/viewtopic.php?p=44813#44813 Little_Bear's] post on the [http://aegidian.org/bb/index.php Oolite Bulletin Board])}}

== Diagnosing Problems ==

{{FAQ|question=Someone asked me for my log file. What is that, and where is it?|answer=In the test releases of Oolite, various diagnostic information is written to a file called Latest.log. Where it is depends on your operating system:
* '''Mac OS X''': ~/Library/Logs/Oolite/Latest.log (that is, in your home folder, open the folder named ''Library'', then ''Logs'', then ''Oolite''). Alternatively, select “Show Previous Log” from the “'''Oolite'''” menu in the menu bar when running Oolite.
* '''Windows''': in Oolite’s folder (typically in C:\''Program Files''), there is a folder called ''oolite.app'', which contains a folder called ''Logs''.
* '''Linux and other Unix-like systems''': ~/.Oolite/Logs (that is, in the hidden folder ''.Oolite'' in your home folder). If you’re using Nautilus or Konqueror—if you’ve never heard of them, you probably are—select Show Hidden Files from the View menu.}}

== Other Questions ==

{{FAQ|question=I have a question not answered here, where can I get help?|answer=Post your queries onto [http://aegidian.org/bb/index.php the friendliest board this side of Riedquat™]. Satisfaction is not guaranteed, but then what is, in this mixed-up universe? Help keep the board friendly by making sure your question isn't already answered here!

If you want to report a bug, please read [http://aegidian.org/bb/viewtopic.php?t=3778 this]. Yes, all that work is a drag, but if nobody reports the bug it probably won’t get fixed.

Or join us in #oolite, or #oolite-dev if you're working on Oolite or OXPs, on irc.oftc.net or ipv6.oftc.net.}}

[[Category:Oolite]]

Oolite FAQ

2011-12-22T03:59:35Z

Kaks: /* Known Issues / Bugs */

== Getting Started ==

{{FAQ|question=Where do I get the program? And what about the different versions that exist?|answer= The latest 'official' stable release is version 1.76, and is available on the [http://oolite.org/download.shtml oolite.org download page] for OS X, Windows, and Linux(x86). The last stable release made by the original programmer, Giles Williams (a.k.a. Aegidian) was 1.65 and is best available from his website [http://oolite.aegidian.org/ oolite.aegidian.org]. The latest test releases/development versions can be [http://developer.berlios.de/project/showfiles.php?group_id=3577 downloaded from BerliOS] with installers also available for OS X, Windows and Linux. More detailed information can be found on the [http://aegidian.org/bb/index.php Oolite Bulletin Board], in the respective sections for [http://aegidian.org/bb/viewforum.php?f=10 Oolite-Mac], [http://aegidian.org/bb/viewforum.php?f=9 Oolite-Linux] and [http://aegidian.org/bb/viewforum.php?f=8 Oolite-PC].}}

{{FAQ|question=What's the point of the game?|answer=To fly from planet to planet, buying and selling goods, shooting pirates or committing acts of piracy. There's no goal other than perhaps to achieve the rank of ELITE.}}

{{FAQ|question=I'm still confused, how do I play?|answer=It's a good idea to start with the [http://wiki.alioth.net/images/0/0d/Oolite_1.65_ReadMe.pdf.zip Oolite ReadMe] file for some basic information. For further information you may wish to consult the [http://wiki.alioth.net/index.php/Oolite_Instruction_Manual Oolite Instruction Manual] here on the wiki. A load of helpful information can be obtained from [http://wiki.alioth.net/index.php/Mr_Gimlet Mr Gimlet], the quite talkative dockmaster on Lave Station. If you're a fresh graduate from the Flight Academy on the way to your first ship, you should see him. It's also a good idea to have a look at Ian Bell's [http://www.iancgbell.clara.net/elite/manual.htm Flight Training Manual] for the original BBC Elite, although some of Oolite's control keys are different from the original, so be careful.}}

{{FAQ|question=How do I configure my joystick or gamepad for Oolite in Linux?|answer=See [[Linux Joysticks and Gamepads]].}}

== Gameplay ==

{{FAQ|question=What do the various colors represent on the radar?|answer=White - unpowered items that can't mass-lock the in-system drive (jumpdrive). Green/Yellow - navigation buoys. Yellow - powered craft. Red - powered craft identified as hostile. Green - space stations. Green/Red - thargoids. Purple - police. Blue/Red - police on intercept. Red/Yellow - active mine (about to detonate). Blue/Cyan - witchspace wormhole.}}

{{FAQ|question=I keep crashing when trying to dock. How do I dock manually?|answer=Many young Jamesons have met a sticky end and had to be scraped from the docking port of Lave Station whilst attempting docking. Its fairly easy once you get the hang of it. Check the [[How_to_Dock|How to Dock]] guide from the Galactic Navy Flight Manual. Or you can get the [[Traffic_Control_OXP|Traffic Control OXP]] for friendly instructions given by the station crew as you try to dock.}}

{{FAQ|question=How do I make decent profits?|answer=Trade between a Poor or Average Agricultural and a Rich or Average Industrial planet. Write down the prices for everything on both planets and find out where you make the most profit per ton. You can also download the [http://wiki.alioth.net/images/d/df/OoliteRS_rev1.8.zip Oolite Reference Sheet], which features a table with the average prices. From there you can figure out whether you're on a buyers' or a sellers' market. The [http://wiki.alioth.net/images/9/9e/OoliteTradingChart2.zip Trading Chart] allows you to create your own statistics along your way. [http://www.box.net/shared/bchkkloi32 This spreadsheet] highlights Poor Agricultural and Rich Industrial planets on a star chart (the spreadsheet is in .xls format and needs the Analysis Toolpak installed). You can also earn credits by taking cargo contracts - courier goods of varied type and volume between planets near and far. The spreadsheet helps assess whether you will be be able to complete the contract on time, and so build your reputation as an outstanding courier. Another option is to fit one or more [http://wiki.alioth.net/index.php/Passenger_Berth Passenger Berths] in your ship and earn credits by transporting individuals who, for one reason or another, prefer not to use the commercial Passenger Liners to reach their destination. As with cargo contracts, you can build your reputation up, which will result in your being offered more lucrative fares.}}

{{FAQ|question=It takes so long to get to the station after each jump. Can I do anything to speed the trip up?|answer=Well, space is huge. It is vast. I mean, have you ever imagined a football-field with an orange in one of the goals and a walnut in the other goal? If you haven't, then don't. It takes you nowhere. As will your ship's engine at normal speed. But then that's what your jumpdrive is for. Hit '''J''', and your journey speeds up. Unfortunately your jumpdrive doesn't work when other masses, like ships or planets, are nearby. They will 'lock' it. And in the 'corridor' between the witchpoint and the planet you are very likely to meet other ships. On the other hand there is no rule that you have to stick to the corridor. Just leave it sideways in any direction with your jumpdrive engaged for about 10-15 seconds, and head for the planet then. Makes your voyage much smoother. If you're a bounty-hunter and eager to meet lots of pirates, however, this is not your method of choice.}}

{{FAQ|question=I have already made my first intergalactic jump to Galaxy 2, but now I remember that I forgot my Zero-G cricket set/food blender/deadly lobstoid/edible arts graduate on Lave/Tionisla/Xeesle/Reesdice! Or I just found out that there are some more missions I'd like to do in the first galaxy. So how can I jump back to Galaxy 1?|answer=You can't. Unfortunately due to their very physical nature intergalactic wormholes allow for one-way travel only. Fortunately, though, the intergalactic wormhole in Galaxy 8 connects back to Galaxy 1. So you can go full circle. And you have to, if you want to return to the first galaxy. Of course that will cost you another 5000 credits for each galactic hyperjump. So the complete 8-Galaxies-Sightseeing-Tour has a pricetag of a total 40000 credits.}}

{{FAQ|question=I've got a trumble! First it was cute and fluffy. But then it started to multiply. Even worse, they started to eat everything on board and they are confusing my sights. I don't want them anymore! How can I get rid of them? Help!|answer=First of all, don't feel embarrassed. It happens to all commanders sooner or later. I mean, they're really cute and fluffy, aren't they? But seriously, there are several things you could try. E.g. sell them to other unsuspecting noobs. If you don't find enough willing buyers, you could use your escape capsule and abandon your infested ship, hoping that they haven't yet made it into the escape pod, of course. I mean, you can always hope, can't you? If that all doesn't work for you, just remember the old Klingon saying: 'Revenge is a dish that is best served cold.' Now consider that for trumbles it's just the opposite. Want some BBQ-sauce?}}

{{FAQ|question=My keyboard doesn't have a particular key used by Oolite, or I even want to change the keyboard layout completely to my liking. What can I do to change the keys?|answer=Oolite reads a key configuration file called keyconfig.plist that you can find at /AddOns/Config/keyconfig.plist; that is the Config-folder that you find inside your AddOns-folder; which is where you put your OXPs. (PC-users have to create the folder /AddOns/Config/ first and then drop a copy of the keyconfig.plist found in /Oolite.app/Contents/Resources/Config/ to this folder.) You can open this file in any text editor and change the ASCII values of the keys used to suit your own preferences. Information on the default keys is also found in the [http://wiki.alioth.net/index.php/Oolite_Keyboard_Controls Oolite Keybord Controls-documentation] here on the wiki.}}

{{FAQ|question=I've completed a number of native and OXP missions and my [http://wiki.alioth.net/index.php/Cobra_Mk.3_%28Oolite%29 Cobra Mk. III] has a number of new and funky pieces of equipment. However, I'm planning a change of ship, what pieces of equipment will I lose as a result?|answer=Many missions award equipment as a result of either accepting or completing them. For the majority of ship equipment, trading ships will result in the equipment being sold as well, with a few exceptions. The '''Cloaking Device''' and the '''Mark Transponder Scanner''', available from the (native) Cloaking Device and (OXP) Assassins missions respectively are transferred to your new ship. The '''Naval Energy Unit''', although awarded with the completion of the (native) Thargoid Plans mission, will be sold when you trade ships. However, completing the mission allows you to buy these units from high TL systems.}}

{{FAQ|question=I’m using ECM-hardened missiles, but enemies are still able to destroy them! I never seem to be able to destroy enemy hardheads, though. What gives?|answer=ECM-hardened missiles are not ECM-proof. The probability of a hardened missile being destroyed by ECM is 10%–34% depending on range, and if it is destroyed, there’s a 50% chance that it will detonate. This applies equally to hardened missiles fired by computer-controlled ships and those fired by the player. The most effective use of hardened missiles is to use them against relatively slow targets at moderate range, and only use them on nimble ships if you desperately need to force them to break of an attack. Also, don’t use your ECM until a missile is close to blast range (250 metres).

Specifically, the ECM sends out four pulses with different ranges, at half-second intervals. Each pulse has a 10% chance of destroying each hardhead it encounters. For a missile fired at close range, that’s 1 - 0.94 = 34.39% chance of being destroyed within two seconds.}}

{{FAQ|question=If I believe that sizes and distances in Oolite are given in meters, it is so ''unrealistic''. The planets have a diameter of only 30–50 kilometers, and the suns are only 1000 kilometers away. Can't we get a little more realism in space, please?|answer=First of all, remember that Oolite is a ''game'', not a ''space simulation''. This is because it ''wants to'' be a game, not a sim. So yes, sizes and distances are all messed up. Ships and stations are too big, planets and suns are too small, and too close to each other. But this is ''deliberately'' so, and we are not going to change it.

The reason is simple: Realistic sizes and distances don't make a good game. In reality space is so huge that you never would meet anybody else on your journey. Imagine the dozen or so ships you meet in the 500 or so kilometers between witchpoint and planet spread over the realistic 150 '''million''' kilometers between Sun and Earth. Even if your direction is only one degree off the perfect line, you would miss them all. And how interesting would that be for the gameplay? And finally, if you had a realistically sized station in front of a realistically sized planet, how would you ever even notice it? A grain of sand in front of a, well, '''planet'''. The result would be players in complete loneliness and virtually no interaction with NPCs. An utterly, utterly boring game. Therefore it was the right decision to screw realism in the layout of the planetary systems in Elite and Oolite.}}

== Expanding the Game ==

{{FAQ|question=Speaking of OXPs, I've heard a lot about them. What are they? And where do I find them?|answer=OXP stands for 'Oolite eXpansion Pack'. As the name suggests, an OXP is an expansion to the game. It can contain virtually everything: new graphics for your ship, new ships for the player and/or the NPCs, new stations, new missions, new fun. To install an OXP you simply have to drag it into your AddOns-folder (only the OXP itself, not the folder it probably comes in). And as for finding them, you're already at the right place. All OXPs are now (or will become) accessible through the [[OXP|OXP-page of the wiki]]. Just follow the link. And if you fancy trying to create an OXP, the modifying Oolite FAQ can be found [[Modifying Oolite Informal FAQ|here]].}}

{{FAQ|question=Are there any OXPs that are highly recommended? Or can I get a list of 'must-have' OXPs?|answer=This is a difficult one to answer, because it depends so much on personal taste. There is no list of 'must-have' or necessary OXPs that could be agreed upon by all—or even most—players or contributers. But if you have a look at the [http://aegidian.org/bb/index.php Oolite Bulletin Board], especially the [http://aegidian.org/bb/viewforum.php?f=2 Discussion]- and the [http://aegidian.org/bb/viewforum.php?f=4 Expansion Pack]-forums, you will surely find some topics about this question, and the personal answers of a couple of board members.}}

== Why does this and that not exist? ==

{{FAQ|question=Will there ever be an Oolite Massive Multi-player Online Role-Play Game (MMORPG)?|answer=At present Ahruman and Co. (the developers) have no plans to develop either Oolite or a separate branch to accommodate either an MMORPG or an MOG (Multi-player Online Game). This, however, doesn't mean one of you clever bods out there can't try ;-) We suggest you read [http://aegidian.org/bb/viewtopic.php?t=6173 this Bulletin Board thread] before you commence though, it may save you a lot of hair-tearing!}}

{{FAQ|question=Can the range of hyperspace jumps/my fuelcapacity be increased?|answer=No. Jumprange in Oolite is hardcoded for a reason. The game would become less challenging and thus less fun. (Although I can imagine hacks that give unlimited fuel.) And don't forget that there are already various ways of refueling while you are in flight.}}

{{FAQ|question=I want Laser Cooling Boosters!|answer=There are none at the moment and the reason is simple. It would unbalance the game too much. If they were available for the player only, things would get too easy. And if the NPCs could get them, too, things would get too hard. It's all about maintaining a reasonable balance. So the ultimate advice on this is: Aim carefully. Don't waste your laser fire. Prevent overheating.}}

{{FAQ|question=The other day I got killed when I launched from a Rock Hermit/Behemoth/whatever, and all the profits/kills that I made before were gone. Why couldn't I save there? Why only on main stations?|answer=First of all, congratulations to you for having internalized the ''Golden Rule'': save early, save often! Unfortunately in Oolite you can save and load a commander only on main stations. That's because they are the only 'fixed' objects in space. The rest of the system is populated anew each time you load a game and is not saved in your savefile. So chances are that the Rock Hermit or Behemoth you docked with when saving simply wouldn't exist when you load again, and you would find yourself in nirvana instead of in a safe haven. To prevent odd behavior like this saving and loading is prohibited anywhere else than in a main station. Alternatively you could install [http://wiki.alioth.net/index.php/Save_Anywhere Save Anywhere.oxp], which does exactly what it says on the tin. Note, however, that it is still in beta state. Read the documentation first.}}

{{FAQ|question=I would like to switch between different ships of mine, e.g. have a nice racer for the weekends, meanwhile leave my freighter docked somewhere and take it back on Monday. Why can't I do this?|answer=What else do you want? Custom paintjobs and interiors? A millionaire's spaceship-flotilla, one for every occasion? Who do you think you are? Jay Leno??? (Apologies if you ''are'' Jay Leno, but then you should have something else to do than playing computer games.) Let me tell you something: Space stations are no garages. Docking bays are limited, and the 'garage'-fees would be prohibitive. Imagine everybody else out there would want the same parking facilities!—Having said that, there is also a technical reason: A player can't have two ships and switch between them, because for the game the player ''is'' his ship, and you can ''be'' only one ship at a time. There is no way of storing a ship in your savefile and retrieving it later.}}

== Known Issues / Bugs ==

{{FAQ|question=Every so often some of the messages (either from other ships or from my ship) on the bottom of the screen remain and end up 'scrolling' up the screen to cover my gunsights. What's up with that?|answer=The 'sticky messages' bug is, unfortunately, a long standing issue in Oolite, still present in 1.65 and a few releases since. Starting with Oolite 1.71.1 this problem has been eliminated. If you prefer an older version of Oolite, flicking between views (either internal or external) is probably the quickest way to clear the messages.}}

{{FAQ|question=Every so often I meet a ship or a cargopod that I can't lock on. My laser fire goes right through it. Sometimes it happens with a ship I have just killed. Sometimes after a while it even starts again firing at me, but I can't harm it anymore.|answer=The 'ghost ship' bug is another very old acquaintance in Oolite, and again the tireless developers are trying to rectify this. In the meantime, ignoring the ghost ships (or cargo pods) is the best thing you can do.}}

== System Requirements ==

{{FAQ|question=Does it work on Mac OS X 10.2 (Jaguar)?|answer=Sadly, no. The minimum OS requirement for Oolite on the Mac is now Mac OS X 10.3.9.}}

{{FAQ|question=Does it work on the new Intel Macs?|answer=Yes, from 1.65 Oolite is Universal Binary.}}

{{FAQ|question=What's the latest version?|answer=The last stable release is 1.65. However, the latest test release—1.74.2 at the time of writing—is faster, more reliable, and offers better graphics than the stable version, and is the recommended download. Yes, we're aware this sounds silly. The last stable and latest test versions can be downloaded from [http://oolite.org/download.shtml Oolite's homepage]. More information can be found through the [http://aegidian.org/bb/viewforum.php?f=10 Oolite forums].}}

{{FAQ|question=Is there a port for the PC or Linux?|answer=Yes. Both ports are stable and are at the same level of development as Oolite for the Mac. You can download Oolite for Windows and for Linux PCs from [http://oolite.org/download.shtml Oolite's homepage] (click on "show all platforms" if you can't see the version you're looking for). Information on test releases can be found through the Oolite forums, for the [http://aegidian.org/bb/viewforum.php?f=9 Linux version], and for the [http://aegidian.org/bb/viewforum.php?f=8 Windows version].}}

== Writing OXPs ==

{{FAQ|question=I would like to contribute to Oolite and write my own OXP, but unfortunately my knowledge in scripting/programming is limited. How can I get started?|answer=First of all the Oolite community welcomes all efforts to enhance and enrich their favorite game, so be our guest! Many of us have started with very little knowledge, but over time were able to write and release astonishing OXPs, so why shouldn't you? Anyway, scripting can be learned. Currently there are two scripting languages in use for Oolite, plist-scripting (sometimes referred to as legacy-scripting) and JavaScript. For any serious OXP-plans you will have to learn them. A general starting point is the [http://wiki.alioth.net/index.php/OXP_howto OXP howto]-page, which will link you to further documentation. For plist-scripting you should read the [http://wiki.alioth.net/index.php/OXP_howto_plist OXP howto plist]-page, and also the [http://wiki.alioth.net/index.php/Property_list Property list]-intro. Information on the ongoing implementation of scripting with JavaScript can be found in the [http://wiki.alioth.net/index.php/Category:Oolite_scripting Category page for scripting] (work in progress). If you want to design a new ship, you should have a look at the [http://wiki.alioth.net/index.php/OXP_howto_model OXP howto model]-page and the [http://wiki.alioth.net/index.php/OXP_howto_texture OXP howto texture]-page. And if you want to give it a behavior of its own, you should consult the [http://wiki.alioth.net/index.php/OXP_howto_AI OXP howto AI]-page. I suggest you try to read and understand these first. If you still have questions afterwards, there is always the [http://aegidian.org/bb/index.php Oolite Bulletin Board], where lots of friendly people usually are very willing to lend a helping hand and to answer lots of questions.}}

{{FAQ|question=I want to write an OXP or add content to the Wiki, but some (or all) of the content was written by another author. What copyright issues do I face?|answer=Anything submitted to the Wiki is on the basis that anyone else may edit or fiddle with it. OXPs are submitted under the creative commons licence. The author (stricty speaking) owns the copyright, but licences users to use or distribute the OXP as long as they don't sell or charge for it. In practice virtually all OXP authors don't assert copyright and are pleased and flattered that somebody thinks their stuff is worth writing about or pinching to use in another OXP (its good manners to credit the orginal author in the readme though). I expect the author will be pleased if you want to add some background, but if you are in doubt, send him a PM asking him for permission. At the end of the day, Oolite is a fun project and everbody is doing stuff for it on that basis. (nicked wholesale from [http://aegidian.org/bb/viewtopic.php?p=44813#44813 Little_Bear's] post on the [http://aegidian.org/bb/index.php Oolite Bulletin Board])}}

== Diagnosing Problems ==

{{FAQ|question=Someone asked me for my log file. What is that, and where is it?|answer=In the test releases of Oolite, various diagnostic information is written to a file called Latest.log. Where it is depends on your operating system:
* '''Mac OS X''': ~/Library/Logs/Oolite/Latest.log (that is, in your home folder, open the folder named ''Library'', then ''Logs'', then ''Oolite''). Alternatively, select “Show Previous Log” from the “'''Oolite'''” menu in the menu bar when running Oolite.
* '''Windows''': in Oolite’s folder (typically in C:\''Program Files''), there is a folder called ''oolite.app'', which contains a folder called ''Logs''.
* '''Linux and other Unix-like systems''': ~/.Oolite/Logs (that is, in the hidden folder ''.Oolite'' in your home folder). If you’re using Nautilus or Konqueror—if you’ve never heard of them, you probably are—select Show Hidden Files from the View menu.}}

== Other Questions ==

{{FAQ|question=I have a question not answered here, where can I get help?|answer=Post your queries onto [http://aegidian.org/bb/index.php the friendliest board this side of Riedquat™]. Satisfaction is not guaranteed, but then what is, in this mixed-up universe? Help keep the board friendly by making sure your question isn't already answered here!

If you want to report a bug, please read [http://aegidian.org/bb/viewtopic.php?t=3778 this]. Yes, all that work is a drag, but if nobody reports the bug it probably won’t get fixed.

Or join us in #oolite, or #oolite-dev if you're working on Oolite or OXPs, on irc.oftc.net or ipv6.oftc.net.}}

[[Category:Oolite]]

Oolite FAQ

2011-12-22T03:57:42Z

Kaks: /* Why does this and that not exist? */

== Getting Started ==

{{FAQ|question=Where do I get the program? And what about the different versions that exist?|answer= The latest 'official' stable release is version 1.76, and is available on the [http://oolite.org/download.shtml oolite.org download page] for OS X, Windows, and Linux(x86). The last stable release made by the original programmer, Giles Williams (a.k.a. Aegidian) was 1.65 and is best available from his website [http://oolite.aegidian.org/ oolite.aegidian.org]. The latest test releases/development versions can be [http://developer.berlios.de/project/showfiles.php?group_id=3577 downloaded from BerliOS] with installers also available for OS X, Windows and Linux. More detailed information can be found on the [http://aegidian.org/bb/index.php Oolite Bulletin Board], in the respective sections for [http://aegidian.org/bb/viewforum.php?f=10 Oolite-Mac], [http://aegidian.org/bb/viewforum.php?f=9 Oolite-Linux] and [http://aegidian.org/bb/viewforum.php?f=8 Oolite-PC].}}

{{FAQ|question=What's the point of the game?|answer=To fly from planet to planet, buying and selling goods, shooting pirates or committing acts of piracy. There's no goal other than perhaps to achieve the rank of ELITE.}}

{{FAQ|question=I'm still confused, how do I play?|answer=It's a good idea to start with the [http://wiki.alioth.net/images/0/0d/Oolite_1.65_ReadMe.pdf.zip Oolite ReadMe] file for some basic information. For further information you may wish to consult the [http://wiki.alioth.net/index.php/Oolite_Instruction_Manual Oolite Instruction Manual] here on the wiki. A load of helpful information can be obtained from [http://wiki.alioth.net/index.php/Mr_Gimlet Mr Gimlet], the quite talkative dockmaster on Lave Station. If you're a fresh graduate from the Flight Academy on the way to your first ship, you should see him. It's also a good idea to have a look at Ian Bell's [http://www.iancgbell.clara.net/elite/manual.htm Flight Training Manual] for the original BBC Elite, although some of Oolite's control keys are different from the original, so be careful.}}

{{FAQ|question=How do I configure my joystick or gamepad for Oolite in Linux?|answer=See [[Linux Joysticks and Gamepads]].}}

== Gameplay ==

{{FAQ|question=What do the various colors represent on the radar?|answer=White - unpowered items that can't mass-lock the in-system drive (jumpdrive). Green/Yellow - navigation buoys. Yellow - powered craft. Red - powered craft identified as hostile. Green - space stations. Green/Red - thargoids. Purple - police. Blue/Red - police on intercept. Red/Yellow - active mine (about to detonate). Blue/Cyan - witchspace wormhole.}}

{{FAQ|question=I keep crashing when trying to dock. How do I dock manually?|answer=Many young Jamesons have met a sticky end and had to be scraped from the docking port of Lave Station whilst attempting docking. Its fairly easy once you get the hang of it. Check the [[How_to_Dock|How to Dock]] guide from the Galactic Navy Flight Manual. Or you can get the [[Traffic_Control_OXP|Traffic Control OXP]] for friendly instructions given by the station crew as you try to dock.}}

{{FAQ|question=How do I make decent profits?|answer=Trade between a Poor or Average Agricultural and a Rich or Average Industrial planet. Write down the prices for everything on both planets and find out where you make the most profit per ton. You can also download the [http://wiki.alioth.net/images/d/df/OoliteRS_rev1.8.zip Oolite Reference Sheet], which features a table with the average prices. From there you can figure out whether you're on a buyers' or a sellers' market. The [http://wiki.alioth.net/images/9/9e/OoliteTradingChart2.zip Trading Chart] allows you to create your own statistics along your way. [http://www.box.net/shared/bchkkloi32 This spreadsheet] highlights Poor Agricultural and Rich Industrial planets on a star chart (the spreadsheet is in .xls format and needs the Analysis Toolpak installed). You can also earn credits by taking cargo contracts - courier goods of varied type and volume between planets near and far. The spreadsheet helps assess whether you will be be able to complete the contract on time, and so build your reputation as an outstanding courier. Another option is to fit one or more [http://wiki.alioth.net/index.php/Passenger_Berth Passenger Berths] in your ship and earn credits by transporting individuals who, for one reason or another, prefer not to use the commercial Passenger Liners to reach their destination. As with cargo contracts, you can build your reputation up, which will result in your being offered more lucrative fares.}}

{{FAQ|question=It takes so long to get to the station after each jump. Can I do anything to speed the trip up?|answer=Well, space is huge. It is vast. I mean, have you ever imagined a football-field with an orange in one of the goals and a walnut in the other goal? If you haven't, then don't. It takes you nowhere. As will your ship's engine at normal speed. But then that's what your jumpdrive is for. Hit '''J''', and your journey speeds up. Unfortunately your jumpdrive doesn't work when other masses, like ships or planets, are nearby. They will 'lock' it. And in the 'corridor' between the witchpoint and the planet you are very likely to meet other ships. On the other hand there is no rule that you have to stick to the corridor. Just leave it sideways in any direction with your jumpdrive engaged for about 10-15 seconds, and head for the planet then. Makes your voyage much smoother. If you're a bounty-hunter and eager to meet lots of pirates, however, this is not your method of choice.}}

{{FAQ|question=I have already made my first intergalactic jump to Galaxy 2, but now I remember that I forgot my Zero-G cricket set/food blender/deadly lobstoid/edible arts graduate on Lave/Tionisla/Xeesle/Reesdice! Or I just found out that there are some more missions I'd like to do in the first galaxy. So how can I jump back to Galaxy 1?|answer=You can't. Unfortunately due to their very physical nature intergalactic wormholes allow for one-way travel only. Fortunately, though, the intergalactic wormhole in Galaxy 8 connects back to Galaxy 1. So you can go full circle. And you have to, if you want to return to the first galaxy. Of course that will cost you another 5000 credits for each galactic hyperjump. So the complete 8-Galaxies-Sightseeing-Tour has a pricetag of a total 40000 credits.}}

{{FAQ|question=I've got a trumble! First it was cute and fluffy. But then it started to multiply. Even worse, they started to eat everything on board and they are confusing my sights. I don't want them anymore! How can I get rid of them? Help!|answer=First of all, don't feel embarrassed. It happens to all commanders sooner or later. I mean, they're really cute and fluffy, aren't they? But seriously, there are several things you could try. E.g. sell them to other unsuspecting noobs. If you don't find enough willing buyers, you could use your escape capsule and abandon your infested ship, hoping that they haven't yet made it into the escape pod, of course. I mean, you can always hope, can't you? If that all doesn't work for you, just remember the old Klingon saying: 'Revenge is a dish that is best served cold.' Now consider that for trumbles it's just the opposite. Want some BBQ-sauce?}}

{{FAQ|question=My keyboard doesn't have a particular key used by Oolite, or I even want to change the keyboard layout completely to my liking. What can I do to change the keys?|answer=Oolite reads a key configuration file called keyconfig.plist that you can find at /AddOns/Config/keyconfig.plist; that is the Config-folder that you find inside your AddOns-folder; which is where you put your OXPs. (PC-users have to create the folder /AddOns/Config/ first and then drop a copy of the keyconfig.plist found in /Oolite.app/Contents/Resources/Config/ to this folder.) You can open this file in any text editor and change the ASCII values of the keys used to suit your own preferences. Information on the default keys is also found in the [http://wiki.alioth.net/index.php/Oolite_Keyboard_Controls Oolite Keybord Controls-documentation] here on the wiki.}}

{{FAQ|question=I've completed a number of native and OXP missions and my [http://wiki.alioth.net/index.php/Cobra_Mk.3_%28Oolite%29 Cobra Mk. III] has a number of new and funky pieces of equipment. However, I'm planning a change of ship, what pieces of equipment will I lose as a result?|answer=Many missions award equipment as a result of either accepting or completing them. For the majority of ship equipment, trading ships will result in the equipment being sold as well, with a few exceptions. The '''Cloaking Device''' and the '''Mark Transponder Scanner''', available from the (native) Cloaking Device and (OXP) Assassins missions respectively are transferred to your new ship. The '''Naval Energy Unit''', although awarded with the completion of the (native) Thargoid Plans mission, will be sold when you trade ships. However, completing the mission allows you to buy these units from high TL systems.}}

{{FAQ|question=I’m using ECM-hardened missiles, but enemies are still able to destroy them! I never seem to be able to destroy enemy hardheads, though. What gives?|answer=ECM-hardened missiles are not ECM-proof. The probability of a hardened missile being destroyed by ECM is 10%–34% depending on range, and if it is destroyed, there’s a 50% chance that it will detonate. This applies equally to hardened missiles fired by computer-controlled ships and those fired by the player. The most effective use of hardened missiles is to use them against relatively slow targets at moderate range, and only use them on nimble ships if you desperately need to force them to break of an attack. Also, don’t use your ECM until a missile is close to blast range (250 metres).

Specifically, the ECM sends out four pulses with different ranges, at half-second intervals. Each pulse has a 10% chance of destroying each hardhead it encounters. For a missile fired at close range, that’s 1 - 0.94 = 34.39% chance of being destroyed within two seconds.}}

{{FAQ|question=If I believe that sizes and distances in Oolite are given in meters, it is so ''unrealistic''. The planets have a diameter of only 30–50 kilometers, and the suns are only 1000 kilometers away. Can't we get a little more realism in space, please?|answer=First of all, remember that Oolite is a ''game'', not a ''space simulation''. This is because it ''wants to'' be a game, not a sim. So yes, sizes and distances are all messed up. Ships and stations are too big, planets and suns are too small, and too close to each other. But this is ''deliberately'' so, and we are not going to change it.

The reason is simple: Realistic sizes and distances don't make a good game. In reality space is so huge that you never would meet anybody else on your journey. Imagine the dozen or so ships you meet in the 500 or so kilometers between witchpoint and planet spread over the realistic 150 '''million''' kilometers between Sun and Earth. Even if your direction is only one degree off the perfect line, you would miss them all. And how interesting would that be for the gameplay? And finally, if you had a realistically sized station in front of a realistically sized planet, how would you ever even notice it? A grain of sand in front of a, well, '''planet'''. The result would be players in complete loneliness and virtually no interaction with NPCs. An utterly, utterly boring game. Therefore it was the right decision to screw realism in the layout of the planetary systems in Elite and Oolite.}}

== Expanding the Game ==

{{FAQ|question=Speaking of OXPs, I've heard a lot about them. What are they? And where do I find them?|answer=OXP stands for 'Oolite eXpansion Pack'. As the name suggests, an OXP is an expansion to the game. It can contain virtually everything: new graphics for your ship, new ships for the player and/or the NPCs, new stations, new missions, new fun. To install an OXP you simply have to drag it into your AddOns-folder (only the OXP itself, not the folder it probably comes in). And as for finding them, you're already at the right place. All OXPs are now (or will become) accessible through the [[OXP|OXP-page of the wiki]]. Just follow the link. And if you fancy trying to create an OXP, the modifying Oolite FAQ can be found [[Modifying Oolite Informal FAQ|here]].}}

{{FAQ|question=Are there any OXPs that are highly recommended? Or can I get a list of 'must-have' OXPs?|answer=This is a difficult one to answer, because it depends so much on personal taste. There is no list of 'must-have' or necessary OXPs that could be agreed upon by all—or even most—players or contributers. But if you have a look at the [http://aegidian.org/bb/index.php Oolite Bulletin Board], especially the [http://aegidian.org/bb/viewforum.php?f=2 Discussion]- and the [http://aegidian.org/bb/viewforum.php?f=4 Expansion Pack]-forums, you will surely find some topics about this question, and the personal answers of a couple of board members.}}

== Why does this and that not exist? ==

{{FAQ|question=Will there ever be an Oolite Massive Multi-player Online Role-Play Game (MMORPG)?|answer=At present Ahruman and Co. (the developers) have no plans to develop either Oolite or a separate branch to accommodate either an MMORPG or an MOG (Multi-player Online Game). This, however, doesn't mean one of you clever bods out there can't try ;-) We suggest you read [http://aegidian.org/bb/viewtopic.php?t=6173 this Bulletin Board thread] before you commence though, it may save you a lot of hair-tearing!}}

{{FAQ|question=Can the range of hyperspace jumps/my fuelcapacity be increased?|answer=No. Jumprange in Oolite is hardcoded for a reason. The game would become less challenging and thus less fun. (Although I can imagine hacks that give unlimited fuel.) And don't forget that there are already various ways of refueling while you are in flight.}}

{{FAQ|question=I want Laser Cooling Boosters!|answer=There are none at the moment and the reason is simple. It would unbalance the game too much. If they were available for the player only, things would get too easy. And if the NPCs could get them, too, things would get too hard. It's all about maintaining a reasonable balance. So the ultimate advice on this is: Aim carefully. Don't waste your laser fire. Prevent overheating.}}

{{FAQ|question=The other day I got killed when I launched from a Rock Hermit/Behemoth/whatever, and all the profits/kills that I made before were gone. Why couldn't I save there? Why only on main stations?|answer=First of all, congratulations to you for having internalized the ''Golden Rule'': save early, save often! Unfortunately in Oolite you can save and load a commander only on main stations. That's because they are the only 'fixed' objects in space. The rest of the system is populated anew each time you load a game and is not saved in your savefile. So chances are that the Rock Hermit or Behemoth you docked with when saving simply wouldn't exist when you load again, and you would find yourself in nirvana instead of in a safe haven. To prevent odd behavior like this saving and loading is prohibited anywhere else than in a main station. Alternatively you could install [http://wiki.alioth.net/index.php/Save_Anywhere Save Anywhere.oxp], which does exactly what it says on the tin. Note, however, that it is still in beta state. Read the documentation first.}}

{{FAQ|question=I would like to switch between different ships of mine, e.g. have a nice racer for the weekends, meanwhile leave my freighter docked somewhere and take it back on Monday. Why can't I do this?|answer=What else do you want? Custom paintjobs and interiors? A millionaire's spaceship-flotilla, one for every occasion? Who do you think you are? Jay Leno??? (Apologies if you ''are'' Jay Leno, but then you should have something else to do than playing computer games.) Let me tell you something: Space stations are no garages. Docking bays are limited, and the 'garage'-fees would be prohibitive. Imagine everybody else out there would want the same parking facilities!—Having said that, there is also a technical reason: A player can't have two ships and switch between them, because for the game the player ''is'' his ship, and you can ''be'' only one ship at a time. There is no way of storing a ship in your savefile and retrieving it later.}}

== Known Issues / Bugs ==

{{FAQ|question=Every so often some of the messages (either from other ships or from my ship) on the bottom of the screen remain and end up 'scrolling' up the screen to cover my gunsights. What's up with that?|answer=The 'sticky messages' bug is, unfortunately, a long standing issue in Oolite, still present in 1.65 and a few releases since. Starting with Oolite 1.71.1 this problem has been eliminated. If you prefer an older version of Oolite, flicking between views (either internal or external) is probably the quickest way to clear the messages.}}

{{FAQ|question=Every so often I meet a ship or a cargopod that I can't lock on. My laser fire goes right through it. Sometimes it happens with a ship I have just killed. Sometimes after a while it even starts again firing at me, but I can't harm it anymore.|answer=The 'ghost ship' bug is another very old acquaintance in Oolite, and again the tireless developers are trying to rectify this. In the meantime, ignoring the ghost ships (or cargo pods) is the best thing you can do.}}

{{FAQ|question=The brightness of the rotating ships screen on the start-screen of the game has gone dark, I can hardly see them anymore. Do you know that, and what can I do about it?|answer=This is a problem with the lighting model for ships using shaders. The tireless developers are aware of the problem and are going to fix it. In the meantime, and as the problem only occurs when the shader settings are set to 'Full', you can work around it by setting them to 'Simple' or 'Off' in the Options-screen of Oolite (press '''F2''' and choose 'Game Options...'). Although of course you won't have the shader effects then.

The alternative is to open the controls for your graphics card and boost the gamma setting of your card by 10-20%. This will have a marginal effect on your screen colours when using your computer, but it will make ships in-game a lot brighter and easier to see.}}

== System Requirements ==

{{FAQ|question=Does it work on Mac OS X 10.2 (Jaguar)?|answer=Sadly, no. The minimum OS requirement for Oolite on the Mac is now Mac OS X 10.3.9.}}

{{FAQ|question=Does it work on the new Intel Macs?|answer=Yes, from 1.65 Oolite is Universal Binary.}}

{{FAQ|question=What's the latest version?|answer=The last stable release is 1.65. However, the latest test release—1.74.2 at the time of writing—is faster, more reliable, and offers better graphics than the stable version, and is the recommended download. Yes, we're aware this sounds silly. The last stable and latest test versions can be downloaded from [http://oolite.org/download.shtml Oolite's homepage]. More information can be found through the [http://aegidian.org/bb/viewforum.php?f=10 Oolite forums].}}

{{FAQ|question=Is there a port for the PC or Linux?|answer=Yes. Both ports are stable and are at the same level of development as Oolite for the Mac. You can download Oolite for Windows and for Linux PCs from [http://oolite.org/download.shtml Oolite's homepage] (click on "show all platforms" if you can't see the version you're looking for). Information on test releases can be found through the Oolite forums, for the [http://aegidian.org/bb/viewforum.php?f=9 Linux version], and for the [http://aegidian.org/bb/viewforum.php?f=8 Windows version].}}

== Writing OXPs ==

{{FAQ|question=I would like to contribute to Oolite and write my own OXP, but unfortunately my knowledge in scripting/programming is limited. How can I get started?|answer=First of all the Oolite community welcomes all efforts to enhance and enrich their favorite game, so be our guest! Many of us have started with very little knowledge, but over time were able to write and release astonishing OXPs, so why shouldn't you? Anyway, scripting can be learned. Currently there are two scripting languages in use for Oolite, plist-scripting (sometimes referred to as legacy-scripting) and JavaScript. For any serious OXP-plans you will have to learn them. A general starting point is the [http://wiki.alioth.net/index.php/OXP_howto OXP howto]-page, which will link you to further documentation. For plist-scripting you should read the [http://wiki.alioth.net/index.php/OXP_howto_plist OXP howto plist]-page, and also the [http://wiki.alioth.net/index.php/Property_list Property list]-intro. Information on the ongoing implementation of scripting with JavaScript can be found in the [http://wiki.alioth.net/index.php/Category:Oolite_scripting Category page for scripting] (work in progress). If you want to design a new ship, you should have a look at the [http://wiki.alioth.net/index.php/OXP_howto_model OXP howto model]-page and the [http://wiki.alioth.net/index.php/OXP_howto_texture OXP howto texture]-page. And if you want to give it a behavior of its own, you should consult the [http://wiki.alioth.net/index.php/OXP_howto_AI OXP howto AI]-page. I suggest you try to read and understand these first. If you still have questions afterwards, there is always the [http://aegidian.org/bb/index.php Oolite Bulletin Board], where lots of friendly people usually are very willing to lend a helping hand and to answer lots of questions.}}

{{FAQ|question=I want to write an OXP or add content to the Wiki, but some (or all) of the content was written by another author. What copyright issues do I face?|answer=Anything submitted to the Wiki is on the basis that anyone else may edit or fiddle with it. OXPs are submitted under the creative commons licence. The author (stricty speaking) owns the copyright, but licences users to use or distribute the OXP as long as they don't sell or charge for it. In practice virtually all OXP authors don't assert copyright and are pleased and flattered that somebody thinks their stuff is worth writing about or pinching to use in another OXP (its good manners to credit the orginal author in the readme though). I expect the author will be pleased if you want to add some background, but if you are in doubt, send him a PM asking him for permission. At the end of the day, Oolite is a fun project and everbody is doing stuff for it on that basis. (nicked wholesale from [http://aegidian.org/bb/viewtopic.php?p=44813#44813 Little_Bear's] post on the [http://aegidian.org/bb/index.php Oolite Bulletin Board])}}

== Diagnosing Problems ==

{{FAQ|question=Someone asked me for my log file. What is that, and where is it?|answer=In the test releases of Oolite, various diagnostic information is written to a file called Latest.log. Where it is depends on your operating system:
* '''Mac OS X''': ~/Library/Logs/Oolite/Latest.log (that is, in your home folder, open the folder named ''Library'', then ''Logs'', then ''Oolite''). Alternatively, select “Show Previous Log” from the “'''Oolite'''” menu in the menu bar when running Oolite.
* '''Windows''': in Oolite’s folder (typically in C:\''Program Files''), there is a folder called ''oolite.app'', which contains a folder called ''Logs''.
* '''Linux and other Unix-like systems''': ~/.Oolite/Logs (that is, in the hidden folder ''.Oolite'' in your home folder). If you’re using Nautilus or Konqueror—if you’ve never heard of them, you probably are—select Show Hidden Files from the View menu.}}

== Other Questions ==

{{FAQ|question=I have a question not answered here, where can I get help?|answer=Post your queries onto [http://aegidian.org/bb/index.php the friendliest board this side of Riedquat™]. Satisfaction is not guaranteed, but then what is, in this mixed-up universe? Help keep the board friendly by making sure your question isn't already answered here!

If you want to report a bug, please read [http://aegidian.org/bb/viewtopic.php?t=3778 this]. Yes, all that work is a drag, but if nobody reports the bug it probably won’t get fixed.

Or join us in #oolite, or #oolite-dev if you're working on Oolite or OXPs, on irc.oftc.net or ipv6.oftc.net.}}

[[Category:Oolite]]

Oolite FAQ

2011-12-22T03:55:00Z

Kaks: /* Getting Started */

== Getting Started ==

{{FAQ|question=Where do I get the program? And what about the different versions that exist?|answer= The latest 'official' stable release is version 1.76, and is available on the [http://oolite.org/download.shtml oolite.org download page] for OS X, Windows, and Linux(x86). The last stable release made by the original programmer, Giles Williams (a.k.a. Aegidian) was 1.65 and is best available from his website [http://oolite.aegidian.org/ oolite.aegidian.org]. The latest test releases/development versions can be [http://developer.berlios.de/project/showfiles.php?group_id=3577 downloaded from BerliOS] with installers also available for OS X, Windows and Linux. More detailed information can be found on the [http://aegidian.org/bb/index.php Oolite Bulletin Board], in the respective sections for [http://aegidian.org/bb/viewforum.php?f=10 Oolite-Mac], [http://aegidian.org/bb/viewforum.php?f=9 Oolite-Linux] and [http://aegidian.org/bb/viewforum.php?f=8 Oolite-PC].}}

{{FAQ|question=What's the point of the game?|answer=To fly from planet to planet, buying and selling goods, shooting pirates or committing acts of piracy. There's no goal other than perhaps to achieve the rank of ELITE.}}

{{FAQ|question=I'm still confused, how do I play?|answer=It's a good idea to start with the [http://wiki.alioth.net/images/0/0d/Oolite_1.65_ReadMe.pdf.zip Oolite ReadMe] file for some basic information. For further information you may wish to consult the [http://wiki.alioth.net/index.php/Oolite_Instruction_Manual Oolite Instruction Manual] here on the wiki. A load of helpful information can be obtained from [http://wiki.alioth.net/index.php/Mr_Gimlet Mr Gimlet], the quite talkative dockmaster on Lave Station. If you're a fresh graduate from the Flight Academy on the way to your first ship, you should see him. It's also a good idea to have a look at Ian Bell's [http://www.iancgbell.clara.net/elite/manual.htm Flight Training Manual] for the original BBC Elite, although some of Oolite's control keys are different from the original, so be careful.}}

{{FAQ|question=How do I configure my joystick or gamepad for Oolite in Linux?|answer=See [[Linux Joysticks and Gamepads]].}}

== Gameplay ==

{{FAQ|question=What do the various colors represent on the radar?|answer=White - unpowered items that can't mass-lock the in-system drive (jumpdrive). Green/Yellow - navigation buoys. Yellow - powered craft. Red - powered craft identified as hostile. Green - space stations. Green/Red - thargoids. Purple - police. Blue/Red - police on intercept. Red/Yellow - active mine (about to detonate). Blue/Cyan - witchspace wormhole.}}

{{FAQ|question=I keep crashing when trying to dock. How do I dock manually?|answer=Many young Jamesons have met a sticky end and had to be scraped from the docking port of Lave Station whilst attempting docking. Its fairly easy once you get the hang of it. Check the [[How_to_Dock|How to Dock]] guide from the Galactic Navy Flight Manual. Or you can get the [[Traffic_Control_OXP|Traffic Control OXP]] for friendly instructions given by the station crew as you try to dock.}}

{{FAQ|question=How do I make decent profits?|answer=Trade between a Poor or Average Agricultural and a Rich or Average Industrial planet. Write down the prices for everything on both planets and find out where you make the most profit per ton. You can also download the [http://wiki.alioth.net/images/d/df/OoliteRS_rev1.8.zip Oolite Reference Sheet], which features a table with the average prices. From there you can figure out whether you're on a buyers' or a sellers' market. The [http://wiki.alioth.net/images/9/9e/OoliteTradingChart2.zip Trading Chart] allows you to create your own statistics along your way. [http://www.box.net/shared/bchkkloi32 This spreadsheet] highlights Poor Agricultural and Rich Industrial planets on a star chart (the spreadsheet is in .xls format and needs the Analysis Toolpak installed). You can also earn credits by taking cargo contracts - courier goods of varied type and volume between planets near and far. The spreadsheet helps assess whether you will be be able to complete the contract on time, and so build your reputation as an outstanding courier. Another option is to fit one or more [http://wiki.alioth.net/index.php/Passenger_Berth Passenger Berths] in your ship and earn credits by transporting individuals who, for one reason or another, prefer not to use the commercial Passenger Liners to reach their destination. As with cargo contracts, you can build your reputation up, which will result in your being offered more lucrative fares.}}

{{FAQ|question=It takes so long to get to the station after each jump. Can I do anything to speed the trip up?|answer=Well, space is huge. It is vast. I mean, have you ever imagined a football-field with an orange in one of the goals and a walnut in the other goal? If you haven't, then don't. It takes you nowhere. As will your ship's engine at normal speed. But then that's what your jumpdrive is for. Hit '''J''', and your journey speeds up. Unfortunately your jumpdrive doesn't work when other masses, like ships or planets, are nearby. They will 'lock' it. And in the 'corridor' between the witchpoint and the planet you are very likely to meet other ships. On the other hand there is no rule that you have to stick to the corridor. Just leave it sideways in any direction with your jumpdrive engaged for about 10-15 seconds, and head for the planet then. Makes your voyage much smoother. If you're a bounty-hunter and eager to meet lots of pirates, however, this is not your method of choice.}}

{{FAQ|question=I have already made my first intergalactic jump to Galaxy 2, but now I remember that I forgot my Zero-G cricket set/food blender/deadly lobstoid/edible arts graduate on Lave/Tionisla/Xeesle/Reesdice! Or I just found out that there are some more missions I'd like to do in the first galaxy. So how can I jump back to Galaxy 1?|answer=You can't. Unfortunately due to their very physical nature intergalactic wormholes allow for one-way travel only. Fortunately, though, the intergalactic wormhole in Galaxy 8 connects back to Galaxy 1. So you can go full circle. And you have to, if you want to return to the first galaxy. Of course that will cost you another 5000 credits for each galactic hyperjump. So the complete 8-Galaxies-Sightseeing-Tour has a pricetag of a total 40000 credits.}}

{{FAQ|question=I've got a trumble! First it was cute and fluffy. But then it started to multiply. Even worse, they started to eat everything on board and they are confusing my sights. I don't want them anymore! How can I get rid of them? Help!|answer=First of all, don't feel embarrassed. It happens to all commanders sooner or later. I mean, they're really cute and fluffy, aren't they? But seriously, there are several things you could try. E.g. sell them to other unsuspecting noobs. If you don't find enough willing buyers, you could use your escape capsule and abandon your infested ship, hoping that they haven't yet made it into the escape pod, of course. I mean, you can always hope, can't you? If that all doesn't work for you, just remember the old Klingon saying: 'Revenge is a dish that is best served cold.' Now consider that for trumbles it's just the opposite. Want some BBQ-sauce?}}

{{FAQ|question=My keyboard doesn't have a particular key used by Oolite, or I even want to change the keyboard layout completely to my liking. What can I do to change the keys?|answer=Oolite reads a key configuration file called keyconfig.plist that you can find at /AddOns/Config/keyconfig.plist; that is the Config-folder that you find inside your AddOns-folder; which is where you put your OXPs. (PC-users have to create the folder /AddOns/Config/ first and then drop a copy of the keyconfig.plist found in /Oolite.app/Contents/Resources/Config/ to this folder.) You can open this file in any text editor and change the ASCII values of the keys used to suit your own preferences. Information on the default keys is also found in the [http://wiki.alioth.net/index.php/Oolite_Keyboard_Controls Oolite Keybord Controls-documentation] here on the wiki.}}

{{FAQ|question=I've completed a number of native and OXP missions and my [http://wiki.alioth.net/index.php/Cobra_Mk.3_%28Oolite%29 Cobra Mk. III] has a number of new and funky pieces of equipment. However, I'm planning a change of ship, what pieces of equipment will I lose as a result?|answer=Many missions award equipment as a result of either accepting or completing them. For the majority of ship equipment, trading ships will result in the equipment being sold as well, with a few exceptions. The '''Cloaking Device''' and the '''Mark Transponder Scanner''', available from the (native) Cloaking Device and (OXP) Assassins missions respectively are transferred to your new ship. The '''Naval Energy Unit''', although awarded with the completion of the (native) Thargoid Plans mission, will be sold when you trade ships. However, completing the mission allows you to buy these units from high TL systems.}}

{{FAQ|question=I’m using ECM-hardened missiles, but enemies are still able to destroy them! I never seem to be able to destroy enemy hardheads, though. What gives?|answer=ECM-hardened missiles are not ECM-proof. The probability of a hardened missile being destroyed by ECM is 10%–34% depending on range, and if it is destroyed, there’s a 50% chance that it will detonate. This applies equally to hardened missiles fired by computer-controlled ships and those fired by the player. The most effective use of hardened missiles is to use them against relatively slow targets at moderate range, and only use them on nimble ships if you desperately need to force them to break of an attack. Also, don’t use your ECM until a missile is close to blast range (250 metres).

Specifically, the ECM sends out four pulses with different ranges, at half-second intervals. Each pulse has a 10% chance of destroying each hardhead it encounters. For a missile fired at close range, that’s 1 - 0.94 = 34.39% chance of being destroyed within two seconds.}}

{{FAQ|question=If I believe that sizes and distances in Oolite are given in meters, it is so ''unrealistic''. The planets have a diameter of only 30–50 kilometers, and the suns are only 1000 kilometers away. Can't we get a little more realism in space, please?|answer=First of all, remember that Oolite is a ''game'', not a ''space simulation''. This is because it ''wants to'' be a game, not a sim. So yes, sizes and distances are all messed up. Ships and stations are too big, planets and suns are too small, and too close to each other. But this is ''deliberately'' so, and we are not going to change it.

The reason is simple: Realistic sizes and distances don't make a good game. In reality space is so huge that you never would meet anybody else on your journey. Imagine the dozen or so ships you meet in the 500 or so kilometers between witchpoint and planet spread over the realistic 150 '''million''' kilometers between Sun and Earth. Even if your direction is only one degree off the perfect line, you would miss them all. And how interesting would that be for the gameplay? And finally, if you had a realistically sized station in front of a realistically sized planet, how would you ever even notice it? A grain of sand in front of a, well, '''planet'''. The result would be players in complete loneliness and virtually no interaction with NPCs. An utterly, utterly boring game. Therefore it was the right decision to screw realism in the layout of the planetary systems in Elite and Oolite.}}

== Expanding the Game ==

{{FAQ|question=Speaking of OXPs, I've heard a lot about them. What are they? And where do I find them?|answer=OXP stands for 'Oolite eXpansion Pack'. As the name suggests, an OXP is an expansion to the game. It can contain virtually everything: new graphics for your ship, new ships for the player and/or the NPCs, new stations, new missions, new fun. To install an OXP you simply have to drag it into your AddOns-folder (only the OXP itself, not the folder it probably comes in). And as for finding them, you're already at the right place. All OXPs are now (or will become) accessible through the [[OXP|OXP-page of the wiki]]. Just follow the link. And if you fancy trying to create an OXP, the modifying Oolite FAQ can be found [[Modifying Oolite Informal FAQ|here]].}}

{{FAQ|question=Are there any OXPs that are highly recommended? Or can I get a list of 'must-have' OXPs?|answer=This is a difficult one to answer, because it depends so much on personal taste. There is no list of 'must-have' or necessary OXPs that could be agreed upon by all—or even most—players or contributers. But if you have a look at the [http://aegidian.org/bb/index.php Oolite Bulletin Board], especially the [http://aegidian.org/bb/viewforum.php?f=2 Discussion]- and the [http://aegidian.org/bb/viewforum.php?f=4 Expansion Pack]-forums, you will surely find some topics about this question, and the personal answers of a couple of board members.}}

== Why does this and that not exist? ==

{{FAQ|question=Will there ever be an Oolite Massive Multi-player Online Role-Play Game (MMORPG)?|answer=At present Ahruman and Co. (the developers) have no plans to develop either Oolite or a separate branch to accommodate either an MMORPG or an MOG (Multi-player Online Game). This, however, doesn't mean one of you clever bods out there can't try ;-) We suggest you read [http://aegidian.org/bb/viewtopic.php?t=6173 this Bulletin Board thread] before you commence though, it may save you a lot of hair-tearing!}}

{{FAQ|question=Can the range of hyperspace jumps/my fuelcapacity be increased?|answer=No. Jumprange in Oolite is hardcoded for a reason. The game would become less challenging and thus less fun. (Although I can imagine hacks that give unlimited fuel.) And don't forget that there are already various ways of refueling while you are in flight.}}

{{FAQ|question=I want Laser Cooling Boosters!|answer=There are none at the moment and the reason is simple. It would unbalance the game too much. If they were available for the player only, things would get too easy. And if the NPCs could get them, too, things would get too hard. It's all about maintaining a reasonable balance. So the ultimate advice on this is: Aim carefully. Don't waste your laser fire. Prevent overheating.}}

{{FAQ|question=The other day I got killed when I launched from a Rock Hermit/Behemoth/whatever, and all the profits/kills that I made before were gone. Why couldn't I save there? Why only on main stations?|answer=First of all, congratulations to you for having internalized the ''Golden Rule'': save early, save often! Unfortunately in Oolite you can save and load a commander only on main stations. That's because they are the only 'fixed' objects in space. The rest of the system is populated anew each time you load a game and is not saved in your savefile. So chances are that the Rock Hermit or Behemoth you docked with when saving simply wouldn't exist when you load again, and you would find yourself in nirvana instead of in a safe haven. To prevent odd behavior like this saving and loading is prohibited anywhere else than in a main station. Alternatively you could install [http://wiki.alioth.net/index.php/Save_Anywhere Save Anywhere.oxp], which does exactly what it says on the tin. Note, however, that it is still in beta state. Read the documentation first.}}

{{FAQ|question=I would like to switch between different ships of mine, e.g. have a nice racer for the weekends, meanwhile leave my freighter docked somewhere and take it back on Monday. Why can't I do this?|answer=What else do you want? Custom paintjobs and interiors? A millionaire's spaceship-flotilla, one for every occasion? Who do you think you are? Jay Leno??? (Apologies if you ''are'' Jay Leno, but then you should have something else to do than playing computer games.) Let me tell you something: Space stations are no garages. Docking bays are limited, and the 'garage'-fees would be prohibitive. Imagine everybody else out there would want the same parking facilities!—Having said that, there is also a technical reason: A player can't have two ships and switch between them, because for the game the player ''is'' his ship, and you can ''be'' only one ship at a time. There is no way of storing a ship in your savefile and retrieving it later.}}

{{FAQ|question=I am playing one of the test releases on a PC or Linux system and I want to see the cool new planet textures everyone is going on about. How do I do it?|answer=The next time you leave a station pause the game (press '''P'''), then press '''T'''. A message saying 'Procedural Textures On' will pop up. Unpause the game and the next time you jump and after all subsequent jumps and on exiting stations, you will experience the new textured planets.}}

{{FAQ|question=I am playing Oolite 1.73.4 on a Mac system and I want to see the cool new planet textures everyone is going on about. How do I do it?|answer=Upgrade to the latest test version (currently 1.74.2). Then follow the instructions in the answer directly above.}}

== Known Issues / Bugs ==

{{FAQ|question=Every so often some of the messages (either from other ships or from my ship) on the bottom of the screen remain and end up 'scrolling' up the screen to cover my gunsights. What's up with that?|answer=The 'sticky messages' bug is, unfortunately, a long standing issue in Oolite, still present in 1.65 and a few releases since. Starting with Oolite 1.71.1 this problem has been eliminated. If you prefer an older version of Oolite, flicking between views (either internal or external) is probably the quickest way to clear the messages.}}

{{FAQ|question=Every so often I meet a ship or a cargopod that I can't lock on. My laser fire goes right through it. Sometimes it happens with a ship I have just killed. Sometimes after a while it even starts again firing at me, but I can't harm it anymore.|answer=The 'ghost ship' bug is another very old acquaintance in Oolite, and again the tireless developers are trying to rectify this. In the meantime, ignoring the ghost ships (or cargo pods) is the best thing you can do.}}

{{FAQ|question=The brightness of the rotating ships screen on the start-screen of the game has gone dark, I can hardly see them anymore. Do you know that, and what can I do about it?|answer=This is a problem with the lighting model for ships using shaders. The tireless developers are aware of the problem and are going to fix it. In the meantime, and as the problem only occurs when the shader settings are set to 'Full', you can work around it by setting them to 'Simple' or 'Off' in the Options-screen of Oolite (press '''F2''' and choose 'Game Options...'). Although of course you won't have the shader effects then.

The alternative is to open the controls for your graphics card and boost the gamma setting of your card by 10-20%. This will have a marginal effect on your screen colours when using your computer, but it will make ships in-game a lot brighter and easier to see.}}

== System Requirements ==

{{FAQ|question=Does it work on Mac OS X 10.2 (Jaguar)?|answer=Sadly, no. The minimum OS requirement for Oolite on the Mac is now Mac OS X 10.3.9.}}

{{FAQ|question=Does it work on the new Intel Macs?|answer=Yes, from 1.65 Oolite is Universal Binary.}}

{{FAQ|question=What's the latest version?|answer=The last stable release is 1.65. However, the latest test release—1.74.2 at the time of writing—is faster, more reliable, and offers better graphics than the stable version, and is the recommended download. Yes, we're aware this sounds silly. The last stable and latest test versions can be downloaded from [http://oolite.org/download.shtml Oolite's homepage]. More information can be found through the [http://aegidian.org/bb/viewforum.php?f=10 Oolite forums].}}

{{FAQ|question=Is there a port for the PC or Linux?|answer=Yes. Both ports are stable and are at the same level of development as Oolite for the Mac. You can download Oolite for Windows and for Linux PCs from [http://oolite.org/download.shtml Oolite's homepage] (click on "show all platforms" if you can't see the version you're looking for). Information on test releases can be found through the Oolite forums, for the [http://aegidian.org/bb/viewforum.php?f=9 Linux version], and for the [http://aegidian.org/bb/viewforum.php?f=8 Windows version].}}

== Writing OXPs ==

{{FAQ|question=I would like to contribute to Oolite and write my own OXP, but unfortunately my knowledge in scripting/programming is limited. How can I get started?|answer=First of all the Oolite community welcomes all efforts to enhance and enrich their favorite game, so be our guest! Many of us have started with very little knowledge, but over time were able to write and release astonishing OXPs, so why shouldn't you? Anyway, scripting can be learned. Currently there are two scripting languages in use for Oolite, plist-scripting (sometimes referred to as legacy-scripting) and JavaScript. For any serious OXP-plans you will have to learn them. A general starting point is the [http://wiki.alioth.net/index.php/OXP_howto OXP howto]-page, which will link you to further documentation. For plist-scripting you should read the [http://wiki.alioth.net/index.php/OXP_howto_plist OXP howto plist]-page, and also the [http://wiki.alioth.net/index.php/Property_list Property list]-intro. Information on the ongoing implementation of scripting with JavaScript can be found in the [http://wiki.alioth.net/index.php/Category:Oolite_scripting Category page for scripting] (work in progress). If you want to design a new ship, you should have a look at the [http://wiki.alioth.net/index.php/OXP_howto_model OXP howto model]-page and the [http://wiki.alioth.net/index.php/OXP_howto_texture OXP howto texture]-page. And if you want to give it a behavior of its own, you should consult the [http://wiki.alioth.net/index.php/OXP_howto_AI OXP howto AI]-page. I suggest you try to read and understand these first. If you still have questions afterwards, there is always the [http://aegidian.org/bb/index.php Oolite Bulletin Board], where lots of friendly people usually are very willing to lend a helping hand and to answer lots of questions.}}

{{FAQ|question=I want to write an OXP or add content to the Wiki, but some (or all) of the content was written by another author. What copyright issues do I face?|answer=Anything submitted to the Wiki is on the basis that anyone else may edit or fiddle with it. OXPs are submitted under the creative commons licence. The author (stricty speaking) owns the copyright, but licences users to use or distribute the OXP as long as they don't sell or charge for it. In practice virtually all OXP authors don't assert copyright and are pleased and flattered that somebody thinks their stuff is worth writing about or pinching to use in another OXP (its good manners to credit the orginal author in the readme though). I expect the author will be pleased if you want to add some background, but if you are in doubt, send him a PM asking him for permission. At the end of the day, Oolite is a fun project and everbody is doing stuff for it on that basis. (nicked wholesale from [http://aegidian.org/bb/viewtopic.php?p=44813#44813 Little_Bear's] post on the [http://aegidian.org/bb/index.php Oolite Bulletin Board])}}

== Diagnosing Problems ==

{{FAQ|question=Someone asked me for my log file. What is that, and where is it?|answer=In the test releases of Oolite, various diagnostic information is written to a file called Latest.log. Where it is depends on your operating system:
* '''Mac OS X''': ~/Library/Logs/Oolite/Latest.log (that is, in your home folder, open the folder named ''Library'', then ''Logs'', then ''Oolite''). Alternatively, select “Show Previous Log” from the “'''Oolite'''” menu in the menu bar when running Oolite.
* '''Windows''': in Oolite’s folder (typically in C:\''Program Files''), there is a folder called ''oolite.app'', which contains a folder called ''Logs''.
* '''Linux and other Unix-like systems''': ~/.Oolite/Logs (that is, in the hidden folder ''.Oolite'' in your home folder). If you’re using Nautilus or Konqueror—if you’ve never heard of them, you probably are—select Show Hidden Files from the View menu.}}

== Other Questions ==

{{FAQ|question=I have a question not answered here, where can I get help?|answer=Post your queries onto [http://aegidian.org/bb/index.php the friendliest board this side of Riedquat™]. Satisfaction is not guaranteed, but then what is, in this mixed-up universe? Help keep the board friendly by making sure your question isn't already answered here!

If you want to report a bug, please read [http://aegidian.org/bb/viewtopic.php?t=3778 this]. Yes, all that work is a drag, but if nobody reports the bug it probably won’t get fixed.

Or join us in #oolite, or #oolite-dev if you're working on Oolite or OXPs, on irc.oftc.net or ipv6.oftc.net.}}

[[Category:Oolite]]

OXP List

2011-12-05T08:56:40Z

Kaks: /* Sortable Table of OXPs */

__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 beta 1.75:

"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=2011-09-20
|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=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=2011-03-10
|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=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=2010-03-18
|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=2011-07-17
|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=2011-05-03
|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=2011-11-04
|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=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=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=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=2010-01-09
|work=}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[BGS|BGS - Background Set]] framework for images, sounds and ambient music
|aut=[[User:Pagroove|pagroove]], [[User:Svengali|Svengali]]
|date=2011-09-18
|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=2010-03-08
|work=}}
{{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=[[Boa II Clipper Class]] is a development of the Boa Class Cruiser, adding a third engine at the cost of cargo space
|aut=[[User:Smivs|Smivs]]
|date=2011-01-27
|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]] makes some standard equipment such as HUD/Scanner damageable in combat
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-07-10
|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=2011-06-13
|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=2011-08-10
|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=2011-01-31
|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=Ships
|desc=[[Chopped Cobra]] by Staer9. Chopped version of Griff's Cobra. Includes Enforcer and S9 variants by Smivs.
|aut=[[User:Staer9|Staer9]]
|con=Smivs
|date=2011-07-24
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Cobra 3.5|Chopped Cobra]] by Aegidian. 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=[http://aegidian.org/bb/viewtopic.php?f=4&t=11014 ChupaCabra] is a bird-like ship featuring the ChupaCabraHUD
|aut=[[User:Staer9|Staer9]]
|date=2011-11-17
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://wiki.alioth.net/index.php/ChupacabraHUD 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=[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 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=11206 Coluber] is a medium size cargo ship, fast, maneuverable, and armed well enough
|aut=Captain Beatnik
|date=2011-11-21
|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-07-15
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[[Contractor ZZ1]] Very fast combat 'stealth' ship. Appears in-game as a Bounty-hunter and rarely as Pirate. Buyable
|aut=[[User:Smivs|Smivs]]
|date=2011-01-05
|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=[http://aegidian.org/bb/viewtopic.php?f=4&t=10819 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-09-04
|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-03
|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-07-10
|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=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=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=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=[http://www.aegidian.org/bb/viewtopic.php?f=4&t=11294 Enhanced Misjump] changes the effect of the jump tunnel when having a misjump
|aut=cim
|date=2011-12-04
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Escape Pod Locator OXP|Escape Pod Locator v1.2]] is a piece of equipment to allow tracking of escape pods in system
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-11-20
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Escort Contracts OXP|Escort Contracts v1.4.2]] allows players to enter into short-term escort contracts with NPC lone wolf traders
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-11-20
|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.2.1 keeps a record of the systems you have visited and gives you an explorer rank
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-12-01
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://www.box.net/shared/moreq536ht#/shared/moreq536ht/1/71484311/786362645/1 Extra Thargoids] adds 2 types of Thargoid ship, each of which packs surprises. Replaces the 'Poet' Frigate OXP
|aut=[[User:Uk Eliter|UK_Eliter]]
|date=2011-12-05
|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=2011-07-29
|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=[http://www.box.net/shared/d57y0uip74 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=[[User:Uk Eliter|UK_Eliter]]
|date=2011-12-05
|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=[[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-05-30
|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=[[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=2011-08-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=2011-11-19
|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://www.boxcn.net/shared/5dqx22u06i Galaxy Info] helps you search for systems by criteria you select and will try to locate the nearest one
|aut=Okti
|date=2011-04-02
|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=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11198 GalDrive Programmers] allow to set the target system for a galaxy jump
|aut=Wildeblood
|date=2011-11-22
|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=[[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=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=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.boxcn.net/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=2011-12-04
|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-05-11
|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=2011-02-19
|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]]
|date=2010-06-14
|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=2010-09-05
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Hyperradio js OXP|Hyperradio]] is an expandable music-player
|aut=[[User:Svengali|Svengali]]
|date=2011-02-18
|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]] adds interactions with Galcop customs on docking at a main station with Contraband in the hold
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-08-07
|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 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=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=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=2011-11-23
|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=2010-06-13
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[http://www.boxcn.net/shared/9q1cbydgan LinkG7] is a mission in Galaxy 7
|aut=Okti
|date=2011-02-16
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[http://wiki.alioth.net/index.php/Liners Liners] adds some beautiful and very large vessels to the spacelanes.
|aut=[[User:Smivs|Smivs]]
|con=pagroove, Thargoid, Griff, Eric Walch
|date=2011-11-23
|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/jtpt2vlol5 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=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=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=[[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=[[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=[http://wiki.alioth.net/index.php/MFLPS 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=HUDs
|desc=[[Milspec HUD|Milspec HUD]] is an alternative HUD with targeting aids and an emphasis on functionality
|aut=[[User:Wyvern|Cdr. Wyvern]]
|date=2010-07-08
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[[Misjump_Analyser|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-06-21
|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=2009-12-14
|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=Retextures
|desc=[[Neolite Ships]] is an Oolite ships replacement set
|aut=[[User:Simon B|SimonB]]
|date=2009-07-11
|work=}}
{{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=[[User:Uk Eliter|UK_Eliter]]
|date=2011-10-02
|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=2011-04-14
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://wiki.alioth.net/index.php/Numeric_Style_HUDs Numeric Style HUDs] New invention/numeric gauges.[http://aegidian.org/bb/viewtopic.php?f=4&t=9977 Info]
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-06-13
|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=2010-06-24
|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://www.box.net/shared/rrlm77ztzm Oolite en français] is a French Oolite localization
|aut=Pierre-Olivier
|date=2009-07-12}}
{{OXPSortableTableRow
|cat=Misc
|desc=[http://marc-schaffer.ch/data/OoliteGerman_V0.3.zip Oolite auf Deutsch] is a German Oolite localization
|aut=[[User:User:SwissMÃ¤c|SwissMäc]]
|date=2009-06-02
|work=}}
{{OXPSortableTableRow
|cat=Misc
|desc=[http://www.box.net/shared/p3engis1ds Oolite Italiano] is an Italian Oolite localization
|aut=[[User:Another commander|another_commander]]
|date=2010-06-15
|work=}}
{{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://www.box.net/shared/x9u5xoulkq Orbits] positions planets on orbits around the sun
|date=2010-07-01
|aut=[[User:Ebi|Ebi]]
|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=2011-01-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 means to configure supported OXPs, to recognize errors, or to avoid clashes
|aut=[[User:Svengali|Svengali]]
|date=2011-07-16
|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=[http://wiki.alioth.net/index.php/Pie_Chart_Style_HUDs Pie Chart Style HUDs] New invention=>pie gauges.[http://aegidian.org/bb/viewtopic.php?f=4&t=9788 Info]
|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=2011-08-24
|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]] highlights offender and fugitive ships with custom IFF scanner colours
|aut=[[User:Capt. Murphy|Capt Murphy]]
|date=2011-09-24
|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/xccp8ml5cq 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=[http://wiki.alioth.net/index.php/Q-Charger 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-03-04
|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=2011-11-03
|work=Y}}
{{OXPSortableTableRow
|cat=Missions
|desc=[[Resistance Commander]] gives players a chance to command a squadron in combat
|aut=[[User:Ramirez|Ramirez]]
|date=2011-10-19
|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=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=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=2008-10-01
|work=N*}}
{{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=2010-06-06
|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=[http://aegidian.org/bb/viewtopic.php?f=4&t=11123 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]]
|date=2010-05-21
|work=}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://wiki.alioth.net/index.php/Shield_Equalizer_%26_Capacitors_OXP Shield Equalizer] balances shield energy automatically. [http://wiki.alioth.net/index.php/Shield_Equalizer_%26_Capacitors_OXP Capacitors] store unused shield energy for use later
|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=Retextures
|desc=[[Smivs%27_ShipSet|Smiv's Shipset]] re-skins the ships with a realistic look & non-shader lighting effects. Customisable Player Cobra3
|aut=[[User:Smivs|Smivs]]
|date=2011-08-26
|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=[http://wiki.alioth.net/index.php/Sniper_Camera_System_HUD Sniper Camera System] Zoomable camera for surveillance and long-range sniping.[http://aegidian.org/bb/viewtopic.php?f=4&t=10461 Info]
|aut=[[User:CommonSenseOTB|CommonSenseOTB]]
|date=2011-07-30
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10515 Sniper Sight] is the Ooniverse's most configurable precision gun sight
|aut=Wildeblood
|date=2011-12-04
|work=Y}}
{{OXPSortableTableRow
|cat=HUDs
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10176 Sniper Scope MilHUD integrated] is an version of MilHUD with integrated Sniper Sight functionality
|aut=Wildeblood
|date=2011-06-26
|work=Y}}
{{OXPSortableTableRow
|cat=Ambience
|desc=[[Snoopers]] adds the galactic news network channels
|aut=[[User:Daddyhoggy|DaddyHoggy]]
|con=Disembodied, Drew, Svengali
|date=2011-10-06
|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=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=2011-05-25
|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=Weapons
|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=2010-07-14
|work=Y}}
{{OXPSortableTableRow
|cat=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11054 SunBat] is a black, fast fighter, and even though it only packs one laser, is extremely formidable
|aut=mandoman
|date=2011-10-25
|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=2009-11-12
|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=[http://aegidian.org/bb/viewtopic.php?f=4&t=11156 Talkative Space Compass] is an upgrade to the advanced space compass that shows the name of the current target
|aut=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=2009-10-01
|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=2008-06-12
|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]]
|date=2006-06-13
|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=2011-02-03
|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=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=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=2010-12-23
|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 3 levels of increased toughness of 'Baddies', and gives a backdrop for an immersive storyline
|aut=[[User:Smivs|Smivs]]
|date=2011-12-03
|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=2011-08-22
|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=Missions
|desc=[[UPS Courier]] offers Commanders transport of goods/documents & occasional combat missions
|aut=[[User:Eric Walch|Eric Walch]]
|date=2011-03-29
|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-02-27
|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://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=Mission
|desc=[[Victim 11]] extends the [[The Assassins Guild OXP|Assassins Guild]] mission with an additional target
|aut=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=2011-09-20
|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=2010-06-20
|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=[[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=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=[http://www.xeptatlssword.com Xeptatls Sword] An epic mission to thwart the Thargoids, spanning all eight galaxies.
|aut=[[User:Smivs|Smivs]]
|con=Okti, El Viejo, Fatleaf
|date=2011-11-11
|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-01-05
|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=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=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=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=Mechanics
|desc=[http://www.box.com/shared/moreq536ht Interstellar Tweak] adds chance of empty interstellar space
|aut=[[User:UK_Eliter|UK_Eliter]]
|date=2011-12-05
|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=Retexture
|desc=[http://aegidian.org/bb/viewtopic.php?p=154365#p154365 Commies Retexture] gives the Commies a new face
|aut=Amaranth
|date=2011-10-20
|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=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://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=[http://aegidian.org/bb/viewtopic.php?f=4&t=10631 Kestros & Rockhopper] are a new escort and transporter from Koneko Industries
|aut=[[User:RyanHoots|RyanHoots]]
|date=2011-11-01
|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-04
|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=Mission
|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=Ambience
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11263 Povray Planets] adds procedurally generated textures to planets
|aut=submersible
|date=2011-11-29
|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=[[User:RyanHoots|RyanHoots]]
|date=2011-12-03
|work=Y}}
{{OXPSortableTableRow
|cat=Equipment
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11179 Sensible GalDrive] exchanges the Galactic Hyperdrive for a permanently-installable "Long-Range Hyperdrive"
|aut=Wildeblood
|date=2011-11-15
|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=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=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=10690 Staer9's Shipset] will replace all the ships that the Neolite companion replaces
|aut=[[User:Staer9|Staer9]]
|date=2011-11-28
|work=Y}}
{{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=Ships
|desc=[http://aegidian.org/bb/viewtopic.php?f=4&t=11082 Super Boa] is Koneko Industries' supercharged version of the standard trader's ship
|aut=[[User:RyanHoots|RyanHoots]]
|date=2011-11-01
|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=2011-09-01
|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=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.75.3
{{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=[[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]]

Hotrods OXP

2011-12-05T08:54:36Z

Kaks:

===Overview===
----
This Oolite expansion pack adds a collection of classic Elite ships with custom paint jobs. Includes also a large number of custom and standard racing vehicles and a gang of pirates with tiger stripes that somehow don't like the player.
Replaces (and fixes) Custompaints & Racers by Arexhack Heretic.

===Usage===
----
Once installed, a variety of ships with customised paint jobs are added to the universe.
When going to anarchy systems, the player stands a chance of meeting the tiger gang.

===Requirements===
----
This OXP requires version 1.65 of Oolite for the extra ships, or version 1.75+ for the scripted encounters.

===Download===
----
[http://www.box.com/shared/j2r6frlvq1 '''Hotrods v0.53'''] can be downloaded by clicking on the link.

===Links===
----
* [[OXP#Table_of_all_OXPs|Table of all OXPs]].

{{ship-OXP}} {{mission-OXP}}

Oolite JavaScript Reference: World script event handlers

2011-11-15T13:42:52Z

Kaks: /* playerStartedJumpCountdown */

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

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

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

World scripts are always active.

=== Game State ===

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

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

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

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

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

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

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

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

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

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

=== Docking ===

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

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

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

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

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

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.docked == true", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

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

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect.

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.docked == false", "ship.status == STATUS_LAUNCHING".

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

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect.

this.shipLaunchedFromStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == null", "ship.docked == false", "ship.status == STATUS_IN_FLIGHT".

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

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

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

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

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

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

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

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

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

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

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

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

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED".

=== Witchspace Jumps ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Enter/Exit Aegis ===

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

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Combat ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==== <code>shipTargetDestroyed</code> ====

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

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

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

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

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

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

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

==== <code>shipTargetLost</code> ====

The <code>shipTargetLost</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity.

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

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

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

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

=== Equipment ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Other ===

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

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

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

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

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. "from" is the screen it is changing from and "to" is the screen were it initially switched to. Note that the screen can have changed again in the meantime by the action of other oxps. Therefor it will generally better to test for the global 'guiScreen' to see which page is really on display now instead of using the 'to' parameter. (world script only)

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

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

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

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

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

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

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

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

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

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

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

This handler works a bit different as other handlers. It fires for every installed oxp, until an oxp creates a mission screen during this handler. Than it stops. When the mission screen ends and there is no callback function that created a new mission screen, than the missionScreenOpportunity is send again to all installed oxps, starting with the oxp that used the mission screen as last one. All this means that when this handler fires, it is safe to show a mission screen and no further test are needed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==== <code>viewDirectionChanged</code> ====
{{Oolite-prop-added|1.75}} 
The <code>viewDirectionChanged</code> handler is called when the player view changes, with a string to indicate which view the player is facing. Amongst its possible values are "VIEW_FORWARD", "VIEW_AFT", "VIEW_PORT", "VIEW_STARBOARD",
"VIEW_CUSTOM",
"VIEW_GUI_DISPLAY".

this.viewDirectionChanged = function(viewString)
{
if (viewString == "VIEW_PORT")
{
// Your code here
}
}

=== Missing Events ===

All the initially planned events have been implemented in 1.74.

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

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

[[Category:Oolite JavaScript Reference]]

Shipdata.plist

2011-10-23T10:27:34Z

Kaks: /* missile_role */

'''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically:

= Ship keys=
The following keys are used by all ships
==accuracy==
Used with missiles it has influence on tracking of target. Allowed values with missiles are between 0.0 and 10.0. When not defined, the system assings to the missile the accuracy value of 0.0, which corresponds to the standard missile tracking behaviour.

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

Example:
"accuracy" = 8;

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

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

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

Example:
"aft_weapon_type" = "WEAPON_BEAM_LASER";

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

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

== auto_ai ==
This will autoswitch the ai to the appropriate one if a ship was added in one of its standard roles like trader or pirate. (true by default). See also the comment in the autoAIMap.plist inside Oolite. Defining auto_ai is only necessary when using one of the standard roles mentioned in the autoAIMap.plist for your ship. auto_ai does nothing for ships with custom roles.
Example:
"auto_ai" = yes;
This auto_ai switch is also used for bounties. When auto_ai is false the ship will keep the bounty as defined for the ship but, when true and the ship is added in one of the populator roles, the ship will get the default bounty for that role.

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

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

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

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

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

H = Homing Beacon (ett Homing Beacon)

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

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

We can also use custom icons with the compass. For that you must define a key in descriptions.plist with the same name as the beacon definition. Than define the icon in the same way as missile icons. (An array of x/y-coordinates that will be connected by lines). You can find more info at [http://aegidian.org/bb/viewtopic.php?f=4&t=9529 the Oolite BB]. 
Example in shipdata:
"beacon" = "fuelStation_location";
Example in descriptions.plist
"fuelStation_location" = (1, 2, -3, 2, -3, -4, 3, -4, 3, 4, -3, 4, -3, 3, 2, 3, 2, -3, 1, -3 );
Before 1.75 the ships primary role was used for defining the icon name in descriptions.plist, but since 1.75 the beacon name itself is used.

== bounty ==
Sets a Cr. reward on the NPC's head, and is bound to give it trouble with the law . This bounty setting is overruled when adding ships in one of the populator roles like pirate, trader etc. Pirates are default added with a small bounty and traders are added clean. However, like the player, also the npc bounty can raise when attacking other clean ships or police vessels.

Example:
"bounty" = 50;

== cargo_carried ==
Determines the type of cargo carried as described in [[commodities]] and [[commodities.plist]]. Only one type can be specified. This key can be used for both ships and barrels.

Example:
"cargo_carried" = "Gold";

When used for barrels, it is also possible to add several units in a pod by preceding the commodity name with a space separated number. Adding more than a ton in a pod is not possible. Defining a quantity for ships is not possible this way. 
It is possible to define a mix of random cargo for ships by using the string "SCARCE_GOODS" or "PLENTIFUL_GOODS", instead of a commodity name. The first selects random goods that are scarce at the main station, the second selects goods that are plentiful present at the main station. (Populator added traders heading toward the station always have scarce goods while traders heading from the main station always have plentiful goods on board. It would be wise to stick to this rule with custom ships.) 
To make cargo_carried working for ships, the cargo_type must be "CARGO_NOT_CARGO" to define the ship not being cargo itself. (see below)

== [[cargo_type]] ==
Determines if object is indeed cargo (CARGO_RANDOM, CARGO_SLAVES, CARGO_THARGOID, CARGO_ALLOY, CARGO_MINERALS, CARGO_CARRIED) or a ship, as below, which is not cargo. Works since Oolite 1.71 also for pods spawn by a script. CARGO_CARRIED needs in addition an second key cargo_carried that specifies the cargo. (see below) 

Example:
"cargo_type" = "CARGO_RANDOM";

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

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

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

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

Another notable type of cargo is the scripted item CARGO_SCRIPTED_ITEM, as examplified by the cloacking device. When CARGO_SCRIPTED_ITEM is defined, the barrels will trigger scooping events for the ship-scripts. Other barrels don't trigger scooping events. 
The cargo barrels are stored in the ships hold like normal barrels when a cargo was defined for them with the JS method "setCargo". Without defined content, scripted barrels are removed after scooping. Scripted cargo works with any object that can be scooped. When you have scripted escape pods that must be preserved after scooping, fill it with one ton of Slaves.

== cloak_automatic ==
When false, the cloak of npc ships will never get activate automatic during combat, but is only activated by JS script commands. (True by default) Key added with Oolite 1.75

Example:
"cloak_automatic" = no;

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

Example:
"cloak_passive" = yes;

==conditions==
With this option you can include an array of extra conditions when to add a ship. When the conditions are not met, the ship does not appear in a selection list by role. Useful when you have a standard ship like a trader that should only be added in certain systems.

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

== counts_as_kill ==
Killing this ship will not count as a kill by the player when set to false. (Default is true). Using this key prevents awarding kills to all kind of cargo, debris etc. Key is added with Oolite 1.75

Example:
"counts_as_kill" = no;

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

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

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

For the view_orientation you will probably need a calculator but the basic method is to choose a unit vector (x y z) as the axis for a rotation then calculate the four values W X Y and Z for the quaternion as follows:

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

Four decimal places are probably enough accuracy for these values.

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

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

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

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

Example:
"debris_role" = "my_boulder_foo";

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

Example:
"density" = 1.5;

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

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

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

Example:
"energy_recharge_rate" = "3.5";

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

Example:
"escape_pod_model" = "custom_pod";

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

Example:
"escorts" = 4;
Warning: Ships with scanClass = CLASS_POLICE should always have escorts set to zero. Oolite will set this value here and add wingmans instead of escorts. Without special scripting escorts won't escort a mother with CLASS_POLICE. 
For ships that are added in a trader role, the populator can decide to subtract escorts from the defined value when the system is estimated as safe.

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

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

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

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

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

x y z width height length

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

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

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

'''length''' in meters, how long a plume is on z axis. (This value is in current Oolite versions ignored. Length is now derived from the ships speed)

Below are 2 assigned plumes at coords 5, 0, -25 and -5, 0, -25, and each plume is 6 m wide and 4 m tall. (length info is ignored)

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

== extra_cargo ==
Cargobay extension size can be customised. This is the amount the cargo capacity increases when an extra cargobay is installed. Default value is 15. It is only used with player ships.

Example:
"extra_cargo" = 25;

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

Example:
"forward_weapon_type" = "WEAPON_BEAM_LASER";

== frangible ==
Determines if eventual sub-entities are "loose". By default any given object is already frangible, so the use of this line must be to negate that.
If set to false, the object plus subentities will be regarded as a single object.
If set to true, sub entities can be destroyed seperately from the main object. Frangible sub-entities can have a max_energy and an energy_recharge_rate that is independently set from the main entity.

Example:
"frangible" = no;

== fragment_chance ==
Determines if a ship breaks apart into fragments and generates parts with role "wreckage". By chance factor, or true/false. Default is 90% chance.
The amount of wreckage is based on the ships mass with a maximum of 3. Wreckage is scaled to match the ships size but is very short living. (0.25s -> 1.25s)

Example:
"fragment_chance" = no;

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

Example:
"fuel" = 70;

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

Example:
"has_cloaking_device" = 0.5;

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

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

== has_energy_bomb ==
Determines if a ship has an energy bomb. If it has one, it might launch a mine with role "energy_bomb" as part of his fleeing behavior. currently the only build-in mine with this role is the q-bomb. A ship will only deploy the bomb when it has also fuel-injectors and some fuel left to avoid getting killed by its own bomb. On average it will try to deploy the bomb once every 100 seconds during fleeing.

Example:
"has_energy_bomb" = yes;

== has_escape_pod ==
Determines if a ship has an escape pod. Can be either a boolean value, or a number from 0 to 1 expressing the likelihood of the equipment being present. Starting with version 1.65 ships can have multiple escape pods. To specify more than one escape pod, '''has_escape_pod''' must be set to a numeric value corresponding to the escape pods present on board.

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

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

Example:
"has_fuel_injection" = 0.99;

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

==has_military_scanner_filter==
Determines if a ship has a military jammer filter. Ships equipped with this item can see ships equipped with a military jammer on the radar.
Example:
"has_military_scanner_filter" = 0.50;

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

Example:
"has_scoop" = no;

== has_scoop_message ==
A key for cargo. Determines if a barrel generates a default scoop message when scooped. Default is true, but setting it to false suppresses any messages, so a scripts can generate its custom messages on scooping. (Added with Oolite 1.74)

Example:
"has_scoop_message" = no;

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

Example:
"has_shield_booster" = 0.80;

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

Example:
"has_shield_enhancer" = 0.45;

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

Example:
"heat_insulation" = "2.0";

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

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

== hyperspace_motor ==
If set to false / NO, it will stop ships from executing normal hyperspace jump (player ships will still be able to execute galactic jumps). Default = true / YES. (Planned for Oolite 1.75)

Examples:
"hyperspace_motor" = no;

hyperspace_motor=NO;

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

Examples:
"hyperspace_motor_spin_time" = "15";

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

Example:
"is_external_dependency" = yes;

==is_submunition==
Key added for missiles with multiple warheads. When this key is set and the entity is spawn or fired by a missile, it inherits its parent as owner. This key must be set so the player will be awarded for a kill by submunition.

Example:
"is_submunition" = yes;

==is_template==
Set this to yes/yes; for ships which are only used through like_ships and are not intended to be used directly. If your (otherwise working) OXP generates warnings about ships with no roles or model attribute, you probably need this.

Example:
"is_template" = yes;

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

As colour you can use a [[Materials in Oolite#Colour specifiers|colour specifier]] or a [[Materials in Oolite#Named colours|named colour]]. The game requires laser colours to be reasonably bright; if the brightest colour component is less than 0.5, the colour will be brightened.

Example:
"laser_color" = "cyanColor"

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

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

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

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

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

== likely_cargo ==
This is only used for ships with role asteroid and pirate. With asteroids it gives the likely number of boulders it breaks into. With pirates added by the [[System Populator]]: when lower than 16 it is the cargo, when higher than 15, it is changed in a random value between 0 and 15. This value is overridden by the actual scooped cargo if the pirate had scooped something.

Example:
"likely_cargo" = "2";

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

== max_cargo ==
Sets the ship's cargo limit. On explosion of trader ships added by the [[System Populator]], 10% of this value is used as likely cargo. When the result is lower than 16 it is the cargo, when higher than 15, it is changed in a random value between 0 and 15.

Example:
"max_cargo" = "5";

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

Example:
"max_energy" = "300";

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

Example:
"max_flight_pitch" = "2.2";

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

Example:
"max_flight_roll" = "4.2";

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

Example:
"max_flight_speed" = "320";

== max_flight_yaw ==
Sets yaw factor. Will usually range from a sluggish 0.6 to a very sensitive 3.0 When no value is defined it will use the same value as max_flight_pitch

Example:
"max_flight_yaw" = "2.2";

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

Example:
"max_missiles" = "1";

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

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

This position should lie outside the bounding box of the core entity and not just outside of the ships mesh. Default value: (0, -4, 1) 
If the position does lie inside the bounding box, the launch position is shifted along its direction until the launched missile lies outside the bounding box of the central entity. (Bounding boxes of subentities are ignored) The collision radius of the launched missile is taken into account. The collision radius for a plain missile is 4.52 meter.

== missile_load_time ==
Defines the time in seconds before a new missile is ready to fire after one is fired. Mainly useful for npc ships that have many missiles.

Example:
"missile_load_time" = "2.1";

== missiles ==
Sets the number of missiles the ship is equipped with on ship creation. e.g. you can set this at zero and than use a dedicated script to fill up the bay with specific missiles.

Example:
"missiles" = "0";

== missile_role ==
Defines the type of missiles (or mines) an NPC ship is provided with. Default is "EQ_MISSILE". When missiles are loaded on ship creation, 90% will be of this type and 10% will be random, chosen from all possible NPC missiles and mines. Also affects the javascript [[Oolite_JavaScript_Reference:_Ship#selectNewMissile|selectNewMissile()]] command.
The string defined inside missile_role needs both to be defined inside [[equipment.plist]], and be inside the '''roles''' property of the missile/mine shipdata entry.

To assign a specific missile type to a newly bought player ship, its dependancies must be defined inside [[shipyard.plist]].

Example:
"missile_role" = "EQ_THARGON";

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

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

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

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

== no_boulders ==
With older versions, scripted asteroids had no boulders by default. Starting with 1.70 all asteroids produce boulders when hit by a mining laser. no_boulders can overwrite this to emulate the old situation. By chance factor, or true/false.

Example:
"no_boulders" = yes;

== pilot ==
Gives the ship a predefined pilot, defined in [[characters.plist]]. Can eject in pod, if available, and be captured. 
By default every object starts with a pilot except buoys, missiles, cargo and rocks. By defining a specific pilot, any default pilot is replaced or a pilot is added to previously unpiloted objects.

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

When no pilot is defined, Oolite will create a random pilot based on the ships role. For custom roles this means that Oolite has no clue and the pilot might have other bounties/insurances than desired. For this reason contains Oolite, starting with v 1.75, some predefined pilots: "oolite-trader", "oolite-pirate", "oolite-hunter", "oolite-police", "oolite-miner", "oolite-passenger" and "oolite-slave". When using one of these pilots, a random bounty/insurance will be set appropriate for this pilot role. Pilot bounty is different as ship bounty but on ejecting the pilot inherits the highest of both values. (actually a bitwise OR of both values)

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

The game engine constantly calls for generic roles to populate the universe. In the example below the ship in question will be considered twice as often (2.0) when a trader is called for, only one quarter as often (0.25) when looking for a hunter, and as often as any other pirate ships when looking for a pirate.

'''NB:''' If the ship cannot be docked to, extra care should be taken to avoid using the words '''station''' or '''carrier''' as part of any of the ship's role names. When either of these words are inside the roles key, the ship is automatically given station attributes. Other ships might even fruitless try to dock with it, and it will affect how some ships / entities are shown on the scanner.

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

or an exclusive role, simply:

"roles" = "uniquely_named_role";

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

An item from the [[commodities]] can also be named as a role, for when that commodity is floating in space and called upon, to be represented by a particular model.

Example:
"roles" = "Gold";

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

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

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

An explaining example taken from the Oolite Bulletin board.

The rotational velocity key is rotation per second.

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

a = 360 ° / 20 = 18 °

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

sin a ˜ 0.30902

cos a ˜ 0.95106

Q = (0.95106, 0, 0, 0.30902)

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

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

==== Developer Note ====
Oolite uses scan_class internally to determine the behaviour of some ships (particularly with regard to who may shoot whom without incurring legal penalties). Bear this in mind and don't allocate CLASS_POLICE or CLASS_THARGOID to ships lightly!

Example:
"scan_class" = "CLASS_ROCK";

== scanner_range ==
Sets a custom scanner range. Standard is 25.6 km, thargoids have 50 km. Only applies to NPCs. However, at least since oolite 1.65 all defined scanner ranges are limited to 25.6 km, even for thargoids. This means it only makes sense defining shorter ranges than the maximum range.

Example:
"scanner_range" = "25600";

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

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

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

== script_info ==
A property list whose contents are available to JavaScript scripts, for whatever use they desire. It is exposed to JavaScript as the <code>[[Oolite JavaScript Reference: Ship#scriptInfo|scriptInfo]]</code> property of <code>Ship</code> objects. 
Take note that when using an ascii plist, the JS engine will read in all entries as strings. When you need an entry as number, you might need to explicit convert it to a number. This is specially true for booleans as a "NO" string will be read as true. For all normal keys its Oolite that does the conversion for you.

== script_actions ==
Gives an oportunity to insert events such as in [[script.plist]], to involve a specific shipdata entity. As seen in the following example, this particular object checks if Player has a cloaking device, and if not, will award it. Should Player already have it, the gift will be in gold. See also [[scripts within shipdata]] for more detailled info.

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

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

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

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

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

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

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

Example:
"smooth" = yes;

== spawn ==
The spawn directory is only used when a ship is added with the command: "spawnShip: shipname". This command only allows to add one ship by name (not role!). The position and orientation are taken from a spawn directory that describes the position it is placed and the position it is looking at.

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

== subentities ==
An array of ''subentity definitions''. A ''subentity'' is an object attached to your ship. There are several types of subentity:
* ''Static subentities'', the default type, are simply extra models. They are defined as separate shipdata.plist entries, so technically they’re ships, but they don’t have a mind of their own. If the main ship is [[#frangible|frangible]], static subentities can take damage and blow up separately from the main ship. They can also be individually exploded or removed by scripts.
* ''Docks'' are recognized when setting up a station or carrier, and used to determine the station’s docking port parameters. After set-up, they work just like normal static subentities. The string "dock" in lowercase must be part of the old style name in order to get recognised as the dock subEntity.
* 'Ball turrets'' turn to track the ship’s current target, and shoot plasma balls if the target is within range (6000 metres). A ball turret’s field of fire is a 157 ° cone centred on its original facing. Currently, ball turrets make no effort not to shoot their own ship, so it is up to the designer to ensure this field of fire is clear. Like a static subentity, a ball turret is based on a shipdata.plist entry so its appearance can be customized. Oolite provides a built-in shipdata entry for ball turrets called, imaginatively, '''ballturret'''.
* ''Flashers'' are blobs which glow with a pulsating light. From Oolite 1.74 onwards, constant light will also be an option. Note that while flashers appear luminous – they are unaffected by shadows – they do not cast light on other objects.

=== New-style subentity definition ===
Oolite 1.73 introduced a more flexible, dictionary-based way of specifying subentities. A new-style subentity is a dictionary using the following keys:
{| class="wikitable" border="1" cellpadding="3" cellspacing="0"
|+ Subentity definition properties
! Name !! Type !! Description
|-
| '''type''' || string || One of: “'''standard'''”, “'''ball_turret'''”, “'''flasher'''”. If not specified, “standard” is assumed.
|-
| '''subentity_key''' || string || The key of a ''shipdata.plist'' entry. Required for '''standard''' and '''ball_turret''' subentities, ignored for flashers.
|-
| '''position''' || vector || The position of the subentity relative to its parent. (This can be specified as a string with three numbers in it, or an array of three numbers, or a dictionary with '''x''', '''y''' and '''z''' entries.) Default: (0, 0, 0).
|-
| '''orientation''' || [[quaternion]] || The orientation of the subentity. Ignored for flashers. (This can be specified as a string with four numbers in it, or an array of four numbers, or a dictionary with '''w''', '''x''', '''y''' and '''z''' entries.) Default: (1, 0, 0, 0), which corresponds to no rotation.
|-
| '''is_dock''' || boolean || True if the subentity is a dock; false by default. Only applies to '''standard''' subentities. '''Note:''' this is ''not'' implied by having “dock” in the '''subentity_key''', as it is for old-style subentity definitions.
|-
| '''fire_rate''' || number || Interval between shots in seconds, for '''ball_turret''' subentities. Default: 0.5; minimum: 0.25.
|-
| '''color''' || [[Materials in Oolite#Colour specifiers|colour specifier]] || Single colour for a flasher. Ignored for non-flashers. Default value: '''redColor'''.
|-
| '''colors''' || array || Array of colour specifiers for a flasher. Ignored for non-flashers. Before 1.74, only the first entry was used. If not present, see '''color'''. '''Note:''' like [[#laser_color|laser_color]], flasher colours must be “reasonably bright”.
|-
| '''frequency''' || number || Pulse rate for flashers, in cycles per second. Ignored for non-flashers. If 0, the flasher will have full intensity all the time in Oolite 1.74 and later, but half intensity in earlier releases. Default: 2.
|-
| '''initially_on''' || boolean || Specifiers whether a flasher is turned on when created. Ignored for non-flashers. Default: yes.
|-
| '''phase''' || number || Pulse phase offset for flashers, in seconds. Ignored for non-flashers. (This value is simply added to the time to get the pulse parameter.) Default: 0.
|-
| '''size''' || positive number || Diameter of a flasher in metres. Ignored for non-flashers. Default: 8. (Why 8? I don’t remember.)
|-
|}

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

An old-style subentity definition is a string with eight items separated by spaces. In the description below, words in bold correspond to keys in [[#New-style subentity definition|new-style definitions]]. There are two variants:

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

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

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

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

'''initially_on''' is false.

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

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

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

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

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

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

Example:
"track_contacts" = yes;

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

Example:
"throw_sparks" = yes;

== thrust ==
Gives the entity an 'inertia' value, telling how fast it can increase or reduce speed (in m/s^2). 0 for rocks and cargo, 50 for a very fast ship, 100 for a station. When used with turrets it defines the turn rate in revolutions per second (with 1 being an average value).

Example:
"thrust" = "25"

== unpiloted ==
Used to designate items that will never have a pilot, thus never turn aggressive and never eject a pod. By chance factor, or true/false. 
It will not add a pilot when set to false, but will remove any existing pilot when set to true.
commsMessages can only be broadcasted by piloted ships. Ships are by default piloted. cargo , rocks, missiles etc. are not piloted by default.

Example:
"unpiloted" = yes;

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

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

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

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

Example:
"weapon_energy" = "180";

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

Default values are: WEAPON_PLASMA_CANNON = 6.0; WEAPON_PULSE_LASER = 15.0; WEAPON_BEAM_LASER = 15.0; WEAPON_MINING_LASER = 50.0; WEAPON_THARGOID_LASER = 12.5; WEAPON_MILITARY_LASER = 23.0

Example:
"weapon_energy" = "17";

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

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

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

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

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

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

Example:
allows_auto_docking = "no";

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

Example:
allows_fast_docking = "yes";

== defense_ship ==
Gives an oportunity to designate a particular ship by name that will defend a station/carrier. See also [[Shipdata.plist#defense_ship_role|defense_ship_role]]

Example:
defense_ship" = "my_defender";

== defense_ship_role ==
Gives an oportunity to designate a particular (group of) ships that will defend a station/carrier. This has to be specified in the [[Shipdata.plist#roles|roles]] of the ship(s) that are assigned to defend. When launched from a carrier the scan_class becomes that of the carrier. Default role is "police"/"interceptor" for normal stations and "hermit-ship" for stations of CLASS_ROCK. Defense ships with scanclass police or with a hermit-ship role launch with a policeInterceptAI.plist. All other ships use the ai_type as defined in shipdata.plist. After launch, all primary roles are changed into: "defense_ship"

Example:
"defense_ship_role" = " carrier_defenders";

== equipment_price_factor ==
Equipment price mask for dockables.

Example:
"equipment_price_factor" = "4.5";

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

Example:
"equivalent_tech_level" = 1;

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

Example:
"has_npc_traffic" = yes;

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

Example:
"has_patrol_ships" = yes;

== has_shipyard ==
Determines if a station or carrier has a shipyard. By chance factor as number between 0 and 1, but it can also be an array of conditions. Default is "no", but for main stations has_shipyard is always "yes". (Name is valid starting with Oolite 1.74. Before it was called "hasShipyard".)

Example:
"has_shipyard" = "0.75";

or

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

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

Example:
interstellar_undocking = "yes";

==is_carrier==
Added as a tag for making the model be considered a carrier or station. An alternative to including ''carrier'' or ''station'' among the [[Shipdata.plist#roles|roles]]. When present this key even overrules station/carrier settings with roles. (Name is valid starting with Oolite 1.74. Before it was called "isCarrier".)

Example:
"is_carrier" = yes;

== market ==
Key that sets the market for stations and carriers. The name defines the key in [[commodities.plist]] that will be used as local market. Without a market key, the stations primaryRole is used as market. Added with test release 1.74

Example:
"market" = "none";

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

Example:
"max_defense_ships" = "10";

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

Example:
"max_police " = "10";

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

Example:
"max_scavengers" = "10";

== port_dimensions ==
Defines the size of the docking port and takes 3 numbers, separated by "x". This key is generally of little use and can be skipped as it becomes overwritten by the actual size of the bounding box of the dock subentity when a correct dock subentity is defined.

Example:
"port_dimensions" = "65x30x500";

Size of Oolites main-station dock is: 64.00 x 192.00 x 250.00 while the dimension of a rock-hermit dock is: 138.001 x 138.001 x 250.12 (W x H x L) 
These sizes may be relevant for ship dimensions as since Oolite 1.75 ships must fit in these docks to be allowed docking or launching.

== port_radius ==
Defines the size of the docking port radius. Or more precise, this is the distance from the station centre to the port location. Default value is 500. This key is generally of little use and can be skipped as it will be overwritten by the real position of the dock subentity.

Example:
"port_radius" = "500";

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

Example:
"requires_docking_clearance" = yes;

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

Example:
"rotating" = yes;

== station_roll ==
Determines the rotation speed of a station. Default value is determined by the systemwide station_roll in planetInfo.plist. If that is not defined, the default is 0.4. Negative values are also possible for a rotation in the other direction. (Key is added in Oolite 1.74.2)

Example:
"station_roll" = "-1.5"

==tunnel_corners==
Defines the number of corners in the docking tunnel. Ranges from 4 to 128. Default is "4". (Key is added in Oolite 1.75)

Example:
"tunnel_corners" = 6;

==tunnel_start_angle==
Defines the position of the first corner of the docking tunnel in degrees. 0 means the first corner is straight up. Default is "45". (Key is added in Oolite 1.75)

Example:
"tunnel_start_angle" = 0;

==tunnel_aspect_ratio==
Defines the proportion of the tunnel’s width to its height. Default is "2.67". (Key is added in Oolite 1.75)

Example:
"tunnel_aspect_ratio" = 1;

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

Oolite JavaScript Reference: World script event handlers

2011-04-30T00:05:43Z

Kaks: /* viewDirectionChanged */

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

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

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

World scripts are always active.

=== Game State ===

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

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

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

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

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

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

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

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

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

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

=== Docking ===

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

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

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

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

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

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.docked == true", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

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

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect.

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.docked == false", "ship.status == STATUS_LAUNCHING".

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

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect.

this.shipLaunchedFromStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == null", "ship.docked == false", "ship.status == STATUS_IN_FLIGHT".

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

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

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

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

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

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

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

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

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

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

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

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

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED".

=== Witchspace Jumps ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Enter/Exit Aegis ===

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

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Combat ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==== <code>shipTargetDestroyed</code> ====

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

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

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

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

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

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

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

==== <code>shipTargetLost</code> ====

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

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

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

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

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

=== Equipment ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Other ===

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

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This handler works a bit different as other handlers. It fires for every installed oxp, until an oxp creates a mission screen during this handler. Than it stops. When the mission screen ends and there is no callback function that created a new mission screen, than the missionScreenOpportunity is send again to all installed oxps, starting with the oxp that used the mission screen as last one. All this means that when this handler fires, it is safe to show a mission screen and no further test are needed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==== <code>viewDirectionChanged</code> ====
{{Oolite-prop-added|1.75}} 
The <code>viewDirectionChanged</code> handler is called when the player view changes, with a string to indicate which view the player is facing. Amongst its possible values are "VIEW_FORWARD", "VIEW_AFT", "VIEW_PORT", "VIEW_STARBOARD",
"VIEW_CUSTOM",
"VIEW_GUI_DISPLAY".

this.viewDirectionChanged = function(viewString)
{
if (viewString == "VIEW_PORT")
{
// Your code here
}
}

=== Missing Events ===

All the initially planned events have been implemented in 1.74.

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

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

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: World script event handlers

2011-04-30T00:00:00Z

Kaks: /* Other */

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

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

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

World scripts are always active.

=== Game State ===

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

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

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

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

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

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

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

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

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

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

=== Docking ===

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

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

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

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

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

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.docked == true", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

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

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect.

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.docked == false", "ship.status == STATUS_LAUNCHING".

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

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect.

this.shipLaunchedFromStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == null", "ship.docked == false", "ship.status == STATUS_IN_FLIGHT".

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

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

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

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

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

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

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

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

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

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

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

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

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED".

=== Witchspace Jumps ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Enter/Exit Aegis ===

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

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Combat ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==== <code>shipTargetDestroyed</code> ====

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

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

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

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

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

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

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

==== <code>shipTargetLost</code> ====

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

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

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

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

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

=== Equipment ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Other ===

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

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This handler works a bit different as other handlers. It fires for every installed oxp, until an oxp creates a mission screen during this handler. Than it stops. When the mission screen ends and there is no callback function that created a new mission screen, than the missionScreenOpportunity is send again to all installed oxps, starting with the oxp that used the mission screen as last one. All this means that when this handler fires, it is safe to show a mission screen and no further test are needed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==== <code>viewDirectionChanged</code> ====
{{Oolite-prop-added|1.75}} 
The <code>viewDirectionChanged</code> handler is called when the player view changes, with a string to indicate which view the player is facing. Its possible values are "VIEW_FORWARD", "VIEW_AFT", "VIEW_PORT", "VIEW_STARBOARD",
"VIEW_CUSTOM",
"VIEW_GUI_DISPLAY".

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

=== Missing Events ===

All the initially planned events have been implemented in 1.74.

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

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

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Global

2010-10-28T22:29:50Z

Kaks: /* setScreenOverlay */

The '''<code>Global</code>''' environment includes all Oolite objects and methods accessible by all scripts at all times.

== Properties ==
=== <code>clock</code> ===
'''clock''' : Object(read-only)
This property allows an OXP to access the game clock's properties and methods.

=== <code>galaxyNumber</code> ===
'''galaxyNumber''' : Number(read-only)
Returns the number ot the galaxy the player is in.

=== <code>guiScreen</code> ===
'''guiScreen''' : String(read-only)
Returns the screen the player is looking at. If in flight, it's set to "GUI_SCREEN_MAIN".

=== <code>manifest</code> ===
'''manifest''' : Object(read-only)
This property allows an OXP to directly access the player ship's manifest properties.

=== <code>mission</code> ===
'''mission''' : Object(read-only)
This property allows an OXP to access misson methods.

=== <code>missionVariables</code> ===
'''missionVariables''' : Object(read-only)
The <code>missionVariables</code> object stores values that are stored in saved games. This is the main way for scripts to store information permanently.

Whenever a value is assigned to a property of <code>missionVariables</code>, it is converted to a string object and tracked with the player. When the value is read, it will be converted to a number if possible, otherwise returned as a string. Example:
missionVariables.exampleVar = 42;
let x = missionVariables.exampleVar; // x is now the number 42

Mission variables can also be used in legacy scripts and in [[descriptions.plist]] string expansions, by prefixing the name with “mission_”. Example:
expandDescription("My variable is [mission_exampleVar].")

Setting and retrieving mission variables has a small but non-trivial overhead. If a function needs to use a mission variable value several times, it is strongly recommended that it be copied into a local variable and, if necessary, stored back once. Example:
let x = missionVariables.exampleVar;
if (x < 3) x = processSmallValue(x);
else x = processBigValue(x);
missionVariables.exampleVar = x;

Mission variable names may not begin with an underscore (“_”). Unassigned mission variables are always <code>null</code>.

=== <code>oolite</code> ===
'''oolite''' : Object(read-only)
This property allows an OXP to access oolite's properties and methods.

=== <code>player</code> ===
'''player''' : Object(read-only)
This property allows an OXP to access the player object's properties and methods.

=== <code>system</code> ===
'''system''' : Object(read-only)
This property allows an OXP to access the current system's properties and methods.

=== <code>timeAccelerationFactor</code> ===
'''timeAccelerationFactor''' : Number(read/write)
Also known as TAF. Will change the ratio between game real time and actual real time (default is 1). The accepted range is between 0.0625 (1/16) and 16. Attempting to set numbers outside this range will reset the TAF to 1.

=== <code>worldScripts</code> ===
'''worldScripts''' : Object(read-only)
This property allows an OXP to access all world scripts, their properties and functions.

'''Example:'''
log(worldScripts['oolite-nova'].version);

== Methods ==
=== <code>displayNameForCommodity</code> ===
function '''displayNameForCommodity'''(commodityName : String)
Returns the display name corresponding to the specified commodity. Useful in conjunction with localisation OXPs, or expansions that rename commodities depending on which station / system the player is at.

=== <code>expandDescription</code> ===
function '''expandDescription'''(description : String [, locals : Object (Dictionary)]) : String
Expands a string, substituting special tokens and any key inside square brackets with the substitution rules for [[Methods#Communications|Communications]].
When local key/value pairs are provided, they take precedence over any other values. (buggy at the time of writing, fixed for 1.74.2 and later versions.)

'''Example:'''
expandDescription('My ball is [my_color].', { 'my_color': 'red' });

=== <code>expandMissionText</code> ===
function '''expandMissionText'''(textKey: String [, locals : Object (Dictionary)]) : String
Returns an expanded mission text, substituting any tokens and keys inside square brackets inside the original missiontext.plist value with its corresponding expanded string.
If local key/value pairs are provided, they take precedence over any other values. (buggy at the time of writing, fixed for 1.74.2 and later versions.)

'''Example:'''
expandMissionText('oolite_trumble_title');

=== <code>log</code> ===
function '''log'''([messageClass : String ,] message : String)
Writes a message to Oolite's log. The optional messageClass can be used to specify which type of message is written to the log.

'''Example:'''
log('myOXP.init','MyOXP initialised and ready!');

=== <code>randomInhabitantsDescription</code> ===
function '''randomInhabitantsDescription'''([plural : boolean])
Returns a random capitalised word, suitable to describe one sentient being, or - if using the optional plural argument - a group of sentients.

'''Example:'''
player.consoleMessage("You'll meet a " + randomInhabitantsDescription() +
". She'll be with a group of " + randomInhabitantsDescription(true) +'.');

=== <code>randomName</code> ===
function '''randomName'''()
Returns a random capitalised word, suitable for use as name, or indeed surname.

'''Example:'''
player.consoleMessage(randomName() + ' ' + randomName() +' rules this system with an iron fist.');

=== <code>setScreenBackground</code> ===
function '''setScreenBackground'''(image : String)
Temporary override that sets the background of the current gui screen to the specified image. Override is lost after the player switches screens.

'''Example:'''
setScreenBackground('oolite-nova-system.png');

=== <code>setScreenOverlay</code> ===
function '''setScreenOverlay'''(image : String)
Temporary override that sets the overlay of the current gui screen to the specified image. Override is lost after the player switches screens.

'''Example:'''
setScreenOverlay('trumblebox.png');

[[Category:Oolite JavaScript Reference]]

Shipdata.plist

2010-09-12T06:56:55Z

Kaks: /* hyperspace_motor_spin_time */

'''shipdata.[[plist]]''' will provide Oolite with all the definitions necessary to include it as an entity in the game, be it ship, station, freak object or sub-entity [[shipdata_structure|(extra)]]. The following (property) entries are, for order's sake, listed alphabetically:

==accuracy==
Used with missiles it has influence on tracking of target. Allowed values with missiles are between 0.0 and 10.0. When not defined, the system assings to the missile the accuracy value of 0.0, which corresponds to the standard missile tracking behaviour.

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

Example:
<key>accuracy</key>
<integer>8</integer>

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

Example:
<key>aft_eject_position</key>
<string>0.0 -4.5 -23.0</string>
== aft_weapon_type ==
Assigns the ship's laser.
Any weapon type from the [[equipment.plist]] can be used (and WEAPON_NONE).

Example:
<key>aft_weapon_type</key>
<string>WEAPON_BEAM_LASER</string>

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

Example:
<key>ai_type</key>
<string>pirateAI.plist</string>

== auto_ai ==
Introduced in version 1.69 to autoswitch ai to the appropriate one if a ship was added by a script in one of its standard roles like trader or pirate. See also the comment inside the autoAIMap.plist inside Oolite 1.69 or newer. When not defined it will be true by default. Defining auto_ai is only necessary when using one of the standard roles mentioned in the autoAIMap.plist for your ship.
Example:
<key>auto_ai</key>
<true/>
Starting with Oolite 1.73 also the populator will look at the auto_ai during system setup. When auto_ai is false the ship will keep the ai_type defined for the ship and not give it the default ai for that role.

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

Example:
<key>beacon</key>
<string>X-code</string>

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

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

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

H = Homing Beacon (ett Homing Beacon)

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

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

Starting with Oolite 1.73 we can also use custom icons with the compass. For that you must define a key in descriptions.plist with the same name as one of the roles of the ship with beacon. Than define the icon in the same way as missile icons. (An array of x/y-coordinates that will be connected by lines)
"fuelStation_location" = (1, 2, -3, 2, -3, -4, 3, -4, 3, 4, -3, 4, -3, 3, 2, 3, 2, -3, 1, -3 );

== bounty ==
Sets a Cr. reward on the NPC's head, and is bound to give it trouble with the law . This bounty setting is overruled when adding ships in one of the populator roles like pirate, trader etc. Pirates are default added with a small bounty and traders are added clean. However, like the player, also the npc bounty can raise when attacking other clean ships or police vessels.

Example:
<key>bounty</key>
<integer>50</integer>

== cargo_carried ==
Determines the type of cargo carried as described in [[commodities]] and [[commodities.plist]]. Only one type can be specified. This key can be used for both ships and barrels.

Example:
<key>cargo_carried</key>
<string>Gold</string>

When used for barrels, it is also possible to add several units in a pod by preceding the commodity name with a space separated number. Adding more than a ton in a pod is not possible. Defining a quantity for ships is not possible this way. 
Since Oolite 1.74 it will also be possible to define a mix of random cargo for ships by using the string "SCARCE_GOODS" or "PLENTIFUL_GOODS", instead of a commodity name. The first selects random goods that are scarce at the main station, the second selects goods that are plentiful present at the main station. (Populator added traders heading toward the station always have scarce goods while traders heading from the main station always have plentiful goods on board. It would be wise to stick to this rule with custom ships.) 
To make cargo_carried working for ships, the cargo_type must be "CARGO_NOT_CARGO" to define the ship not being cargo itself. (see below)

== [[cargo_type]] ==
Determines if object is indeed cargo (CARGO_RANDOM, CARGO_SLAVES, CARGO_THARGOID, CARGO_ALLOY, CARGO_MINERALS, CARGO_CARRIED) or a ship, as below, which is not cargo. Works since Oolite 1.71 also for pods spawn by a script. CARGO_CARRIED needs in addition an second key cargo_carried that specifies the cargo. (see below) 

Example:
<key>cargo_type</key>
<string>CARGO_RANDOM</string>

In v1.63, more control of contents of barrels will be available through the CARGO_CARRIED string.

Example:
<key>cargo_type</key>
<string>CARGO_CARRIED</string>
<key>cargo_carried</key>
<string>4 Gold</string>

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

Example:
<key>cargo_type</key>
<string>CARGO_NOT_CARGO</string>
<key>cargo_carried</key>
<string>Computers</string>

Another notable type of cargo is the scripted item CARGO_SCRIPTED_ITEM, as examplified by the cloacking device. When CARGO_SCRIPTED_ITEM is defined, the barrels will trigger scooping events for the ship-scripts. Other barrels don't trigger scooping events. 
Until 1.74 such scripted barrels were removed from the system after scooping. Starting with 1.74 the barrels are stored in the ships hold like normal barrels when a cargo was defined for them with the JS method "setCargo". Scripted cargo works with any object that can be scooped. When you have scripted escape pods that must be preserved, fill it with one ton of Slaves.

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

Example:
<key>cloak_passive</key>
<true/>

==conditions==
Whit this option you can include an array of extra conditions when to add a ship. When the conditions are not met, the ship does not appear in a selection list by role. Useful when you have a standard ship like a trader that should only be added in certain systems.

Example:
<key>conditions</key>
<array>
<string>systemGovernment_number equal 3</string>
<string>systemEconomy_number lessthan 4</string>
</array>

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

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

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

For the view_orientation you will probably need a calculator but the basic method is to choose a unit vector (x y z) as the axis for a rotation then calculate the four values W X Y and Z for the quaternion as follows:

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

Four decimal places are probably enough accuracy for these values.

Example:
<key>custom_views</key>
<array>
<dict>
<key>view_description</key>
<string>External View - Aft</string>
<key>view_position</key>
<string>0.0 100.0 -173.21</string>
<key>view_orientation</key>
<string>0.966 -0.259 0.0 0.0</string>
<key>weapon_facing</key>
<string>FORWARD</string>
</dict>
<dict>
<key>view_description</key>
<string>Scoop camera</string>
<key>view_position</key>
<string>0.0 -38.3333 1.6666</string>
<key>view_orientation</key>
<string>1.0 0.0 0.0 0.0</string>
<key>weapon_facing</key>
<string>FORWARD</string>
</dict>
</array>

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

Example:
<key>death_actions</key>
<array>
<string>spawn: explosive_shrapnel 1</string>
</array>

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

Example:
<key>debris_role</key>
<string>
<string>my_boulder_foo</string>
</string>

== defense_ship ==
Gives an oportunity to designate a particular ship by name that will defend a station/carrier. When launched from a carrier the scanclass becomes that of the carrier.

Example:
<key>defense_ship</key>
<string>my_defender</string>

== defense_ship_role ==
Gives an oportunity to designate a particular (group of) ships that will defend a station/carrier. This has to be specified in the [[Shipdata.plist#roles|roles]] of the ship(s) that are assigned to defend. When launched from a carrier the scanclass becomes that of the carrier.

Example:
<key>defense_ship_role</key>
<string>carrier_defenders</string>

== density ==
This real value is used to calculate a ships total mass. Default is 1.0 (Introduced in version 1.69?)

Example:
<key>density</key>
<real>1.5</real>

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

Example:
<key>display_name</key>
<string>ExampleShip Mark IX</string>

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

Example:
<key>docking_pattern_model</key>
<string>ring.dat</string>

== energy_recharge_rate ==
The rate at which energy is replenished. Stations are at 100, Adders at 2.

Example:
<key>energy_recharge_rate</key>
<real>3.5</real>

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

Example:
<key>escape_pod_model</key>
<string>custom_pod</string>

== escorts ==
Determines how many escorts an NPC shall have. Maximum is 16. In save systems Oolite may randomly decide to subtract escorts from the defined value.

Example:
<key>escorts</key>
<integer>4</integer>
Warning: Ships with scanClass = CLASS_POLICE should always have escorts set to zero. Oolite will set this value here and add wingmans instead of escorts. Without special scripting escorts won't escort a mother with CLASS_POLICE.

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

Example:
<key>escort-role</key>
<string>my_custom_escort_role</string>
Warning: Only usable since Oolite 1.71. It will use the AI file defined in shipdata for this escort and will not use any default escortAI. So make sure the summoned escort has an AI defined in its entry that is capable of supporting escorting.

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

Example:
<key>escort-ship</key>
<string>cobramk1</string>

== equipment_price_factor ==
Equipment price mask for dockables.

Example:
<key>equipment_price_factor</key>
<real>4.5</real>

== equivalent_tech_level ==
Sets shipyard tech level for dockables, different to the local system techlevel.

Example:
<key>equivalent_tech_level</key>
<integer>1</integer>

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

x y z width height length

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

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

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

'''length''' in meters, how long a plume is on z axis. (This value is in current Oolite versions ignored. Length is now derived from the ships speed)

Below are 2 assigned plumes at coords 5, 0, -25 and -5, 0, -25, and each plume is 6 m wide and 4 m tall. (length info is ignored)

Example:
<key>exhaust</key>
<array>
<string>5 0.0 -25 6.0 4.0 10.0</string>
<string>-5 0.0 -25 6.0 4.0 10.0</string>
</array>

== extra_cargo ==
New in version 1.62rc3
Cargobay extension size can now be customised. This is the amount the cargo capacity increases when an extra cargobay is installed. Default value is 15. It is only used with player ships.

Example:
<key>extra_cargo</key>
<integer>value</integer>

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

Example:
<key>forward_weapon_type</key>
<string>WEAPON_BEAM_LASER</string>

== frangible ==
Determines if eventual sub-entities are "loose". By default any given object is already frangible, so the use of this line must be to negate that.
If set to false, the object plus subentities will be regarded as a single object.
If set to true, sub entities can be destroyed seperately from the main object.

Example:
<key>frangible</key>
<false/>
== fragment_chance ==
Determines if a ship breaks apart into fragments and generates parts with role "wreckage". By chance factor, or true/false. Default is 90% chance.
The amount of wreckage is based on the ships mass with a maximum of 3. Wreckage is scaled to match the ships size but is very short living. (0.25s -> 1.25s)

Example:
<key>fragment_chance</key>
<false/>

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

Example:
<key>fuel</key>
<integer>70</integer>

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

Example:
<key>has_cloaking_device</key>
<real>0.5</real>

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

Example:
<key>has_ecm</key>
<real>0.5</real>
or
<key>has_ecm</key>
<false/>

== has_energy_bomb ==
Determines if a ship has an energy bomb. If it has one, it might launch a mine with role "energy_bomb" as part of his fleeing behavior. currently the only build-in mine with this role is the q-bomb. (Since Oolite 1.73 there is a check to only deploy the bomb when having also fuel-injectors and some fuel left to avoid getting killed by its own bomb)

Example:
<key>has_energy_bomb</key>
<false/>

== has_escape_pod ==
Determines if a ship has an escape pod. Can be either a boolean value, or a number from 0 to 1 expressing the likelihood of the equipment being present. Starting with version 1.65 ships can have multiple escape pods. To specify more than one escape pod, '''has_escape_pod''' must be set to a numeric value corresponding to the escape pods present on board.

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

XML example:
<key>has_escape_pod</key>
<false/>

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

Example:
<key>has_fuel_injection</key>
<real>0.99</real>
==has_military_jammer==
Determines if a ship has a military jammer. Ships equipped with this item become invisible on the radar.
Example:
<key>has_military_jammer</key>
<real>0.75</real>

==has_military_scanner_filter==
Determines if a ship has a military jammer filter. Ships equipped with this item can see ships equipped with a military jammer on the radar.
Example:
<key>has_military_scanner_filter</key>
<real>0.50</real>

== has_npc_traffic ==
Determines if a station has NPC traffic (carriers are treated as stations, too). Default is "YES", when set to NO the station will not launch random traders. Introduced in version 1.70

Example:
<key>has_npc_traffic</key>
<true/>

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

Example:
<key>has_scoop</key>
<false/>

== has_scoop_message ==
A key for cargo. Determines if a barrel generates a default scoop message when scooped. Default is true, but setting it to false suppresses any messages, so a scripts can generate its custom messages on scooping. (Added with Oolite 1.74)

Example:
<key>has_scoop_message</key>
<false/>

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

Example:
<key>has_shield_booster</key>
<real>0.80</real>
== has_shield_enhancer ==
Determines if a ship has the coveted shield enhancer. (enlarges max energy with 256 and raises energy recharge rate with 50%)

Example:
<key>has_shield_enhancer</key>
<real>0.45</real>

== has_shipyard ==
Determines if a station or carrier has a shipyard. By chance factor as number between 0 and 1, but it can also be an array of conditions. (Name is valid starting with Oolite 1.74. Before it was called "hasShipyard".)

Example:
<key>has_shipyard</key>
<real>0.75<real/>

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

Example:
<key>heat_insulation</key>
<real>2.0</real>

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

Example:
<key>hud</key>
<string>specialhud.plist</string>

== hyperspace_motor ==
If set to false / NO, it will stop ships from executing normal hyperspace jump (player ships will still be able to execute galactic jumps). Default = true / YES. (Planned for Oolite 1.75)

Examples:
<key>hyperspace_motor</key>
<false/>

hyperspace_motor=NO;

== hyperspace_motor_spin_time ==
Used to modify jump countdown time. Default = 15. (Added with Oolite 1.72)

Examples:
<key>hyperspace_motor_spin_time</key>
<integer>15</integer>

hyperspace_motor_spin_time=15;

==is_carrier==
Added as a tag for making the model be considered a carrier or station. An alternative to including ''carrier'' or ''station'' among the [[Shipdata.plist#roles|roles]]. When present this key even overrules station/carrier settings with roles. (Name is valid starting with Oolite 1.74. Before it was called "isCarrier".)

Example:
<key>is_carrier</key>
<true/>

==is_submunition==
Key added for missiles with multiple warheads. When this key is set and the entity is spawn or fired by a missile, it inherits its parent as owner. This key must be set so the player will be awarded for a kill by submunition. (Key added in Oolite 1.72)

Example:
<key>is_submunition</key>
<true/>

==is_template==
Set this to yes/<true/> for ships which are only used through like_ships and are not intended to be used directly. If your (otherwise working) OXP generates warnings about ships with no roles or model attribute, you probably need this. (Key added in Oolite 1.72)

Example:
<key>is_template</key>
<true/>

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

In Oolite 1.69 and later, this is any [[Materials in Oolite#Colour specifiers|colour specifier]]. In earlier versions, it must be a [[Materials in Oolite#Named colours|named colour]]. Also as of 1.69, the game requires laser colours to be reasonably bright; if the brightest colour component is less than 0.5, the colour will be brightened.

Example:
<key>laser_color</key>
<string>cyanColor</string>

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

Example:
"role = trader"
<key>launch_actions</key>
<array>
<string>setAITo: pirateAI.plist</string>
</array>

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

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

Example:
<key>like_ship</key>
<string>adder</string>
<key>max_flight_speed</key>
<real>700</real>
<key>name</key>
<string>Freak Turbo Adder</string>

== likely_cargo ==
This is only used for ships with role asteroid and pirate. With asteroids it gives the likely number of boulders it breaks into. With pirates added by the [[System Populator]]: when lower than 16 it is the cargo, when higher than 15, it is changed in a random value between 0 and 15. This value is overridden by the actual scooped cargo if the pirate had scooped something.

Example:
<key>likely_cargo</key>
<integer>2</integer>

== market ==
Key that sets the market for stations and carriers. The name defines the key in [[commodities.plist]] that will be used as local market. Without a market key, the stations primaryRole is used as market. Added with test release 1.74

Example:
<key>market</key>
<string>none</string>

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

== max_cargo ==
Sets the ship's cargo limit. On explosion of trader ships added by the [[System Populator]], 10% of this value is used as likely cargo. When the result is lower than 16 it is the cargo, when higher than 15, it is changed in a random value between 0 and 15.

Example:
<key>max_cargo</key>
<integer>5</integer>

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

Example:
<key>max_defense_ships</key>
<integer>10</integer>

== max_energy ==
Sets the ship's energy value.

Example:
<key>max_energy</key>
<real>300</real>

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

Example:
<key>max_flight_pitch</key>
<real>2.2</real>

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

Example:
<key>max_flight_roll</key>
<real>4.2000000000000002</real>

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

Example:
<key>max_flight_speed</key>
<real>320</real>

== max_flight_yaw ==
Sets yaw factor. Will usually range from a sluggish 0.6 to a very sensitive 3.0 When no value is defined it will use the same value as max_flight_pitch

Example:
<key>max_flight_yaw</key>
<real>2.2</real>

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

Example:
<key>max_missiles</key>
<integer>1</integer>
== max_police ==
Designates how many police or patrol ships a dockable entity (station, carrier) can launch. See also [[Station Ships]]

Example:
<key>max_police </key>
<integer>10</integer>

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

Example:
<key>max_scavengers</key>
<integer>10</integer>

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

Example:
<key>missile_launch_position</key>
<string>0.0 -2.25 10.0</string>

== missile_load_time ==
Defines the time in seconds before a new missile is ready to fire after one is fired. Mainly useful for npc ships that have many missiles. Added with test release 1.74

Example:
<key>missile_load_time</key>
<string>2.1</string>

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

Example:
<key>missiles</key>
<integer>0</integer>

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

Example:
<key>missile_role</key>
<string>thargon</string>

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

Example:
<key>model</key>
<string>example_ship.dat</string>

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

Example:
<key>name</key>
<string>ExampleShip Mark IX</string>

== no_boulders ==
With older versions, scripted asteroids had no boulders by default. Starting with 1.70 all asteroids produce boulders when hit by a mining laser. no_boulders can overwrite this to emulate the old situation. By chance factor, or true/false.

Example:
<key>no_boulders</key>
<true/>

== pilot ==
Gives the ship a predefined pilot, defined in characters.plist.
Can eject in pod, if available, and be captured.

Example:
<key>pilot</key>
<string>constrictor-mission-thief</string>


== port_dimensions ==
Defines the size of the docking port and takes 3 numbers. This key is generally of little use and can be skipped as it becomes overwritten by the size of the bounding box of the dock subentity.

Example:
<key>port_dimensions</key>
<string>65 30 500</string>

== port_radius ==
Defines the size of the docking port radius. Or more precise, this is the distance from the station centre to the port location. Default value is 500. This key is generally of little use and can be skipped as it will be overwritten by the real position of the dock subentity.

Example:
<key>port_radius</key>
<string>500</string>

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

Example:
<key>requires_docking_clearance</key>
</true>

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

The game engine constantly calls for generic roles to populate the universe. In the example below the ship in question will be considered twice as often (2.0) when a trader is called for, only one quarter as often (0.25) when looking for a hunter, and as often as any other pirate ships when looking for a pirate.

'''NB:''' If the ship cannot be docked to, extra care should be taken to avoid using the words '''station''' or '''carrier''' as part of any of the ship's role names. When either of these words are inside the roles key, the ship is automatically given station attributes. Other ships might even fruitless try to dock with it, and it will affect how some ships / entities are shown on the scanner.

Example:
<key>roles</key>
<string>hunter(0.25) trader(2.0) pirate</string>

or an exclusive role, simply:

<key>roles</key>
<string>uniquely_named_role</string>

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

An item from the [[commodities]] can also be named as a role, for when that commodity is floating in space and called upon, to be represented by a particular model.

Example:
<key>roles</key>
<string>Gold</string>

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

==rotating==
Given to a station when rotation is desired.

Example:
<key>rotating</key>
<true/>

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

Example:
<key>rotational_velocity</key>
<string>0.707 0.0 0.0 0.707</string>

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

==== Developer Note ====
Oolite uses scan_class internally to determine the behaviour of some ships (particularly with regard to who may shoot whom without incurring legal penalties). Bear this in mind and don't allocate CLASS_POLICE or CLASS_THARGOID to ships lightly!

Example:
<key>scan_class</key>
<string>CLASS_ROCK</string>

== scanner_range ==
Sets a custom scanner range. Standard is 25.6 km, thargoids have 50 km. Only applies to NPCs. However, at least since oolite 1.65 all defined scanner ranges are limited to 25.6 km, even for thargoids. This means it only makes sense defining shorter ranges than the maximum range.

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

Example:
<key>scoop_position</key>
<string>0.0 -4.5 -23.0</string>

== script ==
Specifies a [[Scripting Oolite with JavaScript|JavaScript script]] to attach to the ship. Ship scripts were introduced with Oolite test release 1.70, and are the preferred approach to scripting ships in new versions of Oolite.

== script_info ==
A property list whose contents are available to JavaScript scripts, for whatever use they desire. It is exposed to JavaScript as the <code>[[Oolite JavaScript Reference: Ship#scriptInfo|scriptInfo]]</code> property of <code>Ship</code> objects. 
Take note that when using an ascii plist, the JS engine will read in all entries as strings. When you need an entry as number, you might need to explicit convert it to a number. This is specially true for booleans as a "NO" string will be read as true. For all normal keys its Oolite that does the conversion for you.

== script_actions ==
Gives an oportunity to insert events such as in [[script.plist]], to involve a specific shipdata entity. As seen in the following example, this particular object checks if Player has a cloaking device, and if not, will award it. Should Player already have it, the gift will be in gold. See also [[scripts within shipdata]] for more detailled info.

Example:
<key>script_actions</key>
<array>
<string>debugOn</string>
<string>testForEquipment: EQ_CLOAKING_DEVICE</string>
<dict>
<key>conditions</key>
<array>
<string>foundEquipment_bool equal NO</string>
</array>
<key>do</key>
<array>
<string>awardEquipment: EQ_CLOAKING_DEVICE</string>
</array>
<key>else</key>
<array>
<string>awardCargo: 100 Gold</string>
</array>
</dict>
<string>debugOff</string>
</array>

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

Example:
<key>setup_actions</key>
<array>
<string>initialiseTurret</string>
</array>

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

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

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

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

Example:
<key>smooth</key>
<true/>

== spawn ==
The spawn directory is only used when a ship is added with the command: "spawnShip: shipname". This command only allows to add one ship by name (not role!). The position and orientation are taken from a spawn directory that describes the position it is placed and the position it is looking at.

Example
<key>spawn</key>
<dict>
<key>facing_position</key>
<string>spu 0 0 0</string>
<key>position</key>
<string>wpu 0 0 0.2</string>
</dict>

== station_roll ==
Determines the rotation speed of a station. Default value is determined by the systemwide station_roll in planetInfo.plist. If that is not defined, the default is 0.4. Negative values are also possible for a rotation in the other direction. (Key is added in Oolite 1.74.2)

Example:
<key>station_roll </key>
<string>-1.5</string>

== subentities ==
An array of ''subentity definitions''. A ''subentity'' is an object attached to your ship. There are several types of subentity:
* ''Static subentities'', the default type, are simply extra models. They are defined as separate shipdata.plist entries, so technically they’re ships, but they don’t have a mind of their own. If the main ship is [[#frangible|frangible]], static subentities can take damage and blow up separately from the main ship. They can also be individually exploded or removed by scripts.
* ''Docks'' are recognized when setting up a station or carrier, and used to determine the station’s docking port parameters. After set-up, they work just like normal static subentities. The string "dock" in lowercase must be part of the old style name in order to get recognised as the dock subEntity.
* 'Ball turrets'' turn to track the ship’s current target, and shoot plasma balls if the target is within range (6000 metres). A ball turret’s field of fire is a 157 ° cone centred on its original facing. Currently, ball turrets make no effort not to shoot their own ship, so it is up to the designer to ensure this field of fire is clear. Like a static subentity, a ball turret is based on a shipdata.plist entry so its appearance can be customized. Oolite 1.72 or later provides a built-in shipdata entry for ball turrets called, imaginatively, '''ballturret'''.
* ''Flashers'' are blobs which glow with a pulsating light. From Oolite 1.74 onwards, constant light will also be an option. Note that while flashers appear luminous – they are unaffected by shadows – they do not cast light on other objects.

=== New-style subentity definition ===
Oolite 1.73 introduced a more flexible, dictionary-based way of specifying subentities. A new-style subentity is a dictionary using the following keys:
{| class="wikitable" border="1" cellpadding="3" cellspacing="0"
|+ Subentity definition properties
! Name !! Type !! Description
|-
| '''type''' || string || One of: “'''standard'''”, “'''ball_turret'''”, “'''flasher'''”. If not specified, “standard” is assumed.
|-
| '''subentity_key''' || string || The key of a ''shipdata.plist'' entry. Required for '''standard''' and '''ball_turret''' subentities, ignored for flashers.
|-
| '''position''' || vector || The position of the subentity relative to its parent. (This can be specified as a string with three numbers in it, or an array of three numbers, or a dictionary with '''x''', '''y''' and '''z''' entries.) Default: (0, 0, 0).
|-
| '''orientation''' || [[quaternion]] || The orientation of the subentity. Ignored for flashers. (This can be specified as a string with four numbers in it, or an array of four numbers, or a dictionary with '''w''', '''x''', '''y''' and '''z''' entries.) Default: (1, 0, 0, 0), which corresponds to no rotation.
|-
| '''is_dock''' || boolean || True if the subentity is a dock; false by default. Only applies to '''standard''' subentities. '''Note:''' this is ''not'' implied by having “dock” in the '''subentity_key''', as it is for old-style subentity definitions.
|-
| '''fire_rate''' || number || Interval between shots in seconds, for '''ball_turret''' subentities. Default: 0.5; minimum: 0.25.
|-
| '''color''' || [[Materials in Oolite#Colour specifiers|colour specifier]] || Single colour for a flasher. Ignored for non-flashers. Default value: '''redColor'''.
|-
| '''colors''' || array || Array of colour specifiers for a flasher. Ignored for non-flashers. Before 1.74, only the first entry was used. If not present, see '''color'''. '''Note:''' like [[#laser_color|laser_color]], flasher colours must be “reasonably bright”.
|-
| '''frequency''' || number || Pulse rate for flashers, in cycles per second. Ignored for non-flashers. If 0, the flasher will have full intensity all the time in Oolite 1.74 and later, but half intensity in earlier releases. Default: 2.
|-
| '''initially_on''' || boolean || Specifiers whether a flasher is turned on when created. Ignored for non-flashers. Default: yes.
|-
| '''phase''' || number || Pulse phase offset for flashers, in seconds. Ignored for non-flashers. (This value is simply added to the time to get the pulse parameter.) Default: 0.
|-
| '''size''' || positive number || Diameter of a flasher in metres. Ignored for non-flashers. Default: 8. (Why 8? I don’t remember.)
|-
|}

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

An old-style subentity definition is a string with eight items separated by spaces. In the description below, words in bold correspond to keys in [[#New-style subentity definition|new-style definitions]]. There are two variants:

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

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

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

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

'''initially_on''' is false.

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

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

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

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

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

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

Example:
<key>track_contacts</key>
<true/>

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

Example:
<key>throw_sparks</key>
<true/>

== thrust ==
Gives the entity an 'inertia' value, telling how fast it can increase or reduce speed (in m/s^2). 0 for rocks and cargo, 50 for a very fast ship, 100 for a station. When used with turrets it defines the turn rate in revolutions per second (with 1 being an average value).

Example:
<key>thrust</key>
<real>25</real>

== unpiloted ==
Used to designate items that will never have a pilot, thus never turn aggressive and never eject a pod. By chance factor, or true/false. 
It will not add a pilot when set to false, but will remove any existing pilot when set to true.
commsMessages can only be broadcasted by piloted ships. Ships are by default piloted. cargo , rocks, missiles etc. are not piloted by default.

Example:
<key>unpiloted</key>
<true/>

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

Example:
<key>view_position_aft</key>
<string>0.0 5.0 -20.0</string>
<key>view_position_forward</key>
<string>0.0 1.9375 5.0</string>
<key>view_position_port</key>
<string>-11.85 2.825 -3.5</string>
<key>view_position_starboard</key>
<string>11.85 2.825 -3.5</string>

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

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

Example:
<key>weapon_energy</key>
<real>180</real>

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

Default values are: WEAPON_PLASMA_CANNON = 6.0; WEAPON_PULSE_LASER = 15.0; WEAPON_BEAM_LASER = 15.0; WEAPON_MINING_LASER = 50.0; WEAPON_THARGOID_LASER = 12.5; WEAPON_MILITARY_LASER = 23.0

Example:
<key>weapon_energy</key>
<real>17</real>

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

== weapon_offset ==
Used to change the offsetpoint of a plasma cannon. Removed after version 1.65

Example:
<key>weapon_offset_x</key>
<real>10</real>

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

Example:
<key>weapon_position_aft</key>
<string>0.0 -5.0 -20.0</string>
<key>weapon_position_forward</key>
<string>0.0 0.0417 16.6667</string>
<key>weapon_position_port</key>
<string>-13.75 -2.0625 -1.875</string>
<key>weapon_position_starboard</key>
<string>13.75 -2.0625 -1.875</string>

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

Oolite JavaScript Reference: SystemInfo

2010-07-26T01:06:03Z

Kaks: /* Special Witchspace Location */

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

{{Oolite-class-added|1.74}}

'''<code>SystemInfo</code>''' objects provide information about a specific system.

== Properties ==
=== <code>coordinates</code> ===
'''coordinates''' : {{oojsclass|Vector3D}} (read-only)
The coordinates of the system in light years. e.g. for Lave: <code>(8, 34.6, 0)</code>. The z component is always zero.

The upper left corner has the coordinate <code>(0, 0, 0)</code>. Going right increases the x value while going down on the map increases the y value.

'''Example:'''
System.infoForSystem(galaxyNumber, 7).coordinates
returns the coordinates of the system with an ID number of 7 in the current galaxy. In the first galaxy that would be the coordinates for Lave: <code>(8, 34.6, 0)</code>.

=== <code>galaxyID</code> ===
'''galaxyID''' : Number (read-only nonnegative integer)
The ID number of the galaxy.

=== <code>systemID</code> ===
'''systemID''' : Number (read-only nonnegative integer)
The ID number of the system.

== More properties ==
In addition to the properties above, you can access many other system properties, using the same keys as [[planetinfo.plist]].

'''Example:'''
<code>System.info.description = "This is a dull planet."</code>
sets the description of the current planet to “This is a dull planet.”

Properties that are changed in <code>system.info</code> are stored in the save file and are permanently changed for that commander. When both the planetInfo.plist and the data from a changed <code>system.info</code> file are present, those of the system.info are used. You can undo any changes in <code>system.info</code> by setting the value to <code>null</code>.

== Methods ==
=== <code>distanceToSystem</code> ===
function '''distanceToSystem'''(system : SystemInfo) : Number
Returns the distance in light years to another <code>SystemInfo</code>.

'''Example:'''
System.infoForSystem(galaxyNumber, 7).distanceToSystem(System.infoForSystem(galaxyNumber, 8))
If galaxyNumber is 0, this returns 92.8.

=== <code>routeToSystem</code> ===
function '''routeToSystem'''(system : SystemInfo [, "OPTIMIZED_BY_JUMPS" | "OPTIMIZED_BY_TIME"] ) : Object
Returns a dictionary containing the route information to another <code>SystemInfo</code>. The dictionary contains the array of system IDs that belong to the <code>route</code> found, the <code>distance</code> and the <code>time</code> corresponding to said route. Takes the optional parameter <code>"OPTIMIZED_BY_JUMPS"</code> (default) or <code>"OPTIMIZED_BY_TIME"</code> to calculate least number of jumps or fastest transit time routes respectively.

'''Example:'''
var myRoute = System.infoForSystem(galaxyNumber, 7).routeToSystem(System.infoForSystem(galaxyNumber, 8))
myRoute.route
myRoute.distance
myRoute.time
returns:
7,129,227,73,89,222,29,42,131,62,150,36,28,16,185,86,138,51,8 (the route)
96.40 (distance of added jumps)
530.40 (travelled time)

=== <code>systemsInRange</code> ===
{{Oolite-method-added|1.74.2}}
function '''systemsInRange'''([range : Number]) : Array
Returns an array of <code>SystemInfo</code>s in range (default: 7) from the given system.

'''Note:''' will not produce correct results if used in interstellar space.

'''See also:''' <code>SystemInfo.[[#systemsInRange_2|systemsInRange()]]</code> (which always provides results relative to the current system).

== Static methods ==
=== <code>filteredSystems</code> ===
function '''filteredSystems'''(this : Object, predicate : Function) : Array of SystemInfo
A list of the <code>SystemInfo</code>s for which <code>predicate</code> returns <code>true</code>.

'''Example:'''
// This is the actual implementation of <code>[[#systemsInRange_2|systemsInRange()]]</code> in Oolite 1.74.
SystemInfo.systemsInRange = function(range)
{
if (range === undefined)
{
range = 7;
}

var thisSystem = system.info;
return SystemInfo.filteredSystems(this, function(other)
{
return (other.systemID !== thisSystem.systemID) && (thisSystem.distanceToSystem(other) <= range);
});
}

=== <code>systemsInRange</code> ===
function '''systemsInRange'''([range : Number]) : Array
Returns an array of <code>SystemInfo</code>s in range (default: 7) from the current system.

'''Note:''' As of 1.74.2, this method works correctly for all systemInfos in the current galaxy, and for the current witchspace location. Trying to use it for other galaxies - or for a non-current witchspace location - will produce an error.

'''Example:'''
system.info.systemsInRange(5);

== Special Witchspace Location ==

In order to access information about the current witchspace location while in witchspace itself - an in-between systems location, one that the player can only reach via a misjump - the short form for the local SystemInfo (system.info) will access a special, generic witchspace location, one that always return data for the ''current'' witchspace position, or null values if the player is not in witchspace.

In practice, the witchspace SystemInfo works like all others, with the exception that you cannot store the whole witchspace systemInfo inside a single convenience variable for later use, and that you cannot change specific values to apply to witchspace. As an example, trying to set a value for the local witchspace 'system':

system.info.economy = 5;

will simply be ignored while in witchspace.

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: SystemInfo

2010-07-26T01:00:29Z

Kaks:

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

{{Oolite-class-added|1.74}}

'''<code>SystemInfo</code>''' objects provide information about a specific system.

== Properties ==
=== <code>coordinates</code> ===
'''coordinates''' : {{oojsclass|Vector3D}} (read-only)
The coordinates of the system in light years. e.g. for Lave: <code>(8, 34.6, 0)</code>. The z component is always zero.

The upper left corner has the coordinate <code>(0, 0, 0)</code>. Going right increases the x value while going down on the map increases the y value.

'''Example:'''
System.infoForSystem(galaxyNumber, 7).coordinates
returns the coordinates of the system with an ID number of 7 in the current galaxy. In the first galaxy that would be the coordinates for Lave: <code>(8, 34.6, 0)</code>.

=== <code>galaxyID</code> ===
'''galaxyID''' : Number (read-only nonnegative integer)
The ID number of the galaxy.

=== <code>systemID</code> ===
'''systemID''' : Number (read-only nonnegative integer)
The ID number of the system.

== More properties ==
In addition to the properties above, you can access many other system properties, using the same keys as [[planetinfo.plist]].

'''Example:'''
<code>System.info.description = "This is a dull planet."</code>
sets the description of the current planet to “This is a dull planet.”

Properties that are changed in <code>system.info</code> are stored in the save file and are permanently changed for that commander. When both the planetInfo.plist and the data from a changed <code>system.info</code> file are present, those of the system.info are used. You can undo any changes in <code>system.info</code> by setting the value to <code>null</code>.

== Methods ==
=== <code>distanceToSystem</code> ===
function '''distanceToSystem'''(system : SystemInfo) : Number
Returns the distance in light years to another <code>SystemInfo</code>.

'''Example:'''
System.infoForSystem(galaxyNumber, 7).distanceToSystem(System.infoForSystem(galaxyNumber, 8))
If galaxyNumber is 0, this returns 92.8.

=== <code>routeToSystem</code> ===
function '''routeToSystem'''(system : SystemInfo [, "OPTIMIZED_BY_JUMPS" | "OPTIMIZED_BY_TIME"] ) : Object
Returns a dictionary containing the route information to another <code>SystemInfo</code>. The dictionary contains the array of system IDs that belong to the <code>route</code> found, the <code>distance</code> and the <code>time</code> corresponding to said route. Takes the optional parameter <code>"OPTIMIZED_BY_JUMPS"</code> (default) or <code>"OPTIMIZED_BY_TIME"</code> to calculate least number of jumps or fastest transit time routes respectively.

'''Example:'''
var myRoute = System.infoForSystem(galaxyNumber, 7).routeToSystem(System.infoForSystem(galaxyNumber, 8))
myRoute.route
myRoute.distance
myRoute.time
returns:
7,129,227,73,89,222,29,42,131,62,150,36,28,16,185,86,138,51,8 (the route)
96.40 (distance of added jumps)
530.40 (travelled time)

=== <code>systemsInRange</code> ===
{{Oolite-method-added|1.74.2}}
function '''systemsInRange'''([range : Number]) : Array
Returns an array of <code>SystemInfo</code>s in range (default: 7) from the given system.

'''Note:''' will not produce correct results if used in interstellar space.

'''See also:''' <code>SystemInfo.[[#systemsInRange_2|systemsInRange()]]</code> (which always provides results relative to the current system).

== Static methods ==
=== <code>filteredSystems</code> ===
function '''filteredSystems'''(this : Object, predicate : Function) : Array of SystemInfo
A list of the <code>SystemInfo</code>s for which <code>predicate</code> returns <code>true</code>.

'''Example:'''
// This is the actual implementation of <code>[[#systemsInRange_2|systemsInRange()]]</code> in Oolite 1.74.
SystemInfo.systemsInRange = function(range)
{
if (range === undefined)
{
range = 7;
}

var thisSystem = system.info;
return SystemInfo.filteredSystems(this, function(other)
{
return (other.systemID !== thisSystem.systemID) && (thisSystem.distanceToSystem(other) <= range);
});
}

=== <code>systemsInRange</code> ===
function '''systemsInRange'''([range : Number]) : Array
Returns an array of <code>SystemInfo</code>s in range (default: 7) from the current system.

'''Note:''' As of 1.74.2, this method works correctly for all systemInfos in the current galaxy, and for the current witchspace location. Trying to use it for other galaxies - or for a non-current witchspace location - will produce an error.

'''Example:'''
system.info.systemsInRange(5);

== Special Witchspace Location ==

In order to access information about witchspace locations - ones the player can only reach via a misjump, the short form for the local SystemInfo (system.info) will access a special, generic witchspace location, one that always return data for the ''current'' witchspace location, or null values if the player is not in witchspace.

In practice, the witchspace SystemInfo works like all others, with the exception that you cannot store the whole witchspace systemInfo inside a single convenience variable for later use, and that you cannot change specific values to apply to witchspace. For example:

system.info.economy = 5;

will be ignored in witchspace.

[[Category:Oolite JavaScript Reference]]

OXP mission offering

2010-07-21T12:03:30Z

Kaks: /* How mission offering should be done with JS */

= How mission offering should be done with Legacy script =

== Location for offering ==
Missions should only be offered while being docked. To prevent offering on special stations make sure you are docked at the main station:

conditions = ("dockedAtMainStation_bool equal YES")

Only if you are offering something on a special station you can check for just being docked, but then you should also check the station name.

conditions = ("status_string equal STATUS_DOCKED", "dockedStationName_string equal Your Station Name")

Here is " Your Station Name" the name of the station as defined in [[shipyard.plist]] under "name". You could skip the first test for being docked as dockedStationName_string only has the stationname if you are docked.

== Conditions for offering ==

Before placing text also check if the missionscreen is not in use. (See the documents in the downloadeble package below for more info)

For Oollite versions up to 1.68 that do not know the "notequal" condition or for compatibillity with those versions use:

conditions = (gui_screen_string oneof GUI_SCREEN_MAIN, GUI_SCREEN_STATUS).

At the end of the docking procedure the script runs immediately for one time with gui_screen_string = GUI_SCREEN_MAIN but already with status_string = STATUD_DOCKED. All following moments the script runs with as gui_screen_string the screen you are looking at. When you do nothing further this will be the GUI_SCREEN_STATUS . (= F5) You could also explicit check for the mission screen and put your whole action in the else line.

conditions = (gui_screen_string equal GUI_SCREEN_MISSION); do = (); else = (your stuff);

But this involves an extra nested condition, so most people will probably prefer the first method. Versions 1.69 and newer will have a not-equal option.

conditions = (gui_screen_string notequal GUI_SCREEN_MISSION).

== Setting up the message ==

In the do part you must set a mission image. If you have no image set it to "none", otherwise you can get an image from a previous offer. Be aware that some computers are case sensitive so use the same casing as the actual picture. The pictures are placed in a folder called "images", inside the OXP.

setMissionImage: none
or
setMissionImage: my_pict.png

Then set the output to the MissionScreen with

setGuiToMissionScreen

This command creates an empty missionscreen and any text after this will go to this missionscreen. The text is then placed with:

addMissionText: entryname

"Entryname" is a key value in the file [[missiontext.plist]] If you use a second addMissionText commands the text is added below the previous. If you add to much text it runs off the screen and is lost. So make sure you don't use to much text.
The system automatic puts a "hit space to continue" message at the bottom. On hitting this space key the MissionScreen will clear and the StatusScreen is put up. There exists also a command to put up the StatusScreen but you don't need that with offering.

== Offering with Choices ==

When you in addition use the command:

setMissionChoices: entryname

the "hit space to continue" message is replaced by your choices. Your choices is in this case a key entry in the [[missiontext.plist]] file with as contents an array. On the bottom of your screen you see the contents of the array and if you select one, the variable "missionChoice_string" contains the name of the chosen entry-string. When you are offering choices first make clear that:

conditions = ("missionChoice_string undefined")

And in the following conditions:

conditions = ("missionChoice_string equal Your String")

And make sure that on all possible choices that the player can make, the choice is reseted: "resetMissionChoice"

Some excisting missions reset the choices just before the offering itself, but in that case it is possible that the choices of another active mission that is offered on the same station is reset before it can act on the choices. If you want to play save, just reset the choices on launching so they are clear on the next docking. Also use distinctive text for "Your String" and not just "YES" or "NO" as other badly written OXP could react on those often used responses.

== Setting up the mission desciption ==

If you start a mission it is wise to add a short description and or a location for later reference by the player with:

setMissionDescription: entryname
addMissionDestination: planet_number

Entryname is a key value in the [[missiontext.plist]] file. This must be a short description as long text won't wrap around but runs off the screen at the right side. For planet_numbet you ca use a plain number between 0 and 255 or a variable between square brackets. The destination is visible as a red cross in the galactic chart. If the mission is over you clear this description and the location with:

clearMissionDescription
removeMissionDestination: planet_number

Notice that you do not need to specify the mission name in setting and clearing the missionDescription. The system automatic uses the name of the missionscript that uses this command to store the description. This also means that you can not use these two commands outside the missionscript like inside a death_action of a ship.
The best lessons are taken by examining existing scripts. You can download more info and a test OXP here: [[Media:MOP-Test_1.1.zip|Mission Offering Protocol]]

= How mission offering should be done with JS =

Starting with Oolite 1.74 we have a new method for displaying mission screens, one that minimises the mission screen conflicts that have afflicted scripts for quite some time: [[Oolite_JavaScript_Reference:_Mission#runScreen|mission.runScreen]], please refer to that part of the documentation when writing new missions.

The method described below is only needed with Oolite 1.73 or older, and will not work in future versions of Oolite: it was fairly complex to use, and due to its limitations, conflicts between different OXPs were always likely. The code samples below are offered as documentation of how the system worked in practice in order to understand how older javascript code worked, when updating it to more recent versions of Oolite.

'''N.B.''' From the next paragraph on, whenever javascript is mentioned, that refers to older javascript methods & practices.

For javascript all the legacy scripts considerations apply.
You need make sure you don't set up a message when there is already a mission screen or a report screen displayed. Also you shouldn't set up your mission screen when there are valid mission choices that don't belong to your script. With JS every oxp can react to a handler and when your handler code is triggered you must verify no other oxp has already reacted on that handler before you.

== script example for mission offering on JS ==

Below is an example script for clash free mission offering. It should work with Oolite version 1.73 and newer.

this.name = "demo";
this.author = "eric walch";
this.copyright = "© 2008 eric walch.";
this.description = "Empty script structure that handles population and mission offering";
this.version = "0.0";

// N.B. Works only with 1.73+.

// startUp only runs once at startup before the demoscreen shows up.
this.startUp = function()
{
this.reset(); // this.reset() fires not for a cmdr Jameson. When needed for a Jameson, call it here.
}

// this runs after loading in a saved game. missionVariables are read in at this point.
this.reset = function()
{
this.mustPopulate = true;
/* used for adding ships after a first launch.
This way you don't have to time consuming check every launch if a ship was already there.
*/
}

this.shipWillDockWithStation = function(station)
{
if(missionVariables.offering) missionVariables.offering = null;
/* When using the missionVariables.offering variable in script you need this function to clear the
variable in case the player launched from within the missionscreen without making choices. By clearing
this, most scripts that are created acording this layout will automatic do the offer again.
*/

/*
This is also the place to add your messages to the arrival report with:
if(condition) player.addMessageToArrivalReport(expandDescription("Your message"));
*/
}

this.shipDockedWithStation = function(station)
{
// an other eventhandler could have launched the ship already when it fires before this script.
if(player.ship.docked) this.missionOffers();
}

this.missionScreenEnded = this.missionChoiceWasReset = this.reportScreenEnded = function()
{
if(!player.ship.docked) return;
if(mission.choice) this.choiceEvaluation();
this.missionOffers();
}

this.missionOffers = function()
{
if (guiScreen == "GUI_SCREEN_MISSION" || guiScreen == "GUI_SCREEN_REPORT") return;
// there will be a "missionScreenEnded" or "reportScreenEnded" in future to react uppon.
if (missionVariables.offering || (mission.choice && mission.choice != "")) return;
// when "missionVariables.offering" or "mission.choice" are present it means that an other script claimed the mission_screen.
if (player.ship.dockedStation.isMainStation)
{
// Your stuff for the main station
/*
Missionscreens are set up using the command:
mission.runMissionScreen("mission_text", "backgroundscreen.png", "choices_text", "ship_role", "music")
You can transfer 5 variables at once that formerly had to set or cleared each seperately.
When not needed you can transfer a null. nulls at the end can be omitted, in between must be used.

When you do an offer you must set a variable to tell an offer is made. It is not safe to use the main mission
variable for this. Use missionVariables.offering for this. At the same time you know an other script is busy
offering when this variable is set. In case the player launched from within a missionscreen without making an
offer, the missionVariables.offering should be reset by script. Please do it on docking and not launching.
That way other oxp's that might need the value get an last change on using its content.
*/
}
else if (player.ship.dockedStation.shipDescription == "My Station")
{
// Your stuff for a special named station
}
}

this.choiceEvaluation = function()
{
if (missionVariables.offering == "MY_OFFER")
{
/* It is saver to not use a simple YES, but use a YES_MISSION. This just for the case there is
a conflict with an other bad written oxp that also has a simple YES as answer. */
if(mission.choice == "YES_MISSION")
{
// put your code here.
missionVariables.offering = null;
mission.choice = null;
/* resetting the mission.choice triggers the "missionChoiceWasReset" handler.
therefor this must always happen after other variables are reset to prefent that the script
tries to run again. */
}
else
{
if (mission.choice == "NO_MISSION")
{
// put your code here
missionVariables.offering = null;
mission.choice = null;
} else {missionVariables.offering = null} // one should never get here.
}
}
}

this.setUpShips = function()
{
// Put here your code that populates the system.
}

this.shipExitedWitchspace = function()
{
if(system.isInterstellarSpace) return;
this.setUpShips();
// Put here your code else than setting ships up.
}

this.playerEnteredNewGalaxy = function(Galaxy)
{
// This handler will be rarely needed.
}

this.shipLaunchedFromStation = function()
{
/* The first launch after a restart the system must be populated after a launch.
The other times it happens after a WitchspaceJump */
if(this.mustPopulate) {this.setUpShips(); this.mustPopulate = false}
// put here your other code.
}

[[Category:Oolite scripting]]

OXP mission offering

2010-07-21T11:43:42Z

Kaks: /* How mission offering should be done with JS */

= How mission offering should be done with Legacy script =

== Location for offering ==
Missions should only be offered while being docked. To prevent offering on special stations make sure you are docked at the main station:

conditions = ("dockedAtMainStation_bool equal YES")

Only if you are offering something on a special station you can check for just being docked, but then you should also check the station name.

conditions = ("status_string equal STATUS_DOCKED", "dockedStationName_string equal Your Station Name")

Here is " Your Station Name" the name of the station as defined in [[shipyard.plist]] under "name". You could skip the first test for being docked as dockedStationName_string only has the stationname if you are docked.

== Conditions for offering ==

Before placing text also check if the missionscreen is not in use. (See the documents in the downloadeble package below for more info)

For Oollite versions up to 1.68 that do not know the "notequal" condition or for compatibillity with those versions use:

conditions = (gui_screen_string oneof GUI_SCREEN_MAIN, GUI_SCREEN_STATUS).

At the end of the docking procedure the script runs immediately for one time with gui_screen_string = GUI_SCREEN_MAIN but already with status_string = STATUD_DOCKED. All following moments the script runs with as gui_screen_string the screen you are looking at. When you do nothing further this will be the GUI_SCREEN_STATUS . (= F5) You could also explicit check for the mission screen and put your whole action in the else line.

conditions = (gui_screen_string equal GUI_SCREEN_MISSION); do = (); else = (your stuff);

But this involves an extra nested condition, so most people will probably prefer the first method. Versions 1.69 and newer will have a not-equal option.

conditions = (gui_screen_string notequal GUI_SCREEN_MISSION).

== Setting up the message ==

In the do part you must set a mission image. If you have no image set it to "none", otherwise you can get an image from a previous offer. Be aware that some computers are case sensitive so use the same casing as the actual picture. The pictures are placed in a folder called "images", inside the OXP.

setMissionImage: none
or
setMissionImage: my_pict.png

Then set the output to the MissionScreen with

setGuiToMissionScreen

This command creates an empty missionscreen and any text after this will go to this missionscreen. The text is then placed with:

addMissionText: entryname

"Entryname" is a key value in the file [[missiontext.plist]] If you use a second addMissionText commands the text is added below the previous. If you add to much text it runs off the screen and is lost. So make sure you don't use to much text.
The system automatic puts a "hit space to continue" message at the bottom. On hitting this space key the MissionScreen will clear and the StatusScreen is put up. There exists also a command to put up the StatusScreen but you don't need that with offering.

== Offering with Choices ==

When you in addition use the command:

setMissionChoices: entryname

the "hit space to continue" message is replaced by your choices. Your choices is in this case a key entry in the [[missiontext.plist]] file with as contents an array. On the bottom of your screen you see the contents of the array and if you select one, the variable "missionChoice_string" contains the name of the chosen entry-string. When you are offering choices first make clear that:

conditions = ("missionChoice_string undefined")

And in the following conditions:

conditions = ("missionChoice_string equal Your String")

And make sure that on all possible choices that the player can make, the choice is reseted: "resetMissionChoice"

Some excisting missions reset the choices just before the offering itself, but in that case it is possible that the choices of another active mission that is offered on the same station is reset before it can act on the choices. If you want to play save, just reset the choices on launching so they are clear on the next docking. Also use distinctive text for "Your String" and not just "YES" or "NO" as other badly written OXP could react on those often used responses.

== Setting up the mission desciption ==

If you start a mission it is wise to add a short description and or a location for later reference by the player with:

setMissionDescription: entryname
addMissionDestination: planet_number

Entryname is a key value in the [[missiontext.plist]] file. This must be a short description as long text won't wrap around but runs off the screen at the right side. For planet_numbet you ca use a plain number between 0 and 255 or a variable between square brackets. The destination is visible as a red cross in the galactic chart. If the mission is over you clear this description and the location with:

clearMissionDescription
removeMissionDestination: planet_number

Notice that you do not need to specify the mission name in setting and clearing the missionDescription. The system automatic uses the name of the missionscript that uses this command to store the description. This also means that you can not use these two commands outside the missionscript like inside a death_action of a ship.
The best lessons are taken by examining existing scripts. You can download more info and a test OXP here: [[Media:MOP-Test_1.1.zip|Mission Offering Protocol]]

= How mission offering should be done with JS =

The method described below is only needed with Oolite 1.73 or older. Starting with Oolite 1.74 a new method for displaying a mission screen is introduced that is much easier in use and much less likely to give conflicts between different oxp's. So, when you now start creating a new script, forget the stuff below and start using the [[Oolite_JavaScript_Reference:_Mission#runScreen|new method for displaying a missionscreen]]. The code samples below is at the best useful to understand older code you might want to alter.

For java script all above about legacy scripts applies. Just make sure you don't set up a message when there is already a Missionscreen or a Reportscreen on display. Also don't set up your missionscreen when there are valid mission choices they don't belong to you. With JS every oxp can react on an handler and when your handler code is triggered you must verify no other oxp has already reacted on that handler before you.

== script example for missionoffering on JS ==

Below is an example script for clash free mission offering. It should work with Oolite version 1.73 and newer.

this.name = "demo";
this.author = "eric walch";
this.copyright = "© 2008 eric walch.";
this.description = "Empty script structure that handles population and mission offering";
this.version = "0.0";

// N.B. Works only with 1.73+.

// startUp only runs once at startup before the demoscreen shows up.
this.startUp = function()
{
this.reset(); // this.reset() fires not for a cmdr Jameson. When needed for a Jameson, call it here.
}

// this runs after loading in a saved game. missionVariables are read in at this point.
this.reset = function()
{
this.mustPopulate = true;
/* used for adding ships after a first launch.
This way you don't have to time consuming check every launch if a ship was already there.
*/
}

this.shipWillDockWithStation = function(station)
{
if(missionVariables.offering) missionVariables.offering = null;
/* When using the missionVariables.offering variable in script you need this function to clear the
variable in case the player launched from within the missionscreen without making choices. By clearing
this, most scripts that are created acording this layout will automatic do the offer again.
*/

/*
This is also the place to add your messages to the arrival report with:
if(condition) player.addMessageToArrivalReport(expandDescription("Your message"));
*/
}

this.shipDockedWithStation = function(station)
{
// an other eventhandler could have launched the ship already when it fires before this script.
if(player.ship.docked) this.missionOffers();
}

this.missionScreenEnded = this.missionChoiceWasReset = this.reportScreenEnded = function()
{
if(!player.ship.docked) return;
if(mission.choice) this.choiceEvaluation();
this.missionOffers();
}

this.missionOffers = function()
{
if (guiScreen == "GUI_SCREEN_MISSION" || guiScreen == "GUI_SCREEN_REPORT") return;
// there will be a "missionScreenEnded" or "reportScreenEnded" in future to react uppon.
if (missionVariables.offering || (mission.choice && mission.choice != "")) return;
// when "missionVariables.offering" or "mission.choice" are present it means that an other script claimed the mission_screen.
if (player.ship.dockedStation.isMainStation)
{
// Your stuff for the main station
/*
Missionscreens are set up using the command:
mission.runMissionScreen("mission_text", "backgroundscreen.png", "choices_text", "ship_role", "music")
You can transfer 5 variables at once that formerly had to set or cleared each seperately.
When not needed you can transfer a null. nulls at the end can be omitted, in between must be used.

When you do an offer you must set a variable to tell an offer is made. It is not safe to use the main mission
variable for this. Use missionVariables.offering for this. At the same time you know an other script is busy
offering when this variable is set. In case the player launched from within a missionscreen without making an
offer, the missionVariables.offering should be reset by script. Please do it on docking and not launching.
That way other oxp's that might need the value get an last change on using its content.
*/
}
else if (player.ship.dockedStation.shipDescription == "My Station")
{
// Your stuff for a special named station
}
}

this.choiceEvaluation = function()
{
if (missionVariables.offering == "MY_OFFER")
{
/* It is saver to not use a simple YES, but use a YES_MISSION. This just for the case there is
a conflict with an other bad written oxp that also has a simple YES as answer. */
if(mission.choice == "YES_MISSION")
{
// put your code here.
missionVariables.offering = null;
mission.choice = null;
/* resetting the mission.choice triggers the "missionChoiceWasReset" handler.
therefor this must always happen after other variables are reset to prefent that the script
tries to run again. */
}
else
{
if (mission.choice == "NO_MISSION")
{
// put your code here
missionVariables.offering = null;
mission.choice = null;
} else {missionVariables.offering = null} // one should never get here.
}
}
}

this.setUpShips = function()
{
// Put here your code that populates the system.
}

this.shipExitedWitchspace = function()
{
if(system.isInterstellarSpace) return;
this.setUpShips();
// Put here your code else than setting ships up.
}

this.playerEnteredNewGalaxy = function(Galaxy)
{
// This handler will be rarely needed.
}

this.shipLaunchedFromStation = function()
{
/* The first launch after a restart the system must be populated after a launch.
The other times it happens after a WitchspaceJump */
if(this.mustPopulate) {this.setUpShips(); this.mustPopulate = false}
// put here your other code.
}

[[Category:Oolite scripting]]

Mission variable

2010-07-21T11:41:15Z

Kaks: /* JavaScript */

Mission variables are states that can be set and queried by a script in [[script.plist]], or any JavaScript script.

They may be set to strings of characters that represent states (often in unspaced capital letters - just a style recommendation), or to numeric values, eg.

'''set: mission_myGreatMission_status START_OF_THE_MISSION'''
// mission_myGreatMission_status will be set to the string 'START_OF_THE_MISSION'

'''set: mission_myGreatMission_rewardValue 105.5'''
// mission_myGreatMission_rewardValue will be set to 105.5
// I might alter this value before I award it as credits at the end of the mission

They should have a unique name that is ''always'' prefixed by '''mission_'''. A good naming scheme is to use '''mission_''' followed by a unique identifier for your script (for example, '''fredJamesMission1''') followed by an underscore followed by the use to which the variable is being put (for example, '''_counter1''' or '''_EnemyName''').

Mission variables are saved in the player's saved game file.

=== Good Examples of Mission Variable Names ===

'''mission_fredJamesMission_counter1'''
// might be set to a number that's incremented or decremented every so often

'''mission_trumbles_decisionKey'''
// could be the result of a missionChoice

'''mission_moonShot_stage'''
// could be a phrase describing the current scripted action eg. BEGINNING_MISSION or KILLING_ALIENS or MISSION_COMPLETE

=== Poor Examples of Mission Variable Names ===

'''mission_counter'''
// no mission identifier

'''mission_variable'''
// no mission identifier

'''mission_mymissionisaverycomplexaffairthatImightmisspell_andthisisanequallycomplexvariable'''
// could be easily misspelt or misunderstood

=== JavaScript ===

In JavaScript, mission variables can be accessed through the [[Oolite_JavaScript_Reference:_Global#missionVariables|missionVariables global variable]]. In JavaScript, the '''mission_''' prefix is not used. Two equivalent examples:
missionVariables.myGreatMission_status = "START_OF_THE_MISSION";
missionVariables["myGreatMission_status"] = "START_OF_THE_MISSION";

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

Oolite JavaScript Reference: Global

2010-07-21T11:36:36Z

Kaks: /* Properties */

The '''<code>Global</code>''' environment includes all Oolite objects and methods accessible by all scripts at all times.

== Properties ==
=== <code>clock</code> ===
'''clock''' : Object(read-only)
This property allows an OXP to access the game clock's properties and methods.

=== <code>galaxyNumber</code> ===
'''galaxyNumber''' : Number(read-only)
Returns the number ot the galaxy the player is in.

=== <code>guiScreen</code> ===
'''guiScreen''' : String(read-only)
Returns the screen the player is looking at. If in flight, it's set to "GUI_SCREEN_MAIN".

=== <code>manifest</code> ===
'''manifest''' : Object(read-only)
This property allows an OXP to directly access the player ship's manifest properties.

=== <code>mission</code> ===
'''mission''' : Object(read-only)
This property allows an OXP to access misson methods.

=== <code>missionVariables</code> ===
'''missionVariables''' : Object(read-only)
This property allows an OXP to access and modify misson variables, used to store information inside save game files.

=== <code>oolite</code> ===
'''oolite''' : Object(read-only)
This property allows an OXP to access oolite's properties and methods.

=== <code>player</code> ===
'''player''' : Object(read-only)
This property allows an OXP to access the player object's properties and methods.

=== <code>system</code> ===
'''system''' : Object(read-only)
This property allows an OXP to access the current system's properties and methods.

=== <code>timeAccelerationFactor</code> ===
'''timeAccelerationFactor''' : Number(read/write)
Also known as TAF. Will change the ratio between game real time and actual real time (default is 1). The accepted range is between 0.0625 (1/16) and 16. Attempting to set numbers outside this range will reset the TAF to 1.

=== <code>worldScripts</code> ===
'''worldScripts''' : Object(read-only)
This property allows an OXP to access all world scripts, their properties and functions.

'''Example:'''
log(worldScripts['oolite-nova'].version);

== Methods ==
=== <code>displayNameForCommodity</code> ===
function '''displayNameForCommodity'''(commodityName : String)
Returns the display name corresponding to the specified commodity. Useful in conjunction with localisation OXPs, or expansions that rename commodities depending on which station / system the player is at.

=== <code>expandDescription</code> ===
function '''expandDescription'''(description : String [, locals : Object (Dictionary)]) : String
Expands a string, substituting special tokens and any key inside square brackets with the substitution rules for [[Methods#Communications|Communications]].
When local key/value pairs are provided, they take precedence over any other values. (buggy at the time of writing, fixed for 1.74.2 and later versions.)

'''Example:'''
expandDescription('My ball is [my_color].', { 'my_color': 'red' });

=== <code>expandMissionText</code> ===
function '''expandMissionText'''(textKey: String [, locals : Object (Dictionary)]) : String
Returns an expanded mission text, substituting any tokens and keys inside square brackets inside the original missiontext.plist value with its corresponding expanded string.
If local key/value pairs are provided, they take precedence over any other values. (buggy at the time of writing, fixed for 1.74.2 and later versions.)

'''Example:'''
expandMissionText('oolite_trumble_title');

=== <code>log</code> ===
function '''log'''([messageClass : String ,] message : String)
Writes a message to Oolite's log. The optional messageClass can be used to specify which type of message is written to the log.

'''Example:'''
log('myOXP.init','MyOXP initialised and ready!');

=== <code>randomInhabitantsDescription</code> ===
function '''randomInhabitantsDescription'''([plural : boolean])
Returns a random capitalised word, suitable to describe one sentient being, or - if using the optional plural argument - a group of sentients.

'''Example:'''
player.consoleMessage("You'll meet a " + randomInhabitantsDescription() +
". She'll be with a group of " + randomInhabitantsDescription(true) +'.');

=== <code>randomName</code> ===
function '''randomName'''()
Returns a random capitalised word, suitable for use as name, or indeed surname.

'''Example:'''
player.consoleMessage(randomName() + ' ' + randomName() +' rules this system with an iron fist.');

=== <code>setScreenBackground</code> ===
function '''setScreenBackground'''(image : String)
Temporary override that sets the background of the current gui screen to the specified image. Override is lost after the player switches screens.

'''Example:'''
setScreenBackground('oolite-nova-system.png');

=== <code>setScreenOverlay</code> ===
function '''setScreenOverlay'''(image : String)
Temporary override that sets the background of the current gui screen to the specified image. Override is lost after the player switches screens.

'''Example:'''
setScreenOverlay('trumblebox.png');

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Global

2010-07-20T16:52:26Z

Kaks: added reference to global methods & objects.

The '''<code>Global</code>''' environment includes all Oolite objects and methods accessible by all scripts at all times.

== Properties ==
=== <code>clock</code> ===
'''clock''' : Object(read-only)
This property allows an OXP to access the game clock's properties and methods.

=== <code>galaxyNumber</code> ===
'''galaxyNumber''' : Number(read-only)
Returns the number ot the galaxy the player is in.

=== <code>guiScreen</code> ===
'''guiScreen''' : String(read-only)
Returns the screen the player is looking at. If in flight, it's set to "GUI_SCREEN_MAIN".

=== <code>mission</code> ===
'''manifest''' : Object(read-only)
This property allows an OXP to directly access the player ship's manifest properties.

=== <code>mission</code> ===
'''mission''' : Object(read-only)
This property allows an OXP to access misson methods.

=== <code>oolite</code> ===
'''oolite''' : Object(read-only)
This property allows an OXP to access oolite's properties and methods.

=== <code>player</code> ===
'''player''' : Object(read-only)
This property allows an OXP to access the player object's properties and methods.

=== <code>system</code> ===
'''system''' : Object(read-only)
This property allows an OXP to access the current system's properties and methods.

=== <code>timeAccelerationFactor</code> ===
'''timeAccelerationFactor''' : Number(read/write)
Also known as TAF. Will change the ratio between game real time and actual real time (default is 1). The accepted range is between 0.0625 (1/16) and 16. Attempting to set numbers outside this range will reset the TAF to 1.

== Methods ==
=== <code>displayNameForCommodity</code> ===
function '''displayNameForCommodity'''(commodityName : String)
Returns the display name corresponding to the specified commodity. Useful in conjunction with localisation OXPs, or expansions that rename commodities depending on which station / system the player is at.

=== <code>expandDescription</code> ===
function '''expandDescription'''(description : String [, locals : Object (Dictionary)]) : String
Expands a string, substituting special tokens and any key inside square brackets with the substitution rules for [[Methods#Communications|Communications]].
When local key/value pairs are provided, they take precedence over any other values. (buggy at the time of writing, fixed for 1.74.2 and later versions.)

'''Example:'''
expandDescription('My ball is [my_color].', { 'my_color': 'red' });

=== <code>expandMissionText</code> ===
function '''expandMissionText'''(textKey: String [, locals : Object (Dictionary)]) : String
Returns an expanded mission text, substituting any tokens and keys inside square brackets inside the original missiontext.plist value with its corresponding expanded string.
If local key/value pairs are provided, they take precedence over any other values. (buggy at the time of writing, fixed for 1.74.2 and later versions.)

'''Example:'''
expandMissionText('oolite_trumble_title');

=== <code>log</code> ===
function '''log'''([messageClass : String ,] message : String)
Writes a message to Oolite's log. The optional messageClass can be used to specify which type of message is written to the log.

'''Example:'''
log('myOXP.init','MyOXP initialised and ready!');

=== <code>randomInhabitantsDescription</code> ===
function '''randomInhabitantsDescription'''([plural : boolean])
Returns a random capitalised word, suitable to describe one sentient being, or - if using the optional plural argument - a group of sentients.

'''Example:'''
player.consoleMessage("You'll meet a " + randomInhabitantsDescription() +
". She'll be with a group of " + randomInhabitantsDescription(true) +'.');

=== <code>randomName</code> ===
function '''randomName'''()
Returns a random capitalised word, suitable for use as name, or indeed surname.

'''Example:'''
player.consoleMessage(randomName() + ' ' + randomName() +' rules this system with an iron fist.');

=== <code>setScreenBackground</code> ===
function '''setScreenBackground'''(image : String)
Temporary override that sets the background of the current gui screen to the specified image. Override is lost after the player switches screens.

'''Example:'''
setScreenBackground('oolite-nova-system.png');

=== <code>setScreenOverlay</code> ===
function '''setScreenOverlay'''(image : String)
Temporary override that sets the background of the current gui screen to the specified image. Override is lost after the player switches screens.

'''Example:'''
setScreenOverlay('trumblebox.png');

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Mission

2010-07-20T12:09:01Z

Kaks: /* runScreen */

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

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

== Methods ==

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

Appends text to the currently running mission screen.

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

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

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

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

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

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

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

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

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

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

mission.runScreen(parameters, callback);

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Oolite JavaScript Reference]]

Missiontext.plist

2010-07-20T11:31:46Z

Kaks: /* Special Expansions */

This is the filename of the file that contains all the text relevant to scripted missions. See the [[Property_list|Property List]] page for more detail on plists.

== Structure ==
The file is organised as a dictionary <dict>.
Every entry consists of the name <key>, followed by the text <string>.

Example:
conhunt_short_desc1 = "Hunt for the constrictor stolen from Xeer.";
or in XML:
<key>conhunt_short_desc1</key>
<string>Hunt for the constrictor stolen from Xeer.</string>

==Special Expansions==

These can be included in your text, inside the quotation marks in openStep, or inside the <string>..</string> tags in XML, to automatically insert the following details

[commander_name] - Displays the name of the saved game file.

[commander_shipname] - Displays the name of the player's ship, as specified by [[shipdata.plist]].

[commander_shipdisplayname] - Could be different from commander_shipname.

[commander_rank] - Displays the player's Elite rating.

[commander_legal_status] - Displays the player's current legal status.

[commander_bounty] - Displays the current bounty on the player. ''(Oolite v1.74 & up)''

[nom] - Generate a random surname.

[thanks-for-assist] - Err, thanks the player for their assistance.

[police-thanks-for-assist] - the police thanks the player personally.

[describe-pirate] - Random description for an outlaw.

[describe-Pirate] - Capitalized random description for an outlaw.

[thargoid_curses] - Random Thargoid curses.

[police_warning] - Random impending fines notifications.

[police_attack_warning] - Random warning of immediate(?) attack.

%H - Will display the current system name i.e. Isinor.

%I - Displays the current system name with "ian" attached i.e. Isinorian.

%R - Random word.

%N - Random name. More variation than with %R. (Feature added with Oolite 1.73)

%Jxxx - Will display the system name of system with ID number "xxx". xxx must be a 3 digit number or no replacement takes place. e.g. %J007 is Lave. This replacement follows any system renaming by other oxp's. (Feature added with Oolite 1.73)

If the message contains other elements enclosed in square brackets [like_this]
that correspond to mission_variable names or keys in descriptions.plist, then these will also be expanded and substituted into the original message.

For further details, see also [[Methods#Communications|Communications in Methods]].

== Layout ==
Several spacial characters are used in determining the layout of the text, just as in Wiki.

*'''\"''' Enables the use of colons.
*'''\\n''' Insers a hard Enter.

In XML:
*'''\n''' Inserts a hard Enter.

Example:
<key>trumble_offer</key>
<string>Commander,\n\nYou look like a man who could use a Trumble!...</string>

== Choices ==
Most missions offer a choice, that is the spirit of elite.

Example:
<key>nova_yesno</key>
<dict>
<key>YES</key>
<string>Okay, I'll help.</string>
<key>NO</key>
<string>No, sorry.</string>
</dict>

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

Futurevision OXP

2010-07-16T22:48:29Z

Kaks:

'''Futurevision.oxp''' is a now obsolete [[OXP]] which provided some Oolite 1.71 scripting features for Oolite 1.70. It was intended for use by JavaScript OXP developers.

This version provides the following:
* [http://www.aegidian.org/bb/viewtopic.php?p=47550#47550 Global functions with lowercase names].
* <code>[[Oolite JavaScript Reference: Vector#random|Vector.random()]]</code>, <code>[[Oolite JavaScript Reference: Vector#randomDirection|Vector.randomDirection()]]</code> and <code>[[Oolite JavaScript Reference: Vector#randomDirectionAndLength|Vector.randomDirectionAndLength()]]</code>.
* [http://www.aegidian.org/bb/viewtopic.php?p=46338#46338 <code>Sound</code> and <code>SoundSource</code>] – although they don’t actually play sound.

[[Media:Futurevision.oxp.zip|Download]] (5 KiB)

OXPs 'N' to 'S'

2010-07-14T13:38:53Z

Kaks: /* Others */ updated orbits link to point at the latest version

[[Image:OXP_Icon_3.png‎|128px|right]]
== Index ==

[[OXPs 'N' to 'S'#Links|Go to Index]]

== N ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/newships.oxp.zip ''New Ships'']
| [[Hamadryad]] [[Josher]] [[Naga]] [[Ringhals]]
|
|Ships. Adds a variety of mining and trade ships seen in previous versions of Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Neolite Ships]]
|
|
| Oolite ships replacement set.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip ''NG HUD'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/nuvipers.zip ''Nu Vipers'']
| [[GalCop Viper Mark II]] [[GalCop Viper Cruiser]]
|
|Ships. Increases the types of Viper patrol ships appearing in the space lanes and defending Stations.
|-valign="top"
| [[Nukes.oxp|Nuclear Torpedos]]
|
|
| Equipment. Adds some powerful, but slow moving, missiles.
|-valign="top" bgcolor="#e7e7ff"
| [[Nuit Space Station OXP]]
|
| [[Nuit Space Station OXP|Nuit Space Station]]
| Station. [[Isis Interstellar]] formally announces the availability of their newest creation, the Nuit space station.
|}

== O ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Old Ships]]
| [[Bushmaster Miner]] [[Cat_%28Oolite%29|Cat (Cougar)]] [[Chameleon_%28Oolite%29|Chameleon]] [[Ghavial_%28Oolite%29|Ghavial]] [[Iguana_%28Oolite%29|Iguana]] [[Monitor_%28Oolite%29|Monitor]] [[Ophidian_%28Oolite%29|Ophidian]] [[Salamander_%28Oolite%29|Salamander]]
|
|Ships. A collection of ships from ArcElite and Elite-A.
|-valign="top" bgcolor="#e7e7ff"
| [[Old_Ships_2010|Old Ships 2010]] {{OXPUpdated|2010-05-23}}
| [[Bushmaster Miner]] [[Cat_%28Oolite%29|Cat (Cougar)]] [[Chameleon_%28Oolite%29|Chameleon]] [[Ghavial_%28Oolite%29|Ghavial]] [[Iguana_%28Oolite%29|Iguana]] [[Monitor_%28Oolite%29|Monitor]] [[Monitor 2]] [[Ophidian_%28Oolite%29|Ophidian]] [[Salamander_%28Oolite%29|Salamander]]
|
|Ships. A new version of Murgh's Old Ships, retextured by P.A.Groove. Includes a bonus ship, the Monitor 2.
|-valign="top"
| [[Oo-Haul]]
| [[L-Crate_Hauler|L-Crate Hauler]]
|
|[[Oolite_Missions#Oo-haul_Escort_Missions|Mission]]. Vast corporate bulk haulers can be seen in the space lanes. Commanders with a respectable Elite rating who chose to dock with a [[Pi-42]] base may also be offered missions to escort one of these haulers safely to its destination. You must also install the [[Your Ad Here!|Your Ad Here!]] OXP for this OXP to work properly.
|-valign="top" bgcolor="#e7e7ff"
| [http://terrastorage.ath.cx/Marmagka/9fffb0bdf04397418d5ef9c3715b14c8/OoliteItaliano_v1.4.zip''Oolite Italiano v1.4'']
|
|
|Miscellaneous. First ever Oolite localization OXP. Requires Oolite v1.74 or later.
|-valign="top"
| [http://www.boxcn.net/shared/ch3lsepk9k ''Oolite Russian v1.0'']
|
|
|Miscellaneous. The second Oolite localization OXP. Requires Oolite v1.72 or later.
|-valign="top" bgcolor="#e7e7ff"
| [[Orb]]
| [[Orb]]
|
|Ships. Adds a new alien race, which may (or may not) help GalCop in the battle against the Thargoids.
|-valign="top"
| [http://www.box.net/shared/x9u5xoulkq ''Orbits 1.2.1''] {{OXPUpdated|2010-07-08}}
|
|
|Utility. Positions planets on orbits around the sun. Requires Oolite v1.74.x.
|-valign="top" bgcolor="#e7e7ff"
| [[Ore Processor]] {{OXPUpdated|2010-06-05}}
|
|
| [[Ore_Processor|Equipment]]. When mounted to a ships fuel scoop systems extracts valuable materials from asteroid fragments. A must for any Commander working as a miner.
|-valign="top"
| [[Orisis]]
| [[Orisis]]
|
|BigTraders. New passenger liners that ferry passengers around.
|-valign="top" bgcolor="#e7e7ff"
| [[Outrider_%28Oolite%29|Outrider]]
| [[Outrider_%28Oolite%29|Outrider]]
|
| Ships. A medium fighter produced by the [[Taranis Corporation HQ (Oolite)|Taranis Corporation]].
|-valign="top"
| [[OXPConfig|OXP Config 1.08]]
|
|
| Tools/Utility. This tool gives you the ability to configure several oxps. It changes internal (local) settings of the oxps to enable (or disable) logging or audio functions and special settings to recognize errors or to avoid clashes. (Updated 04/09/2009)
|}

== P ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Pallas]]
| [[Pallas]]
|
|Ships. A fast but lightly shielded fighter.
|-valign="top" bgcolor="#e7e7ff"
| [[P.A. Groove Stations OXP]]
|
|
|Stations. Adds lots of different types of Coriolis and Dodec Stations.
|-valign="top"
| [[Pelamis]]
| [[Pelamis]]
|
|Ships. Adds the Pelamis trade ship.
|-valign="top" bgcolor="#e7e7ff"
| [[Personalities OXP]]
|
|
| Ships. Adds a bunch of unique, well-known personalities to the Ooniverse. Keen to meet yourself in your game (or have others meet yourself in their game)? Submit your own personality in the OXP's thread on the Oolite BBs.
|-valign="top"
| [[Phoenix]]
| [[Phoenix]]
|
|Ships. A strange ship, built from salvaged parts from various Serpent Class ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Pirate Coves OXP|Pirate Coves]]
|
| [[Pirate Coves OXP|Pirate Coves]]
| [[Oolite_Missions#Pirate_Coves|Mission]]. Some rock hermits in the more dangerous systems have been taken over by pirates. Traders coming too close are likely to be assaulted by scrambled pirates keen to relive them of their cargo.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip ''Pirate Traps'']
|
|
|Feature. To combat piracy GalCop sometimes deploys dummies of trade ships. Pirates who fire on them have their details transmitted to the police and face large fines.
|-valign="top" bgcolor="#e7e7ff"
| [[Planetfall_OXP|Planetfall]]
|
|
|System. Allows the player to land on and trade at the planets and moons of each system.
|-valign="top"
| [[Pods_OXP|Pods]]
|
|
|Cargo. Many new varieties of cargo pod, including fuel, missile, bulk, and empty, plus pods which take a couple of goes to scoop, jam in the fuel scoop, explode and even bring a trumble. Designed as a balanced OXP, to add some positives and some negatives to cargo scooping, to give more realism. Those of you who also use the [[UPS_Courier|UPS Courier]] OXP can also [http://www.boxcn.net/shared/sytn2yhpu0 download a little add-on] to the OXP that applies some of the new pods to UPS ones too (UPS Courier needs to be installed for the add-on to work).
|-valign="top" bgcolor="#e7e7ff"
| Probe (Now part of the [[Armoury_OXP|Armoury OXP]])
|
|
|Equipment. A long-range probe missile, flies away from the ship and scans at ranges of 50km and 100km, reporting ships found back to the ship. It then turns around and comes back, ready for fuel scooping and re-use.
|-valign="top"
| [[Pteradyne Technologies Ships OXP]]
| [[Excalibur]] [[Paladin]]
|
|Ships. A powerful combat ship, the Excalibur is offered for sale on the open market. The Paladin is the even tougher Military version, although sometimes these ships fall into the wrong hands.
|-valign="top" bgcolor="#e7e7ff"
| [[Python Class Cruiser]]
| [[Python Class Cruiser]]
|
|Ships. A large powerful trade ship, which can also hold its own in battle. Alternate shader version also available. (Shaders require Oolite 1.69 or later.)
|}

== Q ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|}

== R ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/racers.oxp.zip ''Racers'']
|[[Chicaneer Mk II]] [[Chicaneer Mk IV]] [[Dragster Mk I]] [[Dragster Mk II]]
|
|Ships. Adds dedicated racing ships to the Universe. Although very fast, these ships are pure racers with no cargo bays and light shields. The focus on pure speed makes them ill-suited to combat or trading roles.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/index.php/RingPod.oxp ''Racing Rings'']
|
|
|Feature. Adds Racing Rings to the Galaxy 1 systems of Lave and Zaonce. Fly through the rings in order and completing the race circuit will transmit the competitors' time.
|-valign="top"
|[[Ramon's_Anaconda|Ramon's Anaconda]]
|[[Ramon's_Anaconda|Ramon's Anaconda]]
|
| Ship. This is a fantastic re-imagining of the Anaconda freighter, made by Ramon, with assistance by Griff. Check out its special features!
|-valign="top" bgcolor="#e7e7ff"
|[[Random_Docking_Music_OXP|Random Docking Music]]
|
|
| Utility. Plays a randomly selected music track on activating docking computers (slow dock), from a list set inside the OXP.
|-valign="top"
|[[Random Hits OXP|Random Hits 1.4.2]] {{OXPUpdated|2010-07-05}}
|[[GalMine Hopper]]
|[[Space Bar]]
|[[Oolite_Missions#Random_Hits|Missions]] / Ships / Stations / Feature. Adds [[Space Bar|Seedy Space Bars]] to the space lanes of all Anarchy Systems. Commanders who chose to dock with one can view a Bulletin Board displaying details of the local Galaxies Most Wanted Criminals. Large bounties are paid for killing or capturing one of these offenders. Missions are procedurally generated using a database of over 40,000 words creating over one trillion different Bulletin Board Advertisements. Missions are therefore effectively never-ending. This OXP requires [http://developer.berlios.de/project/showfiles.php?group_id=3577&release_id=13778 Version 1.74 of Oolite].
|-valign="top" bgcolor="#e7e7ff"
|[http://terrastorage.ath.cx/Marmagka/e8e9ce360da6bb40f5952cbe00f02501/RedSet.zip ''RedSet''] {{OXPNew|2010-06-18}}
|
|
| Backgrounds for the UI screens. Just a small demo of one of Oolite v1.74's new features.
|-valign="top"
| [[RegistrationID|Registration ID]]
|
|
| Flavour. All Oolite standard ships now have ID tags.. You need at least Oolite 1.73 and a Graphics card capable of running shaders on a full setting..
|-valign="top" bgcolor="#e7e7ff"
| [[Remorse_Of_Conscience_v2|Remorse Of Conscience]]
| [[Remorse_Of_Conscience_v2|Remorse Of Conscience]]
|
|Ships. A trade ship with a large hold, that can hold its own in combat. A good upgrade from the Cobra Mk III.
|-valign="top"
|[[Renegade Pirates OXP|Renegade Pirates V3.0]]
|
|
|Ships / Feature. Adds rare very well armed pirate versions of Classic Elite ships to the more lawless systems. These pirates carry high bounties, but their multiple lasers and plasma cannons will make mince-meat of a young Jameson. Do not install this OXP until you have an Iron Ass!
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/RVandGS.zip ''Renegade Viper + Grass Snake'']
|[[Renegade Viper]] [[Grass Snake]]
|
|Ships. Sometimes even GalCops are victims of crime, finding their Vipers stolen from the docking berth. The joy-rider gives the stolen Viper a new lick of paint and joins a pirate fleet. Large bounties are paid for ridding the space lanes of these thieves. The Grass Snake is a trade ship with a large hold, often used by pirates.
|-valign="top"
| [[Repair_Bots_OXP|Repair 'Bots]]
|
|
| Equipment. A pylon mounted canister of repair nanobots. These can be activated in-flight, when they scan your ship for damaged equipment and attempt to fix an item of it (a random one if multiple items are found). They are reliable for lower tech items, but as the equipment gets more complicated they sometimes struggle. But if all else fails, buy, try and fly again...
|-valign="top" bgcolor="#e7e7ff"
| [[Ring_Racer_OXP|Ring Racer]]
|
|
| Mission. Corporate Systems Ring Racing League in Galaxy 1.
|-valign="top"
| [[Rock Hermit Locator|Rock Hermit Locator 1.3.2]] {{OXPUpdated|2010-05-31}}
|
|
|Equipment. The Rock Hermit Locator is a piece of equipment for your ship to locate Rock Hermits. Useful for miners and Traders. You need to already have bought the advanced space compass that works in tandem with the RHL ("Rock Hermit Locator").
|}

== S ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Saleza Aeronautics]]
| [[Bellatrix Cruiser]] [[Rigel Bomber]] [[Saiph Interceptor]]
|
|Ships / Feature. High Tech Corporate States gain their own patrol craft. Some of these ships are also available on the open market.
|-valign="top" bgcolor="#e7e7ff"
| [[Santa]]
| [[Santa]]
|
|Ships. Just for fun adds a (very rare) Santa Sledge to the space lanes escorted by plasma gun toting reindeer space bikers!
|-valign="top"
| [[Save_Anywhere|Save Anywhere]]
|
|
|Utility. Save Anywhere allows you to save your game at any OXP Station, instead of only at Main Stations, as in the standard game.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/images/c/c7/BlackBaron1.70.zip ''Scourge of the Black Baron v1.70'']
|
|
| [[Oolite_Missions#The_Scourge_of_the_Black_Baron|Mission]]. A sequel to the [http://capnhack.com/hosting/oolite/Oolite/OXPs/longway.oxp.zip ''Long Way Around''] mission, featuring combat and transport missions. Well suited to a relative novice in Galaxy 1.
|-valign="top"
| [[Second_Wave_OXP|Second Wave]]
|
|
| Ships. Some new variants on the standard Thargoid Warship and Thargon Robot Fighter. Adds a variety of new alien ship variants.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/s-ships1.zip ''Selezen's S-Ships'']
| [[GalCop SWAT Viper]] [[Oresrian Trader]]
|
|Ships. In response to increasing piracy GalCop has introduced the SWAT Viper, a beefed up version of the standard Viper. Also adds the peaceful Oresrian Trader.
|-valign="top"
| [[Sell equipment OXP]]
|
|
| Equipment. Allows you to resell all equipment you bought at an equipment store of suitable techlevel. For a small fee you purchase the "Sell xyz"-option, and are refunded 60 per cent of the original price.
|-valign="top" bgcolor="#e7e7ff"
| [[Shady Billboards OXP]]
|
|
| Demo. The '''Shady Billboards''' OXP demonstrates [[shaders in Oolite]] by displaying adverts from [[Your_Ad_Here!|Your Ad Here!]] on an animated electronic billboard.
|-valign="top"
| [[Shady Cobra OXP]]
|
|
| Ships. A [[shaders in Oolite|Shader]] example (requires Oolite 1.69 or later). Replaces the normal model for the Cobra Mk III with one featuring the new Shaders.
|-valign="top" bgcolor="#e7e7ff"
| [[S.I.R.F.]] {{OXPNew|2010-07-02}}
|
| [[S.I.R.F.|System Independent Repair Facility]]
| Stations. The station is a repair facility for ships in the systems. First released in 2006 on Oosat 2.
|-valign="top"
| [http://oosat.alioth.net/files/All-Stars_0.zip ''Skrounk All-Stars Limited'']
| [[All Stars Large Freighter]] [[Seymour Class Sled]] [[Starbelly Class Sled]] [[Starhawk|Star Hawk]] [[Starwolf_Mark_I|Starwolf Mk I]]
|
| Ships. A set of ships featuring a large trade ship and a variety of fighters and escorts.
|-valign="top" bgcolor="#e7e7ff"
| [[Smivs'_ShipSet|Smivs' ShipSet]] {{OXPUpdated|2010-05-22}}
|
|
| Ships. This OXP is a replacement ship set giving the ships and other objects in Oolite a new, more sophisticated look. This is achieved by applying new textures to the original models. This preserves the originality of the game...the ships are the same, but better looking!
|-valign="top"
| [[Snark]]
| [[Snark]]
|
|Ships. The Snark is a powerful fighter / trader, often used by pirates and bounty hunters.
|-valign="top" bgcolor="#e7e7ff"
| [[Snoopers|Snoopers2.0.3]] {{OXPUpdated|2010-06-17}}
|
|
| Feature. The galactic news network.
|-valign="top"
| [[Solid Gold Cobra Mk.3]] {{OXPNew|2010-06-09}}
| [[Solid Gold Cobra Mk.3]]
|
|Ships. A Solid Gold Cobra Mk.3
|-valign="top" bgcolor="#e7e7ff"
| [[Spearhead Interceptor Mk.I]]
| [[Spearhead Interceptor Mk.I]]
|
|Ships. A pure fighter, fast and nippy but with a weak shield, no cargo bay and can be a twitchy bird to fly. Often used as an escort or part of a pirate fleet acting in a hit an run role.
|-valign="top"
| [[Spy Hunter OXP]]
|
|
| [[Oolite_Missions#Spyhunter|Mission]]. A mission for the Galactic Navy available to a Commander with a rating of 'Dangerous' or above. Spys from the Empire sometimes infiltrate GalCop space. Commanders wishing to volunteer for hunting duties should visit the Navy base at Inines in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/StarWars.zip ''Star Wars Ships'']
| [[A-Wing]] [[B-Wing]] [[Lambda Shuttle]] [[Tie-Fighter]] [[Tie-Interceptor]] [[X-Wing]] [[Y-Wing]]
|
|Ships. Adds a set of ships from the Star Wars Universe to Oolite. Tie Fighters are occasionally used by GalCop to support Viper patrols, but all ships are available on the open market and may be used by traders, pirates and bounty hunters alike.
|-valign="top"
| [[Status Quo Q-bomb OXP]]
|
|
| Equipment. Changes the behaviour of Q-bombs according to the [[Status Quo]] novel. They don't detonate in gravity wells, like close to planets or suns.
|-valign="top" bgcolor="#e7e7ff"
| [[Stealth_OXP|Stealth]] {{OXPNew|2010-06-15}}

|
|
|Mission. Small G3 mission to showcase the new scanner capabilities of 1.74 and to introduce stealth ships.
|-valign="top"
| ''[http://www.box.net/shared/static/9cwp2jk84o.zip Sung's Detailed Textures]''
|
|
|Replacement textures for all Classic Elite Ships. The author's web-site no longer has a link to his textures. The link will download them directly from Lestradae's hosting site.
|-valign="top" bgcolor="#e7e7ff"
| [[Shady Sungs|Sung's Detailed Textures (Shader Version)]]
|
|
|Same as the above oxp, only now with shader support. Normal maps & Effects maps by ADCK. (Includes shaders which require Oolite 1.69 or later)
|-valign="top"
| [http://sancho.dk/oolite/sunskimmers.zip ''Sunskimmers'']
|
|
|Feature. Normally in Oolite ships tend to stick to the space lanes and so are rarely encountered on the way to the Sun. This OXP adds ships to the sun / planet corridor increasing the chance of meeting other ships whilst sun-skimming.
|-valign="top" bgcolor="#e7e7ff"
| [[S.T.E]]
| [[S.T.E]]
|
|Ships. The S.T.E addon ship a step up from the Cobra III improved trading capabilities also has increased speed over Cobra, is also available in 3 colour options blue, red and yellow.
|-valign="top"
| [[SuperCobra]]
| [[SuperCobra]]
|
|Ships. The awesome Super Cobra. A beefed up version of the Cobra Mk III featuring larger engines, more cargo space and stronger shields.
|-valign="top" bgcolor="#e7e7ff"
| [[Superhub]]
|
| [[Superhub]]
| Stations. Traffic congestion in the Ooniverse is growing and while the stations are getting more advanced the market asked for a more radical solution. This solution comes in the form of the [[GASEC]] Superhub. The GASEC Superhub is the first station that is capable of transporting itself to it's destination, two engine bays allow the GASEC SR-GD (Space Rotary Galactic Drive) to be fitted. At the destination these engines can be taken out for re-use in other transport missions. ''v1.2 updated 12th November 2009''
|-valign="top"
| [[Swift]]
| [[Swift]]
|
|Ships. As the name implies, a very fast ship often used by pirates or bounty hunters. Although fast, cargo space is limited and the shield is nominal.
|-valign="top" bgcolor="#e7e7ff"
| [[Switeck's_Mod_OXP|Switeck's Mod]] {{OXPNew|2010-07-08}}
|
|
| Rebalancing of ships and market prices. Pirate ships are more likely to have ECMs and Escape Pods. Adders, Boas and Boa 2s can now be pirates too. Market prices altered slightly. Two Jameson saves included for a Medium and Hard alternative starts.
|-valign="top"
| [[System_Redux_%28Oolite%29|System Redux]]
|
|
| Feature. Texture the home planet, add a planet/moon combination to each system. For Oolite v1.71 to 1.73.4. On v1.74+ use the [[OXPs_'A'_to_'F'#D|Deep Horizons System Redux 2 (beta)]].
|}

== Links ==
{{Navbox OXP}}

[[Category:Oolite expansion packs]]
[[Category:OXP Lists]]

All OXPs by Category

2010-07-14T13:34:39Z

Kaks: /* Others */ updated orbits link to point at the latest version, commented an early js example as obsolete.

[[Image:OXP_Icon_cat.png‎|right|128px]]
== Index ==

[[All OXPs by Category#Links|Go to Index]]

== Sound Sets ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Amiga Replacement Sounds ]]
| Based on the sound set used in the Amiga version of the original Elite.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/CustomSounds.zip ''Custom Sounds'']
|The largest of the currently available sound sets, this pack replaces or adds over 40 sounds, featuring additional music and extensive use of a calm female computer voice to warn the Commander of alarming events.
|-valign="top"
| [http://wiki.alioth.net/images/6/63/Halsis.zip ''Hal's Hot Sister'']
| Featuring a female cockpit voice.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.mediafire.com/file/mm2ekntynom/Hawksound.zip ''Hawksound'']
| Clean sounds. Quality female computer voice, new weapon, damage and some station interface sounds.
|-valign="top"
| [http://wiki.alioth.net/images/5/53/MildAudio.oxp.zip ''MildAudio'']
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds2.zip ''Murgh's Replacement Sounds'']
| No description available.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds.zip ''Wiggy's Replacement Sounds]
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds3.zip ''Xaotik's Replacement Sounds'']
| Same as ''MildAudio'' above.
|-valign="top"
| [http://www.box.net/shared/edl1p4lm3o ''Combined Murgh, Wiggy & Xaotik's sounds'']
| (Needs oolite 1.73+)
|}

== Alternative HUDs ==
[[HUD images here]] 
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/pLists/hud.plist ''Compact HUD'']
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.jblythe.f9.co.uk/Deepspace/Download/DeepspaceHUD_OXP.zip ''Deepspace HUD'']
| No description available.
|-valign="top"
| [[Dr HUD OXP]]
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [[Fighter HUD (Oolite)|Fighter HUD]]
| All-in-one turn coordinator. Combined instrument panel for speed, fuel, cabin temperature, laser temperature, altitude. Polarized glass laser sight.
|-valign="top"
| [http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip ''G-HUD Mk2'']
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [[Killer_Wolf's_Dynamic_HUD|Killer Wolf's Dynamic HUD]]
| HUD that switches display according to the current alert status. Oolite 1.74+ required.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/kleptohud.oxp.zip ''Klepto-HUD'']
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip ''Medusa HUD'']
| No description available.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/megawalnutdash.oxp.zip ''Mega-Walnut Dashboard'']
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [[MilSpec HUD OXP]]
| Adds targeting aids, emphasis on functionality. Current version is now dynamic, switches according to alert status. Oolite 1.74+ required.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip ''NG HUD'']
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/images/d/d9/TrekHud.zip ''Trek HUD'']
| No description available.
|}

== Dockable Objects ==
More information on Carriers appearing in Oolite can be found [[Oolite Carriers|here]]. 
More information on Stations appearing in Oolite can be found [[Oolite Stations|here]]. 
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Anarchies OXP]]
| [[Hacker Outpost]], [[Salvage Gang]], [[Military station|Sentinel Station]], and [[Military station|Renegade Station]]
|-valign="top" bgcolor="#e7e7ff"
| [[Aquatics OXP]]
| [[Aquarian Shipbuilding Corp. HQ]]
|-valign="top"
| [[The Assassins Guild OXP]]
| [[Navy Station]]
|-valign="top" bgcolor="#e7e7ff"
| [[Baakili Far Trader]]
| Adds a dockable Alien ship.
|-valign="top"
| [[Black_Monk_Monastary|Bank of the Black Monks]]
| [[Black Monk Monastary]]
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth]]
| Adds a dockable Navy Cruiser. Updated from the version on Oosat1.
|-valign="top"
| [[ADCK's_Behemoths|Behemoths - Shadered (By ADCK)]]
| Based on the above oxp, but with 2 new behemoths and shaders, plus many new ships. (Includes shaders which require Oolite 1.69 or later)
|-valign="top" bgcolor="#e7e7ff"
| [[Bulk Haulers]]
| Adds many Bulk Haulers to the game, including a retextured version of Aegidians Bulk Hauler as seen in the Oolite video on YouTube, which until recently has not been available to the public. (Requires [[BigShips_OXP|Big Ships]] and Includes shaders which require Oolite 1.69 or later)
|-valign="top"
| [[BuoyRepair]]
| [[Buoy Repair Facility]]
|-valign="top" bgcolor="#e7e7ff"
| [[Commies]]
| [[Astro Mines]], [[CZGF|Collective Zero-G Factory]], and [[SLAPU|Solar Laboratory and Production Unit]]
|-valign="top"
| [[Deep Space Dredger]]
| Adds dockable Space Dredgers to the space lanes, defended by a squad of [[Sabre|Sabre fighters]]. Version 2.3 has new, improved textures.
|-valign="top" bgcolor="#e7e7ff"
| [[Dictators OXP]]
| [[Imperial AstroFactory]]
|-valign="top"
| [http://oosat.alioth.net/files/Diso.zip Diso]
| [[Navy Station]]
|-valign="top" bgcolor="#e7e7ff"
| [[Griff_Industries|Dodo Stations OXP v1.1]]
| Retextured [[Dodecahedron Station (Oolite)|Dodo]] and [[Icosahedron Station (Oolite)|Ico]] stations, by Griff and CaptKev. v1.1 updated 18th May 2010.
|-valign="top"
| [[Feudal States|Feudal States OXP]]
| [[Royal Hunting Lodge]]
|-valign="top" bgcolor="#e7e7ff"
| [[Free Trade Zone]]
| Adds an independent trading post of dubious legality to Multi-Government systems.
|-valign="top"
| [[Fuel Station OXP]]
| Adds fly-thru Fuel Stations and Fuel Satellites near the witchpoint and along route one.
|-valign="top" bgcolor="#e7e7ff"
| [[Galactic Navy OXP]]
| [[Navy_SecCom_Station|Navy Sector Command Station]]
|-valign="top"
| [[Gates OXP]]
| Adds short-cut jump gates to suitable systems, speeding journeys between the main station and witchpoint for a fee of only 250Cr.
|-valign="top" bgcolor="#e7e7ff"
| [[Globe station|Globe Station OXP]]
| A new type of station appears at advanced systems. (Updated 22/10/2009)
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/GrittyCoriolis.oxp.zip ''Gritty Coriolis'']
| The Corolis Station gets a more detailed texture.
|-valign="top" bgcolor="#e7e7ff"
| [[HoOpy Casino]]
| HoOpy Casinos appear near the station in advanced systems. Commanders who chose to dock can win or lose credits in games of chance.
|-valign="top"
| [[Lave Academy OXP]]
| Adds the Lave Academy Orbital station above Lave (and now other planets), with three new mini-game tests of the Commanders' ship skills.
|-valign="top" bgcolor="#e7e7ff"
| [[Military_station|Military Station OXP]]
| Well armed Military Stations appear in the more advanced systems.
|-valign="top"
| [[Nuit Space Station OXP]]
| [[Isis Interstellar]] formally announces the availability of their newest creation, the Nuit space station.
|-valign="top" bgcolor="#e7e7ff"
| [[P.A. Groove Stations OXP]]
| Adds lots of different types of Coriolis and Dodec Stations.
|-valign="top"
| [[Planetfall OXP]]
| Allows the player to land on and trade at the planets and moons of each system.
|-valign="top" bgcolor="#e7e7ff"
| [[Random Hits OXP]]
| [[Space Bar]]
|-valign="top"
| [[Superhub]]
| ''v1.2 updated 12th November 2009''
|-valign="top" bgcolor="#e7e7ff"
| [[Taranis OXP]]
| [[Taranis Corporation HQ (Oolite)|Taranis Corporation HQ]]
|-valign="top"
| [[Taxi Galactica]]
| [[Taxi Galactica|Taxi Station]]
|-valign="top" bgcolor="#e7e7ff"
| [[Thargoid Carrier]]
| Arms the Thargoids with a vast carrier capital vessel. Many OXPs increase the fire-power available to the GalCop Navy. If you chose to play with these OXPs installed, then you should really give the Bugs a chance and allow them access to this mighty craft!
|-valign="top"
| [http://www.wagar.org.uk/downloads/software/oolite/Tianve1.3.zip ''Tianve'']
| [[Navy Station]]
|-valign="top" bgcolor="#e7e7ff"
| [[S.I.R.F.|S.I.R.F. OXP]]
| The station is a repair facility for ships in the systems. First released in 2006 on Oosat 2.
|-valign="top"
| [[Torus station|Torus Station]]
| Adds a vast 2001 style space station to very high tech level systems.
|-valign="top" bgcolor="#e7e7ff"
| [[Trader Outpost (Oolite)|Trade Outpost]]
| Griff trade outpost without ads.
|-valign="top"
| [[Transhab station|Transhab Station]]
| Adds a large station with rotating arms to some medium tech level systems.
|-valign="top" bgcolor="#e7e7ff"
| [[Your Ad Here!]]
| [[Your Ad Here!|Constore]]
|}

== Features ==
''Customisations by Government / Tech Level, Flavour OXPs, System OXPs 

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Anarchies OXP]]
| Complete overhaul of Oolite's legal rating system.
|-valign="top" bgcolor="#e7e7ff"
| [[Asteroid Storm]]
| Adds lots of different types of Asteroids to the Universe.
|-valign="top"
| [[Black Monk Monastery]]
| Loansharks / Banking
|-valign="top" bgcolor="#e7e7ff"
| [[BlOomberg Markets]]
| This expansion varies the in-game economy by generating random events that affect commodity prices.
|-valign="top"
| [[BuoyRepair]]
| Repair company for defect or destroyed nav-beacons (Updated 28/06/2010).
|-valign="top" bgcolor="#e7e7ff"
| [[Cargo Wreck Teaser OXP]]
| Adds lots of different types of cargo canisters.
|-valign="top"
| [[Commies]]
| Communist systems have their own police forces, transports, stations and miners.
|-valign="top" bgcolor="#e7e7ff"
| [http://deephorizonindustries.com/ Deep Horizons System Redux 2]
| This Beta release OXP textures the primary (main) planet of an Oolite system based on a combination of economy and tech level using over 40 custom created textures. It also incorporates the ability to add up to 10 moons and 20 additional planets per system, each featuring it's own custom texture. It replaces [[System Redux (Oolite)|System Redux 1]]. Also on the website linked here, are three compatible OXP's, Light Down OXP (which changes system light levels, stars and nebula settings), Gas Giant Skimming OXP (which allows skimming of fuel and rare gases from Gas Giant planets), and Pirate Ambushes OXP (which gives pirates the ability to move the witchpoint beacons in certain systems).
|-valign="top"
| [[DeepSpacePirates|Deep Space Pirates]]
| This OXP adds ships outside the space lanes.
|-valign="top" bgcolor="#e7e7ff"
| [[Dictators OXP]]
| Dictatorship systems gain their own police forces, supply craft and stations.
|-valign="top"
| [[Famous Planets OXP]]
| Adds unique planetary textures to certain planets.
|-valign="top" bgcolor="#e7e7ff"
| [[Feudal States]]
| The Feudal States is an OXP that adds various new elements to the leading feudal systems in Oolite galaxies.
|-valign="top"
| [[Galactic Navy]]
| Adds to the already formidable arsenal of the Galactic Navy.
|-valign="top" bgcolor="#e7e7ff"
| [[Generation_Ships_OXP|Generation Ships]]
| Adds Generation Ships to interstellar space.
|-valign="top"
| [[Interstellar help OXP]]
| Allows you to help out some traders who got stuck in interstellar space without fuel.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/monument.zip ''Monument'']
| A monument to famous Commanders can sometimes be seen near the Sun.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip ''Pirate Traps'']
| To combat piracy GalCop sometimes deploys dummies of trade ships. Pirates who fire on them have their details transmitted to the police and face large fines.
|-valign="top" bgcolor="#e7e7ff"
| [[Pods OXP]]
| Adds lots of different types of cargo canisters.
|-valign="top"
| [http://wiki.alioth.net/index.php/RingPod.oxp ''Racing Rings'']
| Adds Racing Rings to the Galaxy 1 systems of Lave and Zaonce.
|-valign="top" bgcolor="#e7e7ff"
| [[Random Hits OXP]]
| Bounty Hunting.
|-valign="top"
| [[Saleza Aeronautics]]
| High Tech Corporate States gain their own patrol craft.
|-valign="top" bgcolor="#e7e7ff"
| [[Snoopers]]
| The galactic news network. Updated 17/06/2010
|-valign="top"
| [http://sancho.dk/oolite/sunskimmers.zip ''Sunskimmers'']
| This OXP adds ships to the sun / planet corridor increasing the chance of meeting other ships whilst sun-skimming.
|-valign="top" bgcolor="#e7e7ff"
| [[System Redux (Oolite)|System Redux]]
| Texture the home planet, add a planet/moon combination to each system.
|-valign="top"
| [[Taxi Galactica]]
| Taxi Service
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/TGY.zip ''Tionisla Orbital Graveyard'']
| Adds the graveyard to the Galaxy 1 system of Tionisla.
|-valign="top"
| [[Total patrol OXP|Total Patrol OXP]]
| Replaces the default police AIs with a totalPatrolAI which lets police ships patrol between all three major points of the system: planet, witchpoint and sun.
|-valign="top" bgcolor="#e7e7ff"
| [[UPS Courier]]
| Courier service.
|-valign="top"
| [[Your Ad Here!]]
| Convenience stores.
|}

== Missions ==
More information on Oolite Missions can be found [[Oolite Missions|here]]. 
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Aquatics OXP]]
| Contains a mission based out of the [[Aquarian Shipbuilding Corp. HQ]]
|-valign="top" bgcolor="#e7e7ff"
| [[The Assassins Guild OXP]]
| 21 missions involving murder to order in Galaxy 7.
|-valign="top"
| [[Asteroid Storm]]
| A well known station in Galaxy 1 comes under threat from a large asteroid strike.
|-valign="top" bgcolor="#e7e7ff"
| [[Black Monk Monastery]]
| Deal with the loan sharks.
|-valign="top"
| [[BlackjacksBullion OXP]]
| Starts in galaxy 2 at Telace as Commander Blackjack arrives via escape pod at the same station you have just docked.
|-valign="top" bgcolor="#e7e7ff"
| [[Cataclysm OXP]]
| Sends you on a mission far bigger than anything you have done for the Navy so far.
|-valign="top"
| [http://www.box.net/shared/3smiibdosb Constrictor Mission Hints OXP]
| Gives more hints when doing the native Contrictor Mission.
|-valign="top" bgcolor="#e7e7ff"
| [[Deposed OXP]]
| A series of missions set in Galaxy 4 for an experienced Commander.
|-valign="top"
| [[Galactic Navy OXP]]
| The Galactic Navy needs you.
|-valign="top" bgcolor="#e7e7ff"
| [[Ionics OXP]]
| A series of missions set in Galaxy 2 featuring the Ionics Company of Zaria.
|-valign="top"
| [[Lave Academy OXP]]
| Training missions.
|-valign="top" bgcolor="#e7e7ff"
| [[Localhero OXP]]
| Adds a mission campaign in the first galaxies. (Updated 9.04.2008)
|-valign="top"
| [[LongWay_OXP|Long Way Around]]
| A transport mission well suited to the novice in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/index.php/Lovecats.oxp ''Lovecats 1.2'']
| Love and betrayal amongst the feline races of Galaxy 4.
|-valign="top"
| [[Military Fiasco]]
| A mission for the Navy available to a Commander with more than 1,000 kills.
|-valign="top" bgcolor="#e7e7ff"
| [[Oo-Haul]]
| Be offered missions to escort a hauler safely to its destination
|-valign="top"
| [[Pirate Coves OXP]]
| No description available.
|-valign="top" bgcolor="#e7e7ff"
| [[Random Hits OXP]]
| Bounty Hunting.
|-valign="top"
| [[Ring Racer OXP]]
| Corporate Systems Ring Racing League in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/images/c/c7/BlackBaron1.70.zip ''Scourge of the Black Baron v1.70'']
| A sequel to the [[LongWay_OXP|Long Way Around]] mission, featuring combat and transport missions. Well suited to a relative novice in Galaxy 1.
|-valign="top"
| [[Spy Hunter OXP]]
| A mission for the Galactic Navy available to a Commander with a rating of 'Dangerous' or above.
|-valign="top" bgcolor="#e7e7ff"
| [[Stealth OXP]]
| Small G3 mission to showcase the new scanner capabilities of 1.74 and to introduce stealth ships.
|-valign="top"
| [[Taranis OXP]]
| A mission is also available for law abiding Commanders with a rating of Competent or better.
|-valign="top" bgcolor="#e7e7ff"
| [[Thargoid Wars]]
| War with the Thargoids intensifies featuring new attack and defense missions.
|-valign="top"
| [[TCAT OXP|To Catch a Thargoid]]
| The Bugs are back - G3 follow-up mission to Thargoid Plans, for Dangerous or Elite rank Commanders.
|-valign="top" bgcolor="#e7e7ff"
| [[Trident Down]]
| A series of missions set in Galaxy 4 involving the investigation of a vicious attack on an Trident Shuttle operated by [[Executive SpaceWays]].
|-valign="top"
| [[UPS Courier]]
| The UPS Courier service will randomly offer Commanders the option of taking goods or documents from system to system. Some say experienced Couriers may also be offered combat missions.
|-valign="top" bgcolor="#e7e7ff"
| [[Vector OXP]]
| Special feature - 'Richmans World' - a unusual mission type
|}

== Ship Systems ==
More information on Oolite Equipment can be found [[Oolite Equipment|here]]. 
===Equipment===
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Auto eject OXP|Auto Eject OXP]]
| This OXP adds a piece of equipment which ejects your escape pod automatically when your energy becomes too low.
|-valign="top" bgcolor="#e7e7ff"
| [[Automatic Chaff System]]
| An enhanced chaff-based missile countermeasure system by [[User:Wyvern|Wyvern]], based on [[User:Thargoid|Thargoid]]'s [[Armoury OXP|AMS]] and [[User talk:Ramirez|Ramirez]]'s [[Missiles_and_Bombs|Chaff Dispenser]].
|-valign="top"
| [[Bounty Scanner]]
| The Bounty Scanner adds bounty details (if any) to the targeting lock-box display when locked onto other ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Energy_Equipment_OXP|Emergency Charge Device]]
| Acts as an extra boost to the ships energy supplies in case of emergency.
|-valign="top"
| [[Energy_Equipment_OXP|Emergency Energy Unit]]
| A variance on the Emergency Charge Device.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon'']
| Mark a position in space by deploying a pylon mounted beacon.
|-valign="top"
| [[Fuel Collector OXP|Fuel Collector]]
| The Fuel Collector enables you to very slowly gather fuel whilst cruising in space.
|-valign="top" bgcolor="#e7e7ff"
| [[Fuel Tank]]
| Mounts in place of a missile, to top up 3 light years of fuel.
|-valign="top"
| [[Hyperradio js OXP|Hyperradio]]
| This device gives you the ability to listen to your own music.
|-valign="top" bgcolor="#e7e7ff"
| [[Misjump Analyser]]
| This analyser scans the witchspace in the direction of the target system.
|-valign="top"
| [[Missile Analyser]]
| This analyser scans incoming missiles and sets the target to the incoming missile when it is no standard missile.
|-valign="top" bgcolor="#e7e7ff"
| [[Ore Processor]]
| When mounted to a ships fuel scoop systems extracts valuable materials from asteroid fragments. A must for any Commander working as a miner.
|-valign="top"
| [[Armoury_OXP|Probe Missile]]
| Non-lethal missile that flys away and reports on ships found, when it returns it can be scooped and reused. Part of the [[Armoury_OXP|Armoury OXP]].
|-valign="top" bgcolor="#e7e7ff"
| [[Repair_Bots_OXP|Repair 'Bots]]
| A pylon mounted canister of repair nanobots.
|-valign="top"
| [[Rock Hermit Locator]]
| The Rock Hermit Locator is a piece of equipment for your ship to locate Rock Hermits.
|-valign="top" bgcolor="#e7e7ff"
| [[Target_Autolock_OXP|Target Autolock]]
| A software update for the standard [[Scanner Targeting Enhancement]] equipment that automatically locks onto attacking ships if you have no prior target selected.
|-valign="top"
| [[Target Reticle]]
| A software update for the standard [[Scanner Targeting Enhancement]] equipment that automatically turns the reticle red when the target is in the centre of the reticle.
|-valign="top" bgcolor="#e7e7ff"
| [[Welcome_Mat_OXP|Welcome Mat]]
| Software upgrade for the communications systems to expand the information given to the commander on arrival from witchspace into a new system.
|}

===Weapons===
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Armoury OXP]]
| New meta-oxp containing AMS, Captured Thargons, Drones, Probe and Missile Rack OXPs functionality plus some other new bombs and the missile machine.
|-valign="top" bgcolor="#e7e7ff"
| [[Dragon|Dragon's Military Smart Missile]]
| An improved Hard Head Missile with more bang for your Credit.
|-valign="top"
| [[Hired_Guns_OXP|Hired Guns]]
| Gives the chance to agree a contract for a pair of ships to accompany you on your next journey and fight on your behalf alongside you.
|-valign="top" bgcolor="#e7e7ff"
| [[Killit_OXP|''Killit™'' insta-death super weapons]]
| Adds a bunch of insane super weapons.
|-valign="top"
| [[Missiles and Bombs]]
| Adds the Cascade stand-off missile, Multiple-warhead anti-Thargoid missile, Frag Mine, Frag Missile, EMP Missile and short-range defence missile to the game. The new weapons are available to the player and NPCs alike.
|-valign="top" bgcolor="#e7e7ff"
| [[Nukes.oxp|Nuclear Torpedos]]
| Adds some powerful, but slow moving, missiles.
|-valign="top"
| [[Status Quo Q-bomb OXP|Status Quo Q-bomb]]
| Changes the behaviour of Q-bombs according to the [[Status Quo]] novel. They don't detonate in gravity wells, like close to planets or suns.
|}

== Others ==
''Other objects and miscellaneous eyecandy'' 
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 200px;"|Name !! Short Description
|-valign="top"
| [[Behemoth Spacewar]]
| Adds intelligence to the Behemoth and brings a combat with Thargoids
|-valign="top" bgcolor="#e7e7ff"
| [[BigShips OXP]]
| Adds the new role "bigTrader" to the game, designed for large ships which are unable to dock with stations due to their size. Also includes an AI which can be used for such ships, but DOES NOT include any ships of its own.
|-valign="top"
| [http://oosat.alioth.net/files/clearskies.oxp_.zip ''Clear Skies'']
| Reduces nebula effects. Handy if your system is finding it hard to run Oolite.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Diso.zip ''Diso'']
| Extra planets and stations are added to the Diso system in Galaxy 1.
|-valign="top"
| [[Display reputation OXP]]
| Displays your passenger and contract reputation in your ship's manifest.
|-valign="top" bgcolor="#e7e7ff"
| [[Oolite Docking Clearance Protocol (v1.72 or later)|Docking Clearance]]
| Sets the docking clearance on for all stations in Oolite.
|-valign="top"
| [[External Views OXP]]
| Adds better outside views to all the Classic Elite Ships. Warning: Do not use with Oolite 1.70 and above! From Oolite 1.70 onwards improved outside views have been added to the game itself, so you don't need this OXP anymore. Just throw it away.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/d57y0uip74 ''FarSun'']
| Places suns further away from the planet than standard Oolite. New, improved, and fully compatible with Novae!
|-valign="top"
| [[Freaky Thargoids OXP]]
| Shader example, requires Oolite 1.69. With this OXP installed, Thargoids will use the new Shaders. This was one of the first ships with shaders. Starting with 1.74 the shaders for this ship won't work anymore as intended but the ship can still be used if wanted.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/k2lvh3enuy ''Griff's Explosion Debris'']
| Adds new alloy & debris models to exploding ships.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/illicit_unlock.oxp.zip ''Illicit Unlock'']
| Allows the player to fly all the Classic Elite Ships.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/t3n98yhk6n ''Illicit Unlock - Griff Version'']
| Based on the above, Allows the player to fly Griffs pirate/viper Ships. (Requires [[Griff Industries|Griff's Normalmapped Ships]] )
|-valign="top"
| [[JavaScript test OXP]]
| Initial JavaScript scripting example, obsolete. (was originally created for Oolite 1.68)
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/dropbox/Lave171.zip ''Lave'']
| Gives the Lave System a make-over adding all the features described in The Dark Wheel novella included with the original Elite.
|-valign="top"
| [http://www.box.net/shared/x9u5xoulkq ''Orbits 1.2.1'']
| Positions planets on orbits around the sun. Requires Oolite v1.74.x
|-valign="top" bgcolor="#e7e7ff"
| [[OXPConfig]]
| This tool gives you the ability to configure several oxps. It changes internal (local) settings of the oxps to enable (or disable) logging or audio functions and special settings to recognize errors or to avoid clashes. (Updated 04/09/2009)
|-valign="top"
| [[Random Docking Music OXP]]
| Plays a randomly selected music track on activating docking computers (slow dock), from a list set inside the OXP.
|-valign="top" bgcolor="#e7e7ff"
| [[RegistrationID|Registration ID]]
| All Oolite standard ships now have ID tags.. You need at least Oolite 1.73 and a Graphics card capable of running shaders on a full setting.
|-valign="top"
| [[Save Anywhere]]
| Save Anywhere allows you to save your game at any OXP Station, instead of only at Main Stations, as in the standard game.
|-valign="top" bgcolor="#e7e7ff"
| [[Shady Billboards OXP]]
| The Shady Billboards OXP demonstrates shaders in Oolite by displaying adverts from Your Ad Here! on an animated electronic billboard.
|-valign="top"
| [[Switeck's Mod OXP]]
| Rebalancing of ships and market prices. Adds two Jameson saves, for Medium and Hard difficulty.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/r05ub873b5 ''TAF Reset'']
| Resets the Time Acceleration Factor (TAF) to 1.0 upon docking. Requires Oolite v1.73+.
|-valign="top"
| [http://www.wagar.org.uk/downloads/software/oolite/Tianve1.3.zip ''Tianve'']
| Adds scenery, including a pulsar, to the Galaxy 1 system of Tianve.
|}

== International Versions of Oolite ==

*[http://marc-schaffer.ch/data/OoliteGerman_V0.3.zip Oolite German v0.3] 
*[[Media:OoliteItaliano_v1.3.zip|''Oolite Italiano v1.3'']] 
*[http://www.box.net/shared/ch3lsepk9k Oolite Russian v1.0] 
*[http://www.box.net/shared/rrlm77ztzm Oolite en français] 

== Ship Sets ==
''Retextures / remodels of the Oolite ships and objects''
*[[Accessories OXP]] A re-texture set of all the non-ship objects (eg Stations, Cargo pods, Asteroids etc) in Oolite. Features lighting effects for v1.74 and above. Matches with the [[Smivs' ShipSet]] as below. 
*[[Deepspace Ships]] 
*[[Griff ArcElite]] 
*[[Griff Industries|Griff's Normalmapped Ships OXP]] 
*[http://capnhack.com/hosting/oolite/Oolite/OXPs/mPakRedux.zip ''M-Pack (Rusties)''] Adds rusty versions of all the Classic Elite ships. 
*[[Neolite Ships]] 
*[[Smivs' ShipSet]] A re-texture set of all the Oolite ships, using the original models for authenticity. 
*[http://www.box.net/shared/static/9cwp2jk84o.zip ''Sung's Detailed Textures''] Replacement textures for all Classic Elite Ships. Shader version below. 
*[[Shady Sungs]] 

== Ships and Ship Variants ==
{{Navbox OXP Ships}}

== Links ==
{{Navbox OXP}}

[[Category:Oolite expansion packs]]
[[Category:OXP Lists]]

Oolite JavaScript Reference: Script

2010-06-27T15:52:45Z

Kaks:

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

The '''<code>Script</code>''' class represents a JavaScript script. There are currently two categories of script: ''ship scripts'', which are attached to individual ships / in-game entities, and ''world scripts'', which are effectively attached to the player.

==Scripting overview==
World scripts are run once at game start-up, at which point they may create ''event handlers''. Event handlers are functions with predefined names which are called by the game at specific points. Ship scripts are run when their ship is loaded, and can also create event handlers. An event handler is specified as a property of the <code>Script</code> object itself. For example, to set up an event handler for the ''willDock'' event, a script would typically look like this:
this.willDock = function()
{
// Do stuff when about to dock
Log("Woo, I’m about to dock!");
}

This assigns an anonymous function with no arguments to the <code>Script</code> object’s <code>willDock</code> property. Another way to achieve the same thing would be:
function willDockEventHandler()
{
// Do stuff when about to dock
Log("Woo, I’m about to dock!");
}
this.willDock = willDockEventHandler;

This form has the advantage that it’s easy to remove and re-add the event handler. (Event handlers may be added or removed at any time.)
delete this.willDock; // stop handling willDock events
this.willDock = willDockEventHandler; // start handling willDock events again

A property of the <code>Script</code> object which is a function is called a '''method'''. The most common use for methods is for event handlers, but a script may assign itself arbitrary methods, and any script may call the methods of anothe <code>Script</code> object. For instance, consider the case of a ship which needs to interact with its escorts in an unusual way. The script for the escorts may define a method such as:
this.escortPerformSpecialManoeuvret(target)
{
// Do something very clever here
}
which the mothership might do as follows:
// Warning: untested code
function makeEscortsPerformSpecialManoeuvre(target)
{
this.ship.escorts.forEach(function(escort){escort.script.escortPerformSpecialManoeuvre(this.target)}, this);
}
I can hear the cries of “huh” now, so let’s expand on that a little:
function makeEscortsPerformSpecialManoeuvre()
{
// The function we want to call for each element of the escorts array.
function callEscortMethod(escort)
{
escort.script.escortPerformSpecialManoeuvre(this.target);
}

// Get the list of escorts from our ship.
var escorts = this.ship.escorts;

// For each element in the list, call callEscortMethod().
escorts.forEach(callEscortMethod, this);
}
Note: it is a good idea to use reasonably unique names for methods. If your ship script implements a <code>doStuff</code> method, and some other ship script implements a <code>doStuff</code> method that does something completely different, one may be called when the other was intended.

<code>Script</code> objects to not have many predefined properties. Instead, the script can set whatever properties it needs. Which properties are used by the game depends on the context in which the script is being used.

==Predefined properties==
===<code>ship</code>===
'''ship''' : [[Oolite JavaScript Reference: Ship|Ship]] (read-only)
For ship scripts, the ship to which the script is attached. Undefined for world scripts.

'''N.B.''' ship refers to the entity that 'owns' the script, which might not be an actual ship. If a specific script is a property of an asteroid as opposed to a ship, ''this.ship'' will refer to the asteroid, etc...

==Common properties==
These are properties scripts can set on themselves which have a standard meaning.

===<code>author</code>===
'''author''' : String
Who wrote the script. Currently unused.

===<code>copyright</code>===
'''copyright''' : String
A copyright statement for the script. Currently unused.

===<code>description</code>===
'''description''' : String
A short description of the script. Currently unused.

===<code>name</code>===
'''name''' : String
The name of the script. World scripts must have a unique name. It’s a good habit to set a name for all scripts. If no name is set when the script is first run, Oolite will make one up. While it is possible to set the <code>name</code> property at any time, the value used after the script is first run is the one Oolite will continue to use.

===<code>version</code>===
'''version''' : String
A string specifying the version of the script. This is used, together with name, for identification in log messages and similar. While it is possible to set the <code>version</code> property at any time, the value used after the script is first run is the one Oolite will continue to use.

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Script

2010-06-27T15:51:30Z

Kaks: /* ship */

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

The '''<code>Script</code>''' class represents a JavaScript script. There are currently two categories of script: ''ship scripts'', which are attached to individual ships, and ''world scripts'', which are effectively attached to the player.

==Scripting overview==
World scripts are run once at game start-up, at which point they may create ''event handlers''. Event handlers are functions with predefined names which are called by the game at specific points. Ship scripts are run when their ship is loaded, and can also create event handlers. An event handler is specified as a property of the <code>Script</code> object itself. For example, to set up an event handler for the ''willDock'' event, a script would typically look like this:
this.willDock = function()
{
// Do stuff when about to dock
Log("Woo, I’m about to dock!");
}

This assigns an anonymous function with no arguments to the <code>Script</code> object’s <code>willDock</code> property. Another way to achieve the same thing would be:
function willDockEventHandler()
{
// Do stuff when about to dock
Log("Woo, I’m about to dock!");
}
this.willDock = willDockEventHandler;

This form has the advantage that it’s easy to remove and re-add the event handler. (Event handlers may be added or removed at any time.)
delete this.willDock; // stop handling willDock events
this.willDock = willDockEventHandler; // start handling willDock events again

A property of the <code>Script</code> object which is a function is called a '''method'''. The most common use for methods is for event handlers, but a script may assign itself arbitrary methods, and any script may call the methods of anothe <code>Script</code> object. For instance, consider the case of a ship which needs to interact with its escorts in an unusual way. The script for the escorts may define a method such as:
this.escortPerformSpecialManoeuvret(target)
{
// Do something very clever here
}
which the mothership might do as follows:
// Warning: untested code
function makeEscortsPerformSpecialManoeuvre(target)
{
this.ship.escorts.forEach(function(escort){escort.script.escortPerformSpecialManoeuvre(this.target)}, this);
}
I can hear the cries of “huh” now, so let’s expand on that a little:
function makeEscortsPerformSpecialManoeuvre()
{
// The function we want to call for each element of the escorts array.
function callEscortMethod(escort)
{
escort.script.escortPerformSpecialManoeuvre(this.target);
}

// Get the list of escorts from our ship.
var escorts = this.ship.escorts;

// For each element in the list, call callEscortMethod().
escorts.forEach(callEscortMethod, this);
}
Note: it is a good idea to use reasonably unique names for methods. If your ship script implements a <code>doStuff</code> method, and some other ship script implements a <code>doStuff</code> method that does something completely different, one may be called when the other was intended.

<code>Script</code> objects to not have many predefined properties. Instead, the script can set whatever properties it needs. Which properties are used by the game depends on the context in which the script is being used.

==Predefined properties==
===<code>ship</code>===
'''ship''' : [[Oolite JavaScript Reference: Ship|Ship]] (read-only)
For ship scripts, the ship to which the script is attached. Undefined for world scripts.

'''N.B.''' ship refers to the entity that 'owns' the script, which might not be an actual ship. If a specific script is a property of an asteroid as opposed to a ship, ''this.ship'' will refer to the asteroid, etc...

==Common properties==
These are properties scripts can set on themselves which have a standard meaning.

===<code>author</code>===
'''author''' : String
Who wrote the script. Currently unused.

===<code>copyright</code>===
'''copyright''' : String
A copyright statement for the script. Currently unused.

===<code>description</code>===
'''description''' : String
A short description of the script. Currently unused.

===<code>name</code>===
'''name''' : String
The name of the script. World scripts must have a unique name. It’s a good habit to set a name for all scripts. If no name is set when the script is first run, Oolite will make one up. While it is possible to set the <code>name</code> property at any time, the value used after the script is first run is the one Oolite will continue to use.

===<code>version</code>===
'''version''' : String
A string specifying the version of the script. This is used, together with name, for identification in log messages and similar. While it is possible to set the <code>version</code> property at any time, the value used after the script is first run is the one Oolite will continue to use.

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Script

2010-06-27T15:50:31Z

Kaks: /* ship */

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

The '''<code>Script</code>''' class represents a JavaScript script. There are currently two categories of script: ''ship scripts'', which are attached to individual ships, and ''world scripts'', which are effectively attached to the player.

==Scripting overview==
World scripts are run once at game start-up, at which point they may create ''event handlers''. Event handlers are functions with predefined names which are called by the game at specific points. Ship scripts are run when their ship is loaded, and can also create event handlers. An event handler is specified as a property of the <code>Script</code> object itself. For example, to set up an event handler for the ''willDock'' event, a script would typically look like this:
this.willDock = function()
{
// Do stuff when about to dock
Log("Woo, I’m about to dock!");
}

This assigns an anonymous function with no arguments to the <code>Script</code> object’s <code>willDock</code> property. Another way to achieve the same thing would be:
function willDockEventHandler()
{
// Do stuff when about to dock
Log("Woo, I’m about to dock!");
}
this.willDock = willDockEventHandler;

This form has the advantage that it’s easy to remove and re-add the event handler. (Event handlers may be added or removed at any time.)
delete this.willDock; // stop handling willDock events
this.willDock = willDockEventHandler; // start handling willDock events again

A property of the <code>Script</code> object which is a function is called a '''method'''. The most common use for methods is for event handlers, but a script may assign itself arbitrary methods, and any script may call the methods of anothe <code>Script</code> object. For instance, consider the case of a ship which needs to interact with its escorts in an unusual way. The script for the escorts may define a method such as:
this.escortPerformSpecialManoeuvret(target)
{
// Do something very clever here
}
which the mothership might do as follows:
// Warning: untested code
function makeEscortsPerformSpecialManoeuvre(target)
{
this.ship.escorts.forEach(function(escort){escort.script.escortPerformSpecialManoeuvre(this.target)}, this);
}
I can hear the cries of “huh” now, so let’s expand on that a little:
function makeEscortsPerformSpecialManoeuvre()
{
// The function we want to call for each element of the escorts array.
function callEscortMethod(escort)
{
escort.script.escortPerformSpecialManoeuvre(this.target);
}

// Get the list of escorts from our ship.
var escorts = this.ship.escorts;

// For each element in the list, call callEscortMethod().
escorts.forEach(callEscortMethod, this);
}
Note: it is a good idea to use reasonably unique names for methods. If your ship script implements a <code>doStuff</code> method, and some other ship script implements a <code>doStuff</code> method that does something completely different, one may be called when the other was intended.

<code>Script</code> objects to not have many predefined properties. Instead, the script can set whatever properties it needs. Which properties are used by the game depends on the context in which the script is being used.

==Predefined properties==
===<code>ship</code>===
'''ship''' : [[Oolite JavaScript Reference: Ship|Ship]] (read-only)
For ship scripts, the ship to which the script is attached. Undefined for world scripts.

'''N.B.''' ship refers to the entity that 'owns' the script, which might not be an actual ship. If a specific script is a property of an asteroid as opposed to a ship, this.ship will refer to the asteroid, etc...

==Common properties==
These are properties scripts can set on themselves which have a standard meaning.

===<code>author</code>===
'''author''' : String
Who wrote the script. Currently unused.

===<code>copyright</code>===
'''copyright''' : String
A copyright statement for the script. Currently unused.

===<code>description</code>===
'''description''' : String
A short description of the script. Currently unused.

===<code>name</code>===
'''name''' : String
The name of the script. World scripts must have a unique name. It’s a good habit to set a name for all scripts. If no name is set when the script is first run, Oolite will make one up. While it is possible to set the <code>name</code> property at any time, the value used after the script is first run is the one Oolite will continue to use.

===<code>version</code>===
'''version''' : String
A string specifying the version of the script. This is used, together with name, for identification in log messages and similar. While it is possible to set the <code>version</code> property at any time, the value used after the script is first run is the one Oolite will continue to use.

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Ship script event handlers

2010-06-27T15:17:03Z

Kaks: /* alertConditionChanged */

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

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

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

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

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

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

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

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

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

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

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

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

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

=== Witchspace Jumps ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Enter/Exit Aegis ===

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

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Combat ===

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

The <code>alertConditionChanged</code> handler is called when a station's alert status ([[Oolite_JavaScript_Reference:_Station#alertCondition|Station.alertCondition]]) changes. Only the player and stations have an alert condition. The equivalent player event is handled inside [[Oolite_JavaScript_Reference:_world_script_event_handlers|world scripts]].

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

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

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

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

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

'''Deprecated''' in 1.74 in favour of the more generic shipTargetAcquired

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

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

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

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

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

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

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

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

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

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

==== <code>shipCloakActivated</code> ====

The <code>shipCloakActivated</code> handler is called whenever the script's target ship activates its cloaking device. No parameters are required for this handler (added in test version 1.74).

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

==== <code>shipCloakDeactivated</code> ====

The <code>shipCloakDeactivated</code> handler is called whenever the script's target ship deactivates its cloaking device. No parameters are required for this handler (added in test version 1.74).

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

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

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

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

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

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

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

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

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

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

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

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler added in test version 1.74)

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

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

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

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

==== <code>shipTargetAcquired</code> ====

The <code>shipTargetAcquired</code> handler is called whenever a new target is selected. (Handler added in test version 1.74)

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

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

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

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

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

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

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

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

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

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

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

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

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

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

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

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

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

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

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

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

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

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

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

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

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

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

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

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

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

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

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

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

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

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

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

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

=== Missing Events ===

All initially planned events have a corresponding event handler in v1.74.

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

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

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: World script event handlers

2010-06-27T15:14:29Z

Kaks: /* alertConditionChanged */

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

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

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

World scripts are always active.

=== Game State ===

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

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

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

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

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

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

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

=== Docking ===

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

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

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

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

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

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

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

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

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

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

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

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event) 
playerWillEnterWitchspace (NPC ship event) 
playerEnteredNewGalaxy (world event) 
shipWillExitWitchspace (world event) 
shipExitedWitchspace (world event) 

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite_JavaScript_Reference:_Player#alertCondition|player.alertCondition]]</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>guiScreenWillChange</code> ====
{{Oolite-prop-added|1.74}} 
The <code>guiScreenWillChange</code> handler is called when the guiScreen is about to change. It only fires for the screens: GUI_SCREEN_EQUIP_SHIP, GUI_SCREEN_MANIFEST, GUI_SCREEN_MARKET and GUI_SCREEN_SHIPYARD. On these screens a script could change the content of the page to be displayed. (world script only)

this.guiScreenWillChange = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called after a ship has been added to the system. After a witchspace jump it means that first all ships are added to the system, then all the relevant shipSpawned events are triggered.

this.shipSpawned = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Missing Events ===

All the initially planned events have been implemented in 1.74.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Ship script event handlers

2010-06-27T15:12:17Z

Kaks: /* alertConditionChanged */

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

=== Witchspace Jumps ===

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the recommended time to set up elements which need to be present in-system when the player arrives.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when a station's alert status ([[Oolite_JavaScript_Reference:_Station#alertCondition]]) changes. Only the player and stations have an alert condition. The player event is handled inside world scripts.

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

this.escortAttack = function(target)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

'''Deprecated''' in 1.74 in favour of the more generic shipTargetAcquired

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function( whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipCloakActivated</code> ====

The <code>shipCloakActivated</code> handler is called whenever the script's target ship activates its cloaking device. No parameters are required for this handler (added in test version 1.74).

this.shipCloakActivated = function()
{
// Your code here
}

==== <code>shipCloakDeactivated</code> ====

The <code>shipCloakDeactivated</code> handler is called whenever the script's target ship deactivates its cloaking device. No parameters are required for this handler (added in test version 1.74).

this.shipCloakDectivated = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

this.shipEnergyBecameFull = function()
{
// Your code here
}

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

this.shipEnergyIsLow = function()
{
// Your code here
}

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler added in test version 1.74)

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when a target is lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetAcquired</code> ====

The <code>shipTargetAcquired</code> handler is called whenever a new target is selected. (Handler added in test version 1.74)

this.shipTargetAcquired = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

this.escortAccepted = function(escortship)
{
// Your code here
}

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

this.escortDock = function(delay)
{
// Your code here
}

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

this.playerWillEnterWitchspace = function()
{
// Your code here
}

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

this.shipAcceptedEscort = function(mother)
{
// Your code here
}

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

this.shipExitedWormhole = function()
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

this.shipSpawned = function()
{
// Your code here
}

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

this.shipWillEnterWormhole = function()
{
// Your code here
}

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

this.spawnedAsEscort = function(mother)
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

this.shipWasScooped = function(scooper)
{
// Your code here
}

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

this.otherShipDocked = function(whom)
{
// Your code here
}

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

this.stationLaunchedShip = function(whom)
{
// Your code here
}

=== Missing Events ===

All initially planned events have a corresponding event handler in v1.74.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: world_script_event_handlers|world_script_event_handlers]]

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: Ship script event handlers

2010-06-27T15:11:15Z

Kaks: /* alertConditionChanged */

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

=== Witchspace Jumps ===

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the recommended time to set up elements which need to be present in-system when the player arrives.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when a station's alert status (<code>[[Oolite_JavaScript_Reference:_Station#alertCondition]].alertCondition</code>) changes. Only the player and stations have an alert condition. The player event is handled inside world scripts.

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

this.escortAttack = function(target)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

'''Deprecated''' in 1.74 in favour of the more generic shipTargetAcquired

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function( whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipCloakActivated</code> ====

The <code>shipCloakActivated</code> handler is called whenever the script's target ship activates its cloaking device. No parameters are required for this handler (added in test version 1.74).

this.shipCloakActivated = function()
{
// Your code here
}

==== <code>shipCloakDeactivated</code> ====

The <code>shipCloakDeactivated</code> handler is called whenever the script's target ship deactivates its cloaking device. No parameters are required for this handler (added in test version 1.74).

this.shipCloakDectivated = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

this.shipEnergyBecameFull = function()
{
// Your code here
}

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

this.shipEnergyIsLow = function()
{
// Your code here
}

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler added in test version 1.74)

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when a target is lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetAcquired</code> ====

The <code>shipTargetAcquired</code> handler is called whenever a new target is selected. (Handler added in test version 1.74)

this.shipTargetAcquired = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

this.escortAccepted = function(escortship)
{
// Your code here
}

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

this.escortDock = function(delay)
{
// Your code here
}

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

this.playerWillEnterWitchspace = function()
{
// Your code here
}

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

this.shipAcceptedEscort = function(mother)
{
// Your code here
}

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

this.shipExitedWormhole = function()
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

this.shipSpawned = function()
{
// Your code here
}

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

this.shipWillEnterWormhole = function()
{
// Your code here
}

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

this.spawnedAsEscort = function(mother)
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

this.shipWasScooped = function(scooper)
{
// Your code here
}

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

this.otherShipDocked = function(whom)
{
// Your code here
}

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

this.stationLaunchedShip = function(whom)
{
// Your code here
}

=== Missing Events ===

All initially planned events have a corresponding event handler in v1.74.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: world_script_event_handlers|world_script_event_handlers]]

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: object model

2010-06-27T15:08:35Z

Kaks: Redirected page to Category:Oolite JavaScript Reference

#REDIRECT [[Category:Oolite_JavaScript_Reference]]

Oolite JavaScript Reference: object model

2010-06-27T15:07:23Z

Kaks: created redirect to avoid broken links

#REDIRECT [[Oolite_JavaScript_Reference]]

Oolite JavaScript Reference: Ship script event handlers

2010-06-20T13:32:35Z

Kaks: /* Not Yet Implemented */

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

=== Witchspace Jumps ===

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the recommended time to set up elements which need to be present in-system when the player arrives.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition.

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

this.escortAttack = function(target)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

'''Deprecated''' in 1.74 in favour of the more generic shipTargetAcquired

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function( whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipCloakActivated</code> ====

The <code>shipCloakActivated</code> handler is called whenever the script's target ship activates its cloaking device. No parameters are required for this handler (added in test version 1.74).

this.shipCloakActivated = function()
{
// Your code here
}

==== <code>shipCloakDeactivated</code> ====

The <code>shipCloakDeactivated</code> handler is called whenever the script's target ship deactivates its cloaking device. No parameters are required for this handler (added in test version 1.74).

this.shipCloakDectivated = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

this.shipEnergyBecameFull = function()
{
// Your code here
}

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

this.shipEnergyIsLow = function()
{
// Your code here
}

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler added in test version 1.74)

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when a target is lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetAcquired</code> ====

The <code>shipTargetAcquired</code> handler is called whenever a new target is selected. (Handler added in test version 1.74)

this.shipTargetAcquired = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

this.escortAccepted = function(escortship)
{
// Your code here
}

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

this.escortDock = function(delay)
{
// Your code here
}

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

this.playerWillEnterWitchspace = function()
{
// Your code here
}

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

this.shipAcceptedEscort = function(mother)
{
// Your code here
}

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

this.shipExitedWormhole = function()
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

this.shipSpawned = function()
{
// Your code here
}

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

this.shipWillEnterWormhole = function()
{
// Your code here
}

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

this.spawnedAsEscort = function(mother)
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

this.shipWasScooped = function(scooper)
{
// Your code here
}

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

this.otherShipDocked = function(whom)
{
// Your code here
}

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

this.stationLaunchedShip = function(whom)
{
// Your code here
}

=== Missing Events ===

All initially planned events have a corresponding event handler in v1.74.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: world_script_event_handlers|world_script_event_handlers]]

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: World script event handlers

2010-06-20T13:31:24Z

Kaks: /* Not Yet Implemented */ - brought it up to date!

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event) 
playerWillEnterWitchspace (NPC ship event) 
playerEnteredNewGalaxy (world event) 
shipWillExitWitchspace (world event) 
shipExitedWitchspace (world event) 

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>guiScreenWillChange</code> ====
{{Oolite-prop-added|1.74}} 
The <code>guiScreenWillChange</code> handler is called when the guiScreen is about to change. It only fires for the screens: GUI_SCREEN_EQUIP_SHIP, GUI_SCREEN_MANIFEST, GUI_SCREEN_MARKET and GUI_SCREEN_SHIPYARD. On these screens a script could change the content of the page to be displayed. (world script only)

this.guiScreenWillChange = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called after a ship has been added to the system. After a witchspace jump it means that first all ships are added to the system, then all the relevant shipSpawned events are triggered.

this.shipSpawned = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Missing Events ===

All the initially planned events have been implemented in 1.74.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite JavaScript Reference]]

Oolite JavaScript Reference: SystemInfo

2010-06-06T19:07:24Z

Kaks: /* systemsInRange */

'''Prototype:''' <code>Object</code> 

{{Oolite-class-added|1.74}}

'''<code>SystemInfo</code>''' objects provide information about a specific system.

== Properties ==
=== <code>coordinates</code> ===
'''coordinates''' : Vector (read-only)
The coordinates of the system in light years. e.g. for Lave: <code>(8, 34.6, 0)</code>. The z component is always zero. 
The upper left corner has the coordinate <code>(0, 0, 0)</code>. Going right increases the x value while going down on the map increases the y value. 
e.g.
System.infoForSystem(galaxyNumber, 7).coordinates
returns the coordinates of the system with an ID numberr of 7 in the current galaxy. In the first galaxy that would be the Lave coordinates: <code>(8, 34.6, 0)</code>.

=== <code>galaxyID</code> ===
'''galaxyID''' : Number (read-only nonnegative integer)
The ID number of the galaxy.

=== <code>systemID</code> ===
'''systemID''' : Number (read-only nonnegative integer)
The ID number of the system.

== More properties ==
Additional to these properties you have access to many other system properties, using the same keys as [[planetinfo.plist]]. e.g.
<code>System.info.description = "This is a dull planet."</code>
sets the description of the current planet to "This is a dull planet."

Properties that are changed in system.info are stored in the save file and are permanently changed for that commander. When both the planetInfo.plist and the data from a changed system.info file are present, those of the system.info are used. You can undo any changes in system.info by setting the value to null e.g.
<code>System.info.description = null</code>
will make that the system will use the original description.

== Methods ==
=== <code>distanceToSystem</code> ===
function '''distanceToSystem'''(SystemInfo) : Number
Returns the distance in light year to the other SystemInfo. 
e.g.
System.infoForSystem(galaxyNumber, 7).distanceToSystem(System.infoForSystem(galaxyNumber, 8))
returns: <code>92.8</code> as the distance between system 7 and 8 in light years.

=== <code>routeToSystem</code> ===
function '''routeToSystem'''(system : SystemInfo [, "OPTIMIZED_BY_JUMPS" | "OPTIMIZED_BY_TIME"] ) : Object
Returns a dictionary containing the route information to the other SystemInfo. The dictionary contains the array of system IDs that belong to the <code>route</code> found, the <code>distance</code> and the <code>time</code> corresponding to said route. Takes the optional parameter "OPTIMIZED_BY_JUMPS" or "OPTIMIZED_BY_TIME" to calculate least number of jumps or fastest transit time routes respectively. If the second parameter is omitted, "OPTIMIZED_BY_JUMPS" is implied. 
e.g.
var myRoute = System.infoForSystem(galaxyNumber, 7).routeToSystem(System.infoForSystem(galaxyNumber, 8))
myRoute.route
myRoute.distance
myRoute.time
returns:
7,129,227,73,89,222,29,42,131,62,150,36,28,16,185,86,138,51,8 (the route)
96.40 (distance of added jumps)
530.40 (travelled time)

=== <code>systemsInRange</code> ===
function '''systemsInRange'''(range : Number) : Array
Returns an array of SystemInfos in range from the present planetary system. When no distance is defined, it returns all systems within 7 light years.

Usage:

SystemInfo.systemsInRange(5);

'''N.B.''' will not produce correct results if used in interstellar space.

== Static methods ==
=== <code>filteredSystems</code> ===
function '''filteredSystems'''(this : Object, predicate : Function ) : Array of SystemInfo
A list of the SystemInfos for which <code>predicate</code> returns <code>true</code>.
'''Example:'''
SystemInfo.systemsInRange = function(range)
{
if (range === undefined)
{
range = 7;
}

var thisSystem = system.info;
return SystemInfo.filteredSystems(this, function(other)
{
return (other.systemID !== thisSystem.systemID) && (thisSystem.distanceToSystem(other) <= range);
});
}

[[Category:Oolite scripting]]

OXPs 'A' to 'F'

2010-06-06T15:31:20Z

Kaks: /* F */ removed obsolete oxp from list

[[Image:OXP_Icon_1.png‎|128px|right]]
== Index ==

[[OXP's 'A' to 'F'#Links|Go To Index]]

== A ==

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Aegidian's_Specials|Aegidian's Specials]]
| [[Mussurana]] [[Asp_%28Oolite%29#Notable_features|Asp Mark II Special]]
|
|Ships. The powerful Mussurana and an improved Asp.
|-valign="top" bgcolor="#e7e7ff"
| [[Aegidian's_X-Ships|Aegidian's X-Ships]]
| [[Python_ET_Special|Python ET Special]] [[Cobra_Mk.2_%28Oolite%29|Cobra Mk II]] [[Asp_%28Oolite%29#Notable_features|Asp Mark II Special]] [[Sidewinder_%28Oolite%29#Notable_featuresl|Sidewinder Special]]
|
|Ships. An improved Python, the experimental Cobra Mk II, the Asp Mark II Special and the Sidewinder Special.
|-valign="top"
| [[Pirate_Clan_Blitzspears|Amen Brick's Pirate Clan One: The Blitzspears]]
| [[Assassin_Blitzspear|Assassin]] [[Hoodlum]] [[Mugger]] [[Scoundrel]] [[Spiv]]
|
|Ships. The first of the Pan-Galaxy Outlaw clans to rise through the leadership of some diabolical criminal genius. What are his, or indeed hers or, further indeed, its future plans? Will their nefarious example be followed by others? The answers are out there...
All ships in this version are playable. Future versions (probably modular for memory saving reasons) will have more clans, the ability to join clans (if I master the arcane art of programming), stations and missions. Stay untuned, folks.
|-valign="top" bgcolor="#e7e7ff"
| [[Amen_Bricks_Megaships|Amen Brick's Megaships]]
| [[Battleship]] [[Biodome]] [[Cruiseship]] [[Hospitalship]] [[Supercargo]] [[Superlifter]] [[Yacht - Amen Class]]
|
|Ships. Graceful giants cross the galaxies before our eyes. The forlorn Biodome, destined to forever wander the Ooniverse. The Cruiseship taking citizens to holiday planets. The Supercargo ferrying aid to the needy. The private Yacht filled with luxury and the prosaic Superlifter than helps giant ships get to their new homes or their final resting place. Now amended to make spectacular explosions as they try to dock less likely (sorry!)
|-valign="top"
| [[Amiga Replacement Sounds]]
|
|
| Sound Set, based on the sound set used in the Amiga version of the original Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Anarchies OXP]]
| [[Renegade Viper|Hacker Viper]] [[Phoenix|Salvager Phoenix]] [[Hognose|Salvager Tugger]]
| [[Hacker Outpost]] [[Salvage Gang]] [[Military station|Sentinel Station]] [[Military station|Renegade Station]]
| Feature/Ships/Stations. Complete overhaul of Oolite's legal rating system. It gets harder to become clean again. But there are some new ways to achieve this as well: Hacker Outposts can be found in the higher tech [[Powers_and_Organisations#Anarchy_Worlds|Anarchy systems]], the criminals willing to clear a fugitive's legal record. For a price of course! Salvage Gangs are spread all over the Ooniverse, providing good equipment deals. Those in Anarchy systems offer a service similar to the Hacker Outposts as well. Sentinel Stations are placed in some of the worst Anarchies. But beware! Some of them have been overthrown by the pirates and are now Renegade Stations. Good news for the pirates among the players, because these are as close to a safe-haven for you as it gets! All of these also feature their own ships.
|-valign="top"
| [[AMS_OXP|Anti-Missile System]]
|
|
|Equipment. Adds the anti-missile system, designed to offer a defence against non-standard missiles via automatically firing interceptor darts (6 per launcher, replenishable). Requires [[Missile_Analyser|Missile Analyser OXP]] by Eric Walch.
|-valign="top" bgcolor="#e7e7ff"
| [[Aphid|Aphid Escort Service]]
| [[Aphid]]
|
|Ships. Adds the stylish Aphid escort service.
|-valign="top"
| [[Aquatics_OXP|Aquatics]]
| [[Manta Ray]] [[Shark]] [[Man O' War]] [[Box Escort]] [[Conger|Conger Cargo Hauler]] [[Hawksbill|Hawksbill Fuel Tanker]] [[HammerHead|HammerHead Hauler Carrier]] [[Barracuda]] [[Leviathan_Platform|Leviathan System Platform]] [[Orca|Orca Destroyer]]
|
|Ships/mission/station. Ships from the Aquarian Shipbuilding Corporation of Aqualina, G3. Also includes a brand new station (the Aquarian Shipbuilding Corp. HQ) plus a mission based out of it. And who knows, there may be a few more surprises in there too...
|-valign="top" bgcolor="#e7e7ff"
| [[Armoured_Transport_Type_1|Armoured Transport Type 1]]
| [[Gaundlet_Armoured_Transport_Type1|Gaundlet Armoured Transport Type 1]] [[Gaundlet_Armoured_Escort_Viper|Gaundlet Armoured Escort Viper]]
|
|Ships. Convoys of well armed craft ferry gold and other valuables through the space lanes. Only a pirate with an Iron Ass would dream of attempting a robbery!
|-valign="top"
| [[The Assassins Guild OXP|Assassins Guild OXP]]
| [[Daemon_Class_Cruiser|Daemon Class Cruiser]] [[Mongoose]] [[Nemesis]] [[Scorpion_Frigate|Scorpion Frigate]] [['Balrog' Class Dreadnaught]]
|[[Navy Station]]
| [[Oolite_Missions#The_Assassins_Guild|Missions]] / Ships / Stations / Planets. 21 missions involving murder to order in Galaxy 7, available to experienced Commanders amoral enough to gain admittance to the sinister [[Powers_and_Organisations#The_Assassins_Guild|Assassins Guild]]. Updated from the versions on Oosat1 & Oosat2.
|-valign="top" bgcolor="#e7e7ff"
|[[Asteroid_Storm|Asteroid Storm]]
|
|
| Feature / [[Oolite_Missions#Asteroid_Storm|Mission]]. Adds lots of different types of Asteroids to the Universe. A [[Oolite_Missions#Asteroid_Storm|Mission]] is also included, well suited to a novice Commander. A well known station in Galaxy 1 comes under threat from a large asteroid strike. The updated version fixes a bug that meant that only one new type of asteroid was being added. Now the intended twelve varieties appear in game. '''Note''': this OXP does not work in Oolite v.1.74+.
|-valign="top"
|[[Aurora]]
|[[Aurora]]
|
| BigTraders. Huge passenger ships for the wealthiest in society.
|-valign="top" bgcolor="#e7e7ff"
| [[Automatic_Chaff_System|Automatic Chaff System]] [[Image:New.gif|New]]
|
|
| Equipment. An enhanced chaff-based missile countermeasure system by [[User:Wyvern|Wyvern]], based on Thargoid's [[AMS_OXP|AMS]] and Ramirez's [[Missiles_and_Bombs|Chaff Dispenser]].
|}

== B ==

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Baakili Far Trader]]
|
| [[Baakili Far Trader]]
|Ships. Adds a dockable Alien ship.
|-valign="top" bgcolor="#e7e7ff"
| [[Bandersnatch]]
| [[Bandersnatch]]
|
|Ships. Adds a pirate capital vessel armed with 4 x fore lasers. (Bugfixed at November 2009)
|-valign="top"
| [[Black_Monk_Monastery|Bank of the Black Monks]]
| [[Black_Monk_Gunship|Black Monk Gunship]]
| [[Black_Monk_Monastery|Black Monk Monastery]]
| Feature / [[Oolite_Missions#Bank_of_the_Black_Monks|Mission]]. Monks aboard well armed stations appear in advanced systems. Loans are offered, defaulters will be exterminated! Two versions of the OXP are available, the [http://www.box.net/public/z2ahfudnt3 Non-Shader Bank of the Black Monks OXP'] and the [http://http://www.box.net/shared/7twwbaelcc 'Shady Bank of the Black Monks OXP']. The Non-Shader Version will run on all versions of Oolite. The Shady version uses Shaders and requires Version 1.71 or higher of Oolite. Slow Systems will struggle to run the Shady Version, so if you find installing it is slowing your system down too much, then try the Non-Shady Version.
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth]]
|
| [[Behemoth]]
|Ships. Adds a dockable Navy Cruiser. Updated from the version on Oosat1.
|-valign="top"
| [[ADCK's_Behemoths|Behemoths - Shadered (By ADCK)]]
| [[Destroyer]]
| [[Behemoth - Type 1]] [[Behemoth - Type 2]] [[Behemoth - Type 3]] [[Behemoth - Type 4]] [[Military Station Type 2]]
|Ships. Based on the above oxp, but with 2 new behemoths and shaders, plus many new ships. (Includes shaders which require Oolite 1.69 or later)
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth Spacewar]]
|
|
|Patch. Adds intelligence to the Behemoth and brings a combat with Thargoids
|-valign="top"
| [[BigShips_OXP|Big Ships]]
|
|
|Ships (ish). Adds the new role "bigTrader" to the game, designed for large ships which are unable to dock with stations due to their size. Also includes an AI which can be used for such ships, but DOES NOT include any ships of its own.
|-valign="top" bgcolor="#e7e7ff"
| [[BlackjacksBullion OXP|BlackJacks Bullion OXP]]
|
|
|Missions. Starts in galaxy 2 at Telace as Commander Blackjack arrives via escape pod at the same station you have just docked. Also contains two rare coloured [[S.T.E]]'s available for player purchase.
|-valign="top"
| [[Boa_II_Clipper_Class|Boa II Clipper Class]]
| [[Boa_II_Clipper_Class|Boa II Clipper Class]]
|
|Ships. A development of the Boa Class Cruiser, adding a third engine making it faster, at the cost of 25 TC of cargo space.
|-valign="top" bgcolor="#e7e7ff"
| [[Boomslang]]
| [[Boomslang]]
|
|Ships. Adds a mid-range multi-role ship. Used by pirates and traders alike.
|-valign="top"
| [[Bounty_Scanner|Bounty Scanner]]
|
|
|Equipment. The Bounty Scanner adds bounty details (if any) to the targeting lock-box display when locked onto other ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Bulk_Haulers|Bulk Haulers (by ADCK)]]
| [[Lynx Bulk Carrier (Oolite)|Lynx Bulk Carrier]] [[Long Range Cruiser (Oolite)|Long Range Cruiser]]
| [[Bulk Hauler]] [[Super Bulk Hauler]]
|Ships. Adds many Bulk Haulers to the game, including a retextured version of Aegidians Bulk Hauler as seen in the Oolite video on YouTube, which until recently has not been available to the public. (Requires [[BigShips_OXP|Big Ships]] and Includes shaders which require Oolite 1.69 or later)
|-valign="top"
| [[BuoyRepair|BuoyRepair1.02.5]]
| [[Armadillo]] [[Controller]] [[Guanako]]
|[[Buoy Repair Facility|Buoy Repair Facility]]
|Feature. Repair company for defect or destroyed nav-beacons (Updated 7/10/2009).
|}

== C ==

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Caduceus|Caduceus OXP]]
| [[Caduceus]]
|
|Ships. Adds the very expensive (and deadly) Caduceus, which has six broadside-mounted auto-targeting plasma cannons.
|-valign="top" bgcolor="#e7e7ff"
| [[Capisastra OXP]]
| [[Capisastra Defender]] [[Capisastra Hauler]] [[Capisastra Warrior]]
|
|Ships. Capisatra pirates appear in Galaxy 4.
|-valign="top"
| [[Captured_Thargons_OXP|Captured Thargons]]
|
|
|Equipment. Gives the possibility for player ships to carry and launch captured and reprogrammed Thargon robot fighters
|-valign="top" bgcolor="#e7e7ff"
| [[Cargo_Wreck_Teaser_OXP|Cargo & Wrecks V1.6.2]] [[Image:Updated.gif|Updated]]
|
|
| Cargo. Adds lots of different types of cargo canisters.
|-valign="top"
| [[Cataclysm OXP]]
|
|
| Mission. "Cataclysm.oxp is a mission OXP that takes up the threads of the native Constrictor Hunt and Thargoid Plans missions, and sends you on a mission far bigger than anything you have done for the Navy so far. It gives you the opportunity to re-visit places you have visited before, and re-meet people you had contact with during these missions. And of course it will let you meet various other people, and lead you to a lot of new places, some of which you probably haven't visited before."
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/clearskies.oxp_.zip ''Clear Skies'']
|
|
| Utility. Reduces nebula effects. Handy if your system is finding it hard to run Oolite.
|-valign="top"
| [[Cobra_3.5|Chopped Cobra]]
| [[Cobra_3.5|Cobra Mk 3.5]]
|
|Ships. A slightly faster and tougher variation on the classic Cobra Mk III, at the price of a reduced cargo bay.
|-valign="top" bgcolor="#e7e7ff"
| [[Cobra_Clipper_SAR|Cobra Clipper SAR]]
| [[Cobra_Clipper_SAR|Cobra Clipper SAR]]
|
|Ships. A custom Cobra Mk III to rescue stranded Commanders.
|-valign="top"
| [[Cobra III NjX]]
| [[Cobra III NjX]]
|
|Ships. A faster, tougher variation on the Classic Cobra Mk III.
|-valign="top" bgcolor="#e7e7ff"
| [[Commies|Commies v2.11]] [[Image:Updated.gif|Updated]]
| [[Ray_Mk.I|Ray Mk I]] [[Giant Ray]] [[Astro_Mines|Mining Pods]] [[Astro_Mines|Scavenger Rays]] [[Sturgeon Mk.I|Sturgeon Mk I]] [[Worker's Commuter]]
| [[Astro Mines]] [[CZGF|Collective Zero-G Factory]] [[SLAPU|Solar Laboratory and Production Unit]]
|Ships / Stations. Commie systems have their own police forces, transports, stations and miners.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/pLists/hud.plist ''Compact HUD'']
|
|
|Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [[Condor|Condor OXP]]
| [[Condor]]
|
| Ships. A very powerful police and Navy Cruiser.
|-valign="top"
| [[Croydon_Starsoarer|Croydon Starsoarer]] [[Image:New.gif|New]]
| [[Croydon_Starsoarer|Starsoarer]]
|
| Ships. First new ship from a design discussed on the BB's [http://aegidian.org/bb/viewtopic.php?t=7831 Ship Concepts thread]. The ship is similar to the Asp in specification.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/CustomSounds.zip ''Custom Sounds'']
|
|
| Sound Set. The largest of the currently available sound sets, this pack replaces or adds over 40 sounds, featuring additional music and extensive use of a calm female computer voice to warn the Commander of alarming events.
|}

== D ==

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[DWCobra|Dark Wheel Cobra]]
| [[DWCobra|Dark Wheel Cobra]]
|
|Ships. A custom Cobra Mk III model, as seen on the cover of the Elite Manual.
|-valign="top" bgcolor="#e7e7ff"
| [[Deep_Space_Dredger|Deep Space Dredger 2.4.2]]
| [[Sabre]]
| [[Deep Space Dredger]]
|Ships. Adds dockable Space Dredgers to the space lanes, defended by a squad of Saber fighters. Version 2.3 has new, improved textures.
|-valign="top"
| [[DeepSpacePirates|Deep Space Pirates]]
|
|
|Feature. Normally in Oolite ships do not appear outside the space lanes. This OXP adds ships outside the space lanes. As no police patrols extend this far out pirates and other unpleasant characters can be found in deep space.
|-valign="top" bgcolor="#e7e7ff"
| [[Deepspace Ships]]
|
|
|Oolite Ships replacement set. Replaces the default ships with new textures.
|-valign="top"
| [[Deposed_OXP|Deposed 1.3.4]]
|
|
| [[Oolite_Missions#Deposed|Mission]]. A series of missions set in Galaxy 4 for an experienced Commander. This version is now mission-offering. compatible with other OXPs.
|-valign="top" bgcolor="#e7e7ff"
|[http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Dictators'']
| [[Imperial Censor]] [[Imperial Freighter]] [[Imperial Lictor]] [[Imperial Quaestor]] [[Imperial Tanker]] [[Junta Enforcer]] [[Revolutionary Guard]]
| [[Imperial AstroFactory]]
| Ships / Stations. Dictatorship systems gain their own police forces, supply craft and stations.
|-valign="top"
| [http://oosat.alioth.net/files/Diso.zip ''Diso'']
|
|[[Navy Station]]
| Planets / Stations. Extra planets and stations are added to the Diso system in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [[Display reputation OXP|Display Reputation v1.1]]
|
|
| Feature. Displays your passenger and contract reputation in your ship's manifest.
|-valign="top"
| [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|Docking Clearance]]
|
|
| Feature. Sets the docking clearance on for all stations in Oolite. Click on [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|this link]] for further explanation.
|-valign="top" bgcolor="#e7e7ff"
| [[Griff_Industries|Dodo Stations OXP v1.1]] [[Image:Updated.gif|Updated]]
|
| [[Griff_Industries|Dodecahedron Stations]]
| Stations. Retextured Dodo and Ico stations, by Griff and CaptKev. v1.1 updated 18th May 2010.
|-valign="top"
| [[Dr HUD OXP]]
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [[Dragon|Dragon Assault Craft]]
| [[Dragon|Dragon Assault Craft]]
|
| Ships / Equipment. Adds the Dragon Assault Craft, a heavy combat ship available in several different paint-jobs. Also adds the Military Smart Missile, an improved Hard Head Missile with more bang for your Credit. Both the ship and missile are available to the player and NPCs alike.
|-valign="top"
| [http://www.mediafire.com/?sharekey=ca166c7e38ef78c6e7c82ed4b8f0c380e04e75f6e8ebb871 ''Dragonfly/Firefly S.T'']
| [[Dragonfly S.T]] [[Firefly S.T]]
|
|Ships. Adds the Dragonfly S.T and also the much faster Firefly S.T variant. Small fast ideal ship for pirates or bounty hunters.
|-valign="top" bgcolor="#e7e7ff"
| [[Drones_OXP|Drones]]
|
|
|Weapons. Three new autonomous drones to help the player (and NPCs) in combat. Fire and forget, with targeting taken from the ships scanning computers. Variants are the combat drone (standard fighting drone), the kamikaze drone (upgraded with a low yield warhead) and anti-Thargoid drone (GalCop commission, with stronger lasers and better speed and manoeuvrability, plus battle computer optimisation to seek and destroy Thargoid vessels). All can be recovered and possibly re-used if they survive battle.
|}

== E ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Eagle Mk II]]
| [[Eagle Mk II]]
|
| Ships. Adds the cheap Eagle Mk II escort vessel in several different versions, including an enhanced SE.
|-valign="top" bgcolor="#e7e7ff"
| [[ADCK's Eagles|Eagles Mk's I to IV (By ADCK)]]
| [[Eagle_Long_Range_Fighter_Mk_1_(Oolite)|Eagle Mk 1]] [[Eagle_Long_Range_Fighter_Mk_2_(Oolite)|Eagle Mk 2]] [[Eagle_Long_Range_Fighter_Mk_3_(Oolite)|Eagle Mk 3]] [[Eagle_Long_Range_Fighter_Mk_4_(Oolite)|Eagle Mk 4]]
|
| Ships. Adds 4 Eagle Long Range Fighters to the game, There are 8 different colours to each Eagle, and 4 player versions. Made by ADCK. (Includes shaders which require Oolite 1.69 or later)
|-valign="top"
| [[Energy_Equipment_OXP|Energy Equipment]]
|
|
|Equipment. The emergency charge device - a pylon-mounted top-up for the ships systems, and the emergency energy unit - an internally fitted automatically triggered top-up when the juice runs low.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon]
|
|
| Equipment. Mark a position in space by deploying a pylon mounted beacon.
|-valign="top"
| [[Executive SpaceWays]]
| [[Delta Long-Range Escort]] [[Gemini Escort]] [[Starseeker Personal Shuttle]] [[Strelka Cruise Liner]] [[Trident Executive Shuttle]]
|
| Ships. Adds the Executive SpaceWays fleet of ships.
|-valign="top" bgcolor="#e7e7ff"
| [[External Views OXP|External Views]]
|
|
| Utility. Adds better outside views to all the Classic Elite Ships. Warning: Do '''not''' use with Oolite 1.70 and above! From Oolite 1.70 onwards improved outside views have been added to the game itself, so you don't need this OXP anymore. Just throw it away.
|}

== F ==
{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! style="width: 150px;"|Information / Download !! style="width: 150px;"|Ships !! style="width: 150px;"|Carriers / Stations !! Short Description
|-valign="top"
| [[Famous_Planets_2.0.OXP|Famous Planets v2.0]]
|
|
| Flavour. Adds unique planetary textures to 46 planets in Galaxy 1, with Galaxy 2 coming soon. Adds new planetary descriptions to the F7 screen. And theme tunes for 10 planets on arrival.
|-valign="top" bgcolor="#e7e7ff"
| [[Famous Planets Liners OXP]]
|
|
| Ships. This OXP adds Spaceway Liners on the 4 spaceways from Lave to Zadies. You can find a map on the Bulletin Board. Just search for the latest version of Presti70's trading map of Galaxy 1. It is a separate OXP but is designed to complement the upcoming Famous Planets v2.
|-valign="top"
| [[Far_Arm_ships|Far Arm ships]]
| [[Far_Arm_Sunracer|Sunracer]] [[Far_Arm_Scow|Scow]] [[Far_Arm_Tanker|Tanker]] [[Far_Arm_Corsair|Corsair]] [[Far_Arm_Dart|Dart]] [[Far_Arm_Hunter|Hunter]] [[Far_Arm_Cruiser|Cruiser]] [[Far_Arm_Titan|Titan]] [[Far_Arm_Manchi_Vulture|Manchi Vulture]] [[Far_Arm_Manchi_Wasp|Manchi Wasp]]
|
| Ships. This OXP adds 10 ships, inspired by [http://en.wikipedia.org/wiki/Space_Rogue Paul Neurath's Space Rogue] to the Ooniverse. There is also a new alien race called the Manchi, who pilot ships of bizarre design. Released under the [http://creativecommons.org/licenses/by-nc-sa/3.0/ Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported] License.
|-valign="top" bgcolor="#e7e7ff"
| [[Far Star OXP|Far Star]]
| [[Far_Star_Murderer|Far Star Murderer]]
|
| Ships. A mid-range fighter / trader, with a fair sized cargo bay.
|-valign="top"
| [http://www.box.net/shared/d57y0uip74 ''Farsun v1.05'']
|
|
| Utility. Places suns further away from the planet than standard Oolite. New, improved, and fully compatible with Novae!
|-valign="top" bgcolor="#e7e7ff"
| [[Fer de Lance NG|Fer de Lance NG OXP]]
| [[Fer de Lance NG]]
|
| Ships. Adds a more powerful version of the Fer de Lance with several custom paint jobs.
|-valign="top"
| [[Ferdepai]]
| [[Ferdepai]]
|
| Ships. Adds a new fighter / trader to Galaxy 2.
|-valign="top" bgcolor="#e7e7ff"
| [[Fighter_HUD_%28Oolite%29|Fighter HUD]]
|
|
| Alternative HUD.
|-valign="top"
| [[Firewasp]]
| [[Firewasp]]
|
| Ships. A fast interceptor.
|-valign="top" bgcolor="#e7e7ff"
| [[Flying Dutchman OXP]]
| [[Flying Dutchman OXP|Griff Wireframe Cobra]]
|
| Feature / Ships. Adds the small chance to meet a ''Ghost Ship'' in the Ooniverse. What is it? Some claim that it's the ghost of Commander Peter Jameson, reported lost at the end of the last Thargoid War, others that it is simply a manifestation of all those lost souls who were trapped in the trackless depths of interstellar space. One common story is the trail of bad luck and hideous deaths that follow in the wake of the ship's sightings...
|-valign="top"
| [[Freaky Thargoids OXP]]
|
|
| [[shaders in Oolite|Shader]] example, requires Oolite 1.69. With this OXP installed, Thargoids will use the new Shaders. This was one of the first ships with shaders. Starting with 1.74 the shaders for this ship won't work anymore as intended but the ship can still be used if wanted.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/e43ftmvqmr ''Free Trade Zone'']
|
| [[Free_Trade_Zone|Free Trade Zone]]
| Stations. Adds an independent trading post of dubious legality to Multi-Government systems.
|-valign="top"
| [[Frog Space Rickshaw]]
| [[Frog Space Rickshaw]]
|
| Ships. Adds a chatty space taxi service to the safer systems. [[Image:Updated.gif|Updated!]] Updated with a new download link which was broken before.
|-valign="top" bgcolor="#e7e7ff"
| [[Fuel_Collector_OXP|Fuel Collector]]
|
|
|Equipment. The Fuel Collector enables you to very slowly gather fuel whilst cruising in space, whether en-route to a station, or in interstellar space should a witch-jump malfunction occur. You can also gather any unburnt fuel from destroyed ships as well as tap fuel from derelict or abandoned ships.
|-valign="top"
| [[Fuel Station OXP]]
|
| [[Fuel Station OXP|Fuel Station]]
|Station. Adds fly-thru Fuel Stations and Fuel Satellites near the witchpoint and along route one.
|-valign="top" bgcolor="#e7e7ff"
| [[Fuel Tank]]
|
|
| Equipment. Mounts in place of a missile, to top up 3 light years of fuel.
|}

== Links ==
{{Navbox OXP}}

[[Category:Oolite expansion packs]]
[[Category:OXP Lists]]

OXP

2010-05-06T06:07:06Z

Kaks:

== What are OXPs? ==

[[Image:oolite-oxp-icon.png|128px|right|OXP icon]]
An '''OXP''' (Oolite eXpansion Pack) is an enhancement to the game [[Oolite]]. Typically, an OXP is downloaded as a ZIP file, which is expanded and placed in Oolite's AddOns folder. On the Mac the OXP is a shown as an application, which takes the form of the icon shown here. On Windows the OXP appears as a normal folder ending ".oxp". An OXP could be a new game object (such as a ship, space station or a moon), a mission, or a combination of several elements. OXPs can use all of the facilities of Oolite, including some that are not used in the standard, unexpanded game. Whatever your OS, you need to move the OXP into Oolite's AddOns folder. Oolite will only read an OXP if you move the .oxp folder (or Application on the Mac) into Oolite's AddOns folder.

== Downloading OXPs ==

On this page you will find download links to all the OXPs. The download will create a .ZIP file. Unzip it and a new folder will appear. Open this folder and you will see a folder ending .oxp and usually a README file. Move the folder ending .oxp into the Oolite AddOns folder. Next time you load up Oolite the new features added by the OXP will be added to the game. Be sure to read the README file, as this will tell you what the OXP does. If you are updating an old version of an OXP on Oolite 1.69.1 onwards, hold down the SHIFT key whilst Oolite loads up for the first time after installing in order to ensure the cache is updated.

Below you will see a table of all the OXPs set out in alphabetical order. The link in the first column will take you to a Wiki Page giving you information on the OXP and a download link. If no Wiki page is currently available for the OXP, the link will take you directly to a download link.

The links in the next column will take you to Wiki Pages giving information on ships or stations added by the OXP. Many of the [[Oolite_Missions|Mission OXPs]] will contain lots of other ships, stations or weapons that are not listed here. The Wiki only gives information on the Ships listed in the galaxy wide "Jane's Spacecraft". Many military, criminal and corporate powers do not make information on the craft they build or use available to the galactic public! Below the Main Table is a list of download links to all the OXPs broken down by category.

Most OXPs can also be found at [http://oosat.alioth.net The Oolite Satellite Resource Site] (Oosat2) or the older [http://capnhack.com/hosting/oolite/Oolite/OoSat.html Captain Hack OoSat Site] (Oosat1). Please note however that neither of these sites have been updated for a long time, nor will they be. All updating is now done on this page of the Wiki. You should use the link shown on this page to get the latest version of the OXP. For example, the versions of Assassins.oxp, Ionics.oxp, Thargoid Wars.oxp and Spyhunter.oxp on the Captain Hack site are old versions (and contain bugs). The links on this page will take you to the latest versions.

== Table of all OXPs ==

{| width="100%" style="border: 1px solid #cfcfbf; background-color: #f0f0ff; padding: .5em 1em 1em; cellpadding: 0; cellspacing: 0; color: #000000; vertical-align: top; text-align: left;"
|-valign="top" bgcolor="#e7e7ff"
! Information / Download !! Ships !! Stations !! Short Description
|-valign="top"
| [[Aegidian's_Specials|Aegidian's Specials]]
| [[Mussurana]]
[[Asp_%28Oolite%29#Notable_features|Asp Mark II Special]]
|
|Ships. The powerful Mussurana and an improved Asp.
|-valign="top" bgcolor="#e7e7ff"
| [[Aegidian's_X-Ships|Aegidian's X-Ships]]
| [[Python_ET_Special|Python ET Special]]

[[Cobra_Mk.2_%28Oolite%29|Cobra Mk II]]

[[Asp_%28Oolite%29#Notable_features|Asp Mark II Special]]

[[Sidewinder_%28Oolite%29#Notable_featuresl|Sidewinder Special]]
|
|Ships. An improved Python, the experimental Cobra Mk II, the Asp Mark II Special and the Sidewinder Special.
|-valign="top"
| [http://www.box.net/shared/p9wjemvoc8 ''Amen Brick's Pirate Clan One: The Blitzspears (NEW 07/08)'']
| Assassin, Hoodlum, Mugger, Scoundrel and Spiv
|
|Ships. The first of the Pan-Galaxy Outlaw clans to rise through the leadership of some diabolical criminal genius. What are his, or indeed hers or, further indeed, its future plans? Will their nefarious example be followed by others? The answers are out there...
All ships in this version are playable. Future versions (probably modular for memory saving reasons) will have more clans, the ability to join clans (if I master the arcane art of programming), stations and missions. Stay untuned, folks.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/sm6fpqxsg4 ''Amen Brick's Megaships v1.2 (Amended 07/08)'']
| The Battleship, The Biodome, The Cruiseship, The Hospitalship, The Supercargo, The Superlifter and the Yacht:Amen Class
|
|Ships. Graceful giants cross the galaxies before our eyes. The forlorn Biodome, destined to forever wander the Ooniverse. The Cruiseship taking citizens to holiday planets. The Supercargo ferrying aid to the needy. The private Yacht filled with luxury and the prosaic Superlifter than helps giant ships get to their new homes or their final resting place. Now amended to make spectacular explosions as they try to dock less likely (sorry!)
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/E5Amigasoundpack01oxp.zip ''Amiga Replacement Sounds'']
|
|
| Sound Set, based on the sound set used in the Amiga version of the original Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Anarchies_OXP|''Anarchies.oxp'']]
| [[Hacker_Viper|Hacker Viper]]

[[Salvager_Phoenix|Salvager Phoenix]]

[[Salvager_Tugger|Salvager Tugger]]
| [[Hacker_Outpost|Hacker Outpost]]

[[Salvage_Gang|Salvage Gang]]

[[Sentinel_Station|Sentinel Station]]

[[Renegade_Station|Renegade Station]]
| Feature/Ships/Stations. Complete overhaul of Oolite's legal rating system. It gets harder to become clean again. But there are some new ways to achieve this as well: Hacker Outposts can be found in the higher tech [[Powers_and_Organisations#Anarchy_Worlds|Anarchy systems]], the criminals willing to clear a fugitive's legal record. For a price of course! Salvage Gangs are spread all over the Ooniverse, providing good equipment deals. Those in Anarchy systems offer a service similar to the Hacker Outposts as well. Sentinel Stations are placed in some of the worst Anarchies. But beware! Some of them have been overthrown by the pirates and are now Renegade Stations. Good news for the pirates among the players, because these are as close to a safe-haven for you as it gets! All of these also feature their own ships.
|-valign="top"
| [[AMS_OXP|Anti-Missile System]]
|
|
|Equipment. Adds the anti-missile system, designed to offer a defence against non-standard missiles via automatically firing interceptor darts (6 per launcher, replenishable). Requires [[Missile_Analyser|Missile Analyser OXP]] by Eric Walch.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/aphidv2.oxp_.zip ''Aphid Escort Service'']
|
|
|Ships. Adds the stylish Aphid escort service.
|-valign="top"
| [[Aquatics_OXP|Aquatics]]
| [[Manta_Ray|Manta Ray]], [[Shark|Shark]], [[Man_O%27_War|Man O' War]], [[Box_Escort|Box Escort]], [[Conger|Conger Cargo Hauler]], [[Hawksbill|Hawksbill Fuel Tanker]], [[HammerHead|HammerHead Hauler Carrier]], [[Barracuda|Barracuda]], [[LeviathanPlatform|Leviathan System Platform]], [[Orca|Orca Destroyer]]
|
|Ships/mission/station. Ships from the Aquarian Shipbuilding Corporation of Aqualina, G3. Also includes a brand new station (the Aquarian Shipbuilding Corp. HQ) plus a mission based out of it. And who knows, there may be a few more surprises in there too...
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/att1.zip ''Armoured Transport Type 1'']
| [[Gaundlet_Armoured_Transport_Type1|Gaundlet Armoured Transport Type 1]]

[[Gaundlet_Armoured_Escort_Viper|Gaundlet Armoured Escort Viper]]
|
|Ships. Convoys of well armed craft ferry gold and other valuables through the space lanes. Only a pirate with an Iron Ass would dream of attempting a robbery!
|-valign="top"
| [[The Assassins Guild OXP|Assassins Guild V1.3 (Updated)]]
| [[Deamon_Cruiser|Deamon Cruiser]]

[[Mongoose]]

[[Nemesis]]

[[Scorpion_Frigate|Scorpion Frigate]]
|[[Navy Station]]
| [[Oolite_Missions#The_Assassins_Guild|Missions]] / Ships / Stations / Planets. 21 missions involving murder to order in Galaxy 7, available to experienced Commanders amoral enough to gain admittance to the sinister [[Powers_and_Organisations#The_Assassins_Guild|Assassins Guild]]. Updated from the versions on Oosat1 & Oosat2.
|-valign="top" bgcolor="#e7e7ff"
|[[Asteroid_Storm|Asteroid Storm]]
|
|
| Feature / [[Oolite_Missions#Asteroid_Storm|Mission]]. Adds lots of different types of Asteroids to the Universe. A [[Oolite_Missions#Asteroid_Storm|Mission]] is also included, well suited to a novice Commander. A well known station in Galaxy 1 comes under threat from a large asteroid strike. The updated version fixes a bug that meant that only one new type of asteroid was being added. Now the intended twelve varieties appear in game. '''Note''': this OXP does not work in Oolite v.1.74+.
|-valign="top"
|[[Aurora]]
|[[Aurora]]
|
| BigTraders. Huge passenger ships for the wealthiest in society.
|-valign="top" bgcolor="#e7e7ff"
| [[Automatic_Chaff_System|Automatic Chaff System]] [[Image:New.gif|New]]
|
|
| Equipment. An enhanced chaff-based missile countermeasure system by [[User:Wyvern|Wyvern]], based on Thargoid's [[AMS_OXP|AMS]] and Ramirez's [[Missiles_and_Bombs|Chaff Dispenser]].
|-valign="top"
| [[Baakili_Far_Trader|Baakili Far Trader]]
| [[Baakili Far Trader]]
|
|Ships. Adds a dockable Alien ship.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/dropbox/bandersnatch_1_1.zip ''Bandersnatch v1.1'']
|[[Bandersnatch]]
|
|Ships. Adds a pirate capital vessel armed with plasma turrets. (Bugfixed at November 2009)
|-valign="top"
| [[Black_Monk_Monastery|Bank of the Black Monks]]
| [[Black_Monk_Gunship|Black Monk Gunship]]
| [[Black_Monk_Monastery|Black Monk Monastery]]
| Feature / [[Oolite_Missions#Bank_of_the_Black_Monks|Mission]]. Monks aboard well armed stations appear in advanced systems. Loans are offered, defaulters will be exterminated! Two versions of the OXP are available, the [http://www.box.net/public/z2ahfudnt3 Non-Shader Bank of the Black Monks OXP'] and the [http://http://www.box.net/shared/7twwbaelcc 'Shady Bank of the Black Monks OXP']. The Non-Shader Version will run on all versions of Oolite. The Shady version uses Shaders and requires Version 1.71 or higher of Oolite. Slow Systems will struggle to run the Shady Version, so if you find installing it is slowing your system down too much, then try the Non-Shady Version.
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth]]
| [[Behemoth]]
|
|Ships. Adds a dockable Navy Cruiser. Updated from the version on Oosat1.
|-valign="top"
| [[ADCK's_Behemoths|Behemoths - Shadered (By ADCK)]]
|
|
|Ships. Based on the above oxp, but with 2 new behemoths and shaders (Includes shaders which require Oolite 1.69 or later)
|-valign="top" bgcolor="#e7e7ff"
| [[Behemoth_Spacewar|''Behemoth Spacewar'']]
|
|
|Patch. Adds intelligence to the Behemoth and brings a combat with Thargoids
|-valign="top"
| [[BigShips_OXP|Big Ships]]
|
|
|Ships (ish). Adds the new role "bigTrader" to the game, designed for large ships which are unable to dock with stations due to their size. Also includes an AI which can be used for such ships, but DOES NOT include any ships of its own.
|-valign="top" bgcolor="#e7e7ff"
| [[Boa_II_Clipper_Class|Boa II Clipper Class]]
| [[Boa_II_Clipper_Class|Boa II Clipper Class]]
|
|Ships. A development of the Boa Class Cruiser, adding a third engine making it faster, at the cost of 25 TC of cargo space.
|-valign="top"
| [[Media:BoomslangWIP.zip|''Boomslang'']]
| [[Boomslang]]
|
|Ships. Adds a mid-range multi-role ship. Used by pirates and traders alike.
|-valign="top" bgcolor="#e7e7ff"
| [[Bounty_Scanner|Bounty Scanner]]
|
|
|Equipment. The Bounty Scanner adds bounty details (if any) to the targeting lock-box display when locked onto other ships.
|-valign="top"
| [[Bulk_Haulers|Bulk Haulers by ADCK]]
|
|
|Ships. Adds many Bulk Haulers to the game, including a retextured version of Aegidians Bulk Hauler as seen in the Oolite video on YouTube, which until recently has not been available to the public. (Requires [[BigShips_OXP|Big Ships]] and Includes shaders which require Oolite 1.69 or later)
|-valign="top" bgcolor="#e7e7ff"
| [[BuoyRepair|BuoyRepair1.02.5]]
| Armadillo Controller Guanako
|[[Buoy Repair Facility|Buoy Repair Facility]]
|Feature. Repair company for defect or destroyed nav-beacons (Updated 7/10/2009).
|-valign="top"
| [http://www.crimsonforge.co.uk/cloister/neocaduceus.zip Caduceus]
| [[Caduceus|Caduceus]]
|
|Ships. Adds the very expensive (and deadly) Caduceus, which has six broadside-mounted auto-targeting plasma cannons.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/seosu.zip ''Capisastra'']
| [[Capisastra_Defender|Capisastra Defender]]

[[Capisastra_Hauler|Capisastra Hauler]]

[[Capisastra_Warrior|Capisastra Warrior]]
|
|Ships. Capisatra pirates appear in Galaxy 4. [[Capisastra_OXP|More Information]].
|-valign="top"
| [[Captured_Thargons_OXP|Captured Thargons]]
|
|
|Equipment. Gives the possibility for player ships to carry and launch captured and reprogrammed Thargon robot fighters
|-valign="top" bgcolor="#e7e7ff"
| [[Cargo_Wreck_Teaser_OXP|''Cargo & Wrecks V1.4 (Updated April 2009)'']]
|
|
| Cargo. Adds lots of different types of cargo canisters.
|-valign="top"
| [[Cataclysm_OXP|''Cataclysm'']]
|
|
| Mission. "Cataclysm.oxp is a mission OXP that takes up the threads of the native Constrictor Hunt and Thargoid Plans missions, and sends you on a mission far bigger than anything you have done for the Navy so far. It gives you the opportunity to re-visit places you have visited before, and re-meet people you had contact with during these missions. And of course it will let you meet various other people, and lead you to a lot of new places, some of which you probably haven't visited before."
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/clearskies.oxp_.zip ''Clear Skies'']
|
|
| Utility. Reduces nebula effects. Handy if your system is finding it hard to run Oolite.
|-valign="top"
| [[Cobra_3.5|Chopped Cobra]]
| [[Cobra_3.5|Cobra Mk 3.5]]
|
|Ships. A slightly faster and tougher variation on the classic Cobra Mk III, at the price of a reduced cargo bay.
|-valign="top" bgcolor="#e7e7ff"
| [[Cobra_Clipper_SAR|Cobra Clipper SAR]]
| [[Cobra_Clipper_SAR|Cobra Clipper SAR]]
|
|Ships. A custom Cobra Mk III to rescue stranded Commanders.
|-valign="top"
| [http://oosat.alioth.net/files/cobra3njx.zip ''Cobra Mk III Njx'']
| [[Cobra_III_NjX|Cobra III NjX]]
|
|Ships. A faster, tougher variation on the Classic Cobra Mk III.
|-valign="top" bgcolor="#e7e7ff"
| [[Commies|''Commies v2.10'']] [[Image:Updated.gif|Updated]]
| [[Ray_Mk.I|Ray Mk I]]

[[Giant_Ray|Giant Ray]]

[[Astro_Mines|Mining Pods]]

[[Astro_Mines|Scavenger Rays]]

[[Sturgeon_Mk.I|Sturgeon Mk I]]

[[Worker%27s_Commuter|Worker's Commuter]]

| [[Astro_Mines|Astro Mines]]

[[CZGF|Collective Zero-G Factory]]

[[SLAPU|Solar Laboratory and Production Unit]]
|Ships / Stations. Commie systems have their own police forces, transports, stations and miners.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/pLists/hud.plist ''Compact HUD'']
|
|
|Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Condor'']
| [[Condor]]
|
| Ships. A very powerful police and Navy Cruiser.
|-valign="top"
| [http://oosat.alioth.net/files/CustomSounds.zip ''Custom Sounds'']
|
|
| Sound Set. The largest of the currently available sound sets, this pack replaces or adds over 40 sounds, featuring additional music and extensive use of a calm female computer voice to warn the Commander of alarming events.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/dwcobra3HiRes.zip ''Dark Wheel Cobra''] -
([http://oosat.alioth.net/files/dwcobra3.zip alternative lo-end version])
|[[DWCobra|Dark Wheel Cobra]]
|
|Ships. A custom Cobra Mk III model, as seen on the cover of the Elite Manual.
|-valign="top"
| [[Deep_Space_Dredger|''Deep Space Dredger 2.3'']]
| [[Sabre]]
| [[Deep_Space_Dredger|Deep Space Dredger]]
|Ships / Stations. Adds dockable Space Dredgers to the space lanes, defended by a squad of Saber fighters. Version 2.3 has new, improved textures.
|-valign="top" bgcolor="#e7e7ff"
| [[DeepSpacePirates|''Deep Space Pirates'']]
|
|
|Feature. Normally in Oolite ships do not appear outside the space lanes. This OXP adds ships outside the space lanes. As no police patrols extend this far out pirates and other unpleasant characters can be found in deep space.
|-valign="top"
| [[Deepspace_Ships|''Deepspace Ships'']]
|
|
|Oolite Ships replacement set. Replaces the default ships with new textures.
|-valign="top" bgcolor="#e7e7ff"
| [[Deposed_OXP|''Deposed 1.3.4'']]
|
|
| [[Oolite_Missions#Deposed|Mission]]. A series of missions set in Galaxy 4 for an experienced Commander. This version is now mission-offering. compatible with other OXPs.
|-valign="top"
|[http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Dictators'']
| [[Imperial_Censor|Imperial Censor]]

[[Imperial_Freighter|Imperial Freighter]]

[[Imperial_Lictor|Imperial Lictor]]

[[Imperial_Quaestor|Imperial Quaestor]]

[[Imperial_Tanker|Imperial Tanker]]

[[Junta_Enforcer|Junta Enforcer]]

[[Revolutionary_Guard|Revolutionary Guard]]
| [[Imperial_AstroFactory|Imperial AstroFactory]]
| Ships / Stations. Dictatorship systems gain their own police forces, supply craft and stations.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Diso.zip ''Diso'']
|
|[[Navy Station]]
| Planets / Stations. Extra planets and stations are added to the Diso system in Galaxy 1.
|-valign="top"
| [[Display reputation OXP|''Display Reputation v1.1'']]
|
|
| Feature. Displays your passenger and contract reputation in your ship's manifest.
|-valign="top" bgcolor="#e7e7ff"
| ''Dr HUD'' [http://sancho.dk/oolite/Dr_HUD_Cmk3.zip Cobra Mk III version], [http://sancho.dk/oolite/Dr_HUD.zip Custom version]
|
|
| Alternative HUD.
|-valign="top"
| [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|Docking Clearance]]
|
|
| Feature. Sets the docking clearance on for all stations in Oolite. Click on [[Oolite_Docking_Clearance_Protocol_%28v1.72_or_later%29|this link]] for further explanation.
|-valign="top" bgcolor="#e7e7ff"
| ''Dr HUD'' [http://sancho.dk/oolite/Dr_HUD_Cmk3.zip Cobra Mk III version], [http://sancho.dk/oolite/Dr_HUD.zip Custom version]
|
|
| Alternative HUD.
|-valign="top"
| [[Dragon|Dragon Assault Craft (Updated 9/8/08)]]
| [[Dragon|Dragon Assault Craft]]
|
| Ships / Equipment. Adds the Dragon Assault Craft, a heavy combat ship available in several different paint-jobs. Also adds the Military Smart Missile, an improved Hard Head Missile with more bang for your Credit. Both the ship and missile are available to the player and NPCs alike.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.mediafire.com/?sharekey=ca166c7e38ef78c6e7c82ed4b8f0c380e04e75f6e8ebb871 ''Dragonfly/Firefly S.T'']
| [[Dragonfly S.T /Firefly S.T]]
|
|Ships. Adds the Dragonfly S.T and also the much faster Firefly S.T variant. Small fast ideal ship for pirates or bounty hunters.
|-valign="top"
| [[Drones_OXP|Drones]]
|
|
|Weapons. Three new autonomous drones to help the player (and NPCs) in combat. Fire and forget, with targeting taken from the ships scanning computers. Variants are the combat drone (standard fighting drone), the kamikaze drone (upgraded with a low yield warhead) and anti-Thargoid drone (GalCop commission, with stronger lasers and better speed and manoeuvrability, plus battle computer optimisation to seek and destroy Thargoid vessels). All can be recovered and possibly re-used if they survive battle.
|-valign="top" bgcolor="#e7e7ff"
| [[Eagle Mk II]]
| [[Eagle Mk II]]
|
| Ships. Adds the cheap Eagle Mk II escort vessel in several different versions, including an enhanced SE.
|-valign="top"
| ''[http://www.box.net/shared/xkltqit3oj Eagles Mk's I to IV (By ADCK)]''
|
|
|Adds 4 Eagle Long Range Fighters to the game, There are 8 different colours to each Eagle, and 4 player versions. Made by ADCK. (Includes shaders which require Oolite 1.69 or later)

|-valign="top" bgcolor="#e7e7ff"
| [[Energy_Equipment_OXP|Energy Equipment]]
|
|
|Equipment. The emergency charge device - a pylon-mounted top-up for the ships systems, and the emergency energy unit - an internally fitted automatically triggered top-up when the juice runs low.
|-valign="top"
| [http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon]
|
|
| Equipment. Mark a position in space by deploying a pylon mounted beacon.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.arcadia-digital.net/steve/Oolite/Ships/Executive%20SpaceWays%20v2.2.zip ''Executive Spaceways'']
| [[Delta_Long-Range_Escort|Delta Long-Range Escort]]

[[Gemini_Escort|Gemini Escort]]

[[Starseeker_Personal_Shuttle|Starseeker Personal Shuttle]]

[[Strelka_CruiseLiner|Strelka Cruise Liner]]

[[Trident_Executive_Shuttle|Trident Executive Shuttle]]
|
| Ships. Adds the Executive SpaceWays fleet of ships. Commanders may consult the [[Executive_SpaceWays|Executive SpaceWays Sales Brochure]] for further details.
|-valign="top"
| [[External Views OXP|External Views]]
|
|
| Utility. Adds better outside views to all the Classic Elite Ships. Warning: Do '''not''' use with Oolite 1.70 and above! From Oolite 1.70 onwards improved outside views have been added to the game itself, so you don't need this OXP anymore. Just throw it away.

|-valign="top" bgcolor="#e7e7ff"
| [[Far_Arm_ships|Far Arm ships]]
| [[Far_Arm_Sunracer|Sunracer]] 
[[Far_Arm_Scow|Scow]] 
[[Far_Arm_Tanker|Tanker]] 
[[Far_Arm_Corsair|Corsair]] 
[[Far_Arm_Dart|Dart]] 
[[Far_Arm_Hunter|Hunter]] 
[[Far_Arm_Cruiser|Cruiser]] 
[[Far_Arm_Titan|Titan]] 
[[Far_Arm_Manchi_Vulture|Manchi Vulture]] 
[[Far_Arm_Manchi_Wasp|Manchi Wasp]]
|
| Ships. This OXP adds 10 ships, inspired by [http://en.wikipedia.org/wiki/Space_Rogue Paul Neurath's Space Rogue] to the Ooniverse. There is also a new alien race called the Manchi, who pilot ships of bizarre design. Released under the [http://creativecommons.org/licenses/by-nc-sa/3.0/ Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported] License.

|-valign="top"
| [[Far Star OXP|Far Star]]
| [[Far_Star_Murderer|Far Star Murderer]]
|
| Ships. A mid-range fighter / trader, with a fair sized cargo bay.

|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/d57y0uip74 ''Farsun v1.05'']
|
|
| Utility. Places suns further away from the planet than standard Oolite. New, improved, and fully compatible with Novae!

|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/ferdelance_ng.oxp.zip ''Fer de Lance NG'']
|
|
| Ships. Adds a more powerful version of the Fer de Lance with several custom paint jobs.

|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/ferdepai.oxp_.zip ''Ferdepai'']
| [[Ferdepai]]
|
| Ships. Adds a new fighter / trader to Galaxy 2.

|-valign="top"
| [http://www.msdownload.co.uk/Oolite/FighterHud.zip ''Fighter HUD Mk. II'']
| [[Fighter_HUD_%28Oolite%29|Fighter HUD]]
|
| Alternative HUD.

|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Firewasp.zip ''Firewasp'']
| [[Firewasp]]
|
| Ships. A fast interceptor.

|-valign="top"
| ''[[Flying Dutchman OXP|Flying Dutchman]]''
| [[Griff Wireframe Cobra]]
|
| Feature / Ships. Adds the small chance to meet a ''Ghost Ship'' in the Ooniverse. What is it? Some claim that it's the ghost of Commander Peter Jameson, reported lost at the end of the last Thargoid War, others that it is simply a manifestation of all those lost souls who were trapped in the trackless depths of interstellar space. One common story is the trail of bad luck and hideous deaths that follow in the wake of the ship's sightings...

|-valign="top" bgcolor="#e7e7ff"
| ''[[Freaky Thargoids OXP|Freaky Thargoids]]''
|
|
| [[shaders in Oolite|Shader]] example, requires Oolite 1.69. With this OXP installed, Thargoids will use the new Shaders.

|-valign="top"
| [http://www.box.net/shared/e43ftmvqmr ''Free Trade Zone'']
|
| [[Free_Trade_Zone|Free Trade Zone]]
| Stations. Adds an independent trading post of dubious legality to Multi-Government systems.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/fsr.zip ''Frog Space Rickshaw'']
| [[Frog_Space_Rickshaw|Frog Space Rickshaw]]
|
| Ships. Adds a chatty space taxi service to the safer systems. [[Image:Updated.gif|Updated!]] Updated with a new download link which was broken before.

|-valign="top"
| [[Fuel_Collector_OXP|Fuel Collector]]
|
|
|Equipment. The Fuel Collector enables you to very slowly gather fuel whilst cruising in space, whether en-route to a station, or in interstellar space should a witch-jump malfunction occur. You can also gather any unburnt fuel from destroyed ships as well as tap fuel from derelict or abandoned ships.

|-valign="top" bgcolor="#e7e7ff"
| [[Fuel_Station_OXP|Fuel Station]]
|
|
|Station. Adds fly-thru Fuel Stations and Fuel Satellites near the witchpoint and along route one.
|-valign="top"
| [http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Fuel Tank'']
|[[Fuel Tank]]
|
| Equipment. Mounts in place of a missile, to top up 3 light years of fuel.

|-valign="top" bgcolor="#e7e7ff"
| [[Galactic_Navy_OXP | Galactic Navy]]
| [[Navy_Frigate|Navy Frigate]]

[[Navy_Medical_Ship|Navy Medical Ship]]

[[Navy_Minesweeper|Navy Minesweeper]]

[[Navy_Transport|Navy Transport]]
| [[Navy_SecCom_Station|Navy Sector Command Station]]
| Ships and Stations. A selection of ships and space stations that adds to the already formidable arsenal of the Galactic Navy. Allows commanders to join the Navy Reserves. Requires the Behemoth OXP.

|-valign="top"
| [[Gates_OXP|Gates]]
|
|
|Station. Adds short-cut jump gates to suitable systems, speeding journeys between the main station and witchpoint for a fee of only 250Cr.

|-valign="top" bgcolor="#e7e7ff"
| [[Generation_Ships_OXP|''Generation Ships'']]
| [[Generation_Ships_OXP|Generation Ships]]
|
| Ships. The mythical Generation Ships appear from time to time.

|-valign="top"
| [[Globe_station|Globe Station2.0]]
|
| [[Globe_station|Globe Station]]
| Stations. A new type of station appears at advanced systems. (Updated 22/10/2009)

|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/greekshipset1.zip ''Greek Ships'']
| [[Penelope_Class_Freighter|Penelope Class Freighter]]

[[Telemachus_Class_Escort|Telemachus Class Escort]]

[[Ulysses_Class_Interceptor|Ulysses Class Interceptor]]
|
|Ships. A large trade ship and escorts. Sometimes also used by pirates.

|-valign="top"
| [[Griff_ArcElite|Griff ArcElite]]
|
|
|Ships. New versions of the native Oolite ships textured & shaded to resemble how they originally appeared in the Acorn Archimedes version of Elite
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/k2lvh3enuy Griff's Explosion Debris]
|
|
|Flavour. Box.Net link to an OXP that adds new alloy & debris models to exploding ships. The oxp features some cool scripting and AI coding by Thargoid which chains together various types of exploding junk in some pretty dazzling ways. For more information see [http://www.aegidian.org/bb/viewtopic.php?t=5650 this thread] on the BB.
|-valign="top"
| [[Griff_Industries|Griff's Normalmapped Ships]] [[Image:Updated.gif|Updated]]
|
|
| This is where you can get your hands on some of the best looking ships for Oolite, using shaders and normal-mapping. See the OXP page for a gallery of all the ships. This OXP requires [http://developer.berlios.de/project/showfiles.php?group_id=3577&release_id=13778 Version 1.71 of Oolite] or higher.

|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/griffin2.oxp.zip ''Griffin Mk.II]
| [[Griffin_Two_%28Oolite%29|Griffin Two]]
|
|Ships. Adds the Griffin Mk II from Frontier.

|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/GrittyCoriolis.oxp.zip ''Gritty Coriolis'']
|
|
|Stations. The Corolis Station gets a more detailed texture.
|-valign="top" bgcolor="#e7e7ff"
| [http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip ''G-HUD Mk2'']
|
|
|Alternative HUD.
|-valign="top"
| [[Media:halsis.zip|''Hal's Hot Sister'']]
|
|
|Sound Set, featuring a female cockpit voice.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/boyracers.zip ''Hatchling Boyracers'']
| [[BoyRacer|Boy Racer]]
|
|Ships. The talkative (and often insulting) Boyracers appear in the more advanced systems.
|-valign="top"
| [http://www.mediafire.com/file/mm2ekntynom/Hawksound.zip ''Hawksound'']
|
|
|Sound Set. Clean sounds. Quality female computer voice, new weapon, damage and some station interface sounds.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/Herald.zip ''Herald'']
| [[Herald_Military_Gunboat|Herald Military Gunboat]]
|
|Ships. A powerful police and Navy interceptor.
|-valign="top"
| [[Hired_Guns_OXP|Hired Guns]]
|
|
| Weapons/Equipment. Gives the chance to agree a contract for a pair of ships to accompany you on your next journey and fight on your behalf alongside you.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/tugs.zip ''Hognose Tugships'']
| [[Hognose]]
|
|Ships. The chatty tug ships can be seen towing broken down ships.
|-valign="top"
|[[HoOpy Casino]]
|
|[[HoOpy Casino]]
|Stations. HoOpy Casinos appear near the station in advanced systems. Commanders who chose to dock can win or lose credits in games of chance.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.mediafire.com/?2vgjwpj6xdy ''Hotrods v0.52c''], [http://www.box.net/shared/j2r6frlvq1 ''Hotrods v0.52d'']
|
|
|Ships. Classic Elite Ships appear with custom paint jobs. Includes also a large number of custom and standard racing vehicles and a spacegang in tiger-getup that doesn't like the player. A rework, and a new name, for Custom Paints & Racers. Replaces [http://capnhack.com/hosting/oolite/Oolite/OXPs/custpaint1.zip ''Custom Paint Jobs'']
|-valign="top"
|[[Hyperradio_js_OXP | Hyperradio v1.17]]
|
|
|Equipment. This device gives you the ability to listen to your own music. It is expandable by musicpacks that can be separately installed and compatible to OXPConfig, RepairBots and Snoopers. (Updated 11/02/2010)
|-valign="top" bgcolor="#e7e7ff"
| [[Icarus (Oolite)|Icarus]]
| [[Icarus (Oolite)|Icarus]]
|
|Ships. Adds the Icarus Light Trader from [[Seldar Shipyards]]. A small fighter / trader based on blueprints from the lost Solice system.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/illicit_unlock.oxp.zip ''Illicit Unlock'']
|
|
|Utility. Allows the player to fly all the Classic Elite Ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Imperial_Courier_%28Oolite%29|Imperial Courier]]
| [[Imperial_Courier_%28Oolite%29|Imperial Courier]]
|
|Ships. The powerful Imperial Courier from Frontier, constructed by [[Seldar Shipyards]]. Updated from the version on Oosat1.
|-valign="top"
| [[Interstellar help OXP|''Interstellar help'']]
|
|
|Feature. Allows you to help out some traders who got stuck in interstellar space without fuel. You will be rewarded.
|-valign="top" bgcolor="#e7e7ff"
| [[ionics_OXP|Ionics 1.2.3]]
| [[Ionics_Funnelweb|Ionics Funnelweb]]

[[Ionics_Huntsman|Ionics Huntsman]]

[[Ionics_Redback|Ionics Redback]]

[[Ionics_Whitetail|Ionics Whitetail]]
|
| [[Oolite_Missions#Ionics|Mission]]. A series of missions set in Galaxy 2 featuring the Ionics Company of Zaria. [[Ionics_OXP|More Information here.]] Updated on 7-4-2009. This version is now compatible with multi-mission offering of other OXPs.
|-valign="top"
| [[Ixian_Ships|''Ixian Ships'']]
| [[Ixian_Battle_Cruiser|Ixian Battle Cruiser]]

[[Ixian_Bezerka|Ixian Bezerka]]

[[Ixian_Freighter_MK1|Ixian Freighter Mk I]]

[[Ixian_Gunship|Ixian Gunship]]

[[Ixian_No-Ship_Mark_I|Ixian No-Ship Mk I]]
|
|Ships. A set of ships from Dune. Used by pirates and traders alike.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/jabberwocky.zip ''Jabberwocky'']
|
|
|Ships. Adds the powerful Jabberwocky fighter / trader.
|-valign="top"
| ''[[JavaScript test OXP|JavaScript test]]''
|
|
| [[Scripting Oolite with JavaScript|JavaScript scripting]] example, requires Oolite 1.68.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/dropbox/kestrel_falcon1_71_0.zip ''Kestrel&Falcon v1.71.0'']
| [[Kestrel]]
[[Falcon_%28Oolite%29|Falcon]]
|
| Ships. Adds a powerful Star Wars style Falcon, used by pirates and traders alike, and an interceptor used by the Police and Navy. Both models are also available on the open market. Improved from the older Kestrel.oxp and Falcon.oxp models, still available from the [http://www.box.net/public/b2tic3tjsk#1:4083657 ''Benulobiweed''] main download area.
|-valign="top"
| [[Killit_OXP|''Killit'']]
|
|
| Weapons. Adds a bunch of insane super weapons.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.crimsonforge.co.uk/cloister/kirin.zip ''Kirin'']
| [[Kirin]]
|
| Ships. Adds a heavy military hauler, CV and XM versions used by both pirates and traders.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/kleptohud.oxp.zip ''Klepto-HUD'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://sancho.dk/oolite/lane_legal.zip ''Lane Legal Racers'']
| [[Krait]]

[[Mamba]]

[[Sidewinder]]
|
|Ships. Adds NPC versions of ships from different [[Racers#Listing_of_sponsored_teams|racing teams]].
|-valign="top"
| [http://capnhack.com/hosting/oolite/dropbox/Lave171.zip ''Lave v1.71'']
|
|
| Planets. Gives the Lave System a make-over adding all the features described in The Dark Wheel novella included with the original Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Lave_Academy_OXP|Lave Academy]]
|
|
| Station. Adds the Lave Academy Orbital station above Lave (and now other planets), with three new mini-game tests of the Commanders' ship skills.
|-valign="top"
| [[Media:Llama.zip|Llama]]
| [[Llama]]
|
|Ships. Adds the Llama fighter / trader. Updated from the version of Oosat1 to fix a small bug.
|-valign="top" bgcolor="#e7e7ff"
|[[Localhero_OXP|Localhero v1.05]]
|
|
|Mission. Adds a mission campaign in the first galaxies. (Updated 9.04.2008)
|-valign="top"
| [[LongWay_OXP| ''Long Way Around 1.1'']]
|
|
| [[Oolite_Missions#The_Longway_Mission|Mission]]. A transport mission well suited to the novice in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Longshot.zip ''Longshot'']
| [[Longshot]]
|
|Ships. Adds the Longshot fighter / trader, regarded by many as a cheaper alternative to the Cobra Mk III.
|-valign="top"
| [[Lovecats.oxp|''Lovecats 1.2'']]
|
|
| [[Oolite_Missions#Love_Cats|Mission]]. Love and betrayal amongst the feline races of Galaxy 4. A fast ship, fuel injectors, fuel scoops and a hard heart are advised before you tangle with these cats! Version 1.1 missionclash proof.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/mPakRedux.zip ''M-Pack (rusties)'']
|
|
| Ships. Adds rusty versions of all the Classic Elite ships. Bargain basement prices, although these old bangers are in a poor condition compared to a brand new model. Engines may be worn out reducing maximum speeds and shield generators are frequently held together with duck-tape. When you try to trade one of these old rust buckets in at the shipyards, you may also find that the trade-in value is reduced. None the less, they are cheap and can still haul cargo between the stars.
|-valign="top"
| [http://oosat.alioth.net/files/manta.oxp_.zip ''Manta'']
| [[Manta]]
|
|Ships. Adds the Manta light escort craft.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/marett_vol1.zip ''Marett Space Corporation'']
| [[Adder_Mk_II|Adder Mk II]]

[[Mosquito_Trader|Mosquito Trader]]

[[Mosquito_Sport|Mosquito Sport]]
|
|Ships. A collection of fighters and medium traders from Marett Space Corps.
|-valign="top"
| [http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip ''Medusa Hud'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/megawalnutdash.oxp.zip ''Mega-Walnut Dashboard'']
|
|
| Alternative HUD.
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Merlin'']
| [[Merlin_%28Oolite%29|Merlin]]
|
|Ships. An interceptor used by the Police and Navy, but also available on the open market.
|-valign="top" bgcolor="#e7e7ff"
| [[Media:MildAudio.oxp.zip|''MildAudio'']]
|
|
| Sound Set.
|-valign="top"
| [[Military_Fiasco|Military Fiasco]]
| [[Basilisk]]

[[Hydra]]

[[Leviathan]]

[[Rattle_Cutter|Rattle Cutter]]

[[Wolf_Mk.2_%28Oolite%29|Wolf Mk II Paragon]]
|
| [[Oolite_Missions#Military_Fiasco|Mission]]. A mission for the Navy available to a Commander with more than 1,000 kills. Also equips the Navy with powerful cruisers. Version 2.0 is updated version of the Military OXP over the version on Oosat2. Use this one, as the old version can clash with other Mission OXPs. You must also use the Updated version of [http://oosat.alioth.net/files/Murgh-Xships.zip ''Murgh's X-Ships''] to play this OXP.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/gwxstations.oxp.zip ''Military Station'']
|
| [[Military_station|Military Station]]
|Stations. Well armed Military Stations appear in the more advanced systems.
|-valign="top"
| [http://www.msdownload.co.uk/Oolite/stingray.zip ''Military Stingray'']
| [[Stingray_%28Oolite%29|Stingray]]
|
|Ships. Adds the Military Stingray to the GalCop Navy fleet. Second hand versions are sometimes available on the open market.
|-valign="top" bgcolor="#e7e7ff"
| [[Milspec HUD|Milspec HUD]]
|
|
| Alternative HUD. Adds targeting aids, emphasis on functionality.
|-valign="top"
| [[Missiles and Bombs|Missiles and Bombs]]
|
|
|Equipment. Adds the Cascade stand-off missile, Multiple-warhead anti-Thargoid missile, Frag Mine, Frag Missile, EMP Missile and short-range defence missile to the game. The new weapons are available to the player and NPCs alike.
|-valign="top" bgcolor="#e7e7ff"
| [[Missile_Rack_OXP|Missile Rack]]
|
|
|Weapons. Pylon mounted racks of three mini-missiles. Smaller and less powerful than standard missiles, but effectively triple the available armaments a ship can carry.
|-valign="top"
| [http://sancho.dk/oolite/missionaries.zip ''Missionaries v1.1'']
| [[Happy_Eye_Pulpit_Pod|Happy Eye Pulpit Pod]]
|
|Ships. Clerics of four faiths are added to the Universe, spamming Commanders with requests to worship their Gods.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/monument.zip ''Monument'']
|
|
|Feature. A monument to famous Commanders can sometimes be seen near the Sun.
|-valign="top"
| [http://capnhack.com/hosting/oolite/dropbox/morrigan101.zip ''Morrigan'']
|
|
|Ships. Adds a vast trade ship to the Universe. (v 1.0.1, Bugfixed december 2009)
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds2.zip ''Murgh's Replacement Sounds'']
|
|
| Sound Set.
|-valign="top"
| [[Murgh_Xships OXP|''Murgh's X-Ships'']]
| [[Bandy-Bandy]]

[[Chuckwalla]]

[[Eel_Rapier|Eel Rapier]]

[[Taipan]]
|
|Ships. A fast courier craft and two light escort ships are added. Updated from the version on Oosat1. You MUST use this version for the [[Military_Fiasco|Military Fiasco]] Mission to run properly!
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Navy Starships'']
|
|
|Ships. Arms the Navy with powerful cruisers including a docakable Star Trek style Starship.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/newships.oxp.zip ''New Ships'']
| [[Hamadryad]]

[[Josher]]

[[Naga]]

[[Ringhals]]
|
|Ships. Adds a variety of mining and trade ships seen in previous versions of Elite.
|-valign="top" bgcolor="#e7e7ff"
| [[Neolite Ships]]
|
|
| Oolite ships replacement set.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip ''NG HUD'']
|
|
| Alternative HUD.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/nuvipers.zip ''Nu Vipers'']
| [[GalCop_Viper_Mark_II|GalCop Viper Mark II]]
[[GalCop_Viper_Cruiser|GalCop Viper Cruiser]]
|
|Ships. Increases the types of Viper patrol ships appearing in the space lanes and defending Stations.
|-valign="top"
| [[Nukes.oxp|Nuclear Torpedos]]
|
|
| Equipment. Adds some powerful, but slow moving, missiles.
|-valign="top" bgcolor="#e7e7ff"
| [[Old Ships]]
| [[Bushmaster_Miner|Bushmaster Miner]]

[[Cat_%28Oolite%29|Cat (Cougar)]]

[[Chameleon_%28Oolite%29|Chameleon]]

[[Ghavial_%28Oolite%29|Ghavial]]

[[Iguana_%28Oolite%29|Iguana]]

[[Monitor_%28Oolite%29|Monitor]]

[[Ophidian_%28Oolite%29|Ophidian]]

[[Salamander_%28Oolite%29|Salamander]]
|
|Ships. A collection of ships from ArcElite and Elite-A.
|-valign="top"
| [[Old_Ships_2010|Old Ships 2010]] [[Image:Updated.gif|Updated]]
| [[Bushmaster_Miner|Bushmaster Miner]]

[[Cat_%28Oolite%29|Cat (Cougar)]]

[[Chameleon_%28Oolite%29|Chameleon]]

[[Ghavial_%28Oolite%29|Ghavial]]

[[Iguana_%28Oolite%29|Iguana]]

[[Monitor_%28Oolite%29|Monitor]]

[[Monitor2|Monitor 2]]

[[Ophidian_%28Oolite%29|Ophidian]]

[[Salamander_%28Oolite%29|Salamander]]
|
|Ships. A new version of Murgh's Old Ships, retextured by P.A.Groove. Includes a bonus ship, the Monitor 2.
|-valign="top" bgcolor="#e7e7ff"
| [[Oo-Haul]]
| [[L-Crate_Hauler|L-Crate Hauler]]
|
|[[Oolite_Missions#Oo-haul_Escort_Missions|Mission]]. Vast corporate bulk haulers can be seen in the space lanes. Commanders with a respectable Elite rating who chose to dock with a [[Pi-42]] base may also be offered missions to escort one of these haulers safely to its destination. You must also install the [[Your Ad Here!|Your Ad Here!]] OXP for this OXP to work properly.
|-valign="top"
| [http://wiki.alioth.net/index.php/Image:OoliteItaliano_v1.3.zip ''Oolite Italiano v1.3'']
|
|
|Miscellaneous. First ever Oolite localization OXP. Requires Oolite v1.73 or later.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/ch3lsepk9k ''Oolite Russian v1.0'']
|
|
|Miscellaneous. The second Oolite localization OXP. Requires Oolite v1.72 or later.
|-valign="top"
| [[Orb]]
| [[Orb]]
|
|Ships. Adds a new alien race, which may (or may not) help GalCop in the battle against the Thargoids.
|-valign="top" bgcolor="#e7e7ff"
| [[Media:Orbits.zip|''Orbits'']]
|
|
|Utility. Positions planets on orbits around the sun.
|-valign="top"
| [[Ore_Processor|''Ore Processor'']]
|
|
| [[Ore_Processor|Equipment]]. When mounted to a ships fuel scoop systems extracts valuable materials from asteroid fragments. A must for any Commander working as a miner.
|-valign="top" bgcolor="#e7e7ff"
| [[Orisis]]
| [[Orisis]]
|
|BigTraders. New passenger liners that ferry passengers around.
|-valign="top"
| [http://oosat.alioth.net/files/outrider.zip ''Outrider'']
| [[Outrider_%28Oolite%29|Outrider]]
|
| Ships. A medium fighter produced by the [[Taranis Corporation HQ (Oolite)|Taranis Corporation]].
|-valign="top" bgcolor="#e7e7ff"
| [[OXPConfig|OXPConfig1.08]]
|
|
| Tools/Utility. This tool gives you the ability to configure several oxps. It changes internal (local) settings of the oxps to enable (or disable) logging or audio functions and special settings to recognize errors or to avoid clashes. (Updated 04/09/2009)
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Pallas'']
| [[Pallas]]
|
|Ships. A fast but lightly shielded fighter.
|-valign="top" bgcolor="#e7e7ff"
| [[P.A. Groove Stations OXP]]
|
|
|Stations. Adds lots of different types of Coriolis and Dodec Stations.
|-valign="top"
| [http://oosat.alioth.net/files/Pelamis.zip ''Pelamis'']
| [[Pelamis]]
|
|Ships. Adds the Pelamis trade ship.
|-valign="top" bgcolor="#e7e7ff"
| [[Personalities OXP|''Personalities'']]
|
|
| Ships. Adds a bunch of unique, well-known personalities to the Ooniverse. Keen to meet yourself in your game (or have others meet yourself in their game)? Submit your own personality in the OXP's thread on the Oolite BBs.
|-valign="top"
| [http://oosat.alioth.net/files/Phoenix.zip ''Phoenix'']
| [[Phoenix]]
|
|Ships. A strange ship, built from salvaged parts from various Serpent Class ships.
|-valign="top" bgcolor="#e7e7ff"
| [[Pirate Coves OXP|Pirate Coves]]
|
| [[Pirate Coves OXP|Pirate Coves]]
| [[Oolite_Missions#Pirate_Coves|Mission]]. Some rock hermits in the more dangerous systems have been taken over by pirates. Traders coming too close are likely to be assaulted by scrambled pirates keen to relive them of their cargo.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip ''Pirate Traps'']
|
|
|Feature. To combat piracy GalCop sometimes deploys dummies of trade ships. Pirates who fire on them have their details transmitted to the police and face large fines.
|-valign="top" bgcolor="#e7e7ff"
| [[Planetfall_OXP|Planetfall]]
|
|
|System. Allows the player to land on and trade at the planets and moons of each system.
|-valign="top"
| [[Pods_OXP|Pods]]
|
|
|Cargo. Many new varieties of cargo pod, including fuel, missile, bulk, and empty, plus pods which take a couple of goes to scoop, jam in the fuel scoop, explode and even bring a trumble. Designed as a balanced OXP, to add some positives and some negatives to cargo scooping, to give more realism. Those of you who also use the [[UPS_Courier|UPS Courier]] OXP can also [http://www.box.net/shared/sytn2yhpu0 download a little add-on] to the OXP that applies some of the new pods to UPS ones too (UPS Courier needs to be installed for the add-on to work).

|-valign="top" bgcolor="#e7e7ff"
| [[Probe_OXP|Probe]]
|
|
|Equipment. A long-range probe missile, flies away from the ship and scans at ranges of 50km and 100km, reporting ships found back to the ship. It then turns around and comes back, ready for fuel scooping and re-use.
|-valign="top"
| [http://oosat.alioth.net/files/PTI.zip ''Pteradyne Technologies Ships''] - ([http://oosat.alioth.net/files/PTI_bugfix11.zip ''bug fix''])
| [[Excalibur]]
[[Paladin]]
|
|Ships. A powerful combat ship, the Excalibur is offered for sale on the open market. The Paladin is the even tougher Military version, although sometimes these ships fall into the wrong hands.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/pcc.oxp.zip ''Python Class Cruiser]
| [[Python_Class_Cruiser|Python Class Cruiser]]
|
|Ships. A large powerful trade ship, which can also hold its own in battle.
|-valign="top"
| ''[[Media:Python_Class_Cruiser.oxp.zip|Python Class Cruiser version 2.6]]''
|
|
| As above, but features [[shaders in Oolite|Shaders]]. Shaders require Oolite 1.69 or later.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/racers.oxp.zip ''Racers'']
|[[Chicaneer Mk II]]

[[Chicaneer Mk IV]]

[[Dragster Mk I]]

[[Dragster Mk II]]
|
|Ships. Adds dedicated racing ships to the Universe. Although very fast, these ships are pure racers with no cargo bays and light shields. The focus on pure speed makes them ill-suited to combat or trading roles.
|-valign="top"
| [[Ring_Racer_OXP|Ring Racer]]
|
|
| Mission. Corporate Systems Ring Racing League in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [[RingPod.oxp|''Racing Rings'']]
|
|
|Feature. Adds Racing Rings to the Galaxy 1 systems of Lave and Zanoce. Fly through the rings in order and completing the race circuit will transmit the competitors' time.

|-valign="top"
|[[Ramon's_Anaconda|Ramon's Anaconda]]
|[[Ramon's_Anaconda|Ramon's Anaconda]]
|
| Ship. This is a fantastic re-imagining of the Anaconda freighter, made by Ramon, with assistance by Griff. Check out its special features!

|-valign="top" bgcolor="#e7e7ff"
|[[Random_Docking_Music_OXP|Random Docking Music]] [[Image:New.gif|New!]]
|
|
| Utility. Plays a randomly selected music track on activating docking computers (slow dock), from a list set inside the OXP.

|-valign="top"
|[[Random Hits OXP|Random Hits Version 1.3.6 Beta (Updated 5/8/09)]]
|[[GalMine Hopper|GalMine Hopper]]

[[GalMine AutoMiner|GalMine AutoMiner]]

[[GalMine Cargo Drone|GalMine Cargo Drone]]
|[[Space Bar|Space Bar]]
|[[Oolite_Missions#Random_Hits|Missions]] / Ships / Stations / Feature. Adds [[Space Bar|Seedy Space Bars]] to the space lanes of all Anarchy Systems. Commanders who chose to dock with one can view a Bulletin Board displaying details of the local Galaxies Most Wanted Criminals. Large bounties are paid for killing or capturing one of these offenders. Missions are procedurally generated using a database of over 40,000 words creating over one trillion different Bulletin Board Advertisements. Missions are therefore effectively never-ending. This OXP requires [http://developer.berlios.de/project/showfiles.php?group_id=3577&release_id=13778 Version 1.72.2 of Oolite].

|-valign="top" bgcolor="#e7e7ff"
| [[RegistrationID|Registration ID]]
|
|
| Flavour. All Oolite standard ships now have ID tags.. You need at least Oolite 1.73 and a Graphics card capable of running shaders on a full setting..

|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/RoC.oxp.zip ''Remorse of Conscience'']
| [[Remorse_Of_Conscience_v2|Remorse Of Conscience]]
|
|Ships. A trade ship with a large hold, that can hold its own in combat. A good upgrade from the Cobra Mk III.

|-valign="top" bgcolor="#e7e7ff"
|[[Renegade Pirates OXP|Renegade Pirates V3.0]]
|
|
|Ships / Feature. Adds rare very well armed pirate versions of Classic Elite ships to the more lawless systems. These pirates carry high bounties, but their multiple lasers and plasma cannons will make mince-meat of a young Jameson. Do not install this OXP until you have an Iron Ass!
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/RVandGS.zip ''Renegade Viper + Grass Snake'']
|[[Renegade Viper]]

[[Grass Snake]]
|
|Ships. Sometimes even GalCops are victims of crime, finding their Vipers stolen from the docking berth. The joy-rider gives the stolen Viper a new lick of paint and joins a pirate fleet. Large bounties are paid for ridding the space lanes of these thieves. The Grass Snake is a trade ship with a large hold, often used by pirates.
|-valign="top" bgcolor="#e7e7ff"
| [[Repair_Bots_OXP|Repair 'Bots]]
|
|
| Equipment. A pylon mounted canister of repair nanobots. These can be activated in-flight, when they scan your ship for damaged equipment and attempt to fix an item of it (a random one if multiple items are found). They are reliable for lower tech items, but as the equipment gets more complicated they sometimes struggle. But if all else fails, buy, try and fly again...

|-valign="top"
| [[Rock Hermit Locator]]
|
|
|Equipment. The Rock Hermit Locator is a piece of equipment for your ship to locate Rock Hermits. Useful for miners and Traders.. You need to already have bought the advanced space compass that works in tandem with the RHL ("Rock Hermit Locator").
|-valign="top" bgcolor="#e7e7ff"
| [http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Saleza Aeronautics'']
| [[Bellatrix_Cruiser|Bellatrix Cruiser]]

[[Rigel_Bomber|Rigel Bomber]]

[[Saiph_Interceptor|Saiph Interceptor]]
|
|Ships / Feature. High Tech Corporate States gain their own patrol craft. Some of these ships are also available on the open market.
|-valign="top"
| [http://www.box.net/shared/mcmeur2axl''Santa''] - ([http://oosat.alioth.net/files/Santa.zip alternative lo-end version])
|
|
|Ships. Just for fun adds a (very rare) Santa Sledge to the space lanes escorted by plasma gun toting reindeer space bikers!
|-valign="top" bgcolor="#e7e7ff"
| [[Save_Anywhere|Save Anywhere]]
|
|
|Feature. Save Anywhere allows you to save your game at any OXP Station, instead of only at Main Stations, as in the standard game.
|-valign="top"
| [[Media:BlackBaron1.70.zip|''Scourge of the Black Baron v1.70'']]
|
|
| [[Oolite_Missions#The_Scourge_of_the_Black_Baron|Mission]]. A sequel to the [http://capnhack.com/hosting/oolite/Oolite/OXPs/longway.oxp.zip ''Long Way Around''] mission, featuring combat and transport missions. Well suited to a relative novice in Galaxy 1.
|-valign="top" bgcolor="#e7e7ff"
| [[Second_Wave_OXP|Second Wave]]
| A variety of new alien ship variants.
|
| Ships. Some new variants on the standard Thargoid Warship and Thargon Robot Fighter.

|-valign="top"
| [http://oosat.alioth.net/files/s-ships1.zip ''Selezen's S-Ships'']
| [[GalCop_SWAT_Viper|GalCop SWAT Viper]]

[[Oresrian_Trader|Oresrian Trader]]
|
|Ships. In response to increasing piracy GalCop has introduced the SWAT Viper, a beefed up version of the standard Viper. Also adds the peaceful Oresrian Trader.
|-valign="top" bgcolor="#e7e7ff"
| [[Sell equipment OXP|''Sell Equipment'']]
|
|
| Feature / Equipment. Allows you to resell all equipment you bought at an equipment store of suitable techlevel. For a small fee you purchase the "Sell xyz"-option, and are refunded 60 per cent of the original price.
|-valign="top"
| ''[[Shady Cobra OXP|Shady Cobra]]''
|
|
| Ships. A [[shaders in Oolite|Shader]] example (requires Oolite 1.69 or later). Replaces the normal model for the Cobra Mk III with one featuring the new Shaders.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/All-Stars_0.zip ''Skrounk All-Stars Limited'']
| [[All_Stars_Large_Freighter|All Stars Large Freighter]]

[[Seymour_Class_Sled|Seymour Class Sled]]

[[Starbelly_Class_Sled|Starbelly Class Sled]]

[[Starhawk|Star Hawk]]

[[Starwolf_Mark_I|Starwolf Mk I]]
|
| Ships. A set of ships featuring a large trade ship and a variety of fighters and escorts.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/snark.zip ''Snark'']
|
|
|Ships. The Snark is a powerful fighter / trader, often used by pirates and bounty hunters.
|-valign="top" bgcolor="#e7e7ff"
| [[Snoopers|Snoopers2.0]]
|
|
| Feature. The galactic news network. Updated 05/02/2010
|-valign="top"
| [http://oosat.alioth.net/files/Spearhead.zip ''Spearhead Interceptor Mk.I'']
|
|
|Ships. A pure fighter, fast and nippy but with a weak shield, no cargo bay and can be a twitchy bird to fly. Often used as an escort or part of a pirate fleet acting in a hit an run role.
|-valign="top" bgcolor="#e7e7ff"
| [[Spy_Hunter_OXP|''Spy Hunter'']]
|
|
| [[Oolite_Missions#Spyhunter|Mission]]. A mission for the Galactic Navy available to a Commander with a rating of 'Dangerous' or above. Spys from the Empire sometimes infiltrate GalCop space. Commanders wishing to volunteer for hunting duties should visit the Navy base at Inines in Galaxy 1.
|-valign="top"
| [http://oosat.alioth.net/files/StarWars.zip ''Star Wars Ships'']
| [[A-Wing]]

[[B-Wing]]

[[Lambdashuttle|Lambda Shuttle]]

[[Tie-Fighter]]

[[Tie-Interceptor]]

[[X-Wing]]

[[Y-Wing]]
|
|Ships. Adds a set of ships from the Star Wars Universe to Oolite. Tie Fighters are occasionally used by GalCop to support Viper patrols, but all ships are available on the open market and may be used by traders, pirates and bounty hunters alike.
|-valign="top" bgcolor="#e7e7ff"
| [[Status Quo Q-bomb OXP|''Status Quo Q-bomb'']]
|
|
|Feature. Changes the behaviour of Q-bombs according to the [[Status Quo]] novel. They don't detonate in gravity wells, like close to planets or suns.
|-valign="top"
| ''[http://www.box.net/shared/static/9cwp2jk84o.zip Sung's Detailed Textures]''
|
|
|Replacement textures for all Classic Elite Ships. The author's web-site no longer has a link to his textures. The link will download them directly from Lestradae's hosting site.
|-valign="top" bgcolor="#e7e7ff"
| ''[http://www.box.net/shared/535vddgddh Sung's Detailed Textures (Shader Version)]''
|
|
|Same as the above oxp, only now with shader support. Normal maps & Effects maps by ADCK. (Includes shaders which require Oolite 1.69 or later)
|-valign="top"
| [http://sancho.dk/oolite/sunskimmers.zip ''Sunskimmers'']
|
|
|Feature. Normally in Oolite ships tend to stick to the space lanes and so are rarely encountered on the way to the Sun. This OXP adds ships to the sun / planet corridor increasing the chance of meeting other ships whilst sun-skimming.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.mediafire.com/?sharekey=ca166c7e38ef78c6e7c82ed4b8f0c380e04e75f6e8ebb871 ''S.T.E'']
| [[S.T.E]]
|
|Ships. The S.T.E addon ship a step up from the Cobra III improved trading capabilities also has increased speed over Cobra, is also available in 3 colour options blue, red and yellow.
|-valign="top"
| [[SuperCobra]]
| [[SuperCobra]]
|
|Ships. The awesome Super Cobra. A beefed up version of the Cobra Mk III featuring larger engines, more cargo space and stronger shields.
|-valign="top" bgcolor="#e7e7ff"
| [[Superhub]]
|
| [[Superhub]]
| Stations. Traffic congestion in the Ooniverse is growing and while the stations are getting more advanced the market asked for a more radical solution. This solution comes in the form of the Gasec Superhub. The Gasec Superhub is the first station that is capable of transporting itself to it's destination, two engine bays allow the GASEC SR-GD (Space Rotary Galactic Drive) to be fitted. At the destination these engines can be taken out for re-use in other transport missions. ''v1.2 updated 12th November 2009''
|-valign="top"
| [http://www.box.net/public/b2tic3tjsk#f4083657 ''Swift'']
| [[Swift]]
|
|Ships. As the name implies, a very fast ship often used by pirates or bounty hunters. Although fast, cargo space is limited and the shield is nominal.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.msdownload.co.uk/Oolite/system_redux.zip ''System Redux'']
| [[System_Redux_%28Oolite%29|System Redux]]
|
|Texture the home planet, add a planet/moon combination to each system.
|-valign="top"
| [http://www.box.net/shared/r05ub873b5 ''TAF Reset'']
|
|
|Utility. Resets the Time Acceleration Factor (TAF) to 1.0 upon docking. Requires Oolite v1.73+.
|-valign="top" bgcolor="#e7e7ff"
| [[Taranis_OXP|''Taranis Corporation HQ'']]
|
| [[Taranis_Corporation_HQ_%28Oolite%29|Taranis Corporation HQ]]
| [[Oolite_Missions#Taranis|Mission]]. Adds the vast orbital [[Taranis_Corporation_HQ_%28Oolite%29|Taranis Corporation HQ]] to the Lerelace system in Galaxy 1. A mission is also available for law abiding Commanders with a rating of Competent or better. You must also have the [http://oosat.alioth.net/files/outrider.zip ''Outrider''] OXP installed for this OXP to work properly.
|-valign="top"
| [[Target_Autolock_OXP|Target Autolock]]
|
|
| Equipment. A software update for the standard [[Scanner_Targeting_Enhancement|scanner targeting enhancement]] equipment that automatically locks onto attacking ships if you have no prior target selected.
|-valign="top" bgcolor="#e7e7ff"
| [http://sancho.dk/oolite/Shield-tail.zip ''Teretrurus Mk.I'']
| [[Teretrurus Mk.I|Teretrurus MK.I]]
|
|Ships. A medium fighter / trader somewhat faster and tougher than the Cobra Mk III, but with a smaller cargo bay.
|-valign="top"
| [http://oosat.alioth.net/files/Terrapin.zip ''Terrapin Trader'']
| [[Terrapin]]
|
|Ships. A medium fighter / trader. A good upgrade from the Cobra Mk III.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/Tescoura.zip ''Tesoura'']
| [[Tesoura]]
|
|Ships. A slow, but well shielded trade ship.
|-valign="top"
| [http://oosat.alioth.net/files/Thargoid_CarrierV1.zip ''Thargoid Carrier'']
| [[Thargoid_Carrier|Thargoid Carrier]]
|
|Ships. Arms the Thargoids with a vast carrier capital vessel. Many OXPs increase the fire-power available to the GalCop Navy. If you chose to play with these OXPs installed, then you should really give the Bugs a chance and allow them access to this mighty craft!
|-valign="top" bgcolor="#e7e7ff"
| [[Thargoid_Wars|Thargoid Wars V4.4 (Updated)]]
|
|
| [[Oolite_Missions#ThargoidWars|Mission]]. War with the Thargoids intensifies featuring new attack and defense missions. To avoid young Jamesons being out-gunned, the OXP missions will run in all Galaxies except Galaxy 1. Updated from the version on Oosat1. It is important that you use the updated version as the old version will clash with many other missions.
|-valign="top"
| [[Thargorn_Threat_oxp|''Thargorn Threat v1.3 (updated)'']]
| [[Terroriser_Frigate|Terroriser Frigate]]

[[Thargoid_Thargorn_Battleship|Thargoid Thargorn Battleship]]

[[Thargoid_Thorgon_Cruiser|Thargoid Thorgon Cruiser]]
|
|Ships. Redresses the game imbalance caused by the number of OXPs arming the Navy with warships. These Thargoid craft are very powerful and re-establish the Thargoid's place as a threat to mankind. Best played with the Behemoth OXP installed, for epic space battles.
|-valign="top" bgcolor="#e7e7ff"
| [http://www.wagar.org.uk/downloads/software/oolite/Tianve1.3.zip''Tianve'']
|
|[[Navy Station]]
|Planets / Stations. Adds scenery, including a pulsar, to the Galaxy 1 system of Tianve. A Station orbits the pulsar and fleets of pleasure liners can be seen taking tourists on flights around the pulsar. There are various adverts in the system, along with two extra 'space lanes', one between the planet and the pulsar and another between the pulsar and the witchpoint.
|-valign="top"
| [http://oosat.alioth.net/files/Tiger.zip ''Tiger'']
| [[Tiger_Mark_I|Tiger Mark I]]
|
|Ships. A truly awesome (and very expensive) multi-role craft.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/TGY.zip ''Tionisla Orbital Graveyard]
|
|
|Feature. Adds the graveyard to the Galaxy 1 system of Tionisla, as described in the Dark Wheel. Long dead Commanders are buried in their rusting ships amongst monuments, Stars of David, Crucifixes and other religious symbols. Security patrols will make short work of any Commander foolish enough to desecrate the tombs.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/tori.zip ''Torus Station'']
|
| [[Torus_station|Torus Station]]
|Stations. Adds a vast 2001 style space station to very high tech level systems.
|-valign="top" bgcolor="#e7e7ff"
| [[Total_patrol_OXP|''Total patrol'']]
|
|
|Feature. Replaces the default police AIs with a totalPatrolAI which lets police ships patrol between all three major points of the system: planet, witchpoint and sun.
|-valign="top"
| [http://www.box.net/shared/eil0djqhca ''Trade Outpost v1.1'']
|
| [[Trader_Outpost_%28Oolite%29|Trade Outpost]]
|Griff trade outpost without ads.
|-valign="top" bgcolor="#e7e7ff"
| [[Traffic_Control_OXP|Traffic Control]]
|
|
| Station upgrade. Adds traffic control personnel to each system main station. They are happy to talk new Commanders (and older ones who've got too reliant on Docking Computers and then lost them) through approaching and manual docking with the station. There's even a cheery goodbye when you leave, just don't dawdle and block the station approach lane!
|-valign="top"
| [http://oosat.alioth.net/files/Trans-Hab.zip ''Trans-Hab Station'']
|
| [[Transhab_station|Transhab Station]]
|Stations. Adds a large station with rotating arms to some medium tech level systems.
|-valign="top" bgcolor="#e7e7ff"
| [[Transports]]
| [[CoachWhip]]
[[Coral]]
[[Woma]]
|
|Ships. Adds more variety to the game. Passenger liners can be seen in the space lanes of the safer systems transporting paying customers to their destinations. Also features Moray Transporters and Large Woma fuel tankers to bring much needed supplies and fuel to space stations.
|-valign="top"
| [[Trident_Down|Trident Down]]
|
|
| [[Oolite_Missions#Trident_Down|Mission]]. A series of missions set in Galaxy 4 involving the investigation of a vicious attack on an Trident Shuttle operated by [[Executive_SpaceWays|Executive SpaceWays]].
|-valign="top" bgcolor="#e7e7ff"
| [[UPS_Courier|U.P.S. Courier]]
|
|
|[[Oolite_Missions#UPS_Courier_Company|Mission]] / Feature. The UPS Courier service will randomly offer Commanders the option of taking goods or documents from system to system. Some say experienced Couriers may also be offered combat missions.
|-valign="top"
| [http://oosat.alioth.net/files/UrutaMK3.zip ''Urutu Mk.III'']
| [[Urutu_Mk.III|Urutu Mk III]]
|
|Ships. A medium fighter / trader from Elite-A.
|-valign="top" bgcolor="#e7e7ff"
| [http://oosat.alioth.net/files/UrutaMK4.zip ''Urutu Mk.IV'']
| [[Urutu_Mk.IV|Urutu Mk IV]]
|
|Ships. A medium fighter / trader from Elite-A.
|-valign="top"
| [http://www.purgatori.net/Isis_Interstellar.htm ''Vampire'']
| [http://www.purgatori.net/Isis_Interstellar.htm Vampire]
|
|Ships. Adds the Purgatori Vampire series of combat ships. A strong combat ship in numerous different versions and paint-jobs. A Military version is used by the police, but several civilian versions of the ship are also available on the open market. Clicking the download link will take you to the sales brochure, where you can inspect further particulars and download the OXP.
|-valign="top" bgcolor="#e7e7ff"
| [[Vector_OXP|Vector1.3]]
| Vector
|
|Mission/Ships. Fast, rare and expensive. And some small surprises - So dive in and have a good time (Updated 31.08.2009)
|-valign="top"
| [[Velocity_OXP|Velocity]]
|
|
|Ships. A fast fighter ship.
|-valign="top" bgcolor="#e7e7ff"
| [[Venom]]
| [[Venom]]
[[Venom|Venom Renegade]]
|
|Ships. From Isis Interstellar who previously also made the [http://www.purgatori.net/Isis_Interstellar.htm Vampire]. This ship also provides three extra HUDs.
|-valign="top"
| [http://capnhack.com/hosting/oolite/Oolite/OXPs/weeviloid2.zip ''Weeviloid'']
| [[Weeviloid_Hunter|Weeviloid Hunter]]
[[Weeviloid_Scoutship|Weeviloid Scoutship]]
|
|Ships. The scout-ship is a light trade ship. The hunter is a fearsome multi-gunned war ship. Little is known about the Weeviloids and many Commanders meeting them have found them hostile.
|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds.zip ''Wiggy's Replacement Sounds'']
|
|
| Sound Set.
|-valign="top"
| [[Welcome_Mat_OXP|Welcome Mat]]
|
|
| Misc. Software upgrade for the communications systems to expand the information given to the commander on arrival from witchspace into a new system. Augments the system name message with planetary biographical details via the buoy network, plus the latest safety and alien presence information from Galcop. Also fully compatible with [[OXPConfig|OXPConfig]].
|-valign="top" bgcolor="#e7e7ff"
| [http://www.box.net/shared/vhho2av2az ''Wolf Mk.II v3.3]
| [[Wolf_Mk.2_%28Oolite%29|Wolf Mk II]]
|
|Ships. Adds the powerful Wolf Mk II, as seen in Elite-A.
|-valign="top"
| [[Media:Wolfs_variants.zip|''Wolfwood's Variants v1.5'']]
| [[Asp_Mk.I|Asp Mk I]]

[[Cobra_Courier|Cobra Courier]]

[[Cobra_Rapier|Cobra Rapier]]

[[Drake]]

[[Drake_Mk_II|Drake Mk II]]

[[Wolf Mk I]]
|
|Ships. A large selection of traders and fighters based on models seen in Classic versions of Elite. The ships strive to be on the same level with original ships and not too powerful in comparison to them. Tested on Oolite v1.70.

|-valign="top" bgcolor="#e7e7ff"
| [http://capnhack.com/hosting/oolite/Oolite/extra/oosounds3.zip ''Xaotik's Replacement Sounds'']
|
|
| Sound Set.

|-valign="top"
| [[Your Ad Here!]] [[Image:Updated.gif|Updated]]
| [[Pi-42 security|Sidewinder Pi-42 Security]]

[[Tescoo security|Sidewinder Tescoo Security]]

[[Star security|Sidewinder Star Security]]

[[Mall Wart security|Sidewinder Mall Wart Security]]

[[Sainsboory's security|Sidewinder Sainsboory's Security]]
| [[Pi-42]]

[[Tescoo_Oxpress|Tescoo Oxpress]]

[[Star]]

[[Mall Wart]]

[[Sainsboory's]]

|Feature. This OXP adds a lot of variety to the Universe. Witch-point and navigation beacons are replaced with giant bill boards displaying adverts.
Every set features 50 different adverts and also adds a different type of constore to the universe (Set A introduces the Pi-42 constore, Set B the Tescoo Ooxpress constore etc). A constore is a dockable commercial base which is added to the space lanes of most systems with a large population.
Also from version 4 and above of this oxp each constore has its own security force, the ships of which are skinned in the colours of the store they protect, and billboards will occasionally appear in asteroid fields of Corporate Systems.
|-valign="top" bgcolor="#e7e7ff"
| [[Z-ships|Z-ships]]
| [[Z-ships_Asp_Explorer|Asp Explorer]] 
[[Z-ships_Cobra_Commodore|Cobra commodore]] 
[[Z-ships_Porcupine|Porcupine]] 
[[Z-ships_Python_Courier|Python Courier]]
|
| Ships. This OXP adds 4 ships (+variants) to the Ooniverse. Released under the [http://creativecommons.org/licenses/by-nc-sa/3.0/ Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported] License.
|}

==All OXPs by Category==

===Sound Sets===
[http://capnhack.com/hosting/oolite/Oolite/OXPs/E5Amigasoundpack01oxp.zip ''Amiga Replament Sounds''] 
[http://oosat.alioth.net/files/CustomSounds.zip ''Custom Sounds''] 
[[Media:halsis.zip|Hal's Hot Sister]] (female cockpit voice) 
[http://www.mediafire.com/file/mm2ekntynom/Hawksound.zip ''Hawksound''] 
[http://capnhack.com/hosting/oolite/Oolite/extra/oosounds2.zip ''Murgh's Replacement Sounds''] 
[http://capnhack.com/hosting/oolite/Oolite/extra/oosounds.zip ''Wiggy's Replacement Sounds] 
[http://capnhack.com/hosting/oolite/Oolite/extra/oosounds3.zip ''Xaotik's Replacement Sounds''] (= [[Media:MildAudio.oxp.zip|MildAudio]]) 
[http://www.box.net/shared/edl1p4lm3o ''Combined Murgh, Wiggy & Xaotik's sounds''] (Needs oolite 1.73+)

===Alternative HUDs===
[http://capnhack.com/hosting/oolite/Oolite/pLists/hud.plist ''Compact HUD''] 
[http://www.jblythe.f9.co.uk/Deepspace/Download/DeepspaceHUD_OXP.zip ''Deepspace HUD''] 
[http://sancho.dk/oolite/Dr_HUD_Cmk3.zip Dr HUD Cobra Mk.III version], [http://sancho.dk/oolite/Dr_HUD.zip Custom version] 
[http://oosat.alioth.net/files/FighterHud.zip ''Fighter HUD''] 
[http://wiki.alioth.net/images/2/2d/G-HUD_Mk2.oxp.zip ''G-HUD Mk2''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/kleptohud.oxp.zip ''Klepto-HUD''] 
[http://www.crimsonforge.co.uk/cloister/MedusaHud.oxp.zip ''Medusa HUD''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/megawalnutdash.oxp.zip ''Mega-Walnut Dashboard''] 
[http://oosat.alioth.net/files/MilHUDv2.zip ''Milspec HUD v2''] (1.65-1.72) |
[http://www.box.net/shared/hczsm8gyi0 ''Milspec HUD v3''] (for 1.73 onwards) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/hud_ng.oxp.zip ''NG HUD''] 
[http://wiki.alioth.net/images/d/d9/TrekHud.zip ''Trek HUD''] 
[[HUD images here]]

===Dockable Objects===
[[Anarchies OXP|Anarchies]] 
[[Aquatics_OXP|Aquatics]] 
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[[Baakili_Far_Trader|Baakili Far Trader]] 
[[Black_Monk_Monastary|Bank of the Black Monks]] 
[[BuoyRepair|BuoyRepair1.02.5]] - Updated (7/10/2009) 
[[Deep Space Dredger|Deep Space Dredger]] 
[http://www.mediafire.com/?dnzltr0cit5 ''Free Trade Zone''] 
[[Fuel_Station_OXP|Fuel Station]] 
[[Globe_station|Globestation2.0]] (Updated 22/10/2009) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/GrittyCoriolis.oxp.zip ''Gritty Coriolis''] 
[[HoOpy Casino]] 
[[Lave_Academy_OXP|Lave Academy]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/gwxstations.oxp.zip ''Military Station''] 
[[Planetfall_OXP|Planetfall]] 
[[Random Hits OXP|Random Hits]] 
[[Superhub]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/tori.zip ''Torus Station''] 
[http://oosat.alioth.net/files/Trans-Hab.zip ''Trans-Hab Station''] 
[http://www.box.net/shared/eil0djqhca ''Trade Outpost v1.1''] 
[http://oosat.alioth.net/files/Taranis.zip ''Taranis Corporation HQ''] 
[[P.A. Groove Stations OXP]] 
[[Your Ad Here!]] 
More information on the Station images appearing in Oolite can be found [[Oolite Stations|here]].

[[Dockable Object images here]]

===Customisations by Government (or Tech Level)===
[[Anarchies OXP|Anarchies]] 
[[BuoyRepair|BuoyRepair1.02.5]] 
[[Commies|Commies]] 
[[DeepSpacePirates|DeepSpacePirates]] 
[http://www.arcadia-digital.net/steve/Oolite/Oolite.html ''Dictators''] 
[[Feudal_States|The Feudal States]] 
[[Random Hits OXP|Random Hits]] 
[[Snoopers|Snoopers2.0]] (Updated 05/02/2010) 

===Other System Objects===
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[http://oosat.alioth.net/files/Diso.zip ''Diso''] 
[[Fuel_Station_OXP|Fuel Station]] 
[http://www.mediafire.com/?zahdnac0tj1 ''Lave v1.70''] 
[[Lave_Academy_OXP|Lave Academy]] 
[[Pirate Coves OXP|Pirate Coves]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/piratetraps.oxp.zip ''Pirate Traps''] 
[http://www.box.net/shared/b2tic3tjsk#1:3775170:31020120 ''Planets''] 
[[RingPod.oxp|Racing Rings]] 
[[Ring_Racer_OXP|Ring Racer]] 
[http://www.wagar.org.uk/downloads/software/oolite/Tianve1.3.zip''Tianve''] 
[http://oosat.alioth.net/files/TGY.zip ''Tionisla Orbital Graveyard] 
[[Traffic_Control_OXP|Traffic Control]] 
[[Your Ad Here!]] 

===Missions===
[[Aquatics_OXP|Aquatics]] 
[[The Assassins Guild OXP|Assassins Guild V1.3]] 
[[Asteroid_Storm|Asteroid Storm 1.52]] 
[[BlackjacksBullion_OXP|Blackjacks Bullion]] 
[[Cataclysm_OXP|Cataclysm]] 
[[Deposed_OXP|Deposed 1.3.4]] 
[[Ionics_OXP|Ionics v.1.2.3]] 
[[Lave_Academy_OXP|Lave Academy]] 
[[Localhero OXP|Localhero v1.05]]  (Updated 27.04.2008) 
[[LongWay_OXP|Long Way Around 1.1]] 
[[Lovecats.oxp|Lovecats 1.2]] 
[[Military_Fiasco|Military Fiasco V2.3]] 
[[Oo-Haul]] 
[[Random Hits OXP|Random Hits]] 
[[Media:BlackBaron1.70.zip| ''Scourge of the Black Baron v1.70'']] 
[[Spy_Hunter_OXP|Spy Hunter]] 
[[Taranis_OXP|Taranis Corporation HQ]] 
[[Thargoid_Wars|Thargoid Wars V4.4 (Updated)]] 
[[Trident_Down|Trident Down]] 
[[UPS_Courier|U.P.S. Courier]] 
[[Vector_OXP|Vector1.3]]  (Updated 31.08.2009) 

More information on the numerous Oolite Missions can be found [[Oolite Missions|here]].

===Ship Systems===
[[AMS_OXP|Anti-Missile System]] 
[[Automatic_Chaff_System|Auto-Chaff System]] 
[[Captured_Thargons_OXP|Captured Thargons]] 
[[Drones_OXP|Drones]] 
[http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon] 
[http://oosat.alioth.net/files/External%20Views.zip ''External Views''] 
[[Energy_Equipment_OXP|Energy Equipment]] 
[[Fuel Tank|Fuel Tank]] 
[[Hired_Guns_OXP|Hired Guns]] 
[[Hyperradio_js_OXP|Hyperradio v1.17]] 
[[Killit_OXP|''Killit™'' insta-death super weapons]] 
[[Missile Analyser|Missile Analyser]] 
[[Misjump Analyser|Misjump Analyser]] 
[[Missiles and Bombs|Missiles and Bombs]] 
[[Missile_Rack_OXP|Missile Rack]] 
[[Nukes.oxp|Nuclear Torpedos]] 
[[Ore_Processor|Ore Processor]] 
[[Probe_OXP|Probe]] 
[[Repair_Bots_OXP|Repair 'Bots]] 
[[Rock_Hermit_Locator|Rock Hermit Locator]] 
[[Sell equipment OXP|Sell equipment]] 
[[Status Quo Q-bomb OXP|Status Quo Q-bomb]] 
[[Target_Autolock_OXP|Target Autolock]] 
[[Target Reticle|Target Reticle]] 
[[Welcome_Mat_OXP|Welcome Mat]] 

===Ships and Ship Variants===
See below for ship names and stats. 

[[Aegidian's_Specials|Aegidian's Specials]] 
[[Aegidian's_X-Ships|Aegidian's X-Ships]] 
[http://uploading.com/files/CTQ4YDB4/Blitzspear%20Clan.rar.html''Amen Brick's Pirate Clan One: The Blitzspears v1.0 (new 07/08)''] 
[http://www.uploading.com/files/QERHQBAE/Amen_Bricks_Megaships.oxp.zip.html''Amen Brick's Megaships v1.1 (new 07/08)''] 
[[Anarchies OXP|Anarchies]] 
[http://oosat.alioth.net/files/aphidv2.oxp_.zip ''Aphid Escort Service''] 
[[Aquatics_OXP|Aquatics]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/att1.zip ''Armoured Transport Type 1''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/bandersnatch.zip ''Bandersnatch''] 
[[Baakili_Far_Trader|Baakili Far Trader]] 
[[Behemoth]] 
''[http://www.box.net/shared/nv87fgfyf2 Behemoths - Shadered (By ADCK)]''(Includes shaders which require Oolite 1.69 or later) 
[[BigShips_OXP|Big Ships]] 
[[Boa_2_Class_Cruiser|Boa Class Cruiser]] 
[[Boa_II_Clipper_Class|Boa II Clipper Class]] 
[[Media:BoomslangWIP.zip|''Boomslang'']] 
''[http://www.box.net/shared/sxcsfa47hf Bulk Haulers (By ADCK)]''(Requires [[BigShips_OXP|Big Ships]] and Includes shaders which require Oolite 1.69 or later) 
[[Caduceus]] 
[http://oosat.alioth.net/files/seosu.zip ''Capisastra''] 
[http://oosat.alioth.net/files/clearskies.oxp_.zip ''Clear Skies''] 
[http://oosat.alioth.net/files/ChoppedCobra.zip ''Cobra 3.5 (chopped Cobra)''] 
[[Cobra_Clipper_SAR|Cobra Clipper SAR]] 
[http://oosat.alioth.net/files/cobra3njx.zip ''Cobra Mk.III Njx''] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Condor''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/custpaint1.zip ''Custom Paint Jobs''] 
[http://oosat.alioth.net/files/dwcobra3HiRes.zip ''Dark Wheel Cobra''] - ([http://oosat.alioth.net/files/dwcobra3.zip alternative lo-end version]) 
[[DeepSpacePirates|DeepSpacePirates]] 
[[Deepspace_Ships|Deepspace Ships]] 
[[Dragon|Dragon Assault Craft (Updated 9/8/08)]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/eagle2.zip ''Eagle Mk.II''] 
''[http://www.box.net/shared/xkltqit3oj Eagles Mk's I to IV (by ADCK)]'' (Includes shaders which require Oolite 1.69 or later)
 
[http://oosat.alioth.net/files/ettBeaconLauncher.zip ''ETT Homing Beacon] 
[http://www.arcadia-digital.net/steve/Oolite/Ships/Executive%20SpaceWays%20v2.2.zip ''Executive Spaceways''] 
[[Far_Arm_ships|Far Arm ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/farstar.oxp.zip ''Far Star''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/ferdelance_ng.oxp.zip ''Fer de Lance NG''] 
[http://oosat.alioth.net/files/ferdepai.oxp_.zip ''Ferdepai''] 
[http://oosat.alioth.net/files/Firewasp.zip ''Firewasp''] 
[[Flying Dutchman OXP|Flying Dutchman]] 
[[Freaky Thargoids OXP|Freaky Thargoids]] ([[shaders in Oolite|shader]] example, requires Oolite 1.69 or later) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/fsr.zip ''Frog Space Rickshaw''] 
[[Galactic_Navy_OXP|Galactic Navy]] 
[[Generation_Ships_OXP|Generation Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/greekshipset1.zip ''Greek Ships''] 
[[Griff_ArcElite|Griff ArcElite Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/griffin2.oxp.zip ''Griffin Mk.II] 
[[Griff_Krait|Griff Krait]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/boyracers.zip ''Hatchling Boyracers''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/Herald.zip ''Herald''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/tugs.zip ''Hognose Tugships''] 
[http://www.mediafire.com/?2vgjwpj6xdy ''Hotrods v0.52c''], [http://www.box.net/shared/j2r6frlvq1 ''Hotrods v0.52d''] 
[http://wiki.alioth.net/index.php/Icarus_%28Oolite%29 ''Icarus''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/illicit_unlock.oxp.zip ''Illicit Unlock''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/impcourier.zip ''Imperial Courier''] 
[[Interstellar help OXP|Interstellar Help]] 
[[Ixian_Ships|Ixian Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/jabberwocky.zip ''Jabberwocky''] 
[http://capnhack.com/hosting/oolite/dropbox/kestrel_falcon1_71_0.zip ''Kestrel&Falcon v1.71.0''] 
[http://www.crimsonforge.co.uk/cloister/kirin.zip ''Kirin''] 
[http://sancho.dk/oolite/lane_legal.zip ''Lane Legal Racers''] 
[[Media:Llama.zip|''Llama'']] 
[http://oosat.alioth.net/files/Longshot.zip ''Longshot''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/mPakRedux.zip ''M-Pack (rusties)''] 
[http://oosat.alioth.net/files/manta.oxp_.zip ''Manta''] 
[http://oosat.alioth.net/files/marett_vol1.zip ''Marett Space Corporation''] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Merlin''] 
[http://sancho.dk/oolite/missionaries.zip ''Missionaries v1.1''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/monument.zip ''Monument''] 
[http://capnhack.com/hosting/oolite/dropbox/morrigan101.zip ''Morrigan''] 
[[Murgh_Xships OXP|Murgh's X-Ships]] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Navy Starships''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/newships.oxp.zip ''New Ships''] 
[[Neolite Ships]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/nuvipers.zip ''Nu Vipers''] 
[[Old Ships]] 
[[Orb]] 
[http://oosat.alioth.net/files/outrider.zip ''Outrider''] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Pallas''] 
[http://oosat.alioth.net/files/Pelamis.zip ''Pelamis''] 
[[Personalities OXP|Personalities]] 
[http://oosat.alioth.net/files/Phoenix.zip ''Phoenix''] 
[http://oosat.alioth.net/files/PTI.zip ''Pteradyne Technologies Ships''] - ([http://oosat.alioth.net/files/PTI_bugfix11.zip ''bug fix'']) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/pcc.oxp.zip ''Python Class Cruiser] 
''[[Media:Python Class Cruiser.oxp.zip|Python Class Cruiser version 2.6]]'' (Includes shaders which require Oolite 1.69 or later) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/racers.oxp.zip ''Racers''] 
[[Ramon's_Anaconda|Ramon's Anaconda]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/RoC.oxp.zip ''Remorse of Conscience''] 
[http://oosat.alioth.net/files/RenegadesV3.zip ''Renegade Pirates''] (Wait until you have an Iron Ass before installing this OXP!) 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/RVandGS.zip ''Renegade Viper + Grass Snake] 
[http://oosat.alioth.net/files/Saleza%20Aeronautics%20v2.0.zip ''Saleza Aeronautics''] 
[http://oosat.alioth.net/files/santa_v2.zip ''Santa''] - ([http://oosat.alioth.net/files/Santa.zip alternative lo-end version]) 
[[Second_Wave_OXP|Second Wave]] 
[http://oosat.alioth.net/files/s-ships1.zip ''Selezen's S-Ships''] 
[[Shady Cobra OXP|Shady Cobra]] 
[http://oosat.alioth.net/files/All-Stars_0.zip ''Skrounk All-Stars Limited''] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/snark.zip ''Snark''] 
[http://oosat.alioth.net/files/Spearhead.zip ''Spearhead Interceptor Mk.I''] 
[http://oosat.alioth.net/files/StarWars.zip ''Star Wars Ships''] 
[http://www.box.net/shared/static/9cwp2jk84o.zip ''Sung's Detailed Texture''s] 
[http://www.box.net/shared/535vddgddh ''Sung's Detailed Textures (Shader Version)''] (Includes shaders which require Oolite 1.69 or later)
 
[http://sancho.dk/oolite/sunskimmers.zip ''Sunskimmers''] 
[[SuperCobra|Super Cobra]] 
[http://www.box.net/public/b2tic3tjsk#f4083657 ''Swift''] 
[http://sancho.dk/oolite/Shield-tail.zip ''Teretrurus Mk.I''] 
[http://oosat.alioth.net/files/Terrapin.zip ''Terrapin Trader''] 
[http://oosat.alioth.net/files/Tescoura.zip ''Tesoura''] 
[http://oosat.alioth.net/files/Thargoid_CarrierV1.zip ''Thargoid Carrier''] 
[[Thargorn_Threat_oxp|Thargorn Threat v1.3 (updated)]] 
[http://oosat.alioth.net/files/Tiger.zip ''Tiger''] 
[[Transports|Transports]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/tugs.zip ''Tugs''] 
[http://oosat.alioth.net/files/UrutaMK3.zip ''Urutu Mk.III''] 
[http://oosat.alioth.net/files/UrutaMK4.zip ''Urutu Mk.IV''] 
[http://www.purgatori.net/Isis_Interstellar.htm ''Vampire''] 
[[Velocity_OXP|Velocity]] 
[[Vector_OXP|Vector1.3]]  (Updated 31.08.2009) 
[[Venom|Venom]] 
[http://capnhack.com/hosting/oolite/Oolite/OXPs/weeviloid2.zip ''Weeviloid''] 
[http://www.box.net/shared/vhho2av2az ''Wolf Mk.II v3.3] 
[http://wiki.alioth.net/images/0/06/Wolfs_variants.zip ''Wolfwood's Variants v1.5''] 
[[Z-ships|Z-ships]] 

[[Ship data table|Ship data table here]] 
More information on the Ships appearing in Oolite can be found [[Oolite Ships|here]].

[[Ships and Ship Variant images here]]

=== Other objects and miscellaneous eyecandy ===
[[Asteroid_Storm|Asteroid Storm]] 
[[Cargo_Wreck_Teaser_OXP|Cargo & Wrecks v1.4]] 
[[Famous Planets OXP|Famous_planets_oxp and FP Expansion packs]] 
[[Famous_Planets_2.0.OXP]] 
[http://www.box.net/shared/d57y0uip74 Farsun v1.05] 
[[Hyperradio_js_OXP|Hyperradio v1.17]]  (Updated 11/02/2010) 
[http://marc-schaffer.ch/data/OoliteGerman_V0.3.zip Oolite German v0.3] 
[[Media:OoliteItaliano_v1.3.zip|''Oolite Italiano v1.3'']] 
[http://www.box.net/shared/ch3lsepk9k Oolite Russian v1.0] 
[http://www.box.net/shared/rrlm77ztzm Oolite en français] 
[[Media:Orbits.zip|''Orbits'']] 
[[OXPConfig|OXPConfig1.08]]  
[[Pods_OXP|Pods]] 
[[Pods_OXP#UPS_PODS|Pods UPS Pack]] 
[[Snoopers|Snoopers2.0]] (Updated 05/02/2010) 
[[RegistrationID|Registration ID ]]

== Installing an OXP ==
Unzip the OXP and place it in the folder named '''AddOns'''. Sometimes the zipped files contain several folders, make sure you only copy the folder -or file for Macintoshes- ending with '''.oxp''' into the AddOns folder. This folder is found in different locations, depending on the platform:

=== Mac OS X ===
Found in the folder that contains the Oolite application.

'''Troubleshooting:''' If you get an error saying "The item could not be moved because "AddOns" cannot be modified", that can happen if you weren't the user that installed Oolite.
The solution is to put the OXP's of your choice in '''~/Library/Application Support/Oolite/AddOns/''' instead (you may need to create this folder).
The error could also be triggered because you’re running from the disk image, you’ll need to copy the game somewhere else. Having done so, if you still get the error, use the Get Info command on the AddOns folder, open the Ownership & Permissions pane and check that it says You Can: Read & Write.

=== Linux ===
The OXP directory can be found in '''$HOME/.Oolite/AddOns.''' for all current versions of OOlite

=== Windows ===
If the installable package was used (post Jan 06) then the AddOns folder needs to be created in '''C:\Programs Files\Oolite'''. Note that this applies if the default installation location is used. If the install location is changed then use the path to the Oolite folder that corresponds to your installation.
If the GNUStep dedicated versions (pre-Jan 2006) is used, then the AddOns folder must be created in the oolite.app folder.

After unzipping the file, make sure that it is ''the'' OXP folder that put into the AddOns directory - some zipped OXPs can contain a top level folder with a readMe file, and the actual OXP folder is a level further down. If this is the case, move the item with the '''.oxp''' extension into the AddOns folder.

== Caveats ==
If you purchase a ship that is an OXP ship and save the game, you will only be able to load that commander as long as this OXP is installed in AddOns. If it's not, Oolite will give you an error instead of trying to load the commander.

== Creating an OXP ==
It is intended to be easy to create expansion packs. With a few simple [[List_of_software|tools]], a player can make small or big changes, and customize the gaming experience.

* [[OXP howto|How to make OXPs]]

[[Category:Oolite]]
[[Category:Oolite expansion packs]]
[[Category:Factual]]

Oolite JavaScript Reference: Ship script event handlers

2010-02-13T18:24:24Z

Kaks: /* playerTargetedMissile */

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

=== Witchspace Jumps ===

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the recommended time to set up elements which need to be present in-system when the player arrives.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition.

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

this.escortAttack = function(target)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

'''Deprecated''' in 1.74 in favour of the more generic shipTargetAcquired

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function( whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

this.shipEnergyBecameFull = function()
{
// Your code here
}

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

this.shipEnergyIsLow = function()
{
// Your code here
}

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler added in test version 1.74)

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when a target is lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetAcquired</code> ====

The <code>shipTargetAcquired</code> handler is called whenever a new target is selected. (Handler added in test version 1.74)

this.shipTargetAcquired = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

this.escortAccepted = function(escortship)
{
// Your code here
}

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

this.escortDock = function(delay)
{
// Your code here
}

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

this.playerWillEnterWitchspace = function()
{
// Your code here
}

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

this.shipAcceptedEscort = function(mother)
{
// Your code here
}

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

this.shipExitedWormhole = function()
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

this.shipSpawned = function()
{
// Your code here
}

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

this.shipWillEnterWormhole = function()
{
// Your code here
}

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

this.spawnedAsEscort = function(mother)
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

this.shipWasScooped = function(scooper)
{
// Your code here
}

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

this.otherShipDocked = function(whom)
{
// Your code here
}

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

this.stationLaunchedShip = function(whom)
{
// Your code here
}

=== Not Yet Implemented ===

A handler does not yet exist for the following event:
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: world_script_event_handlers|world_script_event_handlers]]

[[Category:Oolite scripting]]

Oolite JavaScript Reference: Ship script event handlers

2010-02-13T18:22:41Z

Kaks: added new shipTargetAcquired handler

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

=== Witchspace Jumps ===

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the recommended time to set up elements which need to be present in-system when the player arrives.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition.

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is sent to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

this.escortAttack = function(target)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord. '''Deprecated''' in 1.74 in favour of the more generic shipTargetAcquired

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function( whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

this.shipEnergyBecameFull = function()
{
// Your code here
}

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

this.shipEnergyIsLow = function()
{
// Your code here
}

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler added in test version 1.74)

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when a target is lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetAcquired</code> ====

The <code>shipTargetAcquired</code> handler is called whenever a new target is selected. (Handler added in test version 1.74)

this.shipTargetAcquired = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

this.escortAccepted = function(escortship)
{
// Your code here
}

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

this.escortDock = function(delay)
{
// Your code here
}

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

this.playerWillEnterWitchspace = function()
{
// Your code here
}

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

this.shipAcceptedEscort = function(mother)
{
// Your code here
}

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

this.shipExitedWormhole = function()
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

this.shipSpawned = function()
{
// Your code here
}

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

this.shipWillEnterWormhole = function()
{
// Your code here
}

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

this.spawnedAsEscort = function(mother)
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

this.shipWasScooped = function(scooper)
{
// Your code here
}

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

this.otherShipDocked = function(whom)
{
// Your code here
}

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

this.stationLaunchedShip = function(whom)
{
// Your code here
}

=== Not Yet Implemented ===

A handler does not yet exist for the following event:
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: world_script_event_handlers|world_script_event_handlers]]

[[Category:Oolite scripting]]

Wormhole Scanner

2010-02-11T00:41:39Z

Kaks: /* Use */

== Overview ==
Displays detailed information about a targeted wormhole

== Use ==
When in flight, press '''r''' to activate the ship's identification system, and place your target reticle over a wormhole to select it as the wormhole scanner's target. The scanner will then start displaying all the information available for the selected wormhole.

== Availability ==
Price: 2395.0 Cr
Techlevel: 10

== Links ==
Back to: [[Oolite Equipment]]
[[Category:Oolite]]

Wormhole Scanner

2010-02-11T00:39:33Z

Kaks: Created page with '== Overview == Displays detailed information about a targeted wormhole == Use == When in flight, press '''r''' to activate the ship's identification system, and place your targe…'

== Overview ==
Displays detailed information about a targeted wormhole

== Use ==
When in flight, press '''r''' to activate the ship's identification system, and place your target reticle over a wormhole to select it as the wormhole scanner's target.

== Availability ==
Price: 2395.0 Cr
Techlevel: 10

== Links ==
Back to: [[Oolite Equipment]]
[[Category:Oolite]]

Oolite Equipment

2010-02-11T00:21:19Z

Kaks: /* Ship features */

This lists standard equipment (non OXP) available to all players.

== Ship features ==

* [[Advanced Navigational Array]]
* [[Advanced Space Compass]]
* [[Cargo Bay expansion]]
* [[Docking Computers]]
* [[E.C.M. System]]
* [[Escape Pod]]
* [[Extra Energy Unit]]
* [[Fuel Scoops]]
* [[Fuel Tank]]
* [[Galactic Hyperdrive]]
* [[IFF system]]
* [[Military Shield Enhancement]]
* [[Multi-Targeting System]]
* [[Naval energy unit]]
* [[Passenger Berth]]
* [[Scanner Targeting Enhancement]]
* [[Shield Boosters]]
* [[Target System Memory Upgrade]]
* [[Witch fuel injectors|Witchdrive Fuel Injectors]]
* [[Wormhole Scanner]]

== Weapons ==

* [[Beam Laser]]
* [[ECM Hardened Missile]]
* [[Energy Bomb]]
* [[Military Lasers]]
* [[Mining Lasers]]
* [[Missile]]
* [[Pulse Laser]]
* [[Q bomb]]
* [[Twin Plasma Cannon]]

[[Category:Oolite]]

Oolite JavaScript Reference: World script event handlers

2009-12-22T18:37:25Z

Kaks: /* shipSpawned */

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event) 
playerWillEnterWitchspace (NPC ship event) 
playerEnteredNewGalaxy (world event) 
shipWillExitWitchspace (world event) 
shipExitedWitchspace (world event) 

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called after a ship has been added to the system. After a witchspace jump it means that first all ships are added to the system, then all the relevant shipSpawned events are triggered.

this.shipSpawned = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Not Yet Implemented ===

Handlers do not yet exist for the following events:
* Target changed.
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite scripting]]

Oolite JavaScript Reference: World script event handlers

2009-12-22T18:20:12Z

Kaks:

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event) 
playerWillEnterWitchspace (NPC ship event) 
playerEnteredNewGalaxy (world event) 
shipWillExitWitchspace (world event) 
shipExitedWitchspace (world event) 

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called after a ship has been added to the system. After a witchspace jump it means that first all ships are added to the system, then afterwards all the relevant shipSpawned events are triggered.

this.shipSpawned = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Not Yet Implemented ===

Handlers do not yet exist for the following events:
* Target changed.
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite scripting]]

Oolite JavaScript Reference: Ship script event handlers

2009-12-22T18:17:32Z

Kaks:

This page provides a list of event handlers which can be implemented by [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Ship scripts are linked to Oolite either using the appropriate [[shipdata.plist#script|shipdata.plist]] setting or via javascript using [[Oolite JavaScript Reference: Ship#setScript|ship.setScript]] and are only active when the ship is present. More than one ship can be assigned the same ship script. Each ship will create its own separate copy of the script, each one independent from the others.

(this page has just recently been split from world script event handlers, bear with us while we tidy up the content)

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

=== Witchspace Jumps ===

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the recommended time to set up elements which need to be present in-system when the player arrives.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition.

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>escortAttack</code> ====

The <code>escortAttack</code> handler is send to all escorts of a mothership that are deployed. The mother first changes the escorts AI to interceptAI.plist and also sets the escort target to his own target before sending this handler to the escorts.

this.escortAttack = function(target)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function( whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. There is no parameter provided to identify the cloaked ship.

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipEnergyBecameFull </code> ====

The <code>shipEnergyBecameFull </code> handler is called when the energy level reaches it's maximum value again.

this.shipEnergyBecameFull = function()
{
// Your code here
}

==== <code>shipEnergyIsLow</code> ====

The <code>shipEnergyIsLow</code> handler is called every time when a ship gets energy damage while the energy level lies below 25% of it's maximum value.

this.shipEnergyIsLow = function()
{
// Your code here
}

==== <code>shipFiredMissile</code> ====

The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile. (Handler is added in test version 1.74)

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== NPC only ===

==== <code>escortAccepted</code> ====

The <code>escortAccepted</code> handler is called for mother ships that have accepted an escort. The escort simultaneously gets a <code>shipAcceptedEscort</code> event.

this.escortAccepted = function(escortship)
{
// Your code here
}

==== <code>escortDock</code> ====

The <code>escortDock</code> handler is called by a mother ships that uses the AI command: <code>dockEscorts</code>. Escorts are instructed to change AI into dockingAI.plist and enter the ABORT state of this AI after a certain delay. Than this event is send to all his escorts, each with a different delay with 3 seconds spacing.

this.escortDock = function(delay)
{
// Your code here
}

==== <code>offenceCommittedNearby</code> ====

The <code>offenceCommittedNearby</code> handler is only send to police ships in scanner range of a hostile action. It transfers the attacker and the victim to the police vessel.

this.offenceCommittedNearby = function(attacker, victim)
{
// Your code here
}

==== <code>playerWillEnterWitchspace</code> ====

The <code>playerWillEnterWitchspace</code> handler is called just before a witchspace jump starts and after the <code>shipWillEnterWitchspace</code> handler fires. It is send to all ships in the system to signal that the player is about to leave the system. (By jump or by wormhole)

this.playerWillEnterWitchspace = function()
{
// Your code here
}

==== <code>shipAcceptedEscort</code> ====

The <code>shipAcceptedEscort</code> handler is called for ships that are accepted as escort. The mother simultaneously gets a <code>escortAccepted</code> event.

this.shipAcceptedEscort = function(mother)
{
// Your code here
}

==== <code>shipExitedWormhole</code> ====

The <code>shipExitedWormhole</code> handler is called when a ship exits a wormhole.

this.shipExitedWormhole = function()
{
// Your code here
}

==== <code>shipSpawned</code> ====

The <code>shipSpawned</code> handler is called for newly added ships. It does not trigger on adding but on the first update after adding. On a witchspace jump it means that first all ships are added to the system, then afterwards all the shipSpawned() events are triggered.

this.shipSpawned = function()
{
// Your code here
}

==== <code>shipWillEnterWormhole</code> ====

The <code>shipWillEnterWormhole</code> handler is called when a ship enters a wormhole. only)

this.shipWillEnterWormhole = function()
{
// Your code here
}

==== <code>spawnedAsEscort</code> ====

The <code>spawnedAsEscort</code> handler is called for newly added escort ships. It does trigger on adding the ship and before the shipSpawned() handlers is activated. It has the mothership as argument.

this.spawnedAsEscort = function(mother)
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>shipWasScooped</code> ====

The <code>shipWasScooped</code> handler is send to the cargopod when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) The scooper is transferred as argument. The scooper itself gets a trigger on the handler <code>shipScoopedOther</code>. (ship script only)

this.shipWasScooped = function(scooper)
{
// Your code here
}

=== Stations only ===

==== <code>otherShipDocked</code> ====

The <code>otherShipDocked</code> handler is called with a station script only, when an ship docks. It has the docked ship as argument.

this.otherShipDocked = function(whom)
{
// Your code here
}

==== <code>stationLaunchedShip</code> ====

The <code>stationLaunchedShip</code> handler is called with a station script only, when a ship launches. It has the launched ship as argument. 
''Starting with 1.74 is also triggers for player.ship launches.''

this.stationLaunchedShip = function(whom)
{
// Your code here
}

=== Not Yet Implemented ===

Handlers do not yet exist for the following events:
* Target changed.
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: world_script_event_handlers|world_script_event_handlers]]

[[Category:Oolite scripting]]

Oolite JavaScript Reference: Timer

2009-12-21T08:25:43Z

Kaks:

'''Prototype:''' <code>Object</code> 
'''Subtypes:''' none

{{Oolite-class-added|1.70}}

'''Timer''' objects are used to perform tasks after a delay or on a repeating schedule. When a timer is created, it is given a function to call, and a ''delay'' and an optional ''interval'' in seconds in [[Time scales in Oolite#Game real time|game real time]]. The ''next fire time'' of the timer is set to the current time + the delay. When the game clock reaches (or passes) the next fire time, the function is called. If the timer has a positive interval, the interval is added to the next fire time. Otherwise, the timer stops.

'''Note:''' in order for a timer to work consistently, you must keep a reference to it as long as it is in use. The easiest way is to make it a property of your script: <code>this.timer = new Timer(this, this.doSomething, 5, 5)</code>. If this is not done, the JavaScript runtime may delete the timer at any time to free up memory.

'''N.B.:''' Before 1.74, timers associated with ship scripts did not stop when the ship itself died.
If scripting for Oolite 1.73.4 or earlier, either the timer is deleted inside the ship's this.shipDied, or a check for the existence of the ship must be placed inside the timer itself, as in the timers examples at the bottom of this page. Timers run independent of the script and are not deleted with a ship script. When the timer is not stopped and uses a property of a removed ship script, it can crash Oolite.

== Constructor ==
'''new Timer'''(this : Object, function : Function, delay : Number [, interval : Number]) : Timer
Creates a new timer which will call <code>function</code> after <code>delay</code> seconds, and optionally repeatedly every <code>interval</code> seconds. If <code>delay</code> is zero or more, the timer will be started automatically. If <code>interval</code> is 0 or less, the timer will not repeat. If <code>interval</code> is greater than 0 but less than 0.25, it will be rounded up to 0.25.

'''N.B.:''' as of Oolite 1.74, if the first parameter ('this : Object') goes out of scope (usually because the ship attached to the 'this' object is destroyed, or left behind when the player executes a hyperspace jump), the timer will now be stopped and removed automatically.

== Properties ==
=== interval ===
'''interval''' : Number (read/write)
The rate at which the timer repeats. For a one-shot timer, this will be -1. If set to 0 or a negative number, it will be treated as -1. If set to a number between 0 and 0.25, it will be rounded up to 0.25.

=== isPersistent ===
{{Oolite-script-item-deprecated|property|1.74|test}}
'''isPersistent''' : Boolean (read/write)
A persistent timer will continue to run when the game resets (i.e., the player dies or loads a new game). A non-persistent timer will be stopped when the game is reset (but can be restarted using <code>[[#start|start()]]</code>). Timers are not persistent by default.

=== isRunning ===
'''isRunning''' : Boolean (read-only)
<code>true</code> if the timer is running, <code>false</code> if it is stopped.

=== nextTime ===
'''nextTime''' : Number (read/write when stopped)
The next time the timer will fire, if it is running at that time. This can be modified if the timer is stopped. Note that this is an absolute time, not a delay. You can get the current absolute time using <code>[[Oolite JavaScript Reference: Clock#absoluteSeconds|clock.absoluteSeconds]]</code>.

== Methods ==
=== start ===
function '''start'''() : Boolean
Starts the timer, if it is not currently running. This will fail if it is a one-shot timer (i.e., its <code>[[#interval|interval]]</code> is -1) ''and'' its <code>[[#nextTime|nextTime]]</code> is in the past. Returns <code>true</code> if successful or the timer was already running, <code>false</code> on failure (i.e., the same as <code>[[#isRunning|isRunning]]</code> after <code>start()</code> is called).

=== stop ===
function '''stop'''()
Stops the timer, if it is currently running.

== Examples ==

Timer connected to ship. When the ship dies or when the player leaves the system, its timer is removed.

this.shipSpawned = function () {
this.shipTimer = new Timer(this, this.testTimer, 10, 10);
delete this.shipSpawned;
};

this.shipDied = function () {
if (this.shipTimer) {
this.shipTimer.stop(); delete this.shipTimer;
}
// other shipDied actions.
...
};

this.playerWillEnterWitchspace = function () {
if (this.shipTimer) {
this.shipTimer.stop(); delete this.shipTimer;
}
...
};

this.testTimer = function () {
// main timer code.
...
};

Timer connected to ship. The timer itself keeps track of the ship it's attached to, and removes itself when necessary.

this.shipSpawned = function () {
this.shipTimer = new Timer(this, this.testTimer, 10, 10);
delete this.shipSpawned;
};

this.testTimer = function () {
// stop the timer if its associated ship doesn't exist anymore
if (!this.ship || !this.ship.isValid) {
log(this.name, "ERROR detected; Timer fired but this.ship is undefined");
if (this.shipTimer) {
this.shipTimer.stop();
delete this.shipTimer;
}
return;
}
// main timer code.
...
};

'''N.B.:''' as of Oolite 1.74, timers will be removed automatically by Oolite when the 'this' object goes out of scope, without the need to use any of these examples.

[[Category:Oolite scripting]]

Oolite JavaScript Reference: World script event handlers

2009-12-11T17:40:18Z

Kaks: /* playerEnteredNewGalaxy */

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event) 
playerWillEnterWitchspace (NPC ship event) 
playerEnteredNewGalaxy (world event) 
shipWillExitWitchspace (world event) 
shipExitedWitchspace (world event) 

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Not Yet Implemented ===

Handlers do not yet exist for the following events:
* Target changed.
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite scripting]]

Oolite JavaScript Reference: World script event handlers

2009-12-11T17:39:03Z

Kaks:

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. Use this event to set up elements which need to be present in-system after the player exits witchspace.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before shipWillExitWitchspace.

the sequence of events for a player jumping to a different galaxy is as follows:

shipWillEnterWitchspace (world event)
playerWillEnterWitchspace (NPC ship event)
playerEnteredNewGalaxy (world event)
shipWillExitWitchspace (world event)
shipExitedWitchspace (world event)

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Not Yet Implemented ===

Handlers do not yet exist for the following events:
* Target changed.
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite scripting]]

Oolite JavaScript Reference: World script event handlers

2009-12-11T17:11:35Z

Kaks:

This page provides an exhaustive list of event handlers which can be implemented inside world scripts [[Scripting Oolite with JavaScript|JavaScript scripts for Oolite]].

Most event handlers can be used both in world scripts and in ship scripts. Generally speaking, handlers starting with "ship" can be used for both scripts and those starting with "player" are meant only for the player (= can only be used in a world script). Exceptions on this rule are mentioned with the individual handlers below.

World scripts can be either found inside Config\script.js, or be distinctly named .js files inside the Scripts directory - in the latter case, the worldScript.plist will list the active world scripts.

World scripts are always active.

=== Game State ===

==== <code>startUp</code> ====

The <code>startUp</code> handler is called after all OXPs have been loaded. It can be used to do one-off initialisation such as registering to listen for certain keystrokes etc. (world script only)

this.startUp = function()
{
// Your code here
}

==== <code>reset (removed in 1.74)</code> ====

The <code>reset</code> handler is called whenever the player is respawned, such as after dying or when loading a saved game. It should be used to reset any local state in the script. (world script only)

this.reset = function()
{
// Your code here
}

in 1.74 the startUp event is called in its place, eliminating the need for two separate events.

=== Docking ===

==== <code>shipWillDockWithStation</code> ====

The <code>shipWillDockWithStation</code> handler is called at the beginning of the docking tunnel effect.

this.shipWillDockWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == nil", "ship.status == STATUS_DOCKING"

==== <code>shipDockedWithStation</code> ====

The <code>shipDockedWithStation</code> handler is called at the end of the docking tunnel effect.

this.shipDockedWithStation = function(station)
{
// Your code here
}
At this moment "ship.dockedStation == the station", "ship.status == STATUS_DOCKED" and "gui_screen" is either GUI_SCREEN_STATUS or GUI_SCREEN_REPORT. However, any identical handler from an other oxp could have changed those values. Never count on it but double check when important.

==== <code>shipWillLaunchFromStation</code> ====

The <code>shipWillLaunchFromStation</code> handler is called at the beginning of the launch tunnel effect. (world script only)

this.shipWillLaunchFromStation = function(station)
{
// Your code here
}

==== <code>shipLaunchedFromStation</code> ====

The <code>shipLaunchedFromStation</code> handler is called at the end of the launch tunnel effect. (The station parameter is added at release 1.73)

this.shipLaunchedFromStation = function(station)
{
// Your code here
}

==== <code>playerStartedAutoPilot</code> ====

The <code>playerStartedAutoPilot</code> handler is called when the player starts autopilot docking. It is not called for the instantaneous dock command.

this.playerStartedAutoPilot = function()
{
// Your code here
}

==== <code>playerCancelledAutoPilot</code> ====

The <code>playerCancelledAutoPilot</code> handler is called when the player cancels autopilot docking.

this.playerCancelledAutoPilot = function()
{
// Your code here
}

==== <code>playerDockingRefused</code> ====

The <code>playerDockingRefused</code> handler is called when a station refuses to provide autopilot docking instructions.

this.playerDockingRefused = function()
{
// Your code here
}

==== <code>playerRequestedDockingClearance</code> ====

The <code>playerRequestedDockingClearance</code> handler is called when a station answers on a docking request of the player by targeting the station and pressing L (shift-l).

this.playerRequestedDockingClearance = function(message)
{
// Your code here
}

Message is a string and can take the values: "DOCKING_CLEARANCE_GRANTED", "DOCKING_CLEARANCE_DENIED_TRAFFIC_OUTBOUND", "DOCKING_CLEARANCE_DENIED_TRAFFIC_INBOUND", "DOCKING_CLEARANCE_DENIED_SHIP_FUGITIVE", "DOCKING_CLEARANCE_NOT_REQUIRED", "DOCKING_CLEARANCE_EXTENDED" or "DOCKING_CLEARANCE_CANCELLED". (Feature is added with Oolite 1.72)

=== Witchspace Jumps ===

==== <code>playerStartedJumpCountdown</code> ====

The <code>playerStartedJumpCountdown</code> handler is called when the user starts a witchspace or galactic witchspace jump countdown. The <code>type</code> parameter is a string specifying which type of jump is occuring; currently, the possible values are “standard” and “galactic”. Other values may be added in future.

this.playerStartedJumpCountdown = function(type)
{
// Your code here
}

==== <code>playerCancelledJumpCountdown</code> ====

The <code>playerCancelledJumpCountdown</code> handler is called when the user cancels a witchspace or galactic witchspace jump countdown.

this.playerCancelledJumpCountdown = function()
{
// Your code here
}

==== <code>playerJumpFailed</code> ====

The <code>playerJumpFailed</code> handler is called at the end of a witchspace or galactic witchspace countdown, if the jump is not possible. The <code>reason</code> parameter is a string specifying why the jump failed; currently, the possible values are “blocked”, “too far” and “insufficient fuel”. Other values may be added in future.

this.playerJumpFailed = function(reason)
{
// Your code here
}

==== <code>shipWillEnterWitchspace</code> ====

The <code>shipWillEnterWitchspace</code> handler is called immediately before a witchspace jump, while the player is still in the starting system. The <code>cause</code> parameter is a string specifying what sort of jump is occuring; currently, the possible values are “standard jump”, “galactic jump” and “wormhole”. Other values may be added in future.

this.shipWillEnterWitchspace = function(cause)
{
// Your code here
}

==== <code>shipWillExitWitchspace</code> ====

The <code>shipWillExitWitchspace</code> handler is called as a witchspace jump concludes. When it is called, the player is (from a program perspective) in the destination system, but the tunnel effect has not yet been shown. This is the reccomended time to set up elements which, so to speak, were already there when the player arrived.

this.shipWillExitWitchspace = function()
{
// Your code here
}

==== <code>shipExitedWitchspace</code> ====

The <code>shipExitedWitchspace</code> handler is called after a witchspace jump has concluded and the tunnel effect has been shown.

this.shipExitedWitchspace = function()
{
// Your code here
}

==== <code>playerEnteredNewGalaxy</code> ====

The <code>playerEnteredNewGalaxy</code> handler is called just before a witchspace jump starts.

this.playerEnteredNewGalaxy = function(galaxyNumber)
{
// Your code here
}

=== Enter/Exit Aegis ===

==== <code>shipEnteredStationAegis</code> ====

The <code>shipEnteredStationAegis</code> handler is called when the player enters the aegis of the main-station (2x scanner range from main-station). Other stations than the main-station don't give aegis messages.

this.shipEnteredStationAegis = function(station)
{
// Your code here
}

==== <code>shipExitedStationAegis</code> ====

The <code>shipExitedStationAegis</code> handler is called when the player leaves the aegis of the main-station (2x scanner range from main-station).

this.shipExitedStationAegis = function(station)
{
// Your code here
}

==== <code>shipEnteredPlanetaryVicinity</code> ====

The <code>shipEnteredPlanetaryVicinity</code> handler is called when the player enters the planet aegis (3x planet radius).

this.shipEnteredPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipExitedPlanetaryVicinity</code> ====

The <code>shipExitedPlanetaryVicinity</code> handler is called when the player leaves the planet aegis (3x planet radius).

this.shipExitedPlanetaryVicinity = function(planet)
{
// Your code here
}

==== <code>shipApproachingPlanetSurface</code> ====

The <code>shipApproachingPlanetSurface</code> handler is called when the player is very close to the planet (crosses a border ± 500 meter above the surface).

this.shipApproachingPlanetSurface = function(planet)
{
// Your code here
}

==== <code>shipLeavingPlanetSurface</code> ====

The <code>shipLeavingPlanetSurface</code> handler is called when the player leaves the planet (crosses a border ± 500 meter above the surface).

this.shipLeavingPlanetSurface = function(planet)
{
// Your code here
}

=== Combat ===

==== <code>alertConditionChanged</code> ====

The <code>alertConditionChanged</code> handler is called when the player’s alert status (<code>[[Oolite JavaScript Reference: object model#player|player]].alertCondition</code>) changes. Only the player and stations have an alert condition. (world script and station scripts)

this.alertConditionChanged = function(newCondition, oldCondition)
{
// Your code here
}

==== <code>playerTargetedMissile</code> ====

The <code>playerTargetedMissile</code> handler is called when the player targets the nearest missile by pressing T (shift-t) on the keybord.

this.playerTargetedMissile = function(missile)
{
// Your code here
}

==== <code>shipAttackedWithMissile</code> ====

The <code>shipAttackedWithMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>whom</code> the identity of the ship that launched the missile.

this.shipAttackedWithMissile = function(missile, whom)
{
// Your code here
}

==== <code>shipBeingAttacked</code> ====

The <code>shipBeingAttacked</code> handler is called when a laser shot hits. <code>whom</code> the identity of the ship that attacked.

this.shipBeingAttacked = function(whom)
{
// Your code here
}

==== <code>shipBeingAttackedByCloaked</code> ====

The <code>shipBeingAttackedByCloaked</code> handler is called when a laser shot from a cloaked ship hits. Guess what, there is no parameter because he is cloaked!

this.shipBeingAttackedByCloaked = function()
{
// Your code here
}

==== <code>shipDestroyedTarget</code> ====

The <code>shipDestroyedTarget</code> handler is called when the target gets destroyed. <code>target</code> contains the destroyed target entity. This command is always preceded by the <code>shipLostTarget</code> handler.

this.shipDestroyedTarget = function(target)
{
// Your code here
}

==== <code>shipDied</code> ====

The <code>shipDied</code> handler is called when the ship or player dies. Expect a <code>reset()</code> shortly when it is the player ship.

this.shipDied = function(whom, why)
{
// Your code here
}
'''whom''' contains the entity that caused the kill. '''why''' is the cause written as string and is one of: "removed", "hit a planet", "energy damage", "scrape damage", "heat damage", "cascade weapon". 
("cascade weapon" is new in 1.74 and "removed" / "energy damage" were accidentally switched in 1.73)

==== <code>shipFiredMissile</code> ====
{{Oolite-prop-added|1.74}} 
The <code>shipFiredMissile</code> handler is called when a missile is fired. <code>missile</code> contains the missile entity and <code>target</code> the identity of the target. The handler is send to the ship that launched the missile.

this.shipFiredMissile = function(missile, target)
{
// Your code here
}

==== <code>shipLostTarget</code> ====

The <code>shipLostTarget</code> handler is called when the target gets lost. <code>target</code> contains the lost target entity. (As with Oolite 1.71 this is not yet working properly. It returns not the right target but just "unknown". It does nothing when target lost because of "out of range")

this.shipLostTarget = function(target)
{
// Your code here
}

==== <code>shipTargetCloaked</code> ====

The <code>shipTargetCloaked</code> handler is called when the target cloakes.

this.shipTargetCloaked = function()
{
// Your code here
}

=== Equipment ===

==== <code>equipmentDestroyed</code> ====

The <code>equipmentDestroyed</code> handler is called when equipment gets destroyed completely beyond repair. (in strict mode) (world script only)

this.equipmentDestroyed = function(equipment)
{
// Your code here
}

==== <code>equipmentDamaged</code> ====

The <code>equipmentDamaged</code> handler is called when equipment get damaged. (world script only)

this.equipmentDamaged = function(equipment)
{
// Your code here
}

==== <code>playerBoughtEquipment</code> ====

The <code>playerBoughtEquipment</code> handler is called when equipment is bought at the outfit screen.

this.playerBoughtEquipment = function(equipment)
{
// Your code here
}

==== <code>playerBoughtNewShip</code> ====

The <code>playerBoughtNewShip</code> handler is called when a new ship is bought. May be needed to re-evaluate the old equipment as buying a new ship does not trigger equipment removal.

this.playerBoughtNewShip = function(ship)
{
// Your code here
}

=== Other ===

==== <code>compassTargetChanged</code> ====
{{Oolite-prop-added|1.74}} 
The <code>compassTargetChanged</code> handler is called when a new target is selected. Mode can be any of the following:

COMPASS_MODE_BASIC
COMPASS_MODE_PLANET
COMPASS_MODE_STATION
COMPASS_MODE_SUN
COMPASS_MODE_TARGET
COMPASS_MODE_BEACONS

script example

this.compassTargetChanged = function(whom, mode)
{
log(' Now targeting ' + whom);
// Your code here
}

==== <code>guiScreenChanged</code> ====

The <code>guiScreenChanged</code> handler is called when the guiScreen changes. 1.71 only transfers the "to" screen. 1.72 will also transfer the "from" screen. Note that the screen can have changed again in the meantime. (world script only)

this.guiScreenChanged = function(to, from)
{
// Your code here
}

==== <code>missionChoiceWasReset</code> ====

The <code>missionChoiceWasReset</code> handler is called when the mission choice is set to null via script (either using the legacy script method resetMissionChice, or using mission.choice = null; in javascript)

this.missionChoiceWasReset= function()
{
// Your code here
}

==== <code>missionScreenEnded</code> ====

The <code>missionScreenEnded</code> handler is called when the missionscreen ends. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.missionScreenEnded = function()
{
// Your code here
}

==== <code>missionScreenOpportunity</code> ====
{{Oolite-prop-added|1.74}} 
The <code>missionScreenOpportunity</code> handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended. (world script only)

this.missionScreenOpportunity= function()
{
// Your code here
}

==== <code>reportScreenEnded</code> ====
{{Oolite-prop-added|1.73}}
The <code>reportScreenEnded</code> handler is called when the last arrival-report screen ends. This is a screen that should not be written by a missionscreen. The code should wait until this eventhandler fires. Note that an other script may have put up a new missionscreen in the meantime. (world script only)

this.reportScreenEnded = function()
{
// Your code here
}

==== <code>shipCollided</code> ====

The <code>shipCollided</code> handler is send after a collision with otherShip.

this.shipCollided = function(otherShip)
{
// Your code here
}

==== <code>shipScoopedOther</code> ====

The <code>shipScoopedOther</code> handler is called when a ship scoops scripted_cargo. ("cargo_type" = CARGO_SCRIPTED_ITEM) Other cargo, even scooping escapepods, doesn't trigger a handler. The scooped item is transferred as argument. The scooped cargo itselfs gets the handler: <code>shipWasScooped</code> with the scooper as argument.

this.shipScoopedOther = function(whom)
{
// Your code here
}

==== <code>shipLaunchedEscapePod</code> ====

The <code>shipLaunchedEscapePod</code> handler is called when the player bails out. This will be followed by a <code>shipWillDockWithStation()</code>/<code>shipDockedWithStation()</code> pair after a few seconds.

this.shipLaunchedEscapePod = function(escapepod)
{
// Your code here
}

==== <code>tickle</code> ====

The <code>tickle</code> handler is called periodically-ish, whenever the old [[property list|plist]] scripts are updated. For performance reasons, it is reccomended that you avoid using this if possible, but it may be needed until the planned timer mechanism is implemented. (world script and ship scripts)

The <code>status</code> parameter is a string containing the player’s current status - “STATUS_IN_FLIGHT” and “STATUS_DOCKED” being commonly-seen examples.

this.tickle = function(status)
{
// Your code here
}

=== Not Yet Implemented ===

Handlers do not yet exist for the following events:
* Target changed.
* Cloaking device events.

If there are other events you would like to be able to respond to, please write a request [http://www.aegidian.org/bb/viewtopic.php?t=3296 on the forum].

'''See also:''' [[Oolite JavaScript Reference: ship_script_event_handlers|ship_script_event_handlers]]

[[Category:Oolite scripting]]