Have we forgotten? - Page 2

**daithi1** · 02-11-2008, 11:46 AM

Quote:

Originally Posted by bulletproofsoldier

I second this observation. On a game when I was commanding on Cebre landing, a sniper was in the base blowing up assets, so i went to stop him... Upon doing so I got warned for CO in battle, thinking nothing of it I went back to work, just to be rushed by a squad moments later, inevitably leading to a battle and me being kicked for CO in battle ;-(. This isn't so much as gripe as it is an example of how things are not always as they seem.

This is an obvious misunderstanding. If you were actually kicked for being a fighting CO the the solution is to get in TS and explain yourself. Rage (I assume it was him) can only go on the reports he recieves in TS so in his eyes youv'e been reported twice for the same offence so you get kicked. If you were in TS you could have explained and averted the kick.

**rage4order** · 02-11-2008, 11:58 AM

There are some very good points being made. Please keep things general in statements, please do not get into finger pointing or he said she said statments. Thanks.

Daithi makes a great point here. When admining while not in game, I can only go on the reports I have. There are times I am sure mistakes are made due to the fast pace of the game. By having our players in TS while gaming, we have the best opportunity to make good reports and have them backed up by others seeing the infraction. If I kicked you it was based off of reports I get and I felt it warranted at the time or I would not have done it. If any admin does something you do not agree with, start a post in the contact an admin forum and we will discuss it there. Also if you have a screenshot or a complaint about any player TG or not, the contact an admin forum is the place for those, we should not be having a public conversation about who did what, it is not what this community is all about.

**skullhedman** · 02-11-2008, 12:55 PM

Quote:

Originally Posted by bulletproofsoldier

I second this observation. On a game when I was commanding on Cebre landing, a sniper was in the base blowing up assets, so i went to stop him... Upon doing so I got warned for CO in battle, thinking nothing of it I went back to work, just to be rushed by a squad moments later, inevitably leading to a battle and me being kicked for CO in battle ;-(. This isn't so much as gripe as it is an example of how things are not always as they seem.

Usually it's someone on your own squad who reports you for being a Fighting CO. Unless the squad who rushed in knew that you would fight back and reported you.

Which is wrong, IMO. I never fight as a commander, but if someone is in my base - or kills me (which means they had to run by me, see my prone and semi-hidden, and the decided to turn and go after me,) I'm going to shoot back. If I it happens again, I report them for camping a UCB.

**MDFubar** · 02-11-2008, 01:09 PM

Commanders are allowed to defend themsleves, but the commander should never have to defend themsleves. You are not allowed to kill in the UCB unless you are fired upon. What this means is that the CO is doing his job and should not be killed by the opposing force unless that CO engages them.
A squad should also not be in the UCB unless it is for the sole purpose of destroying assests.

TS is a wonderful tool, there are many times that Rage will come on and verify what is happening with someone on the battlefield. He has even asked us, as SL's, to warn players or CO's that they are breaking server rules.

If you are a CO and you engage the enemy, you will probably be shot. If you are commanding and someone is in your UCB, then call a squad back to help you. If you are killed while in your CO screen, then I guess you could report that person for killing you.

I urge everyone that is not sure, to PLEASE READ THE SERVER RULES. Refresh your memory, hell I am not sure about certain things at times and have to ask too.

By the way, for the new people here I have bumped the gentlemen's agreement. Please read that too.

**skullhedman** · 02-11-2008, 01:14 PM

Quote:

Originally Posted by MDFubar

Commanders are allowed to defend themsleves, but the commander should never have to defend themsleves. You are not allowed to kill in the UCB unless you are fired upon. What this means is that the CO is doing his job and should not be killed by the opposing force unless that CO engages them.
A squad should also not be in the UCB unless it is for the sole purpose of destroying assests.

I agree. 9 times out fo 10 the CO is standing there doing nothing, or is prone. They're not moving because they're watching the CO screen. Which means that in order to kill them YOU are the aggressor, which is an offense.

In addition to this - if you're a CO, spawn in as an engineer. It only takes 5 - 10 seconds with the repair tool to repair a broken asset. Fix one, check your CO screen, inform your SL's that you're repairing assets, and that if they need you, they must call for something.

**rage4order** · 02-11-2008, 01:35 PM

As a commander you can also drop a supply crate on downed assets to repair them as well, I have done this many times to get my vision back.

**machowner** · 02-11-2008, 01:53 PM

Yea, that CO thing is a pain. If you want to kill the CO however, just blow his assests and stand behind him. I've never seen a CO resist trying to kill me. Then hide and wait for the fresh supply box to drop and reload rdx for round 2 of assest destruction! Another pointer is to blow the SAT scan and UAV first, you can then hide without the fear of the CO spotting you on the scan. Then when you resupply put two rdx on the assest, one on the box, reload and run to next assest and throw rdx on it. Blow those while running to the last assest. This takes up a considerable about of the CO's time and most likely he will ask for help. When help arrives, run!

**Arithea** · 02-11-2008, 02:54 PM

Note to self: While commanding, do not ever turn around. That "I'm being watched" feeling is machowner, and as long as I ignore him, he'll just stand there and not kill my teammates or me.

**Jakaleel** · 02-11-2008, 05:43 PM

Quote:

In addition to this - if you're a CO, spawn in as an engineer. It only takes 5 - 10 seconds with the repair tool to repair a broken asset. Fix one, check your CO screen, inform your SL's that you're repairing assets, and that if they need you, they must call for something.

Quote:

RULES: BF2142 Rules & Guidelines - Conclusion
During an attack on an enemy's UCB, you MAY attack enemy units attempting to repair UCB assets and may NOT spawn camp.

A Commanding Engineer can be potted if repairing assets.

Quote:

RULES: BF2142 Rules & Guidelines Rule 8
8) Commanders MUST make commanding their top priority. Commanders are not to engage in combat unless absolutely necessary.

Allows commanders limited combat, mostly in self defense. EU, on some maps, has no unlock. An enemy prone, obvious, and yakking away is likely the EU commander. Their choices when found are fight & die or run & die.
PAC commanders however should rarely leave the uncap.

02-11-2008, 11:58 AM	#17 (permalink)
rage4order Join Date: Apr 2007 Location: Northern Colorado Age: 38 Posts: 2,668	Re: Have we forgotten? There are some very good points being made. Please keep things general in statements, please do not get into finger pointing or he said she said statments. Thanks. Daithi makes a great point here. When admining while not in game, I can only go on the reports I have. There are times I am sure mistakes are made due to the fast pace of the game. By having our players in TS while gaming, we have the best opportunity to make good reports and have them backed up by others seeing the infraction. If I kicked you it was based off of reports I get and I felt it warranted at the time or I would not have done it. If any admin does something you do not agree with, start a post in the contact an admin forum and we will discuss it there. Also if you have a screenshot or a complaint about any player TG or not, the contact an admin forum is the place for those, we should not be having a public conversation about who did what, it is not what this community is all about. __________________ \|TG-8th\|RAGE *SigPic provided by www.davidclair.com* New to TG start HERE * 8th Mercs * Admin List * Supporting Membership Quote Sc1ence: "My parachute pants are rad! Check out all the zippers!" *****

02-11-2008, 01:09 PM	#19 (permalink)
MDFubar Join Date: Feb 2007 Location: New Castle, DE Age: 40 Posts: 1,545	Re: Have we forgotten? Commanders are allowed to defend themsleves, but the commander should never have to defend themsleves. You are not allowed to kill in the UCB unless you are fired upon. What this means is that the CO is doing his job and should not be killed by the opposing force unless that CO engages them. A squad should also not be in the UCB unless it is for the sole purpose of destroying assests. TS is a wonderful tool, there are many times that Rage will come on and verify what is happening with someone on the battlefield. He has even asked us, as SL's, to warn players or CO's that they are breaking server rules. If you are a CO and you engage the enemy, you will probably be shot. If you are commanding and someone is in your UCB, then call a squad back to help you. If you are killed while in your CO screen, then I guess you could report that person for killing you. I urge everyone that is not sure, to PLEASE READ THE SERVER RULES. Refresh your memory, hell I am not sure about certain things at times and have to ask too. By the way, for the new people here I have bumped the gentlemen's agreement. Please read that 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

02-11-2008, 01:35 PM	#21 (permalink)
rage4order Join Date: Apr 2007 Location: Northern Colorado Age: 38 Posts: 2,668	Re: Have we forgotten? As a commander you can also drop a supply crate on downed assets to repair them as well, I have done this many times to get my vision back. __________________ \|TG-8th\|RAGE *SigPic provided by www.davidclair.com* New to TG start HERE * 8th Mercs * Admin List * Supporting Membership Quote Sc1ence: "My parachute pants are rad! Check out all the zippers!" *****

02-11-2008, 01:53 PM	#22 (permalink)
machowner Join Date: Apr 2007 Location: New Tazewell, TN Posts: 2,723	Re: Have we forgotten? Yea, that CO thing is a pain. If you want to kill the CO however, just blow his assests and stand behind him. I've never seen a CO resist trying to kill me. Then hide and wait for the fresh supply box to drop and reload rdx for round 2 of assest destruction! Another pointer is to blow the SAT scan and UAV first, you can then hide without the fear of the CO spotting you on the scan. Then when you resupply put two rdx on the assest, one on the box, reload and run to next assest and throw rdx on it. Blow those while running to the last assest. This takes up a considerable about of the CO's time and most likely he will ask for help. When help arrives, run! __________________ \|New to TG? Start here\|*\|Become a Supporting Member\|*\|What is Frontlines?\| "Remember to pillage BEFORE you burn!"

02-11-2008, 02:54 PM	#23 (permalink)
Arithea Join Date: Jun 2007 Location: North Port, Florida Age: 25 Posts: 1,785	Re: Have we forgotten? Note to self: While commanding, do not ever turn around. That "I'm being watched" feeling is machowner, and as long as I ignore him, he'll just stand there and not kill my teammates or me. __________________ my tank is burning not an enemy in sight Arithea lurks -Spiff913 WeeWar: Arithea Ikariam: Arithea, Chehios [88:57] Ankh-Morpork, Crystal Glass .....Find me! Send me stuff! ....................... Rhiatheos [88:56] Sto Lat, Wine ...................Find me! Send me stuff! ....................... Echeeos [87:57] Lancre, Marble ...................Find me! Send me stuff!

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Sponsored links

Sponsored links

Sponsored links