since its a little late for cal season i was thinking about entering us into a ladder tourney. We can still get the match exp we need but without the mandated time and date of play that Cal has. With TWL we can have our match any day of the week between 830 and 1030 pm est. Plus its not a mandated schedule. its more based upon challenging other teams to matches and then just deciding on a map.



here are the rules of TWL they really arent so bad but i think everyone who is interested should at least read this list once

-Server and Client Sides:

Only the following versions, patches and modifications are allowed to be used, no other game modifications are to be employed:




Patch 1.22


-Server Types:
The match must be played on a dedicated server connected to at least a T1 connection. Cable, DSL, Satellite or other broadband connections are not acceptable at this time. LAN Center players are not allowed to use servers located at their LAN Center. Additionally, any server that allows one of the teams to ping less than 10 to is not usable for match play. A suitable neutral server should be used instead.


↑Top

--------------------------------------------------------------------------------


Contacting an Admin

-IRC Channel Info:




Server: 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. 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 you.

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

-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 match please email BF2NAstaff@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 BF2NAstaff@teamwarfare.com


↑Top

--------------------------------------------------------------------------------


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"




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 Battlefield, 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 characers 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 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.



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.



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 incase 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, 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 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: Grassy - grassy@teamwarfare.com

League: CLAYMAN - clayman@teamwarfare.com


-Invalid PBGUID's:
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 BF2NAstaff@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.

-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:
BF2NAstaff@teamwarfare.com


↑Top

--------------------------------------------------------------------------------


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.




Team Rosters

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




Log in under your registered Account.

Under the top left hand corner of the site select your name.

Scroll down to "Account Maintenance" tab.

When the menu expands highlight and select "Register Team."

Fill out as much information about your team as possible.

Once team is registered you should be redirected to your new TWL team homepage.

In the middle of the screen you will see a panel labeled "Team Administration"

Click on "Join New Competition".

Look for the drop box labeled "Join A Rung Based Ladder With ."

Select the Battlefield Ladder you want to join from the drop down menu..

Congratulations you have successfully added your team to TeamWarafare 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. However, this 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."

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

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. Should you have a any questions and/or concerns, please contact an Admin.


↑Top

--------------------------------------------------------------------------------


Match Communications

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

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.

-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 Comm’s. 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.



↑Top

--------------------------------------------------------------------------------


Captain's Responsibility

-Accepting the Match:
To challenge a team you must log into your team's Admin panel, also see Ladder Movement. If you are challenging a team you are considered the Attacker of the match. The team being Attacked is referenced as the Defending team. Once attacked the Defending team has 48hrs to respond to the challenge of the Attackers by selecting two different dates and two different times for the Attacking team to select from. Also note that some Ladders may require additional selections such as maps and/or side selection.

Failure to accept the match within 48hrs will result in the following consequence.

Consequence - Defender's forfeit match. Dropped 10 Ladder rungs. Attacker takes Defender's rung.

Note: Forfeit will NOT include a loss on the record of the team, nor will the other team gain a win on their record.

-Confirming the Match:
Once the Defender has offered the dates and times the Attacking team will have 48hrs to confirm one of the two offers by the Defending team. Also note that some Ladders may require additional selections such as maps and/or side selection.

Failure to confirm the match 48hrs after it was accepted will result in the following consequence.

Consequence - Attacker's forfeit match. Dropped 10 Ladder rungs.

Note: Forfeit will NOT include a loss on the record of the team, nor will the other team gain a win on their record.

Teams that have these consequences applied will be notified by the auto mailer system. The TWL System monitors and flags all matches in violation. A llama is added each time to the team that violates the Match Acceptance process. Teams that receive more than 2 llama's in a row for inactivity will 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 prior to match time 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.

-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. Without screenshots, regardless of the match outcome, the match may be canceled.

-Reporting Match Results:
It is the Team Captain's responsibility of the losing team 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 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 and a TWL issued response.


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.


↑Top

--------------------------------------------------------------------------------


Match Start

-Sportsmanship:

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

-Match Start:
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/Round End:
At the conclusion of each round, each team is required to take a screenshot of the final scores. It is each team's responsibility to retain these screenshots for a minimum of two weeks.


↑Top



--------------------------------------------------------------------------------


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.




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.

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.

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.

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 the Match Comms will results in penalties.

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 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. Admins may use their discretion of listening to a dispute that is later then an hour.

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

-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

--------------------------------------------------------------------------------


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

An example of a current exploit is spawning out of bounds on a squad leader.



↑Top

--------------------------------------------------------------------------------


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.

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


Below are the general ladder rules. The BF2 NA Ladder rules (above) are to be adhered to. Below is just a generalized ruleset for all ladders


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 preperation 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 Specfic rules superceed the corresponding general ladder rule.****

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"

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

Guys d/l ATC for bf2

If no one is dead, I'm in.

Jesus christ did you put the entire terms of the league in your reply Black-Sheep.
Anyways im in. Im ready to own some fools and I do believe that since we've been a team for this long we can really compete against other teams. (Pep Talk)

PS- Fish, keep rocking those bitches with the claymores