Matticus, Author at World of Matticus

The Body and Soul Spec

September 14, 2012March 31, 2010 by Matticus

I’ll admit, I’ve always dismissed Body and Soul as an odd talent that had little to no use in raids. Players should be able to run out of anything dangerous on their own or with the aid of a boot speed enchant if they’re slow. As such, I’ve never really considered it at all.

But ever since that Power Word: Fail round table event held by the Raid Warning guys where Aliena, Derevka and myself chatted, I had to reconsider. Have I mentioned that they’re my personal favourite podcast crew to work with?

The spec

Here it is (14/57/0)

This is the one I’d use as it has many of the traditional elements of a Holy spec. You can shift your points around from Empowered Healing, Blessed Resilience, and Test of Faith accordingly based on your own preferences. Personally, I favor Blessed Resilience but that’s because I’m aware of what kind of an effect it has. You may prefer Test of Faith for the extra throughput (even though it is conditional). If you’re not a Flash Heal or Greater Heal type of player, you might opt for full points in Blessed Resilience and Test of Faith. Anyway, that discussion is for a separate post entirely (hopefully soon assuming Derevka has spare time at some point).

Why would you ever use Body and Soul?

For me, I’ve discovered that it has extra utility in progression fights. The talent a minor run speed increase for 4 seconds which is enough to give players a quick boost when running away. When learning fights for the first time, I often use this at specific times.

In an extremely high level raiding guild, I would argue that this talent is unnecessary. Players can easily handle movement fights and do not require the aid of extra sprint abilities to escape hostile spells. It’s just not necessary. Connections and computers are at peak efficiency resulting in near-zero lag. Situational awareness is so high that players will move without realizing that they had to move.

But not every guild is like that. Not every raid can perform like that. For me, I need to look at every possible edge I can utilize in an encounter. Nothing frustrates me more than a player who is unable to outrun a Sindragosa explosion, or a Necrotic Plague on Lich King or any number of other abilities because of technical problems. Doesn’t matter how good the player is as bad connectivity connections will almost always negate that. I can’t make everyone’s connection super awesome. I can’t magically snap my fingers and create 102 FPS conditions. The next best thing I can do is cast a spell that’ll make people run quicker and get them out of dangerous situations faster. I may not be able to account for lag, but I can at least function as a safety net and buy an extra second or two for that player and help them live when they otherwise would have been lost.

Just keep in mind that it might annoy your Discipline Priest.

Anyway, it’s largely used on progression fights to help “smooth” things over until a fight “clicks”. You’re giving up potential throughput for increased (but selective) movement speed which comes in handy for heavy movement bosses. Plus it also makes the run back from wipes slightly quicker and I know I won’t be last back! Go ahead and give it a shot. Let me know what you think.

[VIDEO] Healing Valithria Dreamwalker

March 29, 2010 by Matticus

My first foray into video editing! I managed to compile the footage and stitch together some audio as well. There are enough boss strategy videos out there that explain what the overall raid needs to be doing on different encounters. My focus here was to target the individual who was healing. I’m not the perfect, top-tier Priest so you’ll catch a glimpse of several misplays throughout the video that I’ve made. All the while, I’ll be narrating the things I’m doing and why I did them. Therefore, it is assumed that viewers know the mechanics of the encounter.

You can tell by listening to the first several seconds that I’m extremely nervous and it took a few retakes when I was recording before I managed to calm my nerves.

The narrations will sound different periodically because I was experimenting with different amplification levels and microphone distances. Initially, I started writing down what I wanted to say at different points and then just recording it into Adobe Audition before importing them back into Movie Maker. About halfway through, I just gave up and recorded the rest of it in one shot on the fly without any serious scripting at all. We used to play a game in drama class that involved doing a bit of improv so I figured I could wing the rest of it. It’s the same thing during any sort of in-class skits, right? Get the rough outline and improvise the rest of it on the fly.

The various voices you’ll hear throughout the video is chatter from vent. I decided to leave them in there largely because I haven’t figured out how to strip them. Also, it’s there as a glimpse into the way my raids operate.

Next video is on Sindragosa which I hope will be infinitely better.

Things I need to improve on

Problem: Expanding into high-def or widescreen at least
Solution: No idea yet

Problem: It’d nice if I could freeze frame for a few seconds
Solution: Software issue? I’m using Movie Maker, but I’m going to see if I can grab an educational copy of Vegas from school at some point

Problem: Zooming in and drawing football-style X’s and O’s
Solution: Ditto the above

Problem: Too tense and nervous
Solution: Two beers

Your thoughts? Again, this is my first video so be nice. Once I get better and more polished, I’ll put subsequent ones on the WoW dot Com Youtube channel. I didn’t feel that this one was particularly up to snuff yet. But, I wanted to at least get my feet wet.

Software: Adobe Audition, Movie Maker, Fraps.

Healing: Priority, Priority, and Priority

March 25, 2010 by Matticus

Several weeks ago, I mentioned how much I didn’t like two-healing 10 man raids. Why? Basically because if a healer goes down, there’s utmost pressure on the other healer. A raid almost never recovers. With 3 healers, if one dies, you can still pull off a kill. And today, I’m going to write about one of those experiences where I was 2-healing a guild 10-man raid where another healer went down.

Sometimes you hit one of those days where your ego gains a massive boost because you’ve singlehandedly healed a raid down to 0%. The worst case scenario that you’ve planned for countless of times in your head actually happened in a raid encounter and you pull off every pre-planned spell, move, and cooldown with such eye surgeon-like precision leading to an unexpected kill.

And I still can’t believe I pulled it off. Anyway, while the kill is still fresh from memory, I’ll walk you through my various thought processes in the event something like this should happen to you. Healing can be a sleepwalk. Other times, it can be a big kick in the groin. Our healing pairing happened to be Holy Priest and Discipline Priest (I was Discipline for the fight). We determined ahead of time that since we had a Prot Paladin tanking Ooze, they could tackle the dispels.

We were taking on Rotface in ICC 10. Everything began smoothly. It started around 85%, give or take. I had just cleaned off a disease and was in the process of running back in after my ooze had merged. I look up where the group is and see a massive ooze heading in the direction of the boss. Uh oh. Someone’s about to eat it. Then I see Priestly angel wings and I knew our only other healer would have a few heals before she’d be out of action. Our only druid was tanking the boss so executing a battle res was out of the question. There were essentially two things we could do at this point:

Wipe the raid: Start fresh, rebuff, get everyone at full strength.
Play the stress the @#$% out of Matt game: Essentially, it’s to see how long the raid can do as is with just one healer.

So if you happened to be in Matt’s guild and you had those two as options, which one would you pick?

Naturally, the raid decides to opt for the second option.

At this point, no cooldowns had been used. Everything was still available. I hustled back into position in the middle of the raid. The Ooze Explosion indicator goes off. I swivel the camera and watch for it. But there’s still more to it than that.

Priority, priority, and priority

My thinking instantly turned from “Top off players to 100%” mode to “Keep players from reaching 0%” mode. And I guarantee you, there is a huge difference in spell usage and target selection when that happens. DPS doesn’t exactly become expendable. You still need them. You can get by with 1 DPS dead. But if 1 tank dies, it’s an instant game over. Thus the healing priority shifts slightly towards a greater emphasis on keeping tanks alive.

Analyze the raid: There are two tanks and the overall raid to worry about.

Raid frame shows that the Rotface tank (our Druid) takes approximately 7000-9000 damage a hit. She has about 59000 health. 7 goes into 59 about 8 times (roughly). In other words, she can survive 8 melee swings before it’s game over. Rotface swings at a rate of about a second and some change (1.* seconds of which I didn’t know off the top of my head and it wasn’t the time to look it up). I ballparked it at around 9 seconds without a heal.
The Ooze tank is tanking a Big Ooze that had already absorbed several smaller Oozes. I knew the Big Ooze was 1 or 2 small Oozes away from exploding. From that, I could further deduce that the Ooze tank would get 2 shot if they were within melee range of it.
Raid health was at varying levels due to Slime Sprays and some coming back in from being infected.

I threw shields on both of the tanks immediately (they weren’t at full health, but they weren’t exactly at imminent death either. I figured the shields would buy at least one or two hits). The raider with lowest health was immediately Penance’d.

All of us scattered to avoid the incoming smattering of green stuff in the middle of the room. A few players were hit but still managed to survive because they only took a blow or two. I didn’t have time to think, so I slammed the Inner Focus –> Divine Hymn macro bringing everyone back to the top before rejoining the raid in the middle of the room.

There happened to be a small pool of Ooze between me and the raid. I ran into after hitting myself with a Prayer of Mending (Note: Risky. Don’t actually run into bad things on the ground unless you know you will survive it). Every player that did not have Weakened Soul was continuously chain shielded. Somewhere in my head, I knew I felt super sluggish. I needed much more heals than what I could cast because at the rate we were going, the damage incoming to the overall raid was greater than the heals I could muster.

And then it hit me.

“We have a Shaman, moron. We usually blow Heroism at 30%. He’s at 70% right now. Just use the damn thing!”

Sure the extra speed from the Heroism would help with the damage. More importantly, it allowed the heals to go off at a much faster pace.

Anyway, I believe there were a few Paladin bubbles and Divine Guardians going on to help lower the damage. The tanks blew their cooldowns at various points to give me precious seconds to catch up. Now I had to worry about dispels. Infections were either getting progressively faster or the Ooze tank had other things to worry about. This is where you play the balance game and go back to thinking priority, priority, and priority. I could spare them a quick shield and then focus back on ensuring my tanks, myself, and other players were above 20% health or so. While the Infection would slowly kill them, it wasn’t going to be immediate. It gave them time to run out and it’d avoid any slimes that happened to be in the middle. If there happened to be two Oozes dispelled back to back, it’d morph into an Uberooze right in the middle of the raid. I didn’t even look at them to see if they were completely clear. Either I hit them with a dispel, or the tank would hit them. Either way, they were slowly piling up quicker.

“I think I made an angry poo-poo. It gonna blow!”

And this is where I made a crucial misplay. My first instinct is to run away from the center when I see the Unstable Ooze Explosion go off. I had no idea which direction the Rotface tank was running. I should have slapped our bear with a blind Pain Suppression in the event we ran to opposite sides of the room. Doing so would’ve dropped her down on my mental list of healing priorities. I know they’re not likely going to die with a defensive cooldown up (at least not as fast) and I could work on stabilizing the Ooze tank and everyone else.

Unfortunately, I didn’t think about that.

But she still lived. Maybe someone gave her a Hand of Sac or she popped a cooldown or something. But thank goodness because we actually did run to opposite sides of the room when I glanced at the map. I was out of tricks. No more Hymns, no more Pain Suppressions, but I still had a Power Infusion. I could put it on myself to keep the fast heals going or I could drop it on our Mage to speed up the fight. Out of the question though since right when I was contemplating doing that, they died (Again, proof that you shouldn’t actually think. You should simply react. Thinking leads to death, right?). I figured I may as well Power Infuse myself and started the entire process of priority, priority, and priority again. Pain Suppression had well worn off and we were all grouped in the middle again.

*BOOM*

Hear that? That’s the unmistakable shrill of Omen sounding. It means you have about 3 seconds before you’re dead. I figured it wasn’t the boss. Not a chance in hell I could’ve caught up on threat. Our tanking Paladin was still running around with another large Ooze.

… But it turned out there happened to be a second large Ooze that I didn’t see. It made short work of me. I exhaled and collapsed back into my chair before clicking on the boss. Rotface was at 3%. BOOM! Another DPS dead. BOOM! Paladin tank dead. BOOM! I saw another player fall over. Rotface is down to 1% and I knew we had it.

And people wonder why I sometimes hate two healing raids.

14 Things that can go Wrong and will go Wrong on Sindragosa

March 23, 2010March 23, 2010 by Matticus

She is the General Vezax to Yogg-Saron. Never has such an encounter led me to curl up in my chair and cry. The margin of error is so small and so minute (my-noot?). There are so many things that can cause failures. It contains of 6 minutes of sheer endurance before you get to the final phase. Anyone with a compromised computer or a laptop or a bad connection will not even do well. On other encounters, you can get away with a disconnect or a death. Here? Not so much. So here I’ve compiled the ultimate list of things that can go wrong when taking down Sindragosa.

Guild leader’s WoW crashes during ground phase (True story, happened to me last night, and miraculously didn’t get pulled in)
Raider inability to run out when Sindragosa chain pulls everyone (I specced into Body and Soul so I could hit the players who had the most difficulty)
Raider inability to mouse turn when pulled into Sindragosa and go in the wrong direction.
Raider runs out to the wrong side when pulled in and happens to be the target of a Frost Beacon in phase 3 thereby getting caught on the wrong side leading to insane stacks of Mystic Buffet resulting in a wipe.
Inability to use own judgment to spread out on the bottom of the stairs when hit with frost beacons. We don’t need 4 guys on one side. It’s 2 left, 2 right, and 1 middle.
People cheating too close to Frost Beacons before they hit resulting in more Frost Tombs.
Melee building up too many debuffs and having to run out when pulled in and not getting a heal because the healers go one way and they go the other.
Healers dying to Backlash because we’re too busy tunnel visioning the raid (I am guilty of this). Fixed it by setting Power Auras to show Instability in big flashing letters, 100% opacity, and 300% size. Manage to cut down the deaths some. It still happens.
Mystic Buffet not clearing because we mis-time our ability to run behind a block and shake off the buff.
Raiders cheating up the stairs instead of staying on the bottom as specifically instructed to before Frost Beacons are hit and then having to run back down and look for an open spot. God this pisses me off so much. I don’t know why people have to cheat up the stairs. I don’t know why waiting at the bottom of the stairs is so difficult to do.
Thunderstorms knocking out internet connections.
People who don’t have the Frost Beacon stand where people with Frost Beacons are supposed to run to resulting in a double tomb or a death on phase 3.
People who are too slow and don’t get into position in time.
Instability on half the healers leading to temporarily reduced healing on the raid, leading to more deaths due to insufficient heals. Like the Backlash problem I had earlier? It’s me getting people up to the survivability levels without realizing I have that stuff.

All I can say is, thank goodness we managed to take her down last week. It’s just unfortunate to have players who have computers or connections that just can’t seem to handle the stress of the encounter. The expansion is also winding down now even though we have Ruby Sanctum coming up and it’s getting a little harder to find raiders.

If we get her down again, I’m tempted to simply extend the lockout so we can focus exclusively on the Lich king.

Raid Leading 101: Maximizing DPS Uptime

September 14, 2012March 16, 2010 by Matticus

Normally, most bosses are kept still. There’s a cleave effect or some other ability which makes it difficult for tanks to herd them around. Every so often, a boss comes along where even though it isn’t necessary to move them, it can sometimes be extremely beneficial. In this week’s Raid Leading 101 post, I want to highlight a little trick that Conquest used during our first kill of Professor Putricide. It’s a really minor adjustment that our raid leader came up with and looking back now, I almost wish I had thought of it first. Who knew something so simple and minor would’ve helped out so much?

Initially, we had a DPS problem. We were having a difficult time burying slimes and phasing Putricide within a timely fashion. We were rocking six healers at the time. The raid was taking obscene amounts of damage and many players were struggling with avoidable damage. I myself hit a streak where I went 9 consecutive attempts being hit by Malleable Goo on the same night. That’s some serious tunnel vision going on.

If we downgraded to five, we’d solve our DPS issue but our stressed healers were going to be stressed even further. We found a way to help resolve these issues and it’s nothing to do with player substitution or gear. It was all due in part to improved movement and positioning.

In last week’s post about Placement and Direction, blogger What’s My Main Again made an excellent suggestion:

If I may make a suggestion on putricide… after the green ooze dies you waste a lot of time moving all the way to the other side of the room. Just have everyone move to the center. Ranged can dps the gas cloud as soon as it spawns and then melee can quickly switch after it targets someone. This also makes it easier to run back into the orange corner for the green ooze.

We’ve actually been doing that for a while, but I wanted to elaborate on that further and illustrate how we tackle it.

The orange ooze

We’ll use the Professor Putricide example.

When the orange ooze was active, we used to tank Putricide on the far right very close to the green wall. Our melee DPS had to run the length of the room to open up on the orange ooze when it fixated on a target. It was during these parts of the fight that we were able to close the gap on our damage. In order to do that, we made two changes.

First change: Instead of tanking him on the right, we placed Putricide closer to the middle where the pattern is. The orange ooze spawns, it locks on to a target and goes after them. If it happens to be a melee player, they still have plenty of time to hustle it and kite it around the room. Regardless, we cut the distance the melee had to travel to DPS the Ooze by half! They didn’t have to run as much. There was more DPS on the ooze meaning it died quicker which led to more DPS on the boss.

Second change: Instead of simply keeping Professor Putricide stationary, our Putricide tank was instructed to keep Putricide as close to the orange Ooze as possible. The reason? It allowed for incidental AoE attacks from melee to hit multiple targets. Chain Lightning would help. Divine Storm would help. Cleave, and the list goes on. The orange vials that the Professor drops wouldn’t be a problem since the entire melee group is constantly moving alongside the Professor and the orange Ooze anyway.

While it doesn’t seem like much, those two changes were enough to help put us over the top on our kill.

The lesson here is when working on a boss, try to set your tactics up in such a way that will cause the boss to take extra damage. Again, not every encounter will allow for this, but the possibility is there. Put those AoE strikes to maximum effect whenever it is feasible to do so.

If you’re curious, here’s a video of our first kill up:

Conquest_Professor_Putricide from Dannamoth on Vimeo.

This is from the perspective of one of our top mages. Look at how our tank gradually follows the orange ooze around. We have a set path to use when orange oozes are up that involve running toward the green wall, up to the table, then down the orange wall.

Also, excellent use of Invisibility during tear gas phases. Such cheater DPS!

If you look closely at the end of the fight, there’s about 6 or 7 players still alive. Yeah, we barely scraped by on this kill.

Last night, we managed to take down Sindragosa on 25. I want to stab my eyes out. We managed to get a video of it as well, so I’ll see if it can be placed up somewhere.