29 August 2009 - 8:50How to: Lead your PUG to success, Part II
Part I of the series is here. Part II of the series will deal with how to lead the raid during the actual raiding phase.
To begin with, you need to make sure that you have authority over the raid and that you will be listened to. It’s important that your raiders don’t go running around and ignoring your commands. This might sound like an ego-trip on the part of the raid leader – but there is a fine line between ego-tripping and asserting your authority. There’s nothing worse than deciding on a strat on a boss, trying to implement it, then some other guy deciding to follow his own strategy anyway, and that needs to be prevented.
Yes, leading a large PUG is very reminiscent of herding cats, why do you ask?
The easiest way of asserting your authority is commanding respect. Let your raid follow you not out of threat of a raid removal, but because they have respect for you.
To help with this, always speak in correct English, with proper grammar, punctuation, and capitalisation. Stay calm and collected, don’t spew obscenities or use all caps. People are a lot likely to listen to you when you sound like you’re someone worth listening to. Don’t abuse /rw, in fact don’t use it at all if the information you’re conveying is not crucial. Most players start ignoring raid chat altogether if /rw is being overused.
You need your assistants to be listened to, too, since they’ll also be leading when you’re for one reason or another busy. The raid also needs to be respecting them. Don’t contradict them publicly, don’t have a disagreement with one of them in raid chat. If you want to sort something out, sort it out in whispers or a chat channel. Let the leadership present a unified front.
Loot is a very big part of any raid, and there is nothing that puts a damper in a good PUG quite like masterlooting issues. Make your loot rules crystal clear, before the run starts. There needs to be absolutely no mistake on that, make sure everyone has understood them.
A set of loot rules I like to use, that has worked for me so far is:
Every item is open for regular rolls, highest wins. Mainspec before offspec. Armor class priority – as in, if a cloth wearer and leather wearer covet the same cloth item, the clothie has priority on the item. Otherwise, use of common sense is required, otherwise the leadership may interfere. (As in, if a hunter and a rogue both roll on Sinister Revenge, we may well tell the hunter to fuck off.) If someone wins too many items, too many meaning > 5, again, the leadership reserves the right to interfere. BOE items may be won on mainspec rolls, but the winner is required to equip it right away and be inspected. BOE items may not be won on offspec rolls, they will be raidrolled if no one wants them for their mainspec. If no one wants a piece of loot, it goes to a designated disenchanter.
Note that in these set of rules, you have to define what mainspec is. We define it as “the spec you have been in for the majority of the raid”. Letting people define their own mainspecs, especially with the dual spec system, is way too complex. And again, you can’t trust them to not abuse the system.
As for offspec rolling. I try not to permit offspec rolling as it’s not fair to other people – offspec rolling in this context meaning that someone forfeits the right to roll on anything for their mainspec, but gains the right to roll on offspec loot as if it was their mainspec. This can go pretty badly if everyone decides that they want to roll offspec, it’s again open to exploitation, it’s overcomplex, and more often than not leads to drama. If I have to, though, I’ll let one or two people roll offspec, with the agreement of other people who are interested in the same loot.
If someone will be rolling offspec, make sure everyone in the raid is made aware of that fact so as to prevent potential drama.
Reserving loot also tends to lead to drama. I’ll never do it, out of principle, because I feel it’s very unfair. I suggest that all PUG leaders avoid it.
If you’re the raid leader – don’t masterloot. Just don’t. You have more important things to be doing, so resist the temptation and pass it off to an assistant you have confidence in to do it right.
Your assistant will need to know very well who’s rolling on what, for what spec. Make no mistake, people will try to cheat others out of loot, and that needs to be nipped in the bud. There will be people who will try to roll multiple times, hoping their duplicate rolls are hidden among other rolls. There will be people rolling on offspec items, hoping the masterlooter isn’t paying enough attention and will give them the item.
If there is no one else you trust to do it right, do it yourself, but this will quite likely slow down the raid.
From the first pull onwards, the raid leader has a very important role: Assessing your group. I’ve mentioned in part I of my guide that no matter how many achievements and epics someone has, they might make mistakes, or just have areas they are weak at. It’s your responsibility as the raid leader to find those weak spots and patch them up, or otherwise compensate for them.
This endeavor has tiers. First off, you’d like to weed out the people who are clearly underperforming. If someone’s damage done is below the tanks’ on Patchwerk, that person has to go, unless they had a good reason why they did badly.
In fact, as a side note, everytime I start a Naxx PUG, I do Patchwerk first, since it’s a pretty good indication of your DPS, healing, threat, and general survival capability. If you wipe on Patchwerk, the reason is generally pretty obvious, and the people who caused it can easily be spotted.
This is also part of the mistake compensation that I’ve mentioned. Sometimes, a player is not bad enough to warrant removal from the raid – they are just weak at one thing or the other.
Some people who are otherwise good inexplicably fail at certain fights. You might have a really great DPSer who’s bad at kiting. Your amazing single-target tank might be bad at add pickup. Your holy priest might be great, just don’t ask her to juggle her cooldowns with the tank’s. Until I got a new computer, I was incapable of tanking Heigan because I had about 5 FPS maximum during the entire fight. My amazing co-raidleader’s computer always froze whenever he got a void zone underneath him on KT, which resulted in him eating dirt for the majority of the fight. A good raid leader keeps an eye on these things and moves people around as needed.
Part of mistake compensation is putting people on roles they’re familiar with, unless you’re confident they’re capable of learning quickly. If a tank has never done tunnel on Thorim, off into arena he goes, even if his specific class would have functioned better in the tunnel.
Speaking of learning, as the raid leader, there will inevitably be times where you’ll have to teach people a fight. Handling these times well will make the difference between success and failure. Remember that in a PUG, you cannot afford to fail repeatedly, as you will, more than likely, lose people doing so – as a result, helping people learn the fight quickly with the minimum amount of attempts is important.
Keep the explanation simple. I cannot stress this enough. As simple as you possibly can make it. The less they have to keep in mind, the better.
Don’t use ability names if you can help it – “big spell with 8 second cast time” is easier for a lot of people to remember than “Flash Freeze”. Obviously though if it’s a well known spell, like Blizzard, Rain of Fire, void zone, etc, go for it.
Try to draw parallels between fights that your raid is likely to already know, and the one you’re working on. When I’m introducing a bunch of oldschool raiders to Mimiron, telling them that Spinning Up/Laser Barrage is the same as C’thun’s Dark Glare is a lot simpler than explaining the ability. They’ll know exactly how to avoid it, and feel a lot more confident in their ability to do so.
Don’t explain to people anything they don’t have to know. Your DPSers don’t have to know about Thorim’s tank switch requirement, only your tanks and healers do. To explain it to the DPS is just overcomplicating things.
As an example, here is how I explained the Twin Valkyrs fight to a DPSer who was new to it.
“Okay, we’ll split into two groups. You’ll either be DPSing the light twin, white, or the dark twin, black.
“In the beginning of the fight, touch the portal that is the opposite color to your twin for a debuff. This debuff is called your essence, and it’s a DPS boost.
“There will be little orbs floating around during the fight. Run into the orbs that are the same color as your essence. That’s also a DPS boost and it prevents the bosses from getting stronger.
“If your twin is casting the long Vortex spell, you immediately have to run to a portal and take on the same color essence as the twin. Otherwise you will die.
“Once in a while any of them will shield up and start casting a big spell. It’s the same deal as Kael in MGT – break down the shield and interrupt the spell, except the end result of the spell is a heal instead of Pyro. If it’s not your twin that is casting it, you should change essences, go to the other twin, and help DPS and interrupt.
“So to sum up: Have the opposite color as your DPS target, absorb the same color orbs as yourself, have the same color as the twin that’s casting Vortex, help burst down shields and interrupt. DPS target = opposite color, orbs = same color, Vortex = same color. ”
You can see how the explanation is getting progressively shorter as I go on. First a rundown of the fight, then a simpler summary, and yet another even simpler one. The repetition also helps reinforce the basic concepts of the fight. Also note how I’ve omitted the damage spike ability on tanks, as it has nothing to do with a DPSer.
Keep up the pace! Efficiency and speed are key to a happy group. Encourage tanks to pull for as long as healer mana looks okay. Don’t waste time on looting – as soon as a boss dies, resses need to immediately go out, rebuffs done, and trash should be pulled. The master looter stays behind to link items and take the rolls. 15 seconds after the roll command goes out, close the rolls, there’s really no reason to wait longer. If someone hasn’t done their homework on loot, that’s their problem, not yours.
Speed up wipe recovery, encourage people to heal and buff on the run. After a wipe, remember that it’s faster if everyone releases and runs. If someone dies, there’s no need for the entire raidgroup to sit and wait around. Go pull the next group (but yeah, don’t put your resser in combat).
Set master looter threshold to Epic, anything less can be individually looted with no penalty.
Ask your raid to cut down on AFK breaks. If anyone needs to go AFK, they should do so between bosses and be back before the next boss, or wait until you announce a break. Here is where that authority and respect comes in handy!
This is it for Part II of the series. Part III will deal with common problems that arise in a PUG, and how to solve them most efficiently.
1 Comment | Tags: ugh it's a pug, useful posts