"persistent" events problem, has anyone a workaround?

[unmerged(38177)]

Re-firing of "Persistant" events (such as the USA Lend-Lease events) upon reload of a savegame seem to make some problems. Has anyone come up with a workaround?

I'm working on a calendar routine, which would enable someone to test if it is a particular month (similar to what a 'Month = " event command would do... shame it's not built in) so I could re-write the trigger sequence. Any interest?

 

[ulmont]

Re-firing of "Persistant" events (such as the USA Lend-Lease events) upon reload of a savegame seem to make some problems. Has anyone come up with a workaround?

Rewriting the triggers so that they are evenly spaced for any given day (something like a 1 / 270 chance) is the current favorite.

 

[Spocky]

The hardest but possibly best way is writing a seperately event for every firing.
What I mean : If you want 1 lend lease every year , then write an event for 1940 , 1941 , 1944 , ... . With copy and paste it is not that much in work.

Spocky

 

[unmerged(38177)]

This is what I am trying to AVOID . .

The hardest but possibly best way is writing a seperately event for every firing. What I mean : If you want 1 lend lease every year , then write an event for 1940 , 1941 , 1944 , ... . With copy and paste it is not that much in work.

I am trying to REDUCE, not increase, the size of the event code blocks. Larger size (and more events) decreases game speed. The "calendar routine" will make the following code blocks possible:

OR { AND { Year = 1939 Flag = MonthMarch }
AND { Year = 1939 Flag = MonthDecember }
AND { year = 1940 Flag = MonthJune }
Etc . . .

Sometimes I just wish there was more externalization of internal data. Luckily, this routine should work in "Doomsday", where I expect the "Presistant" problem to be "Persistant" in the enhancment.