Skip to Content
1-09-2012 @ 4:47PM
It's obvious that running instances is a commitment. It is absolutely your responsibility to only commit when you can give it your full attention, without interruptions. However, I feel like the question posed by the OP was more-or-less unanswered. He wanted to know what you do when the unexpected happens. If the doorbell rings or the kids wake up, do you ignore it and fight until the boss is down? Do you bolt like hell to the door, jumping furniture as if it were hurdles just to get to the door fast enough? Do you tell the shady high school student that the key is under the doormat and they can come in, take money out of your wallet and pay themselves for the pizza delivery? I could be wrong, but I get the impression he was wondering what is best etiquette in those situations when they happen, even if they took every precaution to prevent them.
1-09-2012 @ 5:30PM
Actually, I think those points were answered... If you ordered food, don't queue until it gets there. If the doorbell rings, and you're not expecting anyone, hell, ignore it. If it's someone you wanted to see, they would have called first, or when you don't answer the door they can call you then. For kids/family needing you at a moments notice, try to schedule "don't bother me" time with your significant other, so you aren't interrupted during the raid/instance. Etc etc.
1-09-2012 @ 5:41PM
Well, part right. The answer was to minimize those interruptions when running pugs. Again, if you just ordered pizza, don't queue for a random or LFR since you know you're going to be AFK for a few minutes at some point in the next 35 minutes most likely, and you know it will happen right in the middle of something. And then you have the 50/50 of folks deciding to kick you for being a jerk.So yes, the mamas might have not answered in the intended format, but that's because the writer is asking for permission to do something they know deep down they shouldn't be doing - which is putting their schedule ahead of the 4-24 strangers they just got grouped with.
1-09-2012 @ 7:12PM
Yeah, you're right. It does mention those things, and I wholly agree with the preventative measures. I think I was expecting to see answers about reacting to the situations as they arose, and in particular, how best to convey them to the group. Obviously, if you're leaving on Deathwing to go chow on a pizza, you deserve a kick, regardless of what you say. I guess I'm just curious what to tell these people you're letting down, even if you already know the outcome.And just out of unmerited curiosity, I would like to know what's best to say in emergency situations. I like to think a simple "brb, desk on fire" would suffice, but I'm open to more polite and/or hilarious responses.
1-09-2012 @ 8:05PM
Dan, I agree. One of us should have mentioned proper etiquette when you must unavoidably afk. If you have time to type it out, you should be politely communicative while giving an expectation of return. Examples:"Sorry must afk unexpectedly. I should be back in 2 minutes tho.""AFK RL. Not sure how long it will take."And if you come back and are booted, don't get upset. In case of actual emergencies, try to type out AFK 911 if you have time. If not, well, it's an emergency. You have to deal with it.I left it out of my answer because he seemed to be polite enough about it, but seemed to feel it was alright to inconvenience those other people and they were being the rude ones for not understanding. However, we should have addressed it.
1-10-2012 @ 10:13AM
And I think that part of the problem is that we don't really have a universally agreed on list of what falls into these two categories:a) Really unexpected emergencies that couldn't reasonably be planned for and warrant inconveniencing up to 24 other real people, andb) Real-life events that one really should have either planned for before hand or not engaged in group WoW play at all because of them.For many events, most people will agree what category they fall in. But there's a whole grey area in the middle where the same event may be a "omg! emergency, gotta afk" for one person and a "well, this might happen, so I probably shouldn't queue up right now" for another.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.