WowAce

In reply to mitchnull:

Well, for your situation, that makes a lot of sense.

But, I have seen others that clearly  - actively - work on their mods but will usually be several game versions behind for some reason. Seems like to me that might cause them to get passed over by anyone that might browse based on certain game versions.

I know it most cases it's more of a nitpick thing - if the mod still works, it works. But, also, some people might also not load out of date mods.

I guess it's just one of my "poet peeves" as they call it. lol >< Either way, have a good day.

In reply to JDM12983:

 Completely depends on the addon and how much of WoW's API they make use of. Generally, with major expansions or patches, they add or remove API functions and sometimes change the behavior of existing ones, so if your addon relies on something that went away or changed, you have to hope that either it's an easy fix or that there's some kind of work around that isn't a huge pain. As for not updating the version, I believe the author here mentioned that nothing had changed since the last time they updated it (9.0.5) from an API standpoint, so the displayed game version (9.0.5), while out of date, didn't affect functionality (at least, til pre patch). To get the displayed game version to match up, there's a .toc file you edit to set. I believe that would be the first line of RangeDisplay.toc where it says ## Interface: 90005, though to be fair, the only thing that line does is indicates to the game whether or not an addon is out of date: you can still load it. My guess is the author basically forgot to bump TOC versions or didn't care since the TOC version doesn't affect your ability to load the game nor will it cause LUA errors. The above LUA errors are from the most likely large amount of API changes to the 10.0 new expansion and they also seem to look like they're the result of another library: AceAddon, rather than RangeDisplay. However I am not the author so I could be totally wrong on that reason. However looking at the Ace3 addon page, it still shows version 9.27, but it does look like there's been a lot of recent activity so my guess is once Ace3 gets updated (and that'll probably happen quickly as a lot of addons depend on it) RangeDisplay will auto get fixed and still be left working but saying that it's for game version 9.05 =) If the 9.05 bothers you, you could just change that line in the .toc file.

Suggestion: Might it be possible to have an option to count how many targets are within a certain range?  Ex. all targets in a 5 yard range, or all targets in melee range, etc. 

This would let Rangedisplay replace a weak aura that counts how many targets are currently in range for blade flurry, etc. as the weak aura is a bit of a performance hog.  

In reply to mitchnull:

 Ah, I see; I thought an addon would be able to do it more efficiently.  Ty for the reply!

Nameplate distance weakaura

Hi Mitch, is there any way to arrange the range box to vertical fashion?

Broken as of Classic era 14.1

hey!

I wanted to ask...

is there any way to get the exact distance and not x - y ?

thx!

In Classic (yes RD works in Classic!) Is there anyway to extend the max range distance displayed?  I'm thinking of my fire mage who has flame throwing and who can cast a fire spell at a mob further than 35 yards away.  Thanks in advance.

Unfortunately, the max range display was changed Blizzard-side between RangeDisplay releases, so this is likely impossible to fix now.

In reply to spiralofhope:

 Thanks anyway :)  Happy holidays!

Hoping for the Shadowland Update!!!

If anyone was looking for sounds, I believe I was able to get sounds working by enabling lines 135 and 138 set to true.

line 135:     bgEnabled = true,

line 138:     bgTile= true,

I was able to start hearing the sound effects on my client again. 

--Updated for a friend, if anyone still keeps the project live, please continue to support the sound effects portion :)

 2x RangeDisplay\RangeDisplay-v4.9.3.lua:262: attempt to call method 'setDisplayColor' (a nil value)
[string "@RangeDisplay\RangeDisplay-v4.9.3.lua"]:262: in function `targetChanged'
[string "@RangeDisplay\RangeDisplay-v4.9.3.lua"]:800: in function <RangeDisplay\RangeDisplay.lua:799>
[string "=[C]"]: ?
[string "@TomTom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua"]:29: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25>
[string "@TomTom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua"]:64: in function `Fire'
[string "@TomTom\libs\AceEvent-3.0\AceEvent-3.0-4.lua"]:120: in function <...aceTomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
[string "=[C]"]: in function `TargetUnit'
[string "@FrameXML\SecureTemplates.lua"]:496: in function `handler'
[string "@FrameXML\SecureTemplates.lua"]:654: in function `SecureActionButton_OnClick'
[string "@FrameXML\SecureTemplates.lua"]:694: in function <FrameXML\SecureTemplates.lua:686>

I fixed it:

https://www.wowace.com/projects/range-display/issues/16

In reply to spiralofhope:

 Thank you so much for this! Now mine is working like it used to. :D

In reply to spiralofhope:

 Thank you! It works well now!

In reply to spiralofhope:

 Thank you! It works well now!