CD timer error

Aarthas · 12-14-09, 06:07 PM

I've noticed what seems to be an error in the ability cooldown timer with my deathknight. It will sometimes think scourge strike has 5 seconds left on its cooldown when really it will only have a second or two. So for example, it will begin counting down from 5, 4, then refresh at 4. I assume the existence (or near existence) of a death rune will be at the heart of this issue. It's an annoying bug because it causes me to stare at scourge strike instead of believing the timer that comes up on it.

Try using the following rotation to replicate the problem.
PS-IT-BS-BS-SS-DC-HoW
SS-DC-SS-SS-DC-(DC)

IT - Icy Touch
PS - Plague Strike
BS - Blood Strike
SS - Scourge Strike
DC - Death Coil
HoW - Horn of Winter
( ) - Indicates you should use if possible

Spec - http://www.wowhead.com/?talent#jfVMM...ux0uIqo:LsbMmV

Glyphs - Glyph of Dark Death, Glyph of the Ghoul, Glyph of Icy Touch

spiel2001 · 12-14-09, 06:13 PM

See if this post answers your question for you on the cooldown counter...

http://www.wowinterface.com/forums/s...light=cooldown

Aarthas · 12-14-09, 06:22 PM

I don't think this explains the situation. Scourge strike does not apply anything to the target. It is not a HOT or a DOT. The only timer mechanism that should apply to it, is the timer count down until the attack can be used again (i.e when will the correct runes be refreshed). Thus I still believe there is a bug here.

Xrystal · 12-14-09, 06:32 PM

Yeah, this was one that I couldn't find an explanation for either. Usually these queries are due to the cooldown and debuff both having a timer of different values. But, I am now wondering whether the debuff timer is latching onto another spell linked to it and using that as well.

Perhaps the tests used to determine a debuff timer is returning a value from somewhere and it is confusing the issue. Perhaps an earlier debuff that is being reused ?

spiel2001 · 12-14-09, 06:51 PM

My apologies for misunderstanding the question.

Is it possible that your runes are on cooldown? Scourge strike requires one unholy rune and one frost rune. If you don't have one of each, then the cooldown timer would be showing you the amount of time until your runes will come off cooldown and allow you to cast scourge strike again.

Aarthas · 12-15-09, 12:17 PM

Yes you're right it does require 1 unholy and 1 frost rune. The issue though is that the timer makes you think you are going to need to wait longer then you really do. It starts counting down from 5 seconds on some occasions, leading you to believe you have 5 seconds until your next scourge strike. Then after 2 seconds of countdown, when there is the number 4 on top of scourge strike on the action bar, it just refreshes and is ready to use again. The timer numbers on top of scourge strike just disappear, they don't change color and continue to countdown. It just disappears and scourge strike is completely active and ready to go.

spiel2001 · 12-15-09, 12:29 PM

Well... I strongly suspect this has much to do with the complexity of the DK game mechanics and I'm not sure what the solution is. The countdown "time remaining" on the spell is coming from Blizzard's code, not mine.

If I had to guess, what's happening is that when you do the scourge strike when this happens, you are missing either a frost rune or a unholy rune to be able to execute the next scourge strike. However, some event or action either causes the missing rune to refresh or, more likely, causes you to convert a rune to a death rune which makes what was going to be a 5 seconds cooldown suddenly a zero second cooldown and, voila, all the sudden you are able to cast a scourge strike that a moment ago you couldn't cast.

The problem is there's no way to predict this. The only data I have to work with is the data WoW provides and if WoW says it's 5 seconds, I have to believe it is 5 seconds and there's just no way I can predict it's going to be something less.

Aarthas · 12-15-09, 12:47 PM

OK. I will try to pay attention to the circumstances a little more closely then. It is one thing if a player blood taps causing a death rune to appear instantly causing the timer to refresh on the spot. But I don't believe that or any similar mechanic is happening. There is no way to instantly refresh runes other then 2 abilities that require you to click them (blood tap and empower rune weapon) both of which I didn't use in the circumstance. There is no other hidden or passive way to suddenly gain runes.

So what I think is happening can be best explained with an example. Consider the case where you use blood strike, which converts a blood rune to a death rune that is usable after the 8 second normal rune refresh. Two seconds later you use scourge strike, so 1 set of unholy and frost runes now have 8 seconds until they refresh, while the death rune now has 6 seconds to refresh. Two seconds later you use plague strike, which requires 1 unholy rune. The situation is now 4 seconds until your death rune is refreshed, 6 seconds until the frost/unholy rune set is refreshed, and 8 seconds for the 2nd unholy rune to refresh, with 1 frost rune unused. So, the timer I suspect would think that you have 6 seconds to wait before you can cast your next scourge strike, because that is the quickest a new set of frost/unholy will become available. However, it is ignoring the fact that a death rune will be avilable in 4 seconds, combined with the existence of an already unused frost rune, would allow you to use scourge strike in 4 seconds, not 6.

I know thats hard for any non DK player to follow, but I'm not sure of any better way to get that across. I needed to get that out so that I can be sure my issue is understood (eventually). I won't post anymore about it and accept that it's blizzards code that is at fault unless you ask me to. Thanks for the attention.

Xrystal · 12-15-09, 12:54 PM

Thanks for the explanation. The Death Knight is one class I never could handle. Tried twice and got 2 levels out of it before giving up. Even a warrior I managed to get to level 25 before getting bored with all that boring melee

spiel2001 · 12-15-09, 12:55 PM

I believe the "Death Rune Mastery" talent in the Blood talent tree does this... I'm not sure if the conversion resets the cooldown or not though... I've honestly never looked that closely.

What we need to figure out is what exactly is causing the 5 second timer initially and, then, what it is that is modifying the timer. Keep in mind that the cooldown value is coming directly from Blizzard, not from a calculation of my own.

EDIT: FWIW -- I do have a level 80 DK of my own and I do see exactly the mechanic you're describing. I'm just not sure there's anything I can do about it. It actually sounds like this may be a bug in the Blizzard game engine.

Aarthas · 12-15-09, 03:29 PM

It is reaping in the unholy tree that converts a blood rune to a death rune for the unholy spec I listed in my first post. If you read the wording carefully for reaping it says it will convert a blood rune to a death rune when it activates. You still need to wait out the 8 second cooldown to use the death rune.

Alpha Dog · 12-16-09, 08:10 AM

Like Aarthas I'm having a similar timing issue, although with a different spell as I play a Warlock.

When I cast Conflagarate, which has a 10 sec cooldown the timer might start counting down showing 7 or 8 (usually 8 but not always

) seconds till next use. Then when the timer is down around 2 sec & I think I can use Conflag soon, it will continue down to 0 sec & then refresh to the actual time remaining from the initial 10 seconds.

During this countdown period the button fades out as normal with no changes in colour.

This started with the 3.3 patch so I'm sure it's a Blizzard issue & not nUI.

Hope this info helps.

Devilmon

Xrystal · 12-16-09, 09:11 AM

http://www.wowhead.com/?spell=17962

Countdown = 10 secs
Debuff = 6 secs

Normally this should show 10 seconds in one color for 4 seconds then change to another color at 6 seconds and be available for reuse. I couldn't see any talents that may reset the cooldown or cut down the cooldown. Hmm, I see Backdraft affects your next set of spells but not your existing but whether that is affecting it or not I don't know.

Hmm. 3.3 Warlock change :

Conflagrate: Redesigned. This talent now consumes an Immolate or Shadowflame effect on the enemy target to instantly deal damage equal to 9 seconds of Immolate or 8 seconds of Shadowflame, and causes additional damage over 3 seconds equal to 3 seconds of Immolate or 2 seconds of Shadowflame. In addition, the periodic damage of Conflagrate is capable of critically striking the afflicted target.

Do those numbers seem to be reflecting what you are seeing ?

Alpha Dog · 12-16-09, 11:05 AM

I'm not sure if the burst damage/DOT damage of Conflagarate is the problem or not, but whatever burst/dot accounts for, the cooldown is still 10 seconds till next use. So a cooldown timer should ignore those I would think.

Devilmon

spiel2001 · 12-16-09, 12:29 PM

Is the timer purple for the first six seconds, then turns yellow (maybe red) ?

Alpha Dog · 12-16-09, 06:02 PM

I just tested on the dummy's & what I found was;

Cast Conflagrate, button "browns out", timer shows 6 sec, counts down to 0, resets to 4 seconds, still "browned out" counts down to 0 & is usable again.

Colour never changes from a brown out, just the same colour as it was pre 3.3.

The annoying thing is that in the heat of battle when I glance at the timer & see 4 or less seconds remaining I cant tell if thats the FIRST or SECOND time it's reached that point.

Devilmon

neuralassassin · 12-16-09, 06:05 PM

What color is the timer is what scott was asking I believe as that will give us some idea of wither it's seeing the debuff or just using the cooldown. Though either way if its Blizzards calculations and nUI just receives them like scott said don't know how much anyone can help really

Alpha Dog · 12-16-09, 08:16 PM

Colour never changes from a brown out, just the same colour as it was pre 3.3.

I thought I made it clear that the colour was just a browinsh colour, browned out, not purple, yellow or red, it doesnt change at all, which is why I don't think it's seeing or acting on the other spell effects.

neuralassassin · 12-16-09, 08:40 PM

hmm misunderstood thought you meant the icon was browned out sorry about that. You don't by chance have another mod like omniCC on by mistake? I can't seem to remember the numbers ever being a brown color with nUI's buttons, are all you cooldowns and dots showing in that color? Maybe toss up a screen shot if you get a chance

spiel2001 · 12-16-09, 09:05 PM

A screen shot would be most appreciated, or a series of screen shots as the counter goes through the phases. As already noted, nUI does not ever use "brown" as a counter color.

A list of the other mods you have installed would also be helpful.