Complaint

CronoDroid · Post by **CronoDroid** » Thu Jul 23, 2009 4:25 pm

Some people just don't have the micro skillz to simultaneously run an econ, command their pilots, research tech, build bases, drive a ship and accept pilots at the same time. You all don't all have our RTS skillz, so give them a $#@!ing minute.

Post by **FreeBeer** » Thu Jul 23, 2009 6:07 pm

The key here is communication, I think. Commanders, in my mind, should communicate as promptly as possible to join requests. Either accept, or don't but give a reason (and the reason must fall within the RoC and "Pook's Rule"). That is not to say that he has to reply to the same request 20 times in one minute... just something reasonable. NOAT folks can (and do) explain what's going on to the recent arrivals... "he's busy atm", "he can only accept voobs and higher to keep things balanced", etc. If the Commander is really busy, I understand and accept that he can't always immediately respond to these requests. But I do expect a response within 2 minutes - most "busy events" are shorter than that.

If it's that crazy, he can always delegate it to someone else on the team (TS helps in this regard, guys.) There's bound to be someone on the team that is free to respond on his behalf.

Now having said that, joiners should be patient. And for the most part, they are *if* they at least have some acknowledgment of their join request in a reasonable amount of time. The exception, of course, is the newbie joiner. He doesn't have enough familiarity with the game or how we play it to know or understand that a join request can take some time. That's where NOAT can help (and often does). Personally, when I see a newbie trying to join the game and isn't getting accepted immediately, I'll PM him a reason. (The PM is a little more noticeable because it gives the "beep" sound to draw his attention to the chat). Doesn't always work but what else can you do?

Summary:

Commanders: at the very least acknowledge in a reasonable time (say under 2 minutes) the join request.
Joiners: Be patient. PM (after a reasonable amount of time) the Commander as a reminder - it's easy to forget or miss a request when you're busy.
NOAT: Help folks out by 'splainin' stuff.
MrC: Monkey! Monkey!

Personally, I will not ban a Commander during the game - that just messes up the two teams. Unless he's being a real dick and is an obvious violation of the RoC or I can invoke the Texas Defence ("he needed killin'").

But expect to go bye-bye at game's end if you've violated the Rules. I will also ban joiners if they are being annoying about it without cause. If I am on NOAT, let *me* intervene on your behalf. I'll give Commanders every lee-way that I can that is consistent with the Rules.

That's my

guitarism · Post by **guitarism** » Thu Jul 23, 2009 6:28 pm

MrC i think the issue isnt so much that one commander wasn't letting someone join, but both were, and when one finally did let raum on, it was a prompt boot for no reason.

Remember when you had to have a reason to boot, no matter how far fetched? Same idea.

Post by **zombywoof** » Thu Jul 23, 2009 7:13 pm

MrChaos wrote:QUOTE (MrChaos @ Jul 23 2009, 09:20 AM) so I have to accept people no matter what finger? Not being a forum lawyer but really?, Or is this just one of those unwritten rules?

I don't think anyone would say you have to accept everyone all the time. But as Guitarism said, this is an issue of none of the commanders accepting anyone. Besides, Raum isn't the kind of guy who'd be on a "no fly" list.

FingerBang · Post by **FingerBang** » Thu Jul 23, 2009 8:02 pm

MrChaos wrote:QUOTE (MrChaos @ Jul 23 2009, 11:20 AM) so I have to accept people no matter what finger? Not being a forum lawyer but really?, Or is this just one of those unwritten rules?

Pook's Rules of Conduct for Dummies

Act like an adult.

Even if you aren't one. This is a mature community based around a game. G-A-M-E - it's not a lifestyle, it's not your fan club, it's not your escape from reality where you're the playground bully. Being good at a video game doesn't mean anything except that you have too much time on your hands and can't find a productive way to spend it.

Be Civil. Everyone wants to play, nobody wants to be hassled. When in doubt, see the rule above.

Everyone gets to play. You don't get to decide who gets to play and who doesn't. I don't care if they have a !@#$&% (-3) tag, let them play... so long as they follow the rules.

Don't be stupid. When you're doing something you know you shouldn't do, you're being stupid. I don't care if you're trying to make a point, push a political agenda, or just like annoying other people. Don't do that. When in doubt, see the above rules.

There you have it. If you follow these four simple rules you won't violate the official RoC and everyone will be happy. If you don't follow these simple rules, then you don't get to play.

— Quoted from Pook

Kltplzyxm · Post by **Kltplzyxm** » Thu Jul 23, 2009 8:07 pm

Freyja wrote:QUOTE (Freyja @ Jul 22 2009, 10:16 PM) Spamming = Accept and boot. And then accept the others waiting.

LOL. Talk about self incriminating. You deserve a ban to serve as an example for not reading the rules carefully and being a douchebag.

MrChaos · Post by **MrChaos** » Thu Jul 23, 2009 8:14 pm

so the answer is no he doesn't have to accept him, but can't be an arse about doing so and that's where the boot comes into play.

that was some good learnin' thanks

Bobo

Broodwich · Post by **Broodwich** » Thu Jul 23, 2009 8:15 pm

i dont get it. as a commander there are a few pilots i wont accept on my team because i greatly dislike them

snufkin · Post by **snufkin** » Thu Jul 23, 2009 8:20 pm

once i misclicked and instead of accept i clicked on boot when a player was requesting. what happens then?

Jyppa · Post by **Jyppa** » Thu Jul 23, 2009 8:34 pm

If you mean that you clicked reject, nothing at all. If you mean that you accidentally clicked boot, nothing at all.