Hardwire wrote:I had a second son who was betrothed to the daughter of another Duke-level Lord to gain a powerful alliance and he got sucked up by the Kingsguard event. He was still betrothed after joining the Kingsguard, so I wasn't sure what would happen when she came of age, and it was a little annoying, so I modified the event file. I added "is_betrothed = no" under all of the "is_married = no" checks, and that took care of the problem.
I think the son was the only valid character because he kept getting selected on reload. After I modified the event, another Kingsguard replacement wasn't found for about a year. I kept checking, and eventually another replacement was selected, so the event still works.
Anyway, just a heads-up that you may want to add "is_betrothed = no" to all of the "is_married = no" checks.
Wolfgang Pauli wrote:]It'd be easier to just break betrothals. We have few enough candidates for the Kingsguard as it is.
Hardwire wrote:Wolfgang Pauli wrote:]It'd be easier to just break betrothals. We have few enough candidates for the Kingsguard as it is.
You could do that, but since the AI doesn't seem to initiate betrothals, it's only going to screw the player. If a player wants a character to be ineligible, they can just marry them off to whoever right away. Betrothals, at least the way I use them, are mainly for securing alliances.
AlecTrevelyan006 wrote:That worked well for Tywin Lannister.
Users browsing this forum: No registered users and 1 guest