Game Concepts

Zones, cards, power, and the pieces the game is built from.

Core Rules version 2026-03-30

101

Deck Construction

102. Riftbound is a Trading Card Game where a player must provide their own cards to play against other players.
103. To play Riftbound, a player must have two Decks, a Champion Legend, and a number of Battlefields determined by the Mode of Play.
103.1. 1 Champion Legend
103.1.a. This is placed in the Legend Zone at the start of the game.
103.1.b. This will dictate the Domain Identity of the Main Deck.
103.1.b.1. Cards included in your Deck must abide by your Domain Identity.
103.1.b.2. Your deck’s Domain Identity is dictated by the domains of your Champion Legend. In the default card frame, these domains appear as symbols in the legend’s upper left corner.
103.1.b.3. If a card has a single Domain, then that card is permitted in the Domain Identity that corresponds to the same Domain.
103.1.b.4. If a card has more than one Domain, then that card is permitted only in a Domain Identity that contains all of the indicated Domains on that card.
103.2. A Main Deck of at least 40 cards 1 Chosen Champion Unit, Units, Gear, Spells
103.2.a. Chosen Champion
103.2.a.1. This will be placed in the Champion Zone at the start of the game.
103.2.a.2. Must be a champion unit with a champion tag that matches the tag on your Champion Legend. Example: Loose Cannon has the tag Jinx. Therefore, a player could choose Jinx, Rebel or Jinx, Demolitionist as their Chosen Champion, because they also have the tag Jinx. Example: Tibbers has the tag Annie, but it is a signature unit, not a champion unit. It cannot be your Chosen Champion, even if your Champion Legend has the tag Annie.
103.2.a.3. A player’s Chosen Champion is both the specific card chosen for this slot during Deck Building and also any Champion Unit with the same name as the specific card selected for this specific slot during the course of play. Example: A player chose Jinx, Rebel as their Chosen Champion. One copy of Jinx, Rebel starts the game in their Chosen Champion zone. Any additional copies of Jinx, Rebel in their Main Deck, their hand, their trash, or on the board also count as their Chosen Champion for any game rules and effects that care about Chosen Champion status during the game.
103.2.b. Your Main Deck can include up to 3 copies of the same named card.
103.2.b.1. This includes your Chosen Champion. Example: A deck could include Volibear, Furious as its Chosen Champion and still include 2 more copies of Volibear, Furious.
103.2.b.2. Cards have different names even if they represent the same character. Example: A deck could include 3 copies of Yasuo, Remorseful and 3 copies of Yasuo, Windrider, because they have different names.
103.2.c. Subject to Domain Identity.
103.2.d. Your deck may only contain 3 total Signature cards that have the same Champion tag as your Champion Legend.
103.2.d.1. Regardless of name, a deck may only contain a sum total of 3 Signature cards.
103.2.d.2. All of the Signature cards must have the Champion tag that corresponds to the Champion Legend of the deck.
103.2.d.3. Signature cards are not Champion units and cannot be placed in the Champion Zone.
103.2.e. During Gameplay, the Main Deck is Secret Information.
103.2.e.1. It cannot be looked through or revealed unless instructed by a card effect.
103.3. Rune Deck
103.3.a. 12 Rune Cards
103.3.a.1. Cards in this deck must be of the Domain Identity of your Champion Legend.
103.3.b. Must be shuffled and kept separate from the Main Deck.
103.4. Battlefields
103.4.a. The number will be dictated by your Mode of Play.
103.4.b. Subject to Domain Identity if applicable.
103.4.c. Cannot include more than one of a Battlefield of the same name when there are more than one required for the deck.

104

Setup

105

Spaces

106. The Play Area is a collection of logical Zones that are defined by their behaviors and relationships to Players. These Zones are grouped into The Board and Non-Board Zones.

107

The Board

107.1. Bases
107.1.a. Each player has their own Base.
107.1.b. Each Base is a Location.
107.1.c. Permanents and Runes controlled by a player reside in that player's Base.
107.1.c.1. Permanents attached to Permanents controlled by a player may also be found in that player’s Base.
107.1.d. Permanents and Runes in Bases are Public Information.
107.2. Battlefield Zone
107.2.a. The Battlefield Zone houses multiple Battlefields.
107.2.b. Each Battlefield is individually a Location.
107.2.c. Battlefields and permanents at Battlefields are Public Information.
107.3. Facedown Zones
107.3.a. Each Battlefield is associated with a sub-zone called a Facedown Zone, a single logical space that a card can be put facedown in through various Game Effects.
107.3.b. Each Facedown Zone has a maximum occupancy of one card.
107.3.b.1. The maximum occupancy of a Facedown Zone can increase or decrease.
107.3.b.2. If the maximum occupancy of a Facedown Zone decreases to a number less than the number of cards currently located there, the controller of that Facedown Zone must put a number of cards equal to the difference in the trash from the Facedown Zone.
107.3.c. Cards can only be placed in or occupy the Facedown Zone if the controller of the card also controls the associated Battlefield.
107.3.d. If a player loses Control of a Battlefield, any cards in the Facedown Zone associated with that Battlefield are removed during the next Cleanup. See rule 318. Cleanups for more information. See rule 421. Hide for more information.
107.3.e. Facedown Zones are not locations.
107.4. Legend Zone
107.4.a. The space for each player's Champion Legend.
107.4.b. This is not a location.
107.4.c. The Champion Legend here is a Game Object. See rule 120. Game Objects for more information.
107.4.d. The Champion Legend cannot be removed, moved, or displaced from this zone.
108. Non-Board Zones.
108.1. The Chain
108.1.a. Cards and abilities are placed here as part of the process of being played. See rule 327. Chains for more information.
108.1.b. Cards and abilities on the Chain are Public Information.
108.2. Trashes
108.2.a. Each player has their own Trash.
108.2.b. This space is where cards are placed when they are killed or discarded, when they finish being executed as spells, when they are moved to the trash as an effect, etc.
108.2.c. Cards in each player’s Trash are unordered. Their sequence does not matter, and they may be reorganized.
108.2.d. Cards in a player's Trash are Public Information. See rule 128. Privacy for more information.
108.3. Champion Zones
108.3.a. Each player has their own Champion Zone.
108.3.b. The space each player puts their Chosen Champion at the start of the game.
108.3.c. The Chosen Champion cannot be returned to this zone by normal means.
108.3.c.1. If a Chosen Champion is instructed to be returned to this zone, it can only do so if there is not a card already in this zone.
108.3.d. The Chosen Champion can be played from here as normal, following the rules of Playing a Card. See rule 349. Playing Cards for more information.
108.3.e. Cards in a player’s Champion Zone are Public Information.
108.4. Main Deck Zones
108.4.a. Each player has their own Main Deck Zone.
108.4.b. The space for the player's Main Deck.
108.4.c. Primarily houses the face-down deck during gameplay.
108.4.d. The order of cards in the deck is Secret Information during the course of play. See rule 128. Privacy for more information.
108.5. Rune Deck Zones
108.5.a. Each player has their own Rune Deck Zone.
108.5.b. The space for the player's Rune Deck.
108.5.c. Primarily houses the face-down runes during gameplay.
108.5.d. The order of runes in the deck is Secret Information during the course of play. See rule 128. Privacy for more information.
108.6. Banishments
108.6.a. Each player has their own Banishment.
108.6.b. This space is where cards are placed when they are banished by a spell or effect.
108.6.c. Represents cards that have been removed from play in a more difficult-to-recover way, or a temporary space to hold cards while effects are being processed.
108.6.d. The cards in the banishment are unordered. Their sequence does not matter, and they may be reorganized.
108.6.e. The cards in any player's Banishment are Public Information. See rule 128. Privacy for more information.
108.7. The Hand
108.7.a. Each player has their own Hand.
108.7.b. This is the location cards go when Drawn.
108.7.c. The cards in a player's hand are Private Information.
108.7.d. The number of cards in a player's hand is Public Information.
108.7.e. The hand can be targeted as a zone, and cards there can be affected by spells and effects when specified.
109. All Game Objects in the collective Play Areas are Public Information.
109.1. Any player may view, or be provided with the details of the face-up information printed on the cards in the Play Area.
109.2. The State of all Game Objects in the Play Area is also Public Information. Examples: If a Unit is Buffed If a Gear is Exhausted Etc.
110. Whenever a Game Object changes zones to or from a Non-Board Zone, all Temporary Modifications of all kinds cease to be tracked on it in all capacities. Examples: Damage is cleared. Buffs are removed. Granted Keywords are no longer granted.

111

Setup Process

112. Each player separates their Champion Legend and places it in the Legend Zone.
113. Each player separates their Chosen Champion and places it in the Champion Zone.
114. Each player sets aside their Battlefields.
114.1. Your Mode of Play will dictate how these are used and placed into the Battlefield Zone. See rule 476. Modes of Play for more information.
115. Each player shuffles their decks, separately, then places them into their respective Zones.
115.1. The Main Deck is placed in the Main Deck Zone.
115.2. The Rune Deck is placed in the Rune Deck Zone.
116. Determine Turn Order using any fair random method agreed on by all players.
116.1. Turn Order is established as a repeating set of the players.
116.1.a. The Mode of Play will specify how to determine a First Player.
116.1.b. If not otherwise specified, Seating then determines the sequence, play proceeding clockwise from the First Player.
116.1.b.1. The First Player is the player who becomes the Turn Player first.
116.1.c. The Turn Order generates a looping queue of turns, starting with the First Player and repeating until the game ends.
116.2. See the selected Mode of Play for any adjustments to each player's first turn. See rule 476. Modes of Play for more information.
117. Players each draw 4.
118. In turn order, players perform their Mulligan.
118.1. A player may choose up to two cards in their hand. They set those cards aside.
118.2. Then, that player draws as many cards as they set aside.
118.3. Finally, that player Recycles the cards that were set aside. See rule 416. Recycle for more information.
119. Begin play with the First Player taking their turn.

120

Game Objects

121. A Game Object is any game piece that can produce one or more Game Effects or grant prerequisites for players to take Game Actions.
122. A Game Object does not include nor preclude any inherent properties beyond the ability to produce, or act as the prerequisite for, Game Effects and Game Actions.
123. A Game Object can be a literal object or a logical object.
124. Game Objects include, but are not limited to, the following: Main Deck cards in any zone Runes in any zone Legends Battlefields Tokens in any zone Abilities of any type on the chain Buffs and other status markers

125

Cards

126. Riftbound games are composed of players playing the cards in their respective decks.

127

Ownership

127.1. For gameplay purposes, a card's Owner is the player who brought it into the game, either as their Champion Legend, one of their Battlefields, or part of their Main Deck or Rune Deck. The legal owner of a card doesn't matter during gameplay. Example: Bo didn't bring a deck, so Alice loans him a deck. During the game, Bo is considered the owner of those cards, even though legally they belong to Alice.

128

Privacy

128.1. A card will always exist in one of the many Zones described during Setup.
128.2. A card will have a different level of Privacy based on where it resides at a given time
128.3. Secret: This level of Privacy indicates that no player may read or look at the face of the card.
128.4. Private: This level of Privacy indicates that only the controller of a card on the board or the owner of a card in any other zone may read or look at the face of the card. Example: Cards in a player's hand are owned by that player. Only that player may read or look at their faces. Example: If a player controls a facedown card at a battlefield, that player and only that player may read or look at that card's face, regardless of who owns that card.
128.5. Public: This level of Privacy indicates that any player may read or look at the face of the card.

129

Back Side

129.1. The back side of a card is the side with the Riftbound logo.
129.2. There is a unique pattern of back side for each of the three categories of card: Main Deck cards, Rune Deck cards, and Battlefields and Champion Legends.
129.3. The back side of a card is presented to conceal information for Private and Secret information cards. For example, cards in the Main Deck and cards in hand have their back side presented.
129.4. The term facedown is used to describe the state during regular play of having a card's back side presented on the Board. A facedown card’s front side is considered Private Information.

130

Front Side

130.1. The front side of a card is the opposite of its back.
130.2. This is also referred to as a front face.
130.3. This can be identified in situations where the back is not easily discernible by the presence of the Play Cost in the upper left corner of the card.
130.4. Cards, when played, are played with their front face presented.
130.5. The term face up is used to describe the state during regular play of having a card's front face presented
130.6. Cards are considered to be Public Information while in this state, even if obscured by other cards in a pile. Example: The Trash is Public Information because all cards there have their front face presented even while stacked.

131

Cost

131.1. Main Deck cards have a Cost, listed in the upper left corner of the front face of the card. See rule 164. Rune Pools for more information.
131.2. Energy Cost
131.2.a. The numeral listed in the Cost element in the upper left corner of the card.
131.3. Power cost
131.3.a. The symbols, listed vertically, in the Cost element in the upper left corner of the card.
131.3.b. This section may not be present on every card.
131.4. Effects that need to determine a card’s cost for any purpose always use its printed cost, even if that cost is altered or ignored as the card is played. Example: Sky Splitter is a spell that costs 8 Energy and says in part “This spell's Energy cost is reduced by the highest Might among units you control.” Lux, Illuminated is a unit that says “When you play a spell that costs 5 or more, give me +3 [M] this turn.” If a player who controls Lux plays Sky Splitter, Lux’s ability will trigger, regardless of how much was actually paid for Sky Splitter.

132

Name

132.1. Each card has a name that identifies it uniquely.
132.2. This is usually located in the middle of the card.
132.3. Cards that are printed in different languages but represent the same card are considered to have the same name for the purposes of deckbuilding and gameplay. Example: Chemtech Enforcer in English and its counterpart in Chinese are considered the same card, despite the Name element on the card reading differently.
132.4. Some cards have both a short name and a subtitle. For all purposes, including rules and deckbuilding, such a card’s name is “[Short Name], [Subtitle]”. Example: Kai’Sa, Evolutionary and Kai’Sa, Survivor both have the short name Kai’Sa, but they have different names. You can include 3 of each in your deck under normal deckbuilding rules. If one of them is your Chosen Champion, the other is not.

133

Domain

134.1. Most cards belong to one or more of six Domains, identified by one or more symbols in the lower right corner.
134.2. Each Domain has an associated color, a unique symbol, and a shorthand used to represent that symbol in written text.
134.2.a. Fury is associated with the color red and represented by a circular symbol with three projecting points. Its shorthand is [R].
134.2.b. Calm is associated with the color green and represented by a symbol resembling a leaf. Its shorthand is [G].
134.2.c. Mind is associated with the color blue and represented by a symbol resembling a sun and moon. Its shorthand is [B].
134.2.d. Body is associated with the color orange and represented by a blocky diamond-shaped symbol. Its shorthand is [O].
134.2.e. Chaos is associated with the color purple and represented by a hexagonal symbol with swirls emanating from its center. Its shorthand is [P].
134.2.f. Order is associated with the color yellow and represented by an angular winged symbol. Its shorthand is [Y].

135

Rules Text

135.1. All cards have a section that describes how they affect the game. This section is known as the Rules Text of the card.
135.2. This section may contain:
135.2.a. Abilities
135.2.a.1. Abilities are discrete pieces of text that describe what a card may or must do. See rule 360. Abilities for more information.
135.2.a.2. They may appear on any card.
135.2.b. Instructions
135.2.b.1. Instructions are a type of text that appears on spells and within abilities.
135.2.b.2. They describe the actions to be taken as the spell or ability resolves.
135.2.b.3. Instructions will self-describe when they are to be executed. If there is no timing described, they will execute during resolution. Example: An instruction says “as you play me, kill a unit as an additional cost.” That instruction will execute as the card is being played. If the card is given Repeat and the Repeat cost is paid, this instruction will not execute because the Repeat execution does not happen until resolution of the spell, after this instruction has executed.
135.2.b.4. Instructions can usually be recognized by the way they are written. An instruction is written in the imperative mood, using the base form of a verb and omitting the subject unless necessary.
135.2.c. Keywords
135.2.c.1. Keywords are short words or phrases that represent longer abilities or instructions. See rule 800. Keywords for more information.
135.2.c.2. Keywords may or may not have reminder text.
135.2.d. Reminder Text
135.2.d.1. Reminder text appears in italics and parentheses.
135.2.d.2. Its purpose is to summarize relevant rules, including keywords and other rules.
135.2.d.3. The presence, absence, or exact wording of reminder text has no effect on game function.
135.2.e. Symbols
135.2.e.1. Rules text sometimes contains symbols that express game concepts. Each symbol also has a shorthand used to represent it in written text.
135.2.e.2. The cost of Exhausting a Permanent is represented by the “exhaust symbol,” which resembles a card turning sideways. Its shorthand is [E]. (Some previous rules information has given its shorthand as [T].)
135.2.e.3. Might is represented by the “Might symbol,” which resembles a sword and shield. Its shorthand is [M]. (Some previous rules information has given its shorthand as [S].)
135.2.e.4. Power of a specific Domain is represented by its domain symbol and the corresponding shorthand. See rule 134. Domain for more information.
135.2.e.5. Power of any Domain is represented by a swirling rainbow symbol. Its shorthand is [A].
135.2.e.5.a. When required as a cost, [A] can be paid by Power of any Domain.
135.2.e.5.b. When Added to a player’s Rune Pool, [A] can be spent to pay a Power cost of any Domain.
135.2.e.6. Power of a domain corresponding to a card’s own Domain is not represented by a symbol, but appears in these rules similarly to other symbols. Its shorthand is [C].
135.2.e.6.a. When a [C] shorthand is printed on a card as reminder text, it assumes that card’s usual Domain, but it still means “one Power of this card’s Domain.”
135.2.e.6.b. A [C] shorthand on a card with no Domain or with multiple Domains is processed as [A] instead.
135.2.e.7. A keyword associated with an ability is indicated by the [>] symbol.
135.2.e.7.a. This could be a dependent keyword like [Legion][>] or [Level][>], or it could be a permissive keyword like [Action][>] or [Reaction][>].
135.2.e.7.b. Whatever instruction or ability comes after the [>] is modified by the keyword that comes before the [>]. Either it will be inactive, in the case of a dependent keyword, or it will receive the permission granted by the keyword in the case of a permissive keyword.
135.3. Rules text can be blank.
135.4. A card’s printed Rules Text is Inactive while that card is Attached to another card. See rule 716. Attachment for more information. See rule 720. Inactive for more information.
135.4.a. The presence of text, rules, Keywords, and other effects can still be referenced and detected by other game effects, even while Rules Text is Inactive.
135.4.b. Any granted or appended Rules Text on a card is still Active even if that card is Attached to another card.

136

Effect Text

136.1. Some cards have a separate section of text below the Rules Text. This is referred to as the Effect Text.
136.2. Effect Text can contain additional Abilities.
136.2.a. Effect Text can be blank.
136.2.b. Effect Text is inactive unless the card with the Effect Text is Attached to another card. See rule 716. Attachment for more information. See rule 720. Inactive for more information.
136.2.c. The abilities in the Effect Text section of a card are appended to the Rules Text of the card to which the card with the Effect Text is Attached.

137

Might Bonus

137.1. Some cards have a Might Bonus in their lower right corner, expressed as an operator plus an integer.
137.2. A card’s Might Bonus can be +0.
137.3. A card’s Might Bonus modulates the Might of the card to which the card that has the Might Bonus is Attached. See rule 716. Attachment for more information.
137.3.a. The Might Bonus is applied while Attached and stops applying as soon as the card with the Might Bonus is no longer Attached.
137.3.b. If the card to which a card with a Might Bonus is Attached has no Might value, the Might Bonus is ignored.

138

Flavor Text

138.1. Flavor text is text that appears at the bottom of some cards to provide aesthetic enjoyment. It conveys no gameplay information. Example: The card Void Seeker features a quote from the character Kai'Sa. It does not have the Kai'Sa tag and has no gameplay connection to the Champion unit Kai'Sa.
138.2. Flavor text is located at the bottom of the section provided for rules text, usually in a shaded bar. It appears in italics.

139

Illustration

139.1. Each card has an illustration. It conveys no gameplay information.

140

Units

141. Unit is:
141.1. A Game Object
141.1.a. While on the Board:
141.1.a.1. Units are at one of several Locations while on the Board: a Battlefield or their Base.
141.1.a.2. Units and their details are Public Information while on the Board.
141.1.a.3. Units can be chosen, affected, or manipulated by spells, affects, or game actions that specify Units.
141.1.a.4. Units can be Killed. See rule 428. Kill for more information.
141.1.b. While in the Trash:
141.1.b.1. Units are treated as Cards, similar to when in the Hand.
141.1.b.2. They retain the properties of being a Unit, but are not on the Board and thus cannot take actions or be affected by spells, abilities, or game actions that target Units on the Board.
141.1.b.3. Units can be affected by spells and game effects that target Units in the Trash.
141.2. A Card Type
141.2.a. This is a unique identifier that some spells or abilities will use to restrict what they can choose or affect.
141.2.b. The card type is relevant in all zones.
142. Damage is a marked value that is applied to Units.
142.1. Damage is not a Game Object.
142.2. Damage is a value tracked per-Unit.
142.3. Damage tracks how close a Unit is to being Killed. See rule 428. Kill for more information.
142.4. Damage can be Healed. See rule 418. Heal for more information.
143. Units have multiple Intrinsic Properties unique to them:
143.1. Tag: A Unit has zero or more Tags representing one or more champions, regions, factions, or species it belongs to.
143.1.a. These have no intrinsic rules or behaviors by themselves.
143.1.b. Spells, abilities, and game actions can reference these types as part of their execution.
143.2. Might: The combat statistic of a Unit. Used to determine a Unit's contribution to Combat, as well as when it is Killed by damaging effects.
143.2.a. If a Unit ever has nonzero damage marked on it equalling or exceeding its Might, it is Killed.
143.2.b. If a unit's Might is ever less than 0, it is treated as 0 when referenced by spells and abilities, and when summing Might to be assigned as damage in the Combat Damage Step. See rule 460. The Combat Damage Step for more information.
143.2.b.1. Although the unit’s Might is treated as 0, it is not 0. Effects that calculate Might increases and decreases use the actual value of the unit’s Might.
143.3. Units can have damage marked on them.
143.3.a. When spells, abilities, or other game effects deal damage, Units mark that damage on them temporarily. This can be tracked with coins, dice, or other markers, or by memory.
143.3.b. Damage is Healed from Units at two specific times:
143.3.b.1. At the end of each player's turn.
143.3.b.2. During a Combat Cleanup. See rule 461.1. for more information about Combat Cleanups.
143.4. Units enter the Board exhausted.
143.4.a. This can be altered by Accelerate or similar game effects. See rule 805. Accelerate for more information.
144. Units have the Inherent Ability to perform a Standard Move.
144.1. This action is limited in when it can be performed.
144.1.a. This action can be done any time during a player's Main Phase.
144.1.b. This action cannot be performed during a Closed State.
144.1.c. This action cannot be performed during a Showdown or Combat.
144.2. Exhausting the Unit is the Cost for this action.
144.3. Players may perform multiple Units' standard move simultaneously.
144.3.a. When a Move like this is declared by a player, the units' Destination must be the same.
144.3.b. When a Move like this is declared by a player, the Origins do not need to be the same.
144.3.c. The Costs of Exhausting the Units are also paid Simultaneously.
144.4. The Destinations where Units can Move to with their Standard Move are restricted:
144.4.a. Units may move from their Base to a Battlefield.
144.4.a.1. Units cannot Move to a Battlefield that already has units from 2 other players present, or where a Combat is ongoing that has 2 other players as participants.
144.4.b. Units may move from a Battlefield to their Base.
144.4.c. Ganking is a unique ability that affects a Unit's Standard Move
144.4.c.1. Units with Ganking may use their Standard Move to Move from Battlefield to Battlefield. See rule 810. Ganking for more information.
145. Units may have Activated Abilities.
145.1. Activated Abilities are Game Effects that are written as Costs followed by a ":", and then succeeded by an effect. See rule 376. Activated Abilities for more information.
145.2. The Activated Ability of Units may be executed at any time during the controlling player's Main Phase during an Open State, and not during a Showdown.
145.2.a. This follows the same process as playing a card. See rule 349. Playing Cards for more information.
145.2.a.1. This behaves, once activated, like a spell without an associated card.
146. Units have a Location.
146.1. A Unit’s Location is the Base or Battlefield it currently occupies.

147

Gear

148. Gear are:
148.1. A Game Object
148.1.a. While on the Board.
148.1.a.1. Gear can only be played to a player's Base unless an effect specifies otherwise.
148.1.a.2. Gear and their details are Public Information while on the Board.
148.1.a.3. Gear can be chosen, affected, or manipulated by spells, effects, or game actions that specify Gear.
148.1.a.4. Gear can be Killed. See rule 428. Kill for more information.
148.1.b. While in the Trash
148.1.b.1. Gear are treated as Cards before Game Objects, similar to the Hand.
148.1.b.2. They retain the properties of being Gear, but are not on the Board and thus cannot take actions or be affected by spells, abilities, or game actions that affect Gear on the Board.
148.1.b.3. Gear can be affected by spells and game effects that affect Gear in the Trash.
148.2. A Card Type
148.2.a. This is a unique identifier that some spells or abilities will use to restrict what they can choose or affect.
148.2.b. The card type is relevant in all zones.
149. Gear have several Intrinsic Properties unique to them.
149.1. Gear enter play Ready.
149.2. Gear can only be played to a player's Base unless an effect specifies otherwise.
149.3. If an unattached Gear is at a Battlefield for any reason during a cleanup, then it is recalled to its controller's Base as a corrective action. See rule 449. Recalls for more information. See rule 318. Cleanups for more information.
150. Gear may have Activated Abilities.
150.1. Activated Abilities are Game Effects that are written as Costs followed by a ":", and then succeeded by an effect. See rule 376. Activated Abilities for more information.
150.2. The Activated Ability of Gear may be executed at any time during the controlling player's Main Phase during an Open State, and not during a Showdown.
150.2.a. This follows the same process as playing a card. See rule 349. Playing Cards for more information.
150.2.a.1. This behaves, once activated, like a spell without an associated card.
151. Gear have a Location.
151.1. A Gear’s Location is the Base or Battlefield it currently occupies.
151.2. Gear cannot normally become located at a Battlefield unless by some special means. Example: Gear are always played to Base. The only exception is a gear played from Facedown, which is played to the Battlefield it was played from. Gear can also become located at a Battlefield if they are attached to a unit who becomes located at a Battlefield. See rule 811. Hidden for more information. See rule 716. Attachment for more information.

152

Spells

153. Spell is a card type.
154. A spell can be played during an Open State outside of Showdowns on its controller's turn.
155. A spell is controlled by the player who played it.
156. A spell creates a game effect according to its instructions and is then placed in the Trash of the player who owns it.
157. When a spell is successfully played, a player executes the rules text of the spell. This is called Resolving the spell.
157.1. Spells have their rules text executed from top to bottom when they are Resolved.
157.2. If a later part of a spell applies a Replacement Effect that alters earlier parts of the spell, apply those replacement effects as appropriate. Example: A spell says "Choose a unit. Kill it the next time it takes damage this turn." and "[Legion] — Kill it now instead. (Get the effect if you've played another card this turn.)" If the Legion condition is satisfied, the unit is killed immediately and the instruction to kill it the next time it takes damage is ignored, even if the unit remains on the board somehow. See rule 367. Replacement Effects for more information.
157.3. While a spell or ability on the chain is Resolving, no other spells or abilities can be finalized on the chain or resolved, including triggered abilities or game effects that would occur as a result of the execution of the spell.
157.3.a. Finish resolving all effects of a spell before addressing any chain items or Tasks the spell may have added or made outstanding through execution.
158. Certain Keywords on spells are not executable rules text, but instead intrinsic properties of the spell.
158.1. These determine inherent properties and behaviors of the spell before being played or while on the chain.
158.2. These keywords are:
158.2.a. Action
158.2.a.1. This indicates that, in addition to being able to be played during an Open State, this spell may also be played during Open States during Showdowns. See rule 806. Action for more information.
158.2.b. Reaction
158.2.b.1. Grants all cases and rules of Action.
158.2.b.2. In addition to all prior cases, may also be played during all forms of Closed State.
158.2.b.3. This will result in this spell resolving before spells and abilities that are already on the chain. See rule 813. Reaction for more information.

159

Runes

160. Rune is a Card Type.
160.1. A Rune is not a Main Deck card.
160.1.a. This means, despite remaining on the Board until Recycled or otherwise removed from the board, it is not a Permanent.
160.2. Runes are kept in the Rune Deck.
160.2.a. Exactly 12 Rune cards chosen during Deck Construction. See rule 103.3. Rune Deck for more information.
160.2.b. When a Rune is Recycled it is returned to the Rune Deck, not the Main Deck. See rule 416. Recycle for more information.
161. Runes produce the resources needed to pay costs.
162. Runes produce Energy and Power.
162.1. Energy is used to pay numeric Energy costs.
162.1.a. Energy has no Domain.
162.1.b. Energy has no type.
162.2. Power is used to pay Domain-associated Power Costs.
162.2.a. Power has a Domain.
162.2.a.1. Power's Domain usually corresponds to the Domain of the Rune that produced it.
162.2.b. Some Power is Universal and can be used to pay for costs of any Domain.

163

Basic Runes

163.1. There are six Basic Runes, each with a Domain corresponding to its name: Fury Rune Calm Rune Mind Rune Body Rune Chaos Rune Order Rune
163.2. A Basic Rune always has the following two Abilities:
163.2.a. [E]: [Reaction] — Add [1].
163.2.b. Recycle this: [Reaction] — Add [C].
163.2.b.1. The Power added this way corresponds to the Domain of the Rune that is being Recycled.

164

Rune Pools

165. The Rune Pool is a conceptual collection of a player's available Energy and Power available to pay Costs.
165.1. When a card adds Energy or Power, it is added to the controlling player's Rune Pool.
165.2. Players must first add Energy and Power to their Rune Pool in order to be able to spend it to play cards or pay for Abilities with costs.
165.3. Energy and Power do not have a physical marker or tracker, although players may wish to use a physical tracker if they are retaining unspent Energy and Power over the course of their turn.
166. Every player's Rune Pool empties at the end of each player's draw phase and the end of each player's turn.
166.1. Any unspent Energy or Power are lost.
167. All Abilities that include the action "Add" are abilities that are adding Energy or Power to the Rune Pool. See rule 429. Add for more information.

168

Battlefields

169. Battlefields are Game Objects.
169.1. Battlefields are Owned by a player.
169.2. Battlefields are not shuffled into Decks at the start of a game.
169.2.a. Battlefields are not played during the course of regular play.
169.2.b. Battlefields are established at the start of a game and remain in place for the duration of regular play.
169.3. Battlefields cannot be Killed during the course of regular play.
169.4. Battlefields cannot be Moved.
169.5. Battlefields are Locations.
169.5.a. Battlefields can be Origins of moves.
169.5.b. Battlefields can be Destinations of moves.
169.6. Any number of Units can be present at a Battlefield.
169.7. Battlefields can be targeted by spells or game effects.
169.8. Battlefields can have Passive Abilities. See rule 363. Passive Abilities for more information.
169.9. Battlefields can have Triggered Abilities. See rule 382. Triggered Abilities for more information.
169.10. Battlefields can be referenced in different states in card text:
169.10.a. Battlefields can be “occupied.” This means they have a Unit present.
169.10.b. Battlefields can be “uncontrolled.” This means no player controls them.
169.10.c. Battlefields can be “open.” This means they are unoccupied and uncontrolled.
170. Battlefields are not Permanents.
171. The number of Battlefields on the Board is determined by the Mode of Play.

172

Legends

173. Legends are Game Objects.
173.1. Legends are Owned by a player.
173.2. Legends are not shuffled into Decks at the start of a game.
173.2.a. Legends are not played during the course of regular play.
173.2.b. Legends are established at the start of a game, and remain in place for the duration of regular play.
173.3. Legends cannot be Killed during the course of regular play.
173.4. Legends cannot be Moved.
173.5. Legends can be targeted by spells or game effects.
173.6. Legends can have Passive Abilities. See rule 363. Passive Abilities for more information.
173.7. Legends can have Triggered Abilities. See rule 382. Triggered Abilities for more information.
173.8. Legends can have Activated Abilities. See rule 376. Activated Abilities for more information.
174. Legends are not Permanents.
175. Legends may have one or more Domains.
175.1. The Legend determines the Domain Identity of cards its owner can include. See rule 101. Deck Construction for more information.

176

Tokens

177. Tokens are Game Objects created by spells and abilities during play.
178. Tokens can be represented by anything. Printed tokens are included in Riftbound booster packs, but they are not required to play a token.
179. A token's controller is the controller of the spell or ability that created it, unless the token's type innately determines control or that spell or ability specifies that a different player is the token's controller.
180. A token's owner is the player who controlled the effect that created it.
181. The effect that creates a token may specify the conditions or circumstances under which it enters the board. These stipulations may alter the usual steps for playing a card.
181.1. The effect may state that the token enters ready or exhausted, if that state is contrary to the default for the token's type.
181.2. The effect may restrict the location to which the token may be played.
181.3. The effect may grant temporary abilities or modifications to the token.
182. Tokens are not cards.
182.1. Tokens have some properties in common with cards.
182.1.a. Tokens are played by their owner if their card type is played, following all the applicable steps for playing a card plus any restrictions or modifications from the effect that created the token. See rule 349. Playing Cards for more information.
182.1.b. Token units have a Might.
182.1.c. Tokens may have one or more tags.
182.1.d. Tokens have a type. They follow all rules for their type unless otherwise specified. Example: A token unit is a unit. It enters exhausted, can take the standard move action, deals damage equal to its Might in combat, is destroyed if it takes damage equal to or greater than its might, can be chosen or otherwise affected by spells or abilities that choose or affect units, etc.
182.1.e. Tokens inherit the recycle destination of their type. Example: Token runes will be recycled to the Rune Deck. Token units, gear, and spells will be recycled to the Main Deck. Token battlefields and legends can’t be recycled.
182.2. Tokens differ from cards in some ways.
182.2.a. Tokens do not have costs.
182.2.a.1. Although tokens do not have costs, their cost is treated as being 0 for all purposes.
182.2.b. Tokens do not have domains.
183. Tokens are Created on the board or the Chain and cannot exist elsewhere.
183.1. If a token is put into any Non-Board Zone besides the chain, it ceases to exist immediately after moving to its new zone.
184. The spell or ability that Creates a token specifies some of its characteristics. It may have other characteristics, as listed below.
184.1. A 1 [M] Recruit token is a domainless unit token with 1 Might and the Recruit tag.
184.2. A 3 [M] Sprite token with Temporary is a domainless unit token with 3 Might, the Fae tag, and the Temporary keyword. See rule 816. Temporary for more information.
184.3. A 2 [M] Sand Soldier token is a domainless unit token with 2 Might and the Shurima tag.
184.4. A 3 [M] Mech token is a domainless unit token with 3 Might and the Mech tag.
184.5. A Gold gear token is a domainless gear token with “[Reaction][>] Kill this, [E]: [Add] [A].”
184.6. A 0 [M] Reflection token is a domainless unit token with 0 Might.
184.7. A 1 [M] Bird token is a domainless unit token with 1 Might, the Bird tag, and the Deflect keyword. See rule 809. Deflect for more information.
184.8. A Brush battlefield token is a domainless battlefield token with “Bird, Cat, Dog, Poro, and Ivern units here have +1 [M]” and “When you score here, you may replace this with the battlefield it replaced.”
184.9. The Baron Pit battlefield token is a domainless battlefield token with “Units can move here from anywhere.”

185

Control

186. Control is the concept of a player having influence of a Game Object and applies differently to different card types.

187

Battlefields

187.1. Control is established over Battlefields through the course of play.
187.2. Control is a binary state for Battlefields and an Identifier for players.
187.2.a. A Battlefield is Controlled or Uncontrolled.
187.2.b. A Battlefield is Controlled by a specific player or Controlled by no one.
187.3. Control can be Contested through the course of play.
187.3.a. Contested is a temporary status applied to the battlefield when a Unit controlled by a Player who does not currently Control that Battlefield Moves or otherwise becomes present there.
187.3.a.1. Units moving to or being played to a battlefield apply Contested status if that battlefield is not already contested and that Unit’s controller does not already control that battlefield.
187.3.b. A Battlefield remains Contested until Control is established or re-established.
187.3.c. The state of a Battlefield being Contested is used to determine when Combat should occur, when a Non-Combat Showdown should occur, and when Control will change.
187.3.d. At this time Game Effects cannot reference this status.
187.4. Control is established by having Units at a Battlefield at the end of a Showdown or Combat after applying the contested status.
187.4.a. If a player controls Units at a Battlefield, outside of Combat, they maintain Control of that Battlefield for as long as they have Units at that Battlefield.
187.4.b. While a Combat or Showdown is ongoing at a Battlefield, Control of that Battlefield cannot change until instructed by steps of the Combat or Showdown.
187.4.c. If a player has no Units at a Battlefield and the turn is in an Open state, they lose Control of that Battlefield in the following cleanup, unless there is a Combat or Showdown ongoing there.
187.5. Control is a constant state.
187.6. Control of a Battlefield determines Control of its Abilities.
187.6.a. While a Battlefield is Controlled, its Controller controls its Abilities. That player takes responsibility for adding them to the Chain if applicable, and makes all choices required by them unless otherwise specified.
187.6.b. While a Battlefield is Uncontrolled, its Abilities are also Uncontrolled. The Turn Player takes responsibility for adding them to the Chain if applicable, makes all choices required by them unless otherwise specified, and is treated as their Controller if any game rule or effect requires one. Example: The Arena’s Greatest is a battlefield that reads “At the start of each player's first Beginning Phase, that player gains 1 point.” This ability will usually trigger while the battlefield has no controller. If it does, the Turn Player goes through the steps of adding the ability to the chain and receives priority after doing so, exactly as if they controlled the ability.
187.6.c. “You” in a battlefield’s abilities refers to the battlefield’s Controller, as does the implied “you” in instructions like “draw 1.” If the battlefield has no Controller, “you” refers to no one, and all such instructions are ignored.

188

Everything Else

188.1. When a player Plays a Card or other Game Object, they are established as that Game Object's Controller.
188.2. For Spells, they are the Spell's Controller.
188.2.a. That player chooses targets.
188.2.b. That player chooses modes.
188.2.c. That player pays costs.
188.3. For Permanents and Runes, when they Enter the Board, that player is assigned as that Game Object's Controller.
188.3.a. That player may make decisions about the Game Object's Inherent Abilities.
188.3.b. That player may make decisions about the Game Object's Unique Abilities.
188.3.c. That player may make decisions about any game effects or decisions necessary while the card is being played.
188.3.d. That player may make decisions about any game effects created from "When you play me" effects of Permanents.
188.4. For Abilities, they are the Ability’s Controller.
188.4.a. By default, the Controller of an Ability’s Source is the Controller of that Ability.
188.4.b. Changes to Control of an Ability’s Source do not change Control of that Ability.
188.4.c. That player chooses targets.
188.4.d. That player chooses modes.
188.4.e. That player pays costs.
189. When a game effect or rules text refers to the Controller of a specific object, it can be referring to either context interchangeably.
189.1. The method of assignment of control is different, but the status of Control is the same across all Game Objects.

Deck Construction

Setup

Spaces

The Board

Setup Process

Game Objects

Cards

Ownership

Privacy

Back Side

Front Side

Cost

Name

Category

Domain

Rules Text

Effect Text

Might Bonus

Flavor Text

Illustration

Units

Gear

Spells

Runes

Basic Runes

Rune Pools

Battlefields

Legends

Tokens

Control

Battlefields

Everything Else