• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

unmerged(25996)

Second Lieutenant
Feb 20, 2004
103
0
I have noted some events fire on reloading the game. On events I have written, it seems to occur when the trigger conditions are satisfied after the start date. This includes events without an offset. Events where the start date is satisfied after all the trigger conditions are satisfied seem to fire right on schedule. I have noted AI events fire on reloading a game so this phenomena occurs for events I have not written also, though not necessarily for the same reason.

Does anyone know if this is intended?
 

unmerged(6159)

Field Marshal
Oct 23, 2001
9.458
1
Visit site
I think it is. Daywalker's Site of how this is supposed to work. I'm a little surprised about the evnts with no offsets, but I guess it makes sense if you don't give them a death date. (I always do)
 

unmerged(25996)

Second Lieutenant
Feb 20, 2004
103
0
I reread the info on sparking and triggering. Let me see if I understand this correctly.

1.) If you specify a trigger condition(s) and a start date and no death date and no offset, it will only check on the start date whether the trigger is satisfied, but not on future dates. I am not sure what reload would do here as I have not written any events like that.

2.) If you specify trigger(s), start date, death date, no offset, it will pick a random date sometime between start and death and check whether trigger is satisfied on that date only. I have written events this way and on reload they fire.

3.) If you add offset to number 2, it picks a date between start and start + offset to check the trigger(s) and will repeat this process every offset days until the death date passes.

So the offset is not only a random element, but also determines how often the program will check the trigger(s) ?