BUG: NEW: Unable to release a vassal you created

[unmerged(5822)]

Unable to release a vassal

As Prussia, I set Finland free as a vassal of mine. However, I want them to be entirely free so that my alliance leader (our friendly neighbourhood Russia) will see the benefits of allying with an orthodox Finland. The option for ending the vassalization is highlighted (non-grey), but nothing happens when I click it.

Current version is 1.05.

 

[sirbruce]

I think this is a known bug; I saw someone mention it before.

Bruce

 

[AndrewT]

285 : Type: Interface | Status: NEW | Severity: MINOR
Vassalization can only be broken when both parties are at peace; however, the option is always available.
Reported In: 1.04 | Correction planned In: | Corrected In:

 

[sirbruce]

That's a different bug, AndrewT.

In 1.05, at least, the command to *release* a vassal by the parent country does nothing. The vassal has to actually break the vassalage.

Bruce

 

[unmerged(5822)]

Vassalization can only be broken when both parties are at peace

I'm quite sure that neither of us was at war; Finland was just created, and I was not involved in any currently ongoing war.

 

[AndrewT]

Yes, sorry, I misread. Are you saying that no-one can turn free one of their vassals since 1.05? That seems like a big bug for no-one to report by now. Let me try it.

 

[AndrewT]

No, I was able to cancel Spain's vassalisation of Naples at the start of the AoEx just fine in 1.05 and in the current beta.

The only other bug I know of like that is the failure of the breakvassal command in events, but I don't think that's what you are talking about here.

So, Onslaught, I'll need a save game of this to see what's happening. Do you have one you can send?

 

[sirbruce]

Andrew, perhaps it only works on newly created vassals? Because that is how I had tested this.

So, try this instead as a test... load up a Grand Campaign as the Mameluks, wait until January 3rd, and then create the Kingdom of Jerusalem as a vassal. Then try to release them via the diplomacy menu. It won't work.

Bruce

 

[unmerged(5664)]

Why don't you try waiting a few days, or even a month, and then see if it works?

I know that there's a problem with creating vassals - often you can't do it on Jan 1, but you can on Jan 8 or so. Maybe the same kind of factor is at work...

 

[sirbruce]

The problem with creating vassals ends at Jan 3rd; I already reported it but its pretty minor.

Not being able to release a vassal, though, is more of a problem.

Bruce

 

[AndrewT]

You're right, the bug does happen if you create a vassal but not if you have one already at the start of the game. I'm still surprised no-one's noticed this but I think I see where the problem is too. I'll check up on this and let you know.

 

[AndrewT]

Logged as Public bug 317, Bugzilla bug 2740. Thank you.

 

[unmerged(5822)]

I'm still surprised no-one's noticed this

I think that tells us a lot about the general playstyle of the EU2 population...

Think you could mark this thread, now that it has been verified as a new bug? (i.e. put "BUG: NEW: " first in the line or something?) I've always wanted to start a bug thread that would get a positive marking...

 

[unmerged(5664)]

Originally posted by AndrewT
You're right, the bug does happen if you create a vassal but not if you have one already at the start of the game. I'm still surprised no-one's noticed this but I think I see where the problem is too. I'll check up on this and let you know.

Out of curiosity, do you know why this is? I can't think of anywhere in the savegame that would show whether you had released a country as a vassal, or gained it as a vassal in some other way.

 

[AndrewT]

The alliance type is a dynamic code 4712 which is different to the static code assigned to ones that exist in the scenario files of 6000. I assume the bug comes from that.

 

[unmerged(5664)]

Interesting - I had no idea it would be saved differently. Thanks for the info!