Standalone mods are modified at little as possible from the FSO release they are based on. BtRL had certain changes which weren't in CVS at the time, but are now, like a new cmdline option for instance. Other changes would just be to enable some helpful user things. Both BtRL and the WCS Prologue require a minimum resolution of 1024x768, so in the Linux and OS X versions at least, the code defaults to using 1024x768 and also presents an error message if anything less than that is used. The user directory is different, to avoid any issues interacting with the general FSO stuff. That also makes it far easier for mod tech support as well.
The APP is changed as little as possible, with the only real differences being exec name and icon file. Those are things easily found in the APP's Info.plist though.
I'm still going over the code for the launcher, but I haven't really had much time to do anything but give it a very quick browse. Other than some memory leaks in the flags.lch parsing, nothing has really jumped out at me yet. One thing that I did just think about as I was writing this message, there isn't a way to enter in custom cmdline options. Not all builds advertise all options, usually for a good reason, so testing said options requires manually editing the cmdline_fso.cfg file if there isn't a way to enter them in the launcher GUI.
And a couple other things to possibly add to the todo list:
- A dropdown for resolution selection would be good, kinda sucks to have to manually enter it in. A custom setting would also be nice, but only if that setting was only usable when running with -window
- If the argument based cmdline options (like -ambient_factor) are going to be in the GUI then they need range checking as well as listing default values and value ranges prominantly in the tool tip (rather than just a copy-paste out of the wiki)
- The -no_emissive_light option doesn't take an argument, it's just left out of flags.lch on purpose.
That's all I really have at the moment though.
