Eradicating planet message bug

[Smiling_Spectre]

Several times in my early game I lost my weak planets, that was destroyed by enemy completely. Unfortunately, I forgot to report it right away, so I cannot remember exact message associated with it, but each time it was reported as just opposite to what happened.

I.e. let's say Kor'tahz destroyed my Human planet Zenta I. Message says something like "You totally eradicated Kor'tahz population on the Zenta I".

[Flinx]

It happens when you lose an invasion and the winner exterminated your population. Interestingly if you win an invasion of their planet and choose to exterminate their population, you get slightly different wording but the correct 'direction' of you doing it to them.

If I recall correctly the win/lose notice of invasion is in the military section and the later notice of exterminated population is in the colony section

[Flinx]

Or are you being bombed to dust from orbit?

[Smiling_Spectre]

Or are you being bombed to dust from orbit?

Nah, it was proper invasion.

But why game think that it's _me_, who destroyed population? %)

[Flinx]

Code: Select all

		<turnMsgs>
			<type>__eventMsg</type>		<!-- eg. Our forces have exterminated the Human population on Earth. -->
			<text>Our forces have exterminated the %1% population on %2%.</text>
		</turnMsgs>
		<turnMsgs>
			<type>__eventMsg</type>		<!-- eg. The Varaians have exterminated our people on Earth. -->
			<text>The %1% have exterminated our people on %2%.</text>
		</turnMsgs>
		<turnMsgs>
			<type>__eventMsg</type>		<!-- eg. ...the Human population on Earth... -->
			<text>Our forces have exterminated the %1% population on %2%. And the planet was abandoned due to the hostile environment.</text>
		</turnMsgs>

It looks like what is happening is that the first message is being called when the second is required.

You can switch the order of the two messages in the .xml file to solve the problem (I would imagine).

[Zaimat]

Thanks, I found where it was using the wrong message (when they exterminate you) and will fix it for the next update.