Hekili Priority Helper

Hekili Priority Helper

46M Downloads

[REC] Warrior Fury,Execute priority seems wrong

Closed this issue · 11 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).

Spec

Warrior - Fury

Describe the Issue

Hekili doesn't seem to recognize the target's "Marked for Execution" debuff, it always prompts me to use Execute even if the target doesn't have any "Marked for Execution"
1111

How to Reproduce

1.using fury slayer
2.target health ≤ 20% or 35%(choose Massacre)
3.single or multi-target combat

Snapshot (Link)

https://pastebin.com/TVXw8Jw8

Raidbots Sim Report (Link)

No response

Additional Information

No response

Contact Information

No response

commented

2222
target doesn't have any "marked for execution" and I didn't choose "Ashen Juggernaut"

commented

Link a quicksim.

commented

There's a good chance this is a dummy-only issue because of how tracking resets on enemy death and combat exit. Will investigate.

commented

这很有可能只是一个虚拟问题,因为跟踪会在敌人死亡和战斗退出时重置。将进行调查。

no, this DEBUFF will not be reduced and will always show 3 layers.

commented

这很有可能只是一个虚拟问题,因为跟踪会在敌人死亡和战斗退出时重置。将进行调查。

PLS FIX

commented

Can you provide a snapshot where this is happening on real enemies (not target dummies)?

commented

Also: There are updates to the Fury priority in the next release.

commented

Can you provide a snapshot where this is happening on real enemies (not target dummies)?

Yes, any target is like this. "11.0.2-1.0.20a" is correct. "11.0.5-1.0.7" still has this bug.

commented

That's not a snapshot.