Confirmed Stellaris - Systems that had a mercenary enclave which got destroyed cannot have a new mercenary enclave. [3.4.3] & [9d15]

[RabbaDooDabba]

Description
Systems that had a mercenary enclave which got destroyed cannot have a new mercenary enclave. [3.4.3] & [9d15]

Game Version
Cepheus v3.4.3 (9d15)

What version do you use?
Steam

What expansions do you have installed?


Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
If a mercenary enclave gets destroyed and you want to found a new mercenary enclave in the same system, the 'There already is an enclave here' flag is not cleared, preventing you from creating a new mercenary enclave.

Steps to reproduce the issue.
Create a mercenary enclave in a system, destroy said enclave and after that, try to create a new mercenary enclave in the same system.

Upload Attachment
File(s) attached

 

[MortiferMaestus]

I have also encountered this issue both in single player and multiplayer. On the lattest, it is pretty annoying as you can end up cramped in 10 systems and 5 of them become useless to implement enclaves after a war that kinda cleaned them at first...

 

[PDX-Nicou]

Same issue here.

 

[nat.hol]

It just happened to me (on 3.8.1), it was a bit annoying as I was doing a 1 system only challenge. Still an ongoing issue it seems.

 

[RabbaDooDabba]

It just happened to me (on 3.8.1), it was a bit annoying as I was doing a 1 system only challenge. Still an ongoing issue it seems.

Yeah, unfortunately this bug is still around :\

 

[MajorContraption]

Bug still exists. Must keep relevant

 

[hart30]

Yeah and the destruction of the enclave deletes the starbase in the system (at least during player war if the player first occupies the starbase and then takes down the enclave).
Then the player (or a awakened fallen empire, or a become the crisis/genocidal empire) can sent a construction ship and build their own outpost there, flipping all planets in the system to their ownership.

 

[Meme_Drone [Qloc]]

Hello!

Thank you for the report!

We have added the issue to our bug database.