Combo · ENGINE
Sett, Kingpin under one mass buff — six buffed bodies read at once
Pieces
- Sett, Kingpin ×1
OGN-240 · payoff · order
[Tank] (I must be assigned combat damage first.) I get +1 Might for each buffed friendly unit at my battlefield.
- 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.)
Payoff
Deck
- Both mono-Order (103.1.b.3), so any legend carrying Order runs the pair.
- Sett and the garrison must be at the SAME battlefield — his count is 'at my battlefield', unlike Ivern's 'your units'.
Run play
Prerequisites
- Arithmetic against the declared board, before authoring. Sett is M5. Peak Guardian played to his battlefield with four other bodies already there buffs six units in total — himself, Sett and the four — so Sett reads six buffed friendly units at his battlefield and stands at M11, as a [Tank] that 815.1.b makes the compulsory first recipient of combat damage.
- 702.3 ('There can only be one Buff on a Unit at a time') is what makes the count honest: a second mass buff adds nothing to bodies that already carry one, so the ceiling is how many UNBUFFED bodies stand there, not how many buffers you play. That is the #106 finding stated on the other side of the transaction.
- A body that dies takes its buff with it (705: 'If a Unit leaves play, remove all Buffs from it'), so Sett shrinks as the garrison is cleared — which is exactly backwards for a [Tank] and is the honest weakness of the line. Peak Guardian is a one-shot ETB and cannot re-buff.
- Sibling, deliberately kept separate: sett-kingpin-karma-army-might-wall grows the same counter one buff a turn off OGN-235 Karma, Channeler, unbounded but slow. This is the one-card, one-turn version, and the two are alternatives rather than halves of one line — a deck can run both, but neither needs the other.
- Peak Guardian's second sentence is live because 355.2.a lists 'a Battlefield the controller controls' among the default valid play locations. That was the #111 correction to the #100 hunt, which had called the clause dead letter.
- THE SIX IS AN ILLUSTRATION, NOT A REQUIREMENT, AND THE ENTRY SHOULD NOT CARRY AN `anyBodies` ROW (ruled 2026-09-13, #200). A body-requirement sweep proposed this line at count 4 on the strength of `terminatesIn`’s *"six is M11 on the declared board"* — a board `uses` does not declare. **REFUSED, because the mechanism works at ANY garrison size**: `OGN-223 Peak Guardian` buffs all other friendly units there (702.2.a) and `OGN-240 Sett, Kingpin` reads his `[Tank]` Might off the buffed bodies beside him, so the pair is live at two and the six is a worked figure rather than a condition. `anyBodies` means the line CANNOT RUN without the bodies — the same test that keeps `sprite-queen-dusk-rose-lab-shard-undoing` out of the field, where the entry itself calls its second body *"a deckbuilding choice, not a requirement"*. What IS owed is the smaller thing: the M11 figure is stated ON AN ASSUMED BOARD, and 705 shrinks it as the garrison dies, which the `terminatesIn` already says.
Steps
- Assemble a garrison at a battlefield you control with Sett, Kingpin among them and the other bodies unbuffed.
- Play Peak Guardian to that battlefield (355.2.a). He buffs himself, then every other friendly unit there — 702.2.a places one buff each, 702.3 refuses a second on anyone who already has one.
- Sett's continuous ability re-reads the board: +1 Might for each buffed friendly unit at his battlefield. With six buffed bodies present he is M11.
- [Tank] (815.1.b) makes him the compulsory first recipient of combat damage, so 465.2.c.3's lethal-in-full rule forces the attacker to spend 11 on him before anything else there takes a point.
- Conquer or hold from behind that wall; 466.5.d or 469.2 pays, not this line.
How it ends
engine only — a [Tank] at Might 5 plus one per buffed body at his battlefield, six is M11 on the declared board, shrinking as the garrison dies (705). 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 §26), issue #153, from the orphan rule sett-kingpin-mass-buff. Card text verbatim from data/corpus_flat.txt. Citations opened: 103.1.b.3, 355.2.a, 465.2.c.3, 466.5.d, 469.2, 702.2.a, 702.3, 702.3.a, 703, 705, 815.1.b. Formula checked against its own declared quantities before authoring: Peak Guardian plus Sett plus four other bodies is six buffed units at that battlefield, so Sett is 5 + 6 = 11. Trap check: no attack is claimed for the entry itself; no [Repeat]; no [Temporary]; no token; no recall — and 705 is stated as the weakness rather than hidden; nothing added in Awaken, so 167 does not bite. Depends on no unruled reading.
Walked against Core Rules 2026-07-16