Filed under: Cheats

Earlier in the day, raiding group Paragon apologized for exploiting a bug in the Raid Finder tool that allowed their raiders to obtain loot from a boss more than once in a lockout period. Blizzard has followed up with a statement of its own, explaining that people who exploited the bug in a similar manner will be receiving temporary suspensions.

Raid Finder Loot Exploit Suspensions

Shortly after patch 4.3 was released, we became aware that some players were abusing an exploit to obtain loot from the same Raid Finder bosses multiple times in a single raid lockout period (one week). The Raid Finder loot mechanic is of course intended to only allow a person to roll on boss loot drops once per raid lockout period. The raid lockout mechanic has been a mainstay of the World of Warcraft rules since Onyxia and Molten Core, ensuring that no one can obtain loot from a boss more than once per lockout. Due to the nature of the exploit and the clear intent of those who abused it, they've been issued notices and given temporary suspensions from the game. We're also working to remove all Raid Finder items from those who used the exploit.

source

It's good to see Blizzard taking action on this. Certainly there will be some who will believe this to be too mild a punishment. But given the number of people who abused the exploit (Paragon was far from the only guild doing this) and a need to hand out punishment evenly and consistently, a temporary suspension appears to be the right solution.

---

Brace yourselves for what could be some of most exciting updates to the game recently with patch 4.3. Review the official patch notes, and then dig into what's ahead: new item storage options, cross-realm raiding, cosmetic armor skinning and your chance to battle the mighty Deathwing -- from astride his back!

---

High-end raiding guild Paragon issued an apology today for exploiting a bug in the Raid Finder that allowed its raiders to accumulate a large quantity of tier 13 gear. The statement reads, in part:

We acknowledge that using this unintended behavior, which was quite clearly a bug, to our gain, was wrong. The fact that others were using it as well is no justification for doing it ourselves. We apologize for doing it, and accept whatever consequences follow.

Paragon had come up with a plan to run the Raid Finder multiple times, once for each raider. While executing the plan, they noticed and exploited a bug that allowed the raid the ability to loot passed gear -- a violation of Blizzard's rules. The exploit has since been hotfixed.

---

Brace yourselves for what could be some of most exciting updates to the game recently with patch 4.3. Review the official patch notes, and then dig into what's ahead: new item storage options, cross-realm raiding, cosmetic armor skinning and your chance to battle the mighty Deathwing -- from astride his back!

---

A stern but necessary warning from Bashiok today:

Dragon Soul loot exploit

If you are getting loot off of a boss twice then it is an exploit. This has always been the case in World of Warcraft, and we expect players to know better.

We're in the process of implementing a hotfix to fix the exploit, and are deciding what steps we'll be taking for the gear that was already obtained.

source

We're not going to post about what people are doing (we never have and never will post exactly how the serious exploits are done), but there is a clear and intentional way people are getting a lot of loot out of the Dragon Soul raid using the Raid Finder.

This method they're using gets around the "one shot at loot per week" rule, and it's something that Blizzard clearly from the get-go didn't want to happen. Bashiok is absolutely right as well -- it's well known amongst WoW's experienced playerbase that such exploits are never to be done.

There are reports that some people who've exploited the system are getting the exploited gear stripped from them in the EU; however there is no official announcement yet as to what's happening.

Once that's announced, we'll let you know.

---

Got trade skills? Want money? Insider Trader is the column to read. Whenever they let Basil write it, he'll do his best to fill your head full of ideas and your bags full of valuables and gold.

I'm going to come right out and say it: Don't do this. I recently wrote about ways engineers can make money, mentioning (among other things) selling epic ammo to hunters. The problem with making the best raiding and PvP ammo in the game only available from players is that it forces hunters to either find an engineer with the recipe who is willing to do all the crafting by mail, or buy it off the auction house.

What do I have against the auction house, you ask? Well, overall it's an excellent tool and far superior to the much nastier alternative of being forced to actually use trade chat for, you know, trade. It's not perfect, however. In fact, there's one massive glaring inadequacy that can be found.

Blizzard appears to be cleaning house in preparation for its StarCraft II release as well as its Battle.net revamp. In a recent announcement on the service's forums, Blizzard rep Bashiok revealed that over 300,000 accounts were punished for violations of the terms of service for Warcraft III and Diablo II for using hacks and illegal third-party tools (which are essentially hacks).

For those of you who have had past experience with Battle.net, these numbers probably don't surprise you. The network has had a long reputation of being fairly easy on people using hacks as Blizzard tends to save up over a long period of time in order to do a massive batch of bans at once. This means that those who are using hacks have a long period of time to abuse the system before anything is done about it. The hacks for some games were rampant enough that other players began using hacks that detect other hacks. Regardless of the reason behind using a hack, it is still against the terms of service and means if you get caught, you're out.

It's hard to judge exactly how many players know about GM Island. Some of the older players will remember the flood of trade chat and guild chats whenever a GM was online and visible in GM Island, and those folks who like to mess around with private servers and unexplored places will have at least heard of its existence. However today, with the island being so cordoned off, many players probably are not familiar with the mythical island of the game masters.

GM Island is a piece of land that used to exist in the very upper left hand coordinates of Azeroth, far beyond the reach of players. It exists as an in-game entrance point for Blizzard GMs, and is a relatively mundane place. It has a small keep and a dock, a few trees and bushes, and that's it.

There was a time when players were able to swim out to the island, and that swim took around an hour of hard work. It involved using a level one character constantly casting renew and other healing spells; and the player had to know exactly where to point themselves or risk being hopelessly lost in the vast oceans of Azeroth. The trick used to get there was similar to the one that allowed players to get to the Isle of Quel'Danas on the patch 2.4 PTR back in 2008. It was also possible to water-walk out there, but not much is known anymore about that method, at least publicly.

After the break we'll take a look at a few of the features and lore surrounding GM Island, as well as look at some videos. However, please be forewarned that some of the images and videos in this post are from private servers. Enough legitimate in-game footage simply doesn't exist.

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.