Guild Wars 2

It’s simple Anet. The only way to get the Ancient Stone Summit Shoulder Spike for the Treasure Hunter achievement is to have the event Protect Krewe Leader Dobbs finish successfully. However the quest is bugged and has been bugged for over a year. After searching through the forums there is evidence of this since March 2013. Maybe the quest was fixed temporarily, but this sort of problem has happened again.

Last night, I waited at Dobbs for over an hour thinking that this event would fire at some moment. Myself and about 5-6 others were in the same boat. Wanting that SSSS for the TH achievement. There may have been others, because plenty of other players came zipping through the spot several times. After awhile I went back to the wiki and then read the bottom notes section and that’s when I realized it’s been bugged since Oct. I then went to the forums and then found the history for this bug.

I know about programming and bugs. I know that it’s not possible to squash them all, and it’s not possible to fix them quickly. Shouldn’t this one though, be somewhat of a high priority? I know that the accepted work around is to wait for a patch or for a new map to spawn, but this has been the case for over a month. I also realize that this is not the only item collection bugged and I have to wonder why they’re still broken after being implemented since the feature patch.

Why put something in and then leave it broken? Is it really that hard of a fix or do you have other priorities right now that you can’t divert resources to fixing it. So why then why remain mute on the subject when everyone knows this one and others regarding item collection bugs are still broken? Is it disdain for us, the players?

I’d ask you to fix this, but I would have to believe that you are more than aware of this problem. I’ll keep checking back and hopefully I’ll get lucky. I still have to ask though, I know you have a tight-lip policy regarding this game, but do you try to fix bugs in a timely and quick manner, or are they put in a “pile” to be dealt with when there is time? I mean in some regards, you’ve been able to fix popular dynamic event “bugs” seemingly overnight when they were considered exploits, why not this one, then?

Short answer: Because Living Story takes up all their resources. (apparently)

More in depth answer:

If gw2 has a bug that is not a deal breaker or serious exploit or game breaker and it is not effecting the Majority (this is a key word btw) of its players. That bug goes on a pile of things to do some day when we maybe have some time to work on them.

The word “Soon” gets thrown around a lot with it’s meaning stretching somewhere between a few days to over 2 years.

A lot of players don’t care about the collections, the rewards for the effort and time are laughable and Anet knows that, this isn’t a majority issue and is thus going to end up on the pile of “Soon to be looked at, it’s not off the table, when we get time and resources” bugs..

Let’s remember that the old haunted house in Iron Marches and its event were broken for 2 years until LS came through and required it to start working….

If I had this sort of work ethic at my job I would have been fired years ago.

I know that the equivalent here would be: “Well, just stop playing the game, moron!”, but I don’t get it. If you work hard and devote a lot of time to making something, why then make it available to the public as anything less than the best representative of your work?

Maybe I’m comparing apples to oranges here, but if the product I turned out was regularly flawed and not working as advertised than there would not be much of future for me or the company I worked for. I’ll never understand why executives and supervisors consider this acceptable. It goes a long way to eroding trust and optimism in the player community which seems to be their life’s blood. Don’t they take pride in their work?

Well, about 3 month passed by since the first complain and the knowledge of this bug.
As there is no other way to finish the collections “Treasure Hunter” and “Brewmaster”, it would be very kind of ANet to fix this Event in the near future.

It’s a recurring issue, it gets fixed every time there’s an update, then gradually breaks over time.