Duplicate Stellaris - Can't genetically modify uplifted species that have been assimilated into a hivemind

[Imperitor Foxx]

Description
Can't genetically modify uplifted species that have been assimilated into a hivemind

Game Version
Andromeda v3.12.1 (73 e4)

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.
Playing as an Overtuned hivemind that has taken the Genetic Ascension I cannot modify pops taken from another hivemind. These pops have the uplifted trait and some of them have been assimilated into the other hivemind. I took their planet but now they have no traits to modify when I attempt to do so. In the screenshot you can see the original template which isn't a hivemind but is uplifted, the second is the assimilated version, but I cannot make changes to them. This isn't the only pop there are several in my list exactly like this so this seems to be the source.

Steps to reproduce the issue.
Start as a Overtuned, ravenous swarm hivemind and take genetic ascension.
Capture a pop that was uplifted and assimilated by another hivemind.
Attempt to modify the pop

Upload Attachment
File(s) attached

 

[PointlessSerpent]

I haven't been able to modify uplifted pre-sapients at all since 3.12, even when playing as an individualist biological or individualist machine empire.

 

[Imperitor Foxx]

I haven't been able to modify uplifted pre-sapients at all since 3.12, even when playing as an individualist biological or individualist machine empire.

You are right, I actually can't modify any uplifted pre-sapient. I didn't think to check because they are just food, but I can modify normal pops before I eat them if I wanted to, but not the uplifted pre-sapients.

 

[Druesling]

I can't modify uplifted pops either, even when I go the full biological ascencion and tradition route. Is this by design? What could be the reasoning behind it?

 

[Qloc_Faceless]

Hello!

Thank you for the report!

We are aware of the issue, it has already been added to our bug database.