Commander - damned if you do, damned if you don't

[Guest]

Archived from groups: alt.games.battlefield1942 (More info?)

"Bryan" <Idontthinkso@tim.com> wrote in message
news:df3jgl$21oo$1@otis.netspace.net.au...
> I noticed something odd the other day. I was Commander and noticed one of
> our guys at an enemy flag. Zoomed in and there he is standing next to 2
> enemy. "Aha!!!" I thought, a conspirator! but then it got wierd .One of
the
> enemy guys jumped into a vehicle (humvee I think) and then OUR guy jumped
> in too. Is this some sort of reverse red tag syndrome that only effects
the
> commander or a hack?
>
> Anyone else seen this happen?

My friend has managed to jump into an enemy jeep once. The driver was
definitely an enemy (and not just a false red tag).

 

[Guest]

Archived from groups: alt.games.battlefield1942 (More info?)

"Kilgaard" <Kilgaard@hotmail.com> wrote in
news:1125534865.94d79a89c0269ba49c3d191cbd8400f4@teranews:

> My friend has managed to jump into an enemy jeep once. The driver was
> definitely an enemy (and not just a false red tag).

That used to be great fun in Tribes 2: Wait at the enemy runway for a
transport to load up with guys in heavy armor (who can't drive because the
pilot's seat won't accomodate heavy armor) and jump in the pilot's seat and
fly it off to some distant corner of the map. Hop out and suicide, leaving
them stranded with no one who can drive.

 

[Guest]

Archived from groups: alt.games.battlefield1942 (More info?)

>ace72ace wrote:
>
>> I know there are more, but that's about all I can come up with right now...
>
>8) Don't switch objectives all the time. Even if an order is not
>perfect, leave it be for a while. Set general objectives, and led the
>squads get on with it.
>
>regards,
>
>Achtung Ecco


I played commander twice (won both times) never gave an order, just
watched the mini map mostly, scanned a few times, used the UAV's and
used the arty to soften up areas I either knew or thought there was
enemy. I found the few times I managed to hit the enemy on the road to
a flag were the most effective. The other players know what needs to
be done by just looking at the map so I don't issue orders.

I was riding atop a tank while commander and had to tell the driver
to stop so we wouldn't be killed by the arty I had ordered just before
I hopped on. That was an order I guess but not issued through the
commander screen. It was fun to sit just outside the base and watch
the defenders blown to bits as they waited for us to come on in.


Arguing on usenet is like competing in the special
olympics, even if you win you're still retarded.

 

[Guest]

Archived from groups: alt.games.battlefield1942 (More info?)

Alleged Accomplice <my_ass@my_chair.com> wrote in
news:9l9si1l1alnql8u5a39sdgl5qt7qsj5bcj@4ax.com:

> The other players know what needs to
> be done by just looking at the map so I don't issue orders.

Not so. I find it frustrating to play for a commander who doesn't let the
SL's know what's going on. Only the Commander sees the whole situation with
the scan map. If a squad takes a point and nothing is happening there, how
does one know whether to stay and push off an attack or move on because no
one's interested in the point? If I know a pad will be heavily-contested
(like the Chinese helipad on Fushe Pass), then I'll recommend to the
commander that I Stay and hold it. But on most maps the Commander has the
Big Picture and should use the orders icons (attack/defend/destroy) to tell
squads at least where to go. Better, add VOIP to explain what they'll see
when they get there. And please don't send a squad all the way across the
map if you can avoid it. A lot of us will be on foot and don't want to
spend the whole mission running from place to place without seeing battle.
Pick a squad that's close by to hit a CP.

 

[Guest]

Archived from groups: alt.games.battlefield1942 (More info?)

ScratchMonkey wrote:
> Alleged Accomplice <my_ass@my_chair.com> wrote in
> news:9l9si1l1alnql8u5a39sdgl5qt7qsj5bcj@4ax.com:
>
>
>>The other players know what needs to
>>be done by just looking at the map so I don't issue orders.
>
>
> Not so. I find it frustrating to play for a commander who doesn't let the
> SL's know what's going on. Only the Commander sees the whole situation with
> the scan map. If a squad takes a point and nothing is happening there, how
> does one know whether to stay and push off an attack or move on because no
> one's interested in the point? If I know a pad will be heavily-contested
> (like the Chinese helipad on Fushe Pass), then I'll recommend to the
> commander that I Stay and hold it. But on most maps the Commander has the
> Big Picture and should use the orders icons (attack/defend/destroy) to tell
> squads at least where to go. Better, add VOIP to explain what they'll see
> when they get there. And please don't send a squad all the way across the
> map if you can avoid it. A lot of us will be on foot and don't want to
> spend the whole mission running from place to place without seeing battle.
> Pick a squad that's close by to hit a CP.

When I am playing commander, I try to avoid interfering, if the game is
going well, and nobody is asking for orders. Then I simply focus on
supporting the team (arty, supplies, spotting sneaky bad guys, etc.).

If I can see that something needs to be done, I will start asking people
to move. Likewise, if a SL asks for orders, I will supply them.

I hate games where squads just totally ignore the commander. In that
case I usually resign, and find another server.

regards,

Achtung Ecco

 

[Guest]

Archived from groups: alt.games.battlefield1942 (More info?)

In article <432ec735$0$94389$edfadb0f@dread15.news.tele.dk>, nospam@nospam.no
says...
> I hate games where squads just totally ignore the commander. In that
> case I usually resign, and find another server.

Nah... grab an armor and start capping yourself 🙂
But oh god when you dont immediatly drop a crate when asked then.
Wining immediatly starts.

--
Tiny Pat