They all must apply in order for the rest of the event's trigger to be evaluated.

The game has already eliminated every character who doesn't match up to your pre-triggers, so it's wasteful to have the game check these a second time.Īlso keep in mind that pre-triggers are inherently within an AND limiter. Put as many in as apply to your event, and remember that you don't need to repeat them again in the trigger section. * = these are only useable in pre-triggers - don't use them anywhere else! Want to avoid doing that? Keep a few rules in mind when writing your code.Ī 'pre-trigger' is a set of triggers which appears above the actual 'trigger' section in character-based events (and only in those events), like so: Checking every character against every other character resulted in a noticeable period of lag every twenty-day period.for a single event. I once innocently wrote an event that checked against any_independent_ruler in the world, but also against any_realm_character for each of those rulers.and, having not limited the event in any way, it was doing this for every single character in the game. Your computer can do this fairly quickly, but when we're talking about hundreds of events and decisions spread over literally thousands of characters, this is going to add up.and it can add up very quickly if you have triggers that are doing many things at once.

Now imagine how many calculations that would require. If the entire thing returns 'true', then the event or decision can potentially fire. It does this at varying levels of efficiency, but at the base level it's going through every line of code in the trigger (for events) or the potential/allow (for decisions) and determining whether the line returns as 'true' or 'false'.

For each character, it is also running through every single event and decision, and evaluating whether they apply to that character. Think of it like this: during every event 'pulse' (which is a period of time determined by the EVENT_PROCESS_OFFSET setting in a, usually 20 days), the game is running through a list of every single character in the game. It's actually quite easy to write a single event in CK2 that, all by itself, can slow down your entire game. It's not something of big concern to every modder, but for a big mod like CK2Plus it's a constant battle we need to fight - so I thought I might be able to share some of my experience to those interested. Since it was asked for in another thread, and there hasn't been a post about it since this previous one (which is now quite out of date), I thought I'd make a post about writing efficient code for events and decisions.

Crusader kings 2 decisions