Blizzard is telling it how it is! Awesome stuff!Blizzard Entertainment
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.
This made me laughAngryparasite wrote: ↑5 years ago
Creature respawn rates are much slower than in Battle for Azeroth
-
centurion • Selexin • Angryparasite • teebling • Brhule • Evocati • Cowyousaid
"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."
Does anyone here remember that? I feel like I've never seen this in my life and I played vanilla all the way to TBC...I guess I don't remember it because it was only added in the very end?
Was it added in that patch then removed for TBC? Can’t seem to recall it either, but if it was in that small frame it would make sense to have no memory.
But then I am not sure why it was there at all if they immediately removed it.
This was always true, wasn't it? Thats the reason to choose gnome, to be less likely as a target.Angryparasite wrote: ↑5 years agoTauren’s hitboxes and their melee reach is slightly larger than other races.
If i'm not mistaken blizz removed this feature in further vanilla patchesAngryparasite wrote: ↑5 years agoBeing critically struck while using /sit to sit does not cause abilities like Enrage, Blood Craze, and Reckoning to activate.
So whats the problem?
yeah it is really hard for the most streamers to tell what a bug is because they played so much private servers.
Manofwar
Kampfzwerg
Mojo
When I saw the video about the Tauren hitbox I had to laugh. Blizzard gave the wrong people access to the beta...
Twitch Channel, feel free to take a look :)!
I think people are just surprised at how high warrior health regen is, that's all.
It's higher than expected?
So I guess the reason for that is that Warriors have a higher scaling with Spirit. (And other Classes might scale less). If that's the case stacking spirit would be even better than it was on private servers.
.
I get a *mic drop* vibe from that blue post
It's so funny to witness this kind of "Mandela Effect" where people were sure that something was working in a different way in Vanilla, and then the dev are saying : "Hmmmm no, it's working just as it did back then", and players are all like "whooooooooaaaat"
Where is the source post for this btw? Or were these individually collected from separate Blizzard posts?
Likes: 35
Blizzard made this because a lot of streamers were reporting things that weren't bugs as actually being bugs. Gross.
There's so many non-streamer players also in the beta. I really don't think that streamers are reporting the bulk of bugs (be they bugs or not), so for this you can probably thank your run-off-the-mill normal WoW player.
I also don't see any reason for negativity here. If anything this gave a good laugh, and I don't think anyone at Blizzard were ever doubting these "bugs".
Turns out aggro range is spot on according to Kalvax.
We saw many similar reports in the first few days of the WoW Classic Beta Test.
As a result, we ran a multitude of comparisons with our 1.12 reference client. In doing so, we varied the player levels and enemy levels. In conclusion, we didn’t see any discrepancies with aggro radius.
I’m adding this to our not-a-bug list / forum post.
Thank you for the feedback!
List has been updated again with these:
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.
Lvl 60
Lvl 35
I'm awed. Gnomes were awfully small back in Vanilla though to an extent where clicking on a gnome would be more difficult than other races. This meant something if you weren't good at tab targetting.
People were actually reporting gnomes to be bigger than in Vanilla. Which apparently turned out to be false.
-
Bumlebi • Selexin • Cowyousaid
- 1
- 2
