For #2, I know the last time I tried it (a few patches back) the validator had a fit and so did the error logs, but I haven't yet taken the time to figure out the actual behavior.1 and 3 are taken from the wiki but 2 is guesswork, my suggestion would be test having two events with identical ids and then lets us know
- Merge, but override of decision by re-using same name does not work (breaks the decision effect, that does nothing)
- Not known for sure, I imagine that the events will function the same as decisions
- Merge, but traits with same name will co-exist, and generated characters may get both versions of the trait at the same time. The last definition gets assigned to a character when using commands.
Make a duplicate event id then test it by launching it via the console and via a separate event and see what happens. That way you can tell if it works like decisions in that either way it breaks or if it still works but like with the traits if launched then only the last one fires or if both happen at the same time.
hmm what formats they need to be saved?I didnt see any kind of detail like that in tutorials.Im using photoshop bytheway.
.png){kind=avatar}
I think you need to do this:
#assuming we are in a province scope already
set_variable = { which = count value = 0 } # in this variable we count the amount of buildings found
set_variable = { which = n value = 0 } # in this variable we count the amount of holdings in the province for the loop below
any_province_holding = { set_title_flag = pending }
export_to_variable = {
which = n
value = num_of_settlements
}
while = {
limit = { check_variable = { which = n value = 1 } }
change_variable = { which = n value = -1 }
random_province_holding = {
limit = { has_title_flag = pending }
clr_title_flag = pending
if = {
limit = { has_building = <your building tag> }
PREV = { change_variable = { which = count value = 1 } }
}
}
}