Menu

Riftbound Tournament Rules

Tournament RulesVendetta · updated 2026-07-16
Official PDF
500

Communication

    501.

    Requirements

    1. 501.1.

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

    2. 501.2.

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

    3. 501.3.

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

    4. 501.4.

      Players are required to treat other players, tournament officials, and spectators with respect.

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

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

    2. 502.2.

      In addition to these levels of information, some information is derived.

      1. 502.2.a.

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

      2. 502.2.b.

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

    3. 502.3.

      Like cards, other relevant information about the game state can be public, derived, private, or secret.

    4. 502.4.

      The additional relevant public information includes:

      1. 502.4.a.

        The current turn player, phase, step, state of the turn, and who has priority and focus.

      2. 502.4.b.

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

      3. 502.4.c.

        All players’ current scores.

      4. 502.4.d.

        A permanent’s current state, as distinct from its printed ones.

      5. 502.4.e.

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

      6. 502.4.f.

        Spells and abilities that resolved previously in the turn, and the sources of them are themselves public.

    5. 502.5.

      The additional relevant derived information includes:

      1. 502.5.a.

        Which public cards have been recycled.

      2. 502.5.b.

        The order of runes in a Rune Deck.

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

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

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

        new
    7. 502.7.

      Players must answer honestly any questions regarding public information.

    8. 502.8.

      Players must not represent public or derived information incorrectly.

    9. 502.9.

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

    10. 502.10.

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

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

    1. 503.1.

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

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

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

    4. 503.4.

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

    5. 503.5.

      Players may interrupt their own shortcuts.

    6. 503.6.

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

    7. 503.7.

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

    8. 503.8.

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

    9. 503.9.

      The following are common shortcuts for Riftbound competitions:

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

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

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

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

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

      1. 504.1.a.

        Example: Drawing a card before channeling runes.

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

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

    4. 504.4.

      When something is recycled, it must be immediately put on the bottom of the appropriate deck.

      1. 504.4.a.

        Example: A player may not keep their recycled runes facedown on the board to track Energy.

      2. 504.4.b.

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

    505.

    Loops

    1. 505.1.

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

    2. 505.2.

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

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

      1. 505.3.a.

        No players

      2. 505.3.b.

        One player

      3. 505.3.c.

        Two or more players

    4. 505.4.

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

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

    6. 505.6.

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

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

    8. 505.8.

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

    9. 505.9.

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

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

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

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

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

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

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

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

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

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

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

        was 506.3.a
      3. 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.

        was 506.3.b
      4. 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.)

        was 506.3.c
      5. 506.3.e.

        Examples of observable impact:

        was 506.3.d
        1. 506.3.e.1.

          The trigger would change a point total. (Example card: Ahri, Alluring)

          was 506.3.d.1
        2. 506.3.e.2.

          The trigger would change a rune total. (Example card: Startipped Peak)

          was 506.3.d.2
        3. 506.3.e.3.

          The trigger would add a Buff token to a unit. (Example card: Sett, Brawler)

          was 506.3.d.3
        4. 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)

          was 506.3.d.4
        5. 506.3.e.5.

          A trigger would cause a player to draw or discard. (Example card: Traveling Merchant)

          was 506.3.d.5
        6. 506.3.e.6.

          A trigger would cause a game object to be exhausted or readied. (Example card: Miss Fortune, Captain)

          was 506.3.d.6
        7. 506.3.e.7.

          A trigger would cause a unit to move. (Example card: Stealthy Pursuer)

          was 506.3.d.7
        8. 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.

          was 506.3.d.8
        9. 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)

          was 506.3.d.9
    4. 506.4.

      A triggered ability that was forgotten never goes on the chain.

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

    1. 507.1.

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

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

    1. 508.1.

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

    2. 508.2.

      Runes must be closer to the player than nonrunes.

    3. 508.3.

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

    4. 508.4.

      Main Deck and trash must be together on either the left side or the right side of the board.

    5. 508.5.

      Rune Deck should be on the other side (right or left) of the board from the Main Deck.

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

    7. 508.7.

      Each card or indicator that attaches to another card must be clearly associated with it physically.

    8. 508.8.

      Tokens must be represented by card objects that show all relevant information including ready state.

    9. 508.9.

      Buffs must be represented by an object that unambiguously represents a buff in game terms.

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

    1. 509.1.

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

    2. 509.2.

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

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

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

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

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

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

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

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

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

      4. 509.4.d.

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

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

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

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