BF2C || Tour Rules Of Engagement

Tour 17 Rules of Engagement (ROE)

ROE 1. Basis for Rules of Engagement

(a) Battlefield 2 Combat's Tour of Duty, is intended to match two teams against each other on a virtual battlefield using the Battlefield 2 game.

(b) It is the intention of the owners of BF2Combat that each army reflects the structure and organization of a real army.

(c) The ROE is designed to match two 30-player armies against each other in the most realistic setting possible in the virtual world.

(d) The Rules Of Engagement (ROE) are in place to create an equal playing field as much as possible and eliminate glitches and exploits whenever possible.

(e) The ROE may be changed at any time during an ongoing tour and during the breaks between tours in an effort to maximize the Tour of Duty experience.

(f) Any staff member wearing [BF2C] or [CS] tags is the ruling admin on the server at the time he or she is on. Both armies on that server will respect the decisions and rulings made by the admin.

ROE 2. Allowable number of players.

(a) Each team is allowed a maximum of 30 players signed into the battle server at one time.

(b) No team may play with fewer than 5 members in the battle server without declaring that round a forfeit.

(c) No team may play with more than 1 players more than the opposing team in the battle server.

If a army drop's more than 1 under. The admin will ask the over army to adjust it's number's....After the total of 2 mins the admin will kick players to adjust the numbers...

(d) The battle day starts at its allotted time regardless of army numbers.

(e) If a round is forfeit due to one team having less than 8 players signed into the battle server, that team will have 20 minutes until the next round begins. This will continue for 60 minutes, if after the 60 minutes we have not began a round and the team still cannot field a minimum of 8 players. The TA's then have the right to forfeit the day awarding the proper points to their opponent.

a. Point scoring for forfeits under this section shall be the same as described in ROE 15(d).

(f) There is a script designed which will kick any players over the rule described in ROE 2(c).

(g) If the "player over" script is not operating on the battle server the command staff of each army is responsible for maintaining the correct numbers available in accordance with ROE 2(a) and ROE 2(c).

(h) Violations of ROE 2(g) are decided by the staff member assigned to the battle server where they occur.

ROE 3. No all chat during battle.

(a) There is to be no "all chat" on the battle server or Teamspeak server during the times allotted for battle.

(b) If a player "all chats" during a battle on either the battle server of Teamspeak, that player will be banned from the battle server for the duration of that round.

(c) If a player "all chats" between rounds, that player shall be banned from the battle server for the next round.

(d) If a player "all chats" during the last round of the day, that player will be banned from the first round of the next battle day.

(e) If a player "all chats" intentionally that player shall be banned for the remainder of the battle day in which the comment is made plus the entire next battle day.

(f) Repeat offenders of ROE 3(e) may face removal from the Tour of Duty.

ROE 4. Battle scores.

(a) Battle scores are reported by the staff member in charge of each battle server where they are assigned.

(b) Battle scores are reported to the automated scoreboard 3rd round at each territory.

ROE 5. Server crash and/or unplayable server.

(a) If the battle server crashes or becomes unplayable due to an unstable server early to middle of the round, the round will be restarted and the ticket count at the time of the crash or determination of the server being unplayable will not be counted.

(b) If the battle server crashes or becomes unplayable due to an unstable server during the middle or later in the round, the ticket count will be reviewed by the staff member in charge of that battle server.

(c) If a team has a 100 point or greater lead at the time of the server crash or determination of un-playability as described in ROE 5(b) they will be awarded the round and the score will be deemed to be 100 tickets to 0 tickets.

(d) If no team has a 100 point or greater lead at the time of the server crash or determination of un-playability as described in ROE 5(b), the round will be restarted in the same manner as described in ROE 5(a).

(e) No round lost due to a server crash or determination of un-playability will count towards the three (3) rounds at a territory except in the case of ROE 5(c).

(f) The determination of server un-playability is in the discretion of the staff member in charge of that battle server.

(g) The determination of when a round is in the "early to middle" stage is in the discretion of the staff member in charge of that battle server.

ROE 6. Battle day times.

(a) Battle days are on Thursday and Sunday.

(b) Thursday battle days begin at 15:00 PM EST and will continue to run for 9 continuous hours.

(c) Sunday battle days begin at 13:00 PM EST and will continue to run for 9 continuous hours.

(d) No round may start with less than thirty (30) minutes left in a battle day.

(e) If time is lost due to a server malfunction, it is the sole discretion of most senior staff member on Teamspeak at the end of the battle day to decide whether to do one of the following:

a. Consider the time lost and end the battle at the pre-designated time;

b. Continue the battle for an amount of time equal to the amount of time lost due to server malfunction;

c. Allow the two (2) competing armies to make up the time at another designated time

i. Time may be added to the end of the next battle in which the two (2) competing teams are set to battle each other in an amount of time equal to the amount of time lost due to server malfunction.

ii. If the two (2) competing teams are not set to battle each other again before the completion of the current tour, another day may be selected for those teams to do battle in an amount of time equal to the amount of time lost due to server malfunction.

(f) Battle day is defined as the time between the start and end of the battles on Thursday and Sunday.

ROE 7. Spying.

(a) No member may be enlisted in two (2) armies at the same time.

(b) Team switching in game is not allowed.

a. If a member accidentally selects or is automatically placed on the opposing team during or between battles on battle day, that person must immediately disconnect from the server and log back into the server on the correct team.

(c) No member may "jump" into a Teamspeak channel of any other army during or between battles on battle day.

a. Joining a Teamspeak channel of your sister army is not a violation of this section.

(d) If a member desires to speak to a person in any army other than that members sister army during battle or between battles on battle day, that player must have a member of the BF2C staff drag that person into a neutral channel.

(e) If a member if discovered to have "team switched" or "jumped" into the opposing army’s Teamspeak channel during or between battles on a battle day, the player in question will be penalized accordingly.

ROE 8. Map exploits and glitches.

(a) The use of any map exploits or map "glitches" is prohibited during battle days.

a. A map exploit or map glitch is defined as anything that alters game play due to incorrect gaming code or a map feature which has been identified as creating an unintended effect during game play.

(b) If a member is caught using a known map exploit or a known map glitch, the offending member’s team will receive a minus one (-1) round score.

(c) In addition to any team penalty, a member caught using a known map exploit or a known map glitch may be punished individually, which may include banishment from the tournament.

(d) Known map exploit and glitches:

a. Rearming aircraft out of bounds.

b. Spawning on a squad leader who is out of bounds.

c. Hiding in walls or other objects.

d. Shooting through walls or other objects.

e. Dolphin diving (Include link to movie)

f. Inch worming (Include link to movie)

g. Use of an oversized name

h. Use of the grappling hook to access areas inside of buildings not normally available.

i. A person finding themselves accidentally in this situation. Immediately move out into the normal play area, or suicide with the suicide tab button, and not explosives of any type, if its impossible to walk out.

ii. A person found to fire any weapon at all while in this situation will be in violation of ROE 8(a)

i. Purposely and Intentionally switching kits via medic-revive.

j. Purposely maneuvering your body position partially inside a wall/object to use it to shield yourself from grenade/blast damage

(e) The changing or adding of game files as to produce advantages not normally allowed in the game.

(f) Known changes are:

a. Full Auto M16.

b. Gaining access to areas that are out of bounds.

ROE 9. Teamspeak.

(a) Every player who is logged into the battle server on battle day is required to be logged into the BF2C Teamspeak server.

ROE 10. Punkbuster.

(a) If a player is kicked from the battle server for a punkbuster violation, that player will be immediately suspended from play.

(b) If a player has been suspended from play for a violation ROE 10(a), the Tournament Administrators will have 3 days to complete their investigation into the cause of the violation.

a. If it is determined that a player has been kicked by punkbuster for using any type of a "cheat" or "hack" that player will be immediately removed from Battlefield Combat and is not entitled to a refund.

ROE 11. In game name tags.

(A) Every player logged into the battle server during battle day shall place their army name in brackets in the prefix option.

(B) No player with incorrect "tags" will be allowed to remain in the battle server until they comply with ROE 11(a).

(C) The current army tags are as follows:

a. German Heer shall use [GER]

b. Army of the Ukraine shall use [UKR]

c. All Battlefield 2 Combat staff shall use [BF2C] or [CS]

(D) Sqaud names in game shall be limited to Default squad names or Named for the respective Regiment.

a. Failure to adhere will incur the following penalties.

i. Individuals found in non-conforming named squads will be removed from battle for the rest of that Map Set (1-3 rounds) for first infraction

ii. Individuals found in non-conforming named squads will be removed from battle for the rest of the day for 2nd Infraction (On the day)

iii. If an army has more than one action in a day against them for non-conforming named squads each action beyond the first will incur a 300 ticket round scored against them for the day on that map. This will be above and beyond the rounds played.
Play will NOT STOP, the end result of that map WILL be recorded.

ROE 12. Earned unlock weapons.

(a) If available, all earned unlock weapons available on ranked servers are allowed by members during battle on battle days.

ROE 13. Statistical padding on ranked servers.

(a) No member of any Combat Studios Tour of Duty shall participate in "stat padding" while using any name which identifies them as a member of Battlefield 2 Combat.

(b) Any member who violates ROE 13(a) may be banished from membership at Battlefield 2 Combat.

(c) Any member who violates ROE 13(a) will be reported to EA games.

ROE 14. Un-capable flag.

(a) During battle, if a flag cannot be "capped" due to a game glitch, the round will be paused and a the staff member in charge of the battle server where the glitch occurred will discuss resolution of the problem with the two highest ranked members of the opposing teams or their appointees. If a resolution cannot be agreed upon between the two highest ranked members or their appointees, resolution of the problem will be determined by the staff member in charge of the battle server.

ROE 15. Refusing to engage in battle or forfeiting a battle.

(a) No team may refuse to engage the enemy in battle during battle day.

(b) If a team refuses to engage the enemy in battle, the offending team will suffer a ten (10) round deduction from their overall score.

a. The non-offending will be awarded an automatic victory for any round in which it is determined that the enemy violated ROE 15(a).

(c) No team may voluntarily forfeit a battle during battle day.

(d) If a forfeit is declared by rule or army decision, the forfeiting team will suffer a minus one (-1) round deduction for every twenty (20) minutes until the end of the battle day.

(e) Any team who fails to engage in the enemy in battle or voluntarily forfeits a round will be immediately placed under review by the Tournament Administrators.

a. The Tournament Administrators may make any team changes they feel is necessary in order to ensure that ROE 15 is not violated again.

ROE 16. Behavior in game.

(a) During battle day or any other Battlefield 2 Combat event, no player shall use excessive course language. The word filter will ban automatically.
(b) Any offensive comments or comments which place the opposing team in a negative light, will be punished at the discretion of the Admins
(c) Any player, who by their actions, knowingly, or should have known, their actions could cause the other team to commit a violation of the ROE, shall forfeit the round to the opposing team and 300 tickets, and will take the remainder of the battleday off. If there are less than 3 sets left in the battleday, the player will also receive the next battleday off.

ROE 17. Spawn blocking and spawn camping.

(a) No player shall intentionally block a spawn point of the opposing army with their own character or a vehicle.

(b) Any player caught blocking a spawn in violation of ROE 17(a) will be banned from current battleday and next battleday. Repeat offenders can be removed from Battlefield2Combat.

a. If a player is discovered violating ROE 17(a) during a battle, The offending members team shall forfeit the round at 300-0 tickets.

i. If a player is discovered violating ROE 17(a) in a round that has been completed, the non-offending team shall be awarded the victory at 300-0 tickets.

(c) Spawn camping during battle day on the battle server is prohibited.

a. Spawn camping is defined as waiting at an enemy spawn point for the enemy to spawn in for the purpose of killing them before they can react.

i. A player may not place C4 or Claymores on spawn points for the purpose of spawn camping.

ii. Placing yourself in a position targeting a spawn point so that you may kill a person,even after they have moved several steps.

b. The following is not spawn camping:

i. Aircraft bombing or strafing runs at enemy spawn points in capable flags.

ii. The use of artillery on enemy spawn points.

iii. Immediately killing an enemy who spawns in while a player or the player’s team is actively inside the flag radius of an enemy flag

iv. Armor and Attack choppers may set up a perimeter around any control point, capable or un-capable, as long as they are not targeting infantry spawn points.

(d) Any player caught violating of ROE 17(c) will be dealt these punishments:

a. This ROE in and of itself is the only warning anyone will receive. No warnings on battleday.

b. If any players are discovered violating ROE 17(c) during a battle, battle will be stopped and the round awarded to the opposing army at 300-0 in tickets.

i. If any players are discovered violating ROE 17(c) in a round that has been completed, the non-offending team shall be awarded the victory.

ROE 18. Vehicle drop.

(a) Use of the vehicle drop feature from the commander screen is available for use during battle day.

(b) Vehicle drop will not be used as cartillery. They will be used for transportation only.

a. The following will be considered an Infraction in accordance to 18 (b)

i. Dropping a vehicle on enemy assets.

ii. Dropping a vehicle in a runway to impede a aircraft's take off/landing ability.

iii. Dropping a vehicle on an enemy vehicle/aircraft.

iv. Dropping a vehicle intentionally on enemy soldiers.

v. Dropping a vehicle on mines or claymores.

b. Intentionally allowing an enemy vehicle drop to kill you, in an attempt to draw an ROE Violation will be considered itself an ROE infraction in accordance to 18 (b)c. Infraction for violation of 18(b) will be forfeit of the round to the opposing army at 300 - 0 on tickets.

ROE 19. Use of C4.

(a) No player may toss C4 during a battle day on the battle server.

a. This rule is not intended to make illegal the following:

i. Dropping C4 from roof tops, helicopters, or bridges.

ii. Placing C4 on vehicles.

iii. Placing C4 around corners or at flag capture sites.

b. This rule has been added to make illegal the ability to throw C4 great distances and use it much like a grenade style weapon.

(b) Any player caught violating ROE 19(a) will be banned from the remainder of the battle day in which their violation is discovered plus one additional battle day.

a. If a player is caught violating ROE 19(a) after the battle day in which the offense occurred has completed, they will be banned from participating in the next two (2) subsequent battles.

ROE 20.Uncapable Main Bases

(A) Enemy Un-capable main bases are OFF LIMITS to Enemy air assets

i. Infantry may enter main bases

(a) Incursions into the Uncap by air assets will be punished
(b) occupying emplaced assets or stealing assets from Uncap Bases is still strictly prohibited.

ii. Firing From the Uncap (Except Immovable Emplacements) will not be allowed

iii. Firing Into the Uncap Will not be allowed.

iv. Flying over the Uncap will BE PENALIZED

(B) Violations of ROE 20 will forfeit that round with a 300 ticket score for the other team.

ROE 21. Cheating

(A) Something like this should completely go without saying, but cheating in any form is expressly prohibited.

(B)If a member of BF2C is shown by the preponderance of the evidence to be cheating, be it through screenshots, recordings, telltales from server logs, or what have you, the resolution will be expulsion of the member, permanently.

(C)Any sort of cheat, is grounds for removal.

• wall hack
• use of the X-Fire crosshair overlay
• aimbot
• skin hack
• speed cheat
• macro
• or something that manipulates,to cause an unfair advantage,
  • the server
  • client
  • or protocol between them

(D) DO NOT CHEAT!!! It should not need to be said or spelled out, but now it is.

(E) If you are ever caught cheating on public servers, in a clan match or scrimmage, during a battleday, or anywhere for whatever reason, you will be dismissed permanently.

(F) There is no "hoho, I was just kidding" or "rats, I won't do it again." BF2C members do not cheat.

(G) Upon review of battleday recordings any person found more likely than not to be using macro's for TVG or any other purpose can be subject to a ban IAW ROE 21 (E)

ROE 22. MAP ISSUES

A. Map changes will be released at least 3 days prior to battleday to allow armies to check vehicle spawns on both the Day 1 and Day 2 version of the map.
B. Any problems with the map must be reported no later than 24 hours prior to battleday
C. If no proiblems are reported the map will be played as is!!!
D. Situations that can cause the map to be skipped:

i. CTD Issues
ii. issues with a map that was changed less than 3 days prior to battleday

Multiple Individual ROE Infractions.

Multiple Infractions of any ROE will earn vacation time for the individual.

3rd infraction will earn 1 week suspension
4th infraction will earn 3 week suspension
5th infraction will earn 12 week suspension
Any infraction of Any ROE after the 5th infraction will earn a 1 year suspension


This ROE is subject to change or modification without Notice

ROE 20 re-written with DoD taken into consideration.

ROE 20 (A) subection (i) has been clarified with the addition of articles (a) and (b)

Removed UN Observer Kit
Added Map Issues ROE to clarify the standard that has been in practice for more than 6 tours now.

Due to the added semi-auto sniper rifles in POE, ROE was updated and snipers are no longer exempted from spawn camping rule.