LibRangeCheck-2.0
This library is deprecated. Development moved to the LibRangeCheck-3.0 fork.
A library to determine estimated range.
Comments
-
mitchnull Owner
This library is deprecated. Development moved to the LibRangeCheck-3.0 fork.
A library to determine estimated range.
mitchnull Owner
-
View User Profile
-
Send Message
Posted Oct 16, 2010GetSpellName has been renamed to GetSpellBookItemName. This error has resulted in the failure of an addon that I am trying to update. I have made the appropriate fixes in my local copy.
-
View User Profile
-
Send Message
Posted Oct 18, 2010v3.6.0 should be working okay.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Apr 27, 2009@zaiph: Those are comments only, the actual ranges are determined by the blizz API, but I changed them in the source, just in case :)
@Sinktinkler: This behaviour is due to how the ranges are determined and how interact based ranges work... The minimum range is the first range that range-check fails for, and for some reason the interact based ranges are determined differently than the "normal" spell/ability ranges. I'll consider ditching the interact-based checks for the friend and harm targets, and only keep them for the "misc" targets (those that you can neither assist, nor attack, like some folks in the neutral cities).
If you'd like to try out how it would work, change these two lines in LibRangeCheck-2.0.lua (in the :init method):
self.friendRC = createCheckerList(FriendSpells[playerClass], {}, FriendItems) self.harmRC = createCheckerList(HarmSpells[playerClass], {}, HarmItems)(the interactList param is replaced with an empty list)
cheers, mitch
-
View User Profile
-
Send Message
Posted Apr 23, 2009Hi! There are some fights where I, as a rogue, am able to use all my melee abilities, yet LibRangeCheck reports a range of 9 - 10 yards (I think) instead of the expected 0 - 5. Mobs where this is an issue include Razorscale chained in phase 1 and Kologarn's arms. While it seems plausible that my target, which in both cases is hovering off the ground, is indeed 9 - 10 yards away, is there (or should there be) a way to know through the LibRangeCheck API that I'm in melee range and able to use my melee abilities?
Actually, is this even intended behavior? Glancing through the code, it seems like it's using my rogue's Eviscerate to check for melee distance, and Eviscerate is certainly in range for these fights.
-
View User Profile
-
Send Message
Posted Apr 23, 2009Warrior's spell range.
355, ["Taunt"], 30 (not 20)
5246, ["Intimidating Shout"], 8 (not 10)
Warriors have no 10yard ranged harm spells except ones of area.
-
View User Profile
-
Send Message
Posted Feb 10, 2009Fixed in v3.2.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Feb 4, 2009