Enchant Weapon: Blade Ward - testing results

[MrDuck]

Heya,
so i applied this Blade Ward thingy to my last laugh and went to Ulduar to let XT002 play with me a bit. It was long 4 hours of wipes to these 250k hp enrages, so I've got plenty of reports from that fight.

In the end, the reports from 19 attempts (each lasting 4-6,5 minutes) all show average uptime of 17-25% on the blade ward buff. That's looking pretty good to me, from testing on dummy I expected it to be much less.
About damage done by the enchant itself, there was one report showing just under 1k from it (so yeah, it procced once-.-), but usually it was around 7k damage per fight. Not much, nothing to get really excited about, however, it's still free threat.

If anyone wants some more detailed information, or actual combat logs, feel free to ask for it

[Fridmarr]

Actual combat logs would be great. If you don't want to post them here publically, you could PM them to me.

[fuzzygeek]

I just did a n10 with a bunch of alts.

http://wowwebstats.com/rmc4xkuxqhvfa

Blade warding itself:
http://wowwebstats.com/rmc4xkuxqhvfa?ab=64440

[Varmin]

Can you post a log of you auto attacking a target dummy for 30mins+? =P

[steadypal]

Can you post a log of you auto attacking a target dummy for 30mins+? =P

target dummies dont hit back and wont cause u to parry and drop it off or do dmg... u just want to test the ppm?

mongoose was great at 1ppm - 1.4ppm

[steadypal]

I just did a n10 with a bunch of alts.

http://wowwebstats.com/rmc4xkuxqhvfa

Blade warding itself:
http://wowwebstats.com/rmc4xkuxqhvfa?ab=64440

procced 135 times thats pretty decent.. and did almost 85k dmg eh


im seeing it procced 135 times but u only parried 86 times from the 10 seconds it was up,,, HMMMMMMMMMMMMMMM


more testing please, i thought it wasnt good but this is kinda making it look a tad better. idk tho

[Fridmarr]

I just did a n10 with a bunch of alts.

http://wowwebstats.com/rmc4xkuxqhvfa

Blade warding itself:
http://wowwebstats.com/rmc4xkuxqhvfa?ab=64440

procced 135 times thats pretty decent.. and did almost 85k dmg eh


im seeing it procced 135 times but u only parried 86 times from the 10 seconds it was up,,, HMMMMMMMMMMMMMMM


more testing please, i thought it wasnt good but this is kinda making it look a tad better. idk tho

Well looking at the bosses fights there is very rarely more than one proc per 30 seconds of fighting, so it seems to have a proc rate of 2ppm or less and it's only affected by autoattack. Mongoose is pretty good at a low proc rate, but it doesn't go away the first time you dodge after the proc.

EDIT: Looking at his total DPS time it was 135 procs in 114 minutes.

[steadypal]

eew so its been confirmed only our autoattacks proc it???? HOTR procs mongoose WTF


im hoping its a bug and parry proc isnt suppose to end the buff,,,

[Fridmarr]

eew so its been confirmed only our autoattacks proc it???? HOTR procs mongoose WTF


im hoping its a bug and parry proc isnt suppose to end the buff,,,

No, I'm not saying that. I'm saying that is what it looks like just based on the amount of time he attacked versus the number of procs. The fact that people have seen the buff stack suggests there's not an internal cooldown. I didn't analyze the data completely, just a quick observation based on DPS time to the number of procs.

[MrDuck]

Actual combat logs would be great. If you don't want to post them here publically, you could PM them to me.

Well i'll try to set up a webserver today and i'll throw you a link as soon as it's up.

[Ekko]

Managed to get Blade ward on Broken Promise (BB).
I haven't done any proc analysis/testing before so here's what I did:

Target: Level 60 target dummy (so I wouldn't miss)
Weapon speed: 2.5
Total time of test: 1800 seconds (30 mins) starting count from 1st hit.
Record method: yeah....just myself counting the procs =S I feel rested etc and would say I'm 90% certain I didn't miss any procs

Results: 32 procs over 720 hits over 1800 seconds (30 secs)
It can stack, therefore has no CD, low proc chance.

Here are the proc times in seconds:
86, 121, 151, 171, 193, 316, 329, 354, 384, 406, 436, 484, 667, 712, 716, 765, 768, 778, 820, 825, 994, 1184, 1241, 1281, 1311, 1326, 1474, 1531, 1561, 1701, 1761, 1779

Stacks occurred, as u can see, @: 716, 768 and 825

Maybe someone can find this data useful for some proper summary/conclusion on bladeward's threat/mitigation.

[Ekko]

eew so its been confirmed only our autoattacks proc it???? HOTR procs mongoose WTF

Just confirmed this to be false
Sat there spamming HotR at a dummy while not hitting it, eventually got a proc.

[Fridmarr]

eew so its been confirmed only our autoattacks proc it???? HOTR procs mongoose WTF

Just confirmed this to be false
Sat there spamming HotR at a dummy while not hitting it, eventually got a proc.

HotR causes an autoattack, are you sure you were able to prevent it? If it is procing off of HotR, that would suggest an incredibly low proc rate with your numbers.

[majiben]

Since when does HotR start an auto attack? In fact that has been a complaint about it.

[Fridmarr]

Since when does HotR start an auto attack? In fact that has been a complaint about it.

I can't say for sure, because I've always had mine macro'd, but it does.