BUG: NEW: Breakvassal command bug

[Third Angel]

Breakvassal command bug

Here is a simple events sequence to check it:

#event1#
event = { 
    id = 150500
    random = no 
    country = ARG 
    style = 1 
    date = { day = 3 month = january year = 1419 } 
    name = "event1" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = vassal which = NAP } 
    } 
}

#event2#
event = { 
    id = 150501
    random = no 
    country = ARG 
    style = 1 
    date = { day = 10 month = january year = 1419 } 
    name = "event2" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = breakvassal which = NAP } 
    } 
}

#event3#
event = { 
    id = 150502
    random = no 
    country = NAP 
    style = 1 
    date = { day = 17 month = january year = 1419 } 
    name = "event3" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = breakvassal which = ARG } 
    } 
}

Both Aragon and Naples are at peace in 1419, so that's not the problem.
Now all three events will fire normally, but events 1 and 3 will always work fine, while 2 will only work if you saved and reloaded your game between the 3rd and 10th of january.
As Aragon you will not be able to break the vassalage through the diplomatic menu either until you save/reload.
As Naples the command will work fine anytime.

 

[AndrewT]

This relates to this thread http://forum.paradoxplaza.com/forum/showthread.php?t=208678

My reading of the Breakvassal command is that indeed it is only intended to ever be used against the vassal itself. That said, there are events in vanilla that go both ways, eg the one which breaks SWE's vassalage from under DEN is in the SWE event file, whereas the one where POR breaks free of SPA is in SPA's file.

So I guess I need to determine if it is intended to work both ways.

I don't understand the difference between your Events #1 and #2, they seem identical. Why would one work and not the other? In whose event file are they, NAP's or SPA's?

 

[Norrefeldt]

I don't understand the difference between your Events #1 and #2, they seem identical. Why would one work and not the other? In whose event file are they, NAP's or SPA's?

One creates and the other breaks the vassalage? The event file doesn't matter, as long as it's in the list of loaded files. It can be SPA's or NAP's or any other file.

 

[Third Angel]

One creates and the other breaks the vassalage? The event file doesn't matter, as long as it's in the list of loaded files. It can be SPA's or NAP's or any other file.

Thanks Norrefeldt.

Andrew T: Maybe I should not have spoken of the save/reload part as it seems to render things messier. If you would just copy the three events to whichever event file and run the game as Aragon you will see that, if the breakvassal command was intended to work both ways, then there is indeed a bug.

 

[AndrewT]

Oops, I was concentrating so much on the Country and target fields that I missed the different command.

The indications backstage are that it is not intended to work both ways; the target (aaa) must be the vassal. How it does anything at all when you put the overlord as the target I don't understand.

Given that, it's hard to understand that event#2 has a problem and #3 doesn't, as #2 is in the overlord's file and correctly targets the vassal. Maybe it needs a month to elapse between the two events?

 

[AndrewT]

A little survey reveals puzzling results. Here is info about every breakvassal commend in the standard events:

major_por.txt - breakvassal which=SPA - 3274b
major_cas.txt - breakvassal which=SPA - 3849c
major_arg.txt - breakvassal which=SPA - 3850c
major_kni.txt - breakvassal which=SPA - 3540b
major_boh.txt - breakvassal which=HAB - 3643a
major_cyp.txt - breakvassal which=VEN - 3843b
major_dai.txt - breakvassal which=CHI - 3904a
major_eir.txt - breakvassal which=ENG - 3829a
major_eng.txt - breakvassal which=HAN - 3039b
major_eng.txt - breakvassal which=HAN - 3043b
major_lit.txt - breakvassal which=POL - 3447b
major_pru.txt - breakvassal which=LAT - 3516a, b
major_nor.txt - breakvassal which=DAN - 3846c
major_swe.txt - breakvassal which=DAN - 3219a
major_swe.txt - breakvassal which=DAN - 3217c

major_spa.txt - breakvassal which=POR - 3168a
major_spa.txt - breakvassal which=ARG, CAS, CAT - 3169a
major_pol.txt - breakvassal which=RUS - 3494a

The last three are the only cases where the command is in the overlord's event file and targets the vassal. The others are all in the vassal's event file and target the overlord. As far as I'm aware, these all work, I suspect we would have heard about it by now otherwise.

So it seems my info is incorrect, but in any case if these do all work it's puzzling why your test example Event #2 doesn't, unless it is the month-end thing I mentioned before.

 

[unmerged(40707)]

So it seems my info is incorrect, but in any case if these do all work it's puzzling why your test example Event #2 doesn't, unless it is the month-end thing I mentioned before.

I made a test with event2 and event3 in march (more than a month) instead of january. The problem remains the same.

 

[Third Angel]

The last three are the only cases where the command is in the overlord's event file and targets the vassal. The others are all in the vassal's event file and target the overlord. As far as I'm aware, these all work, I suspect we would have heard about it by now otherwise.

The first ones working is no surprise as the command always works when targeting the liege. I think you didn't heard about the last three because the breakvassal is only in option A and I think human player usually picks option B and doesn't see the bug. Only AI would pick option A and then human player would not necessarily notice it (unless he is himself the vassal, which is not likely for experienced players)

So it seems my info is incorrect, but in any case if these do all work it's puzzling why your test example Event #2 doesn't, unless it is the month-end thing I mentioned before.

I tried it with events #2 and #3 in january 1420, it didn't work either.

 

[AndrewT]

The only one of the three I listed I could conveniently test was

major_spa.txt - breakvassal which=POR - 3168a

and indeed it seemed to completely fail. Saving and reloading between POR becoming my vassal, and breaking the vassalage, did allow it to work. Also, trying to manually break the vassalage via the diplomatic menu had the same effect - it only worked after a save and reload.

So let me see if I have the situation correct.

- the Breakvassal command always works if placed in the vassal's event file and targeted at the overlord
- the vassal can always manually cancel his vassalage via the diplomacy menu
- the Breakvassal command will not work when place in the overlord's event file and targeted at the vassal, unless the game has been saved and reloaded after the vassalage happened
- an overlord cannot cancel a vassalage via the diplomatic menu, unless the game has been saved and reloaded after the vassalage happened
- an overlord can cancel a vassalage which was present at the start of a scenario via the diplomatic menu
- a vassal which was created by the overlord during the game cannot have the vassalage cancelled by the overlord via the diplomatic menu unless the game has been saved and reloaded after the vassalage happened

This last facet of the problem is actually a known bug:

317 : Type: GAME LOGIC | Status: NEW | Severity: NORMAL
Cannot set free vassal created during game
Reported In: 1,05 | Correction planned In : | Corrected In :

so I think I'll actually update that bug with the full details, as it's a poor description of even that part of the problem.

As I doubt this will ever be fixed, I guess we now have to look at modifying those three events so that at least they will work; this means writing new events containing the Breakvassal command for POR, ARG, CAS, CAT and RUS and having the existing Overlord events trigger those rather than having the Breakvassal commends in the Overlord event files. Anyone care to have a crack at that?

 

[Norrefeldt]

Good it was cleared out, this will have implications in AGCEEP too. Lots of.
I cannot stop myself at being nit-picky, and I would only comment on this in a mod or bug forum, where things like this can lead to misunderstandment:

- the Breakvassal command always works if placed in the vassal's event file and targeted at the overlord
...
- the Breakvassal command will not work when place in the overlord's event file and targeted at the vassal, unless the game has been saved and reloaded after the vassalage happened.
...

This is correct if the word file is removed in both cases. The actual file is irrelevant, and is often the "wrong" one in mods.

 

[unmerged(40707)]

NOT A BUG: WaD: breakvassal command bug

I made a test (1.08b 21 apr 2005) with three sequences and had strange results regarding breakvassal command and wars.

Sequence 1:

#event1#
event = { 
    id = 150500
    random = no 
    country = ARG 
    style = 1 
    date = { day = 3 month = january year = 1419 } 
    name = "event1" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = vassal which = NAP } 
    } 
}

#event2#
event = { 
    id = 150501
    random = no 
    country = NAP 
    style = 1 
    date = { day = 10 month = january year = 1419 } 
    name = "event2" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = war  which = PAP } 
    } 
}

#event3#
event = { 
    id = 150502
    random = no 
    country = NAP 
    style = 1 
    date = { day = 17 month = january year = 1419 } 
    name = "event3" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = breakvassal which = ARG } 
    } 
}

Playing as Aragon, all three events work fine.
Naples is at war with Papal States
Aragon is at peace
Naples breaks Aragon's vassalization (Aragon is the liege).

Playing as Naples, all three events work fine.
Naples is at war with Papal States
Aragon is at peace
Naples breaks Aragon's vassalization (Aragon is the liege).

Sequence 2:

#event1#
event = { 
    id = 150500
    random = no 
    country = ARG 
    style = 1 
    date = { day = 3 month = january year = 1419 } 
    name = "event1" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = vassal which = NAP } 
    } 
}

#event2#
event = { 
    id = 150501
    random = no 
    country = NAP 
    style = 1 
    date = { day = 10 month = january year = 1419 } 
    name = "event2" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = war  which = PAP } 
    } 
}

#event3#
event = { 
    id = 150502
    random = no 
    country = ARG 
    style = 1 
    date = { day = 17 month = january year = 1419 } 
    name = "event3" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = breakvassal which = NAP } 
    } 
}

Playing as Aragon - saving and reloading after event1 or after event2 (in order to avoid bug for event3) and declaring war "manually" to Castille before event3. All three events work fine.
Aragon is at war with Castille
Naples is at war with Papal States
Aragon breaks Naples vassalage (Aragon is the liege)

Playing as Aragon - saving and reloading after event1 or after event2 (in order to avoid bug for event3) but not declaring war (at peace) before event3. All three events work fine.
Aragon is at peace
Naples is at war with Papal States
Aragon breaks Naples vassalage (Aragon is the liege)

Playing as Naples - saving and reloading after event1 or after event2 (in order to avoid CTD when event3 fires). All three events work fine.
Aragon is at peace
Naples is at war with Papal States
Aragon breaks Naples vassalage (Aragon is the liege)

Sequence 3:

#event1#
event = { 
    id = 150500
    random = no 
    country = ARG 
    style = 1 
    date = { day = 3 month = january year = 1419 } 
    name = "event1" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = vassal which = NAP } 
    } 
}

#event2#
event = { 
    id = 150501
    random = no 
    country = ARG 
    style = 1 
    date = { day = 10 month = january year = 1419 } 
    name = "event2" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = war  which = NAV } 
    } 
}

#event3#
event = { 
    id = 150502
    random = no 
    country = NAP 
    style = 1 
    date = { day = 17 month = january year = 1419 } 
    name = "event3" 
    desc = ""
    action_a = { 
	name = "Ok" 
	command = { type = breakvassal which = ARG } 
    } 
}

Playing as Naples, all three events work fine.
Aragon is at war with Castille
Naples is at peace
Aragon breaks Naples vassalage (Aragon is the liege)

Conclusion:
breakvassal command works in any case (war or not).
Not reloading if playing vassal when event3 is fired by the liege (sequence 2) => CTD

It seems that my problem wasn't tied to HAB being at war but really to not saving/reloading (ie. same problem as Third Angel).

 

[unmerged(17856)]

For the vassalage question, it might also have to do with diplomats. I think I read somewhere that you need a spare diplomat in order to break vassal or vassal someone via event. Also, I've had problems with vassal/break vassalage command via a second event that has been triggered by a first event. Anyone else have a problem in this area? It could be a lack of diplomats...

 

[unmerged(17856)]

Yes, I've seen this. You cannot have a new vassalisation event triggered from the event that breaks the current vassalisation.

There it is. This is what I meant. Nice to see confirmation.