Guild Wars 2

The Wurm Demolitionist achievement had its requirements lowered from 30 to 5 but it did not seemingly count towards the achievement.

My achievement tracker shows 7/10 towards the Triple Trouble achievement but the new achievement says it does NOT count towards the Triple Trouble meta.

Yes, if you had more then 5 done but hadn’t finished the achievement, it finished automatically when you log in and DID NOT give you meta credit.

This makes it impossible to finish the meta if you got this bug.

Please fix.

Thanks for the response. I’m having the same issue with the meta achievement.

Yep me too, I found the 30 kegs somewhat horrifying and was pleased to see that they had dropped it to 5. ( finished that last achievement for me) That being said I should be done the Triple trouble and sadly am not.

Wow you guys responded to this problem fast! Mind checking this out Crystal?
https://forum-en.gw2archive.eu/forum/support/bugs/Fix-Minions/first#post3657286

I have the same problem, 15 from 30 before patch and now unpossible to make the meta

Same here, even after the patch. It says [Wurm Demolitionist] is unlocked, but it’s not counted for the meta.

The achievement is still bugged after the 2/19 patch.

Still bugged for me as well.

Here to report that today’s update did not fix this achievement. Still facing the same problem as yesterday.

http://imgur.com/gbrPaFV

Have the same issue, don’t know if today’s patch was supposed to correct this but it didn’t.

Even after the last bugfix patch of 19/02 the Achievement counter is still bugged. I had the chans to complete the rest of the wurm achievements yesterday but the Tripple Trouble achievement still says 9/10 which should now be 10/10.

hey hey look at this plz , i have 9/10 but i do it ! all achiv ! bug bug

Still bugged as of 2/20 hotfix.

Yup… still bugged even with today’s patch

Same here, done all achievements and still the progress of the meta is stuck at 9/10, even after killing wurm again last night.

2 Patches later and still no fix -yay!

Still bugged (stuck at 9/10)…. Has anyone tried dropping a new keg ?

In the lates hotfix patch notes it was noted, that i would be fixed, However i just logged in, and the achievement is still sitting at 9/10 although i have everything. So still not fixed as off 23/02/2014.
Edit: Sorry misread, they were unable to get it in hot fix build, so will be fixed soon i guess.

Like Snake, my progress is stuck at 9/10 even though it shows that I have “completed” all of the achievements. Eagerly awaiting a fix

I am bumping this, because I also am effected by the stuck 9/10 meta tracker with all achievements done.

I have submitted 2 support tickets over the past week, and Anet still has done nothing to fix it.

I guess the 100-200 players who are effected by this bug are not a priority over fixing the crappy, temporary LS content …

I am also stuck on 9/10 with all [including the new ach] finished. Crystal, can we also be guaranteed the 50 achievement points when this is fixed please [that’s assuming we got the ap’s for the keg ach … anyone placing bets on that?]

i have 9/10 but on this screenshot i have 10 achevement so yes this is bugged. may be coding with changing some achievements

i have 9/10 but on this screenshot i have 11 achevement complete. any news? when they will fix it?

Still not fixed …

Funny thing, I wrote the support about that (got 11 but only 9 counted) and they redirected me to a GM which wrote me in email “This has been fixed”… It obviously hasn’t. Sent them some screens now. And such an answer took them several days. Oh well.

FreshM.6729:

Funny thing, I wrote the support about that (got 11 but only 9 counted) and they redirected me to a GM which wrote me in email “This has been fixed”… It obviously hasn’t. Sent them some screens now. And such an answer took them several days. Oh well.

Both myself and my husband have sent many tickets/mails in about this issue and the other wurm bug resulting in no credit for achievements for wurm head kills (there is a thread for that one too- made on this forum a month ago) and the responses we both got have left much to be desired. I gave up on tickets, it’s like banging my head against a wall. I don’t even think more than one, my final one, after a survey was sent in, got read.

I’d love to try the new content when it comes out, but I don’t wanna be a bug tester, and for something that takes as much time and effort as this encounter does, I’d hope if fixes are ready, we could get them, and if we can’t get them, we can at least get some updates so we can understand why.

I just popped my first wurm kill today, and can confirm this is still bugged as of right now.

Still bugged.

Bugged aswell. Had 23/30 kegs placed before it got toned down to 5 and autocompleted, so that should be really the point to look into. Lookin forward for a fix, thanks in advance

my wurmslayer reset to 0. now i have 8/10 again… :s

FreshM.6729:

Funny thing, I wrote the support about that (got 11 but only 9 counted) and they redirected me to a GM which wrote me in email “This has been fixed”… It obviously hasn’t. Sent them some screens now. And such an answer took them several days. Oh well.

It HAS been fixed. Read the anet post above yours a bit. The fix is likely to be out Tuesday. Seems kinda pointless to put out a hotfix that only addresses a single issue when a few days/week later the next major content update is being released. Plus if you’re waiting on retroactive validation, not like you’re waiting for it to be reset to 0.

Edit: Wurmicidal Maniac does not count towards the meta like the description says.

Aidan Savage.2078:

It HAS been fixed. Read the anet post above yours a bit. The fix is likely to be out Tuesday. Seems kinda pointless to put out a hotfix that only addresses a single issue when a few days/week later the next major content update is being released. Plus if you’re waiting on retroactive validation, not like you’re waiting for it to be reset to 0.

Edit: Wurmicidal Maniac does not count towards the meta like the description says.

I think people understand that, once they see this post in this thread. It’s been fixed internally but the fix has not been applied live yet, and that’s what players don’t know, and really, if you’re writing to support, that’s the answer that matters. It can’t be that hard to simply state the fix is ready, just awaiting a patch deployment. Since the search function on the forums is wonky, it can be hard to find the info if you don’t know your way about or where to look. Look at all the people looking for info on the Teq bug.

Wurmicidal Maniac agreed, doesn’t count, but it shouldn’t reset either.

I’m not talking about wurmicidal maniac but wurmslayer in which you need to kill all 3 heads. I’ve killed them a long time ago and now is back to 0.

Underdark.3726:

I’m not talking about wurmicidal maniac but wurmslayer in which you need to kill all 3 heads. I’ve killed them a long time ago and now is back to 0.

Gah, I’m sorry, Underdark. I misread what you wrote, too (through no fault of your yours!), but I get what you’re saying. That’s not good, either. That one does indeed count.

For those confused about what people are talking about having 8 of 10 or 9 of 10, we know that the newest one doesn’t count. What is bugged is that the kegs, which previously took, I think 30, now only takes 5, and for most people, that would complete Triple Trouble. Problem is, it was completed with the change in number, but not the actual count toward the achievement, and since it is “finished”, we have no way ever finishing it (because as pointed out, the new achievement, Wurmicidal Maniac, does NOT count towards the 10 achievements needed for the Triple Trouble achievement, and that is clearly stated), until it is patched.

Triple Trouble (title giver)
Wurm Scrambler
Phytotoxin Enthusiast
Wurm Handler
Wurm Barf
Wurm Decapitator
Wurm Bait
Wurm Kleptomaniac
Wurm Demolitionist (this is the issue)
Wurm Slayer

I just hope somebody is reading this

New content patch… no fix. /sadface

It’s STILL not fixed with the patch…

Crystal Reid.2481:

The code changes were too risky to get checked in and tested properly for the build today. They will go live with the next release build (Note: An actual release build, not a hot fix).

We appreciate an update on this issue, as it’s better than silence, but ‘ll be honest, I’d really hoped at least one of the achievement bugs involving this encounter was finally going to be addressed and fixed. I know the one I, and numerous other players reported over a month ago, still hasn’t been. The good thing about that one is, it won’t hinder you from getting the achievement. You may have to work more than you’d originally planned to (or should be required to), but it can be done.

This one though, the player can do nothing about. If you’d happened to be one of the people that were assigned to a necro team on Cobalt before the change in count, you were gonna take awhile to get those 30 barrels, because running them wasn’t your job, unless you were asked to do so. Achievement Barrel Runners drove the raid leaders insane, I heard the poor people on TS literally imploring people to stop with the barrels and go after the other stuff, or why did people from Amber or Crimson go to Cobalt. The people that didn’t flip out over that 30 barrel count and did what they were asked to do, or were just able to start doing the content when the change was implemented can’t finish their achievement no matter what they do. It is out of their hands.

I know there will be people who say, “it’s just an achievement, it’s just a title” and sure, to a degree, they’d have a point. It’s also just a game. But it’s my time, and I do try to help support the game, even if only in minis or armor skins and character customizations, bank space and stuff like that. Achievements are a large part of the Guild Wars 2 experience, and it’s disappointing when they’re broken. More-so when it’s our new “end-game” content related stuff. We put our time into this stuff, and our time has value, if even only to us.

I don’t proclaim to be a designer, coder, programmer, etc. I’m just a player, a customer. I totally get that things can’t be fixed overnight, and that content should be tested before it goes live. It’s disappointing that this occurred and hopefully it’s fixed in a few weeks. At least until then, people won’t be crossing their fingers for a hotfix.

Thanks Crystal for letting us know why it still is bugged, looking forward to upcoming patches, this one is awesome:)

Maybe I’m confused here, but the way I read your response from Feb. 21 lead me to believe that a fix was in fact worked out, but could just not be implemented into a hotfix because it required code changes. So, today we got an actual content update, not just a hotfix, in which the fix could have/should have been implemented. Instead we are now told that the code changes were too risky to get checked in and tested. My confusion then is that I was under the impression the “bug” was fixed but required an actual content update to get it published. When I hear something is fixed I would assume that to mean the fix was already tested. But, the reason for it not being implemented is because it has not been tested? If I am wrong in my understanding please feel free to recalibrate my logic.

Nicca.3057:

But, the reason for it not being implemented is because it has not been tested? If I am wrong in my understanding please feel free to recalibrate my logic.

Crytal Reid stated that “the code changes were too risky to get checked in and tested properly” which means that the fix has already been implemented (most likely “locally” in a programmers development environment), but it has not been integrated in the code of the live production servers (“checked in” for the new build of today) since it has not been tested thoroughly.

Changes to a software system always bear the risk of creating unforeseen problems in other (and seemingly unrelated) components of the system. Hence, if ANet didn’t have the time to test the fix properly, then they are doing the right thing in pushing the changes back to the next release build.

~MRA

Gaile Gray.6029:

MRA.4758:

Nicca.3057:

But, the reason for it not being implemented is because it has not been tested? If I am wrong in my understanding please feel free to recalibrate my logic.

Crytal Reid stated that “the code changes were too risky to get checked in and tested properly” which means that the fix has already been implemented (most likely “locally” in a programmers development environment), but it has not been integrated in the code of the live production servers (“checked in” for the new build of today) since it has not been tested thoroughly.

Changes to a software system always bear the risk of creating unforeseen problems in other (and seemingly unrelated) components of the system. Hence, if ANet didn’t have the time to test the fix properly, then they are doing the right thing in pushing the changes back to the next release build.

~MRA

Thank you for understanding and for explaining this so clearly. This is an issue that the team actively is working on, but as Crystal explained, it will be fully addressed in a future build. We thank you for your patience while the best possible resolution is developed, tested, and then implemented into the game.

I genuinely appreciate the clarification MRA.

The point I am trying to get across here is that the responses we have been getting as a community of users are not adequate. I have been made to understand that this fix is complete and ready to publish. While the “fix” may be completed, since it is not tested it can hardly be considered a fix. A proposed fix perhaps, but as you said, unforeseen consequences may arise.

At some point, an honest straightforward answer to a legitimate question or concern would be appreciated. I have to answer similar questions and deal with these concerns on a daily basis. I personally do not say something is “ready” or “fixed” unless I am 100% sure and prepared to show it to be so.

I have no issues with allowing the team to take all the time they need to ensure this and any other matter is being handled and corrected properly, but that needs to be communicated more effectively.

Hopefully this will be resolved with the next build as Crystal has stated.

So another 2 weeks, at least. Right? In a game where items like legendaries and fractal weapons and Tequatl Hoard weapons and titles like Wurm Slayer are pretty much the only “bragging rights” you can get, a bugged meta for the rare end game content is not fixed until, like, half the player population gets it? I can see why it has no priority for Anet but I guess I’m not the only one who’s at least slightly disappointed.

Also, don’t worry about introducing new bugs with badly tested changes. I’ve spent a long night trying to get access to Scarlet’s drill but except the very first time, every time we got 3 knights down, we couldn’t get the buff needed to use the teleporter. And half of the times the blues knight just reset to full health mid fight. So much for testing.

I find these ‘red’ posts from Anet quite disturbing, because I do not believe anything they have posted in this thread.

If this was a bugged meta tracker for the LS content, it would be fixed within hours and released as a hotfix, regardless of whatever code changes needed to be made.

Testing is a straw-man excuse, because either very little testing goes on, or, it is the wrong type of testing. If Anet properly tested before releasing, the Wurm meta tracker would not have broken in the first place. Yet, here we are, and still no fix in sight.

The only conclusion I can make is this: The Wurm meta tracker effects too few players and Anet is too busy releasing buggy, crappy LS content and gem shop items to bother with something like this.

Oh, and please stop thanking me for my patience because I have none left.
That ran out over a year ago while playing a ranger!

I think I speak for many when I say it is frustrating that all the new content targets one or 2 servers. To get the worm achievement you had to either guest to Black gate or Tarnished Coast. To do the new LA events you need to guest to those 2 servers as well. So that being said how about you just get rid of all the other servers hmm? Then you will have plenty of time to address the achievements.

I love the graphics, and most of the game content. All the amazing little details rock. But please, STHAP releasing content that only 2 servers can manage and the rest of us cant. Most players don’t have the time to find a server to guest to just to play new content. Not to mention that require a voice server to coordinate the effort just to succeed.