EnsidiaGamingCommunity

The frustration about the latest "news" is actually slowly taking it's toll on me. I have never before felt so brutally insulted without being able to defend myself, nor do I get to see any of the proof of what they claim to be "an intention of exploiting", they just "KNOW" that we knew what caused it. Let me clear some "rumors" up that has been roaming around lately because it just frustrates me that people just assume things out of their minds, without even knowing the encounters mechanics. It's up to you to chose if you want to believe it or not.

1. "They tanked Lich King on the edge".

False, all the way through until approx 17-18% he was tanked in the absolute center of the platform. Our both tanks died when I got ported inside without really knowing how to do that as a healer, since we only had a few ideas how to deal with it as a healer, I died and The Lich King enraged killing our both tanks. At this point he obviously ran around the room as a headless chicken gibbing people. Only time we used the edge was when he was casting "Neverending Winter", which is an aoe that covers the center of the platform and requires you to use the edges.

2. "They knew that the bombs respawned the platform".

Honestly, we are not superminds. During the attempts when this occured there were several things going on at the same time, it's impossible to spot what is actually causing a bug in that mess. Especially when you are learning an encounter (but hey, what do trolls know about that? The bosses are normally nerfed to obilivion before their guilds even get there). We had 3 dps teams assigned to the Valk'yrs. Those teams all had stuns and slows in order to make sure the Valk'yrs died before reaching the edge. For us the bug always occured during this phase, but none of us could explain why. Looking back, it's pretty obvious now that when Nahiko were dps:ing the Valk'yr he was assigned to he also used bombs since its a part of his normal rotation, thus platform respawning due to this unknown bug. Our first and only idea about what could possibly cause this bug was that it had something to do with killing the Valk'yrs in a certain timeframe, therefor an issue with the coding itself.

3. "They continued when they should have stopped and reported".

Alright, so lets see, I actually like this.

Putricide anyone? I've seen for myself several times the Slimes bugging out, therefor not actually targetting anyone during 100-0%. Thus completely removing that bit of the fight.

Ship battle. You can evadebug the boss so he never hits the tank at all for the entire duration of the fight.

Saurufang, heard of several bugs here. You could previously knock the adds over the edge using a moonkin (?). You could sit in a cannon and let the person with the mark die and therefor not heal the boss. You could DI the person with the mark while soulstoning the paladin, thus removing the dmg and the eventual heal if the person would have died (this one is extremely common in pugs).

Blood Queen, intentionally sacrifice a person with a bite in order to not hit the soft enrage.

I'm pretty sure PLENTY and PLENTY of the people right now accusing us for "not stopping when there was a bug" have abused several of these bugs themselfs, ON PURPOSE if I may add, in order to make the boss easier for them (creds to the ones that actually haven't). Would you wipe on putricide because an add bugs out?

Give up the shit about it not being the same thing, because it is exactly the same thing, even WORSE if you actually bug the encounter on purpose which has been the case for SEVERAL pugs atleast on Saurufang. It doesn't matter what boss, what instance, using a bug is using a bug no matter what.

What happened to us was pretty much the same, although we aren't masterminds and it's impossible to prevent a bug if you don't know the actual source of the problem and why on EARTH would we spend our limitied attempts on figuring out what's causing a bug, instead of actually trying to kill the boss?

4. "Ofcourse someone frapsed"

No, noone frapsed. I know its pretty hard to believe that you don't fraps a world first kill, but considering it really gimps your performance most people chose not to fraps because they rather be safe and not lag around with 10 fps on such an important encounter. We focus on killing, not frapsing. That's not why we play this game.

5. "Loads of people rerolled engineering the same day"

Get a grip, noone, NOONE lvled engineering that day. People have had engineering since a long long time back because it is the BiS proffession for most dps/tank classes that has any use of haste/armor, considering the glove enchant Engineering provides.

6. "Ensidia always encounters bugged bosses, bla bla bla bla"

Newsflash boys, we're almost always the first ones to even attempt them. THIS IS why we are the ones running into the bugs, not "Hordekillers" ranked #50450 on wowprogress. It's like buying a brand new car out of the factory, who are common to have "Baby diseases". The one driving it for the first year will run into the most faults, not the one buying it second hand 5 years later when everything has been fixed.

If we wouldn't have run into this bug, some other guild would have done it later on. Lets say the bug appeared on the world #5th kill. Would those people deserve a ban?

I don't see why it's a difference from killing a bugged boss world's first, or world 100th. That's called double-standards, if its wrong to kill a boss with a bug then its ALWAYS wrong to kill a boss with a bug, no matter what instance or boss it is.

If you have your back clean, then you can flame us for going through the fight even though we knew something was bugged. If you EVER at any point killed a boss while any kind of bug has occured, then you should simply just shut the fuck up and stop throwing rocks while standing in a glasshouse, because do you know what? You are just as bad.

Yes, I feel extremely insulted. I couldn't care less about a 72 hour ban if I know I deserved it, but both Blizzard and the people flaming should stop having double standards about what's bannable and not. For me it doesn't matter if its a 5-man heroic boss or the last boss of the expansion. Killing a boss with a bug should at all times be rewarded with a 72 hour ban if that's what their standards are.
If you can't understand the logic behind that, then I'm sorry for you.

And I didnt bother to proofread this blog, so excuse me if my english is absolutely terrible.