Duplicate Stellaris - Imperial fiefdom description appears to be incorrect

[Sheld]

Description
Imperial fiefdom description appears to be incorrect

Game Version
3.6.1

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

Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
When using the imperial fiefdom origin, it is stated that the indolent overlord empire personality will not expand unless forced, but it appears to have no qualms about claiming large numbers of systems, resulting in multiple weak empires when it dissolves/enter a civil war by event - empires tat it generally beats effortlessly due to their pathetic size. - see image to show expansion by overlord

Steps to reproduce the issue.
Play a game with the Imperial Fiefdom origin, and don't enclose your overlord. It will expand - I would suggest one with few if any AIs to see the fullest effect

Upload Attachment
File(s) attached

 

[great lakes]

so this one servives. dang it - fiefdom is such a cool idea, but this makes it unplayable

 

[Starfire Breeze]

I tried out a game with this origin and I agree, Imperial Fiefdom is basically so busted as to be completely unplayable with this release. I tried several game starts, and each time, the overlord immediately expands over your guaranteed habitable worlds and bottleneck systems (remember you're only able to build starbases quite infrequently due to the overlord tax), surveys all anomalies in your space, etc.. That's definitely *not* what it says on the tin for the description when creating an empire with that origin.

 

[Rooker75]

Yep. The overlord that "doesn't expand unless forced to" will expand all over the place, including over guaranteed planets and floods the galaxy with dozens of survey ships that prevent the player and other nearby AI getting any anomalies.

 

[Meme_Drone [Qloc]]

Hello!

Thank you for the report!

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