Home Enter Forums View Downloads View Links Create an account
Navigation
Main
 Home
Clan Information
 Member Application
 Ranks
 Roster
 Rules
 TWL Rules
Community
 Affiliates
 Donations
 Downloads
 Forums
 Members List
 Surveys
Members
 Account
 My Messages


Donations
HELP KEEP OUR SERVERS ONLINE!
Make donations with PayPal!
Plat Treasury Stats

September´s Goal: $50.00
Due Date: Sep 30
Amount in: $0.00
Balance: $0.00
Left to go: $50.00

Donations

Untitled Document

Supported GameTypes


-Patches:
Any patches that are released by Infinity Ward will be tested by TWL to ensure that no adverse side effects occur that restrict or hamper play by both teams or affect performance of the server. Once approved by TWL Administration the said patch will be authorized for competition play and all teams notified through the forums as well as the rules updated.

The official release of the v1.5b Call of Duty™ Server Patch by Activision® is now accepted for match play. The Windows version and the Linux binaries can be found by clicking [HERE]. This patch resolves an exploit that can be used to crash servers.

-PAM Admin Guide:
Complete documentation for Administrating PAM can be found by clicking [HERE]. All hosting teams are required to have PAM setup properly for Ladder play on the TWL CoD Ladders. PAM sets all required settings by the Ladder and enforces the rules for all matches.

-Server Admin Guide:
An excellent resource for Server Administration can be found by clicking [HERE].



Contacting an Admin

-IRC Channel Info:

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

-TWL CoD Admin Contacts:
A complete listing of Teamwarfare's Call of Duty Admin Staff can be found by clicking [HERE].

-TeamWarfare Observer Corps:
The TeamWarfare CoD/CoD:UO takes great pride in the ability to offer Observers for competition. The TWL Observers 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-OC assinged to the match. The Role of an TWL-OC is to:
  • Record a Demo
  • while observing players.
  • Spectate all members on both teams.
  • Take a Screen Shot of PBGUID's.
  • Verify TWL Rule file being used if Pam enabled.
  • Screen Shot final scores on each side.
TWL-OC's are not Admins, they cannot make any decisions before, during, or after a match. Keep in mind their role as an OC is to observe the matches, and make sure the match falls within the ladders or league rules. If a problem occurs the TWL-OC currently assigned to the match will get an Admin to join the server and resolve the issue.

If you would like to request a TWL-OC to observe your match please email codocteam@teamwarfare.com with the following information.
  • Your Team Name & Opponent's Team Name.

  • Which Ladder or League this is for.

  • Match date/time - Server Info IP & Pass.

  • Is this for CoD or CoD:UO.

  • A link to your team profile on Teamwarfare.
Please send all comments and/or complaints to codocteam@teamwarfare.com



PunkBuster PBGUID's

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

-Working with PBGUID's
The following is a general guideline on "How to handle GUID issues"

  1. How to locate your GUID and how to enter it in your profile?

    • PBGUID's are required to be in your personal profile on TeamWafare for all Ladder and League participants. You can add your guid to your profile the following way:

    • Open CoD , join a server (one with Punkbuster running), hit the "~" key and input /pb_plist in your console. Take note of the 8 digits displayed this is your PBGUID. This is all you will need to input into your profile.

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

  2. What do you do if you have entered your GUID incorrectly?


    • Enter the correct GUID and then email the appropriate Competition Manager to request the incorrect GUID be deleted.

  3. 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?

    • Email the appropriate Competition Manager and request to have the GUID deleted.

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

    • Be advised that once your GUID is on the MBL it cannot be removed and will not be removed from your TWL account. If you wish to discuss this issue with an admin you are welcome to email the appropriate Competition Manager.
***All emails must contain the following information***
  • TWL Username

  • 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:

  • Ladder: AADiC - AADiC@teamwarfare.com
  • League: Uki - uki@teamwarfare.com
  • Euro: Anarchy - anarchy@teamwarfare.com

-Master Ban List (AutoMBL):
To take a more proactive stance against cheating, TeamWarfare has approved the use of the Punksbusted.com Master Ban List for match play. Please note, however, that TeamWarfare 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.

-PunkBuster Resources:
Software updates including PBWEB which allows you to manually update your /pb directory by simply opening and running the file from your /pb folder. Click [HERE] for more info on PBWEB.exe

Frequently Asked Questions: FAQ
Online Manuals:PunkBuster for Players and PunkBuster for Admins

*Report any current suspected bans/guid matches to codacteam@teamwarfare.com

 


Team Rosters

-Roster Information:

The maximunm allowed players for the Search & destroy League is 4

Any team fielding fewer than the designated amount is subject to a forfeit loss unless the opposing team allows the match to begin with fewer players.

Players playing under an alias NOT REGISTERED with TWL are ineligible to play. All participants must be playing under their registered nicks regardless of the fact they themselves are signed up.

See "-Supported Gametypes:" and click on your team's League 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. Anyone sitting in spectator for over 5 seconds will be considered observing and risk their team forfeiting the round/match.

Due to the sizes of some teams, it is acceptable to rotate players at the beginning of new maps or during halftime, while in "Ready Up" mode. However, this should be done in a timely manner that does not hinder the progress of the game. The player subbing out MUST disconnect before the new player joins the server. In other words, please have your teammates "waiting in the wings."

-Spectators:
The only spectators that will be allowed to watch a match are those authorized by TeamWarfare. TeamWarfare reserves the right to observe any TeamWarfare match without notification or approval. The Admin's identity can be verified by confirming their GUID by clicking [HERE] or by contacting them on IRC during the match in #twl_cod on Gamesurge.

Any attempt to impersonate a TeamWarfare admin will result in a permanent site ban.

-PlayerNames:
There is only one way you may display your name while in game on the server. Please read and understand the conditions of how to display your name.

Examples:

  • If you are registered as TotalCarnage and a member of Team HiFi then you should show up as |HiFi|TotalCarnage.

  • If you are registered as |HiFi|TotalCarange and a member of the Team |HiFi| then you should show up as |HiFi|TotalCarange.

The use of completely different names or names with ASCII text is not permitted and will result in the ineligibility of the player for the match. It is understood by TWL that some players have had to add special characters or numbers after their name to register. Please use common sense when determining who players are. The opposing team has the right to refuse any player that does not match their registered player name, regardless if the PBGUID matches the player. The player may resume to play in the match once he/she has changed their name to the correct registered name. Should you have a any questions and/or concerns, please contact an Admin in IRC.



Match Communication

-Match Comms:
ALL match communications MUST go through the Teamwarfare Match Communication system. This can be which 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.

NOTE: TWL Admins use the Match Communication system when verifying information regarding disputes and general match iquiries. 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.

-Exchanging Server IP and Password:
The IP and password of the server must be provided to each squad captain 48 hours before the match in Match Comm’s. In case of a server crash, the unfinished rounds are to be completed with the past score in mind. Please be sure to pay attention to the score in case of a difficulty of the server. It is important to prevent disputes by being aware.

-Server Selection:
The Home team has server selection for the first half, and the Visiting team has server selection for the second half. Teams may agree to play on one server. In the event of Overtime, server selection goes back to the Home team. This server is to be used for all of Overtime. If the server does not qualify for reasons such as setup or latency conflict, then it may not be used unless both teams agree.

-Scheduling:
Please consult the League Specific links for Schedule information.



Captain's Responsibility

-PAM Mode
The correct PAM Mode for all TWL Leagues is "twl" Every team has an equal opportunity to view the displayed PAM Mode in the upper-left hand corner of your screen. If the server is running the correct mode then "TWL League Mode" will be displayed. It is the responsibility of the Captain to not proceed and Ready-up until you are certain the proper mode is set. Should the Captain ignore this then by proceeding to play the match you are accepting the current mode as is. If the issue cannot be worked out between teams then a member of either or both teams should log into the IRC and get an Admin.

-Example of RCON usage:
/rcon pam_mode "twl"

-Eligibility for Match:
All Players must be registered on their team's roster with their correct (game specific) GUID listed in their profile 24 Hours prior to the match to be able to play. Exceptions may be agreed upon in Match Comms by the opposing team prior to match start.

-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 play the match then you are authorizing the player to play in the match.

-Half-Time Substitution:
There will be allowed a 10 minute break in between halves (15 minutes if switching servers). Teams that substitute players at the half must have the substitute join immediately so the other team can verify the player's PBGUID on the roster.

-PB_Plist Screenshot.
As much important as it is for Captains to check the opposing team's roster for invalid GUID's, it is also important for disputes. When PBGUID's are brought up in a dispute the Admin must verify the PBGUID's of the players in the match. Captain's need to be able to provide the screenshot upon request.

-Example of Command usage:
/pb_plist

-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 Captains responsibility from both teams to take screenshots at the end of each half so that the score can be verified. If screenshots were not taken then you made need to watch your demo to get them. Without screenshots, regardless of the match outcome, the match may be canceled.

-Reporting the Match Results:
Team Captain's have two options when reporting the match results.

  1. Report Match Results

  2. Dispute Match
Team Captains of the losing team must report the match results no later than one hour after the match's completion. This can be done from the Admin panel for the Call of Duty Ladder. Failure to do so will result in the following consequence. There will be No Exceptions to this rule.
  • Consequence- Team penalized League Points.
Although there is no exception please refer to the below subcategory labeled "-Disputes for Cheating Format:" It has been recognized and is understandable that (1) hour is not enough time to collect all of the evidence needed to submit your case. If you are submitting a Cheating Dispute you MUST report the match as a dispute within the (1) hour time limit. Simply state in your dispute that you are submitting a Cheating Dispute and will have the rest of the information needed as shown below in the example sent to codacteam@teamwarfare.com within 24hrs. of your initial dispute claim. Failure to do this will result in the dispute being rejected and the above consequence will be applied as a penalty. For all other disputes, see "-Filing a Dispute:".

Please also make a post in Match Comms stating that a dispute has been filed so that the other team knows not to report the match until the dispute has been resolved.



Match Start

-Sportsmanship:
See Sportsmanship and Cheating.

The following penalties will be enforced for all players that display Unsportsmanlike Conduct.

  • 1st Offense - 15-day suspension of player involved.

  • 2nd Offense - 30-day suspension of player involved.

  • 3rd Offense - Player Banned 1 year. Team forfeits match.

-Match Time:
All players should join the server on time. Once they have joined they should stay on their respective sides without excessive TKing or killing the other team. This facilitates getting the match started in a timely manner. All members of each team need to be in the server and ready to play no later than 15 minutes after the time the match is supposed to start. The offending team will forfeit.

-Ping Discrepancy:
In the event of a major ping discrepancy, (+/- 50ms Average difference between teams) a neutral server must be used unless both Teams agree that the match should proceed.

-Authorized Communication:
Two captains from each team will be designated to communicate prior to the match starting and between rounds. These captains must be listed as a team captain prior to the start of the match. Team founders that attempt to promote a player after the start of the match to cover up from being disputed will be penalized. No other "global" communication is permitted, however, Good Game or Good Luck prior to and after matches is acceptable. Team Captains ARE responsible for the actions of their team members during matches.

-Voice Taunting:
Voice taunting (team or global) is not allowed, if an Admin deems it was used in excess it will mean the offending round(s) will be overturned.

-Demo Requirement:
To level the playing field, every player is now required to demo every match for the entire duration of the match. These demos are to be handed over to a Teamwarfare Admin upon request, where they will be subject to review by the Teamwarfare Administration Staff. Demos are to be held no less than 2 weeks after match date. There are consequences for not producing demos when asked.
  • 1st Offense - 15-day suspension of player involved. Team forfeits match

  • 2nd Offense - 30-day suspension of player, 15-day suspension of team involved. Team orfeits match. Team penalized League Points.

  • 3rd Offense - 60-day suspension of player, 30-day suspension of team. Team forfeits match. Team Removed from League

  • 4th Offense - Player banned from Teamwarfare, Team disbanded.

-Match Start:
When both teams are ready and all members have been successfully connected to the server, the "map_restart" command is issued. Once the map restarts then PAM will wait until all members from both sides have "readied up" (selected their "use" key). Founders/Captains, do not allow your members to "ready up" until you have all members of your team in the match. Once PAM goes live, the match is live. All teams are required to take screenshots of the score at the end of the 1st and 2nd half.



Filing a Dispute

-Disputes for Cheating Format:
You may not submit a cheating dispute if your team cannot provide demos of each player who played in the match on your team. You may submit a complaint to the TWL CoD AC Team in order to continue Anti-Cheat efforts however as far as the match goes it must be reported. If your team can provide all demos and 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. Watch your own demos, and site specific players at specific times during your match where you feel they were cheating. 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. While you are filing your cheat dispute, get your own team demos uploaded so an Admin can get them instantly.
  5. Notify your opponent in Match Comms as soon as you dispute so they can get their demos 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 the Match Comms will results in penalties.
  6. 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 on top of the roof where there is no textures under the feet. We don't know the name of the player, but the location was on the south west corner of the map. We know there is no textures because our team reenacted the spot after the match.

  • At approx 2:05 left in the second half a member of the other team had destroyed our radio through a texture. We were not able to identify the player's name. The score was almost tied when this happened and we believe this had impact on the outcome of the match.

  • At approx 5:15 left in the second half -Clan-Player6 team killed -Clan-Player1 in order to gain health back by respawning at the end of the 45sec respawn timer.

  • At approx 14:10 during the first half we believe two members of the other team had intentionally team-killed themselves to respawn near their base where the flag was about to be taken.

  • With 11:34 left in the second half, the other team parked a tank on the flag. Members of my team were repeatedly killed while attempting to remove the tank over the flag.

  • The score was tied at 10-10 and during the sudden death round =|Team|= Member4 was using repeated voice taunts as we only had one player alive and could not hear the enemy coming around the corner.

  • At approx 1:01 in the fourth round during the first half, -=Clan=-Member1 was laying prone on the stairs and killing while his gun appeared straight up in the air. His position was not logical and we believe -=Clan=-Member1 was glitching and could not be damaged. I know it was -=Clan=-Member1 because his name was viewed in the obituaries in the bottom left-hand corner as he killed my team mate. You can view this through my team-mate Player4's demo.

     

-General Procedures:
All disputes will be handled by the league admin(s). Each and every dispute inevitably involves different aspects and will be dealt with individually. Disputes must be reported to your league 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, etc) that the admins ask for. The league 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.

-TWL Demo Uploads
Teamwarfare provides a website facility for the public to upload demos and screenshots.

To use this facility, goto www.twl-demos.com and click the "Call of Duty/Call of Duty United Offensive" logo.

When uploading, please zip your files up and rename them as follows: tag_playername_date.zip

(Please note that you are ONLY allowed to upload .zip files). At present there is a filesize limit of 64MB. Please split up your uploads if your .zip is exceeding this size.

Using this FTP service for anything other than match demos, screenshots, or other files requested by an Admin will result in heavy penalties.

-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 and league points deducted.

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



Exploits

-General Info :
Exploiting the game is illegal and will be considered cheating if used in a match. Do not assume that use of a bug or game engine flaw is legal if it is not specifically listed or unknown; 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 occurance. Protect your team from punishment by following these guidelines.

-Suicides and Intentional Team Kills
Any form of intentionally killing yourself or a teammate (via /kill, cratering, grenades, or team killing, etc) in an attempt to respawn with full health has been deemed a gametype exploit. Using this method to your teams advantage may be subject to forfeiture of the match and other penalties directly related to exploiting the gametype.
This rule applies solely to the HQ League.
Admins have the final say in the penalty, and will be determined by the severity of the infraction.

-Destroying Radios Through Textures
Some radios in certain maps have the ability to be destroyed through a wall or other texture. Destroying Radios using this method is considered a map exploit and will result in the violating team forfeitting the match.

-Devmap Abuse
Using /devmap instead of /map to load the map for a match is strictly prohibited. The command is to be used ONLY in locked servers, in any non-twl sanctioned activities. Violators will be severely punished.

-Going 'Under' the map
Going 'under' the map is a map exploit. Using these areas in any strategic way (killing enemies, recon, etc) will result in a forfeited match and a 30 day suspension of the offending player.

-Explosion Jumping
Using explosives (grenades, rockets, etc) to get an elevation boost during jumping to reach areas not attainable from normal jumping has been deemed an engine exploit. Using this method will result in a forfeited match and a 30 day suspension to the offending player.

-Unauthorized cvar changes
Changing ANY cvar from the official TWL Config to create an advantage for your team will result in a forfeited match. Other penalites may be handed out for more severe cases.




Cheating/Hacking

-Message from the TWL CoD 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. If you are caught cheating or hacking in a TWL Match:
     A. Forfeiture of the existing game.
     B. Player Permanently banned from TWL.
     C. Team will forfeit any match (for the present season) that the offending player was proven to have played in.

II. If you are caught cheating or hacking outside of the ladder or in a match outside of TWL:
     A. Player Permanently banned from TWL.
     B. Team will forfeit any match (for the present season) that the offending player was proven to have played in.

III. If you are caught cheating or hacking on a Pub or in a Scrim:
     A. Player banned from TWL for 1 yr.
     B. 2nd Offense Perma Banned.

-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 forfeiture of past league matches.



General League Rules

Rescheduling

Dates can only be rescheduled on a different night (prior) to the match night as long as both teams agree and the admins are contacted by email 24 hours in advance.

Default times are determined by League rules.

Team Rest

If your team chooses to rest or go “inactive” your options are:

1) Request to be dropped from the league
2) Stay and receive forfeits until you become active again.

Team Roster Management

Each team is to have the minimum amount of players as determined by the specific League rules. TeamWarfare Team Rosters will be CLOSED on a night determined by TeamWarfare. Check you league specific rules regarding Roster Locks.

Team founders and Captains are responsible for maintaining a clean and Smurf clear Roster. Failure to do so can lead to Disciplinary Action.

Match Eligibility

Members must be on the roster by 11:59 PM EST the previous day of each weeks matches to be eligible for play.

It is the responsibilty of the opposing team to check the eligibilty of the players from the other team. Its a good idea to have a copy of the other teams roster available to review this at match time. If a team fields an ineligible player it is the responsibilty of the opponent to refuse this player and notifiy an admin. If this is discovered AFTER the match has been played then neither team has grounds for a dispute.

*However if within the Aloted 24 hr Dispute posting time. A team discovers a player on the opposing team is a Smurf,Doubleclanner,ringer or suspended player. The team is allowed to Dispute the Match results.

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

Teams are expected to be on the server and ready to play with the minimum number of players at the scheduled or agreed upon time. Any team that fails to be present with the minimum amount of players and ready to play on a server 15 minutes after the match start time will forfeit the match.

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.

Smurfing/Ringing/Double Clanning Policy

Smurfing/Ringing/Double Clanning is signing up for more than one team (or the same team) in the same League, 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.

Some Games have different levels of League Competition Within a Game. Such instances where a game League has more then 1 league such as an Beta, Alpha and Invite. A player is allowed to play on only 1 team within the Game. There will be no crossover from 1 league to the other within a GAME. Players Caught playing on more then 1 league team will be suspended and the team will at the discression of the admin recieve either forfeiture, suspension or removal of the league.

Teams that recruit higher level players will be subject to removal from a lower competitive League and placed in a League more suitible for the level of the players within the team.



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

Any player caught smurfing will be Suspended or expelled from the League and may be banned from TeamWarfare. Second offenses will result in the team or teams involved being remove from the League. Teams are also subject to recieving forfeit losses of there match if found to have Played Smurfs.

Team Management

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

Access to the Team Admin Console is available to all Captains………… NOTE - You must login to the League in order to administer your team. You will also be able to see that the home/visitor status , as well as issue match communications and report the results of your matches in the admin panel.

Match 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 can be reported in your team admin panel by "EITHER" team or if you are disputing the loss you must report it to your League Admin within 1 hour of match end.
By reporting the results, teams waive their rights to protest (ultimately decided by TeamWarfare Staff).

Failure to Appear

For each league 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.

Server Choice

Server choice must be communicated through in the “Match Communications” section in your teams League 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 admins) discretion. It is each team’s responsibility to provide a server for the rounds that they are responsible for. If a team cannot supply a server they are to use the server there opponent has supplied. If neither team can supply a usable server on a match night then the match will be canceled and both teams will not receive points.

****ANY SERVER USED MUST be running TWL MATCH CFG to be considered eligible servers, unless agreed upon by both teams and approved by an admin.

Complaints about servers are waived after a match is completed.

League Map Schedule

The Map Schedule for the Leagues are to be strictly adheared too. Teams are not allowed to play any other maps than the one listed for that weeks play.
This is not negotiable. Unless the Admin changes the Map for the whole league, teams will play the listed Map.

HACKING

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"



Leagues:

1. Hacker caught in TWL Match:

- forfeiture of the existing game
- Player Permanently banned from TWL.
- Team will forfeit any match (for the present season) that the offending player was *proven to have played in.


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

- Player Permanently banned from TWL.
- Team will forfeit any match (for the present season) that the offending player was *proven to have played in.


3. Hacker caught in a Pub/Scrim :

- Player banned from TWL for 1 Year.
- 2nd Offense Perma Banned.

* Opposing teams will have to provide proof to TWL Admins in the form of Demos, Screenshots or Server logs that the opposing team did have this player on their team. Proof must be provided within a 48 hr period.


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 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.


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 or forfeiture of past league matches.)

PLEASE NOTE

****League Specific rules superceed the corresponding general League rules.****