Beware of this random CTD

[unmerged(29318)]

Have you ever got random CTD around 1534?
Maybe this could explain that.
i have playtest this vanilla event ENG_3009 several times in vanilla and MyMAP game

#The Act of Supremacy#
event = {

	id = 3009
	trigger = {
			religion = catholic
		}
	random = no
	country = ENG
	name = "EVENTNAME3009"
	desc = "EVENTHIST3009"
	style = 1

	date = { day = 1 month = january year = 1534 }
	offset = 30
	deathdate = { day = 1 month = january year = 1541 }

	action_a ={		#Take Command of the Church of England#
		name = "ACTIONNAME3009A"
		command = { type = religion which = protestant }
		command = { type = treasury value = 250 }
		command = { type = breakdynastic which = -1 }
		[COLOR=DarkOrange]#command = { type = relation which = -3 value = -150 }[/COLOR]
		command = { type = breakdynastic which = -1 }
		[COLOR=DarkOrange]#command = { type = relation which = -3 value = -150 }[/COLOR]
		command = { type = domestic which = CENTRALIZATION value = 1 }
		command = { type = stability value = -2 }
	}

	action_b ={	#Accept Rome's Supremacy, but ignore it on a personal level#
		name = "ACTIONNAME3009B"
		command = { type = relation which = PAP value = 100 }
		command = { type = relation which = SPA value = 100 }
		command = { type = stability value = 1 }
	}
}

color line was bugfix for that.
This random CTD will happend if England have no dynastic alliance. that event will lower relation betwen ENG and random state. Like relation with Crimea
Problem was MIN also in this random list
in vanilla-> MIN: (Undefined Nation)
in MyMAP or AGCEEP -> MIN: Masovia
So if event couse lower relation between ENG and MIN ..BOOM.! CTD happen, except for MyMAP or AGCEEP if Masovia exist.
This screenshoot was taken before CTD happen (can't use F11 to take this screenshoot )

Fix this event yourself...
cause there is no more new patch for EU2. maybe there is still other similar event like this.

 

[Duke of Wellington]

Well found Agung. I hope that solves things.

 

[unmerged(51378)]

Here, have a HUGE HUG! Thank you thank you thank you! Now I get what was going on with all those CTD's around that date.

 

[Ayeshteni]

Nice one

Aye.

 

[cool-toxic]

Great, haven't happend for me, but it can happen in the future so thanks

 

[CatKnight]

That's odd. My copy already had those orange lines (relation which = -3) etc. inside of it. Or are you saying I should take those out?

 

[unmerged(3931)]

That's odd. My copy already had those orange lines (relation which = -3) etc. inside of it. Or are you saying I should take those out?

Well random events have the same relations line, like diplomatic insult, boundary dispute, and merchants harrassed.

So the problem is not in relations, otherwise there would be CTDs all the time.

Perhaps the breakdynastic chooses an invalid country when there is no royal marriage. Then the relation line chooses that same invalid country and causes the problem?

 

[Ayeshteni]

That's odd. My copy already had those orange lines (relation which = -3) etc. inside of it. Or are you saying I should take those out?

It confused me at first but if you look carefully he has HASHED THEM OUT (emphasis, not shouting)

so they should be hashed out. I think what he is saying is that the -3 can apply to the MIN non-defined country tag, which would cause a crash.

so hash the two relation lines out.

Ayeshteni

 

[the_genius]

Thanks Agung for the heads-up .... as soon as I get home will check on this

 

[unmerged(20292)]

Matur nuwun!

 

[Ayeshteni]

Matur nuwun!

 

[unmerged(44386)]

Indonesian for 'thankyou'

 

[unmerged(29318)]

Indonesian for 'thankyou'

"terima kasih"
"Matur Nuwun" was Javanese for 'thankyou'

Well random events have the same relations line, like diplomatic insult, boundary dispute, and merchants harrassed.

So the problem is not in relations, otherwise there would be CTDs all the time.

Perhaps the breakdynastic chooses an invalid country when there is no royal marriage. Then the relation line chooses that same invalid country and causes the problem?

That's right. Problem was in this command

command = { type = breakdynastic which = -1 }

But there is no problem if ENG have royal marriage ( dynastic alliance )
So I just suggest to modified this line like this to avoid CTD

[B]#[/B]command = { type = relation which = -3 value = -150 }

Or just delete that line.
IF ENG have royal mariage that will broke up , and if haven't, no CTD happen

 

[unmerged(44386)]

"terima kasih"
"Matur Nuwun" was Javanese for 'thankyou'

Oh well o

 

[unmerged(20292)]

Sorry to violate the English-only rule of this forum. But I am guessing that not many Javanese posts are made, and I promise never to do it again.

Seriously, this was a good find: I have had that CTD numerous times.

 

[AndrewT]

Thanks for finding this. I'd be grateful if someone has a way of searching all the event files for possible occurrences of this.

 

[KaRei]

Good work Agung Pasha.

But one thing isn't still clear to me: if MIN (undefined nation) is in list of randomly choosable countries for commands like change relation with random country, then all commands that are using -1 instead country TAG could cause CTD because of possible selection of undefined country, couldn't they?

This would mean that any command of change relation, break dynastic, random casus belli, etc. using -1 is CTD generator and can't be fixed.

 

[Norrefeldt]

As breakdynastic doesn't work in the first place (the command is bugged) this thread should be moved to the Bug forum so to be included in the text file update Andrew makes there. That's where it should have been posted in the first place.

 

[unmerged(29318)]

As breakdynastic doesn't work in the first place (the command is bugged) this thread should be moved to the Bug forum so to be included in the text file update Andrew makes there. That's where it should have been posted in the first place.

I've playtest that. This breakdynastic command work when ENG have royal Marriage. And I know this thread should be in the Bug forum. I post here cause many people especially newbie only come to general forum. and we know there will be no more new patch for EU2 . All of us need to fix it ourself.
BTW AGCEEP 143b also have this bug

 

[unmerged(29318)]

Good work Agung Pasha.

But one thing isn't still clear to me: if MIN (undefined nation) is in list of randomly choosable countries for commands like change relation with random country, then all commands that are using -1 instead country TAG could cause CTD because of possible selection of undefined country, couldn't they?

This would mean that any command of change relation, break dynastic, random casus belli, etc. using -1 is CTD generator and can't be fixed.

Maybe only for these command but who knows .

command = { type = breakdynastic which = -1 }