Resolved difficulty gets reset to freebooter after quitting the game and reloading any save

[hr443]

Summary:difficulty gets reset to freebooter after quitting the game and reloading any save, from bannerlord and/or warrior
How to Reproduce:play the latest version ,select sandbox, create any character select bannerlord difficulty preset , enter game, save game , exit bannerlord app, relaunch bannerlord app , reload previous save created with bannerlord difficulty, open campaign options see freebooter difficulty whereas it was set to bannerlord and the other options prove the player already set one difficulty and the game resets to the freebooter one .
Have you used cheats and if so which:-
Scene Name (if related):-
Media (Screenshots & Video):https://postimg.cc/R6H7Rvjk
Computer Specs:-
OS:-
GPU:-
GPU Driver Version:-
CPU:-
RAM:-
Motherboard:-
Storage Device (HDD/SSD):

 

[MArdA TaleWorlds]

Forwarded to the QA team for further investigation. We will reach out again if we need more information. Thanks for reporting and sorry for any inconvenience!

 

[hr443]

issue still present in third 1.8.0 update.

 

[Dudsworth]

I have also been having this same issue in 1.8. Is it just a display bug where the difficulty preset shows Freebooter, or are the difficulty options actually set to Freebooter settings despite showing all of the settings for Bannerlord difficulty?

 

[R1919]

damn, and I was wondering why they've made recruiting so easy in 1.8.0 but my difficulty was reset to Freebooter without my notice

 

[Dudsworth]

Well, the difficulty may actually still be on Bannerlord difficulty in actuality. I cannot tell currently if it is just a display bug on the preset only, since all of the other settings still show realistic difficulty correctly, or if the settings are actually being set internally to freebooter difficulty.

 

[Dudsworth]

Okay, I just ran some tests and I can confirm, this is only a preset display bug. If you had it set to Bannerlord difficulty, the actual difficulty is still set to Bannerlord settings despite the fact that it displays Freebooter. Try changing the Map speed to the easiest, and you can see that your map speed is increased for a "Difficulty" setting increase. Also more recruitment slots are added if you set that setting to the easiest. Therefore, we can conclude that the Bannerlord settings are still being applied despite the fact that the Preset shows freebooter.

 

[hr443]

still ongoing in beta e1.9.0

 

[hr443]

still ongoing

 

[hr443]

still occuring in 1.0 release version

 

[hr443]

still occuring in 1.0.1.4833 release version

 

[ThompsoniusIV]

still occuring in 1.0.1.4833 release version

Let me help you.

Still occuring in v1.0.3.9860... it just seems they don't care

 

[hr443]

Still occuring in beta 1.1.0.10414

 

[Lockazz]

I had the same issue, I also thought that it was just a display error, but after the update its like the whole game is 10x times me difficult, so my understanding is that some parameters were configured as freebooter, so I played 200h on my last playthrough as a freebooter instead of bannerlord, being my first playthrough I thought this was normal, i am super disappointed

 

[MArdA TaleWorlds]

I've been informed that this bug is fixed and the fix will be sent to the game with future patches. Thanks for reporting and sorry for any inconvenience!

 

[DMilesMM]

I've been informed that this bug is fixed and the fix will be sent to the game with future patches. Thanks for reporting and sorry for any inconvenience!

This bug is still present at 23 March 2023 (v 1.1.2) on my system

 

[MArdA TaleWorlds]

The fix was not included on the latest hotfix. IT will be in part of the next big patch.

 

[Golimar]

This bug is still occurring in version 1.1.4.17949... Experienced players like me want to be sure if we are playing on a easy difficulty or the hardest one that is what we want to play.

 

[DaniAngione]

Still happening on Beta 1.2...
Campaign options get reset on reload. I can't confirm if just visual.

 

[MArdA TaleWorlds]

Could you send us a save file where you experiencing this issue? We were not able to reproduce this issue on our end.