Latest Diablo 3 News
DiabloWiki Updates
Support the site! Become a Diablo: IncGamers PAL - Remove ads and more!

Blood Thief Exploit Hotfix Details

Discussion in 'Diablo 3 General Discussion' started by Flux, Apr 22, 2015.

  1. Flux

    Flux Administrator

    Joined:
    Jun 22, 2003
    Messages:
    6,710
    Likes Received:
    62
    Trophy Points:
    472
    Flux Submitted a news story

    Blood Thief Exploit Hotfix Details

    Blizzard has posted details about the Blood Thief exploit and the hotfix that has changed some game mechanics to prevent it happening again. Blood Thief Exploit Hotfix Details:

    While this issue is now resolved, we know a lot of players have questions about what happened and how we responded, so we wanted to take some time to discuss a few of the details with you here.

    Following the launch of patch 2.2.0, players discovered an exploit that caused Blood Thief goblins to drop a larger number of Blood Shards than intended. The exploit could only occur in Greater Rifts when in a multiplayer group and required a specific sequence of steps to activate.

    As soon as we were able to able to verify the exploit and identify its underlying cause, we immediately began working on a hotfix for PC. The hotfix was deployed in all gameplay regions on April 16, which made the following changes to the game:

    In order be eligible for experience or loot from any monster (including Treasure Goblins), you must do damage to it or be in the same area when it is killed

    • If you are in a Greater Rift, you are no longer eligible for any experience or loot gained by party members outside of the rift
    • For console, this particular change cannot be implemented via hotfix, so we've temporarily disabled all Blood Thief goblin spawns on PlayStation 4 and Xbox One until further notice (pending a future patch).


    From there, taking the complexity and impact of the exploit into consideration, we also elected to action accounts on a case-by-case basis. In general, one of three things occurred:

    • Accounts which were found to have both used the exploit excessively and publicly promoted its use were permanently banned.
    • Accounts which were found to have used the exploit excessively, but did not publicly promote it, were rolled back and their associated heroes removed from active Leaderboards (both Seasonal and non-Seasonal).
    • Accounts which were found to have used the exploit to a limited degree (or quickly stopped once realizing the scope of what was happening) were effectively pardoned. We understand these situations can inspire a certain level of curiosity and that it may not always be immediately clear if you're undermining intended game mechanics. Mistakes happen, but we hope this leniency won't be taken for granted in the future.


    All in all, this incident has shown us that the vast majority of players, upon encountering an in-game exploit, will not only put sportsmanship and fair play above personal gain, but will also work to bring the matter to our attention quickly via channels like [email protected], our online webform and ticket system, and these very forums. (We even received a few Twitter DMs, Skype messages, and personal emails too!) So, on behalf of the development team, I just want to say thank you to those of you who took the time to notify us, as well as apologize for any inconvenience caused a result.

    As noted in our original post, maintaining an enjoyable and equitable play experience is very important to us, and we're going to continue to monitor the game as well as take steps to prevent exploits like this from happening again.
    [source]http://diablo.incgamers.com/blizzard-tracker/devthread/eu/14381348239[/source]


    That reaction; banning the biggest exploiters/publicizers, rolling back abusers, and sparring experimenters, matches pretty well with the community consensus as expressed in our vote/survey results. As I argued on the last podcast, I'd still like to see a lot more transparency, with names and dates and such, but both guests disagreed, and it's an irrelevant debate since Blizzard has made clear that they're not going to "name and shame."

    So what do you guys think, now that this issue seems to have been resolved?
    Continue reading the Original Story
     
  2. spiffymcbang

    spiffymcbang D3 Trade Moderator<br> America, USEast (D2)<br> Ne

    Joined:
    Feb 14, 2006
    Messages:
    3,151
    Likes Received:
    22
    Trophy Points:
    168
    I like the response, and think the punishments fit the crimes perfectly. I am sure they did not get everyone but they got the big guys.

    Based on the history of hacking. botting and duping that Diablo, especially D2, has endured over the years, the hardcore cheaters need to be dealt a heavy hand of punishment.

    Good job.
     
  3. sneakytails

    sneakytails IncGamers Member

    Joined:
    Mar 10, 2004
    Messages:
    411
    Likes Received:
    0
    Trophy Points:
    98
    As a mostly console d3 player who plays mosly solo why on gods green earth should I loose access to blood goblins due to some PC punks shenanigans?

    This will hurt my blood shard intake greatly as I do not play like a streamer does, this clearly a case of players who had nothing to do with this getting punished.

    I hope they are thinking about a emergency patch in the next few days, because if it's not getting fixed until the next patch cycle then it really is a punishment for console players.

    Very unelegant solution on Console.
     
  4. sneakytails

    sneakytails IncGamers Member

    Joined:
    Mar 10, 2004
    Messages:
    411
    Likes Received:
    0
    Trophy Points:
    98
    Give it to me free
    I wanna get ripped off
     
  5. Raesene

    Raesene IncGamers Member

    Joined:
    Aug 15, 2011
    Messages:
    1,435
    Likes Received:
    1
    Trophy Points:
    167
    How much attention to the issue would be given on the "proper" channels if the exploit wasn't publicized as much as it was?
     
  6. trocadero

    trocadero IncGamers Member

    Joined:
    Feb 4, 2013
    Messages:
    228
    Likes Received:
    1
    Trophy Points:
    27
    Whatever happened to "To the Pain?" Blizzard and Flux have gone soft.
     
  7. Drixx

    Drixx IncGamers Member

    Joined:
    Apr 8, 2006
    Messages:
    3,566
    Likes Received:
    3
    Trophy Points:
    373
    There's an error in that Blizzard statement. Let me fix it for them:

    Start of Paragraph 2: "During the PTR testing of patch 2.2.0, players discovered an exploit that caused Blood Thief goblins to drop a larger number of Blood Shards than intended, which was reported to us and which we decided, as is our usual custom, to ignore in the type of willful arrogance you have come to expect from us as a company. After all, if players found it on the PTR, there's absolutely no reason to expect that it would go wide in full release ... right?"

    Over the top?
     
  8. Nodders

    Nodders IncGamers Member

    Joined:
    Aug 25, 2008
    Messages:
    449
    Likes Received:
    0
    Trophy Points:
    143
    Their philosophy is always about speed , not slowing the game down , moving Kadala etc , well because its faster .

    Now , someone ports to town to sell , we spot a blood thief we all have to hang around twiddling thumbs until the guy gets back .

    I don't understand it , if the exploit has been fixed , why that particular change ?
     

Share This Page