diablo 3 ban wave

Diablo 3 Season 5 Ban Wave Aftermath

MichaelBan WavesLeave a Comment

With the end of Season 5, it seems that the ban waves have stopped as well, unless Blizzard is going to start targeting non-season players as well. It was speculated somewhere that the past 5 sets of ban waves have hit about 48.000 accounts, however, that number hasn’t been officially confirmed. We’ve decided to make a Diablo 3 ban wave aftermath as a follow up post to the initial post to provide you with as much information as we can.

If you’re looking to appeal your ban, you can follow our Diablo unban appeal guide.

diablo 3 ban wave aftermath

What we know so far

  • Blizzard’s Warden has been updated and is capable of detecting any program that is interfering with Diablo 3 and/or Hearthstone. This means RoS-Bot, TurboHUD, D3Helper are detected, according to the BuddyForum, and even though not confirmed, maybe DemonBuddy as well;
  • DemonBuddy’s TripWire has been activated on both 9-Feb-2016 21:52 UTC and 19-Feb-2016 02:23 UTC;
  • Most of the affected players were on the leaderboards, had high playtimes, as well as high paragon levels;
  • First two waves have targeted the bot users mostly, whereas the latter three were a mix of bots, TurboHUD, D3Helper, AutoHotkey and even mouse/keyboard macros;
  • Players who were using bots were banned before and after the TripWire events, so apparently it didn’t make much difference if they stopped or not, however, some of them reported still being safe;
  • A lot of streamers and high ranked players from top clans were banned, with offenses ranging from botting to using TurboHUD or macros;
  • With their leaderboard records removed following the ban, a lot of legitimate players have jumped up to 200 ranks on some classes;
  • Most banned classes on the leaderboards were (in descending order): Wizard, Demon Hunter, Witch Doctor, Crusader, Barbarian, Monk;
  • It is not known how Season 6 will be affected by this, how many people will come back to Diablo 3, how many will give up on it or how many will keep;
  • If you’d like to read more about all 5 sets of Diablo 3 ban waves, you can do so here, here, here, here, here and here;
  • If you’d like to read about how the ban waves affected the leaderboards and various other statistics, you can do so here, here, here, here and here.

Here’s a funny video of Alkaizer’s impersonation of Rhykker and Gabynator:

 
And here’s a video of wudijo getting banned on stream:

 

Conclusion

It’s a good thing to see Blizzard still caring about Diablo 3, even though they moved what was probably the best developer, namely John Yang, from Diablo 3 to World of Warcraft. I’ve personally enjoyed the game a lot more with him as a developer as opposed to before, but hopefully his replacement will be just as good, and I really hope to see John Yang back once he’s finished with designing legendaries for WoW.

Regarding the ban wave, I’m sure a lot of players enjoyed the leaderboard boost, myself included, however, in some cases, I think permanent bans were a bit too harsh, but that’s up to Blizzard to decide.

I really hope everyone will come back to Diablo 3 for next season so we can all play and compete, legitimately this time!

Should you require our help, please don’t hesitate to check out our Diablo 3 unban service!

Need help with a Diablo 3 account ban?

We're here to give you the best help in order to get your Diablo 3 account unbanned!

Get unbanned from Diablo 3!
About the Author

Michael

Michael, founder and writer of Unbanster, brings over 20 years of gaming experience and a law degree to his specialized work in his unbanning service. Though he didn't pursue a traditional career in law, his unique legal perspective enables him to tackle the intricacies of gaming policies and appeals processes. Motivated by a personal unjust ban, Michael launched Unbanster in 2015 to aid gamers facing similar challenges, having successfully assisted thousands to date, striving to ensure fairness and transparency in the gaming community.

Leave a Reply

Your email address will not be published. Required fields are marked *