Combo · ENGINE
Peak Guardian into Albus Ferros — five Power that costs no runes
Pieces
- Peak Guardian ×1
OGN-223 · engine · order
When you play me, buff me. Then, if I am at a battlefield, buff all other friendly units there. (To buff a unit, give it a +1 Might buff if it doesn't already have one.)
- Albus Ferros ×1
OGN-230 · payoff · order
When you play me, spend any number of buffs. For each buff spent, channel 1 rune exhausted.
Payoff
Deck
- Both cards are mono-Order, so 103.1.b.3 admits them under any legend carrying Order: 'If a card has a single Domain, then that card is permitted in the Domain Identity'. Neither is Signature, so 103.2.d.2 forces no legend.
- Peak Guardian must be played to a battlefield you control, with other friendly units already there. Four other bodies is five buffs.
Prerequisites
- The naive reading of Albus is a RAMP — N buffs into N extra runes on the board — and it is wrong. 430.1 channels 'from the top of a player's Rune Deck' and 430.3 says 'If there aren't sufficient runes in the Rune Deck, channel as many as possible.' A deck channelling 2 a turn (315.3.b) is at 10-12 runes by the turn it can afford E10, and the Rune Deck is nearly empty. The naive line channels 2.
- What makes it real is 161.2.b — 'When a Rune is Recycled it is returned to the Rune Deck, not the Main Deck' — read with 164.2.b, 'Recycle this: [Reaction] — Add [C]', a cost with NO exhaust in it, so a rune already tapped for Energy still pays it. Recycle five exhausted runes for 5 Power, then let Albus channel five back. The rune count ends where it started and the Power was free.
- Rate: E10 + 1 Order Power and two cards for 5 Power, against the project's ~9 Energy per Power for a loop (issue #21's ledger). About 2 Energy per Power, and it leaves an M5 and an M3 on the board.
- The honest limit is 430.1: the runes come back FROM THE TOP of the Rune Deck, so the count is restored but the domains are not chosen. A line that needs five Power of one named domain cannot lean on this.
- Not a loop. Albus's trigger is 'When you play me', so it is once per copy — three castings a game (103.2.b), and each needs its own bank of buffs.
Steps
- Tap ready runes for Energy (164.2.a) to pay for the turn. They are now exhausted.
- Play Peak Guardian to a battlefield you control (355.2.a). He buffs himself and every other friendly unit there — five bodies present is five buffs (702.2.a), and 702.3 stops any of them doubling up.
- Recycle five of the EXHAUSTED runes for 5 Power (164.2.b; the cost is 'Recycle this', with no exhaust in it). 161.2.b returns them to the Rune Deck.
- Play Albus Ferros and spend the five buffs (702.2.b). Channel five runes exhausted (430.2's own worked example is this wording). The board is back to the rune count it started the turn with.
- Spend the 5 Power in the same Main Phase. 167 empties the Rune Pool at the START of the Main Phase, so nothing here is carried across a phase boundary.
How it ends
engine only — five Power for E10 + 1 Order Power with the rune count unchanged, once per copy of Albus (three a game). Nothing here scores.
Sources
Published elsewhere
- Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt) 2026-07-16
- Issue #153 (GitHub) 2026-09-06
Walked here, in this project
- Hand walk 2026-09-06, issue #153 — the 55 synergy rules no catalogued entry stands on 2026-09-06 record
How this entry was audited
REFUTE = a refutation pass, with its date and verdict · WOUNDED = the pass found a flaw and the entry was rewritten · BUDGETED = the pass checked the recycle-and-draw ledger · lens = the hunt that proposed it.
HAND-WALKED 2026-09-06 (docs/phase0/walks/2026-09-06-orphan-synergy-rules.md §1), issue #153, from the orphan synergy rule albus-ferros-buff-bank. Card text verbatim from data/corpus_flat.txt. Citations opened in the Core Rules file: 103.1.b.3, 103.2.b, 103.2.d.2, 161.2.b, 164.2.a, 164.2.b, 167, 315.3.b, 355.2.a, 430.1, 430.2, 430.3, 702.2.a, 702.2.b, 702.2.b.1, 702.2.b.2, 702.3, 703. The walk's own first reading (Albus as a rune RAMP) was refuted by 430.1 + 430.3 and replaced by the refill reading; that correction is the entry. Trap check: no attack and no Attacker designation; no [Repeat]; no [Temporary]; no token anywhere, so 185 / 186.1 / 416.1 never arise; no recall, so 455 and 808.1.d.1 do not bite; nothing is added in Awaken, so 167 does not bite; no battlefield of yours is required, so 190.1 / 190.6.d and the 485.5 random draw do not apply. Depends on no unruled reading.
Walked against Core Rules 2026-07-16