Archived from groups: alt.games.battlefield1942 (More info?)
I only started playing CO when I called for supplies and got the reply that it was not
avail because we had no CO. Ok, fine, having ANYONE who can drop supplies and call in
the occasional arty strike is better than nothing. So after a while of getting the hang
of it, I actually enjoy being commander from time to time, but it's not my first choice,
I like to get out and fight.
But if I'm going to play anything, I like to be the best I can be and learn from my
mistakes and also from other commanders. Here now in no particular order are things NOT
to do as a commander.
1) Do NOT repeat "Enemy infantry spotted" 10,000 times when the UAV is ALREADY TELLING
US WHAT WE NEED TO KNOW!!!
2) Do NOT call out enemy troop locations on the other side of the map when the
information is of ZERO use to ANYONE. Why tell us there are troops in the enemy base in
Karkand if there's nobody within 3 grids of that location and there are NO aircraft that
can possibly benefit from your canny observation skills?
3) Do NOT fire your artillery the split second it becomes available, do your scans and
UAV recon first! If all targets have too many friendlies around, then by all means shell
the enemy arty so you don't have it sitting there doing nothing.
4) Do NOT ignore calls for supplies! This is based on my personal rant of being Spec
Forces on MEC playing Clean Sweep and trying to C4 all the USMC artillery, UAV & Sat in
their base. I called for supplied 5 times, and was summarily rejected even after typing
in team chat who I was and why I need a drop. I had to steal a chopper and fly BACK to
my base to find a support guy to give me ammo. ARG!!!
5) Do NOT ignore calls for health, ammo, or repairs from your troops! All too often
there's nobody around to answer the call, and it's up to YOU to take care of your men. I
don't know how many times the tide of battle has turned by dropping a crate on some
badly damaged vehicles trying to attack / defend.
6) Know you squads behavior! Some will obey orders and communicate effectively while
others are off in another world... I was repeatedly ordered to attack bases on the
opposite side of the map on Clean Sweep last night as USMC spec forces who was attacking
& defending the captured MEC base. The CO on crack was ordering me to attack flags on
the opposite side of the map over and over and over and over... I wish squad leaders
could just mute moron commanders sometimes. Ordering squad #6 (mine) to the opposite
side of the map when I'm obviously doing my job at the enemy base is pointless,
irritating, and a waste of time.
7) Do NOT spend a lot of time if any fighting in combat, your job is to COMMAND not
FIGHT! Sure the occasional flag defend or repair of UAV, Sat or Arty is fine, but you
have no business being up in the front lines unless absolutely necessary. By this I mean
you took over CO as there was none and you needed supplies. I've done this and then
later in the map had mutiny votes called (no doubt from someone who just joined) because
some genius thinks he's the best CO ever and assumes you must be a dolt if you are up in
the front fighting. You wanna lead next map? Fine! But I'll finish a job I started,
especially if the way the battle is going looks like the current strategy is working.
I've had some very gratifying moments as commander where I doled out supplies to those
who needed them most, attacked when prudent, fell back and defended as required, and
never ever give up. I had a USMC team that was behind upwards of 100 points on Gulf of
Oman and slowly and gradually turned the tide and won I think 7-0 at the very end of
time. And of course I've had other moments where I've called in arty on targets, yelled
out warnings, only to have retards drive in under it and then ALL file so the tk/punish
and server kick boots you from the server.
Sigh....
I know there are more, but that's about all I can come up with right now...
ace72
I only started playing CO when I called for supplies and got the reply that it was not
avail because we had no CO. Ok, fine, having ANYONE who can drop supplies and call in
the occasional arty strike is better than nothing. So after a while of getting the hang
of it, I actually enjoy being commander from time to time, but it's not my first choice,
I like to get out and fight.
But if I'm going to play anything, I like to be the best I can be and learn from my
mistakes and also from other commanders. Here now in no particular order are things NOT
to do as a commander.
1) Do NOT repeat "Enemy infantry spotted" 10,000 times when the UAV is ALREADY TELLING
US WHAT WE NEED TO KNOW!!!
2) Do NOT call out enemy troop locations on the other side of the map when the
information is of ZERO use to ANYONE. Why tell us there are troops in the enemy base in
Karkand if there's nobody within 3 grids of that location and there are NO aircraft that
can possibly benefit from your canny observation skills?
3) Do NOT fire your artillery the split second it becomes available, do your scans and
UAV recon first! If all targets have too many friendlies around, then by all means shell
the enemy arty so you don't have it sitting there doing nothing.
4) Do NOT ignore calls for supplies! This is based on my personal rant of being Spec
Forces on MEC playing Clean Sweep and trying to C4 all the USMC artillery, UAV & Sat in
their base. I called for supplied 5 times, and was summarily rejected even after typing
in team chat who I was and why I need a drop. I had to steal a chopper and fly BACK to
my base to find a support guy to give me ammo. ARG!!!
5) Do NOT ignore calls for health, ammo, or repairs from your troops! All too often
there's nobody around to answer the call, and it's up to YOU to take care of your men. I
don't know how many times the tide of battle has turned by dropping a crate on some
badly damaged vehicles trying to attack / defend.
6) Know you squads behavior! Some will obey orders and communicate effectively while
others are off in another world... I was repeatedly ordered to attack bases on the
opposite side of the map on Clean Sweep last night as USMC spec forces who was attacking
& defending the captured MEC base. The CO on crack was ordering me to attack flags on
the opposite side of the map over and over and over and over... I wish squad leaders
could just mute moron commanders sometimes. Ordering squad #6 (mine) to the opposite
side of the map when I'm obviously doing my job at the enemy base is pointless,
irritating, and a waste of time.
7) Do NOT spend a lot of time if any fighting in combat, your job is to COMMAND not
FIGHT! Sure the occasional flag defend or repair of UAV, Sat or Arty is fine, but you
have no business being up in the front lines unless absolutely necessary. By this I mean
you took over CO as there was none and you needed supplies. I've done this and then
later in the map had mutiny votes called (no doubt from someone who just joined) because
some genius thinks he's the best CO ever and assumes you must be a dolt if you are up in
the front fighting. You wanna lead next map? Fine! But I'll finish a job I started,
especially if the way the battle is going looks like the current strategy is working.
I've had some very gratifying moments as commander where I doled out supplies to those
who needed them most, attacked when prudent, fell back and defended as required, and
never ever give up. I had a USMC team that was behind upwards of 100 points on Gulf of
Oman and slowly and gradually turned the tide and won I think 7-0 at the very end of
time. And of course I've had other moments where I've called in arty on targets, yelled
out warnings, only to have retards drive in under it and then ALL file so the tk/punish
and server kick boots you from the server.
Sigh....
I know there are more, but that's about all I can come up with right now...
ace72
Facebook
Twitter
Instagram