Card search syntax

Overview

Riftseer search supports a compact keyword language in the site search bar (including the quick-search palette). It targets Riftbound card fields: printed type and supertype (for example Unit, Gear, Spell, Champion, Rune, Legend), classification tags, rarity, artist, keywords, domains, stats, format legality, and the tokens a card creates. Only the constructs listed on this page are available today.

Combining terms

Terms next to each other are combined with AND. All of them must match unless you use or or group with parentheses.

Example: poro t:unit finds cards whose names match "poro" and whose type line, supertype, or tags match "unit" as a substring (case insensitive).

Card name words

Plain words (not tied to a keyword) search card names using full text matching. Multiple words become one name query, not separate unrelated filters.

Type, artist, and rarity

Use a keyword, a colon, then a value. You may quote values that contain spaces.

• t:value or type:value: matches printed type, supertype, or any classification tag.
• st:value or supertype:value: matches the supertype only (for example Champion, Signature).
• tag:value: matches classification tags only, without also matching the type line.
• a:value or artist:value: matches the illustrator name.
• r:value or rarity:value: matches rarity on the physical printing, not the shared oracle.
• name:value: matches the card name as a substring, unlike plain words which use full text matching.

These are substring based and case insensitive. Example: t:"champion unit".

Keywords

kw:value (or keyword:value) matches the [Keyword] badges printed in a card's rules text. Examples: kw:deathknell, kw:deflect, kw:accelerate.

Unlike the fields above, keyword matching is exact rather than substring, so kw:de finds nothing. Numbers printed on a badge are not part of the keyword's identity: kw:deflect matches [Deflect 1] and [Deflect 3] alike, and kw:"Deflect 3" means the same thing.

Comma separated values are an or: kw:deflect,shield is the same as (kw:deflect or kw:shield). Quote the value to search for a literal comma instead.

Domains

d:value (or domain:value) matches a card's domain. Cards may carry several domains, and d: matches if any of them is the one you named — so d:fury finds a Fury/Order card as well as a mono-Fury one.

Matching is exact and case insensitive, because domains are a small fixed set. Combine terms to require several at once, or use a comma list for alternatives:

• d:fury: has Fury among its domains.
• d:fury d:order: has both Fury and Order.
• d:fury,order: has either one.
• -d:fury: has no Fury domain at all.

To search on how many domains a card has, use a comparison instead of a colon: d>=2 finds multi-domain cards and d=1 finds mono-domain ones. The colon form always filters which domains; the comparison form always counts them.

Stats and numbers

energy, might and power accept the comparisons >, >=, <, <=, = and !=. Short forms e, m, p and the alias cost also work.

A colon means equals, so energy:2 and energy=2 are the same. Examples: might>=4, power<3, energy!=0, t:unit might>=4 tag:poro.

Cards with no value for a stat never match a comparison — not even !=. A Spell with no might is excluded by both might>=1 and might!=1.

Format legality

Search by a card's status in a play format, using the format's code:

• f:standard or legal:standard: legal in that format.
• banned:standard: banned there.
• notlegal:standard: not legal there (for example, not in the card pool).

Cards are legal by default: only non-legal statuses are recorded, so f:standard matches every card with nothing stored against it. A printing-specific status wins over the card-wide one. An unrecognised format code matches nothing rather than everything.

Tokens created

produces:value (or makes:value) matches cards that create or reference a token by name. Matching is substring based, so produces:gem finds anything making a Gem token.

Card flags

is:value filters on printing properties. Negate any of them with -.

• is:token: the card is itself a token
• is:signature (or is:sig): a signature printing
• is:alternate (or is:alt): alternate art
• is:overnumbered: collector number beyond the set's base count
• is:special (or is:showcase): a special-collection printing, numbered on its own track such as SP3
• is:foil: available in a foil finish
• is:manual: added by an editor rather than ingested

Example: t:unit -is:token excludes unit tokens from a unit search.

Exact names

Prefix with ! to require one exact normalized card name. Use quotes for multi-word names. Examples: !poro, !"Sun Disc".

Negation

Put - before a term to negate it. Spacing before the keyword is optional. Examples: -t:token, - r:rare.

Using "or"

The lowercase word or combines alternatives. Implicit AND still binds tighter than or. Example: t:gear or t:spell.

Parentheses

Group conditions when mixing AND and OR. Example: t:unit (a:lee or a:kim).

Set filter

Use set:value (or s:value) to restrict results to a specific set by its code. The value is matched case-insensitively. Example: set:OGN t:unit finds units from the Origins set.

All printings

By default, results contain one oracle per card, displayed through the printing that matched. To return one result per physical printing — including art variants and reprints — add unique:prints or the shorthand ++ anywhere in the query.

Examples: poro unique:prints, poro ++.

Ordering

Add order:field to sort results client-side. Combine with direction:asc (default) or direction:desc to control the direction. Null values always sort last regardless of direction.

Valid order fields:

• collector: collector number within the set (default when browsing a set)
• energy: card energy cost
• power: card power value
• might: card might value
• rarity: print rarity, in printed order — common, uncommon, rare, epic, showcase
• artist: illustrator name
• usd: TCGPlayer USD price
• eur: Cardmarket EUR price
• domain: primary domain
• set: set code

Example: poro order:energy direction:desc shows poro cards sorted by energy, highest first.

Limits

Queries are capped for safety (total length, nesting depth, number of parts, and length of individual values). If a query goes past those bounds, search shows an error instead of trimming it quietly.

Where else this syntax is used

Editors can attach a ruling to a saved query rather than to individual cards, using exactly the language on this page. A ruling scoped to t:unit kw:deathknell covers every unit with that keyword, and is re-evaluated whenever new cards are added — so cards printed later pick it up without anyone editing the ruling. Anything you can search for, a ruling can target.

Try it

Open Search or use the keyboard shortcut from the header to try these queries.