Tournament Rules

103.1. Attendees: All competitors AND all competition officials are expected to be responsible for following the rules as written and in the spirit in which they were written. This includes respecting all people at competitions.

103.2. Spectators: Spectators have their own set of responsibilities and expectations. See 204.8 for more information on spectators.

103.3. Penalties: Individuals who violate the frameworks and structures in this document are subject to penalties at the appropriate Organized Play Level (OPL). See 205 for more information on Organized Play Levels.

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

201.1. Premier: A competition that is run by Riot Games or an official competition organizer and has a unique name and features.

201.2. Qualifier: Any competition where rewards include access or advantages for premier events. (Premier events can themselves be qualifiers.)

201.3. Local: Any competition that is neither premier nor qualifier.

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

202.2. Constructed: A constructed competition is one where players compete using decks they prepare beforehand.

202.3. Swiss: A competition or component of a competition where players are paired based on their current standing in the competition.

202.4. Playoff: A competition or component of a competition where players are initially paired based on their standing and are subsequently eliminated by losses.

202.5. Rules: Each format has rules specific to it.

202.6. Multiple: Some competitions may consist of multiple formats within the same competition.

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.1. Official roles: Roles 3-6 are considered competition officials for the purpose of this document.

204.2. Judge roles: Roles 4-5 are considered judges for the purpose of this document.

204.3. Competition Organizer (CO): The CO is responsible for all competition logistics, including:

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

204.8. Spectator

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.3. Competitive (high): These competitions have significant rewards, which may include invitations or advantages at the Professional level.

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

206.1. Additional turns do not affect the round cycle.

301.1. Suspended.

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

301.3. Specifically prohibited by Riot or official partner policy.

301.4. Under 13 years of age and do not have a parent's or guardian's permission.

301.5. Prohibited by law, the rules or policy of the Competition Organizer, or by the venue's rules or policy.

301.6. Restricted by competition addenda regarding age, as long as those restrictions are messaged ahead of time (at low OPL).

302.1. Suspended.

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

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.3. Employees must declare themselves to the CO.

306.4. The CO may decline to allow Riot employees to participate in the competition for any reason; if so, they must abide by this decision.

306.5. No Riot employee is allowed to play in premier or qualifier competitions.

306.6. Families of employees are allowed to play in premier or qualifier competitions, if they are otherwise eligible to compete.

401.1. Players in competitions are required to register their decks and sideboards (if applicable to the format) at high 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.

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.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.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 skips the first game due to a penalty or an intentional draw, neither player qualifies for 403.5.

403.10. 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.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.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.1. The setup process for a game of Riftbound is defined in the Core Rules. See CR 110 Setup Process. Additionally:

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.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.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.3. The winner of a match is the first player who reaches the appropriate game win score.

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:

409.1. In the course of determining standings, the scorekeeper might need to distinguish between two players with equal match records.

409.2. In these cases, the following tiebreakers should be applied in order:

409.3. If after all tiebreakers are applied, two players are still of equal standing in the competition, the scorekeeper should use a random method to break the tie.

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

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

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.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.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.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.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.5. By judge discretion, alters may not be allowed to be used 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.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.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'sMain 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.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.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:

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

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.1. Cards have a level of privacy as specified in CR 127 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.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.5. The additional relevant derived information includes:

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.d. for examples of observable impact.

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.

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:

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

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.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.1. Accountable Player: The player responsible for putting a triggered ability on the chain, as defined by the core rules. See CR 375 Triggered Abilities for more information on triggered 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.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.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.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

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.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, a judge allows it, and the following is true:

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.

601.1. Deck Construction

601.2. Card Legality

601.3. Standard

602.1. Legality

602.2. Abnormal Product

602.3. Building From a Limited Pool

602.4. Limited Formats

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

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

701.1. Philosophy

701.2. Definitions of Penalties

701.3. Applying Penalties

701.4. Shuffling

701.5. Rewinding

701.6. Investigations

702.1. Overview

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.

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.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.5. Looking at Extra Cards [Warning]: A player takes an action that enables them to see the faces of cards they are not entitled to see.

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.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.8. Overpayment for Cost [No Penalty]: A player pays a cost overpaying its power or energy cost.

702.9. Mispayment for Cost [Warning]: A player pays a cost underpaying its power or energy cost, or uses the incorrect domain to pay a power cost.

702.10. Looking at Secret Information [Warning]: A player looks at information that is not available to any player. See CR 127 Privacy for information types.

702.11. Looking at Opponent Private Information [Warning]: A player accidentally looks at information that is private to their opponent. See CR 127 Privacy for information types.

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.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.14. Mulligan Procedure Error [Warning]: A player performs the mulligan procedure incorrectly.

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.16. General Error [Warning]: Any other violation of the Rules of Riftbound.

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.

703.1. Overview

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.3. Decklist Error [Game Loss]: A player submits a decklist for registration that contains illegal elements.

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

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

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

703.7. Insufficient Randomization [Warning]: A player did not sufficiently randomize their deck when required to.

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

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

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

704.1. Overview

704.2. Unsporting Minor [Warning]:

704.3. Unsporting Major [Disqualification]:

704.4. Angle Shooting [Warning]: A player uses the technical precision of the rules to gain an advantage where the spirit of the rules would not have garnered that advantage.

704.5. Bribery [Match Loss]: Tournament attendees and spectators may not bribe tournament players or tournament officials.

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.