Feb 4th 2010 7:26AM Here is a copy of the blog made..along with a link at the end to confirm it.
First of all, I took the time to log onto the account management page and discontinue my payment plan. It's been a long and good 5 years and 2 months since day 1 of the US release of World of Warcraft. Many good memories were made, and fun times were had. That's over now. My subscription runs out of February 21st, which marks the last day of World of Warcraft for me.
Looking back, moving from Final Fantasy X! to WoW was a big step, and there's times that I regret making that decision, while on occasion I was happy to have taken the step. World of Warcraft was different back then. It was new, challenging and interesting. undoubtedly though, it was nowhere near as feature-rich as it is today, but that didn't matter back then. The game was a continuation of EverQuest, a game most of the senior development staff of World of Warcraft are familiar with on a very familiar basis. Many of them played the game for years, and I can see that it served as a major inspiration when I look at what World of Warcraft was when it was released. Being an avid EverQuest player myself during a time, It drew me in further into the game.
Things have changed since those days, changed a lot. The game stopped being that fun. Less challenges were present in the game, and as we got through TBC and more so in WotlK, homogenization started to rear its ugly face in World of Warcraft. Everyone running around with identical gear, looking the same, doing the exact same things. With arenas, changes were made on a monthly basis that affected the way classes were developed, and subsequently also lead to how PvE was being done in the game. It got stale, predictable and repetative. The whole notion of hybrids in the midst of all this was just a fucking slap in the face by Blizzard. If you're going to remove everything unique and interesting about the classes, at least make them equal in the roles that they are performing.
Their idea of hybrid was something taken from classes in EverQuest, where people played classes that were jack of all trades, master of none, or very specialuzed roles, such as a pure buffer (bards etc). Classes that existed for one purpose, and nothing else. They removed most of those in WotlK, but still stick with the notion that hybrids somehow offer something special just because they have the ability to respec to a different role. Kind of a strange taken on the whole thing, considering what they've already to make it easy in leveling and gearing up characters on the same account, with more and more things being accountbound rather than characterbound. Two-faced by Blizzard in my opinion. Removed the boundary between characters on one hand, and at the same time claim hybrids needs to be penalized because they have the option of respeccing to perform different roles that a simple log out/log in would take care of.
Let's face it. This game is boring for veterans. The only reason it's still being played is because there has never been good alternatives during these 5 years. Age of Conan, Warhammer Online and Aion fucking flopped like shit. Really developers, if you want to make an MMO, don't go and fucking try to copy WoW. If people wanted to play WoW, they'd play WoW, not your shitty gimp ass version of it. Let it be a lesson to all you developers out there.
Anyway, back to the subject. This was as good time as any to drop this game and move on. Had been considering it for a while, and I always said to Buzzkill and the gang that I was just waiting for the sign. A sign from heaven to guide me on my way. Today, I received it. I doubt we'll ever get a perm-ban, as the loss of PR from banning topguilds is going to hurt their subscription numbers much more than quelling angry cries of the fucking noobs in this game ever would. Really, if you don't know shit about this game, just shut the fuck up and do something else. You level 1 fuck posters and the forums can honestly go f yourselves, since you're too shit to know even the basics of this game.
Finally dear Blizzard:
Fix your goddamn buggy bull##@% half-assed encounters. The amount of time and effort we dedicated to get through Wrath of the Lich king and Icecrown to see this guy die and take a turn at the Arthas is just sick. To finally see him die only to have the ENTIRE raid banned is simply an insult. It's cheap enough to make a bugged fucking encounter, but to ban people when they do not know what's causing the bugs is just a fucking joke. Whoever came up with this sheer *fisting* of an idea can go fucl themselves. Do me a favor so I don't waste my guild's time on this kind of jackass ##@%-fest again, send me an email at firstname.lastname@example.org when you decide to A) Implement an encounter that wasn't designed by a retarded chimp chained to a cubicle B) Get a Quality Assuarance Department C) Actually beta test the !**#ing thing and D) Patch it live. And please for god's sake -- do it in the order I laid out for you. Don't worry, I won't charge you a consulting fee on that one. And for good luck you might as well E) Pull your heads out of your asses. While you're at it rename the game to World of Betacraft.
Rethink your fucking bullshit. Fix all the buggy motherfucking ICC encounters (I suggest you let whoever made the Blood Queen one do this since that dude apparently laid off the crack the rest of you were smoking). Fix fucking arenas, or better yet, remove that shit. Fix heroic modes (just guessing it's !**#ed up considering your track record). Don't have the resources to fix this stuff? Move the ENTIRE Cataclysm team over to fixing Icecrown Citadel AND DO IT NOW. If you don't fix this shit, you jackassess will be the only ones playing the Cataclysm.
You got 1 week.
Thank you Blizzard, for these 5 years, but also, fuck you Blizzard, for these 5 years.
I just got banned, and I liked it.
Feb 4th 2010 7:03AM UPDATE:
ENSIDIA HAS HAD ALL ITS ACHIEVEMENTS REMOVED FROM LAST NIGHT AND THE ENTIRE GUILD HAS RECIEVED 72 HOUR BANS.
Muqq has also stated that he is cancelling his subscription because of this. The Ensidia site seems to be down as well. May I be the first to congratulate Blizzard for finally punishing Ensidia, they have seemed reluctant in the past to do so.
Feb 4th 2010 12:07AM Mugutu
So because they did it on 10 man, they should know exactly how 25 man works. Bull fucking shit.
Professional Gamers such as Ensidia would not miss a bug as simple as this. These people pride themselves on being the best and regardless of this exploited kill, still have some of the best players in the world today. These are not the sort of people who are going to miss something as blatant as the bug that was used. And yes, they should know the specific's of the encounter from experiencing the 10man with multiple groups running, infact they probaby ran the 10mans to work out the exact strat they would use for their 25man and quite frankly if you dont think that is true, then you sir are a idiot :P
Feb 3rd 2010 11:51PM Let's take a scenario, since some of you morons are saying, "they did it on 10 man they knew theyre haxorz": The glitch only happened in 25 man, apparently. How would they know that the bombs were the culprit? It's not as if they tried it, someone threw a few bombs and saw that the floor rebuilt, and then every single fucking rogue immediately respecced engineering, leveled it, and hoarded bombs. I really, really doubt they'd waste their time with that when trying for world firsts.
Ok so the bug did not work on 10man, then that means they knew how the fight played out as it should have done. This means going into 25man, they would have knew something was up instantly. Show me one fight in Wrath where the fight "Significantly" changes on 25man compared to 10man apart from more healing and the occasional extra adds. The core of the fights have remained the same, the falling down of the platform is a core part of that fight, Blizzard have mentioned before that it would be, infact wow.com posted something about it earlier. And incidentally, apprantly some of their healer's also had engineering as well, im sure they needed the DPS boost from the saronite bombs, I know I need to increase my DPS when im spamming nourish...
Feb 3rd 2010 11:37PM SamLowry
SamLowry Feb 3rd 2010 11:33PM
If I knew nothing about the encounter then I'd assume the floor was doing whatever it was programmed to do. I mean, Blizzard designed and tested it, right? So why would I have to assume that the floor rebuilding itself was somehow "wrong"?
This would be a valid point had Ensidia not done the boss on 10man. They did and were one of the first 20 guilds in the world to do so, so your point is moot. They knew exactly what was supposed to happen..
Feb 3rd 2010 11:13PM DJZygote Feb 3rd 2010 11:04PM
How were they supposed to know that the bombs were the culprit? They were being used every attempt. Also, is it on them to sit there and eliminate what could be causing the bug while they have limited attempts on the boss?
Because they had defeated the boss on 10man and had experienced the entire fight from start to finish. And there is no change to the fight on 10/25man other than his health. And considering the large amount of engineers in their raids along with the fact they claim its been part of their DPS rotation for a long time, odds are they found out on 10mans about the bug. So doing 25man and then just claiming "sorry we didnt know" is not an excuse an person with half a brain could accept. They knew exactly what they were doing and its a shame that people are defending them...
Feb 3rd 2010 11:02PM Its an exploit because the saronite bomb's were forcing the fight to create an overly benefical effect to their attempts on this boss in such a way that was NEVER INTENDED by the designers of the instance...therefore its a bug and if they had such knowledge of the bug going into the fight on 25man and used this bug for which they admit they did, it is classed as an "exploit"
Feb 3rd 2010 10:19PM Here's the first kicker for me. First off up until this week, most of their raiders had JC/BS. Now a large amount of them seem to have engineering right out of the blue. Next kicker is that they had done the fight on 10man and the bug does not effect 10man so they would have known beforehand exactly how the fight should go, therefore claiming that they did not know it was supposed to work like it did, is a non-starter of an excuse. 3rd kicker is taken from their statement:
Yes it seems this bug does relate to our kill. We had no idea that our Rogues using Saronite Bombs in their rotation (as they always do) was causing it and thusly it occured every try we did. Short version, we're not going to stop trying the boss when all we are doing is playing our normal game. It would be nice if these kinds of things, much the same as Holy Wrath on Anub, were tested before release.
It does make the fight easier, but we are 100% sure it would have died either way. It only affects one of the easier phases.
Now read Blizzards response on the severity of the bug:
We just made a hotfix that disables the siege damage dealt by Saronite Bombs and the Global Thermal Sapper Charge. The siege damage of the bombs was causing the Frozen Throne platform to rebuild, which """greatly""" decreases the difficulty of the encounter.
The people who designed the encounter have basically said that its a huge advantage while Ensidia plays it off as being just helpful and not critical to their kill. Now after all that, can you really say that Ensidia was innocent. Of course they weren't, they knew exactly what they were doing and quite frankly its unfair if they are allowed to keep access to this kill because it would mean by sheer poor testing of the content before going live, one guild will now have an entire weeks advantage over other guilds who are forced to fight Arthas without the same bug that Ensidia was able to gain. I dont think Ensidia should be banned, simply that they should be refunded their attempts and allowed to fight Arthas again but without the aid of the bug this time
If it truly was not a big deal, then surely they could repeat their performance..
Feb 3rd 2010 9:57PM Some people are saying that they have had the kill revoked and have recieved temp bans. I dont know if this is true and i would love an offical statement from Blizzard to see if this kill will stand..
Feb 3rd 2010 9:39PM Thats like saying, yeah we knew after the fight that we had beaten the boss even thou the fight was bugged and it was not a fair kill...still we want access to hard modes over any other guild that has been forced to do the fight normally...because we are ensidia..