Evoker Pyre Priority bug/issue maybe?
mightymist3ry opened this issue ยท 15 comments
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).
WoW Version
Retail (Dragonflight)
Describe the Issue
Im noticing pyre stacks overcap and other abillities will recommend use such as Shattering star followed by another azure strike then into pyre. i also notice when insta free cast avalible its not recommending pyre asap either, i was told if the ability pyre is free (procced) its good to use fast on aoe regardless of stacks. But could be wrong.
Will add some screeshots with some extra detail from a friend who tested aswell.
How to Reproduce
- Enter game as dev evoker
- Do AOE rotation on 3+ targets following sequence
- Watch sequence till pyre overstack (sometimes) or not get used when insta essence on aoe.
Talent Loadout
BsbBnWR3R1Z1HmbUKIpvm3XXhDIAAAAAAgWIJikQgEJlkkASLgESSAJJSESSC
Snapshot
Raidbots Sim Report (Link)
No response
Additional Information
No response
Contact Information
Thanks for the Snapshot. Fire Breath, Shattering Star, and Eternity Surge are much higher in priority than Pyre; it looks like Pyre is recommended as soon as they are out of the way in the snapshot you provided.
Devastation; Primary - Fire Breath(0.00), Shattering Star(0.82), Eternity Surge(1.74), Pyre(3.18), Pyre(4.40), Azure Strike(5.63), Azure Strike(6.86), Azure Strike(8.09)
So far, this makes sense because you'll want to use those ASAP such that their cooldowns can start regenerating sooner.
For reference, the priority list works by recommending the highest item in the list that has its conditions met, that is off cooldown, and that has its required resources available.
- The Fire Breath recommendation is effectively the 20th item in the list.
- The Shattering Star recommendation is the 23rd item in the list.
- The Eternity Surge recommendation is the 26th item in the list.
- The Pyre recommendation is the 30th item in the list.
That means, if all of these items were available at the start and had all their requirements met, these recommendations came out in the correct order.
A snapshot that matches those screenshots would be interesting. Seeing Azure Strike over Pyre with max stacks definitely sounds wrong. It's possible that is from an earlier release and has since been fixed, if you're not able to replicate it.
Thanks for the Snapshot. Fire Breath, Shattering Star, and Eternity Surge are much higher in priority than Pyre; it looks like Pyre is recommended as soon as they are out of the way in the snapshot you provided.
Devastation; Primary - Fire Breath(0.00), Shattering Star(0.82), Eternity Surge(1.74), Pyre(3.18), Pyre(4.40), Azure Strike(5.63), Azure Strike(6.86), Azure Strike(8.09)So far, this makes sense because you'll want to use those ASAP such that their cooldowns can start regenerating sooner.
For reference, the priority list works by recommending the highest item in the list that has its conditions met, that is off cooldown, and that has its required resources available.
- The Fire Breath recommendation is effectively the 20th item in the list.
- The Shattering Star recommendation is the 23rd item in the list.
- The Eternity Surge recommendation is the 26th item in the list.
- The Pyre recommendation is the 30th item in the list.
That means, if all of these items were available at the start and had all their requirements met, these recommendations came out in the correct order.
A snapshot that matches those screenshots would be interesting. Seeing Azure Strike over Pyre with max stacks definitely sounds wrong. It's possible that is from an earlier release and has since been fixed, if you're not able to replicate it.
He was using the same version as i was this test was about 2 hours ago in the screenshots above, im not sure i can get a snapshot of that at this time unelss i recreated the issue exactly. i think the event is rare but happens sometimes
this is due to a problem with Essence regeneration
No, that is not settled. There is an issue related to Essence regen as well that I'm testing a fix for, but that logic does not necessarily impact this at all.
edit: I do see how it can be that; since Azure Strike has a higher priority entry when capping Essence isn't imminent. I want data to confirm, though.
https://pastebin.com/347myDiy - Think this is the best one. I was at 20 stacks on Pyre, no essence burst. Had 3 essences, I have 5 icons shown, it showed Azure strike x3, then shattering star, THEN Pyre. So 5 actions later when I had 20 stacks of charged blast on pyre and 3 essence. This was a 3 target count on Automatic on dummies. I took 2 other snapshots though as well.
Basically on 3 target count it should be 10 stack of charged blast, it should be recommending Pyre almost immediately, even before Fire Breath and Eternity Blast as this is AOE and packs die to fast. At 4 target count it should be recommending Pyre ALL the time as long as we have the essence for it, doesn't matter the charged blast stacks at all. At 4 targets its worth spending the essences on Pyre without any stacks.
This has the same root cause as #1980 so I'm closing as a duplicate. The next release will include a fix.
This has the same root cause as #1980 so I'm closing as a duplicate. The next release will include a fix.
Excitement!
I've been noticing the lack of prioritization for Pyre with charged blast too, thank you so much for posting this! There is tons of overcapping going on.
I think this logic may not be working correctly right now.
https://www.wowhead.com/guide/classes/evoker/devastation/rotation-cooldowns-pve-dps
This has the same root cause as #1980 so I'm closing as a duplicate. The next release will include a fix.
Was doing a dungeon today and while i notice pyre is recommended more sense latest update. I did see today that me having my aoe targets set to 3 and while attacking 3 targets i am recommended to use Disintegrate vs pyre in one of the snapshots, then in the other i was fighting 4+ targets and essence came up and im recommended to do 4 more azure strikes and by that time the mob would have been down. I see alot of evokers just launching pyre so much in aoe 3+ compared to me while following hekili. Also if i set hekili to AOE vs Auto it never shows Disintegrate in it. So maybe something is up with the auto mode to? im unsure. Hopefully this data helps!
With Scintillation and Eternity's Span, you use Disintegrate at up to 3 targets.
The priority will probably continue to change, but this is what is available at the moment. You can customize your priority if you want it to do different things.
With Scintillation and Eternity's Span, you use Disintegrate at up to 3 targets.
Is that cause of my talent setup?
With Scintillation and Eternity's Span, you use Disintegrate at up to 3 targets.
The priority will probably continue to change, but this is what is available at the moment. You can customize your priority if you want it to do different things.
I was told if Volatility talent is used then Pyre is much better on 3 target.