Question regarding "cannot" vs. "always"

"

wrajjt wrote:

Adding to this topic, because my question is semi-related.

"Your Hits always Ignite"

How does this interract with the map mod "Monsters have x% chance to avoid elemental ailments". This mod alone is one of the reason I've had a love-hate relationship with ignite builds in the past, since once you start creeping up on 70%+ chance to avoid ignite, ignite builds get really tedious to map with.

Cannot > Always > % chance to avoid

Likely the always will trump the avoidance and apply the minimum effect regardless. You will probably just have less beyond that effect than on a map without that mod.

But:
Shaper of Flames gives 25% more if it is the primary damage dealt, it does not guarantee a minimum amount of fire damage dealt. So your fire trap build (example) will find it's igniting just fine, but not doing a whole lot.

IMO this does need to be clarified, like Profane Bloom can curse hexproof enemies. Shaper nodes ignore chances to avoid ailments, or somesuch, and apply their full effect or some reduced effect.

It's just like with firewalls and share policies in computer systems, deny takes priority over allow.

That's also why it's bad practice to ever use denies in shares, unless you have no other option and why you should always make sure your denies in firewall settings aren't at the top, or it might work a little too well for you.

"

Xavathos wrote:

It's just like with firewalls and share policies in computer systems, deny takes priority over allow.

That's also why it's bad practice to ever use denies in shares, unless you have no other option and why you should always make sure your denies in firewall settings aren't at the top, or it might work a little too well for you.

So you're saying that 'always' just is not factual, and that the % chance to avoid will apply even before the always?

Doesn't seem like very 'always' to me, then.

"

BlaqWolf wrote:

"

Xavathos wrote:

It's just like with firewalls and share policies in computer systems, deny takes priority over allow.

That's also why it's bad practice to ever use denies in shares, unless you have no other option and why you should always make sure your denies in firewall settings aren't at the top, or it might work a little too well for you.

So you're saying that 'always' just is not factual, and that the % chance to avoid will apply even before the always?

Doesn't seem like very 'always' to me, then.

Indeed. If you cannot deal critical strikes, say, using Resolute Technique on the skill tree and use a weapon like Trypanon that allows every hit to be a critical strike (essentially "always") you will still never deal critical strikes.

Same effect applies to Diamond Shrine buffs, which is easy to test yourself. Instead of "never critting", you will instead "always never crit" for as long as the buff remains. ;)