Well you referred to equal opportunity in real life in your earlier post but whatever.
Actually this is more of a design issue.Scottx125 wrote: ↑Tue Sep 20, 2022 11:27 pm And no, this is not about fixing anything. If you hit your ability when an enemy already has an immunity applied and you fire that ability, that's your fault. You failed to take into account that the target has immunity and made a mistake. You should learn to read what buffs/debuffs a target has and not waste abilities by spamming mindlessly. It's not the games job to babysit what abilities you do and don't press. That's up to you.
There are already a number of actions that won't fire if the target isn't suitable for said action or it's condition isn't fulfilled.
Like cleanse, shatter, ressurect, reactionary attacks (parry/block/disrupt), behind attacks, Juggernaut.
On top of that for some classes (KotBS) punt abilities are greyed out if the target is immovable and even gives an error message ("Target can not be knocked back again so soon!") but fire anyway.
(Not sure if this was how punts originally behaved on live or if it's some remnant code that should have been removed.)
So it seems the original devs made various arbitrary decisions on what abilities should be conditionally blocked and not (i.e. "babysits" abilities for you).
And most importantly they added the API to enable addon development to extend and improve on the whole player experience, like this addon aims to do.
This addon just adds the option for anyone to block other abilities in a similar fashion, if you choose to use it.