1. #1
    Deleted

    Addon request legendary ring 20 yards range

    Showing if you are within 20 yards of the current target.
    Simple. Would be really nice.
    Last edited by mmoc20b0a89b82; 2015-08-20 at 06:48 PM.

  2. #2
    This is only possible if the target is a friendly player, in your party / raid. You cannot do this for NPCs, as that is blocked by Blizzard.

    Your best bet would be to install an addon that does a best guess of the range of your target based on which of your spells can be cast on it. (eg. 30-40 if you can heal, 20-30 if you can dot, 0-5 if you can melee, etc). http://www.curse.com/addons/wow/range-display

  3. #3
    Quote Originally Posted by Nathima View Post
    This is only possible if the target is a friendly player, in your party / raid. You cannot do this for NPCs, as that is blocked by Blizzard.

    Your best bet would be to install an addon that does a best guess of the range of your target based on which of your spells can be cast on it. (eg. 30-40 if you can heal, 20-30 if you can dot, 0-5 if you can melee, etc). http://www.curse.com/addons/wow/range-display
    You can do this for any type of target easily, it's just won't be that accurate.

  4. #4
    Quote Originally Posted by Resike View Post
    You can do this for any type of target easily, it's just won't be that accurate.
    Attempting to call location of any NPC or player not in party or raid will give a location of (0, 0), always.

  5. #5
    Quote Originally Posted by Nathima View Post
    Attempting to call location of any NPC or player not in party or raid will give a location of (0, 0), always.
    http://wowwiki.wikia.com/wiki/API_CheckInteractDistance

  6. #6
    Ah, very nice workaround, did not realize this worked for NPCs. That's about all you can do though, and it's only for set intervals (9.9, 11.11, and 28 yards). So you're right in that it would only be very approximate.

  7. #7
    http://wowwiki.wikia.com/wiki/API_IsSpellInRange

    If there is a suitable 20 yard range spell to test with.
    Quote Originally Posted by DeadmanWalking View Post
    Your forgot to include the part where we blame casuals for everything because blizzard is catering to casuals when casuals got jack squat for new content the entire expansion, like new dungeons and scenarios.
    Quote Originally Posted by Reinaerd View Post
    T'is good to see there are still people valiantly putting the "Ass" in assumption.

  8. #8
    Quote Originally Posted by ComputerNerd View Post
    http://wowwiki.wikia.com/wiki/API_IsSpellInRange

    If there is a suitable 20 yard range spell to test with.
    I really wish Blizz would just add 20 and 40y checker to the CheckInteractDistance.

  9. #9
    Deleted
    Made a WA to track the 20y range weeks ago.
    I used the range of http://www.wowhead.com/item=10645/gnomish-death-ray (IsItemInRange("item:10645","target"))
    It will work even without this item in your inventory.The WA shows the duration and the caster of the ring. If the caster is you, then the color will go from green(in range) to red (out of range).

    http://pastebin.com/Ru65hB5d

  10. #10
    Quote Originally Posted by Astraar View Post
    Made a WA to track the 20y range weeks ago.
    I used the range of http://www.wowhead.com/item=10645/gnomish-death-ray (IsItemInRange("item:10645","target"))
    It will work even without this item in your inventory.The WA shows the duration and the caster of the ring. If the caster is you, then the color will go from green(in range) to red (out of range).

    http://pastebin.com/Ru65hB5d
    Is it also works if you are not an engineer?

  11. #11
    Deleted
    Quote Originally Posted by Resike View Post
    Is it also works if you are not an engineer?
    It should, also tried other ranges (with different items ofc).
    Capacitor trinket for example is one (15y random quest item lol).
    I found the items in the rangecheck-lib

    Code:
    local HarmItems = {
        [5] = {
            37727, -- Ruby Acorn
        },
        [6] = {
            63427, -- Worgsaw
        },
        [8] = {
            34368, -- Attuned Crystal Cores
            33278, -- Burning Torch
        },
        [10] = {
            32321, -- Sparrowhawk Net
        },
        [15] = {
            33069, -- Sturdy Rope
        },
        [20] = {
            10645, -- Gnomish Death Ray
        },
        [25] = {
            24268, -- Netherweave Net
            41509, -- Frostweave Net
            31463, -- Zezzak's Shard
        },
        [30] = {
            835, -- Large Rope Net
            7734, -- Six Demon Bag
            34191, -- Handful of Snowflakes
        },
        [35] = {
            24269, -- Heavy Netherweave Net
            18904, -- Zorbin's Ultra-Shrinker
        },
        [40] = {
            28767, -- The Decapitator
        },
        [45] = {
    --        32698, -- Wrangling Rope
            23836, -- Goblin Rocket Launcher
        },
        [50] = {
            116139, -- Haunting Memento
        },
        [60] = {
            32825, -- Soul Cannon
            37887, -- Seeds of Nature's Wrath
        },
        [70] = {
            41265, -- Eyesore Blaster
        },
        [80] = {
            35278, -- Reinforced Net
        },
        [100] = {
            33119, -- Malister's Frost Wand
        },
    }
    The number in [] is the range.

  12. #12
    Quote Originally Posted by Astraar View Post
    It should, also tried other ranges (with different items ofc).
    Capacitor trinket for example is one (15y random quest item lol).
    I found the items in the rangecheck-lib

    Code:
    local HarmItems = {
        [5] = {
            37727, -- Ruby Acorn
        },
        [6] = {
            63427, -- Worgsaw
        },
        [8] = {
            34368, -- Attuned Crystal Cores
            33278, -- Burning Torch
        },
        [10] = {
            32321, -- Sparrowhawk Net
        },
        [15] = {
            33069, -- Sturdy Rope
        },
        [20] = {
            10645, -- Gnomish Death Ray
        },
        [25] = {
            24268, -- Netherweave Net
            41509, -- Frostweave Net
            31463, -- Zezzak's Shard
        },
        [30] = {
            835, -- Large Rope Net
            7734, -- Six Demon Bag
            34191, -- Handful of Snowflakes
        },
        [35] = {
            24269, -- Heavy Netherweave Net
            18904, -- Zorbin's Ultra-Shrinker
        },
        [40] = {
            28767, -- The Decapitator
        },
        [45] = {
    --        32698, -- Wrangling Rope
            23836, -- Goblin Rocket Launcher
        },
        [50] = {
            116139, -- Haunting Memento
        },
        [60] = {
            32825, -- Soul Cannon
            37887, -- Seeds of Nature's Wrath
        },
        [70] = {
            41265, -- Eyesore Blaster
        },
        [80] = {
            35278, -- Reinforced Net
        },
        [100] = {
            33119, -- Malister's Frost Wand
        },
    }
    The number in [] is the range.
    Intresting, actually it would fix some issue like Taurens can duel/trade/inspect/follow from much more far then any other races. Making the yard checker inaccurate.

  13. #13
    Quote Originally Posted by Astraar View Post
    I found the items in the rangecheck-lib

    Code:
        [20] = {
            10645, -- Gnomish Death Ray
        },
    Useful to know.
    Didn't realise it was in such an accessible form.

    Looks like we have an option there for the 20yd range of the ring.
    Quote Originally Posted by DeadmanWalking View Post
    Your forgot to include the part where we blame casuals for everything because blizzard is catering to casuals when casuals got jack squat for new content the entire expansion, like new dungeons and scenarios.
    Quote Originally Posted by Reinaerd View Post
    T'is good to see there are still people valiantly putting the "Ass" in assumption.

  14. #14
    Quote Originally Posted by ComputerNerd View Post
    Useful to know.
    Didn't realise it was in such an accessible form.

    Looks like we have an option there for the 20yd range of the ring.
    The issue is that is does not work for friendly but un-assistable or enemy but not-attackable mobs.

    Maybe someone with an US account could poke the Blizzard forums to give us a proper yards to the CheckInteractDistance (Which works on every unit, friendly-assistable, friendly-non-assistable, enemy-attackable, enemy-non-attackable and the neutral ones too).

    Because the current yard checks are pretty pointless for anything:

    http://wow.gamepedia.com/API_CheckInteractDistance

    We need:
    5, 6, 7, 8, 9, 10, 15, 20, 25, 30, 35, 40, ... to 100.
    Last edited by Resike; 2015-08-21 at 12:17 PM.

  15. #15
    Quote Originally Posted by ComputerNerd View Post
    Useful to know.
    Didn't realise it was in such an accessible form.

    Looks like we have an option there for the 20yd range of the ring.
    Seriously, I didn't think to ever try this. I just assumed that that because Blizz had locked down the coords of all NPCs, that such functionality would be locked down elsewhere. But you know what they say when you assume...

  16. #16
    Quote Originally Posted by Nathima View Post
    Seriously, I didn't think to ever try this. I just assumed that that because Blizz had locked down the coords of all NPCs, that such functionality would be locked down elsewhere. But you know what they say when you assume...
    I'll be honest, I ignored "check interact distance" because it's so inaccurate as to be useless for most practical purposes. Walking the table of items with known 5 yard ranges is fine, and I'd kind of like to shake a Blizzard dev and be all "just unlock five yard accuracy on NPC locations, or at least distances", but whatever.

  17. #17
    Quote Originally Posted by SlippyCheeze View Post
    I'll be honest, I ignored "check interact distance" because it's so inaccurate as to be useless for most practical purposes. Walking the table of items with known 5 yard ranges is fine, and I'd kind of like to shake a Blizzard dev and be all "just unlock five yard accuracy on NPC locations, or at least distances", but whatever.
    The issue is that you still can't build a proper range checker for every target, since the problem i mention above.

  18. #18
    Hey guys i'd tought i just upload the ring weakaura i made for my guild which has following features.

    -the wanted range check to target (background colors in red(20y+)->yellow(20-15y)->green(15-0y)
    there is a value under the 20 yards check cause it is a little bit inaccurate and it can be out of range when you stand right at the 20 yards indicator keep in mind it only checks range to your current target

    -raidwide cooldown tracking + uptime and user

    -hides while out of combat without losing track of the cd

    the range check also only visualizes if you are the initiator of the ring.

    here's a little showcase video:


    DISCLAMER: i'm using elvui so appearance may be a bit off on your system cause of fonts and icon packs.


    and the pastebin link to the WA:
    http://pastebin.com/pNFEg08s


    PS: maybe there is some LUA god out there that could also help me to get an indicator for healers how many ppl are in range of there heal explosion, given the fact that tracking friendly players position is possible via LUA.
    Last edited by Meatleg; 2015-08-22 at 12:03 AM.

  19. #19
    Quote Originally Posted by Meatleg View Post
    maybe there is some LUA god out there that could also help me to get an indicator for healers how many ppl are in range of there heal explosion, given the fact that tracking friendly players position is possible via LUA.
    Challenge accepted: https://gist.github.com/Zireael-WoW/...e59f2410e5b948

    I couldn't find any information about burst radius and assumed it's 20 yards too. Change it if needed.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •