6 types of vassal contracts are reset to defaults/none after save/load + mod fix included for 2

[nullpat]

Information​

I have verifed my game files (Steam only)​

Yes

I have disabled all mods​

Yes

I am running the latest game update​

Yes

Required​

Summary​

Coinage Rights vassal contract is removed after save/load + mod fix included

Description​

Please upvote the green arrow at the top right for visibility and an official fix from paradox -->


Bugged vassal contracts:
Fortification Rights
Coinage Rights
Scutage
March
Palatinate
Castellan

All vassal contracts have a default option of none/not granted, the bugged vassal contracts apply the default option after a save/load despite actual vassal contract state. Commenting out `default = yes` under fortification_rights, and coinage_rights in special_contracts.txt appears to fix this. This does not work for the 4 vassal contracts under special_contract. I made a mod posted below that fixes coinage and fortification as a proof of concept.

Original description:
I found another user who reported this issue but in the wrong forum. https://forum.paradoxplaza.com/foru...age-rights-after-saving-and-charging.1734513/ Sounds like it also affects multiplayer. Please upvote for visibility

Steps to reproduce​

1. Start as Bohemia in 1066
2. Grant Coinage Rights to vassal
3. Save game
4. Load game
5. Coinage rights is gone

Game Version​

1.15.0.2

Platform​

Windows

Additional Information​

Affected Feature​

• Gameplay
• Multiplayer

Save Game​

Other Attachments​

 

[nullpat]

Made a mod fixing "Coinage Rights Granted" to persist through save/load. Really quick and dirty mod, comments out a single line setting default to true, I'm not sure why this appears to fix the issue or what defaults are meant to do (the other contract rights also use this defaults line seemingly without issue), but you can now load an existing save where a vassal has coinage rights and it will work, as well as in a new game. Shrug.

Steam Workshop::(deprecated by 1.16.2) Coinage & Fortification Rights Fix

steamcommunity.com

(deprecated 1.16.2)Coinage & Fortification Rights Fix - Paradox Mods

DO NOT USE. Fixes

mods.paradoxplaza.com

 

[Pleda]

I was curious about this, because I have seen the same with palatinate contract, so I went in the game and tested.
And the problem is not only about coinage rights. All of the following are bugged:

Scutage
March
Palatinate
Fortification Rights
Coinage Rights
Castellan

 

[Pleda]

Update:
So... the coinage and fortification rights were easy enough cause both of them are fixed by the # in front of default, like your mod changes. However I'm not smart enough to figure out the other ones (yet)

 

[Snake_Squeezins]

I have had the same problem for weeks, thanks for flagging this for the devs.

 

[Crookback]

Is this a new bug or did it exist in older patches?

 

[MummyMonk]

Update:
So... the coinage and fortification rights were easy enough cause both of them are fixed by the # in front of default, like your mod changes. However I'm not smart enough to figure out the other ones (yet)

Let me jump in here quickly with how I understand what's going on: the "default = yes" line marks the default contract option that is normally chosen when setting a new fresh vassal contract. I assume that _for some reason_ all the special contract options (those governed by special_contracts.txt file specifically) are now pushed back to the default option after reloading the game, and that is probably a bug in the game engine/scripts due to some botched update. So when we comment out "default" line, we stop this "resetting the contracts to default options" faulty script from happening.

Now, if we comment out the "default = yes" command (by putting a # before it), then which options does the game choose when setting up a new vassal? Quite simply the first ones on each of the lists, and we are in luck here - because right now all the options that are normally default (no coinage rights, no revocation protection, no forced partition etc etc) are already the first ones on their respective lists, so we can simply comment out every instance of "default = yes" line there and be safe, as long as we don't move the options around.

So what about the scutage/palatinage/march/etc contracts? Quite simple: they all are arranged in a single large list of special contract types, and the default option ("None", a standard contract) is listed as the first one here as well, before the scutages, marches, palatinates and all the other special types. And it does have its "default = yes" line which we can comment out too (I did it below):

obligation_levels = {
special_contract_none = {
position = { 0 1 }
# default = yes
score = 0

So just search for "special_contract_none" and comment out the "default" line after it, and the special contract types (scutages etc) should stop auto-resetting to "None" on reload.

Do tell me if I'm awfully wrong and this doesn't work.

And I really hope that the devs fix the "contract auto-reset" that happens for the "special_contracts.txt" file options on their side, so that we don't have to invent the wheel here ourselves.

 

[nullpat]

Vassal contracts are still bugged in 1.16.1, please upvote on the top right of first post for visibility

@MummyMonk the simple commenting out of `default = true` unfortunately does not work for Scutage/March/Palatinate/Castellan as @Pleda said

 

[Pleda]

Upvoted it. I also made a bug report about it right after the newest update was released and it got responded to with that they have added it to their database. Then they locked it.

 

[MummyMonk]

Vassal contracts are still bugged in 1.16.1, please upvote on the top right of first post for visibility

@MummyMonk the simple commenting out of `default = true` unfortunately does not work for Scutage/March/Palatinate/Castellan as @Pleda said

Well, that's sad I must have misinterpreted how this part of the code works then.
Anyway, upvoted this long time ago and hope this gets properly fixed by the devs at last.

 

[Pleda]

This was fixed today. Thanks Paradox!