Re: What do you need in a Commander?

**submit7** · 03-10-2009, 02:43 AM

Originally Posted by Scarface6174

Today I played commander twice, and I got to thinking "What does a SL need from me? When am I too annoying?"

So I guess I'll pose a few questions and mebbe get a few suggestions so that the quaility of commanding on TG improves overall.

What do you need/want from the commander? (information, orders, etc)

What don't you need/want from the commander?( how much talking, too many orders, spelling with mine markers, etc)

How much should TeamSpeak be used with in game VOIP while commanding?

Are there maps where a commander is utterly useless?

1) Need updates on armor positions; hostile aircraft; what assets are available to us; if laze is available (in case pilot didn't get the chat from spec ops guy); if playing Kashan and there aren't at least two inf squads going to the bunker then he needs to allocate them: regardless of vehicle whore complaints (I like to vehicle whore myself, mind you)...this applies to any map where there is the temptation for everyone to make vehicle squads; he doesn't necessarily have to organize everyone, however, he does need a basic gameplan for every map he commands on: if the players are way off from this then he needs to take charge and organize. When you have played this long enough you can tell almost immediately when the team is incorrectly focused...you see everyone running behind enemy lines when the first flag to cap has not even one squad going for it...or everyone is getting in armor/helis, etc...with no inf support...too many sniper and "recon" or "spec-ops" squads. Know the controls to communicate with squads individually; keep the spam down; give precise info. in concise, well organized sentences. Don't yell at the squads but you CAN interject just enough emotion to let them know you are in charge. Use the !reporting function to get the admins involved with tk'ers and idiots not following orders.

2) No spam: be precise and use economy of language when communicating intel and orders; don't use the talk to all squads function when addressing a single squad; if you get frustrated commanding stand down and do not whine about it while spelling your frakking name with enemy spotted markers

; don't use text chat to try out trivia questions that show off how smart/pompous you are (should I even have to say that one? happens more then you think); I am here to win...I just wanna play...if there's only 5 or 6 guys on the server knife-fighting then screw around all you want...if not try to get it going and win; don't be mean...I have a fragile ego

.

**AREM117** · 03-12-2009, 03:32 PM

I want to know where the enemy is, who is defending/attacking, what kind of support my squad has, and if my squad is needed somewhere else.

As a commander I like to have the support of my team. I want to know where they have spotted enemy units and where they have either killed or been killed by something. What assets they want. But most of all I want teamwork.

As randy said TS is sometimes used to bypass the CO, which should never be done, Respect the chain of command. BF2 actually had a reason for not allowing the SMs to hear the CO and the SL not able to speak to other SLs.

The CO is most useful in insurgency maps. I it was awesome when Randy brought the whole team together and got a massive stryker/HMV convoy going in Ramiel, it was epic. The CO can have the power to bring the whole team together or sit there in his CP smoking pot and not really caring. A good commander cares about his team and every ticket available.

**Sabre_Tooth_Tigger** · 03-13-2009, 11:51 PM

Co can pass attack markers from one squad to another. Infantry places marker on tank, CO duplicates position to CAS

Thread Tools

Display