The trick could be repeated every time a Blood Thief was located, word spread quickly, streamers were demonstrating it live, and things rapidly got out of hand with players gambling through tens or even hundreds of thousands of Blood Shards. Blizzard hotfix disabled the exploit by requiring everyone in the game to be within proximity of the goblin in order for Shards to drop, and now that the bug is fixed, outraged fans are demanding that heads roll, and Blizzard seems to agree.
With this, we’re also in the process of actioning accounts which have been found to be actively using this exploit to gain an unfair advantage. This behavior not only undermines the spirit play, but directly violates our in-game policies for Diablo III. As always, maintaining a stable, safe, and enjoyable online environment for legitimate players is very important to us, and we’ll be continuing to keep watch on Battle.net and take additional action as needed.
In the meantime, we encourage everyone to please game responsibly. Not only can using exploits lead to account penalties, but it can also negatively impact the enjoyment of your fellow players. This is why we’re working as quickly as we can to fix the underlying issue, and why we’d appreciate your help in keeping the effects of the exploit as minimal as possible until it’s removed from the game.
There are numerous claims that various streamers were banned for exploiting this, but there’s a lot of trolling going on with people claiming to be banned to get attention, or accusing others of using the exploit. How many people were actually doing it and how much (if at all) this will impact the Leaderboards (chars from banned accounts vanish from the Rankings) remains to be seen. Blood Thief Exploit Hotfixed, Bans Coming.
Also note that the hotfix tonight didn’t properly fix non-splitting Gelatinous Sires, and they will now rarely do some mega-splitting, resulting in dozens of Gelatinous Spawn, rather than just the half dozen or so intended. Hopefully Blizzard won’t deem their execution another exploit, and likely we’ll see another hotfix soon to fix that issue as well.