Combo · ENGINE
The Candlelit Sanctum chooses which of the top two you draw next, and 431.1.c makes it safe with the deck empty
Pieces
- The Candlelit Sanctum ×1
OGN-291 · battlefield
When you conquer here, look at the top two cards of your Main Deck. You may recycle one or both of them. Put those you don't back in any order.
Payoff
Deck
- The Candlelit Sanctum is Colorless and it is the only card in this entry, so 103.1.b puts no constraint on the legend at all — any of the 49 names can run it. The constraint comes from whatever conquer engine feeds it.
Prerequisites
- IT MAKES YOUR NEXT DRAW A KNOWN CARD, WHICH THE REST OF THE FAMILY DOES NOT. Recycle one of the two and the other goes back on top by your own choice of order, and 315.4.b then draws it in your Draw Phase. The project's deck-manipulation survey concluded that 'no deck-manipulation card in the pool turns a draw probability into a certainty' because 416.1.a and 416.5 send recycled cards to the BOTTOM — that holds for tutoring a NAMED card, and this is the one card that refines it: you cannot choose from the deck, but you can choose which of the top two you take.
- AND IT IS SAFE WITH THE MAIN DECK EMPTY. 431.1.c: 'If an instruction directs a player to look at or reveal cards in excess to the number of cards in a player's Main Deck, that player looks at or Reveals as many as possible, but does not Burn Out, then proceeds with the rest of the instruction.' Looking is free where drawing (431.1.a) and milling (431.1.b) are not, so this is one of the few selection effects an empty-deck shell can run.
- IT IS LOOKING, NOT REVEALING, SO IT FIRES NOTHING. 424.1 makes revealing a public presentation; this clause says 'look at', so no 'as I'm revealed' payoff (SFD-175 Undertitan) and no opponent information is given up.
- RECYCLING IS TO THE BOTTOM AND BOTH AT ONCE IS RANDOM. 416.1.a sends Main Deck cards to the Main Deck and 416.5 says that two or more recycled simultaneously 'are placed on the bottom of that deck in a random order' — so recycling both is a genuine shuffle-away of two dead cards, not a stack you can plan around.
- IT NEEDS A REPEATABLE CONQUER AT THIS BATTLEFIELD, like every conquer battlefield: 315.2.b.2's mandatory Hold plus 470 mean one that is taken and kept fires exactly once. It puts no condition at all on the conquering body, so this walk's own sprite-queen-targon-peak-conquer-cycle satisfies it with a 3-Might Sprite — unlike sunken-temple-mighty-conquer-draw.
- IT ADDS NO CARDS. This is selection, not advantage; the entry produces card-advantage-engine because that is the nearest term in the vocabulary, and the honest description is that it removes two dead draws per Conquer and fixes the next one.
- THE CANDLELIT SANCTUM IS NOT GUARANTEED TO BE ON THE TABLE: 485.4.a, 485.5, 486.5 and 103.4.c as for every battlefield entry.
Steps
- Bring The Candlelit Sanctum as one of your three battlefields.
- Conquer it. 348.2.a.1 fires the trigger; look at the top two cards of your Main Deck.
- Recycle whichever you do not want — 416.1.a puts it on the bottom of the Main Deck — and put the one you do want back on top, which the clause lets you choose ('in any order').
- 315.4.b draws that card in your Draw Phase, so the next draw is a card you picked rather than one you rolled.
- If both are dead, recycle both: 416.5 puts them on the bottom in a random order, and the next two cards up are fresh.
- Give the battlefield up and retake it to repeat — the conquer engine this entry needs.
Per iteration
two dead cards buried and the next draw chosen, per Conquer at this battlefield, for no Energy and no cards
How it ends
engine only — pure selection at whatever rate the conquer engine supplies; it draws nothing, scores nothing, and 431.1.c means it never risks a Burn Out
Sources
Published elsewhere
- Riftbound Core Rules, Last Updated 2026-07-16 (data/Riftbound-Core-Rules-2026-07-16.txt) 2026-07-16
Walked here, in this project
- Hand walk 2026-09-07 (docs/phase0/walks/2026-09-07-uncatalogued-cards.md), issue #171 2026-09-07 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-07, issue #171 — the first entry to use OGN-291, and a one-card entry on purpose: the battlefield is the whole line and the partner is whatever conquer engine feeds it, which `needs` expresses better than a named card would. Card text verbatim from data/corpus_flat.txt. It refines rather than contradicts the project's standing 'no card turns a draw probability into a certainty' finding, and the refinement is stated in those terms so the two records agree. Trap check: 416.1.a and 416.5 are quoted so recycling is not imagined to stack the bottom; 424.1 is cited so looking is not mistaken for revealing; 431.1.c is quoted because it is what makes this usable in an empty-deck shell where 431.1.a and 431.1.b are not; the needs declaration is contrasted with sunken-temple-mighty-conquer-draw's extra Might condition; exactly one battlefield is named, so 485.4.a is respected.
Walked against Core Rules 2026-07-16