Pulse events

[Junuxx]

So, since 5.1 many events no longer work with a mean time to happen, but instead are fired from the biannual "event pulse".

Could anyone explain how this works exactly? In particular, how can I tell whether a is_triggered_only event is eligible for the pulse, or triggered elsewhere? And do the mtth modifiers, which are often still present in the event code, play any role in making the event more or less likely to be triggered?

 

[Me_]

So, since 5.1 many events no longer work with a mean time to happen, but instead are fired from the biannual "event pulse".

Could anyone explain how this works exactly? In particular, how can I tell whether a is_triggered_only event is eligible for the pulse, or triggered elsewhere? And do the mtth modifiers, which are often still present in the event code, play any role in making the event more or less likely to be triggered?

Go to common/on_action.txt at the very bottom are the biannual events

# country random events
on_bi_yearly_pulse = 
{
	random_events = {

	#randomevents.txt		
		100 = 5008
		100 = 5014
		100 = 5015
		100 = 5017
		100 = 5018
		100 = 5019
		100 = 5020
		100 = 5021
		100 = 5022
		100 = 5023
		100 = 5024
		100 = 5025
		100 = 5027
		100 = 5032
		100 = 5040
		100 = 5045
		100 = 5050
		100 = 5051
		100 = 5052
		100 = 5053
		100 = 5054
		100 = 5055
		100 = 5056
		100 = 5058
		100 = 5059
		100 = 5060
		100 = 5061
		100 = 5064
		100 = 5065
		100 = 5066
		100 = 5068
		100 = 5070
		100 = 5071
		100 = 5072
		100 = 5074
		100 = 5075
		100 = 5076
		100 = 5077
		100 = 5082
		100 = 5083
		100 = 5084
		100 = 5085
		100 = 5086
		100 = 5088
		100 = 5089
		100 = 5090
		100 = 5091
		100 = 5092
		100 = 5093
		100 = 5094
		100 = 5095
		100 = 5096
		100 = 5097
		100 = 5098
		100 = 5099
		100 = 6000
		100 = 6001
		100 = 6002
		100 = 6003
		100 = 6004
		100 = 6005
		100 = 6006
		100 = 6012
		100 = 6013
		100 = 6015
		100 = 710
		100 = 711
		100 = 712
		100 = 713
		100 = 714
		100 = 715
		100 = 716
		100 = 717
		100 = 718
		100 = 719
		100 = 720
		100 = 722
		100 = 723
		100 = 724
		100 = 725
		100 = 726
		100 = 727
		100 = 728
		100 = 729
		100 = 730
		100 = 731
		100 = 732
		100 = 733
		100 = 734
		100 = 735
		100 = 736
		100 = 737
		100 = 738
		100 = 739
		100 = 740
		100 = 741
		100 = 742
		100 = 850
		100 = 851
		100 = 852
		100 = 853
		100 = 854
		100 = 855
		100 = 857
		100 = 858
		100 = 859
		100 = 860
		100 = 861
		100 = 862
		100 = 863
		100 = 864
		100 = 865
		100 = 866
		100 = 867
		100 = 868
		100 = 869
		100 = 870
		
		100 = 871
		100 = 872
		100 = 873
		100 = 874
		100 = 875
		100 = 876
		100 = 877
		100 = 878
		100 = 879
		100 = 880
		100 = 881
		100 = 882
		100 = 883
		100 = 884
		100 = 885
		
	#sliders
		100 = 6300
		100 = 6301
		100 = 6302
		100 = 6303
		100 = 6304
		100 = 6305
		100 = 6306
		100 = 6307
		100 = 6308
		100 = 6309
		100 = 6310
		100 = 6311
		100 = 6312
		100 = 6313
		100 = 6319
		100 = 6325
		100 = 6326
		100 = 6327
		100 = 6328
		100 = 6329
		100 = 6330
		100 = 6332
		100 = 6333
		100 = 6334
		100 = 6335
		100 = 6337
		100 = 6338
		100 = 6339
		100 = 6340
		100 = 6341
		
	}

As far as I know the MTTH modifiers for those events work in the opposite way to that of other events i.e. the bigger MTTH for those events the more likely they are to fire.

 

[Junuxx]

Go to common/on_action.txt at the very bottom are the biannual events

# country random events
on_bi_yearly_pulse = 
{
	random_events = {

	#randomevents.txt		
		100 = 5008
		100 = 5014
		100 = 5015
		100 = 5017
		100 = 5018
		100 = 5019
		100 = 5020
		100 = 5021
		100 = 5022
		100 = 5023
		100 = 5024
		100 = 5025
		100 = 5027
		100 = 5032
		100 = 5040
		100 = 5045
		100 = 5050
		100 = 5051
		100 = 5052
		100 = 5053
		100 = 5054
		100 = 5055
		100 = 5056
		100 = 5058
		100 = 5059
		100 = 5060
		100 = 5061
		100 = 5064
		100 = 5065
		100 = 5066
		100 = 5068
		100 = 5070
		100 = 5071
		100 = 5072
		100 = 5074
		100 = 5075
		100 = 5076
		100 = 5077
		100 = 5082
		100 = 5083
		100 = 5084
		100 = 5085
		100 = 5086
		100 = 5088
		100 = 5089
		100 = 5090
		100 = 5091
		100 = 5092
		100 = 5093
		100 = 5094
		100 = 5095
		100 = 5096
		100 = 5097
		100 = 5098
		100 = 5099
		100 = 6000
		100 = 6001
		100 = 6002
		100 = 6003
		100 = 6004
		100 = 6005
		100 = 6006
		100 = 6012
		100 = 6013
		100 = 6015
		100 = 710
		100 = 711
		100 = 712
		100 = 713
		100 = 714
		100 = 715
		100 = 716
		100 = 717
		100 = 718
		100 = 719
		100 = 720
		100 = 722
		100 = 723
		100 = 724
		100 = 725
		100 = 726
		100 = 727
		100 = 728
		100 = 729
		100 = 730
		100 = 731
		100 = 732
		100 = 733
		100 = 734
		100 = 735
		100 = 736
		100 = 737
		100 = 738
		100 = 739
		100 = 740
		100 = 741
		100 = 742
		100 = 850
		100 = 851
		100 = 852
		100 = 853
		100 = 854
		100 = 855
		100 = 857
		100 = 858
		100 = 859
		100 = 860
		100 = 861
		100 = 862
		100 = 863
		100 = 864
		100 = 865
		100 = 866
		100 = 867
		100 = 868
		100 = 869
		100 = 870
		
		100 = 871
		100 = 872
		100 = 873
		100 = 874
		100 = 875
		100 = 876
		100 = 877
		100 = 878
		100 = 879
		100 = 880
		100 = 881
		100 = 882
		100 = 883
		100 = 884
		100 = 885
		
	#sliders
		100 = 6300
		100 = 6301
		100 = 6302
		100 = 6303
		100 = 6304
		100 = 6305
		100 = 6306
		100 = 6307
		100 = 6308
		100 = 6309
		100 = 6310
		100 = 6311
		100 = 6312
		100 = 6313
		100 = 6319
		100 = 6325
		100 = 6326
		100 = 6327
		100 = 6328
		100 = 6329
		100 = 6330
		100 = 6332
		100 = 6333
		100 = 6334
		100 = 6335
		100 = 6337
		100 = 6338
		100 = 6339
		100 = 6340
		100 = 6341
		
	}

Thanks, very helpful!

As far as I know the MTTH modifiers for those events work in the opposite way to that of other events i.e. the bigger MTTH for those events the more likely they are to fire.

This I don't understand. Why would it work the other way around, does that make sense to you?

 

[Me_]

Thanks, very helpful!

This I don't understand. Why would it work the other way around, does that make sense to you?

From what I know when calculating which pulse event is going to happen the MTTH of events that can happen is used to calculate their chance of happening in a different way than usually. E.g. if you can have one of 3 events, two of them with no changes to MTTH and one with a modifier of 2 then the chances are 25%,25%,50% (from 1/1/2 MTsTH for events). But I don't really know. It's just what I read somewhere. But you can see that in all those events the modifiers that should logically increase the chance of the event happening are all bigger than 1, while for other events the modifiers that should logically increase the chance of the event happening are less than 1.

 

[jdrou]

Basically for pulse events, the "MTTH" value actually works more like the "chance" value in missions. Every time there's a pulse there will be an event so actual MTTH would make no sense; instead it is the weight used to affect the chance that particular event will be chosen.

.

 

[Junuxx]

So what is the '100 =' in on_action.txt? I thought that might be the weight, but apparently it's not. Is it just a fixed value then?

 

[DanubianCossak]

All you need to know is that any mod events should be handled the old style imo, because the pulse thingy makes 1 event fire every few months out of a bundle of, say, 500 events. So, if you would trigger 5 old random events in a certain time period, with pulse, youd get like 10X less events. For my mod at one point i redid most of randomish events to work with pulse, but the game felt so weird, as there were VERY few events firing.

 

[Junuxx]

Oh I'm asking not for a mod, but for the wiki. There's currently nothing on it about pulse events, and many event pages seem a little strange because of it. Thanks anyway

 

[Me_]

So what is the '100 =' in on_action.txt? I thought that might be the weight, but apparently it's not. Is it just a fixed value then?

I suppose that it may be so that the base chance is actually 100 (from on_action.txt) *1 (base for each event) * modifiers from event file and since all events have 100 then said 100 is effectively meaningles. But again that's just an untested theory. Possibly the 100 is there for some technical reason e.g. all base chances must be >1 (i'm not saying that it is so, just theoretizing), so 1 with a modifier of 0,8 would give 0,8 which is <1 and would be invalid, but with the 100 multiplier you get 80 which is >1, so all's fine. Again just a theory. I seem to remember possibly reading somewhere that if MTTH of ordinary events is less than 1 then you get some strange results and so the same may be true for those events. Perhaps a Dev would be willing to explain this.