Jump to content
FORUMS
Sign in to follow this  
Starym

The Final Not a Bug List Update Before Launch

Recommended Posts

45366-new-classic-wow-realms-opening-aug
 

The probably final update to the infamous "Not a Bug" list has arrived and we have a number of things from all over the place, from non-loot roll triggering chests to offhand Windfury procs, invisible quivers and, most importantly, the fact that logging into Classic or BfA while logged in to the other one will disconnect you!

Blizzard LogoNot a Bug (source)

Hi All,

I’ve just updated the OP with the following:

  • The chest at the end of the encounter with The Seven in Blackrock Depths does not prompt a loot roll. Beware of Ninjas!
  • Shield Slam and other off-hand abilities does not proc extra attacks from Windfury.
  • Logging into World of Warcraft: Battle for Azeroth while playing WoW Classic on the same game account will disconnect you from WoW Classic. This is true in reverse as well.
  • Other players do not see a Hunter’s quiver on their back.
  • Hunters can sometimes experience a slight delay before recasting Auto Shot after moving.
    • Note: There is a hidden “retry” timer that occurs if the hunter is moving when the normal swing timer finishes. This timer checks for hunter movement before trying to resume auto shot, and this timer refreshes every 500ms when the hunter is moving. This means that if a Hunter is moving and stops moving just after this timer refreshes, you need to wait until this retry timer checks again to validate that you are no longer moving before you resume casting auto shot. This is not a result of spell batching or server heartbeats, and is specific to the functionality of a Hunter’s Auto Shot and is consistent with Auto Shot functionality on the Reference client

And here's the full and updated list itself:

Blizzard LogoFull List (source)

As we’ve discussed before, the nature of WoW Classic sometimes invokes different memories for different players, and this leads to certain misconceptions for some about what is or isn’t working as intended.

The following is a list of commonly-reported gameplay in WoW Classic that is not actually a bug, and is working as we expect it to:

  • Tauren’s hitboxes and their melee reach is slightly larger than other races.
  • Being critically struck while using /sit to sit does not cause abilities like Enrage, Blood Craze, and Reckoning to activate.
  • Using the “Automatic Quest Tracking” option does not auto-track newly accepted quests. (It instead will start to track an existing quest once progress towards an objective is started.)
  • Warrior health Regeneration is working at the expected rate.
  • Quests objectives and points of interests are not tracked on the map or minimap.
  • Completed quests are marked on the minimap with a dot. (and not a “?”)
  • Feared players and NPCs run fast.
  • Standing on top of other players while facing away allows spells and attacks to be used.
  • Creature respawn rates are much slower than in Battle for Azeroth.
  • NPCs which offer multiple quests may inconsistently display them as a dot or a “!” on the available quests list. They were inconsistent in 1.12, and we’ve reproduced the exact inconsistency they had back then.
  • Quests that are too low level for do not show up as a “!” in the game world.
  • Available quests do not display a “!” on the minimap.
  • On level up, the message: “Your skill in Protection increased to 15” was added in 1.12.1, and we’re intending to keep that.
  • You are unable to Polymorph enemy targets that are tapped by players with whom you are not grouped.
  • At all levels of player characters and enemies, aggro radius is set to the intended distance.
  • Long quest objectives don’t have text wrapping.
  • Fall damage is equivalent to expected and verified values.
  • Broadcast text can be seen multiple times if multiple players interact with the same NPC.
  • WANTED signs do not have “!”, and are also not highlighted.
  • Player characters do not animate when looting/interacting with quest objects (e.g. collecting pumpkins).
  • Gnomes and Taurens are the correct size.
  • “Melee leeway” is working as intended in both PvE and PvP.
  • Cone of Cold is behaving consistently with the reference client.
  • Arcane Missiles does not put the caster in combat .
  • A Hunter’s Frost Trap ground effect will break Rogues out of stealth.
  • The Berserking Troll racial ability is behaving as expected and matches the reference client.
  • The pet that a Warlock has when initially logging into the game world does not restore a Soul Shard when dismissed by taking a flight path or moving out of range.
  • The trigger range on Hunter’s traps are reduced by Stealth when the stealthed player is a similar or higher level than the Hunter.
  • Soul Link cannot be dispelled by dispelling the Warlock’s pet.
  • A Warlock’s Succubus and Felhunter pet cannot cast spells if they are out of line of sight of the target.
  • Manually cancelling Stealth after using Vanish will remove the Vanish buff as well as the Stealth buff.
  • Escape Artist has a very small chance to fail when used to escape an effect that has a decreased chance to be dispelled (e.g. a Rogue’s Vile Poisons talent).
  • Rogues are not broken out of stealth by Blizzard until they take damage.
  • Taunting Hunter pets that are set to Aggressive or Defensive mode will cause them to attack the taunting player.
  • The threat generated by Battle Shout is not capped at 5 party members and is increased when affecting targets such as Hunter and Warlock pets within the same party.
  • The chest at the end of the encounter with The Seven in Blackrock Depths does not prompt a loot roll. Beware of Ninjas!
  • Other players do not see a Hunter’s quiver on their back.
  • Shield Slam and other off-hand abilities does not proc extra attacks from Windfury.
  • Logging into World of Warcraft: Battle for Azeroth while playing WoW Classic on the same game account will disconnect you from WoW Classic. This is true in reverse as well.

Hunter concerns:

  • 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.
  • 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, Wyvern Sting, and Freezing Trap share diminishing returns.
  • A Hunter’s Frost Trap ground effect will break players out of stealth.
  • The rate at which pet focus regenerates is not always consistent.
    • Note: While the actual amount of focus that can be generated per tick is inconsistent, the total amount generated over time is flat and consistent. There are slight variations in the time between ticks that cause this to display inconsistently.
  • Pet aggro radius is working properly and as expected. This is to say, it was extremely inconsistent in original WoW, and it remains inconsistent in WoW Classic.
  • Pets “remember” targets that they have been instructed to attack previously and when sending a pet to attack a different target, the pet will return to attack any remaining targets they were previously instructed to attack when the currently engaged target dies.
  • Pets that have been instructed to attack dead targets with a special ability or attack will attempt to approach and attack the dead target, but will return to the hunter’s side when the ability fails.
  • Other players do not see a Hunter’s quiver on their back.
  • Hunters can sometimes experience a slight delay before recasting Auto Shot after moving.
    • Note: There is a hidden “retry” timer that occurs if the hunter is moving when the normal swing timer finishes. This timer checks for hunter movement before trying to resume auto shot, and this timer refreshes every 500ms when the hunter is moving. This means that if a Hunter is moving and stops moving just after this timer refreshes, you need to wait until the retry timer checks again to validate that you are no longer moving and can resume casting auto shot. This is not a result of spell batching or server heartbeats, and is specific to the functionality of a Hunter’s Auto Shot. This is consistent with Auto Shot functionality on the Reference client.

We appreciate all of your feedback!

The list is sure to grow once the game is released, so we're looking forward to seeing what other problems aren't really real problems but intended problems!

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 Stan
      We have another interesting video where 33 Hunters defeat Onyxia in 58 seconds.
      Redditor Gunzbngbng explains that every Hunter with the 8/8 Tier 2 bonus adds 9 DPS to every other Hunter in the raid and the effect stacks, so if you have two Hunters, one with and one without the set bonus, it attributes 18 DPS, but if both hunters have the set bonus, it will be 36 DPS, meaning that every Hunter added exponentially increases the output of the set bonus. As a result, the players were able to kill Onyxia in just 58 seconds. Congrats to the speed kill!
      Card
      Logs are available over on WarcraftLogs.

      (Source)
    • By Starym
      Well, this was the inevitable final outcome of all the special raid compositions, from all druid to all paladin, shaman etc, the endgame has always been all naked it seems. We have 40 absolute madlads (and madladies) taking on Onyxia with nothing but their pride equipped (and one warlock who put on a trinket accidentally mid fight through an accidental key-bind click, so I guess the run is null and void!!11), so that's no weapons, gear, trinkets, nothing.
      It is a truly terrifying world out there with the crazy amount of world buffs indeed. As you'd expect, this is the least warriors ever seen in a Classic raid, as they tend to be pretty useless without weapons, but we did have 12 mages, 7 warlocks, 3 hunters, 1 ret pally, 1 shadow priest and 1 balance druid as DPS, 8 priests, 5 holy palas and 1 resto druid as healers and a single prot pala tank. Here's the Warcraft Logs page for more details and here's the video:
      Big congrats to them on this very fun achievement!
      Source.
    • By Starym
      We have a big change to the anti-botting measures put in place for instance farming, as the limit of 30 instances per day has been moved to a per-character basis instead of a per-realm one! It should be as effective against bots, but much less so to real players.
      July 8 (source)
      WoW Classic
      Time-based instance limits are now enforced per-character. Developers’ notes: The newer limit of 30 instances in a 24-hour period is an extension of the 5 instances per hour limit, which was tracked per-realm since it was first implemented in 2005. The intention behind both of these restrictions is to reduce the profits for new bots when they first come online and haven’t been removed yet. We’ve concluded that a per-character limit will be just as effective, while being less restrictive to legitimate players who have multiple characters on the same realm.  
    • By Starym
      The most recent Blackwing Lair fastest speed clear didn't quite last long, as we have a new best time! Progress are back on top, pushing faction rivals Onslaught down to second, as the Alliance guild clears BWL 23 seconds faster, downing Nefarian in 18 minutes and 51 seconds!

      The Blessings have outperformed the totems for now, and the raid composition saw the usual melee stack, with 22 warriors, 5 rogues,  6 priests, 3 paladins, 1 mage, 1 warlock, 1 druid and 1 hunter. You can check out all of the run's stats here.

       
    • By Starym
      Some players have been having issues getting the extra bag slots from adding an authenticator to their account and Blizzard have explained it's related to out of date addons:
      Bad Slots Fix (source)
      We have seen accurate reports of the new bag slots not appearing in-game, due to out of date addons.
      It looks like disabling addons reveals the new bag slots in that case.
×
×
  • Create New...