Guild Wars 2

During our 2nd completion of the Triple Trouble Wurm event, we encountered a bug that I have not seen before. The entire phase 1 of the event went perfect. So perfect that we decapitated all three heads at the same time. Instead of clearing the first timer and succeeding the event by moving to phase 2, it kept the first timer for the decapitate window (the 60 second timer) and placed the head kill timer (the 2 minute timer) in the event window as well. The first timer (the decapitate window) continued to time out to 0 and flagged the entire event as failed. Edit: I’m being corrected. We decapitated all three heads before the original timer reached 0 (hearing 14s left on the original timer) and it only popped the 60s window timer while still counting the original timer down.

Edit: Would like to mention that the heads did pop out of the ground as per normal for the phase 2 portion of the event.

Note: It seems very strange to prioritize the event fail in an event such as this.

When he says “decapitated all three heads at the same time”, he means literally within 1 second of eachother, if not less. Basically. . . We did phase 1 so perfect, the game couldn’t handle the perfectness. YEAH [Att]!

:)

Not to mention all three heads spawned to be killed when the timers dropped. Each group stated that they saw and targeted the heads when they appeared before the event failed after the timers bugged out.

None of the heads were killed by conditions when invulnerable, to be clear. We just had them killed in such a way that there was no chance for the timer to go back to 1 minute. Likely when a wurm went to set the time to 1 minute, it checked to see if the others were killed. It didn’t register them as killed, but it did see that their hp was 0, so that caused the fail state to trigger.

In addition to the above, all worms were dead w/ ~14 seconds left in the timer, but that timer continued to tick down even though the 2 minutes head kill timer had showed up. The 2 minute timer did not start to tick down. It just sat there like it was waiting for something. When the original timer ticked the rest of the way down from 14 secs, the event failed.