The problem with lag tolerance is that it can make the game feel janky/laggy as hell at high settings, even if in theory it should be reducing lag it can make the game feel like the opposite is happening. Spell batching was effectively baked in lag, the lag tolerance is a true spell queue system that reduces lag but it can only handle one spell at a time. WOTLK Classic is never going to be the exact same because it runs on Legion or newer version of the WoW client (perhaps BFA or Shadowlands now?) and while original Classic had spell batching put in by request to mirror Vanilla, it was removed just before TBC came out, while retail WoW had spell batching naturally in some form until WOD, but that spell batching also varied from expansion to expansion and in Cata we got custom lag tolerance. That's effectively the same thing you're experiencing here. Especially noticable when players were trying to fit 5 GCD's within the Battle Cry (recklessness) window, if you didn't stagger you would need like 3% more haste to make it work. Because of this performance/lag related issue a lot of players could be seen weaving the FR ability half way around the GCD because it would eliminate this sluggish response behaviour. If you ever played Focused Rage Arms Warrior you would know how Warriors would stagger the use of Focused Rage between their other GCD's to avoid what felt like the spells were getting "stuck" in server latency and it would cause additional latency, like the ability would clog up the system if you used it at the same time as another ability. 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). What does "queue other spells" mean here? Basically you can queue a spell at most 400 ms before it becomes ready.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |