Hekili Priority Helper

Hekili Priority Helper

44M Downloads

[BUG] Frost mage can't switch to AOE action list even if the condition was met

tangaiyun opened this issue · 6 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 issue (above) so that it describes the issue I am reporting.
  • I am reporting an issue with the default priority included with the specialization (imported or edited priorities are not supported).

Describe the Issue

for my frost mage, I setup the targeting as following:
image

so you can look I checked "Use Nameplate Detection" and Detect Damaged Enemies"

and I setup the display mode always as automatic as following:
image

So when I fight with Cleave training dummies, which inlucdes five targets, but it never recommends skill Blizzard, and "AOE" queue shows the AOE conndition is not match even if I cast an AOE spell to do damage on all five dummies.
image

I watched the profile, there is a sentence as:
actions+=/call_action_list,name=aoe,strict=1,if=active_enemies>=7|active_enemies>=3&talent.ice_caller

Hekili should switch to aoe action list when the condition "active_enemies>=7|active_enemies>=3&talent.ice_caller" meets, as you know, there are five dummies, and my frost mage has the talent ice_caller, my talent looks like:
image

so the condition "active_enemies>=3&talent.ice_caller" should be matched, but the Hekili didn't not switch to the AOE action list

How to Reproduce

  1. set up talent as:
    image

  2. setup Hekili toggle as :
    image

  3. setup targeting as:
    image

  4. then fight with the five Cleave training dummies, you will see Hekili would not switch to the AOE action list

Snapshot (Link)

https://pastebin.com/W2dviCWM

Raidbots Sim Report (Link)

No response

Additional Information

No response

Contact Information

No response

commented

Nameplate target detection supersedes and rules out targets. You're only counting targets within 12 yards of yourself.

Your snapshot would provide more information if it were taken at a point where you clearly have multiple targets and after your initial cooldowns have been used -- it's not even reaching the point where deciding between ST and AOE takes place.

commented

Thanks for response. I uploaded two snatshots : https://pastebin.com/0SLLpLsb and https://pastebin.com/X4bRC9S2
, before took these two snatshots, I cast serveral AOE spells (such as Arcane Explosion) on the five Cleave training dummies. At the same time, I disable the “Use Nameplate Detection", now my targeting config looks like:
image

but it seems still wound not switch to the aoe action list.

commented

Are you using a WeakAura called "Better Hekili Targeting" or anything like that? (You should not.)

commented

Uncheck "On Screen Enemies Only" -- that is a nameplate-based filter as well and only counts enemies with nameplates on screen. Also, nameplates must be visible to count with nameplate detection, too. It looks like your nameplates are set to only appear for your target.

commented

thanks for your response. I solved this problem by checking "Display All Nameplates", but I still have a question:
I unchecked the "Use Namepalte Detection" and checked "Detect Damaged Enemies", why Nameplate display mode would still affect enemies detection? In my opinion, "Use Namepalte Detection" and "Detect Damaged Enemies" should be "OR" relationship, that means anynone meets, the enemies should be counted. I am confused about the current enemies targeting algorithm.

commented

I have plans to refine target detection in a number of different ways. In the current state, nameplate (and nameplate range) is only meant for melee or players with a melee pet who use pet-based target detection. That's why nameplate detection is disabled by default.

I do plan to clear up the messaging as well, but we're in the midst of new patch chaos so it won't be in the immediate future.