Scattered Shots is for hunters. 'Nuff said.

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.

As of 10:50 AM PDT, 1:50 PM EDT, Blizzard has brought down all the realms in the Bloodlust (US) battlegroup for brief maintenance "to address issues relating to high latency and disconnections." The affected realms are expected to be done after about an hour, which means they should come back up around 11:50 AM PDT/2:50 PM EDT, which is in twenty minutes.

The affected realms are listed as: Aman'Thul, Barthilas, Blackrock, Caelestrasz, Dath'Remar, Dreadmaul, Frostmourne, Frostwolf, Khaz'goroth, Kil'Jaeden, Kilrogg, Nagrand, Ner'zhul, Proudmoore, Sen'Jin, Silver Hand, Thaurissan, Tichondrius, and Vek'nilash. Note that as far as I can tell the Dreadmaul realm does not actually exist. Edit: Never mind, it's the new Oceanic realm. It's just not listed on the Battlegroups page for some reason. I kind of wish they'd do some maintenance on my own realm (Shadow Council), since I've been having relatively high latency myself recently (150-200ms as opposed to my usual 60-100ms).

Update (3 PM): Not entirely unexpectedly, the realms are not fixed yet. The new ETA from Bizzard is 1 PM PDT/4 PM EDT.
Update (4:30 PM): The realms are back up, but still experiencing issues. Blizz promises to provide more updates as they are available.
Update (8:15 PM): Realms down again. They were supposed to be back up at 5 PDT/8 EDT, but apparently that is not the case.

According to Drysc, there's a Blizzard-external network problem in the central United States that is currently affecting several WoW realms. Symptoms include high latency, packet loss, disconnection, or inability to connect; side effects may include broken keyboards and bruised fists, or in severe cases, deciding to stop playing WoW for the evening.

I'm not sure which realms are affected, but it's nice to know that this is being worked on anyway; the glowing tree promises that they are actively receiving updates from the (unnamed) parties involved. There is currently no ETA on a fix. I'll keep you posted if I hear anything else. In the mean time, let's start building a list: if your realm is acting up, let us know in the comments.

Update: Drysc is saying the issue "appears to have been resolved," but they're still keeping an eye on it.

Recently members of my guild have been using a tool called Faster Ping to achieve better ping rates in game. My guild is a West Coast based guild, and attracts a lot of people from Hawaii and Australia, so they naturally have higher ping rates than those of us in the States. Faster Ping seems to be working wonders for them. It is not so much of an addon as it is a tool for Windows (though lots of people mistakingly call it an addon).

My first reaction to this was what thinking this sounded like something out of the mouth of Cliff Clavin. I mean, how can a piece of software impact something that is mainly due to physical limits? Well, after thinking about it for a bit, and reading up on what the tool does, it can.

WARNING! This paragraph will be the only one that contains technical content! Faster Ping works by removing the acknowledgement delay from TCP packets. This delay happens inside the kernel's TCP stack, and is a necessity for a lot of functions that go on inside a TCP stack. The other modification Faster Ping does is to remove delay in sending small packets (think anything less than a dozen or so bytes). These changes, at least theoretically, should not impact system stability if the Windows kernel has proper TCP/IP stack implementation. Okay, end technical content.

Raid Rx is designed to encapsulate and cure the shock and horror that is 25-man raid healing. Ok, so it's mostly horror... Anyways, if you're a big fan of X-TREME Whack-A-Mole (or are being forced into it against your will) this is the column for you. I prefer to remember Tom Cruise as he was in Top Gun, crooked smile and no couch jumping.

This is Part 1 of a two-part series on reaching your full casting potential. Today we're going to cover how to get around inherent casting latency and next week I'll assault you with so much info on how haste rating affects healing, you'll come back here to hide.

First I'm going to give you a bit of background, so grab your blankie and settle in for a story of mystery and intrigue. Once upon a time, all of the Elitist Jerks healers prayed to the god of stopcasting. Me, being in SSC at the time, figured if all the cool kids were doing it, why not lemming along, too? So I did me some research.

Many players have experienced faster WoW loading times with Windows Media Player (WMP) running in the background. Some players are also reporting lower latency and higher frames per second.

This tip surfaced in the Europe forums late November and was picked up by the US forums two weeks ago. Many players are reporting shortened loading times, some by more than 50%.

I did a quick test and found that by running WMP in the background, minimized and not playing anything, the login screen popped up about 20 seconds quicker than usual. The world loading time (time between clicking Enter World button and character appearing on screen) was also faster by about 15 seconds. However I did not see any significant improvements in latency or framerate. To eliminate performance boosts due to caching or preloading, I rebooted my machine between each set of timings.

Some players have also suggested adding:

SET timingMethod "1" or SET timingMethod "2"

to the config.wtf file to achieve the same effect without running WMP. For me, this shortened the time for the login screen to appear by 20 seconds as well, but only shortened world loading time by 5 seconds. Combining WMP and the config.wtf tweak resulted in the same timings with just running WMP alone.

There's been no official Blizzard response to this yet, although a likely explanation is that WMP modifies how your computer handles background applications. With WMP open, all available CPU resources apparently become allocated to WoW, leading to better performance.

Does this quirk work for you? Do you see any improvements in framerate and latency?

Ever since patch 2.3, a number of players have been having a lot of trouble with their instant abilities, especially in PvP. They're finding they get constant "spell is not ready yet" and "target is out of range" errors whenever they mash their buttons. The main source of this problem has to do with a change to the way your computer communicates to the server what your character is doing. It's not very easy to explain, but I'll do my best here. First, I'll explain how the change affects longer spell casts, and then afterward look at how it affects instants.

Here's how things worked in patch 2.2:

1. I press a button to cast a spell or activate an ability.
2. My computer says, "Hey! Realm server! David wants to cast Frostbolt!"
3. The realm server says "Okay!" 300 milliseconds or so later (this round-trip communication time is your "latency").
4. My computer then starts a 1.5 second global cooldown, and shows me the Frostbolt casting bar.
5. I cannot use any other abilities from the time I press the button to the time my Frostbalt casting finishes, unless I manually cancel the spell (as with a /stopcasting macro), or unless the server tells my computer, "Okay the spell is finished already!" or "Whoops! That spell got interrupted!"
   
6. Either way, without a manual interruption on my part, I'm waiting on the server to tell me the outcome of the first spell before I can tell it to start casting the second.

Here's how things work in patch 2.3:

1. I press a button to cast a spell or activate an ability.
2. My computer says, "Hey! Realm server! David wants to cast Frostbolt!"
3. My computer goes ahead and starts the global cooldown for me, assuming the Frostbolt will succeed.
4. The realm says "Okay!" 300ms later, and the casting bar shows up.
5. Alternately, if there's a problem, then the realm says "No way, silly! David isn't finished casting Fireball yet! Wait a moment to try again, and cancel that global cooldown while you're at it!"
6. Either way, I can send my commands to the server whenever I want, as long as my global cooldown isn't currently active -- and if it gets activated too early, I just have to wait for the server to tell my computer to cancel it before casting another ability.

Sounds fine, right? Before, we had to wait for latency between our computers and the realms in order for any spell to go through, but now we just have to wait if we press a button too early.

It's the end of the day (or nearly there) and, if you've logged on at all, you've patched WoW up to the latest version. Oftentimes, patch days are fraught with server instability and all sorts of other issues in game. On top of those problems, UI mods get thrown out of whack and usually must be updated in order to avoid screens filled with annoying error messages.

Personally, this patch day was one of the smoothest I can recall in recent memory. Once the servers came back up, I was able to log on right away with no queue and no apparent latency. As the afternoon wore on into evening, there were a few rough patches of lag, but they smoothed out after a little while, never to return. My most important mods were already updated and I can live without the rest for a couple of days. I purposefully try to avoid a reliance on UI mods, which is always helpful on patch days, so I'm not sure that my experience was shared by many other WoW players. Even so, my guildmates who rely on mods more than I do also seemed pretty happy with the transition to the new patch, so hopefully things went well for the majority of WoW fans. How did the patch treat you today? Did you bother logging on at all? If you did, have you had a good experience thus far?

Your character can be less effective if you mash buttons in 2.3, according to Altitis. You can also stop using the /stopcasting command in most macros.

In the 2.3 PTR patch notes, "client spell cast requests are now sent to the server even if your player is already casting another spell. This eliminates the need for /stopcasting in macros to compensate for latency."

What this means in English is that outside of global cooldown, your computer will try to send a new cast command to the server when you press a button, no matter what.

With todays news that Hemorrhage is being buffed yet again in the latest build of patch 2.3, I'm getting more and more excited to take out my old rogue character and use my favorite ability again. Back in the days before The Burning Crusade I used to enjoy using Hemo to succeed as a rogue in PvP when latency and casual gear would have left me at a bad disadvantage otherwise. Hemo was just strong enough that it gave me a real chance at success sometimes, and all the other buffs to stealth in the Subtlety tree made me feel like a real rogue sneaking around and stunlocking people, rather than a warrior without the heavy armor, or a backstabber who could never seem to get behind anyone or crit often enough to kill things.

Once The Burning Crusade was released, I felt terribly disappointed to learn that there were few if any more very slow main-hand weapons at the new level cap. Today there are still very few with a 2.7 weapon speed, and even fewer with 2.8, which, before the expansion, was really the minimum weapon speed you needed to start making use of Hemo successfully. This is because Hemo is not "nomalized" like other abilities; it does progressively more damage the more time passes between weapon swings. With only one high-level 2.9 speed weapon in the game (and that a legendary), and all 2.8-speeds being either too low-level to be useful or to far out of my reach to attain, I feared my preferred playstyle would be dead and useless by the time my rogue reached 70.

But now I'm not so sure. I still don't know why Blizzard didn't add more slow weapons like they used to have in the old days, but I'm hoping these buffs to Hemo will make up for the loss, both in raids and in PvP. Still, I'm hardly the best rogue theorycrafter out there. Are any of you good mathematicians able to speak authoritatively on whether this change is enough to raise Hemo from the dead?

Update: Our commenter, Rick, shared with us a link to an Elitist Jerks discussion in which they provide some good research about this change to Hemo. Among other things, it seems this new version of Hemo is now normalized, meaning that, like Sinister Strike, it won't matter what weapon speed you have when you use it -- it'll still do the same amount of damage. Many of them are eager to try it out.

Lag...the bane of every online gamer. It's even an unpleasant sounding word - "Laaaaaag" - sounds like you're trying to gag on a raw fish. Well, just like any enemy of the people, there are folks out there fighting the good fight against the lag monster, notably the team over at EndLagNow.org, a website dedicated to tracking down & eliminating the menace of the red latency bar.

The latest step is the release of a program called LagMeter, that scans your PC's connection to determine where lag is coming from & what the causes might be. From the description:
Finally, the causes of your Lag will not be a mystery because LagMeter will tell you if it is your gaming PC, the network, or the gaming server that is giving you grief. Once the causes of Lag are better understood, then gamers, game developers, and hardware manufacturers can work together to provide solutions to our #1 problem – LAG!!!!!!!

Sounds like a plan to me. Haven't tried out the program myself yet, but it's definitely worth a look. You can check it out over at EndLagNow's website right here.