Thank you, I seldom send fosterlings, only when I have too many people in my court. However I always accept the children of other rulers though I can not use them as hostagesjordarkelf said:
.-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
.I just had the same thing that a fosterling did not return. The sibling of my current ruler had been send as a fosterling to the Kingdom of Nubia, but is now somehow married to a worthless courtier in the County of Ancona.
Which is a shame, since she is a prodigy with 15, 15, 21, 13 as her stats.
Which is a shame, since she is a prodigy with 15, 15, 21, 13 as her stats.
Which is a shame, since she is a prodigy with 15, 15, 21, 13 as her stats.
<--- (Trying to build up a pattern here)
Had your ruler changed court/moved up in Rank in between sending her off and her end of Fosterling? Were there half-siblings involved at the Court of Nubia?
For a bug like that, i have no problem with giving the advice to go ahead and Mod her (and her worthless husband) back to your court. I'd only do this if you had plans to marry her to one of your courtiers, but if you planned to marry her out, then leave her be.
It's a toss-up on whether to kill the worthless husband or not. You could always get into a RP mindset, and say she married for love, not politics.
I think I still have an event for this...
/Yup, in bugfixes.txt.
Change condition = { type = age value = 17 } to condition = { type = age value = 16 } if you think this bug still hits you -- maybe also change the MTTH to a few days instead of one month. Before it (appeared to be/) was fixed in the betas, I had it as such.
Note that the above was only written for, and should only fire for, the original bug -- where some fosterlings never got their status cleared. It won't work for cases where the fosterling status was cleared by other ways and s/he still ended up in the wrong court.
My best thought on how to prevent that is to set the age condition to 15, and the MTTH to something like 6 months -- this will hopefully force most fosterlings to return home just before the engine fires for them, as this appears to sometimes cause an unwanted effect.
/Yup, in bugfixes.txt.
Code:
character_event = { # Bugfix - Remove trait from adult fosterling & return home
id = 23250
picture = "event_youngsters"
trigger = {
condition = { type = age value = 17 }
condition = { type = trait value = fosterling }
}
mean_time_to_happen = {
months = 1
}
immidiate = { # Remove it!
effect = { type = remove_trait value = fosterling }
effect = { type = courtier_defect value = father }
}
}Note that the above was only written for, and should only fire for, the original bug -- where some fosterlings never got their status cleared. It won't work for cases where the fosterling status was cleared by other ways and s/he still ended up in the wrong court.
My best thought on how to prevent that is to set the age condition to 15, and the MTTH to something like 6 months -- this will hopefully force most fosterlings to return home just before the engine fires for them, as this appears to sometimes cause an unwanted effect.
No changing courts/moving up in rank. Only one of my dynasty at Nubia.
It's a pity, especially because her stats rock so much, but I go for the roleplay method and claim that, after the death of her father, decided that her elder brother (the new Duke) could suck it and left off with a lover.
It's a pity, especially because her stats rock so much, but I go for the roleplay method and claim that, after the death of her father, decided that her elder brother (the new Duke) could suck it and left off with a lover.