Hey CodeGreen,
With finishing up the first pass of the Solar System++ mod pack, that I'll need to define the starting planet value outside of settings (Data/Control layer), and can't set setting in that layer, so I'll need a bit more control to either turn off APS start-up or hopefull call APS "startOn" wrapper around your code that invokes the logic you currently have.
i.e.

if settings.startup["aps-planet"].value ~= "none" then
APS.startOn(settings.startup["aps-planet"].value)
end

Currently nauvis is actually the "none" logic internally so getting APS to do nothing in data stage is as easy as setting the fixed choice to that (though I should probably rename it to none since that's much more clear as to what the setting is actually doing)

I think the best way to handle the rest of it is a remote interface to override what planet APS will actually teleport players to at runtime, which can be done in on_init. As a baseline it'll probably be something like remote.call("APS", "override_planet", "planet-name"). If that works for you, I'll do it after I'm done with work.

Thanks, I think that should work.

If its Nauvis or "none" either is fine.

I think I'm going to change it to "none" with the update, since I've seen a few people think the mod does something with nauvis selected.

Keeping an eye out for the change. Thanks

Sorry about that, got caught up with some stuff IRL and wasn't able to get around to it until today. Added in 1.1.9

control.lua:14 attempt to index field planet-discovery-nauvis a nil value

can you add a nil check before this, incase nauvis doesn't exist
if not force.technologies["planet-discovery-nauvis"].researched then

Sure, though I suggest not deleting prototypes, instead setting .hidden on them and removing all prerequisites (there's a function for that in utils.lua).
I'll add that in 1.1.12

Wait, I'm dumb, that's my own technology, don't mind me