real_father_even_if_dead = {
ROOT = { set_father = PREV }
}change_infamy = {
value = x
localisation = y
}This appears to be the first time this has been communicated anywhere, actually. The command does not appear in any events or anything for us to have examples of how it works, the only places the command even appears in the steamapps\common\Crusader Kings II folder is in the exe, a pdb file, the changelog*, and this bit of localization:
CHANGE_INFAMY_EFFECT;$CHAR|Y$ Threat $VALUE|Y$ added.;Menace de $CHAR|Y$ gagne $VALUE|Y$.;$CHAR|Y$ Bedrohung $VALUE|Y$ hinzugefügt.;;$CHAR|Y$ añadido $VALUE|Y$ Amenaza.;;;;;;;;;x- Added change_infamy effect to add or remove threat from a character.
Thank you again. I'm particularly interested in the details for the revoke trigger for minor titles mentioned in the changelog. Would I be correct in assuming that it works like, and uses the same sort of syntax as dismiss_trigger in job_titles.txt? Also, does it work for commanders? I recall you mentioned that they work differently.
Adding an alliance via commands also seems to not have a line break either.
Thanks for pointing that one out.Adding an alliance via commands also seems to not have a line break either.
eg: add_alliance = { who = ROOT years = 3 } gives the following tooltip
Whew, you made me a little worried there. Good to hear that it's supposedly working as intended then.
revoke_trigger = {
FROM = {
NOT = { religion_group = muslim }
}
}# Commander, granted via its own interaction, so very special
title_commander = {
is_high_prio = yes
attribute = martial
dignity = 0.05
opinion_effect = 10
realm_in_name = yes
monthly_salary = 0.05
monthly_prestige = 0.50
allowed_to_hold = {
OR = {
primary_title = { temporary = no }
NOT = {
primary_title = {
always = yes
}
}
}
liege = { character = FROM }
OR = {
AND = {
OR = {
is_female = no
AND = {
OR = {
religion = messalian
religion = cathar
}
liege = { religion = ROOT }
}
liege = {
primary_title = {
has_law = status_of_women_4
}
}
}
OR = {
NOT = { religion = hindu }
trait = kshatriya
}
is_adult = yes
}
has_character_flag = special_marshal
}
prisoner = no
NOT = { trait = incapable }
NOT = { trait = in_hiding }
NOT = { has_character_flag = guru }
}
revoke_trigger = {
FROM = {
NOT = { religion_group = muslim }
}
}
gain_effect = {
}
lose_effect = {
}
message = yes
}Unfortunately commanders have their own way of working things out.
Any chance of getting a way to lock them in anytime soon? I'm trying to put together a stratocracy type government, and being able to keep the AI from swapping commanders around would really help keep it from getting really messy.
I've added it to my ever-growing list of things I want to get done in the CK project. However any time soon is probably not the case. Unfortunately I don't think I'll get to it before a while.
We like to tinker with employee's and modder's brains for our psychological studies on how much pain the human psyche can withstand.Please either correct "targetted_decisions" to targeted, or add targeted as an alias. Having to intentionally make a typo is a pain in the backside, especially when you don't remember and can't figure out why your perfectly correct scripts aren't working.
has_earmarked_regimentsdisband_event_forcesI think that I managed to nail down this issue to being caused by a tooltip from the number in the unit selection (mouse-over on the number next to the go to location and deselect button crashed the game for characters with non-landed realms). This should be fixed but that won't reach you until a future patch.