![]() ![]() Recently, Ensidia, one of the most famous and talked about guilds in WoW’s history disbanded. The game improves every time a player with that sort of attitude leaves.The Ensidia Journey Nihilum’s End - Buzzkill Perspective I also entirely agree with Muqq sounding like nothing more than a whiny dumbass. This is in no way like Exodus's blatent and horrendous Yogg+0 event. What they should've done was stripped them of their items/achievement, but also refunded them their bugged attempts so they could do it the normal way instead of banning them.ĮDIT: However, that blog post by Muqq comes off to me as nothing more than very long, very whiny and immature QQ.I entirely agree with everything said here. What're they supposed to do? "Sorry rogues, but you'll just have to purposely do less dps because you're profession bonus breaks the game." They didn't go out of their way to evade bug mobs, all they did was go about their normal rotation, and it just so happened that a min-axing rogues rotation fucked up the encounter. On the other hand, this isn't like Exodus's Yogg+0. On one hand, their kill was bugged, so part of me says they should have to do it again. While this may seem as an obvious bug, I can imagine that it is not always clear for everyone. I do agree though that Blizzard should've fixed this bug before launching the last section of Icecrown Citadel. That American fail guild got banned as well, so I think it's only fair Ensidia got banned as well. Many people will probably be laughing at Ensidia, but to be honest I think everyone would have done the same. I am sure they care more about the Heroic mode, but the normal mode is still an achievement on its own. What if we would cancel the raid and another guild claims the world first and doesn't get banned for it?" They were thinking the same thing as everyone would be thinking: " Mhh, chances are that we might get banned for this exploit, but we'd rather take the risk of claiming the world first, because it isn't even certain that we will get banned for this. Thing is though, when you are fighting the greatest foe of Warcraft, the antangonist of Warcraft 3/World of Warcraft, I am 1000% sure that NO ONE is going to cancel their raid and send a ticket to a GM and wait for them to respond. ![]() However, something tells me that they realized there was something odd going on. If they didn't know about the bug, then I am greatly disappointed in Blizzard. Removing saronite bombs from your rotation would have been a gimp to the dps, it's kind of a weird no mans land of exploitation in my eyes. I'm usually pretty steely eyed when it comes to people abusing bugs to overcome a fight, however I am kind of on the fence on this one. However I love the thrill of chasing world firsts, and whoever can take them has earned my respect for that tier of content. This is pretty unacceptable, I am no Ensidia fanboy living in the US. It's unfortunate that something as basic as a saronite bomb, something that should be standard play for any leather working min/maxer was overlooked on the PTR. The way hardmodes need to be unlocked, having this reverted is effectively a week ban as it's going to push Ensidia behind the pack if other guilds are able to down him bug free (and I am sure they will). The 72 hour ban is a bit much as for most of the players in that guild I'm sure they play for little more than the thrill of world firsts. ![]() If it s true finally Cause i m tired of "smart game mechanics using" i mean some previous shitīut anyway cant see anything written there Yeah it's true, and although I wouldn't put it past Ensidia to find and use every venue towards beating a boss first (even unethical) it is ultimately blizzards PTR testing failure that this happened. ![]()
0 Comments
Leave a Reply. |