All rulings / Judge chat /

"Once Per Chain" Activation Caps And Pending Negation

73_once_per_chain_activation_cap_pending_negation.md

"Once Per Chain" Activation Caps and Pending Negation

Some effects can be activated only once per Chain. Once such an effect has been put onto the

current Chain, it cannot be activated again as a later Chain Link of that same Chain, even by

the same card. This cap is distinct from a "once per turn" limit (see

Activation vs. Effect Negation) and from the structural

SEGOC hand-Summon rule (see One Hand-Summon Trigger Per Chain).

Where a once-per-Chain cap comes from

  • Printed wording: "You can only activate this effect of '[Card]' once per Chain," or modern

"You can only use each of the following effects of '[Card]' once per Chain."

  • By official ruling on older cards that predate that template. Example: Skull Lair.

> Skull Lair — "Remove from play any number of Monster Cards in your Graveyard to destroy 1

> face-up monster on the field whose Level is equal to the number of the cards you removed from

> play." (Continuous Trap Card.)

Skull Lair's printed text has no per-Chain clause, but Konami's official card ruling states its

effect cannot be activated multiple times in the same Chain (Konami card-database ruling,

mirrored on Yugipedia Card Rulings: Skull Lair).

  • By the structural SEGOC rule for hand-Special-Summon triggers — covered separately in

file 64.

A negated activation still consumes the per-Chain cap

The cap is keyed to activating the effect, not to the effect successfully resolving. Putting

the effect on the Chain is an activation even if it is later negated. So negating the first

activation does not free up a second activation in the same Chain — exactly parallel to the

per-turn "You can only activate 1 …" rule, where a negated effect still counts but a negated

activation of a per-turn limit does not (see file 09).

For a per-Chain cap the activation already happened on this Chain, so the cap is spent for the

rest of this Chain regardless of negation.

The timing trap: the negation has not resolved yet

The common wrong reason given for "you can't re-activate" is *"the card has already been negated /

destroyed."* That reasoning is incorrect, because a card chained to negate your effect resolves

after you would add your re-activation, not before.

Worked example — Skull Lair vs. Herald of Purple Light.
Player A activates Skull Lair's destroy effect as Chain Link 1. Player B chains
Herald of Purple Light as Chain Link 2:
> "When your opponent activates a Trap Card (Quick Effect): You can send this card and 1 other
> Fairy monster from your hand to the GY; negate the activation, and if you do, destroy it."
Can Player A activate Skull Lair's effect again as Chain Link 3?
No. But the reason is the once-per-Chain cap, not the negation. At the moment CL3 would
be built, Herald (CL2) has not resolved, so Skull Lair is still face-up on the field
and not yet destroyed. If Skull Lair had no per-Chain cap, "still on the field" would
mean it generally could be chained again. The dispositive blocker here is that its effect was
already activated once on this Chain.

Judge calls to watch for

  • Don't justify "can't re-activate this Chain" with "it's already negated/gone." Check the

per-Chain cap first; the negating card usually hasn't resolved when the re-activation is offered.

  • A negated activation still spends a once-per-Chain cap. It does not spend a per-turn

activation limit (file 09) — keep the two limits separate.

  • "Once per Chain" ≠ "once per turn" ≠ "hard once per turn." Read the exact wording or the card's

official ruling.

Sources

  • Konami official card-database ruling for Skull Lair ("cannot be activated multiple times in

the same Chain"), via Yugipedia Card Rulings: Skull Lair.

  • Herald of Purple Light current TCG card text.
  • The Judges' Lounge thread, June 2026 (Skull Lair vs. Herald) — used only to locate the

interaction; verdict verified against the official ruling above, not the thread.

What's new

  • Added to corpus via the YGOResources rulings sweep.