 |
07-25-2005, 11:44 AM
|
#1 (permalink)
|
Join Date: Oct 2003
Location: Fort Mill, SC
Age: 34
Posts: 10,844
Tournaments Joined: 0 Tournaments Won: 0
|
RULES: BF2142 Rules & Guidelines
Server Rules
These rules were created to achieve the goals laid out by TacticalGamer's Primer. We strive to have server environment where there is mutual respect between fellow gamers; where the focus of play is not solely on doing what it takes to win, but doing so utilizing real-world combat strategy and tactics rather than leveraging quirks in the game engine.
At TacticalGamer, we also strive to support game play in a near-simulation environment. In this game, that means playing as if you are a soldier in one of two modern, organized militaries engaged in a conventional war in the near future. Some rules are in place prohibit actions that would be out of place in this setting, such as bunny hopping. Other rules exist to encourage sportsmanship and fair play - while certain tactics may be effective in a win-at-all-costs environment, the same tactics often ruin the enjoyment for the majority of players on the server.
1) Teamwork is required at all times
To help facilitate teamwork, all players MUST join a squad. (This rule exists to allow better teamwork on the server - it is strongly advised that players do not attempt to side-step this rule by creating one-man locked squads.)
Being part of a squad means working together towards a common goal - what that goal is, and the method by which a squad attempts to achieve it are decisions reserved for the squad-leader. Squad members are REQUIRED to follow the SL's orders, including deploying with specific kits/roles if requested. Related to this, squad leaders must give orders. Whether it's using VOIP, commo-rose commands, or a combination of both - they must lead the squad.
The commander’s job is a vital one. As such, commanders should focus their attention not on fighting, but on commanding and supporting their team. Commanders should not engage in combat unless absolutely necessary.
2) Audio is required
Every individual must have the capability to hear the voice-comms of other members of his team. While the use of a microphone is strongly encouraged, the requirement is that you have VoIP enabled and can hear your teammates. If you are unable to hear, please contact an admin and inform them of your situation.
3) No Bunny hopping / Crack Jumping
Bunny hopping and crack jumping are terms we use to describe ANY jump or series of jumps that you wouldn't see in real-world combat.
Things that DO NOT break any rules
- Jumping to navigate terrain. A good example of this would be jumping over the railroad tracks on Camp Gibraltar.
- Jumping to get behind cover.
- Jumping to increase the range of a toss (grenade, RDX, mines, PDS, etc)
- Jumping to get on a ladder.
Things that DO break the rules
- jumping to avoid incoming fire
- jumping to make yourself a more difficult to hit target
- jumping around corners in anticipation of hostile fire
4) No UCB Camping
The UCB is designated as a safe area for "reinforcements" to spawn-in, coordinate, and launch attacks. Players may NOT engage enemy 'reinforcements', and may only enter the enemy UCB to destroy commander assets or engage enemy "combatants". (A "reinforcement" becomes a "combatant", forfeiting any special protection, when they leave the UCB or fire out of it). Titan game mode is exempt from UCB egagement and vehicle rules.
Some examples of things that DO NOT break any rules
- Entering the UCB to destroy CO assets and staying to ensure they don't get repaired
- Killing an engineer (or crate) that's repairing CO assets
- Defending yourself from hostile combatants in the UCB that have engaged you or your squad in combat first. It is acceptable to protect yourself and your teammates to ensure the continued success of your mission.
- Chasing a retreating enemy vehicle back into its UCB to kill it
- Entering a UCB during Titan game mode
- Killing any enemy player in the UCB during Titan game mode
Things that DO break the rules
- Entering the UCB with the intent on killing a disoriented spawning player.
- Entering the UCB with the intent of stealing an enemy vehicle. *
* The ONLY exception to this rule is the asset destruction squad. An asset destruction squad may take an FAV when exiting the UCB. However, they may NOT take the FAV and use it to camp the UCB.
- Flying over the UCB for air raids / bombing runs
- Entering the UCB with the intent to lay mines/RDX
- Killing a commander that has not engaged you in combat first.
- Killing reinforcements in the UCB (enemies that haven't yet engaged in combat.)
- Attacking a locked flag in Frontline Assault mode (Currently only applies to the non-Titan Northern Strike, Highway Tampa, and Operation Shingle maps)
- Sitting in a UCB with the only intent to gain kills while in titan game mode
5) No Spawn Camping
Spawn camping is a premeditated act that takes advantage of a newly spawned player's lack of situational awareness. (This is not to be confused with spawn killing. In Battlefield 2142, you chose where you deploy. If you chose to deploy to a flag that is under attack, you should not be surprised if you are killed the moment you spawn.) For clarity, we have included a short list of examples. This list does not cover every case, and is only provided to illustrate the difference between spawn camping (forbidden) and spawn killing (unfortunate, but acceptable).
Things that DO NOT break any rules:
- While attacking a flag, you get surprised by someone spawning and kill them before they move.
- Shelling a flag from far away with no intention of capturing that flag. (not a terribly useful tactic, but it doesn't violate any rules)
- Constantly bombarding a flag from a transport with the sole intention of killing enemy soldiers.
- Placing motion mines on a titan.
Things that DO break the rules:
- Hiding with a weapon aimed at a known spawn point, waiting for players to 'appear'
- Placing APMs and/or RDX on known spawn points
- ANY action that deliberately exploits spawn-point locations
6) No Suicide Tactics
This includes but is not limited to: RDX Jeeps, RDX suicides in the Titan Core room, suiciding with the intention of changing kits, suiciding with the intention of spawning elsewhere on the battlefield, or intentionally blowing yourself up to cause the death or damage of another.
7) Vehicle use is limited to realistic use only
Vehicles should be used for their intended design. We are not trying to limit the imagination, but we are trying to avoid certain behaviors / actions. The following examples are meant to impart the intent of the rule.
Things that DO NOT break any rules
- Running hostiles over in an FAV while traveling from Point A to point B
- Using a transport as a gun platform
- Parking a ground-based vehicle in such a way as to create an obstacle or roadblock
Things that DO break the rules
- Ramming one vehicle into another. For our purposes, ramming is defined as intentionally making contact with another vehicle regardless of whether or not the contact is meant to destroy or damage the opposing vehicle.
- Using a gunship as a transport
- Using a gunship to neutralize or capture a flag.
- Using an FAV for the express purpose of running people over. We refer to this as NASCAR since the FAV is often seen doing laps of the map or sections of it
- Running hostiles over in an FAV while traveling from Point A to point B, missing a few and then turning around with the intent of running the rest over
- Using a drop pod to destroy a gunship or transport
8) Squad Leader Beacons may NOT be placed on any roof or area which is not accessible through ordinary means.
Ordinary means includes both teams having normal access to stairs, ladders and podding via APC or transport. You may not drop a beacon on a surface that can not be reached by any means other than Squad Leader Beacon pods. This does not mean rooftops are off limits, but it does mean you can not pod onto the roof and drop a new beacon up there. If a map has only one transport on it for one team and not the other, you may not drop a beacon on a rooftop.
Last edited by Eroak; 11-09-2009 at 05:24 PM.
Reason: Updated beacon rule
|
|
|
 |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Similar Threads
|
| Thread |
Thread Starter |
Forum |
Replies |
Last Post |
|
RULES: Basic Rules of Conduct
|
asch |
Battlefield 2142 - Server Rules |
0 |
08-04-2005 06:04 PM |
|
|