Short Tournament Rules

• AHJ → Assistant Head Judge
• CR → Core Rules
• DQ → Disqualification
• FJ → Floor Judge
• GL → Game Loss
• HJ → Head Judge
• ML → Match Loss
• RB → Riftbound
• TL → Team Leader
• TR → Tournament Rules
• WA → Warning

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

A player arrives at their assigned match after the round clock has started.

Penalties:

• [WA]: the player arrives within 2 minutes of the round start. Time extension is issued.
• [GL]: the player arrives after 2 minutes, but within 10 minutes of the round start.
• [ML]: the player arrives after 10 minutes of the round start.
• [ML] + Drop: the player never arrives.

Everything you need to know about decks, games and matches.

• 401. Deck Registration
  • 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.
• 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.
• 403. Sideboard
  • 601.1.c.1. A player’s sideboard can include 8 or fewer cards.
  • 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.
• 406. Start of game procedure
  • 111. CR Each player reveals their Champion Legend and places it in the Legend Zone.
  • 112. CR Each player reveals their Chosen Champion and places it in the Champion Zone.
  • 463.5. CR Each player selects 1 of their 3 Battlefields. The other two are set aside. The selected Battlefields are placed in the Battlefield Zone face up. After this game, the Battlefields that were used are to be removed and not selected again for this Match.
  • 114. CR Each player shuffles their decks, separately, then places them into their respective Zones.
  • 115. CR Determine Turn Order using any fair random method agreed on by all players.
  • 116. CR Players each draw 4.
  • 117. CR In turn order, players perform their Mulligan.
  • 118. CR Begin play with the First Player taking their turn.
  • 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.
• 407. Play First Rule
  • 407.2.a. during playoff matches that occur following the end of Swiss rounds, the higher ranked player from the Swiss rounds is automatically the designated player (who decides whether to go first or second) 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.
  • 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.
• 604. Event and Round Time Limits
  • 604.1. Players are given 60 minutes for rounds of play in the Swiss portion of a competitive event.
  • 604.2. Single elimination matches use untimed rounds so players can play their games to a natural conclusion.
• 408. End of Match Procedure
  • 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.
• 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.
• 419 Proxies and Alters
  • 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. The HJ is the final decider on whether a card is acceptable for a competition.
    • 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.
• 420 Card Language
  • 420.1. Players may include official Riftbound cards of any language in their decks during deckbuilding and gameplay.

Shortcuts and rewinds!

• 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.
• 509. !!! Player Rewind !!!
  • 509.3. A player can rewind and make a different decision about an action just taken if and only if they have not gained any new information since taking the action, and a judge allows it.
  • 509.4. Judges who can’t be sure a player gained no information should not allow that player to rewind.

Philosophy and miscellaneous.

• 701.1. Philosophy
  • 701.1.a. Errors are assumed to be committed unintentionally. If the judge believes it was intentional, it is cheating.
    • 701.1.a.1 Players attempting to abuse error remedies to receive advantages are cheating.
  • 701.1.c. Judges should not stop errors from occurring. Instead they deal with errors that have occurred.
  • 701.1.d. Judges should not intervene in games unless:
    • 701.1.d.1. They believe a violation has occurred.
    • 701.1.d.2. A player requested assistance.
    • 701.1.d.3. They observe a situation related to Unsporting Conduct.
  • 701.1.k. HJ and HJ only may issue penalties outside of these guidelines.
• 701.3. Applying Penalties
  • 701.3.b. Judges should explain the error, the procedure to fix it, and the penalties for involved players.
  • 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.
• 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.c. For rewinds more complicated than a simple rewind, only the HJ or designated AHJ may authorize rewinding in this way.

We need this to go on.

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

The real deal - Game play section.

• 702.1.b. Except for 702.16 (Failure to Maintain the Game State), if a player commits the same category of game play error [WA] 3 or more times in the same day of a competition, the penalty is upgraded to [GL].

• 702.2. Missed Trigger [None] - ↑ [WA]
  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.
• Penalty: [None]
• Upgrade: [WA] If a mandatory trigger is missed by its accountable player and that trigger is disadvantageous for them.
• 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 [None]
  A player is entitled to a point from conquering or holding a battlefield but fails to track it. This does not apply to points that would be scored from card triggers such as Ahri, Alluring.
• Penalty: [None]
• 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 [None] - ↑ [WA]
  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.
• Penalty: [None]
• Upgrade: [WA] If forgetting to draw was advantageous to the erroring player (example: the player is near burning out)
• 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.5. Looking at Extra Cards [WA]
  A player takes an action that enables them to see the faces of cards they are not entitled to see.
• Penalty: [WA]
• Remedies:
  • 702.5.c.1. If the cards remain in a single deck, shuffle the deck appropriately to remove the information advantage.

• 702.6. Channeling Too Many Runes [WA]
  A player channels a number of runes greater than they are entitled to under the Core Rules as the result of a limited action.
• Penalty: [WA]
• 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.
  • 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.
    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 [None] - ↑ [WA]
  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.
• Penalty: [None]
• Upgrade: [WA] If forgetting to channel runes was advantageous to the erroring player.
• 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.8. Overpayment for Cost [None] - ↑ [WA]
  A player pays a cost overpaying its power or energy cost.
• Penalty: [None]
• Upgrade: [WA] If overpaying a cost was advantageous to the erroring player.
• 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.
    b. If overpaying a cost caused a result that would not otherwise have happened, it is a General Error.

• 702.9. Mispayment for Cost [WA]
  A player pays a cost underpaying its power or energy cost, or uses the incorrect domain to pay a power cost.
• Penalty: [WA]
• Remedies:
  • 702.9.b.1. Perform a simple rewind if possible, to the moment before the card was played.
  • 702.9.b.2. If a simple rewind is not possible, correct the cost paid if possible, by exhausting, or recycling runes as needed.
    a. If runes were incorrectly recycled as part of the cost, rewind if possible.

• 702.10. Looking at Secret Information [WA]
  A player looks at information that is not available to any player. See CR 127. Privacy for information types.
• Penalty: [WA]
• 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 [WA]
  A player accidentally looks at information that is private to their opponent. See CR 127. Privacy for information types.
• Penalty: [WA]
• 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 [WA]
  A player draws more cards than they are entitled to under the Core Rules as the result of a limited action.
  a. Drawing extra cards is also looking at extra cards, but only this error should be recorded.
• Penalty: [WA]
• 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 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.3. 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. Nonpublic Card Error [WA] - ↑ [GL]
  A player interacts with a nonpublic card in a manner other than how they are entitled to under the CR.
  a. This includes hiding a card that does not have the Hidden keyword.
• Penalty: [WA]
• Upgrade: [GL] If a player hides a card that doesn’t have the Hidden keyword and doesn’t correct it before it has an impact on an opponent’s action.

• 702.14. Mulligan Procedure Error [WA]
  A player performs the mulligan procedure incorrectly.
• Penalty: [WA]
• Remedies:
  • 702.14.a.1. If a player recycled and replaced more than 2 cards during their mulligan, the next opponent in turn order of the erroring player looks at that player’s hand and may choose cards up to the number of extra cards mulliganed to have that player recycle and replace.
  • 702.14.a.2. If this error is caught after gameplay has begun, instruct the players to proceed.

• 702.15. General Error [WA]
  Any other violation of the Rules of Riftbound.
• Penalty: [WA]
• Remedies:
  • 702.15.c.1. Rewind if possible.
  • 702.15.c.2. Otherwise, instruct the players to continue playing.

• 702.16. Failure to Maintain Game State [WA]
  A player does not call out another player’s failure to maintain the proper game state, including missed scoring from hold and conquer.
• Penalty: [WA]

The real deal - Tournament section.

• 703.2. Slow Play [WA]
  A player is performing their start of game procedure or is playing mid-game at an unreasonably slow pace.
  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.
  c. Intentionally stalling to gain an advantage is cheating. See 704.8. Cheating for more information.
• Penalty: [WA]

• 703.3. Decklist Error [GL]
  A player submits a decklist for registration that contains illegal elements.
• Examples:
  • 703.3.a.1. More or fewer cards than appropriate 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.
  • 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.
• Penalty: [GL]
• Remedies:
  • 703.3.b.1. 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 cards required to correct the decklist cannot be acquired in a timely manner, the HJ can issue a proxy.

• 703.4. Deck Presentation Error [WA] - ↑ [GL]
  A player’s deck’s contents are illegal during presentation to an opponent or during gameplay.
• Examples:
  • 703.4.a.1. A player deck does not match their registered decklist.
  • 703.4.a.2. A player submits a battlefield they have already used in the match.
  • 703.4.a.3. A player forgets to restore their deck to a pre-sideboard state for the first game of a match.
  • 703.4.a.4. A player forgets to take their chosen champion from their main deck and place it in the chosen champion zone.
  • 703.4.a.5. A player’s deck is the incorrect deck size. For instance a player misplaced a card or forgot to shuffle their banished cards back into their deck between games.
• Penalty: [WA] If the error is caught by any player before opening hands have been drawn.
• Upgrade: [GL] If the error is caught by a player other than the erroring player after opening hands have been drawn.
  Downgrade to [WA] (all but Pro 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 regardless of who caught the error and when.
• Upgrade: [GL] If restoring the deck to its correct state is not easily possible.
  Downgrade to [WA] When applying a remedy for a missing Chosen Champion, 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, the penalty may be downgraded and gameplay can continue without the erroring player having a champion in the Chosen Champion zone.
• 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.
  • Example: In game one of a match a player realizes they forgot to restore their deck to a pre-sideboard state. A judge can do so by returning cards to the main deck and sideboard as needed. If sideboard cards are in the player's hand, they are replaced randomly by main deck cards that were incorrectly in the sideboard. Shuffle the randomized portion of the main deck once this process is complete.

• 703.5. Communication Violation [WA]
  A player does not effectively communicate with their opponents during gameplay.
• Penalty: [WA]
• 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.10. Improperly Determining a Winner [ML]
  Games and matches of Riftbound must be decided by playing Riftbound appropriate to the tournament format.
• Penalty: [ML]

The real deal - Conduct section.

• 704.1.b. If a player commits the same category of unsporting conduct [WA] 2 or more times throughout all days of a competition, the penalty is upgraded to [GL] and may be further upgraded at the discretion of the HJ.
• 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 HJ may apply any penalty they deem appropriate, up to and including [DQ].

• 704.2. Unsporting Minor [WA]
  Examples include but are not limited to: disrespecting attendees or spectators; bullying; poor hygiene; offensive play materials.
• Penalty: [WA]

• 704.3. Unsporting Major [DQ]
  Examples include but are not limited to: hate speech; physical violence; displaying aggression.
• Penalty: [DQ]

• 704.4. Angle Shooting [WA]
  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.
• Examples: Asking a player to state a choice that they would make on resolution prior to deciding whether to react.
• Taking actions quickly to prevent opponents from having time to have priority.
• Promising a concession to garner additional information before making a different decision.
• Using a printing of a card that is pre-errata without informing opponents once the card is played.
• Baiting an opponent into a rules violation.
• Intentionally distracting an opponent to get them to miss their priority window.
• Using sloppy play or game state representation to obscure strategy or information.
• Penalty: [WA]

• 704.5. Bribery [ML]
  Tournament attendees and spectators may not bribe tournament players or tournament officials.
• Penalty: [ML]

• 704.6. Wagering [DQ]
  Tournament attendees may not wager on any portion of a tournament, match, or game, including its outcome.
• Penalty: [DQ]

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

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