AGCEEP FAQ & Tips

[Garbon]

What is the AGCEEP?

Soon after the release of Europa Universalis II a group of enthusiasts started the "Event Exchange Project". The purpose of the EEP was to provide players with additional historic events. It also provided what-if events for countries usually doomed to obliteration, like the Byzantine Empire.

Eventually a great schism arose within the EEP causing the "Alternative Grand Campaign" Project to split off from the EEP. The AGC Project sought to also include more historical events and focused on providing more options to allow players to play the version of the Grand Campaign that they wanted to. Eventually the EEP and the AGC were able to put aside their differences and recombine their efforts into the AGCEEP Project.

The AGCEEP has created a large set of new events, modified many existing events, and added or modified leaders, monarchs, graphics, AI files and scenario setup. The AGCEEP has also taken on other mods as part of it such as Alun's Reformation Mod and Peter Ebbesen's Manpower Mod as well as the AI files of Daywalker's greatest AI mod.

Finally, thanks are due to all the people who contributed to this project.

Thanks to Paradox for creating this wonderful game.


Disclaimer: The AGCEEP is not supported in any way by Paradox. Moreover, the AGCEEP and its creators bear no responsibility for any potential problems you might experience while using the AGCEEP.

See our website for more information and helpful tips

http://www.agceep.net/

 

[Garbon]

Note that the version of AGCEEP posted on our website is not currently compatible with FTG

 

[Garbon]

Style Guidelines for Events

When posting on Paradox forum, following format for events is highly recommended but not mandatory:

#(<year> or <startyear-deathyear>) <name of the event>
#By <name of the author> <- modified by ... / with the help of ...>
event = {
	id = <id> #triggered by <TAG>_<corresponding id> <A, B, C or D>
	trigger = {
		...
	}
	random = yes/no
	country = <TAG> or province = <id> #<name of the province>
	name = "EVENTNAME<id>" #<name of the event>
	desc = "EVENTHIST<id>"
	#-#

	date = { day = <> month = <> year = <> }
	offset = <>
	deathdate = { day = <> month = <> year = <> }

	action_a = {
		name = "ACTIONNAME<id>A" #<name of action A>
		command = { ...
	}
	action_b = {
		name = "ACTIONNAME<id>B" #<name of action B>
		command = { ...
	}
	action_...
}

EVENTNAME<id>;<name of the event>;;;;;;;;;;
EVENTHIST<id>;<description on a single line (without carriage return)>;;;;;;;;;;
ACTIONNAME<id>A;<name of action A>;;;;;;;;;;
ACTIONNAME<id>B;<name of action B>;;;;;;;;;;
ACTIONNAME<id>...

*****​

Always use CODE markup (# button in advanced editing) to insert events.

Indentation should be made with tabulations and not spaces.

The id of a new event should be the first free id as found in corresponding events file. Be aware other modders could have already used the first free id... Please be careful.

Use comment "#triggered by ..." only if necessary. If event can be triggered by several events, use / as separator for each event.

Trigger is optional. Never forget to indent inside trigger.

Offset and deathdate are optional but if one of them is used, both are mandatory. A deathdate until the end of the game is deathdate = { year = 1820 }, nothing else...
Never forget day range in EU2 is 0-29 (and not 1-30). See Scripting complements for details.

If no date in the event (triggered event), just have a blank line between #-# and action_a

For commands about provinces, add "#<name of the province>" at the end of the line (without double-quotes)
For commands about monarchs, add "#<name of the monarch>" at the end of the line (without double-quotes)
For commands about leaders, add "#<name of the leader> (<TAG>)" where TAG is the country tag of the leader, at the end of the line (without double-quotes)
For commands about other events, add "#<TAG>: <name of the event>" where TAG is the country tag for the event (or ProvinceSpec), at the end of the line (without double-quotes)
These rules apply to triggers too.

EVENTNAME<id>;<name of the event>;;;;;;;;;;
EVENTHIST<id>;<description on a single line (without carriage return)>;;;;;;;;;;
ACTIONNAME<id>A;<name of action A>;;;;;;;;;;
ACTIONNAME<id>B;<name of action B>;;;;;;;;;;
ACTIONNAME<id>...
These lines must be posted outside CODE markup and are for inclusion in text.csv.

For modified events, use red color to show information to be removed and yellow color to show modifications or added comments.


When new or modified event will have impact on setup of scenarios (province manpower, income, cores, owned or known provinces, policies,...), these effects should be part of submission.

It is useful for all modders to write events in the same way as this helps a lot for:

1. discussion before submission
2. compilation time and inclusion of texts in text.csv
3. readability of the event when modification needed in events file

See events files for examples.