Buff Timers
 

Is there a way to show a timer within a button? What I'm wanting, is to see a countdown timer within my Pulverize button so I can better see when I need to refresh it.

I've tried using that but Pulverize isn't tracking. Lacerate initially tracks but after using Pulverize (Which removes the Lacerate stacks), Lacerate stops tracking as well.

Another druid in need
 

I changed my layout completely for my druid after Cata. I kept the layout that I had used previously for my warlock. All cooldowns show properly for the warlock, however, when I play the druid, only one of the buttons shows a cooldown, but there are at least 10 others that should show. I have button editor> general> aura watch selected. I also have the toggle for "entire bar" set when I do this.

I have tried duplicatinng the settings from the lock to the druid, but it simply doesn't work. Also, to confirm that it isn't related to form switching, [edit:] (most of) the cooldowns do not show up for the caster form or the moonkin form. I am using the dual spec toggle for the bars, not profile switching. Will post again after I get a chance to check the other forms.

I play a frost mage, and i have the Freeze ability of my Water Elemental on a macro button on my main bar in addition to the pet bar.
The cooldown is working properly on the pet bar but on the main bar it doesn't show up. The macro is simply a /cast Freeze. Other cooldowns on my main bar (macro buttons) like Frost Nova are also working properly.

Update: Spell cooldowns for druid stances
 

I found a solution to the problem, but this should not be the best way to solve this problem. (@Dwargh: I do have both aurawatch and cooldowns selected for the entire bar.) The problem was that I was using a macro button type for the spells that show correctly for the lock. I was using action ids for the druid. I just had to rearrange the locks layout and ran into the same problem I had with the druid. If a spell is placed on an action id button, the cooldowns etc do not show. However, going into the macro section and allowing the autowrite to create the macro causes the display to work properly. I hope this gives you a place to start looking for the basic problem in macaroon. I am getting so many errors. So many errors, in fact, that bugsack decides to quit collecting errors after one minute. I think my game performance would be a lot better without that :).

I used to have that many errors myself. but after deleting all old Macaroon saved vars for the now no longer existing macaroon modules, along with the old modules themselves they went away. Also IF you're using the Autohide:ModKey display patch I posted then there was an coding error in that explained in the comments how to fix.

I only get one error now and that has to do with Macaroon Macro Master
This has no significance atm and only comes when one logs in.



Question: You're saying if you have a button with a spell autowritten in the macro button(by dragging a spell onto it) and then changes back to ActionID button you can see the CD, but not if the macro part is empty?

Or do you need to use the macro button for it to display?

This is great news indeed!


It only works if I use the buttons as macro buttons. The spell works fine when I place a blizz macro on an action id button, but the cooldowns and aurawatches don't display. If I copy the macro from the blizz macro to the macaroon macro, then use the macaroon macro, the spells and the text display work correctly.

Now that you've mentioned the old saved var files being a problem though, I'm going to go remove all those. Will post back to let you know if that solves the problem.

Thank you!

@ Dwargh: Thank you so much for the suggestion of removing the old var files. My errors are almost nil now! However, removing those did not correct the display of the cooldowns/aura watches. I still need to use a macro button instead of an action id button to see those.
Also, I'm not sure whether its specific to Macaroon (kinda doubt it) but, when I use a /petattack command in these macros, the displays are correct, however the pet acquires a target and attacks even though I haven't given him a target to attack. I should be getting the "You don't have a target" message. I'm thinking this is a blizz issue though.