All the children I have in my game are being born as secret children and are incorrectly listed as the stepchild of their biological father.
At first, I thought it was mods, so I went through ever...
Ideas
PC version, playing with mods.
MCCC, BS Drugs (Deleted).
Started as all children were born illegitimate, but after I deleted BS drugs (there was some exception related to cheks queue) and adjusted all possible related to children MCCC moduls, ALL kids started to be born legitimate.
So, I did some tests with and without mods.
There is still a problem:
If the family where the child is to be born is not actively played at the moment of birth, all kids are born legitimate, even though this is clearly an affair.
It prevents drama and scandalls to happen.
It happens no matter active or deleted MCCC.
Do not matter whether the family is in the played category or not if you are currently not in the households where birth started.
For me, it breaks the gameplay a lot, if playing with several households in some iteration (as I do mostly).
The bag author mentioned that the first time they had mods when the bug occurred, then they removed them.I ran some tests in my game (really took time, can post here all details and full report summary. Please tag me if someone needs it). Did all of these tests because I also have an exception in addition to random legitimate/secret babies happening and random availability to make a secret lover:
AttributeError: 'object_Baby' object has no attribute 'is_being_destroyed'
After this one, it triggers a bunch of other exceptions. Like a domino effect, it slowly corrupts game files and saves within the one game session. So I decided to test.
Long story short, in all cases, bugs and exceptions continue occur if babies were already born in the save with MCCC even after mod removal. Exceptions do not trigger in the short perspective if script mods are removed before the fact of birth.
In all cases, if pregnancy is initiated through the MCCC (version 2026.1.1), babies are born secret (even if mods are deleted and a couple is married at the moment of birth). MCCC announced an update, maybe it will be fixed.
Looks like stories can do that too. My suggestion, it is better to remove MCCC for now or turn off all functions related to pregnancy/adoption initiation, also to turn off child birth/adoptions stories. Or regularly reload game, clear cash and repair files if the session goes wrong. It has to prevent save corruption as temporary solution till fixes occur.
If pregnancy is initiated through the WooHoo, babies are legitimate in any case.
For a moment, I think I have to run more tests for unmarried couples to confirm whether the baby's legitimacy is random or has some clear sequence to occur. For now, it looks random.
None of the babies joined any dynasty automatically in any case, unless they were added by hand.
But, in my situation, it looks like mods are not the main reason; they only trigger a vanilla bug to occur immediately. I saw many more bug reports about the "exception: object_Baby has no attribute is_being_destroyed during zone spin-up while auto-starting caregiver situation" that happened in a bunch of previous updates.
Feels like Royalty & legacy just add more checks associated with this attribute. Method call is wrong or something like this.
It is not specifically a legitimacy bug at first look, but it feels related to all of the baby bugs and may trigger others. New laundry list says it is planned to be fixed this spring/summer, so I`ll be waiting then.
Featured Places
Read First
- EA_Cade1 month ago
The Sims Team