http://www.bmhq.net Kill or be Killed Born MurdererZ Born MurdererZ Evo RSS Parser 60 http://www.bmhq.net/images/evo/minilogo.gif http://www.bmhq.net 94 15 Nuke-Evolution Xtreme Powered Site en-us webmaster@bmhq.net 2010-09-06T14:11:58-05:00 hourly 1 2010-09-06T14:11:58-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=673#4710 4710@http://www.bmhq.net Led Zepplin Prodigy 2010-04-26T19:30:59-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=670#4709 4709@http://www.bmhq.net new add on 2010-04-26T18:35:57-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=671#4703 floating on the UAV]]> 4703@http://www.bmhq.net Funny bc2 screenshot 2010-04-25T00:49:09-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=667#4694 4694@http://www.bmhq.net weapon tweaks 2010-04-21T22:44:19-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=663#4685 ]]> 4685@http://www.bmhq.net Hey guys! 2010-04-19T23:15:23-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=664#4677 ]]> 4677@http://www.bmhq.net funny 2010-04-17T22:32:28-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=662#4676 4676@http://www.bmhq.net kinda interesting 2010-04-17T17:58:10-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=647#4663 4663@http://www.bmhq.net name the server 2010-04-14T13:14:25-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=655#4624
General

-General:
Below you will find a list of information informing you how to do various simple tasks here at TeamWarfare. Click the relevant link below to view the specific details.

*CLICK TO EXPAND*

[+]   Join a Ladder/League/Tournament
[+]   How to join a Ladder

Only a Team Founder can do this
# Log In to you TWL Account
# Navigate to your team page HOME --> MY TEAMS
# Click Join New Competition
# On this page you have the options to join a ladder (power & rung), league or tournament
# Click on the dropdown for the rung based ladders.
# Find your game, and select the specific ladder.
# Click "Join Ladder"

[+]   How to join a Player Ladder

# Log In to you TWL Account
# Click on Home
# Click on Account Maintenance
# Click on Profile
# Click on Join A Ladder
# Find your game, and select the specific ladder.
# Click "Join Ladder"
[+]   How to join a Power Ladder

Only a Team Founder can do this
# Log In to you TWL Account
# Navigate to your team page HOME --> MY TEAMS
# Click Join New Competition
# On this page you have the options to join a ladder (power & rung), league or tournament
# Click on the dropdown for the power ladders
# Find your game, and select the specific ladder.
# Click "Join Ladder"
[+]   How to join a League

# Only a Team Founder can do this
# Log In to you TWL Account
# Navigate to your team page HOME --> MY TEAMS
# Click Join New Competition
# On this page you have the options to join a ladder (power & rung), league or tournament
# Click on the dropdown for Leagues
# Find your game, and select the specific league you wish to join.
# Click "Join League"
[+]   How to join a Tournament

# Only a Team Founder can do this
# Log In to you TWL Account
# Navigate to your team page HOME --> MY TEAMS
# Click Join New Competition
# On this page you have the options to join a ladder (power & rung), league or tournament
# Click on the dropdown for Tournaments
# Find your game, and select the specific tournament you wish to join.
# Click "Join Tournament"

[+]   Challenge Another Team

# Only a founder, or team captain can do this.
# Log In to your TWL Account
# Navigate to your team's page (Home --> My Teams)
# From your team page, click "Admin Panel" for the ladder you wish to challenge in.
# You will see a list of teams available to be challenged.
If you do not see any teams, there is either no teams that are available to be challenged, or your team does not have the required roster to submit a challenge
[+]   Contact an Admin

There are a few ways to contact a TWL admin. The best and quickest way is through IRC. If you do not have IRC, or have never used it before, Teamwarfare has a simple Java based web client on the TWL Site.

Please use this link: TWL IRC Support

If you are using your own IRC client, the server and channel information are listed below:

-IRC Channel Info:


• Server: http://irc.Gamesurge.net
• Channel: #twl_bf

This channel is open to all of the Battlefield TeamWarfare Public Community. TWL BF Admins are logged in 24 hours a day 7 days a week to help resolve any issues that you may have while competing on the TWL BF Ladders and Leagues. The majority of all disputes that are submitted could have been resolved if a member of the team had logged in to IRC and requested an Admin to join the server. We encourage the community to take advantage of this by logging in and typing !admin BC2 in the lobby. This is what we are here for, to help you.

-TWL BF Admin Contacts:
A complete listing of TeamWarfare's Battlefield Admin Staff can be found by clicking here.

Please include "Battlefield" and "TeamWarfare" in the subject line to avoid having your e-mail caught in a spam filter.

-TeamWarfare Match Observation:
TeamWarfare Admins are available and are a key element for matches and minimize the possibility of the match ending up in a dispute. Please be kind and courteous to the TWL Admins assigned to the match. The role of an observer is to:

# Spectate all members on both teams
# Take a Screen Shot of PBGUID's
# Screen Shot final scores on each side
# Make any decisions before, during, or after a match


If you would like to request an administrator to observe your ladder match please email BC2NALadders@teamwarfare.com with the following information.

If you would like to request an administrator to observe your league match please email BC2NALeagues@teamwarfare.com with the following information.

# Your Team Name & Opponent's Team Name
# Which Ladder or League this is for
# Match date/time - Server IP & password
# A link to your team profile on Teamwarfare


Please send all comments and/or complaints to:
# Ladders:BC2NALadders@teamwarfare.com or
# Leagues:BC2NALeagues@teamwarfare.com
[+]   Add your Anti Smurf In Game Identifier to your Profile


-How to Acquire your GUID's and Anti-Smurf IDs
PB GUID's are required to be in your personal profile on Teamwarfare for all Ladder and League participants. You can add your GUID to your profile in the following way:

# Open Battlefield 2, join a server (one with Punkbuster running), hit the "~" key and input /pb_plist in your console. Take note of the last 8 alphanumeric characters of the 32 alphanumeric characters displayed. This is your PB GUID. This is all you will need to input into your profile.

# Once you have captured your PB GUID go to Account Maintenance ---> Profile ---> Anti-Smurf In Game Identifiers ---> Add another ID. Add the last 8 alphanumeric characters of your GUID in the window there. If you have trouble doing this, clicking your name on your team roster page will bring you to your profile.





↑Top


Game Play Basics

-Gametype Specifications and Concept:
Below is a list of simple information for match play on TeamWarfare. Click the relevant link below to view the specific details.

*CLICK TO EXPAND*
[+]   Game Modifications and Current Version

Game Modifications and Current Version

-Current Version: v1.00

-Current Mod: No mods are currently approved for match play

-Server Requirements: A server capable of handling 2 more players than the format you are playing is to be used (eg. For 8v8, an 18 slot server is required). The server must be located in North America, running in dedicated mode, and using the currently approved TWL game version and/or mod.
[+]   General Ladder Rules

-Round Start Procedure:
Each round for all of the ladders will be started in the same way. Once the map is reset at least one player from each team will load into the map equipped with the kit they plan on playing with. These players are allowed to move around in the spawn area but may not enter any vehicles.

Once at least one player from each team has loaded into the map they will acknowledge that their team is ready to play via global chat (all of their teammates are at least loaded into the kit selection screen). At this time at least one player from each team will open the large map ("M" key by default) and the defending team will state the following in global chat:

"TWL XvX Match mm/dd/yy"

"Ready"

"Go"

The attacking team will respond with "Go" at the same time and the match will go live.

The goal is for each team to capture a screenshot including the date, the map, and both teams stating "Go". These screenshots must be made available to the other team within one hour of match completion, but only if the other team requests them either prior to the match in match comms, or in the server at the conclusion of the match. Teams may use e-mail to transfer screenshots.

Please keep these screenshots no less than two weeks after each match. Failure to provide them to a TWL admin upon his or her request may result in a forfeit loss.

The defending team is the team who received the initial match challenge.

-Match Reporting:
One of the losing team's captains, or the founder, should report the match results within one hour of the match ending via the 'Report Loss' button in the match admin panel unless they intend to submit a dispute. In that case, they should report the dispute within one hour using the 'Dispute Match Results' button.

-Sportsmanship:
All members of all squads are responsible for treating each other with respect during the match. Due to the lack of a language filter, please respect those in the server at all times and please don't be careless with your language. Sportsmanship rules are not limited to communications made within the server, but also apply to match comms.

-Player Drops and Substitutions:
If a player should be disconnected during live play, he may immediately rejoin the server if possible. If he is unable to, then a legally rostered player is allowed to join in order to take his place. Live play does not stop during this time.

Substitutes may be brought into the server between rounds provided they do so in a timely manner and are legally rostered.

-Voice Over IP (VOIP):
VOIP will be not be required to be enabled on match servers. Both teams may agree to use VOIP but only by both parties consenting in 'match comms'. TeamWarfare will not rule on disputes that involve VOIP.

-Team Size:
Each team is to fill the minimum number of players for each ladder. If a team is unable to meet this requirement then the offending team must forfeit the match and report it immediately. However, if the opposing team agrees, then re-scheduling the match to a later date is an option. In this case, both teams should post immediately in match comms indicating this decision.

If neither Team is able to field the minimum number of players by match time, or within the grace period (+15 minutes after the schedules time), the match will need to be rescheduled or killed unless both teams choose to play the match with less than the number of required players.

Matches may be played with uneven numbers in cases where one team is able to field the minimum but not the full roster against a team who does have the full roster. The team with a full roster may play with an advantage so long as they like. Teams may bring in additional players during a live round so long as they do not go over the full roster limit and the other team is given a chance to verify their legality following the round.
[+]   8v8 Conquest Ladder

8v8 Conquest Ladder-Format:
Type of Gameplay: Conquest
Number of Maps: 1
Number of Teams: 2
Members per Roster: 20
Members per Match: 8 (6 minimum)
Rounds: 3 (Best 2 out of 3)
Friendly Fire: On
3D Spotting: Off
Vehicle Third Person: On
Crosshair: On
Kill Cam: Off
Hardcore: Off
Minimap: On
Minimap Spotting: On
Map Selection: Randomly selected by site
Side Selection: Attacking team gets round 1 side selection
Server Selection: Defending team gets server selection if both teams are capable of providing a server

-How You Win:
Matches consist of three rounds with each team playing at least one round on both sides. The attacking team will have first round side choice and then teams will switch sides for the second round*. The team with the highest score at the end of the round is the round winner.

Matches are scored based on rounds won, not total scores. Thus, the match winner will be the team who wins more rounds at the conclusion of three.

The third round does not have to be played if a team is able to win the first two rounds.

There are no limits on classes or how many of each class may be used by a team at any given time.

* For the third round, the team with the highest combined score between the first two rounds will have side choice. In the event of a tie, the defending team will take side choice.

-Round Scoring
After each round both teams should announce what they believe the final score was prior to starting the next round. Most likely the scores will not differ more than 3-5 tickets*. If both teams are not in perfect agreement, just note the differences and contiune.

Play the next round and again do the same thing. If a third round is needed take both scores, add them up, and give the winner side choice. Use the score that gives each team the highest total possible from both rounds. Usually, one team will have a significant advantage regardless of the minor discrepancies.

However, if it is a close match, and the discrepancies will place one team ahead of the other, go look at the screenshots your team has of each round. If both teams have screenshots of the same round, the one with less total tickets will take precedence.

For example, Team A took a screenshot when it was 5-2 (in favor of Team A), Team B has one of 2-1 (in favor of Team A); Team B's screenshot will be used and a +1 ticket advantage will go to Team A for that round.

If your team does not have a screenshot then the other team's screenshot will be used by default.

It is not neccesary for teams to submit their screenshots to the other team for review prior to the third round. We are working on the honor system here. However, after the match is over teams should submit screenshots claimed for scoring purposes to the other team at their request. If a team fails to do this then the other team may submit a query to the admins and then they will ask for them. Failure to provide it to the admin will result in a forfeit of the match (retroactively) and competition suspensions. If you claim to have a screenshot of the score at XX-XX then you should be 100% sure your team has one.

Screenshots should be kept no less than two weeks after a match is played. Failure to do so may result in the match being forfeited.

* If there is a difference of 12 tickets or more in what each team claims, then a screenshot should be reviewed immediately before beginning the next round. This should not take more then 5 minutes.

-Server Crashes:
In the event of a server crash during a round the round should be replayed. All previous round results will stand.

In the event of repeated server crashes (2) the other team's server, or an alternate server, should be used. The match will resume and the previously completed rounds will stand.

If one team has a 35+ ticket advantage and the other team is at or below 25 tickets when the server crashes then the round will be counted as a win for the team who was winning. Screenshots will be neccesary for proof.

-Team Captains
Teams founders are allowed to appoint a maximum of three team captains for this ladder. If we catch a team with additional captains then we will randomly remove the excess captains' status and may kick players if it becomes a persistent problem.


-Demo Recording:
Please click here to refer to the demo recording requirements.


[−]   4v4 Squad Rush Ladder

-Format:
Type of Gameplay: Squad Rush
Number of Maps: 2-3
Number of Teams: 2
Members per Roster: 10
Members per Match: 4 (3 minimum)
Rounds: 2 per map
Friendly Fire: On
3D Spotting: Off
Vehicle Third Person: On
Crosshair: On
Kill Cam: Off
Hardcore: Off
Minimap: On
Minimap Spotting: On
Map Selection: Randomly selected by site
Side Selection: Attacking team gets side selection on the first two maps. The defending team will have side selection on the third map if it is neccesary
Server Selection: Defending team gets server selection if both teams are capable of providing a server

-How You Win:
Matches will consist of two teams playing two maps. Each team will play as the attacker and defender on each map. If the teams are tied after both maps (4 rounds), then play will resume on a third map.

Scoring will be done as follows:

Blowing 2 MComm stations = 2 points
Blowing 1 MComm station = 1 point
Blowing 0 MComm stations = 0 points

Matches will be scored based on total points, NOT rounds won.

-Overtime (3rd map)
The defending team will have side selection for the first round of this map. Teams will play a two round series until one team is able to blow up more stations than the other. Each team will have the opportunity to play as the Attacker and Defender at least once in each series.


↑Top


Founders/Captains

-Founder/Captain Responsibilities:
Below are the things you should know as a founder/captain of your team. Click the relevant link below to view the specific details.

Note: The term Captain also includes the founder in this section.

At TeamWarfare we hold a team's captains and founder to a higher standard. If you do not think you can act in a manner fitting of a team captain then ask the founder to remove you as such. Otherwise, Your actions will be scrutinized much more closely.

*CLICK TO EXPAND*
[−]   Responsibilities

Responsibilities

-Accepting the Match:
To challenge a team you must log into your team's Admin panel, also see Ladder Movement. To challenge a team you must log into your team's Admin panel, also covered in Ladder Movement. If you are challenging a team you are considered the Attacker of the match. The team being Attacked is referenced to as the Defending team. Once attacked the Defending team has 48 hours to respond to the challenge of the Attackers by selecting two different dates and two different times for the Attacking team to then select from. The Attacking team will also have 48 hours to lock in a date/time. Failure to complete either step of this process within the allotted time may result in a forfeit loss. Teams may agree to reschedule the match at any time as long as both teams post this agreement in match comms.

If the Defending team does not accept the match within 48 hours then this will result in the Defending team forfeiting the match and being dropped 10 rungs. The Attacking team will also take their rung.

If the Attacking team does not accept a date within 48 hours of them being issued, then they will also forfeit the match and lose 10 rungs.

Note: This type of forfeit loss will not count toward either team's record. They are called 'llamas' and are displayed inside parentheses next to a team's name on the ladder.

Teams that forfeit matches in this manner will be notified by the TWL auto mailer system. Teams that receive more than 2 llamas in a row for inactivity may be removed from the ladder.

-Eligibility for Match:
All Players must be registered on their team's roster with their correct (game specific) GUID listed in their profile the day before the match. This means as long as they are on the roster by 11:59 pm est the day prior to the match, they are eligible. Exceptions may be agreed upon in match comms or in the server at match time.

-Roster PBGUID checks:
It is the Captain's responsibility to check their opponents roster and verify PBGUID's before the match begins. Should the Captain ignore this and begin the match, then he is authorizing any otherwise illegal players currently in the server to play.

-Screenshots of the Score:
Periodically you may need an Admin to finish the match results. Every Admin must be able to verify the scores in order to report the match as completed. It is the Captain's responsibility to take screenshots at the end of each half so the score can be verified. Without screenshots, regardless of the match outcome, the match may be nullified.

-Reporting Match Results:
It is the Captain's responsibility to accurately report the match results in a timely manner. The Team Captain of the losing team MUST report the match results NO LATER THAN 1 HOUR after the completion of the match. Teams who fail to report match results accurately and in a timely manner will be punished in the following manner:

   * 1st Offense: Loss of 10 rungs and a TWL issued warning.

   * 2nd Offense: Loss of 25 rungs and a TWL issued warning.

   * 3rd Offense: Team is removed from the ladder.



NOTE: It is the winning team's responsibility to ensure that the match score is accurately reported and submitted in a timely manner. If the opposing team fails to report the match score, it is then the winning Team's responsibility to file a dispute indicating the losing team failed to report a loss. They must also be prepared to prove their case.

↑Top
[−]   Team Rosters and Player Eligibility

Team Rosters & Player Eligibility

-Joining a Ladder:
If you would like to join a Battlefield Ladder competition with Teamwarfare then please follow these steps.

  1. Log in under your registered Account.
  2. Under the top left hand corner of the site select your name.
  3. Scroll down to "Account Maintenance" tab.
  4. When the menu expands highlight and select "Register Team."
  5. Fill out as much information about your team as possible.
  6. Once team is registered you should be redirected to your new TWL team homepage.
  7. In the middle of the screen you will see a panel labeled "Team Administration"
  8. Click on "Join New Competition".
  9. Look for the drop box labeled "Join A Rung Based Ladder With ."
 10. Select the Battlefield Ladder you want to join from the drop down menu..
 11. Congratulations you have successfully added your team to Teamwarfare competition. Good Luck!.


-Account/Team Deletion:
If you would like your account or team removed from TeamWarfare please visit Site Support & Member Services and follow the instruction on this thread here.

-Team Name Change.:
If you would like to request a name change for your team then please visit Site Support & Member Services and follow the instruction on this thread here.

See "-Supported Gametypes:" and click on your team's Ladder for specific details of team sizes.

-Substitutions:
Due to the nature of the Internet, it is possible for players to be disconnected or dropped from a server. Should this happen, you may substitute an eligible player to fill the spot or allow the dropped player to rejoin. Once connected, the player must join their respective team immediately.

Due to the sizes of some teams, it is acceptable to rotate players at the beginning of new maps. The team's captain who is making the substitution should notify the other team via global communications. At that time, the other team may ask for time to check if that player is in fact elgible. If they do not request time to check or agree that the next round is live on restart (LOR) then they are voiding their right to dispute the substituted player at any time during the match. Once a player is approved by the opposing team they may continue to play out the match regardless of being rostered or not. However, substitutions should be done in a timely manner that does not hinder the progress of the game. In other words, please have your teammates "waiting in the wings."

After the completion of a round where a player was dropped and a DIFFERENT player filled in the opposing team has the right to verify that any substituted players are legally on the roster with correct GUIDs in their TWL profile.

-Spectators:
The only spectators that will be allowed to watch a match are those authorized by TWL. TeamWarfare reserves the right to observe any TWL match without notification or approval. The Admin's identity can be verified by contacting them on IRC during the match in #twl_bf on Gamesurge. Any attempt to impersonate a TeamWarfare admin will result in a permanent site ban.

-Player Names:
Due to the account system in Battlefield 2 please have your name be similar to that of your Teamwarfare account.
Examples:


   * If you are registered to Teamwarfare as Player1 and a member of Team 123 then your registered name in game should be something such as 123|Player1, Player1, etc. This is so that it is easy to recognize which player is which.

     It is understood by TWL that some players add special characters or numbers after their name to register. Please use common sense when determining who players are. Should you have any questions and/or concerns, please contact an Admin.

     If there is any doubt as to the identity of the player in question match their in-game GUID to the GUID on their Teamwarfare profile for final verification.

     ↑Top

[+]   Match Comms

Match Comms


-Match Comms:
ALL match communications MUST go through the Teamwarfare Match Communication system. This can be accessed by team Founders and Captains via the Admin Panel link in the Team Administration section of their team's page. Issues discussed in Match Comms should be Server IP(s), passwords, match settings, scheduling times, or any other relevant match specific information.

Abuse of the Match Comms system is grounds for a competition suspension.

NOTE: TWL Admins use the Match Communication system when verifying information regarding disputes and general match inquiries. If teams have not communicated in Match Comms, any disputes relating match specific issues, other then cheating or smurfing, may be summarily dismissed by an admin because of an inability to validate such problems.

Communications made outside match comms, or the match itself, will not be considered when ruling on disputes.

-Exchanging Server IP and Password:
The IP and password of the server must be provided to each squad captain 24 hours before the match in match comms. It is recommended that both teams post an IP so that there is an alternate valid server available if needed. Please be sure to pay attention to the score in case of a difficulty on the server and need to change servers, it is important to prevent disputes. If neither team is able to provide as server then the ladder admin must be notified immediately in order to kill the match.
[+]   Filing a Dispute


-Disputes for Cheating Format:
If you feel your opponent was cheating during your match, you must do the following to file a valid cheating dispute.

  1. Take a reasonable amount of time to discuss the issue with your own teammates. Take time to cool off and rationally talk about the issue.
  2. You need to have reasonable evidence to file charges. A text file with information regarding times and players involved it a vital piece of information for use in your dispute.
  3. If you feel you have reasonable grounds, initiate a dispute. List your concerns over specific instances during your match and include these in your dispute.
     Example: At x:xx minutes in the X round, player XXXXX did this. At x:xx in the X round, same player XXXXX did this. etc etc.
  4. Notify your opponent in Match Comms as soon as you dispute so they can get their evidence ready for review. Keep in mind that a disputed team becomes defensive. If your team has a dispute filed against you, cooperation is your best ally in a dispute. DO NOT use the Match Comms to flame the other team for disputing against you.Unsportsmanlike Conduct in Match Comms will result in penalties.
  5. Counter-Disputes - Please do not submit a counter-dispute against a team that has disputed against you. TeamWarfare's investigation of a dispute includes hearing BOTH sides. You will have your chance to supply the Admin handling the dispute with any information you have.


-Examples of Cheating Dispute Format:


   * At approx 7:35 in the first half, |Team|Player3 was able to kill 5 of my team members in a single clip without reloading once in less then 20sec after we all spawned. We suspect symptoms of an Aimbot.
   * {Clan}Player5 was able to come around corners prefiring the weapon on several occasions as if we could be seen through the walls. This happened during the first half at 10:20, 6:50, and 3:23. Then it happened again during the second half at 18:43, 12:08, 10:22, and 5:16.
   * During the first half at approx 5:15 left on the clock, a member of the other team was in the capture radius completely submerged. Please consult our screenshot as evidence of this.
   * At approx 1:01 in the third round during the first half, -=Clan=-Member1 had their tank barrel pointing through a wall and was firing on us, we could not kill his tank because he was protected by the wall.
   * Somewhere around 12:34 on the second round [clan]member7 began to use "all-talk" to type racist insults at our team, please consult our server logs and included screenshots for the evidence.



-General Procedures:
All disputes will be handled by the ladder admin(s). Each and every dispute inevitably involves different aspects and will be dealt with individually. Disputes must be reported to your ladder admin within 1 hour of match end. This is done by clicking on "Dispute Match Results", found in your team admin panel. Disputes must be for a valid and specific reason. Teams must identify 'when and where' the violation occured.

-Report to Match Comms:
In the event of a dispute, teams should check their match comms and team emails often, as the admin may request additional information. Once requested, teams have 24 hours to produce the materials (demos, server logs, screenshots, etc) that the admins ask for. The Admin will have the final say in judging the disputes. This game is meant to be fun, let’s keep it clean and avoid any unwanted hassles.

If a team disagrees with the result of a dispute then they may put together an appeal and send it to the admin team. All appeals will be looked at and responded to.

-Making a Habit of Disputing:
Our concern is to have a fun and clean place to play. Although the dispute process is necessary in helping keep a clean match, teams who make it a habit to dispute often with frivilous reasons will subject themselves to possible suspension, rungs lost and/or league points deducted.

Teamwarfare has zero tolerance for cheating and cheating accusations without an effort to submit any evidence.

↑Top

Technical

-Technical Information:
Below is a list of more detailed information needed to participate here at Teamwarfare. Click the relevant link below to view the specific details.

*CLICK TO EXPAND*
[−]   PunkBuster & PBGUIDs

PunkBuster & PBGUIDs

-PunkBuster Requirement:
All matches are required to be running the most current version of PunkBuster available. Servers that are not running PunkBuster are not authorized to play on. If the hosting team cannot get the server properly working by match start time then the opposing team has server priority.

-Special note regarding PIDs and PB GUIDs
***Your PID (Player Identification Number) is NOT your GUID and should NOT be entered in it's place. PID is for stats tracking only and has nothing to do with your Punkbuster GUID***

-PunkBuster updates for Battlefield 2:
Punkbuster offers a free utility called PBSetup which can be used to update any game that uses Punkbuster. Instructions and download can be found here.

Manual Punkbuster updates can be found here.
-Invalid PB GUIDs:
# Players with invalid GUIDs will have their invalid GUID deleted and be removed from their respective team without notification.

# Teams who let players play in a match with invalid GUIDs will fall under the Smurfing Policy at TWL. It is every teams responsibility to ensure valid GUIDs are entered into each of their players profile.


If a player or team finds other players who are missing or have invalid GUIDs, send an email to BFACteam@teamwarfare.com. Having a valid GUID helps the community to have a fair and balanced game for all teams.

-Master Ban List (AutoMBL):
To take a more proactive stance against cheating, the TWL has approved the use of the Punksbusted.com Master Ban List for match play. Please note, however, that TWL does not provide technical support for the Punksbusted.com MBL nor the AutoMBL tool. To find our more information regarding the MBL and or the AutoMBL tool, please visit PunksBusted.com's website by clicking here.

NOTE: Use of the MBL is not required for TWL matches. Therefore, teams cannot dispute against any other team who's server does not utilize this system, nor force a match to be played on a server that does use it.

-The following is a general guideline on "How to handle GUID issues":
# What do you do if you have entered your GUID incorrectly?

-Enter the correct GUID and then email the Battlefield Anti-Cheat team to request the incorrect GUID be deleted.

# What do you do if you have sold the game or got rid of the game for any reason and wish to have the GUID removed so someone else can use it?

-GUIDs will not be removed so that players can still be tracked in case something appears on the MBL. If you buy a copy that is already registered w/ a GUID, return it and get a new copy. Your best bet would not to buy a used copy.

# What do you do if you have been banned for cheating in Battlefield 2, got rid of the game and wish to have the GUID removed so someone else can use it?

-Email the AC team to find out about your ban and what to do next.


***All emails must contain the following information***
# TWL user name
# GUID Number
# Email must come from the email address on your TWL User Account
# You must be specific in your request.

Competition Manager's List:
# Allen - Allen@teamwarfare.com
# SixShotSean - SixShotSean@teamwarfare.com
# MadChild - MadChild@teamwarfare.com

# Anti-Cheat: blip - blip@teamwarfare.com


Report any current suspected bans/GUID matches to:
BFACteam@teamwarfare.com
[+]   Server Config

Server Config

-Server Settings:
rem *** TWL 8v8 Ladder Match Config
rem *** Last Updated October 29th, 2006
rem *** TeamWarfare
rem *** http://www.teamwarfare.com
rem *** Questions or Issues:
rem *** Email bf2naladder@teamwarfare.com
rem *** IRC: irc://irc.gamesurge.net/twl_bf

rem *** Server Settings - Modify as Needed
sv.serverName "(Clan Tag) vs. (Clan Tag) - TWL 8v8 Ladder Match"
sv.password "Your Password Here"
sv.serverIP "Your Server IP Here"
sv.serverPort 16567
sv.welcomeMessage "TWL 8v8 Match in Progress"
sv.sponsorText ""
sv.sponsorLogoURL ""
sv.communityLogoURL ""

rem *** NAT Settings - Modify as Needed
sv.allowNATNegotiation 0
sv.interfaceIP ""

rem *** TWL Match Settings - DO NOT MODIFY
sv.internet 1
sv.punkBuster 1
sv.allowFreeCam 0
sv.allowExternalViews 1
sv.allowNoseCam 1
sv.hitIndicator 1
sv.maxPlayers 18
sv.numPlayersNeededToStart 2
sv.notEnoughPlayersRestartDelay 15
sv.startDelay 15
sv.endDelay 15
sv.spawnTime 15
sv.manDownTime 15
sv.endOfRoundDelay 15
sv.ticketRatio 100
sv.roundsPerMap 3
sv.timeLimit 1500
sv.scoreLimit 0
sv.soldierFriendlyFire 100
sv.vehicleFriendlyFire 100
sv.soldierSplashFriendlyFire 100
sv.vehicleSplashFriendlyFire 100
sv.tkPunishEnabled 0
sv.tkNumPunishToKick 0
sv.tkPunishByDefault 0
sv.votingEnabled 0
sv.voteTime 0
sv.minPlayersForVoting 2
sv.gameSpyPort 29900
sv.adminScript "default"
sv.timeBeforeRestartMap 30
sv.autoBalanceTeam 0
sv.teamRatioPercent 100
sv.radioSpamInterval 6
sv.radioMaxSpamFlagCount 6
sv.radioBlockedDurationTime 30
sv.friendlyFireWithMines 1

rem *** Global unlocks (disabled)
sv.useGlobalRank 0
sv.useGlobalUnlocks 0

rem *** Demo Recordings (enabled)
sv.autoRecord 1
sv.demoIndexURL http://
sv.demoDownloadURL http://
sv.autoDemoHook "adminutils/demo/rotate_demo.exe"
sv.demoQuality 1

rem *** Voice over IP Settings (disabled)
sv.voipEnabled 0
sv.voipQuality 3
sv.voipServerRemote 0
sv.voipServerRemoteIP ""
sv.voipServerPort 55125
sv.voipBFClientPort 55123
sv.voipBFServerPort 55124
sv.voipSharedPassword ""
[+]   Demo Recording

Demo Recording

-Demo Requirement:
The team that is hosting the match server is responsible for a demo being recorded for the entire duration of the match (all rounds played). If the visiting team would like a copy of the demo once the match is completed, this request must be made in match comms prior to the start of the match.

The purpose of the demo is to backup any claim or evidence of a rules violation during the match. If a dispute is filed and the demo is requested by the admins to further investigate the dispute, the hosting team will be contacted and must produce the demo within 24 hours. Failure to produce a demo once requested by an admin (not another team) will result if the following punishment:

# 1st Offense - Team forfeits match.

# 2nd Offense - Team forfeits match, drops 25 ladder rungs.

# 3rd Offense - Team forfeits match, drops 100% of the ladder.

# 4th Offense - Team disbanded.


Note 1: Failure to produce a demo does not constitute a disputable item.

Note 2: Demos are to be held no less than 2 weeks after match date.
[−]   Exploits/Cheating/Hacking

Exploits

-General Info:
Exploiting the game is illegal and will be considered cheating if used in a match. Do not assume that the use of a bug or game engine flaw is legal, contact an Admin if you are unsure.

Glitching and Exploiting are very vague terms. All teams reserve the right to make their case against any questionable position that is used in a match. Consult an Admin if you feel there was an occurrence. Our Anti-Cheat team has created a very useful list of definitions. Protect your team from punishment by following these guidelines.

-Map Bugs:
Including but not limited to going under the map and moving through or shooting from places where flaws in the textures allow you to see through walls or other objects.

Cheating/Hacking

-Message from the TWL BF Administration
TWL has a ZERO tolerence policy regarding Game Hacking. This rule covers players who use code to manipulate a particular game for the purpose of gaining an unfair advantage over other teams and players. Wallhacks, speedhacks and aimbots are just examples of the types of cheats covered by this rule.

"Testing" or "Trying out" Hack Programs will not be accepted excuses. Simply put "Do Not Install Hacks for any reason"

-Consequences:
I. Hacker caught in TWL Match:
 A. Forfeiture of the existing game
 B. Player Permanently banned from TWL
 C. Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom

II. Hacker caught in match outside of the ladder/league match or in a match outside of TWL:
 A. Player Permanently banned from TWL
 B. Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom.

III. Hacker caught in a Pub/Scrim :
 A. Player banned from TWL for 1 year
 B. 2nd Offense Perma Banned. This is globally cumulative. A pub ban on two seprate games equals two offenses.

***NOTE- Each individual game has the option of preventing a person from participating in their specifc game that has been caught cheating on the pubs, regardless of how long ago the violation has occured. This will affect that game only. The player will not be site banned/suspended or prevented from playing another game that allows them to, if the violation is over one year old.

Founder's Responsibility & Consequences:

Team founders are responsible for their team's integrity.

Any team that rosters three or more players who get banned for cheating will be subject to removal from competition. This is cumulative and does not mean at the same time, it encompasses the lifetime of your team at TWL.

Any team that harbors players who have been caught cheating may also be subject to removal and the founder/captains banned from playing together for their lifetime at TWL.

As team founder once you have been informed one of your players has been banned for cheating you should change the "Join Password" for your team so that they can not rejoin your rosters. If you as the team founder allow a banned player to circumvent a ban from TWL you as the founder will receive a competition suspension.

-Admin Notes:
TWL will continue to support teams who Police themselves of hackers and cheaters. In the case where a team Purges a hacker from their ranks and brings it to the attention of TWL staff. TWL will (waive the Drop in ladder rungs)

↑Top


↑Top


Changelog

-Change Log:

-Apr 2, 2010
Allen: Added 4v4 Squad Rush rules and the "General Ladder Rules" section.

-Mar 7, 2010
Allen: Adjusted rules in preparation for the initial opening of the 8v8 conquest ladder.

-Feb 28, 2010
MadChild: Initial Rules Template Loaded

Rung Ladder General Rules

Ladder Movement

You can challenge anyone above you 10 slots or 50% of the remaining ladder from your current rank - whichever is higher. (Ex: Rung 100 can challenge rung 50. Rung 48 can challenge to rung 24. Rung 15 can challenge to rung 5).

On some of the smaller ladders, the challenge slots is 5 slots or 50% of the remaining ladder. Check the ladder's specific rules to be sure.

Ladder Concept

The Ladder is based on a best 2 out of 3 maps scenario. Map selection is random for the first and second maps. The "Defending" team selects the tiebreaker map. The "Defending" team chooses map sides and order. The "Attacking" team picks the tiebreaker map sides.

* THIS IS SUBJECT TO CHANGE IN THE ABOVE RULES SPECIFIC TO THIS LADDER

Team Roster Management

Ladder members join teams per ladder and may only be a member of one team per ladder. Roster changes may be made on any day. In order for a player to be considered 'eligible' for a match, he must be on his team's roster before the Defender accepts the challenge and remain on the team until the match is completed. In the case of games with in game identifiers (PunkBuster), this GUID must be entered into the players profile before the defender accepts the challenge for the player to be considered 'eligible'. If a player drops from a team after a challenge is accepted and rejoins he will only be allowed to legally play if the other team agrees to it in match comms. Leniency is given for people that sign up on the same day match is accepted.

Once a team joins a ladder, that team has 2 weeks to bring their roster to the minimum roster requirement for that ladder. Failure to do so will result in immediate removal from that particular ladder.

Team Management

Teams have one (1) Owner and any number of Captains. Captains are assigned at a ladder level. Owners are captains on all ladders. The team Owner should determine who should be in charge of issuing challenges per ladder and maintaining the team information. Multiple team captains can be assigned to perform such duties.

*There are only to be a maximum of 2 captains assigned to any ladder match.

You can only issue a challenge by making it in your Team's Admin Console on your ladder control panel on any day of the week. Access to the Team Admin Console is available to all Captains………… NOTE - You must login to the ladder in order to administer your team.

Challenge and Match Date Acceptance

All ladders have a time limitation for match responses. This includes Acceptance of a Challenge and/or Date Acceptance. The Present time frame is 48 hours. At that time a "Flag" is created for the Ladder Admins to address the next time they login to their Admin Console. If the problem is resolved by that team prior to the Admin logging in then the match continues as before. If the Admin logs in first the appropriate action will be taken. In this case forfeits will be granted and rungs dropped.

It is the each team's responsibility before the match starts to see that all players are legally registered on each teams roster. After match start or completion, roster disputes are not valid justification for forfeiture or admin intervention. Substitute players, brought in during match, that are not eligible players by the above criteria, will force an immediate forfeiture on the part of the team they were playing for.


Match Results Reporting and Disputes

Once a match has started, it is understood that both teams agree to the terms of the match (number of players, time limit, rosters, etc). If there is a disagreement of match terms AFTER match completion, the disagreement will be thrown out.

Match results are to be reported as a loss in your team admin panel or if you are disputing the loss you must login to your team admin panel and select the "Dispute Match Results" link within 1 hour of match end. If disputed it will send an automatic email to your ladder admin. If a team fails to report or dispute the team needs to notify the ladder admin immediately. Failure to do either within 1 hour of match end will result in :

  1. First Offense : Dropped a percentage of total rungs on ladder.
  2. Second Offense : Removed from ladder.

By reporting the results, teams waive their rights to protest (ultimately decided by TeamWarfare Staff). It is also to be known that once a match has been played / reported neither team can attack each other for 7 days.

If match results are being protested, a ladder admin and the opposing team captains must be made aware of the protest within one hour from the completion of the match via the "Dispute Results" link in your admin panel AS WELL AS through match comms. Failure to do BOTH may result in an admin reporting the match.

After a protest has been initiated, both teams have 24 hours to gather evidence. In this time the team being protested against may issue a counter-protest.

ALL match issues should be resolved within 48 hours from match completion.

Failure to Appear

For each ladder there is a minimum number of players needed to proceed with a match. Teams should have the minimum number of players on the appropriate server no later than 15 minutes after the scheduled match time. Failure to meet this requirement will result in an immediate forfeit against the non-compliant party. Both teams should be ready to play no later than 30 minutes from the scheduled match time (Unless agreed upon by both parties). Failure to agree to start the match at this time will result in forfeiture by the non-compliant party. A TWL admin should be contacted immediately (mIRC - #teamwarfare) for a ruling to be made. If an admin isn't available then the match should be postponed, and a dispute must be filed.

Server Selection

Server preference and choices are communicated through the "Match Communication" Portion of your Team Admin Console. All matches must be played on a server that has the ability to be password protected. If a neutral server cannot be agreed upon then the 1st and 3rd maps will be played on the Defender's Choice and the 2nd will be played on the Attacker's choice. All members should be able to connect to the server. Server disputes must be handled before match completion. Disputing a server after a match has been played will result in the dispute being thrown out.

Server selections are bound by a "reasonable difference" in ping. If the average ping differential is substantial, the opposing team has the right to refuse a server, provided there is a viable alternative server open for match use.

Inactivity

Teams of the TWL are expected to remain active while on the ladder. Any team showing inactivity for a period of three weeks will be deleted from the appropriate ladder. This time frame of course does not include "Rest" time taken.

Challenge Cancelation

On the TWL there is no availability for the team Captains or Founders to cancel a challenge. All Cancellations must be coordinated through a Ladder Admin. Cancellations are not always guaranteed.

Sportsmanship and Cheating

Un-sportsmanlike conduct during matches will not be tolerated by the TWL. If an admin is called in to resolve an issue regarding un-sportsmanlike conduct the judgment/punishment will be swift, efficient and final. We here at the TWL suggest you conduct yourselves accordingly. See the specific ladder areas by this name for the specifics for that ladder and game.

Racist or sexist remarks will not be tolerated.

Simple, straight forward... Play nice.

Server Selection Time

All servers must be posted in the online match communications 48 hours prior to the match time. If no attempt is made to offer a server for your team, and the opposing team has offered a server, all 3 matches may be played on the opposing team's server per their request.

Server Crashes

In the event of a server crash, if both teams can agree upon the remaining time and score, the map will be restarted with the remaining time and score intact. If there is a dispute the entire map will be restarted. In the event that a team loses a player due to connectivity issues, (or his Mom/Dad tells him to get the hell off the PC...LOL) the team may substitute the player immediately with someone from their roster. Substitute players, brought in during match, that are not eligible players, will force an immediate forfeiture on the part of the team they were playing for.

Punctuality

Map side choices and order must be relayed to the attacking team no more than 24 hours after the attacker schedules the match. The attacking team also must relay side choice for the Tiebreaker map no later than 24 hours after scheduling the match. Server choice must be communicated in the "Match Communication" section in your team's ladder control panel 48 hours prior to match time. Failure to keep these deadlines may result in your forfeit of these options at the opposing team's (and admin's) discretion.

In between maps, a maximum preparation time of 10 minutes (15 minutes if you're switching servers) is allowed before starting the next map. Your opponents may start the map if you exceed these time limits.

Rescheduling

Should a match require rescheduling, the new match time should be within 3 days of the original match time. Matches can only be rescheduled once. Mutual consent via match comms between opponents is required.

Resting

Teams in the "Top 20" are not eligible for Rest. Teams may rest for a total of 7 days per 3-month period (13 weeks). Teams may start and stop rest by their own doing so in their Team Admin Console. Rest is counted in whole day amounts. Understand that if a team places themselves on rest to cover time waiting to challenge a soon to be free team they will be "Docked" a complete day for any partial time. (1 hour = 1 day; 4 hours = 1 day; 36 hrs = 2 days)

Smurf Policy

Smurfing is signing up for more than one team (or the same team) on the same ladder, either under the same name, or a different name. It is also the act of playing for a team you are not registered to play for, under a false identity.

Playing for a team you are not registered to play for is prohibited. Playing on more than one team per ladder is also prohibited, as is registering multiple accounts for use on the same team or ladder.

Minimum punishment for the violation of this paragraph is as follows but not limited to : (It will ultimately remain sole discretion of Teamwarfare Staff)


   * The team that the smurf joined or played for most recently will be deleted.

   * The smurf's original team will be dropped 33% of the ladder.

   * The smurf's account(s) on, and possibly access rights to, TWL will be revoked.


Additionally, team captains and founders can contact your games coordinator (SysAdmin). The list is located here. In each games staff list, at the top, is the SysAdmin for that game. The admins will cooperate fully with team captains and founders in order to combat and prevent smurfing. We will NOT hand out IP's so don't ask but we will be more than happy to check a certain player on your team.

****Ladder Specific rules supercede the corresponding general ladder rule.****

HACKING

TWL has a ZERO tolerance policy regarding Game Hacking. This rule covers players who use code to manipulate a particular game for the purpose of gaining an unfair advantage over other teams and players. Wallhacks, speedhacks and aimbots are just examples of the types of cheats covered by this rule.

"Testing" or "Trying out" Hack Programs will not be accepted excuses. Simply put "Do Not Install Hacks for any reason"

Ladders:


1. Hacker caught in TWL Match:

- forfeiture of the existing game
- Player Permanently banned from TWL.
- Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom.


2. Hacker Caught in Match outside of the ladder (League match) or in a match outside of TWL:

- Player Permanently banned from TWL.
- Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom.


3. Hacker caught in a Pub/Scrim :

- Player banned from TWL for 1 yr.
- 2nd Offense Perma Banned.This is globally cumulative. A pub ban on two separate games equals two offenses.


Circumventing your ban, either by creating new accounts, or smurfing as another player will result in the player(s) being Permanently banned from TWL.


***NOTE- Each individual game has the option of preventing a person from participating in their specific game that has been caught cheating on the pubs, regardless of how long ago the violation has occurred. This will affect that game only. The player will not be site banned/suspended or prevented from playing another game that allows them to, if the violation is over one year old.


Admin Notes:
- TWL will continue to support teams who Police themselves of hackers and cheaters. In the case where a team Purges a hacker from teir ranks and brings it to the attention of TWL staff. TWL will (waive the Drop in ladder rungs)]]> 4624@http://www.bmhq.net twl rules 2010-04-08T23:32:44-05:00 http://www.bmhq.net/modules.php?name=Forums&file=viewtopic&t=654#4623
-Gametype Specifications and Concept:
Below is a list of simple information for match play on TeamWarfare. Click the relevant link below to view the specific details.



Game Modifications and Current Version

-Current Version: v1.00

-Current Mod: No mods are currently approved for match play

-Server Requirements: A server capable of handling 2 more players than the format you are playing is to be used (eg. For 8v8, an 18 slot server is required). The server must be located in North America, running in dedicated mode, and using the currently approved TWL game version and/or mod.
[+]   General Ladder Rules

-Round Start Procedure:
Each round for all of the ladders will be started in the same way. Once the map is reset at least one player from each team will load into the map equipped with the kit they plan on playing with. These players are allowed to move around in the spawn area but may not enter any vehicles.

Once at least one player from each team has loaded into the map they will acknowledge that their team is ready to play via global chat (all of their teammates are at least loaded into the kit selection screen). At this time at least one player from each team will open the large map ("M" key by default) and the defending team will state the following in global chat:

"TWL XvX Match mm/dd/yy"

"Ready"

"Go"

The attacking team will respond with "Go" at the same time and the match will go live.

The goal is for each team to capture a screenshot including the date, the map, and both teams stating "Go". These screenshots must be made available to the other team within one hour of match completion, but only if the other team requests them either prior to the match in match comms, or in the server at the conclusion of the match. Teams may use e-mail to transfer screenshots.

Please keep these screenshots no less than two weeks after each match. Failure to provide them to a TWL admin upon his or her request may result in a forfeit loss.

The defending team is the team who received the initial match challenge.

-Match Reporting:
One of the losing team's captains, or the founder, should report the match results within one hour of the match ending via the 'Report Loss' button in the match admin panel unless they intend to submit a dispute. In that case, they should report the dispute within one hour using the 'Dispute Match Results' button.

-Sportsmanship:
All members of all squads are responsible for treating each other with respect during the match. Due to the lack of a language filter, please respect those in the server at all times and please don't be careless with your language. Sportsmanship rules are not limited to communications made within the server, but also apply to match comms.

-Player Drops and Substitutions:
If a player should be disconnected during live play, he may immediately rejoin the server if possible. If he is unable to, then a legally rostered player is allowed to join in order to take his place. Live play does not stop during this time.

Substitutes may be brought into the server between rounds provided they do so in a timely manner and are legally rostered.

-Voice Over IP (VOIP):
VOIP will be not be required to be enabled on match servers. Both teams may agree to use VOIP but only by both parties consenting in 'match comms'. TeamWarfare will not rule on disputes that involve VOIP.

-Team Size:
Each team is to fill the minimum number of players for each ladder. If a team is unable to meet this requirement then the offending team must forfeit the match and report it immediately. However, if the opposing team agrees, then re-scheduling the match to a later date is an option. In this case, both teams should post immediately in match comms indicating this decision.

If neither Team is able to field the minimum number of players by match time, or within the grace period (+15 minutes after the schedules time), the match will need to be rescheduled or killed unless both teams choose to play the match with less than the number of required players.

Matches may be played with uneven numbers in cases where one team is able to field the minimum but not the full roster against a team who does have the full roster. The team with a full roster may play with an advantage so long as they like. Teams may bring in additional players during a live round so long as they do not go over the full roster limit and the other team is given a chance to verify their legality following the round.
[+]   8v8 Conquest Ladder

8v8 Conquest Ladder-Format:
Type of Gameplay: Conquest
Number of Maps: 1
Number of Teams: 2
Members per Roster: 20
Members per Match: 8 (6 minimum)
Rounds: 3 (Best 2 out of 3)
Friendly Fire: On
3D Spotting: Off
Vehicle Third Person: On
Crosshair: On
Kill Cam: Off
Hardcore: Off
Minimap: On
Minimap Spotting: On
Map Selection: Randomly selected by site
Side Selection: Attacking team gets round 1 side selection
Server Selection: Defending team gets server selection if both teams are capable of providing a server

-How You Win:
Matches consist of three rounds with each team playing at least one round on both sides. The attacking team will have first round side choice and then teams will switch sides for the second round*. The team with the highest score at the end of the round is the round winner.

Matches are scored based on rounds won, not total scores. Thus, the match winner will be the team who wins more rounds at the conclusion of three.

The third round does not have to be played if a team is able to win the first two rounds.

There are no limits on classes or how many of each class may be used by a team at any given time.

* For the third round, the team with the highest combined score between the first two rounds will have side choice. In the event of a tie, the defending team will take side choice.

-Round Scoring
After each round both teams should announce what they believe the final score was prior to starting the next round. Most likely the scores will not differ more than 3-5 tickets*. If both teams are not in perfect agreement, just note the differences and contiune.

Play the next round and again do the same thing. If a third round is needed take both scores, add them up, and give the winner side choice. Use the score that gives each team the highest total possible from both rounds. Usually, one team will have a significant advantage regardless of the minor discrepancies.

However, if it is a close match, and the discrepancies will place one team ahead of the other, go look at the screenshots your team has of each round. If both teams have screenshots of the same round, the one with less total tickets will take precedence.

For example, Team A took a screenshot when it was 5-2 (in favor of Team A), Team B has one of 2-1 (in favor of Team A); Team B's screenshot will be used and a +1 ticket advantage will go to Team A for that round.

If your team does not have a screenshot then the other team's screenshot will be used by default.

It is not neccesary for teams to submit their screenshots to the other team for review prior to the third round. We are working on the honor system here. However, after the match is over teams should submit screenshots claimed for scoring purposes to the other team at their request. If a team fails to do this then the other team may submit a query to the admins and then they will ask for them. Failure to provide it to the admin will result in a forfeit of the match (retroactively) and competition suspensions. If you claim to have a screenshot of the score at XX-XX then you should be 100% sure your team has one.

Screenshots should be kept no less than two weeks after a match is played. Failure to do so may result in the match being forfeited.

* If there is a difference of 12 tickets or more in what each team claims, then a screenshot should be reviewed immediately before beginning the next round. This should not take more then 5 minutes.

-Server Crashes:
In the event of a server crash during a round the round should be replayed. All previous round results will stand.

In the event of repeated server crashes (2) the other team's server, or an alternate server, should be used. The match will resume and the previously completed rounds will stand.

If one team has a 35+ ticket advantage and the other team is at or below 25 tickets when the server crashes then the round will be counted as a win for the team who was winning. Screenshots will be neccesary for proof.

-Team Captains
Teams founders are allowed to appoint a maximum of three team captains for this ladder. If we catch a team with additional captains then we will randomly remove the excess captains' status and may kick players if it becomes a persistent problem.


-Demo Recording:
Please click here to refer to the demo recording requirements.


[−]   4v4 Squad Rush Ladder

-Format:
Type of Gameplay: Squad Rush
Number of Maps: 2-3
Number of Teams: 2
Members per Roster: 10
Members per Match: 4 (3 minimum)
Rounds: 2 per map
Friendly Fire: On
3D Spotting: Off
Vehicle Third Person: On
Crosshair: On
Kill Cam: Off
Hardcore: Off
Minimap: On
Minimap Spotting: On
Map Selection: Randomly selected by site
Side Selection: Attacking team gets side selection on the first two maps. The defending team will have side selection on the third map if it is neccesary
Server Selection: Defending team gets server selection if both teams are capable of providing a server

-How You Win:
Matches will consist of two teams playing two maps. Each team will play as the attacker and defender on each map. If the teams are tied after both maps (4 rounds), then play will resume on a third map.

Scoring will be done as follows:

Blowing 2 MComm stations = 2 points
Blowing 1 MComm station = 1 point
Blowing 0 MComm stations = 0 points

Matches will be scored based on total points, NOT rounds won.

-Overtime (3rd map)
The defending team will have side selection for the first round of this map. Teams will play a two round series until one team is able to blow up more stations than the other. Each team will have the opportunity to play as the Attacker and Defender at least once in each series.


↑Top


Founders/Captains

-Founder/Captain Responsibilities:
Below are the things you should know as a founder/captain of your team. Click the relevant link below to view the specific details.

Note: The term Captain also includes the founder in this section.

At TeamWarfare we hold a team's captains and founder to a higher standard. If you do not think you can act in a manner fitting of a team captain then ask the founder to remove you as such. Otherwise, Your actions will be scrutinized much more closely.

*CLICK TO EXPAND*
[−]   Responsibilities

Responsibilities

-Accepting the Match:
To challenge a team you must log into your team's Admin panel, also see Ladder Movement. To challenge a team you must log into your team's Admin panel, also covered in Ladder Movement. If you are challenging a team you are considered the Attacker of the match. The team being Attacked is referenced to as the Defending team. Once attacked the Defending team has 48 hours to respond to the challenge of the Attackers by selecting two different dates and two different times for the Attacking team to then select from. The Attacking team will also have 48 hours to lock in a date/time. Failure to complete either step of this process within the allotted time may result in a forfeit loss. Teams may agree to reschedule the match at any time as long as both teams post this agreement in match comms.

If the Defending team does not accept the match within 48 hours then this will result in the Defending team forfeiting the match and being dropped 10 rungs. The Attacking team will also take their rung.

If the Attacking team does not accept a date within 48 hours of them being issued, then they will also forfeit the match and lose 10 rungs.

Note: This type of forfeit loss will not count toward either team's record. They are called 'llamas' and are displayed inside parentheses next to a team's name on the ladder.

Teams that forfeit matches in this manner will be notified by the TWL auto mailer system. Teams that receive more than 2 llamas in a row for inactivity may be removed from the ladder.

-Eligibility for Match:
All Players must be registered on their team's roster with their correct (game specific) GUID listed in their profile the day before the match. This means as long as they are on the roster by 11:59 pm est the day prior to the match, they are eligible. Exceptions may be agreed upon in match comms or in the server at match time.

-Roster PBGUID checks:
It is the Captain's responsibility to check their opponents roster and verify PBGUID's before the match begins. Should the Captain ignore this and begin the match, then he is authorizing any otherwise illegal players currently in the server to play.

-Screenshots of the Score:
Periodically you may need an Admin to finish the match results. Every Admin must be able to verify the scores in order to report the match as completed. It is the Captain's responsibility to take screenshots at the end of each half so the score can be verified. Without screenshots, regardless of the match outcome, the match may be nullified.

-Reporting Match Results:
It is the Captain's responsibility to accurately report the match results in a timely manner. The Team Captain of the losing team MUST report the match results NO LATER THAN 1 HOUR after the completion of the match. Teams who fail to report match results accurately and in a timely manner will be punished in the following manner:

   * 1st Offense: Loss of 10 rungs and a TWL issued warning.

   * 2nd Offense: Loss of 25 rungs and a TWL issued warning.

   * 3rd Offense: Team is removed from the ladder.



NOTE: It is the winning team's responsibility to ensure that the match score is accurately reported and submitted in a timely manner. If the opposing team fails to report the match score, it is then the winning Team's responsibility to file a dispute indicating the losing team failed to report a loss. They must also be prepared to prove their case.

↑Top
[−]   Team Rosters and Player Eligibility

Team Rosters & Player Eligibility

-Joining a Ladder:
If you would like to join a Battlefield Ladder competition with Teamwarfare then please follow these steps.

  1. Log in under your registered Account.
  2. Under the top left hand corner of the site select your name.
  3. Scroll down to "Account Maintenance" tab.
  4. When the menu expands highlight and select "Register Team."
  5. Fill out as much information about your team as possible.
  6. Once team is registered you should be redirected to your new TWL team homepage.
  7. In the middle of the screen you will see a panel labeled "Team Administration"
  8. Click on "Join New Competition".
  9. Look for the drop box labeled "Join A Rung Based Ladder With ."
 10. Select the Battlefield Ladder you want to join from the drop down menu..
 11. Congratulations you have successfully added your team to Teamwarfare competition. Good Luck!.


-Account/Team Deletion:
If you would like your account or team removed from TeamWarfare please visit Site Support & Member Services and follow the instruction on this thread here.

-Team Name Change.:
If you would like to request a name change for your team then please visit Site Support & Member Services and follow the instruction on this thread here.

See "-Supported Gametypes:" and click on your team's Ladder for specific details of team sizes.

-Substitutions:
Due to the nature of the Internet, it is possible for players to be disconnected or dropped from a server. Should this happen, you may substitute an eligible player to fill the spot or allow the dropped player to rejoin. Once connected, the player must join their respective team immediately.

Due to the sizes of some teams, it is acceptable to rotate players at the beginning of new maps. The team's captain who is making the substitution should notify the other team via global communications. At that time, the other team may ask for time to check if that player is in fact elgible. If they do not request time to check or agree that the next round is live on restart (LOR) then they are voiding their right to dispute the substituted player at any time during the match. Once a player is approved by the opposing team they may continue to play out the match regardless of being rostered or not. However, substitutions should be done in a timely manner that does not hinder the progress of the game. In other words, please have your teammates "waiting in the wings."

After the completion of a round where a player was dropped and a DIFFERENT player filled in the opposing team has the right to verify that any substituted players are legally on the roster with correct GUIDs in their TWL profile.

-Spectators:
The only spectators that will be allowed to watch a match are those authorized by TWL. TeamWarfare reserves the right to observe any TWL match without notification or approval. The Admin's identity can be verified by contacting them on IRC during the match in #twl_bf on Gamesurge. Any attempt to impersonate a TeamWarfare admin will result in a permanent site ban.

-Player Names:
Due to the account system in Battlefield 2 please have your name be similar to that of your Teamwarfare account.
Examples:


   * If you are registered to Teamwarfare as Player1 and a member of Team 123 then your registered name in game should be something such as 123|Player1, Player1, etc. This is so that it is easy to recognize which player is which.

     It is understood by TWL that some players add special characters or numbers after their name to register. Please use common sense when determining who players are. Should you have any questions and/or concerns, please contact an Admin.

     If there is any doubt as to the identity of the player in question match their in-game GUID to the GUID on their Teamwarfare profile for final verification.

     ↑Top

[+]   Match Comms

Match Comms


-Match Comms:
ALL match communications MUST go through the Teamwarfare Match Communication system. This can be accessed by team Founders and Captains via the Admin Panel link in the Team Administration section of their team's page. Issues discussed in Match Comms should be Server IP(s), passwords, match settings, scheduling times, or any other relevant match specific information.

Abuse of the Match Comms system is grounds for a competition suspension.

NOTE: TWL Admins use the Match Communication system when verifying information regarding disputes and general match inquiries. If teams have not communicated in Match Comms, any disputes relating match specific issues, other then cheating or smurfing, may be summarily dismissed by an admin because of an inability to validate such problems.

Communications made outside match comms, or the match itself, will not be considered when ruling on disputes.

-Exchanging Server IP and Password:
The IP and password of the server must be provided to each squad captain 24 hours before the match in match comms. It is recommended that both teams post an IP so that there is an alternate valid server available if needed. Please be sure to pay attention to the score in case of a difficulty on the server and need to change servers, it is important to prevent disputes. If neither team is able to provide as server then the ladder admin must be notified immediately in order to kill the match.
[+]   Filing a Dispute


-Disputes for Cheating Format:
If you feel your opponent was cheating during your match, you must do the following to file a valid cheating dispute.

  1. Take a reasonable amount of time to discuss the issue with your own teammates. Take time to cool off and rationally talk about the issue.
  2. You need to have reasonable evidence to file charges. A text file with information regarding times and players involved it a vital piece of information for use in your dispute.
  3. If you feel you have reasonable grounds, initiate a dispute. List your concerns over specific instances during your match and include these in your dispute.
     Example: At x:xx minutes in the X round, player XXXXX did this. At x:xx in the X round, same player XXXXX did this. etc etc.
  4. Notify your opponent in Match Comms as soon as you dispute so they can get their evidence ready for review. Keep in mind that a disputed team becomes defensive. If your team has a dispute filed against you, cooperation is your best ally in a dispute. DO NOT use the Match Comms to flame the other team for disputing against you.Unsportsmanlike Conduct in Match Comms will result in penalties.
  5. Counter-Disputes - Please do not submit a counter-dispute against a team that has disputed against you. TeamWarfare's investigation of a dispute includes hearing BOTH sides. You will have your chance to supply the Admin handling the dispute with any information you have.


-Examples of Cheating Dispute Format:


   * At approx 7:35 in the first half, |Team|Player3 was able to kill 5 of my team members in a single clip without reloading once in less then 20sec after we all spawned. We suspect symptoms of an Aimbot.
   * {Clan}Player5 was able to come around corners prefiring the weapon on several occasions as if we could be seen through the walls. This happened during the first half at 10:20, 6:50, and 3:23. Then it happened again during the second half at 18:43, 12:08, 10:22, and 5:16.
   * During the first half at approx 5:15 left on the clock, a member of the other team was in the capture radius completely submerged. Please consult our screenshot as evidence of this.
   * At approx 1:01 in the third round during the first half, -=Clan=-Member1 had their tank barrel pointing through a wall and was firing on us, we could not kill his tank because he was protected by the wall.
   * Somewhere around 12:34 on the second round [clan]member7 began to use "all-talk" to type racist insults at our team, please consult our server logs and included screenshots for the evidence.



-General Procedures:
All disputes will be handled by the ladder admin(s). Each and every dispute inevitably involves different aspects and will be dealt with individually. Disputes must be reported to your ladder admin within 1 hour of match end. This is done by clicking on "Dispute Match Results", found in your team admin panel. Disputes must be for a valid and specific reason. Teams must identify 'when and where' the violation occured.

-Report to Match Comms:
In the event of a dispute, teams should check their match comms and team emails often, as the admin may request additional information. Once requested, teams have 24 hours to produce the materials (demos, server logs, screenshots, etc) that the admins ask for. The Admin will have the final say in judging the disputes. This game is meant to be fun, let’s keep it clean and avoid any unwanted hassles.

If a team disagrees with the result of a dispute then they may put together an appeal and send it to the admin team. All appeals will be looked at and responded to.

-Making a Habit of Disputing:
Our concern is to have a fun and clean place to play. Although the dispute process is necessary in helping keep a clean match, teams who make it a habit to dispute often with frivilous reasons will subject themselves to possible suspension, rungs lost and/or league points deducted.

Teamwarfare has zero tolerance for cheating and cheating accusations without an effort to submit any evidence.

↑Top

Technical

-Technical Information:
Below is a list of more detailed information needed to participate here at Teamwarfare. Click the relevant link below to view the specific details.

*CLICK TO EXPAND*
[−]   PunkBuster & PBGUIDs

PunkBuster & PBGUIDs

-PunkBuster Requirement:
All matches are required to be running the most current version of PunkBuster available. Servers that are not running PunkBuster are not authorized to play on. If the hosting team cannot get the server properly working by match start time then the opposing team has server priority.

-Special note regarding PIDs and PB GUIDs
***Your PID (Player Identification Number) is NOT your GUID and should NOT be entered in it's place. PID is for stats tracking only and has nothing to do with your Punkbuster GUID***

-PunkBuster updates for Battlefield 2:
Punkbuster offers a free utility called PBSetup which can be used to update any game that uses Punkbuster. Instructions and download can be found here.

Manual Punkbuster updates can be found here.
-Invalid PB GUIDs:
# Players with invalid GUIDs will have their invalid GUID deleted and be removed from their respective team without notification.

# Teams who let players play in a match with invalid GUIDs will fall under the Smurfing Policy at TWL. It is every teams responsibility to ensure valid GUIDs are entered into each of their players profile.


If a player or team finds other players who are missing or have invalid GUIDs, send an email to BFACteam@teamwarfare.com. Having a valid GUID helps the community to have a fair and balanced game for all teams.

-Master Ban List (AutoMBL):
To take a more proactive stance against cheating, the TWL has approved the use of the Punksbusted.com Master Ban List for match play. Please note, however, that TWL does not provide technical support for the Punksbusted.com MBL nor the AutoMBL tool. To find our more information regarding the MBL and or the AutoMBL tool, please visit PunksBusted.com's website by clicking here.

NOTE: Use of the MBL is not required for TWL matches. Therefore, teams cannot dispute against any other team who's server does not utilize this system, nor force a match to be played on a server that does use it.

-The following is a general guideline on "How to handle GUID issues":
# What do you do if you have entered your GUID incorrectly?

-Enter the correct GUID and then email the Battlefield Anti-Cheat team to request the incorrect GUID be deleted.

# What do you do if you have sold the game or got rid of the game for any reason and wish to have the GUID removed so someone else can use it?

-GUIDs will not be removed so that players can still be tracked in case something appears on the MBL. If you buy a copy that is already registered w/ a GUID, return it and get a new copy. Your best bet would not to buy a used copy.

# What do you do if you have been banned for cheating in Battlefield 2, got rid of the game and wish to have the GUID removed so someone else can use it?

-Email the AC team to find out about your ban and what to do next.


***All emails must contain the following information***
# TWL user name
# GUID Number
# Email must come from the email address on your TWL User Account
# You must be specific in your request.

Competition Manager's List:
# Allen - Allen@teamwarfare.com
# SixShotSean - SixShotSean@teamwarfare.com
# MadChild - MadChild@teamwarfare.com

# Anti-Cheat: blip - blip@teamwarfare.com


Report any current suspected bans/GUID matches to:
BFACteam@teamwarfare.com
[+]   Server Config

Server Config

-Server Settings:
rem *** TWL 8v8 Ladder Match Config
rem *** Last Updated October 29th, 2006
rem *** TeamWarfare
rem *** http://www.teamwarfare.com
rem *** Questions or Issues:
rem *** Email bf2naladder@teamwarfare.com
rem *** IRC: irc://irc.gamesurge.net/twl_bf

rem *** Server Settings - Modify as Needed
sv.serverName "(Clan Tag) vs. (Clan Tag) - TWL 8v8 Ladder Match"
sv.password "Your Password Here"
sv.serverIP "Your Server IP Here"
sv.serverPort 16567
sv.welcomeMessage "TWL 8v8 Match in Progress"
sv.sponsorText ""
sv.sponsorLogoURL ""
sv.communityLogoURL ""

rem *** NAT Settings - Modify as Needed
sv.allowNATNegotiation 0
sv.interfaceIP ""

rem *** TWL Match Settings - DO NOT MODIFY
sv.internet 1
sv.punkBuster 1
sv.allowFreeCam 0
sv.allowExternalViews 1
sv.allowNoseCam 1
sv.hitIndicator 1
sv.maxPlayers 18
sv.numPlayersNeededToStart 2
sv.notEnoughPlayersRestartDelay 15
sv.startDelay 15
sv.endDelay 15
sv.spawnTime 15
sv.manDownTime 15
sv.endOfRoundDelay 15
sv.ticketRatio 100
sv.roundsPerMap 3
sv.timeLimit 1500
sv.scoreLimit 0
sv.soldierFriendlyFire 100
sv.vehicleFriendlyFire 100
sv.soldierSplashFriendlyFire 100
sv.vehicleSplashFriendlyFire 100
sv.tkPunishEnabled 0
sv.tkNumPunishToKick 0
sv.tkPunishByDefault 0
sv.votingEnabled 0
sv.voteTime 0
sv.minPlayersForVoting 2
sv.gameSpyPort 29900
sv.adminScript "default"
sv.timeBeforeRestartMap 30
sv.autoBalanceTeam 0
sv.teamRatioPercent 100
sv.radioSpamInterval 6
sv.radioMaxSpamFlagCount 6
sv.radioBlockedDurationTime 30
sv.friendlyFireWithMines 1

rem *** Global unlocks (disabled)
sv.useGlobalRank 0
sv.useGlobalUnlocks 0

rem *** Demo Recordings (enabled)
sv.autoRecord 1
sv.demoIndexURL http://
sv.demoDownloadURL http://
sv.autoDemoHook "adminutils/demo/rotate_demo.exe"
sv.demoQuality 1

rem *** Voice over IP Settings (disabled)
sv.voipEnabled 0
sv.voipQuality 3
sv.voipServerRemote 0
sv.voipServerRemoteIP ""
sv.voipServerPort 55125
sv.voipBFClientPort 55123
sv.voipBFServerPort 55124
sv.voipSharedPassword ""
[+]   Demo Recording

Demo Recording

-Demo Requirement:
The team that is hosting the match server is responsible for a demo being recorded for the entire duration of the match (all rounds played). If the visiting team would like a copy of the demo once the match is completed, this request must be made in match comms prior to the start of the match.

The purpose of the demo is to backup any claim or evidence of a rules violation during the match. If a dispute is filed and the demo is requested by the admins to further investigate the dispute, the hosting team will be contacted and must produce the demo within 24 hours. Failure to produce a demo once requested by an admin (not another team) will result if the following punishment:

# 1st Offense - Team forfeits match.

# 2nd Offense - Team forfeits match, drops 25 ladder rungs.

# 3rd Offense - Team forfeits match, drops 100% of the ladder.

# 4th Offense - Team disbanded.


Note 1: Failure to produce a demo does not constitute a disputable item.

Note 2: Demos are to be held no less than 2 weeks after match date.
[−]   Exploits/Cheating/Hacking

Exploits

-General Info:
Exploiting the game is illegal and will be considered cheating if used in a match. Do not assume that the use of a bug or game engine flaw is legal, contact an Admin if you are unsure.

Glitching and Exploiting are very vague terms. All teams reserve the right to make their case against any questionable position that is used in a match. Consult an Admin if you feel there was an occurrence. Our Anti-Cheat team has created a very useful list of definitions. Protect your team from punishment by following these guidelines.

-Map Bugs:
Including but not limited to going under the map and moving through or shooting from places where flaws in the textures allow you to see through walls or other objects.

Cheating/Hacking

-Message from the TWL BF Administration
TWL has a ZERO tolerence policy regarding Game Hacking. This rule covers players who use code to manipulate a particular game for the purpose of gaining an unfair advantage over other teams and players. Wallhacks, speedhacks and aimbots are just examples of the types of cheats covered by this rule.

"Testing" or "Trying out" Hack Programs will not be accepted excuses. Simply put "Do Not Install Hacks for any reason"

-Consequences:
I. Hacker caught in TWL Match:
 A. Forfeiture of the existing game
 B. Player Permanently banned from TWL
 C. Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom

II. Hacker caught in match outside of the ladder/league match or in a match outside of TWL:
 A. Player Permanently banned from TWL
 B. Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom.

III. Hacker caught in a Pub/Scrim :
 A. Player banned from TWL for 1 year
 B. 2nd Offense Perma Banned. This is globally cumulative. A pub ban on two seprate games equals two offenses.

***NOTE- Each individual game has the option of preventing a person from participating in their specifc game that has been caught cheating on the pubs, regardless of how long ago the violation has occured. This will affect that game only. The player will not be site banned/suspended or prevented from playing another game that allows them to, if the violation is over one year old.

Founder's Responsibility & Consequences:

Team founders are responsible for their team's integrity.

Any team that rosters three or more players who get banned for cheating will be subject to removal from competition. This is cumulative and does not mean at the same time, it encompasses the lifetime of your team at TWL.

Any team that harbors players who have been caught cheating may also be subject to removal and the founder/captains banned from playing together for their lifetime at TWL.

As team founder once you have been informed one of your players has been banned for cheating you should change the "Join Password" for your team so that they can not rejoin your rosters. If you as the team founder allow a banned player to circumvent a ban from TWL you as the founder will receive a competition suspension.

-Admin Notes:
TWL will continue to support teams who Police themselves of hackers and cheaters. In the case where a team Purges a hacker from their ranks and brings it to the attention of TWL staff. TWL will (waive the Drop in ladder rungs)

↑Top


↑Top


Changelog

-Change Log:

-Apr 2, 2010
Allen: Added 4v4 Squad Rush rules and the "General Ladder Rules" section.

-Mar 7, 2010
Allen: Adjusted rules in preparation for the initial opening of the 8v8 conquest ladder.

-Feb 28, 2010
MadChild: Initial Rules Template Loaded

Rung Ladder General Rules

Ladder Movement

You can challenge anyone above you 10 slots or 50% of the remaining ladder from your current rank - whichever is higher. (Ex: Rung 100 can challenge rung 50. Rung 48 can challenge to rung 24. Rung 15 can challenge to rung 5).

On some of the smaller ladders, the challenge slots is 5 slots or 50% of the remaining ladder. Check the ladder's specific rules to be sure.

Ladder Concept

The Ladder is based on a best 2 out of 3 maps scenario. Map selection is random for the first and second maps. The "Defending" team selects the tiebreaker map. The "Defending" team chooses map sides and order. The "Attacking" team picks the tiebreaker map sides.

* THIS IS SUBJECT TO CHANGE IN THE ABOVE RULES SPECIFIC TO THIS LADDER

Team Roster Management

Ladder members join teams per ladder and may only be a member of one team per ladder. Roster changes may be made on any day. In order for a player to be considered 'eligible' for a match, he must be on his team's roster before the Defender accepts the challenge and remain on the team until the match is completed. In the case of games with in game identifiers (PunkBuster), this GUID must be entered into the players profile before the defender accepts the challenge for the player to be considered 'eligible'. If a player drops from a team after a challenge is accepted and rejoins he will only be allowed to legally play if the other team agrees to it in match comms. Leniency is given for people that sign up on the same day match is accepted.

Once a team joins a ladder, that team has 2 weeks to bring their roster to the minimum roster requirement for that ladder. Failure to do so will result in immediate removal from that particular ladder.

Team Management

Teams have one (1) Owner and any number of Captains. Captains are assigned at a ladder level. Owners are captains on all ladders. The team Owner should determine who should be in charge of issuing challenges per ladder and maintaining the team information. Multiple team captains can be assigned to perform such duties.

*There are only to be a maximum of 2 captains assigned to any ladder match.

You can only issue a challenge by making it in your Team's Admin Console on your ladder control panel on any day of the week. Access to the Team Admin Console is available to all Captains………… NOTE - You must login to the ladder in order to administer your team.

Challenge and Match Date Acceptance

All ladders have a time limitation for match responses. This includes Acceptance of a Challenge and/or Date Acceptance. The Present time frame is 48 hours. At that time a "Flag" is created for the Ladder Admins to address the next time they login to their Admin Console. If the problem is resolved by that team prior to the Admin logging in then the match continues as before. If the Admin logs in first the appropriate action will be taken. In this case forfeits will be granted and rungs dropped.

It is the each team's responsibility before the match starts to see that all players are legally registered on each teams roster. After match start or completion, roster disputes are not valid justification for forfeiture or admin intervention. Substitute players, brought in during match, that are not eligible players by the above criteria, will force an immediate forfeiture on the part of the team they were playing for.


Match Results Reporting and Disputes

Once a match has started, it is understood that both teams agree to the terms of the match (number of players, time limit, rosters, etc). If there is a disagreement of match terms AFTER match completion, the disagreement will be thrown out.

Match results are to be reported as a loss in your team admin panel or if you are disputing the loss you must login to your team admin panel and select the "Dispute Match Results" link within 1 hour of match end. If disputed it will send an automatic email to your ladder admin. If a team fails to report or dispute the team needs to notify the ladder admin immediately. Failure to do either within 1 hour of match end will result in :

  1. First Offense : Dropped a percentage of total rungs on ladder.
  2. Second Offense : Removed from ladder.

By reporting the results, teams waive their rights to protest (ultimately decided by TeamWarfare Staff). It is also to be known that once a match has been played / reported neither team can attack each other for 7 days.

If match results are being protested, a ladder admin and the opposing team captains must be made aware of the protest within one hour from the completion of the match via the "Dispute Results" link in your admin panel AS WELL AS through match comms. Failure to do BOTH may result in an admin reporting the match.

After a protest has been initiated, both teams have 24 hours to gather evidence. In this time the team being protested against may issue a counter-protest.

ALL match issues should be resolved within 48 hours from match completion.

Failure to Appear

For each ladder there is a minimum number of players needed to proceed with a match. Teams should have the minimum number of players on the appropriate server no later than 15 minutes after the scheduled match time. Failure to meet this requirement will result in an immediate forfeit against the non-compliant party. Both teams should be ready to play no later than 30 minutes from the scheduled match time (Unless agreed upon by both parties). Failure to agree to start the match at this time will result in forfeiture by the non-compliant party. A TWL admin should be contacted immediately (mIRC - #teamwarfare) for a ruling to be made. If an admin isn't available then the match should be postponed, and a dispute must be filed.

Server Selection

Server preference and choices are communicated through the "Match Communication" Portion of your Team Admin Console. All matches must be played on a server that has the ability to be password protected. If a neutral server cannot be agreed upon then the 1st and 3rd maps will be played on the Defender's Choice and the 2nd will be played on the Attacker's choice. All members should be able to connect to the server. Server disputes must be handled before match completion. Disputing a server after a match has been played will result in the dispute being thrown out.

Server selections are bound by a "reasonable difference" in ping. If the average ping differential is substantial, the opposing team has the right to refuse a server, provided there is a viable alternative server open for match use.

Inactivity

Teams of the TWL are expected to remain active while on the ladder. Any team showing inactivity for a period of three weeks will be deleted from the appropriate ladder. This time frame of course does not include "Rest" time taken.

Challenge Cancelation

On the TWL there is no availability for the team Captains or Founders to cancel a challenge. All Cancellations must be coordinated through a Ladder Admin. Cancellations are not always guaranteed.

Sportsmanship and Cheating

Un-sportsmanlike conduct during matches will not be tolerated by the TWL. If an admin is called in to resolve an issue regarding un-sportsmanlike conduct the judgment/punishment will be swift, efficient and final. We here at the TWL suggest you conduct yourselves accordingly. See the specific ladder areas by this name for the specifics for that ladder and game.

Racist or sexist remarks will not be tolerated.

Simple, straight forward... Play nice.

Server Selection Time

All servers must be posted in the online match communications 48 hours prior to the match time. If no attempt is made to offer a server for your team, and the opposing team has offered a server, all 3 matches may be played on the opposing team's server per their request.

Server Crashes

In the event of a server crash, if both teams can agree upon the remaining time and score, the map will be restarted with the remaining time and score intact. If there is a dispute the entire map will be restarted. In the event that a team loses a player due to connectivity issues, (or his Mom/Dad tells him to get the hell off the PC...LOL) the team may substitute the player immediately with someone from their roster. Substitute players, brought in during match, that are not eligible players, will force an immediate forfeiture on the part of the team they were playing for.

Punctuality

Map side choices and order must be relayed to the attacking team no more than 24 hours after the attacker schedules the match. The attacking team also must relay side choice for the Tiebreaker map no later than 24 hours after scheduling the match. Server choice must be communicated in the "Match Communication" section in your team's ladder control panel 48 hours prior to match time. Failure to keep these deadlines may result in your forfeit of these options at the opposing team's (and admin's) discretion.

In between maps, a maximum preparation time of 10 minutes (15 minutes if you're switching servers) is allowed before starting the next map. Your opponents may start the map if you exceed these time limits.

Rescheduling

Should a match require rescheduling, the new match time should be within 3 days of the original match time. Matches can only be rescheduled once. Mutual consent via match comms between opponents is required.

Resting

Teams in the "Top 20" are not eligible for Rest. Teams may rest for a total of 7 days per 3-month period (13 weeks). Teams may start and stop rest by their own doing so in their Team Admin Console. Rest is counted in whole day amounts. Understand that if a team places themselves on rest to cover time waiting to challenge a soon to be free team they will be "Docked" a complete day for any partial time. (1 hour = 1 day; 4 hours = 1 day; 36 hrs = 2 days)

Smurf Policy

Smurfing is signing up for more than one team (or the same team) on the same ladder, either under the same name, or a different name. It is also the act of playing for a team you are not registered to play for, under a false identity.

Playing for a team you are not registered to play for is prohibited. Playing on more than one team per ladder is also prohibited, as is registering multiple accounts for use on the same team or ladder.

Minimum punishment for the violation of this paragraph is as follows but not limited to : (It will ultimately remain sole discretion of Teamwarfare Staff)


   * The team that the smurf joined or played for most recently will be deleted.

   * The smurf's original team will be dropped 33% of the ladder.

   * The smurf's account(s) on, and possibly access rights to, TWL will be revoked.


Additionally, team captains and founders can contact your games coordinator (SysAdmin). The list is located here. In each games staff list, at the top, is the SysAdmin for that game. The admins will cooperate fully with team captains and founders in order to combat and prevent smurfing. We will NOT hand out IP's so don't ask but we will be more than happy to check a certain player on your team.

****Ladder Specific rules supercede the corresponding general ladder rule.****

HACKING

TWL has a ZERO tolerance policy regarding Game Hacking. This rule covers players who use code to manipulate a particular game for the purpose of gaining an unfair advantage over other teams and players. Wallhacks, speedhacks and aimbots are just examples of the types of cheats covered by this rule.

"Testing" or "Trying out" Hack Programs will not be accepted excuses. Simply put "Do Not Install Hacks for any reason"

Ladders:


1. Hacker caught in TWL Match:

- forfeiture of the existing game
- Player Permanently banned from TWL.
- Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom.


2. Hacker Caught in Match outside of the ladder (League match) or in a match outside of TWL:

- Player Permanently banned from TWL.
- Team, Loss of rungs 20%. In cases of ladders having few teams they will be dropped to the bottom.


3. Hacker caught in a Pub/Scrim :

- Player banned from TWL for 1 yr.
- 2nd Offense Perma Banned.This is globally cumulative. A pub ban on two separate games equals two offenses.


Circumventing your ban, either by creating new accounts, or smurfing as another player will result in the player(s) being Permanently banned from TWL.


***NOTE- Each individual game has the option of preventing a person from participating in their specific game that has been caught cheating on the pubs, regardless of how long ago the violation has occurred. This will affect that game only. The player will not be site banned/suspended or prevented from playing another game that allows them to, if the violation is over one year old.


Admin Notes:
- TWL will continue to support teams who Police themselves of hackers and cheaters. In the case where a team Purges a hacker from their ranks and brings it to the attention of TWL staff. TWL will (waive the Drop in ladder rungs)]]> 4623@http://www.bmhq.net twl rules 2010-04-08T23:31:55-05:00