CardConveneSign inCommunity Beta
Guided example · beginner

Example: filter by domains first

See how a Legend turns a large catalog into a focused deckbuilding pool.

Rules 2026-07-16Reviewed 2026-08-11

Objective

Explain why the Legend should be selected before main-deck cards.

Before

The library is unfiltered

The player has not selected a Legend and is considering cards from every domain.

  • Legend: not selected
  • Chosen Champion: not selected
  • Domain filter: none
No deck identity has been established yet.
Action

Choose the Legend

The player selects an abstract Legend showing two domains.

  • Legend: selected
  • Chosen Champion: available
  • Domains: two identified
The Legend now supplies the deck's domain identity.
Resolution

Narrow the card pool

The player applies those domains to the library and reviews cards relevant to the deck.

  • Legend: selected
  • Chosen Champion: selected next
  • Library: matching domains shown
Unrelated domain choices leave the immediate browsing view.
Why

One decision guides the rest

Starting with the Legend reduces rework and keeps the selected champion and main deck connected.

  • Next task: choose Chosen Champion
  • Then: add matching main-deck cards
The player has a clear next action instead of a catalog-sized decision.

Reviewed sources

Learn to Play RiftboundAccessed 2026-08-11 · reviewed 2026-08-11How to Play: Get Started NowPublished 2025-06-06; accessed 2026-08-11 · reviewed 2026-08-11Riftbound Rules HubCore Rules last updated 2026-07-16 · reviewed 2026-08-11