Confirmed CK III - Elected Player Heir not inheriting Realm Capital

[blubmaster]

Short summary of your issue
Elected Player Heir not inheriting Realm Capital

Game Version
1.4.0 Azure

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled?
No

Have you tried verifying your game files (Steam only)?
Yes

How much "pain" is this causing you?
10

Please explain the issue you experienced in the most condensed way possible
Using Scandinavian election, my Primary Title (Empire of Britain) and Kingdom Titles (incl. Kingdom of England) will be succeeded to my nephew (winner of the election), i.e. my Player Heir. However, all county duchies - including the Realm Capital Middlesex/London - will go to my first-born son instead.

Realm succession is set to Confederate Partition and states "... with the Player Heir always being given the Primary Title, Realm Capital, and ...". Therefore I would have expected my Player Heir to receive the Realm Capital.

Please explain how to reproduce the issue
1. Take decision to choose Scandinavian Election on top tier titles
2. Have majority vote for a candidate that is not Primary Heir
3. Lose Realm Capital to Primary Heir, instead of Player Heir

Is there anything else you think could help us identify/replicate the issue?


I have attached a save game
Yes

Upload Attachment
File(s) attached

 

[Duke Reginald of Chutney]

Hello blubmaster!

I played around with this for a bit and it seems to be a problem with the wrong titles being divided based on the Confederate partition. But it only shows the wrong titles in the succession tab. I've played it through till your main ruler dies and all of the titles look like they are inherited properly.

So there is definitely a bug here, but it is purely the wrong titles being displayed and does not seem to effect the mechanics of title inheritance once you die.

I will add it to our system for further review.

Thanks for the report!

 

[Sapient_Pest]

Just posting that I'm having confederate partition issues myself, and title inheritance is absolutely not working correctly. I have made another post about this issue, but I'm also bringing it up here in-case anyone else having this issue comes here and thinks that they're just imagining things.

 

[Cuna]

Same issue.
can somebody from mods or devs elaborate? or just keep ignoring it?
the heir is NOT even getting the capital as the description says for all partition type rules.
capital always goes to some random son

 

[TheUnspeakable]

Just to let you all know. The bug is that, if you only hold one of your highest tier realm and it and your lower tier realms are all Elective or you a using max Crown Authority to select your heir, then your capital duchy's counties will go to whomever would be your heir if you were running plain Confederate Partition with no Heir selected. Having multiple of your highest tier realm (Kingdom or Empire) will prevent the bug.

 

[FrontLine1111]

For me it is not just a display problem. I'm playing as Anglo-Saxon with AS Elective/confederate. I have like 5 sons and have elected my second born. Under no circumstances does he ever get London when I die. My primary duchy gets chopped up and my oldest gets the capital no matter what.

Oh I should mention, I have the Kingdom of England with capital set to London. I have duchies of East Seaxe and Kent with all counties in my domain as well as westmoreland county by itself.

 

[BoVice9]

I'm baffled that there has been no urgency to fix this issue in over a year. But, to share what I've discovered to work around the issue, it only occurs when you have one of your highest title (i.e. 1 dutchy, 1 kingdom, 1 empire). To prevent this bug from completely derailing your playthrough, try to maintain 1 or more if you plan to elect any other heir than your oldest.

 

[FrontLine1111]

I'm baffled that there has been no urgency to fix this issue in over a year. But, to share what I've discovered to work around the issue, it only occurs when you have one of your highest title (i.e. 1 dutchy, 1 kingdom, 1 empire). To prevent this bug from completely derailing your playthrough, try to maintain 1 or more if you plan to elect any other heir than your oldest.

I think you mean more than 1 as opposed to 1 or more, correct? I think I'll just use debug mode until the problem is fixed. Pretty disappointing to have to do this though. I certainly won't be buying any expansions with glaring bugs like this going unaddressed.

 

[BoVice9]

I think you mean more than 1 as opposed to 1 or more, correct? I think I'll just use debug mode until the problem is fixed. Pretty disappointing to have to do this though. I certainly won't be buying any expansions with glaring bugs like this going unaddressed.

Correct. I meant to say 2 or more.

 

[BoVice9]

Unsurprisingly, but none the less disappointedly, this bug is still present in 1.7. If anyone is experiencing this bug please upvote next to OP's post to hopefully get some visibility on this persistent issue.

 

[Guinnessmonkey]

Got the same in 1.7.

I have a Norse-Angle Empire of Brittania with Scandinavian Elective and Partition set. My second son has been elected heir. But the worthless first son is still set to inherit my capital, London. This has happened two generations in a row.

 

[mistilteinne]

Same thing happened for me (I guess). I've elected a heir who was supposed to inherit the kingdom title (and he had the majority of votes), then my character died, and the game should have switched me to my new heir but for some reason I was left 'watching' the game with my dead character; I decided to switch to the heir manually but it turned out he was landless, and the kingdom was inherited by some other son (not even the oldest, idk how it was chosen).

 

[explosivealan]

i have this bug reported 2 years ago XD
and it is still here XDDDD

 

[TheUnspeakable]

They claim it's "not a major issue" because "only a small percentage use elective." Well DUH, it's because it's broken!

 

[DrahcirThorne]

So they know their game is broken, they know exactly how it's broken, and they just...don't care?

I would imagine it would be quite a quick and easy fix, too.

Oh, and in case it's not obvious, I'm here because this just happened to me and totally derailed my game. I had to reload several times and try to make things work properly by working around the problem. After an hour of work I was able to get it to where I only had to revoke one title after succession, but presumably I have to go through this nonsense every time my player character dies.

Extremely disappointing that they have known about this bug for over a year and just don't care, meanwhile they keep churning out new content and adding new features without bothering to fix the broken features we already have.

This is an act of Tyranny and I have just lost a lot of opinion for Paradox.

 

[BoVice9]

*sees that a new patch focusing on big fixes has been released… ready to reinstall the game he once loved*

*reviews 1.8 patch notes for bug fixes….*

*closes eyes for a number of seconds*

*lets out a deep, defeated sigh*

*opens up another game*

 

[kazper]

They claim it's "not a major issue" because "only a small percentage use elective." Well DUH, it's because it's broken!

Did they really say that? Can you link me?

This is pretty outrageous. I just came back to playing this game after playing it a lot right after release and was immediately hamstrung by this bug.

Elective is one of the most powerful ways to manage succession early on - or it was before it was broken. If not a lot use it it's because it's hidden away in duchy/kingdom law, where many people never look.

Either fix your bugs or remove the option to go elective, Paradox. As it is your game is unplayable without debug mode for me. Going 200 years with no alternative to partition is a no-go.

 

[TheUnspeakable]

Did they really say that? Can you link me?

This is pretty outrageous. I just came back to playing this game after playing it a lot right after release and was immediately hamstrung by this bug.

Elective is one of the most powerful ways to manage succession early on - or it was before it was broken. If not a lot use it it's because it's hidden away in duchy/kingdom law, where many people never look.

Either fix your bugs or remove the option to go elective, Paradox. As it is your game is unplayable without debug mode for me. Going 200 years with no alternative to partition is a no-go.

Dude, I reported this in 1.2 and have made sure it was reported every major patch since then, I have no idea how far back they said it. If you want to go dumpster diving, be my guest.

 

[Lord Swearingen]

Just came here to express my utter astonishment that the devs have allowed this straightforward, gamebreaking bug to go unaddressed for years.

No wonder they had to rewrite the community guidelines in an effort to spare their own feelings. This outrageous negligence just broke my ironman game.

HEY, DEVS, WAKE UP.

 

[Lord Swearingen]

This is absolutely infuriating. It shows total contempt for a devoted player base.