Showing Posts For Bivrington.5931:
I have at this point abandoned my Ranger for a new character. Think its pretty terrible for an ANet rep to tell us that they have a fix ready for it, yet they still have not put it in a patch. Starting to doubt ANet’s customer service commitment.
ANet, you guys really need to work on your new build timer. Its not very cool when I see “A new build is available, your client will restart in 55 minutes.” then immediately get kicked off and the new build is being downloaded.
If anyone has a problem with this quest I am in Harathi today in Tarnished coast if you are there and on that server or are willing to transfer to have help to keep all the skritt alive (which I pinpointed to have caused this bug when I did it and then got help to keep them alive).
As I said in my previous post it will block progress when one of them dies prematurely.
I’ll try this out today and see if this is a reproducible work-around.
I must say, I am very disappointed by the amount of time it is taking to get this fixed. I realize that small changes can have a big ripple effect, but the personal story is one of the main selling points of Guild Wars 2, and is advertised all over.
The fact that 1/3 of the player base may not be able to progress their personal story is a huge issue. Yes, I can continue to play and advance my character, but part of the fun in the personal story line is doing them for level appropriate rewards, and as a part of the story for the location it is in.
With all the content updates and patches being done toward the Mad King event, I find it hard to believe that this fix could not be added in. This fix is to make something that only happens in an instanced environment trigger properly. I find it hard to believe that this fix could have consequences and repercussions so large that it requires a large content update to implement.
Being told “we’ll fix it when we get around to it” does not sit well with me.