• 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.
some bugs in in descriptions

I'm translating Aberration into polish (translating into my language is much
easier than writing in english here :rolleyes: ) and just found some bugs in country
descriptions. Only parts of several descriptions are visible (Hungary, Hanza,
Granada, Genua) - I think it has correlation with using 'enter' in 'text.csv'
file - text is visible to line with enter (i removed it for myself and all is now
correct for me).
 
Not sure if this is specific to Aberration, but I'm playing as Byzantium. Declared war on Bulgaria and called allies. Albania dishonoured the alliance, so I decided to attack them as well - but the Declare War option is greyed out and on mouseover a message appears saying "You cannot declare war on Albania again until 0"
 
It doesn't sound like Aberration-specific issue. Were you perhaps in a war together with Albania against someone else already or had stab at -3 or something?
 
In epo_rus, the byzantine reaction event, you gain 150 relations with yourself. For some reason I don't think thats right.
 
I bet it should be KIE instead of BYZ in that epo_rus event 202214 relation effects.

And yes, that nasty "Two Bs" bug seems to not have been corrected yet. Event 201939, second action_b should be action_d.

While waiting for next patch, you may fix these yourself for your version if you like.
 
Erik Pleskow (Hansa's monarch #30259) should be "dormant = yes". He's the action_c for the 6th Hansetag-event (200204)
 
Some more errors I found in 1.06b:

202192 (epo_hus) has 2 action_a
200228 (major_hsa) has 2 action_a
200977 (major_sav) has action_b instead of action_a
200333 (major_sco) has 2 action_b
 
Hansa bugs

In 200223 (A Question of orientation), if Option B is chosen (focus on Germany), both 'Religion is all' events remain active. This means that come 1560-odd, the Hansa must choose Protestant or Catholic, then choose Reformed or Protestant, or possibly in the other order, but the A choices entail two conversions in quick succession. This amount of turmoil seems excessive, especially as choosing to focus on Germany is meant to be the 'safe' option for a weak Hansa. So I think Option B needs to sleep 200225.

About the Sund Crisis events: the simplest solution here would be to not have 200206 trigger anything, and to make 200206 the condition on the resolution events. On the subject of those, the 'Hansa loses' event seems a bit harsh - are we saying that if they don't OWN Sjaelland within 5 years of getting a core on it, they must be incapable of securing the Sund? The trouble is the AI will often be in other wars, or will even beat the UoK but ask for the wrong province or indemnities, so I think we need to either give them longer; put a DOW and some soldiers/ships in the crisis event (with opt-out); or allow the Hansa to reverse the damage if they do later take Sjaelland.
 
Last edited:
Bug in Byzantium Events?

event = {
id = 200137
trigger = {
event = 200134
OR = { NOT = { domestic = { type = aristocracy value = 2 } }
domestic = { type = centralization value = 9 }
}
}
random = no
country = BYZ
name = "Noble revolt"
desc = "As emperor Theodoros II had died and his weak and incompetent brother Ioannes VIII had succeeded him, the nobility saw that it was time to demand back their rights. They have risen up in arms and demand return of their rights. Shall we give in or fight them?"
style = 3
date = { day = 1 month = august year = 1646 }

action_a = {
name = "Give in"
command = { type = domestic which = aristocracy value = 4 }
command = { type = domestic which = centralization value = -4 }
}
action_b = {
name = "Fight them"
command = { type = stability value = -3 }
command = { type = revolt which = -2 }
command = { type = revolt which = -2 }
command = { type = revolt which = -1 }
command = { type = revolt which = -1 }
command = { type = revolt which = -1 }
command = { type = revolt which = -1 }
}
}

event = {
id = 200149
trigger = {
NOT = { event = 200136 }
event = 200134
OR = { NOT = { domestic = { type = aristocracy value = 4 } }
domestic = { type = centralization value = 7 }
}
}
random = no
country = BYZ
name = "Noble revolt"
desc = "As emperor Theodoros II had died and his weak and incompetent brother Ioannes VIII had succeeded him, the nobility saw that it was time to demand back their rights. They have risen up in arms and demand return of their rights. Shall we give in or fight them?"
style = 3
date = { day = 1 month = september year = 1646 }

action_a = {
name = "Give in"
command = { type = domestic which = aristocracy value = 2 }
command = { type = domestic which = centralization value = -2 }
}
action_b = {
name = "Fight them"
command = { type = stability value = -3 }
command = { type = revolt which = -2 }
command = { type = revolt which = -1 }
command = { type = revolt which = -1 }
}
}


In the above events, I think there may be an error in 200149. It appears that it should read Not event 200137 rather than 200136, as 200149 is clearly the alternative event if 200137 does not fire.

Matty
 
And Moreover

Byakhiam said:
You are correct Matty, it should be 200137 instead 200136.

I think there is also a possible disconnect with the following event


####################################
# Choice after Michael Doukas, naming for Palaiologoi
####################################

event = {
id = 200150
trigger = {
OR = { event = 200122
event = 200123
event = 200124
}
}
random = no
country = BYZ

As Michael Doukas is also gained through submission to his revolt (or victory over the Bulgarian line) in events 200140 or 200141, shouldn't there be a link to 200150? Currently this event seems only triggered by the standard Palaiologos and Kantakouzenos lines.

Perhaps the trigger for 200150 could be changed just to Michael Doukas' monarch number.

Byakiam, I have been slowly compiling an event flowchart for Byzantium, so I've been going through the events with a fairly fine comb. I'm only at 200150 so far, however. Once it is done, I'd like to send it to you for checking. Mayne afterwards it can be posted.

Matty
 
Actually, 200150 is only triggered by Palaiologoi lines, as it has "Naming for Palaiologoi" remark in it. You have to remember that after Michael Doukas there are "Palaiologoi" and "Kantakouzenoi" namings to keep the numbers in order.

The Kantakouzenoi version, which also takes Boulgaroi into account is event 200152. :)

EDIT: Though it seems Michael Doukas' rebellion against Boulgaroi has a slight bug. Submitting should also sleep 200143.
 
Byakhiam said:
Actually, 200150 is only triggered by Palaiologoi lines, as it has "Naming for Palaiologoi" remark in it. You have to remember that after Michael Doukas there are "Palaiologoi" and "Kantakouzenoi" namings to keep the numbers in order.

The Kantakouzenoi version, which also takes Boulgaroi into account is event 200152. :)

EDIT: Though it seems Michael Doukas' rebellion against Boulgaroi has a slight bug. Submitting should also sleep 200143.

Then I have a little conundrum.

Selecting choice A (Michael, Monarch 40185) in 200115 is one of the triggers for event 200117, Sale of Athens. This triggers the Palaiologoi end-time events (either 200118 or 200120), which I had assumed meant that by selling Athens, that the Kantakouzenoi line re-entered the Palaiologos event-stream, thus leading to 200150.

However, 200151 (Kantakouzenoi version of the Doukas end-time event) is triggered by event 200138, which refers back to having chosen the original Kantakouzenoi options back in 200115. But one of those was Michael.

So, it would appear on the surface that if you chose Michael (200115 A) then you will ultimately trigger both 200150 and 200151.

Have I missed something?
 
You are correct that choosing Michael in either 200115 or 200116 will give you 200117, Transfer of CoT to Hellas. But in Palaiologoi end time event 200118 (only one of the three which matter for this case) also states as a trigger that monarch may not be 40186, who is the Kantakouzenoi line monarch of Michael's line for the event's time period. So Kantakouzenoi will not trigger Palaiologoi Turmoil events.
 
Event 201124 for BYZ (but in major_gen.txt), which is triggered by a 1-prov Genoa seeking Roman protection, should have the line

command = { type = inherit which = GEN }
 
In misc_colony.txt the Uruguay events (210339-210344) all have two province 216 entries in their triggers and add cores, instead of a 215 & 216.

E.g.:
event = {
id = 210339
random = no
province = 215
trigger = {
NOT = { core = { province = 215 data = -1 } }
owned = { province = 215 data = -1 }
OR = {
owned = { province = 218 data = -1 }
owned = { province = 216 data = -1 }
owned = { province = 214 data = -1 }
}
OR = {
owned = { province = 217 data = -1 }
owned = { province = 216 data = -1 }
owned = { province = 214 data = -1 }
}
OR = {
owned = { province = 217 data = -1 }
owned = { province = 218 data = -1 }
owned = { province = 214 data = -1 }
}
OR = {
owned = { province = 217 data = -1 }
owned = { province = 218 data = -1 }
owned = { province = 216 data = -1 }
}
OR = {
owned = { province = 216 data = -1 }
owned = { province = 216 data = -1 }
owned = { province = 214 data = -1 }
}
OR = {
owned = { province = 216 data = -1 }
owned = { province = 218 data = -1 }
owned = { province = 214 data = -1 }
}
OR = {
owned = { province = 216 data = -1 }
owned = { province = 218 data = -1 }
owned = { province = 216 data = -1 }
}
OR = {
owned = { province = 216 data = -1 }
owned = { province = 217 data = -1 }
owned = { province = 214 data = -1 }
}
OR = {
owned = { province = 216 data = -1 }
owned = { province = 217 data = -1 }
owned = { province = 216 data = -1 }
}
OR = {
owned = { province = 216 data = -1 }
owned = { province = 217 data = -1 }
owned = { province = 218 data = -1 }
}
continent = europe
}
name = "Claim of Uruguay"
desc = "Congratulations! We have now established a strong colonial base in Uruguay."
style = 2
date = { day = 1 month = january year = 1419 }
offset = 3600
deathdate = { day = 30 month = december year = 1819 }
action_a = {
name = "Excellent"
command = { type = addcore which = 216 }
command = { type = addcore which = 217 }
command = { type = addcore which = 218 }
command = { type = addcore which = 216 }
command = { type = addcore which = 214 }
command = { type = vp value = 10 }
}
}
 
nlilith said:
In misc_colony.txt the Uruguay events (210339-210344) all have two province 216 entries in their triggers and add cores, instead of a 215 & 216.

E.g.:

215 is in all options by it's placement outside the OR-lines.

However it is quite obvious that there are several bugs in the trigger, seeing as how there are dozens of OR where there should be one OR and several AND - like this..

Code:
event = {
	id = 210339 
	random = no
	province = 215 
	trigger = {
		NOT = { core = { province = 215 data = -1 } }
		owned = { province = 215 data = -1 }
		OR = { 
			AND = {
				owned = { province = 214 data = -1 }
				owned = { province = 216 data = -1 }
				owned = { province = 217 data = -1 }
				}
			AND = {
				owned = { province = 214 data = -1 }
				owned = { province = 216 data = -1 }
				owned = { province = 218 data = -1 }
				}
			AND = {
				owned = { province = 214 data = -1 }
				owned = { province = 217 data = -1 }
				owned = { province = 218 data = -1 }
				}
			AND = {
				owned = { province = 216 data = -1 }
				owned = { province = 217 data = -1 }
				owned = { province = 218 data = -1 }
				}
			}
		continent = europe #not so sure about this one
		}

		name = "Claim of Uruguay"
		desc = "Congratulations! We have now established a strong colonial base in Uruguay."
		style = 2
		date = { day = 1 month = january year = 1419 }
		offset = 3600
		deathdate = { day = 30 month = december year = 1819 }

		action_a = {
			name = "Excellent"
			command = { type = addcore which = 214 }
			command = { type = addcore which = 215 }
			command = { type = addcore which = 216 }
			command = { type = addcore which = 217 }
			command = { type = addcore which = 218 }
			command = { type = vp value = 10 }
		}
	}

Nice spot - there is a lot of text in that file, making it dull to check (obviously)