Get an Epic Experience with Premium

ButtonTimers

Buffs & Debuffs Login to Add Favorites
  • 10 Likes
  • World of Warcraft
  • 9,355 Monthly Downloads
  • Supports: 6.0.2
  • 438,342 Total Downloads
  • Updated 10/15/2014
  • Created 02/16/2009
  • 584 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File: 2.5.14
or

About ButtonTimers

ButtonTimers is action buttons with timers attached. The timers can be configured to show a buff/debuff or the cooldown of a spell. The timers are highly configurable, with lots of options to play with.

Important note:

There are a limited number of action slots (1-120). These correspond to 10 bars of 12 buttons each. These are the same 120 slots that every action bar mod has to use (Bartender, PitBull, Blizzard's standard UI, etc.)

Chances are you aren't using all 12 slots on all 10 bars. You can configure ButtonTimers to use any of the 120 action slots you want. Do this with the "First button on bar is.." slider in the bar configuration.

If you don't change the "First button on bar is..", the bars will default to bars 10, 9, 8, 7. Note that bars 7-9 are by default the stance bars, so if your class uses stances you may wish to change it.

Getting Started:

When you first start the mod, you will see 4 bars of 12 buttons each. Open up the options (in the interface->addons panel), and disable the bars you won't be using. Next change the number of buttons from 12 to however many buttons you would like to see.

Now change the action slots the bar is showing you. Just take the action offset slider and slide it until you see some unused action buttons. Then drag the spells/abilities of your choice onto the bar.

The default is to track dots/debuffs/buffs. If that's what you want the timer to reflect, you are done. If you want to see a cooldown instead, select the configuration for the button and change the selector from "Aura" to "Cooldown".

There are lots of configuration options, go ahead and play with them. But that should be enough to get you started.

Bar configuration options are:

  • '''Bar Enabled:''' enable / disable the bar.
  • '''Hide out of combat:''' don't show the bar out of combat.
  • '''Bar Locked:''' lock the bar in position so that it cannot be dragged.
  • '''Orientation:''' horizontal or vertical layout for the buttons on the bar. You can also put the timers on the buttons themselves.
  • '''Timer Location:''' you can select whether you want the bar be on the left or right of the button (in vertical orientation) or above/below the button (in horizontal orientation)
  • '''Button Spacing:''' the space between the buttons on the bar.
  • '''Bar Scale:''' size the whole bar larger or smaller
  • '''Bar Length:''' length of the timer bar
  • '''Button Count:''' number of buttons on the bar (1-12)
  • '''First button on bar is..''' action slot number of the first button on the bar. Blizzard gives 120 action slots, which are traditionally allocated into 10 bars, but this mod gives a finer control over which slots you wish to use. Just slide this control until you find some unused slots.

Button options are:

  • '''Type:''' Set whether you wish to monitor a cooldown or an aura on the default bar target. You can also monitor both aura and cooldown. The cooldown will show up on the button and the aura timer on the bar if you select both.
  • '''Timer Type:''' The timer can either be shown as a percentage of the aura/cooldown duration or in fixed time. For example, if you choose a fixed time with a time of 10s, a full bar will always represent 10 or more seconds. This makes it easier to see which aura/cooldown will complete first, regardless of the spell's length.
    • '''Bar Time:''' This sets the max time displayed on a fixed time timer bar. Any timer durations longer than Bar Time will show as a full bar.
  • '''Show others' spells:''' By default, the timer will only monitor auras on the target if you were the caster of the spell. Click this button if you wish to see other's spells as well. The timer will always show your own spell if you have one on the target. Note: Pet spells do not count as being cast by you, so if you wish to monitor a pet spell then click this button.
  • '''Other Auras:''' By default, an aura timer will monitor the bar's default target for an aura matching the name of the spell on the action button. In this field you can enter additional auras (in a comma separated list) to look for.
    • "Show Aura Icon:" When checked, the icon on the button will update to match the aura we are showing the timer for.
    • "Ignore Button Aura:" When checked, timers will only be created for the auras specified in the Other Auras field. If Show Aura Icon is also checked, then the icon on the button when no timer is present will be the first aura listed in the Other Auras field.
  • '''Cooldown spell:''' By default, a cooldown timer will monitor the cooldown on the action on the bar. But you can also enter a spell name to monitor instead.
  • '''Bar Color:''' The color of the timer bar.
  • '''Target:''' This will select the default target (to target, focus target, self, party, pet) for all actions on the bar. It also controls what target to monitor for auras.
  • '''Use as spell target:''' If set, target will be the spell target as well as the target to monitor for the selected aura.
  • '''Warn less than cast time:''' Change the bar color when timer less than cast time. Also tints the action button.
  • '''Warning Bar Color:''' Bar color for timers when remaining time less than cast time.
  • '''Adjust Timer:''' Number of seconds to add to timer (can be negative).

Command line options:

'''/buttontimers reset''' - reset bar positions to default

'''/buttontimers config''' - open the configuration dialog (can also be accessed on Blizzards interface -> addons panel)

------------------------------------------------------------------------
r59 | stencil | 2014-10-15 09:32:58 +0000 (Wed, 15 Oct 2014) | 1 line
Changed paths:
   A /tags/2.5.14 (from /trunk:58)

Tagging as release 2.5.14
------------------------------------------------------------------------
r58 | stencil | 2014-10-15 09:25:27 +0000 (Wed, 15 Oct 2014) | 1 line
Changed paths:
   M /trunk/ButtonTimers.toc
   M /trunk/Core.lua

bug fix - return values for GetSpellInfo changed, affects us when we're looking at the casttime of a spell
------------------------------------------------------------------------
r56 | stencil | 2014-10-15 01:58:29 +0000 (Wed, 15 Oct 2014) | 1 line
Changed paths:
   M /trunk/ButtonTimers.toc

... and version number /facepalm
------------------------------------------------------------------------
r55 | stencil | 2014-10-15 01:57:37 +0000 (Wed, 15 Oct 2014) | 1 line
Changed paths:
   M /trunk/ButtonTimers.toc

bumping toc file
------------------------------------------------------------------------

Comments

First Previous Page 1 of 60 Next Last
  • #918
    ButtonTimers dual profile

    First of all thx a lot for this addon, it's a must have in my UI since many years :)

    Then a question: till 2013 (i stopped for 1 year) enabling the dual profile created also 2 different profiles named "CharName - primary" and "CharName - secondary". I don't remember i ever did something special. Now it seems it uses as deafault always the same profile and if i want to switch between 2 of them i have to create a new one and set the addon. Does It work as intended or am i missing something?

  • #919

    The difference between "then" and "now" is actually a difference between "characters that had used buttontimers before dual profiles were added" and "brand new characters".

    So, originally the addon had this weird behavior where it saved a few bar settings (like position) seperately based off what profile you were in, but the majority of the settings were shared which was really yucky and confusing.  So, when I added the support for LibDualSpec, there already was existing data that did, or could, differ between specs and so to preserve it the user was migrated into the two different profiles.

    I didn't do anything for new characters, I guess thinking that not automatically configuring a second profile seemed more like the conventional thing in addons using LibDualSpec.  In hindsight, this was probably a poor decision. 

  • #915

    Thanks for all your work on this add-on! It's quite easy to setup and has been an excellent support for advanced buff and debuff management. I've used it extensively on my monk during MoP and most recently with the WoD patch I opted to level my Warlock and noted a particular feature missing.

    I'm not sure if you do feature requests, but given you play a Warlock perhaps you may find a use for this as well?

    I noticed you have a warn below cast time option. For Affliction specifically I found it would be especially helpful if this could be adjusted to instead warn when debuff is below x seconds(eg Agony <7.2s, Corruption <5.4s, etc). The old pandemic mechanic is now a staple game mechanic gained by other classes with DoT's/HoT's in the WoD patch so I feel an option like this would greatly help to visually fine tune spec gameplay through the addon if added.

    It's my only want in an otherwise very complete addon. I haven't had any issues with it in the WoD patch(thanks!).

    Last edited by Ryozaras on 10/23/2014 9:58:35 AM
  • #916

    I may get around to adding that, but not sure when. In the meantime, my suggestion would be, for those spells, to set the TImer Type to FIxed Time and the Bar Time to the time when you would refresh.  That way if the bar is still at max size then you know it's too early to refresh; once it starts shrinking you can safely recast.

  • #914

    working great now.  Hanx!

  • #913

    This is a silly request, but Masque no longer retroactively supports arguments that call on ButtonFacade. Is there any chance to get the outdated ButtonFacade arguments changed to Masque so the addon can be skinned again?

  • #917
    Quote from timewitch »

    This is a silly request, but Masque no longer retroactively supports arguments that call on ButtonFacade. Is there any chance to get the outdated ButtonFacade arguments changed to Masque so the addon can be skinned again?

    Well, it would all depend on how complicated it is and how much work would be involved.  I don't know anything about ButtonFacade or Masque so I don't know yet the answer to those two questions. My first reaction is to wonder if the the reason Masque dropped the support is because the two had become too divergent, in which case that would mean the conversion could be complicated. Anyway, I'll try to take a look at it but I can't promise anything.  I've still got some other addons that I think need work for WoD and those should probably get the priority before supporting skinning (unless it turns out to be very easy fix).

    Last edited by stencil on 10/24/2014 3:30:06 PM
  • #909

    sage: ...ace\AddOns\ButtonTimers\Libs\AceDB-3.0\AceDB-3.0.lua:263: bad argument #1 to 'sub' (string expected, got nil)
    Time: 10/14/14 20:25:22
    Count: 1
    Stack: [C]: in function `sub'
    ...ace\AddOns\ButtonTimers\Libs\AceDB-3.0\AceDB-3.0.lua:263: in main chunk

    Locals: (*temporary) = nil
    (*temporary) = 1
    (*temporary) = 2
    (*temporary) = "string expected, got nil"

     

    That's the error I'm getting.

  • #911

    So, it looks like its an AceDB bug. I install Ace3 as a standalone addon to be sure that I have the most recent version which is why I didn't see the bug.  I'm going to check in the toc bump which should result in a new package containing new ace3 libs and that should fix the problem.  Weird though ... I'd have thought that if you had even one addon running with the latest version of the ace3 libs then that would have been what was loaded and we'd be fine.

    Anyway, I ran with only ButtonTimers and a bug catcher addon and reproduced the problem. Then I synched the ace3 libs and the problem went away so I expect a new release would fix the problems.

  • #904

    Yes it keeps crashing!! an amazing addon and would like to see a WoD updated 6.0 please

  • #905
    Quote from Retrojunk22 »

    Yes it keeps crashing!! an amazing addon and would like to see a WoD updated 6.0 please

    I haven't encountered any errors from it. I haven't tried it with the patch, but I popped into the beta last night and it seemed to be working. Can you open a ticket on the development site (there should be a link above) and provide the crash info?

  • #907

    Different commenter here.I don't remember having trouble with it in beta, but in live 90% of the time it isn't even showing up or the bars are vanishing completely. If I can snag some errors, I'll send mine in as well.

    Edit; Posted some of the errors to the Project Page.

    Last edited by timewitch on 10/14/2014 8:01:39 PM
  • #902
    Plz update for WoD

    luv this addon

  • #903
    Quote from Xogal »

    luv this addon

    Are you seeing any errors or just getting the out of date thing because the toc number hasn't been updated yet?

  • #912
    Quote from Xogal »

    yes.  i have them both selected.  Have even tried disabling other addons to see if any were interfering.  No matter what I cant get the bars or config screen to appear.  Im not getting any errors tho.

    I've put out a new version. It bumps the toc number (so no longer out of date) but more importantly (I think) is packaged up with a newer version of the ace3 libs.  Lemme know what happens.  Weird that you aren't seeing any kind of error though as the other posters who have reported errors seem to be getting the same one (which hopefully means there's just the one problem).

  • 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 »

VIP trip to SMITE World Championship