View Issue Details

IDProjectCategoryLast Update
0026225AI War 2Bug - GameplayFeb 2, 2022 2:56 am
ReporterApthorpe Assigned ToBadgerBadger  
Severitymajor 
Status resolvedResolutionfixed 
Product VersionBeta 3.791 Network Defragmentation 
Fixed in VersionBeta 3.792 Thread And Entity Sanity 
Summary0026225: ZA taking worlds without pioneers
DescriptionIn this campaign, the ZA would expand, and after their expansion had ended (no pioneers left), I would pop some of their spawners. After the ZA had rushed to retake their non-core territory with overwhelming force, the spawners would then be warped back in well prior to the next expansion phase.

Here are the repro steps for this particular save.
*Note that the ZA territory value is only 4 and no hacks have been conducted to raise this. ZA currently has no pioneers.

1) Attack Lyonesse to draw enemy mega fleet attention. Good if you can take out the spawner, but don't depend on it due to enemy spawning in defenses piecemeal for invulnerability before overwhelming reinforcements arrive.
2) Once mega fleet arrives, divert forces to Esthar and take it.
3) Allow enemy to defeat your defenses on Esthar.
4) Once Esthar is overwhelmed ZA will immediately begin building a new spawner.

If expansion's definition is constrained to only when ZA is taking territory they have never owned, then this is not a bug, but my understanding is that once ZA lose a non-core world, their retaking that world qualifies as expansion.

Beyond this, there are two oddities I observed which I would like ZA dev(s) to confirm are expected.
1) ZA indicates willingness to consistently commit majority of their fighting force to defend non-core territory.
2) ZA is able to 'cheese' to an extent to extend the time their spawners stay alive against overwhelming force. All defenses can be down, but for a time the ZA will keep building defenses in piecemeal fashion, and your fleets will necessarily target the defenses while wasting their excess firepower. If this is not intended, one potential fix could be introducing a time limit before a warping in defense contributes to providing the spawner invulnerability.

This thread provides some context: https://steamcommunity.com/app/573410/discussions/0/

Because severity offers no 'moderate' option, I have opted for major over minor due to the degree this impacts ZA balance.
TagsNo tags attached.

Activities

Apthorpe

Feb 2, 2022 1:14 am

reporter  

attackLyonesse.save (514,165 bytes)

BadgerBadger

Feb 2, 2022 1:40 am

manager   ~0064048

Esthar is in the ZA Core Territory though. You can see it's visually distinct from the planets around it (the planet has little cinkly edges), and the tooltip tells you that it's in the Core Territory.

I'm a bit surprised at how many planets the ZA has though...

BadgerBadger

Feb 2, 2022 1:56 am

manager   ~0064050

The ZA territory logic was mangled in the transition to the BaseInfo/DeepInfo paradigm, unfortunately. Chris noted in his commit message on that changeover that this faction was very complicated, and alas he was right.

The trick is that in the previous regime, the Territory was only cleared at game start time or at game load time; it was never Cleared otherwise. Having the Territory Cleared in stage2 (as is normal in the new regime) requires some additional modifications to the code.

The practical upshot of this seems to be that every planet the ZA captures becomes part of its Core Territory. This is not intentional.

BadgerBadger

Feb 2, 2022 2:13 am

manager   ~0064051

Fixed. This fix will not reduce the size of the Core Territory for the ZA in this current game (so they will be tremendously more impactful than usual), but it should stop their runaway expansion. You may want to start a new game

Apthorpe

Feb 2, 2022 2:56 am

reporter   ~0064052

Thanks, no worries about the save impact. I saltily quit that campaign days ago after a not-after-you hunter ran over my MDC :P

Issue History

Date Modified Username Field Change
Feb 2, 2022 1:14 am Apthorpe New Issue
Feb 2, 2022 1:14 am Apthorpe File Added: attackLyonesse.save
Feb 2, 2022 1:14 am Apthorpe File Added: attackLyonesse.savemet
Feb 2, 2022 1:21 am Apthorpe File Deleted: attackLyonesse.savemet
Feb 2, 2022 1:40 am BadgerBadger Note Added: 0064048
Feb 2, 2022 1:56 am BadgerBadger Note Added: 0064050
Feb 2, 2022 2:13 am BadgerBadger Assigned To => BadgerBadger
Feb 2, 2022 2:13 am BadgerBadger Status new => resolved
Feb 2, 2022 2:13 am BadgerBadger Resolution open => fixed
Feb 2, 2022 2:13 am BadgerBadger Fixed in Version => Beta 3.792 Thread And Entity Sanity
Feb 2, 2022 2:13 am BadgerBadger Note Added: 0064051
Feb 2, 2022 2:56 am Apthorpe Note Added: 0064052