Unfortunately scripting limitations prevent showing who broke away. It's not intentionally left hidden when it could have been shown. We are not that evil. 
-
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.
In CK, there is only BB, lack of diplomacy and bad traits (aside from kinslayer) that keeps your realm intact, engine-wise. And since you can breed people with high diplomacy, can steer your way around most bad traits, and can cheese remove BB fairly quickly by simply appointing some bishops, these events are about the only thing you can't avoid at all, only reduce the likelyhood. Giving a way to avoid them entirely isn't right.CatKnight said:
Relatives as I said, just like primary heir in elective, should be less likely. For the primary heir, its basically should be limited to it actually happening, not RoF. This would be appropriate because its just like someone who is second guessing himself, undecided which path he most likes, security and patience or freedom and immediacy.CatKnight said:
For relatives, its a matter of loyalty, but loyalty only goes so far. And the check for family is quite difficult (sicne we have no condition for a family id)
IMO 1.1 modifier for primary heir, 1.01 for other heir are descent enough to convey this.
ulmont said:
Doesn´t work, since then the vassal could become more loyal than before when the liege changes and the new king has different traits.
Does that really matter, though? I would have thought a new king should reset the relationship.Grosshaus said:
-Richard Campbell.
Having the events fire based upon being distant from the ruler is not the most easiest triggers for the CPU, so I'd rather not have multiple versions of them.
How does the CK engine evaluate? If it's a short-circuit process (and surely it is, or the system would require a Cray), then putting the ruler trait requirements first would make multiple versions not a problem, right?Byakhiam said:
That is,
Code:
condition = { type = and
condition = { type = ruler }
condition = { type = is_vassal }
condition = { type = liege { condition = { type = trait value = suspicious } } }
}
condition = { type = and
# massive area check goes here
}-Richard Campbell.
check out the events first and remember any_xxxx triggers are among the most cpu intensive.
Jinnai, whatever you may think, I can read the events. In fact, I've read them better than you, because the distant vassal breaking free (and the catholic middle east breaking free event) event does not use an any_xxxx trigger at all.Jinnai said:
If you check out the event first, you will find it does a csc check to the liege before going to the any text:
Code:
#################################
# Distant vassals break free, general event
character_event = {
id = 6104
picture = "event_claim"
trigger = {
condition = { type = is_vassal }
condition = { type = age value = 18 }
condition = { type = not value = { type = atwar } }
condition = { type = not value = { type = trait value = modest } }
condition = { type = or
condition = { type = martial value = 5 }
condition = { type = stewardship value = 5 }
}
condition = { type = liege
condition = { type = and
condition = { type = not value = { type = diplomacy value = 9 } }
condition = { type = not value = { type = chancellor_csc condition = { type = diplomacy value = 12 } } }
condition = { type = not value = { type = prestige value = 5000 } }
}
}
# massive area stuff begins here
condition = { type = or
condition = { type = and
condition = { type = county }
condition = { type = not value = { type = duchy } }
condition = { type = or
condition = { type = and
condition = { type = region value = britain }
condition = { type = capital condition = { type = region value = britain } }
condition = { type = or
condition = { type = and
condition = { type = capital condition = { type = area value = 3 } } # Eire
condition = { type = not value = { type = liege condition = { type = capital condition = { type = area value = 3 } } } } # Eire
# snip remainder of massive area stuff, similar but for the remainder of the regions.-Richard Campbell.
You are correct that it would not alter CPU load significantly in cases where the trait condition does not match. However, if you imagine that we have a ruler with Modest, Just, Trusting and Merciful, we are effectively quadrupling the CPU load for the event for that particular ruler. And since four traits is about average trait amount, we would be effectively doing that load increase all over the board.
Conclusion: Not worth the added CPU load.
Conclusion: Not worth the added CPU load.
Not necessarily. If you prioritized the order of the traits, you could do it without quadrupling the load. Say, Modest, Just, Trusting, Merciful:Byakhiam said:
Code:
condition = { type = liege
condition = { type = trait value = modest }
}
# add proud to vassal
Code:
condition = { type = liege
condition = { type = and
condition = { type = not value = { type = trait value = modest } }
condition = { type = trait value = just }
}
}
# add arbitrary to vassal
Code:
condition = { type = liege
condition = { type = and
condition = { type = not value = { type = trait value = modest } }
condition = { type = not value = { trait value = just } }
condition = { type = trait value = trusting }
}
}
#add suspicious to vassal
Code:
condition = { type = liege
condition = { type = and
condition = { type = not value = { type = trait value = modest } }
condition = { type = not value = { trait value = just } }
condition = { type = not value = { trait value = trusting } }
condition = { type = trait value = merciful}
}
}
#add cruel to vassal-Richard Campbell.
Last edited:
Perhaps, but it's still awfully complicated and it doesn't really sound worth the effort to me. If we want to do it by loyalty way, it'd make more sense to drop their loyalty way down, by say 80 or 90, which can result them declaring war, if they have been somewhat disloyal before or if their loyalty is not growing. However, if that would be the case, I'd say the liege should not be informed of the loyalty drop, since otherwise it'd just mean player being forced to look through the vassals and send money everytime the event notifies them about it and AI wouldn't be sending money anyway.
Probably not. I was just approaching it as an intellectual exercise. Is it possible to define more traits? If so, having a pair of traits that are heavily opposed (king_crappy_liege and duke_crappy_vassal, duke_crappy_liege and count_crappy_vassal) would be a better way to do things. Just give the vassal and the liege the appropriate flags, and eventually you'll spark a loyalty crisis.Byakhiam said:
Of course, if things are pretty much guaranteed to end up in an independent vassal and a war, it does make you wonder what the point is (giving the liege a claim?).
-Richard Campbell.
Well, as the desired target is independent vassal, the current set works towards that goal very efficiently.
I have a question about vassals going independent after a crusade ends. Can someone refresh my memory about what the conditions are for this? Does this apply based on the religion of the province or is it all of the Middle East and North Africa? If your character is a king based in the Mid-East, it doesn't seem like this event should apply.
If your capital is in same(ish) area, then you won't see them go away. For example, if you are king of Egypt, with your capital in Alexandria, your vassals won't start independent crusader realms. Expect maybe if they are in Mauretania or Persia.
I don't have any problem with the event itself, except it doesn't tell you who jumped ship. That would be really nice.
Byakhiam said:
Well this happened in the situation I described in another thread where I am the King of Cyprus. The size of Egypt is far larger than the distance between my capital and the terrritory.
The vassals that left did not have any land connection to my realm -- could that be a factor?
UeberMensch said:
Well I guess that Cyprus is in another area then Egypt. Alltough on the map they look close together, the computer just checks the area codes, if they are different then you get those events.
I am afraid that, that is just a limitation to the game mechanics.
Or it could also have something to do wit the fact that kingdom of Cyprus is not a real kingleveltitle but a 'beefed up' duke title.
Veldmaarschalk said:
Sorry, I wasn't clear enough. I have no vassals in Egypt. If they were in Egypt I would agree that that is too far away. My vassals were in the area of Duchy of Armenia Minor -- very close I thought.