AI mistakes starbases for planets

Messes up the war declaration mechanics.

I remember seeing this awhile ago, but I can't find the thread thanks to the search function only searching titles.

Anyway, when you have transports (or sometimes just one) flying around an AI starbase, it meets the conditions of an invasion buildup and makes the AI likely to declare war.

I post this as a bug, because the text in the war declaration message suggest that Stardock meant for the transport buildup event only to trigger when near planets, not starbases in another race's terriory half the map away from a habitable planet.

Not a gamebreaker, but it's disconcerting to have half the galaxy declare war on you because they had mining starbases in the same sector as an unrelated planet you're in the middle of invading.
2,613 views 1 replies
Reply #1 Top
I agree - it's glitched. The most powerful civ in the game (not me, unfortunately) went from "close" relations to a declaration of war, because they had dropped an influence base next to one of my planets. Next to MY planet, I had a very large number of loaded troop ships and I got "-We know what you're doing..." as a negative relation factor from that point on.

That is BONEHEADED. That is my planet. I am at war. I gave that planet 3 farms specifically to give me a continual supply of troops.

The AI needs to be updated so that troop ships near a starbase NEVER triggers that sort of reaction. Especially since they all spam the entire map with those stupid influence bases. It's a BUG that has a severe effect on game play and throws the entire game out of balance.