First thing I was hoping for was a set of sexps.. set-scannable and set-not-scannable. They seem to be pretty self-explanatory.
The idea is to set something scannable later in the mission so the player can't scan it once and have nothing happen, but then be told to scan it later (I know you can reset cargo-known already) and have something happen. Kinda seems silly when that is the case.
Second is in regards to asteroid fields. Not sure how possible some of it would be, but that's why I ask.
I'll begin with set-field-active and set-field-passive. The idea is that if a ships sensors get destroyed it becomes unable to avoid asteroids. The best solution I can see, short of hurling asteroids individually with FRED is an active asteroid field.
Added to this would be requests for active-field-target and active-field-ignore. I noticed that Active Asteroid Fields hurl asteroid at ships that are on the escort list. Obviously FSO keeps track somewhere which ships that is. So I was hoping to get a sexp to modify that list without having to actually add ships to the escort list. As I type this, I realize these two could be used without the need for the previous two Asteroid Field sexps. (Make the field active and add ships to the ignore list at the beginning of the mission and remove them as necessary).
