This week’s weekly dungeon finder fail will not be read here. Why? Because there is no more epic of a fail group than that which Krizzlybear unfortunately endured. This is one of the most entertaining reads though you can’t help but cringe for Krizz throughout. If you aren’t normally in the habit of reading comments to posts, please take my advice and spend the time to read through these. There are some great ones in there and finally towards the end and epic fail post by the offender themself. While waiting for my desktop to finish loading WoW (after an epic system reinstall that took all evening), I decided to catch up on some blog reading via my phone. This made the time fly by and it also made every fail dungeon I have experienced or heard of this past week seem like bundles of warm sunshiney goodness.

If you’re still wanting more after reading all of that, head over to Dark Nemesis and read the ever-so-funny forum The Scrub Pub. If you don’t have a blog where you can get cathartic relief, try THIS site. Hell, even if you do have your own blog – it’s still funny to visit. I have it bookmarked now just in case. And completely not-WoW related but hilarious none the less: Failblog.org.

So I’m back for the conclusion of the story.

I left you yesterday standing in front of Ignis, about to knock out the weekly raid quest. Things are seemingly more positive for the time being.

At this point, I’m past the red flag moments. I have no excuse from this point on for having looked past any warning signs. I had already failed by letting the raid run rampant so let me just sum up the last fight for you.

Instead of downing Ignis how I have all the previous times I’ve done it, we ended up tanking him at the edge of the pool and not kill any adds. There are certainly multiple strategies for fights and kiting him is not the only way to down him. However, as raid lead I’ve never done it that way and I’m healing for the first time so I would have been more comfortable with the kiting method just because of familiarity. Sort of like my security blankie?

Anyways, we get Ignis down to under 200k the first attempt but we wiped. Not killing the adds meant he was stacking the buff increasing his damage with each stack. DPS didn’t look bad at all. Including the tanks, dps ranged from 7.6k down to 1.7k. We only had two people below 3k for that attempt. So we try it again, after all we really did almost have him. Second attempt was not nearly as pretty. DPS ranged from 4.5k down to 1.8k with again, 2 people below 3k. At this point the mage pug in the group proceeds to start whispering me.

Sadly, I didn’t phrase my response well. My intent was to be nice in telling the mage to stfu because the dps was fine. Instead, much to my dismay it came across as an agreement. I suppose after that I should have expected nothing less than the “I told you so” after downing Ignis. Remember back in the old days before Ignis was nerfed and people used to take him down with much less dps? I wish I had screen-shotted that kind of thing for times like these. To top things off, this mage also spammed DPS meters after each wipe. I detest that and it is easily one of my top three pet peeves. Of course, yet again instead of calling her on it and telling people to not do it again. . .I said nothing. I don’t think I’ve let so much crap slide in one raid – ever.

Two hours after I started looking for pugs and we downed him after the third attempt using the kiting strategy. After loot was done, I logged off the game and vent to save my sanity. Before I logged though, I made a slight comment to the tune of “that’s the last time I get talked into something” and a guildie whispered me immediately “Now you’re thinking with your head”. Last night consisted of a pretty long chain of errors on my part. Am I blaming anyone else but myself – aboslutely not. I cannot and will not put any blame on others if there were no expectations laid out up front nor if zero corrective actions were taken. I’m by no means a “my way or the highway” type, but this was certainly a very clear reminder to me that this is a new server and new guild both chock full with new people. The “norms” here are actually quite different than my old server. While that’s not a bad thing, it’s something that I need to adjust to.

It’s clear off my mind today aside from writing this post, hence the quick storytelling. I’m forming my steps forward and tagging this as Epic Failure #1 for 2010. Fortunately it’s out of the way early and hopefully few follow.

I like to try and find the silver lining to every story and the best I could come up with here is that while this was my first Epic Failure of 2010 . . . at least I didn’t die standing in fire.

And it only took two bosses.

Tonight was the first time ever that I’ve quit a raid.  Yes.  You read that correctly.  I quit the raid after the second boss.  A horrible example as a raid leader, and an even worse one as a guild officer.  But a blood vessel was going to pop, figuratively or literally who knows. My brother was in the raid and saw the shenanigans and my reactions first hand.  He suggested that Starbucks might be a good cure.  So we grabbed our laptops, hopped in the car and headed to Starbucks.  Kharma began the payback immediately because wouldn’t you know, Starbucks was closed.  We peeked across the street and Panera was also closed.  (And my parents wonder why I was in such a rush to move away from home?  Fortunately this is just a short visit and it’s back to civilization for me soon.)  We ended up down the road to Sonics, I picked up a Hazelnut Java Chiller and here I am back at home to admit my failure as a raid lead.

Kind of a huge blow to me personally actually.  I have never once been so frustrated that I could not – not mentally or physically – continue raiding.  The evening started fairly benign.  We went to my parents this evening because it was my mom’s birthday. Trying to excuse ourselves to get back in time for the raid was almost impossible, but we made it just in time.  We didn’t have many people on, but the weekly raid quest was Ignis and I decided to just pug out the spots that we needed.  It took a good 35 mins to fill everything but after losing a couple pugs and finding pugs replacements for the pugs. . .we finally get going.

Red Flag #1.
I ended up going on my druid to heal so that we could fill out the group.  Let me put this into perspective for you: My druid hit 80 on January 2.  That’s just under a week ago as of this post.  She’s fairly decently geared through badge gear, a few hand-me-down BoEs and craftable epics from fellow guildies so I’m actually way ahead of the gear curve as far as turning 80 is concerned.  I’ve been running heroics regularly and picked up some addition upgrades, but the only raids I’ve done are Ony 10/25 and Instructor Razuvious for the weekly quest last week.  I spent most of my time leveling through battlegrounds though so it’s not like raid healing is completely foreign to me.

Regardless, there is still a learning curve.  Healing a raid for the first time while raid leading isn’t generally a good mix, especially when you consider that this is the first alt that I have gotten to 80 and the only one I’ve raided with aside from my mage. Small things like “hey you can heal yourself while in the slag pot” slipped by me tonight.  And yes, I know that there are rockstars out there that solo healed Ulduar 2 days after they hit 80.  /eyeroll First of all you can suck it.  Second of all I have never come close to being a rockstar player and am honestly just a mediocre healer by my standards.  Had we had close to perfect circumstances this would still have been a challenge for me.  I am still in the dps mindset – it’s a harder transition that I thought it’d be.  Plus I’ll admit, I’m not perfect.  I’ve certainly made mistakes as a raid lead before, but I have never. . .ever. . .quit a raid – until tonight.

Red Flag #2.
We lost several pugs before we even started and had to find replacements for them. Before you even start summons and you go through 15 people just to do a 10 man raid, it’s the universe telling you to go fish mats for feasts instead.  I believe in fate and I should have recognized the “stars aren’t aligned” feeling early on (read: gut instinct) and that I needed to mentally prepare myself and I didn’t. However I did try to at least take advantage of the time we had while finding replacements by going ahead with vehicle assignments for Flame Leviathan while waiting.

Red Flag #3.
Someone activates Hard Mode by accident.  Granted, it’s easy to fix – just take out the towers.  A little more trash killing and it’s not an issue.  Plus, not many people run Ulduar so it’s easy to forget these things.  However . . . maybe it was fate speaking.  I did feel a knot in my stomach when someone said “oh I already talked to the big guy”. At this point I realize that I haven’t done my standard raid lead schpeel, especially in Ulduar so people don’t start hard mode unless we are going for hard mode.  I shrug off the bad feeling and roll with it.  Rolling straight to hell in a two-wheel soapbox apparently.  I should have stopped there and set the expectations and foundation.  My soapbox was rolling with loose axles and soggy cardboard at this point.

Red Flag #4.
I let people rush me - I let people rush my raid.  Not cool.  WTF was I thinking?  The minute I said to myself “and you can hold your gd horses, stupid ass” I should have made sure I had solid grip on the reigns.  Instead, this was a wild horse that was having none of it.  (how did we go from soapbox to wild horse, I’m not sure – just got with me on it) Regardless, we haphazardly clear trash and down Flame Leviathan in short order. Next thing I know people are complaining because everyone wasn’t grouped to do buffs for Ignis. Of course not you stupid asses – I was still doing loot so of course I’m not going to be there. But did I say anything? Nope. The knot in my stomach got a little tighter because I felt the reigns slipping away yet wasn’t doing anything about it.

Red Flag #5.
We have two tanks who have not tanked in Ulduar before – before I get to far into this section let me just say they did a great job and it could have been a heckuva lot worse. At this point, vent is bubbling with chatter and we have a couple people giving directions. I on the other hand, couldn’t get a word in edgewise. Normally I nip that in the bud as raid lead but for some odd reason, I let it slide tonight. We lost a few people during the first trash pulls to Ignis but recovered and the rest of the trash went very smoothly. Hey things are looking up right? Not hardly, it was simply the calm before the storm my friends!

Remember, I said it only took two bosses and here we are facing Ignis.  What happens next?  You’ll have to tune in tomorrow.

1.
There once was a game called Warcraft
Sometimes calling for reading and math,
But after all of the hollars,
Blizzard dumbed it down for some followers
Who then turned into elitist asshats.

~-~-~-~-~-~-~-~

2.
At first I created a mage
And I thought it would be just a phase,
But I found spells of fire
Of not which I tired
Oh how I love setting Hordies ablaze.

~-~-~-~-~-~-~-~

3.

I once saw a death knight flying high
above Wintergrasp fortress’s sky.
I casted slow fall
And threw hot fire balls
Then most dead on the ground did he lie.

~-~-~-~-~-~-~-~

4.
A ninja once hid in a group
And rolled need on an epic gold hoop.
I tried to be good
but I did wish that he would
Get hacked by a gold farming troop.

~-~-~-~-~-~-~-~

5.
To patch day we often look forward
To see the new things that we’ve heard of
But why people don’t think
Lag won’t hit us this week
Who knows but see number 1 up above.

~-~-~-~-~-~-~-~

6.
My mage killed Maly already.
My druid tried hard while a Tree
But small details matter
On the drake she went splatter
I forgot that the healer was she!

~-~-~-~-~-~-~-~

7.
There once was a rogue from Nantucket
who enjoyed when he caused quite a ruckus.
Keeping stuns up on me
While I tried PvP
It was enough for me to say “Fuck it.”