Guild Wars 2

Blude.6812:

Ark Bladesteele.2943:

Blude.6812:

Don’t care how they fix, but they need to.
Nerf it would be one way, but I would prefer that the event is changed so wurm is immune to feedback skill and all damage is reflected back at mes that initiated the feedback.
BTW, I do firmly believe that mesmers use it solely to grief others during the wurm event. kitten trolls think it’s funny to stop others from getting rewards.

Why should it damage the mesmer? That makes no sense. Just make it so the wurm can’t one-shot itself by getting hit with feedback from its own attacks. It’s just that simple.

I threw that in just to see the response. Way too many (I know—not all) are using it now JUST to grief the event.
It would only kill the mes that used feedback during the event, so if you didn’t use it during the event—you have noting to worry about.

Ok, pick a side. You either:

a) Just threw that in there to see the response (which is really trollish), or
b) Actually want them to make a change so that any mesmer that uses Feedback against the wurm dies.

If they’re going to make any change, make it so that Feedback functions against the wurm the way it previously did. Why make it so a whole class of players dies if they try to use a viable skill just because a few griefers exploited it when it was bugged against one single enemy in the game?

Blude.6812:

Don’t care how they fix, but they need to.
Nerf it would be one way, but I would prefer that the event is changed so wurm is immune to feedback skill and all damage is reflected back at mes that initiated the feedback.
BTW, I do firmly believe that mesmers use it solely to grief others during the wurm event. kitten trolls think it’s funny to stop others from getting rewards.

Why should it damage the mesmer? That makes no sense. Just make it so the wurm can’t one-shot itself by getting hit with feedback from its own attacks. It’s just that simple.

Reborn.2934:

Realist.5812:

Bug still occurs with warrior burst skills.

If you weapon switch too fast after hitting burst, character CANNOT ATTACK AT ALL for 2-3 seconds.

Main reason for switching out of burst is after Flurry (sword), switching too fast results in being locked out of attacking.

no it is not exist anymore . i burst a lot of times just now and i switched to other weapon with no problem and i continued to attack

Who the hell are you? You have spent an awful lot of time posting that bugs are fixed when they are not, indeed, fixed.

Reborn.2934:

Realist.5812:

Still broken.

Core elements of the game are still broken.

Gem store still receives constant updates. Bugs affecting the core of the game are ignored. Slow clap.

no it is not still broken . it is fixed . i just tested it .

seems ,someone necro a lot of old bugs !

It’s not fixed, and I find it odd that you have gone to the trouble of posting that it is in every thread where it has been brought up. You also offer no insight into where you say it’s “fixed.” Here’s a challenge for you:

1) Use Rush on an ice crystal during the Jormag pre. Make sure it’s targeted.
2) On the Champion Rotting Oakheart in Queensdale.
3) The Great Jungle Wurm (sometimes this does actually work, oddly)
4) Any moving target that is greater than 500 units in front of you.
5) Try to traverse any destructible terrain. Bridges in Edge of the Mists are a great example.
6) Try it on a target behind a wall or other obstacle where it is not possible for Rush to reach it.

Post your results. Include screenshots or preferably videos. I’d love to see the evidence of this “fix.”

Dan Daze.9854:

Hey guys, I (Dazed, the creator of the spreadsheet) submitted a post in the bug forums regarding this exact issue:
https://forum-en.gw2archive.eu/forum/support/bugs/Fractal-drops-were-broken-on-the-3-18-patch/first

Please have a look and show your support.

I myself have stopped playing due to there not being any difficult/rewarding content and the way Anet has handled this issue, they really dont seem to care about anything but LS/Gem store items.

I submitted a ticket a while back about the drop-rates, got one response from player support saying he would forward the issue on to one of the devs followed by multiple copy pasta responses:

“Hello Daniel,

Thank you for contacting us once more regarding the issue you were experiencing.

I understand that it can be frustrating not to see immediate results based on your in-game or forum report. Keep in mind that even if we are able to verify a bug report, it can take time to fully kitten the issue, develop a means to amend it, and then implement that “bug fix” into the game. The exact amount of time can vary widely based on the severity and complexity of each issue.

It is important to remember that in-game bug reports go directly to our Quality Assurance Team for investigation. Such reports provide information that allows the team to verify and reproduce the issue. In addition, the team regularly reviews the Game Bugs sub-forum of the Guild Wars 2 Forums ( http://support.guildwars2.com/forum/support/bugs ) for bug reports, as well.

If you have any other questions, please feel free to contact us."

It kills me that GW2 was designed to be such a wonderful game, but at some point, the devs simply stopped giving a flying kitten about anyone but casual players. I’ll be moving on to bigger/better things. If/When they decide to produce/support interesting content I’ll start playing again.

Hope to be seeing Tyria again soon…

That ticket response is the stock copy/paste response to nearly all tickets. I have seen people re-post this over and over, and I myself have gotten that response to 2 completely separate tickets, one regarding world completion and one regarding the 4/15 patch daily reset bug.

It’s a quick way for them to pass the buck by not actually addressing your concerns, since there haven’t been many dev posts in the bug forums even acknowledging that a certain issue exists, and there is zero way of knowing if your ingame /bug report actually did anything. It’s convenient, and tables any of their responsibility to deal with your ticket in any real or helpful manner.

Also, I am torn between laughing and crying at being able to literally see the air quotes around “bug fix” there.

Sigh.

What the… I swore I posted a response to this but it ended up in another thread? And as an A: to someone’s Q: ? Oooookaaaay.

https://forum-en.gw2archive.eu/forum/support/bugs/When-will-Rush-be-fixed/first#post4012223

My theory on the “rushes into mob forever and never does the swing” issue is due, from a programmer’s perspective, to the skill targeting the collision center or local-to-world origin vector of the model used for the mob. I have seen it fail to finish (rushing forever) on any mob that has a sizable collision area. So, basically, what happens is the rush skill keeps going, thinking it will reach the center of the target, but never does because the collision radius around it is too large. As far is it’s concerned, it’s still closing the gap, which is why the swing never goes off at the end. I can’t think of a better explanation (also very silly since Rush should constantly be doing a quick ( vector(blade tip bone location) – vector(targetmob.centerlocation) ).sizeSquared(), and compare it to scalar(collision radius of the mob – best guess – or if not done by radius in this engine a length check from the center to the nearest collideable area along the Rush’s target path)^2 to determine if it is sufficiently close enough to execute the swing. This would likely solve overshoots and the aforementioned “forever Rush” issue).

It’s an extremely fast mathematical operation that would have an insanely negligible impact on performance. So small, it would be unnoticeable.
Hire me, I’ll fix it for you.

Until then, you can interrupt the infinite rush by swapping weapons or using an emote. I haven’t found anything else that works.

The offer still stands.

Ah, the downfalls of using an unsigned byte instead of an unsigned short. Probably used to reduce memory and storage footprints. Although why it ends up at 244 is a bit strange. I would have expected 255.

Had to set mine to Enemies Only a few months back for the same reasons.

Korossive.7085:

I’m sorry, my signature of neglected-things-that-matter has no more space.

But there’s a brand new <generic animal> Mini you can buy!

Don’t forget those fuzzy hats! There are so many more important things we should be doing than worrying about game-breaking bugs, like paying them more money, silly!

Allisa Wonderland.8192:

What’s the immobilize bug?

https://forum-en.gw2archive.eu/forum/support/bugs/Immobilize-bug-linked-to-condition-transfers/

https://forum-en.gw2archive.eu/forum/support/bugs/Stuck-in-place-after-removing-control-effects/

One of the more recent threads and a thread about my own investigation. Also, try interacting with the Wurm Hole in Edge of the Mists when jumping. Also happened during the Battle for Lion’s Arch event when jumping and interacting with the portal to confront Scarlet.

I generally run solo, so my results are skewed as such. I didn’t know that it was now a near-requirement to be partied to get more/better loot on a world boss. So we just party up with random people if guild members aren’t available for the sake of better loot? Seems a bit silly, but that does explain all the “lfg” and “lf1m” etc I see at world bosses now.

Inculpatus cedo.9234:

I believe it only unlocks the two most recent transmutations. Rather than the original and the most recent.

What happens with gear that I currently possess that is already transmuted?

The skins for both of the items used in the most recent transmutation of your gear will be unlocked in your Wardrobe in this situation. This means that you will have skins representing your most recent stats and appearance choices for each transmuted item.

https://help.guildwars2.com/entries/46419166-Wardrobe

That does seem to be what it says. I did, however, have a quaggan backpack that I skinned over with a wind catcher, then skinned over again with the antitoxin injector skin. I got the quaggan backpack and the antitoxin injector skin after the patch, but not the wind catcher.

Happening right now. No Asura NPCs showed up for the stabilization. That makes it 3 times in a row for me.

How many times did you transmute that back piece? The update will only save the original skin and the current transmutation skin, like a transmutation splitter used to work. If that was your only transmutation, then yeah, that shouldn’t have happened.

Related to this thread:
https://forum-en.gw2archive.eu/forum/support/bugs/Immobilize-bug-linked-to-condition-transfers/

After posting, I decided to do some investigation. Equipping the Warrior trait Last Stand (Activates Balanced Stance when you are dazed, knocked down, launched, pushed back, or stunned), I went off to fight Jormag. Standing where people generally stand when firing at the ice wall, the very first time I was knocked back by Jormag’s ice wave attack I saw Balanced Stance automatically activate, with the stability and swiftness boons up as expected. However, I was completely unable to move. I had no control effects on me, no conditions, and no indication that I was stunned (in fact, this trait triggers stability, so I should not be able to be hit by control effects whatsoever).

I stood there, attempting to move or rotate, but could not. All move input stopped functioning. I continued to attempt to move for the duration of 2 more attacks, ~20 seconds or so, and still no response. No stun indication. No immobilize indication. Manually activating Balanced Stance did nothing. Manually activating Berserker’s Stance did nothing (it shouldn’t, but I tried anyway). Manually activating Dolyak Signet did nothing. Only when I swapped to my axe and used the burst leap was I able to break it and normal movement resumed.

The second time it happened, I used an emote instead as suggested in the above thread (/sit in this case) and the invisible “stun” went away.

Since something similar occurred to me in WvW using a Sigil of Generosity, I decided to try out a Sigil of Purity while randomly fighting as many ogres as I could in Fields of Ruin, and again ended up in the stuck state. Same solution: use an emote or movement skill to break it.

I can only assume this is a much deeper issue now than simply the Sigil of Generosity, especially in WvW where it will most likely lead to a quick death.

I hope this issue gets some attention, as it appears to break many skills, traits, and sigils in the game. I’ll submit an accompanying ticket as well.

So, today I was running around in WvW with an axe/mace, with a major sigil of generosity on the mace. Three separate times I was immobilized completely with no condition on me, no stun indication, nothing. I was just stuck. This has never occurred to me when not using the sigil.

Is that what’s being talked about here? It got me killed 2 out of the 3 times, because seriously, who is going to /sit in the middle of a battle with 20+ people surrounding you? Doesn’t this kinda defeat much of the purpose of this sigil? The third time it happened, I stood hilariously still while our side wiped out the enemy zerg, then finally switched weapons and broke out of it using shield bash when everything was over.

I’d just like to confirm that this is the issue that’s being talked about, because if it is, that sigil is getting replaced. It’s a death trap.

Lishtenbird.2814:

There’s been a rumor about a 50-player contribution limit per champ, and it looks plausible (with both current situation and events like Assault Knights).

It really looks like it means more to “register” yourself at a champ rather than to do enough damage; I checked it several times on Beasts at Ulgoth and on Avatars at Wurm, and I can say that indeed if I tag the champ before everyone else I’m almost guaranteed to get the loot, but if I stay at the champ for the whole time and DPS it down I may not get loot if I was late to tag it.

This is 100% true. When the war beasts at Ulgoth spawn, I get in and do some damage on each of them as soon as possible, then stay and smack around the 3rd one until it’s dead. I’ll get boxes from the first 2 I hit, and nothing from the 3rd (despite doing what I estimate to be about 200k-300k damage on the 3rd).

The same goes for the Avatars of Blight. Also, one thing that’s a bit annoying about these guys is that as soon as the last one dies, the event ends and the Wurm starts. For about a split second when the last one dies, you’ll see the loot prompt, but it seems like the event completion erases all of the avatars and their loot. I’ve tried mashing F as quickly as possible when it gets down extremely low on health, but it doesn’t work. I can only assume that the loot prompt is shown briefly because the client has not yet received the notification that the event is over, thus during that brief period of latency between client and server it thinks there’s an opportunity to collect it.

edit: in response to Saucermote, the Avatars of Blight do drop loot. Go for the farthest one from the mass of bodies and get in as much damage as you can before they swarm it. If it isn’t the last one to die, you will get a champ drop. This is also why I hang out near the champion grub before it spawns; getting in hits as early as possible guarantees me credit and a drop.

I’m having issues with this as well. Specifically, I created a new Guardian, and one of the hints is to hit F1 to grant virtue to allies (I believe). I have done this at least a hundred times, yet the hint comes back every 30 minutes or so and is never marked as complete. Several of the thief hints that I’ve done and should be marked complete are not as well (although they at least lack the annoying popup all the time).

Seems to happen on Eviscerate a lot too. Sometimes I can do whirling axe just enough to fill my burst meter and tap F1 to use Eviscerate and it smoothly goes right from whirling axe to Eviscerate, other times the character stops completely and pauses then suddenly does the Eviscerate a short time later.

My theory on the “rushes into mob forever and never does the swing” issue is due, from a programmer’s perspective, to the skill targeting the collision center or local-to-world origin vector of the model used for the mob. I have seen it fail to finish (rushing forever) on any mob that has a sizable collision area. So, basically, what happens is the rush skill keeps going, thinking it will reach the center of the target, but never does because the collision radius around it is too large. As far is it’s concerned, it’s still closing the gap, which is why the swing never goes off at the end. I can’t think of a better explanation (also very silly since Rush should constantly be doing a quick ( vector(blade tip bone location) – vector(targetmob.centerlocation) ).sizeSquared(), and compare it to scalar(collision radius of the mob – best guess – or if not done by radius in this engine a length check from the center to the nearest collideable area along the Rush’s target path)^2 to determine if it is sufficiently close enough to execute the swing. This would likely solve overshoots and the aforementioned “forever Rush” issue).

It’s an extremely fast mathematical operation that would have an insanely negligible impact on performance. So small, it would be unnoticeable.

Hire me, I’ll fix it for you.

Until then, you can interrupt the infinite rush by swapping weapons or using an emote. I haven’t found anything else that works.

I know this is isn’t a “fix” for the bug, but it’s a “fix” for the megaserver stuff regarding world bosses that I’ve been using since the patch. Since all bosses are now on fixed times, and not spawn windows, if you show up to a world boss event about 5-10 minutes before the timer ticks off the pre events, you’re most likely going to end up in an instance that has a huge number of players. Sometimes this is good (it’s nigh impossible to take on Jormag or The Shatterer etc without a decent number of players) but sometimes it’s not, my case being that I have to turn off player models to get a decent framerate, spell/skill FX with post-processing basically turning the screen into a giant white blob of bloom (really fun terrible on Golem Mk.II if you’re attempting to melee it because it’s impossible to see the trickle of electricity FX that warn you where the electricity is going to cover the platform, and a number of other issues that occur when you have a small condensed area filled with 100+ players.

If the boss’ timer to initiate the pre-events is set for 09:00, enter the map at 09:02 or something similar. It’s going to be different for every boss since the pre can sometimes be locked to a timer (Fire Elemental, Shatterer) rather than the boss spawning as soon as players finish the pre, so I’ll leave it up to you to figure out the best times.

My reason for doing this? Players are now on what I would call a fixed “rotation” where they will go from one boss to the next on every 15 minute cycle, which leaves the instances where people show up right before the timer ticks off completely full or near-full. Earlier today I decided to do the Golem boss 5 minutes after the timer for its pre went off, and was put in an instance with maybe only 10 other people. It took much longer to kill, was actually more challenging than the usual “stand here and press 1 to win” circumstances of a full instance, and I was actually able to melee it without being defeated thanks to finally being able to see the small tells of where the electricity was about to activate.

I’ve done the same with Wurm. Show up late, smaller group of players, chances of a Mes using feedback before getting in a hit has been non-existent.

It’s a bit sad that I have to do it this way, but it works. Usually. There are times I show up too late and the boss has already been defeated because the initial massive instance has already wiped it and cleared out for the next boss in the rotation. It’s not an exact science, unfortunately.

edit: I’ll also note that there are other side effects of having the megaserver with events like Tequatl where people stand around for 40 minutes to make sure they are in the largest instance, but guilds such as TTS have gotten around this by taxiing only the players they want to an instance that they can control, which I’m not sure is a good or bad thing when the instance you just sat in for 30 minutes suddenly empties 5 minutes before the event.

As reported before, this happens when a player opens the client launcher, logs in, but does not launch the game. It’s probably on their to-do backlog (which is most likely massive at the moment) so I wouldn’t worry too much about it.

Item: Monocle
Issue: Chain does not have a double-sided texture, neither does monocle lens
Race: All
Sex: All
Class: All

As seen in the below shots, the chain for the monocle can be seen just fine from the front, however if you try to look at it from the back, there is no texture.

The lens inside the monocle cannot be seen from the back either, leaving only an empty frame.

The Pointless.3869:

Ark Bladesteele.2943:

I believe you may have had a different first post in this thread if you were among those of us that had. It might not have insulted the rest of us. In fact, you might have had a complaint. You might even be a bit upset. One does wonder.

False. My first post would not be any different. If you had bothered to read the post you quoted, you would find I said that I would be infuriated if I had fell victim to it.

Ark Bladesteele.2943:

(Also, I really couldn’t help laughing at your “but I have a black friend and he doesn’t complain much when people are racist” comment when you brought up a guildmate who has the issue, but hasn’t reacted the same way as the people in this thread. Which people were those again, by the way?)

And I can’t help but laugh at the utter complete fallacy of comparing a bug to racism. Nice job of trivialising a serious problem there.

I made no such comparison. I made an analogy. You know what was kind of weird, though? Bringing up the fact that you lost a family member to a “bug.” That’s an awful thing to happen, but I’m unsure it has its place in this discussion. It also ties into the whole “everything is bad everywhere so let’s not complain about anything unless it’s the worst possible thing ever” thing you’ve got going on.

Let’s face it, you didn’t come here to argue in good faith. You came here to pick a fight. Mission accomplished.

The Pointless.3869:

RoyHarmon.5398:

The Pointless.3869:

Nethres.7168:

The Pointless.3869:

This forum doesn’t exist solely for your opinion.

Exactly, it doesn’t exist solely for -your- opinion

Then you have realised that you cannot voice an opinion and expect those in disagreement to stay silent?

Aarean.5398:

Stop flaming eachother and get off this topic. I STILL have this bug after the supposed fix a few hours ago. Im limiting what dungeons i do so i still have something to do when i log in. Fix this please

The red post specifically said next reset. The update missed the one just been by 15 minutes.

It’s true that many people here feel very strongly about this situation, and my opinion is that asking for a refund of the game or gems would be an overreaction (and I both hope and expect that they’ll reconsider). But remember that for many people, this game is their sole form of entertainment and the highlight of the day. Not everyone’s game experience is as casual as yours (you advised them to “go do something else”), and some people find comfort and joy in logging in to join their friends or loved ones online each day. For those people, this bug spoiled their happy time for a week, so it’s quite understandable that they’re unhappy.

If folks are upset about something, it usually doesn’t help to keep telling them, “Hey, you’re being unreasonable. Things could be much worse, so stop feeling so entitled!”
Honestly, your first post in this thread wasn’t the best way to start a constructive discussion, regardless of how constructive the discussion of others had been.

Let’s hope that we never hear of this incident again after a week or so. That would indicate that either the players affected by it were satisfied with the outcome, or it was a minor enough inconvenience that they chose to move on with their lives. It’s possible that some will stop playing the game altogether as a result of this bug, but I don’t think this straw is massive enough to break the camel’s back on its own.

I’ll agree that my first post wasn’t the best was to start a constructive discussion, but on the other hand, I’m not sure a constructive discussion would have borne any hope of blossoming if I tried.

The amount of rage directed at ArenaNet as “thanks” for actually getting a possible fix out there suggests some of these players might want to step away from the keyboard for little while and take a breather at the very least. Yes, this bug is no doubt frustrating. As much as certain people would like to chill my opinions on the basis that I haven’t experience this particular bug, I have been in similar boats before. It’s infuriating, but at the end of the day, this… is just not worth the anger and stress that people are inflicting upon themselves by hurling all the abuse they can at the developers that likely busted a gut to get to the bottom of it. No game is worth that amount of strain.

Floryn.6307:

Note: players unaffected by this bug should stop posting in this thread, they contribue with nothing except antagonizing everyone affected by this fiasco.

And spewing all manner of abuse at a developer on the basis of an imagined slight against the player base is contributing what, exactly?

You addressed an entire thread of people based on, from what I can tell, the people that have been using rather colorful language in reference to the developers. You called us all “entitled.” You didn’t aim your guns at any specific post or person or group of posts, but everyone. That’s on you. Did you read every single post in this thread? All few hundred of them? I have. Some of us don’t feel that we’re entitled to a fix, however we are fully within our rights and abilities to complain. My post outlining the circumstances that led to what I call a complete failure of good development practice, which resulted in above said posts, did you read that? Or did you skim the hateful stuff and arrive at your snarky little jab when you entered the thread, while not even having having suffered from the issue yourself?

I believe you may have had a different first post in this thread if you were among those of us that had. It might not have insulted the rest of us. In fact, you might have had a complaint. You might even be a bit upset. One does wonder.

(Also, I really couldn’t help laughing at your “but I have a black friend and he doesn’t complain much when people are racist” comment when you brought up a guildmate who has the issue, but hasn’t reacted the same way as the people in this thread. Which people were those again, by the way?)

Same for me. I have it stretched so that 20 slot bags will have 3 slots open vertically, and occasionally it will shrink to 4 open slots.

Like I’m sure many others have (I’ve seen one in this thread post it so far) I received this stock response to my support ticket:

GM Talon (Guild Wars 2 Support)
Apr 21 15:49

Hello,

Thanks very much for letting us know about the issue that you noted in Guild Wars 2. The next time that you’re in the game and you find a bug, you can do us a favor by submitting an in-game bug report. This will send detailed information about your character and your position directly to our Quality Assurance Team and will help us kitten the issue as promptly as possible. To submit a bug report in the game, simply click on the “Game Menu” button in the upper left-hand corner of the game interface, then choose the “Support” option on the Game Menu. That option will allow you to review known issues, report a bug, or contact Customer Support.

You’re also welcome to report a game issue in the Game Bugs sub-forum of the Guild Wars 2 Forums ( https://forum-en.gw2archive.eu/forum/support/bugs ). You may include screenshots with your forum report, if you wish to do so. While we are unable to respond directly to each bug report that we receive on the forums or through the game interface, each report is reviewed and escalated, when appropriate.

Thank you again for taking the time to let us know about this issue.

Regards,

GM Talon
Guild Wars 2 Support Team
http://support.guildwars2.com/

I’ve submitted tickets in the past, and gotten the exact same copy-pasted response. Despite being a copy-paste, it almost seems to fault me for not reporting the bug in the proper way (using /bug in the game).

That was sent to me as a direct reply to my inquiry about a timetable on the fix and possible compensation.

We deserve better.

It’s nearing 10am on the west coast. Typical games industry core hours (in my experience at several different companies) are 10am-6pm. If we’re lucky, we’ll hear something soon.

It’s a nice idea, and I like the crowdsourced approach. We haven’t heard anything from ArenaNet about when this bug will be fixed or what kind of compensation, if any, we’ll be getting.

Please don’t donate to me, though. I’m not suffering badly enough from lack of funds this past week that I “need” it. I just think this is a great idea.

Well, I tried my second idea, with a little change based on the the posts read here:

1) All characters parked in Gendarran.
2) Logged off an hour before reset, logged back in 5 hours after reset.
3) Selected a character that I did NOT use when the bug occurred.
4) Loaded into the game. Bug still persisted.
5) Tried moving to Divinity’s Reach. Bug persisted.
6) Tried moving to Snowden Drifts. Bug persisted.

Not fixed for me yet. If there is no dev fix today, I will try to have another character in Snowden online when the daily reset occurs. That’s the last thing I haven’t tried (based on these posts).

DjGriffon.8461:

ok here is a theory after reading through all of the many pages on the forum about this issue. it appears to be caused by the megaservers. and since everything is account bound now, it seems to me if one of your characters is on a megaserver and one is not, then you might be having a problem with the resets. some people claimed that all of a sudden their accounts started to work fine, but the devs had gone home for the weekend and were not going to fix the issue until begining of next week. I had two of my characters on megaservers over the last few days because i don’t play them that often and two that weren’t. so today in about 3 hours and 30 minutes i will see if my theory is correct as i have moved them all to vigil keep

I tried this theory. I had all my characters in Vigil Keep at the time of the last reset, and the issue did not resolve itself. When it came for the dailies to reset, the daily timer was at 00:00 until I moved into another map, when the bug resumed with all dailies complete. Steps I took:

1) Moved all characters to Gendarran (Vigil Keep)
2) Stayed logged in to my main when the dailies rolled over
3) Moved into a megaserver map when I saw they did not reset

What I’m going to try to do today:

1) Still have all characters in Vigil Keep
2) Be logged out/offline when the dailies roll over
3) When I log in, if the timer is at 00:00, instead of zoning to a megaserver map, zoning to another non-megaserver map.

We’ll see how it goes.

Wiz.1543:

Thank you for linking Nouvel!

However this is about daily dungeon reward not daily achievement!

They’re linked. Dungeon chests reset along with the dailies. You’re going to find that any reward you’ve gotten from anything that resets with dailies (bosses, WvW bonus chests, dungeon paths, ascended materials, rich veins, etc) will no longer appear for you if you have gotten them already. Read the rest of the thread for full details of how this affects you.

As an aside, since this is apparently achievement related, I’m 20 AP away from my 6000 chest and am deathly afraid to do ANYTHING that gives me an achievement, in fear of not receiving the rewards from that chest. That limits me even more as to what I can do.

Has anyone gotten an AP chest with this bug and not had issues?

edit: I’d just like to chime in on the dev response. It’s vague, insulting, and downright abysmal. We deserve better than “we’ll fix it next week or sometime or whatever, bye!” Especially since we know that there were developers around after the response because a patch rolled out at the end of the 18th.

humfrid.2615:

Should I submit a support ticket?

Yes.

Race: Sylvari
Sex: Male
Profession: Warrior (most likely Guardian as well)
Height: Any
Build: Any
Armor: Orrian Legguards aka Grasping Dead Legguards

There is a distinct hole in the back between the leggings and the chestplate. I have tested this with 8 different chest pieces, at 3 different heights and builds, and all exhibit the same problem shown in the screenshot. It is especially noticeable with the Nightmare Cuirass (used for image). You can see right through the model, and it is extremely visible/distracting during any movement, especially while running.

It appears to occur no matter what chest piece is used.

Ravenor.3612:

Daishi.6027:

Regina Buenaobra.6193:

Hi, everyone. I’m here with an update.

Unfortunately, we were not able to integrate fixes for the bug affecting the stuck Daily Achievements today.

Ok but why? What is the limitation?

Regina Buenaobra.6193:

We apologize that this is affecting your game play experience.

We’re going to try and fix this at our next earliest opportunity, and that’s going to be early next week.

Next week?… Even if it’s fixed on monday which is 3 days, More if you’ve known about the bug previously. I gotta ask is there no indication as to what the bug is and does it still needs to be investigated? If yes, why so long to isolate the problem. If no? Why so long to implement the change?

While I’m at it why does it take so long for anything to get done? Do you have to personally phone in every time your updating the server to NCsoft? Do you have to get translators on the phone , explain why it’s going to cost an extra 200$ to put out an update so you can get it crossed off the budget so you don’t need to pay it out from gems?

I know I’m shooting far here but the pace at which things are done always seems so sluggish.

Keep in mind that this is a massive change and a brand new system that just came out. Any fix is going to require extensive testing to make sure something else major didn’t break in the process. I’d rather wait a little bit longer and have a perfect fix instead of a fast one that opens up more issues and only makes people angrier. Also I don’t think that the update would have been released with a bug of this size in it if they had known about it, since Achievements is one of the largest and most central systems in the game.

Also, I should add that they have absolutely no requirement to divulge the intricacies of the game’s inner workings to us, since that would be like giving away trade secrets to their competitors. “Megaserver broke achievements” should be about as much explanation as anyone on our side needs (even that’s a lot of info).

I agree with all of this, and being an 11 year game development veteran, it gives me a unique perspective that some people may not have. This was indeed a massive update to the game, there were bound to be bugs, and some of them likely serious. Like the no-chat bug on the first day, megaserver issues with world bosses being at completely different states in different map instances (with no way of knowing which instance you’re traveling to and what status it’s at), and of course this one.

However.

As a veteran developer, I can also look at the other side of this coin. The update was scheduled for April 15th, with full knowledge in advance that Easter weekend would be following shortly. I’m left with these thoughts:

- The production and management should have had the forethought to schedule the update for another time, not when a pending major holiday would be looming days after. This leads to my next thought.

- By scheduling a major update just before Easter, that pushes the entire development team to work harder, longer, and faster to get it done, because most will have holiday plans that they simply can’t abandon. That kind of unnecessary strain (let’s not beat around it here, it’s called crunch for a reason) has plagued the games industry for a very long time. This is poor management, and poor development practice — people who are pushed too hard, get too tired, and work too late, make mistakes. Oftentimes, serious mistakes. This is why we, as end-users, are in the position we are right now.

- Not allowing enough time after the update roll-out to fix any lingering issues is amateur hour. I am digging very deep to find any excuse for this, and feel sorry for the devs that have been grinding away since the 15th to try and help us. I know it’s not your fault.

In addition to your post, I would like to add that we, as paying customers, some who have paid far more into the game than the initial price tag, have every right to be upset about all of this. We are the ones that write the paychecks. Just because our hands aren’t on the pen doesn’t mean we’re not the ones putting money into the bank.

Finally, I believe that anyone who benefited from exploiting any bugs from the patch should not be banned, but simply have those rewards rolled back, and on the counter-side, those of us that have instead suffered should be compensated in kind.

That’s my 2 copper on all this.

Finale.5281:

At least this simplifies my schedule for the weekend. PvP and WvW only! =/

It simplifies mine even more. No Guild Wars 2.

We have an ongoing thread for this here:
https://forum-en.gw2archive.eu/forum/support/bugs/Daily-reset-bugged/first

I too have lost out on 2 days worth so far. I would calculate the lost value out to be at least 40-50 gold.

I’ve submitted a ticket and replied with additional problems as I come across them. Four emails have gone out so far. Hoping they will take notice soon.

Add me to the list. Dailies are not resetting.

Every time the daily reset rolls around, my dailies from the previous day(s) are still marked as complete. Therefore I end up with 5/5 completed dailies already, unable to get the daily reward.

Other related issues:
- Daily boss rewards do not reset
- Daily dungeon path rewards do not reset
- Daily time-gated materials do not reset

Anything related to the daily reset is now broken.