View Issue Details

IDProjectCategoryLast Update
0025353AI War 2SuggestionJul 2, 2021 3:51 pm
ReporterDarkshade Assigned ToBadgerBadger  
Status closedResolutionno change required 
Product Version3.305 Fruits Of A Snipe Hunt 
Fixed in Version3.300 Mapsplosion 
Summary0025353: Dark Spire and the Enable Expansion option
DescriptionWith the said option we can switch if the Dark Spire are allowed to spawned new Vengeneance Generators.

What I would ask for is for this option to be able to differentiate between the Vengeance Generators (that spawn invulnerable and need to be hacked before you can destroy them) and the Conquest Vengeance Generators.

Background:
When you play with both the Dark Spire and the Dark Zenith enabled and they're allied to each other the Dark Spire normally spawn Conquest Vengeance Generators on planets owned by the Dark Zenith. Conquest Vengeance Generators I wouldn't mind as you can just destroy them and with that in mind normally enable the Expansion option for the Dark Spire.
However. Due to the back and forth of the Dark Alliance and the AI's often planets end up unowned/empty. If those then happen to be next to planet with a normal Vengeance Generator those then would/could spawn another normal Vengeance Generator on the unowned planet.
If this happens often enough those Vengeance Generator that you need to hack first can become quite annoying, which often leads to that I don't disable the option for the Dark Spire to expand.

So to summarize what I would like.
I want to be able to allow the Dark Spire to expand together with the Dark Zenith and spawn Conquest Vengeance Generators but at the same do not allow that the Dark Spire are able to spawn new "normal" Vengeance Generator.



TagsNo tags attached.

Activities

BadgerBadger

Jun 28, 2021 2:55 pm

manager   ~0062317

Last edited: Jun 28, 2021 2:55 pm

I think the "Disable expansion" option is there for people who just want the AIWC behaviour back, so I don't think allowing conquest VGs to spawn is appropriate.

What you're asking for is a third option, and this sort of proliferation of options leads down a slippery slope to a terribly complicated and overwhelming UI that scares off new players. I don't intend to implement this. Someone is welcome to make a mod of it though, or Chris could decide to pick it up.

Darkshade

Jun 29, 2021 4:29 am

reporter   ~0062321

I'm fully aware that what i was asking for is third/new option, hence while i labeled it as feature-wish.
If it doesn't get implemented that's unfortunate for my personal preference, but totally understandable.

Darkshade

Jul 2, 2021 3:33 pm

reporter   ~0062328

I get the impression that i made this feature wish under a wrong assumption.

So far i thought that even after entering conquest mode (which they automatically do once allied Dark Zenith enter the game), the Dark Spire still would have the ability to spawn normal Vengeance Generators on neutral planets, and that they only would spawn the Conquest Vengeance Generators on planets owned by the Dark Zenith.

After starting a new game today which had the expansion mode enabled, and an immediate invasion of the Dark Zenith, i could observe that the Dark Spire even on neutral planets would spawn Conquest Vengeance generators.

If someone could confirm me that the Dark Spire completly loses the ability to spawn new normal Vengeance Generators once they have entered conquest mode, then this feature wish could, at least from my side, be closed.

BadgerBadger

Jul 2, 2021 3:50 pm

manager   ~0062329

Once the DZ are in conquest mode they only spawn conquest mode VGs. That's the way it has always worked.

Issue History

Date Modified Username Field Change
Jun 27, 2021 9:38 pm Darkshade New Issue
Jun 28, 2021 2:55 pm BadgerBadger Note Added: 0062317
Jun 28, 2021 2:55 pm BadgerBadger Note Edited: 0062317
Jun 29, 2021 4:29 am Darkshade Note Added: 0062321
Jul 2, 2021 3:33 pm Darkshade Note Added: 0062328
Jul 2, 2021 3:50 pm BadgerBadger Note Added: 0062329
Jul 2, 2021 3:51 pm BadgerBadger Assigned To => BadgerBadger
Jul 2, 2021 3:51 pm BadgerBadger Status new => closed
Jul 2, 2021 3:51 pm BadgerBadger Resolution open => no change required
Jul 2, 2021 3:51 pm BadgerBadger Fixed in Version => 3.300 Mapsplosion