So if you haven’t heard, the mega-European based guild Ensidia downed the Lich King and got a world first doing it. This guild live for world firsts. For some of them this is their actual paid for employment. So this is a big deal for them. Congrats all round, right? Well, no. They then got suspended by Blizzard and had their achivement and loot cancelled because they used an exploit in the game to effect their world first. Apparently this is bad. Whether this is bad or not does not interest me. What arouses my attention is Blizzards definition of the word, exploit.
In a nutshell, a rogue used a saronite bomb, (yey rogues!), to bypass one of the encounters hurdles. The siege destruction nature of the saronite bomb caused the platform during the encounter to respawn, thus making the fight easier. This apparently, is what Blizzard calls an exploitation.
So a player uses a legitamite device that is found within the game, (and has been used by dps for some time now), against a fight mechanic. If this is banworthy then just about anything within the game can get you banned if Blizzard decides it is in their own best interest to do so. The player used an item found within the game on a boss fight. That’s all he did. If this act had unforseen consequences, then how is this the fault of the player? Particularly after all of Blizzards so-called testing beforehand. There are seige weapons in the game, and you design a platform that can be affected by seige weapons. It doesn’t sound like rocket science to me.
This reminds me of the Martin Fury incident earlier this year. A Blizzard employee makes a mistake and sends a player something that he shouldn’t have, and it is the fault of the player for using it? And don’t trot out examples such as if a bank puts more money in your account than you should have then you can’t legally use it. This is not a bank we’re talking about here.
It’s a game.
That we pay money to play.
You give me the game then I will use it. Give me an article within the game and I should be able to assume that I can use it. You gave it to me, I spent time getting it, there was no label saying, ‘do not use in such and such situation.’ Whenever such a situation comes up it is called a BUG, or in the case of the martin fury incident, a mistake. And it is Blizzards job to fix those bugs after they have been identified, not punishing a player, (or in this case an entire guild) for using them. It was an important encounter? This was the Lich King? Well, so fucking what? Spend less time making paid for vanity pets or designing ipad auction house apps and get something right that you have had since November 2008 to get right.
The real reason Blizzard is pissed off? They hoped that the Lich King would be a big mean mother fucker who would cause guilds grief for a long time. The reality? Blizzard didn’t put enough thought into the encounter, and it is punishing real life high profile players who happen to be the messenger. I will finish this little rant with the words of one of the Ensidia team:
“… There are no exploits in the game. Full stop. Period. End of discussion. There’s only retard designers and good players. If retard designs a building and good player uses bomb which does siege dmg, who in this case should get the “ban”? Any person with any common sense would fire that stupid designer so fast he’ll be doing mcdonals free games for the rest of his life…”
I have to say that I agree.
edit: It seems in my haste to read info on this that I made a mistake. The quote above is not from a member of Ensidia but from Larisa’s guild, over at The Pink Pigtail Inn. Here is the link to that post and my apologies to the team over there for not sourcing them.
February 5, 2010 at 4:09 am
Yo Ads,
Thought I’d check in on the noisy rogue – nice to see some up to date ranting!!
I’ll give you a call soon
Strength and Honour
Takuan the slow
“The Resting Druid”
February 5, 2010 at 6:21 am
Yo Steve,
The rant is strong within this one …
February 5, 2010 at 8:54 am
I completely disagree. Exactly, because it’s a game, you should be aware of the possibility of bugs. Bugs can be both positive and negative to your gameplay or progression.
An example for negative is that you can’t loot the boss. This happened with my in EoE and the GM gave me the quest item (for the necklace). It was obviously intended to get to me, just the bug did not allow it.
An example for positive is that some bug let you trivialize some content, like standing on a certain stone make you invincible. Standing in a stone obviously should not make you invincible. You should notice it is a bug and not use it.
Ensidia should have seen that the encounter is bugged. I’m not claiming they knew what’s going on. But they must have seen that the platform acts stupid. They should have contacted a GM, telling that there is a bug, and they don’t know why. But they proceeded, being happy that some bug allowed them a world first.
February 5, 2010 at 10:20 am
I’m not usually moved to bother replying to blogs but on this occassion Gevlon’s opinion has pushed me over the edge.
“You should be aware of the possibility of bugs…”
and so ‘should’ the developers, if they were doing their jobs properly, instead of being too eager to bring in the money. The players pay for a service, to play, they’re not paid to find bugs and carefully avoid them for fear it could upset Blizzards precious money making plans.
And yes I do know what I’m talking about, I’ve been developing software for 25 years, granted not gaming software but software is software. As a developer and tester I’m responsibile for the bugs not the end users. A lame “oh, well just avoid the bugs” is like reporting to your Doctor with the explanation “Doctor it hurts when I lift my arm” and him responding, “well don’t lift your arm then”.
“Ensidia should have known…”
When anyone uses the “should” word, a none definite, received wisdom, indeterminate, I wince. It doesn’t give a cohesive reasoning it just brushes it off as “must do better next time”.
They won, fair and square, using the software that they were provided with.
February 5, 2010 at 3:09 pm
Just a clarification… That quote doesn’t come from any Ensidia player (even though I’m sure he’d like to be one
), it comes from a guildie of mine who never hesitates to tell his views in a very upfront way. I thought they were a good summary of one way you can see this event, so I used it in my blog post.
I understand it could be misinterprated if you read it quickly though.
February 5, 2010 at 7:52 pm
Gevlon,
We’ll have to agree to disagree on this one. It is not the responsibility of the player to ensure that content is not bugged. To punish them for said action beggers belief. They gave them the content, they played with what they had, they were punished? How does that stack up?
Also, it is not so easy to see when content is bugged even when something is obviusly wrong. Case in point, a mob that is out of sight underground but able to attack you above ground. For a while you’re wondering what is going on. I’m getting hit, I’m in combat, but with what exactly? You have to take stock, and have a good look around to see what the problem is. In the middle of a 25 man raid fight, on the last boss of an expansion, the first time that a lot of them are in there, with everything going off like a firecracker and everyone desperate to do their best, (and with a set number of tries available to them), how did they not know that everything is fine? I can imagine that they thought that it was strange that the platform reformed, but how did they not know that that was part of the attack. What if Blizzard had purposely designed the fight to be super hard with the only way around it being the use of a saronite bomb to take out the platform? How are you supposed to know in that moment? And why should the players have to make that call? Isn’t enough that we do free beta testing for them? Now we’re responsible for things that go on in-game as well?
Why couldn’t Blizzard have just said that the fight had a bug that NOBODY knew about, delete the achievement and gear and given Ensidia another shot at it? Why did they have to be punished like this into the bargain?
Larisa,
Thanks very much for the clarification, I missed that point, entirely my bad.
February 8, 2010 at 1:22 am
I believe Ensidia, despite all the fanboys/haters out there, went into the fight not to find bugs, but to down the boss first and foremost. Their “reputation” was on the line to get it first, and why should they give a shit if it was bugged from an otherwise unknown mechanic. Saronite bombs rebuilding the floor? Since when do explosives rebuild things, maybe it was intended, Who knew at the time?
I’m not pretending i know all the information, and those who profess they do are talking shit. They went in to kill the final expansion boss, it was bugged due to no fault of their own, and why should they stop a fight to wait for a GM when the clock is ticking against them vs other world first guilds?
Feels like a PR stunt on Blizzards behalf, making an example when things don’t pan out the way they intend. Ensidia’s whole motivation for playing is to do things first, some people love it, some people hate it (tall poppy syndrome?)
Removing acheivements and drops then resetting it would have been the fair decision imo
February 8, 2010 at 8:40 am
All cheaters should be shot. “I didn’t know the BOMB wasn’t supposed to REBUILD the floor” “Shut the fuck up, liar”
What is sad is the fact that they would have had a first kill anyway, without exploits. And no, a first “kill” done through exploits is not a first kill, it’s shit.