@B_I_G__D_A_D_D_Y the way that PetTauntOverride is designed, is to allow for /pet taunting, when it normally wouldn't and turn off /pet taunting when you shouldn't.
Normal function of kiss is to turn on /pet taunt, if your running one of the following Roles: pettank,pullerpettank,hunterpettank and turn off /pet taunt if your not one of those roles.
So in the first situation, if /pet taunt is off. Then a check is done on PetTauntOverride to see if you want /pet taunt turned on. So the first check is:
/if (${Select[${Role},pettank,pullerpettank,hunterpettank]} || ${PetTauntOverride}) /pet taunt on
Now If /Pet taunt is on then PetTauntOverride is checked, if turned off before turning off /pet taunt. So PetTauntOverride is used here as an override to leaving /pet taunt on when the macro would normally turn /pet taunt off:
/if (!${Select[${Role},pettank,pullerpettank,hunterpettank]} && !${PetTauntOverride}) /pet taunt off
So normally /pet taunt would be turned off if your NOT running one of the following roles: pettank,pullerpettank,hunterpettank so turning PetTauntOverride on overrides this function.
I think what your wanting, is for PetTauntOverride to totally skip any of the /pet taunt code if it is turned on, and not be used to override the individual states as it is currently used.