SexyCooldown
Upgrade Notice
Users upgrading from versions prior to 0.6.6 will lose any aura blacklist settings. A change was made to aura identification to resolve conflicts with skills such as Sacred Shield. Please re-blacklist any auras you aren't interested in after upgrading.
About
SexyCooldowns is a logarithmic cooldown bar. What's that, you say? Well, most timer bars you're used to are linear. That is, the distance between 0 seconds and 10 seconds is the same as the distance between 50 seconds and 60 seconds. A logarithmic cooldown bar is somewhat different - it represents cooldowns on a compressed timeline, so that cooldowns that are closer to being ready are represented as more active on the bar. This lets you represent a large amount of data on a single bar, and have it remain useful.
In short, SexyCooldown is a single consolidated timer bar for all your spell, pet's spell, item, and proc cooldowns, as well as buffs, debuffs, and totem timers. It's very flexible, and can be customized to fit into your UI as best you see fit.
Features
- Spawn as many bars as you want, and show the specific information you want on each.
- Supports spell and talent cooldowns, explicit and internal item cooldowns, buffs on you, debuffs on you, and debuffs on your target or focus.
- Very highly configurable look and feel. Build bars that will fit into any UI.
- Bars may be oriented horizontally or vertically, and move in either direction.
- Extensible - can support virtually any kind of timer. Currently works as a cooldown, buff, and debuff timer, but the possibilities are endless.
Demo
Here you can see that I have set up three separate bars, one for my cooldowns at the bottom, one for short buffs on me (<45 seconds) above my unit frame, and one for my debuffs on my target above the target unit frame.
In a raid setting (Click for HD):
Obfu: The first problem is a bug that I'll fix. For the second, the bar should become click-through once you lock it.
ayst: I'm working on tracking that one down. Do you know what action causes it?
Kazragore: The latest build has an "Inactivy Opacity" setting. Set it to 0 to cause it to disappear when there are no cooldowns.
honorix: You can right-click an icon to blacklist it from the bar. If you accidentally blacklist an item, you can remove it from the blacklist in the options.
Tried it out to replace ForteXorcist, since it's quite large and I only use the cooldown bar. It was easy to configure, and at first seemed an ideal replacement. I discovered 2 things that led me back to FX. 1. I could not get SexyCooldown to track my on use trinkets. They form a key part of my cooldown stacking strategies. 2. The bar is not click-through. This really restricts the placement options, and since this information is very important I like to have it near the centre of my screen.
Message: Interface\AddOns\SexyCooldown\prototype.lua:211 bad argument #2 to 'format' (string expected, got nil)
Time: 10/08/09 18:45:15
Count: 116
Stack: [string "Interface\FrameXML\BasicControls.xml:<Scrip"]:18: in function <[string "Interface\FrameXML\BasicControls.xml:<Scrip"]:4>
(tail call): ?
[C]: in function `format'
Interface\AddOns\SexyCooldown\prototype.lua:211 in function `CreateCooldown'
Interface\AddOns\SexyCooldown\core.lua:140 in function `AddCooldown'
Interface\AddOns\SexyCooldown\core.lua:211 in function `?'
...ion\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146 in function <...ion\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[1]"]:4: in function <[string "safecall Dispatcher[1]"]:4>
[C]: ?
[string "safecall Dispatcher[1]"]:13: in function `?'
...ion\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91 in function `Fire'
...arAutomation\libs\Ace3\AceEvent-3.0\AceEvent-3.0.lua:119 in function <...arAutomation\libs\Ace3\AceEvent-3.0\AceEvent-3.0.lua:118
Locals: (*temporary) = "%s:%s"
(*temporary) = "spell"
(*temporary) = nil
(*temporary) = "string expected, got nil"
Errors after hearthstoning:
and
Error after drinking mana potion with v0-3-1-g215a99b/:
[2009/10/08 03:13:09-411-x2]: SexyCooldown-1.0\prototype.lua:169 attempt to compare nil with number
SexyCooldown-1.0\core.lua:139 in function `AddCooldown'
SexyCooldown-1.0\core.lua:175 in function `?'
CallbackHandler-1.0-5 (Ace3):146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-5 (Ace3):91: in function `Fire'
AceEvent-3.0-3 (Ace3):119: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:118
Locals:
Sometimes debuglocals() returns nothing, it's one of those times... (FYI: This message is a HotFix from Decursive to prevent a C stack overflow)
---
Is it possible that the bar only show when you use any cd's and disappear when no cd's are on?
I love the flexible option, but I don't need to see things like hearthstone cd on it, makes it very filled and crowded. Will there be filtering?
1. When flame shock is used the icon that shows on the bar is earth shock icon.
2. When frost shock is used the icon that shows on the bar is earth shock icon.
Two things I noticed when I tested this out: 1. When frost shock is hit it shows as earth shock icon on bar. 2. When flame shock is hit it shows as earth shock icon on bar.
I only know of two (Forte and CoolLine) but choice can never hurt I guess :P
most cooldown bars that I know of is logarithmic (such as ForteXorcist), but I'm gonna give this a try anyway.