• 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(54975)

Colonel
Mar 18, 2006
1.135
0
#############################################
###### Vital province lost #
#############################################
event = {
id = 55556
random = yes
country = SOV
trigger = {
atwar = Yes (GER)

control = { province = 187 data = GER }
control = { province = 238 data = GER }

}

name = "EVT_55556_NAME"
desc = "EVT_55556_DESC"
style = 0
persistent = yes


action_a = {
name = "ACTIONNAME55556A"
command = { type = add_division which = "militia" value = militia when = 10 }
}

}

i always get a command not recognized error on the following line

control = { province = 187 data = GER }

also will this event give Russia 10 militia divisions?
 
If you wanted to add the
at war = yes (Ger) replace it and say at war = yes # GER

the game will ignore # GER and just continue.
 
GermanWehrmacht said:
If you wanted to add the
at war = yes (Ger) replace it and say at war = yes # GER

the game will ignore # GER and just continue.
Replace it with:

atwar = GER

russ555 said:
command = { type = add_division which = "militia" value = militia when = 10 }

also will this event give Russia 10 militia divisions?
No.

"when =" specifies the model, not the number:

command = { type = add_division which = [name] value = [div type] when = [model]
where = [brigade type] }
 
Last edited:
ok thanks it works now :) but will the event fire everytime 1 of the provinces are taken or only when all of them are taken?

#############################################
###### Vital province lost #
#############################################
event = {
id = 55556
random = yes
country = SOV
trigger = {
atwar = Yes = GER
control = { province = 187 data = GER }
control = { province = 238 data = GER }
control = { province = 175 data = GER }
control = { province = 248 data = GER }
control = { province = 258 data = GER }
control = { province = 253 data = GER }
control = { province = 163 data = GER }
control = { province = 154 data = GER }
control = { province = 1907 data = GER }
control = { province = 1372 data = GER }

}

name = "EVT_55556_NAME"
desc = "EVT_55556_DESC"
style = 0
persistent = yes


action_a = {
name = "ACTIONNAME55556A"
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }
command = { type = add_division which = "militia" value = militia when = 3 }

}

}
 
Hi,

it looks interesting... When are the conditions checked? every 24 hours?

And another question, are the contents of the events.txt loaded only when the game load? I mean, if I modify an event, after 24 hours the NEW event is fired or the old one? (so I can ALT+TAB and edit and not save+reload everytime)

Thanks
 
mikerohan said:
Hi,

it looks interesting... When are the conditions checked? every 24 hours?

And another question, are the contents of the events.txt loaded only when the game load? I mean, if I modify an event, after 24 hours the NEW event is fired or the old one? (so I can ALT+TAB and edit and not save+reload everytime)

Thanks
No, its only loaded when you load the game. no alt+tab modifing
 
atwar = Yes = GER

Are you sure this works? I have never seen a trigger configured thus.

blue emu said this:

atwar = GER
 
russ555 said:
ok thanks it works now :) but will the event fire everytime 1 of the provinces are taken or only when all of them are taken?

For any one province you need use an OR command.
 
theokrat said:
But this would either constantly fire if persistent and the germans occupy only one of these or only fire once, not every time the next has been taken

That is true, but I was not particularily concerned with the logic of the event. ;)

Just answering the question.
:cool:
 
Get rid of the persistence; any random event is automatically persistent.
The event will trigger anything from never to a couple of times a year when the conditions hold true, once the errors are removed.
Unless you have added the model yourself, there is no militia model past the 1946 model, so something will go wrong there.

Please use the code tags in the future to preserve indentation.
 
Wobbler said:
Get rid of the persistence; any random event is automatically persistent.
The event will trigger anything from never to a couple of times a year when the conditions hold true, once the errors are removed.
Unless you have added the model yourself, there is no militia model past the 1946 model, so something will go wrong there.

Please use the code tags in the future to preserve indentation.

You have a keen eye!

Use 'random' setting much? It sounds very useful if that never to a couple times a year holds. Sounds like 'fate'.

I like 'fate' when making a mod.
:rofl:
 
It will depend very much on how many random events are eligible for the nation in question (and possibly how many of those are eligible for other nations aswell - in EU2 a random event can only be queued up for one nation at a time).

For country-specific events, I would prefer a random factor in the trigger.
 
Yukala said:
atwar = Yes = GER

Are you sure this works? I have never seen a trigger configured thus.

blue emu said this:

atwar = GER

the scenario will load with that trigger but i dont no if the event will fire cos all i did to test was fire it manually to make sure there was no CTD's etc.
 
russ555 said:
the scenario will load with that trigger but i dont no if the event will fire cos all i did to test was fire it manually to make sure there was no CTD's etc.

It could just read to the 'yes' and call it good, but since it loads that is half the equation. Using 'yes' in the line seems logically redundant, either to the 'yes' itself or to specificity of GER.