QUOTE(Quark @ Nov 9 2005, 08:24 AM)
Here's the way one guild on our server managed it:
1)Lets say your guild kills Luci on Monday, getting through the first six bosses.
2)On Wednesday, two people from your guild (not in the first raid) attend another's Luci/Mag raid.
3)Thursday, the group locked into the first instance finishes it, killing Ragnaros.
4)On Sunday, your raid ID is expired. Have the two that were on someone else's run start the raid, everyone else joins in (with no raid ID), and you go from there wiping out bosses. Here's the kicker: You've got all but two MC bosses to down, but your raidlock still expires on Tuesday. You can now manage to kill Ragnaros 3 times in 2 weeks.
Even worse, you've now essentially stolen that ID from the group the random players were with. You're progressing in somebody else's instance.
If your guild is big enough, you could manage to do this without outside "help". Do it right, and you're looking at about 3 Ragnaros kills a week.
It get's worse than that, I have heard of a guild that had enough lv 60s (mains and alts) to kill Luci on day 1 (thus locking the instance).
What you would see if the following:
Monday Raid 1 of 20 kills Luci
Tuesday Raid 2 of 20 kills Luci
Wednesday Raid 3 of 20 kills Luci
Thursday Raid 4 of 20 kills Luci
Friday Raid 5 of 20 kills Luci
Saturday Raid 6 of 20 kills Luci
Saturday Raid 1 + 20 others not from raids 2 through 6 finishes off Mag through Rag
Sunday Raid 1 + 1 from Raid 2 + 19 others not from raid 3 to 6 finishes off Mag through Rag
Monday Raid 1 + 1 from Raid 3 + 19 others not from raid 4 to 6 finished off Mag through Rag
Tuesady Raid 1 + 1 from Raid 4 + 19 others not from raid 5 or 6 finish off Mag through Rag
and you repeat, mix and match however you want and you basically can down Rag every day if you so choose after you start the initial rotation. I'm not sure what happened to the above guild I heard about, but they were doing exactly this and were flaunting it on their own server boards. I can only hope that Blizzard permaband the accounts involved in this.