Are repeating events possible?

[kodiak491]

Is it possible to have an event that fires repeatedly, say annually, either on its own or by being retriggered every year by other events?
I want to make a series of choices available every year and since they would be the same choices every time, it would save time if I could just write one event and have it refire.

 

[Codeman]

sure just chage the trigger year each time you copy and paste it

 

[kodiak491]

That's what I have done in the past but I'm trying to avoid having a huge number of events slowing the game. I think one refiring event would be less of a burden than 20 identical events with different dates.

 

[Lt Hilsdorf]

you need to add "persistent = yes" in the first part of the event, right under the ID

This will make the event trigger every time the trigger is true

 

[zeekater]

You can have events fire multiple times by adding the line 'persisten = yes'.

In your case it won't work however, since the event will also go off at each reload. For annual events it's best to use seperate ones I guess.

 

[kodiak491]

Thanks for the help! I didn't think about the persistent command :wacko: One more question if I may. Can multiple countries share the same event?

 

[Sarmatia1871]

Thanks for the help! I didn't think about the persistent command :wacko: One more question if I may. Can multiple countries share the same event?

Not that I'm aware of - events can either be triggered for one specific tag, or be generalised random events that can hit anyone.

However you can get the same effect by copying and pasting the same event, and changing the TAGs and IDs.

 

[Passivocalia]

Not that I'm aware of - events can either be triggered for one specific tag, or be generalised random events that can hit anyone.

However you can get the same effect by copying and pasting the same event, and changing the TAGs and IDs.

This saddens me... I was hoping to make a generic "Occupation of the Vatican" event for enemy units capturing the Rome province, but I guess I'll just make separate ones for each country likely to do so...

 

[zeekater]

The 'invention' events work for all countries, so perhaps you can use a similar layout.

 

[kodiak491]

The 'invention' events work for all countries, so perhaps you can use a similar layout.

That just might work. I'll have to test it thoroughly to see. Invention events don't fire at regular times though. Brilliant idea, wish I'd thought of it

 

[fudd_bopo]

would it be possible to have a random event with 100% of firering every year?

 

[kodiak491]

Dont know about that since I am not exactly sure what effects the chance of a random event with the invention tag.

 

[zeekater]

This is a random event for all countries:

#########################################################################
# Research Sabotaged
#########################################################################
event = {
id = 1000
random = yes
trigger = {
atwar = yes
NOT = {
intel_diff = -5 # Intel Diff < -5
}
}
name = "EVT_1000R_NAME"
desc = "EVT_1000R_DESC"
picture = "reserch_sbotage"
style = 0

action_a = {
name = "ACTIONNAME1000A"
command = { type = research_sabotaged }
}
}

If you compare that with a 'normal' event, the only thing that's gone is the 'COUNTRY = USA' line.
So, I guess you can just leave that line out, and then the event works for all nations. Also for 'random = no' events.
You can always try that out.

 

[kodiak491]

Ok after considerable testing I have found that the persistent = yes tag doesn't seem to work for events that are triggered by other events. Also the invention tag does not fire reliably timewise. It is only useful as a sort of specialized random event.

 

[Ayeshteni]

Ok after considerable testing I have found that the persistent = yes tag doesn't seem to work for events that are triggered by other events. Also the invention tag does not fire reliably timewise. It is only useful as a sort of specialized random event.

look at the vanilla Lend-Lease events.

You can have an event that is persistent that triggers another persistent event, but both have to be persistent.

If the first is NOT persistent, it will fire once and trigger the second persistent event once.

If the first is persistent it will keep firing when the triggers are met, but if the second isn't persistent that second event will only fire the once the first time.

Both events (the original and the event firing from it) need to BOTH be persistent.

Ayeshteni

 

[kodiak491]

look at the vanilla Lend-Lease events.

You can have an event that is persistent that triggers another persistent event, but both have to be persistent.

If the first is NOT persistent, it will fire once and trigger the second persistent event once.

If the first is persistent it will keep firing when the triggers are met, but if the second isn't persistent that second event will only fire the once the first time.

Both events (the original and the event firing from it) need to BOTH be persistent.

Ayeshteni

That makes sense. Problem is I need the event to fire every year and any trigger used would cause it to fire every day with the persistent tag.
I wonder if its possible to include month and day but not year in the date thus causing the event to fire every january 1 st.

 

[Ayeshteni]

That makes sense. Problem is I need the event to fire every year and any trigger used would cause it to fire every day with the persistent tag.
I wonder if its possible to include month and day but not year in the date thus causing the event to fire every january 1 st.

hmm you can try it but I very much doubt that will work.

I think that what you are going to have to do is to make more than one event (in other words one set of events for each year) I am afraid.

Or perhaps if you set the offset to 360 in your persistent events it might fire roughly (there lies the rub - roughly) once a year, though saving and reloading will reset the timer so that they will fire more often.

The best bet, as I say, is to create an identical set of events each year (just change the ids and the date statements).

Ayeshteni

 

[kodiak491]

hmm you can try it but I very much doubt that will work.

I think that what you are going to have to do is to make more than one event (in other words one set of events for each year) I am afraid.

Or perhaps if you set the offset to 360 in your persistent events it might fire roughly (there lies the rub - roughly) once a year, though saving and reloading will reset the timer so that they will fire more often.

The best bet, as I say, is to create an identical set of events each year (just change the ids and the date statements).

Ayeshteni

Thats exactly what I had to do. I was just trying to simplify things abit. I have added a couple of hundred new events and I figured thats got to start slowing the PC down soon.

 

[Ayeshteni]

Thats exactly what I had to do. I was just trying to simplify things abit. I have added a couple of hundred new events and I figured thats got to start slowing the PC down soon.

Good lord, what were you trying to do?!

As for the events, possibly, but I believe it will take less processor times if the date statements and offsets are quite small so that the computer doesnt have to constantly check those events for trigger conditions; so if the events fire within a very small timeframe it shouldnt put too much pressure on the ol PC.

Ayeshteni

 

[kodiak491]

Good lord, what were you trying to do?!

As for the events, possibly, but I believe it will take less processor times if the date statements and offsets are quite small so that the computer doesnt have to constantly check those events for trigger conditions; so if the events fire within a very small timeframe it shouldnt put too much pressure on the ol PC.

Ayeshteni

Actually I am using no offsets. The events fire every year on the same date for each country.

What this is all for is a series of annual events where each country has choices for the direction its army and air force will take in the coming year.

For example the air force choice is the option of extending, shortening, or not altering their pilot training times. Each nations ai chances for the 3 options are different depending on their historical choices. Thus the alles tend to extend training times where the Axis tend to shorten them.

The army option involves whether to increase manpower, firepower, both or neither. Thus nations can slowly shift to divisions better adapted to their needs.

In both cases the changes are small to avoid game imbalances.