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

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

The side with rcon access must taken 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 "snapshot".

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. HLTV demos are not valid.

Incomplete, defective or manipulated 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

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.

Maximum amount of demos that can be requested:

- 5on5,3on3,2on2 : 4 demos per match, a maximum of 2 demos per player

- 1on1: a maximum of 2 demos per player

Both sides should check the demo requests of a match after the 30 minutes has passed. The requested demos must be uploaded to the ESL page within 48 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 demos are missing after 48 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 demos(s).

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

3. Settings

3.1. Player Settings

3.1.1. Scripts

The following scripts are legal:

• buy scripts
• toggles (like sneaking/duck)*
• weapon switch scripts
• demo scripts
• DuckJump script

All other scripts are illegal, especially if they provide a gameplay advantage (bug use, no recoil, bunny hop, multiple-ducking etc.).

3.1.2. CVARs

The following must be set

• cl_movespeedkey 0.52
• cl_pitchspeed 225
• cl_showevents 0
• cl_pmanstats 0
• cl_lc 1
• cl_lw 1
• d_spriteskip 0
• gl_monolights 0
• gl_picmip 0
• gl_polyoffset 0-4
• s_show 0
• s_a3d 0
• lightgamma 2.5
• texgamma 2.0
• net_graph 0

Binding "+duck" on your mouse wheel is also forbidden.

Other values can be changed as long as they do not result in an unfair game play advantage that is comparable to a cheat.

Any wrong client settings will be penalized, even if it is not stored in the Counter-Strike folder. If possible, the scripts and config values should be stored in separate files. The maximum number of config files you are allowed to use for bindings/cvars/scripts/execs is 5. Please note that config files in subfolders also count. The ESL server settings do not count. If an admin cannot do his job properly because of too many config files, the player concerned will get penalty points. Filing a protest or writing a support ticket because of too many config files is not possible.

3.1.2.1. Match deletion due to wrong client settings

A match will be deleted if more than one player is using wrong client settings.

3.1.3. 32 bit

Using Video - Color Quality - Highest (32 bit) is mandatory.

3.1.4. A3D

Using A3D (2.0) is illegal.

Using tools/drivers that result in an A3D like effect it will be punished like using A3D (2.0).

3.1.5. Custom Files

Custom files (except Steam skins) are illegal.

Steam skins are skins that only change the Steam layout or the console. Changing models, crosshairs, the HUD, the scoreboard or any other files is illegal and results in the match being deleted (except for custom scoreboards) and penalty points to your player and team account.

Custom files include CS:CZ models, HLTV models and even little changes like the bomb LEDs or brasses.

Remember that if you own Counter-Strike Condition Zero, your default models are the Condition Zero ones, this will result in penalty points and the match will be deleted.

You can download the official Counter-Strike 1.6 models here.

3.1.6. Graphics tools

Changing the graphic options or textures with the help of graphic card drivers or similar tools or programs is illegal.

3.2. Server Settings

3.2.1. Config

Config files with the settings for all ladders can be found in the eslconfig.zip file which is available for download. It also contains a readme file.

The most important settings can be found on the "Rules & Information" page.

The team/player that provides the server is responsible for the server and the settings. In case of a server manipulation the team/player will be held accountable. In case of team matches this means that any player on the server can be held accountable.

3.2.2. Maps

drax's anti flashbug map pack is mandatory. In addition to that the map de_tuscan has to be available on the server.

3.2.3. VAC2

The server must be VAC2 protected.

3.2.4. Illegal mods

VAC, HLG, Soundcheck, Metamod, Clanmod or AMXMod are illegal.

4. Match rules

4.1. Game preparations

Please resolve any problems that might occur before the match starts. Agreements between the teams/players have to be posted as match comments.

4.1.1. Choice of server

Each team/player has the right to play one half of the match on their/his server. You can only make use of this right as long as the second half of the match has not started and if the alternative server fulfils the requirements as mentioned in the set of rules. If both teams have a server, the first half of the match will be played on the server of the team listed on the left side of the match details.

4.1.2. HLTV

A match can be broadcasted via HLTV without asking the opponent, but the team who ordered the HTLV has to make an announcement via the match comments. The arrangement is up to the teams themselves.

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

4.1.3. Nicknames compulsory

Each player has to use a nickname that is at least very similar to the nickname he/she entered in his/her ESL player sheet. You are not allowed to change your nickname during the match. In team matches the players are allowed to use a clan tag which has to be the same for all players of the team. Filing a protest or writing a support ticket due to wrong nicknames is not possible. If an admin cannot do his job properly because of wrong nicknames, the players concerned will get penalty points.

4.1.4. Agreements

In case of agreements you always have to fulfil the requirements as mentioned under the previous Agreements point.
The following settings can be changed if one party requests it:

- sv_voiceenable 0 to 1

- HLTV

The following settings can be changed if both parties agree on it:

- mp_fadetoblack 1 to 0

- map changes once the map has been set

- accept players of the opposing team who are barred due to "Changing teams"

Agreeing on these changes must not depend on further conditions.

4.1.5. Warm up – Map Check

During the warm up the teams/players have to check whether the server settings are correct, whether the map has been loaded properly and whether the server uses the right maps (Anti Flashbug Mappack + ESL Mappack).

Before the match starts both teams have to say clearly that they are ready.

4.2. Ingame

4.2.1. Choice of team

A knife round has to be played before the match starts. It is up to the winner to choose sides (CT/T). If a team obstructs finishing the knife round before the round ends, the team gets 1 penalty point and the opposing team has the right to choose sides.

4.2.2. Number of players

Matches should be played 5on5, but if either side is missing a player the match can be played 4on5 or 4on4. The other team can choose whether to volunteer to play with one less player.

4.2.3. Player drops

In case of a player drop the pause function is to be used at the end of the round in order to wait for the dropped player for at least 10 minutes.

If there are not enough players on the server after the waiting time, you either have to file a protest or to continue according to Game intermissions. The pause is to be made by the team of the dropped player and unpaused as soon as both sides declare they are ready.

Exception for 5on5 ladders: The waiting time for one dropped player is 5 minutes. Should more players drop the waiting time is 10 minutes. If the complete team requests it, the match can be finished 4on5 after the waiting time.

4.2.4. Game Intermissions

If the match is interrupted during a map, the points that have been scored so far will be rated. The game is continued according to the following procedure:

The start money is set to 2000 and the team that lost the last round kills itself using the function “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. Abortion of a match

If a team/player wins the majority of rounds on a map (e.g. 16 rounds for MR 15), the match can be aborted and the result must be entered (e.g. 16-4).

There is no need to play all rounds.

4.3. Illegal Actions

Any actions that result in an unfair advantage are illegal. This includes bug using of any kind and the following actions.

To throw grenades below walls is illegal while throwing them over walls or roofs is legal. If you do have questions about legal/illegal positions, please write a support ticket (subject: Map bugs).

4.3.1. Shield

Using the shield is illegal.

4.3.2. Mapbugs

de_airstrip, de_aztec, de_cbble, de_chateau, de_piranesi, de_storm, de_survivor, de_torn, de_vertigo, de_tuscan: none

de_dust: The following positions are illegal: [1] [2]

de_dust2: The following positions are illegal: [1] [2] [3]

It is legal to have several players on this box but they must not stand on each other: [1]

de_inferno: This roof is illegal.

de_nuke: Walking on this wall is illegal.

de_prodigy: Sitting on this lamp is legal, but not on the barbed wire.

de_train: Looking through this gap is illegal.

4.3.3. Selfkills/Teamkills

The intentional use of the console command ‘kill’ as well as intentional selfkills by other means are illegal.

Intentional teamkills during the match are illegal.

4.3.4. Planting the bomb

Planting the bomb in a in a non-reachable area is illegal.

The same goes for areas in which the bomb cannot be heard. (silent bomb)This does not go for areas that can only be reached with the help of a teammate.

4.3.5. Bugs General

Before the match:

Before the match starts the teams have to check whether the map has been loaded properly. In case of bugs (e.g. missing boxes, ladders etc.) the map has to be loaded again. By failing to check the map for bugs the teams agree to play on the map under the current conditions. Protests filed due to map bugs after the match will therefore be rejected.

During the match:

• Walking through walls, floors or roofs and 'skywalking' is illegal.

• Climbing rule: Climbing with the help of a team mate is legal. However positions where textures, walls or floors can be removed by certain movements are illegal (e.g. jumping). (e.g. the barbwire on de_prodigy, the upper roof on de_nuke etc. for further information please check the rule on map bugs)

• Using flashbugs is illegal.

• Please note that in addition to rule 3.3 Maps, the team who owns the server cannot file a protest if the teams failed to check whether drax's anti flashbug map pack has been installed or not.

• Throwing grenades below walls is illegal.

• 'Map swimming' or 'floating' is illegal.

• 'Pixelwalking' is illegal (to walk or stand on invisible edges)

• The intentional looking through gaps below boxes (e.g. with the AWP) is illegal.

• Defusing silently or with another sound is illegal.

4.3.6. Bypassing barrages and penalty points

Bypassing barrages and penalty points due to the creation of new teams is strictly forbidden. Existing penalty points / barrages will be transferred, barrages which result out of it may remain. Further sanctions for the teams and players in case of recurrence are reserved.

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