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 Starym
      Ever since the gong was rung and all the Qiraji started busting out of the ground and the potential Scarab Lords started trying to finish up their quests, it's been a wild and crazy time down in Silithus, and we're going to take a look at some of the highlights!

      We start off with the biggest bang, as one of the giant bugs was pulled into Cenarion Hold, where it proceeded to detonate the entire settlement and players in it in a very spectacular way:

      Then we have the case of the ACTUAL 10 hour war, where a whole lot of Horde players on Sulfuras got a little upset with the resident "bigtime" guild, GRIZZLY FROM REDDIT (who also provided almost all of the War Effort mats), after said guild decided to  abuse mass reporting to prevent other guilds/players from getting the Scarab Lord quest completed. They way they chose to express their anger was quite spectacular, as hordes of Horde gathered outside the Caverns of Time and kept Anachronos in combat, while defending him from Alliance interference so they couldn't turn in the quest. For 10 hours straight.
      While they managed to succeed in preventing GRIZZLY from getting their Scarab Lord, unfortunately there were a few other Alliance guilds trying to complete the quest as well, but they were also prevented from doing so, despite a few attempts by the Horde to let them do it, but the GRIZZLY GM was always close with a rez so they couldn't risk allowing the dragon to be out of combat. One player that fell victim to all this and didn't end up completing his quest, after all the effort put in, was Snub from the guild High Council, who was trying to get to the dragon for a long time:

      Then we have some nicer stories, as many servers managed to ring their gongs without too much incident, and we see the entire trip, from finishing off Nefarian to the actual ringing on Icendius beliw:
      And a few nice shots from Skeram, Earthfury, Netherwind, and Sulfuras itself, either just before or after the ringing:




    • By Starym
      Update: two more guilds have downed C'Thun, as Fusion and Rise take US spots 2 and 3.

      They really should have waited another 2 minutes. While ONSLAUGHT aren't quite done with AQ 40 yet, they have cleared the final boss already, with the bug trio, Viscidus and Huhuran remaining and being cleared now. Skeram was also the first server to open the gates, which makes sense as this is the US first kill for the endboss. The setup was 13 DPS warriors, 4 rogues, 2 hunters, 5 mages, 4 warlocks, 2 warrior tanks, 5 resto shamans, 4 priests and 1 resto druid.
      It took the guild 38 minutes and 14 seconds to down the old god, and you can check out their clear below:

      Fusion and Rise have also managed to down the old god, as Blizzard confirms and congratulates the top 3:
      C'Thun Kills (source)
      Congratulations to the first guilds to kill C’Thun in this region: Guild Realm Time Onslaught Skeram 20:08 PDT Fusion Incendius 20:31 PDT Rise Netherwind 20:43 PDT Very impressive!
    • By Starym
      Update: the issue has been fixed in today's hotfixes!

      As the Chinese servers have opened the gates and cleared AQ40 already, players have noticed a discrepancy in C'Thun's eye beam behavior when entering the room, and it turns out the reason why it's different in Classic is quite the coincidence and an interesting story. As noted by many, when entering C'Thun's room, the giant green eye beam seemed to have a 10 second delay before firing, which makes entering the room, one of the more challenging tasks in the original fight, trivial. Clearly this is different than in Vanilla, and with Classic's #nochanges policy, it's very strange this would get purposefully altered. But it turns out, it wasn't.
      As redditor lonelyman1968 explains, what actually happened was that Blizzard's reference client was coincidentally taken from a several week period when a temporary hotfix was applied to the beam to counteract another bug that occurred with patch 1.12 (the Classic reference patch, which was significantly after the AQ patch, as we'll recall), which made entering the room much harder than intended. This bug got a proper hotfix a few weeks later, but the reference client for Classic is in the middle of the "band-aid" hotfix period, which is why the range on the beam is smaller, meaning C'thun targets players much later, making the encounter significantly easier. Here's the full explanation, by lonelyman1968:
      C'Thun Eye Beam Hotfixes (source)
      Taken from this thread by user Blntd - https://eu.forums.blizzard.com/en/wow/t/cthun-beam-delay/170783/65
      On August 26th 2006, a bug was discovered by Blizzard that made entering the C’thun’s room significantly harder than intended, as explained in this blue post from Tigole (Jeff Kaplan):
      (I can’t include links in my post but if you just google the quote you will find the blue post, it is archived on mmo-champion).
      As explained in the same blue post, they instantly applied a fix that reduced the “range” of the beam when players entered the room. This is the version we have now in classic.
      A couple of days after, on patch 1.12.1 (September 27th 2006), they implemented a “clean” fix of the original bug, and reverted the hotfix, making C’Thun work properly again (beam goes out as soon as someone peaks at the entrance). Again, it is explained in the blue post:
      TL;DR: It is consistent with the reference client…but the reference client is a snapshot of a hotfix that was patched in a matter of weeks, and is not a reflection of how the fight is supposed to happen in vanilla.
      And if you're interested in knowing what the actual bug was that triggered all of this back in 1.12, here's chandrasekharr with the explnanation:
      The Eye Beam Bug (source)
      From theemus in another thread:
      Hopefully Blizzard will revert this change ASAP!
    • By Stan
      Blizzard congratulated the first few gong ringers on Classic servers that have completed the Scepter of the Shifting Sands questline and started the 10-hour war.
      (Source)
      Since the launch of WoW Classic 12 months ago, we’ve been looking forward to this day with many of you. We watched along this morning as intrepid adventurers on five realms in this region completed the Scepter of the Shifting Sands questline, went to Silithus along with hundreds of others, and rang the gong, starting the 10 Hour War.
      Congratulations to the first few gong ringers on each realm:
      Player name Guild Realm Souffle Amnesty Sulfuras Flashmob Limitless Sulfuras Danaima Benediction Sulfuras Varkings Onslaught Skeram Eriuc SPACEFORCE Skeram Örc Unstable Skeram Aiggaa Fusion Incendius Vyrcee Pretty Good Incendius Boh Hazard Incendius Zhava - Netherwind Slaydex Deadbeats Netherwind Yoinkers Scuba Cops Netherwind Macaronii HELL YEAH BROTHER Earthfury Virtua Parry Haste Earthfury Bzmode HELL YEAH BROTHER Earthfury We’ll see you in Ahn’Qiraj later today!
    • By Starym
      As the Chinese servers got the weekly raid reset first, they've been able to enter AQ40 and push though (after a bit of an early start that was thwarted by Blizzard)! They cleared the raid in a few hours, with some interesting pulls and weird attempts at a nature-resist-gear-free Huhuran, but finally managed to down C'Thun, technically World First for Classic, but since the different regions get the raid at different times, we can't really call it a true WF.
      Prefoxfox from APES was kind enough to re-stream several Chinese guilds from theor own Doyu platform, so we can check out a whole lot of raids, including the first C'Thun, which has been marked below.

      You should definitely look through the rest of the VoD, however, as there are some really interesting and weird strategies going on.
×
×
  • Create New...