You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Give us a clear and concise description of the problem, and what you expect to happen
I expect a pulse finishing animation to fire whenever a cooldown within my settings becomes ready. Currently this ONLY happens for spells with more than 1 charge. So the finishing animation fires for Lava Burst and Riptide but not Flame Shock for example.
Screenshots can help quite a bit.
On WeakAura
On default actionbar
Do you have any steps to reproduce this issue?
Tested with both original action bars and WeakAuras, same results on both. Plug and play or messing with the settings does not matter, always same results. Have not tried anything with rules but I don't know if that would help in any way.
Are you getting any error messages?
What version of OmniCC are you running?
11.0.2
What version of World of Warcraft are you on?
What other addons are you running?
None.
The text was updated successfully, but these errors were encountered:
Give us a clear and concise description of the problem, and what you expect to happen
I expect a pulse finishing animation to fire whenever a cooldown within my settings becomes ready. Currently this ONLY happens for spells with more than 1 charge. So the finishing animation fires for Lava Burst and Riptide but not Flame Shock for example.
Screenshots can help quite a bit.
On WeakAura
On default actionbar
Do you have any steps to reproduce this issue?
Tested with both original action bars and WeakAuras, same results on both. Plug and play or messing with the settings does not matter, always same results. Have not tried anything with rules but I don't know if that would help in any way.
Are you getting any error messages?
What version of OmniCC are you running?
11.0.2
What version of World of Warcraft are you on?
What other addons are you running?
None.
The text was updated successfully, but these errors were encountered: