Jump to content
FORUMS
Sign in to follow this  
Starym

Instance Reset Bans and Exploit Clarification

Recommended Posts

45761-repeated-instance-encounter-reset-
 

The previously mentioned punitive measures have arrived for those that exploited the instance reset bug that was hotfixed today, and the suspensions are ranging from 1 month to permanent bans, presumably based on previous infractions, as well as all items gained from the exploit getting removed. We don't know the exact details of what criteria was used for the suspension, but Lore did come out and very clearly explained what is considered an exploit in this case and why it's different from similar situations (specifically the MC resetting bug), and as always, the key word is intent.

yotlavwps0n31.jpg?width=960&crop=smart&a
One of the suspension mails, posted on reddit.

You can check out the full explanation from Lore below and also read up on the various lengths of the suspensions in the reddit thread.

Blizzard LogoExploit Clarification (source)

Soooooo since I’m seeing a lot of confusion (here and elsewhere), here’s some insight into how we draw the line between what makes something a punishable exploit versus a “happy little accident.”

The key factor here is intent. Did the player do something with the specific intention of causing a glitch to occur, and did they do it order to exploit said glitch for their own benefit?

This recent glitch makes a pretty clean example. The players who were abusing it had to do some Very Weird Stuff to cause it to occur, and then did so repeatedly. No reasonable person would expect that this behavior was intended, and the players involved had to go out of their way to cause it. It’s obviously unintended, it’s obviously a glitch, and the people who abused it were obviously exploiting said glitch for their own benefit. That’s pretty open and shut.

Someone mentioned Esfand’s random MC reset in this thread, which is a pretty clean example of the other end of the spectrum. In that case, they just turned up to raid and the instance had been reset. They didn’t do anything intentional to cause it or go looking for reproduction steps so they could abuse it - in fact, they reported it to us and didn’t continue until they got confirmation that it was out of their control (and that we wouldn’t consider it an exploit if they cleared).

Side note for the curious: that was a completely separate bug that has existed since 2004, and actually happened several times back then, it just wasn’t being broadcast to thousands of viewers at the time.

Obviously, neither situation is ideal - we try our best to provide a fair playing field for everyone - but there’s a pretty massive difference between “the instance is reset and we don’t know why” and “if we do this One Weird Trick we can infinitely farm this dungeon boss.” That’s the key factor that turns something from an accident into an exploit.

This ended up being longer than I expected so I’ll wrap it up with one last caveat: there is a lot of context and nuance that goes into these situations, and they’re not usually as cut and dry as these two examples. We end up making a lot of judgement calls based on the specifics of each exploit as well as their overall impact on the game (the phrase “clever use of game mechanics” originally came from one such convoluted situation). These two cases just happen to be pretty obvious.

  • Like 2
  • Thanks 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 Staff
      Here come some big spell batching changes to the Classic PTR, with a huge rediction in the batch window:
      PTR 1.13.7 (source)
      Today, we’ve opened the WoW Classic Public Test Realm (PTR) to test version 1.13.7 of WoW Classic. In this upcoming version, we intend to reduce the spell batching delay.
      There are numerous class abilities and spells from Original World of Warcraft that were re-implemented in WoW Classic with spell batching in mind, and we initially expect bugs or adverse consequences with spell batching reduced. In this PTR, testers have an opportunity to join us in finding such issues. Raids and battlegrounds are available in this PTR to facilitate testing in a wide variety of game content.
      Initially, the spell batch window is set to 10 milliseconds on the 1.13.7 PTR, a reduction from the 1.13.6 live window of 400 milliseconds. Please use the in-game bug reporter (default hotkey: mouseover+F6) in the PTR to submit your bug reports or feedback on abilities with spell batching reduced.
      8
      When logged into the PTR, you can mouse over any item, spell, or talent and press the assigned hotkey to initiate a bug report for that item or spell. Bug reports created in this way include valuable metadata about the spell, your talents, and your player-state when the bug is submitted.
      If you’ve unbound your “Open Bug Report” hotkey, you can rebind it in Keybindings -> PTR.
      5
      If you wish to discuss class issues related to this update with other players, we’ve opened a new discussion thread in the WoW Classic Bug Report forum here 34.
      Thank you for testing WoW Classic with us!
    • By Stan
      Salad Bakers have cleared Naxxramas in WoW Classic under 60 minutes. This is the fastest speed clear of the raid so far. Congratulations!
      Salad Bakers have beaten their own record (1 hour 3 minutes 56 seconds) by a couple of minutes and the guild cleared Naxxramas in 59 minutes and 44 seconds!

      Here's a video of their speed clear. As TehBananaBread pointed out, a boss died every 4 minutes, which is insane!
      Source: Reddit
    • By Starym
      As the Castle Nathria RWF is going on we thought it was time to share the spotlight, as another, equally as impressive and dedicated group of players has taken down the antagonist of many low level players. You can see top level raid leading, the tactics and strategies below, as things get very hairy at the end, with all cooldowns popped and the tank having to kite!
      Unfortunately for the pro group above, this isn't the World First, as it's actually been done before - by a single player:
      Whether this is "end of expansion" type activity or just some usual clean fun, it's always great to see players just doing their own thing and finding their own fun in WoW!
    • By Starym
      After the recent survey that went out and talked about interest in the Burning Crusade Classic, we now have a fairly reliable source talking about more news on the much expected continuation of Classic coming before the end of the year!
      Nano, formerly a core staff member of the Nostalrius private server team, who had a meeting with Blizzard about how they made their server while Vanilla Classic was being developed, tweeted this yesterday:
      While he may theoretically have been referring to the survey, the tweet was posted significantly after it, so it seems more likely this is related to an actual official confirmation/announcement, especially since it refers to a schedule specifically. This comes after Nano correctly predicted/leaked the release schedule for Naxxramas, but also had a time set for the TBC Classic beta in said earlier leak:
      So this source has been pretty reliable in the past, and this tweet sure makes it sound like we won't have to wait for BlizzConline to hear about the Burning Crusade coming to Classic!
    • By Starym
      Blizzard have timed their releases very tightly, as Classic Naxxramas also seems to hold/produce a river of souls of its own... however a very different one than the Shadowlands Maw version. In both cases souls are going to their doom, although in Classic at least they get to have their bodies back!

      Source.

      Source.
      Just in case you're not quite sure what you're looking at, that's a whoole lot of players running back to the raid after death, in a very organized fashion, and it really does look like, and to some extent is, a river of souls.
      And here's the real one from the Maw for comparison:

      (Image courtesy of Warcraft Radio)

      Interestingly, none of the souls in retail seem to be screaming about having to go back to Naxx and the Four Horsemen.
×
×
  • Create New...