Meridia’s blessed armor set needs a nerf

SnubbS · December 2017

Meridias is the funniest set—I was in the middle of 30 people with proxy about to go off, then it misses and my destro misses every tick.

Juhasow · December 2017

VaranisArano wrote: »

Juhasow wrote: »

This set kinda destroyed meaning and fun of duels. Now every scrub can wear it in duel and be immortal.

I would reccomend to change the 5 piece bonus to for example Major Maim. That would made set usefull in PvE also while tune it down in PvP to the point it's reasonable.

You mean like the Knightmare set? http://elderscrollsonline.wiki.fextralife.com/Knightmare+Set

@VaranisArano You know the difference between words "major" and "minor" ?

generalmyrick · December 2017

ParaNostram wrote: »

This set definitely doesn't need a nerf. This set is underused as is, just because OP got frustrated and lost a fight and that person happened to be wearing this underused set does not mean it needs nerfed.

we all know how sensitive it is to have a good build and have it defeated by a gimmick...

love the set, actually i'm going to play it again!

danno8 · December 2017

Maura_Neysa wrote: »

Nelson_Rebel wrote: »

This set is incredibly stupidly broken. Whenever you block you have a 33% chance to cause all your attacker’s to miss ALL damage and attacks or effects of any kind for 5 seconds and occurs every 10 seconds.

This is a stupidly broken set that is what is helping to cause the perma tank cancer in BG’s and Open world cyrodill. This set has a near 90% uptime due to the HIGH percentage chance to occur, the short cooldown period between and the long duration to ignore every single effect (all damage and CC’s and anything else) on you while blocking...

Heavy armor and sword and board aren’t the problem in PvP. It’s sets like THIS and ravager and other stupidly broken things that cause pvp issues. So please ZoS do some QA on skill sets that are obviously broken, so you can stop nerfing PvE and PvP players

Actually you genius it has exactly a 16.5% max uptime making it only slightlty better than Hist Bark WHEN 1v1 and much less when 1vX
33% chance every 10 seconds for 5 seconds. So 0.5 x 0.33.
The upside to this set is that it allows a tank to apply their set to everyone.

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

Malamar1229 · December 2017

Keep spreading mis-info. It only causes misses for the 1 attacker who procd it. It performs great in duels but poorly in 1vX

generalmyrick · December 2017

cant wait to try out this reactive and meridia in battlegrounds!

Maura_Neysa · December 2017

danno8 wrote: »

Maura_Neysa wrote: »

Nelson_Rebel wrote: »

This set is incredibly stupidly broken. Whenever you block you have a 33% chance to cause all your attacker’s to miss ALL damage and attacks or effects of any kind for 5 seconds and occurs every 10 seconds.

This is a stupidly broken set that is what is helping to cause the perma tank cancer in BG’s and Open world cyrodill. This set has a near 90% uptime due to the HIGH percentage chance to occur, the short cooldown period between and the long duration to ignore every single effect (all damage and CC’s and anything else) on you while blocking...

Heavy armor and sword and board aren’t the problem in PvP. It’s sets like THIS and ravager and other stupidly broken things that cause pvp issues. So please ZoS do some QA on skill sets that are obviously broken, so you can stop nerfing PvE and PvP players

Actually you genius it has exactly a 16.5% max uptime making it only slightlty better than Hist Bark WHEN 1v1 and much less when 1vX
33% chance every 10 seconds for 5 seconds. So 0.5 x 0.33.
The upside to this set is that it allows a tank to apply their set to everyone.

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

Basic math, last 5 seconds, can proc every 10 Seconds, has a 33% chance. 0.5×0.33 = 0.165 aka 16.5% chance of this set being up when an attack comes in. Hist Bark is 15% chance to dodge an attack. Therefore in 1v1 situation Blessed Merida is 1.5% more effective for the wearer. In a 1v2 situation Hist Bark still has a 15% chance, Blessed is now only an 8.25% chance, half what it was before since it can only effect 1 person.

The set isn't OP, not even in a duel, where its on par with any other defensive set. What this set IS amazing for is a PvP tank, where your role is it to kill people and you don't need a survival set because you already are the survival. It allows you to effectively keep | person out of the fight whether we are talking BGs, open world Cyodiil or anti-zerging. A good tank regardless of content isn't just surviving, they are controlling the enemy, de-buffing the enemy and buffing allies.

I've run this set on my Warden tank since Morrowind dropped. I run a lot of CC, minor maim, major defile, a fair amount of healing. I 1vX (Some), open world and antizerg

Blessed in action in BG 2v2v3

https://youtu.be/Lipc4O9qgr8

Blessed in action in Cryodiil open world 1vX

https://youtu.be/a1maQEIHflM

TheMystid · December 2017

Nelson_Rebel wrote: »

SydneyGrey wrote: »

So this is yet another "everything that kills me in PvP has to be nerfed" thread.

*Yawns*

lmfao ok buddy.

I’m going to wear this set and go duel as many people on the server and upload a video and show you exactly why it’s broken as hell xD lololololol

I guess you're going to have a hard time having your dueling requests accepted.

Slick_007 · December 2017

danno8 wrote: »

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

your point is correct, but your math is wrong

Cage_Lizardman · December 2017

Slick_007 wrote: »

danno8 wrote: »

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

your point is correct, but your math is wrong

Sounds about right to me, maybe more like 5 out of 11.5, and normally you'd be doing more than one attack per second, so a more realistic uptime would be closer to 50% as long as you block at the right moments.

Maura_Neysa wrote: »

Basic math, last 5 seconds, can proc every 10 Seconds, has a 33% chance. 0.5×0.33 = 0.165 aka 16.5% chance of this set being up when an attack comes in.

This on the other hand, is complete nonsense. Back to grade school with you.

Maura_Neysa · December 2017

Cage_Lizardman wrote: »

Slick_007 wrote: »

danno8 wrote: »

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

your point is correct, but your math is wrong

Sounds about right to me, maybe more like 5 out of 11.5, and normally you'd be doing more than one attack per second, so a more realistic uptime would be closer to 50% as long as you block at the right moments.

Maura_Neysa wrote: »

Basic math, last 5 seconds, can proc every 10 Seconds, has a 33% chance. 0.5×0.33 = 0.165 aka 16.5% chance of this set being up when an attack comes in.

This on the other hand, is complete nonsense. Back to grade school with you.

@Cage_Lizardman go head tell me again how it’s up 5 out of 11.5 seconds

https://youtu.be/a1maQEIHflM

Thogard · December 2017

Maura_Neysa wrote: »

Cage_Lizardman wrote: »

Slick_007 wrote: »

danno8 wrote: »

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

your point is correct, but your math is wrong

Sounds about right to me, maybe more like 5 out of 11.5, and normally you'd be doing more than one attack per second, so a more realistic uptime would be closer to 50% as long as you block at the right moments.

Maura_Neysa wrote: »

Basic math, last 5 seconds, can proc every 10 Seconds, has a 33% chance. 0.5×0.33 = 0.165 aka 16.5% chance of this set being up when an attack comes in.

This on the other hand, is complete nonsense. Back to grade school with you.

@Cage_Lizardman go head tell me again how it’s up 5 out of 11.5 seconds

https://youtu.be/a1maQEIHflM

Wow, so you’re just doubling down on your hilariously awful math. I respect your gumption.

What your missing is that if it doesn’t proc in the first second, it can still proc in the second second... it’s not like if you block once and it doesn’t proc that you have to wait a full ten seconds again... (that is the only scenario your formula would work for, by the way, but that is not how blessed works)

Thogard · December 2017

The actual formula would depend on quite a few things but let’s simplify and say that A = blockable attacks per second, and let’s simplify further and say that that’s just 1.

So for the first attack we have a 33% chance to block it. If we do block it, we have 5s of uptime and 5s of downtown, for a total update of 5s / 10s. Odds of that happening are 33% so

.33 * (5 / 10).

But what about the 2/3 of scenarios where the proc doesn’t occur? We can still block again... that would be an uptime of 5 but downtime of 6s... 1s before proc and still 5s after, for a total uptime ratio of 5s / 11s. We have a 33% chance of proccing, but we have to remember that we only had a 2/3 chance of getting to this stage anyway, because in 1/3 of scenarios we would proc on the first attack

So we get

.33 * (5 / 10) + .66 ( .33 * (5 / 11))

And then we can repeat again, but this time it’s 2/3 of 2/3 probability since we’ve now had two chances to proc it...

.33 * (5 / 10) + .66 [ .33 * (5 / 11) + .66 { .33 * (5 / 12)}]

So the actual formula would go on like that infinitely. Fortunately there’s some nifty math we can use to simplify. Unfortunately there’s no easy way for me to do a sigma in B.B. code lol

It would be:

Limit (as n -> infinity, for all positive integers of n) of Sum of { [.33 * (5 / ( 10 + n - 1))] * [(2 / 3)^(n - 1)]}

The answer is 42.5997% when we assume one blockable attack per second.

http://www.wolframalpha.com/input/?i=sum+(.33+*+(5+%2F+(+9+%2B+n+)))*+((2+%2F+3)%5E(n+-+1)),+n%3D1+to+infinity

I’m so mad at myself for doing this on my phone lol. My thumbs hurt.

Maura_Neysa · December 2017

Thogard wrote: »

Maura_Neysa wrote: »

Cage_Lizardman wrote: »

Slick_007 wrote: »

danno8 wrote: »

Well if you do the math it is a MAXIMUM uptime of 50%, assuming it procs for five seconds every 10 seconds with some good luck on the 33% chance.

It would have an AVERAGE uptime of 38% (5 out of 13 seconds) assuming 1 attack per second and it procs on average every third attack (33%) of the time.

The MINIMUM uptime would be 0%, if you get an unlucky streak, which is less and less likely to happen the longer the fight continues.

Nonetheless the 90% uptime the OP came up with is completely impossible, based on the set description and the fact it procs only on one opponent at a time.

If this set was able to proc on more than one opponent at a time, it would be the best defensive set in the game hands down.

your point is correct, but your math is wrong

Sounds about right to me, maybe more like 5 out of 11.5, and normally you'd be doing more than one attack per second, so a more realistic uptime would be closer to 50% as long as you block at the right moments.

Maura_Neysa wrote: »

Basic math, last 5 seconds, can proc every 10 Seconds, has a 33% chance. 0.5×0.33 = 0.165 aka 16.5% chance of this set being up when an attack comes in.

This on the other hand, is complete nonsense. Back to grade school with you.

@Cage_Lizardman go head tell me again how it’s up 5 out of 11.5 seconds

https://youtu.be/a1maQEIHflM

Wow, so you’re just doubling down on your hilariously awful math. I respect your gumption.

What your missing is that if it doesn’t proc in the first second, it can still proc in the second second... it’s not like if you block once and it doesn’t proc that you have to wait a full ten seconds again... (that is the only scenario your formula would work for, by the way, but that is not how blessed works)

Thats not how odds work. Its 33% on each, its not garentee to go off on 1 of 3 consecutive attacks. It has a 33% chance on each attack except when in the cool down. Between 2:34 and 2:58 the set doesn't proc once. 24 second window, now most of the time it is 8 seconds between proc. Funny thing about math, it can't lie. 0.5× 0.33 = 0.165

If you can answer this, we can continue to discuss. 6-1×0+2 ÷2=?

Maura_Neysa · December 2017

Thogard wrote: »

The actual formula would depend on quite a few things but let’s simplify and say that A = blockable attacks per second, and let’s simplify further and say that that’s just 1.

So for the first attack we have a 33% chance to block it. If we do block it, we have 5s of uptime and 5s of downtown, for a total update of 5s / 10s. Odds of that happening are 33% so

.33 * (5 / 10).

But what about the 2/3 of scenarios where the block doesn’t occur? We can still block again... that would be an uptime of 5 but downtime of 6s for a total of 5s / 11s. We have a 33% chance of proccing, but we have to remember that we only had a 2/3 chance of getting to this stage anyway, because in 1/3 of scenarios we would proc on the first attack

So we get

.33 * (5 / 10) + .66 ( .33 * (5 / 11))

And then we can repeat again, but this time it’s 2/3 of 2/3 probability since we’ve now had two chances to proc it...

.33 * (5 / 10) + .66 [ .33 * (5 / 11) + .66 { .33 * (5 / 12)}]

So the actual formula would go on like that infinitely. Fortunately there’s some nifty math we can use to simplify. Unfortunately there’s no easy way for me to do a sigma in B.B. code lol

It would be:

Limit (as n -> infinity, for all positive integers of n) of SIGMA { [.33 * (5 / ( 10 + n - 1))] * [(2 / 3)^(n - 1)]}

The answer is 42.5997%

http://www.wolframalpha.com/input/?i=sum+(.33+*+(5+/+(+9+++n+)))*+((2+/+3)^(n+-+1)),+n=1+to+infinity

again, not how odds work. They don't get better the longer you play. They stay the same, they stay 33% chance whether its the first blocked attack or the 1Oth its still 33%

Thogard · December 2017

Maura_Neysa wrote: »

Thogard wrote: »

The actual formula would depend on quite a few things but let’s simplify and say that A = blockable attacks per second, and let’s simplify further and say that that’s just 1.

So for the first attack we have a 33% chance to block it. If we do block it, we have 5s of uptime and 5s of downtown, for a total update of 5s / 10s. Odds of that happening are 33% so

.33 * (5 / 10).

But what about the 2/3 of scenarios where the block doesn’t occur? We can still block again... that would be an uptime of 5 but downtime of 6s for a total of 5s / 11s. We have a 33% chance of proccing, but we have to remember that we only had a 2/3 chance of getting to this stage anyway, because in 1/3 of scenarios we would proc on the first attack

So we get

.33 * (5 / 10) + .66 ( .33 * (5 / 11))

And then we can repeat again, but this time it’s 2/3 of 2/3 probability since we’ve now had two chances to proc it...

.33 * (5 / 10) + .66 [ .33 * (5 / 11) + .66 { .33 * (5 / 12)}]

So the actual formula would go on like that infinitely. Fortunately there’s some nifty math we can use to simplify. Unfortunately there’s no easy way for me to do a sigma in B.B. code lol

It would be:

Limit (as n -> infinity, for all positive integers of n) of SIGMA { [.33 * (5 / ( 10 + n - 1))] * [(2 / 3)^(n - 1)]}

The answer is 42.5997%

http://www.wolframalpha.com/input/?i=sum+(.33+*+(5+/+(+9+++n+)))*+((2+/+3)^(n+-+1)),+n=1+to+infinity

again, not how odds work. They don't get better the longer you play. They stay the same, they stay 33% chance whether its the first blocked attack or the 1Oth its still 33%

Yes the odds stay the same. Hence the limits. If you aren’t familiar with them then there’s no point to discuss further until you learn more about them in high school (pretty sure they’re the last thing taught in precalc, because limits segue perfectly into derivatives which is calculus.) My math is correct.

Maura_Neysa · December 2017

Don't forget, you have to divide your results by the number of attacker, since it only works on 1

Thogard · December 2017

Maura_Neysa wrote: »

Don't forget, you have to divide your results by the number of attacker, since it only works on 1

That is correct. My formula is for proc uptime. Not proc uptime per attacker.

Azurya · December 2017

Nelson_Rebel wrote: »

This set is incredibly stupidly broken. Whenever you block you have a 33% chance to cause all your attacker’s to miss ALL damage and attacks or effects of any kind for 5 seconds and occurs every 10 seconds.

This is a stupidly broken set that is what is helping to cause the perma tank cancer in BG’s and Open world cyrodill. This set has a near 90% uptime due to the HIGH percentage chance to occur, the short cooldown period between and the long duration to ignore every single effect (all damage and CC’s and anything else) on you while blocking...

Heavy armor and sword and board aren’t the problem in PvP. It’s sets like THIS and ravager and other stupidly broken things that cause pvp issues. So please ZoS do some QA on skill sets that are obviously broken, so you can stop nerfing PvE and PvP players

the only cancer in PvP are players that cannot accept that they will die!

Thogard · December 2017

Maura_Neysa wrote: »

Thogard wrote: »

The actual formula would depend on quite a few things but let’s simplify and say that A = blockable attacks per second, and let’s simplify further and say that that’s just 1.

So for the first attack we have a 33% chance to block it. If we do block it, we have 5s of uptime and 5s of downtown, for a total update of 5s / 10s. Odds of that happening are 33% so

.33 * (5 / 10).

But what about the 2/3 of scenarios where the block doesn’t occur? We can still block again... that would be an uptime of 5 but downtime of 6s for a total of 5s / 11s. We have a 33% chance of proccing, but we have to remember that we only had a 2/3 chance of getting to this stage anyway, because in 1/3 of scenarios we would proc on the first attack

So we get

.33 * (5 / 10) + .66 ( .33 * (5 / 11))

And then we can repeat again, but this time it’s 2/3 of 2/3 probability since we’ve now had two chances to proc it...

.33 * (5 / 10) + .66 [ .33 * (5 / 11) + .66 { .33 * (5 / 12)}]

So the actual formula would go on like that infinitely. Fortunately there’s some nifty math we can use to simplify. Unfortunately there’s no easy way for me to do a sigma in B.B. code lol

It would be:

Limit (as n -> infinity, for all positive integers of n) of SIGMA { [.33 * (5 / ( 10 + n - 1))] * [(2 / 3)^(n - 1)]}

The answer is 42.5997%

http://www.wolframalpha.com/input/?i=sum+(.33+*+(5+/+(+9+++n+)))*+((2+/+3)^(n+-+1)),+n=1+to+infinity

again, not how odds work. They don't get better the longer you play. They stay the same, they stay 33% chance whether its the first blocked attack or the 1Oth its still 33%

For visualization go to the following link and check out the “partial sums” graph. Half way down the page.

http://www.wolframalpha.com/input/?i=sum+(.33+*+(5+%2F+(+9+%2B+n+)))*+((2+%2F+3)%5E(n+-+1)),+n%3D1+to+infinity

Notice that the first dot is right at your original answer.. .33 * (5 / 10)

But then you have to remember that if we don’t proc it on the first attack we can still proc it on the second. The odds of us NOT proccing it on the first attack are 66%... so the odds of us proccing it on the second attack are 66% * 33 %... which is 22%. But then remember we have an extra second of downtime in this scenario, so we’d only get (5 / 11) instead of 5 / 10.

Now if we add that .22 * (5 / 11) to our first attacks .33 * (5 / 10) then we get that second dot on the partial sums graph. And the same idea gets the third one. And because theoretically speaking it is possible for us to never proc it, we have to continue this “chain” out to infinity. Which is why we have the calculators and limit theorems to measure these things.

Put another way, we have a 33% chance of 5/10 uptime, a 22% chance of 5/11 uptime, a 14.4% chance of 5/12 uptime, etc, and we have to solve to get to the final 100%.

You can see that represented by the fact that each additional value of n increases the total uptime by an incrementally smaller amount on the partial sums graph.

Qbiken · December 2017

Azurya wrote: »

Nelson_Rebel wrote: »

This set is incredibly stupidly broken. Whenever you block you have a 33% chance to cause all your attacker’s to miss ALL damage and attacks or effects of any kind for 5 seconds and occurs every 10 seconds.

This is a stupidly broken set that is what is helping to cause the perma tank cancer in BG’s and Open world cyrodill. This set has a near 90% uptime due to the HIGH percentage chance to occur, the short cooldown period between and the long duration to ignore every single effect (all damage and CC’s and anything else) on you while blocking...

Heavy armor and sword and board aren’t the problem in PvP. It’s sets like THIS and ravager and other stupidly broken things that cause pvp issues. So please ZoS do some QA on skill sets that are obviously broken, so you can stop nerfing PvE and PvP players

the only cancer in PvP are players that cannot accept that they will die!

And players raging when they can´t kill ppl.....

Malmai · December 2017

I see tears

Cage_Lizardman · December 2017

Maura_Neysa wrote: »

Between 2:34 and 2:58 the set doesn't proc once. 24 second window, now most of the time it is 8 seconds between proc. Funny thing about math, it can't lie. 0.5× 0.33 = 0.165

True, but the words next to the math can easily be wrong. Hopefully Thogard explained well enough why that is and how to do it right.

From the video it doesn't seem like he's getting hit much in that period. Also can't always tell when he's blocking.

VaranisArano · December 2017

Juhasow wrote: »

VaranisArano wrote: »

Juhasow wrote: »

This set kinda destroyed meaning and fun of duels. Now every scrub can wear it in duel and be immortal.

I would reccomend to change the 5 piece bonus to for example Major Maim. That would made set usefull in PvE also while tune it down in PvP to the point it's reasonable.

You mean like the Knightmare set? http://elderscrollsonline.wiki.fextralife.com/Knightmare+Set

@VaranisArano You know the difference between words "major" and "minor" ?

Hmm. That's fair. I missed the Major vs Minor distinction. However, that only brings up the little issue of how to get Major Maim. See, from what I can see, there's plenty of ways to get Minor Maim. Only 2 ways to get Major Maim - a hard to use and rather random warden ability and a templar Ultimate: http://en.uesp.net/wiki/Online:Buffs

Its an interesting thought, basically a single target but nastier version of Wizard's Riposte. All the same, ZOS seems pretty stingy with handing out the Major Maim effect.

Maura_Neysa · December 2017

Cage_Lizardman wrote: »

Maura_Neysa wrote: »

Between 2:34 and 2:58 the set doesn't proc once. 24 second window, now most of the time it is 8 seconds between proc. Funny thing about math, it can't lie. 0.5× 0.33 = 0.165

True, but the words next to the math can easily be wrong. Hopefully Thogard explained well enough why that is and how to do it right.

From the video it doesn't seem like he's getting hit much in that period. Also can't always tell when he's blocking.

It’s me and I permablock, I left out the 30 seconds before where I fell because that’s when I wasn’t taking damage or blocking. Also, my full on trials capable tank, just with set swap and some skills swapped. It’s easy enough to tell when the damage is coming because all combat metrics are on. (At least all for a consol)

As for the math, I can tell you from experance Hist Bark is far better if I was only concerned about me. Blessed’s advantage is that when it procs, that person misses everyone, not just me, making it useful for groups. Which is also the only time a Tank is useful in Cryodiil at all anyway.

Wreuntzylla · December 2017

GrumpyDuckling wrote: »

Nelson_Rebel wrote: »

Cage_Lizardman wrote: »

But does that really work on more than one target at a time?

Yes it’s everything in that timeframe

Incorrect. The set only works against ONE target (you'll see the stars circling their head) and EVERY other target can still hit you.

It's a powerful enough set that when you could only get it in mid-40's levels, I think my pieces were Lvl45-46, I would wear it on my capped CP toon and murder everyone. Nobody thought to wear low level gear so i was constantly accused of cheating.

I stopped using it because the old version of the set, I think the name was Akatosh's, would make the enemy sparkle. I couldn't stand making sparkly vampires.

Insandros · December 2017

Nelson_Rebel wrote: »

This set is incredibly stupidly broken. Whenever you block you have a 33% chance to cause all your attacker’s to miss ALL damage and attacks or effects of any kind for 5 seconds and occurs every 10 seconds.

This is a stupidly broken set that is what is helping to cause the perma tank cancer in BG’s and Open world cyrodill. This set has a near 90% uptime due to the HIGH percentage chance to occur, the short cooldown period between and the long duration to ignore every single effect (all damage and CC’s and anything else) on you while blocking...

Heavy armor and sword and board aren’t the problem in PvP. It’s sets like THIS and ravager and other stupidly broken things that cause pvp issues. So please ZoS do some QA on skill sets that are obviously broken, so you can stop nerfing PvE and PvP players

Save the Developpers a huge amount of time reading all the Nerfs this and that posts, simply list down man all the Sets you can't overcome or cannot figure out on out to beat in boring Duals and let's get over with, seriously.

KRBMMO · April 2018

Now I want to try and get a set of this at level 10 and wander around a starter zone light attacking everything and wait for the duel requests to start flooding in.

WakeYourGhost · April 2018

We have a Necromancer in our Midst.

Arobain · April 2018

As someone that HAS AND USED the set, it literally one works on one persons that's why it says it blinds that attacker