AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Blizzard spell queue window12/30/2023 ![]() ![]() It wasnt a system that was implemented back then, and it is completely illogical to queue an ability outside of the spellqueuewindow, and then it disables any other interaction with the spellqueuewindow till the next melee hit is processed. ![]() So I dont see much reason to discuss whether its authentic wrath behavior. The iteration of the current spellqueue system is not like it was back when it was introduced in cata. With the 4.3 patch the lag tolerance slider was introduced.Īnd at that point heroic strike was changed "is no longer a On-Next-Swing ability, but instead is a normally activated attack."Īnd that isnt the current spellqueue system either as it was changed during legion.Įven so, while Wotlk classic is trying to imitate the original wrath release, it is running on a different system. You have quite a few mentions of it when it was introduced. The current spell queue system wasnt a part of wrath. Still don't see any information about how it used to work originally to confirm whether the interaction is authentic or not The spellqueue window timing can be found using: The spellqueue window can be set from 0-400, and 400 is the default that most players are using. This removes the local delay and system delay one would typically get. The spell queue functions as a system for lag mitigation, allowing users to queue an ability while waiting for GCD cooldown to come off. The red bar is the GCD of the ability and I am casting BT and WW. Repeat this process without using Heroic Strike (or Cleave) and notice how Whirlwind does fire. Once the GCD cooldown is over, the next ability should be cast, but it doesnt.ħ. Once the GCD cooldown timer is below the spellqueuwindow (400ms in this example) press another ability on the GCD, whirlwind.Ħ. Use an ability that's on the GCD, for example Bloodthirst.ĥ. Attack a dummy and use Heroic Strike (or Cleave) right after your main hand has struck the target~.Ĥ. Ensure that spellqueuewindow is set to the default value of 400ģ. To reproduce it does requires you to attempt several times, as we are talking about a small window of where you can queue your ability and therefore it is not always transparent when you are using the spellqueue system.ġ. There has also been other mentions of this. This forces the warrior to spam abilities to counter some of the delay, but it will still result in some delay depending on human factors and your own latency. Resulting in no spellqueue window, which increases delay on abilities and therefore lowering dps. However once HS is queued you are unable to do so. The way that spellqueue currrently works for warriors, is that as long as HS/cleave is not queued you can queue up your next ability correctly. ![]()
0 Comments
Read More
Leave a Reply. |