Aloha! Blizzard has put out a series of reports that players in the Classic beta are reporting a lot and… that it's not really bugs.
Players Report Bugs in the Classic Beta… .which are not
[blue author = »Blizzard» source = »https://us.forums.blizzard.com/en/wow/t/175887/1 ″]
-
As we've discussed above, the nature of Classic sometimes invokes different memories in players, and this leads to certain misconceptions for some about what works or doesn't work as intended.
- The range and melee range of the Tauren are slightly higher than in other races.
- Hitting yourself with a crit while using / sitting to sit does not cause abilities like Enrage, Bloody Mania, and Crunch Time to activate.
- Using the "Automatic Mission Tracking" option does not automatically track newly accepted missions. (Instead, it will start tracking an existing mission once progress towards an objective starts.)
- The Warrior's health regeneration is working at the expected rate.
- Mission objectives and POIs are not tracked on the map or minimap.
- Completed missions are marked on the minimap with a dot (and not a "?").
- Players and NPCs affected by Fear run fast.
- Standing on top of other players while your back is turned allows you to use spells and attacks.
- Creature spawn times are much slower than in Battle for Azeroth.
- NPCs offering multiple quests may inconsistently display them as a dot or a "!" in the list of available missions. They were inconsistent in patch 1.12, and we have reproduced that exact inconsistency that they had back then.
- Missions that are level too low not to appear as a "!" in the map.
- Available missions do not show a "!" on the minimap.
- When leveling up, the message "Your Protection skill increased to 15" was added in patch 1.12.1 and we intend to keep it.
- You cannot use Polymorph on enemy targets that have been marked by players who are not in your party.
- Agro radius is set to the intended distance at all player and enemy character levels.
The following is a list of the most common reports that are not really a bug, and are working as expected:
[/blue]