Officers' Quarters: Managing the alt invasion

I'll never forget that first month after Wrath went live and the endless requests from guild members to invite their death knight alts into the guild. The second anyone rolled a DK, they wanted to bring that toon into the roster to be part of the social experience as we all explored what the new expansion had to offer. I couldn't blame them. It is painful to be cut off from your guild during such an exciting time.
As it turns out, the DK influx was only a small taste of what the Shattering has wrought. Now it's troll druids, tauren paladins, and undead hunters springing out of the woodwork, or dwarf shaman and gnome priests for Alliance guilds. Even this, however, is just the rumblings before the earthquake. In one week, a deluge of goblins and worgens will engulf our rosters.
How can we manage this alt invasion? Let's take a look!
1. Make sure to ask whose alt you're inviting. This advice seems like a no-brainer, but when you're getting requests all day long, it's easy to become lazy and just invite everyone without asking who they are. It seems harmless, but the next two points will explain why this is a bad idea.
2. Use a security question. Nonmembers will sometimes try to perpetrate "alt fraud." Alt fraud is when they claim to be the alt of a current member in order to infiltrate the guild. There are several reasons why a player would commit alt fraud:
- They've been denied membership to your guild but they are still trying to find a way in.
- They have a grudge against your guild or its officers and they want to stir up trouble while wearing your guild tag.
- They belong to the opposite faction and they're trying to get information about where your guild might strike or where to look for people to gank.
You could try to think of a question that only that particular player would know the answer to, but that's a tall order for every guild member. The easiest way to prevent alt fraud is to post the answer to a security question in a members-only area of your website or in the guild info section of your UI. Your question shouldn't be something that is able to be researched or guessed, so the best answers are actually nonsense. For example, your security question could be, "What did the whale say to the seagull?" The answer? "Mustard pancakes."
3. Label the main of every alt in the guild UI. Whether you use the public note or the officer note, label the alt so that officers and other members can attach a main to that character (and his or her behavior). As we all know, sometimes players will try to get away with behaving badly (or other high jinks) when they're anonymous, and the easiest way to become anonymous in your own guild is to switch to an unlabeled alt. Labeling them takes away that anonymity, although if you only label them in the officer note, they won't be aware that they're not anonymous to the officers -- and that's a good way to test whether or not someone will act like a jerk when they think they can get away with it!
4. Set a level requirement. A level requirement will be a controversial move, but it could save your officers some headaches. Players will want their goblins and worgen in the guild ASAP, but do they really need them in the guild immediately? Like I said in the intro, I understand that people want to be in the guild during the weeks after an expansion launch. There's a lot of excitement, even giddiness, and players don't want to be cut off from that.
However, by setting a level requirement, you can make sure that only the alts that players intend to level will be invited. The requirement will cut down on the number of invites during that first week. It will also ensure that your roster isn't cluttered up with level 5 worgen druids that never see the light of day in 2011.
You don't have to make the requirement punishing. I recommend level 15, which is when players gain access to the dungeon finder. There aren't any group quests that I know of below that level, so players lose nothing besides the social experience.
For death knights, I would recommend somewhere around 60, since they will be done with the DK starting area by then. Anyone can play through that and maintain interest in the toon -- it's when you hit boring old Outland that tests whether or not you intend to keep playing that character.
Players will complain, of course, but you can recommend that they form parties, create a custom chat channel, or use your guild's voice chat server to communicate until they reach the required level.
5. Train your officers to do all of the above and prepare your members for the process. You're not the only one inviting alts -- everyone with this power will be pestered every time they log in for the next few months. Make sure they all know the proper procedures. Likewise, be sure to communicate your alt-inviting process so that members know what's expected.
6. Have an alt policy for raids. Over the lifetime of the Cataclysm expansion, you're going to run into more alt issues than during any other time in WoW's history so far. You need to decide how you will handle alts in raids. Some questions to address:
- Under what circumstances will alts be allowed into raids?
- What requirements will alts have to meet in order to fill a raid slot?
- How will alts fit into the framework of our loot policy?
- May a member switch their designated main character to an alt?
- What must they do to allow for such a switch?
How does your guild plan to deal with the alt invasion? Tell us below!
/salute
Filed under: Officers' Quarters (Guild Leadership)






Reader Comments (Page 1 of 3)
Vaylie Nov 29th 2010 9:17AM
Why go through all the hassles of security/level requirements? Our guild leader just has us whisper him on our already-guilded toons the name of our alt and then we can swap over for an invite. If we happen to be on vent, I can also just ask over vent for an invite.
mathias Nov 29th 2010 9:32AM
The second point answers that question. You must have just missed it.
Snowfeather Nov 29th 2010 9:40AM
This is what we do in our guild as well. Though notes are already set up for mains and alts, since we use EPGP.
Kel Nov 29th 2010 9:40AM
This is a good policy to have and generally one that we follow. If I'm going to log off and create that human hunter, I will ask my GM first if he's up for inviting said hunter and then he knows to expect my whisper.
Hoof Nov 29th 2010 3:20PM
Have to agree with Vaylie. Waste of time writing this all up. Just have your guild member make the request on their main or over Vent.
Rai Nov 29th 2010 10:44AM
Real ID is a useful way to deal with this concern, if you're close to your guildmates like I am.
Undeniable proof of who you are? Excellent.
talkingmike Nov 29th 2010 11:51AM
Hey! Hey you! You can't say that! You can't say anything positive about RealID!
Four legs good, two legs bad!
loop_not_defined Nov 29th 2010 3:17PM
This is what we do. The policy for alt invites is to ask for the invite (giving the name of the alt in advance) while logged in with your main. I've set up all the officer notes to say "Main" or "Alt: " in order to keep track of it all.
steelfan555 Nov 29th 2010 3:37PM
@Mike
Four Legs good, two legs Better!
Jeremy Nov 29th 2010 4:41PM
Making them ask on their main or in vent IS a security requirement, just a different one from a question or whatever. His point was have some way to make sure you know who you're inviting.
loop_not_defined Nov 29th 2010 6:23PM
Jeremy, his point was to have a security question. It's clearly bolded, and he spends a couple of paragraphs explaining how to make security questions work. I don't think our alternative suggestions were unwarranted.
Boneshòck Nov 29th 2010 9:24AM
Was worth reading it. Especcially #5 is the one I think is quite usefull. Everyone who can invite should be aware of what the requirements are to...
Thanks for this post!
Meatwadz Nov 29th 2010 9:24AM
Do you have any suggested addons for more advanced guild tracking? The current guild UI lets stuff fall off the log quickly and makes tracking who invited who quite a pain if you don't log on every day. Something that shows date of invite, who invited, and maybe also tracks promotes/demotes and number of kicks/invites would be amazing! Something like a guild "black-list" that warns the GM if a new invitee has been previously removed or left the guild in the past.
Adoisin Nov 29th 2010 10:36AM
I'd be interested in something like this too. Anyone have any suggestions?
CK Nov 30th 2010 1:03AM
I run an addon that does just that, called GuildCheck. Works well for my purposes.
Saeadame Nov 29th 2010 9:25AM
I sort of solved the "alt" issue for myself by having my alts in a bunch of different guilds. I have some in the banking guild I made, a couple in a social/any level guild, and my main in a raiding guild. Since the social guild accepts any one of any level anyway, and any member can invite, I just poke someone in the guild for an invite as soon as the introduction thing finishes.
If I want to not have guild chat, I tend to put them in my banking guild, since only my characters are in there. If I want people to chat to, though, I'll stick them in the other one. This has the unfortunate side effect of making me play one alt or the other depending on what kind of mood I'm in. So, if I've been in that mood for long stretch, one alt will become a significantly higher level than the others.
Cbeefman Nov 29th 2010 9:40AM
/gasp thats the SAME password on my luggage!!
Thes Nov 29th 2010 10:35AM
Spaceballs reference made me smile!
Rufio Nov 29th 2010 3:05PM
1,2,3,4!
Koleckai Nov 29th 2010 9:29AM
If your guild uses custom chat channels, you should use an addon like Identity as well. This way you can identify who the alt belongs to without looking at the Guild UI all the time.