Someone put the wrong number in the text, that’s not a bug that’s someone not doing their job correctly.
Did you notice the crit is 6%?
Also known as a bug.
Hmmmmm…
I can’t recall the exact term for someone making a mistake in a computer program. Maybe you can help?
A bug is an unintended problem from coding, this is a typo mistake, a mistake is not a bug
Oh, that’s nice. So all I have to do to avoid bugs is using data driven design!
Thank you. Most illuminating.
What? a typo is not a bug “if a=1 to 10 than print a” will not work as a line of code but “if a=1 to 10 then print a” would. See? A SPELLING MISTAKE or typo.
So what you’re saying is that a spelling mistake led to a bug when attempting to execute it.
Look, you can’t just separate data out from the rest of the program and say “that’s not a bug if it’s in the data”. Of course it’s a bug. If I make an ability that instantly one-shots someone and somehow assign it to warlocks so they learn it at level 56, that does not make it any less of a bug in World of Warcraft, even if the WoW engine is behaving correctly by giving it to warlocks at level 56 and letting them one-shot people. Bugs are mistakes in computer programs, not just mistakes in computer programming.
Its a spelling mistake thats turned into a bug is that better ?
But if people read its for none tank druid changes it does not affect tank druids 
Where exactly does it say that? The datamining has looked at the effects of Bear Form universal for all Druids, not the Guardian specific one, because there is no Guardian specific Bear Form… so yeah.
And yes, that is better, because it’s the truth. A spelling mistake has caused a computer program to misbehave, therefore there is a bug in the program.
Because its not under the changes for guardian can you please go read and stop doing your usual and picking fault with my posts.
1 Like
… wow
It’s under the changes for Druid, aka it applies to ALL Druids.
What is written in a tooltip does not affect the mechanics of classes. If the tooltip said bananas bear form would not act like a banana.
This always happens: every PTR patch tooltip errors cause unneeded rage.
Save it for the weekend folks.
2 Likes
I know… doesn’t make it not a big though. It’s minor, yes. I don’t think it’ll go live with a situation where bears actually do have no armour. I know it’s just a tooltip error.
Just saw someone test druid bear on the ptr in a m+, they had this new talent that gives a proc of getting a ridicolous amount of armor, and it procced alot. Don’t remember the name since I don’t care for bear tanks, but I can assure you that they are alot better on the ptr.
I actually logged into the PTR and I copied my 102 druid and this happened
Feral: Night Elf form armour 221, bear form 707.
Guardian: Night Elf form 221, bear form 707.
Which is 319.9% so an increase of 220% approx. I win, it’s a typo by Blizzard.
The tooltip ingame said 6%, if only the data wasn’t just datamined, which is against Blizzard rules btw, but actually checked.
1 Like
It’s a bug that it says it’s 6% when it’s not. I already knew it just said the wrong thing while the implementation was still correct when I posted to you xD
No doubt in my mind.
Looking forward to it! Goodness knows, we need it.
If I can kill G’huun on a Guardian Druid as they are now and were during Uldir, surely I’ll become a wrecking ball when 8.2 lands. >:D
If you’ve ever played PvP there’s no way you can think this is okay
I did play pvp. I’m not good at it but I don’t play druid so it’s a good change imo.
Also I was obviously joking.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.