OmniCC

Overview
OmniCC is an addon that adds text to items, spell and abilities that are on cooldown to indicate when they will be ready to use. In other words: it turns all the standard analogue cooldowns into digital ones.

Anything should work with OmniCC, from the action bars to the inventory, from the standard interface to your favorite add-on.

Bugs & Requests
Please submit bugs and feature requests at GitHub. You may post comments as well, but you will get our attention much faster there.

====== 5.2.1
* Fixed bug causing settings to reset at login.
* New option: spiral opacity! Now, instead of only being able to toggle them on/off, you can set how transparent they should look. Setting to 0% will hide them.

====== 5.0.5 (beta)
* Optimized the most important bottleneck in OmniCC, for better performance in intense battles.
** Hopefully, this will prevent most of the "script ran for too long" issues.
* Rebuilt OmniCC from the ground-up, for easier bug-fixing and feature addition.

====== 4.3.1
* Fixed a bug freezing the addon at extremely small durations

===== 4.3.0
* Updated for WoW 4.3
* Now follows the new Blizzard's *mandatory* cooldown model standard. Addons not yet supporting it may not be tracked by OmniCC properly.
* Dominos and Cornucopia are both confirmed to work with this new release.

====== 4.2.3
* Jaliborc: Reduced download size by about 70%
* Jaliborc: No more "Jaliborc:" tag from now on. If no tag is here, it means it was me.

====== 4.2.1
* Jaliborc: Added a button at the interface options for selecting the update engine
* Jaliborc: Several aestetical improvements to the options menu

===== 4.2.0
* Updated for 4.2
* Made pulse the default finish effect again, since its working without a flicker in the new patch.
* Adjusted update engine again to prevent some possible lag issues people were having.

====== 4.1.pancakes6:
* Altered settings to disable the finish effect by default. This is to workaround the flickering issue that people have been experiencing since the release of WoW 4.1

===== 4.1.pancakes:
* Extracted the timer scheduling code from the timer code.
* Created two scheduling engines for the timer: One based on the Animation system, and one based on the classic OnUpdate methods, with the animation system used by default. If you're experiencing crashes when using OmniCC, try switching to the OnUpdate engine.
* To switch to the OnUpdate engine, use
/run OmniCC:SetUpdateEngine('ScriptUpdater'); ReloadUI()
* To switch back to the Animation engine, use
/run OmniCC:SetUpdateEngine('AniUpdater'); ReloadUI()

====== 4.0.waffles7:
* More attempts at fixing edge cases, like a pulse happening when a cooldown starts.

====== 4.0.waffles6:
* Theoretical edge case bugfixes

====== 4.0.waffles4:
* Updated localization

====== 4.0.waffles3:
* Added back missing code to handle cooldowns of a day or longer.

====== 4.0.waffles2:
* Added support for deathknight rune cooldowns. Apparently the start time of a cooldown may now happen in the future :P
* Fixed Custom text appearing in the finish effect dropdown

===== 4.0.waffles1:
* This is a major new BETA for OmniCC. Major new features added:
* Added the ability to define settings groups: so that things like your auras/etc can have their own look.
* Added options to adjust text anchoring.
* Switched to using the animation system for timers, resulting in a major reduction in overall CPU usage
* For more information, please take a look at the new wiki page: http://code.google.com/p/tullamods/wiki/OmniCC4

====== 3.0.beta11
* Fixed a bug causing frames to repeatedly be created

====== 3.0.beta10
* Fixed an error causing the show cooldown models option to not work.

====== 3.0.beta9
* Merged some changes from tullCC: Text scaling should work properly again
* Split out the timer code from the config code

====== 3.0.beta8
* Fixed the invalid font issue

====== 3.0.beta7
* Updated localization
* Made a few tweaks to how frequent timers update

====== 3.0.beta6
* Reverted to using a single OnUpdate handler per cooldown text item. Turns out, it actually is faster with my old optimizations :P
* Added scale and opacity options for each duration
* Reimplemented the show cooldown models option
* Dropped the whitelist option. Added back support for the noCooldownCount flag.

====== 3.0.beta4
* Updated localization
* Fixed a bug causing the pulse/shine not to display unless running with the min effect duration setting at 0 seconds.
* Fixed a rendering issue on the pulse effect
* (Hopefully) fixed a bug causing cooldown timers to not properly hide when reset
* Cooldowns should now update instantly when a timer that is already shown is reset for one reason or another
* Removed Ears dependency

====== 3.0.beta3
* This time, it really should use a good bit less CPU than OmniCC 2 :P
* Tweaked text display to show 90 seconds or below as seconds, instead of one minute or below

===== 2.4.0
* Renamed Min Size, Min Duration sliders to Size Threshold and Duration Threshold
* Added a new slider, Finish Effect Threshold - Used to determine how long a cooldown must last before OmniCC will trigger a finish effect (pulse, shine, etc)

====== 2.3.2
* TOC Bump

====== 2.3.1
* Fixed a bug for users with no previous OmniCC settings

===== 2.3.0
* Removed pulse from the core. Reimplemented as a plugin (OmniCC_Pulse)
* For 51d cooldowns, OmniCC will now attempt to estimate the proper remaining duration.
* Added a hidden setting OmniCC.sets.minFinishEffectDuration: This setting controls how long a cooldown's duration (in seconds) needs to be to show a finish effect (ex, shine, pulse)
* Restructured the folder layout. Log out of WoW completely, delete all OmniCC folders, and install the new version to have everything work properly.

====== 2.2.5
* Updated Chinese translation

====== 2.2.4
* Added Korean translation.

====== 2.2.3
* Pulses will now only happen for cooldowns that have a duration > 30 seconds

===== 2.1.0
* Updated a setting to make LSM3 work properly.
* Fixed a bug with embeds.xml
* Switched to using noCooldownCount to signify that cooldown count should not display on an object, instead of noomnicc

====== 2.0.9
* Updated to LSM 3
* Unthrottled the updates for cooldowns with durations > 1 minute. This is to (hopefully) prevent an issue with the rogue ability Preparation.
* Reimplemented the slash commands

Are there any way to make OmniCC not obey the alpha of the parent frame? I use Macaroon and have set abilities on cd to be 0.3 opaque. That is a value that enables me to quickly see what abilities are not usable. However, I would prefer if the timers were more visible.

If you're experiencing crash issues, please download the latest beta (4.1.pancakes). If you continue to experience crash issues after installing the beta, then try the following command:

Code:

/run OmniCC:SetUpdateEngine('ClassicUpdater'); ReloadUI()

That'll switch from using the animation system for timers to using the old OnUpdate script system. Its a less efficient system than the animation system, but it should resolve any crashes you may experience.

The hopeful crash fixes are purely a shot in the dark, not sure if they'll fix you're issue or not. Thanks for another addon to take a look at, though, since I'm not able to reproduce the problem with Shadowed.

Feature request: unless I overlooked it, you can't set the numerical cooldown to only display once the remaining cooldown is below a certain treshold, for example a 30sec CD showing up once the CD is below 20sec, but not earlier.

I better explain my particular interest in this, even if it's kinda niche:
As a feral with Stampede, I made a macro that displays the cooldown of Feral Charge, but uses Ravage. I also made Feral Charge to display the duration of the Stampede buff with InlineAura, but the cooldown number kinda distracts from the duration number, and as the CD is higher than the buff duration, it wouldn't matter while the buff is up.
I guess this could be expanded to every cooldown that gives a short-duration (de)buff, if the user cares to set up the individual buttons via groups (and uses IA, but honestly, who doesn't? :P)

i'm currently using the default unit frames and love the option to position the cooldown text at the bottom of my buffs/debuffs on my target frame. but i am wondering is it possible to do this on ouf layouts?

im sure you have been asked this before so sorry if I bother you.
But is there a way or have you considered being able to move the numbers to specific place on action button?
instead of the middle lets say to the top left corner or exactly in the middle?

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.