Subscribe to download
Legacy Children Fix

That makes sense, though it still doesn't entirely explain the five person campaign I started with two eligible pairs with three legacy children between them not getting any. Will have a tinker next time I'm playing and see if it works though!

If you have a couple, it'll also only pick a child that already has both of the existing heroes as parents, so if there isn't one eligible, it'll give you a new hero.

I've confirmed that if a hero's legacy child has been assigned to a previously encountered town (even if you recruit someone else from that town), they can't be matched and brought in as a child during chapter intervals, and you will get a new child instead. I expect this is also true for legacy children assigned to towns that have not yet been revealed, and I don't know whether it would be possible, or at least safe, to override this limit.

This is my best guess for why it is failing sometimes. It should naturally be less of issue as you get a larger legacy families, but you could also get around the issue by marking the children of your chosen heroes as unplayable when first starting the campaign, then making them playable again once the campaign starts. I understand would be annoying to do, though.

@Eresian: Thanks for the report. Was the child a possible recruit at any of the towns from any chapter? Would you be able to send me a campaign save and legacy file?

I can confirm that this is not working for me either. Random children even with soulmate parents and a child in legacy. Rerolled several times and I'm always getting random children from these parents.

Ah well, worth a shot.

I removed my local version and subscribed to the workshop version and it is still working for me. I don't believe the modId field is what's causing the issue.

https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3561017358
My attempts at prodding around, even after unloading and reinstalling both this and the original mod, haven't done anything. So I've posted a screenshot of what I think might be the culprit, I'm just not technical enough to fix it.

Might have turned up a lead via poking around in the mod injections. It was trying to use a mod ID that wasn't spelt correctly and thus showed as missing, when looking through the list of available ids turned up the correct one. Just going to check that off and see if it fixes the problems...

Well, found you through the Discord. Settings are messing with messages again, so for now I'll just try and look through the mod code myself to see if anything's gone horribly wrong.