Officers' Quarters: The art of wiping
Every Monday Scott Andrews contributes Officers' Quarters, a column about the ins and outs of guild leadership.It happens to the best of us: We tried our best, and it wasn't good enough. We're no longer epic heroes bravely marching into battle but broken corpses littering the cave of some huge, slobbering monster or the fortified hideout of a powerful villain. We've all been there, and it always sucks (though it can occasionally be hilarious). As an officer and/or raid leader, what you do next can determine whether you find yourself in the same place all over again -- or standing victorious over the fallen body of your foe, sparkling with purple-ly epic awesomeness.
This week's question asks about wiping.
What is a good post-wipe process? I feel that we often just wipe and throw ourselves at an encounter -- rather than pausing and debriefing on what caused us to struggle.
-- Ciacco, Malygos, 70 human rogue
I'm not going to talk about strategy or tactics here -- I'm just going to share what I think is the best way to handle a wipe for the purposes of both morale and long-term raiding success. Here we go:
1) Don't lose your cool.
So somebody forgot to click a box. Your tank forgot to stance-dance. A healer took the wrong beam. DPS'ers shattered each other to kingdom come. Your demon-form warlock tank forgot to equip his shadow resist set. Stupid mistakes are going to happen, especially on the first try of a boss before everyone goes, "Oh yeah, I remember this now."
Flipping out and screaming at people, instantly docking them DKP, swearing, or booting people from the raid (or the guild) might have the short-term effect of getting your raid to focus better on the next try. But the long-term effect will be to make everyone more tense. Tense people will generally perform worse than relaxed, comfortable people. And also, they will hate you.
2) Give everyone a few moments to let the failure sink in.
When the last toon drops dead to the floor, don't immediately launch into a laundry list of what went wrong. Let everyone ponder their own mistakes for a minute or two. If you have experienced raiders, they probably already know what happened, particularly if they were the cause of it. Give them a short time to analyze the fight in their own heads so they can absorb it and more effectively communicate to the raid what they need to do better.
3) Talk about what (if anything) went right.
A little positive reinforcement never hurts. If the rogues did an awesome job interrupting spells or a lone, undergeared shaman kept the tank up much longer than expected, say so.
4) Let people volunteer to take credit for the wipe.
Rather than laying blame, give the person who made the mistake a chance to speak up and apologize for causing the wipe. Everyone feels a bit better when someone confesses rather than when the leaders point fingers. It's a sign of maturity and respect for your fellow raiders to tell them you screwed up. Give your members a chance to do that, even when you know for sure who was at fault. If they don't speak up, ask, "Can someone tell me what happened there?" If they still don't 'fess up, whisper them and ask them about it specifically. If they still don't admit their error, don't bring them to any more raids. Accountability and honesty are too important. But odds are they'll feel more comfortable talking about it in private. Make sure you mention to the other officers or raid leaders that they told you, so they know that person did actually come clean. Don't announce it to the raid. Rather, remind everyone of the importance of remembering to do (or not to do) whatever it is that person failed at.
5) Consult your class leaders.
Talk to your class leaders about what adjustments need to be made. This is the most important part of their job, so don't ignore them. Sometimes a small adjustment you haven't even thought of can be the key to victory.
6) Stay confident.
It may seem hopeless, but given enough gear, consumables, and practice, you will win -- even if practically by accident! Raiders key off the attitudes of their leaders. If they sense you don't believe in them, they will get discouraged. They may not try as hard that night, and they might not come back next time because they feel like they are just holding everyone else back.
7) Don't dwell.
Once you've gone over what needs to be done better next time, get people focused on that next attempt rather than harping on what just happened. I had a writing professor once who would read a sample of your work, pick out the one minor detail he didn't like, and just hammer you with it over and over again until you wanted to smack the giant thick glasses off his wrinkly bald head. Don't be that guy.
Until next week, may you wipe with grace, dignity, and confidence -- or better yet, not at all.
/salute
Send Scott your guild-related questions, conundrums, ideas, and suggestions at scott.andrews@weblogsinc.com. You may find your question the subject of next week's Officers' Quarters!
Filed under: Guilds, Raiding, Officers' Quarters (Guild Leadership)






Reader Comments (Page 1 of 1)
Vylemacer Sep 17th 2007 1:21PM
Here is wipe that happened to our guild. I am main tank for Kara (a prot Paladin at that) and we ended up getting the Oz opera event. Because I was tank, I was to kite Tinman around while everyone else did their specific duty. Well... (here is the embarassing part) I didnt bother looking at the names of each of the bosses and automatically assumed that the big harvest-reaver-looking mob was Tinman (who was actually Scarecrow; remember the mechanical reavers in Westfall?). So as the fight begins, Tinman starts whailing and one-shotting everyone while I'm at Scarecrow just whacking away. We had a good laugh, but very embarassing.
Shawn Sep 17th 2007 1:21PM
Even if you aren't to blame, sometimes it is good to be modest and shoulder some of it.
"Sorry, I should've grabbed aggro on X a little faster."
"My bad, I just couldn't get Y healed quick enough."
Good players/leaders will know it wasn't your fault and appreciate you setting the mood where it is OK to admit mistakes.
Oblivion Sep 17th 2007 1:27PM
We have several raid leaders and they are all very encouraging. During the corpse running or the resurrecting after a wipe, they always goes over what went well and what we need to do better. They will iterate certain key strategical aspects of the encounter and get everyone on the same page. Furthermore, they are always open to suggestions from others in the raid (usually class leaders or other officers) about ways to tweak our approach. Raiding for us is usually a casual, successful experience with minimal frustrations--though, there are times when things just don't go well.
The biggest problem our guild has is wasting time between wipes. There are always people that look at a wipe as a time to go AFK. Getting people to stay focused, run back, and rebuff is, sadly, a huge challenge for some reason. I've never understood why it's so hard to run back, eat, drink, throw up a soul well and rebuff. It boggles my mind.
FireStar Sep 18th 2007 3:34PM
#5 is very important for morale. It's also bad in pugs where its obvious someone calls a wipe and when they get pointed out (for the purpose of learning so they dont do it again) they deny it (even though by the logs is obvious). that puts a huge damper on the group.
Sylythn Sep 17th 2007 1:32PM
Thank you so much for choosing that image over several other types of wiping I could imagine.
Jessica Sep 17th 2007 1:49PM
A little gallows humor never hurts, especially if you're on your 5th+ wipe.
Salty Sep 17th 2007 2:20PM
I've been in a lot of scenarios where a wipe turns into 30 minutes of waiting around for one person. This is the most annoying thing in this damn game, period. In this game, 30 minutes is 30 minutes into a respawn timer, 30g worth of farming, 30 minutes with your kids/wife/friends/chores, 30 minutes closer to having to be at work/school/other functions, 30 minutes before your upcoming scheduled run to get in the mindset, research the bosses, get pots/elixirs/bullets/repairs, get there on time, etc.
In Kara or any 25-man raid, here are some "best practices" for wiping:
1) Get everybody back in the instance and in position ASAP. Once your ass is planted at the buff spot and if you have a large number of people not zoned in or taking their time running back, go ahead and get your beverage. But don't do long things like smoke a cig, make a sandwich, talk to your aunt or anything like that. If you do, type /afk so people see you're gone and don't assume you’re there and ready just because you have buffs and full mana. Don't forget to move around and say something in raid/vent to let people know you're back. It's just dumb waiting around for somebody for 5 minutes just to find out they were there and ready and waiting for it to start, or have someone go afk away from the party and postpone buffing.
2) WAIT until everyone is back and ready before rebuffing... but go ahead and roll out some soulwells, res pets, drink AND eat up, etc. The worst is when pallies start buffing right when they get back. For fights that can be ~10 minutes, the worst is when it's time to pull and someone says "9 minutes left on Salv/Kings/Might" and then you have to re-buff and drink up again. Don’t hold up the pull for a little extra mana, just start drinking inside the “door” if it shuts behind you and then start when you’re ready.
3) Coordinate and rotate the usage of soulstones, battle resses, divine interventions, feign/vanish+cables, ankh, etc. Making sure there is a way to avoid a FULL wipe (everyone dies, everyone runs back, nobody left to res, etc) can shave a lot of time on deaths. This is especially important when you've gone over the respawn timer and you're now "behind enemy lines." A wipe without a contingency plan usually results in calling the run, as re-clearing trash is not always an option that long into the run. Repair bots and stocking up on soul shards for summoning people post-repops helps in the latter scenario.
4) Our raid leader uses a 2 minutes buff timer, which he sets off after we discuss what went wrong, how we could improve. The pep talk can be "Okay guys that was great, bad luck or one person fix this or that... same thing" or it can be "Okay, we've got to switch tanking and healing assignments, work out a kick/counterspell/earthshock rotation, move raid members around for the best use of party buffs, configure an addon/announces, etc. It can be 5 minutes or 15 minutes before we start the fight, and buffing is the last thing to do before the fight.
5) EVERYBODY should do their part to learn from whatever mistake took place. Whether it was your mistake or another's that you noticed... it's your obligation to offer advice and your perspective on the issue - without an accusative tone or drama (another HUGE source of delays). "Silent Wipes" are not progressive and if that starts to happen... it's typically just a stacking repair bill. You have to learn or you don't get better and communication is vital. This means looking back in your combat log to see what happened. Was it bad luck? Consecutive crushing blows or a “Heal Hole” maybe? Don’t waste time changing your strategy, if you look in your logs it can explain a lot – re-try that strategy with the quickness if it was just poor luck.
To extend this point to an extreme… if you’re undergoing a learning experience or having evasive problems you just can’t pinpoint, combat logging is highly advisable. There are lots of stats analyzers out there for your own system that can summarize dmg/healing/deaths, etc, and there are even some that can post your log online to be viewed by all attendees. Have people analyze themselves, dig a little and see who is performing poorly or what keeps killing people. This can also help people analyze their builds/gear from one week to the next and even add a little “edge” by forcing people to be competitive in one aspect or another.
Slayblaze Sep 17th 2007 3:11PM
@6 Excellent advice Salty -thank you for that. Even though my guild is pretty good at wipe recovery, I just had to copy/paste your reply onto the guild website, as it really sums up how recovery should be handled.
Great advice from Scott too...you hit it spot on!
Samus Sep 17th 2007 4:11PM
My advice: /roll for blame.
It's funny, but I'm not joking. In a situation where people are upset at each other for things not going how they'd hoped, this will really lighten things up. Players who are upset and thinking about what other people should be doing are not focusing on what they should be doing, and you're more likely to get mistakes.
Just have everyone /roll, and whoever rolls lowest gets a joking round of "how could you!?" and "way to go, noob! :)" It never fails to entertain, and it gives people something to do while the raid is reassembling rather than casting blame at one another.
Thingy Sep 17th 2007 5:00PM
Hear hear. There's many encounters that go down to pure luck, some just need a miss-click or standing in slightly the wrong spot. I'm a big fan of people talking about both good and bad encounters, giving their experiences and yes, admitting when they fucked up. I've done it myself more than enough times and admitted to it. State clearly what caused the problem and how you know it can be rectified and people seem to be ok as it shows you've learned.
The worst thing for me in a wipe is when I don't actually know what went wrong, I can't see anything being done incorrectly and there's always room to learn.
BenMS Sep 18th 2007 4:50AM
We spent last week working on the Prince Malchezaar fight in Kara, having one-shotted the Curator and Shade the week before - we were really on a high. Our Main Tank, while well-geared, simply didn't have the avoidance to deal with the thrash chance during Phase 2 of the Prince - we wiped a good 5 or six times after clearing to him, and ended up calling it, having takend down zero bosses in a night for the first time in a long time. Our MT posted what was pretty much an apology on the guild forum - he realised that as 2IC of the guild and Raid Leader, he was putting his warrior up as main tank when we had better tanks waiting in the wings. The next night, we switched out his warrior for his 'lock, and switched out another 'lock who couldn't make it for another tank, and got him down 2nd try. Taking responsibility for it, and owning his mistake facilitated the rest of the guild having a major morale boost. Now all we have left are the dragons!