Something strange is afoot in the wee ours of the morning here, as Nihilum is reporting that the Death and Taxes guild on the Korgath US PvP server has disbanded. This guild has long been considered perhaps the premiere raiding guild of the US Servers. As of this writing, there is no further word on why they have disbanded, only that they have and that some of them will reroll Horde.
The front page of the official Death and Taxes site does not have any sort of news post on the issue, but does have a banner that reads "Rest In Peace Death and Taxes, Beta 2004-May 2008," and has a list of their world and US first kills. The forum's name has been changed to "Death and Taxes - Keep in Touch," though there does not appear to be a forum post accessible by a basic account that gives any insight or information as to the disbanding. Hopefully more information is revealed soon.
For now, we'll watch and see if more information comes forth. Perhaps they may be like Risen, believing the end-game progression is worthless but possibly reappearing in WoTLK. Either way, their achievements were many, and they will be missed.
Thanks to Liam for tipping us off on this.
Update: A poster called Flux (who is not a DnT member but claims he has talked to some), posting on Nihilum's forum thread on the disbanding, claims that they were having trouble retaining guild members due to the long stretch of time between Illidan's downing and any new content, and that the first week of Sunwell raiding was difficult. After attempts to mass-recruit to fill holes ended in a lower level of raiding ability than they were used to, DnT's leaders decided to disband. Apparently, many DnT members will be rerolling Horde on Blackrock.
You might want to take this information with a grain of salt, but it's the best we have for now.
Behind the cut is a list of Death and Taxes' world and US first kills.
Yesterday my guild was getting ready for our nightly foray into the Black Temple (we downed the first five bosses in 3 ½ hours, not too bad). Out of the blue, a member who has been having some "issues" as of late decided it was high time to leave the guild. And he didn't just stealth gquit, he went out in style.
Instead of being adult about it, which everyone in my guild is, he posted a long winded and rambling message to the guild and then left. His tantrum was quite good, one of the most epic I've seen. But the epicness of his lack of class wasn't the best part. The best part was that he had enough foresight to do it all with a macro. So after a bunch of us got done laughing about him leaving on ventrilo I thought to myself, "Self, I should post this on WoW Insider tomorrow. After all, a gquit macro sounds like a good idea!"
Take a look after the break to see some screenshots of this ex-guildie's gquit macro, and how you too can make your own gquit macro!
Menzoberranzan on Tichondrious-H decided recently that after a spat of drama, they were going to go on hiatus until Wrath, so their GL cooked up this video to show off some of the highlights of the guild. Most of it is just a slideshow of screenshots (so we're using it as the header shot this week), but jump up to 7:19, because there's some funny kids dancing.
Lots (and I mean lots) of drama in the GW this week (including the "corrupt loot council" that spawned that gem of a title), so make sure to click the link below to read it all. And don't forget to send your own tips in -- wowguildwatch@gmail.com is the email address. We want your downed, drama, and recruiting news, so send it all.
The short version of the tells above: Renzor tried to start some drama by posting a vent recording on the forums, and when Avasa (who took the screenshot) posted against him, Renzor threatens to kick him (and, as you can see, claims Avasa "likes to create drama" when Renzor was the one who posted the vent recording). Click the image above to see the uncut convo (with some not so SFW language), and click the link below to check out the whole story, along with all of the other drama (including a bit of bank drama that will surprise you) from this week's GW.
And if you've got drama, downed, or recruiting news from your own guild or someone else's, send it along to wowguildwatch@gmail.com. Your tips keep this thing running, so thanks in advance.
Looking for something to read. Look no further -- here's the best of our weekly features from the last seven days, presented in a handy roundup format. If you missed it the first time, don't make the same mistake twice.
Guildwatch: The aftermath The messiest part of guild drama comes after it happens. And when the bank has been ninja-d the last gquit has been typed in, and the last wipe happens -- that's when Guildwatch appears.
Just want to get something straight, so you all sending in Downed news can be sure to work out the "notice" mechanic correctly: every guild gets to put just one boss on notice every week. You can't put instances on notice (although if you do, you have to clear that instance all in one go, and we're going to need video or it didn't happen), and you can't put more than one boss on notice -- otherwise, everyone would put everyone on notice. One boss per guild, per week. Any other kills after that are just bonuses.
Now that that's out of the way, on to the Guildwatch! Click the link below to see this week's drama, downed and recruiting news from around the realms, and be sure to send us your tips, from your guild or anyone else's at wowguildwatch@gmail.com.
One person in the conversation above is making sense. And the other one is named "Krazyhunter." Be careful whose alt you roll against in Kingdom of Fire on Khadgar -- losing a roll on a piece you need to an alt of a co-GM might get you kicked. And, oh yeah, no matter what guild you're in, be careful who you send angry whispers to, because they might show up here on Guildwatch.
The story above and much more in this week's GW, including the return of lots of recruiting news. If you have tips for any of the sections below, send them along to wowguildwatch@gmail.com, and click the link below to see this week's drama, downed, and recruiting news.
Guildwatch is back, and boy do we have a drama-stacked edition for you this week. How about this Vent recording we've got, complete with classical piano playing in the background. Or this hacked guild that didn't really get hacked at all? We've got Shaman ninjas, Auction House drama, and even a Warglaive fight. Our tipsters really, really came through this week (thanks everybody!), and you reap the benefits.
Additionally, there's also plenty of downed news behind the break as well, and just a bit of recruiting news also (seems like most guilds are filled up for the time being). If you've got a tip for GW, whether for your guild or a great piece of drama you've seen somewhere, drop us a line at wowguildwatch@gmail.com and see it here next week. In the meantime, click the link below to see this week's GW!
Here on GW, we mostly focus on guild drama, obviously -- every week, we hear about GMs /gquitting with as little style as possible, ninjas cleaning out the guild bank, and friction between guild members. But guilds are really only a part of the ingame drama -- people can find silly things to fight about all over Azeroth. Think the fishing tournament is tame enough to avoid an argument? Think again.
That story, and more, are in this week's GW, which you can read by clicking the link below. And don't forget to submit your own tips to us, whether they be drama, downed, or recrutiing news. Wowguildwatch@gmail.com is the address, and any tips you send to it will be much appreciated.
Patch 2.4, much like most other things in WoW, has managed to bring the worst out of some people. The mask of anonymity strikes again!
No, I don't mean the node-stealing, ninja-tapping, mob-training stupidery(which is a word as of right now) you see all over the Isle of Quel'Danas. I refer to the standing-on-NPCs-while-PvP-flagged griefing. If you're lucky and haven't seen this happen on your server, what most servers are seeing is a bunch of Blood Elf and Draenei players standing directly on top of Shattered Sun Offensive NPCs, so players accidentally, unknowingly, right click on them instead of the quest NPC. This results in inadvertently hitting the player, and then getting destroyed by the SSO guards.
Here at GW, we love even the small downs (heck, this week, we reported on a downing in the Stockades -- although it was by the Horde), but when other guilds are able to clear out the whole endgame in the time it takes you to go from one endgame boss to another, it's probably not the best idea to go on to the forums bragging how great your progression is.
That story and many others in this week's GW, which starts right after the break. Your tips fuel our column -- please send any and all tips about drama, downed, or recruiting guild news to wowguildwatch@gmail.com. Click the link below to read on.
Only in the best situations do you have great documentation of great drama, and only in the best of the best do you have actual screenshots of it as it happens. But then again, that might just be more evidence that they're just messing around -- it's hard to believe that this really happened and was captured so perfectly.
But as always with Guildwatch, you be the judge. For all the drama, downed, and recruiting news you can handle (most of it probably true... probably), click the link below. And don't forget to send us your own tips (anonymous or otherwise) at wowguildwatch@gmail.com.
Spensi on WoW LJ says she may have accidentally ninja'ed -- it was clear before the raid that if Moroes' Pocket Watch dropped, she would get it. But when it actually dropped, she apparently looted it herself as main looter without saying anything, and her guildies didn't quite remember the deal before the instance started. Was it a ninja? I don't know -- there are good points on both sides.
In fact, it seems the only way to really avoid loot drama is to, unfortunately, be as selfless as possible. Last night, I did a run of Ramparts on my up-and-coming hunter, and on the first boss, the Hunter mail pants dropped. The other Hunter in the party needed them as well, so we rolled on them, and I won. Later in the instance, another green piece came up that we both needed, but to be fair, I let him have it. And finally, on the second boss, the mail hands dropped, and I did need them, but once again, to avoid drama, I just let the other Hunter have them. I could probably have made a case for at least rolling on them, but it wouldn't have been fair for me to walk away from the instance with two blues when he only had a green, so to keep the peace I let it go.
It worked out, too, because I picked up some great blue hands anyway when I turned the quest in. And that's the thing to remember when it comes to loot -- there will always be more of it. Even if your item doesn't drop, or you don't win this roll, or your guildie gets angry because you nabbed an item, even though they knew you needed it, there'll always be more drops and more rolls and more loot to get.
Yes, we know the headline is spelled wrong -- that's the joke. (So feel free to make fun of anyone who points out the misspelling in the comments; they're fair game.) In the meantime, the more "rediculous" the guild names, the better for us. Why would you want to name your guild Sentinels of Azeroth when you could name it something like Dont Be That Guy?
In the meantime, click the link below to see all the drama, downed, and recruiting news we got from across the realms this week. And don't forget to send your tips (especially drama -- let us know if you see anything either on your realm's forums or on your guild's forums) to wowguildwatch@gmail.com. Because not sending your tips to Guildwatch is pretty rediculous, if you ask us.
There will be drama, and when there is, Guildwatch is there to ridicule and call out all parties involved. Because WoW is serious business! I've abandoned my main tank! I've abandoned my boy! I am the Third Revelation!
Whoops, got a little carried away there. Meanwhile, this week's look at guild drama, downed and recruiting from across the realms starts right after the jump. And be sure to send your tips to wowguildwatch@gmail.com -- this column flows directly from them like so much black, slick oil.