The existing comparison operators for range checking are limited to <= and >= which are FINE if the trigger condition you're looking for is "I am in range" but not all auras are looking for that. If you're looking for something NOT in range of one spell but in range of a second spell (for instance) or an on-screen warning that you're out of range for your primary rotation abilities (for instance) or something similar you have to set the trigger up so that you accept a "yes, I'm in range" but then use a custom trigger function to negate it to actually fire correctly (in the case that you want it to fire when you're NOT in range of the second spell/ability).

I would like to see either a negation option on range overall or !>= and !<= added to the drop down for the range comparison operators.

What I've done as a workaround was use custom triggers, but it seems unnecessary. Virtually every other numerical or boolean in the "build an aura using drop downs" has either a negation choice for the trigger condition or has a full set of comparison operators. I realize that = and != are impractical in this case and > and < are imprecise in this case, but !>= and !<= are not.

No additional context. I think I explained things enough and laid out a case for adding the comparison operators or a negation to the range check.

Those are not implementable.