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 two penalty points. If both participants are in the top 10 then the refusal will be punished with 3 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.

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 half must be taken and uploaded to the match page within 24 hours.

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

The side with rcon access must take rcon status screenshots.

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

In order to take a status/rcon status you have to use the console command "status"/"rcon status" (don’t forget to enter your rcon password) 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.

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 half of a 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.

A demo request has to be made in the following format: Team side (e.g. CT)

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.

In all Ladders: You are allowed to demand one demo per match.

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.

2.3. Aequitas

Players must upload their Aequitas files to the ESL page within 24 hours of the match date.

If any Aequitas files are missing after 24 hours then you must open a protest ticket within the 72 hour protest period to complain. The player(s) will get an additional 24 hours from the opening of the protest to upload their Aequitas file(s).

If after this deadline the player(s) still have not uploaded their Aequitas file(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 Aequitas file(s) by this deadline, then the player(s) and team will receive 1 penalty point.

3. Settings

3.1. Player settings

3.1.1. Anti-cheat (Aequitas)

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

If the website is down, making Aequitas unusable, then the match must be postponed.

3.1.2. CVARs

The following CVAR values must be used:

• mat_dxlevel 80/81/90/95 (using a mat_dxlevel between 80 and 95 is mandatory)
• mat_bumpmap 1/0 (if you use "mat_bumpmap 0", you also have to use "mat_specular 0"; if you use "mat_bumpmap 1", you can either use "mat_specular 0" or "1")

The above settings are forced by Zblock, i.e. joining the server with wrong client settings is not possible. Therefore you are not allowed to file a protest if your opponent uses different settings.

• mat_fastnobump 0
• mat_fastspecular 1
• r_rootlod 0/1/2 ( 0, 1, 2 is allowed)
• cl_pitchspeed 225
• cl_yawspeed 210
• net_graph 0/3 (0 and 3 are allowed values)

The usage of "vprof" and any related functions is forbidden.

3.1.3. Illegal scripts

In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts:

• Stop Shoot scripts [Use or Awp scripts]
• Center view scripts
• Turn scripts [180° or similar]
• No Recoil scripts
• Burst fire scripts
• Rate changers (Lag scripts)
• FPS scripts
• Anti flash scripts or binding (snd_* bindings)
• Bunnyhop scripts
• Stop sound scripts

3.1.4. Custom files

Custom-files are not allowed. Everything is considered as custom-file which changes or replaces the original ingame-grafics, *.gcf-files or sounds. This also includes changed HUDs, Scoreboards or sounds (volume, soundscapes).

3.1.5. Illegal programmes

3.1.5.1. Config changes - Videocard drivers or similar tools

Changing the game graphics or textures with the help of videocard drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. Nvidia SLI Display, Rivatuner Overlays) is illegal. Failure to comply with this rule will result in 6 penalty points for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized.

Punishment will be given regardless of whether the script/binding is executed via external hardware or software.

The usage of "vprof" and any related functions is forbidden. Also binding any snd_ command is forbidden.

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

Using the latest version of zBlock is mandatory.

3.2.3. CrashBlock

CrashBlock may be used but is not mandatory. Announcement news

3.2.4. Config

Using the latest server configs is mandatory. The .zip file contains configs for all ladders plus a readme file.

3.2.5. Serverplugins

No Serverplugins except the above listed are allowed to be used.

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. If you cannot come to an agreement with your opponent then the match is split over two servers by half or by map.

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.1.1. Server Tickrate

It is advisable to play on a server with a tickrate of 100. If you cannot reach an agreement you have to play on the server with a tickrate of 100.

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

Before a match starts, both teams must state that they are ready to start the match. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated.

4.1.4. Map check

Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug.

4.1.5. 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.5.1. SourceTV delay

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

4.1.5.2. 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.5.3. LAN matches

It is possible to play a match on LAN when the following requirements are fulfilled:
- both sides agree (either via support (both sides) or protest)
- the ticket must be filed at least 72 hours before the match
- Aequitas is still mandatory
- Protests, which are not comprehensible by an admin will be rejected (e.g. ringer, fake match, deceptions, etc.)

4.2. During the match

4.2.1. Choice of Side

In all CS:S matches you have to play a knife round first. The winner will then choose the side. Only knives and kevlar vests are allowed to be used.

4.2.2. Number of players

Following terms of minimum number of players are:
2on2: 1on2 is forbidden, only 2on2 is allowed.
3on3: Only 3on3 is allowed.
5on5: 4on4, 4on5 and 5on5 is allowed. If one player in a team is missing the team can nevertheless play the match. The opposing team can decide freely whether they want to play with all players or with one player less as well.

4.2.3. Server crash

If the server crashes before three rounds have been completed, the server must be restarted and the match's score will be reset to 0-0.

If the server crashes after the third round has been completed, the match must be restarted with startmoney 5000 and the score will be counted from the last completed round. The start money is set to 2000 and the team that lost the last round kills itself using "kill" in the console. This round does not count. The match begins with the following round. The start money has to be set to 800 again.

4.2.4. Player drop

If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server will be paused at the end of the current round (see rule Usage of Pause function).

The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed.

When the match is continued, the start money is set to 2000 and the team that lost the last round kills itself using "kill" in the console. This round does not count. The match begins with the following round. The start money has to be set to 800 again.

4.2.5. Change of players

Players can be changed at any time but the opposing team has to be informed in advance. If necassary 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 HL2/CSS and it's recommended to do a status screenshot when a new player arrives on the server.

4.2.6. Game intermissions

If a game is interrupted, the match is valuated up until that point. The game is continued according to the following procedure: - The start money is set to 2000 for the remaining game time. - The team that lost the last round kills itself using the function “kill” in the console. This round does not count. - The game begins with the next round. - Should further maps have to be played after this map, the start money must be set back to the normal value (800).

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.7. 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 (freezetime). You have to announce the reason before or immediatly 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 (see 7.3. Unsportsmanlike behaviour). If the problem can't be solved (max. 10 minutes pausetime) see rule 5.7.6. Game intermissions.

4.2.8. Abortion of a map after 16 victorious rounds

If a team achieves 16 won rounds at a map, the teams can abort this map. All missing rounds of this map will then be added to the team that stayed on the server.

4.2.8.1. Abortion of a map after 10 victorious rounds

In MR9 ladders (Handgun, Aimmap) the match can be aborted under the same conditions after achieving 10 won rounds.

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.

Boosting, sky walking, sharking

To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.

Climbing

Climbing with help of the team mates is allowed in general. Not allowed are positions where textures disappear in walls or grounds if a special movement (e.g. a jump) is required. For example the barbed wire fence in prodigy and nuke upper hall roof.

Grenades

To throw grenades inside walls is not allowed. Above walls and roofs is allowed.

Self-kills

Self-kills by console or by other means (e.g. Abysses) in order to receive money quickly or in order to shorten the round time is strictly forbidden.

Any bug-using is forbidden.

4.3.1. Bomb

Planting the bomb

To plant the bomb in a way that it cannot be reached is forbidden. Places that can reached with help of a team mate are allowed. Violating this rule will result in the deduction of 3 rounds.

Hiding the bomb

You are allowed to move the bomb, but you must not move it to a place where your opponent cannot pick it up. Violating this rule will result in the deduction of 3 rounds.

4.3.2. Map specific bugs

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

de_dust2

Only one player at a time is allowed to stand on the following position: #1

The following positions are illegal: #2, #3, #4, #5, #6, #7, #8

Looking through these gaps is not allowed: #9, #10

de_cbble

Looking through this gap is not allowed: #1

de_tides

Looking through this gap is not allowed: #1

de_inferno

To plant the bomb at/in the fountain so that it cannot be defused is illegal.

The following positions are illegal: #1

de_nuke

The following positions are illegal: #1, #2

de_train

The following positions are illegal: #1, #2

de_tuscan

Looking over this wall is not allowed: #1

4.3.3. Spraylogos

The use of custom spraylogos is restricted. Spraylogos must not: - contain racist contents - show weapon/player models or bombspot logos etc. or any other things that might confuse the players - contain single-coloured textures that are used to achieve a higher contrast - spraylogos that look like parts of a cheat (e.g. esp-boxes) are forbidden. Usage may be punished according to Unsportsmanlike behaviour!

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. Ladder specific rules

5.1. 3on3 Ladder

5.1.1. Map-Pool

The current Map-Pool can be found here.

5.1.1.1. General rules for all 3on3 Ladders

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

Because of the reason that in 1on1, 2on2 and 3on3 leagues pausable "1" is obligated, any player can pause the game. 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 according to 7.2.6. Game intermissions. To file a protest is obligated in this case.

6. Penalty points

In general, a player can receive up to 6 penalty points, and a team up to 4 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.

6.1. Illegal scripts

Using illegal scripts will be penalized with 2, 4, 6 or 12 Penalty Points if the script leads 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.

The use of No-Flash and No-Recoil bindings/scipts in any and all forms will be punished with 6 Penalty Points after the first violation without active usage and 12 Penalty Points after repeated violation or after active use of them.

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

6.2. Weapon choice in special ladders

Using a restricted weapon will result in two penalty points for the player and the team (the maximum per match is four) and the deduction of three rounds.

6.3. Game specific penalties