Using the Expansion Pack Manager
- Note that there are many Expansions (OXPs/OXZs) which are not listed in the Manager. See Guide to Unlisted OXPs
- Note that the Expansions Manager depends on this wiki - if this wiki is down (and you are - for example - looking at a backup of this page), you will need a workaround.
Use the four arrow keys to skip between pages and to move up and down on a page.
Press f to filter the selection of 700-odd listed expansion packs. (eg Search for keyword, Search for author, list only uninstalled packs etc)
Guide to Expansions Manager list colours
- Yellow Ready to download and install.
- White Installed and at the current version.
- Cyan Installed; updated pack available for download.
- Orange Ready to download, but Oolite will also download extra packs to make it work.
- Brown Conflicts with an already installed pack.
- Gray Incompatible with this version of Oolite.
- Red Manually installed: cannot also be installed automatically (eg. a tweaked oxp in the AddOns folder)
- Blue Installed but no longer available for download.
Downloading and Unzipping an Expansion for Tweaking
- Go to the Expansion Pack Manager in game.
- Select List installed expansion packs (the second choice at the bottom of the screen).
- It will now show you the list of OXZ files in your ManagedAddOns folder.
- Highlight the one you want to fiddle with and press x.
- Oolite will then extract the OZX to your AddOns folder and add .off to the end of the expanded (was .oxz but is now .oxp) folder.
- Change this .off to .oxp and tweak away to your heart's delight!
- Oolite will now ignore the original version and will run the newly-expanded OXP version in AddOns (with any changes you now make to it).
If you make a mess of it, deleting the .oxp version (in the AddOns folder) will cause Oolite to go back to using the OXZ version (in the Managed AddOns folder).
- The Windows text editor sneaks in invisible bits of code which muck up the OXPs: Avoid it like the plague!
- To edit I'd recommend Edit Pad Lite 8. It's free, won't mess up the file format and is colour coded (so will highlight code typos).
- Eg. If you have missed a , or a " in a text string, it will show up as white rather than yellow, so you can quickly see the mistake. ;-)
- Been a bit of a blessing when I've been C&Ping long lists of procedurally generated text from my latest.log to my array file (adapted from LittleBear's BB post).