RangeDisplay
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.
New in v3.8.0: It is possible to add sound notifications to "range sections" (similar to color setting). The sound will be played when entering the section. If two sections have the same sound file attached to them, then the sound is not played again if switching between the two sections.
This sound notification is enabled by default for the target unit's close range section.
Displaying max range only: if you want to display only the maxRange, you need to set Text to "%d" and tick the Reverse option for the section(s).
Comments
-
mitchnull Owner
-
View User Profile
-
Send Message
Posted Apr 6, 2010Some version of PitBull used to support range display via dogtags ([Range] or somesuch). You can probably do the same with luatexts in recent versions somehow, but I'd just place the standard RangeDisplay frames (probably without border and background) above your PitBull frames (just enable the Target and Focus frames in RangeDisplay). If you don't move your PitBull frames around much, this sounds the simplest approach. Just make sure RangeDisplay's "Strata" is higher than PitBull's.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Apr 7, 2010so what luatexts should I write?
and another question:
I am a priest so I can cast Mind Vision rank 1 on any unit within 100 yards, but rangedisplay show nothing if a friendly target is out of 27 yards. how to add this spell to check range?
-
View User Profile
-
Send Message
Posted Apr 7, 2010(that said, I'd still recommend not integrating it into pitbull, as that tends to be less efficient, at least that was the case with the DogTag version).
About the mind vision thing: do you see at most 27yds on every kind of friendly targets? party members and such? That would either be a bug, or some strange configuration on your part, as the heal ranges should be 40yd, so you'd have to see those at least. Make sure you have Range Limit set to max. The only "friendly" units where you should see 27yd range as max are units in sanctuaries and other "misc" units, but for those normal spell range checking doesn't work, so RangeDisplay is using interact distances there.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Apr 8, 2010the targets I said before are sporelings/the oracles/something like that, but indeed I can cast some spells (inc. Mind Vision r1 of 100yds, Dispel Magic of 30yds) on them, so my question is how to add these spells to check range?
thank you very much.
-
View User Profile
-
Send Message
Posted Apr 13, 2010My first feeling is that you can't do this in a way that wouldn't break on other units where the current ranges work (that is, it is fairly simple to add these spells to the "misc" type targets, but it won't work on all "misc" targets, and you'll see misleading 100+ yd displays on those).
Try changing line 729 in RangeDisplay/libs/LibRangeCheck-2.0/LibRangeCheck-2.0.lua from
if updateCheckers(self.miscRC, createCheckerList(nil, nil, interactList)) then
to
if updateCheckers(self.miscRC, createCheckerList({527, 2096}, nil, interactList)) then
and see if it works for your sporelings. then check what else it broke... :)
cheers,
mitch
-
View User Profile
-
Send Message
Posted Mar 31, 2010-
View User Profile
-
Send Message
Posted Mar 24, 2010their is a problem with the "short" range area, in that it will not display at all if you set its limit to less than 8 yards. I want to keep my short limit as 5 yards because being a hunter, that is my Min. bow range. Plus this 3.3.3 patch seems to have messed it up a bit. the ranges it displays are all off. not sure if the short range is the reason its messed up or not.
-
View User Profile
-
Send Message
Posted Apr 6, 2010I do try to keep it updated, but I don't have an active subscription at the moment, so I have to rely on reports like yours to get notified of any issues...
Regarding your issue:
The ranges you can set up must be distinct, and the shorter range must really be shorter.
You have these sections:
Close range
Short range
Medium range
Long range
[Default]
Out of range
The check goes something like this:
First, the measured max range is compared to first 4 sections in that order, and the first that fits (that is, its configured ranges is greater than or equals the measured max range) is used for the display.
Then if the current min range is over the one set for "Out of range", then that section is used.
Otherwise the "default" section is used.
I guess you have Close range set to 5 yards (melee range). You should set Short range to 8 yards, as there isn't any other measurable ranges between 5yd and 8yd, so setting it to 7yd for example will never trigger that section (as the measured range will either be 5 or at least 8).
What exactly do you mean by all ranges being off since 3.3.3? Could you provide some examples? Test with all sections disabled, and make sure the default section's text override thing is disabled, too. Since some spell ranges are modified by talents, please attach your current talent spec, too. I might have missed some talent changes or some item range changes...
thanks for the help,
cheers,
mitch
-
View User Profile
-
Send Message
Posted Feb 17, 2010Little request, if its even possible.
Since the activation range of nameplates has been increased in 3.3 to 40 yards, it would be really great to have a range check attached to them, like mouseover range check anchored to the mouse.
-
View User Profile
-
Send Message
Posted Feb 19, 2010Unfortunately, it's not possible. The range checking stuff only works with valid units (player, target, focus, etc) and the nameplates don't have those.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Jan 6, 2010-
View User Profile
-
Send Message
Posted Jan 7, 2010- Make sure you have "Enabled" is unchecked in the "Background Options" section
- Make sure the frames are locked (either type /rangedisplay locked or check "Locked" in the main config group (if your current background is just an ugly green semi-transparent square, then it's because the frames are not locked)
cheers,
mitch
-
View User Profile
-
Send Message
Posted Dec 23, 2009I can send a jpg if you like.
Thanks for Range Display
Kortash, Sentinels
-
View User Profile
-
Send Message
Posted Dec 28, 2009The "ghostly green hand" is a positioning-aid for the mouseover unit display, it goes away if you lock the frames (either by left-clicking the LDB icon, ticking "Locked" in the config menu, or typing /rangedisplay locked).
cheers,
mitch
-
View User Profile
-
Send Message
Posted Dec 29, 2009-
View User Profile
-
Send Message
Posted Dec 17, 2009-
View User Profile
-
Send Message
Posted Dec 17, 2009Right now "Chat Frame" seems to work (I also have one called "Solid" but that's probably coming from some other addon, maybe from SharedMedia).
Make sure to set the alpha on the background color tab to max, too.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Nov 13, 2009I've added a short delay at initialization in the v3.7.6 release, please give it a try and report back if it solved the problem with ranges not updating with regard to talent modifiers.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Nov 13, 2009thank you for your work.
-
View User Profile
-
Send Message
Posted Nov 11, 2009I'm investigating the issue with the ranges not getting the talent-updated values. Till I find the issue and manage to fix it, you can force a re-init with the following chat command:
/run LibStub("LibRangeCheck-2.0"):init(true)
sorry for the inconvenience,
cheers,
mitch