Rules

play CS:GO 5on5 Female Open Summer 2017

Last change: 24.05.2017 17:02

These are the rules for the CS:GO 5on5 Female Open Summer 2017. 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 Info Page and News for additions, exceptions and modifications that may apply. 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. General

1.1. Validity

If there are single terms of this rulebook invalid or impracticable, the efficacy of the other terms stays untouched. In this case, the term which is invalid will replaced by another term, which is similar to the other term.

1.2. Code of conduction

Every participant has to behave respectful towards the representatives of the ESL, press, viewers, partners and other players. The participants are requested to represent the eSport, the ESL and their Sponsors worthy. This is meant for delicts ingame and also in chats, messengers, comments and other media. The participation of matches in the tournament under the influence of drugs or alcohol is forbidden. Violation against the Code of Conduct will result in penalties or in heavy cases to disqualification.

1.3. Broadcasts

The right of Broadcasts for all matches are in hand of the ESL and Munich Finest Gaming. This contains every form of Broadcasts and Capturing, for example: IRC Bots, Shoutcasts, GoTV, Replays or Television Broadcasts. The ESL and Munich Finest Gaming is allowed to assign the rights to a third party or participants. This has to be arranged with the league admin team. Officially named streams cannot be declined by the participants.

1.4. General behavior

Make sure to obey the instructions made by the referee. Every attendant has to behave sportsmanlike and fair. Swearing, insulting and every form of aggressive behavior (e. g. hitting the table with your fists) can be punished by the referees.

1.5. Right to play

Every team that has 5 female players has the right to play. Due to the specific restriction of this tournament, only female players are allowed to play. If we are not sure about the gender of any player we will need an official documentation stating a player's gender is female. All teams globally can participate, but must provide one official document if requested. Teams outside the European continent must possess a good connection to the European ESL servers of <200ms ping to not affect a bad game performance.

1.6. Cheating / Bugusing

Every form of cheating is illegal. For example: Aimbots, Maphacks, Ghosting in streams, and also match arrangements. Cheatbans apply in the whole ESL. If a player participating in Female Open gets caught cheating this will result in a disqualification for the team. That means all matches are deleted. If a cheater fakeaccount gets detected, matches where he participated will be deleted.

1.7. Penalties

Penalties can be: Bans, penalty points and disqualifications. The heaviness of the penalty is based on the heaviness of the delict and can get higher by repeated delicts. Extreme delicts (e.g. Cheating), or bad behavior will result in an instant disqualification. In case of a disqualification the participant loses all the prize money he has won.

1.8. No show

The waiting time is 20 minutes starting from the time of the match. You have to confirm the match and start ESL Anticheat in order to show your presence and willingness to play. The Anti Cheat Logs prove your presence. In case of Steam problems (e.g. VAC authentication error) the waiting time may be extended by 15 minutes. A screenshot showing the error has to be uploaded to the match page immediately. Please open a protest to get a default win, this is the fastest way to get your match checked, as the admins can not check all matches of a tournament manually.

1.9. Disqualification

Teams showing no real effort to play matches or teams that are obviously blocking may be disqualified.

1.10. Adding new players

During the group stage teams are allowed to add three new players. During the playoffs teams are allowed to add two more players. The start of the group stage and playoffs is defined by the first default match date. Teams will be locked one day prior to the first default match date. As of then this rule is effective. Every new player must be announced via support ticket. It’s recommended to announce new players in a timely manner because the team needs to be unlocked and locked again. It’s also recommended to start the season with enough players since it’s not possible to add more players than defined above. If a team is not able to play with 5 players this will be handled as a no show.

1.11. Voice Server

The teams have to join the Teamspeak server MunichFinestGaming.de for there matches. Admins will do voice checks if needed there.

1.12. Playoff seeding

Seeding is in accordance with the ranking. Example: 1st place group A – seeding 1, 1st place group B – seeding 2 and so on … 2nd place group A – seeding 6, 2nd place group B – seeding 7 and so on …

2. Offline Event

2.1. Behavior

Instructions of referees must be followed in any event. Eating is not allowed in our tournament area. Drinks have to be stored in our special bottles. Items which are not required to play (cellphones, watches, chewing gums etc.) should be removed from the tables. Exceptions are possible with the agreement of a referee (mascots, tissues, etc.) After the Game, every garbage made by the player has to be removed. Delicts can be punished with penalty points. Every attendant has to behave sportsmanlike. Swearing, insulting and every form of aggressive behavior (e. g. hitting the table with your fists) can be punished by the referees.

2.2. Dresscode

A representative of the league admin team can ban pieces of clothes, if there are unwanted Logos, slogans or symbols.

2.3. Hardware and Software

Generally, the monitors, PCs, consoles and headsets provided by the sponsors, have to be used. The participants are responsible for the peripheral devices (Mouse, Keyboard, Mousepad, In-ears, Headsets, Gamepads). Players can use their own config with the agreement of a referee. The usage of mass storage devices (CDs, USB Sticks, etc.) is forbidden without the agreement of a referee. Referees can inspect and ban every peripheral device, software, mass storage unit or setting at any time.

2.4. Game preparation

Please make sure, a match can be played without any interruptions. Arrangements between the Teams/Players have to be written down in the match comments.

3. Gamespecific rules

3.1. Matchmedia

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 his work because of bad match media names, penalty points can be assigned.

3.1.1. ESL Anticheat / Linesman

ESL Anti-Cheat is mandatory for all players to use for the full duration of all matches without exception. If a player cannot use Anti-Cheat then they are not allowed to take part in a match. For a missing or an incomplete Anti-Cheat file the player/team will be punished. Apart from this rule are all players which have evidence (screenshot of a bug)) that ESL Anti-Cheat stopped/crashed due to an error. The first time a player has no logout or no Linesman file, a warning will always be given, whether he can prove it was an error or not. Warnings for a missing logout and linesman are valid for 14 days. We only handle and warn a missing logout if they are reported within a protest. A match won’t be deleted if warnings have been given.

3.1.2. Screenshots (on servers without game integration)

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 end of the match. Screenshots must be uploaded in the following format: .jpg, .jpeg, .png, .bmp

3.1.2.1. Score screenshot

A screenshot of the scoreboard at the end of the match must be taken and uploaded to the match page within 24 hours. The screenshot must show the end result of the match.

3.1.2.2. Status screenshot

A status screenshot must be taken:

  • at the beginning of the match
  • in case of a server / player change
  • if a player reconnects

In order to take a status screenshot, you have to use the console command „status“. A missing status screenshot is no reason to open a protest.

3.1.3. Demos

It is mandatory for all players to record one point-of-view (POV) demo per map for the full duration of all matches without exceptions. A possible knife round is part of demo and has to be recorded. Possible overtimes have to be recorded as well. In general not working demos will be treated as missing demos, although the final decision is up to the admin. If the demo is incomplete, the admin will decide whether or not it will be treated as a missing demo. If a protest has been opened for a match, all match media must be kept for at least 14 days until after the protest is closed. In case of a match abort the aborting team loses any right for a demo. If the server crashes no automatic replay will be available. In this case players have to upload demos on admin request.

3.1.4. Requesting demos

3.1.4.1. On game integration servers

It’s not possible to request player ineye demos. Only the Anti Cheat team is allowed to request the ineye demo of an accused player if they deem it’s required. Failure to provide the demo will be punished with 6 pps (missing demo with cheat suspicion). The Anti Cheat team will nevertheless perform the analysis based on the Go TV demo.

3.1.4.2. On non game integration servers

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 the map, if more maps have been played. 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 report. This is possible as long as the other side did not yet fulfill 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 the demo request is wrong and has not been corrected (e.g. more demos than allowed were requested), the opponents do not have to upload any demos at all. If a player or a team illegally aborts the match, they lose their right to demand demos. It is not necessary to split the demo in two halves per Map. The request refers to one demo per map, so after a request the player have to upload the complete demo/map (one demo = one map of one player). Maximum amount of 4 demos can be requested Both sides should check the demo requests of a match after the 30 minutes have passed. The requested demos must be uploaded to the match page within 24 hours. Please check cup rules for special deadlines. If any demo is missing after 24 hours, you have to 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 the requested demos. If after this deadline the player(s) still have not uploaded their replay(s), 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, the player(s) and team will only receive 1 penalty point and the match stays rated.

3.1.4.3. Uploading demos

Demos have to be compressed into an archive (.zip, .rar, .7z). Apart from that all match media has to be uploaded to the ESL website (the match page). You are not allowed to upload your match media to your personal web space or any other kind of external hoster.

3.1.4.4. Editing demos

It is strictly forbidden to edit demos. If a replay has been manipulated, the admin team will decide what penalty is appropriate.

3.1.4.5. Accusation of cheating by timetable

If you want to accuse your opponent(s) of cheating, you need to hand in a timetable within 72 hours after the requested replay of the accused player has been uploaded. Instructions on how to do this can be found on this page. A timetable should be handed in along with the opening of the protest, so please make sure you have your timetable(s) ready when you open the protest. Nevertheless the timetable can still be handed in later (as long as it is within the 72h deadline) in case you did not do that along with the opening of the protest.

3.2. Settings

3.2.1. Player settings

3.2.1.1. Illegal scripts

In general, all scripts are illegal except for buy, toggle and demo scripts. Here are some examples for illegal scripts:

  • Jumpthrow
  • 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)
  • Bunny hop scripts
  • Stop sound scripts

Violations of this rule will lead to a warning the first time. If in team matches more than 1 player played with wrong client settings and they have been warned before already, the match will be deleted.

3.2.1.2. In-Game overlays

All In-Game overlays - provided by the game itself - except the following are forbidden:

  • cl_showpos 1
  • cl_showfps 1
  • net_graph 0/1 (nevertheless you are not allowed to abuse the net_graph to help you aiming, like in this screenshot)

3.2.1.3. Custom files

The HUD can be changed as long as no information is deleted or falsified which is available in the standard HUD. If you use a custom HUD, it has to be readable. If an admin is hindered in his work because of unreadable HUDs, penalty points could be assigned. Protests or support tickets because of unreadable HUDs will be rejected immediately.

Custom files are only allowed for your HUD and GUI.

Other custom files are forbidden, including custom models, changed textures or sounds (volume, soundscapes).

3.2.1.4. Illegal software and hardware tools

Changing the game graphics or textures with the help of video card 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. Tools that only display the FPS are legal.

You will be punished regardless of whether the changes have been made using external hardware or software and regardless of actively using them or not.

3.2.1.5. Color depth

The usage of a color depth of 16 bit is not allowed. Evidence of usage can only be given by ESL Anticheat. Trying to prove the use of 16 bit with screenshots is not allowed and protests about this will be rejected.

3.2.1.6. Content of the config folder

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 config files, penalty points (1-3) can be assigned. Protests and support tickets opened because of this rule are illegal and will be rejected.

3.2.1.7. Game account (on non game integration servers)

It is mandatory to register a CS:GO SteamID in your player profile. If a player plays with no or a wrong CS:GO game account, the player/team might be punished. If the CS:GO game account you played a match with is missing, but that same game account is already entered in your profile as VERSUS game account or CS/CSS game account, you will be warned at first. If you simply made a mistake while entering your game account (e.g. copy/paste error, last digit is missing), you will also be warned at first.

3.2.1.8. Game account (on game integration servers)

It is mandatory to register a CS:GO SteamID in your player profile otherwise you will be auto kicked from the server. If you get kicked from the server with the message "You are not a match participant", please open a protest to the match.

3.2.2. Server choice

The game integration servers you have to be used. If there are problems you can use your own server, but you have to come to an agreement with your opponent. The purpose of this rule is to determine which server is going to be used, if you cannot agree on one.

3.2.2.1. Usage of protected game servers

We recommend to play on a certified server. If one party is providing such a server, this server has to be used for the match.

3.2.2.2. Tickrate

If there is a server with 128 tickrate available, this one has to be chosen.

3.2.2.3. Tiebreaker

If both players/teams should have equal servers as defined previously in this rule, the match is going to be split over two servers. The server of the player/team which is on the left side in the match sheet will be used for the first half of the match. The other server for the second half of the match.

3.2.2.4. Ping

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.

3.2.3. Serversettings (on non gameintagration servers)

3.2.3.1. Server plugins

No server plugins except those listed below are allowed to be used:

  • VAC2

3.2.3.2. Config

You have to download the official ESL server config and upload them to your server in order to load the correct server config in-game. The server settings must be checked before the start of the match and may only be contested if they were changed during the match. A protest because of wrong server settings after the match started will be rejected!

3.2.3.3. sv_pure 1

The use of sv_pure 1 is mandatory in all matches. Please check this before the start of the match, as a protest will be rejected after the match has started.

3.3. Match rules

3.3.1. Nickname and clan tag

Each player has to use a nickname that is similar to the nickname entered in the ESL player sheet. You are not allowed to change your nickname in-game. Protests or support tickets because of a violation of this rule will be rejected.

If an admin's job is hindered because of wrong or difficult nicknames and/or clan tags, penalty points can be given to the players and teams.

3.3.2. Warmup

To start the match all contestants have to type .ready in the chat.

3.3.3. Number of players

A match can only start when the following minimum number of players are available:

  • 5on5: only 5on5 is allowed.

Only players who were in the team prior to match confirmation are allowed to play in the match.

This rules only relates to the number of players which have to be available at match start, in case a player should drop see rule Player drop.

3.3.4. Coaching

Coaching is possible on game integration servers. Only team members are allowed to coach on the server. ESL Anticheat is mandatory for coaches to use for the full duration of all matches without exception. If a coach cannot use ESL Anticheat then they are not allowed to coach in a match. The coach is not allowed to interfere in the match in any way. Abusing the coaching feature will be punished as unsportsmanlike behaviour.

3.4. During the match

3.4.1. Choice of side

A knife round will be played to determine the side. This is forced by the server. The winner of this knife round will choose the side by typing .stay or . switch in the chat.

3.4.2. Server crash

If the server crashes before three rounds have been completed (in a half), the server must be restarted and the half's score will be reset to 0-0.

If the server crashes after the third round has been completed, the half must be restarted with start money 2000 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 half continues with the following round. The start money has to be set to 800 again.

3.4.3. Player drop

If a player drops the server will be paused at the end of the current round (see rule Game pausing).

The waiting time for a dropped player is 15 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. In case the dropped player does not reconnect within 15 minutes and there should be no substitute available, the team must continue playing with one less player.

3.4.4. Change of players

Players can be changed at any time but the opposing team has to be informed in advance. If necessary the game can be paused (see rule Game pausing). This change may not take more than 5 minutes. After the waiting time the match can also be continued without the full team and the player can join in the running game. Changed players must be registered in the team with their CS:GO SteamID prior to the match.

3.4.5. Game intermissions

If the match is interrupted, the match is valuated up until that point. The match will be continued according to the following procedure (does not apply to Handgun competitions since the money is 1000 there):

  • The start money is set to 2000 for the remaining game time.
  • The team that lost the last round kills itself using the command “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 willfully 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'.

Only players who were in the team at the initial play-date are allowed to continue the game. New players have no permission to play the match, except the opponent teams grants it.

3.4.6. Game pausing

If you have a problem that prevents you from playing on, you are allowed to pause the game. You have to announce the reason before or immediately after you paused the game. Pausing the game without any reason will lead to penalty points (see Unsportsmanlike behaviour). If the problem can't be solved (max. 10 minutes pause time) see rule Game intermissions.

3.4.7. Overtime

Playing overtime is mandatory and will be forced by the server. The overtime will be played MR3 (maximum of 6 played rounds) with $10.000 start money. For the start of the overtime, teams will stay on the side which they played the previous half on, during half-time sites will be swapped. Teams will continue to play overtimes until a winner has been found.

3.5. Bugs and forbidden actions

3.5.1. Bomb

To plant the bomb in a way that it cannot be reached anymore is forbidden. Places that can be reached with the help of a team mate are allowed. Violating this rule will result in the deduction of 3 rounds.

3.5.2. Climbing

Climbing with the help of team mates is in general allowed. Not allowed are positions where textures disappear in walls or grounds if a special movement (e.g. a jump) is required.

3.5.3. Boosting, skywalking, sharking

Boosting through walls, ceilings or the ground, invisible pixels or surfaces, sky walking, map swimming, floating and sharking are all forbidden.

3.5.4. Grenades

Throwing grenades inside walls is not allowed. Throwing them above walls and roofs is allowed.

3.5.5. Self-kills

Self-kills by console in order to shorten the round time is strictly forbidden.

3.5.6. Negev

The usage of the Negev is forbidden.

3.5.7. Other

The use of bugs is in general not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary.

3.6. After the match

3.6.1. Right to write a support ticket/file a protest

Only players/teams involved in a match are allowed to write a support ticket or to file a protest. Players can open a protest up to 72h after match start.

3.6.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 match, you must definitely file a protest. You are not allowed to enter a result yourself. This can be penalized as a fake result.

3.7. Penalties

Rule violation Amount of Penalty Points
General
Fake result Player / Team: 4
Illegal config settings Player / Team: Warning / 2 per setting and default loss
Illegal script Player / Team: 1, 4 or 6 and default loss
Custom files Player / Team 2 and default loss
Wrong models Player: 3 - 6 and default loss / Team: 3
Wrong server settings Team: 2 - 4
Missing / incomplete demos Player / Team: 3 and match deletion
Missing / incomplete screenshot Player / Team: 1
Manipulation of Screenshots Player / Team: 6
Manipulation of demos Player / Team: 6
Missing / incomplete ESL Anticheat default loss in the played map
Missing / incomplete linesman logfile Player / Team: warning / 2
Missing match media with cheat suspicion Player / Team: 6 and default loss in the played map
Bug use Player / Team: 2 per use
Self-Kills Player / Team: 2 per match
Other Player / Team: Up to 4