MDFubar

Ok, this is a tough thread for people to post in. Only the brave will do so. I have started this thread because I have noticed people trying to command and then think that they do not do a good job.
So, come here and post what you think you did wrong, ask for an eval of your commanding, or just read what others have to say.
This IS NOT A POST FOR PEOPLE TO BE RIDICULED, but one for people to get help.

Example:

I commanded last night on Berlin and thing went very badly. My squads couldn't punch thru, the APC and Walker where killing my troops. We lost the round and it was just bad.
I think I could have done more spotting, but I seemed to miss the Walker and Apc each time with the orbitals, what can I do to make sure I hit them?

Did I communicate too much or not enough? I think I should have focused more on getting one flag at a time vs. trying to punch to the back.

Any thoughts?

Now, I did not command last night and this is just an example. My intention is to provide a thread where people can get some honest feedback and help.

The next question is, should we have one for SL's too?

__________________


"No bastard ever won a war by dying for his country. He won it by making the other poor dumb bastard die for his country."
- General George Patton Jr

Bc2ID

I think if we get in the habit of posting AAR's then possibly people will respond with their opinions and suggestions. I know how tough it is to take screenies and command at the same time, but these will enhance the discussion. It would be great..but darn near impossible to have both commanders post their AAR's with screenies. This will show both sides of the story and can prove to be a useful tool.

B

__________________

Arithea

Great idea, Fubar. And I like the idea of AARs, Bc2, but I never feel like I have time to write them up, as I'm often just trying to get in a few games either before rushing off to do something else or before bed. I'll try to do more of that in the future; I've had some pretty decent rounds, lately, and I've been commanding more often.

Speaking of commanding, I know there are some of you out there who have lead squads while I was commanding. If you have, please post a few things I should work on. I feel like I'm doing all right (though not great), but I really don't know where I need to improve. If nothing else, if you squad lead, post some of the things you like to see a commander do. Personally, I know I'm really bad about not putting out supply drops, especially if there are vehicles in play. Other than that, I don't know if I'm giving my squad leaders all the intel and leadership they need. Please, help us help you!

__________________

MDFubar

Thanx for leading the way Arithea! I would +rep, but it says I must spead it around.....

__________________


"No bastard ever won a war by dying for his country. He won it by making the other poor dumb bastard die for his country."
- General George Patton Jr

rickrock

I don't have much experience as others on TG but what I can say you are a terrific commander Arithea! I was one of your SLs on Cerbere Landing this week and had a "near perfect" experience. Actually it was the first time the commander talked to me and understood my plan and gave me the support for it... Thumbs up!

__________________




TG-55th Infantry Division

Arithea

Thanks, rickrock. I think I remember that round, and it's one of the few rounds I've commanded on Cerbere where all of my squads actually listened to me. Usually, as EU, we end up with nothing but Command Center, and the entire team just throws themselves at Roadblock like lemmings, regardless of command orders. But none of you guys did that. In fact, you even managed to keep most of your squad members in line and behind the danger zone. You guys were awesome!

On another note, it's good to see some of the new people taking initiative and squad leading. It took me about a month after I joined before I had the guts to do it.

__________________

ThePromQueen

Oh come on, Ari! You know we won because of my 7 DOOMCANNON kills

__________________

Arithea

Yeah...Prom just has to gloat because he happened to even the ticket count with his Rorsch kills. In fact, right after doing so, he said to me, "Commander, I want you to know that I just singlehandedly evened the ticket count with Rorsch kills."

Of course, the other five squads rocketing the crap out of Roadblock didn't help at all...

__________________

JRiop1

Hi,

I just joined, and this is my first jump into forums here, so go easy on me.

I've played on TG servers many times. It is my favorite server. I've also commanded on the server several times and I would like to know how I did. If anyone remembers my games, that is. lol

My biggest flaw that I know of is that I don't have VOIP. I rely heavily on people asking for supply drops and I make my own choice of orbitals and EMP.

As I said, please let me know how I can improve my game.

Thanks.

pred011586

I just recently started to do some Commanding also, generally when the teams are small. My most recent Commanding job was on Tunis Harbor last night. After the round I think I was communicating a little too much, and overestimated alot of potential threats. (My apologies to the 2 man TG squad that I had running from halfway to Eastern Docks back to Junkyard for a non-existant threat! <3). To be completely honest, I don't even know HOW to be a good commander. I'm alot more comfortable as a SL than a CO (and even more comfortable as just a SM).

To make my post more on-topic, should I be communicating EVERYTHING i see? I understand the importance of pointing out if a lone enemy/squad/FAV gets past the frontlines, but at times I feel like relaying too much intel, such as info reports of an enemy walker approaching the front lines when it's already there and everyone who needs to know it's there can clearly see it.

Zhohar

Pred, one of the worst things you can do as a CO is communicate too much. Give your SLs only the information they can use.

Edit: Let me clarify: If you keep on talking, the SLs can't hear their SMs and the squad can't respond. And chances are, if you keep on talking for more than a brief bit, you're giving people information they don't need to know. Give people what they need to know and allow them to focus on getting things done.

For example, if you see an enemy walker at a flag heavily defended by friendlies, and you say:
"Okay we have a walker at Crossroads flag, squads 3 & 4 destroy it please."
That is wrong. What you should instead do is:
"Heads up Squads 3 & 4, enemy walker is up. It's still empty but it'll come your way in a bit."

The former is direct information -- you've done nothing to help your team. There is no value added to that sentence stemming from the fact that you're the CO. A random infantry could have spoken that sentence just as well.

Good rule of thumb: if a SL can't take immediate action based on your words, don't say them.

__________________

MDFubar

Glad to see this is getting some use!

Jriop1, not having VOIP is a bit of a problem when it comes to communicating specific orders but still is not a deal breaker. You should be able to hear the SL's talking to you though, correct? Not being able to hear VOIP could be a bit of a problem.
Do whatever you can to enable voip, especially if you can not hear it. Communicate with the SL's in the beginning of the game and tell them via chat that you do not have a mic, so they know in advance and can compensate for that. I have never played while your where commanding, so I can't give any kind of eval.

Pred011586, communication is the key to success and yes there can be too much. Overestimating a threat is much better than underestimating one. Remember that one person could be an SL and potentially be 6 at any time. If one person gets to a flag and the entire squad spawns on them at once, they can turn a flag in seconds.

Cudos to both of you for taking the CO position and working with it! Check out the CO's guide that we have and a few other fine reading guides in our forums.

Keep it up!

__________________


"No bastard ever won a war by dying for his country. He won it by making the other poor dumb bastard die for his country."
- General George Patton Jr

Arithea

That's a good way of putting it, Zhohar.

While I'm commanding, I will occasionally give an overall update on enemy troop positioning. For example, if I'm commanding the PAC team on Cerbere Landing and we have South Town, Church, and Office Ruins, I'll throw up a UAV north of our troops and say over general comms, "Looks like the bulk of their force is north of South Town Center. The eastern route to Roadblock looks pretty clear." I will often follow that up with orders to defend, attack, or flank to individual squads based on that information.

Do you guys think that's helpful, or is it TMI? Should I simply give the orders without giving the overall sitrep prior to doing so?

__________________

MDFubar

I think that once you put the UAV up, that is good enough for me. I can see what's going on. If you give me an order to attack and it is outside of the UAv, then I would like to know what is coming my way.

__________________


"No bastard ever won a war by dying for his country. He won it by making the other poor dumb bastard die for his country."
- General George Patton Jr

Arithea

Gotcha. I always wondered if that was too much info, but I figured better too much info than too little. I'll keep that in mind next time I command. Thanks!

__________________