After some trial & error I figured out that if in the same event there's a trigger isoverlord = no that is false and either a trigger isvassal = no or NOT = { isvassal = yes } that is true, then when the event is first checked the game crashes.
There should be a warning in the triggers post on page 1 that isoverlord = no is to be avoided and should be replaced with NOT = { isoverlord = yes }.
Also, can someone verify this? Possibly the issue is more complex than that and there are other factors at work that I didn't consider.
There should be a warning in the triggers post on page 1 that isoverlord = no is to be avoided and should be replaced with NOT = { isoverlord = yes }.
Also, can someone verify this? Possibly the issue is more complex than that and there are other factors at work that I didn't consider.