1. League Information

Team Fortres 2 (TF2) 8vs8 is a public league that is part of the Team Fortress League (TFL). The league is comprised of divisions with different levels of competition, ranging from new clans looking for a place to start to highly competitive clans looking to be the best in the game. The 8vs8 division uses a ladder format for clan ranking and scheduling clans and is used for placement in the TFL Open Tournament. The TFL Open is for any clan currently in TFL and wants to compete for the championship of their division.

Please contact a league official if you have any questions, suggestions, and comments about the TFL or its TF2 8vs8 league.

A summary of rules can be found at the Rules FAQ

(last edited 11/04/07)

2. Joining TFL

A clan needs to have a minimum of twelve (12) active members in the clan, a functioning website with roster names and SteamIDs, a registered internet relay chat (IRC) channel, and a valid email contact information of clan leadership. If your clan meets these requirements, than please sign up for the TF2 8vs8 league by clicking on the Sign Up Link.

By joining the TFL, you are consenting that you have read these rules and that you will abide by them. Failure to do so will result in suspension or expulsion from the league. A player that plays in a TFL match expressly states that he has read the rules and will abide by them. Failure to do so can result in suspension or expulsion for the individual player or clan he is a member of. If you have a problem with the rules, please do not join this league. If you decide that you will disregard the rules and play as you wish, please leave or refrain from joining the league.

(last edited 11/04/07)

3. Scheduling Information

A. League Schedule

All TF2 8vs8 matches will start at 9 p.m. Eastern Standard Time (EST) every Thursday. Clans can alter the start time of the match, but matches must take place on Thursday.

(last edited 11/04/07)

B. Seasons

TF2 8vs8 operates in 12 week seasons divided by the TFL Open. The number of clans that sign up for the TFL Open will determine the length of time between each season. For clans that do not or cannot participate in the TFL Open will be scheduled as normal in their respective divisions. For those interested in the TFL Open can find more information by clicking here.

(last edited 11/04/07)

C. League Maps

All servers must have the correct map version. The definition of "correct map version" is: The map located on the TFL files page and any corresponding entity update also located on the files page.

The maps are decided by the TF2 8vs8 admins. Clans may change the league-selected map as long as both clans agree to it (and can document this agreement) and the map is listed on the TFL map list. If both clans cannot agree to a new map, the clans must play the league-selected map.

Clans may NOT change the map if they are involved in any of the following:

1. A Division Title Shot Match
2. A Division Title Match
3. A TFL League Sponsored Tournament

Clans who change the map during one of the above mentioned matches, run the risk of having their match forfeited.


(last edited 11/04/07)

4. Game Servers

A. Server Requirements

Servers must be able to reasonably handle the bandwidth and CPU load of a full 20-player game. The TFL has the final authority in determining what is or is not reasonable. If you have a chronically bad server that receives multiple complaints you may be asked to find a different server for Official TFL matches.

Matches must be played on a T1 server or better. Cable and DSL servers will not be allowed in TFL. With prior admin approval, DSL servers with a dedicated 1.5 up and down line will be allowed. Contact your division admin for official approval.

(last edited 02/27/07)

B. Required Software

·Clans must use the TFL server.cfg
·Clans must use Valve Anti-Cheat (VAC)
·Clans must use up to date version RingerFree
·Clans must provide HLTV proxy and demo
·Clans must use up to date verison of ETANA (see ETANA section below)

TFL Server.cfg
All clans must use the latest TFL Server.cfg file, which can be downloaded by clicking here.

Valve Anti-Cheat
All clans must have Valve Anti-Cheat (VAC) enabled on their servers during a TFL match. To enable VAC, you must edit the file "liblist.gam" via FTP on the server and add the following line:

secure "1"

Than restart the server. If you need help with this, please contact a TF2 8vs8 admin.

RingerFree
TFL requires the use of the newest version of RingerFree (RF) for all TFL matches, which can be downloaded here. This is a server side program that only needs to be run on one computer associated with the "home clan" of each round. This program checks the people playing in the TFL match with the respective TFL rosters. If players with the wrong Steam ID are found in the server, they may be kicked and/or banned from the server. Ensure that your clan's rosters are current and correct prior to the roster "lockdown" period. RF will also check various server CVARs. Any incorrect CVAR will be automatically changed.

Violations found by RF will be broadcast to the players on the server, and will automatically notify TFL staff of any infractions. Failure to run RF properly or not at all could result in forfeiture of said match. If two clans agree that a non-rostered player can play in a game, then the Division Admin or League Admin may, at their discretion, agree to allow the player(s) in question to play by adding the player(s) to the Ringer Free exception list. This is solely at the Division Admins or League Admins discretion, and is in no way to be considered a process or entitlement by the TFL clans. If you wish to have the members in question added, have your opponent contact the league admin a considerable time prior to the match with the request.

All RF disputes must be filed before the dispute time-limit expires.

HLTV
Use of HLTV during Official TFL Matches is Mandatory by all clans playing in TFL. You can download the HLTV Config by clicking here.

Clans must follow these guidelines when using HLTV

1. Use of the tflhltv.cfg file is mandatory by all clans
2. You must provide your opponent with the IP along with any passwords to the HLTV Server
3. You must provide any admin with the HLTV IP/passwords/logs upon request and without delay
4. You must provide a minimum of 2 slots in your hltv for spectators. One for your opponent and one for TFL Admin. More spectator slots can be used at the discretion of the the hosting clan.
5. TFL reserves the right to change/adjust these guidelines without notice at anytime.

Recording HLTV demos is required in TFL. If your clan files a dispute for a round played on your server and you cannot provide your HLTV demo, the dispute may be rejected by TFL or your clan risks losing the dispute. If the round disputed was played on your opponent’s server, the HLTV demo for that round is still required. Clans must provide their opponent a link to download HLTV demo's within 24 hours of the match even if no dispute was filed. Demos should be available to TFL Staff and to your opponents up to 14 days after a TFL Match via the provided link.

It will be the responsibility of the hosting clan to ensure that there is an HLTV server up and running for the match. If a hosting clan does not have HLTV available for a match(es) for whatever reason the hosting clan must 1) allow the visiting clan to run HLTV on the hosting clan’s server, or 2) allow a third party to run HLTV on the hosting clan’s server.

(last edited 08/26/07)


ETANA

Since this is a new mod, TFL reserves the right to require ETANA or not to require it depending on how the game plays during our trial period(s). If TFL decides to require ETANA, the below settings will serve as only an example of possible enforceable server settings.

This metamod server pluggin will be utilized to enforce various server settings. These may include:

_special
tracerlength at 0.8
traceroffset at 30
tracerspeed at 6000
cl_lw (locks player's starting value)
sprites/explode01.spr
sound/weapons/ax1.wav
fullupdate

Users found to be in violation of these settings will risk having their clans match overturned, or loss of a Division Title or Title Shot. Users found to be in violation of these settings also run the risk of being suspended for two weeks and or being banned from the league for up to one year or more.


(last edited 08/26/07)

C. Prohibited Software

The use of Admin Mod in any Official TFL Match is strictly prohibited. The round in which Admin Mod is used the hosting clan will have their points forfeited, in addition to possibly losing use of that server in future TFL matches. If any admin mod commands are used during the match can result in suspension or removal from TFL.

The use of any Anti-Cheat software in TFL, such as CSGuard, Cheating Death, Sparkies Server v2, or any other anti-cheating software is strictly prohibited. If a server is found running any anti-cheating software, the visiting clan has the right to refuse to play on that server. In addition, the hosting clan found using anti-cheating software on their server during their round, runs the risk of losing any dispute related to the round or match, their points forfeited during the round it was ran, and possibly losing use of that server in future TFL matches.

If you have any suggestions as to which anti-cheating software should be used in TFL, please contact your division admin with all the relevant information concerning the proposed anti-cheating software.

(last edited 02/27/07)

D. Server Crashes/Multiple Player Drops

If a server crashes unintentionally or multiple player “drops*” (defined below) occurs before the 15 min mark (not including pre-match), then the visiting clan has the option to restart that round, or to add the remaining time to the next round. If the latter option is chosen, any captures up to that point will be counted. If a server crashes unintentionally or multiple player drops occur (defined below) , and the match has proceeded for at least 15 minutes (not including pre-match) then the visiting clan has the option to add on the lost minutes to next round (if there is one), or keep the score when match ended as the official round score. Clans are encouraged to find a mutually acceptable solution.

*Multiple player drops - where 3 or more players are dropped from the server at the same time or within a very, very short time span (this type of drops usually occur at once or within 10 – 20 seconds of one another and usually encompasses 3 or more players on one team. If the multiple player drops are questionable (as far as reason for and or time frame), the clan with doubts can file a normal dispute.

Either participating clan may refuse to start the match until no later than 15 minutes after game time. At this time the match starts, or the refusing clan forfeits. Should a match have already begun and the visiting clan recognizes that there is a problem with any server setting, whether it be fraglimit, teamplay, floodprot, watervis, etc. the visiting clan has the option of restarting the match up to the 15-minute point (i.e. prematch + 15 minutes). After this time, as long as the server data mismatch is minimal, the round is considered legal. Should a visiting clan notice before the 15-minute mark that there is something amiss, they still may wait until the 15-minute point to decide whether to restart the match.

Should the visiting clan decide to restart, the server must be reset to TFL norms and the match restarted at time zero. The scores from the aborted round are not counted. Should a server variable be found to be incorrect after the match, or after the 15 minute time has expired, clans may bring their cases to a TFL dispute admin, however for the most part if a variable is noticed to be incorrect after 15 minutes then it did not have a significant effect on the match.

(last edited 09/01/07)

5. Match Play

A. Pre-Match

It is mandatory that all clan contacts meet in IRC 30 minutes prior to your match to contact your opponent to ensure that there are no problems. TFL is located on irc.gamesurge.net #tfleague. If an admin does not answer your channel message, private message your division, league admin, than league director for urgent matters. The schedule is generally posted within 48 hours after league matches have been played. Try not to make last minute contact with your opponent as you have at least five to six days to make arrangements for matches.

Clans have 15 minutes after the default time, or the mutually agreed to time, to join the server. Failure to comply will cost that clan a forfeit. Under extraordinary circumstances, such as connection problems for a significant number of players due to Internet problems, the TFL may allow exceptions to this rule.

We recognize that issues with members may come up from time to time such as getting out of work late, or some other family activities that may prevent some members from being on time for a TFL match. With this in mind, clans must have at least 7 active members present (for a 9v9 Match, 6 for an 8v8, 8 for a 10v10) at the agreed upon match time for a match to be considered valid in TFL. If a clan cannot field the minimum active members before the end of the first pre-match, the clan will be forced to forfeit the match and will receive as a loss for the match. If neither clans can field the minimum players required, than the match will be recorded as a mutual forfeit.

In maps where you may leave your respawn during prematch, you may NOT leave your base. Dropping dets, spamming the enemy respawn as PM ends, caltoping their entrance etc., etc., will be grounds for immediate forfeit and/or suspension. Building sentry guns and dispensers during a PM are also prohibited and is a forfeitable offense. Purposefully dying at the end of prematch in order to leave an ammo pack for the future engineer is allowed.

All clans shall permit spectating for the purpose of match broadcasts unless they explicitly request that none of their matches be broadcast well in advance to the 9v9 admin. All Tournament Matches are subject to broadcast, regardless of individual clans' requests not to be broadcast. It is for this reason, that servers be able to handle at least 20 players: 18 slots for clan members, and 2 slots for an Admin and or match broadcaster. Currently, no organization has exclusive rights to broadcast TFL Matches.

Personal demos are required of all players in TFL matches. Failure to record personal demos can contribute to forfeiture of match or suspension.

(last edited 02/27/07)

B. Playing A Match

Matches consist of two rounds with a 3-minute pre-match and a 30-minute game, for a total of 33 minutes per round. Some maps do not work properly if the 3-minute pre-match is enabled, and thus are played without a pre-match. These maps will always be marked on the schedule, and will be the responsibility of both clans to ensure that the proper settings are used. Please refer to the TFL Server Config file for non-prematch settings. The hosting clan will have the first choice in which server and color they wish to use.

From time to time, matches sometimes run into problems and the pre-match must be restarted. All clans need to keep in mind that Excessive pre-match restarts can result in forfeiture of the match.

Only leaders/admins are permitted to use MM1 during a match. Excessive MM1 spamming may result in sanctions for the clan’s offending member(s), loss of all point scored that round, or in a disqualification for the offending clan. Treating your opponent in an unsportsmanlike manner will be dealt with appropriately. It is advisable to NOT respond to clans doing so, but to play the match to completion and then dispute the round in question.

After the first round is completed, clans should take a 5-minute break.

If the match is tied after two rounds of 30 minutes: (The definition of a tie is when the sum of both team's score in round 1 and round 2 are equal), then the match will continue as a 30 minute sudden-death 9vs9 round on the hosting clan's choice of server after a 5 minute break to allow for roster changes. FIRST CAP WINS THE MATCH. Should the 3rd round end as a tie, a final match must be played, sudden-death 5vs5 on the same map. FIRST CAP WINS THE MATCH. If the match is still tied after this it will be considered a draw.

Asymmetric maps (i.e. Canalzon, Darkness, Enclave, put FF maps that apply here) in order to negate any imbalance in the map, whether real or perceived, will have each overtime round split into 2 sub-rounds on the same server, with each team playing 1 round on each color. Each of the split rounds will be 15 minutes in duration with a 3 minute pre-match, and the result for that overtime round will be the combination of scores from the 2 sub-rounds. Neither team will be permitted to leave the server between sub-rounds. However, players may be substituted during the pre-match as needed as long as pre-match is not restarted (except in case of server issues).

Maps that either have a built in pre-match, or break the standard pre-match (i.e. Darkness and Enclave) will use the maps built in pre-match. Clans should restart the map ONLY when each team has made their substitutions and are ready to play, or when the standard 5-minute break has passed.

(last edited 09/01/07)

C. Post Match

To report a match, the winning Clan MUST submit the results and a detailed match recap using the form located on the TFL scoring page no later than Friday, 9PM EST. Failure to do so will negate the match results for both teams.

(last edited 02/27/07)

D. Forfeits

TFL will not tolerate forfeits due to the lack of available players by any clan actively participating in TFL-Sanctioned Matches. By joining this League, your team has committed to arrive and compete with at least the minimum number of players per League specifications every Thursday at 9:00 PM ET.

However, we recognize that sometimes things do not go as planned. Out of respect to your opponents, your team is expected to provide notice whenever possible if your team is unable to meet their Thursday commitment.

If your team is unable to meet their Thursday commitment on match night, it is your responsibility to notify your Division Admin and your opponent contact of your intention of forfeiting a match due to lack of available players. Failure to do so will be classified as a No-Contact Forfeit, and your team will be subject to sanction.

If you believe your team will not be able to meet their Thursday match commitment and you notify your Division Admin 24 hours before the scheduled match, your team may not be sanctioned.

Forfeits are defined as:
Any clan that fails to arrive in a timely manner with the minimum number of players (8v8: 6 | 9v9: 7 | 10v10: 8) for a TFL-Sanctioned match. Any clan that fails to field enough players for round 2 of matches. Overtime/Sudden Death rounds are inclusive. See the Overtime/Sudden Death Rounds section for further detail.

No-Contact Forfeits are defined as:
Any clan that fails to make contact with their opponent and/or fails to show for an officially scheduled TFL match/round.

Sanctions in regard to Forfeited matches are as follows:

First Offense: One Week Team Suspension
Second Offense: Two Week Team Suspension, if previous offense is within a 12 week timeframe
Third Offense: Team to be taken Inactive, if previous offense is within a 12 week timeframe
Fourth Offense: Subject to review by TFL Staff, if previous offense is within a 12 week timeframe

TFL Admins may, under certain circumstances, vary these sanctions as they deem necessary on a case-by-case basis.

.

(last edited 09/01/07)

6. Clan Placement/Divisions

A. Clan Placement

When applying for FF 9vs9, clans may request which division to be placed in, but the league has final say in where a clan will start. Factors used to determine clan placement include, but are not limited to the clan’s league experience, roster composition, individual player skills, and reputation.

(last edited 02/27/07)

B. Changing Divisions

TFL encourages clans to strive to reach the next level. With that in mind, the following will apply to clans moving between divisions in TFL:

Movement to a Higher Division
If a clan wins the title match of their division, they must successfully defend the title in their next two (2) matches. If the clan accomplishes this, they will be moved to a higher division. In addition, if a clan achieves a record of plus six (6) wins over .500, they will be moved to a higher division.

Movement to a Lower Division
If a clan achieves a record of minus six (6) loses below .500, they will be moved to a lower division. In addition, if a clan has a streak of six (6) loses, they will be moved to a lower division.

The Admins reserve the right to move a clan between divisions at any time.

(last edited 02/27/07)

7. Clan Operations

A. Clan Roster/Member SteamID and Clan Information

Each clan will be required to maintain a complete and accurate clan roster on the TFL Site. Leaders who have access to the Clan Management function will be able to maintain this roster. Each Clan will also have to provide a current list of SteamID's of all members playing on their roster. This information is used for tracking and various other details available to League Admins. Clan leaders will also list working email addresses as a source of contact. This is to allow timely communications between TFL Staff and clans and between clans. Any clan found to have an inaccurate or incomplete clan roster or incomplete contact information will be placed on suspension till one or both violations are resolved to the satisfaction of your Division Admin.

If a player requests to be removed from a clan roster, it is the responsibility of the clan leader to do so in a timely manner. Any documented player request to be removed that does not occur within 5 days will result in the offending clan or clan leader to receive a 1-week suspension from TFL match play. It is the player's responsibility to inform the clan leader that he no longer wishes to play in that organization. It is also the clan leader's responsibility to maintain an updated roster.

If a player claims that he/she has requested to be removed from a given roster and has not been removed by his/her Clan Leadership, please refer to E. Player Removals.

(last edited 02/27/07)

B. Roster Violations

Non-Match Violation

Any clan found to have an inaccurate or incomplete clan roster will be placed on suspension till one or both violations are resolved to the satisfaction of your Division Admin.

Clans may seek their opponent’s permission to play a new recruit in a match. Once permission is given, no dispute involving said player would be accepted as it pertains to this section. Logs will suffice as proof of said permission upon request by any TFL Admin. Admins do not have the power to Add/Remove members from rosters once they are locked from 12:00AM on Thursday until 12:00AM on Friday. However, if a recruit is allowed to play via agreement, the 9v9 admin has the ability to allow that player to bypass RingerFree's detection algorithm. This will only be done if both clan leaders contact the 9v9 admin expressing their consent to allow the non-rostered player to play. The 9v9 admin reserves the right to refuse to add this player for ANY reason. It is a request, not a process. Do not request to use a recruit that is still listed on their old team's TFL roster, but the 5 day grace period has not expired yet.

Match Violation

A non-rostered player is defined as a player of a clan who is not listed in any form on the TFL roster page of the clan in question. Any clan found to have a non-rostered player in a match would be subject to a thorough investigation. Upon completion of said investigation, the Division Admin will hand down a ruling based on the results of the investigation.

If a clan can prove that the non-rostered player is in fact apart of their clan, only the round or rounds in which the non-rostered player played in will be forfeited. Proof of this can and will consist of logs from a previous organized league match such as CAL/STA/IGL/OGL, in which said player is shown in the match, or from a clans server log in which said player is practicing with the clan. Excessive violations of this rule will constitute increased resolutions including but not limited to 2-week suspension and or removal from the league.

If a clan cannot prove that the non-rostered player is a part of their clan, that clan will be subject to TFL’s Ringer Rule.

A mis-rostered player is defined as a player who has a SteamID entered incorrectly, but can be verified as the player in question through FF databases, server logs, ip lookups, or other resources. A mis-rostered player is different than a non-rostered player. Clans found guilty of having and or using a mis-rostered player in an official TFL match, will run the risk of having said match and or round(s) forfeited in which the mis-rostered player in question was used. Admins reserve the right to determine said course of action.

Using a player banned from the TFL for any reason will invoke the same penalties as using a ringer.

(last updated 02/27/07)

C. Conduct with TFL Admins

Clans and clan representatives are expected to be courteous when dealing with TFL staff. By the same token, we will extend the same courtesy to you.

Refusals to provide requested logs, demos, screenshots and/or other files, respond to emails or other methods of communication, and/or maintain tact and courtesy when communicating with TFL staff is grounds for suspension or removal.

To put this in plain English, the TFL staff will be courteous to you when attempting to resolve a dispute or perform their duties. Please extend this same courtesy back to them. Failure to do so *can* incur undesirable consequences.

(last edited 02/27/07)

D: Sportsmanship

Poor sportsmanship is defined as follows:

Abusive and offensive general conduct & language during TFL-sanctioned matches, Official TFL IRC channels, and TFL match write-ups.

Those clans and individuals that choose to endeavor in unsportsman-like conduct will be subject to IMMEDIATE sanctions pending review by league officials ranging from a warning to removal from the League. Clans and individuals removed from TFL will be required to resubmit their registration to the League Director for reconsideration.

Admins reserve the right to determine what is and what is not offensive.

(last edited 02/27/07)

E. Player Removals

The normal procedure for removing/adding players either prior to/after the TFL rosters lock is by way of the Clan Captains (Clan Leadership), as it is their responsibility to manage their team's roster efficiently in TFL.

If a player claims that he/she has requested to be removed from a given roster and has not been removed by his/her Clan Leadership, the following rules apply to ensure player removals are performed by the Clan Leadership in a timely manner, as well as ensuring the Clan is not abandoned by the player at the last minute. The player must complete the following procedure:

1. Advise the Clan Leadership that he/she wishes to part company.
2. Email his/her Clan Leadership (See Clan Contacts Page) and carbon-copy (CC:) his/her Division Admin of his/her request to be removed from their roster. It is also encouraged to CC: your new Clan Leadership as well.

IRC Logs are not under any circumstances acceptable as the above required documentation.

These steps must be completed and recieved by TFL Staff no later than three days prior to the next match (The Monday prior to your next scheduled match). Failure to do so will result in the player's ID remaining on his original team's roster until the TFL rosters unlock.

Failure of Clan Leadership to remove a player from his/her TFL Roster after the player has provided sufficient notice will result in a one week suspension for the offending clan, subject to DivAdmins' discretion. Further incidents will incur more severe sanctions.

The reason we require players to email their requests for removal is to provide a paper trail that demonstrates that the player in question isn't abandoning the clan at the last minute. This is also proof for the player that reasonable notice (Minimum of 3 days before match day) was provided to Clan Leadership, so they're held accountable as well.

Your Division Admin will intervene on the Player's behalf only if the above tasks are performed as outlined above or if you contact your Division Admin in irc and present your request to him/her. At the Division Admins’ discretion, he/she may try to contact your clan leader or team captain in irc to get permission to remove you from your clan’s roster. If the clan leader or team captain gives permission for your removal or if the permission is denied, the Division Admin, again at his discretion, may make a judgment call based on the clan’s history and the history of the person requesting to be removed.

(edited 09/01/07)

8. Cheating

TFL has a ZERO TOLERANCE policy on cheating of any kind. If a suspicion of cheating has been brought to the Admin's attention he may spot-check that team in game. If you suspect another clan or member of a clan of cheating we suggest you bring it to the attention of the Admin quietly, his course of action will be to go into that team’s server during their next match and spectate each player. It is in all of our best interest to not accuse a clan of cheating openly or the likelihood of the Admin finding a cheat the following week will be slim. In addition to these spot checks, TFL will randomly spot check game in progress every once in awhile to ensure that everything looks okay. TFL also reserves the right to randomly pull personal demos, server logs, and or HLTV demos to help in their investigations or to spot check for cheating.

Make no mistake this league will not hesitate to deal with cheating clans in the most drastic of manners. Please consider carefully the members you recruit and consider implementing spot checks periodically on your members in practices/prematches to ensure that your team is cheat free.

(last edited: 09/01/07)

A. Banned Console Commands

The following console commands are examples that MAY NOT be permitted for use in the TFL [TFL reserves the right to edit (add to the list or remove from the list) and enforce any console command we deem harmful to a fair playing environment]:

force_centerview
fullupdate
cl_pitchdown 0
cl_pitchup 0
-mlook
any console commands that "center" the crosshair or view to the middle of the screen, or place the crosshairs automatically within 2 inches radius (at 800x600) of the center of the screen.

Exception: Currently, there are exceptions to the rule to allow soldiers to continue using a "rocketjump" script, and for demomen to use the "pipe-down" script. These are the ONLY 2 exceptions.

ex_interp MUST be kept at the default setting, which is "0.1"

cl_lw must be a value of "1"
cl_lc must be a value of "1"

(last edited 09/01/07)

B. Hooks/Wrappers

Hooks or OpenGL Wrappers with the following features are banned from league play:

Flag Timers
Speedometers
Pogo-Style Jump/Bhop Assist

Any player found using these features will be banned and the match may be overturned.

(last edited 02/27/07)

C. Ringers

TFL will not tolerate any kind of "ringers" or "multi-clans" within TFL. That is to say, Any TFL clan who plays a TFL match with a player who is not on their official team's roster will be considered a "ringer." (with the exception defined in the previous section) Any player on an official TFL team roster, who plays in a match under a tag different from his TFL clan tag, will be considered "multi-claning." (This includes other TFC Leagues) In short and to the point, you may not play for another clan in any league, while playing in TFL. Guild formats (including 5vs5), Mutt tourneys, For Fun Formats, (IE: FnF) etc. are the only exceptions to the above, as the rule applies to organize clan leagues and matches only.

Clan's using ringers, and or lending out ringers will forfeit their match or matches, have their rankings reset, and forfeit any title that the clan or clans may or may not hold, and serve a two-week suspension. Clans found to have a "multi-claner" in TFL, or found to have a member of their roster multi-claning, will be removed from TFL and not allowed to rejoin.

(last edited 02/27/07)

D. Other

Pak Editing: ANY pak editing - Client-side bots - TFL Admins will vote on any bot issues after thoroughly reviewing the incident.

Global Timers: The use of global timers in TFL (ax1.wav) has been banned. Clans who members have been found to be using such timers will be subject to TFL's Clan Integrity Rule.

Console Commands: Any command that can be activated/deactivated through the console, or by a script that is activated by pressing a key on the keyboard, that clearly gives a player an advantage over others that the command was not intended to give: ie the Timerefresh Exploit.

Proxies: Any player found using a proxy will result in his/her Clan being disqualified. Excuses such as "It's only for my location binds" are not acceptable. We certainly can't take it on faith that every player in TFL is simply using their proxy for location binds.

Map Hacks: Any player found using a wall-hacked map during matches will result in his/her clan being disqualified. Any players found using retextured or untextured maps will also result in his/her clan being disqualified.

Explosions Sprites: Clear/transparent/translucent explosions sprites in any form are banned in TFL, as they give a distinct advantage over your opponents. Custom explosion sprites are permitted provided that the explosions are solid and are not reduced to a level less than 30% of the default Valve explosions. Examples of illegal sprites can be viewed here: http://tfc.clan.halibut.com/images/explosions.html If you are not sure about whether or not an explosion sprite is legal or not, PM an admin in #tfleague.

Bunny Hopping: TFL has lifted the current ban on bunny hopping provided that clans do NOT exceed/break the 170% max speed allowed in the game. However the rule will remain in the books should the need arise to reinstate the rule/ban.

Chop Hopping: Chophopping is illegal in the TFL. Chophopping is defined as The employment of a series of commands which enable a player to gain speed passing the 170% speed barrier by use of script or commands bound to keys or a mouse wheel.

Elevators: It is illegal to use objects (dispensers, sentry guns, etc) that function as a means to hold elevators or lifts in a position other than their "at rest" state.

Exploits: Exploits used in a malicious manor to gain and place an unfair advantage over your opponent in any map used and played with in TFL will be grounds for an automatic forfeit and a two week suspension. Exploits used in TFL's Championship Tournament will be expedited in the same manor as stated above and the offending clan will not be allowed to continue in the Tournament. Exploits used in TFL's Championship Match will be expedited in the same manor as mentioned above and the offending clan will not be allowed to take part in the following season's Championship Tournament

This rule can and does extend to TFL's Sportsmanship rule. It also, can, and will be treated as if it were one in the same. TFL reserves the right to determine the extent of this and any violation of this rule. Proof of such intentions and or act's must be in the form of a demo and brought to the immediate attention of your division admin.

A couple examples of bugs/exploits are: Items that are, but not limited to grenades/nail grenades, and flags which are not intended to go through walls/ceilings/floors/objects. Using grenades of any kind to propel through entities not intended to be passed though. Including, but not limited to lasers, push entities, trigger_hurt entities.

A few examples of acceptable exploits: Rocket jumps, conc jumps, and grenade jumping. Emps, gas grenades and conc grenades DO NOT apply as the "energy" passes through the wall/ceiling/floor/objects.

(last edited 02/27/07)

9. Disputes

A. Submitting A Dispute

Should there be any kind of dispute between Clans, you must submit the dispute using the website interface on the ff.tfleague.com site. A dispute admin and/or division admin will then look over both sides, and make a decision based on the grievance before them. To aid in this decision, clans should provide as much evidence as possible in the form of server logs, HLTV/demos, and screenshots. If a Dispute Admin is not available in IRC, contact your Division Admin.

To aid in the rendering of a decision of a dispute, please have at least one member of your clan record a demo of a TFL match. Without at least a demo, disputes may not be heard or decided on based on "he said she said" disputes.

All disputes must be filed before the dispute time limit expires. The current dispute time limit is 6 days from the end of the match. Any dispute that involves cheating such as wall hacks, aim bots, or anti-conc cheats is not affected by this time limit.

(last edited 02/27/07)

B. Resolving A Dispute

All disputes will be resolved in a timely manner or until such time that TFL Admins are satisfied that the proper decision has been made. If more time is needed, both clans involved will have the decision sent to them via email. Should the decision not be satisfactory, clans have the right to appeal any decision made in the following order:

Division Admin
League Admin
TFL League Director
Any decision made by the League Director is final.

Disputes will be resolved with consideration of both the letter of the law, as well as the intent. Although we have written rules to codify the standards which we expect from the players of TFL, the administration can and will use their best judgment to determine what the original intent was when the rule was created. We support the values of fairness, honesty, integrity, and sportsmanship. It is these principles, which we will use to determine the outcome of every dispute. If more time is needed to ensure that the aforementioned values are upheld, then our Admins will take such time to ensure that each dispute is handled with fairness and integrity to all parties involved.

(last edited 02/27/07)

10. Rule Updates

It is your responsibility to periodically check for updates on this page. TFL reserves the right to make changes, add or remove rules governing this League at any time without notice to anyone, written or otherwise.

We will attempt to date the latest revision on each section and sub-section page. This may not always be entirely accurate, but we will make a "good faith" effort to ensure that the dates are current. In addition, rule changes are typically announced on the news page at www.tfleague.com.
(last edited 02/22/03)

11. Miscellanea and Summation

Following are various rules that are commonly asked or are important enough to be mentioned again.

1.) Upto date RingerFree must be used
2.) HLTV demo links must be provided within 24 hours, and remain active until the dispute time limit expires.
3.) Personal demos are required to be recorded and kept for 2 weeks.
4.) Server logs are to be provided on request to TFL staff, or your opponent of said match, within 24 hours of request. They must remain available until the dispute time-limit expires.
5.) Being rude or abusive to TFL staff will be dealt with in a grave manner.
6.) There are no set max defense, turtling or chasing rules in the TFL. This may change at any time, as certain maps may require adjustments to ensure a fun match.

(last edited: 09/01/07)

Account and Password sharing

"Login-Sharing" is defined as giving out the username/e-mail and password associated with your STEAM Account to a third-party to whom the STEAM account does not belong. “Community” steam accounts are examples of login-sharing. This is a violation of Steam's subscriber agreement.

ALL parties caught sharing accounts on or after May 20, 2006 will be removed from TFL and added to our banlist as follows:

1. Login-sharing with a currently banned player is a permanently bannable offense for the PROVIDER regardless of the situation in which the login-sharing occurs, and ALL IDs of the provider will be banned. "I didn't know it was a banned player" is no excuse. Any logins that can be shown to have been used by a banned player prior to May 20, 2006 will be placed on the ban list as compromised, however the previous owner of that login will not be banned personally.

2. Login-sharing with a non-banned player in a league that has policies against login-sharing is illegal if the login-sharing was used to allow a non-rostered player to participate in a match. This will result in a 6 month ban for BOTH the PROVIDER of the ID as well as the USER/receiver of the ID. However, ALL parties, both the provider and recipient, caught sharing accounts in this manner in TFL matches after May 20, 2006 will be suspended for six months.

3. Login-sharing with a non-banned player in order for the recipient to participate in a match in a league that does not regulate login-sharing will result in a 3 month Suspension for BOTH the PROVIDER of the ID as well as the USER/receiver of the ID.

The sale, transfer, or gift of steamids to a friend or family member is not a bannable offense, although it DOES violate Steam's subscriber agreement. If you still choose to hand your account information to a third party, it is in your best interest to notify the leagues in which you play that you have given away that STEAMID and no longer have access to it.

May these rules be incentive NEVER to share your login with ANYONE, and NEVER to accept or use the login information of another player. If you are unsure of the security of your account, we advise you to change your password.


(last edited 02/27/07)