• 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.

Norrefeldt

Porphyrogenitus
Aug 1, 2001
7.433
2
Visit site
NOTE: Most errors mentioned here have now been corrected. Still, continue to share your knowledge here!

There are several errors in his eminent Bible that people stumble on again and again. I have just started to collect some of them in a sticky in the AGCEEP forum, to be able to direct people to a list and to give overall better scripting. Other useful information for modders can also be posted there. Perhaps this can end up in the Wiki, where hard facts on modding is currently lacking.
(I'll add IDLF's AI Bible as a link and also the outcome from the thread half a year ago about the content of the province.csv.)
The humble start is here:
http://www.europa-universalis.com/forum/showpost.php?p=4364576&postcount=8

Please add your knowledge. :)
 
Last edited:
Breakvassalage command doesn't work if liege and/or vassal is at war too. Not sure for liege, never experienced myself, but sure for vassal when triggered by liege.
And Builder's Paradise is down actually :(
 
In Point 5
Flagname extension code, so that events can change the graphic flags/shields of a nation with the command "type = flagname which = "test", to change for example from using the standard file "flag_ENG.bmp" to "flag_ENGtest.bmp", same for shields.
At the end, instead of just "same for shields", I would say:
The command applies to shields too, ie. you need to have flag_ENGtest.bmp and both shield_ENGtest.bmp and smallshield_ENGtest.bmp aswell. All three bmp are required, otherwise, flag or shield will simply disappear in-game with no error encountered.
 
Norrefeldt said:
You don't happen to know when the WAR command does not work. IIRC it won't work if at war or allied to the target.
My post is related to the breakvassal command not working if liege or vassal is at war. Some tests to be made starting with Third Angel's sequence...

This wasn't about the war command.
 
And it does not work if you are -3 in stability
 
I found this in the bug forum, not very easy to get what he ment by it.

Daywalker said:
Yep -3 stab, alliance and Mil access I already knew, - yes Mil access also blocks the war command. I 2nd both -3 stab and alliance.
Mil access no. In-game, with the current working of Mil access, yes, - via event no.

I can’t get guaranty to block tho?? Or any other for that matter.

I suspect ‘war’ is subject to all in-game rules, as the only dip command.
Might be worth testing.
 
A couple of things I can think of that are incorrect in Havard's guide are the discovered trigger and the breakvassal command. The discovered trigger does work, but it affects the recipient of the event only. Anotherwards, it's the event recipient's exploration or lack of it that effects whether the event will fire or not. It's not the map knowledge of anybody else that matters.

The breakvassal command only works for the vassal. The suzereign can't break vassalage with it. I think ideally the guide should point that out.

Oh BTW, great modding guide Havard. You'd be amazed if you knew how often I use it. It's high on my list of bookmarks and I go to your site very often. Copy and paste, over and over again. :)
 
idontlikeforms said:
The breakvassal command only works for the vassal. The suzereign can't break vassalage with it. I think ideally the guide should point that out.
Problem is more complex. See here.

Btw, breakvassal command working or not is absolutly not tied to wars. See here.


idontlikeforms said:
Oh BTW, great modding guide Havard. You'd be amazed if you knew how often I use it.
Me too :)
 
idontlikeforms said:
A couple of things I can think of that are incorrect in Havard's guide are the discovered trigger and the breakvassal command. The discovered trigger does work, but it affects the recipient of the event only. Anotherwards, it's the event recipient's exploration or lack of it that effects whether the event will fire or not. It's not the map knowledge of anybody else that matters.
Thanks, should be included.

idontlikeforms said:
The breakvassal command only works for the vassal. The suzereign can't break vassalage with it. I think ideally the guide should point that out.
I have it on my list, but after YM's latest test I have to rewrite it.
 
Commands for countries and provinces:

command = { type = province_revoltrisk which = x value = y }

Modify the revolt risk in province x with value y indefinitely, until lowered by another event, or until the province is in the hands of another nation (this also applies to nations changing tags).
What is "this" intended for?
1) just "until the province..."
2) full sentence

This is confusing or maybe it is just my bad english...

To be really clear: changing tag doesn't change provinces revoltrisk value.

EDIT: grammar...
 
Last edited:
To be more precise: revoltrisk is cleared when a province change ownership but remains intact if owner just changes tag.

To be sure, I made this test:
Code:
#event1#
event = { 
    id = 150500
    random = no 
    country = KNI 
    style = 1 
    date = { day = 3 month = january year = 1419 } 
    name = "event1" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = province_revoltrisk   which = 481 value = 20 }
    } 
}

#event2#
event = { 
    id = 150501
    random = no 
    country = KNI 
    style = 1 
    date = { day = 10 month = january year = 1419 } 
    name = "event2" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = country  which = JER } 
    } 
}
In AGCEEP with 1.08b 21th apr (not tested with 1.08 alone and should work in vanilla same way), without any in-game modification, RR in Rhodes is 19% after event1. It is still 19% after event2.

EDIT: IIRC, this is related to the "lost loans when changing tag bug" patch. Same logic anyway.
 
Last edited:
Clarification for random events (section 3.3):
As I figured out in AGCEEP with "Petty Kingdom of the Barabary Coast" random events, and checked in other random events:
Date, offset and deathdate are not taken in account in random events. In order to check dates in random events, use of "year" condition in triggers is the only one solution.