Guild Wars 2

Hi all,

My guild mates and I discovered last night that AC path 3 is still bugged, and it is a confirmed repeatable bug.

This post was made 7 months ago https://forum-en.gw2archive.eu/forum/support/bugs/Replicable-AC-Explorable-Event-Bugs.

We were running the dungeon with a person that was new to dungeons and trying to show them the ropes. We’d done this many, many times before without issue, so this seemed the smartest and safest way to ensure that this new person would have a good time.

However, after getting to the Lover’s Crypt, the game bugged as described before. Tzark was killed while giving his dialogue, rendering the dungeon broken.

Our greatest disappointment was that the new person was severely turned off by the bug to any dungeons, and my roommate, who is also an avid player, was greatly frustrated when he read that this bug is both repeatable and has been known for over a half of a year.

I’m an avowed fanboy, and I love this game, but I’d like to give the feedback that game breaking bugs need to be given much higher priority than things that do not affect the game such as clothing skins, etc.

(ed. I noticed that someone posted concerning a skin purchased with gems that was bugged with a tiny bit of a nose showing. The devs got right on that. That’s fine. I understand they have a microtransaction system where gem purchases are the life-line of the game. However, in the sticky-post up top concerning bug posts, the post spells out that game-breaking bugs are given priority. I’m sorry, but this seems a bit disingenuous when a 7 month-old bug doesn’t receive any feedback, but a purchase does within a little while.)

You do realize they aren’t going to get an artist(people for fixing stuff like skins) to go fix a dungeon bug right?

Yep, I do. The post was meant to be constructive criticism. Sure, there was a tad of a whine in there. However, it has been 7 months, the bug is easily repeatable, and we get no word yet. I’ll assume like the forum directions state that the dungeon team has seen this.

It’s just rather disappointing that given that they have seen this (and the previous post from 7 months ago linked above), they have elected to not prioritize a dungeon-breaking bug.

Maybe the patch today will fix this (after a seven month wait).

There is no longer any dungeon team. They folded up shop and rolled those guys into the living story team.

No excuse for bugs like this really.

Indeed, though, I’m wondering, with what Colin said a few days ago concerning the changing of a few dungeon mechanics that would be introduced through the Living World system, if this would render this bug moot anyway. This would explain why they haven’t even acknowledged it at all. However, if that weren’t the case, it’s just sad.