Hekili Priority Helper

Hekili Priority Helper

46M Downloads

ALL TARGET DETECTION / RANGE CHECK RELATED ISSUES GO IN THIS THREAD

Hekili opened this issue ยท 12 comments

commented

Before You Begin

  • I confirm that I have downloaded the latest version of the addon.
  • I am not playing on a private server.
  • I checked for an existing, open ticket for this issue and was not able to find one.
  • I edited the title of this bug report (above) so that it describes the issue I am reporting.

Describe the Issue

On 16 November, Blizzard issued a hotfix that prevents addons from using IsItemInRange and CheckInteractDistance. This addon used these API functions to aid in target detection and to determine (roughly) how far you are from targets. Doing so, I could reasonably reliably provide target counting filtered by range to simplify target detection for melee specializations.

As of v10.2.0-1.0.2wtf (intentional, WTF?), I have stopped using IsItemInRange and LibRangeCheck-2.0, which relied upon the above API. I'm grateful to be borrowing a newer, modified LibRangeCheck from the ElvUI team. This does not restore the full previous functionality, but your UI should no longer taint and lock as you play with the addon.

As an additional workaround for melee, you can turn off Use Nameplate Detection in your specialization's options. This will rely on counting targets you've recently damaged instead of nameplates.

image

This means that nearby targets don't count as enemies until you've hit them with something. You'll want to "prime the pump" using an AOE ability that tells the addon you care about those nearby enemies.

If you're still having issues, you can add to this thread, including your snapshot and/or error messages in your first post. If you don't include that information, I'll delete the post to save room. Try to share everything relevant in one post to keep things manageable here. Thank you.

Additional Information

Read the above. Keep me sane-ish. Thanks.

Contact Information

Hekili

commented

Hello, For enhancement shaman, Sundering and Crash lightning will still not be recommended EVEN IF YOU UNCHECK "use nameplate detection". You have to go into enh core and uncheck "crash lightning range check" and "sundering range check" due to the above issues. It's possible similar things may exist on other classes

commented

Hi.
On my side, it doesn't even load, no matter which character I use. And the right mouse button does pretty much nothing, on both the icon and the UI setup. Ofc, the addon is turned on.
ElvUI is not installed.

commented

Hello, For enhancement shaman, Sundering and Crash lightning will still not be recommended EVEN IF YOU UNCHECK "use nameplate detection". You have to go into enh core and uncheck "crash lightning range check" and "sundering range check" due to the above issues. It's possible similar things may exist on other classes

Can confirm this is the case. Will also over-recommend lava blast on aoe, even 5+ targets. Essentially staying on the ST rotation unless you uncheck the ranged checks for sundering/CL

commented

Hello, I posted to closed issue #2950 re: Warrior Charge

Hello, I've followed the steps indicated for disabling target detection. I have installed wtf-b
https://pastebin.com/FcU1JwbG
Short video of charge popping up when the character moves:
https://www.veed.io/view/9abddd22-8a99-4a08-ab54-bf5f5e054b97?sharingWidget=true&panel=

commented

While in arms spec:

  • If you are in combat
  • In either multi- or single target situation
  • You are moving within melee range, and not standing still

It will recommend charge for some strange reason.

https://pastebin.com/KgSnvc2a

commented

I am aware of the changes with the range thing, and I'm not sure if my snapshot is correct, but thought I would post for Frost mage As cone of cold is not being recommended for AOE cheers https://pastebin.com/Kx8XjCkd

Cone of cold and frost nova are with range detection issue

commented

Hekili version v10.2.0-1.0.4
Arcane explosion is not suggested in Mage Arcane rotation.

commented

I discovered remote employment, which cannot be identified by nameplates. I suspect it might be due to an issue with this section of code on line 368 in Targets.Lua. Perhaps it should be: local checkPlates = not filterPlates and showNPs and spec and spec.nameplates and spec.rangeChecker?

commented

Choose Frost specialization for the Mage class, select the use of nameplate recognition, confirm that all nameplates are enabled, select the skills used for identification, unable to correctly identify nameplates on the screen

commented

Gnome, Prot Warrior. Once I am in melee range, the rotation stops advancing. If I back up beyond melee range, rotation starts cycling again. Doesn't seem to have any problems with fury or arms. Doesn't seem to happen with my DH (both specs) or rogue (combat). Just prot warrior.

I have bug sack and bug grabber installed. They captured no lua errors.

https://pastebin.com/VgkAnMxY

edit: redid the snapshot because I had a 2h equipped. Doh.

commented

I think still something is wrong with APL/range check for enh shammy. When there are more than 5 targets, still priority for EB/LB instead of chain lighting, which is not being shown in any situation - got a feeling like Chain Lightning is kind of cut out of the APL

All options like on pinned screen are on.

commented

I think still something is wrong with APL/range check for enh shammy. When there are more than 5 targets, still priority for EB/LB instead of chain lighting, which is not being shown in any situation - got a feeling like Chain Lightning is kind of cut out of the APL

All options like on pinned screen are on.

You'd need to supply a snapshot for investigation (it can be a new ticket), but I suspect that you have AOE Funnel Priority enabled which means you're trying to burn a single-target in AOE scenarios. If you uncheck AOE Funnel Priority, you'll probably see more Chain Lightning.

image