Jump to content
FORUMS
Sign in to follow this  
Staff

Frost Nova and Other Root Effect Break Damage Bug Solved

Recommended Posts

58555-no-guild-banks-at-burning-crusade-
 

Blizzard have found the culprit behind a BCC beta bug causing Frost Nova and other root effects to take too much damage to break and will be applying a hotfix before the first Burning Crusade Classic Arena season starts! 

Blizzard LogoFrost Nova Hotfix (Source)

We’ve gotten a lot of feedback about how much damage is necessary to break an enemy trapped in a root-effect, such as Frost Nova. Beta testers reported that it took too much damage to break root effects, and it turns out, they were correct. It took quite a bit of sleuthing to find the issue, but we ultimately found a bug that explains the odd behavior we saw in the Beta, and we should be able to fix it well before the first Arena season.

The Story

To start, one of the reasons this was such a challenge to find is that the behavior is intentionally random. There’s no fixed amount of damage that’s necessary to break roots; there’s a range of damage that might be necessary, which makes it a risk/reward calculation for the players. Reproducing the issue isn’t guaranteed, and testing it can look like normal luck streaks.

When this was first reported, we looked at the scripts on the spell, and verified that they matched the original data, which led us to initially conclude that this was just random luck streaks. However, we’ve seen previous examples of there being a deeper layer to issues like this one, so when the bug reports continued to come in, we knew it warranted further investigation.

What we’re looking at are scripts that are in data, so we can be confident that those match 100%. At the same time, we’re not using the exact same code as was used in 2007, so sometimes we see issues caused by steps we’ve taken to make the original data and the current code compatible with one another. Our next step was to examine the inputs to the spell script and verify that we really were sending all the same information for the script to evaluate. After completing an audit of that data, we once again concluded that this appeared to be just random chance. The data values that our code was sending the script matched, the things it did with the results from the script matched, and the script itself matched.

Everything we looked at appeared to be correct on all fronts, so after a second investigation we once again concluded that the random calculation was correctly matching our intent.

But it still felt wrong.

This is the point where uncovering a bug gets really challenging, and where sometimes we hope to get lucky. It turns out that after continuing to look at the bug and test it in the debugger, we saw an odd behavior: when the Waterbolt landed on a target that was in a Frost Nova, it was evaluated as though it was a melee attack, which is not correct. That turned out to be the clue that led us to the truth. There was no bug in the root-break calculation, the bug itself was a random.

The bug that would sometimes send the incorrect damage source to the formula. And since it wasn’t incorrect every time, we missed it on our code evaluation. It turns out that melee attacks are significantly less likely to break roots than ranged attacks are, and the bug was that ranged attacks could randomly be treated as melee attacks under certain hard-to-reproduce conditions.

The Conclusion

What made this such a challenge to find was that it was a randomly occurring bug in a system that behaves randomly when it’s working correctly, and two sources of randomness combined to confound us.

Thank you to everyone out there who helped us find this one!

A Hotfix is on the Way

One interesting aspect of this is: with this fix, the chance to break roots with damage will actually be slightly higher than it was in the first season of original Burning Crusade in 2007. This is because we’re using the 2.4.3 data, which raised the chances for damage to break roots slightly on targets above level 60.

But don’t throw away those mage alts! They still have Ice Block, too.

Share this post


Link to post
Share on other sites

This will be interesting to see, as Asmongold's TBC tournament was won by Hydra's team, with Warlock Mage Priest, which clearly benefitted a lot from this bug, so I wonder if Mage dominance will go down to the expected levels of RMP and such being the meta comps rather than just full ranged frost nova'ing someone 100-0.

  • Like 1

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
      Here come the final hotfixes of the week.
      June 18 (Source)
      [With regional restarts] Area 52 Bruisers are no longer shirking their job duties and will now intervene to break up nearby fights. [With regional restarts] Fixed an issue where repeatedly clicking a Soulwell would unintentionally consume additional charges under certain conditions. Fixed an issue where a Priest’s Prayer of Mending would persist on the target if it fails to find a new target to jump to, true to reference behavior. Activating Prismatic Sphere’s cooldown should no longer put enchanting materials on cooldown. Fixed an issue where Socrethar was not made vulnerable by Voren’thal’s Presence for “Turning Point.” The Aldor will now come to your aid during the quest “Deathblow to the Legion.” Fixed an issue where Halaa Battle Tokens were not granted as expected. Fixed an issue where Warchief Kargath Bladefist could charge outside of his area and reset the encounter.
    • By Staff
      As you might have read here today, a recent bug with the launch of Arena Season 1 saw players be able to acquire Season 2 rings for a brief period of time and the Classic community has been in an uproar over it. Now Blizzard are confirming that they're currently in the process of removing the items (and refunding the honor) from the 81 players that bough them. There will be no other consequences.
      Season 2 Rings (Source)
      On Tuesday, a bug with our initialization of Burning Crusade Classic Arena Season 1 made three Season 2 rings available on Honor vendors on NA realms for about two hours before we hotfixed the situation.
      We immediately got to work designing and implementing a process for identifying the 81 players who purchased the Season 2 rings and reversing their transactions.
      That process is underway at this time. All Season 2 PvP gear that was inadvertently available will soon be removed, and the Honor spent refunded.
      As always, we appreciate everyone who reported it to us, so that we could act quickly to ensure fair play.
      Thank you!
    • By Starym
      Today's hotfixes bring raid changes and fixes, for Magtheridon's Lair as well as Karazhan, in addition to a Warlock Arena fix and more.
      June 17 (Source)
      Warlocks are no longer revealed on the arena frames if they sacrifice a demon before the gates have opened. Magtheridon’s Lair Fixed animation issues with Blast Wave and Quake. Blast Nova now always has a raid warning when cast. Blast Nova will no longer be immediately recasted if he was interrupted before he began channeling. Developers' note: Magtheridon's Blast Wave was set up in original Burning Crusade in a way that it was possible for players to see a raid warning for an attack that would never come, or for Mag to use an ability without warning. These misbehaviors were recreated in Burning Crusade Classic as we matched the boss configuration with our pre-nerf reference. With the fixes above, we've made it so that Blast Wave is used consistently after a raid warning, and no longer fails to be put on cooldown if interrupted during its cast. Karazhan Fixed an issue where Shade of Aran's Dragon Breath was dealing more damage than intended. Fixed an issue where the title "Champion of the Naaru" would be repeatedly granted to players who had earned it.
    • By Starym
      It seems some switches were turned on a LOT earlier than intended and the Burning Crusade Classic PvP vendors were selling some Season 2 gear pieces for a short time. Plenty of players got their hands on them, many of them streamers, and now there's a public outcry that said items haven't been removed yet.
      Not all Season 2 gear was available, apparently only off-set gear pieces were (or just the one ring, it's unclear at the moment), as one particular streamer seems to be using the epic version of the Veteran's Band of Triumph (as only the rare version if available at the moment):
      As you can see, the title and most of the comments in the thread above (and others) seem to assume that the items won't be removed, but that seems impossible, despite the fact it's been a few days since the bug occurred. Especially with Blizzard's recent fairly aggressive action with the Karazhan Chess resets, the AFK battleground and bot banwaves, it's extremely unlikely this doesn't get addressed very soon.
      Now, that doesn't mean anyone will be getting suspended here, as what seems to have happened is that the PvP vendors were simply offering the Season 2 gear for a while, and players could normally buy it, without any additional action on their part. An argument could be made that some players knew better and abused the bug, carrying the gear into Arenas and getting an unfair advantage for just being in the right place at the right time, but Blizzard can't really assume that's ALL the players that bought this gear. An unknowing player that didn't think much of the significantly better stats on the item could just Have bought it naturally and perhaps not given it a second thought. It would be pretty hard to prove otherwise (despite it being pretty obvious for some players), and would require going on a player-by-player basis, which just seems very impractical.
      So the best we can hope for is a swift removal of the items in question, whether with or without a refund of the marks and honor spent to buy them. But it seems clear that this will happen, perhaps a little too slow for some, but the current doomsaying in the reddit threads is just a little ridiculous, as it truly seems impossible that Blizzard won't address this.
    • By Starym
      Blizzard are bringing the banhammer down in BCC, but this time using a measured and careful approach, as some players have been suspended for significant amounts of time for exploiting Karazhan, but others that did the same thing are not, and it actually all makes sense.
      As initially mentioned by alecn and many others in several reddit threads, there's two things going on here and three groups of players. First off, the key thing is that the Chess event is (was?) exploitable, as players could reset it and basically get the same loot again, repeatedly. Unfortunately there was also a bug that saw the doors to the Chess room closed if the raid left the instance after the encounter was completed (as many did to resume at a later time), and so the only option was to use the exploit and reset it in order to gain access to the rest of the raid.
      We then have the three separate player groupings that used the exploit for different reasons and in different amounts:
      Players that abused the exploit and reset the event many times, who received suspensions (possibly a 2 week default, or based on previous infractions, we don't have enough data to be sure) and most likely/almost certainly got all the extra loot removed. Players that used the exploit once due to the door bug, who did not get any suspensions nor got their extra loot taken. Players that used the exploit a few times in order to get more loot (in one example so they could actually clear the raid that week, as they were lacking gear). There are players reporting doing it 3 times and not receiving any punishment. And so Blizzard acted pretty swiftly, didn't overreact and just suspend everyone, and seem to have done about as well as could be expected. There may be an argument for the 3-reset crowd needing to at least get their extra gear removed, but that's most likely a VERY small number of players. The relative caution in handing out the suspensions is especially good to see after the recent problematic bot banwave which caught many players that were simply using Console Port (which you can read more about here)      .
      Source.
×
×
  • Create New...