GMs Talk: Things We Share, Things We Do Not

© Monkey Business - Fotolia.com

<Apotheosis> must be sick of me whenever I pop into their mumble late at night. That’s Kurn’s guild. Every so often I like to drop in there and have a chat with another GM (who doubles as a blogger herself). Not too many of us around, I’m afraid. She doesn’t know this, but she plays a big part in making sure I remain grounded. When it comes to guild matters, there are certain unspoken rules even among the company of those similar to us. There are topics that we’ll talk about and others that we do not ever, ever discuss. It’s the equivalent of talking shop with others in the trade.

Stuff That’s Fair game

War stories

“And he’s slowly backing up pulling Arthas with him and then falls over the ledge! He just starts screaming over vent, Taunt! TAUNT! I fell off the ledge!”

Everyone loves a good war story. Hilarious events or tales of awesome heroics (that may or may not have been slightly embellished). It’s even funnier if it’s a player that both GMs are familiar with. Typically, whenever war stories are exchanged, there’s usually an important lesson that can be learned and applied. Both leaders walk away knowing more about how to avoid similar situations in the future. The exchange of knowledge means that only one of us would have to experience an event. We’ll then share it with our GM friends in the hopes that they can recognize the symptoms of a problem before it occurs.

In this case, like not tanking Lich King so close to an edge.

Policy

Anytime I’ve wanted to make sweeping policies that affected the guild or the raid, I’d try to consult with someone outside. I search for someone who’s familiar with a similar issue. Even better if the guild leader successfully implemented a policy in the first place. I also to try to get in touch with someone who wanted to put a policy in place but ultimately didn’t and listen to their point of view as well. An outside perspective can shed a spotlight on additional factors that weren’t taken under consideration. I listen to what worked well and what didn’t. Maybe some changes or adjustments were made after the fact to help smooth the transition over.

Speaking of which, I need a consult about whether or not I should implement a policy dictating that all raiders show up with pants worn at all times.

Strategy

This is another reason why I’ll consult with another GM. Sometimes we’ll run into a brick wall when we’re working on an encounter and I like to turn to other people outside who have done the boss. Oftentimes they can offer a little insight into a possible solution. Not everyone’s raid composition is exactly the same. But with strategy changes, you can usually account for that by getting a different class to try and do the same thing. Sometimes it’s a simple solution like moving the raid over slightly or altering the timing! Asking a “How did your guild handle this obstacle?” can sometimes lead to light bulb illuminating moments.

Evaluation techniques

Determining player performance is never going to go away in progression raiding guilds. We’re always looking for methods where we can excel and find tune the players under our raiding core. If a GM happens to be an expert at a class, it’s not a bad idea to pick their brain a bit and find out what they look for when gauging the effectiveness of players.

Stuff That’s Off limits

Current damaging drama

Any active, dramatic issues are kept off the table. I don’t like discussing things like ultimatums, problems or people just giving me a hard time without making certain things really vague. If the guild is going through a really rough time, a lid’s kept on it. However, if a problematic issue has been resolved and passed, I’ll classify it under the war stories category.

Exception: If it really does get to a breaking point, and every option had been considered, I’d probably shoot some ideas and get someone to play devil’s advocate and see if there’s a possible solution that was missed or we walkthrough scenarios of what would possibly happen. Sometimes it isn’t possible to do that within the guild.

Names

I tend to obscure names unless it’s someone well known to the community. If I’m describing a situation, I tend to go with the class or the role.

Example: I think Lodur’s moustache is compromising his ability to heal.  Or worst yet, he’s using the moustache to heal.

Applicants

I’ve had players who leave Conquest apply to guilds of other bloggers and vice versa. As a personal rule, I never bring them up at all. As far as I’m concerned, the business is always between the recruit and the guild they applied to. I don’t ever ask about their application nor would I ever meddle in any guild’s affairs. I have a hard enough time running my guild and it’s not my place nor interest to run someone else’s.

Exception: However, if the player who applied did something particularly heinous like break into the guild bank or exploited in game, I believe it’s the duty of the former GM to relay the necessary information and then let them deal with it how they see fit.

Code 21

We never, ever talk about code 21 unless it’s under extreme circumstances. Sorry guys, it’s a GM thing.

And there you have it folks! If you’ve ever wondered what goes in the GM’s lounge, I can assure you that there’s no plot to take over the world or to gkick everyone from the guild. It’s mostly business and nothing to be worried about!

A Letter from a Level 25 Guild Leader

First, I just want to say to my Chicago readers that you should be extremely proud of your team. They’re going to be an awesome hockey franchise for years to come. And oh my god did they give me the biggest scare of my life.

Anyway…

I found this letter linked on Reddit the other day. It’s one of the side effects of the new guild leveling and perks system in WoW.

Dear Plebs,

If you’re here, and raging, it’s probably because you just realized you were gkicked. I’ve already deleted all your forum accounts, and removed all your boards. There’s nowhere you can post or vent so please, just read this.

For the most part this was an awkward experiment we never intended to go as far as it did. I jokingly recruited a few people out of trade chat, gave them ginvite power, and this thing for the most part grew itself. With it was the nice realization that our 10m raid crew could push levels faster and not have to farm heroics every day, so we let it ride. We figured it was a nice give and take, you guys got the best perks available and we got our XP cap every day. To be honest we mostly let it go because we thought cash flow was going to be awesome, but it turns out you guys were collectively pretty sh*tty at farming gold. (Over the last 5 months we’ve made about 14k off of a roster of 900+ people). But the XP was flowing, life was easy, and this was a nicely self-sustaining little eco-system that we just sat back and watched grow.

Unfortunately what accompanied this was an alarming number of less desirable members. Guild chat was basically useless, there were too many idiots to even try to manage, and for the most part nobody wanted to do anything. We gave you forums. We gave you vent. We gave you calendar events. We left GMOTD’s saying “come sign up on the forums for X event!” and 2-3 people would do it. We tried to coax some of the more promising members into leadership roles, we gave them an entire section of the forums with spelled out raid strats, pvp discussion, and more.

We tried. We really did try.

What we got was a whole lot of nothing but people bitching that we wouldn’t buy their epic flying, or pay their repair bills, or let them have potions out of the bank. People whining that we never carried them in our main raids, or that we didn’t run them through heroics or lower level dungeons. We got a million stupid questions a day about how to spec or what stats are good for X class. We got the few people we thought were worth keeping making a mess out of the little power we gave them. Promotions / Demotions were fucked around enormously, guild MOTD and notes were all ruined, and gchat just eventually became a giant sea from which all the idiots could troll.

When we hit 25 I kicked everyone that was inactive. I gave you all a few weeks after I cleaned out the roster to see if you would actually do anything other than occupy space in the guild pane and badger the bejesus out of us with stupid f*cking tells. I gave you your time to finish reps, buy heirlooms, get what you needed, and get out. The time has come, and now, the ride has come to an end.

That’s not to say you’re all bad, or useless, but let’s be honest; any of you worth a sh*t shouldn’t be in this guild anyway because the reality of it is that we’re never going to do anything but 10m raiding. We have no spots for you. We have no spots in an alt raid for you. We have nothing to offer you but a backup spot on a roster of people that don’t ever miss raids. It probably seems like a dick move to kick you, but in the long run we’re doing you a favor.

So, to all of you, thanks for what you did, we hope you enjoyed the perks while they lasted, but we’re ready to have our nice quiet, mellow guild chat back. Enjoy the heirlooms, enjoy the mounts, enjoy the recipes, and I hope you enjoyed the ride. I can definitely say it was at least, interesting, for me.

I sympathize with what the GM went through. The guy tried to help create a cohesive ecosystem  out of chaos but ultimately wasn’t able to pull it off. It virtually polluted the guild and he got frustrated with everything before dropping the reset button. It sucks putting time and effort in, just to get stomped on or disregarded.

At the same time, I can’t help but imagine if there were a few productive members in that pool. If the GM had been open from the start stating that they were going to be utilized in power leveling the guild to 25 and in exchange those members could purchase whatever rewards they wanted heirloom  wise, would that disclosure have made a difference? I can’t help but wonder if the situation could have been salvaged. What if incoming players were more thoroughly filtered? 

I still think the design of the guild leveling and perks system was a good decision for WoW.

There are always going to be guilds that will abuse the system and the players. That isn’t the fault of the system though. There is much more “power” to the GM’s position and that of the leadership. When there were no guild levels or perks, guilds were nothing more than organized geeks. But now, not only can a GM wipe away membership they can also remove a member’s access to powerful bonuses and items.

On a side note, we discussed player satisfaction and guild leaving in  Episode 16 of the Matticast. If you’re torn between leaving your guild for personal progressions, listen to our thoughts on the matter.

Matticast Episode 16 – Adopting Change, Unnecessary Heroics, and Patch 4.1

On Episode 16 of The Matticast, BorskMattKatChase and Brian discuss:

– Adopting Change

– Are Heroics Necessary?

– Parting Ways

– 4.1 For Healers

Don’t forget you can send us your questions or topics or tweet us with the hashtag #matticast

Subscribe to the show: iTunesRSS

 

3 Questions to Ask After a Recruit’s Trial Period Ends

In a recent episode of the Matticast, one of the topics we discussed was what guilds look for in applications. Once a player gets accepted, they typically undergo a trial process. The period could range anywhere from days to weeks. An application is a start, but it’s during this evaluation period where the recruit’s skill and attitude are truly scrutinized.

The questions vary from guild to guild, but there are 3 big ones that cross my mind.

can-they

We’re looking for the technical players. Can we count on recruits to execute? In Cataclysm raids, we want players who can easily understand and respond to the different challenges with minimal hand holding. For Conquest, things like DPS rotations are foundations that are expected before applying. If I give a Rogue a spell or an ability, I expect them to shut it down when paired up with another player. If I give tank healers their assignment, I expect tanks to survive through the worst. It shouldn’t take more than an attempt or two to stay out of fires, dodge discs or deal with any easily avoidable mechanics.

Because if a recruit can’t handle that, then we’re not the guild for them.

will-they

The nature of boss fights means there will be players who have to do the crappy job. No one really wants take on these responsibilities because they’re either:

  • Boring
  • Crappy
  • High stress

These are the roles that won’t get you the girl, but it is a necessity all the same.

Taking one for the team and volunteering for these will amplify your value. The guy who says yes to doing the hard stuff looks better. It’s one thing if you can’t actually do your job because your class or setup prevents you  from doing so. But not doing interrupts or dispels because you don’t want to and making the raid jump through hoops is a frustrating experience for leaders because we need to come up with a functional setup that might not be optimal for what we’re doing.

That’s just selfish. It might end up being the reason you get passed over for future raid invites.

Normally, I’m the guy that tackles the dispels . But it’s reassuring to know that another player or two in the raid is both able and willing to tackle the high stress jobs in the event I’m not around.

Especially with playoffs starting today. Go Canucks go!

they-fit

This is actually something more along the lines of what Kat would say. Although she is the more warm and fuzzy hosts on the Matticast, I would have to back her sentiments on this one (but don’t tell her I said that, I have an image to maintain). While the aforementioned skills and willingness to do the dirty work are important, at the end of the day if recruits aren’t fitting in with the guild, then they need to get cut loose. Not every guild is right for every player. It’s easy for guilds to say yes, you’re in. It is much harder for guilds to say no, you didn’t make the cut especially after a breakout performance. Being able to recognize players who don’t fit in and acting on it swiftly will save you grief in the long run.

It was a difficult lesson for me to learn during the first year of Conquest. I had to make several compromises. I either found a way to work with troubling recruits or we didn’t raid. It took every ounce of diplomacy to maintain an uneasy peace. The two week grace period we have going lets me check out players and see if they fit in both in the raid and outside the raid. I might even join up with them in PuGs or other activities and see how they react to the banter in guild chat. I actually booted a really creepy player a few months ago because he made several members in the guild uncomfortable. But that’s a story for another time.

If you happen to recruit a player who answers positively to all of the above questions, then the odds are in your favour that they’ll be an excellent addition to your guild.

Tough Call: Fighting Progression Frustration

Image courtesy of leonardobc

This week the crew has been hitting our heads against a progression boss, and the talk around the campfire has a decided air of frustration to it. As a leader, you need to be aware of your team’s motivation levels when tackling new challenges. Encounters surpassing your raid team’s ability level can often turn frustration into futility.

But how do does a raid leader handle this precisely?

The same way we handle any problem – with planning and execution.  Sun Tzu, who probably would have been a Vodka/Paragon level raid leader, teaches us:

“The general who wins the battle makes many calculations in his temple before the battle is fought. The general who loses makes but few calculations beforehand.”

It sounds simple, and when you’re doing it well, it really is simple.  Knowing what needs to be done ahead of time and adjusting as you go along are the two key ingredients to successful raid progression no matter the size of the raid or the strategy being used.

Below are a few points I recommend keeping in mind when your raid team is approaching difficult content:

Planning For Raid Progression

  • Read, understand and analyze the intended boss strategies as dictated by your raid leaders well in advance of attempting the fight. This allows you to see mistakes as well as make changes easily.
  • Be honest with yourself about the capabilities of your team. Have an idea where your weaknesses and strengths lie. This could be include aspects ranging from movement, DPS, healer skill or people with high raid awareness.
  • Know when to call a wipe and when to extend an attempt to see the next phase. Part of your team being dead might still allow the rest of the raid to practice key mechanics of the fight.
  • Experimentation is good. Figure out what works and what doesn’t when you deviate from a typical boss strategy. It might just be easier for your team.
  • Ensure your team is on the same page. Present a united and focused front for your troops to follow.

Sometimes, though, even our best-laid plans… well, you know what happens.  So the question becomes, what next?  What do I do when my team is getting weary, my strategies are in question, and I need a win quickly?

First of all, do not ditch your plan just because it isn’t working.  A strategy can fall apart in a lot of places. It may be execution, it may be a certain raid composition due to attendance; it could be any number of factors.  Find out where the strategy is failing and decide which elements you can change.  Can you swap personnel?  Slight positioning adjustment?  Time your cooldowns better (this is often a fix in Cataclysm raiding)?
Whether your plan needs a complete overhaul or just some minor adjustments, it is still crucial to address the frustration of your raiders and regroup.

  • Do not avoid the tough conversations. When your members bring up their gripes, listen to them. Answer appropriately.
  • Know the difference between toxic negativity and someone just blowing off steam. Sometimes people just need to vent. However, there is line between getting out some frustration and poisoning the morale of your squad.
  • Give responses that are logical and concise. You need to lay out for your team exactly what you’re doing, why you’re doing it that way,  and why you don’t think it can be done in an alternative way.  The more details, the better.
  • Accept suggestions and give them their due consideration. After all, if the 9 or 24 other people in your raid aren’t intelligent enough to help you with their observations, then you probably shouldn’t be raiding. Applaud valuable and constructive criticism from your raid.
  • Kill the boss and go out for beer!

Remember, the future is brighter.  Your raid will down this boss and will continue downing bosses. Success breeds further success.  Get out there and prove you’re all winners.


Reader Question

Last week, regarding my post on Real Officer Set-Ups, Kalette asked:

“Do you have any comments on how to incorporate this into a 10 man guild with two separate 10 man teams?”

Recently I had a conversation with Matticus about different ways guilds could operate more than one progression-oriented raid team within the same guild. (See Matt’s post here for his thoughts.) My feeling on the idea is that when you’re setting up policies for your guild, (attendance, loot, recruiting, critique, etc) they should apply to everyone playing that portion of the game, not just your raid team.

Clearly each raid needs their own raid leader, both of whom will need to be equally trusted by the GM, and trusted to work alone, because at least one of them will likely be raiding in without you overseeing them.

Beyond that, I think you could pull off a two 10-man raid guild with the same positions mentioned before.  You may have to get creative about which officer raids with which team, but in theory your role officers could oversee recruiting, critique and mentoring for every raider under their domain.  Since we’re talking about smaller numbers, they would each be responsible for roughly the same amount of players as they would in a healthy 25-man team, they would probably just need to be better at analyzing WoL logs parses since they can’t see everyone first hand.

Another approach is to combine a few roles, and have those role leaders cooperate with each other.  Tanks and melee DPS can easily be combined, and you could put ranged DPS and healing in a group together.  Then each 10-man raid would have one officer over each of those pairs.  Outside of raid, you may naturally specialize and have one ranged/healing role leader who is more attuned to healing and another who is better at the pew-pew, but so long as they can learning from each other, you can benefit from both being specialized.

By the numbers:
1x GM
2x RL
1x each Role Leader

Alternative:
1x GM
2x RL
2x Tanks/Melee Leader
2x Ranged/Healing Leader

I think the key caveat I’d make is that recruiting should still be done on a scale of “does this person meet our guild’s standards”, not just will they meet the needs of Raid A or Raid B.  When you’re fielding two squads who are both responsible for pushing progression and increasing your guild’s standing, it’s important to make sure that every raider meets the criteria to deserve that guild’s name above their heads.
Kalette, great question; I hope this helps.  If not, call me dumb and I’ll give it another look.

As always, leave your questions/comments/paternity suits in the comments.  I’ll lovingly read them all.  Also, if you have a topic you’d like to see addressed in a future episode of Tough Call, just let me know.