Might of the Tanker, chance for +Res

I have it in haymaker as well and it doesn't fire off anywhere near as much as I expect it to

My dom can stack his proc (3/min not catalyzed) relatively quickly and keep it up without much trouble in a power that has an identical recharge time (8 seconds) while my tanker has the epic proc (6/min) can hardly ever stack it and often goes with no procs at all.

My expectations aren't high I just expect it to work as advertised.

I have mine catalyzed and slotted in Jab. I still have a hard time having it fire more than a twice per minute. I'm very lucky if it even double stacks.

This is very odd. Mine basically fires every time I use it. I hope it's you that is bugged and not me, I'd hate to lose the way the proc is working now.


EDIT: Here's a weird thought: The text says that the proc fires up to 5 times per minute. How does it do that? Does it consider the recharge time of the power it's slotted into?

Crowd Control has a base recharge of 12 seconds, and 60 seconds / 5 = 12 seconds on the money. Whereas Jab has a recharge of 2 seconds, which would yeild a proc chance of about 16.5% if you wanted 5 of them per minute. Hmmm.

From what I'm reading elsewhere, it seems like it's chance to fire depends on the base recharge of the power it's slotted into. The way my build is slotted, only Foot Stomp and LBE would have room for the proc. I don't even know if LBE would take it or not though. I figured since I use Jab heavily in my attack chain, it was good to slot with it.

My testing in beta indicated that the proc chance uses combined Base Recharge and Cast times for the calculation. For single target attacks (currently no Tanker attacks are considered single target due to punch-voke) the formula appears to be Proc/Minute Rate * (Recharge + Cast) / 60s.

For AoEs I believe the only change is that this value is divided by a factor that estimates the number of hits per cast and appears to be based off just Radius, Arc and Maximum Targets. I only have the sketchiest idea what the formula for that AoE factor is at the moment. However, for melee cones this factor appears to be fairly small, which is why Crowd Control is at or near a 100% proc rate. If the factor is less than 1.167 then it should be at 100%.

Unfortunately, due to the punch-voke bug, right now you are usually better off putting the Tanker proc in a true AoE, as the radii for the Taunt for longer recharge ST attacks can get to be quite large (17' on a 20s Recharge attack such as Seismic Smash or Knockout Blow) and so it will knock the proc chance way down.

On top of that punch-voke bug alluded to above, the IO also has only one chance to proc per casting, regardless of how many targets you hit. Which means you pay the penalty for it being in an AoE but actually get no benefit whatsoever from hitting multiple targets. (Almost all of the self-buff SBE/ATOs that I tested in Beta suffer from this handicap; the only one that didn't was the Brute proc, but that has now been changed, invalidating my Beta test, and probably resulting in it having the same problem as the others.)

Just to point out: in my very brief test on Beta yesterday, I was often finishing up a single boss in a spawn, and on a single target I saw no change in the frequency of the proc. It was always 100%.

I strongly suspect that whatever you think you are seeing as a bug here doesn't exist. For melee attacks, a small radius does NOT change the chance to proc. It does not knock down the chance to proc. I had 100% proc rates the whole time. Likewise, this "puch-voke bug" certainly wasn't affecting Crowd Control.

There may be an issue with actual large radii AoE. I'll make another copy and test with Shield Charge.

There is a definite AOE factor in the proc calcs. Doms slotting the Dom proc into the AOE immobs (big area, plus very fast recharge) are seeing the worst proc chances -- which go up remarkedly when the proc is re-slotted into the ST hold (which has a relatively long recharge).

First, Crowd Control doesn't have the extra punch-voke AoE added on to it, no Tanker AoEs do, only the ST attacks. The do have punch-voke, but since they're already AoEs, they're already paying the SBE/ATO proc rate penalty. ST attacks do have an extra AoE hiding in the background that does nothing but taunt... and ruin their SBE/ATO proc rate.

Second, you misunderstood the bug... the proc rate doesn't change with the number of targets you have, it only changes with the particulars of the power. Once it's slotted in a power it's always the same (unless it's an ATO and you upgrade it with a Catalyst). What I'm trying to say is that it only checks once per activation no matter how many times it hits. Since you're using powers with a 100% chance to proc you aren't seeing this. Though you would if you noted that it never procs more than once per activation no matter how many you hit.

For Crowd Control the AoE modifier is apparently less than 1.167, so it's proc chance is 100% when you hit 1 target or 5. If it was 80% it would also have an 80% chance of firing whether you hit 1 target or 5. Not 1-(0.2^5) = 99.968% chance as you'd expect when hitting 5 if it was checking for each target hit. I say as you'd expect because you'd be paying a proc chance penalty for the IO being in an AoE so naturally I think you'd expect it being in an AoE to provide some sort of benefit.

For Shield Charge to reduce the proc rate to less than 100% it would have to have an AoE mod of 9.84 or higher, which is highly improbable. It should be in the 4-5 range. For observing this bug you need to deliberately choose powers that will NOT give you a 100% chance to proc. You've chosen two that do. Once again, when you choose a power that gives a 100% chance to proc the issue of one activation = one chance to proc if you hit anything is completely irrelevant unless there is a possibility for multiple procs per power activation (as there should be if you're paying a penalty to have the proc in an AoE). However, with a power such as Tremor it does matter even without considering the multiple proc potential; as the proc rate is somewhere around 43%. It has a 17.3s cycle time compared to Crowd Control's 14s. So the AoEMod is clearly much higher. In the neighborhood of 3. So the IO pays a significant penalty to its proc chance for being in Tremor. However, in testing versus 1 target it proc'ed on 43% of the hits, while in testing against 4 it proc'ed in just 12% and there were never instances where it proc'ed more than once on a cast. That's not because the proc chance changed, it's because any hit past the 1st on each activation didn't result in a chance to proc at all. The proc rate per activation in which there was at least one hit was 48%, consistent with the 1 target tests. If it was giving me the benefit of multiple checks I should have seen an average of 1.67 procs per activation and at least one on 89% of my casts.

I believe the reason this proc behaves this way is because it targets the caster, not the target of the power it is slotted in. To try to confirm this during beta I tested all of the procs that target the caster and on beta all but the Brute proc behaved this way. And since going live they have changed the Brute proc. So I suspect it now behaves this way as well.