Haven't been able to play much today, but managed to do a vehicle type quest (slaying Thane Whatshisface in Grizzly Hills using a dragon) without any lua error messages after updating to 3.0.14 - thanks for the fix!

the issue should be fixed with 3.0.13.
Thanks for reporting (haven't found the issue as i use "Default" for me and the bug caused the Default to be active until Options opened ^.~)

Installed 3.0.13 and can confirm I no longer have to open and close options to force settings. Thanks!

EDIT: I'm getting a lot of errors that seem to be vehicle related. Been questing in Dragonblight today and when using abilities while driving a tank to destroy scourge wagons, flying a wyrmrest dragon or shooting a cannon to rescue npc's, I get "spells.lua:109: bad argument #1 to 'string_find' (string expected, got nil)" errors every time.

I think it's something that got messed up in one of your later MoP versions, because I seem to recall it wasn't happening in your earlier 3.0.x releases... Not sure which, think I used .3 (where it worked fine as far as I can remember) before updating to .12 and now .13...

Hey Obscuros,
i'll lookup the issue as soon as possible (i hope this evening i can give it a try)

the issue should be fixed with 3.0.13.
Thanks for reporting (haven't found the issue as i use "Default" for me and the bug caused the Default to be active until Options opened ^.~)

Installed 3.0.13 and can confirm I no longer have to open and close options to force settings. Thanks!

EDIT: I'm getting a lot of errors that seem to be vehicle related. Been questing in Dragonblight today and when using abilities while driving a tank to destroy scourge wagons, flying a wyrmrest dragon or shooting a cannon to rescue npc's, I get "spells.lua:109: bad argument #1 to 'string_find' (string expected, got nil)" errors every time.

I think it's something that got messed up in one of your later MoP versions, because I seem to recall it wasn't happening in your earlier 3.0.x releases... Not sure which, think I used .3 (where it worked fine as far as I can remember) before updating to .12 and now .13...

I'm running into a minor issue that's sorta bugging me. I have my notification output set to "None", yet the addon does not seem to care. Here's what I've noticed:

I log on, use an ability with a cooldown and the icon and timer display just fine. When the cd is done, even with the notification set to "None", I get the "cooldown ready" message. I type /cdb and close the config window without clicking anything, and after that everything works fine, no more messages. The notification setting still shows as "None" by the way, it hasn't changed to anything else - not as fas as the options show anyway. It's as if I need to remind the addon about my notification settings, and just pulling up the config window is enough (don't even have to go to the notification tab, simply /cdb and close will do)...

I've not created specific profiles, so I guess whatever changes I've made have been to the default profile. I can't completely rule out conflicting addons (yet), though I have tried disabling my other cooldown related addons. Still get the same behaviour from CooldownButtons I'm afraid.

Would be great if you could look into it. Like I said I consider it a minor issue, but it does get a little annoying having to pull up and close the config window every time I log on ;-)

Hey,

the issue should be fixed with 3.0.13.
Thanks for reporting (haven't found the issue as i use "Default" for me and the bug caused the Default to be active until Options opened ^.~)

I'm running into a minor issue that's sorta bugging me. I have my notification output set to "None", yet the addon does not seem to care. Here's what I've noticed:

I log on, use an ability with a cooldown and the icon and timer display just fine. When the cd is done, even with the notification set to "None", I get the "cooldown ready" message. I type /cdb and close the config window without clicking anything, and after that everything works fine, no more messages. The notification setting still shows as "None" by the way, it hasn't changed to anything else - not as fas as the options show anyway. It's as if I need to remind the addon about my notification settings, and just pulling up the config window is enough (don't even have to go to the notification tab, simply /cdb and close will do)...

I've not created specific profiles, so I guess whatever changes I've made have been to the default profile. I can't completely rule out conflicting addons (yet), though I have tried disabling my other cooldown related addons. Still get the same behaviour from CooldownButtons I'm afraid.

Would be great if you could look into it. Like I said I consider it a minor issue, but it does get a little annoying having to pull up and close the config window every time I log on ;-)

Real shame this addon was abandonded, I've used it since it's release until this patch (5.0X where it has finally broken). It was just very much to the point and easy to use. So, for anyone looking for an alternative I think Raven is the closest one that is being updated for MoP. Even though it has a lot of other functionality you might not need you can make it look and perform pretty much exactly like CDB.

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.