Hekili Priority Helper

Hekili Priority Helper

53M Downloads

[REC] ⚠️ Demonic Strength not recommended during Tyrant window in current Demo APL

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

Warlock - Demonology

Describe the Issue

Demonic Strength is no longer recommended after summoning tyrant, despite doing so yesterday.
After the update tagged 11.2.0-1.0.0m (“Demo: More current priority”), DS appears to have been removed from the APL entirely.

I went through a snapshot looking for something going wrong but its just not evaluated at all.
Every guide uses demonic strength after tyrant and even the current top sims, so I assume this is just an error.

How to Reproduce

  1. Enter game as Demo Warlock
  2. Talents: Demonic Strength and Summon Demonic Tyrant
  3. Perform opener or tyrant setup
  4. Demonic Strength is never recommended

What is your information source?

Based on Class Guides (e.g., IcyVeins, Wowhead)

Snapshot (Link)

https://pastebin.com/dS7dYq4A

Raidbots Sim Report (Link)

https://www.raidbots.com/simbot/report/kyE6kZMVagK3ZNPbxfJ5TR

Additional Information

No response

Contact Information

.dedd

commented

Warlock is not yet fully supported: #5010

commented

Sorry about opening a ticket on this, I skipped over that 11.2 status post while looking to see if anything was already posted. Since Demonic Strength was working before and then disappeared, I assumed it was a mistake rather than an unfinished priority. I’ll hold off until Warlock is fully supported. Thanks for clarifying!

commented

Resolved in latest release