Last Updated: Jul 19, 2018
Game Version: 8.0.1
Oct 11, 2010
tullCC adds cooldown text to any button with a cooldown (provided it's not too small). In comparison to other cooldown count addons, tullaCC offers less features and configuration but uses less CPU and memory.
Source code can be found on GitHub
Hi. I can't get the duration timer to work from Grid2's buffs/debuffs with TullaCC.
It does work with OmniCC, but I do like TullaCC better, and want it to work with it as well. Can you please check this? Thank you.
I am a beginner with lua. I want to increase the number size when a cd is under 5 seconds (red) from 23 to 27. Is this possible and if how ?
In reply to bloodywl:
So for performance gains, this is the way to go over Omnicc? :)
In reply to Onevik:
Been playing around with lua til the point of giving up and breaking everything, I was wondering if theres a way to have a MM:SS duration on cooldowns under 5 minutes been trying to find a way to implement it myself if it's possible and some guidance would be awesome, might be an idea of something you could add as an update to this with a config option of true or false. I know OmniCC has the feature however this is the only feature that I need from it so the performance tax for using omni is not worth it
In reply to Pendragon:
In reply to Tuller:
I love this as a lightweight and efficient omnicc alternative, but I have one big issue - on abilities with multiple uses (like Dire Beast), when you use one stack the entire icon is completely grayed like it's on cooldown even if you have another use remaining. This makes visibility of the remaining stack hard to see. The default Blizzard cooldown does not do this.
In reply to Ickz:
Just switched from OmniCC to this, managed to adjust the settings I wanted from the .lua files (font size, custom font etc), but can't seem to find a way to show text bigger when the cooldown is about to expire (the last 5 seconds, when text turns red). So for last 5 seconds before CD expires, I'd just want text scale to be 1.3. What kind of function should I need to change for that?
This is a limitation on the part of tullaCC, there's no per duration scaling.
Over the past week I've been having issues with tullaCC with raids buffs/debuffs. Below are 2 examples, one with just single buff and another more extreme example of many buffs.
I thought maybe it was ElvUI but after disabling it and just trying with default raid frames the issue is the same. Anybody have any ideas?
Hey sorry for posting a question for a Different AddOn but its from the Same Creator and hopefully i could get to him this way. Im reffering to OmniCC
Hey i still got the same Problems maybe now the Creator could answer or rather Fix the ISSUES i got.
I still got the Problem that if u Target someone and Dot him the Timer Display (The Number in the Frame of the Dot) is way to small compared to the Timer Display from WoD. The Problem is if i change the Size of the Timer Display everything else gets messed up so i would be really appreciate if the Creator please could somehow fix it here are some screenshots:
Back in the Day it looked like this:
and now it looks like this:
Latest patch (7.2) is causing this to use 40+% cpu usage. Any fixes?
tullaCC will always appear to use more CPU than most things, if only because at least one function is called for every cooldown fired.
I do have a possibly more efficient implementation that I wrote up today, though, but its only really geared towards handling the case of one cooldown, but many displays.
Well after a few minutes of playing the game will start stuttering every 3 seconds and I pinpointed it to this mod, I didn't get any lua errors though
Появляется КД даже на способностях, у которых несколько зарядов и использован первых из них :( WoW 7.2 + последняя версия tullaCC :(
Its showing CD timers on action bars with a stack of an ability still remaining. Looks like blizzard changed some code as its happening with other addons as well. Anyone know if its possible to fix?
I have the same problem. Also experienced it with CooldownCount. EDIT: seems even blizzards own cooldown display is bugged this way.[EDIT2]It was apparently LibActionButton-1.0 shipped with Bartender that was causing this problem.