Protect Your Guild Bank with an Alt Invite Policy

Just a quick reminder for guild lead­er­ship: your guild bank con­tents might be full of L70 mate­ri­als and gear, but that doesn’t mean that shady peo­ple won’t want them and the gold your guild has stashed aside.

Every alt-invite request from a per­son with guild bank access should come directly from that character’s main.

This vul­ner­a­bil­ity exists all the time, but in this brave new Death-Knighted world, alt invites are going to be rampant.

GOOD:

Offi­cer­Main: “Hey, I just made a DK alt, name is Offi­cerD­KAlt. Can I get an invite?”

GM: “Yeah sure!”

Offi­cer logs off of Offi­cer­Main, logs on Offi­cerD­KAlt, receives invite, gets pro­moted to guild bank access. Noth­ing bad happens.

BAD:

Ran­dom­Per­son: “Hey, this is YourFriend­Of­fi­cer. Can I get an invite?”

GM: “Yeah sure!”

Ran­dom­Per­son receives invite, gets pro­moted to guild bank access, emp­ties guild bank.

From the looks of it, Blizzard’s going to have its hands full with tech­ni­cal prob­lems, so help your­self out and pre­vent this from hap­pen­ing to your guild.

More Words!

This entry was posted in world of warcraft and tagged , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

One Comment

  1. Dave
    Posted January 14, 2009 at 4:10 am | Permalink

    Our guild requires all alt requests to be posted on the guild forum by the forum account asso­ci­ated with the main, and once access is granted that is posted as well, and the result­ing thread is placed in a read-only archive for future reference.

    It’s a bit of over­head dur­ing times like this, but stick­ing with a process like this will keep you nice and safe.

    (Unless your offi­cer falls for a key­log­ger popup and gets hacked, not that we’ve ever had that hap­pen. Twice.)

Post a Comment

Your email is never published nor shared.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>