CK II - Ragnar's descendents lose pirate traits upon reloading the game

[Slaists]

One line summary of your issue
Ragnar's descendents lose pirate traits upon reloading the game

Game Version
3.0.1.1 (ONDO)

What expansions do you have installed?
All of the above

Do you have mods enabled?
No

Please explain your issue is in as much detail as possible.
I have a catholic ruler of England whom I have turned Norse . He also has the blood of Ragnar, which provides pirate traits for raiding. The problem is, whenever I reload the game, his pirate trait resets to zero... Looks like a bug.

Steps to reproduce the issue.


Upload Attachment

 

[Ceebie]

Hello, I cant reproduce this issue. I tried starting in 867 as one of Ragnar's sons and giving myself the "Pirate" trait. Upon reloading the game, the trait is still present in-game. are you sure you dont have any mods active? have you verified your files through steam?

 

[Joshua Flier]

I've also experienced this issue but it didn't happen every time I reloaded, just intermittently. I got all the way up to Sea Queen twice on one character and she had nothing when she died. The only mod I had active was the flat water graphics mod and I verified the files.

 

[junassa]

Hello, I cant reproduce this issue. I tried starting in 867 as one of Ragnar's sons and giving myself the "Pirate" trait. Upon reloading the game, the trait is still present in-game. are you sure you dont have any mods active? have you verified your files through steam?

The lowest tier will stay, but the higher tiers will be lost. I don't know if this bug exists for his dynasty or only for others. All I can say as African pagan I've gotten his blood in my main line but I've been unable to keep the higher tier traits upon reloading.

edit: also this has been reported multiple times here. This is one of threads I was able to find: https://forum.paradoxplaza.com/foru...g-trait-every-time-i-reload-the-game.1159133/

another thread:

https://forum.paradoxplaza.com/foru...line-lost-on-game-load.1130680/#post-25011472

 

[Slaists]

Hello, I cant reproduce this issue. I tried starting in 867 as one of Ragnar's sons and giving myself the "Pirate" trait. Upon reloading the game, the trait is still present in-game. are you sure you dont have any mods active? have you verified your files through steam?

Yes, no mods active, default Ironman settings.

As others commented below, this happens intermittently. Sometimes, the trait disappears, sometimes not. As others mentioned, the bug seems to affect the higher tier traits, not the first tier. How I noticed it myself was when I got messages that my character has just earned the lower tier trait, but I knew he had the higher tier before. Then, I started to pay attention.

This does not seem to happen when I play as Norse pagan. Then again: for Norse Pagan players, the trait is available even without Ragnar blood. The bug showed up when I played as a Christian ruler of Wessex (having brought Ragnar's blood into my line).

 

[Joshua Flier]

What the above posts reported about only losing traits above Pirate also jives with what I recall. I just wasn't certain enough of it to put it in my report.

 

[redtide]

I suspect that this is due to a difference in the "potential = { }" block.

The pirate trait has the condition:

has_character_flag = acquired_pirate_trait_by_bloodline

The ravager, seaking, and sea_queen traits do not have that condition and instead have the condition:

any_owned_bloodline = {
    has_bloodline_flag = bloodline_viking
}

My current character is an African pagan, Berber, Ragnarr-blooded pirate. I replaced the "has_character_flag = acquired_pirate_trait_by_bloodline" condition with the "any_owned_bloodline" condition. When I loaded the save, the character was no longer a pirate. Thus, I believe that adding "has_character_flag = acquired_pirate_trait_by_bloodline" to the potential blocks of the ravager, seaking, and sea_queen traits will allow them to be kept upon reloading.

 

[junassa]

I suspect that this is due to a difference in the "potential = { }" block.

The pirate trait has the condition:

has_character_flag = acquired_pirate_trait_by_bloodline

The ravager, seaking, and sea_queen traits do not have that condition and instead have the condition:

any_owned_bloodline = {
    has_bloodline_flag = bloodline_viking
}

My current character is an African pagan, Berber, Ragnarr-blooded pirate. I replaced the "has_character_flag = acquired_pirate_trait_by_bloodline" condition with the "any_owned_bloodline" condition. When I loaded the save, the character was no longer a pirate. Thus, I believe that adding "has_character_flag = acquired_pirate_trait_by_bloodline" to the potential blocks of the ravager, seaking, and sea_queen traits will allow them to be kept upon reloading.

where'd you find this file?

 

[redtide]

common / traits / 02_traits.txt

 

[junassa]

common / traits / 02_traits.txt

Thanks. I hope to have this modded in a few hrs. (I say hrs cuz I stink at this lol).

Well that was easy. Made the mod, consoled myself to have sea king, saved and exited, reloaded and still had sea king trait. Gonna publish in a sec.

https://steamcommunity.com/sharedfiles/filedetails/?id=1708899938

edit: just so everyone knows this mod is bugged for reasons I don't understand. From what I can see it works fine if you don't have Sea bound + daring in your religion, otherwise the pirate trait will overwrite higher traits. This is now in the description of the mod.

 

[redtide]

Hello, I cant reproduce this issue. I tried starting in 867 as one of Ragnar's sons and giving myself the "Pirate" trait.

Try it with a character who meets none of the other conditions in the "potential = { }" block aside from the bloodline condition (Ragnar's sons wouldn't lose the traits because they're of the Germanic religion). Only the second and third tier traits are lost (i.e. Ravager, Sea King, Sea Queen). The fix I proposed seems to work. Maybe something wrong with the "any_owned_bloodline = { }" condition?

 

[Ceebie]

Hello everyone, just to update as it appears to have become quite a discussion. we now have this issue logged internally as another forum user provided us with a reproduction case.
thank you all.