02-10-2005, 05:30 AM
Explanation of what (that I know) went down:
One night they used LoS bugs to split a linked boss group. So instead of 3 monsters in a boss fight, it was only 1. Some members even admitted to this. Blizzard warned everyone in that raid to stop exploiting.
The next night, they pulled a (pretty ingenious) trick with a Warlock / Rogue combo. Rogue snuck all the way through, aggro'd a boss (and his linked members). Warlock summoned the Rogue, so the boss group starts running all the way back, grabbing adds along the way. But the adds were slower than the boss group, so a Vanish or death once the boss group reaches removes the aggro from all other adds, so they skipped the entire content of MC to just grab the boss. Blizzard then despawned the instance about half an hour into the fight, and suspended accounts that had been present during both nights.
They only did the 2nd thing after the entire instance had bugged out, causing a reset. That excuse didn't fly with Blizzard, though. The fact they explained both exploits in detail on the forums shows they've done it. I don't see how posting logs from the times they've legitametely run through MC exonerates them from the times they haven't.
Everyone who got in trouble cried out "no fair" because they were warned for one exploit, then suspended for another. Then CQ tries to save its face with stuff like it's "proof" guide.
One night they used LoS bugs to split a linked boss group. So instead of 3 monsters in a boss fight, it was only 1. Some members even admitted to this. Blizzard warned everyone in that raid to stop exploiting.
The next night, they pulled a (pretty ingenious) trick with a Warlock / Rogue combo. Rogue snuck all the way through, aggro'd a boss (and his linked members). Warlock summoned the Rogue, so the boss group starts running all the way back, grabbing adds along the way. But the adds were slower than the boss group, so a Vanish or death once the boss group reaches removes the aggro from all other adds, so they skipped the entire content of MC to just grab the boss. Blizzard then despawned the instance about half an hour into the fight, and suspended accounts that had been present during both nights.
They only did the 2nd thing after the entire instance had bugged out, causing a reset. That excuse didn't fly with Blizzard, though. The fact they explained both exploits in detail on the forums shows they've done it. I don't see how posting logs from the times they've legitametely run through MC exonerates them from the times they haven't.
Everyone who got in trouble cried out "no fair" because they were warned for one exploit, then suspended for another. Then CQ tries to save its face with stuff like it's "proof" guide.
Trade yourself in for the perfect one. No one needs to know that you feel you've been ruined!