Riftbound tokens: playing and representing them
On this page
Riftbound tokens are game objects created by spells or abilities during play. You do not need the official printed token to represent one, but the representation must make its identity, location and state understandable. Permission to represent tokens does not authorise homemade replacements for cards in your deck.
A unit token follows unit rules unless its creating effect specifies otherwise. When it moves to a Non-Board zone other than the Chain, it ceases to exist immediately after that movement. It cannot remain in your hand or trash as a card to retrieve later.
A game object rather than a deck card
The rules distinguish tokens from cards. An object created as a token retains that nature even if its physical representation resembles an ordinary card. The cardboard reminder does not independently determine the object's game characteristics.
Consequently, printed tokens are not added to the Main Deck as ordinary units during construction. Keep them separately and use them when an effect creates the relevant object. Owning a printed Recruit does not permit putting it on the board without an instruction authorising that creation.
Being a token does not make the object irrelevant to normal rules. It has a type and follows that type's requirements. A unit token can participate in combat, receive damage and be affected by effects concerning units, subject to its state and applicable conditions.
The rules allow tokens to be played where their type and creating procedure use that process. Do not import an absolute rule from another game saying tokens can never be played. Read how Riftbound creates the object and which steps or modifications apply.
Reading the creating effect
First establish how many objects are created, their types and characteristics. Then check where they can appear and whether their entry state differs from the normal state. An instruction creating a ready unit must not be resolved as exhausted, or vice versa.
A unit token normally enters exhausted under the rules for that type unless another instruction applies. Creation does not automatically grant a free move or permission to ignore restrictions. Show ready and exhausted states as clearly as you would for a unit represented by an ordinary card.
The effect can restrict location, grant temporary abilities or modify characteristics. Choosing a reminder with the correct printed name is not enough if you ignore the creating text. That text may explain the difference between two tokens that otherwise look identical on the board.
Normally, the controller of the creating spell or ability controls the token unless its type or the instruction specifies otherwise. Supplying the physical cardboard does not make you the controller. Lending another player a token reminder does not transfer the created object to you.
Examples and their characteristics
The Riftbound core rules define several token models. Recruit, Mech and Sprite are not interchangeable names for one generic piece: their different characteristics can matter to effects.
| Token defined in the rules | Might | Characteristics to represent |
|---|---|---|
| Recruit | 1 | Domainless unit with the Recruit tag |
| Mech | 3 | Domainless unit with the Mech tag |
| Sprite with Temporary | 3 | Domainless unit with Fae and Temporary |
| Sand Soldier | 2 | Domainless unit with the Shurima tag |
These values describe the model, not a promise that current Might never changes. A later effect can modify it. Keep the base value distinct from an applied change, especially when several tokens of one model receive different bonuses.
Temporary has a precise operation: at the start of its controller's Beginning Phase, before scoring, the ability kills that permanent. Do not simplify it to disappearance after combat or an unspecified one-turn duration. The actual point in the turn sequence matters.
Representing tokens without official printings
An identified card, object or other mutually understood reminder can work. The important information includes type, quantity, location, state and relevant modifications. An attractive object understood only by its owner can still make the board confusing despite the broad representation permission.
For a unit, an orientable reminder displaying name and Might often communicates better than an indistinguishable coin. If you use dice, explain what each die represents. One die should not alternate between token quantity and Might without a clear indication.
Separate tokens in different places. Three Recruits at your Base and two at a Battlefield should not appear merely as one die showing five. Location affects available actions and applicable effects, so it is more than an aesthetic detail.
At an event, show the organiser any representation likely to cause questions. Flexible rules do not remove the need for an understandable state. Prepare readable materials and enough reminders for the objects your actual deck can produce.
Identical tokens may need individual tracking
Grouping can simplify a board when all objects share location and state, but you must distinguish them as soon as one changes. If one becomes ready while another remains exhausted, a single shared orientation no longer communicates the whole state.
Damage and modifications create the same issue. A token with added Might or marked damage must not be confused with an unchanged one. Give it an individual reminder or separate the group before proceeding to a decision affected by that difference.
When removing an object, specify which one leaves. “One of the three” is insufficient if only one carried a particular ability or modification. Clear identity prevents private memory replacing visible information when an opponent needs to choose an affected object.
Also distinguish available reminders from existing tokens. A pile of printed tokens beside the mat is not a reserve in play. Only objects created through relevant effects exist in the game state; the rest are materials available for future instructions.
For multiple token models, avoid identical unlabelled counters. A Recruit and a Mech can have different Might and tags even when both are currently exhausted in the same place. Distinct labels reduce the need to reconstruct identity from the order in which they were created.
What happens outside the board
Tokens can exist on the board and on the Chain. If one moves to another Non-Board zone, it ceases to exist immediately after arriving. The sequence matters: this is not a rule that the movement never occurs, but a rule that the token does not remain in that zone.
A unit token killed and moved to the trash does not remain there as a recoverable card. If an effect returns it to hand, you do not receive a token card to save and replay later. Remove its physical reminder when the object ceases to exist.
A recycled token follows the recycle destination appropriate to its type, but cannot remain there either. Do not physically shuffle its reminder into the Main Deck or Rune Deck. Return the representation to your auxiliary materials once the game object has ceased to exist.
Effects observing movement or results still follow their text. Do not retroactively erase the event because the token disappears afterwards. If an interaction depends on that distinction, identify the movement and disappearance timing before asking for a ruling.
Costs, domains and later modifications
Tokens have no cost by default, with their cost treated as zero for applicable purposes. That does not make the spell creating them free. Pay the creator's or ability's actual cost unless an effect gives another instruction.
Tokens also have no domains by default. Applied effects can append domains or costs, including through copying or other modifications recognised by the rules. Avoid the absolute claim that a token must always cost zero and can never have a domain.
When an interaction checks Might, tag, domain or cost, use the object's current characteristics. The illustration on the reminder does not outrank what the creating and modifying effects establish. A clearly written marker can record the change without obscuring relevant information.
The distinction is particularly useful with copied tokens. A printed generic reminder may not display every copied characteristic. Make those changes understandable rather than insisting the reminder's original text controls an object that the game has modified.
Preparing a token-producing deck
Check which models each card can create and bring reminders that distinguish them. Add markers for damage, modifications and state where required. Preparation avoids stopping every resolution to find an object that can serve as a temporary substitute.
During play, announce creation, location and state, then recount after movement or destruction. That routine helps more than acquiring one particular illustration. Official tokens can be appealing collectibles, but representation quality follows clarity rather than purchase price.
Frequently asked questions
Must I own the official token to use a card that creates it?
No. The rules allow other representations, provided the object and its state are understandable. This does not authorise proxies of ordinary deck cards; the permission concerns representing tokens created during play.
Can a token return to hand and be played later?
It does not remain there. Moving to a Non-Board zone other than the Chain causes it to cease to exist immediately after movement. Remove the reminder instead of adding it to your hand as a future card.
Are all tokens units with one Might?
No. Different models and types have characteristics defined by rules and creating effects. Recruit has 1 Might, while the described Mech and Sprite have 3. Check tags, abilities and current modifications as well as the base number.