WowAce

In reply to mitchnull:

 well that's a pitty :( 

but's not reduced accuracy, the only thing I'm getting all the time while in combat is 0-40.

My bad didn't make profile for each spec. Works fine.

Thanks for a great Addon.

Under profiles "Enable spec profiles" says each spec will have it's

own profile. Doesn't work as specified.

Any changes to a spec profile is reflected in the other spec's.

So only one spec profile.

+40 yards only shows out of combat! -40 yards works in/out of combat

Still not working on combat since last update

1315x ...Display/libs/LibRangeCheck-2.0-10000000000002/LibRangeCheck-2.0.lua:441: IsSpellInRange(): Invalid spell slot

[string "=[C]"]: ?

[string "@RangeDisplay/libs/LibRangeCheck-2.0-10000000000002/LibRangeCheck-2.0.lua"]:441: in function <...Display/libs/LibRangeCheck-2.0/LibRangeCheck-2.0.lua:440>

[string "@RangeDisplay/libs/LibRangeCheck-2.0-10000000000002/LibRangeCheck-2.0.lua"]:558: in function `checker'

[string "@RangeDisplay/libs/LibRangeCheck-2.0-10000000000002/LibRangeCheck-2.0.lua"]:623: in function <...Display/libs/LibRangeCheck-2.0/LibRangeCheck-2.0.lua:615>

[string "=(tail call)"]: ?

[string "@RangeDisplay/RangeDisplay.lua"]:415: in function `update'

[string "@RangeDisplay/RangeDisplay.lua"]:477: in function <RangeDisplay/RangeDisplay.lua:472>

Locals:

(*temporary) = <function> defined @RangeDisplay/libs/LibRangeCheck-2.0/LibRangeCheck-2.0.lua:500

(*temporary) = "spell"

(*temporary) = nil

As someone else mentioned having Mortal Coil for 20 yard check would be splendid.

Gateway has a 10-40 yard range check. Not sure if the 10 yards can be used for anything?

Perhaps it would also be possible when out of range of your highest range spell to show >X yards

Thanks for the update!

I see what you were saying about "limited" range estimates. Not your fault, Blizzard screwed the pooch on this one.

Can an update fix that bug and show the range again in combat? It would be lovely many thanks xx

Same here. Disappears in combat. Something change with WoW?

Just started.

In reply to msc6399: Yep, Blizzard rolled out a patch today and changed something in their rubbish code that affects the 'IsItemInRange()' function.

it works until i get into combat, then it disappears...

Thanks for this addon, I have been using it since forever! <3

With a patch that Blizzard rolled out just today, Rangedisplay works as intended (ie; select a target, shows in range. Then walk away until shows out of range), however as soon as entering combat, Rangedisplay simply shows out of range regardless of distance from target and only returns to working normally once out of combat again.

LUA error is:

2x [ADDON_ACTION_BLOCKED] AddOn 'RangeDisplay' tried to call the protected function 'IsItemInRange()'.

[string "@!BugGrabber/BugGrabber.lua"]:481: in function <!BugGrabber/BugGrabber.lua:481>

[string "=[C]"]: ?

[string "@RangeDisplay/libs/LibRangeCheck-2.0-10000000000001/LibRangeCheck-2.0.lua"]:465: in function `checker'

[string "@RangeDisplay/libs/LibRangeCheck-2.0-10000000000001/LibRangeCheck-2.0.lua"]:590: in function <...Display/libs/LibRangeCheck-2.0/LibRangeCheck-2.0.lua:585>

[string "=(tail call)"]: ?

[string "@RangeDisplay/RangeDisplay.lua"]:415: in function `update'

[string "@RangeDisplay/RangeDisplay.lua"]:477: in function <RangeDisplay/RangeDisplay.lua:472>

Locals:

_ = Frame {

RegisterEvent = <function> defined @!BugGrabber/BugGrabber.lua:487

0 = <userdata>

UnregisterEvent = <function> defined @!BugGrabber/BugGrabber.lua:487

SetScript = <function> defined @!BugGrabber/BugGrabber.lua:487

}

event = "ADDON_ACTION_BLOCKED"

events = <table> {

ADDON_ACTION_BLOCKED = <function> defined @!BugGrabber/BugGrabber.lua:553

ADDON_ACTION_FORBIDDEN = <function> defined @!BugGrabber/BugGrabber.lua:553

PLAYER_LOGIN = <function> defined @!BugGrabber/BugGrabber.lua:547

LUA_WARNING = <function> defined @!BugGrabber/BugGrabber.lua:562

ADDON_LOADED = <function> defined @!BugGrabber/BugGrabber.lua:507

}

In reply to dmeister406:

I'm guessing that the "can't check distance when in combat" thing is a side effect of this patch note; what I don't know is if it's intentional or not, and it affects the outdoor world as well where I thought it was only intended to impact the raid. I'm not getting your LUA error, though, I'm just getting nonsense distance indications whenever I go into combat.

Restricted addon functions that allowed for in-combat distance checking between players.

Developers’ notes: This change was intended to be implemented with the launch of the Guardians of the Dream patch, to avoid requiring that addon authors update their addons separately after the content is already being played. We apologize for the confusion and inconvenience.

any chance of a friendly only setting? I'm trying to use this for ressing, to know if I'm in range or not. warning sound when I'm not. but I don't need a warning sound whenever I mouseover a random enemy