The Validator is very reliable, vanilla CK2 and its error logger are not. That's why I and a few others created CleanSlate, that has erased tons of mistakes in vanilla CK2. It's a recommended resource to base your new mods on.
I typically (temporarily) remove all files from the relevant folder (events folder if I'm validating events) except the ones I'm specifically validating, in order to prune the excess vanilla errors from Validator's log.
My strategy is as follows:
# Audax Validator "!" Ignore_NEXT at the top of the file)
Alright, are there any workarounds then? Maybe do it in reverse? Increase the age for everyone but give negative modifiers via on_yearly_pulse to those who aren't eligible?
In short, yes, this is approximately the way I'd do it.
day_of_birth, month_of_birth, year_of_birth, day, month and year are all exportable variables. Some quick maths, and you can easily calculate the number of days/months until the character's next birthday. So, starting from an on_yearly_pulse event, you could write some (probably rather annoying) code to trigger an event on their next birthday.birthday_search_started or birthday_events_are_set_up? if yes, do nothing and exit. if no, set the birthday_search_started flag and continue. is their birthday in more than 30 days? if yes, check everything again in 30 days' time. if no, is their birthday in more than 5 days? if yes, check everything again in 5 days' time. if no, is it in 4 days? ... 3 days? ... ... ... is it today? if yes, set up a recurring birthday event for all future time, remove the birthday_search_started flag and set the birthday_events_are_set_up flag. This recurring birthday event can do whatever you like for attractiveness etc.)on_adulthood_pulse - it's also every single character that's generated by event. And there are lots of these: rebel leaders, random commanders, random women, even major plot figures like Seljuk and Temujin, etc etc etc. Some people are generated at quite old ages (eg. gurus are always 50+, and I think random theocrat successors also tend to skew quite old), so you can't assume that every newly-generated character (ie. who hasn't yet had a yearly pulse and therefore hasn't yet had any recurring birthday events) is young and attractive. However, it's not too bad if a random nobody is erroneously considered to be "attractive" for a few months, so I think my yearly-pulse strategy outlined above is acceptable.on_host/employer_change).
ai_will_do = {
factor = 1
trigger = {
# AIs will not take the last counties off their liege's direct vassals
trigger_if = {
limit = {
ROOT = {
same_liege = FROM
}
}
FROM = {
num_of_count_titles > 1
}
}
trigger_if = {
limit = {
ROOT = {
has_character_flag = is_temujin
has_landed_title = e_mongol_empire
is_landed = yes
}
}
FROM = {
NOT = { has_landed_title = e_china_west_governor }
}
}
}
coronation_factor = yes
}It's the
factor = 1 that does it. Modifiers only affect the base factor.
trigger = {} is met. CleanSlate uses triggers instead of modifier blocks with a factor of 0, to avoid inverted logic. That makes it much easier to read, and often more concise too.It depends on the specific "something". For event options, if there is no option with AI weightings, the AI will pick a random valid option, with each option having an equal chance of being picked. (Not sure exactly how it works if some but not all options have AI weightings - this is probably not a good idea...) For decisions, omitting an AI weight means the AI will always take the decision if possible. Etc etc.
Should be able to, the Conditions wiki page says the target scope (in this case ROOT) can be any scope with a religion, and characters do have religions.