Renegade Public Forums
C&C: Renegade --> Dying since 2003™, resurrected in 2024!
Home » Renegade Discussions » Tactics and Strategies » Beacon-end game etiquette
Beacon-end game etiquette [message #2302] Mon, 03 March 2003 18:14 Go to previous messageGo to previous message
[sg]the0ne is currently offline  [sg]the0ne
Messages: 442
Registered: February 2003
Location: Houston, TX
Karma:
Commander

This is a little off topic but here I go . . . .
I noticed that ppl tend to destroy buildings that have beacons on this -- this is in bad form in my opinion.

For example on City Flying as Nod last night someone had placed nuke @ barraks. I was covering the nuke (on the AGT side) with my flame as I attacked barraks. Now I attacked the barraks until it was down to a sliver of health -- my inention was to let the nuke destroy the barraks (it had less thn 15secs left) but some infi decided he wanted to do it ! What a fucking waste of a beacon !

I think it should become one of the new unspoken rules that when beacon is layed all u should do is cover NOT DESTROY THE BUIDING BEING NUKED. There have been COUNTLESS # of beacons wasted because of this. One of the most common situations is Nod or GDI is down to last building, they get tank rushed and someone plants beacon while they attack the last building. The engies inside realize the futileness of repairing so they stop...health drops, drops, drops, drops the boom - game over. Great - your team won BUT they won beacause of the beacon NOT the tanks. However instead of the beacon planter getting the credits/points the tanks do !!!


yahoo : chapstic25
aim : lamant281
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Engie bomb ! »not what your thinking«
Next Topic: Tactics 101
Goto Forum:
  


Current Time: Sun Feb 16 10:32:58 MST 2025

Total time taken to generate the page: 0.00942 seconds