So until a smart person corrects me, it looks like your SQW is way more about your need to stop casting on a short notice (CCs and such), or if you need to target swap quickly while spamming spells, as your target is also queued inside the SQW. A shorter SQW would seem to affect this though, as if your SQW is <= latency, you're effectively playing with 0 SQW, meaning nothing gets queued. Illustrated with a picture: - A longer SQW won't affect this at all. Meaning any spells I hit after the 200ms mark won't reach the server in time to be queued, meaning I will cast my previous spell. If my SQW is 400ms, but my server latency is 200ms, my last "queued" spell will be sent 200ms before my 400ms window is over. I wish someone would do a technical write-up on all of this stuff with some actual data and explanations backing it up.Įdit2: Playing around on the dummy for a while on the PTR with that juicy 200ms ping, I think the reason people believe that spells can't be "overwritten" in the SQW is because there's still a server interaction going on. Tldr leave it at 400ms and go on with our business?Įdit: I'm finding a worrying amount of anecdotes contradicting the idea that the SQW is open for overrides though. So the reason we have the /cqs command is more likely to give us a way to cancel spells during the SQW that would otherwise go off if we just stopped spamming keys. I can't figure out a reasonable explanation as to why the game would lock in the first spell cast during the SQW anyway. Just keep an open window where you queue up whatever spell was last ordered before the GCD rolls around and then send that off to the server. Yeah that would be a far more logical implementation. R/wowguilds for recruitment and looking for guild posts R/wownoob for more noob-friendly questions. r/wow is the main wow Subreddit, and maintains some excellent resources, including a list of other WOW subreddits.
Please message moderators if you think something should be added or edited! Links to useful resources or discords can be found in our Wiki. will be appreciated if they are detailed and not purely self-advertisement. Sharing Guides - Psychology, map strategy, metagame posts, detailed guides about UI set up, etc. or complaints/ventingģ) Guild/Team/Partner requests and/or advertisements.Ĥ) Questions which have been asked before or basic questions that can be answered by looking at relevant class guides, appropriate discords/pins or a quick Google search.Ħ) Questions or posts that involve breaking the WoW/Blizzard ToS (exploits, private servers etc.), bans will result.ħ) Log submissions (except under the sticky comment in our weekly posts) The most general guideline that exists is your post must contain quality content that generates discussion and helps improve gameplay.ġ) Jokes, funny stories, etc. The only thing I can think of is if I need to cancel a spell that you can’t normally cancel by movement or other obvious means.Our moderation will be subjective, and we plan to err on over-moderation rather than under-moderation. Is there another way to do it, or another use for /stopcasting that I am not seeing?
Unless I’m missing something, is this correct? So, what’s the point? I either have to keep hitting the key, or move first to stop the cast, then do my instant, completely negating the need for /stopcasting.
Wow spell queue macro no cd#
There should be no CD from completing the 1.8 second cast, because I canceled it, but still, it doesn’t do my instant spell.
Now, if I bind that to a key, and cast something, like Frost Bolt, which is a 1.8 second cast, then 1/2 way through the cast, hit my new Ice Barrier macro key, it stops the FB cast, but doesn’t do the Ice Barrier, unless I keep tapping the key. cast Ice Barrier (or Frost Nova, or any other instant spell…) I was just trying on my mage, for example Not without multi-pressing the macro key, so defeating the purpose. I was just trying to use /stopcasting, and it seems like it doesn’t work on anything I have tried.
0 kommentar(er)
