1. Ladder Rules

1.1. Challenging

In a ladder any participant may challenge any other. The challenge may be refused by the challenged if they choose. In ladders with more than 20 participants compulsory challenges are activated. If a participant is within 20 places above the challenging participants the refusal will be punished with one penalty point. If both participants are in the top 10 then the refusal will be punished with 2 penalty points.

A challenging participant from the newcomer pool (unranked) is considered as being at the bottom of the ladder, therefore the 20 participants ranked last in the ladder would be punished for rejecting a challenge.

Participants that have more than 5 outstanding challenges in a ladder, no matter if the matches are confirmed or not, may not take on any further challenges. This is scripted into the ESL system and cannot be changed.

1.2. No show

If your opponent does not show after 20 minutes, you must enter the result as your opponent did not appear in time. Do not enter a default win for yourself.

In Instant Challenger matches the no show time is 10 minutes.

1.3. Several squads (sub-teams) per team in one ladder

Any team may enter as many squads into any one ladder. However, only one squad can qualify for a premiership. A team is not allowed any more than one squad in a premiership.

During ladder play, no two squads from the same team are allowed to play each other.

1.4. Agreements

Certain agreements between participants are allowed to slightly differ from the ESL rules. Agreements that differ greatly from ESL rules are however not allowed. Please note that the ESL rules were made to ensure a fair match for all participants. You are not allowed to file a protest after the match if you think that the agreements made before the match in the end resulted in a disadvantage for your or your team.

Rules that can be changed with agreements are explicitly stated. Rules that do not explicitly state they can be changed by agreement, cannot have agreements made.

All arrangements between participants, made in addition to the ESL rules have to be written down in the match comments. The other participant has to confirm the arrangements also in the comments. To avoid abuse of the edit function, a third comment must be written.

Please also keep screenshots and/or logfiles of your arrangements. If you do not fulfil these requirements, any protests or supports concerning arrangements will be rejected.

The following rules may never be changed by arrangement:
- Entering results for matches that have not been played
- Allowing players to play that are barred because of penalty points, or are barred in the league due to a ban
- Allowing players to play that in leagues with premium requirement that are barred for not having Premium
- Allowing players to play without the Anti-Cheat

2. Match Media

All match media (screenshots, demos, etc) must be kept for at least 14 days. In general, you should upload the match media from a match to the match page as soon as possible. Faking or manipulating match media is of course forbidden and will result in severe penalties. Match media should be named clearly based on what it is. It is not possible to file a protest or write a support ticket to complain about bad match media naming. However, if an admin is hindered in their work because of bad match media names then it can be punished for.

2.1. Screenshots

2.1.1. Score screenshot

A screenshot of the scoreboard at the end of each round must be taken and uploaded to the match page within 24 hours.

2.1.2. Status screenshot

A status screenshot must be taken:

• at the beginning of the match
• in case of a server/player change
• if a player reconnects

Status screenshots made with the help of programs like HLSW etc. are not sufficient.

In order to take a status you have to use the console command "status" followed by "jpeg".

It is the responsibility of both sides to ensure all screenshots are uploaded to the match page within 24 hours of the match ending.

After a match, the teams should compare the SteamID TF2 with the ones given in the team-sheets. If there are any friction with the SteamIDs open a protest.

2.2. Demos

It is mandatory for all players to record point of view (POV) demos for the full duration of all matches without exception. Players should record one demo per map. SourceTV demos are not a replacement.

Incomplete, defective, manipulated or edited demos will be treated as missing demos.

2.2.1. Requesting Demos

Demos can only be demanded up to a maximum of 30 minutes after a match via the 'Request match media (demos/replays)' function on the match details page.

If it turns out that your demo request was not made according to the rules, you can correct it within the 30 minutes by posting it as match comment or reports. This is possible as long as the other side did not yet fulfil the previous request. If a demo request is corrected, the upload time limit will be extended by 30 minutes from the time of correction.

If a player or a team illegally aborts the match, they lose their right to demand demos.

You are allowed to request the demos of a maximum of 2 players.

Both sides should check the demo requests of a match after the 30 minutes has passed. The requested demos must be uploaded to the match page within 24 hours (packed in separate *.zip files). If you use a program other than Winzip to zip your files, make sure that you choose "Compression method – normal". If you do not then you will get an error message like "file corrupted" and the upload will be aborted.

If any demo is missing after 24 hours then you must open a protest ticket within the 72 hour protest period to complain. The player will get an additional 24 hours from the opening of the protest to upload their demos.

If after this deadline the player(s) still have not uploaded their replay(s), then the match may be deleted and the player(s) and team punished with 3 penalty points. If the player(s) do upload their replay(s) by this deadline, then the player(s) and team will receive 1 penalty point.

2.2.2. Uploading Demos

Demos have to be packed into .zip archive. While being uploaded the server will check whether the file is corrupted or not. If you use WinRar to zip your files make sure that you choose "Compression method - normal", if you don't you will get an error message like "file corrupted" and the upload will be aborted. Apart from that all match media has to be uploaded to the ESL-Website. You are not allowed to upload your match media to your personal web space etc.

2.2.3. Editing Demos

It is strictly forbidden to edit demos.

3. Settings

3.1. Player settings

3.1.1. ESL Wire Anti Cheat

ESL Wire Anti Cheat is mandatory for all players to use for the full duration of all matches without exception. If a player cannot use ESL Wire Anti Cheat then they are not allowed to take part in a match.

If the website is down, making ESL Wire Anti Cheat unusable, then the match must be postponed.

3.1.2. CVARs

The following CVAR values must be used:

• cl_pitchspeed 225
• cl_yawspeed 210
• mat_softwarelighting 0
• mat_texture_limit -1

3.1.3. Illegal scripts

The usage of the following scripts is forbidden:

• Doublejump scripts
• Fastshoot scripts
• Stopsound-scripts (snd_)

Regardless of being actively used, if these scripts are found in parts or in full in your config files, the player and the team will be penalized. Punishment will be given regardless of whether the script/binding is executed via external hardware or software.

3.1.4. Custom files

Custom files are absolutely forbidden. Custom files are files that change or exchange the in-game graphics (materials, models, particles, ...), gcf or sounds (volume, soundscapes). HUD modifications and custom hit sound (sound/ui/hitsound.wav) are allowed.

3.1.5. Content of the Configfolder

In the config folder you are only allowed to have config files. Pictures, Demos, Screenshots and zipped Files are forbidden. If an Admin is hindered in his work because of too many unclear/chaotic config files, penalty points ( 1-3 ) will be distributed. Protest and Support tickets opened because of this rule are illegal and will be ignored.

3.2. Server settings

Only the following server settings and mods may be used.

3.2.1. VAC2

VAC2 must be enabled on the game server.

3.2.2. Server Settings

The official ESL TF2 server settings mentioned in the various game rules must be used. All server settings must be checked before the match begins. As soon as the match begins, the players therewith accept the set configurations.

Should any changes in the server settings take place during a running game, the server administrator is to be informed immediately. In case of a protest, it must be proven using screenshots and /or demos.

3.2.3. Server plugins

The maximum Field of View (tftrue_maxfov) allowed can only be changed if both teams agree on the value via the match comments. Otherwise, it should be set to 90.

4. Match rules

4.1. Before the match

4.1.1. Server choice

The ESL does not supply servers for matches, players and teams must provide their own and come to an agreement with their opponent as to which to use. In case no agreement can be reached, each team decides on a map which is then played on each of the two team’s servers. The teams can of course play on a completely neutral server, if they decide to do so.

The internet is changing continuously and the connection to a server is not always perfect. Players and teams have to agree on a server that offers both sides an equal ping. Nevertheless every player should know, that they will sometimes have to play with a bigger ping difference. In this case we have to appeal to the sportsmanship and fairness of the players and teams. The right to change server or fake lag does not exist.

4.1.2. Nickname and clan tag

Each player has to use a nickname that is at similar to the nickname he/she entered in his ESL player sheet. You are not allowed to change your nickname in-game. In team matches the players are allowed to use a clan tag, but it has to be the same for all players of this team. However you cannot file a protest or write a support ticket to complain if your opponent breaks this rule.

If an admin's job is hindered because of wrong or difficult nicknames or clan tags, the players and team concerned will get penalty points.

4.1.3. Match Broadcasting

All forms of game broadcasting are allowed if both sides agree. If one side wants to broadcast a match, the details of the broadcast should be discussed before the match takes place. Further details can be found in rule 1.4 Game Coverage.

4.1.3.1. SourceTV

It is legal to broadcast a match via SourceTV as longs as one teams wants to do so and is able to provide the necessary server. Any other kind of broadcast is legal if both teams agree on it. If you want to broadcast a match please discuss it with your opponent in advance. For further information please check 1.4 Game Coverage . However you are obliged to upload an rcon status (and tv_status) screen that shows the necessary delay of at least 90 seconds.

4.1.3.1.1. SourceTV delay

If SourceTV broadcasts a game, the delay has to be 90 seconds or more.

4.2. During the match

4.2.1. Server crash

Should the server crashes during a match, the match must be paused. The points that have been scored so far will be rated. If the server problem can't be solved within 10 minutes, the complete match must be stopped and has the continued later. To file a protest is obligated in this case.

4.2.2. Change of players

Players can be changed at any time but the opposing team has to be informed in advance. If necessary the game can be paused (see rule Usage of Pause function). This change may not take more than 5 minutes. After the waiting time the game can be also continued without the full team and the player can join in the running game. Changed players must be registered in the team with their SteamID TF2 and it's recommended to do a status screenshot when a new player arrives on the server.

4.2.3. Game intermissions

If the match is interrupted during a map, the points that have been scored so far will be rated.

This rule serves the purpose of covering unexpected intermissions that are not wilfully brought about by the teams. So if a game is interrupted but cannot be continued on the same day, the remaining game time can be played at a later date but within seven days. If the teams/players fail to agree on a date, an admin will determine the date. If a team/player fails to appear an admin will decide whether the match is rated as 'did not show up' or 'match abort'.

4.2.4. Usage of Pause function

If you have a problem that prevents you from playing on, you are allowed to use the pause function. The pause function has to be used at the beginning of the next round. You have to announce the reason before or immediately after you used it. If no reason is given, you may unpause the game and continue playing. Unpausing or pausing the game without any reason will lead to penalty points. If the problem can't be solved (max. 10 minutes pausetime) see rule Game intermissions. If the opponent agrees you are allowed to pause during the round.

4.2.5. Spamming

Up to 2 penalty points for misusing the in-game chat function for excessive spamming in order to irritate the opponent or to disturb the course of the game. The chat function is solely meant for communicating with your opponent.

4.3. Bugs and forbidden actions

The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary.

Sky walking, sharking

Sky walking, floating and sharking are all forbidden.

Taunt bug

Taunting while falling from ledges is forbidden.

Any bug-using is forbidden.

4.3.1. Map specific bugs

The following map specific bugs/positions are forbidden to use:

cp_gravelpit

You are not allowed to build a teleport in the red spawn area.

You are not allowed to put stickies under cp A and damage targets trough the floor.

4.4. After the match

4.4.1. Right to write a support ticket/file a protest

Only teams/players involved in a match are allowed to write a support ticket or to file a protest.

4.4.2. Game Abort

If a team aborts a match before it is finished, a win may be granted to the remaining team if the match advanced to a point where the end-result can be determined. If your opponent should deliberately leave the game, you must definitely file a protest. You are not permitted to enter a result yourself. This would be penalized as a faking of results.

5. Penalty points

In general, a player and the team can receive up to 6 penalty points per match, unless a single violation has a higher punishment. A team is only punished once per violation, regardless of how many players. Where a player or team receives penalty points for multiple violations, the penalty points are added together.

5.1. Illegal scripts

Using illegal scripts will be penalized with 2, 4, 6 or 12 Penalty Points if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized.

Regardless of active use, if these Scripts are found in parts or in full in your config files, this will be penalized.

5.2. Game specific penalties

6. Ladder specific rules

6.1. 1on1 Scout Ladder

6.1.1. Map-Pool

Map overview
	Timelimit	Winlimit	Stopwatch?
duel_duel2_pro	-	11
dm_whiskas	-	11

duel_duel2_pro can be downloaded here.

dm_whiskas can be downloaded here.

6.1.2. Class restrictions

You are just allowed to use the following classes:

• Only the Scout class is allowed

6.1.3. Interchangeable weapons

The following restrictions are applied to interchangeable weapons:

• No Interchangeable weapons are allowed

6.1.4. Numbers of players

Following terms of minimum number of players are:

• Only 1on1 is allowed

6.1.5. Playerdrops

Should a player drop during a game (e.g. disconnected due to technical problems), then the game is paused (see rule Usage of Pause function). If the dropped player is not rejoining the server in time for the next round, at the beginning of the next round the pause function must be used until the team is complete again.

The waiting time for dropped players is 10 minutes. If a player does not rejoin in this time the match must be stopped and if necessary continued. To file a protest is obligated in this case.