Hekili Priority Helper

Hekili Priority Helper

53M Downloads

[REC] Ele Shaman Ascendance conditions does not seem to work without an on-use trinket equipped

Closed this issue ยท 1 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

Shaman - Elemental

Describe the Issue

I noticed I was never seeing ascendance recommended ever for my ele shaman. Looking at the conditions for both the aoe and single target conditions for the Ascendance entry, I think it does not ever recommend ascendance if the "variable.ascendance_trinket" flag is false. From what I can tell based on my limited testing, this flag is ALWAYS false if you do not have an on-use trinket equipped. It is part of the first segment of the conditions:

( talent.first_ascendant.enabled | variable.ascendance_trinket ) & ( buff.fury_of_storms.up | cooldown.stormkeeper.remains > 12 | ! talent.fury_of_the_storms.enabled ) & ( cooldown.primordial_wave.remains > 25 | ! talent.primordial_wave.enabled )

Due to the AND operator, if you do not either have first ascendant talented or a trinket available to use this will never evaluate to true. I use preeminence talent and have two passive trinkets, hence why it never shows up. It needs to check to see if the trinket exists first before requiring a trinket to be available to use before recommending Ascendance.

How to Reproduce

Use preeminence talent in elemental tree, make sure you do not have any on-use trinket equipped, and perform opener. raidbots uses ascendance after prim wave/ancestral swiftness, hekili does not suggest it.

Snapshot (Link)

https://pastebin.com/pDWwjV60

Raidbots Sim Report (Link)

https://www.raidbots.com/simbot/report/4BNwhqZF2fNeXcRWdd8gwL

Additional Information

No response

Contact Information

No response

commented

This should be resolved in today's release.