Stellaris - In Breach of Galactic Law when Capturing Tiyanki

[Jammie_Jammie]

Description
In Breach of Galactic Law when Capturing Tiyanki

Game Version
Circinus v3.1415926 (68ca)

What version do you use?
Steam

What expansions do you have installed?
Synthetic Dawn, Utopia, Leviathans Story Pack, Apocalypse, Megacorp, Distant Stars, Ancient Relics, Lithoids, Federations, Nemesis, Aquatics, Overlord, Toxoids, First Contact, Astral Planes, The Machine Age, Grand Archive

Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
When ever I Capture a Tiyanki I get the pop-up of being in breach of galactic law for killing them, is this intended behaviour as the law states that you are not allowed to kill them.

Steps to reproduce the issue.
Capture a tiyanki while the preservation act is passed.

Upload Attachment
File(s) attached

 

[Blastinburn]

Even if it's intentional, there needs to be a way to opt-out of capturing tiyanki in that case as my options are don't use the entire auto-capture feature or randomly breach galactic law.

 

[Levedis]

As i understand it, it is not the capturing that is a problem, but the subsequent culling from your vivarium
Which you CAN selectively disable...
Ok. Only selectively prioritize...

 

[Renira]

As far as I'm aware, this pop-up happens only when an active herd is cleared out. Culling does not affect it. So, if you capture the last tiyanki in the herd, it's considered a "kill". However, I just had a new problem crop up in my game today where I had zero scientists on auto-snare or even near the system with tiyanki. Still, the game said I captured them with a gravity snare, and it popped the message that I killed the herd, putting me once again in breach of galactic law (2nd time this game now) and costing me another 10 years of penalty + 1k energy. I only saw a federation science ship nearby, and I don't know of any automatic planetary or station snare. I even removed the tiyanki lure from my station because I didn't want to risk the breach again. This bug is ridiculous.