The random = 2 should be checked every <however log the offset is>, I think it was just chance it fired then you reloaded, as I've experianced that once or twice but not on a regular basis.
-
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.
It appears that faust_xlh is correct.
Changing the opium trade to persistent = yes offest =31 random = 50.
My previous tests have shown that in continuous play the event fires only once in 5 years.
However in this run.
1) It fired in Jan '36 and never again up to Feb '37 when I saved.
2) Let it continue running until May '37 and it still hadn't fired.
3) I quit and reloaded the Feb '37 game
4) Opium Trade fired in Feb '37
5) I left the game run till March '38 with no other firings when I saved
6) I loaded the March '38 game and Opium Trade fired in March '38.
Whilst DR is probably right that it was chance that random = 2 triggered immediately after loading, it does appear that the random part of a persistent event is only reset by the act of loading the game.
This makes it impossible for any one to write an event that fires (roughly) every X amount of time using persistent and random as it would require the user to save and reload the game. within that time period.
Changing the opium trade to persistent = yes offest =31 random = 50.
My previous tests have shown that in continuous play the event fires only once in 5 years.
However in this run.
1) It fired in Jan '36 and never again up to Feb '37 when I saved.
2) Let it continue running until May '37 and it still hadn't fired.
3) I quit and reloaded the Feb '37 game
4) Opium Trade fired in Feb '37
5) I left the game run till March '38 with no other firings when I saved
6) I loaded the March '38 game and Opium Trade fired in March '38.
Whilst DR is probably right that it was chance that random = 2 triggered immediately after loading, it does appear that the random part of a persistent event is only reset by the act of loading the game.
This makes it impossible for any one to write an event that fires (roughly) every X amount of time using persistent and random as it would require the user to save and reload the game. within that time period.
That can't be quite true, I've had the opium trade fire twice in one session as the UK without loading. It seems reloading does help though.
Darkrenown said:
It is perfectly possible for "Opium Trade" to fire twice in one session although I doubt it is fired more than once by the random trigger.
There are three ways for the UK to get its "Opium Trade" event (6938):
1 & 2) China's "Opium Trade" event (12500) triggered by random or explicitly "The Treaties of Beijing" (12516)
3) China's "High Commissioner Corrupted!" (12502)
The third case is nothing to do with China's "Opium Trade" event and therefore has not bearing on the persistent/random debate. It simply looks the same to the UK.
Cases 1 and 2 however are part of the debate.
persistent = yes definitely allows an event to be fired several times. It can be explicitly triggered by several different events. However, it appears that the random element can only trigger a persistent event once unless it is reset by a save and load.
my event won't fire more than once at all even if I use lots of triggers.... like atwar and such 