DEV: GCD off? Abilities Available Before the REC Suggests to Use Them.
Closed this issue ยท 4 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
Evoker - Devastation
Describe the Issue
Global CD display is wrong? I can use abilities about a second before the display tells me I can use them.
How to Reproduce
Normal rotation, the display says to wait to use something that is already available. Maybe not considering haste or just the global CD is incorrect?
What is your information source?
Snapshot - Contains errors/warnings
Snapshot (Link)
Raidbots Sim Report (Link)
https://www.raidbots.com/simbot/report/wZ17bNGr1Yp2T4BVG4NByH
Additional Information
No response
Contact Information
No response
The snapshot you provided waits 0.04s for the GCD to expire before Engulf, which is basically no time at all. Is there a snapshot where it is indicating more time than that?
Normal rotation, the display says to wait to use something that is already available.
In many cases, you don't use something immediately even if it's available, like Rogues who are waiting to reach a certain Energy amount before spending.
I understand how to play, it's specifically the empowered spells. I can use them before the recommendation says I can, by just a bit, but enough to be noticeable. I tried to catch it again: https://pastebin.com/qrbHWv72
That snapshot doesn't show any wait time; when you take a snapshot, unless you've disabled it, a screenshot is also created. It might be helpful to provide both.
I've made some changes related to channeled abilities that might be the actual underlying cause of this issue. If so, the fix should already be in place. Are you still experiencing this issue?