Counter-Strike: Source Cups 1on1 Handgun Cup #3

[ 7. Penalty points index ]

1.  Rules
1.6.  ESL Timezone
1.7.  Suggestions
2.  Cheating
2.1.  General  Legal scripts*  Legal Programmes*  Illegal scripts*  Custom files*  Illegal programmes*
3.1.2.  Playerphoto
3.2.  Teams
3.2.1.  Team players
3.2.4.  Team fusion
3.2.6.  2on2 teams
4.2.  Ladders
4.2.2.  Entries
4.2.3.  Exits
4.3.  Premierships
4.3.2.  Entries
4.3.3.  Exits
4.3.4.  Team accounts
4.4.1.  Entries
4.4.2.  Exits
5.  Matches  HLTV*  HLTV/ Source.TV*
5.1.3.  SteamID/HL2*
5.1.6.  LAN matches*
5.2.  Server
5.2.2.  Server settings
5.2.3.  Ping  Server Tickrate*  Choice of Side*  Game Mode*  Maps*
5.4.  Results
5.6.1.  Illegal actions*  Bugs*  Map specific Bugs*  Spraylogos*
5.6.3.  Game offenses
5.6.4.  Server problems
5.6.5.  Player drops  Number of players*  Change of players*
5.9.1.  Handgun Ladder*
5.9.2.  Aimmap Ladder*
6.1.  Screenshots  Editing Demos*
7.1.  In General
7.2.1.  Insults
7.2.2.  Spamming
7.3.2.  Game Abort
7.4.  Deceptions
7.4.1.  Fake match
7.4.2.  Faking results
7.4.5.  Country Faking*
7.5.2.  Barred players
7.5.4.  Ringers/Fakers
7.8.  Cheating  Custom files*
7.8.2.  Cheating  Illegal scripts*
7.11.2.  Selfkills*
7.11.3.  Planting bomb*
7.11.4.  Map bugs*
10.1.5.  Risultato
10.1.6.  Game Account

* This rule is game or leaguespecific. All other rules apply to all other leagues, too.

1.  Rules
1.1.  General Points
The rules, which are listed below, are to be followed at all times by ESL players. Anyone who registers on the ESL website accepts that they understand and will follow the rules.

As many changes happen within the ESL, the following rules are not finalised. Parts, or even all, may be changed, updated or altered at anytime, depending on the circumstances. For this reason, all players should regularly check the rules page for updates. Changes will be announced in the news by the administrators.
1.2.  Team and Player Conduct
All players are asked to behave in a humane way towards other competitors, and to any member of the administration team; treat others as you would like to be treated! If a player is found guilty of misconduct by an administrator, he/ she may receive penalty points. Also, teams risk league kicks, bans and expulsions from ESL competitions.
1.3.  Game Versions
Every league participant must own a legal copy of every game they play. If it is proven that a player is using a pirate or illegal copy, he/she will be immediately removed from the league and banned from the website. Unless otherwise stated in each ladder, the latest version of each game (update patch) should be used for matches.
1.4.  Game Coverage
The ESL reserves exclusive right to the coverage of Electronic Sports League matches. This includes all forms of transmission, including IRC Bots, Shoutcast-streams, HLTV and ESL-TV Broadcasts. The Electronic Sports League can assign the coverage rights of a match or of several matches to a third party or to the actual players themselves. In this case, terms and conditions would have to be arranged with the ESL management before the match.

In general, the ESL will contact any player or team if they wish to broadcast one of their matches. If no contact is made, individual players are allowed to arrange their own broadcasts. Should the game take place on a server that ESL administrators have no direct access to, it must be made sure that enough slots are available for the according clients.
1.5.  Amendment of Terms and Conditions or Rules
The ESL reserves the right to change any rule at any time according to the Terms and Conditions. Rule changes can take place during a seasonal event in which case it effective from the date it is introduced. As a general rule, any changes are posted on the main page in the news. If it is necessary, the players will be also informed by email.
1.6.  ESL Timezone
By default all times given are in Central European Time (CET). In Autumn/Winter this is one hour ahead of UTC/GMT and in Spring/Summer this is two hours ahead of UTC/GMT.

Your current timezone is displayed in the top right hand corner of the page.
1.7.  Suggestions
Should a clan or a player have any suggestions for improvement to the rules or to any ladder, it is possible to inform the administrators via either writing a support ticket or speaking with an admin in IRC.
1.8.  Internal Texts
All texts written in either protest or support tickets, or written by the administrators to members of a certain league or tournament, cannot be published without the permission of the Electronic Sports League.
1.9.  International language
The language to be used at all times in the European section of the ESL is English. This is to allow all of our users from different countries to take part. This includes all comments, protest tickets, support tickets, match communication, and IRC conversations.

Failure to comply with this rule can lead to bans from posting on the website or penalty points being added to your account.
2.  Cheating
2.1.  General
All forms of cheating in ESL matches are forbidden and will be penalized by the Electronic Sports League.

Players found cheating outside of the ESL may be barraged on the ESL depending on the evidence available. Note, we do not accept publicly submitted demo or screenshot evidence in these cases.

Should it become known to the ESL administrators that any form of cheating was used to the advantage of a player or a team during an ESL match, the ESL reserves the right to punish them to the full extent of the rules available (see 7.8. Cheating). By breaking any rule a player risks being barred or completely excluded from a specific league or from all leagues. This also includes his or her team.
2.1.1.  Bypassing Wire Anti-Cheat
The use of programs (or "hacks") to circumvent, modify or in any way manipulate Wire Anti-Cheat is forbidden.

Any use of such programs will be penalized within the rule 7.8. Cheating. Even testing of such programs in a match not happening within the ESL will be prosecuted.
2.2.  Game Modifications and Changes
In general, all programs which are not part of the original game, including custom-data and modifications, are not allowed in any ESL game. Exceptions will be outlined in each ladder’s own specific rules or below in 2.2.1. Legal programs and configuration modifications.
2.2.1.  Legal programs and configuration modifications
All external voice programs are allowed (e.g. Battlecom, Gamevoice, Teamspeak, Ventrilo etc.). Script changes and changes to the game’s configuration are allowed, unless they are partly or completely forbidden by the game-specific rules.  Legal scripts
All scripts, except those listed at Illegal scripts, are legal.  Legal Programmes
2.2.2.  Illegal programs and configuration modifications
Programs that provide an advantage during game play (e.g. drivers that allow the removing of walls such as ASUS or Wallhack) are forbidden. Any programs that change the game itself are forbidden.  Illegal scripts
The following scripts are illegal:
Turn scripts [180° or similar]
Stop-Shotscripts [Use- or Awp-scripts]
Ratechangers (Lagscripts)
Anti-Flash scripts or Anti-Flash binds (see also rule
No-Recoil scripts/binds (see also rule

A penalty will also be given if the script/binding is executed via external Hard- or Software.  Custom files
Custom files are absolutely forbidden. Custom files are files that change or exchange the ingame graphics, *.gcf or sound files. ASCII codes that generate crosshairs or similar game contents faking/replacing it, changed HUDs, scoreboards or sounds are also regarded as custom files.  Illegal programmes
No programms, except those listed at Legal programmes, are allowed.
Server plugins of any kind are illegal.
- zBlock
- CrashBlock  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.
2.2.3.  New programs and/or modifications
New programs and/or modifications are forbidden, as long as they are not specifically listed as legal.
2.2.4.  Compulsory programs
Additional programs have been developed for some games. These mostly serve the purpose of ensuring fair play. These additional compulsory programs are listed in the game-specific rules.  Compulsory programmes*
VAC2 is compulsory
The latest zBlock version is compulsory Download

The latest Aequitas version is compulsory.
2.2.5.  Server modifications
Server modifications that are neither explicitly mentioned as legal nor as illegal in the set of rules are only allowed if they do not affect the normal gameplay.
3.  Teams and Players
3.1.  Player Registration
To play in a ladder, a method of contact (an IRC channel or an ICQ number) must be available and visible to all users in your playersheet. Each player in the ESL must only have one account! If a player can not access his account and then creates a new one, then he/she must write a support ticket explaining in detail the reason for not being able to access the account.

Also, the permanent residence must be chosen according to the country he/she is currently living in. Should the country differ from his/her nationality, the player can add an additional flag in the setting.
3.1.1.  Nicknames and URL Aliases
Turtle entertainment reserves the right to edit Nicknames and/or URL aliases, if the user
fails to comply with the following requirements.
Nicknames/aliases are forbidden if they:
* are protected by third-party rights as long as the user has no written authorisation
* resemble or if they are identical to a brand or trademark, no matter whether it has been
registered or not
* refer to personalities
* consist of names of Turtle Entertainment products
* resemble or if they are identical to the names of Turtle Entertainment employees
* are nothing but gibberish
Apart from that any nicknames/aliases that are purely commercial (e.g. product names),
defamatory, pejorative, offensive, vulgar, obscene, anti-Semitic, inciting hatred, or
offending against good manners are forbidden. Names of real persons must not be used
as nicknames as long as it is not the users own name proven by the trusted status.
Using alternative spelling, gibberish or wrong spelling in order to avoid the requirements
mentioned above is illegal. We reserve the right to extend, change, exchange or delete
these rules if necessary.
The requirements mentioned above also apply to team names.
3.1.2.  Playerphoto
The photo must clearly show the face of the player, for adding anything else (graphics, other people, other parts of body, etc.) please use the logo function. The photo must always be up-to-date, manipulation of your appearance is prohibited. For anything else please use the gallery. Pictures with weapons are not allowed!
3.2.  Teams
To play in any of the ESL’s leagues, a team must have the following details written in their teamsheet:
• a name
• a team shorthandle
• a contact method (IRC/ICQ)
• a team logo (180x180 pixels)

The name does not have to be unique, but the ESL reserves the right to refuse clans with the same or similar names as a well-known clan (e.g. If you named your team “Schroet Kommando" or “Schroet Commando” etc, that would not be allowed).

Names which are restricted by law will not be accepted and will be deleted and punished with penalty points if found. Also, names which go against all forms of etiquette and good manors will not be accepted.

If a team deletes its account because of a certain amount of active penalty points and registers a new account, the penalty points will be transferred to the new account if the team rejoins the same ladder. Furthermore 1 additional penalty will be added for the attempted deception.

As a method of contact, the player's ICQ or the team's IRC channel has to be entered in the teamsheet.

The logo must represent the team and have some reference to the team's name or to the team's shorthandle. Copyrighted logos, or logos which go against etiquette and good manors will not be accepted.
3.2.1.  Team players
Each player can only play in one team per ladder, cup or tournament. A list of examples can be found here:
In tournaments with premium duty or trusted obligation, only players with this status are allowed to play.

Generally players who are entitled to the position "Inactive" or "Honorary member" are not allowed to play, therefore they are greyed out in the team sheet.  SteamID HL2/CSS of the players
A sufficient number of players with a SteamID HL2/CSS must be listed in the clan’s sheet.
It is not enough to list the SteamIDs in the team description!

The teams need at least x members with an entered SteamID HL2/CSS:

CS:S 5on5 -> at least 6
CS:S 3on3 -> at least 3
CS:S 2on2 -> at least 2
CS:S 1on1 -> at least 1

The clan leader is responsible for correct entry of the player's SteamID HL2/CSS.

If separate players or the whole clan is playing from an internet café, this must be announced beforehand.

For further information please check 3.3 Internet Cafés
3.2.3.  Changing team names
A team can change its name at any time. This also applies when a team is restructured. The team’s points and score are transferred.

Changing a team’s name in order to fool other teams is forbidden. The team’s former name must be mentioned on the team-sheet. Extremely long names, or consistent changing of team names is prohibited and can be punished with penalty points.
3.2.4.  Team fusion
Should two teams fuse (merge), they are free to choose which of the two accounts they would prefer to keep on using. The other account(s) should then be deactivated. Scores and data can only be adopted by different leagues. If both teams played for the same league, the teams’ match data are erased.
3.2.5.  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.  Intensification in CS:S
Matches between members of the same clan within one and the same ladder are forbidden.
- Matches generated by the autochallenger (including EAS matches)

Note: Matches generated by the Instant Challenger are not allowed.
3.2.6.  2on2 teams
2on2 teams are only allowed to have exactly two members. A 2on2 team is a fixed two-player-team, which means changing players is forbidden, unless the 2on2 team leaves the league, rearranges itself, and re-joins again.
3.2.7.  Changing squads, sub-teams etc
A team-account is owned by the leader or, as the case may be, by the person who registered the account. However, should a squad have qualified for a premiership/cup/pro-series or a competition other than a regular ladder, the squad has qualified in the name of its team. This means that the team that qualified, even if the squad that played is no longer part of that team, will be eligible to play but not the squad which moved to a different team.

Example: The team “Big Clan” has a squad that has qualified for a premiership. However, the squad decides to change teams during the season and becomes part of “Another Big Clan”. In this case, the team “Big Clan” can appoint a new squad to take over from the old one, which continues playing for “Big Clan” during the premiership. “Another Big Clan” has no right to participate in the premiership.
3.3.  Internet cafes
Internet cafes or similar locations that want to offer their clients the possibility of participating in the ESL have to contact the admin responsible. They have to register all SteamIDs they wish to use and they also have to inform the admin of their IP-range. All players and clans that want to play from the Internet cafe have to be listed on the homepage. Additionally, the players must be registered with the responsible admin. The Internetcafe is responsible for the correctness of the data and they also have to check the players and to make sure that no other player participates in an ESL Match using the same nickname.
In case of problems the ESL reserves the right to exclude the internet cafes involved.

Currently the admin responsible is stinger ([email protected])
Registered Internet cafes.
3.3.  Internet Cafés
Should Internet cafes or similar locations want to offer their customers the possibility of participating in the ESL, the cafes must contact the responsible admin. They must register all the SteamIDs they wish to use and must inform the admin of their IP-range.

All players that want to play must be entered on the team sheet and the homepage. Additionally, the players must be registered with the responsible admin. He is responsible for the correctness of their data and he is obligated to check the players and make sure that no other player participates in an ESL Match using the same Nick.
Should problems occur, the ESL reserves the right to exclude the internet cafes involved.

Currently the responsible admin is Stinger ([email protected]).
4.  Ladders, Premierships and Cups
4.1.  General Points
The Electronic Sports League offers many different game systems. You can find out which one is used in your particular game by visiting the "Info & Details" page of your specific game.
4.2.  Ladders
4.2.1.  General Terms and Conditions
The ladders in the Electronic Sports League are based upon the ELO points system. The points calculation of any match is calculated from the position of a player/team in the ladder, their opponents position, and the result of the match. For full details, please read the FAQ.

Challenges within a ladder:
Any participant may challenge any other, no matter if a team is ranked or still in the newcomer pool. The challenge may be refused by the other team/player if he/she wishes to do so. However, should the challenged team be within 20 places above the challenging team, the refusal will be punished with one penalty points. A challenging team from the newcomer pool would be ranked last within the ladder plus one, and therefore the 20 teams/players at the bottom would be punished for rejecting a challenge. Players or teams that have more than 5 outstanding challenges, 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 by individual players/teams.

Only one match is allowed between two participants within 7 days. After a team/player has been challenged, further challenges between the two teams/players are blocked for 7 days. After this, the team/player can be challenges once again.  Matches Between Players in the Top 10
The so-called "challenge spam protection" does not apply within ladders with more than 20 participants and 5 open matches if both teams / players are positioned within the ladder's Top 10. Usually, matches between two players in the Top 10 are obligatory.
4.2.2.  Entries
Players or teams may enter or leave a ladder at any time during the season.
4.2.3.  Exits
On leaving a ladder, the team’s/player’s score is automatically put on hold. After leaving a league, a team is normally not able to re-enter the same ladder for 5 days. If a team/player rejoins the same ladder, their score will be automatically reactivated.
4.3.  Premierships
4.3.1.  General terms and conditions
A premiership-league participant either qualifies by having performed very well within a ladder or by being nominated by the ESL-Admins to take part in the premiership.
4.3.2.  Entries
The teams enter the premiership at the beginning of the premiership season. It is not possible to enter the premiership during a running season.
4.3.3.  Exits
Teams can exit a premiership at any time. All the team’s matches are then deleted.
4.3.4.  Team accounts
The team account that qualifies and plays for the Premiership will hereafter be called “account” .

1.The team owns the account
2.The team alone decides which players are chosen for the account, no matter if the original players have left the team in the meantime.
3.The team may not change the account’s name until the end of the season.
4.The account is not transferable.

These rules are guidelines. Special cases are treated and rated seperately.
4.4.  Cups and other events
4.4.1.  Entries
A team can enter a cup according to the established cup-rules.
4.4.2.  Exits
A team can exit a cup according to the established cup-rules.
4.5.  ESL Pro Series
The ESL Pro Series is a “Premiership” and is carried out according to the rules.
4.6.  ESL Amateur Series
5.  Matches
5.1.  Game Preparations
In addition to challenging other teams via the ESL Page, it is also always a good idea to contact the challenged team per e-mail, irc, icq or other means a few days before the match.
5.1.1.  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.  HLTV
If HLTV broadcasts a game, the delay has to be 90 seconds or more.  HLTV/ Source.TV
It is legal to broadcast a match via HLTV/Source 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.
5.1.2.  Match Arrangements
Arrangements must be done before a match takes place.
See 8. Arrangements for further information.
5.1.3.  SteamID/HL2
A 'rcon status screenshot' has to be made before the match starts ('rcon status' in your console). This screenshot has to show all players with their SteamID and their IP address. Screenshots made of other programs such as HLSW etc. are not allowed. If a player reconnects during the match or you change the server an additional rcon status screenshot has to be made. The screenshot has to be made by the team that owns the server by using the 'rcon status' command (enter your password first) followed by 'jpeg'. The rcon status screenshot is mandatory and has to be uploaded immediately after the match.
After a match, the teams should compare the SteamID HL2/CSS with the ones given in the team-sheets.

Only the team that owns the server can make screenshots as mentioned above. If the screenshot is missing penalty points will therefore only be given to this team. If a match is played on two different servers, both teams will get penalty points.

An admin will decide whether a match will be deleted or not if the rcon status screenshot is missing.
5.1.4.  Warmup und Mapcheck
Before a match starts, both teams must state that they are ready to start the match. Should a player or a team have temporarily problems the opponent must be informed and the start must be repeated. Before the match starts the map must be checked for load errors.
5.1.5.  Nicknames compulsory
Each player has to use a nickname that is at least very similar to the nickname he/she entered in his ESL player sheet. You are not allowed to change your nickname ingame. In team matches the players are allowed to use a clantag which has to be the same for all players of this team. However you cannot file a protest or write a support ticket if your opponent breaks this rule.

If an admin cannot do his job properly because of wrong nicknames the players concerned will get penalty points.
5.1.6.  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.
5.2.  Server
5.2.1.  Choice of server
In case a game-server is needed for the game, the players must provide a server for the game themselves and come to an agreement on which server 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.
5.2.2.  Server settings
The server settings mentioned in the various game rules (e.g. config. values) 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.
5.2.3.  Ping
The internet is changing continuously and the connection to a server is not always perfect. The teams / players have to agree on a server that offers both sides an equal ping. Nevertheless every player should know, that he sometimes has to play with a bigger ping difference. In this case we have to appeal to the fairness of the teams/players, the right to change server or fakelag does not exist.
5.3.  Client settings
The client settings (e.g. config. values) that are listed in the game-specific rules are to be abided by.
5.3.1.  Player Settings CS:S
The following config values have to 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")

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

- cl_pitchspeed 225
- cl_yawspeed 210
- Only net_graph 0 and 3 are allowed

For these settings it is allowed to file a protest.

The usage of "vprof" and any related functions is forbidden. Also any "snd_commands" as bindings are forbidden.  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.  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.
5.3.2.  Content of the Configfolder
In the Configfolder you are only allowed to have Configfiles. Pictures, Demos, Screenshots and zipped Files are forbidden. If an Admin is hindered in his work because of too many unclear/chaotic Configfiles, penaly points ( 1-3 ) will be distrtibuted. Protest and Support tickets opened because of this rule are illegal and will be ignored.  Server Settings - CS:S
Using the latest server configs is mandatory. The .zip file contains configs for all ladders plus a readme file.

The server settings can slightly be changed. For further information on this issue please check rule 8.1. Notes to arrangements Counter Strike: Source .  Game Mode
In the CS:S Amateur Series MR15 has to be played. All rounds count.  Maps
The folowing maps are being played in Counter-Strike: Source:

1on1 Ladder Handgun / Ladder:
de_aztec, de_chateau, de_dust, de_dust2, de_nuke, de_prodigy, de_tides

1on1 Aim Map:
aim_1deag, aim_ancients, aim_aztecs, aim_dust, aim_glockon, aim_icemap, aim_map2, aim_furiouz (DOWNLOAD)

2on2 Handgun / Ladder:
de_aztec, de_chateau, de_dust, de_dust2, de_nuke, de_prodigy, de_tides

2on2 Amateur Series:
de_aztec, de_cbble, de_contra, de_dust, de_dust2, de_inferno, de_nuke, de_prodigy, de_train, de_tuscan*

3on3 Ladder:
de_aztec, de_dust, de_dust2, de_inferno, de_nuke, de_prodigy, de_train, de_tuscan*

5on5 Ladder:
de_cbble, de_contra*, de_dust2, de_inferno, de_nuke, de_strike_rc4*, de_train, de_tuscan*

*click on the map to download it
5.4.  Results
Both players / teams are responsible for entering the correct results. Both players / teams may enter a detailed report or statements on the game. The admins are also free to enter a report , either written by themselves or by third parties.

Should the opposing player / team be late to the game, follow rule 5.6.1.

In case of disagreements concerning the score, both players / teams should keep screenshots of the game that can be sent to the admins when requested.
5.5.  Illegal actions
Should a team fail to turn up in time for a game, it receives penalty points which are due after 20 minutes, counting from the previously arranged time at which the game was to commence. Exiting a server during a game without a good reason is forbidden.
5.6.  Trouble shooting / protest procedures
As a basic rule, every game is played through to the end. Should problems occur, these must be announced clearly by one of the players by calling “Protest”. As soon as the match is over, the protest form must be filled in on the website. The admins will then check the case with the help of the form and impose a penalty if necessary.

A protest must be handed in within 72 hours after the beginning of a match. A protest must be made using the protest form. It is not possible to use the support form. The opposing team then has 72 hours in which it may comment on the accusations made against it. An additional request by the admin is not necessary, as the notification occurs automatically.

If no response is received within the 72 hours period allowed, the team forfeits it’s right and the admin alone must decide according to the available data and facts.

Protest Rules

The codes of conduct must also be kept to in case of a protest. Verbal misconduct or abuse in any form can be punished with penalty points.
5.6.1.  Failure to appear to a match
Should a player / team not appear to a match on time, and the other player / team waited for at least 20 minutes, an entry is made in the result sheet.

For ESL Instant Challenger matches the waiting time is 10 minutes.

For EAS match, generated through ESL Auto-Challenger, a player / team is allowed to ask for default win via protest, if the opposing player / team did not show up.

The incident has to be documented with screenshots. You need to hand them to the responsible admin in case of a protest. It is forbidden to enter a result by itself.
5.6.1.  Illegal actions
1. 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.
2. Any bug-using is forbidden  Bugs
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.

Before the match:
01. Bugs of 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. If it will be not checked or ignored there is no claim for a protest.

During a match:
01. To boost through walls, ceilings or the ground and skywalking is forbidden.

02. To place a bomb in a way that it can't be reached anymore is forbidden. Places that could be reached with help of a teammate are excluded!

03. Following thumb-of-rule exists for climbing: climbing with help of the teammates is allowed in general. Not allowed are positions where textures disappear in walls or grounds if a special movement (e.g. a jump) will be done. For example the barbed wire fence at prodigy, nuke upper hallroof, please see Mapspecific Bugs.

04. To throw grenades amongst walls is not allowed. Above walls and roofs is allowed.

05. "Mapswimming" or "floating" is forbidden.

06. Moving the bomb - You are allowed to move the bomb. Please note that you must not move it to a place where your opponent can't pick it up. Failure to comply with this rule will result in the deduction of 3 rounds.  Map specific Bugs
The following map specific bugs are not allowed:

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]

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

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

Looking over this wall is not allowed: [1]  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
5.6.2.  Not enough players in a team
Should a team have too few players at a match for any reason, they are nevertheless allowed to compete against the complete opposing team, providing they have the minimum amount of players necessary. Unless stated differently in the game’s specific rules, the minimum amount of players a team is allowed to compete with is the designated amount minus one. The opposing team may freely decide to take players off their team in order to make it a fairer match. The match may also be postponed, if both the teams are agreed.
5.6.3.  Game offenses
Should a team ascertain a game offence, the best procedure is to write a support-mail via the ESL page. The match-ID and an exact description of the occurrences must be given in this mail. The accusations must be provable and the page on which the proof can be viewed by the admins must also be given.

The support-function should only be utilized when the problem that occurs is not during a match. Problems that apply to a match directly, must be dealt with using the protest-function.
5.6.4.  Server problems
Should problems with a server occur, a different server must be found and used. Should no other server be found in a measurable amount of time and should the original game server not be functional for an indefinite time, the game can be resumed at a later time and date.
5.6.5.  Player drops
Should a player drop during a game (e.g. disconnected due to technical problems), then the game is either paused or the map is restarted, if the still complete team wishes to do so. In the event of a drop, a registered substitute may enter the game in the dropped player’s place.
5.7.  Fixed dates / appointments
Rules concerning the dates and times of a game, should any exist, are to be found in the specific game rules.  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.  Playerdrops in CS: Source 1on1, 2on2 and 3on3
Should a player drop during a game (e.g. disconnected due to technical problems), then the game is paused. 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 5.7.6. Game intermissions. To file a protest is obligated in this case.

The procedure as described under 5.7.5. Player drops must not be followed in this case.  Playerdrops in CS: Source 5on5
Should a player drop during a game (e.g. disconnected due to technical problems), then the game is paused. 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 5on5 leagues pausable "0" is obligated, the team that owns the server needs to have 2 players who are able to set pausable 1 and pause the game at the beginning of the next round. The waiting time for one dropped player is 5 minutes. Should more players drop the waiting time is 10 minutes. If after the waiting time, there are not enough players on the server the match must be stopped and if necessary continued according to 5.7.6. Game intermissions. To file a protest is obligated in this case.

The procedure as described under 5.7.5. Player drops must not be followed in this case.  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. 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.
5.7.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'.
5.7.7.  Right to write a support ticket/file a protest - CS:S
Only teams/players involved in a match are allowed to write a support ticket or to file a protest.
5.8.  Abortion of a map after 16 victorious rounds - CS:S
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.
5.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.
5.9.  Ladder specific rules - CS:S
Below all rules applying to a specific ladder are listed.
5.9.1.  Handgun Ladder
The only weapons to be used are pistols, grenades and the knife. Primary weapons are not allowed (see rule 7.12.1).
5.9.2.  Aimmap Ladder
Allowed are all weapons, except for the AWP, that can be found on the map including Grenades. Using purchased weapons is not allowed (see rule 7.12.1).
6.  Data and records
6.1.  Screenshots
A screenshot of the on-screen results must be made of every game that is played. The screenshots must be uploaded onto the page with the match details as soon as possible after the game has ended. One screenshot showing each result (e.g. per half or map) is needed and can be uploaded by either the winners or the losers.

Non-existent screenshots lead to the assumption of a so-called “fake match”, a match that never took place. The screenshots must be uploaded within 24 hours after the game ends. They are to be kept for at least 14 days and must be presented to a player, or an admin at request.
6.1.1.  RCON Status - Counter Strike: Source
As described under 5.1.3. SteamIDs a 'rcon status screenshot' has to be made before the match starts ('rcon status' in your console). This screenshot has to show all players with their SteamID and their IP address. Screenshots made of other programs such as HLSW etc. are not allowed. If a player reconnects during the match or you change the server an additional rcon status screenshot has to be made. The screenshot has to be made by the team that owns the server by using the 'rcon status' command (enter your password first) followed by 'jpeg'. The rcon status screenshot is mandatory and has to be uploaded immediately after the match.
6.1.2.  tv_status - Counter Strike: Source
The server owning team is responsible for uploading a screenshot (rcon status/status) showing the mandatory delay of 90 seconds.
6.1.3.  Screenshots - Counter Strike: Source
CS:Source screenshots have to be made using the .jpeg format ('jpeg' in your console) or the .tga format. However only .jpeg files can be uploaded as match media.
6.1.4.  Editing Screenshots
It is strictly forbidden to edit screenshots. You are only allowed to compress them to an uploadable file format.
6.2.  Demos and replays
If your game supports a demo- or replay-function, it is obligatory for all players to use it. The demos are to be kept for at least 14 days and must be presented to the admin at request. If it should come to a protest, the demos must be kept until 14 days after conclusion of the protest.

If a player or team suspects that another player or team is violating a regulation during a game, the demo can be demanded of the opposing team straight away. The admins are only to be called in, when suspicions continue to exist even after the demos have been viewed. In this case, the clan or player may proceed and send the admin the game demos. The admin will then take the appropriate action.

It is recommended to voluntarily make all demos available to the public in order to keep the ladders transparent and interesting. For specific rules, please read the respective game rules.
6.2.1.  Demos and replays
Each player must record a demo.
HLTV demos are not valid.  Demanding demos - Counter Strike: Source
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 separate demo per map half has to be recorded. If the match is paused a new demo has to be recorded when the match is continued. Protest due players who have recorded one single demo instead of separate ones are illegal if the demo can be viewed.

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

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

In all MR9 ladders: You have to upload both demosites of the played map.
Because of that you needn't include the demosites (t or ct). If one half is missing it will be punished as missing demo.

If it turns out that your demo request was not made according to the rules or if you have requested too many demos, you can correct it within the 30 minutes by posting the entire request as match report.

This is possible as long as the opponent team didn't fulfill the previous request. If a team corrected the demo request, the upload time limit will be extended by 30 minutes from the point of correction.

Each team is obligated to check the match comments within 30 minutes after the match and if necessary load up the demanded demos within 24 hours.

The team or player that requested the demos can file a protest within 72 hours after the match. This protest has to start right with a demo report/timetable. In case of missing demos an admin will extend the period of time to make the timetable.

Should this not be done the match can be deleted and penalized by filling out a protest ticket. The match can only be deleted due to missing demos within 72 hours after the match.  Uploading demos – Counter Strike: Source
CS: S 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-FTP. You are no longer allowed to upload your match media to your personal web space etc.  Editing Demos
It is strictly forbidden to edit demos.
6.3.2.  Aequitas Files Counter-Strike: Source
Each player has to use the latest Aequitas version during the entire match. Uploading the Aequitas files to the ESL FTP within 24 hours after the match is mandatory. You do not have to demand them via the 'Request match media (demos/replays)' function on the match details page!

Should this be not done or if the file has been manipulated, the match can be deleted and penalized by filing a protest.

The players and teams will get 3 penalty points per missing or incomplete Aequitas file. The files are to be kept for at least 14 days. If a player intentionally manipulate his Aequitas file, he and his team will get six penalty points. Players who repeatedly manipulate their Aequitas files will be barred from all ladders. The usage of third-party programs to bypass Aequitas will be punished with 12 penalty points (Cheating).
7.  Penalties after offences
7.1.  In General
If a player or team disregards or violates one or more of the legal rules of the league, this can have various consequences depending on the severity of the offence. The ESL possesses an official catalogue of penalty points according to which points are given for each offence.

If a punishment affects a player in a team match, the player and the team receive the same penalty points. Up to 6 penalty points may be given per team and player within a single match.

The responsible admin decides whether an offence has affected the game to such an extent that it can not be assessed and must be deleted. Offences committed by the losing team seldom lead to match deletion.

In addition to penalty points, players and teams may be barred (also known as frozen, locked and barraged) if they have accumulated a certain amount of penalty points:

- After obtaining 4 penalty points: 1 week barrage
- After obtaining 8 penalty points: 2 weeks barrage
- After obtaining 10 penalty points: 1 month barrage

Barred players and teams must finish playing their open matches. They cannot challenge nor be challenged. Barred players may not take part in team matches with exception of 2on2 teams.

As a rule, the penalty points are deleted after a certain period of time. There are different clearance periods depending on the amount of points:

- 1-2 penalty points: 2 months
- 3-6 penalty points: 3 months
- 7 penalty points: 6 months
- 12 penalty points: 2 years (see cheating, rule 7.8.)

A player or team can receive a maximum of 11 penalty points. A player or team account that goes above 12 or more penalty points is kicked from all leagues and may not re-enter any of them until the sum of their penalty points drops below 12 again.

Bans are independent of the time of day and expire overnight. A player is not allowed to play as long as the red warning box is still displayed at the team or player sheet.

In particular cases the penalties imposed by the admins may vary from the catalogue of penalty points and can be transfered to other plattforms. The admins can impose penalties or delete matches for offences that are not listed here. The same applies for Streak- and Award-Deletions or making pointless Support/Protest tickets.

Penalties (penalty points/barrages/bans) given on ESL subplatforms (e.g. ESL Europe, ESL America) are valid on all ESL subplatforms.
7.2.  Breach of netiquette
Just as in other interpersonal areas in life it is also inevitable to preserve a certain degree of politeness within the ESL. Offences against this rule are penalized according to their severity and frequency. In particular cases, the penalties imposed by the admins may vary from the degree of penalization mentioned below.
7.2.1.  Insults
All insults that occur in connection with the ESL will be punished. This mainly includes insults during a match but also insults within the ESL website (forums, match comments, player comments, support- and protest pages, etc.). Insults via IRC, ICQ, e-mail or other media may be penalized, providing a connection to the ESL is given and provable.

Extreme insults such as radical statements or threats to do someone bodily harm can lead to strong punishments including exclusion and account deletion.

Written warning for the first offence
1 Penalty point + 1 week barrage for the second offence, or first serious offence
2 Penalty points + 2 weeks barrage for the third offence, or second serious offence
3 Penalty points + 3 weeks barrage for subsequent offences

The deciding factor therefore is the amount of active penalties for insults, the extremeness of the insult(s) will also be taken into account.

Insults can only be reported by a support ticket, matches may not be protested to report insults.
7.2.2.  Spamming
The excessive posting of futile, annoying or offensive contributions within the ESL is considered as spamming.
Spamming on the website (forums, match comments, player comments, support- and protest pages, etc) is penalized as follows:

1 penalty point + 1 week comment ban for the first spamming incident.
2 penalty points + 2 week comment ban for the second spamming incident.
3 penalty points + 3 week comment ban for the third and any further spamming incidents.

The decisive factor therefore is the amount of active penalties for spamming.
7.3.  Unsportsmanlike behaviour
In order to secure a well-regulated and pleasant course of game, it is inevitable that all players act in a sportsmanlike and fair way. A breach of this rule will be penalized with 3 to 6 penalty points; the most important and most common offences are listed below. An admin may, however, impose a penalty for not explicitly listed offences that are unsporting (e.g. unnecessary harassment) on the basis of this rule.
7.3.1.  Failure to appear
3 Penalty Points. If an opponent fails to appear to a match it is not necessary to file a protest. Simply enter that your opponent did not show up in the result sheet. When choosing this option, the remaining result panels should be left blank.

2 Penalty Points, otherwise the same procedure as above.

If your opponent does not appear for an AutoChallenger match in an ESL Amateur Series, you may request a default win by opening a match protest. You may not enter a default win for yourself, this is considered a fake result and will be punished!
7.3.2.  Game Abort
4 penalty points. If your opponent should deliberately leave during a match, you must make a protest. You must not enter a result yourself. This may be penalized as entering a fake result (rule 7.4.2.). Should the game have advanced to a point at which an evaluation of the result is possible, a win may be granted to the remaining team. The decision whether a match can be evaluated or not is in each case decided by the responsible admin.  Game Abort - CounterStrike Source
Team match: 4 penalty points for the team, 1on1 match: 4 penalty points for the player and a win will be granted to the remaining player/team. 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 (rule 7.4.2.).
7.3.3.  Spamming during a game
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.
7.3.4.  Player kicks during a match
4 penalty points. It is forbidden to kick opposing players from the server during a match.
7.3.5.  Modified/wrong server settings
Both parties must check the server settings. Wrong server settings must be corrected before a match. Should the wrong settings be noticed after the game has already begun, they must immediately be corrected. If this is not possible because e.g. the server provider is not willing to make changes, the match may be interrupted in order to file a protest. If the settings concerned are relevant for the course of the game, the match must be restarted as soon as one of the parties wishes it to be.
Should wrong server settings be noticed at any later point in time then both teams are responsible. If possible, the wrong settings must be corrected. The match is, however, only repeated if both teams wish it to be. A completed game that had wrong server settings all along may only be repeated if both teams agree to do so.

Non-relevant server settings:
2 penalty points. Even deviations from the stipulated server settings that have no or near to no influence on the course of the game are penalized.

Game deciding server settings:
4 penalty points if server settings that have a large influence on the course of the game are wrong or have been modified.
7.3.6.  Breaking engagements
Agreements concerning rule 8 that are not complied with are penalized as violations against the according ESL rule.
7.4.  Deceptions
Attempts to deceive admins or other players with wrong or fake statements, information or data are penalized as follows:
7.4.1.  Fake match
6 penalty points if a match or matches were created for the sole reason of not actually playing but of entering a fake result in order to receive illegitimate points within the ladder.
7.4.2.  Faking results
4 penalty points for entering a fake game result, e.g. when the game was aborted by the opponent or when you do not wish to play the game. If problems should arise that you can not solve amongst yourselves, a protest must always be made.

Note: If you agree on not playing a match it is forbidden to enter 0:0 or similar as the game result. If no result is entered matches are deleted seven days after the date the game was scheduled at, excluding compulsory games (e.g. Auto challenger or Cup matches). It is also possible to delete matches yourself, providing both opponents agree to do so. The link for this option is to be found in the match setup of each match.
7.4.3.  Fake match media
Match media includes all records e.g. demos, screenshots or logos that are generated within the scope of a match.
The faking of match media is forbidden and is penalized with 1-4 penalty points dependent on the severity of the case. For example: Uploading senseless screenshots, hoping the match will not be checked too closely, is not penalized as heavily as when screenshots are uploaded that are meant to cover up a fake match.

Intensification when cheating is suspected:
6 penalty points when fake match media is handed in and the player/team is strongly suspected of cheating.
7.4.4.  Other deceptions
Other attempts of deceiving an admin or another player are penalized with 1-4 penalty points depending on the severity of the case and according to the judgement of the responsible admin.
7.4.5.  Country Faking
Changing your country via your command center to avoid the player card league restriction in order to join an International ladder is illegal and will be penalized with 2 penalty points. The player concerned is barred for one week. If a player who has changed his country plays a team match, the team will get 3 penalty points and the match is deleted.
7.5.  Use of unauthorized players
7.5.1.  Inactive player barrage
3 penalty points if a player whose status on the team was changed from inactive in the last five days takes part in a match. These players are clearly marked as "inactive" or "barrage" on the ESL team page.

It is, however, possible for these players to take part in a game if the opposing team agrees beforehand (see rule 8.).

This rule is ignored in 2on2 ladders.
7.5.2.  Barred players
6 penalty points if a barred player participates in any gaming activity. It is not possible to make use of barred players by any form of agreement (rule 8.).
7.5.3.  Unregistered players
3 penalty points if a player who is not listed on the ESL team page, but is known to have been a member of the team for some time, participates in a game.
7.5.4.  Ringers/Fakers
6 penalty points if a player who is neither listed on the ESL team page nor a member of the team participates in a game. In special cases there may be barrages up to four weeks.
7.6.  Missing records/match media
Match media includes all records e.g. demos, screenshots or logs that are generated within the scope of a match.
7.6.1.  Compulsory Match media uploads
1 penalty point if the compulsory match media (e.g. screenshots of the results, replays) has not been uploaded within 24 hours after a match. If media of several matches is missing, up to 3 penalty points may be given as a collective penalty. If the match media is filed subsequently, the penalty points may be deleted or reduced on request.  Compulsory Match media uploads - Counter Strike: Source
Shouldn't there be the right amount of screenshots to prove the result of a match, the match can be deleted. Both teams will get one penalty point for Result-Screenshots and two penalty points for a missing Rcon-Screenshot (please see 7.6.1). The match will not be recovered even if the screenshots are uploaded after the penalisation.
7.6.2.  Requested records/match media
1-3 penalty points if no or insufficient media is handed in on request of an admin. The responsible admin decides which records or match media is necessary depending on the circumstances (e.g. demos, server logs, chat recordings, etc.).  Missing demos - Counter Strike: Source
Should a player not upload a demanded demo within 24h after the match the player and the team get 3 penalty points and the match will be deleted.
7.6.3.  Requested match media after strong suspicion of cheating
6 penalty points if no or insufficient media is handed in on request of an admin in order to rebut a strong suspicion of cheating.
7.6.4.  Subsequent uploading of demos/Aequitas files - Counter Strike: Source
Missing or incomplete demos/Aequitas files can be uploaded subsequently within 24 hours after the protest has been filed. An admin may however decide to extend this period of time. If the match media is uploaded, the penalty points will be reduced to one. The match will be rated.
7.7.  Missing/Wrong Gameaccounts
7.7.1.  Without strong suspicion of faking
3 penalty points if a player’s compulsory game account entry is missing or wrong after a match.
7.7.2.  With strong suspicion of faking
6 penalty points if the player’s compulsory game account entry is missing or wrong after a match and there is additionally a strong suspicion that a faker or ringer took part in the match.
7.8.  Cheating
7.8.1.  Programs / modifications / settings
These penalties are explained in the game specific rules.  Custom files
Custom files as described under rule will result in two penalty points.
7.8.2.  Cheating
12 penalty points for the player and 6 penalty points for the team. The use of severe cheats (e.g. aimbot, wallhack, multihack) is penalized with a two year ban from the ESL. On top of that all the statistics for the player from the last 12 months will be removed. For the team in question the statistics from the last 3 months will be removed. The removal of the statistics will solely consist of the ladders of the game where the player was caught cheating in.

Rehabilitation is only available to players caught cheating in ESL matches. After at least six weeks the cheater receives the one-off opportunity of handing in an essay on the topic of cheating in multiplayer games. The exact subject of the essay is set by the ESL. The complete essay must be handed in within three month after the subject is decided upon. It will then be reviewed for a week. If it complies with the requirements (form and length) and if its content is convincing, the cheater may receive the chance of rehabilitation. (Further details concerning rehabilitation). The penalty points for the cheating offence are, in case of rehabilitation, reduced to 7 for the player and 5 for the team. The statistics will however not be reinstated.  Cheats - Counter Strike: Source
Cheats of the first category are all kinds of multihacks, wallhacks and aimbots as well as coloured models, No-Recoil, No-Flash and any Sound changes.  Wrong models - Counter Strike: Source
Custom models are illegal.
The use of custom models will result in three penalty points for the team and between three and six for the player depending on the severity of the case.  Illegal scripts
Using illegal scripts (see also rule 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 as in Rule 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.  Wrong client settings
Two penalty points per changed value (the maximum is six). Wrong client settings will also be punished if they are found with the help of Aequitas even if the config files concerned have not been loaded during the match. If a player uses more than one wrong value in a 1on1 match, the match will be deleted.  Wrong client settings - team leagues
Should more than one player have wrong client settings the team will get four penalty points and the match will be deleted.
7.9.  Multi accounts
1-4 Penalty points depending on the severity of the offence. Additionally, all penalty points are transferred to one account and all other accounts are deleted.

Furthermore it is not permitted to delete an old account in order to open a new one. If you should forget your login password it is always possible to contact the admins via the support form or IRC in order to retrieve your account. It is helpful to enter non-public information in your account, as admins can then confirm your identity more easily should you forget your login data.
7.10.  Declining compulsory challenges
Intense compulsory challenges only become active in ladders with more than 20 participants.
7.10.1.  Normal compulsory challenges
1 penalty points for the challenged if he is positioned within 20 places above the challenger in the same ladder.
7.10.2.  Intense compulsory challenges
2 penalty points for the challenged if both participants are positioned within the top 10 of the same ladder.
7.11.  Other unauthorized offences
7.11.1.  Deliberate exploitation of bugs on the website
These penalties lie within the discretion of the responsible admin and are penalized according to their severity. This type of offence is e.g. the postponement/abortion of matches that were already confirmed.
7.11.2.  Selfkills
Selfkills are punished with 2 penalty point for the team every time the function is used (maximum: 6 penalty points).
7.11.3.  Planting bomb
2 penalty points when the bomb is planted in a non-reachable area (maximum: 6) and the deduction of 3 rounds for each offence. The same goes for areas in which the bomb cannot be heard (see rule 5.6.1.) This does not! go for areas that can only be reached with the help of a teammate.
7.11.4.  Map bugs
Abusing map bugs as listed under is penalized with two penalty points for the player and the team. The maximum amount of penalty points per match is six.
7.12.  Ladder specific regulations
7.12.1.  Weapon choice Handgun/Aimmap
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.
8.  Arrangements
Certain arrangements between the teams/players are allowed. These arrangements may slightly differ from the ESL rules. Arrangements that differ greatly from the set of rules are however not allowed. Please note that the ESL rules were made to guarantee the same advantages/disadvantages for all teams. 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 by agreements are to be found in the game specific (*) rules. Should this not be the case then you are not allowed to agree on changes.

All arrangements between teams in addition to the ESL rules have to be written down in the match comments. The other team has to confirm those arrangements in the comments. To avoid an abuse of the edit function, a third comment has to be written.

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

The following rules cannot be changed by arrangement:
- Entering results for matches that have not been played
- Game privileges of players which are barred because of penalty points, or are barred in the league due to a ban
- Game privileges of players in leagues with premium requirement, which have are barred for inactivity
8.1.  Notes to arrangements Counter Strike: Source
The following settings can be changed if one party requests:

- sv_voiceenable 0 or 1
- change mp_fadetoblack 1 to 0

If both parties agree, you can:

- accept players of the opposing team who are barred due to 3.2.2. Changing teams
10.1.5.  Risultato
Concluso il match, ognuno dovrà inserire il risultato corretto (in caso di party, inserisce il risultato solo il leader del party), è obbligatorio inserire il risultato affinchè il match venga valutato. Se un giocatore inserisce un risultato non corretto, verrà penalizzato, è altrsì possibile reportare un player con comportamento scorretto e l'admin team deciderà se assegnare un ban temporaneo da versus.
10.1.6.  Game Account
IL GA è di fatto un'assicurazione sul con chi si sta giocando, E' dunque obblgatorio utilizzare in game lo stesso Game Account registrato sul profilo di ESL. Chi non lo avesse, non può partecipare ai match Versus. Il team avversario può far valere questa regola sino all'inizio del match.
All content appearing in this document is the property of Turtle Entertainment GmbH or is being used with
the owner's permission. Unauthorized distribution, duplication, alteration or other use of the material
contained in this document, including without limitation any trademark image, drawing, text, likeness or
photograph, may constitute a violation of the laws of copyright and trademark and may be prosecuted under
criminal and/or civil law.
No part of the content of this document may be reproduced in any form or by any means or stored in a
database or retrieval system, except for personal use, without the written permissions of Turtle Entertainment
All content in this document is accurate to the best of our knowledge. Turtle Entertainment GmbH assumes
no liability for any error or omission. We reserve the right to change content and files on our website at any
time without prior notice or notification.