Parryhaste and raid bosses - Page 3

GravityDK · 12/05/08, 4:16 AM

Thanks Berthold, great contribution.

Could you, or anyone with the smarts to understand the code, answer these questions about the simulator:
- how does it determine 'wipe probability', does it assign weightings to probability of occurances such as when the healers cannot catch up with the incoming damage because it all came within one second, or assume the healers produce only a constant HPS and therefore any spiky breaches of incoming damage above that threshold produce a wipe probability?
- does it account for the reduced likelihood of dodging a parrygib due to the extra 1% or so avoidance that DW tank has thanks to the 1H itemisation?

I presume this statement are true:
- it does not account for reduced Death Strike self-healing, and probably doesn't account for DS at all

Berthold · 12/11/08, 7:50 AM

Originally Posted by GravityDK

Thanks Berthold, great contribution.

Could you, or anyone with the smarts to understand the code, answer these questions about the simulator:
- how does it determine 'wipe probability', does it assign weightings to probability of occurances such as when the healers cannot catch up with the incoming damage because it all came within one second, or assume the healers produce only a constant HPS and therefore any spiky breaches of incoming damage above that threshold produce a wipe probability?

As mentioned in my first post, it does no statistical probability calculations, but more of a "brute" force approach.
It simulates a real boss fight in 0.1 second steps:
1)Weaponswings are updated
2)if swingtime is over, the hit(MT and boss) is calculated (hit/parry/avoid). If hit-> deal damage, if parry -> speed up the others next attack
3) if hitpoints of MT are 0 or below-> increase number of wipes by 1.

4)every n-th 0.1 second step a heal is cast (depending on kind of heal). Increase current MT HP. Has a 10% chance, that the heal is not cast due to brainlag, out of range, AE stun/fear effects etc.
5) go to 1

This boss "try" is done until the MT is dead(increase number of wipes by 1) or 6 minutes are over(increase number of kills).
We now repeat this 10000 times to make sure we got a statistically stable number of wipes and kills.
The overall "wipe possibility" is then
#wipes/ (#wipes+#kills)

- does it account for the reduced likelihood of dodging a parrygib due to the extra 1% or so avoidance that DW tank has thanks to the 1H itemisation?

yep

I presume this statement are true:
- it does not account for reduced Death Strike self-healing, and probably doesn't account for DS at all

yep

T1mm4h · 01/09/09, 3:55 AM

Originally Posted by Gort

Because the ability of bosses to do that is a granular ability that can be individually toggled by Blizzard. As such, the discussion about whether or not an individual boss has a particular flag, i.e. "whether a particular boss has their attacks hasted by parry mechanics", which is entirely unrelated to the ability of any other boss to do the same.

To be honest, thought I never saw the original thread/quote, but think of it this way: Parry-haste used to or is a regular mechanic on WoW, thus instead of setting the flag as on for each individual mob they want with it (as in "X mob benefits from parry-haste"), they just flag mobs/bosses they want to NOT have the parry-haste e.g. X mob is flagged as not having parry-haste.

Hopefully that clarifies it a bit. No sense in Blizzard wasting time setting flags or even scripting something as flagged for a particular property when they can just put it in globally and divvy out what they don't want using it.

Also, I believe player parry-haste is still working because quartz seemed to reset when I've noticed it before. I haven't parsed anything however, is anyone able to verify this?

Quigon · 01/10/09, 2:37 AM

If you're really concerned with the parry haste flag and how it is implemented, there was another blue post concerning it in the days of the Mother Shahraz fiascos - when it was of large concern to the tanking community. If you hunt that down perhaps it would give more detail (and perhaps nothing at all) - but the idea was they would create such a flag, and I believe Tigole mentioned that the flag would disable parry haste for that particular encounter. This would imply that the haste was still native.

humbe · 01/14/09, 5:31 PM

I did some math on how much extra damage I expect to take due to parry-haste effect in order to weight how good expertise was for druid mitigation.

The calculations in detail are here: World of Warcraft - Evaluating druid tank gear

I hope I haven't miscalculated anything, but as it looks to me, like even with no expertise (but 10 expertise talent), a druid will only take around 4.3% extra damage on average, given 16% parry chance for boss. Druids don't hit that often though, so might be more for other tanks. Especially a duel wielding one.

I doesn't sound like that bad burst damage to me. There still has to be 60% of base swingtime between hits. A streak of non-dodged attacks sounds like a much bigger burst. Anyways, unless I got something wrong, I don't see expertise as a strong mitigation stat for druids.

Elimbras · 01/18/09, 2:57 PM

Take care that if you want to compare the survavibility of tanks, you should also take into account talents. With the same available gear, not all classes have the same stats.
Take also care that somes classes (read warriors) have more (and good) panic buttons for tanking. Since we are interested in the occurence of rare events, this can have an impact.

Kethas · 02/02/09, 2:22 AM

So when guessing which bosses Blizzard would disable parry haste for - surely they'd throw a bone to the folks working on the hardest encounter ingame, where the "main" boss's melee damage isn't even a major part of the fight, right?

Wow Web Stats

In particular, try 10, filtering for actions performed by Sartharion:

23:13'58.227 Sartharion melee swing hits Gingivitus for 464 Physical. (6154 Absorbed)
23:14'01.952 Sartharion Flame Breath hits Gingivitus for 11003 Fire. (4715 Absorbed)
23:14'03.293 Sartharion attack misses Gingivitus.
23:14'05.622 Sartharion Cleave was dodged by Gingivitus.
23:14'06.975 Sartharion melee swing hits Gingivitus for 7188 Physical.
23:14'07.490 Sartharion melee swing hits Gingivitus for 6890 Physical.
23:14'09.128 Sartharion melee swing hits Gingivitus for 8288 Physical.
23:14'10.445 Sartharion melee swing hits Gingivitus for 1550 Physical. (6154 Absorbed)
23:14'12.825 Sartharion Flame Breath hits Gingivitus for 16399 Fire.
23:14'15.172 Sartharion melee swing hits Tatsumasa for 8482 Physical.
23:14'16.723 Sartharion melee swing hits Frägment for 9747 Physical.

So. A 0.50 second swing timer. Interesting. Let's see who attacked in that time (excerpt):

...
23:14'06.881 Pawnstarr attack was parried by Sartharion.
...
23:14'06.975 Skammadix attack was parried by Sartharion.
23:14'07.123 Kistler Rupture was parried by Sartharion.
...

Conclusion: in Sarth10+3 (and, while not confirmed, presumably in Sarth25), Sartharion has parry haste enabled.