Tournament Rules

Last Updated: 2026-07-16

# 000. Golden Rule

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.

# 100. Introduction

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.

102. Consistency: All Riftbound competitions must be run consistently regardless of their organizer or location to ensure equal treatment of players and interchangeability of events no matter the region or level.

103. Responsibility:

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. Precedence:

104.1. vs. Core Rules: In some cases, information in this document may contradict, or provide information not contained in, the Riftbound Core Rules. In all such cases, this document 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.

# 200. Definitions

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. Tournament Modes:

202.1. Competition Formats:

202.1.a. Limited: A limited competition is one where all product needed for play is provided during the competition.

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. Swiss: A competition or component of a competition where players are paired each round against players they haven't already played in the competition who, if possible, share the same current record.

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.2.b. Playoff: A competition or component of a competition where players are initially paired based on their standing and are subsequently eliminated by losses.

202.3. Multiple: Some competitions may consist of multiple formats and/or structures within the same competition.

203. Units of Play:

203.1. Game: A Riftbound game is defined in the Core Rules.

203.2. Match: A Riftbound match is defined in the Core Rules.

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.2. Judge roles: Roles 4-5 are considered judges for the purpose of this document.

204.2.a. Judges equally serve as both rules arbiters and ambassadors of a healthy and welcoming environment for all players.

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.

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. At high OPL, judges may not answer direct questions about the results of game actions a player has not yet taken. In these situations, players must ask questions about the rules. Examples:

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. Assist with translation if able.

204.5.d. Assist players in technically precise play (at low OPL). (This should generally not include strategic advice.)

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.a. Generating each round of the competition and necessary data to proceed with that round (e.g. match pairings).

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.a. Any non-official participant of the competition is a player.

204.7.b. Players have responsibilities, including:

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.4. Calling to the attention of a judge any rules or policy violation in their matches.

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.6. Reporting the result of their competition matches to an official in a timely manner.

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.c. Even if officials assist, the player remains ultimately responsible for the above.

204.7.d. Individual members of a team in a team competition are each individually responsible for the above.

204.7.d.1. Teammates are responsible for calling to the attention of a judge any rules or policy violations they observe in each others' matches.

204.7.e. Violations of the above responsibilities may be subject to penalties, suspension, or revocation of that player's eligibility.

204.8. Spectator

204.8.a. Any person present at a competition but not in one of the above roles is a spectator.

204.8.b. A player who is at a competition but not currently playing a match is also a spectator.

204.8.c. Spectators have responsibilities, including:

204.8.c.1. Remaining silent during matches and anywhere else in the venue where silence is required.

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. Spectator are prohibited from the following:

204.8.d.1. Personally indicating rules or policy violations to players.

204.8.d.2. Providing strategic advice to players.

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.

204.8.e. Players may request to a judge that a spectator not observe their match, at that judge's discretion.

204.8.e.1. Players can't request this for strategic reasons.

204.8.e.2. At non-local competitions, there may be additional rules for spectator behavior and presence.

204.8.f. Competition officials may instruct that a spectator not observe a match.

205. Organized Play Level (OPL): OPL is shorthand that helps communicate expectations to players and judges.

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.a. Players are expected to know most of the rules as defined in the Core Rules.

205.2.b. Players are responsible for playing according to the rules in the Core Rules and this 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.2.c. Generally, violations at this level have lower penalties which are covered below in section 700.

205.3. Competitive (high): These competitions have significant rewards, which may include invitations or advantages at the Professional level.

205.3.a. Players are expected to know the rules as defined in the Core Rules and this document.

205.3.b. All attendees are expected to maintain the integrity of the competition, while recognizing that some players may not be used to playing at the highest and most technically precise level of play.

205.3.c. Generally, violations at this level have stricter penalties which are covered below in section 700.

205.4. Professional (high): These competitions have significant rewards and prestige.

205.4.a. Players are expected to know the rules as defined in the Core Rules and this 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.

205.4.c. Generally, violations at this level have the strictest penalties which are covered below in section 700.

206. Round Cycle: A round cycle is the duration (in turns) that contains the standard turn for all players.

206.1. Additional turns do not affect the round cycle.

# 300. Eligibility

301. Anyone is eligible to participate as a player in Riftbound competitions, unless the player is:

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. Anyone is eligible to participate as a competition official, unless the player is:

302.1. Suspended.

302.2. A player in that same competition, unless the competition explicitly allows it (non-premier competitions only).

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.

305. Some competitions have additional criteria regarding eligibility for players or competition officials (for example, invitation-only competitions).

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.

# 400. Policies

401. Deck Registration

401.1. Players in competitions are required to register their decks and sideboards (if applicable to the format) at high OPL.

401.1.a. The Head Judge may require deck registration at low OPL.

401.2. A registered decklist must have a complete, unambiguous record of the player's Champion Legend, battlefields, Main Deck including Chosen Champion, Rune Deck, and sideboard (if applicable to the format).

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.a. In an open decklist competition, each round players are provided with their opponent's decklist to review at the start of the match and in between games of the match. Players may not review decklists during gameplay.

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. Deck Size

402.1. In a constructed event, players must register a Main Deck of exactly 40 cards (including a chosen champion), 1 Legend, 12 runes, and exactly 3 battlefields each with a unique name.

402.2. Otherwise, deck construction is defined in the Core Rules.

403. Sideboard

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.2. Sideboard size and contents are dictated by the competition format.

403.3. Limits on copies of named cards as defined by competition format apply to the combination of Main Deck and sideboard.

403.4. Players may use sideboard cards to modify their deck in between games of a match. Sideboard cards must be exchanged 1 for 1 with Main Deck cards.

403.4.a. During that time, a player may change their Chosen Champion to one from their sideboard or Main Deck that meets the deckbuilding rules of the competition format.

403.4.b. In constructed formats, a player may not change their Runes, Legend, or Battlefields at any point after deck registration.

403.4.c. After the sideboarding process, a player's Main Deck must meet deck size requirements dictated by the competition format.

403.5. Players may not use sideboard cards in the first game of a match.

403.6. Players may count the cards in their opponents' sideboards at any time.

403.7. A player may look at their own sideboard at any time, but must keep it distinguishable from other cards.

403.8. A player's deck and sideboard must be returned to their registered states before the first game of the next match.

403.9. If a match completely skips the first game due to a penalty, neither player may sideboard for the following game.

403.10. If a game ends in a draw, neither player may sideboard for the following game.

403.11. If a game restarts due to an in-game effect or due to corrective action by judges, the state of each player's deck and sideboard must remain the same in the restarted game.

404. Match

404.1. A match of Riftbound consists of a series of games that are played until one side has won a predetermined number of games.

404.2. Most matches of Riftbound are "best of 3," meaning the predetermined number of games to win is 2.

404.3. Games that end in a draw do not count toward this goal.

404.4. If the competition round ends (due to time limits) prior to any side achieving the goal, the winner of the match is the one who has won the most games.

404.5. If all sides have equal game wins, the match is a draw.

405. Start of Match Procedure

405.1. Prior to the start of each round, players must seek out information about their imminent match, opponent, and seating in the venue.

405.2. Players must arrive at their seats prior to the start of the round.

406. Start of Game Procedure

406.1. The setup process for a game of Riftbound is defined in the Core Rules. See CR 110 Setup 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.b. If a game ends in a draw, players must use the same battlefields for the following game.

406.1.c. Each player must shuffle their Main Deck and their Rune Deck. See 420 for more information on shuffling.

406.1.d. Each player must present their Main Deck, Rune Deck, and sideboard (if applicable to the format) to their opponents.

406.1.e. Each player may shuffle the Main Deck and Rune Deck of each of their opponents.

406.1.e.1. In team competitions, each player may shuffle the Main Deck and Rune Deck of one of their team's opponents.

406.1.e.2. At Professional OPL, this is required.

406.1.e.3. A player may request a judge shuffle their deck in lieu of an opponent, to be honored at judge discretion.

406.1.f. For the first game of a match, start of game procedures may be performed as soon as both players reach their assigned seat, even before the start of the round clock. Gameplay must wait for the round clock to begin.

406.1.g. 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.g.1. Each player separates their Champion Legend and places it in the Legend Zone.

406.1.g.2. Each player randomly selects one of their three Battlefields, and places it into the Battlefield Zone.

406.1.g.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.g.4. The designated player chooses if they would like to go first or last.

406.1.g.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.

406.1.g.6. After sideboarding is complete, each player separates their Chosen Champion and places it in the Champion Zone.

406.1.g.7. Players perform shuffling steps 406.1.c.-406.1.e.3. listed above, then proceed to CR 110 Setup Process.

407. Play First Rule

407.1. For the first game of a match, a designated player decides whether they wish to play first or last.

407.2. Any random method that is agreed upon by all players in the current game may be used to determine the designated player.

407.2.a. At high OPL, during playoff matches that occur following the end of Swiss rounds, the higher ranked player from the Swiss rounds is automatically the designated player for the first game of each match.

407.3. The player is designated and the choice of playing first is made during the Start of Game procedure. See CR 115 Determine turn order.

407.4. For games after the first game of a match, the loser of the previous game gets to choose if they play first or last. If the previous game was a draw, the starting play from the previous game is maintained.

407.5. For alterations to this rule for 2v2, see 603.7.

408. End of Match Procedure

408.1. A match is complete once a match result is recorded by players or a tournament official.

408.2. If the time limit for a competition round is reached before a winner is determined, the player whose turn it is finishes their turn.

408.2.a. After that player's turn is complete, three additional turns are played, and then the match ends.

408.2.b. If the game is incomplete at the end of the additional turns, a player is declared the winner of the game if they have a point lead of two or more. If no player has a point lead of two or more, the game is a draw.

408.2.c. Additional turns are untimed, but at professional OPL a judge must be present to ensure a reasonable pace of play.

408.2.d. If the players are between games when the round time ends, no new game is started.

408.3. The winner of a match is the first player who reaches the appropriate game win score.

408.3.a. If neither player has reached that score by the end of the end of match procedure, the player with more game wins wins the match.

408.3.b. If players are tied on game wins, the match is a draw.

408.4. Single elimination matches use untimed rounds so players can play their games to a natural conclusion. In the event that single elimination rounds must use a timer, the following altered End of Match Procedure can be used to determine a winner if time runs out:

408.4.a. When time is reached before a winner is determined, if players are in-between games, if a player has more game wins in the match they win the match. If game wins are tied, proceed to 408.4.d.

408.4.b. When time is reached before a winner is determined, if players are in the middle of a game, the player whose turn it is finishes their turn.

408.4.c. After that player's turn is complete, three additional turns are played. At the conclusion of those additional turns:

408.4.c.1. If a player has the most points in the current game, they win that game. Then, if a player has more game wins in the match, they win the match. If the game score is tied, proceed to 408.4.d.

408.4.c.2. If the point score of the current game is tied, but a player has the most game wins in the match, that player wins the match.

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.

408.4.d. If the game score is tied and a new game needs to be started, players start the new game and act as though time immediately runs out, beginning the process of 408.4.a., except with five additional turns following the first player's turn before moving into sudden death scoring as described in 408.4.c.3. if the point score is tied at the end of those turns.

409. Tiebreakers

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.2.a. The player with higher opponents' mean (average) match win percentage.

409.2.b. The player with higher game win percentage.

409.2.c. The player with higher opponents' mean (average) game win percentage.

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. Concessions and Intentional Draws

410.1. At any time before a game is completed, any player may concede that game or all players may mutually agree to draw it.

410.2. At any time before a match is completed, any player may concede that match or all players may mutually agree to draw it.

410.3. Players can't agree to concessions or draws in exchange for anything. See 704.5 for more information on bribery.

410.4. Players can't scout other match results before deciding to concede or draw their match and need to remain in their seats while their match is in progress.

410.5. If a player refuses to play, tournament officials should treat that as conceding the match.

411. Deck Checks

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. Deck checks for the players in a match should occur after players have randomized and presented their decks, but before opening hands are drawn.

411.3.a. If a deck check is performed within a match, judges should grant a time extension to that match sufficient to cover the logistical time needed to perform the check.

412. Judge Calls

412.1. At any point during a match, a player may pause to flag a floor judge. See 204.4 for floor judge responsibilities.

412.2. Time extensions should be granted if the total time of a judge call is more than 1 minute.

413. Appeals

413.1. If a player disagrees with a judge's ruling, they may appeal to the head judge.

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.

413.3. Players may not appeal before a full ruling is made by a judge.

413.4. Players may not appeal a ruling of an appeals judge or the head judge.

413.5. If a penalty is applied outside the scope of a competition, the appeals process should follow what's laid out on the official Riot Games website. [citation needed]

414. Dropping

414.1. Players may drop from a competition at any time.

414.2. If a player drops before the competition begins, they never participated in the competition.

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.5. Players who drop from limited format tournaments own the cards that they correctly have in their possession at the time of dropping, including unopened packs.

414.6. If a player drops from a competition after a top placement cut has been made, no player is advanced in replacement. The highest ranked remaining player receives a bye if the drop happens before pairings.

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.

414.8. Players can't re-enter a competition if they missed a portion where a deck construction activity was required.

414.9. Players can't re-enter a competition after a top placement cut.

415. Tracking Score & Resources

415.1. All players within a game are responsible for tracking all players' scores throughout the game.

415.2. Changes to score should be announced and acknowledged by all players.

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.3.b. If any player notices a score discrepancy, they must immediately make all players aware of it. If it can't be resolved easily by the players, a judge must be called.

415.4. Players must track their own resources such as XP and unspent Energy/Power they have floating. They are not required to be written down, but they must be represented in a way that is clear and understandable to all players, such as with dice or counters.

415.4.a. Resources being immediately spent need to be communicated, but do not need to be tracked in this way.

415.4.b. If any player notices a resource discrepancy, they must immediately make all players aware of it. If it can't be resolved easily by the players, a judge must be called.

416. Taking Notes

416.1. Players may take written notes during a match and refer to those notes during games in the same match.

416.2. At the beginning of each match, each player's written note sheet must be empty and visible to all opponents and tournament officials.

416.3. Players do not have to reveal their written notes to opponents. Judges may ask players to reveal and/or explain their notes.

416.4. Players may not refer to notes from outside the current match, including notes from previous matches, during games.

416.5. Between games, players may refer to notes they made prior to the match. They do not have to reveal these notes to opponents.

417. Electronic Devices

417.1. Players may use electronic devices during competitions, but can't use them during matches.

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. Coverage

418.1. Some competitions at high OPL use video capture of matches.

418.2. Certain events or portions of events may require players to appear on camera.

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.

418.6. Judges should never honor a player's request to consult video capture.

419. Proxies and Alters

419.1. A proxy is a stand-in, unofficial version of an actual Riftbound card.

419.2. Proxies are not allowed at competitions of any OPL.

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. Alters are allowed in competition only if the modifications do not:

419.4.a. Modify or obscure the card name or cost, or make the art unrecognizable.

419.4.b. Contain substantial strategic advice.

419.4.c. Contain offensive images or text.

419.5. By judge discretion, alters may not be allowed to be used during matches that are streamed or otherwise broadcast.

419.5.a. Players using altered cards are responsible for having official unaltered versions of those cards to use during gameplay that is streamed or otherwise broadcast if instructed by a judge.

419.5.b. When instructed, players must replace the altered versions with the official unaltered versions before gameplay begins for a match that is streamed or otherwise broadcast.

419.5.c. Alters containing material outside of Riot Games intellectual property may not be permitted during matches that are streamed or otherwise broadcast.

419.6. The head judge of a competition is the final decider on whether a card is acceptable for a competition.

420. Card Language

420.1. Players may include official Riftbound cards of any language in their decks during deckbuilding and gameplay.

420.2. A player may call a judge at any time to get the Watcher wording for any card in the language of their preference.

421. Shuffling

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.3. Shuffling by methodically placing cards into distinct piles (informally known as "pile shuffling") may be used as a method to count the deck, but can't solely be used to make a deck random.

421.4. When a deck is made random, it is presented to the player's opponent. This signals that the player believes their deck is legal and random.

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.

421.6. Players may shuffle their opponents' decks additionally.

421.7. Players must take care not to damage cards or sleeves through this process of shuffling, nor cause cards or sleeves to become marked.

421.8. When two or more cards are recycled to the player's Main Deck as part of a single action, the above procedures 1-7 should be followed for that group of cards to properly randomize them before recycling them.

422. Sleeves

422.1. Players may use plastic sleeves or other protective devices on their cards.

422.2. If a player chooses to do this, all such sleeves must be identical and all cards in a deck must be placed in sleeves in the same manner. Cards in decks must have the same number of layers and be the same orientation at all times.

422.2.a. It's suggested but not required that players use different sleeves for the different decks (Main, Rune).

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 during gameplay. See CR 128 Privacy for information types.

422.3. Sleeves must have opaque backs.

422.4. During a match, a player may request that a judge inspect an opponent's sleeves.

422.5. Judges may disallow any specific sleeve or the sleeves generally if they believe they are marked, worn, inappropriate, offensive, or otherwise interfere with shuffling or play.

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. At high OPL, sleeves must also not:

422.7.a. Have highly reflective backs.

422.7.b. Contain holographic patterns on the front or back.

423. Marked Cards

423.1. Players are responsible during competitions to make sure their cards and/or sleeves are not marked.

423.2. Marked is defined as bearing something that makes it possible to identify the card without seeing its face.

423.3. If cards are sleeved, they should be inspected for marking while in the sleeves.

423.4. Judges may ask players to remove sleeves or replace any specific sleeve at any time during a competition.

424. Display

424.1. During a match, the start of match procedure, and other relevant times during a competition, players must keep cards above the vertical level of the playing surface.

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.3. Players may reveal private information unless specifically prohibited by the Core Rules.

424.4. At high OPL, players don't need to inform opponents of accidentally revealed private information.

# 500. Communication

501. Requirements

501.1. Players are required to communicate honestly about the state of the game with their opponents.

501.2. Players are required to communicate honestly and completely with tournament officials.

501.3. Players are not required to assist their opponents in playing the game.

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. Information

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. In addition to these levels of information, some information is derived.

502.2.a. Derived information is a combination of public information and a player's own skill or calculation.

502.2.b. Players are not required to assist opponents in determining derived information.

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.a. The current turn player, phase, step, state of the turn, and who has priority and focus.

502.4.b. Rune Pools and the number and quantity of resources in them.

502.4.c. All players' current scores.

502.4.d. A permanent's current state, as distinct from its printed ones.

502.4.e. Spells and abilities on the Chain, their order, and play choices made for them.

502.4.f. 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.5.c. Consequences of actions that might happen in the future, such as a unit receiving a Might bonus from the Shield ability if a player attacks.

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.7. Players must answer honestly any questions regarding public information.

502.8. Players must not represent public or derived information incorrectly.

502.9. Players must point out discrepancies between announced and recorded public information.

502.10. Judges are encouraged to help players determine public information, but not derived information.

502.11. In 2v2, teammates may share Private information, including directly showing each other the cards in their hand as defined by 484.8.e. in the Core Rules.

503. Shortcuts

503.1. In competitions, players may take actions that skip parts of the technically precise play sequence without explicitly announcing that sequence.

503.2. The most common type of shortcut is skipping one or more parts of a turn, phase, or step to the mutual understanding of all involved players.

503.3. Players may request to use a new shortcut in a game but must be clear about the game state at the start and end of the shortcut.

503.4. Players may interrupt shortcuts by explaining where they want to intervene to take an action.

503.5. Players may interrupt their own shortcuts.

503.6. Players can't use shortcuts they haven't previously announced or modify existing shortcuts without announcement.

503.7. Players can't interrupt a shortcut with the intent to do nothing.

503.8. When resolving spells or abilities, players can't assume their opponents are using shortcuts without asking.

503.9. The following are common shortcuts for Riftbound competitions:

503.9.a. When a player channels runes or draws a card at the start of their turn, it is assumed that they have passed through the Beginning Phase.

503.9.b. When a player places a spell or ability on the chain, they are assumed to be passing priority unless they explicitly announce they intend to retain it.

503.9.c. When a player puts a spell or ability on the chain and announces choices for it that are normally made upon resolution, they must adhere to those choices unless their opponents react.

503.9.d. When a player asks about choices normally made upon resolution, they are assumed to be passing priority and allowing the spell or ability to resolve.

504. Sequencing

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.

504.1.a. Example: Drawing a card before channeling runes.

504.2. Players may ask their opponents to do these actions, or a subset of these actions, in the correct order so that they can react at the appropriate time.

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.a. Example: A player may not keep their recycled runes facedown on the board to track Energy.

504.4.b. Failure to recycle in this way is a Communication Violation. See 703.5 for more information on Communication Violations.

505. Loops

505.1. Some sequences of actions can be repeated and are shortcutted as a loop.

505.2. Players performing a loop must have each iteration of the loop be identical with no conditional actions.

505.3. To decide how to proceed with a loop, determine how many players are needed to maintain it (who must take actions or make decisions to sustain the loop):

505.3.a. No players

505.3.b. One player

505.3.c. Two or more players

505.4. For each maintaining player (if any), in turn order, that player chooses a number of iterations.

505.5. Each other player (if any), in turn order, may choose to agree to that number or choose a number of iterations after which they commit to taking action to break the loop or choose not to break the loop.

505.6. If no player chooses to break the loop and there were no maintaining players, the game ends in a draw.

505.7. Otherwise, the loop continues until the lowest number of iterations chosen, then that player either gains priority (if a maintaining player) or breaks the loop.

505.8. If a player intervenes to break a loop, they may choose to interrupt a partially completed iteration.

505.9. If a sequence of actions is non-deterministic, it may not be shortcut and iterations must be performed manually.

505.10. Some loops are maintained by decisions rather than actions. In these cases, apply 505.4-505.8 but with the player making a different decision rather than a different action.

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.

506. Triggered Abilities

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.2. Players are not required to notify other players of triggered abilities when they are not the accountable player, but may if they wish.

506.2.a. At low OPL, a player is not required to notify other players of triggered abilities when they are not the accountable player, but it is encouraged for sportsmanship and learning.

506.3. The accountable player must acknowledge their triggers by the time they would have an observable impact on the game. If they do not, they are forgotten.

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.b. A trigger is considered forgotten once its point of observable impact has been reached and a new game action is taken without the accountable player acknowledging the trigger.

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.5. A trigger would cause a player to draw or discard. (Example card: Traveling Merchant)

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.9. A player would be required to make a choice of whether or not to place an optional trigger on the chain. (Example: Overzealous Fan)

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. Teams in Separate Matches

507.1. Players may communicate with teammates at all times unless explicitly prohibited by the format rules.

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. Layout

508.1. In high OPL, players must arrange their cards according to the following rules, for clarity.

508.2. Runes must be closer to the player than nonrunes.

508.3. Nonrunes must be closer to the player's opponent than the player's runes.

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.8. Tokens must be represented by card objects that show all relevant information including ready state.

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. Gameplay Decisions

509.1. In competitions, players are responsible for considering options before taking actions.

509.2. Once an action is communicated to an opponent, that action can't generally be taken back.

509.3. At low OPL, a player can reverse their most recent action and make a different decision for that action (including not taking it at all) as long as no new action has been taken by either player. The change in decision does not need to be immediate.

509.4. At high OPL, a player can reverse their most recent action and make a different decision for that action (including not taking it at all) if no new action has been taken by either player and the following is true:

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:

509.4.a.1. A player plays Discipline indicating a unit. They immediately change their mind and choose a different unit, or choose not to play the Discipline at all.

509.4.b. The player wants to make a different decision for playing a unit or gear immediately after playing it to a location. Example:

509.4.b.1. A player plays Traveling Merchant to Reaver's Row. They immediately change their mind and choose to play it to their base instead, or choose not to play it at all.

509.4.c. The player wants to make a different decision immediately after making a choice such as moving a unit to a location or discarding a card. Example:

509.4.c.1. A player moves Pouty Poro to Void Gate. They immediately change their mind and choose to move an additional unit there as well, or they decide not to move at all.

509.4.d. The player wants to undo a decision to exhaust or recycle runes.

509.4.d.1. A player exhausts two Calm runes. Before taking a new game action, the player decides they do not want to exhaust them, and readies them.

509.5. 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.6. 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.

# 600. Competition Formats

601. Constructed

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.b. In competitions, a player's Main Deck must be exactly 40 cards.

601.1.c. In competitions where a sideboard is allowed:

601.1.c.1. A player's sideboard can include 10 or fewer cards.

601.1.c.2. A sideboard can consist only of valid Main Deck cards.

601.1.c.3. Limits on copies of named cards apply to the combination of main deck and sideboard.

601.1.c.4. A player may change their Chosen Champion to one from their sideboard or main deck that matches their Legend whenever sideboarding would be allowed.

601.1.c.5. See 403 for more information about sideboards.

601.1.d. In some competitions, the legal battlefields are different from the format-legal battlefields. If this is the case, it will be communicated to players via specific event addenda.

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.

601.2.c.1. 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. At low OPL, if a player is using the exact deck configuration of a preconstructed Riftbound deck product, they are allowed to play with cards on the banned list. For example:

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.5.a. Release Date: July 31st, 2026

602. Limited

602.1. Legality

602.1.a. A limited competition is one where all product needed for play is provided during the competition.

602.1.a.1. A card may only be included in a limited deck if it is provided to the player as part of the competition.

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.2. Players may utilize any number of the 6 basic Runes from any source, even if they are not in the player's provided card pool. 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.b. If a player notices a discrepancy between expected rarity or frequency of cards in a pack and what is opened, they must notify a judge.

602.2.c. The head judge may, at their discretion, replace atypical product in these cases.

602.2.d. In some cases, competition officials may allow players to provide their own product, but in such cases player-brought products must be pooled and distributed amongst participants randomly.

602.3. Building From a Limited Pool

602.3.a. 602.1.a. The rules for constructing a Riftbound deck are found in CR 101 Deck Construction, except where modified here below for limited formats.

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. Limited decks can use battlefields from their provided card pool or any number of "blank" battlefields. Players may opt to use "blank" battlefields in place of battlefields they received in their provided card pool.

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 the Core Rules.

602.3.d.2. At low OPL, "Blank" battlefields can be represented by anything agreed upon by all players in the game.

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. At high OPL, players must register a starting configuration from the card pool provided and must register the remaining contents of their card pool as their sideboard.

602.3.e.1. Players must use their registered starting configuration in the first game of each match.

602.3.e.2. Legend, Chosen Champion, and Rune deck composition must be registered as part of a player's starting configuration.

602.3.e.3. For "best of 1" competitions, players must register three battlefields to randomly select from during the start of game procedure, including any "blank" battlefields they wish to use.

602.3.e.4. For "best of 3" competitions, players may select any battlefield from their card pool or a "blank" battlefield during the start of game procedure.

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.3.g. For card pool generation and deck construction rules specific to each limited format, see Limited Formats below.

602.4. Limited Formats

602.4.a. Sealed

602.4.a.1. Sealed is a limited format where players are each provided with 6 unopened Riftbound booster packs to open and use to construct their deck.

602.4.a.2. Main Decks for sealed decks must be at least 25 cards, but can be more.

602.4.a.3. The domain identity of a sealed deck is any three domains, or any domain plus the domains of the deck's Champion Legend.

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.

602.4.a.3.b.1. 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.4. Players may only include Runes from any source in their Rune Deck that match the domain identity of their sealed deck.

602.4.a.5. A sealed deck is still legal if it has no Champion Legend or Chosen Champion.

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. The normal restrictions on quantities of named or signature cards do not apply. For example, a player may use 10 Pouty Poro in their Main Deck if they received them in the provided card pool.

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. Sealed Pool Registration & Deck Construction

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. Preconstructed Decks in Sealed Competitions

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.1. Draft is a limited format where players are each provided with 3 unopened Riftbound booster packs to open and draft amongst other players.

602.4.b.2. Draft groups consist of as close to eight players as possible, seated randomly around a table. Draft process is as follows:

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.3. Main Decks for draft decks must be at least 20 cards, but can be more.

602.4.b.4. The domain identity of a draft deck is any three domains, or any domain plus the domains of the deck's Champion Legend.

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.

602.4.b.4.b.1. 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.5. Players may only include Runes from any source in their Rune Deck that match the domain identity of their draft deck.

602.4.b.6. A draft deck is still legal if it has no Champion Legend or Chosen Champion.

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. The normal restrictions on quantities of named or signature cards do not apply. For example, a player may use 10 Pouty Poro in their Main Deck if they selected them during the draft.

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. 2v2

603.1. A 2v2 team consists of 2 players who enter a competition together and register together as a team to play congruently in a single match as described in the Core Rules.

603.2. Each player must provide their individual registration information to enter the competition.

603.2.a. When registering, teams must specify an ordering for the players on their team for seating purposes by indicating an A player and a B player.

603.3. If a player drops from a competition, their entire team is dropped.

603.4. If a player is disqualified from a competition, their entire team is disqualified.

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. During matches, teammates sit next to each other in their registered AB order. The setup process for a game of Riftbound is defined in the Core Rules, with these additional exceptions for 2v2:

603.7.a. Turn order is as follows:

603.7.a.1. The first team's A player.

603.7.a.2. The second team's A player.

603.7.a.3. The first team's B player.

603.7.a.4. The second team's B player.

603.7.a.5. Return to the top of the order.

603.7.b. A random method is used to decide which team selects the starting player.

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.

603.7.c.1. For games after the first game of a match, the losing team of the previous game gets to choose who plays first. If the previous game was a draw, the turn order from the previous game is maintained.

604. Event and Round Time Limits

604.1. It's recommended that players be given 60 minutes for rounds of play in the Swiss portion of a competitive event.

604.2. It is strongly recommended that single elimination matches use untimed rounds so players can play their games to a natural conclusion. If single elimination rounds must be timed, see 408.4. for an altered End of Match procedure.

604.2.a. Players are still expected to play at a reasonable pace. See 703.2 the Slow Play penalty.

# 700. Enforcement and Penalties

701. General

701.1	Philosophy
701.2	Definitions of Penalties
701.3	Applying Penalties
701.4	Shuffling
701.5	Rewinding
701.6	Investigations

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.

This is a point that really deserves to be highlighted. The vast majority of errors are unintentional and not cheating. Don't just blindly assume malice.

Some things to look for to make this distinction:

How advantageous was the error? (small incremental or game winning)

How easy is it to make the error?

Did they need to do this now or risk losing?

701.1.a.1. Players attempting to abuse error remedies to receive advantages are 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.

If we see a player about to make an error and we say something in an effort to prevent that, we can easily end up in a situation where we've accidentally provided them outside assistance. As described below, we shouldn't be interjecting ourselves until we've been asked to or until we see something that needs to be fixed.

701.1.d. Judges should not intervene in games unless:

701.1.d.1. They believe a violation has occurred.

701.1.d.2. A player requested assistance.

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.f. Judges should not account for a player's history or skill when determining whether errors occurred.

701.1.g. Judges may take into account a player's history or skill when investigating.

Whether a player is a seasoned veteran or new to the game or competitive scene does not change whether or not they have broken the rules of the game. However, when a player claims they did not know the rule that they broke, we are allowed to believe the new player and cast doubt on the seasoned veteran when deciding if the violation was intentional.

701.1.h. Penalties are designed to educate players on mistakes and encourage them not to make them in the future.

As judges versed in rules and tournament, we understand the severity and impacts to match and tournament integrity implicated by some errors and violations a player can commit. Players, conversely, often do not. However, players do understand that being issued a [Game Loss] is a worse outcome for them than being issued a [Warning], and they will make a greater effort to avoid the former.

701.1.i. Penalties are also designed to deter other players from similar errors.

Penalties also serve to function as a safety net in case we miss something. As judges are neither omnipresent nor omniscient, we cannot catch every instance of Cheating. Harsher penalties for more abusable situations change the risk/reward/cost evaluation to potentially nefarious players and protect the rest of the tournament from the damage they can cause if we do not detect intentionally malicious behavior.

701.1.j. Penalties are issued and tracked to help judges understand intent over patterns of behavior.

Penalties are tracked throughout an event not only because of the potential for upgrading, but also to help us detect a pattern. If we see the same player is consistently receiving penalties for the same or similar circumstances, it communicates to us the need to pay attention for potential Cheating or education.

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.m. If a judge recognizes their own mistakes, they should acknowledge them and correct them if possible.

Every judge will make mistakes and give a wrong ruling or incorrectly give a player a penalty they should not have received. This is part of why we have the process of appealing to the head judge at events with multiple judges.

If you make a mistake during an event, and you realize that mistake during the event, you should let the head judge know if you are not the head judge. If you gave a player a penalty in error, that penalty needs to be reversed if possible. You should also try to find those players to own up to it and let them know what the correct ruling should have been. This prevents them from acting on your previous ruling and committing misplays or errors in the future.

If you realize the mistake after the event, and you know and have regular contact with the players involved, it is still a good idea to own up to it and let them know what the correct ruling should have been.

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.

These are typically going to be served for small easy to make infractions. The game rules and tournament rules are complicated; this is why we get hired as expert judges. It wouldn't make sense to overly penalize a player for not perfectly computing the entire ruleset while trying to play a game.

701.2.a.1. Time extensions should be granted if the total time to rule and correct is more than 1 minute.

701.2.b. Game Loss: A game loss causes the erroring player and any of their teammates to concede the game. If this does not result in a winner, remaining players continue the game.

Game losses serve to negate situations where major unfixable advantage has occurred. Continuing that game would not make sense in terms of fairness so we end it and start anew from a fully even state.

These also serve as the first line of upgrade. The upgrades apply as a player has continually made errors that may have created advantages and we want to offset the advantage that has been occurring with this penalty.

701.2.b.1. Game losses are applied immediately if the game is ongoing, or to the player's next game in the competition if it is not.

701.2.b.2. If a player would receive multiple game losses at the same time, they only receive one.

701.2.b.3. If all players in a match receive a game loss simultaneously, the current game ends in a draw. All game losses are recorded but do not affect the match score.

701.2.c. Match Loss: A severe penalty that's issued when the entire match has been compromised by the error.

Match losses mean something *severe* has happened. Most commonly, we have a player who is so late it would cause an untenable delay to the entire event, a situation where it would be unreasonable to have 2 people keep playing the match together, a player has run afoul of unsporting conduct rules or has received an upgrade for repeated severe infractions.

In these cases the best thing for the integrity of the event is to end the match.

701.2.c.1. Match losses are applied to the current match, or to the player's next match in the competition if their previous match has ended.

701.2.d. Disqualification: A penalty issued for errors that damage the integrity of the competition or for severe misconduct.

701.2.d.1. Disqualification causes that player to lose the current match and be dropped from the competition.

701.2.d.2. If a player has already physically received prizes from the competition, they keep them, but they will not receive any other prizes after disqualification, even if their placement in the event would otherwise entitle them to prizes.

701.2.d.3. When a player is disqualified, they are removed from the competition and from standings.

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.b. Judges should explain the error, the procedure to fix it, and the penalties for involved players.

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. Shuffling

701.4.a. Some remedies require shuffling the randomized portion of the deck.

701.4.b. Many cards recycle cards to the bottom of a deck. The judge should do what they can using information available from the game state and from the players to determine which portion of the deck is knowable by one or more players, and separate those before shuffling that deck.

The game mechanic of recycling creates an interesting play dynamic where players are potentially tracking information about their deck. "Knowable" is an important word here - if we know a player has recycled cards but since forgotten which cards they recycled, we still want to preserve them having been recycled. Just because the player does not remember them anymore does not mean that they were not part of a player's decision making that led to the current and potential future state of the game.

If we have to shuffle cards into either the Main Deck or Rune Deck, we want to be sure to look at all cards in all players' Board and Trash as well as all Battlefields to make sure we are not missing potential sources of cards having previously been recycled (such as an opponent having played a card that recycles cards from the hand or having a unit that has Deflect). If a card as a repeatable effect that can cause recycling, we should try to determine how many times that effect has been used. We should also consider how cards a player recycled during the mulligan process.

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.4.d. Shuffles performed by a judge in this way are not considered shuffles in game terms.

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.

The definition of "simple" is very specific here. Simple doesn't mean easy to do but instead is limited to *exactly the last actions done*. I.e. undoing an object illegally put on the chain, readying a object that has just been exhausted etc. These can include readying and unrecycling runes in their fixes.

For everything else see 701.5.c

701.5.b.1. Any judge may perform a simple rewind of the most recent action of a game.

701.5.b.2. When performing a simple rewind of a player's game action, rewind to before the action began, such as before a played card would be put on the chain. The player may then opt not to take the action, or take the action making different decisions.

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.5.d.4. If a player learned the identity of a card in a deck, but did not draw or channel it, it should be shuffled into the random part of the deck.

701.6. Investigations

Start here:

https://blogs.magicjudges.org/articles/2014/12/30/investigations-the-search-for-collateral-truths/

701.6.a. Any penalty that results in disqualification automatically starts an investigation into that player and patterns of behavior that might impact their eligibility in future competitions.

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.

701.6.c. The result of an investigation can be suspension of the player from Riftbound competitions.

701.6.d. Suspended players may not enter Riftbound competitions. If a suspended player is found to have registered for a competition, the organizer reserves the right to issue a disqualification at any time.

702. Game Play Errors

702.1	Overview
702.2	Missed Trigger [No Penalty]
702.3	Forgetting to Score a Point [No Penalty]
702.4	Forgetting to Draw Cards [No Penalty]
702.5	Looking at Extra Cards [Warning]
702.6	Channeling Too Many Runes [Warning]
702.7	Channeling Too Few Runes [No Penalty]
702.8	Overpayment for Cost [No Penalty]
702.9	Mispayment for Cost [Warning]
702.10	Looking at Secret Information [Warning]
702.11	Looking at Opponent Private Information [Warning]
702.12	Drawing Extra Cards [Warning]
702.13	Facedown Card Error [Warning]
702.14	Mulligan Procedure Error [Warning]
702.15	Forgetting to Ready During the Awaken Phase [No Penalty]
702.16	General Error [Warning]
702.17	Failure to Maintain Game State [Warning]

702.1. Overview

702.1.a. A game play error is caused by incorrect and inaccurate play of the game that violates the Core Rules.

702.1.b. Repeated game play error [Warnings] can upgrade to [Game Loss].

702.1.b.1. Except for 702.17, if a player commits the same exact category of game play error [Warning] 3 or more times in the same event, the penalty is upgraded to [Game Loss].

702.1.b.2. At competitive OPL, if a player commits a total of 6 or more of any category of game play error [Warning] in the same event, the penalty is upgraded to [Game Loss].

702.1.b.3. At professional OPL, if a player commits a total of 5 or more of any category of game play error [Warning] in the same event, the penalty is upgraded 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.c.1. At low OPL, penalties that require an opponent of the erroring player to make a choice are made at random by a judge when they can't be avoided by a rewind.

702.2. Missed Trigger [No Penalty]: The accountable player for a triggered ability doesn't demonstrate awareness of the trigger before the first time it would have an observable impact on the game.

Clarification:

"Have an observable impact on the game," an be a bit of a confusing phrase for many. If a trigger would have a player take an immediate physical action like draw a card, buff or move a unit that trigger is considered missed if another game action is taken by the controlling player that couldn't have happened with that trigger still on the Chain. For example if a player plays a Lecturing Yordle ("When you play me, draw a card.") and does not draw a card before moving a unit to a battlefield to start a showdown, that trigger has been missed.

Any triggers that target or have a cost to be paid must be announced immediately as they must have a legal target and their costs paid to be finalized on the Chain.

Triggers that do not have an observable impact on the game are often triggers that modify the might of a unit without targeting such as Ravenbloom Student, or Thousand-Tailed Watcher. These triggers must be acknowledged by the first time the might change would have a visible impact, such as a player asking about the unit's might, an effect that references the might of the unit, or assigning damage in combat. Other examples of triggers that do not create observable impacts of the game include triggers that stun units without targeting or a trigger that creates a delayed effect to discount the cost of the next card played.

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.15 for more information about General Errors.

702.2.c. Players may not attempt to cause triggered abilities where an opponent is the accountable player to be missed by taking game actions or otherwise prematurely advancing the game, including through otherwise acceptable shortcuts.

Ultimately, players control the pace of their own effects. Riftbound is not a competition to see who is the fastest player in the tournament.

If a player, during a showdown in their opponent's turn, plays Ride the Wind to move their Qiyana, Victorious to an empty battlefield and conquers that battlefield, the opponent cannot rush to play a unit and claim the Qiyana trigger was missed. That player has the opportunity to pause their opponent to score their trigger. If, however, they acknowledge the units being played, then they have demonstrated that the trigger has been missed.

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.

This prevents players from "accidentally" missing a trigger that can only happen a limited number of times in order to "remember" the trigger at more opportune moment later.

702.2.e. If a mandatory trigger is missed by its accountable player and missing that trigger is advantageous for them, this penalty is a [Warning] instead.

A good way to evaluate whether a trigger being missed was advantageous is to ask ourselves whether we expect the opponent will choose to resolve the trigger or not (see 702.2.f.2). If we expect the opponent will choose to resolve the trigger, that is a sure sign it is advantageous for the player to have missed the trigger. If we expect the opponent will choose to not resolve the trigger, we should probably not be giving a [Warning] for the trigger being missed. It is not relevant whether the opponent actually chooses to resolve the trigger or not, as sometimes opponent's will choose to resolve a trigger that is beneficial to the player who missed the trigger out of a feeling of sportsmanship.

We should not tell the players we are giving the Warning for missing the trigger being advantageous until we have given the opponent the option to resolve the trigger or not! We do not want to be giving the opponent outside assistance.

702.2.f. Remedies:

702.2.f.1. If the trigger was missed during a previous turn, instruct the players to continue playing.

702.2.f.2. Otherwise, the next opponent in turn order of the player who missed the trigger chooses whether to resolve the trigger immediately or miss it altogether.

702.3. Forgetting to Score a Point [No Penalty]: A player is entitled to a point from conquering or holding a battlefield but fails to track it.

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.3.b.1. If the correct score can be determined and no more than a full round cycle has passed, increment the appropriate player's score to that total.

702.3.b.2. Otherwise, instruct the players to continue playing.

702.4. Forgetting to Draw Cards [No Penalty]: A player is obligated to draw a card, either as part of their draw phase or instruction from a card, but fails to do so.

702.4.a. Remedies:

702.4.a.1. If the missed draws can be determined and no more than a full round cycle has passed, the appropriate player draws the missing cards.

702.4.a.2. Otherwise, instruct the players to continue playing.

702.4.b. If forgetting to draw was advantageous to the erroring player (example: the player is near burning out), this penalty is a [Warning] instead.

If a player is intentionally not drawing cards to avoid Burning Out, the penalty is Cheating.

702.5. Looking at Extra Cards [Warning]: While taking a game action that allows a player to look at cards from a deck, they look at more cards than they are entitled to.

In important distinction is that they player must be taking a legal game action to let them look at the cards. If the player looks at cards not due to a game action, such as accidentally knocking over the top of their Main Deck, the penalty is Looking at Secret Information. If the player looks at cards due to an illegal game action, assess the penalty for that illegal game action. For example, if they Predict 2 for a trigger that should not have triggered, it is a General Error.

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. If the error is caught while the erroring player is looking at the extra cards, the next opponent in turn order of the erroring player looks at the private group and chooses the appropriate number of extra cards to shuffle back into the randomized portion of the appropriate deck.

Looking at more cards than a player is entitled to can create a powerful advantage, and there is generally no way for the opponent to verify which card is the extra card. Allowing the opponent to look at and choose the card to return to the deck offsets any potential advantage that could be gained by the erring player.

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

For example, if a player resolving Stacked Deck looks at four cards and puts one into their hand before the error is discovered, we will apply this remedy first to the hand to return one of the cards to the set of four and then also to the set of four to return one to the random portion of the Main Deck.

702.5.c.2. If the error is caught at a later stage in the game, instruct players to continue playing.

702.6. Channeling Too Many Runes [Warning]: A player channels a number of runes greater than they are entitled to under the Core Rules as the result of a limited action.

702.6.a. Errors of this sort are generally public, and all players are expected to be mindful of game state.

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.6.b.3. Otherwise, instruct the players to continue playing.

702.7. Channeling Too Few Runes [No Penalty]: A player channels a number of runes less than what they are entitled to under the Core Rules as the result of a limited action.

702.7.a. Errors of this sort are generally public, and all players are expected to be mindful of game state.

702.7.b. Remedies:

702.7.b.1. If no more than a full round cycle has passed, allow the player to channel the appropriate number of runes.

702.7.b.2. Otherwise, instruct the players to continue playing.

702.7.c. If forgetting to channel runes was advantageous to the erroring player, this penalty is a [Warning] instead.

702.8. Overpayment for Cost [No Penalty]: A player pays a cost overpaying its power or energy cost.

702.8.a. Errors of this sort are generally public, and all players are expected to be mindful of game state.

702.8.b. Remedies:

702.8.b.1. If a cost is overpaid and it is still the turn where the cost was paid, the overpaying player is considered to have the extra resources floating in their resource pool.

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.

For example, if a player pays [4] for a spell that should have cost [3] and it causes Virtuoso (Jhin) to trigger when it should not have, this is a General Error.

702.9. Mispayment for Cost [Warning]: A player pays a cost underpaying its requirements or using the incorrect requirements. See CR 201 Costs for more detail on costs.

702.9.a. Errors of this sort are generally public, and all players are expected to be mindful of game state.

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.9.b.3. If rewinding is not possible, instruct the players to continue playing.

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.

702.10.a. Players should not be penalized via a remedy for errors their opponents make. 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.

702.11.a. Players should not be penalized via a remedy for errors their opponents make. 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. Drawing Extra Cards [Warning]: A player draws more cards than they are entitled to under the Core Rules as the result of a limited action or a player draws cards when they are not entitled to under the Core Rules.

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.

702.13. Facedown Card Error [Warning]: A player places a card into a facedown zone in a manner other than how they are entitled to under the Core Rules.

702.13.a. Example: Hiding a card that does not have the Hidden keyword.

702.13.b. Remedies:

702.13.b.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.b.2. If the error is caught after additional game actions have been taken but before any 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 that zone and replace it with a random card from that zone that is legal for the facedown zone and resume play.

702.13.b.2.a. If there is no available legal replacement, this penalty upgrades to [Game Loss].

702.13.b.2.b. If the error is caught after cards have been added to the zone where the illegal card came from, this penalty upgrades to [Game Loss].

702.14. Mulligan Procedure Error [Warning]: A player performs the mulligan procedure incorrectly.

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.1.a. Example: If a player accidentally mulliganed 3 cards, the next opponent in turn order would look at that player's hand and may choose up to one card 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. Forgetting to Ready During the Awaken Phase [No Penalty]: A player forgets to ready one or more game objects during their Awaken Phase.

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.15.b. If forgetting to ready was advantageous to the erroring player, this penalty is a [Warning] instead.

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.b. Errors of this sort are generally public, and all players are expected to be mindful of game state.

702.16.c. Remedies:

702.16.c.1. Rewind if possible.

702.16.c.2. Otherwise, instruct the players to continue playing.

702.17. Failure to Maintain Game State [Warning]: A player does not call out another player's failure to maintain the proper game state, including missed scoring from hold and conquer.

702.17.a. Generally this error occurs when a player's opponent commits a game play error and the player doesn't call a judge immediately.

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. Tournament Errors

703.1	Overview
703.2	Slow Play [Warning]
703.3	Decklist Error [Game Loss]
703.4	Deck Presentation Error [Warning]
703.5	Communication Violation [Warning]
703.6	Marked Cards [Warning]
703.7	Insufficient Randomization [Warning]
703.8	Late to Match
703.9	Outside Assistance
703.10	Improperly Determining a Winner [Match Loss]

703.1. Overview

703.1.a. A tournament error is caused by actions in or around a tournament match that violate tournament procedure expectations.

703.1.b. Repeated tournament error [Warnings] can upgrade to [Game Loss].

703.1.b.1. If a player commits the same category of tournament error [Warning] 3 or more times in the same event, the penalty is upgraded to [Game Loss].

703.1.b.2. At competitive OPL, if a player commits a total of 6 or more of any category of tournament error [Warning] in the same event, the penalty is upgraded to [Game Loss].

703.1.b.3. At professional OPL, if a player commits a total of 5 or more of any category of tournament error [Warning] in the same event, the penalty is upgraded 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.1.c.1. Penalties that require an opponent of the erroring player to make a choice can be made at random or by a judge if they can't be avoided by a rewind.

703.2. Slow Play [Warning]: A player is performing their start of game procedure or is playing mid-game at an unreasonably slow pace.

703.2.a. Players must take their turns in a timely manner, appropriate to a judge according to the state of the game at the time, and adhere to time limits specified for the tournament.

703.2.b. Players may ask a judge to watch their game for slow play.

703.2.c. Intentionally stalling to gain an advantage is cheating. See 704.8 for more information about cheating.

703.3. Decklist Error [Game Loss]: A player submits a decklist for registration that contains illegal elements.

703.3.a. Examples:

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.a.3. More than 3 copies of a main deck card between main deck and sideboard.

703.3.a.4. Cards that do not match the domain of the registered legend.

703.3.a.5. A chosen champion that does not match the identity of the legend.

703.3.a.6. A player's decks contain cards that do not match their registered decklist.

703.3.b. Remedies:

703.3.b.1. If the player's registered decklist is illegal, the player must correct their decklist to a legal state making as little change as possible and ensure that their deck matches the newly registered deck.

703.3.b.2. If the player's presented decks do not match their registered decklist but their presented decks are legal, the player must change their registered decklist to match their presented deck.

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.

703.4. Deck Presentation Error [Warning]: A player's deck's contents are illegal during presentation to an opponent or during gameplay.

703.4.a. Examples:

703.4.a.1. A player submits a battlefield they have already used in the match.

703.4.a.2. A player forgets to restore their deck to a pre-sideboard state for the first game of a match.

703.4.a.3. A player forgets to take their chosen champion from their main deck and place it in the chosen champion zone.

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.a.5. A player has cards in their deck box with their deck that are not part of the registered contents of their decklist. Promotional cards given out as part of the event, tokens, and damaged cards replaced with official proxies are allowed to be stored this way and do not warrant this error.

703.4.a.5.a. At Professional OPL, extra cards stored in the deck box this way upgrades to a [Game Loss].

703.4.b. Remedies:

703.4.b.1. If the error is caught by any player before opening hands have been drawn, restore the deck to its correct state if possible and instruct players to proceed.

703.4.b.2. If the error is caught by the erroring player after opening hands have been drawn and it is easily possible, restore the deck to its correct state and instruct players to proceed. For example:

703.4.b.2.a. In game one of a match a player realizes they forgot to restore their deck to a pre-sideboard state.

703.4.b.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.b.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.b.2.a.2. Shuffle the randomized portion of the main deck once this process is complete.

703.4.b.3. If the error is caught by a player other than the erroring player after opening hands have been drawn, the penalty is upgraded to [Game Loss].

703.4.b.3.a. At casual or competitive OPL, if the error is a player forgetting to move their Chosen Champion from their Main Deck to the chosen champion zone at setup, the judge may downgrade the penalty to a [Warning] and restore the gamestate if possible, regardless of who caught the error or at which stage of the game it occurred.

703.4.b.3.b. Players may request a judge check an opponent's deck for legality. (Example: A player believes an opponent has a sideboard card in the first game.)

703.4.b.4. If restoring the deck to its correct state is not possible, the penalty is upgraded to [Game Loss].

703.4.b.4.a. When applying a remedy for a missing Chosen Champion is applicable, if it occurs at any point after opening hands have been drawn and no copies of the Chosen Champion are available in the Main Deck to move to the Chosen Champion zone to restore the gamestate, the penalty may be downgraded to a [Warning] and gameplay can continue without the erroring player having a champion in the Chosen Champion zone.

703.4.b.4.b. 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, restoring the deck is not possible.

703.4.b.5. If the cards required to correct the deck cannot be acquired in a timely manner, the head judge can issue a proxy.

703.5. Communication Violation [Warning]: A player does not effectively communicate with their opponents during gameplay.

703.5.a. This error includes any unintentional violation of the communication policies listed in section 500.

703.5.b. Remedies:

703.5.b.1. If any incorrect information was communicated, the correct information is supplied.

703.5.b.2. If any decisions were made based on incorrect communication, perform a rewind if possible.

703.6. Marked Cards [Warning]: A player's cards are possible to identify without seeing their face.

703.6.a. This includes but is not limited to scratches, discoloration, and bends.

703.6.b. If a player's cards are sleeved, the cards must be examined while in the sleeves to determine if they are marked.

703.6.c. The Head Judge has the authority to determine if a card in a player's deck is marked.

703.6.d. Remedies

703.6.d.1. Judges may request that a player remove their current sleeves or replace any of the deck's current sleeves or cards immediately, or before the next round.

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. Insufficient Randomization [Warning]: A player did not sufficiently randomize their deck when required to.

703.7.a. If a player believes an opponent has not sufficiently randomized their Main Deck or Rune Deck before presenting them, they may call a judge.

703.7.b. Pile shuffling is not a sufficient randomization method and should only be used as a counting method.

703.7.c. Remedies:

703.7.c.1. A judge may instruct a player to rerandomize their deck.

703.7.c.2. A judge may randomize the player's deck for them.

703.8. Late to Match: A player arrives at their assigned match after the round clock has started.

703.8.a. If the player arrives within 2 minutes of the round start, the penalty is a [Warning] and a time extension is issued.

703.8.b. If the player arrives within 10 minutes of the round start, the penalty is a [Warning] and a time extension is issued. At high OPL the penalty is upgraded to [Game Loss].

703.8.c. If the player arrives after 10 minutes of the round start, the penalty is a [Match Loss].

703.8.d. If a player never arrives for their match, the penalty is a [Match Loss] and the player is dropped from the tournament unless they report to a judge before the next match begins.

703.8.e. Players may call a judge before the round clock starts or in between games of a match to request up to a 10 minute time extension in lieu of penalty at the judge's discretion. (Example: A player requests to use the restroom.)

703.9. Outside Assistance: A player receives advice or strategic assistance from an individual outside of the match.

703.9.a. If the player receiving the advice actively refuses the advice by calling a judge, they receive a [Warning]. Otherwise, that player receives a [Match Loss]. This penalty does not apply if the head judge deems the advice was delivered maliciously.

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.c. If the spectator giving the outside assistance is also a player in the event, this penalty is also applied to them.

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.f. At a judge's discretion, a player may receive assistance with the physical logistics of the competition, including game actions such as shuffling or card movement. This is not considered outside assistance.

703.10. Improperly Determining a Winner [Match Loss]: Games and matches of Riftbound must be decided by playing Riftbound appropriate to the tournament format.

703.10.a. Other methods, including but not limited to flipping a coin, rolling dice, or playing other games, may not be used to determine a winner.

703.10.b. Playing other formats of Riftbound other than the one designated for the tournament with the appropriate registered decklist may not be used to determine a winner.

703.10.c. Offering or accepting such offers is considered improperly determining a winner.

704. Unsporting Conduct

704.1	Overview
704.2	Unsporting Minor [Warning]
704.3	Unsporting Major [Disqualification]
704.4	Angle Shooting [Warning]
704.5	Bribery [Match Loss]
704.6	Wagering [Disqualification]
704.7	Theft [Disqualification]
704.8	Cheating [Disqualification]

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. Examples include but are not limited to:

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. Examples include but are not limited to:

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. Angle Shooting [Warning]: A player intentionally uses the technical precision of the rules to gain an advantage where the spirit of the rules would not have garnered that advantage.

704.4.a. Examples include but are not limited to:

704.4.a.1. Asking a player to state a choice that they would make on resolution prior to deciding whether to react.

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.a.3. Receiving an offer is not considered bribery unless entertained or accepted, but the receiving player must inform a judge.

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.c.1. Players may end their participation in the tournament at this point or continue to play. If this is a major streamed event, players must continue to play for final rankings.

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.6. Wagering [Disqualification]: Tournament attendees may not wager on any portion of a tournament, match, or game, including its outcome.

704.7. Theft [Disqualification]: Stealing or attempting to steal the property of a tournament attendee, spectator, vendor, or event organizer.

704.8. Cheating [Disqualification]: Riftbound does not tolerate cheating at any level of play.

704.8.a. Cheating includes but is not limited to performing any action that results in a penalty listed under 702 or 703 if it is done knowingly or maliciously to obtain an advantage.

704.8.a.1. This includes attempting to create game errors to use a remedy to the player's advantage.

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. Disciplinary Code

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. Players accept and agree to be bound by these Riftbound Tournament Rules including this Disciplinary Code by: a) signing a contract or registration form in which these Riftbound Tournament Rules are incorporated, linked, referenced, or 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. Monitor compliance with these Riftbound Tournament Rules, other 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 Tournament Rules or other regulations referenced above, as further 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. Reporting: Players must report any violation of these Riftbound Tournament Rules 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 Tournament Rules. Players have a duty to tell the truth in connection with any such 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. Violations of these Riftbound Tournament Rules may be sanctioned by the 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.4. Game, match, or competition forfeiture (including the disqualification of competitions in progress and/or exclusion from future competitions)

705.2.d.5. Replaying a game or match

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 credible evidence may suggest a breach of these Riftbound Tournament Rules, the 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. Intent. Violations of the Riftbound Tournament Rules are subject to disciplinary 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 Tournament Rules.

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.

705.3.b. Unsporting Conduct. Players may not engage in any unsporting conduct listed in 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.d. Unauthorized Communications. Unauthorized coaching and other communications during a match can give a player an unfair competitive advantage, and are 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 violation of these Riftbound Tournament Rules in good faith or who provides 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.

Back to Home