In a multiplayer game that actually got to a proper orbital stage, I had two moon bases orbiting one planet, while an opponent had a single one orbiting another. My opponent had, some fifteen minutes prior, missed my suggestion that he build nukes on the one-moon planet and glass the moon from there, leaving me with the task of sending my first moon base to crash the commander on their moon base. The alarm went off, but the moon did not move for such a long time that I presumed it to be bugged, and thereby doomed never to launch itself. So I kept chucking nukes at the helpless world below from both bases. Lo and behold, however, the planets align just as their Halleys become active. No sooner have I zoomed over to watch the fireworks than does my moon base come zooming over the horizon, erasing a third of the enemy moon's mass, and with it the halleys and any threat of lunar demolition - except the "activity detected" flag, which I take for another bug. Ten or more minutes later, the enemy moon - desolate and barren, with its massive crater staring like some cyclopean eye, crashes into my second moon base, killing my commander. --- It appears, based on this evidence, that there is a planetary "alignment proximity" check going on in the background for moon crashes (and maybe other events in the future). If so, then can we get an "alignment timer" visible for these, and not set off Halleys or other such blaring warnings before the proper time?
