character_event => trigger

[stryhf]

If you specify a trigger for a character_event and call the character_event from another character_event, the trigger is never checked.

I tried calling 2 character_events from another character_event with mutually exclusive triggers, and both character events still fired. I was doing this as a workaround since I couldn't limit = { } THIS, it seems THIS always returns.

 

[Peter Ebbesen]

I thought triggering an event (A) from another event (B) was supposed to bypass A's trigger [i.e. what you consider a bug] whether it be character, province, or country event [within scope], but admittedly I've never tested it.

 

[stryhf]

There is a trigger = { always = yes } option for triggers to always trigger.

As it stands I was trying to use the called character_event as a workaround since there is no easy way within an event to limit on your focus scope once you've called the event and it has met the requirements for the trigger.

I had to use a hack to set a character flag via immediate = { } then change scope to country = { any_character = { limit = { } } }. Having to use these contortions to determine whether you want to call another character event makes having a viable trigger within that character all the more convenient. Since there already exists within the current framework a way to make the trigger always kick off, then why ignore it?