-
-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unholy: Primary - Death Coil Auto Pop #4264
Comments
Looks like maybe it's trying to wait for the next rune to regen even though you already have enough? Will keep looking at it. If you have the screenshot that it took, please share it.
|
Another pastebin: https://pastebin.com/VufkY5Uq Slightly different I think, but @syrifgit asked me to add it in here. |
Here are some of the screens shots. Here is another paste bin |
With the screenshots I definitely think it's the rune thing we talked about @bjth. Do you want to PR that change you made using the FDK rune stuff? |
Sure, I got Wren to try it with the updated class file and he was still getting pops. I'll get a PR up later today either way. |
Glad I can be the test subject for you. It makes me feel a part of something important:-) |
The underlying issue here is the strict forking for AOE burst and regular AOE. When DND is wearing off, you can have enough remaining time to check the AOE burst list, but not enough time to actually select an ability from that list. There is also some nuance with Death and Decay itself ticking vs. having the buff from standing in DND. I am testing some changes to address these. |
Awesome, I can't wait to see what awesomeness comes along. Thanks you guys |
… with Frost) Relates 4264 Update Rune and RP logic to align with Frost
Before You Begin
Describe the Issue
Doing m+ and it auto snapped.
How to Reproduce
Do mythic and just auto popped.
Player Information (Link)
https://pastebin.com/9cvykm42
Error Messages (Link)
https://pastebin.com/9cvykm42
Additional Information
Just helping
Contact Information
Wren1740
The text was updated successfully, but these errors were encountered: