![]() If your macro cannot find a spell to fire within that window you are then encountering a delay on top of the GCD until it can find one. This means with a macro firing every 100ms it should have 4 chances to find a spell that is not on cooldown to queue up and fire once the GCD of 1.5s is up (or less if you have haste). So in summary, the Spell Queue Window is working as expected. The result was Concussive Shot followed by Multi-Shot. Now the final Arcane Shot is scheduled to fire at 1.0s so outside the queue window, concussive shot is on cooldown so they fail to queue at 1.2s and 1.4s, so I expect Multi-Shot to fire at 1.6s. The result was Concussive Shot followed by Barbed Shot as expected. So with a 400ms queue window I would be expecting the previous spell Barbed Shot queued at 1.2s which hasn’t been replaced with concussive shot due to concussive shot being on a 14s cooldown. Now the second concussive shot when attempted at 1.4s in will be on cooldown. ![]() The result was Concussive Shot followed by Cobra Shot, so far so good, the spell queue window is working as intended. If the spells are not queued then Concussive Shot would be followed by Multi-Shot after 1.6s. The theory would be if spells are queued you would get Concussive Shot followed by Cobra Shot after 1.5s although the spell would be attempted at 1.4s (the intervening spells skipped due to either GCD effect or being replaced within the Spell Queue Window. 200ms) and then created a macro with the following sequence to run on it: Setup my razer hardware to fire a key 5 times a second (i.e. Issued the command /dump GetCVar(“SpellQueueWindow”) and it returned 400 (i.e. ![]() ![]() Logged on as one of my hunters, removed trinkets and all gear with any haste, checked my stats and it showed no haste. I thought I’d test out the assumption that SpellQueueWindow has no bearing and did a little experiment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |