Devotion weapon proc linked to skill proc

How exactly does it work?
Let’s say both have a 25% chance of activating. The skill itself would on average proc once every 4 strikes, or 1/4. Now if we assume the devotion can only proc when the skill procs, does it mean it will on average activate every 16th attack? (4 attacks to ‘guarantee’ skill, 4 x 4 for guaranteed devotions).

Seems like devotions linked to passive skills only have a chance of activating when the passive does. For example I tied ‘Targo’s Hammer’ devotion (chance to proc on block) with the ‘Resilience’ skill (activates below 66% hp) and I only ever saw the hammer procs at the same time of Resilience being active. So my conclusion is it should extend to on attack devotions too.

Yes. That’s what it means.

There’s a difference when dual wielding, and it gets complicated.

Since many WPS uses both weapons to attack when DW, each of the 2 attacks has a chance of proccing it. So you double your chances.

Also, WPS like storm spread which fires up to 4 projectiles has 4x the chance of proccing a devotion. This goes up to 8 when DW.

EDIT: The same multiplicative rule applies with WPS which attacks several enemies in an arc - e.g. zolhan’s technique, whirling death, etc.

In essence, you sacrifice efficiency for convenience when using WPS as a devo-proccer. Some good skills to bind to WPS would be say hungering void, which has a 100% chance to proc.

Seems like devotions linked to passive skills only have a chance of activating when the passive does. For example I tied ‘Targo’s Hammer’ devotion (chance to proc on block) with the ‘Resilience’ skill (activates below 66% hp) and I only ever saw the hammer procs at the same time of Resilience being active

And duh. What did you expect? :rolleyes:

If you bind it to resilience, wouldn’t it make sense for the devotion to proc while resilience is up? Bind it to a permanent buff like oleron’s rage and notice the difference.

It’s worth noting that if you bind something like giant’s blood to blade barrier, it’ll only proc when you use blade barrier. So in essence, you have a lot more control as to when such a heal actually occurs.

No, I don’t think targo’s anvil (edited) should extend to attack devotions. It’s clearly a devotion aimed at trying to offset the dps loss which comes with using a shield.

Devotion has 25% chance per hit to activate. AFAIK dual wield counts as two hits as a wps like execution uses both hands. Same for dw shadow strike, nightfall etc.

Attaching a 25% active chance on execution: execution has 20% chance to occur, when execution does occur it has two hits so 2x25% activation chance so 50% chance to proc the devotion skill. Overall chance to proc the devotion per auto-attack would be 0.2x0.25x2 which is 10% chance, that means on average 10 auto attack need to occur to see the effect which at max attack speed is approx every ~2.5 seconds. Many devotion have lower cooldown than 2.5 seconds so it is inefficient to attach devotion to wps like execution.

Targo hammer is best attached to a permanent aura like field command as it would only proc when the resilience buff is activate otherwise.

Thanks for clearing it up.
Yeah I obviously have it bound to a permanent effect, was just explaining how I came to realize the underlying mechanic.
And again, wasn’t saying Targo’s Anvil should be an attack devotion, just used it as a comparison since it’s very easy to test how it interacts with a passive skill unlike weapon proc upon weapon proc.

Yeah I had just never thought about it before as the devotions flatly state ‘chance on hit’ or ‘chance upon being hit’ and assumed they’d work like the skill passives. But relying on the activation of the things they’re bound to makes sense as well from a mechanical point of view, just wasn’t very obvious to me without testing and experiencing it first-hand.

Ok, my misunderstanding. :slight_smile:

Anyhow, at the risk of sounding patronizing - any on-being-hit, on-block, on-being-crit proc are bound to passives, and will only activate when that passive is up.

It fires twice even when 2h, so also 8 projectiles :wink:

REALLY? Is this new? Is this why we no longer have 5 projectiles?

It always worked like this and was mentioned long time ago)