1. Ladder Rules

1.1. Challenging

In a ladder all the participants can challenge every team. The challenge may be refused by the challenged if they choose to do so. In ladders with more than 20 participants compulsory challenges are activated. If a participant is within 20 places above the challenging participant 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 will 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

You have to wait for you opponent on the server for 20 minutes. Enable Anti-Cheat ESL Wire, join the server and if your opponent does not show within 20 minutes after the matchtime, take a db_status screenshot as a proof of noshow. After that upload that screenshot in matchmedia and enter the result as your opponent did not appear in time. Do not enter a default win for yourself. In Instant Challenger matches you have to wait 10 minutes for your opponent.

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 to much from ESL rules are 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 you or your team.

Rules that can be changed with agreements are explicitly stated. Rules that aren't explicitly stated can't be changed in any way. 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 in the comments. To avoid abuse of the edit function, a third comment must be written.

It would also be wise to keep screenshots and/or log files of your arrangements. If you can't proof that the arranged agreements haven't been for filled the protests or supports concerning the 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.

2.1. Screenshots

Both parties are responsible for uploading a screenshot of every played round in matchmedia. You also have to take a "rcon status" and "db_info" screenshot, but only the team/player who provided the server is responsible for taking them. All screenshots have to be uploaded to the match page within 24 hours after the match. If you failed to upload them in time you can also write a support ticket and the ESL admins may delete the penalty points given.

For taking a valid rcon status + db_info screenshot you have to write the following commands into console:

1. rcon_password XXX
2. clear (to hide your rcon_password)
3. db_info
4. rcon status
5. jpeg

The information given by these two commands (rcon status and db_info) have to be clearly visible in the screenshot.

2.2. Wire Anti-Cheat

ESL Wire Anti-Cheat is mandatory!

If a player can't start ESL Wire Anti-Cheat, he is not allowed to play. Error screenshots made before the match are no valid replacement and will be punished. For not starting ESL Wire Anti-Cheat you will also be penalized, excepting there is an error and you opened a support ticket within the next 24 hours and if there is no obvious problem on your turn. If a team plays a match in which at least 2 aren't running ESL Wire Anti-Cheat and a protest ticket has been opened the match will be deleted (Ladder) or the other team will get a default win (e.g. Spring Season).

Note that some error-fixes are explained on the FAQ and forums. In case your error is among these known fixes you can receive penalty points for this.

2.3. Linesman

Linesman is an integrated ESL Wire module that sends information like your game-configs, color-depth, SteamID and used starting parameters directly to the ESL. There is no need to manually upload any files after your match. Though there are some constraints regarding the size and number of used config files:

• The total size of all configs may not be larger than 200kb
• One file may not larger than 50kb
• The maximum amount of config files is 30

If the Linesman file is incomplete because of a violation of the above rules, a penalty will be given out and the match can be deleted. If your Linesman file is incomplete because of another reason, then you need to contact support to help fix your issues.

2.4. Demos

It is mandatory for all players to record point of view demos (in-eye-demos) for the full duration of all matches without exception. Players should record one demo per half of a map. SourceTV demos are no valid replacement. Incomplete or defective demos will be treated as missing demos.

If a protest is opened for a match, all match media files need to be kept for at least 14 days until after the protest is closed.

2.4.1. Requesting demos

Demo requests are only obligatory if they are done till 30 minutes after match end via "Request match media". In that request you have to write which demo you exactly want: map, side and Steam ID of the player. If your request is incorrect, you can edit it via match comments, but still under the same requirements as mentioned.

In each match you can request demos of maximum two players (from all played rounds). Every team is obligated to check back after 30 minutes if demos of their players has been requested. If so the players mentioned have to upload them within the next 48 hours.

3. Settings

3.1. Server settings

All matches have to be played on servers that operate on 66 tickrate with the server config (download here) provided by ESL. Once the match started, both teams have agreed to the settings. If a game is played with the wrong settings, an admin may force a rematch with the correct settings.

3.2. Programs

VAC3 and DBlocker are mandatory! During ESL matches all other programs and plugins are not allowed (e.g. SourceMod).

3.2.1. DBlocker

You have to download and install the latest version of DBlocker on your gameserver. Also the following DBlocker settings have to be used in your match:

• db_active 1
• db_silent 0
• db_anti_noflash 0
• db_anti_purebypass 1
• db_anti_speedhack 1
• db_anti_wallhack 0
• db_check_cvars 1
• db_check_viewangles 1
• db_enforce_esl_rules 1
• db_show_steamid_on_connect 1

Shall you not follow this rule in your matches, you will be penalized in accordance with the rule "6. Penalty points - Wrong server settings".

3.3. Client settings

The following settings have to be entered into your client config:

• cl_bob 0.002
• cl_bobcycle 0.8
• cl_bobup 0.5
• r_drawdetailprops 1
• net_graph 0 or 1
• rope_rendersolid 1
• snd_mixahead 0.1
• mat_filtertextures 1
• cl_detaildist 1200 or higher
• cl_detailfade 400 or higher
• r_shadowrendertotexture 0

If you change one of these settings or you don't pass default DBlocker's check, you will get kicked by DBlocker. You're not allowed to protest about client settings because DBlocker completely prevents the use of forbidden client settings.

Custom crosshairs are allowed, but changing the sniper crosshair is forbidden. Custom HUD's are allowed as long as forbidden symbols are not included. A direct X value under 8.x is forbidden. All other cvars can be changed as long as they provide no clearly unfair advantage.

*Note: When you manually force dxlevel (via config or game launch options) higher than Software DirectX Level (see in video options) it will lead that cvar r_shadowrendertotexture 0 written in your config won't work properly and you will get kicked by DBlocker because aformentioned cvar still will have value 1. In that case before joining the server you have to set quality of shadows in video options to 'Low' value or write in console r_shadowrendertotexture 0.

3.4. Standalone Programs

Changes to the game or texture using video card drivers, other tools, graphics configuration or programs of this type are forbidden. In principle each program may be used, which has no influence on the game (Teamspeak, Ventrilo, Administrationtools, etc.). All other programs are forbidden (e.g. cheats).

4. Match rules

4.1. Nicknames

Each player must be tagged up with his nickname that is listed in the ESL playersheet. Protest or support tickets for violating this rule are not allowed. If an admin is being hindered in his work by a player having a different nick, he could give penalty points.

4.2. Number of Players

• 6on6: 5on6 and 6on6 allowed
• 2on2: only 2on2 allowed

4.3. Choice of server

ESL does not supply servers for matches. Players and teams must provide their own server and come to an agreement with their opponent as to which one 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 (that has to be done before match start). 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.4. Player drops

• 1on1/2on2: If a player leaves/drops from the server the match must be paused by the other player/team. You must wait at least 5 minutes for the return of the player and then each half is played again. If the player should not come back a protest ticket must be opened.
• 6on6: There is no obligation to pause the game and idle. Should a player dropped due to technical problems, one player could join as a substitute per round (even if several players dropped). He must be registered at the ESL team account and allowed to play. More substitutes can connect while changing the map.

Generally: If a team is completely leaving the match must be paused and you have to wait for at least 10 minutes for their return. If the team should not come back a protest ticket must be opened.

4.5. Player changes

Players may be changed at any time during a game. If the change is during a match the game must not be paused and the opposing team doesn't have to “idle”.

If the change takes more than 3 minutes you have to start the round without the missing player. The missing player is allowed to join the server at any time, but he must be registered on the team page. In a case of changing players you have to take a new rcon status.

4.6. Inactive barrage

If a player is barraged due of an Inactive barrage and needs to play you have to ask your opponent. Only if they agree he is allowed to play. That includes swapping a player from Inactive or Honorary Member status to an active one.

4.7. Unauthorized acts

In principle all acts are forbidden which bring up an unfair advantage. These include all kinds of bug using and the acts mentioned in the following rules.

4.7.1. Leaving the server

The intentional leave from the server is considered as aborting the match. Should the leave happen due to issues of the server the match has to be replayed. If there is no agreement a protest ticket must be opened.

4.7.2. Delaying the match

You are not allowed to delay the match on purpose, also read 1.2 No show. The time between rounds should not be more than 3 minutes. We reserve further sanctions for teams and players by breaking this rule.

4.7.3. Spawn protection

The team leaders are responsible for ensuring that all members know and follow the spawn rules. Should a player break this rule he will be punished. Play fair and show that you are the better team without “dirty tricks”!

Forbidden

• grenades into spawn
• excessive spawn camping

Allowed

• Quickly passing of the spawn
• throwing grenades in front of the spawn ramp
• You are allowed to shoot players from the spawn ramp, but don’t camp in front of it just to kill them

4.7.4. Fast spawn

It is not allowed to change the player class or the team to accelerate the respawn, to get a better spawn position, speed reloading of the weapon, receiving back full health or to provide other benefits. If this rule is violated unintentionally penalties can be avoided by standing still and dropping your weapon for at least 5 seconds. We reserve the right to decrease the amount of full caps if it's affected to the result of the match and may penalty point will be given out.

4.7.5. Illegal scripts / binds

Any binds or aliases which change the original movement of the game, speed up progresses of the game or change any cvars in order to gain an advantage over the opponent are forbidden. Simple binds or aliases to change maps or scripts which don’t give an advantage while being in game are allowed.

The presence of illegal scripts in the configs is sufficient for punishment.

The examples of forbidden scripts:

• Turn scripts (180° or similar)
• mlook
• Stop-shots scripts
• Center view scripts
• No-Recoil scripts
• Burst fire scripts
• Sniper scope scripts
• Stop sound scripts
• Aliases that include +attack(2)
• +attack(2), +jump, +duck with mouse wheel
• Fast switch (hud_fastswitch is allowed)

*Note: You're not allowed to protest about net settings binds/scripts because DBlocker completely prevents advantages obtained by such scripts/binds.

Penalty (the more illegal scripts the longer a barrage will be):

• In general: for player 6 points + 1...3 months barrage; for team 6 points
• In hard cases: for player 10 points + 6 months barrage; for team 6 points (e.g. active use of norecoil)

4.7.6. Modified files

Any custom files (e.g. models/textures/sounds) are forbidden! The presence of such modified files in Linesman archive is sufficient for a punishment.

Exception

• custom HUD (as long as no forbidden symbols are included)

Breaking this rule will be penalized by at least 3 penalty points or more. Any modification of files in the "scripts" folder is forbidden!

4.7.7. Cheating

Any kind of cheating is forbidden, see global rules.

4.7.8. Bug using

In general bugs that give an unfair advantage are forbidden.

4.7.9. Insults

If you have been insulted in a match, you have to open a seperate support ticket. Opening a protest ticket due to insults is not valid.

4.7.10. Avoiding barrages and penalty points

Avoiding barrages and penalty points by creating other teams is not allowed. Existing penalty points/barrages will be transferred to the new account. We reserve further sanctions for teams and players.

4.8. Results in ladder matches

• 1on1 Ladder: A match will be valued by full caps (e.g. 1on1 Ladder) or kills (1on1 Sniper Ladder). In case of a draw in the normal Ladder you will go for tick points. The player with more tick points gets an additional full cap. If it’s still a draw, you will go for kills. The player with most kills gets an additional full cap and wins the match.
• 2on2 & 6on6 Ladder: A match will be valued by full caps. In case of a draw you have to sum up the tick points of all played rounds. The team with more tick points gets an additional full cap. If it’s still a draw, the match has to be valued as draw.

4.9. SourceTV

It is legal to broadcast a match via SourceTV as longs as one team 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 obligated to upload an rcon status screen that shows the necessary delay of at least 90 seconds.

4.9.1. SourceTV delay

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

5. Season League specific rules

5.1. Team barrages

If a team is barraged during the groupstage or Playoffs it is allowed to play its open matches. But if the team has 12 or more penalty points at the beginning of Playoffs it will be disqualified.

5.2. Default match dates

If both teams can’t agree on a match date they have to play on the last day of the stated match week. In case the one of the teams is still not able to play they have to make use of the Wildcard (see 5.3 Wildcard). If the opponent still doesn’t show up or isn’t responding you have to open a protest ticket, but do not enter a default win for your team.

5.3. Wildcard

Each team has one Wildcard during the whole tournament. This card has to be used 24 hours before the match should be played to move the match date to another one. The team that decides to use their wildcard has to suggest two new match dates on different days which are within the next 3 days. Wildcards that are being used within 24 hours of the agreed match start will be rejected.

5.4. Match result

The match result is based on the full captures ("Rounds Won" in the scoreboard). If this ends in a draw, the points of all played rounds scored by the teams (tick points) for holding flags are summed up. The team which has the most points gets one additional full cap. If both teams still have the same number of tick points you have to play an additional 2x5 minutes on last map you played. Draw isn't possible!

5.5. Player changes during season

In general player changes during a season are allowed excepting the following restrictions:

• Player changes from a higher to a lower division
• Player changes from folded teams
• Player changes from teams which didn't reach Playoffs
• Player changes in Playoffs

After changing the players are allowed to play the matches for their new team if there is no visible barrage.

5.5.1. Penalties by offending

• If a team restricts against these rules the opposing team will get a default win. Also the offending team and player will get penalty points according to the rule "Barraged players".
• Penalties have to be opened by the opponent in form of a protest ticket.

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