Guild Wars 2

Thing is I maxed out my tradeskills to do that, and that’s not something I can repeat easily.

Stopped playing 3 months ago during this bug when a 2nd bug pushed me over the edge and I figured to take a break until they clean things up a bit. At least this one eventually got fixed.

I was doing it in one session and there was a mandatory update with only a 3 minute warning, without which it would have been completed.

I haven’t played in 3 months because I don’t want to die until this issue is fixed for me as I won’t be able to recreate it easily. Shortly after a fix went in for the Achievement “Lifetime Survivor” I gained 391,160/500,000 exp maxing out my tradeskills, and then there was a mandatory update with only a 3 minute warning.
I STILL have not died since this happened, but after the update my progress was no longer updating, as if I had died. As I haven’t died since I gained this 391,160 exp please set my achievement so it continues progressing or just give me the achievement so I can start playing the game again.

I polished off my leatherworking to 400 and was up to 390,000 of 500,000.

Then there was an emergency patch with a 3 minute warning.

I still haven’t died, but when I was able to log back in, my progress towards the achievement just stopped.

It’s a bit frustrating as the last points of a tradeskill are the most expensive and useful to get this achievement, and now my leatherworking is wasted.

Kaltern.9586 it’s not that. It’s that they regularly edit delete modify merge posts and threads in a fashion to change the appearance of how this has been handled. For instance, this thread originally had no moderator replies for the first 3 pages, now that’s been changed.

Others are upset because we were told it was going in on Nov 5., but that post has been edited. Ect.

Esmerine.9465, the sticky issue, # of replies, ect all has to do with the incorrectly assigned Severity because when you have this many end users this upset about a lower severity defect, you need to revise your models.

Esmerine.9465:

What would sticky get us? I don’t think it’s appropriate or useful here:

• This thread is not useful to all players; it applies only to a subset of players (however important the issue is to us).

That’s sort of my point. Anet has not assigned this defect the correct Severity due to that thinking.

I’ve worked in software development for almost 20 years. First as a developer, then QA, project management and finally as department director, and I think I have a pretty good idea what happened.

This defect was not given a high enough severity due to it not affecting ALL players. Severity is different from Priority and severity always has criteria that determines it’s level; ex. a critical defect may cause the application to go down or be unusable, High has major impact, while a low severity has a more limited impact to end users.

The mistake that the development team made here is not recognizing the impact this defect has to the playability and perceived end user service of their application.

This defect did not affect ALL players, but it effected many. And for the ones it effected, it had a Very HIGH severity impact to their gaming experience. That’s why it should have been assigned a higher severity and why it warranted a patch of it’s own.

Between this and the locked thread, this topic now has 750 replies (more than any stickied post) and 24,000 views, and hundreds of unique posters.

Yet it’s still not a sticky. Can we ask why please?

Thanks but no thanks.

Most of the people effected by this bug don’t need it fixed anymore. It has taken so long that we’ve already hit 80.

It’s not like we’re going to go back and run through all the zones again.

Guild Wars 2 effectively has no story for us. Might as well have left it out and spent more time coding other aspects of the game.

Jeffrey Vaughn.1793:

It’s not a matter of priorities, it’s just bad timing, really. A general audio fix went in about 2 hours before the bug was reported here and I fixed it, and unfortunately, the audio fix left the story step incompatible with Live. In the upcoming update they’ll be adding the audio fix, so the fixed story step will also go in.

When was that? Was that the 9/9 patch that affected The Hatchery?
“The Hatchery” You can no longer do the final step before doing the intermediate steps.

Has this actually been broken for 2 months?

I hit 80 tonight. This bug existed before I bought the game. The game was a bit bland without a storyline.

Jeffrey Vaughn.1793:

I apologize if my reply seemed curt, but I’m trying to funnel people towards one thread so I don’t have to spend all day updating multiple threads with info.

Stickying this thread may help reducing duplicate threads.

And afterall between the locked thread and this thread we do now have over 600 replies and 18,000 views. With hundreds of unique posters.

Imaginos.3756:

Ryan.2356:

Please hear me out, I have a genuine question here.

Regarding the Hatchery Bug thread with 291 replies and 9,560 views, which has been locked: https://forum-en.gw2archive.eu/forum/support/bugs/The-hatchery-bugged/page/6

Hundreds if not thousands of players are still stuck unable to play the game as intended while we wait for a fix.

It’s important for players in this situation to have a venue to vent their frustration while we wait for a fix. If the Game Bugs forum is not the appropriate place for this, where should our thread be so we can continue to talk about this until it’s been fixed?

Thanks for listening,
Ryan.2356

I find it discouraging, disheartening and disgusting that I have to go and check the wiki to find out if a quest that I am going to take is bugged and I should avoid it instead so that I’m not stuck waiting for months before I can continue to progress my character.

I am now suffering from this bug just like everyone else as I did not check the wiki beforehand.

Is there an eta on getting this fixed for everyone so that the thousands of players stuck in this mission can continue along our personal story and actually finish the game?

Thank You.

Thanks for the reply Imaginos.3756. Btw they didn’t even update the Wiki. I did.

New Patch! Somebody check it?

Between the Locked thread and this thread, this topic now has over 500 replies and 14,000 views.

With hundreds of unique posters.

Your community is telling you that this IS your biggest and highest priority defect.

Somebody needs to run this up the chain and get it prioritized.

Ryan

Now they edited the topic of my thread? I mean, why?
It was “The Outstanding Hatchery Thread” which was so titled due to the first thread being locked while the bug is still outstanding.

Guys. Set yourself to Online via the Friends menu and relog.

It fixes the bug.

Setting yourself to Online via Friends menu and relogging works.

See this is what happens when you rush in a patch to fix droprates for dyes …

Instead of prioritizing and appropriately addressing game breaking main storyline bugs like:
https://forum-en.gw2archive.eu/forum/support/bugs/The-outstanding-Hatchery-Bug/first

Nov 6 in the US est now too.

That was the Nov 5 content patch. Reducing the drop rate of dyes ..

The game breaking main storyline bug fix got bumped.

Loptimist.1832:

Nov 6th, still bugged, didn’t they say it will be patched on Nov 5th……

Yes, but later edited that post.

Between the Locked thread and this thread, this topic now has over 400 replies and 11,000 views.

With hundreds of unique posters.

Your community is telling you that this IS your biggest and highest priority defect.

Somebody needs to run this up the chain and get it prioritized.

Ryan

This is likely just because they force everybody to patch and thus everybody to try to relog back into the game, at the same time.

New patch! Somebody check it?

Haven’t logged in for a few days. Any updates?

Well idk. I already paid $80 for this game. I might be willing to put up another $5 if it meant them hiring a developer to make it work.

It’s missing a prioritization of Bug fixes.

Peoples’ main storyline has been broken for going on a month now.

https://forum-en.gw2archive.eu/forum/support/bugs/The-hatchery-bugged/page/6#post614279

Where is the fix for The Hatchery? LOTS of people have had their main storyline broken for going on a month now.

This bug existed before I bought the game. Now I’m 65 and still can’t play my storyline.

https://forum-en.gw2archive.eu/forum/support/bugs/The-hatchery-bugged/page/6#post614279

What zone comes after Sparkfly Fen?

I don’t know because my storyline is broken …

New patch, somebody check it?

So much for this being a priority.

New patch, somebody check it?

This bug existed before I bought the game.

I’m now level 51 and my storyline is stuck, unable to proceed because nothing been done to fix it or to disable it or to warn us about not choosing this path.

I myself updated the wiki to at least notify other players that this chain is bugged.

Can we get an expedited patch here? Lots of people are sitting around twiddling their thumbs getting very frustrated with this game.

Bump. I’m stuck on this now as well.

Bump. I’m stuck on this now as well.

Bump. I’m stuck on this now as well.

Please hear me out, I have a genuine question here.

Regarding the Hatchery Bug thread with 291 replies and 9,560 views, which has been locked: https://forum-en.gw2archive.eu/forum/support/bugs/The-hatchery-bugged/page/6

Hundreds if not thousands of players are still stuck unable to play the game as intended while we wait for a fix.

It’s important for players in this situation to have a venue to vent their frustration while we wait for a fix. If the Game Bugs forum is not the appropriate place for this, where should our thread be so we can continue to talk about this until it’s been fixed?

Thanks for listening,
Ryan.2356

I got in.
char15

It’s just because everybody is trying to log back in at the same time after we all downloaded the patch at the same time.

Done. 700mb, and the patching % is based off number of files, not size …

XPTO.6275:

ok. @2mb per sec now, patch seems big.

but don’t worry, no content was changed… just routine maintenance.

Yes, perhaps giving us a 3 minute warning and kicking everybody to patch at the same time wasn’t a good idea.