Guild Wars 2

GM Awesomeness.8619:

OP:

• Did you happen to take a screenshot or write down any error messages you saw?
• Did your client completely crash, or did you just get booted back to the character select screen?
• If your client did crash (rather than just disconnecting/going to character select), can you please PM me with your crash log? Instructions on getting the log are here.

Everyone else: if you get DCed or crash during the Shatter, it would be super helpful for us if you could take a screenshot of whatever error/crash message you get. If you get a crash message, you get bonus points for sending me your crash log in a PM. Thanks!

Hey there – OP here. I only went to the character screen. I checked my log to make sure, and my last crash recorded in there is from December, so definitely wasn’t that sort of crash. I think the message was just the “lost connection to the server” one, but I didn’t screenshot and not 100% certain.

I’ll start by saying the patch was very positive . Then I will put on a huge sad face at the fact that Dragon Ball falls short again for me this year. If you volunteer to move to the other team to balance, you should get the win (like in normal pvp). I was in a map that was winning 460 to 320 when everyone in the other team left and I was auto-balanced last second and so, lost. This is upsetting, because I put in the time and effort to contribute to a winning team. When there is nothing to be gained at all from losing, and people can leave with no consequence, you encourage people to drop out of games early if they aren’t winning and go find another map. I wish volunteering to auto balance would give you the win. Or at the very least, penalize people from leaving early (5 mins of not being able to join another game, maybe?)

I killed the Shatterer at the 2pm EST spawn, the first spawn after the new changes were implemented. My map was full of anet tags and it was very exciting and smooth overall. From the boss chest, I received Breath of Kralkatorrik and was super stoked, as I was missing this item from the collection achievement. I also received 2 achievements from the boss kill: Bash the Dragon and Shattering Evasion. I pinged Breath in either squad or guild chat (can’t remember), and then account bound it for the treasure hunter collection.

A few minutes later, my entire map instance disconnected. I was in a squad and teamspeak with maybe 10-12 guildies, and everyone DC’d. When I logged back in 30 seconds later, my loot was gone and those 2 achievements were gone.

I submitted a report and received a response saying that the log doesn’t show me as ever having had this item, so they can’t help me. I responded back, confused as to how both pinging the item and unlocking it for collection could not have been registered with the system. I then received another response, saying they were getting more tickets with similar issues and asking for more details.

After providing a long description of events, I received a response from a different GM saying: “Thanks for all of the information! I sincerely apologize for any inconvenience that this may be causing. Unfortunately, this is not something that customer support will be able to directly assist with. Thanks for submitting a bug report and we hope that your issue is addressed by the Dev team soon. Any changes on this issue will be released by the Dev team via our official forums.”

Since I didn’t find anything on the forums about this issue, I’m posting this here. Many of my guildies also lost loot and achieves from the DC, but since it was “junk” they didn’t really care. Breath of Kralkatorrik is now down to like 5 gold on the TP, but I felt like posting this was still necessary.

Does this mean that if I disconnect a few minutes after getting a chak egg to drop, I will just be out of luck?

Has this really not been addressed by Anet? My group just finally got to clockwork and wiped while killing generators. The generators all respawned, but now no holopirates are spawning. After so much time working on this dungeon, it’s infuriating. Did anyone have any success getting around this bug? Thanks.