NeedToKnow

39 - Proc/Buff + Cooldown in one bar

Say for example you get a Buff/Proc, It'll show the Buff/Proc Bar when you gain it, then once the Buff/Proc wears off it will switch to a Cooldown Bar showing how long till it is ready again.

Using this method, you could create a lot less bars to show the same information.

User When Change
lieandswell May 04, 2010 at 13:54 UTC Changed priority from Medium to High
Kitjan Mar 31, 2010 at 16:24 UTC Changed status from New to Accepted
Retlaw Mar 16, 2010 at 01:14 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of dinesh dinesh Jan 16, 2011 at 18:29 UTC - 0 likes

    Might I suggest having the cooldown tracking run in the opposite direction of the bar movement? i.e. you cast the spell/effect, and the bar starts, moving from right to left. Once the effect ends, it switches to tracking the CD, and now the bar goes from left to right. Have the color be muted as well, or switch to gray shading, or some such as well. This way you know that all bars going in the wrong direction are counting cooldowns.

    You might also generally add an option to control the direction the bars work in (and cooldowns would always count in the opposite direction).

  • Avatar of Kitjan Kitjan Jul 06, 2010 at 16:38 UTC - 0 likes

    I've been playing with this off and on since 3.1.2, but I haven't gotten a version that feels good to use. I'm going to shelve this and work on other enhancements instead.

  • Avatar of Kitjan Kitjan May 05, 2010 at 14:56 UTC - 0 likes

    Oh, that is a nice extension of the concept

  • Avatar of lieandswell lieandswell May 05, 2010 at 00:38 UTC - 0 likes
    Quote:

    I'm not sure what you mean by watching a cooldown for an ability and an aura at the same time.

    For example, a bar that tracks the Tricks of the Trade buff on myself that then switches to the Tricks of the Trade cooldown when that buff is not on me.

  • Avatar of Kitjan Kitjan May 04, 2010 at 22:55 UTC - 0 likes

    ICDs start when the buff starts. Many ICDs are triggered by items, which can definitely have different names than the buff the ICD needs to watch for. I'm not sure what you mean by watching a cooldown for an ability and an aura at the same time. If the ability has a cooldown, it's not an internal coodown any more and we don't need to watch the aura.

    I was originally thinkin the two-bar display that's used for "sum all stacks" should suffice for the combo display... I'm not sure how to handle Berserking. There's a buff whcih can be procced from two different weapons and both appear to be cast by the player. Which cooldown do you display? Probably the one that will be available first, but the ICD code will update the cooldown when the second fires. Berserking makes this feature a real mess.

  • Avatar of lieandswell lieandswell May 04, 2010 at 13:53 UTC - 0 likes

    Moving this to high priority, since it's a cool idea that I haven't seen in other timer bar addons.

    Code-wise, we could do this with a single statusbar that has its own behavior, separate from aura-only or cooldown-only bars. Do internal cooldowns start when the buff ends or when it begins? The bar would start counting internal cooldowns at the appropriate time with its own bar.cooldownDuration variable. When the aura drops off, it switches to standard cooldown behavior until the aura appears again. For regular cooldowns we can use GetSpellCooldown() and wait to start counting unitl the aura disappears. Though maybe the code would be cleaner if we do it similarly for both.

    Bars that track spellID would only be able to use internal cooldowns, since auras have different spellIDs than the abilities that cause them. But if you do it by name then you could track auras and ability/spell cooldowns with the one name. Are there abilities with cooldowns that cause differently-named auras? If so, we may need to allow different names for each. DKs' Icy Touch causes Frost Fever, but Icy Touch doesn't have a cooldown.

    Graphically, it makes the most sense to me right now to have cooldowns be 0.5 or so of the aura's transparency, but keep the same background transparency. And a text indicator after auraName indicating it's a cooldown.

  • Avatar of Retlaw Retlaw Apr 19, 2010 at 04:07 UTC - 0 likes

    What i had been doing to work around it is creating one group of bars that shows the procs, and another group of bars that shows the cooldowns and placing them in the exact same location, so that after the proc wears off, the cooldown bar is already in it's place counting down.

    What i'm thinking is that for these dual-use bars, it blends the alpha in and out, so the buff fades away as it wears off, and the cooldown is fading in as it's replacement.

    For the config ui, possibly just give it a menu option where you use the default buff config ui, and another where it has the default cooldown config ui, and it just uses both of those as needed for displaying the apprpriate bar at the time.

  • Avatar of lieandswell lieandswell Apr 15, 2010 at 01:08 UTC - 0 likes
    Quote:

    Using this method, you could create a lot less bars to show the same information.

    Anything that displays the same information in a smaller, simpler package gets my vote. The most difficult part of this will be the config UI (as usual).

    I think keeping the same time/color for both would be fine, but I'd want the internal cooldown bar to be less visible than the actual proc. Maybe a transparency (alpha) option? Maybe cooldowns should fill from the right, so that they're more visible when they're ready/about to proc? You'd want to make sure it's easy to distinguish almost-ready from actually-proccing.

    And what about things like Berserking enchants, where you can proc more than one? Would you want the internal cooldown timer to start after the first one ends, or the second?

  • Avatar of Kitjan Kitjan Mar 31, 2010 at 16:24 UTC - 0 likes

    I have an idea how to represent this with two status bars in one, which will also be useful for Ticket 25

  • Avatar of Beutju Beutju Mar 26, 2010 at 02:10 UTC - 0 likes

    +3 from me =)

Facts

Last updated
Jul 27, 2012
Reported
Mar 16, 2010
Status
Accepted - Problem reproduced / Need acknowledged.
Type
Enhancement - A change which is intended to better the project in some way
Priority
High - Strongly want to resolve in the specified milestone.
Votes
8

Reported by

Possible assignees