Ha, no, I just crippled the function to work on all systems.
I guess it comes down to language and interpretation. I agree with your in-game/out-game dichotomy and most oxp's follow it; look at how many entries are in Ship Systems. Telescope Options belongs there but I don't like the name. Telescope Settings? Telescope Configuration? Telescope Levers & Dials?
If we were starting fresh, Config for AddOns should probably go in the Game category but it's part of the game's lexicon and there's no changing it now.
There is just the one oxp, Station Options; it's totally generic. Other oxp's can 'register' to use it.
All an oxp needs to create an F4 entry is to create/add to entries in the
Config/missiontext.plistfile, add a call to
StartUpComplete()function and add Station Options as a required oxp in their manifest. Along with the readme is a
missiontext-template.plistfile in Station Options with instructions & examples for the entries they will need.
The reason I created the
telescope_StationOptions.oxpwas to get you a working example for an existing oxp (Telescope 2.0 is currently in many pieces scattered over my workshop). The initial intent was to have an author flesh out the
Config/missiontext.plistfile and Station Options would do the heavy lifting. I never thought about creating Station Options for someone else's oxp until your offer to help.
If I may suggest a plan of attack, examine
telescope_StationOptions.oxpto see how it was done. There are only a handful of code lines (you can ignore both
_loadSavedOptions() & playerWillSaveGame()as that's specific to Telescope) and the missiontext was mostly cut/paste from the readme. As you're new to coding, you are well suited to find the places I skip relevant details. The
missiontext-template.plistcan be a template for the wiki; you're job is to make it comprehensible. The more questions you ask the better!