[BUG] Rune costing abilities are sometimes unusable despite having the runes active

[MHMabrito]

1. Current Behavior

1.1. Description

Currently, sometimes you are unable to cast a DK spell that spends a rune, even though you have runes available.

1.2. How to Reproduce

I have been unable to reproduce this in a controlled environment. All of the examples of this happening have happened while raiding.

1.3 Source Material

Example One: Video: https://www.youtube.com/watch?v=ejiTr4iqqLk&ab_channel=persian Logs: https://classic.warcraftlogs.com/reports/VPrRDqvyX1Kjd8hb#fight=14&type=casts&source=21&start=1681544&end=1703990 Description: In the above example, you the video clearly shows he has runes available but D&D is grayed out. To confirm this wasn't a WA or UI bug, you can cross reference the logs with the bosses health to see a abilities casted and by the time between them can tell there were indeed runes available. Also, it's worth noting that he was able to cast D&D only after he used one of the active runes that were unusable with Icy Touch (a single rune costing ability).

Example two: Photo: https://imgur.com/8miEcq4 Description: You can see he has 2 Blood Runes, 1 Death Rune, 1 Frost Rune, and 1 Unholy Rune available. Looking at his bar though, every Rune costing ability is blacked out except for Plague Strike.

Will add more examples as they come in.

2. Expected Behavior

2.1. Description

You should be able to use abilities that cost runes when you have the runes available.

[MHMabrito]

Wanted to circle back around here and add some more evidence the DK community has brought fourth.

In this clip: https://clips.twitch.tv/SuccessfulThirstyHareNononoCat-ixDil8a9w_GBFL1o Around the 0 second mark, you can see his individual casts a Bloodboil, while they have a Frost Rune available. If you look at Icy Touch on their Action bar, it's not registering that there's an active Frost Rune, it's only recognizing the one currently regenerating.

In this clip: https://gfycat.com/cheerfulfrigidfluke Right at the start he uses Plague Strike with Unholy Rune #2, exactly 10 seconds later, Unholy Rune #2 has regenerated, but you can see on his action bar, the game is not registering the Rune as active - despite him pressing Plague Strike multiple times and the rune being available.

In this clip: https://gfycat.com/athleticbriefapatosaur The exact same thing is happening again as above, but it's with a Blood Rune this time. He uses Blood Boil at the start, goes to use Blood Strike 10 seconds later to refresh Desolation but the game is not allowing him. This one in particular is interesting because it shows that a Blood Rune is active, but on his Action Bar, his Blood strike lines up with the regeneration of his Unholy Rune.

In each example above, the abilities regeneration countdown lines up with a different type of Rune than is it's spender Rune. Reviewing multiple vods, and logs all confirms the same thing - that for some reason either: A. Your ability isn't registering itself as a spender of the correct Rune. (This could be the behind the scenes check and balances that the ability does to ensure a rune is available, and for some reason it is getting it mixed up. Not allowing you to use that ability until that "check" is complete by the rune it is identifying with becomes available. It will not spend the "wrong" rune, as it is properly identifying the requirement for it to be used, it seems to only happen occasionally that rune spender abilities are put on the cooldown of other rune types. In my opinion, this seems like the most logical cause. or B. Your runes aren't registering themselves as the correct Runes.

[vindruvor]

PoV from a friend (Naxx25 raid 2022-Dec-15): https://streamable.com/mzjac5

You can see that there is one Frost and Unholy Rune ready but Icy Touch and Plague Strike are both on CD. Runes can be seen in the middle (weakaura) but also at the top left (default UI runes).

This occurs around 42seconds into the fight (https://classic.warcraftlogs.com/reports/kBFL62q1dWhZAw4a/#fight=17&source=13&type=damage-done&view=timeline) just when his last Death and Decay is cast. You can see that 2 Frost runes and 2 Unholy runes are ready -> DnD is cast -> 1 Unholy and 1 Frost rune remain but Icy Touch/Plague Strike can't be cast for another 8sec.

[MHMabrito]

Can also find a vod here: https://www.youtube.com/watch?v=9FSyxgS8vnU At roughly 10 seconds in, this player can't cast D&D despite having the runes available. Here's the logs to confirm time wise that he did infact have the runes available, and this isn't just a wa bug: https://classic.warcraftlogs.com/reports/GpWxvTy2dQ714YBZ/#fight=last

[BigSamuela]

I have the same problem with Army of the Dead. I use the exact same opener each fight, but sometimes I cant use Army for like 5 seconds, even if the icon in the action bar and the runes are ready. Before I use Army, I always go ERW->BS->IT->PS->Gargoyle->Army

[harleyj]

Some further examples of this behavior in the VODs below: Example 1 (Dropbox link) Example 2 (Twitch)

The current thread on Blight Club is here: https://discord.com/channels/894792866658930688/1045965621956968448

My theory is that the server sends "current usable runes" as a response to the player using a spell-costing rune ability - the bug is that some runes (seemingly at random) are flagged as unusable, or on permanent cooldown. After you cast a rune-costing ability, or interact with your runes in some way (e.g. blood tap), the server responds with another update, showing that your runes are actually available and ready to use.

I've only observed this behavior in raids. I suspect it could be some strange interaction with another player's spells.

[Stuffemcv]

Any update on this issue ?? The issue seemed to have solved itself towards the end of ulduar, and wasn't much of an issue in TOGC, but since ICC patch, this has happened on almost every boss fights.

The only way to unbug it, is using another run for another ability (if it's possible) and that makes the bugged rune usable again.

[idesu]

I join the speaker above. I came across this bug on every CD in Ulduar. I recently returned to the game to go to the ICC and I see it again. The problem was so annoying that this time I dug into what was going on and found this bug report from a year ago.

[Speaker1264]

Seems to occur when you spend a rune at the same time another rune of the same type comes off cd. In the case of the first video you can see he spends blood rune 2 at the same time blood rune 1 comes off CD, bugging it out, and preventing it from being used. I'm guessing the game thinks both runes got spent until you use another rune ability, and it does some sort of re-check and sees that the other one actually has not been spent. In most situations you are spending your runes as soon as they come off CD, which is why you don't typically encounter the bug, but as you saw the person in that video had his blood rune off cd for at least 2 seconds, if not more, since that's all the video shows. Spend your runes as soon as they become available and you won't encounter this bug. the video i was referring to: https://www.youtube.com/watch?v=ejiTr4iqqLk&ab_channel=persian