Anyone know where I can find scopes? Trying to add a check to befriend/sway function to make it work on adolescent rulers, but cant find what the right scope to use...
Rather than "found", scopes are "made". Anyways, I haven't checked in detail but it seems you would only need to change scope:recipient = { is_adult = yes } for something like scope:recipient = { age > 13 }. Like this:Anyone know where I can find scopes? Trying to add a check to befriend/sway function to make it work on adolescent rulers, but cant find what the right scope to use...
is_shown = {
scope:actor = { has_perk = befriend_perk } # Unlocked by the Befriend Perk
NOT = { scope:actor = scope:recipient }
scope:recipient = { age > 13 }
scope:actor = { is_adult = yes }
}
Yeah, found it while savaging through various parts of the folder. Now my next challenge to tackle is if else settings. For example if the character in prison is a family member, I want to be able to run an abduction scheme on them.Rather than "found", scopes are "made". Anyways, I haven't checked in detail but it seems you would only need to change scope:recipient = { is_adult = yes } for something like scope:recipient = { age > 13 }. Like this:
As mentioned, I didn't thoroughly checked after seeing this, it's too late for me and I gotta go to bed. Try it out and if it doesn't work I'll promise to look again tomorrow, this time in detail.Code:is_shown = { scope:actor = { has_perk = befriend_perk } # Unlocked by the Befriend Perk NOT = { scope:actor = scope:recipient } scope:recipient = { age > 13 } scope:actor = { is_adult = yes } }
My event doesn't seem to be able to use the following localisation:
[capital.GetNameNoTierNoTooltip]
Do I need to set the scope of the capital in the event to be able to use it? I rather expected it to automatically select the capital of root by default. Obviously not.![]()
[ROOT.GetCapitalLocation.GetNameNoTierNoTooltip]? No promises, though. the_target_character_scope_of_your_choosing = {
if = {
limit = {
is_female = yes
}
add_opinion = {
target = root
modifier = made_up_positive_opinion
}
}
else = {
add_opinion = {
target = root
modifier = made_up_negative_opinion
}
}
}
I was gonna reply similar to YTnuBF, which is probably the easiest way to do it, as I don't think you can create gender specific opinion moddifiers... but then I remembered about attraction opinion. Now of course those are sex specific, not gender, but if you are adamant about having one single opinion modifier affecting both men and women... it may be worth to take a look at that.Thanks YTnuBF. I suddenly realised how dense I was being. I can of course name both traits the same within the localisation, so it outwardly appears to affect each sex differently.
Hahahaha. I meant, use the basis of attraction_opinion to create your own thing, not to actually change what attraction_opinion itself does. That'd be a bit... gamebreaking.Thanks Aregodas, I hadn't though of using that. But I think I shall stick with the "two traits same name" method, otherwise homosexual women would be annoyed by being given permission to use the temple.![]()
When using on-actions we can set a date at which we want our events to fire using the "trigger_on_next_date" line. I am wondering if there is any way to get something like this to work from an event option block. I would like the next event in a chain to fire on the winter solstice. Using the "trigger_on_next_date" line causes the next event to trigger immediately.
edit: All solved. Had a sudden realisation. Sure enough the game uses the back-to-front American date. "trigger_on_next_date" works perfectly with 12.21 instead![]()
It is very simple indeed.Wait, wait, you can do what? I've never encountered that parameter before; can you give me an example of its use?
option = {
name = aesir_statues.0200.a
trigger_event = {
id = aesir_statues.0210
trigger_on_next_date = 12.20
}
}
It is very simple indeed.
Code:option = { name = aesir_statues.0200.a trigger_event = { id = aesir_statues.0210 trigger_on_next_date = 12.20 } }
There is a vanilla use in:
events\yearly_events\yearly_events_persia.txt line 30
1066.09.15, so that dates can be sorted properly in plaintext (e.g., so 1 December doesn't get sorted before 30 November, because 1 is less than 3).councillor_chancellor:0 "Chancellor" so I made my own council file with councillor_chancellor_mandalorian_religion:0 "Adjudicator" and also councillor_mandalorian_religion_chancellor but nothing changes. I could add the Court Chaplin method for every council position, but that is a real pain as you need to create triggered_desc.name = {
first_valid = {
triggered_desc = {
trigger = {