VERSION 1.5 • October 2026
Tournament Rules (TR 1.5)
Guidelines for sanctioned tournaments, round timing, deck checks, and penalties.
Tr 1.5
001. The tournament rules exist to ensure anyone who attends a Riftbound organized play event has a fun, equitable, fair, safe and consistent experience. They aim to empower competitors and judges to work together to have mutual expectations and understandings.
101. Purpose: This document provides the frameworks and structures for Riftbound competitions by defining rules, responsibilities and procedures to be followed in all Riftbound competitions.
103.1. Attendees: All competitors AND all competition officials are expected to be responsible for following the rules as written and in the spirit in which they were written. This includes respecting all people at competitions.
103.2. Spectators: Spectators have their own set of responsibilities and expectations. See 204.8 for more information on spectators.
103.3. Penalties: Individuals who violate the frameworks and structures in this document are subject to penalties at the appropriate Organized Play Level (OPL). See 205 for more information on Organized Play Levels.
104.1. takes precedence for competitions.
104.2. vs. Official Local Language Translations: The English language version of this document will supersede any translation.
104.3. vs. Specific Event Addenda: In some cases, information in this document may be contradicted by alternate or additional policies or procedures in official addenda for specific competitions. In all such cases, those addenda take precedence.
105. Alteration: Riot Games or its official Riftbound partners reserve the right to alter this document, or any subsequent competition-specific addenda, at any time without prior notice.
201. Competition Types: Riftbound competitions come in three types.
201.1. Premier: A competition that is run by Riot Games or an official competition organizer and has a unique name and features.
201.2. Qualifier: Any competition where rewards include access or advantages for premier events. (Premier events can themselves be qualifiers.)
201.3. Local: Any competition that is neither premier nor qualifier.
202.1. Competition Formats:
202.1.b. Constructed: A constructed competition is one where players compete using decks they prepare beforehand.
202.1.c. See 600. for more information on Competition Formats.
202.2. Round Structures:
202.2.a.1. Power Pairing: When the final round of a swiss competition is paired in exact order of the current standings of the competition. For example: Seed 1 plays against seed 2, seed 3 plays against seed 4, etc.
202.3. Multiple: Some competitions may consist of multiple formats and/or structures within the same competition.
204. Competition Roles: Every attendee at a competition has at least one of the following roles.
204.1. Official roles: Roles 3-6 are considered competition officials for the purpose of this document.
204.1.a. Multiple: Any individual can act in any combination of official roles.
204.3. Competition Organizer (CO): The CO is responsible for all competition logistics, including:
204.3.a. Sanctioning the event by registering it with Riot Games or its official partners.
204.3.b. Providing a site for the event (the venue) that meets the competition’s needs, including providing sufficient space and amenities for the expected attendance.
204.3.c. Promoting the event before it begins.
204.3.d. Staffing the event with the necessary tournament officials and support.
204.3.e. Providing all materials necessary to operate the event.
204.3.f. Reporting the event results.
204.3.g. Maintaining records of the event results (by game and match) for a minimum period of 3 months for the purpose of appeals. See 413 for more information on appeals.
204.4. Head Judge: All sanctioned competitions require a Head Judge. The Head Judge is the final authority on competition rules and regulations, and their responsibilities include:
204.4.a. Ensuring that rules, procedures and regulations are followed.
204.4.b. Ensuring that all game or policy violations are dealt with and any appropriate corrective action taken.
204.4.c. Responding to floor judges who bring matters to their attention.deck
204.4.d. Coordinating and delegating responsibilities to floor judges as necessary.
204.4.e. Determining corrective action for errors or violations of the scorekeeper or floor judges.
204.4.f. The head judge has ultimate discretion if situations arise where the written rules are unclear or inadequate.
204.5. Floor Judge: Floor judges respond to players and spectators who have questions about rules and regulations, and/or need judgment on the same, and their responsibilities include:
204.5.a. Answering questions about rules, interactions among cards, providing Watcher wordings, or derived game state.
204.5.a.1.a. Inappropriate question: “If I attack and conquer this battlefield with my Tryndamere, Barbarian, will I score the winning point?”
204.5.a.1.b. Appropriate question: “Can point scoring abilities like Tryndamere’s score you the winning point?”
204.5.a.1.c. Judges may ask players to rephrase their questions to be appropriate where possible.
204.5.b. Provide rulings related to game and policy violations brought to their attention.
204.5.c. Intervening in games when they see an error occur to apply the appropriate fixes and penalties. This does not apply to Missed Trigger errors. See 702.2. For more information on Missed Trigger errors.
204.5.c.1. Judges should intervene AFTER an error occurs and should not attempt to prevent a player from erroring. This does not apply to proactively intervening in cases of Unsporting Conduct.
204.5.d. Assist with translation if able.
204.6. Scorekeeper: All sanctioned competitions require a scorekeeper. Scorekeepers are responsible for correct competition logistics as it relates to games and game records, including:
204.6.b. Generating standings in the competition before the last round of the competition (in Swiss competitions).
204.6.c. Generating standings in the competition after the last round of the competition (in Swiss competitions).
204.6.d. Solving scorekeeping problems with a-c above in conjunction with the Head Judge.
204.6.e. Reporting on the competition afterward and including all necessary data.
204.7. Player
204.7.b.1. Behaving respectfully to all attendees of the competition, including officials and spectators.
204.7.b.2. Maintaining clear game state.
204.7.b.3. Complying with all processes and procedures of the competition, including announcements and time limits.
204.7.b.5. Calling to the attention of a judge any error in their competition record as noted by the scorekeeper.
204.7.b.7. Obeying eligibility rules.
204.7.b.8. Familiarizing themselves with this document and any addenda.
204.7.b.9. Presenting themselves physically for the competition for its duration.
204.7.d. Individual members of a team in a team competition are each individually responsible for the above.
204.8. Spectator
204.8.c. Spectators have responsibilities, including:
204.8.c.2. At Casual and Competitive OPL, spectators can ask players to pause play while they alert a judge of a potential issue.
204.8.c.3. At Professional OPL, spectators can’t ask players to pause play, but they can still alert a judge of a potential issue.
204.8.d.3. At Professional OPL, spectators may not ask players to pause play while they call a matter to a judge’s attention.
205.1. The purpose of OPL is to define how strictly to treat deviations from rules, policy, and procedures as violations and what penalty those violations warrant.
205.2. Casual (low): Most competitions are casual and are focused on fun and social interaction, not rules enforcement.
205.2.b. document, but:
205.2.b.1. The focus of judges and competition officials is on education and sportsmanship.
205.2.b.2. There is no priority placed on technically precise play.
205.3. Competitive (high): These competitions have significant rewards, which may include invitations or advantages at the Professional level.
205.3.a. document.
205.4. Professional (high): These competitions have significant rewards and prestige.
205.4.a. document completely.
205.4.b. All attendees are expected to maintain the integrity of the competition and the highest standard of behavior and technically precise play.
206.1. Additional turns do not affect the round cycle.
301.1. Suspended.
301.2. A competition official in that same competition, unless the competition explicitly allows it (non-premier competitions only).
301.3. Specifically prohibited by Riot or official partner policy.
301.4. Under 13 years of age and do not have a parent’s or guardian’s permission.
301.5. Prohibited by law, the rules or policy of the Competition Organizer, or by the venue’s rules or policy.
301.6. Restricted by competition addenda regarding age, as long as those restrictions are messaged ahead of time (at low OPL).
302.1. Suspended.
303. If a competition official for an event participates in that event, it must be run at Casual OPL.
304. Owners of organizations that run premier competitions may not play in those competitions, even if otherwise allowed.
306. Employees of Riot and their families are subject to additional restrictions.
306.1. Family is defined here as any person living with or related to the relevant employee, but not themselves an employee.
306.2. All employees and their family are allowed to participate in local competitions.
306.2.a. If the reward is product or cash, the employee or family member may claim that part of the reward.
306.3. Employees must declare themselves to the CO.
306.4. The CO may decline to allow Riot employees to participate in the competition for any reason; if so, they must abide by this decision.
306.5. No Riot employee is allowed to play in premier or qualifier competitions.
306.6. Families of employees are allowed to play in premier or qualifier competitions, if they are otherwise eligible to compete.
401.1.a. The Head Judge may require deck registration at low OPL.
401.1.b. Even when a low OPL constructed event does not require deck registration, players are expected to use the same deck throughout the event unless given permission by the tournament organizer.
401.3. Once a decklist has been registered and delivered to a competition official, it can’t be changed.
401.4. In a constructed event, a player’s deck must be registered prior to the start of the first round of competition.
401.5. Other player’s decklists are normally considered private information. The head judge of an event may run that event or the final rounds of that event using an open decklist policy. In this case, all players’ decklists will be considered public information.
401.5.b. Typically, professional OPL competitions should be run with open decklists, but it is ultimately up to the discretion of the head judge regardless of the event level.
402.1. In a constructed event, players must use a Main Deck of exactly 40 cards (including a chosen champion), 1 Legend, 12 runes, and exactly 3 battlefields each with a unique name.
403.1. In certain competitions, players may have a group of additional cards (outside of their starting configuration) called a sideboard. See 600 for more information on sideboards based on competition formats.
403.4.b. In constructed formats, a player may not change their Runes, Legend, or Battlefields at any point after deck registration.
404.3. Games that end in a draw do not count toward this goal.
405.1. Prior to the start of each round, players must seek out information about their imminent match, opponent, and seating in the venue.
406.1. Process. Additionally:
406.1.a. In competitions where sideboards are allowed, players may exchange cards from their main deck and their sideboard after each game of a match. See 403 for more information on sideboards.
406.1.d. Each player must shuffle their Main Deck and their Rune Deck. See 421 for more information on shuffling.
406.1.f.2. At Professional OPL, this is required.
406.1.h. For competitions run using a “best of 1” format instead of a “best of 3” format, the head judge may opt to use the altered initial setup process listed below to closer mirror the “best of 3” experience:
406.1.h.3. Players use the Play First Rule listed below to determine the designated player. See 407 for more information on the Play First Rule.
406.1.h.5. Players then have the opportunity to sideboard as if they were in between games of a “best of 3” match. See 403 for more information on sideboards.
407.5. For alterations to this rule for 2v2, see 603.7.
408.4.c.3. If the point score of the current game is tied and the game score of the match is tied, players continue to play until the next point is scored. The player who scores that point wins the match. This does not remove normal scoring restrictions if the next point is the Final Point. See CR 469.1.a. for Final Point details.
409.1. In the course of determining standings, the scorekeeper might need to distinguish between two players with equal match records.
409.2. In these cases, the following tiebreakers should be applied in order:
409.3. If after all tiebreakers are applied, two players are still of equal standing in the competition, the scorekeeper should use a random method to break the tie.
410.3. Players can’t agree to concessions or draws in exchange for anything. See 704.5 for more information on bribery.
411.1. At high OPL, judges should perform deck checks during the course of the competition.
411.2. When deck checks are performed, at least 10% of all decks, chosen at random, should be checked during the course of the competition.
411.3. Random deck checks should occur at the start of a round, after players have randomized and presented their decks, but before opening hands are drawn and should verify all elements of the registered decks.
412.1. At any point during a match, a player may pause to flag a floor judge. See 204.4 for floor judge responsibilities.
413.2. At high OPL, the head judge may designate certain floor judges to be appeals judges, who are then empowered to hear and rule on appeals. In such cases, those judges must wear uniforms matching the head judge’s uniform.
414.3. Players who wish to drop must inform the scorekeeper before pairings for the next round of the competition are generated.
414.4. If a player doesn’t show up for their match, they are automatically dropped from the competition unless they report to the scorekeeper.
414.7. Players who have dropped may re-enter the competition before the start of the following round at the discretion of the head judge.
415.3. Scores must be tracked, displayed, and updated legibly in writing.
415.3.a. At low OPL, an electronic device, dice, or similar methods can be used to track score.
415.4.a. Resources being immediately spent need to be communicated, but do not need to be tracked in this way.
417.2. At low OPL, digital devices may take the place of written note sheets.
417.3. The head judge may further restrict or permit usage of electronic devices.
418.3. Spectators and players who are on camera during matches are responsible for behaving respectfully toward all participants.
418.4. Spectators are permitted to record matches using video capture, provided they do so without interfering with the match.
418.5. At Professional OPL, the head judge may consult video capture to help make rulings during a match.
419.1. A proxy is a stand-in, unofficial version of an actual Riftbound card.
419.2.a. The only exception is an official proxy issued by the head judge at their discretion to replace a card deemed unusable.
419.3. An alter is an official Riftbound card that has been modified in some way.
419.4.a. Modify or obscure the card name, Might/Might Bonus, or cost, or make the art unrecognizable.
419.4.b. Contain substantial strategic advice.
419.4.c. Contain offensive images or text.
419.6. The head judge of a competition is the final decider on whether a card is acceptable for a competition.
421.1. Decks must be made random at the start of each game, and whenever an instruction from cards or tournament officials require it.
421.2. Random is defined as a state where no player could have any information about the order or position of cards in any part of the deck.
421.5. Players must notify a judge if they believe their opponents’ deck has not been made sufficiently random. See 703.7 for more information on insufficient randomization.
422.2.b. Players may use a unique sleeve or additional layer to distinguish their Chosen Champion during game setup, but must change its sleeve to match their Main Deck if it would enter a zone whose information level is private or secret during gameplay. See CR 128. Privacy for information types.
422.6. At high OPL, using sleeves for the Main Deck, Rune Deck and Battlefields is a requirement. At low OPL, using sleeves can be required at the discretion of the head judge.
422.7.a. Have highly reflective backs.
422.7.b. Contain holographic patterns on the front or back.
423.2. Marked is defined as bearing something that makes it possible to identify the card without seeing its face.
424.2. Players are responsible for making reasonable effort to prevent secret information from being revealed accidentally. See CR 128. Privacy for information types.
424.4. At high OPL, players don’t need to inform opponents of accidentally revealed private information.
501.4. Players are required to treat other players, tournament officials, and spectators with respect.
501.5. In team events, communication between teammates is allowed and encouraged, but it must be done in a reasonably timely manner. See 703.2 for more information on Slow Play.
502.1. Cards have a level of privacy as specified in CR 128. Privacy. These apply to levels of information accessible to the players as well.
502.2.a. Derived information is a combination of public information and a player’s own skill or calculation.
502.3. Like cards, other relevant information about the game state can be public, derived, private, or secret.
502.4. The additional relevant public information includes:
502.4.c. Rune Pools and the number and quantity of resources in them.
502.4.e. A permanent’s current state, as distinct from its printed ones.
502.4.f. Spells and abilities on the Chain, their order, and play choices made for them.
502.4.g. Spells and abilities that resolved previously in the turn, and the sources of them are themselves public.
502.5. The additional relevant derived information includes:
502.5.a. Which public cards have been recycled.
502.5.b. The order of runes in a Rune Deck.
502.6. Players must acknowledge changes to public information that result from their cards and effects as those effects would have an observable impact on the game. See 506.3.e. for examples of observable impact.
502.6.a. As part of acknowledging changes to public information, the accountable player must communicate the change to all other players in an understandable and observable way. Examples include verbally announcing the change, physically indicating the change, or other means of communication understood and agreed upon by all players in the game.
502.10. Judges are encouraged to help players determine public information, but not derived information.
502.11. Players are not required to share private information, and may bluff in regards to their private information.
502.12. In 2v2, teammates may share Private information, including directly showing each other the
504.1. Complex series of game actions are sometimes shortcutted into out-of-order sequences, which are technically incorrect or imprecise, but arrive at the correct legal and understood game state.
Example
Drawing a card before channeling runes.
504.3. Players can’t shortcut out-of-order in a way that gives them information prematurely that might affect decisions later in that sequence.
504.4. When something is recycled, it must be immediately put on the bottom of the appropriate deck.
504.4.b. Failure to recycle in this way is a Communication Violation. See 703.5 for more information on Communication Violations.
505.1. Some sequences of actions can be repeated and are shortcutted as a loop.
505.2.a.1. Legal Loop: With enough Energy available, playing Grim Apothecary to a battlefield then using its trigger to return itself to hand 100 times.
505.2.a.2. Illegal Loop: A card reads "Recycle 3 cards from your trash: Ready a unit." A player with enough Energy available wants to use this to recycle 2 copies of Stupefy from their trash and 1 copy of Downstage Dramatics with an additional copy of Dramatics in hand, planning to play the Downstage Dramatics from hand, and then play each card as they draw it until there are 3 cards in the trash for them to recycle.
505.2.a.2.a. This is a non-deterministic loop because the order you play the cards is not guaranteed. If the loop only included copies of the same exact card draw spell, it would be deterministic.
505.2.b. Players can manually execute non-deterministic loops, but must do so in a timely fashion. Failure to do so is Slow Play. See 703.2 for more information on Slow Play.
505.9. If a sequence of actions is non-deterministic, it may not be shortcut and iterations must be performed manually.
505.11. Judges are the final arbiter of what constitutes a loop, or if choices are available to continue a loop when secret information is involved.
505.12. Players who try to opt-out of shortcutting or propose incorrect shortcutting to use up time are cheating. See 704.8 for more information about cheating.
505.13. Players cannot use loops to stall. When other actions are available, attempting to perform a loop that doesn’t change the game state is cheating. See 704.8 for more information about cheating.
506.1. Accountable Player: The player responsible for putting a triggered ability on the chain, as defined by the core rules. See CR 383. Triggered Abilities for more information on triggered abilities.
506.1.a. The accountable player for triggers sourced from battlefields depends on control of the battlefield and is not automatically the player who brought the battlefield to the game. See CR 190.6. For more information on battlefield abilities.
506.3.a. As part of acknowledging a trigger, the accountable player must communicate the trigger to all other players in an understandable and observable way. Examples include verbally announcing the trigger, physically indicating the trigger, or other means of communication understood and agreed upon by all players in the game.
506.3.c. Players ruled to be abusing this rule to intentionally forget mandatory triggers that they are the accountable player for will be penalized. See 702.2 for more information about missed triggers as a penalty.
506.3.d. For triggers that occur “At the start of each player’s first Beginning Phase”, the accountable player has the full duration of the turn in which the trigger occurs to acknowledge the trigger before it's considered forgotten, regardless of its observable impact. (Example cards: Obelisk of Power and The Arena’s Greatest.)
506.3.e. Examples of observable impact:
506.3.e.1. The trigger would change a point total. (Example card: Ahri, Alluring)
506.3.e.2. The trigger would change a rune total. (Example card: Startipped Peak)
506.3.e.3. The trigger would add a Buff token to a unit. (Example card: Sett, Brawler)
506.3.e.4. The trigger would impact combat or other game procedures. A card that reads “When you play a spell, give me +1 Might this turn.” does NOT have an immediate observable impact. It has an observable impact once it’s Might would be relevant. (Example card: Ravenbloom Student)
506.3.e.6. A trigger would cause a game object to be exhausted or readied. (Example card: Miss Fortune, Captain)
506.3.e.7. A trigger would cause a unit to move. (Example card: Stealthy Pursuer)
506.3.e.8. A player asks for public information that would be impacted by a trigger. See 502 for more information on public information.
506.3.e.10. A trigger would require a player to choose something, such as a unit or gear, even if there is only one legal choice. (Example: Abandoned Hall)
506.3.e.11. A trigger would cause a player to gain resources, such as XP or floating Power/Energy. (Example: Jhin, Murderous Artist)
506.3.e.12. A trigger would cause a card to change zones, such as a unit taking lethal damage. (Non-lethal damage is not an observable impact.)
506.4. A triggered ability that was forgotten never goes on the chain.
506.5. A triggered ability that was forgotten is still considered to have triggered for the purpose of non-optional “First time” or similarly restricted triggers.
507.2. Players that acquire secret or private information about a match in which a teammate is playing can’t communicate with that teammate for the remainder of that match. See CR
128. Privacy for information types.
508.4. Main Deck and trash must be together on either the left side or the right side of the board.
508.5. Rune Deck should be on the other side (right or left) of the board from the Main Deck.
508.6. Legend must be between nonrunes and Chosen Champion, and both legend and Chosen Champion must be together on either the left side or the right side of the board.
508.7. Each card or indicator that attaches to another card must be clearly associated with it physically.
508.9. Buffs must be represented by an object that unambiguously represents a buff in game terms.
508.10. Ready objects must be oriented facing the controller. Exhausted objects must be oriented at a 90 degree rotation to ready objects, either clockwise or counterclockwise, but all exhausted objects must be rotated consistently.
509.2. Once an action is communicated to an opponent, that action can’t generally be taken back.
509.4.a. The player wants to make a different decision for a spell or ability immediately after all choices have been made and communicated for putting it onto the chain.
Example
Example
A player exhausts two runes and plays Pouty Poro from hand to their base, then immediately decides they do not want to play it. They may return it to their hand and ready those two runes.
509.6. At high OPL, flexibility on gameplay decisions is not intended as a tool to allow players to reverse decisions after an opponent is required to indicate information that reveals that decision to be a tactical error.
509.6.b. Decisions made based on inaccurately represented public information may still be rewound at the discretion of the head judge. Inaccurately representing information to try to get a rewind is cheating.
509.7. Intentionally attempting to reverse decisions to gain information from an opponent is considered angle shooting. Players may not change their decisions based on an opponent’s physical reaction or as a response to an opponent starting to take a game action. See 704.4. for more information on angle shooting.
509.8. While changing decisions as described above is allowed, players must still maintain an appropriate pace of play. See 703.2 for more information on Slow Play.
601.1. Deck Construction
601.1.a. The rules for constructing a Riftbound deck are found in CR 101. Deck Construction, except where modified here below for the competition Constructed play format.
601.1.c.5. See 403 for more information about sideboards.
601.2. Card Legality
601.2.a. A card may only be included in a deck if it is from a set that is legal in that format or it has the same name as a card from a set that is legal in that format.
601.2.b. Until set release parity is reached, regional limitations on the legality of cards will be enforced according to the official product launch date in the region where an event is being held.
601.2.c. If an existing card is reprinted in a new set, but its collector number is not within the normal numbering of that set, it does not affect the card's format legality.
Example
A card with collector number 300/250 is not automatically legal within the standard format of that set.
601.2.d. If a card is banned in a specific format, that card may not be included in a deck.
601.2.d.1. Riftbound’s list of banned cards can be found here.
601.2.d.2.a. At Nexus Nights, if a player is playing a deck matching the exact contents of the preconstructed Jinx Champion Deck, they are allowed to use the banned cards in the deck, such as Fight or Flight, Scrapheap and Reaver’s Row. If the player makes any changes or adds a sideboard, they can no longer include the banned cards.
601.3. Standard
601.3.a. Standard is a format consisting of the most recent 5-8 sets.
601.3.b. Each Standard consists of the current year’s sets plus the previous year’s sets.
601.3.c. The current Standard consists of:
601.3.c.1. The Origins supplemental set contained in Proving Grounds (OGS)
601.3.c.2. Origins (OGN)
601.3.c.3. Spiritforged (SFD)
601.3.c.4. Unleashed (UNL)
601.3.c.5. Vendetta (Ven)
601.3.c.6. Radiance (RAD)
601.3.c.6.a. Release Date: October 23rd, 2026
602.1. Legality
602.1.a.1.a. For some limited competitions, players may be given additional promotional cards that the head judge will specify are not part of that player’s limited card pool and can’t be used for that event.
602.1.a.3. Players may utilize as many “blank” battlefields as they need for limited gameplay. See 602.3.d. below for more information on “blank” battlefields.
602.1.b. Even if a card is banned in constructed, it is legal to use in a limited deck as long as it is not also banned in that limited format.
602.2. Abnormal Product
602.2.a. There is no guarantee that the composition or distribution of any specific unopened product is correct.
602.2.c. The head judge may, at their discretion, replace atypical product in these cases.
602.3.b. At high OPL, players may not use electronic devices to take notes or as a strategic aid during deckbuilding. At low OPL, this can be allowed by the head judge.
602.3.c. At high OPL, players may not receive any outside assistance during deckbuilding. At low OPL, this can be allowed by the head judge.
602.3.d.1. “Blank” battlefields function as battlefields that do not have any rules text. Otherwise, they adhere to all other normal battlefield rules as defined in
602.3.d.2.a. At high OPL, “Blank” battlefields must be represented by any official Riftbound card, put in an opaque card sleeve with the cardback facing outwards.
602.3.e.4.a. Players may only use a specific copy of a battlefield once per match, but may use the same named battlefield as many times as they have copies of it in their provided card pool.
602.3.f. At low OPL, starting configuration registration is not required and players may freely change the composition of their starting deck and sideboard between games and matches unless otherwise specified by the head judge. Players may still only use a specific copy of a battlefield once per match, but may use the same named battlefield as many times as they have copies of it in their provided card pool.
602.4.a. Sealed
602.4.a.3.a. A sealed deck may have any Champion Unit that is included in its domain identity as its Chosen Champion, even one that does not have a champion tag that matches its Champion Legend (if it has one).
602.4.a.3.b. A sealed deck may contain any signature spells that are fully included in its domain identity, even if the deck does not include the corresponding champion.
Example
A sealed deck with a domain identity of Fury/Body/Order could use signature spells that are Fury/Order or Body/Order, but not signature spells that are Fury/Mind or Body/Chaos.
602.4.a.5.a. A player may opt not to use a Champion Legend or a Chosen Champion in their sealed deck even if they have one in their provided card pool.
602.4.a.5.b. If a player's deck is missing a Champion Legend and/or a Chosen Champion, they draw a card at the start of their first Beginning Phase each game. (If both are missing, they still only draw one card.)
602.4.a.6.a. The “Unique” keyword does not apply in sealed.
602.4.a.7. A sealed deck’s sideboard is every card provided to the player as part of the competition that isn’t used in their starting deck configuration, unless otherwise specified. See 403 for more information on sideboards.
602.4.a.7.a. Additionally, players may change their domain identity, Rune Deck, Legend, and Chosen Champion while sideboarding as long as the resulting deck still meets 602.4.a.2-602.4.a.4.
602.4.a.8.a. At high OPL, the head judge must require registration of the sealed pool prior to deck construction.
602.4.a.8.b. Each player receives the unopened product at their seat.
602.4.a.8.c. Players on one side of the table (A) open their product, observed by players on the other side (B).
602.4.a.8.d. Players verify that the product has the correct undamaged quantity of cards and rarity distribution. If a pack with an error is found, call a judge to replace the pack if possible.
602.4.a.8.e. Once all unopened product has been opened and observed by B, those cards are placed next to B.
602.4.a.8.f. Repeat the steps outlined in 602.4.8.c-e but with (B) opening and (A) observing.
602.4.a.8.g. Each player now sorts and registers the contents of the pool placed next to them.
602.4.a.8.h. After registration is complete, each player returns the pool and registration sheet to the other player.
602.4.a.8.i. Each player verifies that their own pool has been registered correctly.
602.4.a.8.j. Deck construction begins.
602.4.a.8.k. It’s recommended that players be given 20 minutes for deck registration and 30 minutes for deck construction. Deck construction can be increased to 45 minutes for low OPL events where players are experiencing the cards for the first time, such as pre-rift and release events.
602.4.a.8.l. The starting deck configuration and sideboard are registered on the same sheet as the total card pool.
602.4.a.9.a. Some competitions or portions of competitions provide preconstructed decks for players to use. These are considered sealed decks.
602.4.a.9.b. Players must use exactly the decks provided, except as modified by any addenda to the competition.
602.4.a.9.b.1. This may override the sealed deck construction rules above.
602.4.b. Draft
602.4.b.2.a. Each player opens one of their boosters, removes the Rune or token, then looks through the remaining contents to ensure there are thirteen undamaged cards in the pack with a correct rarity distribution.
602.4.b.2.a.1. Players can keep the Rune or token they opened.
602.4.b.2.a.2. If an opened pack has an error, players must call a judge to replace the pack if possible.
602.4.b.2.b. Once pack contents are verified, players will look through the cards in their pack and select one to draft to the top of a single unobscured facedown pile in front of them, then pass the remaining contents facedown to the player to their left. Players repeat this process with the cards passed to them until there are no cards remaining.
602.4.b.2.b.1. Once the first pack is completed, repeat
602.4.b.2.a. -602.4.b.2.b with the second pack, except passing cards to the right.
602.4.b.2.b.2. Once the second pack is completed, repeat
602.4.b.2.a. -602.4.b.2.b with the third pack, again passing cards to the left.
602.4.b.2.b.3. Once a card has been added to a player’s single facedown pile in front of them it is considered selected and can’t be returned to the pack.
602.4.b.2.b.4. Players must make a reasonable effort to conceal the front face of cards they have selected and cards in their current pack from other players.
602.4.b.2.c. Once this process is complete, each player should have 39 cards to use as their limited card pool.
602.4.b.2.d. At high OPL, players may not use electronic devices to take notes or as a strategic aid during drafting. At low OPL, this can be allowed by the head judge.
602.4.b.2.e. At high OPL, players may not receive any outside assistance during drafting. At low OPL, this can be allowed by the head judge.
602.4.b.2.f. At high OPL, during the draft process players may not reveal cards they have seen or selected, or openly discuss the draft. At low OPL, this can be allowed by the head judge.
602.4.b.2.g. During the draft process, players are not permitted to seek knowledge of cards fronts other drafters are viewing or have already selected through any means. Attempting to do so is cheating.
602.4.b.2.g.1. It is not cheating for a player to see card backs of cards other players are viewing or of cards players have added to the facedown pile in front of them.
602.4.b.2.h. At high OPL, players can’t look at the cards they have already drafted, except during intervals designated by a judge between packs. At low OPL, this is allowed at any time as long as the player is not holding other cards at the same time.
602.4.b.2.i. At professional OPL, drafts must be timed. At competitive OPL, drafts are timed at the discretion of the head judge. At casual OPL, drafts are untimed but players must draft at a reasonable pace.
602.4.b.4.a. A draft deck may have any Champion Unit that is included in its domain identity as its Chosen Champion, even one that does not have a champion tag that matches its Champion Legend (if it has one).
602.4.b.4.b. A draft deck may contain any signature spells that are fully included in its domain identity, even if the deck does not include the corresponding champion.
Example
A draft deck with a domain identity of Fury/Body/Order could use signature spells that are Fury/Order or Body/Order, but not signature spells that are Fury/Mind or Body/Chaos.
602.4.b.6.a. A player may opt not to use a Champion Legend or a Chosen Champion in their draft deck even if they have them among their drafted cards.
602.4.b.6.b. If a player's deck is missing a Champion Legend and/or a Chosen Champion, they draw a card at the start of their first Beginning Phase each game. (If both are missing, they still only draw one card.)
602.4.b.7.a. The “Unique” keyword does not apply in draft.
602.4.b.8. A draft deck’s sideboard is every card drafted by the player as part of the competition that isn’t used in their starting deck configuration, unless otherwise specified. See 403 for more information on sideboards.
602.4.b.8.a. Additionally, players may change their domain identity, Rune Deck, Legend, and Chosen Champion while sideboarding as long as the resulting deck still meets 602.4.b.3-602.4.b.5.
603.5. In some competitions, 2v2 teams may provide a team name to be displayed. Tournament officials may disallow a specific name for any reason.
603.6. A 2v2 competition can be either constructed or sealed. In sealed 2v2, the team shares a single product pool of 8 packs.
603.7.a. Turn order is as follows:
603.7.a.5. Return to the top of the order.
603.7.c. Once the appropriate step in the core rules process is reached, the team that earned the decision chooses where within the a.1-4 turn order play begins.
701.1. Philosophy
701.1.a. Errors are assumed to be committed unintentionally. If the judge believes it was intentional, it is cheating. See 704.8 for more information about cheating.
701.1.b. Judges are neutral arbiters and enforcers of policy and rules.
701.1.c. Judges should not stop errors from occurring. Instead they deal with errors that have occurred.
701.1.d. Judges should not intervene in games unless:
701.1.d.1. They believe a violation has occurred.
701.1.d.3. They observe a situation related to Unsporting Conduct.
701.1.e. Judges should model fair play, sporting conduct, and diplomatic behavior.
701.1.j. Penalties are issued and tracked to help judges understand intent over patterns of behavior.
701.1.k. Head judges and head judges ONLY may issue penalties outside of these guidelines. They have discretion to apply harsher penalties or investigate cheating if needed. See 704.8 for more information about cheating.
701.1.l. Judges are human and they make mistakes.
701.1.n. If a competition official makes a mistake and it results in a penalty applied to a player, the head judge can downgrade the penalty.
701.1.o. If a player acts on information given in error by a competition official, the head judge can rewind the game to account for it, even if there were no other errors.
701.2. Definitions of Penalties
701.2.a. Warning: An indication that an error occurred that provides a record of the error.
701.2.a.1. Time extensions should be granted if the total time to rule and correct is more than 1 minute.
701.2.d. Disqualification: A penalty issued for errors that damage the integrity of the competition or for severe misconduct.
701.2.d.4. Any attendee of a competition can be issued a disqualification, not just players. Being barred from the tournament venue may apply to disqualification at the head judge’s discretion.
701.2.d.5. This penalty can be issued by the head judge even without conclusive proof if the head judge determines the integrity of the competition has been compromised.
701.3. Applying Penalties
701.3.a. Penalties of Game Loss of higher (b-d) should be reported to the head judge.
701.3.c. Some errors include remedies beyond the scope of the base penalty, to protect competition officials from accusations of bias.
701.3.d. If a single error leads to multiple related penalties, judges should issue only the one with the most severe penalty.
701.4.b2. If judges can’t confidently determine the full randomized portion of a deck, they may shuffle as much of the deck as needed to perform a remedy.
701.4.c. Once the deck has been shuffled, any cards set aside in this way should be returned to their proper locations in the deck.
701.5. Rewinding
701.5.a. Some remedies allow rewinding the game state in extreme circumstances, where leaving the game in its current state is substantially worse than rewinding.
701.5.b. Some rewinds are simple; this means rewinding only the last action completed or one currently in progress.
701.5.c. For rewinds more complicated than a simple rewind, only the head judge or designated appeals judges (at high OPL) may authorize rewinding in this way.
701.5.d. To rewind:
701.5.d.1. Each individual action since the time of the error is reversed, starting with the most recent one.
701.5.d.2. Every action must be reversed in the correct sequence.
701.5.d.3. If the identity of a card involved in a rewind is non-public (e.g. a drawn card), a random card is chosen from possible candidates.
701.6. Investigations
701.6.b. Investigations may also occur at a judge's discretion following the application of a penalty if cheating is suspected. See 704.8 for more information about cheating.
702.1. Overview
702.1.a. A game play error is caused by incorrect and inaccurate play of the game that
702.1.b. Except for 702.17, repeated game play error [Warnings] can upgrade to [Game Loss].
702.1.b.4. Even if a player has not yet met the threshold to upgrade their penalties, a head judge may initiate a cheating investigation if they feel it is appropriate. See 704.8 for more information about cheating.
702.1.c. At low OPL, penalties should generally be less harsh and rewinds may be applied even if the erroring player gains an information advantage.
702.1.d.1. Judges should only upgrade these penalties when the advantage is obvious. If it is ambiguous, judges should not upgrade.
702.2.a. See 506 for definition of triggered abilities.
702.2.b. After the initial point at which a triggered ability is missed, any further errors related to that trigger are considered a General Error instead. See 702.16 for more information about General Errors.
702.2.d. A triggered ability is considered to have triggered even if it was subsequently missed. Effects that count or restrict the number of times that ability can trigger will count the missed one.
702.2.f. Remedies:
702.3.a. This does not apply to points that would be scored from card triggers such as Ahri, Alluring.
702.3.b. Remedies:
702.4.a. Remedies:
702.5.a. Cards being looked at from secret information such as a deck are added to a private information group while they are being looked at.
702.5.b. Once extra cards being looked at have touched a new private or secret group from their original source, they become part of that group. If the extra cards have not touched a new group, this is instead a Looking at Secret Information error. See
702.10. for more on Looking at Secret Information errors.
702.5.b.1. For example, if a player plays a Stacked Deck and adds a fourth card to the private set of cards they are looking at, it is Looking at Extra Cards. If they correctly look at the top three, but knock the top card of their Main Deck over without adding it to the private group, it is Looking at Secret Information.
702.5.c. Remedies:
702.5.c.1.a. If one or more of the cards has already been added to a new group of cards, the next opponent in turn order of the erroring player looks at that group and chooses the appropriate number of cards to return to the original group of cards being looked at. Then perform 702.5.c.1
702.6.b. Remedies:
702.6.b.1. If the additional runes have been used to pay for actions, rewind if possible. If rewinding is not possible, this is a General Error instead. See
702.15. for more information about General Errors.
702.6.b.2. If the additional runes are caught and no more than a full round cycle has passed, shuffle them appropriately into the rune deck.
702.6.b.2.a. If the specific runes can’t be identified, shuffle random runes instead.
702.7.b. Remedies:
702.8.b. Remedies:
702.8.b.1.a. If overpaying a cost was advantageous to the erroring player, this penalty is a [Warning] instead.
702.8.b.1.b. If overpaying a cost caused a result that would not otherwise have happened, it is a General Error. See 702.15 for more information about General Errors.
702.9.b. Remedies:
702.9.b.1. If possible, perform a simple rewind to before the card or ability was put on the chain.
702.9.b.2. If a simple rewind is not possible, correct the cost paid if possible.
702.9.b.2.a. If runes were incorrectly recycled as part of the cost, rewind if possible.
702.10. Looking at Secret Information [Warning]: A player looks at information that is not available to any player. See CR 128. Privacy for information types.
Example
If one of your opponents inappropriately flips over the top card of their deck, you do not receive a penalty if you see it.
702.10.b. Remedies:
702.10.b.1. If possible, take involved cards in the now-known secret information and re-randomize them with the original randomized source of appropriate cards to remove the information advantage.
702.10.b.2. If this is not possible, reveal the information to all players to remove the information advantage and instruct the players to continue playing.
702.11. Looking at Opponent Private Information [Warning]: A player accidentally looks at information that is private to their opponent. See CR 128. Privacy for information types.
Example
If one of your opponents inappropriately drops a card from their hand on the table, you do not receive a penalty if you see it.
702.11.b. Remedies:
702.11.b.1. The opponent whose private information it is may decide whether to take involved cards in the now-known private information and re-randomize them with the original randomized source of appropriate cards.
702.11.b.2. If they decide not to, instruct the players to proceed.
702.12.a. Drawing extra cards is also looking at extra cards, but only this error should be recorded.
702.12.b. Remedies:
702.12.b.1. If the error is caught before the extra cards drawn are added to a private set, shuffle them into the main deck appropriately to remove the information advantage.
702.12.b.2. If the error is caught when a player draws their opening hand during the start of game procedure and the player has not performed their mulligan yet, shuffle the extra cards into the main deck appropriately to remove the information advantage.
702.12.b.3. If the error is caught after the cards drawn are added to a private set and it is within the round cycle, the next opponent in turn order of the erroring player looks at that player’s hand and chooses the appropriate number of cards to shuffle into the main deck appropriately.
702.12.b.4. If at a later stage in the game it is determined a player has more cards in hand than they should, the remedy should be applied at this time.
Example
Hiding a card that does not have the Hidden keyword.
Example
Moving a hidden card from a battlefield to a hand or Main Deck illegally.
702.13.c. Remedies for illegally added cards:
702.13.c.1. If the error is caught by the erroring player immediately and before any additional game actions have been taken, return the card to the zone it came from and resume play.
702.13.c.2. If the error is caught after additional game actions have been taken but before any unknown cards have been added to the zone where the illegal card came from (such as a new card being drawn), return the illegal card to the zone it came from and replace it with a random card from that zone that is legal for the facedown zone and resume play.
702.13.c.2.a. If there is no available legal replacement, this penalty upgrades to [Game Loss].
702.13.c.2.b. If the error is caught after unknown cards have been added to the zone where the illegal card came from, this penalty upgrades to [Game Loss].
702.13.d. Remedies for illegally removed cards:
702.13.d.1. If the error is caught during the turn it occurred, and the card is easily identifiable and recoverable, return the card to the zone it came from and resume play.
702.13.d.2.a. If the error is caught on a later turn or the card is not easily identifiable and recoverable, this penalty upgrades to[Game Loss].
702.14.a. Remedies:
702.14.a.1. If a player recycled and replaced more than 2 cards during their mulligan, the next opponent in turn order of the erroring player looks at that player’s hand and may choose cards up to the number of extra cards mulliganed to have that player recycle and replace.
702.14.a.2. If this error is caught after gameplay has begun, instruct the players to proceed.
702.15.a. Remedies:
702.15.a.1. If it is still the turn the erroring player forgot to awaken, ready all game objects that should have been readied. If a game object being readied this way would put a trigger on the chain, it is not put on the chain instead.
702.15.a.2. If it is no longer the turn the erroring player forgot to awaken, leave game objects in their current state and proceed with play.
702.16. General Error [Warning]: Any other violation of the Rules of Riftbound.
702.16.a. This is a catch-all for any other game play error.
702.16.c. Remedies:
702.16.c.1. Rewind if possible.
702.16.c.2. Otherwise, instruct the players to continue playing.
702.17.b. Unlike other Game Play Errors, this error is primarily for tracking and never upgrades unless specifically instructed by the head judge.
703.1. Overview
703.1.b. Repeated tournament error [Warnings] can upgrade to [Game Loss].
703.1.b.4. Even if a player has not yet met the threshold to upgrade their penalties, a head judge may initiate a cheating investigation if they feel it is appropriate. See 704.8 for more information about cheating.
703.1.c. At low OPL, penalties should generally be less harsh and rewinds may be applied even if the erroring player gains an information advantage.
703.2.c. Intentionally stalling to gain an advantage is cheating. See 704.8 for more information about cheating.
Example
703.3.a.1. More or fewer cards than appropriate deck size. See 402 for more information about deck size.
703.3.a.2. Cards not legal in the format of the tournament.
703.3.b. Remedies:
703.3.b.3. If the cards required to correct a decklist cannot be acquired in a timely manner, the head judge can issue a proxy.
Example
703.4.a.4. A player’s deck is the incorrect deck size. See 402 for more information about deck size. (Examples: A player misplaced a card, a player forgot to shuffle their banished cards back into their deck between games, a player's deck has an extra card or is missing a card due to an effect like Possession from a previous game.)
703.4.b.1. At Casual OPL, if the error is caught after the start of the first player’s turn, instruct the erroring player to search the randomized portion of their main deck, their hand and sideboard for a legal chosen champion and place it in their chosen champion zone, then shuffle the randomized portion of their main deck. If the champion came from their hand, instruct them to draw a card.
703.4.b.1.a. If none are found, instruct players to continue playing with the erroring player’s chosen champion zone empty.
703.4.b.2. At Competitive OPL, if the error is caught after the start of the first player’s turn, a judge searches the randomized portion of the erroring player’s main deck and hand for a copy of their registered game one chosen champion and move it to their chosen champion zone, then shuffle the randomized portion of their main deck. If the champion came from their hand, instruct them to draw a card.
703.4.b.3. Purposely leaving your Chosen Champion zone empty during setup to gain an advantage is cheating. See 704.8 for more information about cheating.
703.4.c. Other Remedies:
703.4.c.2.a. In game one of a match a player realizes they forgot to restore their deck to a pre-sideboard state.
703.4.c.2.a.1. A judge can restore their deck to the appropriate state by returning cards to the main deck and sideboard as needed.
703.4.c.2.a.1.a. If sideboard cards are in the player's hand, they are replaced randomly by main deck cards that were incorrectly in the sideboard.
703.4.c.2.a.2. Shuffle the randomized portion of the main deck once this process is complete.
703.4.c.4. In either case, if restoring the deck to its correct state is not possible, the penalty is upgraded to [Game Loss].
Example
A player has two total copies of Traveling Merchant on their registered decklist, one in their Main Deck and one in their Sideboard. During game one of a match a player draws and plays one Traveling Merchant. On a later turn, they draw the second copy and realize they forgot to de-sideboard. At this point, since both Traveling Merchants have been drawn, restoring the deck is not possible as there is no easy 1 to 1 swap that can be made to restore the correct deck state.
703.4.a.5. upgrades this penalty to [Game Loss].
703.4.d. For all deck presentation errors, if the cards required to correct the deck cannot be acquired in a timely manner, the head judge can issue a proxy.
703.5.b. Remedies:
703.5.b.2. If any decisions were made based on incorrect communication, perform a rewind if possible.
703.6.d. Remedies
703.6.d.2. If the cards required to correct the deck cannot be acquired in a timely manner, the head judge can issue a proxy.
703.7.c. Remedies:
703.9.b. If the player receiving the advice solicited the advice, it is cheating. See 704.8 for more information about cheating.
703.9.d. Spectators providing advice may be barred from the tournament venue if the advice was given maliciously or knowingly.
703.9.e. It is not outside assistance to receive strategic advice from a teammate in the 2v2 format or in other team formats when specified.
703.9.g. Violating electronic devices policies will result in an outside assistance [Warning].
703.10.b. Playing other formats of Riftbound other than the one designated for the tournament with the appropriate decklist may not be used to determine a winner.
703.10.c. Offering or accepting such offers is considered improperly determining a winner.
703.10.e. Knowingly attempting to improperly determine a winner or attempting to goad an opponent into doing so is cheating. See 704.8 for more information about cheating.
704.1. Overview
704.1.a. Riftbound does not tolerate unsporting conduct. Tournament attendees and spectators must behave in a respectful and honorable manner.
704.1.b. If a player commits the same category of unsporting conduct [Warning] 2 or more times in the same event, the penalty is upgraded to [Game Loss] and may be further upgraded at the discretion of the head judge.
704.1.c. Infractions and penalties listed in this section aim to serve as general guidelines. Listed infractions are examples and are not exhaustive. All judges are empowered to escalate unsporting conduct issues and the head judge may apply any penalty they deem appropriate for unsporting conduct, up to and including [Disqualification].
704.2. Unsporting Minor [Warning]:
704.2.a.1. Disrespecting attendees or spectators
704.2.a.2. Bullying
704.2.a.3. Poor hygiene
704.2.a.4. Offensive play materials
704.3. Unsporting Major [Disqualification]:
704.3.a.1. Use of racial slurs
704.3.a.2. Physical violence or the threat of physical violence
704.3.a.3. Displaying aggression
704.3.a.4. Intentionally misgendering an event attendee
704.3.b. This penalty often comes with ejection from the venue at the discretion of tournament officials.
704.4.a.2. Taking actions quickly to prevent opponents from having time to have priority.
704.4.a.3. Promising a concession to garner additional information before making a different decision.
704.4.a.4. Attempting to mislead an opponent during gameplay based on cards that have rules errata.
704.4.a.5. Baiting an opponent into a rules violation.
704.4.a.6. Intentionally distracting an opponent to get them to miss their priority window.
704.4.a.7. Using sloppy play or game state representation to obscure strategy or information.
704.5. Bribery [Match Loss]: Tournament attendees and spectators may not bribe tournament players or tournament officials.
704.5.a. The outcome of tournament games may not be influenced by offers of out-of-game rewards or incentives.
704.5.a.1. Making or accepting such an offer is considered bribery.
704.5.a.2. Bribery applies to actions within a game, not just the final results.
704.5.b. Sharing prizes that have not yet been awarded in the current tournament does not constitute bribery. Players are permitted to make such agreements before or during their match, provided that the prize sharing is not offered or accepted in return for the outcome of a game or match, any in-game action, or a player dropping from the tournament.
704.5.c. It is not bribery when players in the single-elimination portion of a tournament offering only items such as cash, store credit, and/or unopened product, with the competition organizer’s permission, agree to divide the subsequent tournament prizes evenly. All players still in the tournament must agree to the arrangement.
704.5.d. It is not bribery when, in the final round of the single-elimination portion of a tournament, with the competition organizer’s permission, players mutually agree on a winner and how to divide the remaining prizes. In such cases, one player must agree to drop from the tournament. Prizes are then awarded based on each player’s final standing.
704.8. Cheating [Disqualification]: Riftbound does not tolerate cheating at any level of play.
704.8.a.2. If judges suspect a player is violating the rules knowingly or maliciously, the head judge may initiate an investigation to determine if cheating occurred.
704.8.b. Lying to a tournament official is cheating.
704.8.c. Intentionally neglecting to indicate a teammate's error is cheating.
704.8.d. The head judge has ultimate discretion to issue penalties for cheating.
705.1. Overview
705.1.a. All players participating in a premier or qualifier Riftbound competition are subject to this Disciplinary Code.
705.1.b. including this Disciplinary Code by: a) signing a contract or registration form in attached, b) clicking “Accept” when given the option to do so in an online registration process (or through a similar method of acceptance); or c) participating in any Regional Championship, Regional Qualifier, Showdown Series, or any equivalent events.
705.1.c. Players also accept and agree that the Competition Organizer and Riot Games have the right to:
705.1.c.1. Riftbound competition policies, the Riot Games Terms of Service, and any other competition-specific rules.
705.1.c.2. Investigate (or have a representative investigate) possible violations of any of the foregoing, and/or possible violations of applicable law.
705.1.c.3. Where appropriate, impose sanctions for violations of these Riftbound described below.
705.1.d. This Disciplinary Code applies globally anywhere Riftbound competitions are held. It may also apply to circumstances that occur outside of competition play entirely, if the alleged conduct could have an adverse impact on Riftbound competitions or in circumstances where the alleged conduct could be associated with Riot Games, Riot Games affiliates, Riot Games game titles, or other properties, in each case as determined by Riot Games.
705.2. Investigations of Rule Violations and Consequences
705.2.a. to the Competition Organizer or Competition Officials upon becoming aware of the violation. Reports must be made honestly and in good faith. Knowingly false, fabricated, or recklessly misleading allegations, coordinated complaints made in bad faith, or other abuses of the reporting process are prohibited and may result in sanctions.
705.2.b. Duty to Cooperate: Players are required to cooperate with the Competition Organizer, Riot Games, or designated representatives in any internal or external investigation that is conducted relating to a suspected violation of these Riftbound investigation, and a duty not to obstruct any such investigation, mislead investigators, withhold evidence, or abuse investigative processes.
705.2.c. Abiding to Decisions: Players must comply with all instructions, directions, decisions, or rulings, including any disciplinary measures or final decisions issued by the Competition Organizer or another entity recognized by Riot Games.
705.2.d. Consequences: At the Competition Organizer and/or Riot Games’ discretion, sanctions will be proportionate to the severity of the violation, taking into account any prior sanctions. Multiple sanctions may be applied for a single violation. application of one or more of the following disciplinary measures:
705.2.d.1. Warning (private or public)
705.2.d.2. Prize forfeiture and return of prizes (including previously awarded money and trophies)
705.2.d.3. Restrictions or bans on entering a venue
705.2.d.6. Forfeiture of points or rankings in any competitive ranking system
705.2.d.7. Suspension, disqualification, or ban from one or more Riftbound competitions
705.2.d.8. Riot game account suspension or termination
705.2.e. Interim Measures: The Competition Organizer and/or Riot Games may issue interim or provisional disciplinary measures pending the outcome of an investigation and until a decision on the merits is finalized. In circumstances where Competition Organizer and/or Riot Games may implement provisional measures, including the suspension of individuals involved.
705.2.f. Aggravating and Mitigating Circumstances: The type and extent of the disciplinary measures that may be imposed are based on the specific circumstances of each case, taking into account the seriousness of the offense as well as aggravating and mitigating circumstances. Repeated or multiple concurrent violations or infractions may be considered as aggravating circumstances and may be subject to escalating sanctions.
705.2.g. action, whether or not they were committed intentionally or as part of a joke, a stunt, or some form of social media performance.
705.2.h. Final Determinations. Competition Organizer’s and/or Riot Games’ determination as to the appropriate disciplinary action (or combination of disciplinary actions) will be final and binding.
705.2.i. Public Decisions. The Competition Organizer and/or Riot Games may make decisions public at their sole discretion, which may include certain facts, details, consequences, or other information arising in connection with a ruling or other disciplinary decision regarding a violation or alleged violation of these Riftbound
705.3. Conduct Rules
705.3.a. General Obligations: Players who participate in Riftbound competitions must at all times observe the highest standards of personal integrity and sporting conduct. Players are required to behave in a respectful manner in all of their interactions with other competitors, judges, competition officials, the media, sponsors, fans and other persons. Players must promptly comply with the decisions and instructions of Competition Officials (particularly of Judges) in a respectful and non-combative manner.
704. Engaging in unsporting conduct may additionally be subject to sanction under this Disciplinary Code.
705.3.c. Cheating. Cheating is prohibited. Enabling or assisting others to cheat is also prohibited.
705.3.e. Derogatory or Defamatory Statements and Hateful Acts. Players may not use words, gestures, digital or physical objects, or any other means to transmit, allow or facilitate messages or actions that insult, encourage hatred, undermine, or harm the integrity of a country, individual, or group of people. This includes contemptuous, discriminatory, or denigrating expressions based on race, skin color, ethnic, national, or social origin, gender, language, religion, political or other opinions, financial status, birth, sexual orientation, medical condition or history, or any other characteristic or status.
705.3.f. Vulgar or Provocative. Players may not use words, gestures, digital or physical objects, or any other means to transmit, allow or facilitate messages or actions that are obscene, vulgar, provocative, hateful, racist, insulting, threatening, abusive, libelous, slanderous, defamatory, or otherwise offensive or objectionable.
705.3.g. Harassment. Players may not engage in any form of harassment. Harassment is defined as unwelcome and unwanted behaviors that diminish, demean, or otherwise intimidate. This rule also prohibits sexual harassment, which is defined as any form of unwelcome sexual advances. Stalking, conduct that involves threats of violence (whether physically or online) and sharing personal information of another individual without permission are considered forms of harassment as is any conduct by an individual that incites or encourages abuse by others. All forms of harassment are prohibited, even if the behavior is not sufficiently severe or pervasive to constitute unlawful activity under applicable law.
705.3.h. Bullying and Abuse. Players may not engage in any form of bullying or physical or mental abuse. Bullying is defined as malicious conduct which an objective observer would consider hostile, offensive, and unrelated to legitimate competition, especially in circumstances where the person is perceived as vulnerable. Abuse is defined as treating a person with cruelty or violence (including physical altercation), especially if done repeatedly. Acting with reckless disregard for the potential negative impact of one’s actions is also considered a form of bullying and is prohibited.
705.3.i. Credible Threats. Players may not threaten others. A threat is defined as a statement of intention to commit an act of violence or take other hostile action against someone in retribution for something done or not done that could cause an objective observer to believe it will be carried out.
705.3.j. Match-fixing or Manipulation. Players may not match-fix or otherwise manipulate the outcome of any match or competition or request, encourage, or instruct others to manipulate it. Manipulation is defined as the unlawful or undue influence or alteration, directly or indirectly, by an act or an omission, of the course, result, or any other aspect of a match (i.e. spot-fixing) or a competition, irrespective of whether the behavior is committed for financial gain, sporting advantage, or any other purpose. For the purposes of this rule, manipulation also includes any attempt to manipulate, any action that creates the appearance of manipulation, and/or any behavior that could reasonably give rise to suspicions of manipulation, whether or not the manipulation is ultimately carried out or successful.
705.3.k. Retaliation. Players may not retaliate against anyone who reports a possible truthful information during an investigation. Retaliation (for example, threats, intimidation, harassment, employment actions, or any other form of reprisal) constitutes an independent violation, regardless of the outcome of the underlying report.
705.3.l. Violations of Law. Players are required to comply with all applicable laws at all times during their participation in Riftbound competitions. Players may not engage in (or encourage or solicit others to engage in) any illegal activity or behavior that is under investigation or has resulted in formal charges, whether or not a conviction has occurred, if such activity may bring Riot Games, the Competition Organizer, and/or a Riftbound competition into disrepute, negatively affect the authority, honor, and brand value of Riot Games, the Competition Organizer, and/or a Riftbound competition, or cause harm to the operation of a Riftbound competition.
705.3.m. Violations of Riot Games Terms of Service. Players are required to comply with the Riot Games Terms of Service and may face sanctions under this Disciplinary Code in addition to consequences established in the Riot Games Terms of Service.