to <DST>" mission work

Alright...

I can't make the 'ferry passengers to <DST>' mission work in my TC/plug-in.

I have four systems all of the same government (151). I want the missions to start in one of those system so I set the available stellar field to 10023 (10000 + 151 - 128). My mission availability is 100% for debugging purposes. If I set the travel stellar to -4 (same stellar) the mission works fine. I can also set it to a specific stellar, such as 128, and it works fine too. But if I set it to -2 (any random inhabited stellar), or 10023 (random stellar of 151 government), the mission won't show up at all. I don't know why this is...

Here's my guess. I have several stellars that are of government 151 that are not visible (the systems they inhabit have a bit that is currently set to be invisible). Perhaps the mission is randomly choosing these systems, and since the systems are invisible, its simply not allowing the mission to go.

The only problem is, if this is the case, you'd think by random starting I would eventually randomly get a hit on a visible stellar for the 151 government that is visible. To make a long story short I tested this to near statistical impossibility.

If you're still with me, do you have any idea as to what is going on, or how I can fix it?

I would guess that all of of the possible spobs are or could be replaced over the course of the game.

From the Bible:

Note: When Nova selects a random mission destination, it attempts to ensure
      that the random destination is: a) more than two hyper jumps away from
      the system where the mission is being offered, and b) a stellar which
      is guaranteed to always exist throughout the course of the game,
      regardless of system swapping. This means that if you have multiple
      systems that occupy the same coordinates at different times in the game
      and not all of them contain stellar object X, no missions will use
      stellar object X as their random destination. (This is to keep the
      player from accepting a mission with a random destination that might
      cease to exist before he gets there!) A further important consequence
      of this restriction is that if Nova detects that a mission whose
      TravelStel or ReturnStel is to be randomly selected will violate this
      rule, it will be prevented from being offered regardless of any other
      availability parameters the mission might have - i.e. if you create a
      mission and Nova refuses to make it available, check the debug log
      to see if the mission couldn't find a suitable nontransient random
      stellar of the desired characteristics.