WowAce

The following error occurs when clicking an attackable unit in-game, regardless of whether it's in range or not.

49x ...cePitBull4/Modules/RangeFader/RangeFader.lua:193: attempt to call global 'IsSpellInRange' (a nil value)
[string "@PitBull4/Modules/RangeFader/RangeFader.lua"]:193: in function <...cePitBull4/Modules/RangeFader/RangeFader.lua:187>
[string "@PitBull4/Modules/RangeFader/RangeFader.lua"]:240: in function `GetOpacity'
[string "@PitBull4/ModuleHandling/FaderModule.lua"]:176: in function <...rfacePitBull4/ModuleHandling/FaderModule.lua:162>
[string "@PitBull4/ModuleHandling/FaderModule.lua"]:207: in function `UpdateFrame'
[string "@PitBull4/ModuleHandling/Module.lua"]:314: in function `Update'
[string "@PitBull4/UnitFrame.lua"]:789: in function `Update'
[string "@PitBull4/UnitFrame.lua"]:815: in function `UpdateGUID'
[string "@PitBull4/Main.lua"]:1765: in function `CheckGUIDForUnitID'
[string "@PitBull4/Main.lua"]:1776: in function `?'
[string "@Bartender4/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:109: in function <...er4/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:109>
[string "=[C]"]: ?
[string "@Bartender4/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...er4/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>
[string "@Bartender4/libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function `Fire'
[string "@Bartender4/libs/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <Bartender4/libs/AceEvent-3.0/AceEvent-3.0.lua:119>
[string "=[C]"]: in function `TargetNearestEnemy'
[string "TARGETNEARESTENEMY"]:2: in function <[string "TARGETNEARESTENEMY"]:1>

Locals:
unit = "target"
(for state) = <table> {
 1 = "Arcane Shot"
}
(for control) = 1
_ = 1
name = "Arcane Shot"
(*temporary) = nil
(*temporary) = "Arcane Shot"
(*temporary) = "target"
(*temporary) = "attempt to call global 'IsSpellInRange' (a nil value)"
enemy_spells = <table> {
 1 = "Arcane Shot"
}

 Edit: Confirmed this still exists after updating from 4.2.35 to 4.2.36

Seems this was fixed by updating something else. Possibly a library update fixed it. Closing so you don't have to waste time on it.

I did push a fix in v4.2.36, maybe you just caught that :p