Filed under: Cheats

Are you wondering what has caused all the ruckus in the raiding community the past few days? Have you been typing your fingers to the bone since Wednesday night, arguing for one side or the other in forums and chat channels? Whoever you are, or whatever side you're on, in the still-burning aftermath of Ensidia's ban, I feel some reflection is needed. Thus, I am going explain, to the best of my ability, what happened to cause such uproar in the raiding community this week. I am also going to, as the title implies, offer my speculations.

We've gotten a bunch of tips recently that claim some very e-famous PvPers are botting in BGs. If you aren't familiar with the term "botting," Dictionary.com provides us with the following definitions of bot:

1. Bot:
   –noun
   the larva of a botfly.
2. Bot:
   –noun (Australian Slang)
   a person who cadges; scrounger.
3. Bot:
   –noun
   a device or piece of software that can execute commands, reply to messages, or perform routine tasks, as online searches, either automatically or with minimal human intervention (often used in combination): intelligent infobots; shopping bots that help consumers find the best prices.

As the holiday weekend rolled around, we started to get a number of tips that Hunters were successfully training themselves a...Worgen pet? Worgen?!? How was this level of cool allowed into the game without anyone knowing about it until now?

Well, it turns out that the Worgen pet is in fact a very clever use of game mechanics somewhat akin to those used by Hunters in order to tame the (now sadly vanished) Grimtotem Spirit Guide. Garwal, a warg NPC in northern Howling Fjord who can turn into a Worgen as part of a questline (the link is the Horde version, but it's the same for both Horde and Alliance) can actually be tamed and kept in Worgen form if the timing is right. Mania's Arcania has a look at the process used here, which involves a little math, a little guesswork, and the strategic use of Wyvern Sting.

As previously reported, there were accusations that US guild Exodus used an exploit to obtain the World First of the last unclaimed Hard Mode in Ulduar -- Alone in the Darkness. As it turns out, these accusations were true and blue poster Daelo posted on the official forums that the Yogg-Saron encounter was hotfixed on all servers to prevent this from happening in the future. Owing to this, Exodus' kill is no longer recognized by some achievement trackers.

Contrary to some reports, however, Exodus released a statement on their website that members of their guild were not banned, clarifying that Blizzard meted out a 72-hour suspension for their abuse of game mechanics. They argue that the encounter wasn't beatable to begin with, similar to the C'thun fight in Ahn'Qiraj before it was fixed, prompting the exploit. In the same statement, Exodus also points at Ensidia's arguably hypocritical stance of complaining about the abuse considering Ensidia used similar questionable methods to achieve other World Firsts. Serennia mentions this behavior in his column at wowriot, as well, bringing into question Blizzard's apparent double standard when meting out punishment.

In reading the commentary on the site concerning the brouhaha surrounding Martin Fury and The Marvel Family's steamrolling of raid content, there were a lot of assertions made that left an impression on me, but the overwhelming feeling I had coming away from it was the players were treating it as a TOS issue when ultimately it's not. For obvious reasons, Blizzard doesn't spend a lot of time creating specific rules for what happens when players get ahold of items that are not officially supposed to exist. I do, however, believe it to be a moral issue.

Was Karatechop wrong to use the shirt, or just wrong past a certain point?

Someone made of stricter stuff than myself would probably say that it was wrong to use the shirt at all, but I have to admit -- I don't have it in me to condemn Karatechop's initial impulse to try it out. GM items don't officially exist for players; we know about them only because they've been data-mined, and you'd have to be a fairly frequent habitué of Warcraft fan sites to have any inkling that they're in the game at all. If I'd been in Karatechop's position, like many players I would've believed that Martin Fury was a joke when I first saw it. Who honestly expects to run across an item like that, let alone one that was mailed to a guildie's level 13 Warlock? I don't believe Karatechop was wrong to try the shirt when he had no reason to believe it was anything other than a joke or some bizarre glitch.

Reader comments – ahh, yes, the juicy goodness following a meaty post. [1.Local] ducks past the swinging doors to see what readers have been chatting about in the back room over the past week.

The [1.Local] PuG was in rare form this week, postulating theories and pontificating on issues ranging from the Martin Fury scandal to whether or not Ulduar difficulty and loot is on target. We highlight not one but two in-depth posts on the lore behind the Horde/Alliance relationship, each with extensive reader reaction.

This edition of [1.Local] also spotlights fresh reaction from Karatechop, the player at the epicenter of the Martin Fury brouhaha. What does he think about all the hullabaloo over his banning in the wake of his use of a GM-only item that came into the hands of a guildmate? Karatechop responds to the pages of comments on our exclusive interview with him about the incident. All this and more, after the break.

We've covered the topic of Warden in the past, and you've probably already got an opinion on what it does to your computer system. Blizzard runs the Warden program alongside your WoW client, and while it runs it examines what else is running on your system -- if there are any third party programs (either hacks or cheat programs) interfering with the client, it lets Blizzard know, and shuts down the client. The obvious privacy concern here, of course, is that Warden is basically watching what you do outside of the game. And while Blizzard has maintained that the program is simply meant to check for hacks and cheats (they also say that no personally identifiable information is sent back to them, though IPs and other network information definitely are), there's always a chance that Warden could see you doing something you don't want it to.

Computerworld's Security section has a nice long article on all of the implications of Warden, especially in one of the more sensitive areas of security: the workplace. While most of us probably won't ever play World of Warcraft at work, there are certainly companies where installing and playing the game at certain times is appropriate. And it's probably in those situations where Warden could be its most dangerous. If you trust Blizzard with your information, then you'll have nothing to worry about. But if you don't know what Warden is sending back, there's always a chance that it could be something more sensitive than you'd like.

Of course, there is a hard and fast solution to this: don't play World of Warcraft on computers that have anything you wouldn't want shared with Blizzard or anyone else. As Computerworld concludes, it's a choice-and-consequences kind of thing. Warden is up and running every time you play WoW, for better or worse -- if you don't want it watching what you're doing, the only guaranteed way out is to not play World of Warcraft.

15 Minutes of Fame is our look at World of Warcraft players of all shapes and sizes – from the renowned to the relatively anonymous, the remarkable to the player next door. Tip us off to players you'd like to hear more about.

Daedren (not his former WoW character's name) ruffled more than a few feathers with an internet "confessional" (was it, really?) last week about his experiences botting in World of Warcraft. (To "bot," a term that comes from the word "robot," is to use a third-party program to play the game for you.) He initially declined an interview with 15 Minutes of Fame but was back in touch a few days later, after the comments and reaction began piling on.

With a measured, reasonable approach (somewhat at odds with the abrasive tone he takes with commenters on his blog), Daedren visits with us about botting. Is botting a blot on the soul of gaming humanity or a benign, time-saving technique for busy gamers? Read Daedren's post to learn what his botted characters were up to in WoW, then join us after the break to learn why his botting post was actually a farewell "ode to WoW."

An interesting question was posed over on Less QQ, More PewPew: When would you become a ninja? It made for a pretty good read, the author lays out a few situations that might warrant an act of ninjery* that really made me think about the whole thing. Would I ninja in those situations? The situations that the author describes are situations that would certainly make me consider it, but they're also situations I don't ever put myself in.

The author lays out a scene: Your raid is in Sunwell (when it was still sexy), you have your regular Hunter, and you have a terrible PUG Hunter. You kill Kil'jaeden. Regular Hunter did great, but PUG Hunter was terrible and died almost instantly. You loot the boss and... Thori'dal drops! The two Hunters roll off, and the pickup Hunter wins the roll. Do you Master Loot the bow to your regular Hunter anyway? Or do you play nice and give it to the pickup?

Blizzard (via Nethaera) has released a nice long statement on the Glider outcome over on the forums. She basically runs through the history of the case and why Blizzard is against what Glider is doing, and why going through the courts was the only route left to them. She says that Warden (though called only "security measures") was enabled in response to player concerns about bots, and that when the MDY/Glider people circumvented Warden, their only recourse was to seek an injunction through the courts, which, as we've reported recently, they plan to have soon.

She does say that Blizzard won based on the judge's decision that MDY did violate the Digital Millenium Copyright Act, but Neth doesn't go any further into the issue, and doesn't elaborate at all on what might happen if this case is used as a precedent against other types of Terms of Use violations. As you might expect from an official Blizzard telling of the tale, the case is seen as a victory for Blizzard and their players -- for them, it's all about keeping bots out of Azeroth, and this decision will definitely help them do that.

And that's obviously not a bad thing -- most players will agree that MDY was allowing players to cheat (by letting the game play automatically without them in control), and thus preventing the client from being used in-game is a good thing. It's just that DMCA issue that might be a nagging problem -- we'll have to see what happens with that in the future.

Bornakk just posted an important announcement for all arena participants:

There is now a time limit of 45 minutes for all arenas. If neither team has achieved a victory, both teams will lose 16 arena rating points.

This is posted in the general discussion forums, and we can safely assume that this change is active on live realms.

Bornakk goes on further to say that matches that go on for 45 minutes are currently showing up as a draw and not displaying a loss of arena points. However, the point loss still happens. This means that you can apparently see it when you look at your honor page and you'll notice that your rating has gone down by 16 points

We've covered some very long arena matches in the past. A 13 hour match between a Druid/Warrior and Warlock/Paladin, won by the Warlock/Paladin, and a 10 hour arena match (the classes were not reported on).

Cabinetsanchez over on LJ has documented something that I saw in action yesterday while running a few instances -- while it's a ton of fun to run my Crashin' Thrashin Racer around (I'm undefeated since I picked up the achievement the first day I got the toy, by the way), players have found a few extra ways to make the Racers work for them. Yesterday, I saw one of my group members using the Racer a few times to scout the instance ahead and see what pulled with what, and as CS says, it worked great: while the Racer will aggro enemies, they won't tag on to the rest of the group -- they'll just reset after they destroy the little car.

CS also says that the Racer takes no falling damage, so you can send it exploring off of cliffs and platforms, and he says that though the car is considered level 60, its aggro range is pretty small (I can attest to this, as we were driving it pretty close to enemies yesterday without it registering on their radar). And he's got an even more devious use (some might say this is an exploit): bosses aggroed by the racer will sometimes despawn after they conquer it for up to 30 seconds or so. That seems like a hotfix waiting to happen, but I haven't personally tried it, so it may not be as useful as it sounds.

The downside of this is that the Racer was meant to be a fun item, and if it really does lead to behavior that Blizzard considers exploiting, they might have to think twice about including great items like this in the future. We'll have to see what their ruling on this is, but hopefully no matter what happens (I'm guessing a quick hotfix, maybe even shrinking the range of the Racer's controller), this won't prevent Blizzard from giving us more fun toys later on.