Estimated range display. Type /rangedisplay for configuration or /rangedisplay locked to lock/unlock the frames.
RangeDisplay is a simple range display addon. It is using spell range, item range and interact-distance based checks to determine the approximate range to your current target. Due to the whackyness of interact-distance based checks, recent versions only use those when spell/item based checks are not possible . The display can be configured in many ways (displaying only the max range, adding border and background, etc).
Currently you can set up RangeDisplay to show your current range to your target, focus, pet and mouseover units. The mouseover unit range can be anchored to the mouse or placed at a fixed position.
- 9 comments
- 9 comments
Facts
- Date created
- 06 Apr 2008
- Category
- Last update
- 09 Dec 2009
- Development stage
- Release
- Language
- deDE
- enUS
- frFR
- koKR
- ruRU
- zhCN
- zhTW
- License
- Public Domain
- Curse link
- RangeDisplay
- Recent files
Authors
-
- Manager
- Author
- #9
mitch0 Mon, 31 Aug 2009 13:00:23Hi,
I'm tearing out the options stuff into a separate addon, the upcoming alpha builds will most likely be BROKEN.
You have been warned :)
cheers, mitch
- #8
louis79979 Fri, 24 Apr 2009 05:11:45Thanks, it works perfectly..
- #7
zainph Tue, 17 Feb 2009 21:32:12Thanks, it works perfectly.
- #6
mitch0 Mon, 09 Feb 2009 08:34:02Hi,
I've applied your changes and re-packaged range-display. Please try the r211 alpha build, and report back if it works or not.
thanks
mitch
- #5
zainph Wed, 04 Feb 2009 09:03:39Hi,
First of all, thanks you for this addon. RangeDisplay is my favorate mod. But, there is a little problem for Druid. I couldn't do melee attacks in melee range (displayed 0-5 yard).
So, I modified LibRangeCheck-2.0.lua.
Line 62
Then, I can do melee attacks in 0 ~ 5 yards RangeDisplay displays. And, 5~8 yards is displayed, that was not displayed before modification.
Bash is an instant melee attack, druid can achieve it at level 14 from trainer.
Maul is a range restricted spell, but at any range IsSpellInRange API returns 1.
- #4
mitch0 Sat, 08 Nov 2008 21:46:18Hi,
I've implemented the background thing in v3.1-beta7, check it out. The "ugly" unlocked overlay is still there, just change its alpha to 0 in the code if you really really want to stay unlocked...
cheers, mitch
- #3
Zidomo Tue, 04 Nov 2008 01:53:10Been using disembeds for years; yes, used the newest RangeCheck library with that mod. No range problems. Its errors are (unfortunately) frame related, as with many old mods in WoW 3.x.
Ahhh...so unlocking is what causes the increased CPU usage of RangeDisplay. One of the reasons I was such a fan of Simple Range Indicator--besides its superior aesthetic design--was because it used a fraction of the CPU time that RangeDisplay did when I last tested them (with OptionHouse). RangeCheck and all other libraries were disembedded, so it was an accurate comparative test.
I did not lock RangeDisplay during the testing (that I can remember), so that's probably what contributed to the CPU time differences.
Simple Range Indicator's frame was permanently movable, yet it used a lot less CPU than RangeDisplay. So may be worth looking at it to find a better way of handling those OnUpdates.
Anyway, ty for responding :)
- #2
mitch0 Sun, 02 Nov 2008 19:10:47Hi,
If the bugs with SRI are range related, you might be able to fix it by using a standalone LibRangeCheck-2.0 (or copy the version from RangeDisplay to SRI). I have an open ticket that requests background setting, I'll look into it sometime. I'll see what I can do with keeping the frames unlocked, too (right now keeping it unlocked causes a lot of CPU waste, as OnUpdate is called even when you don't have a target), but since locking/unlocking is just a click away now with the minimap/LDB icon, I don't think it's that useful (and accidently eating up a mouseclick in the middle of a fight can be deadly...).
So, keeping locked would probably still remain the "preferred" state, and there probably will be an apparent visual indicator (like the current greenish background/overlay) if the frames are unlocked. Changing that would have to be done manually as you just did, but at least changing it will also remain as simple as it it now, I promise :)
cheers, mitch
- #1
Zidomo Sat, 01 Nov 2008 16:26:29Now that the terrific Simple Range Indicator (it also used the RangeCheck-2.0 library) is outdated and somewhat buggy in WoW 3.x, RangeDisplay has become my favorite mod of its type.
Not a fan at all of a r187 change, though. "Made background uglier to make it more obvious that users should lock the frames". No actually, I don't need to be reminded to lock the frame. I have them unlocked because I prefer my frames movable (whatever they are: unit, healing, etc.). Its why I have not yet moved to oUF ;).
So, I reverted that change on my local copy. Changed line 214 from ud.rangeFrameBG:SetTexture(0, 0.42, 0, 0.42) back to r186's ud.rangeFrameBG:SetTexture(0, 0, 0, 0.42) (frame went from an "ugly" green back to its original dark grey).
Hope you'll reconsider the frame coloration for those out there that prefer to have their RangeCheck frames permanently movable. Heck, if you added an in-game alpha/color adjuster for the frames, it would be perfect :).