Hekili Priority Helper

Hekili Priority Helper

53M Downloads

[REC] ⚠️Sublety Rogue recommending Symbols of Death twice

Closed this issue · 3 comments

commented

Before You Begin

  • I confirm I am using the latest version of the addon (outdated versions may have problems that were fixed on the newest release).
  • I confirm I am playing on official Blizzard servers (not private servers).
  • I checked for an existing, open ticket for this issue and was not able to find one.
  • I have updated the issue title to clearly describe the problem.
  • I am reporting an issue with the default specialization priority (not a custom or imported priority).

Specialization

Rogue - Sub

Describe the Issue

As discussed on Discord in DM's with Syrif, there is an issue with Symbols of Death casting twice in a row when a target dummy is close to dying.

I changed the action ingame to this:

( buff.symbols_of_death.remains <= 3.5 & variable.maintenance & ( active_enemies >= 3 | ! buff.flagellation_buff.up | dot.rupture.remains >= 30 ) & ( ! talent.flagellation.enabled | cooldown.flagellation.remains >= 30 - 15 * ! talent.death_perception.enabled & cooldown.secret_technique.remains < 8 | ! talent.death_perception.enabled ) | boss & fight_remains <= 15 & buff.symbols_of_death.down  )

Which fixed it for me.

Also feedback from Fuu, confirming it's not an APL issue;

Image

How to Reproduce

Perform an opener on a target dummy and right after opener it recommends Symbols of Death twice.

What is your information source?

APL Conditions - I found a possible typo or mistake

Snapshot (Link)

https://pastebin.com/raw/REuRBC0A

Raidbots Sim Report (Link)

No response

Additional Information

No response

Contact Information

No response

commented

File under: tweak to account for actual gameplay, will implement

commented

This shouldn't occur on dummies, regardless, so partially an issue with Kelpfist not being flagged as a dummy.

The proposed priority change still makes sense, though -- the logic to dump CDs works, so I'll make the change.

commented

Fix for this has been committed, should be in next release.