Description

A system of mine was invaded by the Vodyani, and before they could take the system my fleets arrived and both sides poured reinforcement fleets into the system for many turns. Every turn a new ground battle took place regardless of whether my fleets were protecting the system or not. When I finally ousted the Vodyani fleets the ground invasion dialogue still pops up every turn, altho no infrastructure is destroyed nor population reduced.

Steps to Reproduce

Unknown, first time encountering this bug.

Reproducibility

N/A

Expected Behavior

Ground battles should no longer happen without an enemy fleet in-system.

Version

1.0.52 S5 GOLD-Public 

Notes

See attached save file, the system Nihal at the far southwest end of player controlled territory is the one experiencing a neverending invasion.

Attachments

horatio.zip

I'm pretty sure this is working as intended, because the invasion force is already on the planet and they have to be removed. Removing enemy fleets is a good first step because that cuts off the manpower reinforcement on the system. However, this can lead to the system being completely locked down and unable to grow for a very long time if the invader chooses Guerilla because it increases the survivability of the troops.

I think there should be a health penalty for invading troops or additional attack power for the defending forces if there is no invading fleet supporting the invaders.

I'm pretty sure this is working as intended, because the invasion force is already on the planet and they have to be removed.

That makes sense, but in this situation the battle has been going on without any enemy fleets in-system for 5+ turns.  Every time the battle starts both of our manpower strengths are listed as 700 out of 700, regardless of the casualties last turn. It's usually a minor or major victory for the player, leaving the defending system with ~300 manpower and the invaders with ~200 manpower; next turn both armies are back up to 700. That's what leads me to believe it's a bug.

deepsky wrote:

It's usually a minor or major victory for the player, leaving the defending system with ~300 manpower and the invaders with ~200 manpower; next turn both armies are back up to 700. That's what leads me to believe it's a bug.

That part is probably true

I had the same bug in my game playing as the Sophons. Even when I cleared both the invader's fleet and ground troops, the invasion pop-up would reset and both defending and offending forces would go back to 100%. 

I also noticed that the other 2 planets of the system appear to be occupied (they are not outposts) even though I have the other 2 already occupied. 

how big were the fleets that did the invasion?. if the fleet manpower was way overcap which the ai likes to do its possible for them to have "max" manpower for multiple turns for invasion even after you kill the fleet.

how big were the fleets that did the invasion?

I honestly don't remember, but again, the fact that my manpower resets to 700 everytime makes me believe it's a bug.

deepsky wrote:

how big were the fleets that did the invasion?

I honestly don't remember, but again, the fact that my manpower resets to 700 everytime makes me believe it's a bug.

The manpower at 700 is just the maximum deployment. If both sides of a ton of manpower (quite possible) fights can go on many, many turns.

Yes. The tooltip shows only result of the current turn battle. AFAIK there is no way to see total manpower.

Turn 137, ground battle has not yet resolved. Defense strength in system reported as 0, invader strength reported as 540.

Turn 137, pre battle screen. Defense strength reported as 700, invasion strength also reported as 700.

Turn 137, post battle screen. Both sides took casualties.

Turn 137. Battle is resolved, but popup tooltip is unchanged.

Turn 138. Popup tooltip no longer displays any information about respective sides.

Turn 138, pre battle screen. Both sides again at 700 strength.

Turn 138, post battle screen. Both sides took casualties.

Turn 139. Popup tooltip still not displaying any information about respective sides.

Turn 139, pre battle screen. Both sides again at 700 strength.

Turn 139, post battle screen. Both sides took casualties.

Turn 140. Popup tooltip still not displaying any information about respective sides.

Turn 140, pre battle screen. Both sides again at 700 strength.

Turn 140, post battle screen. Both sides took casualties.

Turn 141. Popup tooltip still not displaying any information about respective sides.

Turn 141, pre battle screen. Both sides again at 700 strength.

Turn 141, post battle screen. Both sides took casualties.

Turn 142. Popup tooltip still not displaying any information about respective sides, and never does again, so I'll stop including those images.

Turn 142, pre battle screen. Both sides again at 700 strength.

Turn 142, post battle screen. Both sides took casualties.

Turn 143, pre battle screen. Both sides again at 700 strength.

Turn 143, post battle screen. Both sides took casualties.

Turn 144, pre battle screen. Both sides again at 700 strength.

Turn 144, post battle screen. Both sides took casualties.

Turn 145, Nihal system information screen. In system manpower listed as 306, gaining 350 per turn. 306 + 350 =/= 700.

Turn 145, pre battle screen. Both sides again at 700 strength.

Turn 145, post battle screen. Both sides took casualties.

Turn 146, Nihal system information screen. In-system defense strength at 33%.

Turn 146, pre battle screen. Both sides again at 700 strength.

Turn 146, post battle screen. Both sides took casualties.

Turn 146, Nihal system information screen. In-system defense strength still listed at 33% despite the battle that just took place.

Over the course of 10 turns the Vodyani lost took 4405 casualties, and these screen shots don't even encompass the first several rounds of the ground battle. So the Vodyani had to land well over 4405 worth of manpower in a single system for this battle to continue this long. I find that highly unlikely, but even if it were the case, why are the player casualties not showing up? I still think this is a bug.