Just dropped a little neat feature before we enter code freeze. This one is quite straightforward, but I think it can be very helpful and practical.
The -load command line parameter is now optional. You do not need it when loading games from the command line, but it doesn't hurt if it's there and it stays there also for compatibility with apps like OoliteStarter, which perform handling of command line args to load games.
So now you can just do $>oolite c:/path/to/savegame/savegame.oolite-save and Oolite will go ahead and load up the specified game and start with it.
Why is this practical? Well, now you can associate the .oolite-save filetype with Oolite itself. On Windows you only need to do this once and after that you can just double-click any savegame to launch Oolite. Once the filetype is associated, you can also go to a cmd window and type the path to the savegame (including the .oolite-save extension) and this will launch the game too. Essentially, your save games become like OS commands.
This is especially nice with the MSIX installer, which I have now modified to do the filetype association automatically. As soon as you install the MSIX you can go to your savegames folder and start double-clicking to launch them with Oolite. You can also right-click on a save file and select "Open with" in the context menu and you will see Oolite appearing as a candidate for opening the file with. And of course, with the MSIX the .oolite-save file type association is destroyed automatically and cleanly if you chose to uninstall the package.
