Riftbound Current Public Decklists: Post-Utrecht Meta Deck Workflow

This page is the current RiftStorm deck workflow for players who want real Riftbound decks without fake decklists.

Use Riftbound decks to search public builds, RiftStorm deck builder to rebuild or tune a shell, card database to verify card text, Riftbound counters to connect each deck to a matchup plan, and Riftbound guides when you need beginner or rules context.

The Riftbound meta is moving faster than the public decklist archive. Recent regional coverage gives useful competitive context, but not every public report exposes a full card-by-card export in text.

That creates a trap for content sites: it is easy to write a confident 40-card list that looks useful but is actually invented. RiftStorm should not do that. A fake list gives players bad testing reps, bad binder planning, and bad event prep.

The correct workflow is stricter:

That distinction is the difference between useful deck content and noise.

The current public deck workflow uses these source categories:

Important limitation: the current event reports are strong for meta context, but they should not be read as exact decklists unless the source publishes the full list. RiftDecks pages can expose text decklists and exports, but each page still needs date and set validation before it becomes a current meta reference.

A deck is exact only when you can point to the full card list.

A good exact source has at least one of these:

A source is not exact when it only says a legend finished well, a legend had a high conversion rate, a legend was popular, or a deck used a known card package. Those details matter, but they are not a decklist.

When you find an exact export, rebuild it in RiftStorm deck builder, verify the card text in card database, and save it as a public deck only after the list imports cleanly.

Current public coverage makes these the first decks to build, copy, or test against.

Azir Equipment Tokens

Azir is the first deck to respect because the current public reports put Azir at the center of post-Utrecht testing.

The shell to build is Calm / Order equipment tokens. The core question is whether your deck can beat equipment setup into Sand Soldier pressure without wasting removal on the wrong body.

Start the test shell with:

This is not a claimed exact 40-card list. It is the core package you need in the gauntlet so anti-token, anti-equipment, and source-removal cards get tested against the right problem.

Open the deeper matchup page at Azir Counter Riftbound, then build the gauntlet in decks or builder.

Viktor Recruit Engine

Viktor asks a different question than Azir. Instead of equipment-count pressure, Viktor tests whether your deck can answer repeated Recruit sources before the board becomes too wide.

Start the test shell with:

This is the minimum Recruit-source package. Add interaction, draw, and defensive tools only after you confirm the exact public list you are copying. The important test is whether your deck can identify the source card and remove it before spending premium answers on tokens.

Open Viktor Counter Riftbound when building sideboard plans.

Sett Buffed Midrange

Sett is a Body / Order midrange deck built around buff saves, conquest pressure, and punishing opponents who try to trade fairly.

Start the test shell with:

The reason this deck belongs in the gauntlet is simple: generic removal does not always line up into buffed units. You need to test whether your answers work before Sett spends the buff, after Sett spends the buff, and when the battlefield math changes mid-turn.

Open Sett Counter Riftbound for the counter plan.

Diana Spell Tempo

Diana remains a high-priority testing deck because the shell changes combat timing. A player who only counts visible units will lose to Moonfall, reaction-speed interaction, and Ambush pressure.

Start the test shell with:

The core test is not whether your deck can kill one unit. The core test is whether your deck can fight when Diana changes the battlefield, draws or filters into another spell, and makes one showdown decide the score.

Open Diana Counter Riftbound before tuning the gauntlet.

Rek'Sai Burrow Pressure

Rek'Sai pressure decks punish slow starts and bad battlefield placement. They are also easy to undertest because the exact public builds are less obvious than the headline Azir or Viktor shells.

Start the test shell with:

Do not overclaim the list. Use this package to test early pressure, follow-up bodies, and whether your deck can recover after losing the first meaningful battlefield.

Open Rek'Sai Counter Riftbound for matchup details.

Darius Legion Tempo

Darius tests second-card turns and resource compression. The deck can make ordinary combat math fail when Legion turns switch from setup into pressure.

Start the test shell with:

The main testing question is whether your deck can stop the second-card payoff before the battlefield turns into a forced trade.

Open Darius Counter Riftbound for the counter route.

Master Yi Tall Threat

Master Yi is not just a beginner trial deck. The current shell to respect is the tall-threat plan built around solo defense, protection, and one committed unit deciding the battlefield.

Start the test shell with:

Your deck needs to prove it can pressure early, hold a real reset, and avoid letting one solo defender control the whole game.

Open Master Yi Counter Riftbound for the full plan.

Annie Fury Chaos Pressure

Annie is the pressure deck that punishes players who keep slow hands and assume removal will line up later.

Start the test shell with:

The important test is whether your deck can survive the early pressure without using every card before the closing turn.

Open Annie Counter Riftbound for the matchup plan.

Use the Riftbound decks page in three passes.

First, search by exact legend. Start with Azir, Viktor, Sett, Diana, Rek'Sai, Darius, Master Yi, and Annie. If a public list exists, open it and check whether the card list is complete.

Second, inspect the card panel. If the list has a full card breakdown, export it and rebuild it in builder. If the card panel is only a core package, treat it as a testing shell.

Third, connect it to the matchup. Every gauntlet deck should have a paired counter page in counters. That tells you what the deck is trying to do, what card package creates the problem, and what your test deck needs to answer.

This workflow keeps deck search practical. You are not just browsing names. You are deciding what to build, what to copy, and what still needs validation.

Before calling a deck tournament-ready, check:

If any answer is no, keep the deck as research. Do not publish it as an exact list.

A source-backed package is still useful. It gives you the correct matchup texture, which is usually enough for early testing.

Build the package, then fill the rest of the list with cards that support the same job:

Then play focused games. Do not tune from vibes. Write down the card that actually changed each game, then adjust the shell.

The current Riftbound deck task is not to manufacture 40-card lists from thin air. The task is to make the public deck workflow useful.

Use exact public exports where they exist. Use source-backed shells when the public data only supports a package. For the post-Utrecht gauntlet, start with Azir, Viktor, Sett, Diana, Rek'Sai, Darius, Master Yi, and Annie. Build those shells in RiftStorm decks, verify the cards in card database, tune in builder, and connect every list back to a real counter plan.