Ornn Counter Riftbound: How to Beat Fire Below the Mountain

Ornn is the gear-engine matchup. It is lower priority than Azir, but the counter skills overlap: pressure setup, disrupt equipment, and answer the source before the engine becomes battlefield pressure.

Use Riftbound Counters, search Ornn, gear, Equipment, and Weaponmaster in the card database, test packages in the deck builder, and validate public lists in Riftbound decks.

What Ornn Is Trying To Do

Ornn - Fire Below the Mountain adds a rainbow rune for gear or gear abilities. Ornn's Forge discounts the first non-token gear each turn while controlled. Ornn - Blacksmith finds gear. Ornn - Forge God has Deflect 2, Weaponmaster, and gains Might for each friendly gear.

The deck wants gear density to become both resources and battlefield stats.

Pressure before gear setup is safe. If Ornn spends early turns assembling equipment without losing battlefields, Forge God becomes much harder to answer. Use gear interaction if your domains have it. Otherwise, answer the equipped unit or bounce after equipment is committed.

Keep early pressure and one answer to a gear carrier. Ship hands that only answer small units.

Early game: make Forge or Blacksmith setup cost points.

Mid game: disrupt the first big equipment turn.

Late game: keep hard interaction for Forge God and count Deflect 2 before targeting.

Search Ornn - Fire Below the Mountain, Ornn - Forge God, Ornn - Blacksmith, and Ornn's Forge in the card database. Then search your domains for gear removal, bounce, recall, hard removal, and pressure that punishes setup.

No exact Ornn list is attached here. Current public sources support Ornn as lower-priority coverage, but accessible text does not expose a full export.

Bring 2 gear answers or setup punishers, 2 source-unit answers, 2 early pressure cards, 1 tempo reset, and 1 flex slot.

Aggro And Pressure Decks

Your job is to make Ornn spend resources defensively. Do not race blindly; force the opponent to answer a battlefield before their best setup turn is ready. Keep one cheap interaction piece for the first swing that would actually change the score.

Midrange Decks

You usually have the cleanest counter tools, but you can still lose by trading too fairly. Identify the source card, hold the premium answer for the payoff turn, then turn the corner immediately instead of passing back with no pressure.

Control Decks

Do not keep hands that only become good after the matchup is already stable. You need early speed bumps, one efficient answer, and a plan to stop the card that turns Ornn's setup into repeated points.

Engine And Combo Decks

Buy one clean setup turn without giving up the whole map. If your engine takes time, pair it with early contest bodies or cheap disruption so Ornn cannot choose every fight before your payoff is live.

Use Riftbound Counters to compare this matchup against adjacent threats. Search the named cards in the card database, build both the enemy shell and your counter package in the deck builder, and check Riftbound decks for exact public exports before copying a list into tournament prep.

Do not test this matchup against a vague pile. Build a focused Calm / Mind gear engine gauntlet shell so your counter plan faces the actual pressure pattern: gear discounts and Forge God scaling.

Key cards to add to the test shell:

This is a testing package, not a claimed exact tournament list. If a full public export is available in Riftbound decks, use that exact list. If it is not available, start with these verified card names and tune counts only after games.

Use this as the public-deck workflow for Ornn:

Your answer package should have jobs, not random tech cards:

A practical 8-card sideboard starts with two early contest cards, two clean answers to the source or payoff card, two tempo resets, one recovery card, and one local flex slot. Adjust the split only after you know which exact card is deciding games.

Run at least five focused games before calling the matchup solved:

Use the Riftbound Counters hub to pair this guide with adjacent matchups, then save the tuned list in the deck builder.

This is the section to use when the basic matchup notes are not enough. Build the enemy shell as Calm / Mind gear engine and make sure it can present gear discounts, Forge God scaling, and Deflect. If your test version cannot do that, your counter results are not useful yet.

What You Are Actually Testing

The dangerous pattern is simple: gear setup becomes both resources and Might. The turn to beat is usually the first Forge God or discounted gear turn. Your counter package should be judged by whether gear disruption and bounce after equipment commits works before the score changes, not after.

Card-By-Card Threat Map

Do not treat these as a complete decklist unless you have a public export in front of you. They are the verified cards that create the matchup texture. Use Riftbound decks for exact public lists when available, and use card database to confirm text before adding substitutes.

Opening Hand Templates

A keepable hand into Ornn usually has three parts:

A bad hand is the opposite: slow value, narrow removal, and no way to force Ornn to react. Ship that hand even if every card looks powerful in a different matchup.

Board-State Drills

Run these scenarios in the deck builder test gauntlet:

After each drill, write down the exact card that changed the game. If the answer is vague, the sideboard plan is not ready.

Sideboard Mapping

Map your eight cards by job:

That last slot should change week to week. The first seven should not change unless testing proves a specific job is unnecessary.

Exact Decklist Status

No exact Ornn list is invented here. Where public coverage exposes a full export, use it. Where coverage only gives tier, finish, conversion, or card-package evidence, treat this as a validated testing package and confirm exact counts before tournament registration.

Ornn is beatable when you attack setup. Pressure early, disrupt gear, and answer Forge God after the Ornn player commits resources.