R6TM 2018/03/15

R6TM Rule Book

This Rulebook outlines the rules that should at all times be followed when participating in any R6TM events or matches. Failure to adhere to these rules may be penalized as outlined. It should be remembered that it is always the R6TM administration that has the last word, and that decisions that are not specifically supported, or detailed in this Rulebook, or even goes against this Rulebook may be accepted in extreme cases, to preserve fair play and sportsmanship. The MAIN idea behind R6TM is to be a place where players can come play in a competitive environment, where respect, self-improvement, and improvement of others are the most valued traits. We hope that as you use our services you have an enjoyable experience, and as staff we will do our best to provide a good experience for players like you.

1

TABLE OF CONTENTS 1. General 1.1. Rule Changes 1.2. Code of Conduct 1.3. Additional Agreements 2.

​Confidentiality Clauses ​2.1.​ Privacy Policy ​2.2.​ Confidentiality

​ 3.

Prize Money ​3.1. Prize Money Distribution ​3.2. Prize Deductions ​3.3. Withdrawal of Prize Money ​3.4. Transfer of Prize Money

​4.

Ban of Players ​4.1. Match Start ​4.2. No show ​4.3. Match Procedures ​4.4. Match Result 4.5. Punishments 4.6. Storage and keeping of Match Media ​4.7. Match Protests ​4.8. Match Protest Rules ​4.9. ​Admin Call Abuse

​ 5.

​Game Specific Rules ​5.1. Anti-Cheat ​5.2. Match Procedure ​5.3. Map pool ​5.4. Game hosting ​5.5. Team connection losses 5.6. ​Communication ​5.7. Custom Lobby Settings ​5.7.1. Game Settings ​5.7.2. Match Settings 5.7.3. ​Game mode: TDM BOMB ​5.8. Operators 5.8.1. ​Operator Bans ​5.9. Scoring ​5.10. Nickname Ingame ​5.11. Glitch/Bug Re-hosts due to Operators 5.12. ​Spawn Peeking/Spawn Killing ​5.13. Leaving the Server ​5.14. Rehost ​5.15. Continuing a Disrupted Game ​5.16. Overtime ​5.17. Technical Issues 5.17.1. ​ Reporting 2

​6.

​Graphics drivers, or similar tools 6.1. ​Custom Data ​6.2. ​Use of Bugs and Glitches

​7.

​ ther rules O ​7.1. ​Regional Limitations for Participants ​7.2. ​Home Country/Region ​7.3. ​Nicknames ​7.4. ​Game Accounts ​7.5. ​Legal player prohibitions ​7.6. ​Match Broadcasting

8.

​Other Infringements 8.1. ​ General ​8.2. Breach of Netiquette ​8.3. Insults ​8.4. Spamming ​8.5. Spamming In-game ​8.6. Unsportsmanlike Behaviour ​8.7. Misconduct ​8.8. Faking Match results ​8.9. Ringer/Faker ​8.10. Playing with Disallowed Player ​8.11. Misleading admins or players 8.12. Age Restrictions ​8.13. Cheating ​8.14. Legal

​9.

Copyright Notice

​10.

Appendix

​11.

Definitions

3

1.

​General 1.1.

Rule Changes 1.1.1. The administration reserves the right to amend, remove, or otherwise change the rules outlined in this Rulebook, without prior notice. R6TM administration also reserves the right to make judgment on cases that are not specified, supported, or detailed in this Rulebook, or to make judgments that even go against this Rulebook in extreme cases, to preserve fair play and sportsmanship.

1.2.

Code of Conduct

Ubisoft considers that all players must be able to compete in an Rainbow Six Siege respectful environment, and also expect all players to show good sportsmanship at all times. This code of conduct applies to anyone participating in an R6TM related event. Competition​ ​programs​ ​(including,​ ​but​ ​not​ ​limited​ ​to): ● PUG Matches ● Leagues ● R6TM Events Communication​ ​platforms​ ​(including,​ ​but​ ​not​ ​limited​ ​to): Ubisoft: ● Uplay ● In-game chat & voice chat ● Ubisoft forums ● All forms of Communication towards Ubisoft administration (verbal, emails, social medias, etc) R6TM: ● All forms of Communication towards R6TM administration including, but not limited to: match comments, match chat, protests and support tickets, Discord, face-it client & webchat. Face-It: ● All forms of Communication towards Face-It Staff, including, but not limited to: match comments, match chat, protests and support tickets, and face-it client interaction. Please note that this code of conduct is not limited to the environments above, as we expect all players to be respectful between themselves and also towards of the staff of the tournament organizers, Ubisoft, sponsors, partners, fans, etc. Any individuals not doing so, will have to face the chart below: INFRACTION SANCTIONS LEVEL​ ​1 A WARNING LEVEL​ ​2 A TIMED SUSPENSION LEVEL​ ​3 LONGER​ ​DURATION​ ​BAN

4

Depending​ ​on​ ​the​ ​circumstances​ ​and type​ ​of​ ​infraction the warnings reset at the end of each R6TM season. For second and subsequent offences, participants should expect far harsher sanctions (at least the minimum sanction described for the next offense level) and, in the cases of repeating Level 3 infractions, in all likelihood, a lifetime ban from all R6TM events. Please note that the judgement of the level of the sanction is at the discretion of the staff. R6TM reserves the rights to take the time to investigate the case when the code of conduct is not respected by an individual. Use the following link for more information on Ubisoft Live Services Agreement: https://rainbow6.ubisoft.com/siege/en-us/news/detail.aspx?c=tcm:152-249092-16&ct=tcm:148 -76770-32Xx We reserve the right to update or change this Code of Conduct at any time. See ​Section 8​ for more rules.

1.3.

Additional Agreements

R6TM is not responsible for any additional agreements, nor do they agree to enforce any such agreements made between individual Players or Players with Staff. R6TM highly discourages such agreements taking place, and such agreements that are contradicting R6TM’s Rulebook are under no circumstances allowed.

2.

Confidentiality Clauses 2.1.

Privacy Policy 2.1.1.

2.2.

R6TM’s Privacy Policy is laid out under the following link. https://docs.google.com/document/u/3/d/e/2PACX-1vQ7nkVDPhRkExn4Sa6h mqwmXlIE9C08_Iy8-4Ns6gdPFNhPWgS-nRxXvA2VgqhYpe8gJOprdxXQ91p K/pub

Confidentiality

The content of protests, support tickets, discussions or any other correspondence with officials and administrators are deemed strictly confidential. The publication of such material on private or social media channels (such as Twitter, Twitch, Facebook, Reddit, etc.) is prohibited without a written consent from R6TM Management. Breaking this rule will be punished severely.

3.

Prize Money 3.1.

Prize Money Distribution

TBD

3.2.

Prize Deductions

TBD

3.3.

Withdrawal of Prize Money

As long as the prize money for any R6TM events has not been paid out, administration reserves the right to cancel any pending payment if any evidence of fraud or foul play have been discovered. 5

3.4.

Transfer of Prize Money

TBD Prize money will be paid out to a single individual only.

4.

Ban of Players 4.1. Match Start 4.1.1. No Shows If a player does not show up within 15 minutes, send in a support ticket and an admin will cancel the match and players can requeue for a new one.

4.2.

Match Procedures 4.2.1. Match Result The result must be immediately added and confirmed by both parties within the client. A protest may still be made even after a match result has been confirmed. Players have 300 seconds (5 minutes) to confirm the match before it auto-closes.

4.3.

Punishments 4.3.1.

4.4.

Punishments are set out according to Face-It & R6TM Code of Conduct (See 1.2 Code of Conduct) 4.3.1.1.

For Face-It interactions use: https://support.faceit.com/hc/en-us/articles/208282375-FACEIT-Bann ing-Policy

4.3.1.2.

Our Hubs follow this format for punishments: ​3 minutes​ to a max of ​7 day​ bans from queues. With a permanent ban being the last punishment.

Storage and Keeping of Match Media

If a match was protested, any media must be stored for a minimum of ​4 ​days so adminstration can have time to properly review all evidence relating to a case.

4.5.

Match Protests

Protests must be done within 1 hour of the match being completed, or during. Also see 5.17.1 Reporting.

4.5.1.

Contents of a Protest

The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “They are cheaters“ will not do.

4.5.2.

Mid-Game/Match Protests

Protests done mid-game or before match start, will contact an admin. Once an admin responds, provide reasons in a orderly manner and administration will deal with it accordingly. If a controversial situation not described by this rulebook occurs during a match, the team that has spotted it should record it, immediately stop the match and inform the 6

administrator about it. If the team does not stop the match and continues to play, it is seen as an acceptance of the situation. Because of that the team loses all rights to file a protest concerning that situation after the game has ended.

4.6.

Admin Call Abuse

Anyone found abusing their right to contact an admin will immediately be subject to punishment according to the Code of Conduct.

5.

Game Specific Rules 5.1.

Anti-Cheat

TBD

5.2.

Match Procedure

Matches are played to a ​Best of 1 ​format

5.3.

Map Pool

The map pool includes the following maps: ● Bank ● Border ● Chalet ● Club House ● Coastline ● Consulate ● Kafe Dostoyevski ● Oregon ● Skyscraper

5.4.

Game Hosting

Administrator / Observer / Commentator is allowed to create a server. The game must be hosted on a dedicated server. The dedicated server location must be set to default (based on ping). For NA, CUS is used as default unless both teams are in agreement to change dedicated server location. For EU, ___ is used as a default unless both teams are in agreement to change dedicated server location.

5.5.

Team Connection Losses

A player has the ability to disconnect from a game three times, afterwards each disconnection after will be penalized in a way specified by staff. Penalizations are; up to including but not limited to warnings and temp bans. Each Player is responsible for his/her own Hardware and Software. This rule applies to all hardware, software and connections. I.E. (routers, computer components, power issues..etc). Matches will not be held for issues relating to player responsibilities outlined within this rule set.

7

R6TM reserves the right to hold or force a match to be played. Administration will determine through support ticket if issue warrants another course of action. R6TM ​HIGHLY​ suggests checking all software, hardware and the connection prior to queuing for a game, and if there are issues not to queue until they are addressed.

5.6.

Communication

R6TM requires all players participating in any events to be able to communicate with team members. Including, but not limited to Voice Chat and Discord use. Any players found that do not meet these requirements are subject to temporary suspension until issues have been addressed.

5.7.

Custom Lobby Settings

All players are subject to have these settings and playlists loaded and ready to go while participating in R6TM.

5.7.1.

Game Settings

● Time of the Day: Day ● HUD Settings: Pro League

5.7.2. ● ● ● ● ● ● ● ● ● ● ● ● ● ●

Match Settings

Match Settings: Number of Rounds: 10 Attacker/Defender role swap: 5 Overtime: 3 Overtime score difference: 2 Overtime role change: 1 Objective Rotation Parameter: 1 Attacker Unique Spawn: On Damage handicap: 100 Friendly fire damage: 100 Injured: 20 Sprint: On Lean: On Death Replay: Off

5.7.3.

Game Mode: TDM BOMB

● Plant duration: 7 ● Defuse duration: 7 ● Fuse time: 45 ● Preparation: 45 ● Action: 180

5.8.

Operators

All Operator and Maps are allowed, unless stated otherwise. Information about changes will be posted on Twitter, Discord, Client, and Website.

5.8.1.

Operator Bans

In R6TM Open there will be ​NO ​operator banning. Once a player has reached R6TM Main and up. Operator bans will be carried out using the client’s match room chat. 8

5.9.

Scoring

Match results are expected to be entered in as a 1:0 or 0:1 through the client.

5.10.

Nickname Ingame

Names should be similar to the registered Face-It name, anyone found using a completely different In-game will be subject to protest.

5.11.

Glitch/Bug Re-hosts due to Operators

To request a Rehost in case of a gadget from Hibana or Thermite. All 10 Players need to be alive and requested within the first Minute after the action phase. If the first Minute has passed or players have made no contact to request a Rehost, then any rehost after this, is not valid. Should a Team leave without confirmation to rehost, then the round is considered lost for the team that left. In cases where one side refuses to rehost due to invalid reasons, take the proper procedures (screenshots, recordings) and report them to a staff member using the support system. In the event a rehost is given, players must choose same operators/site that were selected. This rule extends to all operators, in the event an op glitch is present that is not knownAdmins will deal with the rehost according to the same rules if necessary. Admins reserve the right to invoke or modify this rule depending on circumstances of unforeseen glitch/bug. Abuse of this rule can lead to loss of rounds, forfeit of matches, or further punishments. Please see ​6.2​ ​Use​ ​of​ ​Bugs​ ​and​ ​Glitches

5.12.

Spawn Peeking/Spawn Killing

Follow the guidelines below to determine the difference and definition of spawn peeking/killing.

5.12.1.

Spawn-killing

Killing somebody instantly after spawning without any chance to react or move away will be rated as spawn-killing and ​will​ be rated as glitching/bug using.

5.12.2.

Spawn-peeking

Killing somebody who already spawned, moved out of cover or is spawn-rushed is considered spawn-peeking and ​will not​ be rated as glitching/bug using.

5.13.

Leaving the Server

All matches must be played to the end, failure to do so will be punished. A match is considered complete when one Team has reached five (5) out of eight (8) rounds during the regular match time or won two (2) out of the three (3) rounds during overtime.

5.14.

Rehost

In case of Technical or Game specific issues, Players are able to request a rehost directly within the In-Game chat, discord, or face-it client. Teams are allowed to request 3 Rehost’s per game, those requests need to have a specific reasons that cannot be disputed by players, and are not controversial to the rules set out in this rulebook. Requests for a Rehost without a reason will be denied. Once a rehost has been confirmed by both Teams. Teams will choose

9

the same Operators, Gadgets and pick the same Bomb site. Abusing the rehost rule can lead to a temporary suspension, or harsher punishment.

5.15.

Continuing a Disrupted Game

If a match is interrupted (e.g. server crash) then the match should be continued where it left off, by re-host. All fully completed rounds before the crash count towards the final score of the match. The Players can choose different loadouts and operators, but have to select the same bomb site and starting site as before. In the following rounds the bomb sites that have been already used before the restart cannot be used again.

5.15.1.

Disrupted Game Circumstances

Under certain circumstances, a disrupted game may be cancelled altogether depending on staff discretion.

5.16.

Overtime

In case of a draw after all eight (8) rounds have been played, an overtime will be played with best-of-three (bo3) system. The final score of a match with overtime is the official result for that match.

5.17.

Technical Issues

Players are responsible for their own technical issues (hardware/internet). Matches will be played once started hardware/internet issues or not. If problems arise, please open a match protest. Please see rule. More information about protecting yourself can be found in the DDoS Prevention guide.

5.17.1.

Reporting

It is highly encouraged that screenshots are taken for protests and any other issues. Who ever has a proper screenshot R6TM staff are more likely to rule in favor for.

6.

Graphics drivers, or similar tools 6.1. Custom Data Any changes to sprites, skins, scoreboards, crosshairs are strictly disallowed, 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 is punishable through the code of conduct.

6.2.

Use of Bugs and Glitches

The intentional use of any bugs, glitches, or errors in the game are punishable through the code of conduct, or cancellation of matches. Furthermore, it is up to the admins discretion whether or not the use of said bugs had an effect on the match, and whether or not he will award rounds, or the match to the opposing team, or to force a rematch. In extreme cases, the penalty for abusing bugs may be even higher.

7.

Other rules 7.1.

Regional Limitations for Participants

Players are limited to their home region, defaulted by ping. (Max 120) Any player found violating these rules will be punished through the code of conduct. 10

7.2.

Home Country/Region

A home country/region is the closest region to a player to achieve the lowest possible ping.

7.3.

Nicknames

Nicknames must not contain any inappropriate slang, racial slurs, homophobic terms, etc.

7.4.

Game Accounts

While participating in R6TM players are limited to only using ​one ​UPLAY account. Anyone found violating these rules are subject to punishment. The UPLAY account being used in R6TM must be similar in name to the one provided in the client. Special cases will be made at staff discretion.

7.5.

Legal player prohibitions

R6TM staff members are allowed to participate in R6TM events. If a protest occurs with an R6TM staff member in game, a different admin than the one playing in the match will come and deal with the protest. The R6TM staff member that played in the match cannot deal with any protests regarding their own match.

7.6.

Match Broadcasting

Anyone participating in R6TM is free to broadcast/stream the game. Streamers that wish to cast matches must first clear it with a staff member before continuing. Any streams that are casted on the official R6TM Twitch, becomes intellectual property of R6TM.

8.

Other Infringements 8.1. General When a player or team has broken one or more rules, this section is to be referred to for the appropriate penalty. Each rule is indexed with appropriate punishments included.

8.2.

Breach of Netiquette

Good sportsmanship is essential to R6TM and any breach of Netiquette will result in a punishment ranging from a warning, to a suspension to a ban. Common offenses are listed below. However you may be punished for offenses not explicitly listed at the discretion of an administrator.

8.3.

Insults

All insults in relation to R6TM will be issued a punishment ranging from a warning to a permanent ban depending on the severity and the frequency of infractions.

8.4.

Spamming

The excessive posting of senseless, harassing or offensive messages is regarded as spamming. Spamming on the website / discord will be punished depending on the nature and severity of the infraction.

8.5.

Spamming In-game

Using the in-game chat function to disrupt the flow of play will be punished depending on the nature and severity of the fraction. Acceptable uses of chat are: “gg” “gh” “hf” etc. or messages to communicate problems to the enemy team. Anything else may be considered as spam.

8.6.

Unsportsmanlike Behaviour 11

For an orderly and pleasant game it is essential that all players have a sportive and fair attitude. Breaches of this rule will be punished with a warning, followed by suspensions or in extreme cases, a permanent ban. The administration may assign penalties for not explicitly listed types of unsportsmanlike behaviour.

8.7.

Misconduct

The attempt to mislead admins or other players, using false information, or in any other way deceive other participants will be punished depending on the misconduct.

8.8.

Faking Match results

If a team is caught entering false match results into the match page, or in other ways trying to falsify the match result, they will be punished with a warning at first, with long suspensions following repeat infractions. When cheating is suspected and the match media has been faked, severe suspensions and even permanent bans will be issued.

8.9.

Ringer/Faker

Any Players involved in faking or ringing a Player will be immediately suspended. A team that uses a ringer/faker automatically loses all maps played on which the ringer/faker was used.

8.10.

Misleading admins or players

Any attempts to deceive opposing Players, admins, or anyone else related to R6TMs will result in an immediate suspension or a permanent ban depending on the severity of the infraction.

8.11.

Age Restrictions

There are no age restrictions on the hubs apart from the invite hub which is strictly 16+.

8.12.

Cheating

Examples of cheating include: Multi-hacks, Wallhack, Aimbot, Colored Models, No-Recoil, No-Flash and Sound changes. Any cheating will be dealt with via an immediate permanent ban.

8.13. TBD

Legal

9. TBA

Copyright Notice

10.

Definitions

Range of Validity If any provision of the Rulebook shall be invalid or impracticable in whole or in part this shall not affect the validity of the remaining part of this Rulebook. In lieu of the invalid or impracticable provision an appropriate provision shall apply which is nearest to the intent of to what would have been the intention in keeping with the meaning and purpose of the Rulebook.

12

Participants An R6TM participant is a player that is participating in an R6TM competition.

Hub Specific Rules Invite league requirements: Min. 10 matches played in R6TM, or a current Pro League status. + Level 10 on Face-It (Min. Age 16) Open Hub allows ANY age to play.

R6TM Officials Each player/team can contact the following officials for help with disputes or any issues with the client itself.

●

Admins Kornelius Med1cz Panky Reasons Sua Z1ronic Remorce SAANTAAA Shiizam YouSee

●

General Managers Saintscratch DatGuyJesus byTRCrazyman10123 BenWat

●

Regional Managers NA - Frostburn EU - Krazeehhh APAC - Nvendr

●

COO ​Trinity

●

CAO Interro

●

CEO KiXSTAr

Punishments 13

Possible R6TM punishments involve a warning, a suspension which prevents you from participating in R6TM play for a set amount of time. A permanent ban may be issued for severe rule infractions. These punishments will be issued by administrators and may not follow any progression of punishment depending on the severity of the infraction.

Country Restrictions R6TM currently supports all countries within the EU and NA regions.

14