Here is a draft that re-enables hostile enemy range-checking in combat. It updates the InCombatLockdown to include a unit check and has a hackish canAttack flag that can be used to avoid redundant UnitCanAttack checks. There's probably a more clever way to accomplish the same thing and/or cache UnitCanAttack calls.
Results of :GetRange(unit) out of combat:
You can see that both hostile (true) and friendly (false) enemies have detailed range checks out of combat.
Results of :GetRange(unit) in combat:
Friendly enemy ranges drop back to the level of granularity allowed by Blizzard.
In my (minimal) testing, no taint warnings have been generated.
Here is a draft that re-enables hostile enemy range-checking in combat. It updates the InCombatLockdown to include a unit check and has a hackish
canAttackflag that can be used to avoid redundantUnitCanAttackchecks. There's probably a more clever way to accomplish the same thing and/or cache UnitCanAttack calls.Results of
:GetRange(unit)out of combat:true) and friendly (false) enemies have detailed range checks out of combat.Results of
:GetRange(unit)in combat:In my (minimal) testing, no taint warnings have been generated.