Rules
Day of Defeat: Source 6on6 Spring League 2014
Quicklinks
[ 7. Penalty points index ] [ 9. Game specific rules ] [10. Game specific rules - addendum]
[ 7. Penalty points index ] [ 9. Game specific rules ] [10. Game specific rules - addendum]
1.
Rules
1.1.
General Points
1.3.
Game Versions
1.4.
Game Coverage
1.6.
ESL Timezone
1.7.
Suggestions
1.8.
Internal Texts
1.9.
International language*
2.
Cheating
2.1.
General
2.1.1.
Bypassing Wire Anti-Cheat
2.2.4.
Compulsory programs
2.2.5.
Server modifications
3.1.
Player Registration
3.1.1.
Nicknames and URL Aliases
3.1.2.
Playerphoto
3.2.
Teams
3.2.1.
Team players
3.2.3.
Changing team names
3.2.4.
Team fusion
3.2.6.
2on2 teams
3.3.
Internet cafes
4.1.
General Points
4.2.
Ladders
4.2.1.
General Terms and Conditions
4.2.2.
Entries
4.2.3.
Exits
4.3.
Premierships
4.3.1.
General terms and conditions
4.3.2.
Entries
4.3.3.
Exits
4.3.4.
Team accounts
4.4.1.
Entries
4.4.2.
Exits
4.5.
ESL Pro Series
4.6.
ESL Amateur Series
5.
Matches
5.1.
Game Preparations
5.1.1.
Match Broadcasting
5.1.2.
Match Arrangements
5.2.
Server
5.2.1.
Choice of server
5.2.2.
Server settings
5.2.3.
Ping
5.3.
Client settings
5.4.
Results
5.5.
Illegal actions
5.6.1.
Failure to appear to a match
5.6.2.
Not enough players in a team
5.6.3.
Game offenses
5.6.4.
Server problems
5.6.5.
Player drops
6.1.
Screenshots
6.2.
Demos and replays
7.1.
In General
7.2.
Breach of netiquette
7.2.1.
Insults
7.2.2.
Spamming
7.3.1.
Failure to appear
7.3.2.
Game Abort
7.3.3.
Spamming during a game
7.3.4.
Player kicks during a match
7.3.6.
Breaking engagements
7.4.
Deceptions
7.4.1.
Fake match
7.4.2.
Faking results
7.4.3.
Fake match media
7.4.4.
Other deceptions
7.5.1.
Inactive player barrage
7.5.2.
Barred players
7.5.3.
Unregistered players
7.5.4.
Ringers/Fakers
7.8.
Cheating
7.8.2.
Cheating
7.9.
Multi accounts
7.10.1.
Normal compulsory challenges
7.10.2.
Intense compulsory challenges
8.
Arrangements
8.2.
Classlimits*
8.3.
IRC Channel*
8.4.
Ingame nick*
9.1.
General rules*
9.1.1.
SteamIDs of the players*
9.1.2.
Statusscreenshot (rcon status)*
9.1.3.
Warmup und Mapcheck*
9.1.5.
Player changes*
9.1.6.
Prohibited actions*
9.1.7.
Illegal actions*
9.1.8.
Bugs*
9.1.8.1.
Map-specific bugs*
9.1.9.
Playercounts*
9.1.10.
Playerdrops*
9.1.11.
Serversettings and serverconfigs*
9.1.12.
Mandatory programs*
9.1.12.1.
Aequitas*
9.1.12.2.
DBlocker*
9.1.13.
Legal programs on the server*
9.1.14.
Clientsettings*
9.1.15.
Legal scripts*
9.1.16.
Illegal scripts*
9.1.18.
Illegal programs*
9.1.19.
Demos and Screenshots*
9.1.20.
Demos and Screenshot demands*
9.1.20.1.
Subsequent filing of matchmedia*
9.1.21.
Spawnprotection*
9.1.21.1.
General rules*
9.1.21.2.
Forbidden*
9.1.21.3.
Allowed*
9.1.22.
Cheats in Day of Defeat: Source*
9.1.22.2.
Wrong client settings*
9.1.22.3.
Custom files*
9.1.23.
Match result*
9.1.23.1.
Match result 1on1*
9.1.24.
Selfkill*
9.1.26.
Source TV*
9.1.27.
Teampenalties*
9.2.1.
Mappool*
9.2.2.
Matches between Team members*
9.2.3.
Ladder-specific rules*
10.1.
Default matchdays*
10.1.5.
Risultato
10.1.6.
Game Account
10.2.
Choice of maps*
10.3.
Mappool*
* 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
• 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: http://www.esl.eu/faq/110/.
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.
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.
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.
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.
During ladder play, no two squads from the same team are allowed to play each other.
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.
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.
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.
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
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 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.
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.
4.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.
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.
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.
Further details can be found in rule 1.4 Game Coverage.
5.1.2.
Match Arrangements
Arrangements must be done before a match takes place.
See 8. Arrangements for further information.
See 8. Arrangements for further information.
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.
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.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.
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.
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.
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.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.
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.
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.
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.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.
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.
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.
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.
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.
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
Team:
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.
1on1:
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!
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.
1on1:
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.
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.
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.
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.
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.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.
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.
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.).
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.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.
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.
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.
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.
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.
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
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
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
8.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
- mapchange after a map has been chosen
- players barred because of teamchange are allowed to play
8.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 (0 in 2on2s)
Assault (Allied Sergeant/Axis Unteroffizier): max. 1
Heavy:(Allied Support , Axis Support): max. 2
Sniper: max. 1
MG(Allied Machinegunner/Axis MG42): max. 1 (0 in 2on2s)
Assault (Allied Sergeant/Axis Unteroffizier): max. 1
8.3.
IRC Channel
The official IRC channel for Day of Defeat 1.3 and Day of Defeat:Source is #esl.dod (QuakeNet).
8.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.
It must be clearly recognizable, which playeraccounts belong to the players on the server.
9.
Special rules for Day of Defeat:Source in the ESL
The following rules overrule all previous rules regarding the same topic.
9.1.
General rules
9.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)
2on2: 2 SteamIDs
3on3: at least 3 SteamIDs
6on6: at least 7 SteamIDs
2on2: 2 SteamIDs
3on3: at least 3 SteamIDs
6on6: at least 7 SteamIDs
9.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.
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.
9.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.
9.1.5.
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.
9.1.6.
Prohibited actions
Leaving the server during a match is not permitted.
9.1.7.
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, skip a weapon reload time, regain full health, get a better spawn position or gain other advantages. In case you accidentally violated the rule, penalties can be avoided by staying where you are and dropping your weapon for at least 5 seconds.
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, skip a weapon reload time, regain full health, get a better spawn position or gain other advantages. In case you accidentally violated the rule, penalties can be avoided by staying where you are and dropping your weapon for at least 5 seconds.
9.1.8.
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
- The constant spamming of the crouchfunction ingame is forbidden. This also includes abusive spamming of the crouch function to achieve a lag while jumping or moving around a corner. Punishments will only be given away by abusive usage of the crouchbugs, this does not include pressing the duck-key e.g. twice or thrice.
In general
The use of bugs which offend normal gameplay is forbidden.
During the match
- To throw grenades under walls or sandbags is not allowed. Above walls and roofs is allowed.
- no pixelwalking
- The constant spamming of the crouchfunction ingame is forbidden. This also includes abusive spamming of the crouch function to achieve a lag while jumping or moving around a corner. Punishments will only be given away by abusive usage of the crouchbugs, this does not include pressing the duck-key e.g. twice or thrice.
In general
The use of bugs which offend normal gameplay is forbidden.
9.1.8.1.
Map-specific bugs
dod_anzio:
- Jumping into the beachhouse is forbidden
- It is forbidden to use clipping bugs to see enemys through walls
- Jumping into the beachhouse is forbidden
- It is forbidden to use clipping bugs to see enemys through walls
9.1.9.
Playercounts
2on2: 1on2 is forbidden
3on3: 3on3 and 4on4 are allowed
6on6: 5on6 und 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.
3on3: 3on3 and 4on4 are allowed
6on6: 5on6 und 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.
9.1.10.
Playerdrops
1on1: if a player leaves the server, the game has to be paused by the other player. You have to wait at least 5 min for the return of the dropped player.
2on2: if a player leaves the server, the game has to be paused by the team still complete. You have to wait at least 5 min for the return of the dropped player.
3on3: If a player leaves the server, a player of the opponent team can idle.
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.
2on2: if a player leaves the server, the game has to be paused by the team still complete. You have to wait at least 5 min for the return of the dropped player.
3on3: If a player leaves the server, a player of the opponent team can idle.
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.
9.1.11.
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.
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.
9.1.12.
Mandatory programs
VAC2 and Aequitas are mandatory.
9.1.12.1.
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.
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.
9.1.12.2.
DBlocker
If both Teams agree to play on a Server with DBlocker no punishments for wrong clientsettings will be given away. Before playing on a DBlocker Server, both teams have to agree to play on such a server in the matchcomments
9.1.13.
Legal programs on the server
-DBlocker
9.1.14.
Clientsettings
The following values have to be set in the player's config:
cl_bob 0.002
cl_bobcycle 0.8
cl_bobup 0.5
developer 0
r_drawdetailprops 1
m_yaw 0.022
m_pitch -/+0.022
mat_debugdepth 0
mat_debugdepthmode 0
mat_showlowresimage 0
mat_picmip 0, 1 or 2
net_graph 0 or 1
rope_rendersolid 1
snd_mixahead 0.1
snd_show 0
mat_filtertextures 1
cl_detaildist 1200 or higher
cl_detailfade 400 or higher
Changing the crosshair of sniper weapons is not allowed.
Custom HUDs 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.
cl_bob 0.002
cl_bobcycle 0.8
cl_bobup 0.5
developer 0
r_drawdetailprops 1
m_yaw 0.022
m_pitch -/+0.022
mat_debugdepth 0
mat_debugdepthmode 0
mat_showlowresimage 0
mat_picmip 0, 1 or 2
net_graph 0 or 1
rope_rendersolid 1
snd_mixahead 0.1
snd_show 0
mat_filtertextures 1
cl_detaildist 1200 or higher
cl_detailfade 400 or higher
Changing the crosshair of sniper weapons is not allowed.
Custom HUDs 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.
9.1.15.
Legal scripts
All scripts are allowed, except the ones listed in 9.1.16.
9.1.16.
Illegal scripts
- Turn Scripts(180° or similar)
- mlook Scripts
- Stop-Shotscripts
- Centerviewscripts
- No-Recoil Scripts
- Burstfirescripts
- Sniper-Scopescripts
- Stopsound-Scripts
- Scripts that change the netsettings in connection to game actions
- Aliases containing +attack(2) are forbidden
- No binding of +attack(2) on the mousewheel
Any binds or aliases which change the original movement of the game, speed up progresses of the game or change any cvars such as rates or fps in order to gain an advantage over an opponent are forbidden. Simple binds or aliases to change ingame nicks, maps or scripts which do not give the player an advantage while being ingame are still allowed.
Examples for forbidden Scripts are: Weaponswitchscripts (only +lastinv bound to a key and hud_fastswitch 1 is allowed), Sprinttoggles, Duckjumpbinds, etc.
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
- mlook Scripts
- Stop-Shotscripts
- Centerviewscripts
- No-Recoil Scripts
- Burstfirescripts
- Sniper-Scopescripts
- Stopsound-Scripts
- Scripts that change the netsettings in connection to game actions
- Aliases containing +attack(2) are forbidden
- No binding of +attack(2) on the mousewheel
Any binds or aliases which change the original movement of the game, speed up progresses of the game or change any cvars such as rates or fps in order to gain an advantage over an opponent are forbidden. Simple binds or aliases to change ingame nicks, maps or scripts which do not give the player an advantage while being ingame are still allowed.
Examples for forbidden Scripts are: Weaponswitchscripts (only +lastinv bound to a key and hud_fastswitch 1 is allowed), Sprinttoggles, Duckjumpbinds, etc.
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
9.1.18.
Illegal programs
The use of programs which are not listed in 9.1.13 is forbidden!
9.1.19.
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:
1 missing demo in 1on1/2on2/3on3 or two missing demos in a 6on6 lead to a match delete (ladder) or defloss (cups).
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:
1 missing demo in 1on1/2on2/3on3 or two missing demos in a 6on6 lead to a match delete (ladder) or defloss (cups).
9.1.20.
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.
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.
9.1.20.1.
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.
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.
9.1.21.
Spawnprotection
9.1.21.1.
General rules
The clanleaders are responsible for ensuring that all members know and obey the spawn protection rules.
If a player violates the rules, the admins will punish that and add further actions.
Play fair and show that you can win in a clean fight.
If a player violates the rules, the admins will punish that and add further actions.
Play fair and show that you can win in a clean fight.
9.1.21.2.
Forbidden
• throwing grenades into the spawn
• shooting into the spawn (exception: players on the spawnramps)
• shooting into the spawn (exception: players on the spawnramps)
9.1.21.3.
Allowed
• pass the spawn (see mapscreens)
• throwing grenades in front of the spawnramps
• players situated on the spawnramps can be killed, but without blocking the spawn
In cases of doubt, a certain behaviour will rather be seen as allowed than as prohibited.
• throwing grenades in front of the spawnramps
• players situated on the spawnramps can be killed, but without blocking the spawn
In cases of doubt, a certain behaviour will rather be seen as allowed than as prohibited.
9.1.22.
Cheats in Day of Defeat: Source
Cheats of the first category in Day of Defeat are all kinds of Wallhacks, Multihacks and Aimbots.
9.1.22.2.
Wrong client settings
2 penalty points for each modified settings with a maximum of 6.
9.1.22.3.
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.
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.
9.1.23.
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 are summed up. The team which got more point 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 teampoints gets an additional fullcapture.
If this results in a draw, the points scored by the teams for holding flags are summed up. The team which got more point 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 teampoints gets an additional fullcapture.
9.1.23.1.
Match result 1on1
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 players for holding flags (the + value next to the fullcapture count, not the flagcap count in front of the frag count) are summed up. The player which got more point gets one extra fullcap in the final result.
If there is still a draw after counting the flag points, the frags will be compared. The player with more frags wins the game.
If this results in a draw, the points scored by the players for holding flags (the + value next to the fullcapture count, not the flagcap count in front of the frag count) are summed up. The player which got more point gets one extra fullcap in the final result.
If there is still a draw after counting the flag points, the frags will be compared. The player with more frags wins the game.
9.1.24.
Selfkill
1 penalty point for the team for each intentional selfkill with a maximum of 4.
9.1.26.
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.
9.1.27.
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.
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.
9.2.
Special rules for Day of Defeat:Source ladders in the ESL
9.2.1.
Mappool
The mappool and links to mappacks can be found in the Infos&Details section of each ladder.
9.2.2.
Matches between Team members
Matches between Team members are not allowed. Should the Instant Challenger generate a match between Team members, the match must be deleted at the match setup page. When this will be not done the match will be deleted and if necessary, penalty points will be given.
This rule does not apply to 1on1 matches.
This rule does not apply to 1on1 matches.
9.2.3.
Ladder-specific rules
The Infos&Details section of the ladders might contain more rules which are specific for this ladder (e.g. the Sniper Ladder).
10.
Special rules for Premierships (aka Seasons)
These rules apply to the premierships (tournaments with groupstages and playoffs like e.g. Winter/Spring/Autumn Season), not to the ladders.
10.1.
Default matchdays
The default time to play the matches is the Sunday of the current matchweek, at 20.00 CET. However, both teams can schedule the match freely within the matchweek, 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.
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.
10.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.
10.3.
Mappool
The following maps are available to be played in a Premiership match:
dod_anzio
dod_argentan
dod_catania_rc2
dod_coire_rc3
dod_diversion_b4
dod_harrington
dod_lennon
dod_salerno
dod_santos_b3
dod_solitude_match
dod_vallente_rc3
dod_anzio
dod_argentan
dod_catania_rc2
dod_coire_rc3
dod_diversion_b4
dod_harrington
dod_lennon
dod_salerno
dod_santos_b3
dod_solitude_match
dod_vallente_rc3
Copyright
All content appearing in this document is the property of Turtle Entertainment GmbH or is being used withthe 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
GmbH.
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.