Ozox, the Clattering King

A death trigger that refuses to close. Kill it, and it hands you Jumblebones, a legendary 2/1 whose own departure returns the King to your hand: two bodies and a rebuy stapled to a 3/2 attacker. The design is a closed cycle disguised as a single card. Neither half can block, which is the tax that pays for the resilience; this is aggression that keeps coming back rather than a body that trades and holds a lane. What makes the loop tick is the sequencing. The King has to die before Jumblebones exists, and Jumblebones has to leave the battlefield before the King comes back, so directing removal at either one advances the machine rather than stopping it. Critically, the recursion keys off Jumblebones leaving, not dying, so exile answers the King but not the token: bounce it, sacrifice it, exile it, and the return trigger fires all the same. Sacrifice fodder and recursion engines lean on exactly this: a creature you actively want dead, that generates a second creature you also want gone, that returns the first to be recast. The one seam is that the return targets Ozox by name, so the recursion only refills the King if a copy is waiting in your graveyard when Jumblebones goes. The Skeleton Noble framing sells it as a joke about a monarch who cannot be dislodged, and the mechanical joke lands the same way: the enemy is never quite finished with the King.