Guild Wars 2

So, here it goes:

The past two days, I have run AC (path 2, specifically) 4 times. Every time, Detha has bugged out forcing us to start over or move on. Three out of the four times she bugged out at the Ghost Eater and the other time she bugged out by the spike traps. Each time, she fails to start the event (i.e. no cut-scene, so no event starts).

We’ve tried getting her killed (resurrecting and having her rubber-band), doing every pre-event that pops up (Kholer, graveling burrow, etc), killing all of the oozes in front of the Ghost Eater room (one time, we even went back and tried to kill every enemy on the map), etc. I have tried everything. I have no idea what the issue is, but it’s really annoying and also dis-heartening when my group runs path 1 with no problems, moves on to path two just to have it bug for us twice in a row.

Are there any solutions that you have found? And any developers out there, do you know what causes Detha to bug out and when can we expect a fix? I understand that there probably is no way we could ever be compensated with Tears for these bugged runs, so it’s just getting to me that these issues first popped up over a month ago (if I remember correctly) and we still haven’t seen a fix. In fact, it seems to me that it’s becoming more and more buggy.

I keep reading about Detha bugs, on the gravelings or on those oozes that pop up right before the final room, but never experienced it myself. Almost every run I’ve done path 2 it’s the standard party debate over whether you kill kohler or not, and then run the rest of the way to the graveling/chain traps part. I’ve found that the npc usually follows one specific party member, usually the party leader, so perhaps the party leader is not getting to the right part of the room to trigger next cutscene??? I know that’s a “duh” answer, but something it’s the right one.

I know this problem was brought up in a previous thread and a dev has actually responded (rarer on the forums than I would like, but I’m sure they’re too busy to answer everyone). I’d search around the forums for other detha bug threads, I can’t remember where the thread I read was, but if I find it I’ll link it. They did say they were working on it though.

here’s the thread i mentioned

https://forum-en.gw2archive.eu/forum/game/dungeons/Why-is-AC-more-broken-than-ever/first#post1034797

Ah, thanks for the link. I’ll take a look. Yeah, what happens when she’s bugged out is she will start to follow anyone around (not just the party leader) if you “f” talk to her.

Just ran it once again. Same thing happened again (for the 5th time in a row) in the Ghost Eater room. Think this has anything to do with my specific character?

Does the ghost appear at all? (the one that Detha talks to)

One solution is to drag one of the gravelings from the room outside into the room and let it kill Detha. After reviving Detha, path 2 should progress as normal.

Each time it happened, we had her killed by one of the Gravelings. It didn’t reset it any of the times. And, no the Ghost she talks to doesn’t appear. It seems like she is “not getting in position” to talk to the ghost. She will basically just follow whoever last talked to her around the room for forever.

I ran it again last night to try my luck and it finally worked (we skipped Kholer and the Ooze outside the gate), so I have no idea what was bugging it at this point.

Sylvanwood.2746:

One solution is to drag one of the gravelings from the room outside into the room and let it kill Detha. After reviving Detha, path 2 should progress as normal.

Unfortunately, this does not always work.

And, um (making fun of the folks who say “just kill all the mobs, you lazy kittens!”), if you actually kill all the gravelings and jellies before bringing Detha into that room, you have nothing you can drag to her to even attempt this workaround.

Hmm. Chicken or Egg? Robert, are you reading this? How about a different fix than the one you’re mulling over, which is to simply lock the door to the turret room until after the oozes are all killed. What if you do that and we still run into this extremely common bug?