Ready Check: On wipes and wiping

Ready Check is a weekly column focusing on successful raiding for the serious raider. Hardcore or casual, ZA or Sunwell Plateau, everyone can get in on the action and down some bosses. It's not easy, though...
Let's take a look at the problems and challenges arising from wipe nights, or even a failed try or two at something on farm.
Mood and Morale
Regardless of why you're wiping, constantly throwing yourself at a seemingly undefeatable boss can make your entire raid force, even those leading it, dejected and unmotivated. It's even more frustrating to be really close to killing something and then wipe to a series of mistakes, or fail to kill a farm boss that you should be overthrowing with ease. All of this is entirely normal and part of raiding, and good raiders have the discipline to keep going through these periods until you make a breakthrough and finally kill it.
How do you deal with an extended period like this? Whether it's hours or days, there are probably steps you can take to help with the mood of the raid and your morale. For example, it obviously depends on your guild's attitude to raiding, but light-hearted jokes and funny music clips (the Benny Hill corpse-run theme) can stop things becoming too depressing, although be really careful with this -- some people don't appreciate it. Officers don't see everything, so if someone is playing particularly well then you can help point this out rather than focusing entirely on the raid's mistakes.
Bear in mind other people's feelings and performance. Some raiders get nervous and perform worse if they're under more scrutiny. If someone does badly at a particular job, instead of hurling abuse at them from the get-go and calling them all kinds of names, let the officers deal with them and tell the officers in private if you see that person repeating their mistake. Of course, your guild culture might be different; if you're used to freely insulting each other for minor slip-ups then all's well, and everyone takes it in good humour. Generally, though, lowering the mood doesn't really help.
If you're running into the same troubles over hours or days, there are other things you might be able to do to help, such as suggesting improvements or fixing problems with your own play. This is all dependent on why you're wiping, though.

Why you wipe and how to fix it
There are a few key reasons behind wipes, and any connoisseur will recognise them all.
Attack of the Stupid. Someone did something extremely idiotic (such as auto-ran into the boss) and you all fell over as a result.
Minor Mistakes. One person, or multiple people, make small mistakes. Cast a spell a little too late, pulled aggro, didn't run away fast enough. One or more people die and it cascades into a wipe.
Healing problems. Something's not quite right with the healing setup and tanks (usually) fall over, shortly followed by the DPS.
Tanking problems. Mob in the wrong place? Adds not picked up? Wearing the wrong gear? Sometimes the tanks are at fault, other times they simply get blamed.
DPS problems. Hit an enrage timer with everyone alive? Most of your DPS failing to pay attention and dead?
Strategy problems. Perhaps what you're doing simply won't work, and you need to take a break and rethink.
Being unprepared. Not having the right resistance gear, a good raid setup or even running out of potions or flasks. Not understanding the boss fights or knowing what to do. This could be the raid as a whole, or simply individual mistakes that can be corrected with a bit of preparation.
Of course, just when you think you've seen every type of wipe possible, one will come along that doesn't fit into the above categories. Feel free to share your stories in the comments below!

So, how do people fix wipes? Using combat logs, or addons such as Grim Reaper can help you analyse exactly why people died, and staying on the ball to watch what happens to the raid during the fight itself is paramount. It's quite difficult keeping track of everything that's going on as a raid leader, especially if (say) you're trying to tank at the same time, so having officers that you know will help with feedback and getting help from members is useful too. However, try not to point fingers too much. Sometimes everyone knows who screwed up and it doesn't need to be re-stated ten times; just pick yourselves up and move on, if you're confident that it won't happen again.
Adding encounter-specific buffs and debuffs to Grid helps, as does asking people what happened to them and checking that they know how to avoid repeating it. However, don't look too clueless! If the raid leader is asking "so.. why did we wipe?" it doesn't instil confidence in the rest of the raid. Even if you don't know because your position in the raid couldn't observe what happened, ask the other officers who might have an idea.
It's important to listen to your raiders, but it can also be extremely irritating if twenty people have the next bright idea that you've already discarded or that misses a fundamental problem with what you're doing. One way to deflect suggestions that aren't critical to the raid's current exact strategy is to ask people to post them on the guild's forums, or discuss it after the raid. It helps to make people realise they're being listened to, and keeps morale up. Sometimes, suggestions are simple and relevant, and one small change can make a big difference -- it's amazing how people react to a tiny change after hours of wiping on the same thing.
If strategy or preparation are your problem, sometimes wiping on the same thing for the rest of the night isn't going to help unless you make on-the-fly strategy changes. At times like this, sometimes you have to call the raid, which inevitably leads to people feeling disappointed and let down. From their point of view, they were playing perfectly and doing everything they could -- why stop? Point out in clear terms why you are stopping the raid and start a discussion in guild, on voice or on the forums to make sure it doesn't happen again.

Trying again
The first time you wipe, your raid reforms, rebuffs and thinks to itself "okay, this is it". The second time, it thinks "maybe this time!". By the fourteenth, it's thinking "when can I go to sleep?". Communicating what's changed from pull to pull can help keep people alert, as can breaks and distractions such as a trash clear. If you wiped to something stupid, that can surprisingly wake people up a little, though it can also simply annoy them (repairs don't pay themselves). Remind people of better pulls to beat, and try to assess the mood of the raid.
Your guild might be familiar with "famous last tries". For some reason, when it's the last pull of the night and everyone can go home afterwards, suddenly people remember how to play. Phases are executed flawlessly, DPS is on track and everything clicks. It might be your best try of the night, or it might even be that fantastic first kill -- but don't underestimate the power of the raid's mood as it suddenly lightens when you utter the words "famous last pull".

What changed?
When you finally get that kill, take a few minutes to think about what made the difference between the kill and all the wipes preceding it. Was it a minor change that had far-reaching effects? Was the RNG in your favour? Perhaps people just stopped sucking and finally played their roles perfectly. Give credit where credit's due, to the person who suggested the change, to the player pulling off a timely combat rez, to the tank that picked up an add when another tank died. Most importantly, remember what you did for next time!
Filed under: How-tos, Raiding, Ready Check (Raiding)






Reader Comments (Page 1 of 1)
Vepa May 24th 2008 7:24PM
A fairly decent read, even for someone that doesn't raid anymore like myself.
I gave it up after awhile because my guild would rather try to "even out" gear amongst all the members, where I've noticed all the high-end raiders stick to one group. It's sad that we practically have Karazhan on farm, but the group still wipes and has some weeks that just don't work.
And nobody is geared enough to hit anything outside of KZ, so it's just a single group from the entire guild with like, the same 3 rotating tanks, and 3-4 rotating healers.
I guess what I'm getting to, is group composition plays an important part of raiding. Get comfortable with the people you're playing with and try not to swap raid members because it means have to re-strategize as well as re-teach the fights.
Damiya May 24th 2008 8:01PM
We wiped right after Gorefiend died one night. Yeah, after. We had a good 20 people alive, Gorefiend took his little nap on the floor, and all of a sudden... constructs popped while we were all congratulating each other on our first Gorefiend one-shot (previous raids we spent a few tries on him.) The person who had the debuff was afk and the constructs proceeded to trash us and then stand on top of us for a good long while before they despawned. Good times.
Sirg May 25th 2008 4:09AM
Constant wiping turn this game's fun experience into something much different than you expected when you started wow.
Raiding can be fun when you have a good team, and by this I mean good people, not only good raiders, but on the other side is quite time consuming and it hardly pays off. Some classes get that burnout feeling and quit faster than others.
John Woodard May 25th 2008 7:52AM
Other reasons for wiping:
Lag
Chrissie May 26th 2008 4:42AM
Ahh yes, wiping. Something comfortably familiar to the topic of this article that gave me a nice warm fuzzy feeling.
It's something I've long observed about my guild that while we aren't bad (like our entire server, we're way behind on progression, but we do meet the progression goals we aim for- first pull in a t5 instance last September to 4/5 Hyjal and 7/9 BT now [and Kael down before the attunement nerf] isn't all bad I'd say)- but we play so, so terrible some nights.
It's amazing. The day we first downed Mother Shahraz, our raid leader decided to make a few ill-fated attempts on Council, then go to Hyjal afterwards and kill some quick bosses (even though official raid end was well past). We wiped twice on Anetheron before we decided to leave well enough alone. How the heck do you down Shahraz and wipe on Anetheron?
and similar examples are to be found all throughout our raiding "career", such as wiping on Lurker when we'D already downed Vashj. Or spending a full 2 hours on Gurtogg when we 2-shot him the previous week.
That's the kind of wiping that's frustrating and demoralizing. Everyone expects to wipe, a lot, when you walk up to a new boss (with the exception of Rage Lootchill keke). Wipes that seem unnecessary drive people up the wall.
I only partially agree with the "famous last pull". Sometimes this works, but in my experience, a lot of the time people are just burned out, tired, and no longer focused, and even a "last attempt" comes to a swift end because of an "Attack of the Stupid"- and the next day, you walk up and 1-shot the boss. (This is what happened to us with Shahraz- we had wiped at 1% and thus kept going about 2 hours past our regular raid time trying to force the kill to no avail- then finally gave up. The next day, we did the first 2 attempts without a shadow protection cauldron just to get back into things, and bam! downed her on the 2nd.)
On farm bosses, the problem tends to be either a) people underestimating the "easy farm boss" and not paying enough attention or b) a big change in group composition since that boss was a progression boss. We for example have been having a lot of healer turnover, and that hurts- especially on, say, Gurtogg.
Trying to distill some sort of insight from this ramble, I guess what I can say is
- Preparation should be a given. Wiping because people haven't done their reading and watched their videos, or forgot their consumables, is irritating and hurts both morale and group cohesion. Plus the people who did do their homework will feel cheated and possibly not do it next time, either, leading to a cascade of suckage.
- Don't underestimate farm bosses. You might not need full consumables, but do pay full attention. Make sure any new people for whom the boss isn't a farmed bore yet know what's going on.
- Don't try to force things. Calling a raid with a boss at 1% may be preferable to wiping on it for another hour.
- Don't run from volcanoes/death and decay/infernals/fatal attraction in tree form >.>
ghusnak May 26th 2008 4:03AM
we wiped numerously times on Mother Shiizle Dizzle... with 9 healers...and we ended the raid even though we've slain her lots of times b4.
one day after we one shot her and council with 7 healers and 23 ppl. mood & morale...
Destra May 26th 2008 4:32AM
"However, don't look too clueless! If the raid leader is asking "so.. why did we wipe?" it doesn't instil confidence in the rest of the raid. Even if you don't know because your position in the raid couldn't observe what happened, ask the other officers who might have an idea."
It's interesting you should say this... I find it preferable to discuss it with the entire raid, and see what input people have. Sometimes they notice something none of the officers see, and it's also much better for morale than the officers going silent before announcing "It's ______'s fault."
Silverrealm May 27th 2008 11:17AM
I do this in every instance I have run regardless if I am leading it.
Then when people advise what happened I try to contribute with anything I saw.... and offer what I personally would have done differently. No one is perfect, even if you think you didn't make a big mistake, some times minor mistakes all around the group are enough to wipe it.