Get an Epic Experience with Premium

OmniCC

Combat Login to Add Favorites
  • 139 Likes
  • World of Warcraft
  • 163,058 Monthly Downloads
  • Supports: 5.2.0
  • 12,334,206 Total Downloads
  • Updated 04/12/2013
  • Created 04/13/2006
  • 16,748 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: All Rights Reserved
  • Newest File: 5.2.3
or
Support development! **
Donate

About OmniCC

Doing pet battles? Check out my latest addon, PetTracker!

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.

Notes

  • Need help? Check the Guide!
  • Please submit bugs and feature requests at GitHub. You may post comments as well, but you will get our attention much faster there.
  • Visit me at jaliborc.com.
5.2.3
  • Fixed "Activate" effect incompatibility with some addons.
5.2.2
  • Fixed bug affecting new users on first login.
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.2.0
  • Updated for patch 5.2: The Thunder King
5.1.3
  • Fixed issue causing problems to users coming from extremely outdated versions (pankake and before).
5.1.2
  • Fixed issue causing the script engine to not be loaded properly.
5.1.1
  • Fixed bug causing french to be the default language.
5.1.0
  • Updated for patch 5.1: Landfall.
5.0.9 (beta)
  • OmniCC is now fully localized in french! (by Noaah)
5.0.8 (beta)
  • Fixed bug preventing the "None" effect from working properly.
  • Fixed several issues in the rules panel.
5.0.7 (beta)
  • Fixed bug preventing OmniCC from working with addons that do not support spell charges (ex: Ion).
5.0.6 (beta)
  • Fixed bug preventing OmniCC from working with addons such as Bartender.
  • Fixed settings migration issue.
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.
5.0.4
  • Added new Monocrome font outline option.
  • Added new Flare finish effect (artwork by Renaitre).
5.0.3b
  • Wrong file upload.
5.0.3
  • Fixed charges bug, still happening in some non-standard action bar addons (ex: Bartender).
5.0.2
  • Fixed bug causing abilities with multiple charges to show cooldowns before all are spent.
5.0.1
  • Tagging as release.
5.0.0 (beta)
  • Updated and tested for Mists of Pandaria.
4.3.2
  • Almost finished portuguese translations
  • Fixed a bug with the activate effect
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.2
  • Jaliborc: Introducing 2 new finish effects - "Activate" and "Alert"
  • Jaliborc: Fixed a bug causing the new update engine button to allways be checked
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.pancakes5:
  • Updated TOC for 4.1
4.1.pancakes4:
  • Updated localization and readme
4.1.pancakes3:
  • Fixed a typo that was causing a crash.
4.1.pancakes2:
  • Added new slash commands:
  • /occ config - Shows the options menu
  • /occ setengine <animation | classic> - Switches the timer update engine
  • /occ engine - Displays the current timer update engine
  • /occ version - Displays the current addon version
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.waffles12:
  • More hopeful crash fixes
4.0.waffles11:
  • Tweaks to hopefully prevent FPS/crash issues
4.0.waffles10:
  • Updated localization
4.0.waffles9:
  • Adjusted text update algorithm to hopefully prevent hanging updates
4.0.waffles8:
  • Added text anchor offset scaling for buttons of different sizes
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.4/3.1.4:
  • Fixed 0:59 display issue (for reals)
3.0.3/3.1.3:
  • Fixed 0:59 display issue
3.0.2/3.1.cata4
  • Removed 90s display
  • Fixed tooltip corruption (thanks cremor)
  • Updated localization (thanks cremor)
3.0.1/3.1.cata3
  • Removed 0 seconds display
  • Adjusted text scaling algorithm
3.0.0/3.1.cata2
  • First release of OmniCC 3.0
3.0.cata1
  • Updated toc for Cataclysm
3.0.beta16
  • Made font size independent of UI scale
3.0.beta15
  • More bugfixes
  • Moved LibSharedMedia from the core addon to the config addon
3.0.beta13
  • Applied some performance tweaks to the text updating algorithm
  • Applied some fixes to the text scaling algorithm
  • Applied some fixes to text display
3.0.beta12
  • Hopeful FPS bugfix
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.beta5
  • Updated localization
  • Added color options, tweaked the defaults
  • Added settings to control tenths of seconds display, as well as MM:SS display
  • Altered GetFormattedText to handle transition points a bit better
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
3.0.beta2
  • Fixed bugs for non US locales
3.0.beta1
  • Rewrote OmniCC. Delete all OmniCC folders before installing, or you may have issues.
  • Hopefully reduced overall CPU usage by a good bit.
  • Rewrote the options menu. Hopefully the font selector won't blow up anymore :)
  • Added whitelisting functionality via CooldownTextFrames.
  • Added blacklisting functionality.
  • Added the ability to disable text scaling
  • Merged Pulse and Shine into the core addon. Added a new options menu item to pick between them.
  • Changed the minimum size filter to minimum font size to hopefully make it a bit easier to understand
2.5.9
  • Updated French localization
2.5.8
  • Updated TOC for 3.3
2.5.7
  • Implemented kujanssen's bugfix for the noCooldownCount flag
2.5.6
  • Updated for patch 3.2
2.5.5
  • Increased frequency of updates at the seconds level to fix some tenths of seconds issues (hopefully)
2.5.4
  • Adjusted tenths of seconds timing to work for cooldowns under 2 seconds instead of 3.
2.5.3
  • Updated localization
2.5.2
  • Updated localization
2.5.1
  • Added a fix for displaying 0 seconds when in non tenths of seconds mode
2.5.0
  • Added an option to display tenths of seconds for durations < 3 seconds.
2.4.1
  • Updated localization
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.2.2
  • Added a check before calling GetTexture to prevent redbox issues.
2.2.1
  • Updated options menu code for the new Wrath build. This will probably break people on the PTR
  • Added Russian translation
2.1.1
  • Rethrottled the updates
  • Tweaked the no cooldown count flag to hide active timers.
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* Reimplemented the slash commandsndssssss

Comments

First Previous Page 106 of 111 Next Last
  • #359

    Thanks for all your hard work on this. :)

  • #360

    I think someone mentioned this earlier, but any way we can get a slider or alignment clicky to offset the location of the counter?

    With Dr.Damage running there's a bit of an overlap unless I shrink down both sets of text below my ideal threshold. There's plenty of room left if I offset OCC to the top of the icons with an optional amount of padding vs centered.

  • #361

    Thx Tuller,again :> always loved omni can`t see myself using anything else.Stop the bitching. Cheers

  • #362

    How to disable the countdown of the target buffs/debuffs? The number on target buffs makes the buff icons hard to recognize...

  • #363

    I agree. the Countdowns on buffs on character panels are geting in the way. Now I am unable to see how many stacks of Lifeblooms I have on a target because the countdown is covering everything. Other than that, this is one of the staple addons i ALWAYS recommend to people. Please fix the "countdowns on everything" problem. Thanks!

  • #364

    Hiding cooldowns
    By adjusting the minimum scale option, you can set how big an icon must be for OmniCC to display on it. The bigger the value, the bigger an icon must be.

    Bacon is a cheese.

    -- Tuller

  • #365

    (copied from my post on www.wowinterface.com , in case the author doesn't see it there)

    An error occurred recently in a Kara raid with v2.0.6 (recorded with BugSack/BugGrabber):
    "OmniCC\\full.lua:192: <unnamed>:SetText(): Font not set\nOmniCC\\full.lua:192: in function `UpdateTimer'\nOmniCC\\full.lua:126: in function <Interface\\AddOns\\OmniCC\\full.lua:124>"

    Same error has occurred previously here with v2.0.6 during a 5-man Heroic run. But this time it was so severe that I've had to uninstall v2.0.6 and revert back to v1.3.

    Windows PC, USEng client/server, WoW 2.2.3 live. During a pause in the action (not in combat, no cooldowns active), had someone switch to another character and I brought that character into the raid (as I was leader). They got automatically placed into raid group 3 as their former character had not been removed from group 1. Removed the former character from 1, change the new one from 3 to 1 and OmniCC goes nuts.

    The error above occurred and the BugSack counter on it kept rolling at high speed. Nothing I tried at the time would stop it (cast a spell, change the person out of the raid group, etc.) except, of course, turning on BugSack excessive-error throttling . The error counter reached 1500+ in a few seconds before I decided to exit WoW, delete 2.06 and revert to 1.3. I brought up the seemingly unrelated details of the issue (switching raid members around) as that's when it started.

    Have used v1.3 in two raids and several 5-mans since the v2.0.6 problem last occurred on Oct. 28. No errors and no problems with it. So am staying with v1.3 until this problem with v2.0.6 is fixed. Hope it can be.

  • #366

    I actually like the numbers on buffs/debuffs. Other than just disabling it completely, maybe you can make it so there's a separate number scale for the minimum icon size option. I would rather have the numbers displayed smaller than not at all, and yet still be able to see it bigger on the other icons. Also, you might consider being able the offset the number from the center which would be another solution. I wouldn't mind having both ways. ;P

  • #367

    I stuck a 2.3 version up. It includes another check for tiny font sizes (what I think people are getting errors from), and the options menu has been recoded for 2.3 compatibility. It should work on the normal realms, but I've not tested it there yet.

    Bacon is a cheese.

    -- Tuller

  • #370

    I run X-Perl as well, and you can turn of the X-Perl timer(s) very easily.

  • #368

    Hi Tuller - In a recent version of x-perl, Zeksie the author made a dot timer like yours. The problem is that these 2 doesn't works together very well, when showing the remaining time on dots and hots on your target. I don't think its complicated to solve, but a bit complicated to explain, especially since I don't have much time to get to the bottom of it at the moment - however, I hope you may be able to solve it.
    Basically, if I have both your addon and hit timers activated, there will be 2 timers running on the dot on my target. If I disable either addon/function I can't see the timer on my hots on my target.
    I can't say if it may be a bug in x-perl, but I have posted it as a comment there as well.

    Thanks for a great addon though:)

  • #372

    Noted, but I'm unsure how to fix this one.

    Bacon is a cheese.

    -- Tuller

  • #369

    erro for Taiwan wow 2.3

    omnicc 2.0.7

    can't show cooldown time

    http://photo5.yupoo.com/20071115/234316_128221533_jnskpyji.jpg

  • #371

    Thank you so so much!

  • #373

    I'm having a problem where my cooldowns reset.

    Scenario: I cast Blessing of Protection on someone, it goes on cooldown. We kill mobs, exit combat. With no target, my BoP will appear to be off cooldown. However when I try to cast it nothing happens, but it still has no cooldown timer. When I click on the person I cast the BoP on, however, the cooldown comes back. As soon as I click off that person, it goes back to showing no cooldown.

    It also does this for my Righteous Defense, making it very difficult to know if I can taunt or not >.< sometimes the timer is there, sometimes it isn't ^_^

    Tell me if you need more information...I don't know how else to explain it, though.

  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Infinite Crisis NA

Get Your Preferred Access Code!