Altadin
14Apr/091

Wait, what?

flying cats on a farm

I'm not sure what scares me the most.

The fact that someone actually typed these words into a search engine ...

SuperKitteh!

... or that they brought them to my blog?

Tagged as: , 1 Comment
14Apr/091

Extended maintenance is extended.

Also: amused oozling is amused.  Tad's gurgling happily — and I'm giggling right along with him.

Why?  Because while there's still no ETA on the servers coming back up, there is an ETA on the ETA!   So if you're stuck at work, like I am ... don't worry.  You aren't missing anything!

Blizzard, I don't know how we'd get through the workday without you. 

*glub glub*

Tagged as: 1 Comment
14Apr/099

Love is a disgusting oozling.

And his name is Tad.

Heart Tad

 

Clearly, some bear loves me.

<3

Tagged as: 9 Comments
13Apr/096

No one is truly anonymous

Even online.

Ailis in Hunterland wrote about anonymity today:

Anonymity is a powerful thing.  When no one knows you in real life (i.e. can come knocking at your door to teach you a lesson, son), you can get away with any type of behavior you wish.  Get /gkicked because of your attitude?  Not really an issue, just go join another [guild].  And so on.

For some reason, this reminded me of something that happened years ago, when Blizzard was just a local employer (seriously; half of the guys I went to high school with worked as in-house testers!) and not the demigod of my online existence that it is today.

I was a moderator on an Internet forum that my then-boyfriend had created.  It was attached to prominent anime fansite, and while I've never cared much for anime myself (truth be told, I rather detest it), C. was understandably invested in the community he had built and I did my best to help with the administrative end.

One March 31st, one of our regulars posted a suicide note on the forum.  He wrote that he had just overdosed on insulin, and updated the thread every few minutes to update us on his "weakening condition."

It was the night before April Fool's Day.  I was pretty sure it was a joke, and loathe to make a public fool of myself by taking it seriously if it was.

... but what if it wasn't?

The doubt persisted, and for several minutes I was torn between my pride and my conscience.

Then I realized how utterly stupid that was, and called the poster's local police department.  I knew from previous threads that his father was a police officer, so I hoped someone at the station would know who he was and how to check on him.  I also provided the non-emergency dispatcher with the forum URL and the OP's IP address and Internet service provider.

It must have been enough, because the police department called me back a few hours later with the news that an officer was able to track the OP down and verify that he was fine; it was indeed an April Food's Day prank.  Supposedly, someone did knock on his door to teach him a lesson — much to the shock and chagrin of his parents!

The OP played it off afterwards, telling everyone that of course it was a joke (and wasn't I stupid to fall for it?), and bragging that he "didn't even get in trouble."

Anyway, Ailis's actual post isn't so much about anonymity as it is about how to take responsibility for your raid preparation and performance — and it's a good one.  But that one little paragraph got me to thinking: anonymity isn't always so anonymous!

Tagged as: 6 Comments
10Apr/098

Unmixy things: Castsequence Macros and Affliction

Like Buffy and cars, /castsequence macros and Affliction are unmixy things.

This is because Affliction doesn't have a set rotation.  What it has is an opening sequence, which (in the 3.0.8 world) looks something like this:

  1. Shadowbolt
  2. Haunt
  3. Unstable Affliction
  4. Immolate
  5. Corruption
  6. Curse of Agony
  7. Siphon Life

Some Affliction warlocks pair Unstable Affliction with Immolate because these spells have the same DoT duration.  Others alternate their instant casts with non-instants to minimize the impact of global cooldowns, or cast Corruption sooner rather than later to maximize Molten Core uptime or Nightfall procs.  (I frequently do this if I'm still moving into position as the tank pulls, and can't necessarily stop to cast a Shadowbolt or Haunt but can throw a few instants at a boss.)

As far as I can tell, this is largely a matter of personal preference.  Beyond casting Shadowbolt first (to proc Shadow's Embrace) and Haunt second (for the +20% to DoT damage), there is no significant DPS gain or loss from casting Unstable Affliction ahead of Immolate or vice versa.

For this reason, most Affliction locks will choose an opening sequence that's comfortable to them or amenable to the situation and simply memorize the keybindings.  For me, it's 2-1-D-3-4-5-S.  Intuitive?  No.  But after several months of raiding as Affliction, my fingers know the cast sequence better than my brain does — so much so that if I respec Metamorphosis/Ruin or Felguard/Emberstorm, I literally have to trade keybindings.  Otherwise, I'll find myself casting Shadowbolts instead of Incinerates because my fingers want to spam 2.

The (Sort Of) Exception

If your little black heart is absolutely set on macroing your initial sequence for simplicity or convenience — okay, fine.  I personally don't see the point (you'll have to memorize those binds sooner or later, because a /castsequence macro is ineffective for anything beyond your opening salvo!), but there's no real harm in it.

In this case, a simple macro like

/castsequence reset=12/combat/target Shadowbolt, Haunt, Unstable Affliction, Immolate, Corruption, Curse of Agony, Siphon Life

will allow you to cast all seven spells by spamming the same keybind seven times.  It will also reset after 12 seconds, or every time you exit combat or change targets.

However, once you've cycled through your opening sequence, and have six DoTs of various durations rolling on a target — or multiple targets, if you're feeling particularly ambitious! — then Affliction becomes a priority system rather than a rotation.  Some spells are more important than others (Hint: Haunt > *).  Some DoT's can be clipped without a significant DPS loss; others can't, or least shouldn't be.

If you rely upon your /castsequence macro at this point, then you're setting yourself up for failure.

Juggling DoTs

Managing a DoT rotation requires two things: (1) attention and (2) conscious thought.  A /castsequence macro isn't capable of either — so maximizing DoT uptime is entirely up to you.

Some things to keep in mind:

  1. Haunt is your #1 priority.  Not only does it increase your periodic damage by 20%, but it also refreshes Corruption via talents.  It's okay to clip Haunt; in fact, there will be times that you have no choice.  Because Haunt has both a cast time and a travel time, it has to be refreshed early.  If one of your DoT's is expiring at about the same time, refresh Haunt even earlier so you can refresh the DoT as well.
  2. The final ticks of Curse of Agony and Immolate do more damage than any of the ticks that precede them.  Try to avoid clipping these DoTs.  Your goal is to refresh them immediately after their last ticks.  If you can't — because Haunt needs to be refreshed or you know you won't be able to stand still or stay in range long enough to cast — then it's better to clip the last tick than to allow the DoT to fall off for more than three seconds at a time
  3. You can't refresh a DoT early if the previous cast was modified by a talent or trinket proc, unless the same or an equivalent proc is also active at the time that you attempt to refresh it.  In other words: if your last Immolate was buffed by Molten Core, attempting to refresh Immolate early while not under the effect of Molten Core will result in "a more powerful spell is already in use" error and a wasted cast time.
  4. Use Shadowbolt as your primary filler when a mob is above 25% health, and Drain Soul when a mob is below 25% health.  You will still need to refresh your shadow DoTs (i.e., everything except Immolate) at 25% and below, but to maximize DPS, cast them after Drain Soul ticks (which come every three seconds) whenever possible.

Timing! is! Everything!

When it comes to Affliction DPS, timing is everything.  That's why the spec is so hard to play right; it requires active thought rather than simple memorization, which absolutely cannot be replicated with a /castsequence macro. Do yourself and the rest of your party or raid a favor, and don't use one beyond your opening sequence.  (I would even go so far as to suggest not using one, period, because of the bad habits it can easily engender.)

In lieu of a /castsequence macro, I strongly recommend downloading DoTimers and Quartz.  DoTimers is a wonderful little add-on that creates countdown timers — and, for the more visually inclined, bars — for each mob that you have DoTed.  It tracks the duration of each active DoT in descending order, and even changes colors when a DoT or spell effect is about to expire.  Meanwhile, Quartz is a modular cast bar that accounts for latency; I use it primarily to chain Haunt-Unstable Affliction-Immolate and time Shadowbolt casts.

The advantage to these add-ons over a /castsequence macro is that they will help you manage your DoTs and maximize uptime, not attempt to do it for you — and fail utterly in the process.

The moral of this post?  If you wouldn't let your cat tailroll across the keyboard (and believe me, mine tries!), don't use a /castsequence macro for Affliction DPS!

On the Other Hoof: Totems

That said,

/castsequence reset=8 Totem of Wrath, Flametongue Totem, Strength of Earth Totem, Mana Spring Totem

is all kinds of awesome. ;)

Tagged as: , 8 Comments
9Apr/098

I had the oddest dream last night …

DaisiesIn this dream —

... And, yes, I am writing in the present tense (and thoroughly abusing punctuation in the process!) because I cannot for the life of me remember if I should be using dreamed, the past tense, or dreamt, the past participle ...

— Ahem.  In this dream, I was working on a presentation for school (Why? I graduated from college in 2003!) with one of the hunters in my guild and a prominent warlock blogger who I'm too embarrassed to name.  >.>

I think the presentation was about airplanes, because I very vaguely remember cutting pictures of jets out of military magazines and gluing them to poster board.

Um, yes.  Anyway.  At one point, the warlock blogger — still not naming names! — volunteered to create a title page for our presentation, which she meticulously shaped out of pink and yellow cardboard daisies.

I was far too nice to say anything, even in my dream, but I remember being absolutely mortified.

You're a warlock.

These are daisies.

What exactly is wrong with you?!

... and then I woke up.

/blush

Tagged as: 8 Comments
9Apr/092

Answers for Abigore

Alternate title?  "Alliteration.Win."

Abigore of Fear.Win is curious about what 3.1 has in store.  Sure, we've all read the patch notes (well, you probably have; I think I might be a build or two behind >.>) — but how are the upcoming changes going to affect how we spec and play?  And are these changes going to be driven by cold, hard math or by our enduring passion (<insert obligatory stamina joke>) for the class? 

What spec are you currently?

Felguard/Emberstorm (0/41/30) currently; Haunt/Ruin (53/0/8) traditionally.

How long have you used this spec and why did you choose it?

I much prefer the playstyle of Haunt/Ruin to Felguard/Emberstorm, but (as I've observed before) the former tends to be much less forgiving than the latter — and after raiding primarily as a resto shaman for the last few months, I'm finding that I've actually forgotten 'how to lock.  /shameface

I recently had an opportunity to 'lock it up in Obsidian Sanctum because some odd twist of fate had us running healer-heavy and DPS-light.  I was still specced Haunt/Ruin and slightly outgeared the other Affliction warlock in the raid.  Nonetheless, he trounced me — and everyone else — on the damage meters. 

The dust was still settling around Sartharion's corpse as I fled to Undercity to respec Felguard/Emberstorm.  Going Demo/Destro doesn't help me relearn Affliction, but it does spare me the embarrassment of subpar DPS when I PuG into raids.  Now, I'm just kind of waiting for 3.1; there's no point in camping a target dummy to practice a rotation that will be obsolete in a few weeks.

What are you most unhappy with in your current spec?

It's not Affliction. 

At the risk of repeating myself, the problem with Affliction isn't its relative complexity; it's the fact that it's completely unforgiving.  If you've ever lost a 20+ stack on Malygos after eating two Power Surges in a row and had to start all! over! again! ... then you know exactly what I mean. 

What spec will you be taking in 3.1?

I haven't decided yet.  I haven't been following the 3.1 news at all, and I never bothered to copy my warlock (or any other character, for that matter) to the PTR.  I've been so focused on completing Glory of the Raider that I think I actually managed to convince myself that if I didn't think about the patch, it wouldn't arrive until after I earned my Plagued Proto-Drake ...

Rawr!

If you plan on dual speccing, what will be your offspec?

If I were still raiding on my warlock, I'd probably dual-spec Affliction for long fights and some variation of Demo/Destro for heroics and trash.  (Yay, burst!)  But since I'm semi-retired, I don't think I'll bother — as much as it pains me to admit that it what started as a "warlock blog." 

The dual-spec I'm most looking forward to is Resto/Enhancement.  (Windfury, how I missed thee!)

Tagged as: 2 Comments
8Apr/0910

How we defeated Sartharion-10 with three drakes

First, please understand that this isn't intended to be a comprehensive guide to the fight.  This is why I don't write guides is a blog tag for a reason!

No, my intention here is simply to share how we defeated the single-hardest encounter in the game, and hopefully provide some insight into our strategy, thought processes and basic positioning to other groups looking to attempt it.

For the purposes of this discussion, I'm going to assume that anyone reading it is already familiar with the basics.  If not, WoWWiki is an excellent resource.  (Go!  Check it out.  I'll wait.)

Okay, then.  Very briefly:

  • Sartharion is a typical dragon, in that he cleaves, breathes fire and tail swipes.  He has to be tanked throughout the encounter and will summon three Twilight Drakes at timed intervals.
  • The Twilight Drakes are Tenebron, Shadron and Vesperon.  Like Sartharion, the Twilight Drakes drakes also have a breath attack, although theirs deal shadow damage rather than fire.  In addition, each drake (1) opens a portal to another realm and (2) has an aura that will remain active on the entire raid for as long as the drake is alive.
  • Tenebron lands first, a mere 30 seconds into the fight, at the far west end of the island.  Her aura, the creatively-named Power of Tenebron, increases the amount of shadow damage taken by the raid by 100%.  She spawns eggs in the portal realm that hatch into Twilight Whelps, which must be picked up by the add tank.  Otherwise, Tenebron's portal can be safely ignored.
  • Shadron lands 60 seconds seconds into the fight, towards the south end of the island.  His aura increases the amount of fire damage taken by the raid by 100%.  He also spawns an acolyte in the portal realm, who increases fire damage done by Sartharion by 50% and renders Sartharion immune to all damage.  For this reason, Shadron's acolyte is the only one we bother to kill.
  • Vesperon lands 75 seconds into the fight, towards the north end of the island.  His aura reduces everyone's maximum health by 25%.  Like Shadron, Vesperon spawns an acolyte in the portal realm.  While his acolyte is active, Vesperon gains the Twilight Torment effect, which increases fire and shadow damage taken by 75% and reflects a percentage of all non-periodic damage done to Vesperon back onto the raid.
  • In addition to Sartharion and the Twilight Drakes, there are several AoE effects to contend with: (1) a lava wave that sweeps across the island, and must be avoided; (2) lava strikes that target individual players, deal painful splash damage and spawn fire elementals; (3) the fire elementals themselves, which will become enraged if struck by a lava wave; and (4) void fissures summoned by the Twilight Drakes.
  • When all three drakes are alive, Sartharion's breath and most AoE effects can one-shot the raid.  Cooldowns like Divine Guardian and Guardian Spirit are absolutely required to save a tank from a one-shot breath.

If it sounds like a lot to deal with at once — it is!  Once upon a time, a resto shaman of my acquaintance described the Illidari Council as the "Superbowl of Not Standing in Bad®" ...

Ha!  How naive and innocent we were back then!

Group Composition

We experimented with several different group compositions.  In the end, this was the winning combination:

Main Tank: Death Knight
Drake Tank: Feral Druid
Add Tank: Protection Warrior
MT Healer: Holy Paladin
Raid Healers: Holy Priest, Restoration Shaman
DPS: Elemental Shaman, Fire Mage, Mutilate Rogue, Shadow Priest

As you can see, it's a fairly straightforward, three tank/three healer/four DPS set-up.

As Ashellia noted, many of the strategies you'll find online recommend bootstrapping a hybrid to fill the role of two characters.  For several attempts, we tried having a healadin tank the fire elementals and Twilight Whelps by using Consecrate and Righteous Fury plus Flash of Light to keep himself up and hold healing aggro.  The idea was to replace our add tank with a fifth DPS class — preferably an unholy death knight, balance druid or affliction warlock for the +13% buff to magical damage.  Unfortunately, this put us at the fickle mercy of the RNG: if we caught a bad string of void zones or lava waves, then our multitasking paladin would be forced to concentrate more on dodging The Bad® and less on healing.  Lacking the mitigation and/or avoidance of a real tank, he would inevitably succumb and loose adds on the raid.

Switching to a three tank/three healer combination put considerable pressure on our DPS, but also gave us much better control over the fight and the fifteen hundred things (I'm not exaggerating: there really are that many — I counted!) that can go wrong.

A few things worth mentioning about this particular composition:

  • Death knights have more panic buttons available to them than any of the other three tanking classes.  Using a death knight tank meant that we only had to coordinate two other cooldowns to survive what we came to refer to as Sartharion's "one-shot breath phase."
  • Protection warriors make excellent add tanks!  It seems to me that many, many warriors are still locked into the old TBC mindset (i.e., that warriors are single-target tanks — period, dot — and paladins are the superior AoE tanks).  This is no longer the case.  Don't believe me?  Ask Spinks!
  • Our priest was Discipline for our first few (dozen...) attempts.  At first blush, Grace and Pain Suppression seemed too good to pass up.  But we eventually came to realize that a combination of one single-target healer and two AoE healers was vastly superior to two single-target healers and one AoE healer, and so our priest donned wings for the occasion.
  • Two shamans = two Bloodlusts!  This meant we had a Bloodlust available for every learning attempt.
  • A rogue was the lone melee DPS in our caster-heavy raid.  (/tar Ignus /lick).  Not only was he expected to DPS the drakes and tank Shadron's acolyte during portal phases, but he was also tasked with tranquilizing enraged fire elementals.  The add tank pulled them to the rogue, and the rogue used anesthetic wound poison and Fan of Knives to great effect.
  • (The downside of calling for fan of Fan of Knives is that it inspires the raid to make awful FoK puns all night.  Be warned.)
  • Finally, having only four DPS meant that we had to eke every last bit of damage out of them.  To this end, our holy priest dusted off his Smite button and our bear tank learned how to dance!  (More on that, later...)

Safe Spots & Basic Positioning

3D

Our Death Knight tanked Sartharion in the southeast corner of the island, alternating between the two "safe spots" marked (roughly!) in yellow.  His healer, a paladin, moved with him — running through Sarth to the easternmost tip of the island for waves originating from the north.  (I highly recommend running through Sarth rather than around him, as less movement = more healing, especially for an MT healer without instant casts.  Just be sure to stay closer to his forelegs than his hindlegs to avoid an untimely tail swipe.)

Meanwhile — and this is one of the keys to our success, because it maximized DPS time — our drake tank moved between three tanking postions, from (1) the western edge of the island, where Tenebron landed 30 seconds into the fight, to (2) the southwest corner, a south- wave safe zone, to (3) the center of the island's southern border, a north wave safe-zone as well as Shadron's landing point.

While Tenebron and Shadron were active, the raid spread out throughout the island's central band, in the north-wave safe zone.  For south waves, we ran west (away from the instance entrance).  The drake tank and melee DPS shifted west well.  Meanwhile, the Sarth tank and his healer alternated between the two eastern safe zones (closer to the instance entrance.)

Positions (more or less)

The challenge with this positioning was that it frequently put the MT and MH out of range of the rest of the raid.  For this reason alone, it was absolutely critical that the healers trust each other to cover their respective assignments.  (I was going to elaborate on this point, but Bellwether published an excellent post on the subject this morning, so I'm going to direct you to her instead.)

Finally, once Tenebron and Shadron went down, the entire raid shifted east and alternated between the same safe zones as the MT and MH.

A Walk-Through

We started each attempt with our death knight on foot, and the rest of the raid mounted — or ghost wolf'd, for the sheer novelty of it. <insert wolfish grin here>

The death knight pulled Sartharion into position, closely followed by his healer.  At the same time, the raid road around Sarth (mindful of his tailswipe!) to the center of the island, a north-wave safe zone.  Although we weren't concerned about damaging Sartharion at this point, the drake and add tanks and lone rogue had 15-20 seconds to generate rage or combo points before Tenebron landed.

Twenty seconds into the fight, our raid leader called "Positions for Tenebron!" over Vent.  This was the cue for our drake tank and melee DPS to peel off of Sartharion and dash/sprint to the western edge of the island in preparation for Tenebron's landing.

Because he was already in position, our drake tank was able to pick up Tenebron the moment he became targetable and move her around the southwest corner of the island.  This in turn allowed DPS to unleash on her almost immediately, especially if we were lucky enough to catch a south wave.

We typically blew our Bloodlust at this point, with a goal of bursting Tenebron down before she could open a second portal and thus spawn a second wave of Twilight whelps.  Since raid damage relatively light this early in the fight, our holy priest was able to DPS (lolsmite?) until Shadron landed.

... I might've cast a Lightning Bolt or two, myself.  Don't tell my raid leader.  >.>

In preparation for Shadron's arrival, the drake tank moved Tenebron along the southern edge of the island, towards that central band/north-wave safe zone.  He tanked Shadron here when he landed, and fifteen seconds later pulled Vesperon to this location as well.  (In the 25-man version of OS, our drake tank typically drags Shadron to Vesperon's landing point and tanks both drakes on the north end of the island, but this strategy caused range issues for our healers in OS-10 so we abandoned it after a few attempts.)   The drakes were tanked on the southern edge of the island for the rest of the fight.

As soon as Tenebron went down, DPS switched to adds and AoE'd them down— providing some much welcome relief to our warrior tank, who by this point was holding at least one wave of Twilight whelps and all of the fire elementals spawned thus fars.

With the whelps slain and fire elementals back under control, DPS focused Shadron.

After Shadron died, DPS and one healer entered the portal realm to kill Shadron's acolyte, as Sartharion is immune to damage whenever Shadron's acolyte is active.  We ignored Vesperon's acolyte (we learned after one particularly heartbreaking wipe that killing both acolytes extends the fight unnecessarily and causes undue strain on healer mana), and simply exited the portal after Shadron's acolyte went down.

Since Vesperon's acolyte was alive (and ranting impotently) in the portal realm, the Twilight Torment remained active as DPS began the slow, controlled burn on Vesperon — backing off any time they dipped below 40% health.  By this point, the fight had long-since become a blur to me; between frantically dodging void fissures and lava waves, not to mention healing through constant AoE and reflective damage, I didn't even notice Vesperon die until I heard Keaton's perpetually calm voice reminding us not to panic, because this is the fight we've done a hundred times before.

With all three of the Twilight drakes down for the count, our bear tank taunted Sartharion and took over as MT and our death knight switched over to DPS.  At this point, the fight became the simple tank 'n' spank ('n dodge The Bad®!) that we all know so well.  The only difference was that we did it while holding our breaths, because victory was seconds away ... and history tells us that's usually when something goes disastrously wrong!

Fortunately — this time — it didn't.

Tips

Some final comments and tips from our experience:

  • Don't worry about DPSing Sartharion in the 30 second window before Tenebron lands.  First, it isn't necessary.  Second, your MT will probably be in stamina gear, and won't have the hit or the swift threat generation you're accustomed to this early into the fight.  Feral druids, warriors and rogues can take a swipe or two (no pun intended!) at Sarth to build rage or combo points, but everyone else should use this time to get situated: drop your totems or Demonic Circle, familiarize yourself with the safe zones, cast a Riptide on the MT to proc Tidal Waves, etc.
  • The drake tank and melee DPS should already be in position when Tenebron lands.
  • If raid DPS is a little low (and ours was, with only "four" real DPS and a Smite-spamming priest), use Bloodlust/Heroism to burst Tenebron down as quickly as possible.  If he lives long enough to summon a second wave of Twilight whelps, then your add tank can become overwhelmed.
  • Coordinate your tank-saving cooldowns before the fight, and have someone call for each cooldown in a pre-determined order.  If you're in the cooldown rotation, this is your #1 priority; with all three drakes in play, Sartharion can and will one-shot the tank.  Communication is key, not only to ensure that no one misses a cooldown, but to cover other raid roles as well.  (For example, when it was our holy priest's turn to use his cooldown, our elemental shaman assisted with raid heals.)
  • You don't need a plate DPS class to tank Shadron's acolyte in the portal realm.  Our rogue did it, and was very easy to heal.
  • Have someone who isn't in the portal realm call lava waves on Vent.  If a lava wave is active or imminent, wait until it passes to exit the portal.
  • Play to your strengths. Don't feel trapped by someone else's strategy; assess your strengths — and weaknesses — and adjust accordingly.
  • Don't get discouraged! This is the hardest fight in the game, and you're meant to wipe on it ... a lot.  It took us close to 20 hours of attempts over the course of several weeks to learn.  Progress can be agonizingly slow and is often difficult to measure, especially because there are so many random elements to overcome.  It isn't unusual to down two and half drakes in one solid attempt... and then wipe in the first thirty seconds of the next one because your drake tank found himself trapped between a void fissures and a lava wave or your holy priest ate two successive lava strikes.  As frustrating as this encounter can be, it is the cumulative challenge of all these rage-inducing elements that makes the eventual victory worthwhile.  Believe me, triumph is sweet ... and it tastes like dragon.
3Apr/0914

Argh!

If you were my debit card, where would you be?

Tagged as: 14 Comments
1Apr/096

Finally!

Of the Nightfall!

9 visitors online now
9 guests, 0 members
Max visitors today: 22 at 12:15 am MST
This month: 22 at 09-08-2010 12:15 am MST
This year: 147 at 03-09-2010 06:38 pm MST
All time: 285 at 11-05-2009 01:25 pm MST