Command and Conquer: Renegade Official Forums: Tactics and Strategies

Home » Renegade Discussions » Tactics and Strategies » anti-proxy strats

Show: Today's Messages :: Polls :: Message Navigator

anti-proxy strats [message #5730]

Wed, 12 March 2003 03:40

[sg]the0ne
Messages: 442
Registered: February 2003
Location: Houston, TX

Karma: 0

Commander

Never seen a thread on this so here it is :

Point #1
When you have two or more ppl and encounter proxy in a time sentisive situation (APC rush to OB/AGT) rotate who takes mine blast. Try to take out two or three @ per person. Carefull of the lag I've died many times cause of non-realtime movement.

Point #2
The least expensive charator should take it upon themself to be the proxy spounge IMO save they don't have a beacon. This is commonly refered to as 'taking one for the team'. Smile

Poing #3
Proxy does not explode on vehicle contact. There is a 'player area' that trigger proxy, this area size does not change. Meaining the vehicle can safely travel over proxy permitting the player area does not enter the proxy trigger zone. So just because there is proxy doesn't mean you have to plow right through it, there is another option. Smaller vehicles obviously have the less of an advantage here since a higher % of total vehicle size shares space w/the player area.

Thats all I got for now. I'm sure yall have some good tips to share so lets hear them.

yahoo : chapstic25
aim : lamant281

Report message to a moderator

anti-proxy strats [message #5765]

Wed, 12 March 2003 06:35

Majiin Vegeta
Messages: 2186
Registered: February 2003
Location: London

Karma: 0

General (2 Stars)

i normally kill my self in the mines for other people...but when i do....they never succseed in blowing the buildiong up..maybe i should stay alive for once...

Report message to a moderator

Previous Topic:	sniping
Next Topic:	canyon.mix strategie

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Jun 25 11:22:04 MST 2025

Total time taken to generate the page: 0.00950 seconds