With the default 400ms queue window, the game play feels awful.I don't think it's a bug tho, even in Legion this was an issue. That being said, I still consider this a bug that should be fixed or at least improved. I will take your advice and try it out next time when I have a chance.

Again doing something like this was a sign of a really bad player, terrible gameplay advice. But even in Legion you could do it with Focused Rage. Macroing it to all your abilities would cause you to just rage starve all the time, whether tanking or dps you're talking about clown levels of performance, like kicked from the raid performances.Īnd actually they didn't remove this possibility until Heroic Strike was removed entirely in Legion. Heroic Strike was used for rage management, and you would very often not have the rage to use Heroic Strike. They eventually changed heroic strike so that this didn't work.Doing something like this is something really really bad players would do, it's not normal gameplay. In BC, heroic strike was not on the global cool down, so you would macro heroic strike to all of your warrior abilities which were on the GCD. However, I do remember how Heroic Strike worked in BC. I don't have a clear memory of how heroic strike worked in this specific version of Wrath. Which means its supposed to work like that. So what do you think?Havent played vanilla or classic in ages but I did main warrior for ages and I want to distinctly remember heroic strike/cleave specifically is queued to be on your next melee hit. I have made a video recording and posted it on Blizz forums -> bug report, but got no response whatsoever.

What you should do is play the game like in WOTLK, which means you should spam your keys as abilities are about to come off cooldown. So what do you think?I'm not sure this is a bug, because WOTLK didn't have spell queue, it's a modern feature that has been ported to a game that has gameplay elements that no longer exist. Then of course it would fail, because the server knows the spell is not ready yet. So instead of putting bloodthirst in a short queue, the game will try to cast the bloodthirst immediately. If HS/Cleave is in queue, then there won't be any queue for other spells, say bloodthirst. i haven't tested DK/Druid yet, but it could also be the case). This spell queue works fine, until you are also queuing spells that works with your next weapon swing (heroic strike and cleave. For example, you can queue the next spell before the current spell finishes casting or if the next spell is in cooldown, you can queue it 400 ms before it completely cools down (this include GCD). Note that the numbers will change for any characters below level 120.What does 'queue other spells' mean here? Basically you can queue a spell at most 400 ms before it becomes ready. If you want to use the macro simply replace the '_'s with the number of the bg you want. Any bgs below SVM (silvershard mines) which are ToK, Wintergrasp, Ashran and Seething Shore do not function properly since the script only checks for a single numeric digit, and it does not account for the scrollbar. So all you have to do is press “Join Battle”.Īs a reference point the BG codes are numeric so for a 120 character it is as follows. My macro queues for the 1st one and selects the 2nd one. If you want to select 2 bgs the WoW interface does not allow you to queue for both simultaneously. If you like to queue for the same bg or bg(s) all the time (for me its WSG and AB) a macro makes it easy. While messing around with my macros I found a timesaver.

Wow spell queue macro