Open Toludin opened 5 days ago
Seeing the same myself. Happening for my weakauras when I have omnicc enabled. Things likes vampiric blood show a cool down of DAYS.
just wanna add to this that i've noticed it only happens for me with auras that have charges(might also be the fact that it is disabling cooldown text in conditions) = it only happens from going from multiple charges to one(timer text hidden to timer text enabled), does not happen to any other aura as far as i've noticed and neither does it happen when going from 0 charges to one (timer text enabled at both 0 and one) https://wago.io/uDPh4LMCc this is example of one of my wa's that does it
Give us a clear and concise description of the problem, and what you expect to happen
Since the update to 11.0.3, I've noticed some CDs are displaying incredibly long CDs on the timer (even though the actual swipe is correct). I'm not sure exactly which ones, but you can see in this clip that:
https://warcraftrecorder.com/link/bbd14692-a68c-4ead-8617-411326476a6d
I reverted back to 11.0.2 and went to a test dummy and didn't see the issue anymore (specifically checking with Mind Blast). I then re-updated to 11.0.3 and tested again, and the issue was back.
Do you have any steps to reproduce this issue?
I haven't recently changed anything in my long-time setup for OmniCC. I'm not sure what caused this, though the changelog for the 11.0.3 update seems to indicate something related to the cooldown calculations might've changed. I use different themes for OmniCD and WeakAuras timers, and can provide screenshots of those if they'd be helpful.
Are you getting any error messages?
No, I don't have any errors related to OmniCC showing up in Bugsack.
What version of OmniCC are you running?
11.0.3
What version of World of Warcraft are you on?
Retail (11.0.5)
What other addons are you running?
Lots, though nothing new in the past few days that has changed. But if I seem to be an outlier in being affected by this, I'm happy to try removing them and seeing if I can find which one is conflicting. But given everything is fine when I'm back on 11.0.2, I think it's OmniCC-specific.