Saturday, February 13, 2010

Ensidia got a 72 hours ban

In the past there have been numerous bans for guilds that exploited certain end boss mechanics and they deserved it because they were doing it knowing that it was an exploit. I hate those people and I would like them to be banned for ever on their second attempt to use an exploit.

Still I want to talk about the actions that were taken :

Date of Violation: 03/02/2010
Type of violation: Exploitation – Abuse of in-game mechanics or glitches with intent to exploit or cheat in World of Warcraft.
Details: Use of Saronite Bombs to bypass The Lich King fight mechanics
Consequences for Account: Account suspended for 72 hours, all items and achievements gained removed


I agree with removing the items and the achievements but not with the suspension. Why? Because they probably had no idea what was causing the bug in the first place. How the hell do you know that Saronite Bombs cause the Lich King encounter to be easier, apparently it is part of a rogues optimal? dps rotation(I have no idea if it is optimal or not since I don't play a rogue).
There has been no chat logs posted but I doubt that would confirm anything since they were most likely using a vent, team speak etc. to communicate(I doubt they would type "We are so going to get ban for this!! LOL LOL LOL!!!" in their chat and post it on you tube for the hole world to see like a certain guild of idiots). When it comes to end game boss bugs only minute potion of the player base gets to see them because those are hot fixed before they get there.

Who will discover these bugs and report them? Well of course that would be maybe the top 5 guilds in the world. As stated here http://www.ensidia.com/Kungen/blog/4081/ these guilds are the real beta testers. So fuck you stupid idiot, retarded, paid beta testers(I bet they don't even play WOW except to fuck up on their jobs, or better yet they are only a myth made by Blizzard because it seems there are no beta testing done on these bosses except for the animations, but that would be silly).

Again if you have read the blog post made by Kungen it is most likely that a GM was watching their entire fight with The Lich King and this is my problem with the 72 hours ban. If you knew about the bug why didn't you appear and say "Just a minute! You used HAAAAX!!!! " and before taking action explaining them what the problem was, talk about it, then resolve the problem by simply removing the items, the achievements and then respawning the boss until they got it right. OK so the GM probably did not know what was causing the bug. I am quite sure that this would stop him to appear and tell them what was going on, removing the items and achievements they got, making a note of the bug for the devs to fix, then to respawn the boss until it was a legitimate kill. Another scenario would be that a dev would have been watching the fight and since he knew what happened in the beta tests, he would compare the combat logs and he would most likely determine on the spot what was the cause of the problem.

I know that the GM doesn't need to prove beyond the fact that that the exploit happened in order to ban some one or some guild.

Type of violation: Exploitation – Abuse of in-game mechanics or glitches with intent to exploit or cheat in World of Warcraft.

So how would the GM prove that Ensidia had the intent to exploit or cheat in World of Warcraft? And this isn't about the fact that Ensidia is a famous guild and it being banned would create a lot of controversy, I am also talking about the other guild that no one ever heard about. WOW is a very big game and one could encounter a new bug on a boss that the previous guilds have not due to new talents, spells, consumables?(like in the Gruul encounter stated by Knugen in his blog), and other various mechanics.

THIS MAKES YOU WANDER HOW MANY INNOCENT GUILDS GOT BANNED DUE TO A BUG THAT THEY HAD NO IDEA THAT THEY WERE RESPONSIBLE FOR.

I hope that this will never happen again, but... I really don't know what to think... If there is some one or some thing to blame then that would be the human factor.

No comments: