Hardcore Rollbacks Possible Due to “No Gear” Bug

Hardcore Rollbacks Possible Due to “No Gear” Bug

Blizzard continues to deal with the “no gear” bug and they are going so far as to offer some rollbacks to restore Hardcore characters who died due to the bug.

We’re currently investigating an issue that’s affecting some characters, causing their items, armor, and weapons to go missing upon login. Although this issue is in most situations temporary and can be corrected with repeated login attempts, there are reports that some Hardcore heroes were lost as a result of this. For accounts which were specifically impacted by this issue, our Support team is investigating the possibility of providing a special one-time exception to allow for a rollback of the account, and subsequent restoration of the fallen heroes.

To contact our support with the request for this specific rollback exception, we encourage you to create a ticket through the following support portal with ‘MISSING GEAR DEATH’ in the body of the ticket:


Please know that the decision to allow such an exception is not an easy one to make, and that this is not a guarantee that we will offer the rollback to all accounts that petition us with this request. Only accounts which we can verify were affected by this missing gear issue leading to the death of a Hardcore character will be considered for these rollbacks. With that said, we do want you to know that we are continuing to address this issue, and ask for all players to be aware that the issue is currently ongoing.

Your deeds of valor will be remembered.

I haven’t seen this bug or heard anyone in the clan(s) complaining about it, so I have no idea how wide spread it is. I’m also not clear how anyone would die from it; if you log in and your character has no gear on, do you rush out into battle anyway, just assuming it’s a display error? Maybe in Softcore, but in Hardcore? (Update: As pointed out in the forum and comments, some nudists play with all their gear invisible dyed, and thus wouldn’t notice unless before battle, unless they opened their inventory.)

At any rate, we’ve come a long way from the early days of Hardcore. To quote from the official Blizzard North reply to any and all HC death issues from Diablo 2:

Note: Blizzard Entertainment is in no way responsible for your Hardcore character. If you choose to create and play a Hardcore character, you do so at your own risk. Blizzard is not responsible for the death and loss of your hardcore characters for any reason including Internet lag, bugs, Acts of God, your little sister, or any other reason whatsoever. Consult the End User License Agreement for more details. Blizzard will not, and does not have the capability to restore any deceased Hardcore characters. Don’t even ask. La-la-la-la-la, we can’t hear you…

Do you guys approve of this new era of compassion and player support? Or do you pine for the “good” old days where not only was Blizzard not responsible for your deaths (even if it was their fault), but they actively taunted you once it occurred!

Related to this article
You're not logged in. Register or login to post a comment.

17 thoughts on “Hardcore Rollbacks Possible Due to “No Gear” Bug

  1. I’m not a regular Hardcore player by any means (yeah I do play hardcore once n a while for the achievements and the challenge to level new chars) but I think that restoring chars because of a real deadly bug is fine as long as there is proof it was caused by said bug while restoring for any other reason is just ain’t going to happen.

    I can understand that some people are emotionally attached to their chars and especially after having invested so much time to gather the right items to make the char perfect would lose it to something that is out of their control and caused by Blizzard, that’s where it crosses the line.

  2. Blizzard did rollback D2 HC accounts on several occasions, despite their claim that they couldn’t. For instance, the times (note the plural! terrible!) when there were bugs that allowed anyone to take over any account and people used it to slaughter the ladder.

    I don’t know how this bug killed anyone, but if it did, a rollback seems fine. Then again, I also think a rollback would’ve been fine when my DH died as a result of them cutting the duration of her only defensive skill in half without telling me.

    • “I also think a rollback would’ve been fine when my DH died as a result of them cutting the duration of her only defensive skill in half without telling me.”

      Patch notes?

      • This was very early on and they did stealth nerf Smokescreen to 1/1.5 seconds (previously 2/3).

  3. I would think the amount of people legitimately killed because of this bug would be very few anyway. Not hear about the bug, log in, still not hear about bug from friends/clanmates, start fighting, still not figure out your character has no gear before you can run away, and then die. That’s pretty much what would have to happen in order for this bug to ‘kill’ you.

    I’d almost say leave them dead, they need to learn to pay better attention. =/

  4. “investigating the possibility of providing a special one-time exception to allow for a rollback”

    “Of course such Special, Exceptional measure would require the Personal authorization of none less than our CEO himself. Did we mention it was a One-time only offer of limited duration?”

    You heard it people, HC went casual hehe.

  5. I saw an experienced player on my friends list broadcast “Did anyone else lose all their gear?” That’s the only direct knowledge I had of the bug.

    As to how you could die from that bug? Well…let me sheepishly explain how that could happen. My main is a female monk and I have dyed all of her gear invisible-because I’m easily amused. So, if I logged in and did not have any gear on, I wouldn’t notice unless I specifically looked at the weapons. Furthermore, if I join a game with players I know and see a red banner, I click on it almost immediately. Therefore, I can understand how that bug might deeds someone.

    • I can kind of understand that, but even still, I personally usually open my character window when the game starts. If you’ve dyed your clothes invisible, that’s one thing, but if your character page doesn’t have any gear on, then that’s different.

      Also, while I will admit myself to also be easily amused, I think that few people dye all of their gear invisible. I’ve played a bunch of public games, and I’ve never seen another character running around in the buff. As a result, I don’t think deaths of your sort would be happening a lot.

  6. I thought the point of hardcore was that you accept the likelihood of death due to server f’ups. A server crashes that you’re on. It’s Blizzard’s fault. A lag spike happens because the server had a hiccup or somewhere else in the internet line had one etc. This time you where stupid enough to enter a portal or use a waypoint even after seeing your character naked in the out-of-game menu and in-game. Not only is it Blizzard’s fault, it’s yours as well.

    Seems weird that when it’s not your fault they’d not do rollbacks but when it’s half your fault they would.

  7. I think anybody that had their character die and his gear wasn’t dyed with Vanishing Dye , should be left dead.

    No exceptions should be given because this can be easily exploited to dupe gems and ruin the hardcore economy.

    I played hardcore in D2 and players always died to bugged affixes like Fire Enhanced champions that could one shot a hardcore player with their corpse explosion , or Iron Maiden in Act4 as a WW Barb, these things were fun regardless of being bugged, because it required players to pay extra attention and play very carefully at certain areas and not let their guard down no matter how good their gear is and this type of thing is missing from D3 I think , Hardcore players in D3 almost always play in a safe Difficulty level where the risk of dying is minimal and only it could happen only due to sudden disconnects and even then the risk is low because they are always outgearing the content.

    If anybody decides to play hardcore then they should accept all the rules and live with the fact that their characters are at risk of dying any moment due to bugs , disconnects , lags and whatever else that might happen. No Rollback , no restoring.

  8. I think hardcore characters are never entitled to a rollback, but I don’t have any issue of them giving them out in very specific situations like this (but I would also have no issue with them NOT giving them out).

    I would even have no issue with them giving a rollback in this specific situation, and then deciding not to at a later time if the same situation occurred (too bad, so sad).

  9. And I thought it was said countless times before that no rollback would be acceptable, ever, no matter the circunstances. For instance: they didn’t rollback fallen heroes due to brawler’s bug, did they?

  10. There were plenty complaining in IncHC2. As to how you die to it: You play as normal, you don’t notice the gear that was previously on suddenly vanished and you get hit once by any attack (twice if you have a second life passive). I think it got 1-2 people. If you use a lot of vanishing dye you won’t even have a visual cue.

    If I weren’t playing AHablo at both times it probably would have gotten me.

  11. I play Hardcore and I don’t think there should be any precedent for restoring Hardcore characters. Yes it sucks if you die but that’s what you signed up for. Seriously, the cause of your death DOES NOT MATTER!

    Stop crying and reroll. Or play Softcore.

  12. Blizzard didn’t restore other deaths caused by bugs like the blackfeather cloak bug, so I am against the restoration in this case as well, otherwise I am would be ok with that. I don’t know why they restored in this case but not in the blackfeather cloak bug case, I tried to contact the support but they said they won’t restore my character because it wasn’t a ‘wide spread bug’. They also didn’t define what is a ‘wide spread bug’, so looks like they are discriminating a group of customers and giving advantage for another group, I bet some of the support folks died ’cause of this bug, this is why they decided to open an exception case.

Comments are closed.