WoW Classic “Not A Bug” List


(Kaivax) #1

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.
  • Non-targeted, group, or AoE buffs will not affect party or raid members if you are flagged for pvp and your party or raid members are not flagged for pvp, or vice-versa.
  • It is much easier to not get quest credit for escort quest objectives in WoW Classic than in Battle for Azeroth. Follow your NPC allies closely to ensure quest credit is obtained!
  • Monsters will respawn more aggressively when reduced past certain thresholds of their original populations in many areas of the game. This is working correctly and is consistent with the reference client.

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!


"NOT A BUG" List from the Beta Forum
Exploits or Clever Use
/sit enrage still works according to a streamer
Food for Thought
/sit enrage still works according to a streamer
Level Cap Increase?
Mob aggro proximity
How Close is the Beta to Vanilla?
Tin Foil Hat Theory - The "Hit Box"
Is Paladin hard to learn in Classic?
Mining Agro Radius [Bugged?]
Character size display bug
A Loot Bug?
[New Bug?] Battle Shout
No Beta invite for people who played vanilla?
Hunters/mages? Leeway
Hunter Beta Issues Update
Hunter Pets
Is Scatter Shot really a long Mez?
Demoralizing shout/roar generating too much threat
Warlock, Mage Or Spriest?
Can Shadow Priests dispel a Warlock’s SL in Classic?
Can Shadow Priests dispel a Warlock’s SL in Classic?
Can Shadow Priests dispel a Warlock’s SL in Classic?
[POSSIBLE BUG] WARRIOR Demoralizing shout causing too much threat
Looting Bug
Demoralizing shout is bugged and it is why we have this AoE meta
Can we get a developer answer on this please?
Sit/Stand spam
WTB - Beta Invites
Beta NEEDS more testers
Question for people on beta
Open beta?
WoW Classic Closed Beta - Level 40 and Arathi Basin Testing
Feign Death + Trap Bug
Fear is busted
Class Skills? Huh?
Refunding a shard when taking a flight path?
(Reese) #2

Thanks for posting this.


#3

I’ve encountered what may be a bug, but I’m not sure so haven’t submitted a report. I’ve had several creature that have empty loot boxes after they are killed. I know the data base for classic had to be changed/converted to the new format to fit the current client so I’m thinking maybe something was missed. Should these be reported as a bug?


#4

I’ve encountered a couple of instances where there was a loot window, but no loot as well.


#5

Loot windows with no loot was normal in vanilla, from my memory. Only things that don’t drop any loot whatsoever didn’t sparkle.


#6

This list itself is pretty classic.


#7

LOL that’s great. Thank you for posting this.


#8

I did report a bug kinda along these lines, What would happen is on auto loot I would see the loot window pop up just long enough to see there was loot in it but not what it was then it would go away and I would get no loot.
So I turned auto loot off until the next time I logon to see if it is still doing it.


#9

lol This one actually made me laugh.


#10

Can we get this stickied please?


(Kaivax) pinned #11

(Azreluna) #12

The extent to which people misremember this game astounds me.

This is working as expected. Some mobs simply have no loot.

For the record…

This one is my favorite.


(Kaivax) #13

I’ve added this to the OP:

  • You are unable to Polymorph enemy targets that are tapped by players with whom you are not grouped.

(Kaivax) #14

I’ve added this to the OP:

  • At all levels of player characters and enemies, aggro radius is set to the intended distance.

(Azreluna) #15

I assume someone doesn’t remember aggroing a mob 20 levels above you from 150 yards away?


#16

Predicting Aggro range is hard, again. LOL.


#17

Time to reroll

In all seriousness though I’m both happy and sad because it means I can’t do it to other people and they can’t do it to me. Thanks for the clarifications. Both time and misinformation on the internet have made some things which are intended seem like bugs simply because videos from another patch, etc show us otherwise or we just forgot.


A Loot Bug?
(Kaivax) #18

I’ve added several items to the list in the OP:

  • 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.

The last one has been carefully verified.


#19

Hopefully not TOO carefully. Respect people’s personal space.


#20

I lol’d irl.