[REC] Demonology Warlock recommends Tyrant right before Charhound (Vilefiend replacement talent)
jmusick opened this issue · 5 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).
Describe the Issue
When following the rotation for Demo lock. Often times I'll find that Tyrant will be the current recommendation but the next recommendation will be Charound (Vilefiend replacement). The expected result would be that Charhound is cast first so that it's buffed and extended by Tyrant. This does not always happen, only seems to happen when the CDs get desynced at some point. If you start from scratch on a target dummy the Charhound is recommended early enough in the rotation that it gets buffed by Tyrant because it casts Hounds after Charhound.
It seems to be an issue where Hounds are already out and Charhound and Tyrant are coming off cooldown around the same time.
My guess is there needs to be some padding that if Charhound (vilefiend) is coming off CD within a few seconds, delay Tyrant a second to get Charhound into the Tyrant buff window. Not sure.
How to Reproduce
Follow Hekili rotation with Demo lock with Tyrant and Charhound talented.
Snapshot (Link)
Raidbots Sim Report (Link)
No response
Additional Information
No response
Contact Information
No response
There are priority updates for Demo Lock for 1.0.7 that may or may not address this. I'll need a ticket from 1.0.7 after it's posted.
The APL for Tyrant is not affected by Charhound/Vilefiend so this can happen with pre pull hound or desync holding CDs for something. Doesn't look like the APL will change either.
Have to make a custom condition, or maybe use the grimoire felguard interaction.
Conclusion doesn't look like the apl will change because it syncs 100% in a perfect world. Just giving some input from the demo lock apl guy.
This is not my ticket, but as a Demo lock I haven't experienced this after the new patch.
I have no clue if the owner of the ticket is still experiencing the problem.
For me it is a closed case 🙂
