Penance Priest

Discipline Priest Blog

Showing posts with label pugs. Show all posts
Showing posts with label pugs. Show all posts

It's not your fault. You're not the original sinner. Your motives were pure, of that I'm convinced. But times have changed, and your services are no longer providing the benefits to the community that they once were. In fact, quite the opposite.

So I will have to put you on notice. You have one month to clear out.

Your only other option is to help us clean up this god-awful mess. The mess begins and ends with:

“LFM Ulduar10, 2300 required…”

Am I geared enough to ...

Stop. Stop right there. Look carefully at this simple question, so innocuous, so common, so flawed. Let's turn it inside out: “If I have X gear, then I will be able to down Y boss.” It sounds weird when you put it that way. We all know that gear does not kill bosses, people kill bosses. But answering the question “yes you have enough gear to down X boss” is feeding that very wrong idea.

Gear does not kill bosses. People kill bosses.

How much spell power do I need to ...

You're not listening.

How much mana ...

No. Not answering.

What gear score do I need to …

Wow-heroes, pack it up.

The Gevlon Experiment

If you haven't already heard about Gevlon's experiment, go read it now. A few months ago, he and his merry band of misfits re-geared themselves in heroic blues and cleared Ulduar. It wasn't pretty, but they did it. Full clear.

Be honest: the first time you heard that – perhaps it was now – didn't it shock you? Impress you? And make you question your own obsession with gear as a ticket to higher-level content?

I'm a fan of Gravity's response to the matter, in which he created a graph to illustrate the wide range of gear requirements for each raid. Because we all know that gear is not totally irrelevant. Just less relevant than many people think.

I know you know that gear isn’t enough

But if I hear one more person asking if they have enough spell power or mana or crit or haste in order to do this or that raid…

/shakes fist
/screams
/pummels people who actually try to answer the question earnestly
/quits trying to bring sanity to this crazy crazy world

Scratch that last one. I’m in it for the long haul.

A few weeks ago in Nax25, Serene Echoes dropped off Heigan. It’s the sort of thing that turns an intelligent player into a drooling puddle of desire. Gimmegimmegimme. It also is arguably best in slot for a disc priest, especially if you’re not after the hasty boots that drop off Maly25.

One of the three GMs of the guild I was in, Qban, was running the raid. He invited all casters to roll, and in fact, I think every clothy was drooling about as much as I was. I protested rather loudly. As much as a warlock might enjoy all that crit, the mp5 is wasted itemization (wtb Lifetap), the same way +hit would be wasted on a healer. As far as I’m concerned, those are for healing priests and healing priests only. (They’re really itemized for disc, but I would have few qualms rolling against a holy for those boots. However, I might ever so gently point them to Forlorn Wishes that drop off Razuvious…far better for a holy priest.)

Qban was in his “let’s get this shit done” mode, which means any discussion was seen as stalling. Roll roll roll, and as luck would have it, Qban won the boots. (He’s a mage.) Grats.

Ten minutes later, Lof, one of the other GMs, got online. He saw me ranting in guild chat about the insanity of what just happened. He looked at the boots, did 10 seconds of research, then started yelling at Qban for taking them. Turns out the Wyrmrest boots Qban was wearing are far better for a mage than the Heigan boots. Qban withdrew into himself, and didn’t utter a single word for the next hour (which is kind of lame for a raid leader).

All three GMs quit WoW a couple of days later, so there wasn’t a chance to rectify the policy before the guild dissolved. Qban vendored the boots after the raid though. Truly a shame.

And lest you think this is just my outlet for QQing about loot that I should have gotten if justice had prevailed, it ain’t so. Another heal-priest outrolled me anyway. I’m more interested — much more interested — in loot policy than I am in loot.

Individual vs group perspective

Qban was a very good player, creative, alert, knowledgeable. So what went wrong? Well that’s easy: the loot policy was too soft and undefined, and relied on a priority scheme that works for individuals, not groups.

The existing loot policy was simple: roll if the item is an upgrade for your main spec. Armor class was taken into account, so holy pallies weren’t rolling on the cloth healing boots. This type of policy is probably the most common I’ve seen in raids that don’t use a “harder” system like DKP. It works for guild runs as wells as pugs.

In a system like this, it is left to the individual to recognize a main-spec upgrade. And how do individuals make that call? Most likely, they use a ranking site.

There are all sorts of loot ranking sites that people use to create wish lists (Maxdps, Wowhead, Lootrank, etc). And of course, many experts have created customized wish lists for us (Dwarfpriest, Matticus, Shadowpriest.com). The very significant problem is that every one of these sites looks at loot from the perspective of the individual, not the raid. Serene Echoes might show up very high on a warlock’s wish list in Lootrank. And with a soft system that allows the individual to determine their own loot upgrades, that warlock will surely roll. (Grr.) However, it’s the raid leader’s job to take the perspective of the raid, not the individual.

The real problem, as you can see, is that any item that qualifies as best-in-slot for one class will surely be an upgrade for other classes. Naturally, this doesn’t apply only to the absolute best gear, but any item. So we need a raid-oriented policy that takes into account the needs of the individual. Sounds complicated, but it’s actually not.

Defining a policy

There are three ways we can arrive at a solid policy here. One is easy, the other is nearly impossible, and one is riddled with problems.

The easy way is to rely on an outside authority to determine what spec each piece of gear is designed for. That way when something drops, the raid is not in danger of the sort of thing that happened to our group.  Consult the “oracle” to determine who is eligible to roll on an item for their main spec, and if no one of that class/spec is in the raid (or wants the item), check to see what class can roll for offspec.

This frees the raid leader from having to be an expert on all the subtleties of class design. Is that a rogue item, hunter item, or enhancement shammy? Damn…all I know is that they like sharp sticks. But between the different stats and weapon speeds, forget about it. I could always ask the resident sharp-stick-users, but what if there were any disagreement? Who should resolve it, and how? We’d be back in deep water.

If we had an outside authority, it would minimize arguments in the moment. Any challenges would have to be taken up either before or after the raid. Because the raid leader is not making the call, the outside oracle is, so the challenge would be: “we should not be using that oracle!”

The second way to get a solid foolproof policy is to rely on all the individuals in the raid to have two qualities: first, to be high-level authorities on their classes, and second, to place the best interests of the group above their own. So everyone in raid would have to be an unassailable expert on their class, and they would be able to look at any item and determine if it was itemized for their spec. They would know if an item isn’t a bulls-eye (even if it’s an upgrade), and they would have the integrity and courage to pass to the person for whom it is a bulls-eye. They would probably also need to be knowledgeable on all classes and specs in order to know who the bulls-eye actually hits for any given piece of loot. In theory raid members could pool knowledge and discuss (rationally!) when an item dropped.

See why one is easy and one is nearly impossible? I thought so. I don’t mean to imply that it can’t happen ever. I’ve seen it happen, and it’s beautiful and exciting to participate in. But to rely on it as a policy? Are you serious?

In an excellent guild, you could certainly have some amount of those qualities: deep class knowledge, or team-oriented play. However, even in the best of all worlds, having both qualities firmly in place just does not happen. And to be honest, that’s not a problem: all we need is a little structure to hold it together.

The third way is to use a loot council. A loot council is excellent for answering the question “who deserves this gear most?” based on whatever factors you want to include. Typically a loot council would weigh things like: raid attendance, performance, the level of gear being replaced, overall benefit to the raid, etc. It is certainly a group-oriented loot policy, but addresses issues I don’t feel should be addressed during loot rolls. If someone is not participating in enough raids to further the guild’s progress, that should be addressed offline, not in the form of loot lockout. You are also relying on the integrity of the loot council, which is where power lies, and therefore where corruption is seeded. It could work, potentially, but is delicate beyond belief. Again, I’ve seen it in action when it’s working well, but as a policy, we’re in a danger zone.

Enter the Oracle

The Oracle’s name is Kaliban. All rise for the Great Kaliban!

Kaliban’s loot tables have been around since classic raids. They have been used by raid leaders for years. His page explaining the rationale behind his choices is extremely thorough. In other words, he is a well-respected authority.

Each item is ranked into three tiers: first rollers, second rollers, and third rollers. In some cases, the breakdown is simply by armor class. So Belt of False Dignity, for example, is offered first to clothies (mages, locks, and all priest specs), second to leather casters, and third to mail casters. Ruthlessness, as a more typical example, is rated based on which class/spec is most appropriate for those particular stats.

So now, when an item drops, all the raid leader needs to do is look it up on Kaliban and invite the primary classes to roll. A resto druid might have the Belt of False Dignity on their list of potential upgrades, but first roll goes to clothies. A prot warrior might see Ruthlessness as an upgrade, but first roll goes to other specs.

And as I mentioned above, if anyone has issues with Kaliban’s recommendations, the raid leader should say that the Oracle’s authority is final for now, and if it needs to be discussed whether or not we use Kaliban in the future, that can be addressed in a guild meeting.

The Oracle is INSIDE YOUR WOW

That’s right. There is a plugin that embeds all of the information on Kaliban’s site right into your game. So a raid leader doesn’t even need to leave their window to get Kaliban’s loot list. The addon is called ClassLoot.

As far as I’m concerned, it is an absolute must-have for any raid leader. I mean that. Absolute.

Here is how the item card looks for my beloved boots. Kaliban has not yet drawn any distinction between holy and discipline priests. Perhaps someday, but even without it, it’s a tremendous improvement over the “soft” systems most raid leaders use.

I currently know of no other authority that compares or competes with Kaliban. If you know of any, I’d love to hear!
 

In which he digressed radically from the stated mission of priesting, and veered into the more interesting territory of leadership and integrity.

Ah, the craziness that is raid leadership. There is too much to say to capture it all in one post. Or one blog, devoted entirely to raiding. Or one blogosphere.

Failure #1: “We don’t take pugs”

I spent several months in a casual guild. More accurately, “a casual guild that raids.” Ok, so failure is built right in, but let’s ignore that for now.

One time in TK we had to pug a healer. Twenty four guildies, one pug. It seemed that folks kind of knew him, so he wasn’t a complete stranger. Loot reaver drops T5 shoulders, and because we had a pug, our GM said that anyone who needed it (guild or pug) should roll, rather than using DKP. Pug priest wins the roll, and the guild’s main tank, who had been saving DKP for months for those shoulders, seethes, since it was a warrior/priest/druid item.

After the raid is over, seething turns into full-on hissy fit. Spreads to other guildies. GM turns hissy fit turns into new guild policy: No. Pugs. Ever.

“Wow,” I said to myself. “How come this only became an issue after the pug won? Shouldn’t loot rules have been clearly articulated and acknowledged by all beforehand? Maybe even discussed, before the GM announced a final policy? Shouldn’t our MT have been ticked off before the run? At the policy, not the result? Or shouldn’t he at least have accepted the fact that loot rules would be different because we needed to pug a healer to do the run?”

Failure #2: “No, we really don’t take pugs”

Fast forward a month. Casual Guild that Raids is having a hard time filling SSC on Saturday night. Really hard time. Nineteen…ok, now twenty…twenty-one…and that’s it, we hit the ceiling of people that even vaguely qualify for SSC. And this is not a raid on farm, or an easy-mode post-nerf walk through the park. Twenty-one is not enough. Desperate phone calls to offline guildies commence.

I’ve been politely whispering to the RL that I have two friends I play with a lot, a mage and a hunter, who are not only geared enough for the raid (far more geared than most guildies), but are skilled players. Team players. Know how to run out of the fire. Have offered to pass on loot, just willing to help. I believe I had enough clout to make my recommendations carry some weight.

“I’d rather take some half-dead guildie than wipe ‘cause of some pug.”

Hard to describe the amount of spit required to say the word “pug” in that sentence as it came thru on vent.

Okies…begin planning an exit strategy from Casual Guild that Raids.

Alternate Universe: This time, with Leadership

Original TK raid goes down without a pug. We can live with 24.

Or – we get a pug to fill slot #25. GM announces that, like it or not, we need to fill a slot with a guest healer, and therefore they have a right to roll on loot, within certain reasonable and stated bounds. This is the price we must pay to make this happen. Guildies surrender, because they want to do the raid rather than not.

Loot reaver drops T5 shoulders. GM acts on the stated policy, allows priest to roll. And lo, the pug priest wins. Grats from all, perhaps even with an acknowledgement that in some way he deserved such good luck for helping us out. Main tank bites his tongue, hopes for better luck next time.

GM gives two epic gems to the top DKP, the one who would have won the shoulders, as a consolation. The warrior, while not as happy as he would have been with shoulders, realizes that the GM did the best job under the circumstances.