This is pretty minor, but felt it is worth pointing out. I was having wormhole connection issues with a custom map I made, and after much troubleshooting I believe InterStarConnections do not generate properly on maps where there are planets with a spawnprobability that come before the wormhole in the planet list.
For example, you design two star systems with 10 planets each with a spawnprobability of 0.5000. Then you add wormholes to each. Everything seems fine, but when you launch the game the wormholes will either not work, or will dump you somewhere other than the intended target because the the wormhole path has had its planetIndex count thrown off by the planets which didn't spawn.
I am about pretty darn sure this is what is happening, because I made a test map where I made one wormhole that is very high in the stack before all of the random spawning planets, and one that has a destination low in the stack. As expected, the "low in the stack" wormhole did not work properly.
I realize this is a small issue, but I thought I would point it out since it I have lost a small part of my sanity trying to identify the problem. Planet connections within the star are not thrown off by some planets not spawning, so I wouldn't expect interStarConnections to be thrown off by some planets not spawning.
The only work-around I can think of is to create your wormhole objects first when building a custom map so they are not affected by any random spawning planets.
If any brilliant people can think of a way to retroactively fix a custom map without scrambling all of the regular star connections, I'd love to hear it.
(As a side note, for the love of god, why does the connection index data come from the relative position in the planet list and not from the planet identifier????)