⚡ Offline Mode: All rules, cards, and rulings are accessible directly on your device.

Relevant changes from CR 1.4 to CR 1.5

[1.5] Core Rules ANALYSIS

This document has been written by Judges Giuseppe Visconti (poig_122 on Discord) and Marco Riggio (lollow88 on Discord) as a way to highlight most of the changes we deemed noteworthy in the updated 1.5 Core Rules (10-09-2026).

We tried to better explain and contextualize each of the changes, hopefully helping to smooth out the transition from one rules version to the other.

This is a living document and will be changed as better interpretations arise and mistakes are pointed out. If you spot anything you feel could be corrected, please do reach out and let us know!

The document is divided into 3 parts: one for rules that have been completely added in, one for rules that have been changed and so functionally altered, and one for rules that have been clarified, meaning changed either to give a formalized base to rulings that were previously already known or to clear existing doubts on game systems and cards interactions.

Gameplay Impact Notice: Changes that affect the rules in a way such that the gameplay is mechanically affected are highlighted throughout this analysis.

PART 1 — ADDED RULES

Cards That Alter Deck Construction

Rule 103.1
Neeko, Blending In
Neeko, Blending In (RAD 167/167)
103.1. Cards in a player’s deck or rules of a Game Mode may indicate additional choices to be made while building the deck.
Example: A unit reads in part “If [Name] is in your deck, choose 3 different legends in addition to your starting legend.” This decision is made while building the deck.
Example: The rules of a game mode read in part “Choose an additional Chosen Champion with a different Champion Tag and Domain than your Champion Legend. Place it in the Champion Zone at the start of the game alongside your other Chosen Champion. Your deck’s Domain Identity includes that additional Chosen Champion’s Domain, if applicable.” The Chosen Champion chosen this way is decided while building the deck.

This is basically support for <<Neeko, Blending In>> and future-proofing work. Also see Create from a Finite Set of Choices and this section of the Radiance Patch Notes for more info on how this card works.

Note that there are still doubts on how this interacts, if at all, with the deck’s domain identity (e.g., do the additional legends have to abide by the same domain rules set by the original legend?).

Cards With No Domain

Rule 103.2.b.5
103.2.b.5. If a card has no Domain, then that card is permitted in decks of any Domain Identity.

Provides explicit, formal rules grounding that domain-less (neutral) cards are legal in decks regardless of the Starting Legend's Domain Identity.

Referencing a Unit’s Might

Rule 143.2.a
143.2.a. A Unit’s Might can be referenced by cards and effects.

Summary scheme:

  1. Printed Might: found on the printed Object.
  2. Base Might: handled in the Trait-Altering Effects Layer (#2); it can be modified by game effects.
  3. Effective Might: calculated in the Arithmetic Effects Layer (#4) considering all the Effects that modify Might; this is the value that is referenced by abilities and effects when they use only the word “Might”.

Units Cannot Be Attached to Other Permanents

Rule 143.5
Lady of Clockwork
Lady of Clockwork (RAD 145/167)
143.5. Units cannot be attached to other permanents. If a permanent that is attached to another permanent becomes a unit, it immediately detaches. If a unit would become attached to another permanent, that action is ignored.

This basically answers these 3 questions:

Ruling Q&A

“What happens if an attached gear becomes a Unit-Gear through <<Lady of Clockwork>>’s ability?”
It immediately detaches.

“What happens if a Unit-Gear’s Equip Ability is about to resolve?”
Nothing happens on resolution.

“What happens if a Unit-Gear with the Equipment tag is targeted through a Weaponmaster trigger and the Weaponmaster trigger is about to resolve?”
Nothing happens on resolution.

Created Legends

Rule 173

Added the possibility of creating Legends (relevant for <<Neeko, Blending In>>).

Abilities Played by Non-Controller or Non-Owner of the Source

Rule 191.5.a.2
Black Market Broker
Black Market Broker (SFD 121/221)

Added that certain abilities can allow players other than the controller or owner of a permanent to play them and, in that case, it is the player that adds it to the chain that controls the ability (and not the controller or owner of the source). For example, this would apply to any effects with the “each player may use this ability” line, such as <<Black Market>>.

“Picking”

Rule 412.1

This term defines a game action used to specifically select game objects during finalization, or resolution (see the example in 412.1), without them becoming Targeted.

Targeting Exemption for Legends

Rule 355.10.g
Example If a player controls 2 Legends (one is the Champion Legend, and another is a Legend created with <<Neeko, Blending In>>), and an instruction reads “ready your legend”, that instruction will not target a Legend. It will be chosen on resolution instead.

Before this update, an instruction like “ready your legend” wouldn’t have targeted a legend, since that object would have been programmatically selected anyways. With the addition of Neeko, however, this needed to have an exception carved out for it.

Mandatory Requirements and Restrictions

Rule 355.17 (355.17.a / 355.17.b)

First and foremost:

  • What is a mandatory requirement? It directs you to perform an action (“Do this thing, this way”);
  • What is a restriction? It’s a sentence that explicitly limits the range of possibilities (“You can do this thing only this way” or “You cannot do this thing”).
Everyday Life Analogy My mother tells me "go buy groceries at the supermarket" → this is a mandatory requirement because, by not directly limiting other existing options, it does not eliminate the possibility that, after following the instruction (since it must be followed), I might then go to the videogame store.

My mother tells me "if you go out, you can only go to the supermarket" or “if you go out, you cannot go to the videogame store” → these are restrictions, because they directly limit my other existing options. No video games, neither before nor after.

Back to the rules, this is a summary scheme:

  • Multiple non-conflicting requirements → All of them must be followed (see the second example in 355.17.a).
  • Multiple contradictory sets of non-conflicting requirements → Follow one set and ignore the other ones [e.g.: There are a total of 3 mandatory requirements: 2 of them are non-conflicting with each other, so they form a set; the last one is contradictory to the first two, so it forms a set by itself. One of the sets will be followed, and the other one will be disregarded. So note that for the sake of the rule, even a single requirement can form a set if it contradicts every other requirement: with two contradictory mandatory requirements, one will be followed and the other one disregarded; see the first example in 355.17.a].
  • Restrictions → All of them must be followed, or finalization will fail. Restrictions have priority over mandatory requirements, if they conflict; contradictory restrictions cause the chain element to fail finalization (because one of them will not be possibly followed). We strongly recommend reading the examples in 355.17.b.

Checkpoint for Variable Discounts

Rule 337.3

This addition to Step 3 of the Play Process (“Determine Total Cost”) is intended to give more stability to the game system and clarify that, once determined, the costs to be paid don’t change.

Replacement Effects of Objects in Secret Zones

Rule 370.1.c.1

Given the fact that Replacement Effects are usually applied before their qualifying events, this was added to take into account replacement effects that depend on information disclosed from a secret zone, and thus can’t be accessed until the qualifying event.

Rules on Activating Abilities

Rule 170.11.b
  • Who can play an activated ability when the source is uncontrolled (and is not a battlefield)? The owner of the source.
  • When can such an ability be played? In a Neutral Open State, during the Main Phase of the Source’s Owner.

These last two rules complement and reinforce what was explained in 191.5.a.2 (See also Abilities Played by Non-Controller or Non-Owner of the Source).

Doubling Damage as a Replacement Effect

Rule 433.1.b
Lotus Trap
Lotus Trap (UNL 013/219)

Previously the rules didn’t cover this even though the gameplay mechanic was already there (e.g.: through <<Lotus Trap>>); now we know this mechanic is formalized as being a Replacement Effect.

Creating from a Finite Set of Choices

Rule 440.3.c

Applicability, simplified:

  • We have a card with an Ability that affects deckbuilding in such a way that leads us to make some choices. These choices form a finite set of objects.
  • This Ability is linked with another one which instructs us to Create one object from that set.

Though the rules text seems to imply that only one of those objects within the whole set can exist at a time, Patch Notes and further text point to being able to have multiple of these game objects, as long as they are different from each other. As of now, this rule applies only to <<Neeko, Blending In>>; we strongly recommend reading this section of the Radiance Patch Notes for more info on how this card works.

Paying [0] Cannot be Declined

Rule 445.1.b
Fizz, Trickster
Fizz, Trickster (SFD 140/221)
Wages of Pain
Wages of Pain (SFD 070/221)
Example I play <<Fizz, Trickster>> to play <<Wages of Pain>> from trash. Once on the chain, since the total cost of the card is 0 Energy and 0 Power, payment for it cannot be declined, and the resources will be paid without the Pay Game Action being performed by the player.

“Copy” Game Action

Rule 446 (and 446.3)

Formalization of what is already present in the game, in practice. 446.3 is notable, though, even if it doesn’t seem relevant as of now: if a Game Object is Created as a Copy of another Object (i.e.: it doesn’t “become” a copy), the original, printed traits of the first object are taken from the copied object; in other words, the Game Object that is Created as a Copy originates with the traits of the copied Game Object, there is no subsequent “application” of a Copy effect.

Object Level Dependency in Layers

Rule 478.1.a
Core Engine Addition: Introduced the concept of Dependencies between different Game Objects (“object level Dependency”), whereas previously Dependencies were something that could only occur within the Layers of a singular Game Object.

When such cases occur, Layer evaluation of all other Game Objects is paused; we go up the dependency chain to the Game Object all latter ones depend on first, and evaluate all layers for that one first. Later Game Objects that depend on it are determined after that in order, going down the dependency chain.

Example Layers’ evaluation for Game Object A depends on Game Object B, and B depends on C. So we evaluate Layers for C first, then we move on to B, and at the end, we evaluate A’s Layers.

If, within an object level dependency chain, there is a mutual dependency, the Game Objects that have such mutual dependency have their layers evaluated at the same time, layer by layer.

This clarification on “dependent evaluations” of Layers is another fundamental step to understanding Riftbound’s rule engine, so we recommend fully reading this new block.

Copy Layer (#1)

Rule 479.1

Adding a separate Layer for copy effects takes away the confusion about what traits are copied over to another object and prevents overloading the Traits-Altering Layer.

Example If an effect alters the base might of a unit, and that same unit is used as a source for a copy effect, the base might alteration in the Trait-Altering Effects Layer (Layer #2) will not be copied over to the target object, since that wasn’t an update within the copyable traits of that unit, which are handled in the Copy Layer (Layer #1).

This was already prefaced and explained previously (with confirmation by UVS), but now it is formalised in the rules.

Facedown Cards are not Cards with Hidden

Rule 811.5.a

A facedown card is not a card with “Hidden” for the sake of referenceable characteristics, because the Keyword on the card is not public information.

Example If an imaginary instruction needs us to target or pick a card with Hidden, then a facedown card at a battlefield is NOT a valid choice.

Note: The passive ability that reads “Play or create this only to a battlefield” is a restriction on the Play Process; we recommend reading Mandatory Requirements and Restrictions to better understand how this could potentially interact with other requirements or restrictions.

  • The target for the Disarm ability has to be present at the same location as its Source (because of “here” in 831.1.d).
  • Multiple instances of Disarm on the same Source all flow into the same trigger: only one trigger will be added to the chain with a Disarm value equal to the sum of all instances.

While Showing Off a set of Game Objects, I can mix revealed cards from hand with friendly Game Objects picked from the board (also see “Picking”).

Following 832.2.a, every Show Off keyword is bound to linked instructions from the same Source.

What if an instruction referencing “showing off” is appended to the Rules Text of a card (that doesn’t also grant a linked Show Off keyword)? In that case, the appended instruction is linked to all Show Off keywords (appended or not) on the appropriate card.

Step 5 of the Cleanup

Rule 178.1.a.1.a (107.3.d)
Akshan, Mischievous
Akshan, Mischievous (SFD 109/221)

Added support for Deploy through “Recall all of the following Game Objects unless an effect would indicate otherwise”). Also see Deploy.

“Now” gear controlled by a player different from the one controlling their Top-Most Card are not recalled during the next cleanup (it was already ruled this way, thanks to 107.1.c.1, even if the Cleanup rules did not state it - by mistake).

Example I gain control of an opponent’s Equipment through <<Akshan, Mischievous>>’s triggered ability, then I play a unit with Weaponmaster. The Equipment gets attached to this unit through Weaponmaster. After that, Akshan leaves the board, so control of the Equipment switches back to the opponent, but the gear still stays attached to the unit. Under the previous version of the CR, in theory, step 5 of the Cleanup (and only it) would have recalled that gear.

Step 5 (“Check Legality”) of Playing a Card

Rule 329.2 (337.5)

It has been made explicit that during this step we’ll check the legality of all choices that were made, including the observance of requirements and restrictions affecting the play process.

Even though it’s made clear through an example, what was stated in the Vendetta FAQ about Temporal Breach on a unit controlled by a player different from its owner, was confirmed: an opponent’s Base is not a legal play location for friendly permanents, even if required by an effect.

Added more clarity about the scope of the check for illegal states as outcomes of the resolution. The addition in 358.5 addresses external events related to the finalization of an object.

Example A unit (A) reads in part “as an additional cost to play me, you may kill a friendly unit”; if the killed unit had Deathknell, and the finalization of unit A fails, that Deathknell is removed from the chain and is considered to have never happened.

Ignored and Negated

Rule 128.6.a

To summarize:

  • If an instruction isn’t executed due to a mistarget or unavailable information → that instruction is Ignored.
  • If an instruction isn’t executed for any other reason (e.g.: because it was replaced, prevented, or skipped) → that instruction is Negated.

It's important to clarify that, in fact, despite being a noticeable change in the rules, the intentions have always been these, so there's nothing new regarding how the game functions (it's very unlikely that incorrect rulings were given regarding this aspect).

Still regarding the rules framework, the greatest impact of this change falls on linked instructions (the above consideration also applies here).

Given 2 subsequent linked instructions… If the first one is… Then the second one is…
Ignored Ignored
Negated Not affected, unless it directly references the Game Action being performed (e.g.: “If you do, …”)

Abilities that Trigger when the Source Leaves the Board

Rule 359.3.e.16

This change aligns this kind of trigger with how Deathknells work in regards to noting info about the source of the ability or the state of the game before moving the source outside of the board.

When such a triggered ability meets its condition, this series of steps has to be followed:

  1. Evaluate applicable Replacement effects →
  2. Add the ability to the chain (noting all relevant information as above stated) →
  3. Move the object outside of the board.

“Add” Triggered and Activated Abilities

Rule 346.1 (402.1)
Threshold of the Gray
Threshold of the Gray (VEN 166/166)
Diana, Lunari
Diana, Lunari (UNL 079/219)

“Add” Triggered and Activated Abilities finalize before any other “non-Add” pending Triggered or Activated ability finalizes (so this rule does NOT apply to spells that Add resources, as they will be finalized and will resolve at the normal timing for spells [430.2.b]); it is remarkable that they finalize and resolve in this fashion even in between Tasks and FEPR steps, that are paused. Basically, given this timing, chain ordering doesn’t matter for these abilities; following the game dynamics, the resources they provide are immediately available to be spent as soon as they go on chain, because they immediately finalize and resolve.

Example I control <<Threshold of the Gray>> with a unit. In their turn, my opponent moves in their <<Diana, Lunari>>. The battlefield’s and Diana’s triggers both go on the chain, and despite the order being Diana > Threshold, Threshold’s Add ability will finalize and resolve before Diana’s trigger’s finalization, so the 1 Energy provided will be available to be spent to finalize her ability.

Removal of the Focus Task at the Start of Combat

Section 316

The reason is likely due to this being already covered in the Chains and Showdowns section and complemented by the rules within the Attacker/Defender designation task.

2v2 Scoring Rules

Rule 491 (473.1.b.1)
Flash
Flash (OGS 011/024)
Example 1 My turn starts, all battlefields are uncontrolled. I conquer one of them with one of my units, and after that I move it to base using a spell. Then, I use another spell to move one of my teammate’s units to the same battlefield I conquered this turn: our team will NOT score that battlefield again this turn. This exact dynamic was instead allowed by the previous version of the Core Rules.

It was already previously assumed that this check happened in the Scoring Step, but it is now formalized.

Example 2 I start my turn, and Battlefield A is currently controlled by my Teammate through a unit that is present there, while Battlefield B is controlled by me through a unit with Temporary. In the Beginning Step of the Beginning Phase, the unit’s Temporary trigger is added to the chain; in response (following legal priority timings), my teammate plays <<Flash>> targeting their unit on Battlefield A. Both chain elements resolve. We advance to the Scoring Step of the Beginning Phase: Battlefield B is uncontrolled at that moment, so it qualifies for Scoring by our Team during my turn.

Only when trying to win from Conquer on my turn or my teammate’s, the battlefields controlled by my teammate (in the Scoring Step) don’t count for the purpose of evaluating how many remain to be Scored that turn.

Conquer Win Scenarios (Team A vs Team B)

1) Team A is at 10 points. Player B1 starts their turn and team A controls 2 out of 3 Battlefields, while the third is uncontrolled. If Player A1 or A2 scores that third Battlefield during this turn, Team A will NOT win: in order to win, since it is an opponent’s turn, they need to Score every Battlefield in that same turn — there are no exceptions for controlling battlefields at the start of the turn, and normal rules for scoring the winning point apply (473.1.b.1).

2) I start my turn and Team A is at 9 points; Scoring Step happens: Battlefield 1 is controlled by my teammate and Team A scores one other point by Holding Battlefield 2, thanks to one of my units. At this moment, the game checks how many Battlefields I’ll have to Score in order to win this turn, and the answer is “Battlefield 2 and 3”. Battlefield 2 was indeed scored, bringing the point total for Team A to 10; now, if I want Team A to win, only Battlefield 3 is left to be Conquered.

But…what happens if it's my turn, my team is at 10 points, my teammate controls two battlefields, and they want to score on the remaining uncontrolled battlefield? Do we still win on my turn? Following RAW, the answer is no, but we believe it will be addressed.

Making New Choices

Rule 355.15

3 main key points:

  • When a player is allowed to make new choices for a chain element, they must decide between remaking all choices or not making new choices at all: this is an alignment to the Vendetta FAQ; they are allowed to choose the same original objects again, if legal.
  • Restrictions apply to the process of making new choices as they were applied on the original choices: this is a clarification of something that was already assumed.
  • Choosing an object through the process of “making new choices” will make Targeting Effects trigger even if the object in question was already previously targeted: this is different from before.

Play Effects of Hidden Permanents

Rule 355.10

Reminder: The play effects of permanents played from facedown are treated as though they had “at the battlefield I was played to from facedown” added to the text of the instruction that targets, acting as a targeting requirement (also see Targeting Requirements from External Sources), and as such it has to be met both on finalization and on resolution.

To check information about the battlefield the permanent was played to from facedown (in order to fulfill the targeting restriction and choose legal targets), that permanent must be on the board during finalization and resolution of its play effect; otherwise, that information is not referenceable.

This is because we now know that this info is referencing the source of the ability — this means that “the location a permanent was played to from facedown” is information belonging to that permanent that can only be referenced as long as it exists on the board. We also recommend reading the example in the added rule.

Knowing the Number of Cards in a Main Deck

Rule 108.4.d

This was already heavily assumed but an explicit confirmation was needed: the number of cards in each player's Main Deck is public information that can be asked and known at any time.

Scope of Conditional Clauses

Rule 135.2.b.5.b

To simplify: a conditional clause applies to everything between it and the period at the end of that sentence. This is purely housekeeping and future-proofing.

Actions “You” Performed During Finalization & Control of One’s Own Champion Legend

Rule 191.1 (354.2)
Heartening Soul
Heartening Soul (RAD 040/167)
Profiteer
Profiteer (VEN 082/166)
Heimerdinger, Inventor
Heimerdinger, Inventor (OGN 111/298)

Clarifies the relationship between actions performed during finalization and control of one’s own Champion Legend. This is relevant for cards like <<Heimerdinger, Inventor>>, <<Profiteer>>, <<Shock Blast>>, <<Heartening Soul>> and <<Forge of the Fluft>>.

Base Cost Determination for Activated Abilities

Rule 204.1

Clarified that when multiple options for costs of activated abilities are present, the chosen one is counted as base cost during step 3 of the play process.

Cost Determination for Objects with a Copied Cost

Rule 206

Clarified that objects with both a printed and a copied cost will use the copied cost for the purpose of reference by other effects.

Step 2 of Playing a Card

Rule 337.2
Baron Nashor
Baron Nashor (UNL 147/219)

Clarified the timing for the performance of actions such as creating the Baron Pit through <<Baron Nashor>> or revealing/picking cards through Show Off.

Rule 312.2.c

It is also clarified that the words “spell” and “ability” in the text of an instruction refer to finalized game objects.

Choosing a Subset of Targets

Rule 355.10

Specified that a legal subset has to include the largest number possible. This was necessary as forgoing this left room for interpretation.

Targeting Requirements from External Sources

Rule 355.10

This clarifies the nature of targeting requirements applied to hidden cards: they are treated the same as any other targeting requirements on a chain element, so they have to be met both on finalization AND on resolution.

“At the End of Turn” Abilities

Rule 317.1.a (359.3.e.16)

“At the end of turn” is synonymous with “at the end of this turn”: we know this thanks to the example in 359.3.e.16 and this section of the Radiance Patch Notes.

As a housekeeping fix, these effects are also added to 317.1.a.

Note: “This turn” in “at the end of this turn” refers to the turn in which the ability that generated the trigger resolved.

“You may” as first part of a Reflexive Trigger

Rule 355.5.b
Guards
Guards (SFD 154/221)
Death from Below
Death from Below (UNL 186/219)

Specified that you can choose whether or not to perform the reflexive trigger when it says “you may” in the first part of the effect (after the “do this” part). This isn’t a change to how such effects were already perceived and played previously.

This can be applied to cards like <<Guards>> or <<Death from Below>>.

“Deal X… for each…”

Rule 418.8

Specified that dealing X damage “for each…” is conglomerated into a single instance of damage and not split up into several.

Instructions affecting Play as a Limited Action

Rule 312.1.b.1

Formalized how the limited action of Play may be modified by instructions directing you to perform it. It was previously understood to work in this way; however, there are now rulings on which to base that understanding.

Empowering Multiple Times

Rule 442.1.c.1
Kayle, Justified
Kayle, Justified (VEN 134/166)

For Game Objects that can be Empowered multiple times, Empowered is a Stacking Status (disempowering such a Game Object still causes only one instance of Empowered to be removed).

Furthermore, if a Game Object with an Empower Activated Ability has permission to be Empowered multiple times, it ignores the “Play only if not empowered” restriction of the Empower Ability.

Example You can activate <<Kayle, Justified>>’s Empower ability even if she has been empowered three times, though nothing will happen on resolution.

Start of Showdown Effects

Rule 466.2.b
Diana, Lunari
Diana, Lunari (UNL 079/219)
Moonfall
Moonfall (UNL 198/219)

The fix is only meant to prevent these effects from applying/triggering an additional time if the current Combat Showdown originally opened as a Non-Combat Showdown.

Example It’s my turn, I control <<Diana, Lunari>> and I move her to an uncontrolled battlefield. A Non-Combat Showdown starts there, so her Triggered Ability goes on the chain; it resolves. Using Focus, I play <<Moonfall>>, targeting that battlefield she’s currently on and one enemy unit in base; when it resolves, the Showdown becomes a Combat Showdown; 466.2.b checks that the current showdown did not open as a Combat Showdown, so Diana’s Triggered Ability will not go on the chain again.

Scoring VS Scoring Points

Rule 470.1 (473)
Trinity Force
Trinity Force (SFD 115/221)
Sumpworks Map
Sumpworks Map (UNL 085/219)
Otterpus
Otterpus (VEN 053/166)
Fundamental Distinction: “Scoring X Points” is NOT Scoring: it’s Gaining Points.

On card text, “Scoring” as a term by itself refers to the act of Scoring, and it results in a player Gaining Points.

Example 1 The resolution of <<Trinity Force>>’s appended ability does not cause <<Sumpworks Map>> to meet its trigger condition.
Example 2 Otterpus does not prevent Scoring Abilities from triggering, since its ability causes players to just replace the act of Gaining a Point.

Layers’ Evaluation and Update Timing

Section 479

Clarified that all Layers are evaluated at the same time (excepting non-looping object level Dependencies). Also see Object Level Dependency in Layers.

Deathknell’s Effect in Past Tense

Rule 808.1.c.2
Lonely Poro
Lonely Poro (SFD 036/221)
Example “If I died alone” in <<Lonely Poro>>’s Rules Text references the moment in which the Deathknell was added to the chain.
← More Rules Changelog All Articles Archive →