Could we get trait flag "cannot_command = yes", which would block rulers from commanding armies like the toggle button player has? It is tedious to lose a crusade because Pope got captured after losing a battle.
I've done something like that with traits.I wish it was possible to give certain cultures fighting bonuses in certain terrains, such as Frisians fighting better in marshes and the Steppe people getting a bonus on plains and steppes.
That's indeed a possible solution, but I would prefer to just set the bonuses in the cultures.txt file in order to not clogg up the list of traits.I've done something like that with traits.
For instance, you could make a trait with 'potential = { culture = frisian }', 'random = yes', 'birth = 10000' and the appropriate command_modifier... It needs a couple of checks to make sure that they all get the trait, but it's definitely already possible.
Could set it as hidden, then it won't clog up the list.That's indeed a possible solution, but I would prefer to just set the bonuses in the cultures.txt file in order to not clogg up the list of traits.
any_province_character..It would be cool to have a scope that looks at all characters at a location (including in command and councillors). Hopefully, it wouldn't be expensive processing wise.
It doesn't work for people who are leading troops there or councilors in that province.any_province_character..
Seems to work fine.It doesn't work for people who are leading troops there or councilors in that province.
It doesn't work the way you think it does.Seems to work fine.
..II just tested it to make sure. Made a decision that kills characters with any_province_character scope, and it wiped out everyone in the province. Including army leaders who happened to be there.
Some councillors survived, but they were elsewhere (researching, studying technology, etc).
Would be odd if a scope called 'any province character' doesn't actually scope to all of them, but if that really doesn't work... then why not just use this?:It doesn't work the way you think it does.
any_character = {
limit = { at_location = PREV }
<effect>
}
Exactly. If the character locations are cached when they enter an area, then it wouldn't be CPU intensive at all. Currently, I check between any realm character who is at war with (which cuts down the check by a lot).Would be odd if a scope called 'any province character' doesn't actually scope to all of them, but if that really doesn't work... then why not just use this?:
Code:any_character = { limit = { at_location = PREV } <effect> }
Because it's too CPU-intensive?
You can remove these by clicking on the "Delete" button next to "Edit".EDIT: Sorry for the accidental double post.
Was this not already disabled in RD? I thought I read that in one of the developer diaries..Would love a defines option or something that disables the feature where the game spawns as many courtiers as you have in "max_wives=" in religions.
You're right, I found this:Was this not already disabled in RD? I thought I read that in one of the developer diaries..