[REC] Archon Shadow Priest fails to maintain Voidform for more than 60s
Amortalist opened this issue · 10 comments
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
Priest - Shadow
Describe the Issue
When playing Archon in an Archon optimized gear (32% haste) on Dummy, Hekili consistently fails to maintain Voidform for 90s (which is near mandatory for the build) and it usually falls off around the 1 mn mark. It seems to not prioritize DP enough. Raidbots sims with both buffs and no buffs no lust shows to keep Voidform for at least 80+ seconds.
How to Reproduce
Play Archon ST build on Dummy, do ST rotation
What is your information source?
Based on my own Raidbots Quick Sim results
Snapshot (Link)
Raidbots Sim Report (Link)
https://www.raidbots.com/simbot/report/jyQ8s63BZxwfhM9g2iML6j
Additional Information
No response
Contact Information
I was trying to find the right place to snap shot this as well, but my initial observation is it sits with Mind Blast at 2 charges ALOT during Voidform.
Hrmm, it's weird. With Archon I underperform my quick sim by about 400k when following Hekili, but I match my sim with Voidweaver. That’s not a scientific analysis—I just don’t know when to snapshot, because no individual recommendation looks wrong as far as I can recognize in time. I'll keep tinkering with it to try and find some useful information.
Can you add context to your snapshots? For each of them, what did you think should've been recommended at that time instead?
example of falling off voidform by using Halo instead of DP : https://pastebin.com/b7q2xWi5
Per discussion in Discord, need to model:
- Halo (baseline)
- Power Surge (Halo in 5s, Halo in 10s) - hasted?
- 2pc (2 Insanity per sec for 5 sec) at time of Devouring Plague cast - hasted? refreshed, overwritten, or multiple applications?
- 4pc (similar stuff)
Syrif worked on these models, but there are no Power Surge / Halo / set bonus related Halo events queued before your Voidform would expire in that last snapshot.
If you can do Halo, immediately Devouring Plague, and then snapshot, that'd be helpful.
Just to add some context from the Discord discussion so it doesnt get lost:
- 4pc does extend power surge by 5s per application
- 2pc does generate 10 insanity over 5s per halo ring, so a halo cast without any interaction generates 10 + 10/5s Halo per Spawning Ring (=60 insanity total for 3 rings). A "full" Halo with 2 additional rings from 2pc generates 100 insanity overall.
- The modelling is already there by Syrif, but seems to be implemented wrong. See
TWW3ArchonTriggerand thereset_precastparts. - might be important: the 10/5s is subject to pvp diminishing returns (getting 41 insanity instead of 60 for 3 rings)
Halo DP DP Snapshot by @Amortalist https://pastebin.com/qepDaB9B
Going to mark this as closed for now, if you find improvements beyond the fixes submitted, we can discuss
Unfortunately this is going to require a lot more work than just a snapshot of voidform falling off when you don't have enough insanity to cast DP. That doesn't really showcase over a minute worth of addon decisions that led to this point.
Can you find specific examples of incorrect recommendations during voidform?
Adding videos here to keep a trace : https://youtu.be/oneSmoO7GJo
Basically it seems to often try to cast something else before using DP meaning it tends to fall off .5s per .5s
It's pooling a lot and sends DP to "not overcap" instead of maximizing the refresh time. Sometimes VF falls off at the last second because something else was recommended before (like Mindbender)
Not sure what to snapshot here.