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

I get the exact same error, whenever i open omniCC config and try and select the font dropdown box it doesn't have any drop down at all and isn't clickable.. Is there a way to fix this? copy some fonts somewhere? is it being confused by perhaps the ace library in fubar vs the ace3 in addon directory or soemthing like that?

Hello, I have a long-standing problem with OmniCC that had forced me to disable it. I have not tried OmniCC since around version 2.4.

On my old system OmniCC caused in-game slowdown if I opened windows (e.g. character gear sheet, quest log) while grouped like in instances. On my old Athlon 1.8 the frame rate would dip to 2-3 fps. Even on my Core2Duo 2.6 I notice frame rate drops and sluggishness although it doesn't drop as low. There is no noticeable performance drop when I am opening windows and not grouped.

I have tried running with just the default Blizz UI and OmniCC but it still happened. Does OmniCC do something funny in the background when windows are open and when you're grouped? I don't see anyone else reporting anything similar.

Flash/pulse do not really work on debuffs, since the flash itself is semi parented to the cooldown's parent. So, when the parent is hidden (as is the case of buffs when they expire), the flash goes away.

Haha, my English is not good Can I have your Email?I want you to look at a pictures and i hope to have that effect on the image.

Flash/pulse do not really work on debuffs, since the flash itself is semi parented to the cooldown's parent. So, when the parent is hidden (as is the case of buffs when they expire), the flash goes away.

Originally posted by Juunas Hi, so im getting "attempt to index field 'long' (a nil value)" long, medium, small errors and what im here asking is that, is there any solution to fix them, or must I stick with these errors until they're fixed?

Hi, so im getting "attempt to index field 'long' (a nil value)" long, medium, small errors and what im here asking is that, is there any solution to fix them, or must I stick with these errors until they're fixed?

Originally posted by slammurai i'm not sure what the problem is, but i've disabled all the timers that come with pitbull 4 so that only omnicc's timers will show. the problem is that now that i'm using both pitbull 4 and omnicc, omnicc shows timers for both my debuffs and everyone else on my target (whereas in the past when i didn't have pitbull 4, it would only show timers for the debuffs i put on it.) anyone have this problem?

It's not a problem, it's a program design. And since OmniCC is a service module, this is a PitBull design.
Go blame them.

i'm not sure what the problem is, but i've disabled all the timers that come with pitbull 4 so that only omnicc's timers will show. the problem is that now that i'm using both pitbull 4 and omnicc, omnicc shows timers for both my debuffs and everyone else on my target (whereas in the past when i didn't have pitbull 4, it would only show timers for the debuffs i put on it.) anyone have this problem?

Originally posted by Dreadthill Anyway to disable OmniCC's countdown on Pitbull frames? It appears that when I put the Buffs/Debuffs on the player frame (versus the standard Blizzard area) Omni throws up cool down. Problem is Pitbull already has a cool down for the buffs/debuffs in that area.

Anyway to disable OmniCC's countdown on Pitbull frames? It appears that when I put the Buffs/Debuffs on the player frame (versus the standard Blizzard area) Omni throws up cool down. Problem is Pitbull already has a cool down for the buffs/debuffs in that area.

Is it possible to have Omnicc functioning like previous version..ie
When u cast a spell/abilty it will grey out all the action bars and do a clockwise count/turn for one global cooldown instead of showing (1) for one global cooldown on current version?

Timing and things will be reviewed when I start working on the next version.

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.