Blizzard just banned over 100,000 World of Warcraft accounts in the name of stopping cheaters. But did it work?

It’s doubtful that all cheaters and botters are gone from WoW forever, but it sounds like Blizzard latest huff and puff succeeded in blowing them down. Bossland, creator of WoW’s most notorious bot, the PVP-centric Honorbuddy, admitted that they’re pretty much beat—at least, for now:

“With Honorbuddy you thought that we are unbeateable, we never thought that, we’ve succeeded since 2010—Honorbuddy had not a single software detection. It seems there is one now.”

“We are sorry for all your lost WOW Accounts, hopefully you can use them again after the 6 months ban is lifted. I have read here in the forums a bit, a lot of the accounts where 10 years old. This is a pity. We always say, do not use your valuable accounts as the risk is always there.”

“You ask yourself what happens next? For now we closed our Honorbuddy Authentication, when we know any more details we will inform you.”

Functionally speaking, that means the bot is done for. That’s good news, given that Honorbuddy bots would often clog up PVP matches with mindless machines, ruining matches for everyone else. It was, of course, very against Blizzard’s terms of use, but Honorbuddy was a total bitch to get a bead on. For years, Blizzard couldn’t pin it down, reliably discern between players who were employing the honor-farming automaton and folks who were actually, well, honorable. Now that they finally have, it seems Honorbuddy’s creators have no choice but to throw in the towel.

Advertisement

It’s all quite sad for them, but also they were wrecking PVP matches for a lot of people, so they had it coming. WoW players in the crowd, how are things going for you? Have you noticed any major changes since Blizzard tossed thousands of bots into the trash heap? Alternatively, are you a botter yourself? If so, why, and did this latest round of bans affect you?

To contact the author of this post, write to nathan.grayson@kotaku.com or find him on Twitter @vahn16.