Jump to content
FORUMS
Sign in to follow this  
Starym

Hunter Beta Issues - Not a Bug, Fixed and Actual Bugs

Recommended Posts

48aSMPZ.jpg
 

We have a large post over on the WoW Classic beta forums where Blizzard are addressing all the outstanding issues with Hunters. We have a huge amount of problems listed below, from the now expected "not a bug" things players report that are actually working as intended, to bugs that have already been fixed or will be very soon, and actual bugs that aren't fixed yet but are on the known issues list.

Blizzard LogoHunters (source)

Greetings!

Since the beginning of beta, we’ve seen a lot of bug reports around the Hunter class in particular, and we’ve been working diligently over the past weeks to shore up some of the issues that players have been reporting to us. We felt that it would be helpful to post an update on our progress as well as to clear up some confusion around issues that were reported that are behaving consistently with the Reference client and are not considered to be actual bugs.

The following issues are behaving as expected and are considered to be “Not a Bug” (we’ll be updating the Not A Bug list with these issues as well):

  • Hunter “dead zone” is working as expected and is consistent with the Reference Client
  • A wolf pet’s Howl buff is consumed by anything that causes damage, even if it does not benefit from the buff
  • A Hunter pet’s Bite and Claw ability damage will not change in the tooltip based on the happiness of the pet. The tooltip will always display the damage as if the pet were Content (yellow). This is consistent with the Reference client
    • Note: This was reported several times to us based on 1.2 patch notes which seem to have been misunderstood. The intent here is simply that damage displayed is what the pet would deal if it were Content, not what it deals based on its current happiness level.
  • Traps can sometimes not be triggered if a player moves over them very quickly (i.e. a Warrior’s Charge ability). This behavior is consistent with the Reference client.
  • Auto Shot does not make a sound when cast during the animation of Hunter’s Mark and certain other abilities
  • Scatter Shot and Freezing Trap share diminishing returns

The following reported issues are either confirmed fixed in recent builds, or we have upcoming fixes currently in testing:

  • Crocolisk pets cause noticeable server lag when summoned
  • Beast lore does not display the targeted creatures armor in the tooltip
  • Feign death does not immediately drop the Hunter from combat in a Battleground
  • Feign Death does not cause the Hunter’s health and mana bar to zero out as if the Hunter was dead
  • Feign Death does not kill the hunter if they stay feigned the entire duration
  • Hunters are performing a WalkBackwards animation while strafing left during Auto Shot
  • Hunters have the ability to tame pets 2 levels higher than the Hunter’s level
  • Hunter Pets do not auto-cast Dash or Dive when engaging their target
  • The Bonus Armor from Thick Hide is dropping off of Hunter pets shortly after talenting into it
  • Sending Hunter pets into combat with a special ability such as Bite does not also trigger your pet to begin attacking
  • Multiple instances of Hunter’s Mark can be applied to a target
  • Hunters are unable to cancel the animation associated with placing a trap by moving
  • Explosive Trap and Frost Trap place the hunter into combat each time they apply their associated effects or deal damage
  • Enemies will ignore collision when in combat with a player
    • Note: This isn’t hunter specific and was a global issue. This did affect Hunter pets so we listed it here
  • Pets do not display a “ding” visual when leveling up
  • Activating a Night Elf Hunter’s Shadowmeld racial ability at the same time that the Eyes of the Beast cast completes will give the player control over pet movement without snapping to the Pet’s point of view
  • Ranged attacks cannot be blocked
  • Training pets may cause your client to become unresponsive
  • The spell animation for flare is significantly different than the animation used in 1.12

Please note that this list is not comprehensive. There have been many other issues that affect hunters that have been fixed recently, and we are still hard at work fixing other bugs.

The following issues are confirmed bugs and are still Known Issues as of our current Beta build:

  • Hunter pets that died while the hunter was in a battleground are resurrected in an unhappy state when the battleground ends
  • Auto Shot does not animate or display a missile when it fires immediately after Aimed Shot
  • Aspect of the Pack will sometimes attempt to apply itself to mounted party members
  • When a Quiver or Ammo Pouch is equipped, the tooltip for Aimed Shot incorrectly reflects an attack speed bonus from the Quiver or Ammo Pouch that it does not actually receive
  • When taming a pet that teaches the Hunter a new Beast Training ability, the chat message does not report the ability’s rank
  • The Hunter’s quiver may occasionally appear in the Hunter’s hand instead of the Hunter’s equipped weapon

We hope to have fixes in place for these issues before launch, but please note that we can never guarantee when or if any known issue will be fixed.

Thank you all for your reports on the WoW Classic Beta so far!

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
      The honor system has been having a lot of troubles lately, but as we found out in the previous blue post, it's all just  been a display issue with the statistics which they are now in the process of fixing. Since a lot of players aren't trusting these findings/fixes and are convinced something is off for their honor totals, Classic developer Pazorax went in-depth to explain how the system actually works. He reiterated that honor has been calculated correctly this week and emphasized the long, long road towards the higher honor ranks, including a minimum 12 week journey to the very top, and that's only if you're the very best in your faction ever single week.
      Honor (source)
      I know the honor system can be frustrating, and even more so if it feels like you’re not getting credit for your efforts, so I wanted to post and let you know we are looking at people’s honor for the week, and so far all the checks we’ve done indicate that honor was calculated correctly this week.
      As we mentioned before, our data repair job on Monday caused the “This week” totals to display an inflated value for the rest of the day, and that appears to explain a lot of the confusion we’ve seen so far.
      We also know that some players confuse “estimated honor” with actual honor (estimates don’t account for diminishing returns), or confuse honor with rank (honor is earned from kills, rank is based on your relative standing within your faction). The honor system is slow to progress you through the ranks, even in the best case, so many of these reports aren’t a case of the honor going “missing” as much as they’re a case of an unforgiving system giving you less progress toward a rank than you were expecting.
      In addition to being based on your relative standing within your faction, your progress to the next rank also slows down as you reach higher ranks. Achieving the same standing each week won’t award the same amount of progress toward each rank, it awards a fixed percentage of the delta between your current rank, and your current standing. It is actually impossible to achieve rank 14 in less than 12 weeks, and that assumes that you’re the top player on your faction for every one of those 12 weeks.
      Those are all intentional behaviors, and are not bugs, but they can all contribute to a feeling of difficulty progressing through the ranks.
      We also see reports of missing kills when you’re playing during the daily reset job, and we’ve checked that too. In fact, I just checked right now, on some of the people who reported errors in this thread, and last night’s job did calculate their honor correctly. Those kills are still there, its just a display issue, and they’ll show up on the next day’s daily report now that the underlying issue is fixed.
      We are continuing to investigate, but at this time we don’t see any problems in the week 3 data. Once we conclude this investigation we can move on to investigating the problems that occurred during week 1 and 2, and we’re beginning to do that now.
      Thank you again for your patience as we work through these issues.
    • By Stan
      Free Character Moves are closing for all WoW Classic realms on December 5-6. Will paid character transfers be announced soon?
      Blizzard said they were considering paid character transfers in WoW Classic back in September because the service was available in original WoW, but no other paid services beyond that.
      Blizzard (Source)
      Piggy backing on this...will PAID transfers also be a thing should a server drop heavily in population and a player wishes to move to find more activity or reconvene with friends on another server.
      We're considering integrating a character transfer service once players have reached higher levels. This was available in the original WoW. We'll look at the rules we imposed at that time and also discuss the implications of players moving to a new realm. We believe realm identity is an important aspect of Classic so any guidelines around transfers should support this belief.
      Will there be paid services for Classic?
      We aren't considering other services beyond character transfer at this time.
      While we have no specific details to share at this time, Free Character Moves that have been available since the launch of WoW Classic are going away this week, and perhaps, we're not too far away from paid character transfers being integrated into WoW Classic now that players will be locked to low-population servers.
      EU
      Blizzard (Source)
      On 6 December at 1:00 a.m. CET, we will close the Free Character Move service for all realms in this region. We suggest that any player who has not yet taken a planned Free Character Move please do so as soon as possible.
      Thank you very much!
      US
      Blizzard (Source)
      On December 5 at 11:00 a.m. PST (2:00 p.m. EST), we will close the Free Character Move service for all realms in this region. We suggest that any player who has not yet taken a planned Free Character Move please do so as soon as possible.
      Thank you very much!
    • By Stan
      Last week, we reported about a bug in WoW Classic which caused Honor not to calculate between 3-7 AM. Blizzard has now replied that the bug has nothing to do with the previous caching issues and they're pretty close to fixing it.
      The issue was apparently caused by the daily honor script running before the end of the day, causing it to miss kills that haven't yet happened. The good thing is they have all the kills recorded, even though you can't see them in-game, so you won't lose any Honor when this is fixed.
      Blizzard (Source)
      It would be nice to have a blue at least respond saying there is an issue…
      I agree, but unfortunately, we didn’t have the chance to respond sooner. We’ve been investigating, and can now confirm that yes, this is a separate issue, that’s not related to the caching issues we were experiencing previously. The caching issues made it more difficult to uncover this issue, and I appreciate the detailed reports of which kills were missing and over what time range which helped us track this down.
      We’re getting pretty close to fixing this, and it turns out it was caused by the daily honor script running before the end of the day, causing it to miss kills that haven’t yet happened. But worry not! Those kills are still recorded, they just weren’t getting collected into the daily statistics correctly, so they’re not displaying in-game for “yesterday” or “this week” kills/honor. The source of the issue appears to be a scheduling system treating a UTC time as a local time, and we believe we’ve found and fixed that problem a few minutes ago.
      We’re also working on a fix to repair the daily statistics which we’re hoping to run Monday, in advance of the weekly rank adjustment, so it will correctly count all your kills and honor correctly for this week.
      I want to stress, that we do have all the kills recorded, even though you can’t see them all in-game, and we’re working hard to get the weekly statistics correct.
      Thank you for your patience as we untangle this issue.
    • By Stan
      Players are currently reporting a bug in WoW Classic where Honor is not properly calculated between 3-7 AM. We're still waiting for a reply from Blizzard.
      Blizzard (Source)
      I’d like to apologize for being incapable of formatting this in a more legible manner. Hopefully I can get all of this information across.
      My friend and I have done a bulk of our play time during the hours of 3-8 AM PST. After much perceived loss of honorable kills disappearing and achieving extremely sub par honor returns every day and after weekly roll over.
      I then proceeded to catalogue my honorable kills and honor gains.
      My hypothesis being that in the time frame of 3-8 am there is a period where any gains are not being accounted towards weekly standing.
      My findings are as follows.
      Daily and weekly honor resets are happening at 3 AM.
      3-7 AM I had achieved 47 HK totaling 3800 honor.
      7-9 AM I had achieved 36 HK totaling 2800 honor.
      12-7 PM I had achieved 196 HK totaling 7400 honor.
      (All of this honor was calculated including diminishing returns)
      Now if I total all of these honorable kills and honor together; 279 HK 14000 honor.
      Now what happened during reset time of 3 AM you may ask? My total honorable kills were reduced to 213 and honor 9075.
      Obviously 3-9 AM period had rolled over an extra hour but let’s still go with those numbers anyway.
      Let’s take my total 279 HK and 14000 H and subtract my numbers I have gained during the period of 3-9 AM, 83 HK 6600 HONOR we arrive at:
      196 HK 7400 HONOR.
      Now obviously as previously stated I had gone over the 3-8 AM period by an hour with this sample. But it is closer to what was returned on reset than what I had gained.
      Then subtracting just 3-7 AM gains leaves us at:
      232 HK 10200 HONOR.
      Even closer to what was returned after roll over.
      I believe there is something wrong in the code in regards to when a day ends and begins. As current reset time for dungeon/raids is 8 AM, where as the old reset time and also the current honor roll over time is 3 AM.
    • By Stan
      In an effort to remove the ability of addons to extend players' senses and detect enemies, the in-game combat log range has been decreased and now only displays information for units that are within 50 yards of the player.
      The hotfix has been deployed to live realms earlier today together with the fix for Onyxia's buff which prevented buffs from stacking.
      Blizzard (Source)
      Earlier today, we deployed a WoW Classic hotfix to all regions:
      The in-game combat log radius has been fixed, and now only displays information for units that are within 50 yards of the player. This is closer to the original behavior of WoW 1.12, and should eliminate the ability for addons to extend players’ senses and detect enemy actions at a greater distance than intended.
      This fix does not affect text logs that the game outputs for raid parses.
×
×
  • Create New...