Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Even setting it to just 1 trait required from the pool and it can't find a single pawn with any trait from a large pool of possible traits. Hell even setting it to 0 traits required from the pool and it can't find a pawn 😅
It seems like it's not working as intended.
Thanks a lot for the mod, however, the mod only works when I select one trait - it doesn't work when I select more than one trait in the filter menu - am I alone?
literally none of the options come up at all
Accessing TicksAbs but gameStartAbsTick is not set yet (you most likely want to use GenTicks.TicksAbs instead).
Tested in the state of 3 DLC (I don't have Anomaly), rerolling the character too many times will also cause the memory to slowly increase.
It seems that the memory leak problem is caused by the original version, and this mod just exacerbates the process.
Manual rerolls can detect memory increases, and the increase in memory under violent rerolls can be imagined.
The comments section reported that the crash after rerolling is likely due to this reason. Including being unable to enter the map afterwards.
The solution is simple: just go back to the previous screen (either the map or ideology selection). You may need to do this a few times to make it work. If the reroll count resets to zero, the filter should start working again.
Once you find pawns that suit your criteria, save them, because sometimes the filter will break again. Also, the "Allow None" filter can cause the issue sometimes. There's no error log, so I'm not sure which mod is responsible for the bug, probably a trait mod, since I have a few of those along with that forbidden mod.