Re: Main Server Map Schedule Changes:

**daithi1** · 03-30-2008, 03:18 PM

Originally Posted by INSUNABULA

And so then what happens when the player count starts to rise without anyone knowing, an admin pops in to see what's happening and had to start posting warnings which the CO shouldn't have to pay attention to if he/she is doing the right thing in the first place.

You check tab frequently and make your way to uncap/safe place when player count becomes to high... Well that'd be me anyway.

**Uranium - 235** · 03-30-2008, 06:23 PM

Originally Posted by daithi1

You check tab frequently and make your way to uncap/safe place when player count becomes to high... Well that'd be me anyway.

Aye, I was keeping an eye on the squad tab, because I had two squads eventually and couldn't figure out how to automagically drop supplies on someone's head so I had to manually look at who asked and where they were so I could drop them

**DaBrit** · 03-31-2008, 01:09 AM

Originally Posted by Augustus Gloop

Commanders must do everything in their power to stay safe. They must stay in their UCB if possible, and MAY NOT defend it from anyone entering. If they are killed within the UCB they should report the player killing them to admins.

As a CO, if I see one hostile in my UCB (blowing assets, not stealing / base camping), and I know that there is only one guy, and he most likely has no idea where I am whereas I will know where he is, it seems like an absolutely terrible command decision to recall a full squad to the ucb to deal with one enemy. I'm pretty certain I have seen other rule enforcers say that it is okay to kill people in the UCB as the CO. I feel like the TG rules should be promoting teamwork, not getting in the way of an effective teams operations. Further, on many maps, the time it takes to get a squad back to the UCB would give the one bad guy enough time to blow up at least a couple assets, crippling the COs ability to command while the defending squads are recalled back to the UCB.

**pred011586** · 03-31-2008, 01:25 AM

If the CO is in the UCB, and there's an enemy there. I can't see it being easy to determine when the CO is fighting for his life and defending his assets. The CO knows if he's just fighting back, and the recon blowing up assets knows he wasn't fighting the CO. But is there even a way for the admins to tell the difference? (unless of course their playing, then they can just go DL the BR files).

I've never admined a game server of any kind, so I have no idea what's possible and what's not =(.

**machowner** · 03-31-2008, 01:34 AM

Originally Posted by DaBrit

crippling the COs ability to command while the defending squads are recalled back to the UCB.

This is pretty much what I was going to point out. If a sniper comes back into the base and blows assets your pretty much useless. With no orbital, Sat-track, and UAV you can't reasonable tell squads where to go. Sure you can zoom in on an area, but you can't tell your guys if someone is going to be coming from the North, East, etc. Just as a side comment, I never shoot in the UCB without being shot at first and I know I have been killed more than a few times by admins who were commanding, something about that active camo that makes guys trigger happy, lol.

Originally Posted by pred011586

If the CO is in the UCB, and there's an enemy there. I can't see it being easy to determine when the CO is fighting for his life and defending his assets. The CO knows if he's just fighting back, and the recon blowing up assets knows he wasn't fighting the CO. But is there even a way for the admins to tell the difference? (unless of course their playing, then they can just go DL the BR files).

I've never admined a game server of any kind, so I have no idea what's possible and what's not =(.

Its not super easy, but easy enough. Over 90% of time a number of guys in the server are also on TS. All an admin has to do is ask if the commander is fighting in the field or back in the base killing a sniper.

**pred011586** · 03-31-2008, 02:02 AM

Well, I meant like, is it easy to tell the difference between:

A.) CO killing Recon in UCB to protect assets.

B.) CO killing Recon in UCB to protect himself.

I believe, unless I'm misunderstanding, that Case A is not allowed, but Case B is.

**Uranium - 235** · 03-31-2008, 02:31 AM

Were you to follow the rules precisely, you could get some crazy Mexican Standoff going on there....

**MDFubar** · 03-31-2008, 08:56 AM

The rules are put in place to govern the way our server runs. These rules help to ebsure that we have consistent playing and governing condidtions, day in and day out. The admins enforce to rules, they make the rules, and only they can change the rules.
8 V 8 shouldn't require a CO in the first place, you would be much more effective running a squad until it fills up. Once the server restarts and goes live(no longer waiting for players), then it is live and the rules are also in effect.
What happens when you tell someone that they cannot fight and command at the same time, then they respond with "*****TG was doing it earlier and it was ok".
Understandably that the server is not at it's best when it is unbalanced, but that doesn't mean you ignore the rules. When you put on the TG tag you have decided to follow the rules and set the best example possilbe, not just in our server...but anytime. We lead by example, people join and follow because they like the structure.

As for the commander thing, I see it like this: Someone attacks the UCB and you feel that you should defend it. As soon as you engage that hostile, you are now free game and can be killed. According to our rules, the Co may not be killed unless he engages first. Are you more valuble as a fighting CO trying to defend your assets and possilby ending up dead? Are you more valuble calling for 1 or 2 Sm's from a squad to come and help you?
CO: " I need help at the UCB, please have someone spawn here ASAP" That being said to all squads should have the SL's instructing that to be done.
I too have been a fighting CO, usually with only one other person in the server that happend to be TG. We had fun orbitalling each other while trying to fight in tanks. But, as soon as other people started in, it stopped.

Please just keep in mind that when wearing the TG tag, your are looked upon as an example to follow.

Sorry to go off topic. The mix-up with the maps is great! Uranium, thanx for bringing it to the attention of the admins.

**sc1ence** · 03-31-2008, 02:09 PM

While some of us could command effectively while fighting, the majority can not. The role of a CO is to command. The spirit of the rule here is to have COs that are commanding the game not fighting the battle.

If the player count is low, the rules do not change. But I suspect most admins would not do much about you engaging a single person that was attempting to destroy your assets - even if the server was full.

We do enforce our rules, but not blindly.

**Kaboodles** · 03-31-2008, 04:22 PM

There have been some situations where I, as commander, have been forced to dirty my hands with a little killing. In low-pop situations where we find ourselves without a commander, and I take on the role while sitting in a capture-able base, I'm not going to waste time hoofing it to the UCB. I'll drop whatever useful items I have on my person (Mines, IDS, etc.) and put myself in a safe spot within a grenade's throw of the flag. If I find myself with a some unpleasant persons visiting my house while my friends are out, I won't pass up the opportunity to show them the door with a few grenade throws after informing the squads of their presence. Or an orbital, if it's not needed elsewhere. Or both.

If I succeed, I've just stopped or considerably delayed an enemy attack on the flag, and if I bite it, I'll respawn at the UCB after 15 seconds and continue my duties from there, hopefully undisturbed. The squads already know where the enemies are. They'll know what to do in the meantime.

**Uranium - 235** · 03-31-2008, 08:06 PM

Originally Posted by sc1ence

If the player count is low, the rules do not change. But I suspect most admins would not do much about you engaging a single person that was attempting to destroy your assets - even if the server was full.

We do enforce our rules, but not blindly.

Yeah but according to the rules, I wasn't actually breaking them, as the game was extremely small... so why are we still arguing about this?

**twiddilywink** · 04-13-2008, 11:14 PM

Sweet, i finally found this post!! is this still accurate?

**sc1ence** · 04-13-2008, 11:22 PM

Originally Posted by Uranium - 235

Yeah but according to the rules, I wasn't actually breaking them, as the game was extremely small... so why are we still arguing about this?

Since this was bumped I should point out that shortly after I typed that messaged we change the rule from:

Rule: Commanders MUST make commanding their top priority. Commanders are not to engage in combat unless absolutely necessary.

to

Rule Commanders MUST make commanding their top priority.

There was some discrepancy in how admins were enforcing the rule. We are now on the same page. This discussion was quite helpful in clarifying the enforcement of the rule for us.

The map cycle listed here is still in effect.

**Basic1** · 04-16-2008, 07:08 PM

tampas only in the list once, its a good map should be in there more is all i can say... good rotation though.

**draeh** · 04-22-2008, 09:14 PM

Originally Posted by Augustus Gloop

We will play each map ONCE, then move on to the next...

This change alone is very refreshing.

Sorry to necropost, but I haven't been playing 2142 for a while.... well since the BFCL 5v5 championship anyway.

Thread Tools

Display