Scattered Shots: Auto Shot

One of the most confusing things about a hunter's repertoire of spells is the exact use of Auto Shot. This ability is unlike the abilities of any other class, quite different from a warrior's swing timer, or a caster's wand shooting. Auto Shot is like a metronome, and the music of hunter DPS requires that we play according to its beat.
We've discussed Auto Shot a little bit in last week's introduction to Shot Rotation, but Auto Shot is much more complex than is first apparent from simply reading the ability's tooltip. First of all, there is a discrepancy between what the interface shows you of Auto Shot and what is actually going on. If you don't use any hunter addons, you may have great difficulty getting a feeling for any of what this article is about, because Auto Shot doesn't have any representation in the default UI. If you use an addon like Quartz or ZHunterMod, however, you'll be presented with a timer that looks something like a regular casting bar -- and while this Auto Shot bar will help a great deal, it is still not complete. No matter what, your imagination and inner sense of timing are going to have to do a good bit of work in getting your shots timed right.
Picturing Auto Shot
Pictured on the right is the little Auto Shot bar I have set up on my computer. Here, Quartz is telling me that I have a 2.2 weapon speed, and I have 0.4 seconds left before my next Auto Shot. I used to see this timer and think that Auto Shot goes off regularly every 2.2 seconds or so no matter what, but this is not exactly correct. Actually, Auto Shot has a 0.5 second casting time (just like Multi Shot), which is not displayed anywhere with any addon that I am aware of. The first apparent purpose of this short casting time is to help limit hunters' damage while moving, to force us to stand still in order to do damage. It also forces us to time our shots more precisely, however, as anything we do during that half-second will cause the casting time to start over. Anything from short movements to instant abilities like Arcane Shot and even Kill Command can reset the Auto Shot casting time, and can potentially cause a delay of up to a second or more.
So in order to time our other shots right, we have to get a very clear picture of when this hidden casting time takes place. To the left is what the true casting bar would look like if you only cast one Auto Shot, and both the casting time and waiting time were properly displayed.When two or more Auto Shots are strung together, however, the half-second casting time fits in right at the tail end of the previous Auto Shot's waiting time. You can imagine them as a cascade of Auto Shot waves, one beginning just as the previous one finishes.


Auto Shot and latency
All this is very important because, in some ways, Auto Shot is the best spell you can cast. Not only is it the only damage you get for the exact cost of zero mana, but all you have to do to let it go off again is stop doing anything else for half a second. It also goes off independent of your computer's latency. As computer-savvy people put these things, the Auto Shot timer is entirely server-side, not client-side, meaning the timing of it actually takes place over there in Blizzard land, not on your own computer. As you'll notice if you ever have any huge latency spikes, your other spells like Arcane Shot and Steady Shot may seem pretty much locked down, but Auto Shot will go off quite happily on its own -- perhaps by the time your connection speeds up again, you'll find your enemy has died because of your Auto Shots alone.
If, like me, your connection sometimes has variable latency, such as 200 milliseconds one moment and 700 milliseconds the next, Auto Shot timer may seem long one time and short the next. This is a situation in which having your own sense of internal timing is very useful. Even if your Auto Shot isn't displaying exactly right, you can still have a good sense of how often it should be going off, and just touch other special shots whenever the right time comes, regardless of what you see in the display. You can't be sure that everything will go off exactly right, but you can at least be sure that you are doing your best with the internet connection you have been given.
Latency is the bane of any class. Some classes find that big latency spikes can completely lock them down and prevent them from being useful in any way at all. Rogues, for instance, have automatic swings similar to a hunter's Auto Shot, except that these swings only take place as long as the enemy is in melee range. Latency can cause all kinds of confusion when the enemy moves around and can prevent these automatic swings from hitting at all.
As hunters, on the other hand, your Auto Shots will likely still hit in such situations, but your damage won't be nearly as optimal as it could be with good latency and good timing. In fact, with variable latency (like mine, sadly), it may be extremely difficult to predict when you should cast your next ability so as to not interrupt or delay your Auto Shots. As long as your latency is steady, however, you can usually time things appropriately by just factoring in your delay time and pressing the button for your special shots a little bit early (as portrayed in Quartz with a red section of your casting bar).Filed under: Hunter, Tips, Guides, (Hunter) Scattered Shots, Analysis / Opinion, Add-Ons






Reader Comments (Page 1 of 1)
Znodis May 1st 2008 4:44PM
"Auto Shot is like a metronome, and the music of hunter DPS requires that we play according to its beat."
Poetic.
I'm curious to know how a Steady Shot 'mash it' macro works for variable latency, whether better or worse. It's an issue for me too.
Khelben May 1st 2008 4:48PM
"This ability is unlike the abilities of any other class, quite different from a warrior's swing timer."
I don't agree with this statement. With 2h PvE which is based upon a mixture of instant abilities with caste slam our DPS is also based upon the swing timer which we absed our DPS upon.
pudds May 1st 2008 4:56PM
That's true, but unlike Auto-shot, warriors don't need to stand still to auto-attack.
David Bowers May 1st 2008 9:17PM
As Pudds says: a warrior's swing timer is an instant thing, not a half-second cast time like Auto Shot -- there's nothing "hidden" about it at all. This means instant abilities like Mortal Strike or Bloodthirst can be used any time, whereas hunters need to avoid that hidden Auto Shot casting time for anything they might want to do. Also, using "slam" resets the warrior's swing timer, and doesn't fit in between swings in the same way that Steady Shot fits between Auto Shots.
A warrior's swing may require timing, but it's basically a straightforward thing: What you see is what you get. It doesn't require an understanding of weird timing mechanics that don't even show up in the interface! That's the difference I'm talking about here.
Boom May 1st 2008 4:55PM
Great article Bowers. Thanks!
Quick question. We've had a running joke in our guild about a hunter friend of mine, who went DC during a boss fight in Molten Core. Even though he was DC'd, and told us so through vent, his toon kept on shooting the boss.
We didn't have the foresight to check the combat logs, but instead assumed he was doing damage to the boss as a hunter, even while DC. (we always joke that you can raid with a hunter while watching simpsons... in another room.) :)
Anyways, when you loose connection, and your toon keeps shooting, is it actually doing damage to the mob?
Boom
Charn May 1st 2008 5:06PM
Ya i can say it does. For about 18 months i did contract work in Kuwait and played with an average latency of 2000 (yes that was 3 zeros). Sometimes up to 4000 and higher. I got pretty good at latency playing. Of course this meant no group runs or PVP but i could grind away usually to my heart's content. often I would hit a lag spike of 30 sec to a min (if i was lucky) as soon as I attacked something. Send in my pet and cast arcane shot and lag out. When I caught up to the server finally usually my mob was dead. Of course, about a 3rd of the time I was dead from some other mob that was now no where to be seen. Such is life.
Keysdawg May 1st 2008 5:41PM
I'd love to figure out how to move the red latency bar to the end of the cast bar in Quartz. On all my bars they show at the beginning, which is not nearly as useful. >.<
Eothor May 1st 2008 6:02PM
@6: I believe you need to uncheck the "embed" option under the latency option menu in Quartz.
Keysdawg May 1st 2008 7:45PM
You kind sir have made me a very happy Quartz user. =) Thank you.
LFD May 1st 2008 8:49PM
Noob question alert:
Is the Auto Shot icon a dreamcatcher? What exactly is that?
Badger May 1st 2008 9:19PM
I think it's supposed to be either the image of a very bizarre crosshair, or - as the light blue "motion blur" and the centered vertical line lead me to believe - it's supposed to represent the top half of a bow quickly being brought to bear.
Zephyrion May 1st 2008 11:13PM
I think that was also the icon for the Blademaster hero from Warcraft 3's move Whirlwind, or something along those lines. There appears to be a sword standing upright, and the blue flash on the side and the other "swords" are the afterimage of the Whirlwind (or whatever) move, created due to the Blademaster's blinding speed or something like that. Never really got what the ring was though.
Zephyrion May 1st 2008 11:19PM
Also, it's the same icon as the Warrior move Whirlwind, among others, which lends credence to my earlier statement. Not sure why they would choose that icon for Auto Shot.
Aggrajag May 2nd 2008 6:58AM
I still can't get my head around this after reading loads of articles in the last month.
If I ask it simply, you might help me...
*If* I just alternated Auto-shot and Steady Shot (forget Arcane and Kill Command) do I just wait to hear the autoshot fire and then press Steady shot so it should beat autoshot to it's next autoshot?
...or to put it another way; Using Quartz do I have to get the fat bar (Steady) to beat the thin bar (auto) to the end?
Raven May 2nd 2008 8:05AM
Okay, guys, I can see why this spell is important, but, as a newbie, I think I'd require a little more than just that. Once I get my RAM, I'm goint to be full tilt into WoW, and I'd like a road map of sorts to use as I level up and learn tactics and such. Which leads me to these questions:
1)Which mobs would be best to practice on for the various different tactics a Hunter is required to use?
2)How do I maximize a 0/11/50 Hunter build through tactics after capping at 70?
3)What would be a 'safe' level to begin PvP play?
4)What gear am I looking for? And, as I level up, what to replace it with per every few levels?
5)What would be the best order to learn the Talents up to about 70?
6)What would be the best pet to use for such a build?
I am aiming for competency, so the hard work does not deter me one bit. :-)
bugmaster May 2nd 2008 8:58AM
that are some good questions i guess. ill try to aswer them(i'm ashamed to admit i'm not nearly as good with playing my hunter then id like to be)
ok question nr:
1) well to practice doing dps there are some mobs in blasted lands that can't die but they display the dmg you do to them(so there not evading) these mobs combined with a dmg meter like swstats can help u alot.
kiting u can practice on about every mob in wow as long as there not casters cause then you will run into the problem of them not following you.
2) well as far as i know i think that build would be only good if u maxed agi and hit an unbuffed amount of 700 of it (dont know if thats supposed to be with or without lightning reflexes) so i am wondering why you want a build like that.
3) pvp is something u can always do, but since im geussing u meant at what level u could star pvp in BG's well i recommend doing BG's when your level is something with a last nr from 6-9, so 48 would be good but 41 wouldnt.
4) when you are leveling u want te be looking for items with agi, stam, ap or crit rating on them int is good to but not to important with leveling i would put those stats in theis order agi>stam>ap>crit. but min/maxing your gear while leveling is quite useless since the time you spent maximizing your gear could be spent gaining more xp
5) well for levling i recommend a beast mastery build since this works really good for leveling. but i think there is more info on this subject on www.wowwiki.com or http://www.gotwarcraft.com/guides/leveling/class/hunter.php
6) well for leveling i would recommend something with alot hp or armor such as a bear or a boar but tbh anything will do just fine
hope you found something usefull in there
p.s.: dont watch the spelling neither did i:P
Mity May 2nd 2008 9:24PM
ever had a hunter in guild that just plain coulnt dps? ever had a tank beat a hunter on dps in a pug or (godforbid..) a raid?
thats what autoshot does. not that he uses it, and nothing else, as the classic Auto-afk'er, but, that he does use everything else, and messes with the hidden autoshot timer to such an extent, that it cuts his dps by 35-40 %.
the correct use of auto used to seperate scrubs from pro's, before the macro's. now however, there is almost no excuses anymore ;)
Toque May 2nd 2008 5:42PM
I use an autoshot timer as well (Sorrentimers). And I've also use Karthis' Hunter Timers. Both show a delay of the autoshot timer when you're casting (steadyshot) rather than a reset of the timer.
This also correlates with what I see my shots doing in the game.
But you say "Anything from short movements to instant abilities like Arcane Shot and even Kill Command can reset the Auto Shot casting time"
And then later you said, "it may be extremely difficult to predict when you should cast your next ability so as to not interrupt or delay your Auto Shots"
So you also see a delay... which is it? reset or delay? I've heard a lot of other hunters talking about autoshot timer getting reset as well, but it doesn't match what i see in game.
Boobah May 6th 2008 2:39PM
It's a floor wax and a desert topping!
You seem to be misunderstanding; doing anything (moving, casting an instant shot/spell, whatever) resets Auto Shot's (0.5 second) cast timer, which means it's delayed until another whole, uninterrupted half second goes by. It does NOT reset the shot's cooldown timer; how could it, when the shot never actually fired?