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://psteamcommunity.yuanyoumao.com/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.

@titanbass1: Is this mod working for you then?

@titanbass1: Thanks!

I don't think adding an entirely new relationship category is something that's possible with the regular modding tools, but even in vanilla it's possible for a parent and child to be rivals (still limited to one rivalry, though)

This isn't related to the mod, but I'm curious if there is a mod that adds different relationship bonuses for parents, children, and grandparents. Right now the game treats parents and children as friends with block chance increases when adjacent. It seems like a missed opportunity for a new relationship bonus category and I don't know if another mod has covered this or not.
Great work on this fix.

I think the easiest way would probably be joining the official discord (https://discord.gg/wildermyth) and sending me a DM with the campaign folder and legacy.json.zip file.

I may not have a chance to look at it before the weekend, though.

Right, so a reroll got another random kid, this time with both soulmate parents. So I've probably screwed something up somewhere... what's the best way to get what I hope is the right save to you?

Right, because I couldn't find the original save game, started a new one making sure one pair were locked soulmates who previously had kids. I'll figure out tossing out an interval save after I redo this battle because I got another kid to the other random heroes... again.

It has been working for me with the default load priorities, but it might be safer to give the fix a slightly higher number?

...something really stupid just occurred to me. I'd never messed with the load order because it looked like they were in the right order... but if I was to manually set the patch to load a little lower than the original mod, could that fix it?

I just did a test campaign with a couple with 3 playable children in legacy and one hero with no children in legacy and I was able to get the legacy children to join (and sometimes a new child from the other hero). Let me know about the save thing when you have the chance!

Pretty sure everyone has random children checked. Did three or four games after, didn't see any legacy joinings then either, so hopefully not just luck? It's past midnight here, but I'll see about figuring out the save thingy for you tomorrow or thereabouts. Appreciate the help!

Okay, I don't think any of those mods should have caused an issue. Both of the heroes in the couple had "Allow Random Children" checked? Also, it's possible you may have just been unlucky. Would you be willing to join the Wildermyth discord and send me a copy of the campaign save from before the chapter interval where the child joined along with you legacy? That would make it a lot easier for me to figure out what is happening.

Ah, and yes, the full list of mods I'm using was actually what I said for once. Nether Owl, Legacy Children (base), this mod, Wracke's Incursion Defence Pack, and the updated version of My Precious.

Right, so the first run I tried had two heroes who had a total of three possible legacy children between them. In all three children spawns that run, it was a child of the lone wolf dude (literally a wolf) who had no kids at all. It was in the third, fourth, and fifth chapters, so the characters were old enough and their kids were set to playable in the legacy. Does your targeting check the last campaign age of the kid/parent characters in the legacy by accident? That could botch it up rather bad, but it's probably unlikely?

Is it a child of both heroes? If two heroes have a romance that is old enough for them to both be the parents, it may create a new child if there isn't one from both of those parents already. I will have to look back at how the targets work.

Thanks. How many playable children does that hero have in legacy?

It's creating a new child for involved heroes. Other mod wise... I'll find you a list later, but it's mostly minor bits (couple of yours too, notably the Netherowl), an incursion map pack, the My Precious one (not sure if that would affect more than just artefacts?), and this plus the original. Might be one or two more I'll check for later.

@ Terminus_X: Are you using any other mods? Also, I believe if a hero has already been assigned to a town (even if you haven't revealed the town yet or recruited someone else first), they can't be brought in as a child. That might be what's happening?

What behavior are you seeing now? Is it just generating a new hero?

Maybe I'm using this wrong, but it doesn't seem to have been working for me? I have the original in the load order too, so is it just that I only need characters with potential children?

Ah, thanks for this! I'd never actually figured out if it was/wasn't working at all, so this both answers that AND fixes it! Doubly appreciated!