Jump to content
FORUMS
Sign in to follow this  
Starym

Bot Banwave in WoW Classic: 74,000 Accounts Suspended

Recommended Posts

50145-blizzard-responds-to-bot-player-co

 

Here comes another in the recent actions to address the epidemic of bots and other exploitative behavior in Classic, with Blizzard banning/suspending 74,000 accounts over the past month, including today!

This comes after the lukewarm response players had big issues with, as well as the 30 instances per day limit, which seems to have had an effect. This particular action seems very decisive and should show the community that Blizzard takes botting and similar exploits seriously.

We also get some details on the way Blizzard detect bots and how the have to manually examine some incidents, which is why it's taken so long for a big action like this.

Blizzard LogoBanwave (source)

We’ve recently completed a round of actions against players who were found to be cheating in World of Warcraft.

We rarely communicate publicly about this, because we’ve found that describing our sources and methods can make it easier for malicious actors to work around them, but we feel that it’s worthwhile to expand on the subject today, as many players have recently asked us for more details.

Including today’s actions, over the last month in the Americas, Oceania, and Europe regions, we’ve closed or suspended over 74,000 WoW accounts that were found to be in violation of our End-User License Agreement. The majority of these were found to be using gameplay automation tools, typically to farm resources or kill enemies much more efficiently than legitimate players can.

While today’s suspensions were applied in a batch (often referred to as a “banwave”), it is a top priority for us to identify accounts that are botting and remove them. Our team works around the clock, every day of the week, and many of the suspensions and account closures over the last few months have gone out in the middle of the night, or on weekends.

Like you, we play World of Warcraft. We understand what it’s like to spot a player in-game who appears to be botting. We always want to eliminate the botting player, if it can be proved that they are indeed cheating. And that raises a big difficulty in addressing this issue – we have to prove to ourselves that the accused player is not a person who’s actually controlling a character with their hands on a keyboard.

We use powerful systems to determine if the suspected player is using an identifiable cheat, and our heuristics (which we do not outline publicly) are constantly improving and evolving. But when we examine a suspect and these measurements aren’t out of line, we have to manually gather evidence against the accused player, which can be very time consuming and complex. It’s worthwhile though, because we never want to take action against a legitimate player.

Yes, there have been cases where a legitimate player appeared (to another player) to be botting. In those cases, where a legitimate player is reported and then cleared of wrongdoing, it can be very frustrating to the reporting player to again see what they think is a bot. We’ve also seen examples where the reported player was caught exploiting the game, and was removed from the game, and then quickly returned to doing the same thing on a new account with the same character name. That’s an infuriating sight for the players who initially reported it. We greatly appreciate your reports, and we understand how you feel about this.

We’re ultimately working to unravel a challenging circumstance. Real money trading drives third parties to put an enormous amount of effort into circumventing our detection systems. As much as this is a very high priority for us, it is the only priority for profit-driven botting organizations. The bans we issue are simply a cost of doing business for them.

We’re working on further improvements to every part of the game that might address cheating issues more swiftly and completely, and we’ll continue to let you know as those next steps are taken.

Thank you very much for your feedback on these issues, and thank you for your reports!

Hopefully this will at least begin to rectify the situation in Classic, which was really getting out of control and making players very frustrated. It definitely showcases that the community can impact big changes and affect Blizzard, so definitely GJ for all of those reddit posters that pushed hard against the bot epidemic.

  • Like 3

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Starym
      We have a big change to the anti-botting measures put in place for instance farming, as the limit of 30 instances per day has been moved to a per-character basis instead of a per-realm one! It should be as effective against bots, but much less so to real players.
      July 8 (source)
      WoW Classic
      Time-based instance limits are now enforced per-character. Developers’ notes: The newer limit of 30 instances in a 24-hour period is an extension of the 5 instances per hour limit, which was tracked per-realm since it was first implemented in 2005. The intention behind both of these restrictions is to reduce the profits for new bots when they first come online and haven’t been removed yet. We’ve concluded that a per-character limit will be just as effective, while being less restrictive to legitimate players who have multiple characters on the same realm.  
    • By Starym
      The most recent Blackwing Lair fastest speed clear didn't quite last long, as we have a new best time! Progress are back on top, pushing faction rivals Onslaught down to second, as the Alliance guild clears BWL 23 seconds faster, downing Nefarian in 18 minutes and 51 seconds!

      The Blessings have outperformed the totems for now, and the raid composition saw the usual melee stack, with 22 warriors, 5 rogues,  6 priests, 3 paladins, 1 mage, 1 warlock, 1 druid and 1 hunter. You can check out all of the run's stats here.

       
    • By Starym
      Some players have been having issues getting the extra bag slots from adding an authenticator to their account and Blizzard have explained it's related to out of date addons:
      Bad Slots Fix (source)
      We have seen accurate reports of the new bag slots not appearing in-game, due to out of date addons.
      It looks like disabling addons reveals the new bag slots in that case.
    • By Stan
      The guild Onslaught of Skeram (US) was able to speed-clear Blackwing Lair in just 19 minutes and 10 seconds, beating the previous record by over one minute!
       

      You can find more details about the run by clicking on the image above.
      It is worth noting that healers in the raid used a total of 59 Flasks of Distilled Wisdom throughout the run since it gives you 2,000 Mana instantly on no cooldown.
      Watch the run over on Twitch.tv!
      We recommend watching the VoD muted, as it contains strong language.
      (Source)
    • By Starym
      In a bit of a strange move, Blizzard have just posted the patch notes for the next phase of World of Warcraft Classic, patch 1.13.5 aka phase 5, ahead of it's July 28/29th release.

      However, there seems to be a large part of the update that has gone live now or will soon, namely Alterac Valley updates (including many bug and exploit fixes), addon APIs, bug fixes and authenticator bag slots.
      1.13.5 Patch Notes (source)
      Ahn’Qiraj
      Behind the Gates of Ahn’Qiraj are two large, unique raids – the Ruins of Ahn’Qiraj, a 20-person raid, and the Temple of Ahn’Qiraj, a 40-person raid. As players delve deeper into the mysteries of Ahn’Qiraj, they will discover revelations of the Silithid infestation and their shadowy masters, the Qiraji. Players will have to complete a world event of massive proportions before they can open the Gates of Ahn’Qiraj on their realm.
      The Ahn’Qiraj event will unlock with the weekly raid reset in each region the week of July 28. At that time, players can begin the quest chain to craft a Scepter of the Shifting Sands, and players can turn in gathered resources to advance the Ahn’Qiraj war effort. Once both of those activities are completed on a given realm, the gates of Ahn’Qiraj will be available to be opened. Content Updates
      The Dungeon Set 2 items, dungeon questline, and vendor are now available. Wizard Oil and Mana Oil are now available. Nexus Crystals can now be obtained via disenchanting Epic items. This update includes Dungeon loot table adjustments, increased drop chances for epic items, and many new caster DPS items from original WoW patch 1.10.
      Several Relics are now available. Reputation rewards from Warsong Gulch, Alterac Valley, Thorium Brotherhood, and Timbermaw Hold vendors are updated. The content updates above will unlock with the weekly raid reset in each region the week of July 28. Alterac Valley Updates
      This patch includes many bugfixes for issues found in the 1.12 version of World of Warcraft. These were issues that were clearly unintended by the design of the time, and are now fixed:
      Terrain exploits You can no longer climb the waterfall and enter the Frostwolf base near the Relief Hut. You can no longer climb the cliff and enter Dun Baldar near the Aid Station. You can no longer bypass Icewing Bunker. Reputation inconsistencies between Alliance and Horde Alliance now always receive Reputation and Honor for defeating Captain Galvangar, regardless of whether Captain Balinda Stonehearth is alive. Developers’ notes: This now correctly mirrors the Horde behavior, which grants them Reputation and Honor for defeating Captain Balinda Stonehearth, regardless of Galvangar’s status. Alliance Druids can no longer have their actions disrupted by talking to them. Developers’ notes: This now correctly mirrors the behavior of the Horde Elementalists, who were already just as steadfast in executing their intended actions. Exploits for defeating the enemy general. The Horde War Masters can no longer be kited far enough to allow General Drek’thar to be engaged and defeated alone. The Alliance Prospector can no longer be tricked into pulling General Vandar Stormpike out of the bunker so that he can be defeated alone. Developers’ notes: As always, our intention is to accurately represent the 1.12 design intent of the game, and these bugs are clear examples of behaviors that were never intended. Addon APIs
      Recently, we’ve seen an increase in the chat traffic generated by addons that synchronize data between their users. While the vast majority of addons do this responsibly, some can be problematic to the point of degrading the game service for all players. We’ve previously hotfixed the server-side of the game to incorporate chat throttles that work to alleviate some of this, but during our investigations, we found common use cases that we can improve for addon authors.
      Threat
      The community has largely solved threat calculations, and has created robust tools for displaying this in-game. We’d like to improve the addon APIs so they can display this data in an addon without needing to transmit a great deal of chat traffic. Larger combat log range
      We originally restricted the combat log range in the open world to prevent a larger radius of stealth detection than existed in original WoW, but this isn’t an issue in Dungeons and Raids. As a result, addon authors send a great deal of chat to synchronize combat events across the raid. In this patch, we’re increasing the combat log range in dungeons and raids so that damage meter addons can get accurate data without the chat traffic. Authenticator Bag Slots
      Since before WoW Classic was first launched, we’ve been very concerned with replicating the original experience while eliminating as many ways that accounts could be compromised as possible. We can’t eliminate them all, and unfortunately, many WoW Classic players have not yet taken steps to protect their account with an authenticator. That leads to difficulty for players when their account is compromised, and they need to contact Blizzard Customer Service to resolve the issue.
      In this patch, we’re activating an additional 4 bag slots for any player who has an authenticator attached to their WoW Classic account. In order to help preserve the new-player experience for players who are new to Classic, this won’t be advertised in-game until you’ve reached level 20. Any player with an authenticator already attached to their WoW account will see the additional 4 slots on their backpack when they log into version 1.13.5, and any player who doesn’t will see an in-game “+” on their bag to remind them to secure their account for this reward.
      We recognize this is a notable change from original WoW. Account security is very important to us, and we want the reward for securing your account to apply to WoW Classic, as it has applied to World of Warcraft for many years.
      Bug Fixes
      Fixed an interface error that occurred when generating a link to a Battle.net Community in-game. Fixed an issue that caused some items with running or mount speed bonuses to not correctly stack multiplicatively. Many large monsters and bosses are no longer missing certain combat sounds. Fixed an issue that caused certain creatures and bosses to be missing screen shake effects during abilities, such as Onyxia’s Bellowing Roar. Fixed an issue that caused Kwee Q. Peddlefeet to linger near the winning faction leader far longer than intended after Love is in the Air has ended. Fixed an issue with where some Black Lotus spawns were placed incorrectly. Fixed an issue that caused stacking damage-over-time effects cast by creatures to not calculate damage properly when modified by damage reduction or bonus damage effects. Fixed an issue that caused some creatures to not properly prioritize attacking non-feared targets. Fixed a visual bug that caused the red shader effect to persist too long on players after using a Wind Stone in Silithus. Fixed an issue that caused some casting animations to behave less responsively than expected when a spell is cast immediately after landing from a jump or fall. Fixed an intermittent issue that could cause a Rogue’s energy resource bar to fall out of sync and display an incorrect amount of energy each tick. The “Move to Whisper Window” chat functionality now functions properly. Resolved an issue that caused some Graphics settings to not persist through logout. The patch isn't due for a few weeks yet, but the patch notes are here and some parts of it may be live!
×
×
  • Create New...