Guild Wars 2

There is a bug in the story mode of Sorrow’s Embrace where when you get to the point where Zojja needs to pick the lock, she just stands there and does nothing. The events do not proceed as they should and we cannot progress through the dungeon. The cutscene where Caithe explains Destiny’s Edge is still there and we watch it and we are at that point in the dungeon doing it the normal way.

This is something that needs to get fixed really fast as it halts progression.

I recall same thing happening when I soloed it.
I think it happens if NPCs are dead when you enter the picklock event. However I just needed to wait few minutes and door automatically opened.

Wethospu.6437:

I recall same thing happening when I soloed it.
I think it happens if NPCs are dead when you enter the picklock event. However I just needed to wait few minutes and door automatically opened.

I don’t think that’s the case. I remember doing it on my alt account a few weeks ago, and we had to back-track a little bit to find and res the NPC’s. Once they were res’d, they started the event and everything continued as normal. Maybe it’s just inconsistent? idk.

The Mexican Cookie.3690:

Wethospu.6437:

I recall same thing happening when I soloed it.
I think it happens if NPCs are dead when you enter the picklock event. However I just needed to wait few minutes and door automatically opened.

I don’t think that’s the case. I remember doing it on my alt account a few weeks ago, and we had to back-track a little bit to find and res the NPC’s. Once they were res’d, they started the event and everything continued as normal. Maybe it’s just inconsistent? idk.

Well, for my group and I every NPC was alive and well before we started the cutscene. It just wouldn’t go and we even back tracked a bit killing every single mob just to be sure. Still nothing.

necro topic, my party is experiencing this exact bug right now.

Gatiha.9483:

This is something that needs to get fixed really fast as it halts progression.

I’m sure they will get right on this.

Still having the same problem…. what the heck Anet, why isn’t this fixed yet?