Guild Wars 2

Tonight I ran this path and ran into a situation where we wiped in the “protect detha and her traps” event, and ran back to a group of 8-10 ghosts camping Detha’s corpse. It looked like Detha somehow ran to the third trap (we wiped while she was building the second trap) and triggered the third wave of ghosts which includes Monks. The group was a perfect storm of Monks, Rangers, Necros, Eles, and Warriors. We gave up on it after 2-3 more wipes—this was a surprising outcome because we are all very familiar with that path.

I don’t know if it’s related to the patch, but the patch does “adjust” the spawn rates of this event. On the other hand, my friends say they have run into this situation before, though perhaps not to this extent.

Can we please get more details about what was changed? Are large groups like the one we gave up on the intended experience?

You ressed Detha triggering another pack of ghost to spawn. That is why you ALWAYS kill everything before bringing her up if you wipe.

I don’t think he said anything about resing Detha. Honestly, I’ve seen this happen a couple times and it had nothing to do with Detha dieing, in fact she was alive when it happened. If she runs to the third trap before the second one is cleared, she spawns more mobs. She can run to the third trap as soon as the second one is finished, even if the party is still fighting (and eventually wiping).

When I read the patch notes I thought this was fixed, apparently not.

DancingPenguins.9875:

You ressed Detha triggering another pack of ghost to spawn. That is why you ALWAYS kill everything before bringing her up if you wipe.

We did not revive Detha—all 5 of us went down simultaneously.

Sequence of events:
1. Party wipe during the building of second trap
2. Party revives at Foefire’s Heart and runs back.
3. Detha is dead at the third trap as described above.

Shiren.9532:

I don’t think he said anything about resing Detha. Honestly, I’ve seen this happen a couple times and it had nothing to do with Detha dieing, in fact she was alive when it happened. If she runs to the third trap before the second one is cleared, she spawns more mobs. She can run to the third trap as soon as the second one is finished, even if the party is still fighting (and eventually wiping).

When I read the patch notes I thought this was fixed, apparently not.

This makes a lot of sense. I have often noticed that dungeon NPC allies do not get any aggro unless the party is in combat, but I’m not entirely sure how that works. It’s possible that when we wiped and broke combat she was still alive and finished the second trap successfully. Then she would have walked off and started the third trap, spawning the third wave of enemies which killed her because she was the only target available.

This bug (double wave spawns) happened before, but from the patch description I assumed it had been fixed. Looks like it hasn’t.

When it happens, the easiest ways to deal with it is pull the ghosts to the top of the stairs (where the oozes spawn). Some will reset or freeze half way through, and you can kill them easily in groups of 1-3.

This has to do with a flaw (imo) with how NPC followers work. The issue is that when you wipe on the ghost waves and waypoint to Kholer’s spot you are too far away from Detha’s corpse so her AI tells her to res herself and rush over to you. The problem seems to be that she prioritizes building the cannon over running back to you so she begins building while you are running back, triggering a new wave and putting you in a world of pain depending on how early in the previous wave you wiped.

The best solution I’ve found and that I always use in my guild groups when this happens is that 1 or more corpses must remain in the hall (perferably the closest to Detha) and the others res up and run back. Once the other members are in the room they can either res the others or they can waypoint back and rejoin the group in the hall. This almost always prevents Detha from getting up and messing up your run. Hope this helps.

Now that it’s business hours on the west coast, it looks like we have an answer. Thanks very much for sharing your workarounds!