I'm sad to report that I'm another victim of this bug after putting 57 hours into AC Valhalla on PS5. I've enjoyed AC Valhalla a great deal overall, but, unfortunately, this isn't the first issue I've had with the game. However, unlike the bug with Defensive Measures, reloading an earlier save hasn't solved the issue with A Brewing Storm for me (or for anyone else by the looks of it). It's totally unacceptable that Ubisoft have allowed this game-breaking bug to persist for so long after the launch of the game and I personally believe that AC Valhalla falls under the definition of 'faulty goods' under the UK Consumer Rights Act 2015, which should entitle anyone in the UK to a full refund from their retailer. Unfortunately, I was given the game as a present, so getting a refund isn't as much of an option for me. I don't have time to restart the game, so I'm left to wait for Ubisoft to fix a bug that the game should never have been released with.

I did actually manage to find Dag in Ravensthorpe. He kept becoming hostile and then stopped being hostile. I was able to kill Dag, but then there would be a weird fireworks-like explosion and he would just get up again. I also had something weird happen early on in the game where the Sussex questline completion trophy was unlocked while I was still in Norway, so I don't know if that was a factor in the bug, although it seems like so many people have been affected across all consoles and PC that it must be a wider problem with A Brewing Storm.

Frankly, Ubisoft needs to make fixing this game-breaking bug their number one priority over any other development related to AC Valhalla. It's unacceptable for Ubisoft to continue to release paid or free DLC for the game when so many people have experienced this bug. Cyberpunk 2077 was fairly criticised for the amount of bugs it released with, but at least I was able to complete that game and at least CD Projekt Red now seem to be taking the problems seriously and prioritising them above releasing DLC.

I'm sad to report that I'm another victim of this bug after putting 57 hours into AC Valhalla on PS5. I've enjoyed AC Valhalla a great deal overall, but, unfortunately, this isn't the first issue I've had with the game. However, unlike the bug with Defensive Measures, reloading an earlier save hasn't solved the issue with A Brewing Storm for me (or for anyone else by the looks of it). It's totally unacceptable that Ubisoft have allowed this game-breaking bug to persist for so long after the launch of the game and I personally believe that AC Valhalla falls under the definition of 'faulty goods' under the UK Consumer Rights Act 2015, which should entitle anyone in the UK to a full refund from their retailer. Unfortunately, I was given the game as a present, so getting a refund isn't as much of an option for me. I don't have time to restart the game, so I'm left to wait for Ubisoft to fix a bug that the game should never have been released with.

I did actually manage to find Dag in Ravensthorpe. He kept becoming hostile and then stopped being hostile. I was able to kill Dag, but then there would be a weird fireworks-like explosion and he would just get up again. I also had something weird happen early on in the game where the Sussex questline completion trophy was unlocked while I was still in Norway, so I don't know if that was a factor in the bug, although it seems like so many people have been affected across all consoles and PC that it must be a wider problem with A Brewing Storm.

Frankly, Ubisoft needs to make fixing this game-breaking bug their number one priority over any other development related to AC Valhalla. It's unacceptable for Ubisoft to continue to release paid or free DLC for the game when so many people have experienced this bug. Cyberpunk 2077 was fairly criticised for the amount of bugs it released with, but at least I was able to complete that game and at least CD Projekt Red now seem to be taking the problems seriously and prioritising them above releasing DLC.