MatGB wrote:Hmm, also, suitability reports can get messed up on the turn an evacuation or concentration camp completes, given that's a conquered desert homeworld I'm assuming a Trith population has been removed? That can sometimes cause errors.
The planet in question is not the desert one (which is "Eternal Helix Alpha II"), but the radiated one above ("Helix Alpha I").
Nevertheless, I have the sneaking suspicion that you're right on spot here. I just did some testing, and one thing that I can reproduce consistently is that on the turn right after a colony got depopulated (in my test cases the pop died off because not fit for the environment) the suitability report always
has been messed up. That clears up after another turn.
So my guess is that raptor depopulated the planets, and on the turn he got the message that the planet had been depopulated, checked the suitability report and queued an Exobot colony building. The colony got established and died off, he got the pop died off message and queued another Exobot colony (maybe after checking the suitability report once again).
The probem is, he might have checked the report right after depopulation each time, and so got always the wrong numbers.
@raptor: Is this was happened?
Assuming it is, I'm inclined to scrap the options I listed above, just accept this as a known issue for now and go ahead with RC2 tomorrow (Friday). Commenting out the Temporal Anomaly special is pointless in this case, as it actually has nothing to do with that special (the special probably just compounded the effect because of the high malus it applies, and thus made the underlying issue more obvious). And blocking the release for an issue that most likely has been around for a long time now and is probably quite difficult to fix is also something I don't want to do.
Is that decision seconded, do you guys object? Otherwise I'll proceed as proposed.