[1.9.1][317f] Mobilized army stationed at headquarters won't defend against Naval Invasion targeting said headquarters

[Troyen]

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

Yes

Required​

Summary​

[1.9.1][317f] Mobilized army stationed at headquarters won't defend against Naval Invasion targeting said headquarters

Description​

I'm playing India and being Naval Invaded in West Bengal. I mobilized one of my smaller armies and stationed them in Begnal HQ to try and defend against the invasion. However, the army does not count as a defending army. If I attempt to manually station the army on defense via the Naval Invasion "Station Army" interaction, it lists the army as ineligible even though it also lists it at the same HQ as the invasion.

Steps to reproduce​

1. Be the target of a Naval Invasion.
2. Mobilize an army not stationed at the Invasion HQ target and use "Station in an HQ" to move them over for defense.
3. Wait for them to arrive and observe they don't count as defenders.

Game Version​

1.9.1

OS​

Windows

Additional​

Bug Type​

Other

Save Game​

View attachment east india company_1844_11_02.v3

Attachments​

Player Pain​

9

 

[CaesarVincens]

They changed how invasions work, now they create a front

 

[Troyen]

Then why does the naval invasion UI still have a spot for defending armies if no armies can show up there?

 

[DuncanIdahoTPF]

I'm recreating this issue as the US. I have a raised army stationed in the HQ of my capitol (DC). The enemy lands my undefended capitol and occupies it, then a front is created around my captured capitol. I can't assign any army to defend against the naval landing in any way, shape, or fashion.

This is not expected behavior. Sev ~2 issue; I guess as long as I never go to war.

Game Version​

1.9.2

OS​

Windows 11 Pro 24H2

 

[CaesarVincens]

You need to assign the army to defend against the naval invasion specifically, rather than just being stationed in the HQ as pre-1.9.

If the UI isn't working correctly, that's an error for sure, but the mechanic has changed for sure.