Assassin’s Creed Valhalla’s second major content update the Siege of Paris DLC is out and the game is great so far, but there are some bugs with the game that’s preventing a lot of players from enjoying the game to the fullest or they find themselves stuck with the game. One of the bugs in the game is the Assassin’s Creed Valhalla: Siege of Paris can’t progress in “The Queen’s Gambit.” After you have saved the queen, she goes back into the cave you saved her from and gets stuck.
Nothing you do can get her out and hence you are stuck with the bug. Stick with us through the post and we will share some solutions that can help you progress in the game.
Fix Assassin’s Creed Valhalla: Siege of Paris Richardis Not Leaving Cave Bug in “The Queen’s Gambit”
After you have saved the queen, you need to go after her to a safe place and converse, but the queen walks back into the came she came out of and gets stuck. Does it sound like something you have encountered, then, here is what you need to do.
Abandon the campaign quests for now and do rebel missions. After you have done a number of missions return to the campaign and you will find the Queen in Lisieux. As for the number of quests you need to do before returning to the campaign, 5 or 6 quests are known to do the trick.
If you have just started with the game, it’s advised that you make a save before the “The Queen’s Gambit” just in case something goes wrong. Create a save before “Sister of Sorrow” as “The Queen’s Gambit” is a continuation.
Another solution shared by a user is to completely abandon the conversation with the queen. When you encounter the bug, return to Lisieux and the campaign marker should move to the town. From there on, you can continue the campaign.
There are also users who reported that they didn’t do anything and the bug fixed itself. All they did was allow the game to reset and when they started the game again, the AC Valhalla: Siege of Paris Can’t Progress in “The Queen’s Gambit” bug was fixed.
If the above solutions have not worked for you, waiting for a patch is the only option. The developers are aware of the issue and working on it.
