Counter-Strike: Source 5on5 Amateur Series 1st Division
Last change: 30.03.2011 13:05
These are the rules for the Counter-Strike: Source 5on5 Amateur Series 1st Division. We make every effort to ensure the rules are complete and up to date but this may not always be the case. You should also check the Rules & Information and News for additions, exceptions and modifications that may apply. All players must meet the requirements listed in the Rules & Information at the time the match is scheduled to begin. The rules are a guideline and the decisions by admins may differ from them depending on the circumstances. If you have any questions about the rules, please write a support ticket.
- 1. Match Media
- 1.1. Screenshots
- 1.2. Demos
- 1.2.1. Requesting demos
- 2. Settings
- 2.1. Player settings
- 2.1.1. Wire Anti-Cheat
- 2.1.2. CVARs
- 2.1.3. Illegal scripts
- 2.1.4. Custom files
- 2.1.5. Color depth
- 2.1.6. Illegal programmes
- 2.1.7. Content of the Configfolder
- 2.1.8. In-Game Overlays
- 2.2. Server settings
- 3. Match rules
- 3.1. Before the match
- 3.1.1. Server choice
- 184.108.40.206. Usage of Protected Game-Servers
- 3.1.2. Nickname and clan tag
- 3.1.3. Warmup
- 3.1.4. Map check
- 3.1.5. Match Broadcasting
- 3.2. During the match
- 3.2.1. Choice of Side
- 3.2.2. Number of players
- 3.2.3. Server crash
- 3.2.4. Player drop
- 3.2.5. Change of players
- 3.2.6. Game intermissions
- 3.2.7. Usage of Pause function
- 3.2.8. Abortion of a map after 16 victorious rounds
- 3.3. Bugs and forbidden actions
- 3.4. After the match
- 4. Penalty points
1. Match Media
All match media (screenshots, demos, etc) must be kept for at least 14 days. In general, you should upload the match media from a match to the match page as soon as possible. Faking or manipulating match media is of course forbidden and will result in severe penalties. Match media should be named clearly based on what it is. It is not possible to file a protest or write a support ticket to complain about bad match media naming. However, if an admin is hindered in their work because of bad match media names then it can be punished for.
An admin may extend the upload period of the following matchmedia in special cases.
It is the responsibility of both sides to ensure all screenshots are uploaded to the match page within 24 hours of the match ending.
1.1.1. Score screenshot
A screenshot of the scoreboard at the end of each half must be taken and uploaded to the match page within 24 hours.
220.127.116.11. Rcon Status screenshot
A Rcon status screenshot must be taken:
- at the beginning of the match
- in case of a server/player change
- if a player reconnects
Rcon status screenshots made with the help of programs like HLSW etc. are not sufficient.
In order to take a rcon status you have to use the console command "rcon status" (don’t forget to enter your rcon password) followed by "jpeg".
It is mandatory for all players to record point of view (POV) demos for the full duration of all matches without exception. Players should record one demo per half of a map. SourceTV demos are not a replacement.
Incomplete, defective, manipulated or edited demos will in general be treated as missing demos.
If a protest gets opened for a match, all matchmedia need to be kept atleast 14 days after the protest got closed.
1.2.1. Requesting demos
Demos can only be demanded up to a maximum of 30 minutes after a match via the 'Request match media (demos/replays)' function on the match details page.
A demo request must state only which side, CT' or 'T.
If it turns out that your demo request was not made according to the rules, you can correct it within the 30 minutes by posting it as match comment or reports. This is possible as long as the other side did not yet fulfil the previous request. If a demo request is corrected, the upload time limit will be extended by 30 minutes from the time of correction.
If a player or a team illegally aborts the match, they lose their right to demand demos.
In all Ladders: You are allowed to demand one demo - that is T or CT from one player - per match.
Both sides should check the demo requests of a match after the 30 minutes has passed. The requested demos must be uploaded to the match page within 24 hours (packed in separate *.zip files). If you use a program other than Winzip to zip your files, make sure that you choose "Compression method – normal". If you do not then you will get an error message like "file corrupted" and the upload will be aborted.
If any demo is missing after 24 hours then you must open a protest ticket within the 72 hour protest period to complain. The player will get an additional 24 hours from the opening of the protest to upload their demos.
If after this deadline the player(s) still have not uploaded their replay(s), then the match may be deleted and the player(s) and team punished with 3 penalty points. If the player(s) do upload their replay(s) by this deadline, then the player(s) and team will receive 1 penalty point.
2.1. Player settings
2.1.1. Wire Anti-Cheat
ESL Wire Anti-Cheat is mandatory for all players to use for the full duration of all matches without exception. If a player cannot use Wire Anti-Cheat then they are not allowed to take part in a match.
If the website is down, making WAC unusable, then the match must be postponed.
The following CVAR values must be used:
- mat_dxlevel 80/81/90/95 (using a mat_dxlevel between 80 and 95 is mandatory)
- mat_bumpmap 1/0 (if you use "mat_bumpmap 0", you also have to use "mat_specular 0"; if you use "mat_bumpmap 1", you can either use "mat_specular 0" or "1")
- net_graph 0/1 (0 and 1 are allowed values)
The above settings are forced by Zblock, i.e. joining the server with wrong client settings is not possible. Therefore you are not allowed to file a protest if your opponent uses different settings.
- mat_fastspecular 1
- r_rootlod 0/1/2 ( 0, 1, 2 is allowed)
- cl_pitchspeed 225
- cl_yawspeed 210
2.1.3. Illegal scripts
In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts:
- Stop Shoot scripts [Use or Awp scripts]
- Center view scripts
- Turn scripts [180° or similar]
- No Recoil scripts
- Burst fire scripts
- Rate changers (Lag scripts)
- FPS scripts
- Anti flash scripts or binding (snd_* bindings)
- Bunnyhop scripts
- Stop sound scripts
2.1.4. Custom files
Custom-files are not allowed. Everything is considered as custom-file which changes or replaces the original ingame-grafics, *.gcf-files or sounds. This also includes changed HUDs, Scoreboards or sounds (volume, soundscapes).
2.1.5. Color depth
The usage of a color depth of 16bit is not allowed. Evidence of usage can only be given by ESL Wire, protests because of Screenshots are not allowed and will be rejected.
2.1.6. Illegal programmes
18.104.22.168. Config changes - Videocard drivers or similar tools
Changing the game graphics or textures with the help of videocard drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. Nvidia SLI Display, Rivatuner Overlays) is illegal. Failure to comply with this rule will result in 6 penalty points for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized.
Punishment will be given regardless of whether the script/binding is executed via external hardware or software.
Also binding any snd_ command is forbidden.
2.1.7. Content of the Configfolder
In the config folder you are only allowed to have config files. Pictures, Demos, Screenshots and zipped Files are forbidden. If an Admin is hindered in his work because of too many unclear/chaotic config files, penalty points ( 1-3 ) will be distributed. Protest and Support tickets opened because of this rule are illegal and will be ignored.
2.1.8. In-Game Overlays
All In-Game overlays - provided by the game itself - except the following are forbidden:
- net_graph 0
- net_graph 1
- cl_showpos 1
- cl_showfps 1
2.2. Server settings
Only the following server settings and mods may be used.
2.2.1. Server plugins
No server plugins except those listed below are allowed to be used.
VAC2 must be enabled on the game server.
Using the latest version of zBlock approved by the ESL is mandatory.
Using the latest server configs is mandatory. The .zip file contains configs for all ladders plus a readme file.
3. Match rules
3.1. Before the match
3.1.1. Server choice
The ESL does not supply servers for matches, players and teams must provide their own and come to an agreement with their opponent as to which to use. If you cannot come to an agreement with your opponent then the match is split over two servers by half or by map.
The internet is changing continuously and the connection to a server is not always perfect. Players and teams have to agree on a server that offers both sides an equal ping. Nevertheless every player should know, that they will sometimes have to play with a bigger ping difference. In this case we have to appeal to the sportsmanship and fairness of the players and teams. The right to change server or fake lag does not exist.
22.214.171.124. Usage of Protected Game-Servers
If both teams come from the same country (meaning the majority of players is from a specific country) and one of the teams can provide a certified Gameserver (see ESL Gameserver Certificate), this server has to be used for the entire match. If both teams can provide a certified server, the match may be played on both servers in equal parts if teams cannot agree on playing on one.
3.1.2. Nickname and clan tag
Each player has to use a nickname that is at similar to the nickname he/she entered in his ESL player sheet. You are not allowed to change your nickname in-game. In team matches the players are allowed to use a clan tag, but it has to be the same for all players of this team. However you cannot file a protest or write a support ticket to complain if your opponent breaks this rule.
If an admin's job is hindered because of wrong or difficult nicknames or clan tags, the players and team concerned will get penalty points.
Before a match starts, both teams must state that they are ready to start the match. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated.
3.1.4. Map check
Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug.
3.1.5. 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.
126.96.36.199. SourceTV delay
If SourceTV broadcasts a game, the delay has to be 90 seconds or more.
It is legal to broadcast a match via SourceTV as longs as one team wants to do so and is able to provide the necessary server. Any other kind of broadcast is legal if both teams agree on it. If you want to broadcast a match please discuss it with your opponent in advance. For further information please check 1.4 Game Coverage . However you are obliged to upload an rcon status (and tv_status) screen that shows the necessary delay of at least 90 seconds.
188.8.131.52. LAN matches
It is possible to play a match on LAN when the following requirements are fulfilled:
- both sides agree (either via support (both sides) or protest)
- the ticket must be filed at least 72 hours before the match
- Wire Anti-Cheat is still mandatory
- Protests, which are not comprehensible by an admin will be rejected (e.g. ringer, fake match, deceptions, etc.)
3.2. During the match
3.2.1. Choice of Side
In all CS:S matches you have to play a knife round first. The winner will then choose the side. Only knives and kevlar vests are allowed to be used.
3.2.2. Number of players
Following terms of minimum number of players are:
2on2: 1on2 is forbidden, only 2on2 is allowed.
3on3: Only 3on3 is allowed.
5on5: 4on4, 4on5 and 5on5 is allowed. If one player in a team is missing the team can nevertheless play the match. The opposing team can decide freely whether they want to play with all players or with one player less as well.
3.2.3. Server crash
If the server crashes before three rounds have been completed, the server must be restarted and the match's score will be reset to 0-0.
If the server crashes after the third round has been completed, the match must be restarted with startmoney 5000 and the score will be counted from the last completed round. The start money is set to 2000 and the team that lost the last round kills itself using "kill" in the console. This round does not count. The match begins with the following round. The start money has to be set to 800 again.
3.2.4. Player drop
If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server will be paused at the end of the current round (see rule Usage of Pause function).
The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed.
When the match is continued, the start money is set to 2000 and the team that lost the last round kills itself using "kill" in the console. This round does not count. The match begins with the following round. The start money has to be set to 800 again.
If the player, or a substitute player does not connect within that time then the match is continued 4on5, or 4on4 if the opposing team agrees.
3.2.5. Change of players
Players can be changed at any time but the opposing team has to be informed in advance. If necassary the game can be paused (see rule Usage of Pause function). This change may not take more than 5 minutes. After the waiting time the game can be also continued without the full team and the player can join in the running game. Changed players must be registered in the team with their SteamID HL2/CSS and it's recommended to do a status screenshot when a new player arrives on the server.
3.2.6. Game intermissions
If a game is interrupted, the match is valuated up until that point. The game is continued according to the following procedure: - The start money is set to 2000 for the remaining game time. - The team that lost the last round kills itself using the function “kill” in the console. This round does not count. - The game begins with the next round. - Should further maps have to be played after this map, the start money must be set back to the normal value (800).
This rule serves the purpose of covering unexpected intermissions that are not wilfully brought about by the teams. So if a game is interrupted but cannot be continued on the same day, the remaining game time can be played at a later date but within seven days. If the teams/players fail to agree on a date, an admin will determine the date. If a team/player fails to appear an admin will decide whether the match is rated as 'did not show up' or 'match abort'.
3.2.7. Usage of Pause function
If you have a problem that prevents you from playing on, you are allowed to use the pause function. The pause function has to be used at the beginning of the next round (freezetime). You have to announce the reason before or immediatly after you used it. If no reason is given, you may unpause the game and continue playing. Unpausing or pausing the game without any reason will lead to penalty points (see 6.3. Unsportsmanlike behaviour). If the problem can't be solved (max. 10 minutes pausetime) see rule 4.2.6. Game intermissions.
3.2.8. Abortion of a map after 16 victorious rounds
If a team achieves 16 won rounds at a map, the teams can abort this map. All missing rounds of this map will then be added to the team that stayed on the server.
184.108.40.206. Abortion of a map after 10 victorious rounds
In MR9 ladders (Handgun, Aimmap) the match can be aborted under the same conditions after achieving 10 won rounds.
3.3. Bugs and forbidden actions
The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary.
Boosting, sky walking, sharking
To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.
Climbing with help of the team mates is allowed in general. Not allowed are positions where textures disappear in walls or grounds if a special movement (e.g. a jump) is required. For example the barbed wire fence in prodigy and nuke upper hall roof.
To throw grenades inside walls is not allowed. Above walls and roofs is allowed.
Self-kills by console or by other means (e.g. Abysses) in order to receive money quickly or in order to shorten the round time is strictly forbidden.
Any bug-using is forbidden.
Planting the bomb
To plant the bomb in a way that it cannot be reached is forbidden. Places that can reached with help of a team mate are allowed. Violating this rule will result in the deduction of 3 rounds.
Hiding the bomb
You are allowed to move the bomb, but you must not move it to a place where your opponent cannot pick it up. Violating this rule will result in the deduction of 3 rounds.
3.3.2. Map specific bugs
The following map specific bugs/positions are forbidden to use:
Only one player at a time is allowed to stand on the following position: #1
Looking through this gap is not allowed: #1
Looking through this gap is not allowed: #1
To plant the bomb at/in the fountain so that it cannot be defused is illegal.
The following positions are illegal: #1
Looking over this wall is not allowed: #1
The use of custom spraylogos is restricted. Spraylogos must not: - contain racist contents - show weapon/player models or bombspot logos etc. or any other things that might confuse the players - contain single-coloured textures that are used to achieve a higher contrast - spraylogos that look like parts of a cheat (e.g. esp-boxes) are forbidden. Usage may be punished according to Unsportsmanlike behaviour!
3.4. After the match
3.4.1. Right to write a support ticket/file a protest
Only teams/players involved in a match are allowed to write a support ticket or to file a protest.
3.4.2. Game Abort
If a team aborts a match before it is finished, a win may be granted to the remaining team if the match advanced to a point where the end-result can be determined. If your opponent should deliberately leave the game, you must definitely file a protest. You are not permitted to enter a result yourself. This would be penalized as a faking of results.
4. Penalty points
In general, a player can receive up to 6 penalty points, and a team up to 4 penalty points per match, unless a single violation has a higher punishment. A team is only punished once per violation, regardless of how many players. Where a player or team receives penalty points for multiple violations, the penalty points are added together.
|Rule violation||Number of penalty points|
|No show||Team: 3; Player: 2|
|Reject compulsory challenge||Normal: 1 |
Intense (top 10): 2
|Abort match||Player / Team: 4|
|Use of ineligible player|
|Inactive barrage||Player / Team: 3|
|Barraged||Player / Team: 6|
|Unregistered player||Player / Team: 3|
|Missing Premium (where required)||Player / Team: 3|
|Missing Trusted (where required)||Player / Team: 3|
|Ringer/Faker||Player / Team: 6|
|Playing with wrong gameaccount||Player / Team: 3|
|Playing without a registered gameaccount||Player / Team: 3|
|Multiple/Fake accounts||Warning / 1-3 penalty points|
|Creating new teams||Warning / 4 penalty points / Ladder ban|
|Faking country/nationality||Warning / 1 / 2 / 3 penalty points|
|Kick player(s) from server||Player / Team: 4|
|Deception||Player / Team: 1 - 4|
|Fake result||Player / Team: 4|
|Fake match media||Player / Team: 6|
|Fake match||Player / Team: 6|
|Cheating||Player: 12 / Team: 6|
|Illegal config setting||Player: 2; Team: 2 per setting if more than 1 player|
|Illegal script||Player / Team: 2, 4 or 6|
|16 bit (CS 1.6)||Player / Team: 2|
|Custom files||Player / Team: 2|
|Custom HUD/scoreboard||Player / Team: 1, no match delete|
|Wrong server settings||Team: 2 - 4|
|Missing, incomplete demos||Player / Team: 2|
|Missing, incomplete Aequitas file||Player / Team: 2|
|Late Aequitas file||Penalty points deleted|
|Missing, incomplete screenshots||Player / Team: 1 |
|Missing matchmedia with cheat suspicion||Player / Team: 6 |
|Bug use||Player / Team: 2 per use|
All content appearing in this document is the property of Turtle Entertainment GmbH
or is being used with the owner's permission. Unauthorized distribution, duplication,
alteration or other use of the material contained in this document, including without
limitation any trademark image, drawing, text, likeness or photograph, may constitute a
violation of the laws of copyright and trademark and may be prosecuted under criminal
and/or civil law.
No part of the content of this document may be reproduced in any form or by any means or stored in a database or retrieval system, except for personal use, without the written permissions of Turtle Entertainment 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.