Quicklinks

1.1.  Behavior

1.1.1.  Insults

1.1.2.  Spamming

1.1.3.  Unwanted contents

1.1.4.  Unsportsmanlike behavior

1.1.5.  Fraud

1.1.6.  Abusing bugs on the website

1.1.7.  Exclusion from the ESL

1.2.  Privacy of letters

1.3.  Accounts

1.3.1.  Registration

1.3.2.  Multiaccounts

1.3.3.  Account data

1.3.4.  Games

1.3.5.  Nicknames, Teamnames und URL aliases

1.4.  Coverage rights

2.1.  Scale of penalties

3.1.  Cheating*

3.1.  General Points*

3.1.1.  General*

3.1.1.1.  Bypassing Aequitas*

3.1.2.  Game Modifications and Changes*

3.1.2.1.  Legal programs and configuration modifications*

3.1.2.2.  Illegal programs and configuration modifications*

3.1.2.3.  New programs and/or modifications*

3.1.2.4.  Compulsory programs*

3.1.2.5.  Server modifications*

3.2.  Ladders*

3.2.  Teams and Players*

3.2.1.  Teams*

3.2.1.  General Terms and Conditions*

3.2.1.1.  Team players*

3.2.1.1.  Matches Between Players in the Top 10*

3.2.1.2.  Changing teams*

3.2.1.3.  Changing team names*

3.2.1.4.  Team fusion*

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

3.2.1.6.  Changing squads, sub-teams etc*

3.2.2.  Internet cafes*

3.2.2.  Entries*

3.2.3.  Exits*

3.3.  Cups and Other Events*

3.3.  Ladders, Premierships and Cups*

3.3.1.  General Points*

3.3.1.  Entries*

3.3.2.  Ladders*

3.3.2.  Exits*

3.3.2.1.  General Terms and Conditions*

3.3.2.2.  Matches Between Players in the Top 10*

3.3.2.3.  Entries*

3.3.2.4.  Exits*

3.3.3.  Premierships*

3.3.3.1.  General terms and conditions*

3.3.3.2.  Entries*

3.3.3.3.  Exits*

3.3.3.4.  Team accounts*

3.3.4.  Cups and other events*

3.3.4.1.  Entries*

3.3.4.2.  Exits*

3.4.  Matches*

3.4.1.  Game Preparations*

3.4.1.1.  Match Broadcasting*

3.4.1.2.  Match Arrangements*

3.4.2.  Server*

3.4.2.1.  Choice of server*

3.4.2.2.  Server settings*

3.4.2.3.  Ping*

3.4.3.  Client Settings*

3.4.4.  Results*

3.4.5.  Illegal actions*

3.4.6.  Trouble shooting / protest procedures*

3.4.6.1.  Failure to appear to a match*

3.4.6.2.  Not enough players in a team*

3.4.6.3.  Game offenses*

3.4.6.4.  Server problems*

3.4.6.5.  Player drops*

3.4.7.  Fixed dates / appointments*

3.5.  Data and records*

3.5.1.  Screenshots*

3.5.2.  Demos and replays*

3.6.  Arrangements*

3.6.1.  Arrangements Day of Defeat: Source*

3.6.2.  Classlimits*

3.6.3.  IRC Channel*

3.6.4.  Ingame nick*

3.7.  Special rules for Day of Defeat:Source in the ESL*

3.7.1.  General rules*

3.7.1.1.  SteamIDs of the players*

3.7.1.2.  Statusscreenshot (rcon status)*

3.7.1.3.  Warmup und Mapcheck*

3.7.1.4.  Player changes*

3.7.1.5.  Prohibited actions*

3.7.1.6.  Illegal actions*

3.7.1.7.  Bugs*

3.7.1.8.  Playercounts*

3.7.1.9.  Playerdrops*

3.7.1.10.  Serversettings and serverconfigs*

3.7.1.11.  Mandatory programs*

3.7.1.12.  Aequitas*

3.7.1.13.  Legal programs on the server*

3.7.1.14.  Clientsettings*

3.7.1.15.  Legal scripts*

3.7.1.16.  Illegal scripts*

3.7.1.17.  Illegal programs*

3.7.1.18.  Demos and Screenshots*

3.7.1.19.  Demos and Screenshot demands*

3.7.1.20.  Cheats in Day of Defeat: Source*

3.7.1.21.  Match result*

3.7.1.22.  Source TV*

3.7.1.23.  Teampenalties*

3.7.1.23.  Teampenalties*

3.8.  Special rules for Premierships (aka Seasons)*

3.8.1.  Default matchdays*

3.8.2.  Choice of maps*

3.8.3.  Mappool*

4.1.  Game Preparations*

4.1.1.  Match Broadcasting*

4.1.2.  Match Arrangements*

4.2.  Server*

4.2.1.  Choice of Server*

4.2.2.  Server Settings*

4.2.3.  Ping*

4.3.  Client settings*

4.4.  Results*

4.5.  Illegal Actions*

4.6.  Troubleshooting / Protest Procedures*

4.6.1.  Failure To Appear To A Match*

4.6.2.  Not Enough Players In A Team*

4.6.3.  Game Offenses*

4.6.4.  Server Problems*

4.7.  Fixed Dates / Appointments*

5.1.  Screenshots*

5.2.  Demos and Replays*

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

1.1.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) will be penalized.

1.1.3.  Unwanted contents

It is forbidden to publicize offensive, pornographic or violence-glorifying content (images, links, texts) which violates applicable law. Furthermore you are not allowed to upload copyright protected images without the agreement of the holder of rights.

1.1.4.  Unsportsmanlike behavior

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

1.1.5.  Fraud

Every kind of economic fraud will be reported to the police (forgery and defalcation).

1.1.6.  Abusing bugs on the website

Any abuse of bugs on the ESL website is forbidden and can lead to legal steps.

1.1.7.  Exclusion from the ESL

In extreme cases a user can be excluded from the ESL.

All contents of tickets (protest and support) and admin e-mails are strictly confidential. The publication of such contents is not allowed without permission on the site of ESL.

User and team accounts are not transferable. It is especially forbidden to trade them on "eBay" or similar pages. The owner of a team account is the leader or the person who registered the account. If a user do not want to use his account anymore for some reason, he needs to open a support ticket especially if he wants to create a new account (which is forbidden).

1.3.1.  Registration

Every player is allowed to have exactly one user account on the ESL. You need to be at least 6 years old to register an ESL account.

1.3.2.  Multiaccounts

It is not allowed to possess multiple ESL accounts. Multiaccounting will be penalized according to the scope of penalties on the bottom of this page.

1.3.3.  Account data

The user obliges that all information, which have been entered during the registration and the usage of the ESL, are given to the best of one's knowledge and belief. False information can be penalized with penalties and barrages.

1.3.4.  Games

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.3.5.  Nicknames, Teamnames und 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.

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.

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.

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 9 penalty points: 2 weeks barrage

After obtaining 10 penalty points: 1 month barrage

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)

Insults result in the following penalties:

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 admins reserve the right to give additional penalties.

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.

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

3.1.1.1.  Bypassing Aequitas

The use of programs (or "hacks") to circumvent, modify or in any way manipulate Aequitas is forbidden.

Any use of such programs will be penalized. Even testing of such programs in a match not happening within the ESL will be prosecuted.

3.1.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 3.1.2.1 Legal programs and configuration modifications.

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

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

3.1.2.3.  New programs and/or modifications

New programs and/or modifications are forbidden, as long as they are not specifically listed as legal.

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

3.1.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.2.1.  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.  General Terms and Conditions

Points:
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 two 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.

3.2.1.1.  Team players

Each player can only play in one team per ladder, cup or tournament.

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 grayed out in the team sheet.

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

3.2.1.2.  Changing teams

Any player can change team whenever he pleases to do so. A player is barred from playing with his new team for 10 days after changing and may not take part in any of his new team’s games or tournaments during this period of time, as long as the team is older than 20 days. This also applies for newly registered players. If a player plays in a game while being banned, he will be considered as a ringer.

For exceptions, especially in premierships or cups, the rules, news and membermails should be read carefully, and in cases of doubt an admin should be contacted.

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

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

3.2.2.  Entries

Players or teams may enter or leave a ladder at any time during the season.

3.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 not able to re-enter the same ladder for 2 weeks. If a team/player rejoins the same ladder, their score will be automatically reactivated.

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

3.3.1.  Entries

A team can enter a cup according to the established cup-rules.

3.3.2.  Ladders

3.3.2.  Exits

A team can exit a cup according to the established cup-rules.

3.3.2.1.  General Terms and Conditions

Points:
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 two 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 14 days. After a team/player has been challenged, further challenges between the two teams/players are blocked for 14 days. After this, the team/player can be challenges once again.

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

3.3.2.3.  Entries

Players or teams may enter or leave a ladder at any time during the season.

3.3.2.4.  Exits

On leaving a ladder, the team’s/player’s score is automatically put on hold. After leaving a league, a team or player is not able to re-enter the same ladder until a 4 weeks clearance has passed. If a team/player rejoins the same ladder, their score will be automatically reactivated.

3.3.3.  Premierships

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

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

3.3.3.3.  Exits

Teams can exit a premiership at any time. All the team’s matches are then deleted.

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

3.3.4.  Cups and other events

3.3.4.1.  Entries

A team can enter a cup according to the established cup-rules.

3.3.4.2.  Exits

A team can exit a cup according to the established cup-rules.

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

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

3.4.1.2.  Match Arrangements

Arrangements must be done before a match takes place.
See 3.6 Arrangements for further information.

3.4.2.  Server

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

NOTE: All servers must be located in the United States, unless agreed otherwise.

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

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

3.4.3.  Client Settings

The client settings (e.g. config. values) that are listed in the game-specific rules are to be abided by.

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

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

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

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

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

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

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

3.4.6.5.  Player drops

Should a player drop during a game (e.g. disconnected due to technical problems), then game does not have to be paused. In the event of a drop, a registered substitute may enter the game in the dropped player’s place.

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

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

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

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

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

3.6.1.  Arrangements Day of Defeat: Source

The following changes require agreement of both teams:
- mapchange after a map has been chosen
- players barred because of teamchange are allowed to play

3.6.2.  Classlimits

Lights(Allied Rifleman, Axis Rifleman): max. 3
Heavy:(Allied Support , Axis Support): max. 2
Sniper: max. 1
MG(Allied Machinegunner/Axis MG42): max. 1
Assault (Allied Sergeant/Axis Unteroffizier): max. 1
Bazooka (Allied Bazooka/Axis Pan.): max. 1

3.6.3.  IRC Channel

The official IRC channel for Day of Defeat: Source is #esl.dods (GameSurge).

3.6.4.  Ingame nick

The ingame nick of each player has to have a clear reference to the nick used on the ESL page.
It must be clearly recognizable, which playeraccounts belong to the players on the server.

The following rules overrule all previous rules regarding the same topic.

3.7.1.  General rules

3.7.1.1.  SteamIDs of the players

The ESL teamsheet of a team has to list enough players with a valid STEAMID (entered as STEAMID DoD:S)

6on6: at least 7 SteamIDs

3.7.1.2.  Statusscreenshot (rcon status)

Before the match begins, a "rcon status" Screenshot has to be made. It shows the SteamIDs and the IPs of the connected players.
It must contain all users which want to take part in the match, so it can only be done after all players have connected to the server.

Console commands:

> rcon status
> jpeg

Screenshots made with other programs like HLSW are not valid.
If a player reconnects during the match, making a new screen is recommended.

Both teams are obliged to compare the STEAMIDs on the screenshot with the STEAMIDs of the players in the ESL teamsheet.

One rcon status Screenshot has to be uploaded into the matchdetails after the match.

As only the team providing the server can provide such screen it is their obligation to upload the screen and only they will receive one penalty point when the screen is missing.

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

3.7.1.4.  Player changes

Players can be changed anytime during the game. If the change happens during the round the game does not need to be paused and the opponent does not need to put one player to idle. If the player change happens between rounds, the change shouldn't take more than 5 minutes. Should it take more than 5 minutes, the game has to continue with fewer members. The changed players must be member of the ESL team-sheet including their SteamID DoD:S. It is advisable to take a screenshot of the new player and his SteamID DoD:S.

3.7.1.5.  Prohibited actions

Leaving the server during a match is not permitted.

3.7.1.6.  Illegal actions

1. the intentional use of the "kill" command or other possibilites to eliminate yourself are forbidden. The use of the kill command is only permitted if a player is stuck.
2. the use of any bugs is forbidden
3. you are not allowed to change to another class and back or to spectator to gain a faster respawn

3.7.1.7.  Bugs

The use of bugs is forbidden. If non listed bugs are used, an admin can decide if there has to be a punishment.

During the match:
- To throw grenades under walls or sandbags is not allowed. Above walls and roofs is allowed.
- no pixelwalking

In general:
The use of bugs which offend normal gameplay is forbidden.

Map-specific bugs:
dod_anzio:
- Jumping into the beachhouse, from bridge to over the sewer pipe exit, is forbidden
- It is forbidden to use clipping bugs to see enemys through walls

Game-specific bugs:
-Norecoil/sound glitch that you can get with the heavy and garand (Anyone found using this will be punished under the scale of penalties for cheating.)

3.7.1.8.  Playercounts

6on6: 5on6 and 6on6 are allowed
If a team has not enough players, their opponent can play with one player less. The necessary minimum playercount must be obeyed by both teams.

3.7.1.9.  Playerdrops

6on6: there is no need to idle or pause the game after a playerdrop

In general:
If a team leaves the server completely, the game has to be paused and you have to wait at least 10min for their return.

3.7.1.10.  Serversettings and serverconfigs

All settings of the server must be done according to the config (Download) provided by the ESL.

It contains the base settings like time- and classlimits and the scoring configuration.

If a game is played with wrong settings, an admin can force a rematch with correct settings.

3.7.1.11.  Mandatory programs

VAC2 and Aequitas are mandatory.

Log into esl.eu to download Aequitas and to run it.

3.7.1.12.  Aequitas

The use of Aequitas is mandatory.

If a player cannot present an Aequitasfile after a match he will get 3 penalty points and his team will get 2 penalty points.
This applies to cases in which the file is missing because the player could not start Aequitas. If the player cannot start Aequitas, he is not allowed to play.

If the ESL page is down so all players cannot start Aequitas, you have to wait 20 minutes for the page to come back. In case of doubt contact an admin in #esl.dod.

The files generated by Aequitas have to be uploaded to the match not later than 48 hours after the match.

If more than one Aequitasfile of the winning team or the Aequitasfile of the winning player in a 1on1 match is missing without good reason the match might get deleted (ladder) or the opponent might be granted a default-win (Cups) in the discreationary of an admin.

Uploading a wrong Aequitasfile to a match leads to 4 penalty points for the player and his team.

3.7.1.13.  Legal programs on the server

none

3.7.1.14.  Clientsettings

The following values have to be set in the player's config:

cl_detaildist 1200
m_yaw 0.022
m_pitch +/-0.022
mat_debugdepth 0
mat_debugdepthmode 0
net_graph 1
net_showevents 0
r_drawdetailprops 1
snd_mixahead 0.1

Using custom crosshairs is allowed, but changing the crosshair of sniper weapons is not allowed.

CustomHUDs are allowed as long as they do not contain symbols which are forbidden by law.

Using a DirectX level less than 8.x is forbidden

All other variables in the configs can be changed as long as there is no game-deciding and unfair advantage, comparable with the effect of a cheat.

Additional rules:
Changes of any setting in the scripts folder are strongly forbidden and usually considered as cheat of the highest category (12 PP).

Changing the ingame graphic or textures of the game in the driver, other tools to change to graphics configuration are forbidden!

If your opponent uses different values, you are allowed to file a protest. Only teams/players involved in a match can protest against wrong settings.

3.7.1.15.  Legal scripts

All scripts are allowed, except the ones listed in 3.7.1.16.

3.7.1.16.  Illegal scripts

- Turn Skripte (180° or similar)
- mlook Skripte
- Stop-Shotskripte
- Centerviewskripte
- No-Recoil Skripte
- Burstfireskripte
- Sniper-Scopeskripte
- Scripts that change the netsettings in connection to game actions
- Aliases containing +attack(2) are forbidden
- No binding of +attack(2) on the mousewheel

Penalties (existence of scripts in config is sufficient): in general 6 penalty points + 3 months barrage, in exceptional cases (e.g. active use of No-Recoil) 12 penalty points

3.7.1.17.  Illegal programs

The use of programs which are not listed in 3.7.1.13 is forbidden!

3.7.1.18.  Demos and Screenshots

Each player has to record a demo of each round. SourceTV Demos are not a valid replacement.

If at least one requested demo is missing, the player will get 3 penalty points and his team will get two penalty points.

Missing demos can lead to a Default Win or Matchdelete in the discreationary of an admin.

General rule:
Two missing demos in a 6on6 lead to a match delete (ladder) or defloss (cups).

3.7.1.19.  Demos and Screenshot demands

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. In this request you have to name unequivocally map and side (Axis/Allies) of the demo you want, as well as the SteamID of the player concerned as shown on the status screenshot. If you see within the 30 minutes that your demo request has not been made according to the rules you can correct it by posting a match comment. Please note that this match comment has to fulfill the criteria as mentioned above!

Only if the 'Request match media' function is not available a matchcomment according to the conditions is sufficient to demand demos.

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. If a team aborts the the match, they loose their right to demand demos.

Demos can only be requested from a maximum of 2 players (every round they played), if something suspicious is found more demos can be requested.

Each team is obligated to check the match comments within 30 minutes and if necessary upload the demanded demos within 48 hours.

Should this be not done the match can be deleted and penalized by filing a support ticket. Furthermore the team which demanded the demos can open a protest up to 72 hours after a match. This complaint has to start right with a timetable.

The match can only be deleted due to missing demos within 72 hours after the match.

Subsequent filing of matchmedia
It is not possible to provide demos after the initial timeframe to reduce the penalty.

It is possible to provide missing screenshots up to 72 hours after the end of the match, penalty points which were given for that will be removed.

It is possible to provide missing Aequitas files up to 72 hours after the match has finished. The penalty points for this will be reduced to 1.

In any case an admin has to be contacted to inform him of the subsequent filing.

3.7.1.20.  Cheats in Day of Defeat: Source

Cheats of the first category in Day of Defeat are all kinds of Wallhacks, Multihacks and Aimbots.

Wrong client settings
2 penalty points for each modified settings with a maximum of 6.

Custom files
Using custom files (e.g. models, textures, sounds) is strongly forbidden!

Exceptions:
- muted fullcapture sounds
- Custom HUDs (as long as they do not contain symbols which are forbidden by law)

3 penalty points when using modified files

Any modification of files in the scripts folder is strictly forbidden! Depending on the changes done, up to 12 penalty points might be issued.

3.7.1.21.  Match result

The match result is based on the full captures achieved ("Rounds Won" in the scoreboard).

If this results in a draw, the points scored by the teams for holding flags (tick points) are summed up. The team which got more tick points gets one extra fullcap in the final result.

If two maps are played, the results of both maps are summed up and if there is a draw after both maps the team with more tick points gets an additional fullcapture.

3.7.1.22.  Source TV

A Source TV proxy can be used to broadcast a match as long as it's delay is at least 90s. It is sufficient if one team wants to have a proxy.

It is MANDATORY that if you have a Source TV, it MUST be recording. The team who is in charge of the server will be punished with penalty points if STV demos were requested and they are not able to provide the other team/admins with them.

3.7.1.23.  Teampenalties

In general, the transfer of player penalties to the team defined in rule 2. Penalties applies.

Exceptions are:
- missing demo: 2 penalty points
- missing Aequitasfile: 2 penalty points
- wrong Clientsettings: 2 penalty points
- wrong STEAMID: 2 penalty points

In all of these cases, the maximum penalty given to the team is limited to a maximum of 4 penalty points.

For all other cases, the maximum of 6 penalty points still applies.

3.7.1.23.  Teampenalties

In general, the transfer of player penalties to the team defined in rule 7.1 applies.

Exceptions are:
- missing demo: 2 penalty points
- missing Aequitasfile: 2 penalty points
- wrong Clientsettings: 2 penalty points
- wrong STEAMID: 2 penalty points

In all of these cases, the maximum penalty given to the team is limited to a maximum of 4 penalty points.

For all other cases, the maximum of 6 penalty points still applies.

These rules apply to the premierships (tournaments with groupstages and playoffs like e.g. Winter/Spring/Autumn Season), not to the ladders.

3.8.1.  Default matchdays

The default time to play the matches is the Wednesday of the current matchweek, at 8:00 CST/9:00 EST. However, both teams can schedule the match freely within the matchweek (before the next matchday), if this does not happen and a team can not play on the default date the team has to draw a wildcard, but every team only has 1 wildcard during the groupstage.

3.8.2.  Choice of maps

Each time has to announce the map if chooses at least 48 hours before the match is supposed to start, if this does not happen the opponent can refuse to play the match and the match will be rescheduled to another date.

3.8.3.  Mappool

The following maps are available to be played in a Premiership match:

dod_anzio
dod_argentan
dod_palermo
dod_catania_rc2
dod_coire_rc3
dod_diversion_b4
dod_harrington
dod_lennon
dod_rails_b2
dod_salerno
dod_santos_b3
dod_solitude_match
dod_strausbourg_b3
dod_stug
dod_vallente_rc3

You can download the official mappack here.

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.

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

4.1.2.  Match Arrangements

Arrangements must be done before a match takes place.
See 8. Arrangements for further information.

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

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

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

The client settings (e.g. config. values) that are listed in the game-specific rules are to be abided by.

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.

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.

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.

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.

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

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

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

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

Rules concerning the dates and times of a game, should any exist, are to be found in the specific game rules.

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.

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.

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

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 been barred for inactivity