Since the Daze condition was introduced in World of Warcraft, there has been a lot of confusion on the mechanics of the whole thing. Well, whether you’re one of those players who has a driving need to understand that (primarily considering you’ve probably had a nasty experience with it), thereupon you’re in luck.

The guys at Blizzard has caught on to the general confusion that that ability has been causing so they have decided to send Blizzard Poster/ Moderator Drysc to explain it. First up he gave a “short” explanation on how it works.

The chance to be dazed is determined by the character s base defense rating as compared to the mobs level, or technically the defense of the character versus the attack skill of the mob (which is always maxed at [5 x mob level]).

A level 70 mob would have an attack of 350 as compared to a level 70 s character defense of 350. The base chance is 20 and that lowers or raises based on the difference amoung player defense and mob attack, to a minimum of 0 chance, or maximum of 40 chance.

This formula is in fact altered to have a lower chance to daze characters below level 30. The chance to for a level 1 character to be dazed by an equal level mob is less than 1 , and the chance soon after scales up to level 30 where it reaches the base 20 (assuming an equal mob level vs defense at all times).

Of course, that is just the basic formula. So how does one go about with avoiding being dazed? Well, there’s no idiot proof method to stop dazing completely. Drysc recommends, “keeping a maxed defense rating the best thing you can do to keep from being dazed is to simply avoid the aggro radius of mobs you don t mean to fight.”

All in all, it’s not a very simple instruction to start with, but at least we now have a general notion from Blizzard themselves on how it works. whether you want to read Drysc’s full post on that, go on our read link to head by to the WoW forums. Now excuse us, as we try to go around the outland to see whether Daze is working as the developers hoped it would.

Original post by Enrico S.