R6: Siege (PC) 5on5 Bomb Community Cup 2017 Europe #100
Last change: 01.02.2020 07:15
These are the rules for the R6: Siege (PC) 5on5 Bomb Community Cup 2017 Europe #100. 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. Global R6:Siege Tournament Rules
- 1.1. Players
- 1.1.1. Eligibility
- 1.1.2. Requirements
- 1.1.3. Technical Issues
- 1.1.4. Forbidden on Consoles
- 1.1.5. Player Settings
- 1.2. Team rules
- 1.3. Tournament rules
- 1.3.1. Settings for the tournament
- 1.3.2. Map Veto and Hosting rights
- 1.3.3. Start of the last match
- 1.3.4. No show
- 1.3.5. Forfeit
- 1.3.6. Protests
- 1.3.7. Results
- 1.3.8. Add Result
- 1.3.9. Closed matches
- 1.3.10. Match media
- 1.3.11. Disqualification
- 1.4. Ingame
- 1.4.1. Player drops
- 1.4.2. Re-host
- 1.4.3. Pausing the game
- 1.4.4. Illegal Actions
- 184.108.40.206. Spawnkilling / Spawnpeaking
- 1.5. Casting
- 1.6. Cheating
- 2. Game settings
1. Global R6:Siege Tournament Rules
Any person that has a standing cheating ban by Ubisoft for Rainbow Six Siege is ineligible to participate in any ESL-run Rainbow Six leagues and tournaments that have prize funding by Ubisoft, or are an ESL-run qualification event to a Ubisoft-funded Rainbow Six league or tournament. This ineligibility will last long as Ubisoft upholds the cheating ban.
|Plattform||Kind of Gameaccount|
|Xbox One||Xbox Account|
|Playstation 4||PSN Online ID|
- All players need to enter their correct gameaccount associated to the plattform in their ESL profile before the start of the tournament.
1.1.3. Technical Issues
Players are responsible for their own hardware and internet connection. Matches will not be rescheduled because of technical issues or substitute a player. If a team can´t play with the amount of players which are written in the requirements then this will be resulted as forfeit.
Everyone is responsible to have a connection (ping) as good as possible for their team region and technical situation. Also, all downloads and other programs which are unnecessary for the match must be turned off. For abusing this rule, the team can be disqualified.
220.127.116.11. High Ping
The ping limit for an ESL match is 150 ms. If a player is over this value please try to do a re-host first, before a protest is opened. Be sure a dedicated server was created. In the case the player has still a ping over 150 ms and it´s not possible to play the match without problems, a protest can be opened. It only counts as high ping if the ping is continuously over 150 (same player)! By opening a protest due to high ping the match mustn´t be finished and the team must hand in at least three screenshots of the scoreboard which was taken in different time over two rounds (In action phase).
1.1.4. Forbidden on Consoles
Usage of a non-licensed controller is strictly prohibited, it will be penalized with 3 penalty points. Usage of all console keyboard adapters is strictly prohibited, it will be penalized with 6 penalty points. If a licensed controller has a macro/turbo/auto-fire option, it cannot be used during league play, otherwise it will be penalized with 6 penalty points.
1.1.5. Player Settings
18.104.22.168. Graphics drivers, or similar tools
Any modification or changing of the game using external graphics solutions or other 3rd party programs are strictly prohibited and may be punished under the cheating paragraph
Furthermore, it's forbidden to use all kinds of overlays which will show the usage rate of the system in any way in-game (e.g. Nvidia SLI display, Rivatuner Overlay). Overlays which will show only the frames per second (FPS) are not forbidden and can be used.
22.214.171.124. Custom Data
Any changes to sprites, skins, score boards, crosshairs are strictly disallowed, also only the official models are allowed. If a player plays with custom files (not models) or removed files that have been installed by the game, then this will be penalized with two penalty points per player. If a player plays with custom models, then this will be penalized with five 6 penalty points per player and the opponent of the match may request a rematch.
1.2. Team rules
Team rosters must consist of at least 5 players to participate in a tournament. All roster changes must be made prior the generation of the matches:
- In a single or double elimination tournament, this is the creation of the bracket
- In a Swiss tournament, this is the generation of the first SWISS round
Playing with different players and/or illegal ringers will be punished.
1.2.2. Substitute Players
It is only allowed to substitute a player before the match starts. If the match is started (picking operator and spawn points) all 5 players of a team must play the game till the end. It is possible to switch players in a Bo3 between the maps.
1.3. Tournament rules
1.3.1. Settings for the tournament
All players are expected to follow the given settings. Different agreements are not allowed.
1.3.2. Map Veto and Hosting rights
Map bans must be done via the map veto system on the matchpage.
The team with the higher seed (lower number in the bracket) gets the host right. The game must be hosted on a dedicated server. The dedicated server location must be settled by default (based on ping). Who is the lower and higher seed? Example: Seed Number
The Team who picked the Map in a Best of One can not choose the starting sides, the other Team can do that. During a Best of Three each can pick the sides of the Map picked by the other Team. Team A picks the Map and Team B can choose the starting sides on that one. Team B picks a map as well and Team A can choose the starting sides on this one.
1.3.3. Start of the last match
Any match that can start before 11:00 PM (CET for EU tournaments) must be played on the tournament day. Matches where one (or both) of the teams progress to after this deadline can be moved to the next day. (If only the finals and 3rd place matches has to be moved, exceptionally, they can be moved up to 3 days)
If both teams agree to play a match on the tournament day after 11:00 PM (CET for EU tournaments), they may of course play it. Matches which started after this time must be played till the end. However, in case of an issue, the admin team may not be available.
1.3.4. No show
If a contestant is not ready to play after 15 minutes, then they should be reported as a no show to an admin via protest ticket. The countdown starts from the moment both teams have progressed to the match, and not at the time stated in the match page.
If a contestant chooses to forfeit a match, they will forfeit any prizes and if possible will be replaced by their opponent in the previous round.
If a controversial situation occurs, whether or not it is described in this rulebook during a match, the team that has spotted it should immediately stop the match and inform the administrator about it. If the team does not stop the match and continues to play, will be taken as an acceptance of the situation. Because of that the team will lose all rights to file a protest concerning that situation after the game has ended. Protests must be made immediately, or they may be ignored depending on the circumstances.
Both teams are responsible to enter correct results on the ESL website. Therefore, both teams should take a screenshot at the end of the match, where we can see the correct result and they need to upload it after the match to the ESL website. If you have a conflict in the match, please open a protest, so the staff team can check the case and take a decision. The decision can also mean that both teams are disqualified, if there is not enough proof for either team to be the clear winner. Overall Results: Bo1: 1:0 or 0:1 Bo3: 2:0 2:1 1:2 and 0:2 Possible Overtime Score to win the map: 2:0 2:1 1:2 and 0:2
Example of a correct screenshot: Correct #1
1.3.8. Add Result
It is only allowed to add a score when the match is finished. Enter a team score before the match is finished to the match, this will be taken as unsportsmanlike behaviour and disqualification of the team. If a team lost a match, it will be automatically closed. If a team add a score to the match, the opponent has 15 minutes to accept the result or to open a protest ticket. The match will be closed automatically when the time expired.
1.3.9. Closed matches
Already closed matches stays closed, if there was a mistake by the teams. The teams haven´t a right to claim this via protest or support tickets, in exception the rule point MOSS file mandatory and Accusation of cheating by timetable. The admins have the right to reopen a match in certain cases.
1.3.10. 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.
- The match must be played as soon as possible (both teams added to the match).
- To keep the delay during the cup as low as possible we reserve the right to disqualify teams from the tournament. This will only be done in cases where a team shows no real effort to get a match done or is even obviously blocking. In severe cases this can even affect both teams.
- To prevent delaying the SWISS rounds, every match must be played in the period of 1:50 hours ( 90 minutes ). If the match takes longer then the period of time the match will be cut and a random default win given. Any abuse of this rule is considered to be deception and will result in punishment, up to and including disqualification of the Team.
1.4.1. Player drops
If a player drops from the server during a match, the round will continue uninterrupted until the end (Round starts with the first second of the preparation phase). After completion of the round, the player who disconnected will be allowed to re-join the server or a re-host can be requested. The match is considered “live” when the first round has started. At least the half of all players need to remain and the match need to be played until the match end and a winner is decided. If this isn’t possible due to connection issues, it will be considered as a forfeit in favour for the team who is able to have all players on the server.
Every team can re-host the server once in a match. If problems like this appear again, such as a player dropping out when the match has already been re-hosted, the team need to play the match with the remaining players to its conclusion. Any abuse of this rule will be considered as deception and will result in penalization and including disqualification of the team.
If a Team leaves the server without informing the opponent, the team risks forfeiting the match. Each user is responsible for his/her own Hardware.
In a re-hosted game, each player need to choose the same settings as they picked at the start of the original game. All ruling which isn’t explained in the previous point, the teams had to open a protest ticket. Only admins of the staff can decide, if the game will be complete restarted by a score 0:0.
1.4.3. Pausing the game
If a player pauses a game they must state the reason for the interruption and how long it will approximately take. The game can only be resumed by the player that paused the game after they asks their opponent if they are ready. The pause should not be longer than 10 minutes.
Violation of this rule are handled as unsportsmanlike behaviour and can lead to a re-game.
1.4.4. Illegal Actions
Any actions that result in an unfair advantage are illegal. This includes bug and glitch using of any kind. In a tournament by using any bug or glitch, the team got a warning, by the second time of using it, the team will be disqualified.
126.96.36.199. Spawnkilling / Spawnpeaking
- Killing somebody who already spawned, moved out of cover or is spawnrushed is considered spawnpeaking and will not be rated as glitching / bug using.
Casting an ESL match is only allowed with an ESL admin agreement. To get an agreement please write a Support ticket.
Observers are allowed only if both teams agree. Exception to these rules are ESL admins and people that are explicitly allowed to observe by an admin (e.g. shout casters or streamer). Under no conditions is it allowed to play with referee’s other those decided by an admin.
Teams should only allow observers they trust. It is not allowed to protest after a match to complain about observers that were allowed in the game.
1.5.2. Personal Streaming
Personal Streaming is always allowed if ESL TV is not casting a match. If ESL TV is casting a match, personal streaming is not allowed without an admin agreement. Personal Streaming of a match shown by ESL TV, without permission from an ESL admin, can lead into a disqualification of the team or ban of the streaming player in the tournament. The ESL advised to use a delay in the streams.
1.6.1. 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 match has been finished. Timetables must be prepared based on videos in full HD quality. 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 (if it is within the 72h deadline) in case you did not do that along with the opening of the protest. Accusation of cheating by timetable will not be executed during a tournament. All timetables which are not in the correct form will be directly declined.
188.8.131.52. Timetable structure
The timetable should contain following information:
Name and account link of the player In game nickname of the player you want to be checked Art, description or name of the suspected cheat Link and name of the video Specific times of the demo which look suspicious, along with a reason for each (e.g. why it cannot have been coincidence, luck, hearing or skill)
I have the suspicion that the player1 cheated against player2 because he was afraid to lose the match.
Player link: link to the player’s profile. In game nick: Mister Spock1337 Cheat: aimbot, flashhack and wallhack/ESP Demo link: link to download the demo from the matchsheet Demo name:
12:21 – I creep to the ramp and the player1 stays at the ramp too because he “sees” that I’m coming.
14:34 – I’m throwing a flash grenade to the entry of the hall and the player1 stands there, therefore he has to be blinded but he see everything and kills me immediately when I come out of the door.
15:01 – I creep in the anteroom of the radio room to the chippy, and the crosshair of the player 1 remains on my head
18:00 – The player1 stands on the ct base and looks up to the hall, I creep from the ramp to the ladder. All at once his crosshair moves to my head and then he shoots. He couldn’t hear me!
20:21 – I’m running in the hall and the crosshair of the player1 is locked at my head. Although I jump his crosshair is still on my head.
27:12 – The player1 sits on the hall and he is aiming at the entry of the hall. I’m coming out of the chippy (I creep out) and the crosshair of the player1 immediately is locked at my head. Unbelievable reaction!
30:12 - I throw another flash in front of the player1, but he is aiming unchecked at me.
2. Game settings
Matches have to be played with the following settings:
- All matches will be played with 5 players per team in a Bo1
- Playlist Type: Normal Mode
- Server Type: Dedicated Server
- Voice Chat: Team Only
- Time of the Day: Day
- HUD Settings: Pro League
2.2. MATCH SETTINGS
- Number of Bans: 4
- Ban Timer: 20
- Number of Rounds: 12
- Attacker/Defender Role swap: 6
- Overtime Rounds: 3
- Overtime Score Difference: 2
- Overtime Role Change: 1
- Objective Rotation Parameter: 2
- Objective Type Rotation: Rounds Played
- Attacker Unique Spawn: On
- Pick Phase Timer: 15
- 6TH Pick Phase: On
- 6TH Pick Phase Timer: 15
- Reveal Phase Timer: 5
- Damage Handicap: 100
- Friendly Fire Damage: 100
- Injured: 20
- Sprint: On
- Lean: On
- Death Replay: Off
2.3. GAME MODE: TDM BOMB
- Plant Duration: 7
- Defuse Duration: 7
- Fuse Time: 45
- Defuse Carrier Selection: On
- Preparation Phase Duration: 45
- Action Phase Duration: 180
- Nøkk and Warden are not allowed to be used!
- All other operators are allowed.
- Club House
- Kafe Dostoyevsky
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.