Grand ID and tag repository

• Electors of the HRE. There's a trigger for elector-status [elector=yes/no] Note: You cannot change the elector status, it's set at scenario start in file country.csv.
  There's a trigger for emperor [emperor = yes/no] Note: You cannot send events to the emperor, only usable as a trigger.
• Emperor. You can now use -6 to indicate current emperor instead of -1 for random country in an event command. (AFAIK this haven't been used much, so I'm unaware of potential problems.)
• Change graphics. Flagname extension code 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". 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. The command type = flagname which = "" will set the graphics to the original one.

• Provinceculture. It does not work at all.
• Discovered. It triggers only works if the particular country getting the event has discovered the province.
• Relation. It should be relation = { country = PAP data = 120 } instead of relation = { country = PAP value = 120 }, which will give false positive whenever relations are positive (positive relations = positive trigger).
• Leader. Trigger works for all leaders, even those of other countries.
• Monarch. Trigger only works for the monarchs of the country getting the event.

• Breakdynastic. It does not work at all.
• Breakvassal. Doesn't work if in the overlord's event, unless the game has been reloaded since the vassalage was created. You cannot have a new vassalisation event triggered from the event that breaks the current vassalisation. It seems to be a problem with when it checks the conditions for the commands.
• Sleepleader. It works for all leaders, even those of other countries.
• Sleepmonarch. It should have the same comment as sleepleader: Note: Does not work if the monarch is living.
• Province_revoltrisk. It modifies 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). It cannot be lowered to below zero.Testing shows that changing tag doesn't change or reset provinces revoltrisk value. (For example Muscovy -> Russia)
• Vassal It can create weird situations. It still works if the two countries are at war with each others and can also create situations where they are vassals to each others. It's up to the event scripter to check conditions in trigger for these situations not to happen.
• Fortress + Population. Use of fortress and population commands in same action and for the same province:
  For fortifications increase, population (increase or decrease) command must be placed before the fortress command.
  For fortifications decrease, population (increase or decrease) command must be placed after the fortress command.
  Otherwise, the fortress command won't work. Remark: fortress command is not limited by landtech.
• Trigger. It says "Triggers event xxxx immediately" Note: this is only true if the event's triggering conditions are met.
• Mine. Unfortunately you cannot mix non-gold trade goods and increased mine income. The event will fire granting the mine, but nothing happens to your revenue from that province.
• War.
  
  The War command doesn't work if one or more following conditions are fullfilled:
  country DoWing is granted military access by the target country
  country DoWing and the target country are in the same alliance
  country DoWing is at -3 stab
  
  First condition can't be checked in triggers but the others should be. If a war command is used in an action, be sure of intended result.
  
  Since war can be avoided without control of modders, it is wise to have it as single command of an action in an event where at least two actions are proposed. Remember, an action where all commands are impossible is simply not displayed. So, if war is impossible, the event will work with the remaining options and still have a meaning. In this case, avoid to ask a question in description unless two other choices can be made.
  
  About -3 stab:
  If war is really wanted, we must be sure stability is greater than -3 for DoWing country before event fires. Adding stability + 1 by command in the same event as the war command has no effect. Nor will lowering stability to -3 (if stability is above -3) in the same event as the war command prevent war.
  
  About Vassal/Suzerain:
  A vassal can have a war command against its suzerain. Vassalage will be broken by the vassal at the same time, with corresponding stability drop for vassal.
  A suzerain can have a war command against its vassal. Vassalage will be broken by the vassal at the same time, with corresponding stability drop for suzerain. Vassalage don't have to be made before game reloading (not the same as bugged breakvassal command).
  
  It is impossible to release a vassal and DoW it in the same event. This is tied to the independence command and not the war command itself.
  A vassal can DoW its suzerain in an event for the vassal triggered by event for the suzerain where the vassal is released. However, in this case, it's recommended for clarity to explicitly add a breakvassal command for the known vassal just before the war command (in case the war command doesn't work, we have at least the minimum effect of a broken vassalage).
  
  Diplomatic relations (sending diplomat) within a month before the war command doesn't prevent it from functioning, as was previously reported to be the case.
  Targeting (-6) declares war on the country holding the Emperor title.

• Location for leaders. For explorers: if province is not owned by the country or not a port, the explorer will appear in nearest owned port according to area in province.csv.
  For conquistador: if province is not owned by the country, the conquistador will appear in nearest owned province (not sure for TP) according to area in province.csv. Admiral and generals seem to appear in the capital if they cannot be placed as intended.
• Rank of monarch leaders. A Leader of the category monarch can have any rank, but will have the icon of that rank, i.e. they wont be displayed as monarchs, but as generals, fieldmarshals etc.
• Events without country or province entries. An event without country tag or province ID specified will trigger for the player as soon as any tag, no matter where in the world it is or who controls it, can make the trigger true. Therefore they are mostly useless.
• Monarch value changes. When changed by -1 (MIL, ADM or DIP) they do not display in the event effect text or mouseover. All other values appear to be OK, and the changes are implemented.
• Monarchs. When a new monarch is available, either because his start date is reached or he is woken within his life span, he will replace any current monarch at once. The replaced monarch is removed from the game, even if his death date isn't reached. So, there's no way to use a monarch twice. If there is no new monarch to replace a monarch after his death date, he will stay as on until replaced.
  If a country is annexed and then released as vassal or revolts, it will always use the setup form the monarch file, regardless of which ones have previously been slept and woken.
• Tag change. Changing tag doesn't reset flagname. As a rule, always reset flagname to "" just before changing tag!
• Tag change. Changing tag doesn't load any new AI file.
• Length of leader names. If the name is too long it wont fit the army window. Maximum length is 18 for vanilla standard font and 17 for the agceep more legible font, always according to the use of capital letters and of spaces.
• Length of monarch names. If the name is too long it wont fit the country window. Maximum length is 35. The monarchs page provided in the ledger allows very short names of (unknown) length.
• Random events. Date, offset and deathdate are not taken in account in random events. Any start and final years has to be set in the trigger. Random event can be nation specific. A random event cannot trigger another event.
• Culture of Revolters. They can only have one culture specified for it in the revolt file. If more cultures are specified they are simply ignored.
• Conditions for Revolters. A "no = tag" in the revolt.csv means that it cannot revolt from the coutry with that tag, but can revolt from any other country. It is possible to have more than 1 "no =" in the same entry in revolt.txt. ( If there are several different countries that you don't want a certain revolter to form from.)
• Diplomaticdate. Setting last diplomatic date in the scenario file:
  diplomaticdates = { ENG = { year = 1422 month = october day = 21 }
  thereby preventing a new diplomat from being sent before a specified date, only works for players. The AI ignore the restriction.

• Revolters. A revolter that revolt another state out of existence, by appearing in the last province of that state, will cause a CTD. For example: if Catalonia appeared in the last province held by Aragon, that is the province Catalonia, it will lead to a CTD. Use the possibility in the revolt file to specify what nations cannot exist for a state to revolt. If it should revolt in the capital of a multi-provincial state, the capital wil be randomly relocated.
• Tag changing. If a nation change tag with the country command, it will cause a CTD if it tries to release it's old tag as a vassal, without a reload in between. (For example: Country A turns into country B and then tries to release country A.)
• Ceding capital. If the capital of a country is ceded (command secedeprovince) the result is a CTD.
• Ceding provinces. If the last province of a country is ceded (command secedeprovince) the result is a runtime error dialog box followed by a CTD.
• Trigger: event = xx If an event is directly triggered by another event, and at the same time has that event as a trigger prerequisite it will result in a CTD.
• Ships. Adding warships or galleys with -3 can lead to a CTD, if the previous -1 targeted a city without a port.

0 - Snow, October through May. It is most prevalant in November through April.
1 - Desert type weather.
2 - Certainly no snow with this value. It appears in a couple of Baltic Sea provinces, a couple of South American provinces, most of North America, and one Siberian province. It might be intended to provide very occasional snow, but still, the province assortment is wierd.
3 - No snow.
4 - Tropical climate.
5 - Some snow December through February.
6 - Tropical climate. This one seems mostly used in equatorial provinces, compared to a value of 4.
7 - Snow, November through March. It is most prevalent in December through February.
8 - Snow, June through August. Used in the southern hemisphere and in a couple of Afghani and Indian provinces (north of the equator).

Click to expand...

0 Plains
1 Forests
2 Mountains
3 Desert
4 Marshes
5 Ocean
6 River
7 Border
8 Terra incognita
9 Unknown

Click to expand...

• War. Can have negative values, as proved in a test where the value -500 led to no wars decared at all. [1, post 1]
• War, Core & Hitlist. A test that give a good feeling for how they combine in the decision of the AI declaring war. It's tested with a strong Ottoman Empire and a weak Byzantium. It seems that the three parameters sum up, with the hitlist adding the most. [1, post 24 & 33]
• Traders. We have tested how fast the AI send traders with different settings. It seems rather linear: no merchants sent on 0 (the merchants are wasted), and more and more for higher settings. Lower values is more profitable for the AI, at least early on. [4, post 5 & 12-14]
• Colonisation. The costs of making Spain achieve historical colonisation have been calculated. The problem that some nations can never make it without help was quantified.[5, post 1]
• Colonists and Colonisation. The net flow of colonists must be above 0, and preferably higher, in order for the AI to send them. A full pool and money is not sufficient.[5, post 134]

• Wether the AI cares about a temporary casus belli in its decision to start a war.
• Is there a noticable effect in the order of the tags, and IDs of provinces. For example, if the AI can chose to declare a war on four tags, is one of them more likely than the others?

1. Meet AGCEEP: Scripted nations & AI aggression The influence of cores, hitlists and the war setting. ALL READ
2. The Effects of Culture, Religion and Cores on AI Tendencies: a controlled experiment NOT READ YET
3. IDLF's AI Bible NOT READ YET
4. A new AI system for AGCEEP Test on how the AI send merchants and background for the current AI system AGCEEP use. ALL READ
5. Why the AI is so bad at colonization? Also about naval exploration, post 40.