Jump to content
FORUMS
Sign in to follow this  
Starym

Parry, Dodge, Miss, Block and Crit Issues in Classic Beta

Recommended Posts

Y5PdZCx.jpg
 

After all the "not a bug" issues that have been reported on the Classic beta, we thought it would be nice to take a look at a more serious report that actually takes some time to take a look at the issues discussed and present some proper evidence and data. Mirayne over on the official forums took time to detail some possible major discrepancies for parry, dodge, block, miss and crit values when facing higher level enemies.

Quote

Conventional wisdom about vanilla hit table mechanics includes the following:

  1. Mobs and players of equal level (more precisely, equal weapon skill and defense) have a base 5% chance to dodge, parry, block, miss (non- dual wielding).

  2. Mobs have (5 * Level) weapon skill and defense values.

  3. Each point of difference between defense and weapon skill changes those percentages by 0.04% per point (except miss, see below). For example, a player hitting a +3 mob (such as a raid boss) from the front without dual wielding will experience 5.6% chance for their attacks to be dodged, parried, and blocked by the mob. For the purposes of this discussion let’s stick to white attacks.

A guide on the old Evil Empire site claimed the source of the knowledge about 0.04% per point of difference between weapon skill and defense, and other information, came from the following three blue posts:

https://web.archive.org/web/20070105001622/http://forums-en.wow-europe.com/thread.aspx?fn=wow-blizzard-archive-en&t=7

https://web.archive.org/web/20070105001622/http://forums-en.wow-europe.com/thread.aspx?fn=wow-blizzard-archive-en&t=15

https://web.archive.org/web/20070105001622/http://forums.worldofwarcraft.com/thread.aspx?ForumName=wow-bugs&ThreadID=62388

Unfortunately these are no longer accessible, at least not that I could find so I can’t see the wording.

A few of us from one of the classic warrior discords have been doing some testing on beta to verify the hit tables and other mechanics work the way we think. The testing is slow going but we have some preliminary results. Good news is certain things like glancing blow chance and penalties seem to be consistent with previous understanding, at least for +5 wep skill and +0 wep skill. Some testing will need to wait until later beta stages (presuming level cap is raised).

However we have found some strange results for other parts of the hit tables. For each result we also report 95% confidence intervals. Admittedly sample size is lower than we would like but testing is tedious and time consuming to do manually. However, even at these sample sizes some important information can be gleaned.

  1. Parry appears to be much too high (13.61% +/- 1.18%) for +3 mobs (no extra weapon skill) and is more consistent with parry values from later expansions. This conflicts with the 0.04% from old blue posts.

  2. Dodge (6.73% +/- 0.86%) appears to match later expansion values (wrath, see below). This conflicts with the 0.04% from old blue posts.

  3. Block (4.52% +/- 0.71%) appears slightly lower than expected. This conflicts with the 0.04% from old blue posts.

  4. Miss (8.41% +/- 0.95%) unfortunately isn’t enough samples to resolve between three prevailing theories on base miss chance for +3 mobs (8%, 8.6%, and 9%), but it’s encouraging that there isn’t a huge surprise here.

  5. Based on the base crit (4.49%) for the “Antlered Courser” test, there appears to be an additional crit suppression happening for +3 mobs beyond the expected 0.04% factor. For that test we are seeing a crit of 1.34% +/- 0.6%. Similar results were obtained for the Giant Yeti test, though slightly different due to different paper doll crit. ~3% crit suppression for +3 I believe was a feature of later expansions but was apparently not seen in vanilla according to any old sources.

Combat logs and summaries can be found here:

https://github.com/magey/classic-warrior/issues/5

Additional references:

This site claimed parry was changed to 14% for +3 in cata pre-patch:

https://wowwiki.fandom.com/wiki/Attack_table?diff=2413116&oldid=2412483

This site claimed dodge of 6.5% for +3 mobs (wrath):

https://wowwiki.fandom.com/wiki/Expertise?diff=1923754&oldid=1918454

This site claimed 5.6% for dodge/parry/block/miss for +3 (5% for +0), perhaps based on the blue posts linked above

http://web.archive.org/web/20061115223930/http://forums.wow-europe.com/thread.html?topicId=14381707&sid=1

All of this leads us to the following questions:

Is it possible that the creation of the 1.13 client led to some accidental setting of parameters from later expansions?

Would it be possible to verify that the beta is behaving as intended, or misbehaving, by devs comparing to their 1.12 reference client?

Blizzard responded, but still don't have a direct answer:

Blizzard Logo Parry, Dodge, Miss, etc. (source)

Hi Mirayne,

First off, the QA team wanted to thank you for the exceptionally detailed report. This is a great example of a professional report that utilizes data to support a hypothesis. Well done!

Regarding the potential issue itself, the team is going to take a look at this tomorrow in the reference client and verify that the current functionality is consistent with 1.12. Thanks again for the diligent, detailed analysis!

So, will this one make it to the "not a bug" list or is there really something fishy going on with those combat stats? Place your bets!

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

well I can definitely say that dodges, parries, misses, blocks, glancing blows, spell resists and partial resists definitely happened hell of a lot more in classic than they do in modern WoW but it is entirely possible that the values are too high pending what the dev team finds.

Share this post


Link to post
Share on other sites
Uncommon Patron

I think it's amazing that a Classic player is taking the time and putting in the effort to glean these numbers from such tedious work. Someone give that human a medal, or a hug, or a medal with a hug on it. Something. Give them something.

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
      Blizzard clarified how PvP progression will look like when PvP Season Season 1 launches tomorrow.
      (Source)
      We’ve seen several questions recently about how PvP progression will look over the next few weeks, and we have answers.
      First and foremost, Honor is the new currency that was introduced with the Shadowlands Pre-patch. Players can earn Honor from honorable kills, Battlegrounds, Epic Battlegrounds, skirmishes, Arenas, and Rated Battlegrounds. Honor can be spent to purchase gear from Purveryor Zo’kuul in Oribos. This gear can be upgraded by Agressor Zo’dash for Honor. The upper limit of this kind of upgrade is determined by your Renown level, and players can hold a maximum of 15000 Honor.
      Conquest is an additional PvP currency. Players can earn Conquest from Battlegrounds, Epic Battlegrounds, Arenas, and Rated Battlegrounds. Players can spend Conquest to purchase gear from Zo’sorg in Oribos. This gear can be upgraded by Agressor Zo’dash for Honor. The upper limit of this upgrade is determined by your current highest rating bracket in Arenas or Rated Battlegrounds:
      Rating item-level Unranked 200 Combatant 207 Challenger 213 Rival 220 Duelist 226 There is a cap on how much Conquest can be earned during a season. This cap increases by 550 each week. This means that during week 1, the cap is 550. During week 2, the cap is 1100.
      If you earn 550 Conquest during week 1, you will then be able to earn 550 Conquest during week 2. If you earn no Conquest during week 1, you will then be able to earn 1100 Conquest during week 2. If you earn 400 Conquest during week 1, you will then be able to earn 700 Conquest during week 2. Finally, you should not have to wait for Conduit upgrades. Conduits appear at higher rank on the vendor automatically when your rating increases.
    • By Starym
      While the Threads of Fate isn't the most popular alt-leveling system ever, it still has some big benefits, and the biggest one, in case you weren't aware, is the fact that there are a couple of ways you can test out all the Covenants while playing.
      In case you didn't know, while in Threads of Fate you can actually swap your Covenant freely by talking to the Covenant NPCs in Oribos, same as you would after level 60, except this time there's no penalty or delay. There's no additional work to be done or anything similar, you can just freely swap your Covenants around as many times as you want while in Threads of Fate.
        
      The second method might be even more handy, as you can simply decide not to choose your Covenant at all, skipping the Choosing Your Purpose quest, at which point you will receive the related Covenant's abilities when you enter a dungeon or world zone! You should be careful to actually pick a Covenant before you finish any of the long-term Threads quests, as you don't want to miss out on the Renown you get from them.
      Both of these methods are extremely handy for testing out all your class Covenant abilities in your various specs under real circumstances, as you can freely swap while leveling and get a feel of how they fit in to each spec.

    • By Staff
      Some more class and Covenant tweaks in today's hotfixes as well as a Classic Naxx fix.
      January 20 (source)
      Classes
      Death Knight Blood Service In Stone (General Draven Soulbind) will now correctly trigger when the Death Knight dies due to Purgatory (Talent). Druid Druid Form sounds should now always match the visual when shapeshifting. No more cheetahs with a deep dinosaur voice running around out there. Warlock The Fatal Decimation (Necrolord Conduit) will now properly increase the damage of Decimating Bolt (Necrolord Ability) at Item Levels 213 and above. Warrior Arms War Banner (PvP Talent) will no longer rarely persist on players after the banner has despawned. Fixed an issue causing the second Mortal Strike from Mortal Combo (Conduit) to deal 20% less damage than intended. Covenants
      Kyrian Fixed an issue during the scenario "The Greater Good" where players who disconnected during the flight with Chyrus would not receive aid from Kleia, Pelagos, and Mikanikos, and would be unable to take a new flight to Elysian Hold. Fixed an issue where Athanos could fail to activate during the scenario "The Greater Good." Night Fae Fixed an issue for level 60 Night Fae players who were eligible for the Threads of Fate quest "Return to Oribos" where the quest start location would appear in the wrong area. WoW Classic
      Naxxramas Kel'thuzad will now reset if any creatures walk past the encounter door.
    • By Starym
      Here's another "things that should stop working when zoning in/out" glitch, as players can actually bring allied mobs with them into battlegrounds and potentially elsewhere as well!
      Traice2020 was doing the Retaining the Court Revendreth World Quest, where you gather some anima to awaken the Darkwing Rebels when a battleground queue popped. So far so normal, but after entering the battleground the awakened rebel was still there, following the player around and actually doing damage!

      Source.
      Apparently the Stoneborn does "pretty good" damage as well (no details on the exact numbers), and if you'll remember the quest, you can actually get quite a few of them with you (there doesn't actually seem to be a limit, with plenty of players having over a dozen during the quest), which would be very powerful in the battleground. It's unclear if this was a temporary bug and if it's just related to battlegrounds or if it can actually be used in dungeons, raids etc. But what is VERY clear is that it's an exploit and will almost certainly result in suspensions if misused, so don't try this at home. And obviously big thanks to Traice2020 for reporting the issue!
      Hopefully Blizzard can fix this weirdness before BGs get overrun by Stoneborn and it becomes and all-out gargoyle fight with a bunch of spectators on the sidelines. Although having now put that into words, it would be an awesome sight right? Right Rextroy?
    • By Starym
      Here's a new one, at least for me, as it seems you can do Mythic+ before level 60, without issues! This isn't one of those clever use/you have do do these steps situations either, as it works just as if you were level 60.
      Considering the screening process of Mythic+ runs, you MIGHT not get in to a PUG under level 60 (but hey, try it, should be hilarious), but if you have some really helpful guild mates like igelaffe, it is very much doable. While you still can't open the end of run chest, you can get the rewards in the mail afterwards, which is the same thing.
      The actual usefulness of it is debatable, but igelaffe's reasoning was to get a head start on max level loot, as they weren't going to make 60 before the reset, so why not do a quick M+ Theater of Pain for some Great Vault goodies! Here's the full story:
      With the loot issues we recently talked about, can you imagine the level 55 in your group actually getting a piece of gear while everyone else gets that wonderful 35 anima?
×
×
  • Create New...