Home Trending Latest threads New posts Developer diaries

Accolade succession goes through multiple characters instantly and doesn't end up on chosen successor

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Crusader Kings III 19825 Console 323 Suggestions 5930 Bug Report 4129 Tech Support 2430 User Mods 1906 Multiplayer 162 AARs (After Action Reports) MP Open Beta Feedback 27
A

arandomuser

Private
Jan 6, 2019
19
22

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​

Accolade succession goes through multiple characters instantly and doesn't end up on chosen successor

Description​

When my current knight who currently holds an accolade dies, the succession process goes through 3 different characters before ending up on a character which I have not specified as the successor. I have designated a successor for the accolade and he fulfills the condition for both the primary and secondary accolade.

In the save file attached, the accolade holder in question will always die in 15 days.

Steps to reproduce​

I have absolutely no idea Accolade succession worked fine up to this point. Save file attached. In the save file, the accolade in question is the first accolade - "Noblest of Noble Warriors". In addition, changing my accolade successor from the one already designated in the save file to the character which ends up as the successor after the 3 jumps will not stop the 3 jumps from happening, but will instead happen again but this time the jumps will end at the character which was supposed to be the successor in the first place. This does not "fix" the issue as the jumps will have sapped away the glory anyway.

Game Version​

Lance 1.9.1

Platform​

Windows

Additional Information​

Affected Feature​

  • Gameplay

Save Game​

View attachment accolade inheritance bug.ck3

Other Attachments​

View attachment accolade inheritance bug.ck3

 
  • 4
  • 2Like
Reactions:
Upvote 7
I have been experiencing similar weirdness - one person dies and I get 2-3 notifications about Accolade loss and different successors - and of course I also end up with the secondary stat of the accolade completely changing. :(
 
  • 1Like
  • 1
Reactions:
For what it's worth - not really a "fix" per say, but a quick hack is out. I dropped a Stam Workshop mod (Unlock all accolades) which bypasses the main issue - resetting accolade secondary. Actual accolade succession / successor selection seems to be hardcoded in CK3.exe, but I was able to remove all personal requirements from accolades, thus allowing any knight to hold any accolade your culture is eligible for. It'll still go through the triple succession, but it will not reset the secondary. As a side effect, well, you have access to all accolades. =/
 
  • 2Like
Reactions:
HatleyD said:
For what it's worth - not really a "fix" per say, but a quick hack is out. I dropped a Stam Workshop mod (Unlock all accolades) which bypasses the main issue - resetting accolade secondary. Actual accolade succession / successor selection seems to be hardcoded in CK3.exe, but I was able to remove all personal requirements from accolades, thus allowing any knight to hold any accolade your culture is eligible for. It'll still go through the triple succession, but it will not reset the secondary. As a side effect, well, you have access to all accolades. =/
Click to expand...

My current fix for accolade succession bugs (and the one in the post is just one of many, there are others) is just to use the default debug mode right click "add glory" command. With a bit of creativity and wiggling this is a workaround for most things these bugs will mess up. [profanity moderated out]
 
Last edited by a moderator:
Did you guys all check that your acclaimed knight succsessor is a knight from you with setting "always/forced" (don't know the exact word, but should be the most left one)
 
TealCat said:
It usually is, because there are many other stronger knights / vassals. Does the bug only happen for those?
Click to expand...
Well I know that I sometimes just forced them, made them successor and then setted them back to allowed
I thought maybe there are multiple successors bc the charater is not a knight when he isn‘t forced to be one
 
Same issue has happened three times now. The chosen successor was set as 'forced' to be a champion but by that time had enough prowess to be a champion anyway. Both the dead knight and his successor were in an activity in the most recent instance, and this may have been the case before (our people feast a lot). The chosen successor, after being promoted and immediately replaced, was not shown as an option for the new successor until retiring and reinstating the accolade. As in previous cases, I had to destroy the accolade (which now had negligible glory) and re-create because the multiple succession had installed a random secondary.

The traits involved, if it matters, were Manipulator primary, Master of Revels secondary, and then randomly chose Scoundrel as the new secondary.
 
SupercanelP085 said:
Well I know that I sometimes just forced them, made them successor and then setted them back to allowed
I thought maybe there are multiple successors bc the charater is not a knight when he isn‘t forced to be one
Click to expand...
I always keep them on forced until they have actually become the acclaimed knight. Not even sure they would still be the successor if you set them to allowed and they don't have the prowess to stay a knight.
 
  • 1Like
Reactions:
Dubonka said:
Same issue has happened three times now. The chosen successor was set as 'forced' to be a champion but by that time had enough prowess to be a champion anyway. Both the dead knight and his successor were in an activity in the most recent instance, and this may have been the case before (our people feast a lot). The chosen successor, after being promoted and immediately replaced, was not shown as an option for the new successor until retiring and reinstating the accolade. As in previous cases, I had to destroy the accolade (which now had negligible glory) and re-create because the multiple succession had installed a random secondary.

The traits involved, if it matters, were Manipulator primary, Master of Revels secondary, and then randomly chose Scoundrel as the new secondary.
Click to expand...
secondary will always depend on the succsessor, since every accolade has its own requierements, and to be succsessor I think only primary gets checked if he/she can be the succsessor
 
SupercanelP085 said:
secondary will always depend on the succsessor, since every accolade has its own requierements, and to be succsessor I think only primary gets checked if he/she can be the succsessor
Click to expand...
Exactly, that's the problem. When this bug happens, your carefully chosen successor who satisfies both the requirements for the primary and secondary gets overridden by someone with a random secondary and that is frustrating.
 
  • 2Like
  • 1
Reactions:
TealCat said:
Exactly, that's the problem. When this bug happens, your carefully chosen successor who satisfies both the requirements for the primary and secondary gets overridden by someone with a random secondary and that is frustrating.
Click to expand...
They should made the secondary accolade attribute fixed as it is with the primary attribute, would be an easy fix for them.
 
You must log in or register to reply here.
Top Bottom
Back