Here are some selected parts of the online documentation, that in my
opinion deserve to be delivered with the executable.

----------------------------------------------------------------------
https://raw.githubusercontent.com/OoliteProject/oolite-linux-dependencies/master/README.TXT

Keyboard shortcut F12 toggles full screen/windowed mode.

Full screen or windowed mode as well as full screen mode resolutions may be
selected in "Game Options..." from the main game menu (F2 key). The settings
you select will be saved to your user defaults.

Some older (much older) OpenGL cards can't cope with Oolite in higher
resolutions and graphics rendering modes. This may result in textures not
properly rendered, text rendered as blocks, visual artifacts to be displayed
or low perfomance and frame rate. You may try various settings in the
"Game Options..." menu, to check if any of these issues are addressed.

Folders that get created during execution
=========================================
Note: Please note that the folders described in this paragraph are not
removed when you uninstall Oolite. They are considered as user folders
(e.g. AddOns, screenshots, savegames with player's in-game status, game
settings, etc.) since they contain files generated with the Commander's own
pain and blood. You will have to manually remove them, if you believe that
you do not need them and that you will not need them even if you reinstall
Oolite in the future.

When you run Oolite for the first time a ~/GNUstep/ (~ stands for your home
folder path) folder will be created into your home folder. The GNUstep
backend needs this.

If you decide to use the "Manage Expansion Packs" functionality the
~/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/ folder will be
created to store the AddOns that you install from within the game itself.
This is the only folder (from the folders described in this section) that
the uninstaller will remove in case it finds it empty.

A ~/.Oolite/Logs/ folder is created to store the application Logs folder.
When Oolite is installed as a system-wide application, the .Oolite folder
may also be used to store OXPs visible only by the specific user
(~/.Oolite/AddOns.); see the "Adding AddOns" section below for more details.

A ~/.Oolite/.oolite-run file is also created at first run and its existence
supresses the display of this README.

A ~/oolite-saves/ folder is created when you save your game status as a
Commander.

Finally a ~/oolite-saves/snapshots/ folder is created when you grab an
in-game screenshot (* key) for the first time.

Saved games
===========
Saved games are all saved in ~/oolite-saves/ in your home folder. You can
copy all the existing .oolite-save files (for example, from a Macintosh)
into this folder, and they will appear in the 'Load Commander' menu screen
in the game.

However, if you decide to install add-ons, make sure that if you buy an
add-on ship you don't remove it, because your save game will stop working
if the ship it's based-on doesn't exist!

Adding AddOns
=============
There are over 500 game add ons available - missions, ships etc.
To find out what is currently available, we recommend you start by looking
at the OXP section of the Oolite wiki: http://wiki.alioth.net/index.php/OXP

To install an OXP, just copy the .oxp folder into the Oolite "AddOns" folder.
Next time you run Oolite, the OXP will be loaded.

If Oolite is installed system-wide then you have the following options:
A. OXPs visible by all users:
        Copy the .oxp folder in the <Oolite installation folder>/AddOns/
B. OXPs visible only to a user:
        Copy the .oxp folder in the ~/.Oolite/AddOns/
Options A and B can be combined. Oolite will look for add-ons in both
folders.

If Oolite is installed in your home-folder you may either copy the .oxp folder
into ~/GNUstep/Oolite/AddOns/ or into ~/.Oolite/AddOns/ . In this case putting
some add-ons in one folder and some add-ons in another does not have any
obvious use.

It is suggested that you keep your OXPs in one AddOns folder.

Caution: if you save a game after buying a ship that was in an OXP, then if you
subsequently remove the OXP, that commander file will be rendered useless!

----------------------------------------------------------------------
http://www.oolite.org/whatsnew/

Upgrading an existing installation

Oolite 1.80 should install straightforwardly and be compatible with almost all the OXPs you already have. However, there are a few things you should be aware of when you upgrade:

    The default key configuration has changed - a few new keys have been added, and "dump cargo" has been changed from "d" to "shift-D" to reduce accidental jettisoning. If you have a custom keyconfig.plist you will need to add the new key settings to it. Check the new keyboard control summary from the start screen to see your current settings.
    Other new keys: ';' and ':' control the new HUD multi-function displays in the tutorial or with appropriate expansions installed, and '?' on the long range chart now highlights systems by economy, government or tech level if you have an Advanced Navigation Array fitted.
    Your Commander name and your save game name are no longer required to be the same - you can set your Commander name in the F4 interfaces screen, then call your save games whatever you like. No more "Hello, Commander Jameson37-backup-2" messages from NPCs.
    The graphics detail settings have changed a little. If you have a dedicated graphics card - or even a reasonably modern built-in one - then your computer can probably handle the new "Extra Detail" graphics setting with no problems, but Oolite won't enable this for you.
    If you use a joystick or other controller, the configuration for deadzones and axis response has been significantly upgraded, and you should be able to get much better results. You can update your configuration through Game Options as usual.
    You can now bind any primable equipment you like to the 'tab' and '0' keys through an interface on the F4 screen. The equipment previously on those keys has been converted to primable equipment.
    If you were using Strict Mode before, this now only disables expansion packs, and does not make any other game play changes.

Expansion pack compatibility

    If you have expansion packs in the OXP format already installed, you will need to uninstall them yourself when you install the corresponding OXZ format releases. Oolite cannot automatically determine which OXP folders might correspond to OXZ releases as the OXP format does not contain appropriate metadata. The OXP versions will not show up as already installed in the expansion pack manager, and will potentially cause conflicts if you don't remove them first.
    While we have tried to keep old ship and shipset OXPs working as much as possible with all the changes made to ship AIs, if you have installed a replacement shipset OXP (i.e. an OXP which replaces the look of the default Oolite ships including the Cobra on the start screen) then you should install the Shipset Compatibility OXZ from the 'Miscellaneous' section of the expansion pack manager. This is only necessary temporarily until the OXP authors release an updated version of the shipset.
    Most alternative HUD OXPs have not yet been updated to use the new features available in Oolite 1.80. They will still work, but other OXPs - and the new tutorial - may require the new HUD features for proper running. You may find it better to temporarily remove your HUD OXP until an updated version is available, or use one of the other updated HUDs already available in the expansion pack manager.
    Older versions of the Energy Bomb OXP are not compatible with Oolite 1.80. If you installed this OXP before November 2013, you will need to upgrade to keep this weapon working. The version available in the expansion pack manager works, of course.
