Forum Discussion

LeDudeAwesome's avatar
LeDudeAwesome
Seasoned Newcomer
5 days ago

Disrupt and Conquer unable to progress

Hello all! After the update on 11/7, I've been unable to complete the solas memory quest "disrupt and conquer", as the enemies are not spawning inside the area. The opening dialogue to the spirits plays as usual, but the Rook dialogue after about being a spirit of disruption does not play. Has anyone run in to this issue/know a fix or way around it?

  • The same is happening with mine except even before the update the quest won’t progress.

    • LeDudeAwesome's avatar
      LeDudeAwesome
      Seasoned Newcomer

      Want to see if we've tried some of the same things. I reloaded previous saves and completely left the area, even tried changing my rook's voice in case that had something to do with it. Anything you've tried outside of that?

      • JTK5694's avatar
        JTK5694
        New Novice

        I tried reloading an auto save, a manual save, and reinstalling the game. The quest won’t spawn enemies and I can’t get the double doors to open after firing the ballista at the rocks.

  • rvanhorn1234's avatar
    rvanhorn1234
    Seasoned Newcomer

    Same here - about halfway through enemy's stop spawning and there is a wall that blocks progress.

    Video of what it looks like for me - https://youtu.be/HScYJPvrpJ4

      

  • I’m so glad I’m not the only one having this issue! I only finished the quest once but it was after letting Dock Town get attacked and I didn’t realize how permanent the consequences of the main story quest was, so I reloaded to an earlier save and haven’t been able to progress past the ballista at all. Now I save-scum out of sheer panic to no avail 😭

  • This quest is all sorts of buggy. I slid down into the area to start, decided I wanted to explore more first and fast traveled away. Now on going back the quest never triggers (not even in the journal) and the opening scene with the spirits won't play and rocks block the path.

    As I'm on PC, I was able to use some debugging trickery to hop over the blocked path, but that was ultimately no help as the whole thing won't progress without the quest script running.