Omann

Pretty good idea. I can't think of a case where that wouldn't work.

I'm looking for a way to interrogate a part to see what it requires. More to the point, I want to be able to identify which engines require oxidizer and which do not. I have a working script for launching an SSTO that selects the engines to activate based on the altitude. I'm currently using the part name, but would like to swap engines models without the need to edit the script. Interrogating the part for resources it supplies is simple, however the engines typically require resources rather than supply them. I'm guessing I would have to query an engine module probably.

That pretty much confirms what I thought. I think I'll try using two KOS processors. One running my navigation. It will crash and need to be restarted. One running my autopilot. It being a separate process should continue running. Or not...

I've been looking for a way to implement an error handler in a script. Specifically, I have a script that accepts site names as arguments and displays heading and distance information. These are stored in a list. When a contract requirement is completed, KSP removes the site from the game. Which quickly clobbers my script trying to access a no longer existing object. What I'm wondering, is there a common method for identifying such an object within the script and removing it or skipping over it in my list. In other languages I would probably use a, "try" block.