/dump GetCVar("SpellQueueWindow")
400 ms latency default… =/ this is poop if expect your spells to go off when intended.
For example if your latency to the server is 100 ms you can reduce the spell Q latency to whatever you like by the following command line.
/console SpellQueueWindow 100
This will change your spell Q latency to 100ms
You can turn it off entirely by replacing 100 with zero or whatever value you like.
6 Likes
What does this do, exactly? Is there a reason why this is a value the player can control? Maybe I should ask, are there any downsides to setting it to zero?
Cuts down the delay on when you push a button to when it actually happens.
1 Like
This is really cool. Thanks for the info!
1 Like
Welcome, its not sense in playing this game dragging a boat anchor.
I’ve messed around with that in retail and found that it made the game harder to play. Say my latency is 30ish…you’d set it to the same number?
Roughly the same value, better to be slightly over than under
1 Like
Maybe I’ll give it another try. I was under the impression that the spell que system that was added was supposed to correct this stuff in the first place. As I recall, that feature didn’t exist in the original TBC.
I’m not very knowledgeable about this thing, but what’s the benefit? More casts?
Basically you’re not waiting on the spell Q to cast your spell, so just make sure you don’t go too far with it. Say if your latency is consistently around 100ms likely set it to 105ms would be safe and still better than 400ms.
I’ll give it a try, thanks. I remember that not working too well in retail lol. Like the next cast just wouldn’t come out at all sometimes. Maybe it’ll be different with less instant cast stuff.
Yeah that can happen if you tune to aggressively.
So if I’m comfortably in the 30 range, maybe set to like 50? Just to be safe?
try out 40 and see if that clips at all.
1 Like
Sounds like a plan, thanks!
1 Like
If you set it to zero, you won’t be able to queue your abilities. Basically, you will no longer chain cast without delay. Your cast will go off and the next time you press a button will start the next cast. Back in the day we had to mash our hotkeys as fast as possible for the abilities to go off sooner.
I’m still not understanding the benefit to this thing. Is being less forgiving on button pushes going to lead to more casts compared to using the default 400?
depends. If you’re chain casting frost bolts constantly this is meh, but if you want to make sure your counterspell is as close to button push as possible; this will help.
1 Like
Right, but maybe I’m just having a senior moment lol, but I’m not sure how useful that it is even. The timing is stricter on hitting the button. The 400 window is pretty big, but even at 100, you need to be pretty close and you have to judge the gcd better. I think I’m just too used to having it at 400. I was missing casts when trying to string instants together.
correct, you’re right that the padding is easier, but this reduces your possible last moments ability to use something like counterspell.
I see what you’re saying now. I’m assuming that most mages will probably be using a /stopcasting macro to get around that problem.