Guild Wars 2

We killed all 3 heads in P1, even got a gold chest. But instead of giving us another 1min it bugged and just failed. Think that this might be related to the old bug of condition bugging heads in P1? Not sure yet, first time we’ve seen this happen.

During a TxS run the same happened to us ^^.We sent a bug report and the answers was : We are lookin in to it Yada yada ..

Good to know Alugjen. We think we know why the bug happens now but also sent in bug reports.

We had a dev with us on our run, and they logged it when it occurred.

To clarify, it’s how they fixed the “invulnerable head not despawning at the end of the event” bug. Previously, if you brought a head to 0% HP with condition damage after the wurm gained the Slick Skin debuff, the game would stop the wurm from dying by placing it at 0.01%. But because game mechanics and event mechanics conflicted, the wurm was considered "dead, but not dead to the event because of the way Slick Skin worked, and became detached from the event. So after the event failed, the supposed-to-be-dead-but-not wurm would not set to the fail condition because it had become detached from the event. Ergo the bug where you would have the head up and mobs constantly spawning.

They fixed this by reattaching the wurm head to the event. So now both the game and the event register the wurm as “dead”, even when it’s clearly not, and then proceeds to “kill” the wurm, resulting in an update to the event tracker saying that the particular wurm in question was dead and ready for phase 2… but the event was “failed”. This resulted in the fact that you would get the rewards for killing three heads, but still not move on to phase 2.

Another point is about the timer. On our [Att] run when it happened, people got confused and thought that timer that expired and didn’t credit the 60 second window for the event. It did, because the other two wurms had already burned to 0% and the window timer was the actual one that expired (I had to rewatch the video just to make sure of this, myself).

So the bug is actually a fix. Just not the kind of fix we were expecting. I would assume it to merely be a bandaid until the event can be tuned proper.

I hope this explains things.