Welcome

Please register for Total War Access to use the forums. If you're an existing user, your forum details will be merged with Total War Access if you register with the same email or username. For more information please read our FAQ’s here.

Categories

Reloading save when reaching 10 fealty skips the confederation event

VenetianFoxVenetianFox Posts: 3Registered Users
I have found an easy-to-reproduce bug relating to the Empire's fealty and confederation mechanics. Upon reaching 10 fealty with an Elector Count and starting a new turn, you will normally be presented with an event to either confederate with the Elector Count at a cost of 3 Imperial Authority or choose to assert his independence for +1 Imperial Authority. If you choose to reload the auto-save from the START of that turn, the event will not fire again and the Elector Count will be stuck at 10 fealty, with you gaining no Imperial Authority.

In my case, I initially chose to confederate with Averland on turn 10, but immediately regretted that decision. Therefore, I chose to reload my turn 10 save so I could assert his independence and get +1 Imperial Authority instead. To my horror I saw that the event would not fire again. I reloaded a couple more times, but as you can see in the first screenshot, I had 10 fealty but no Imperial Authority was gained (or lost) because the event would not fire (turn 10 save file).



In the image above, you can see Averland has 10 fealty but I have not gained or lost any imperial authority from the confederation event because it did not fire.

I decided to play several more turns to see if the event would pop back up (it didn’t, see turn 18 save). Eventually, on turn 29 or 30 I had a DIFFERENT event choice that dropped Averland's fealty to 9. By luck, on turn 31, Averland's fealty went up to 10 by random chance. I once again got the confederation event and made sure to manually copy my save to another location to test my hypothesis. I chose to confederate and ended my turn to make the game generate a new legendary auto-save (to prevent a repeat of my turn 10 issue). I then reloaded the start-of-turn save to test my hypothesis and lo and behold the event had been skipped again (see third save file) and my suspicions had been confirmed. Also see my post-confederation event save to prove that the event did pop up initially, but that the save just before won’t fire that event on reload.

This evidence strongly suggests that something in the save mechanism of Total War: Warhammer 2 prevents an event from firing on reload. Obviously, if you already resolved the event and saved in some way, this is not a problem. However, if you choose to reload a beginning-of-turn save file this can be particularly brutal as you are forced to either go to war with the Elector Count or somehow drop their fealty to raise it again.

I would attach the modified.log file, but it's a zero byte file so that would be pointless.

Comments

  • VenetianFoxVenetianFox Posts: 3Registered Users
    edited October 1
    On further testing, the save reload method prevents many start-of-turn events from firing for that turn, not just the confederation event, so this issue is a bit more broad.
    Post edited by VenetianFox on
  • ComradeFranzComradeFranz Posts: 1Registered Users
    Hello VenetianFox,

    I have had the same issue on my autosave of an Empire Ironman Campaign, and am looking for an resolution that is alternative to playing along until i reduce-increase the fealty of Ostland to 10...

    I had a confederation happen, but after that, I attacked a 3 stack invasion of Norsca in Nordland, and the game crashed... After reloading, the same issue you described happened to me.

    Have you had any success in finding a different solution?

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file