Name Matching and "All Cards With That Name"
Many effects that interact with the Graveyard use the phrase "the same name" or "with the same name." This is a name-matching operation: the effect collects every card with the specified original printed name in the designated zone, then applies the action (banish, shuffle, destroy) to all of them at once.
Karma Cut and the Graveyard banish clause
Karma Cut — "Discard 1 card, then target 1 face-up monster your opponent controls; banish that target, then banish all cards with the same name as that monster from your opponent's Graveyard."
Breakdown:
- Cost: discard 1 card (before the semicolon; paid on activation).
- Target: 1 face-up monster the opponent controls.
- Effect on resolution:
1. Banish the targeted monster.
2. Banish every card in the opponent's GY with the same name as the target (including any card whose name has been changed to match by a "name becomes" / "treated as" clause).
Clause 2 matches all cards by name, regardless of which were there first, how many copies, or what form they're in (Normal, Effect, whatever — as long as the operative name matches).
SPYRAL archetype quirk — "SPYRAL Super Agent" name reach
Name matching is exact — it operates on the entire operative card name, not a prefix or substring. The "SPYRAL" prefix on every monster in the archetype is irrelevant by itself; only cards whose operative name actually equals "SPYRAL Super Agent" qualify for a name match against that target.
The wrinkle: a few SPYRAL cards carry a continuous "name becomes 'SPYRAL Super Agent'" clause that activates while they sit in specific zones. While that clause is in force, the card is treated as having the name "SPYRAL Super Agent" for any check (including Karma Cut's GY-name match).
Worked example
"Anthony's Karma Cut is activated targeting Daniel's face-up SPYRAL Super Agent. Daniel has SPYRAL Super Agent, SPYRAL Tough, and SPYRAL Double Helix in his GY. Which cards will be banished by Karma Cut?"
— Answer: The targeted on-field SPYRAL Super Agent, plus SPYRAL Super Agent, SPYRAL Tough, and SPYRAL Double Helix from the GY. Karma Cut banishes the on-field target, then banishes every card in the opponent's GY whose name matches "SPYRAL Super Agent." SPYRAL Tough and SPYRAL Double Helix each have a "name becomes 'SPYRAL Super Agent' while in the GY" clause, so they qualify alongside the printed-name copy of SPYRAL Super Agent.
A name/text change applies only where its granting text reaches — usually the field only
When a card changes another card's name (or grants ongoing text), that change is a continuous effect that applies only in the location(s) the granting text specifies. If the text does not extend the change to the GY/banishment, the change stops the instant the card leaves the field, and the card reverts to its original printed name in the GY/banished zone.
Red-Eyes Fusion — "Fusion Summon 1 Fusion Monster … and if you do, its name becomes 'Red-Eyes B. Dragon'."
This name change is applied to the Fusion Monster while it is on the field. Red-Eyes Fusion does not say the name persists in the GY, and as a general rule a monster in the GY is treated as a distinct object from the same monster that was on the field — ongoing field effects don't follow it down. So once that monster (e.g. Archfiend Black Skull Dragon summoned via Red-Eyes Fusion) is sent to the GY, it is Archfiend Black Skull Dragon again, not "Red-Eyes B. Dragon."
"I Fusion Summoned Archfiend Black Skull Dragon with Red-Eyes Fusion, so its name is 'Red-Eyes B. Dragon'. When it's sent to the GY, is its name still 'Red-Eyes B. Dragon' so 'Red-Eyes' GY effects can use it?"
— Answer: No. The name change is a field-only continuous effect from Red-Eyes Fusion; it ends when the monster leaves the field. In the GY it is Archfiend Black Skull Dragon. The reasoning "the spell didn't say 'while on the field', so the name sticks" is backwards — a name-changing effect reaches the GY only if its text explicitly says so (compare the SPYRAL "name becomes … while in the GY" clauses above, which do extend the change to the GY).
The decision rule: a "name becomes X" / "treated as X" clause reaches a zone only if its own wording names that zone. Default scope is the field. Don't carry a field name-change into the GY/banishment unless the granting text says it applies there.
Archetype membership is by official designation, not by a name substring
A card belongs to an archetype only if it is officially designated a member — not merely because its printed name contains or resembles the archetype's name string. Archetype support ("add 1 '[Archetype]' monster", "'[Archetype]' monsters you control gain…") collects cards by membership, which is decided by Konami's designation, not by string-matching the title.
The reverse also holds: a card can be a member of an archetype without the archetype word in its name (when its text or official designation says it is always treated as a member), and a card whose name contains the word can be excluded (e.g. by an explicit "this card is not treated as a '[Archetype]' card" line, or because the resemblance is coincidental).
Synclone Resonator — despite the near-identical look to "Synchron," it is NOT a "Synchron" monster, so it is not searchable by "Synchron" support such as Tuning. The Japanese name (シンクローン) differs from "Synchron" (シンクロン) by one character.
"Can Tuning add Synclone Resonator from my Deck (it sounds like a Synchron card)?"
— Answer: No. Tuning searches "Synchron" monsters, which means members of the Synchron archetype; Synclone Resonator only resembles the name and is not a Synchron member. Don't infer archetype membership from a name that merely looks like the archetype — check the official designation. Conversely, do not deny membership just because the name string is unusual when the card is officially a member.
This is distinct from the name-matching operations above: those compare the literal (printed or "treated as") name string in a zone; archetype membership is a separate property a card either has or lacks regardless of how its name reads. Keep the two checks separate when ruling on searchers and archetype buffs. See also the resolver guidance not to tag mechanic/archetype words as card names ([[01_psct_colon_semicolon_cost_target_activation_timing]] vocabulary discipline).
Judge calls to watch for
- A "name becomes / treated as [Name]" change reaches the GY/banishment only if the granting text says so (e.g. "while in the GY"). A bare "its name becomes X" from a summoning Spell like Red-Eyes Fusion is field-only and reverts to the printed name once the card leaves the field.
- Archetype membership ≠ name substring. A card is a member only if officially designated; a look-alike name (Synclone Resonator vs "Synchron") does not make it searchable/supported by that archetype, and a card can be a member without the word in its name. Do not infer membership by matching the archetype string against the title.
- "Treated as [Name]" clauses are applied continuously while the card is resolving the check; they do not persist in unrelated zones unless the "treated as" text applies in all zones (some do, some don't — read carefully).
- Name matching ignores ATK/DEF, Level, and archetype membership; only the (treated or printed) name string matters.
- Effects that banish by type or attribute instead of name (e.g., some Phantasm Spiral effects) are distinct from name-matching effects and follow different resolution rules.
Sources
- Konami card-specific rulings for Karma Cut and SPYRAL monsters
- https://yugipedia.com/wiki/Karma_Cut
- db.ygoresources.com Q&A 20694: a card officially "treated as a '[Archetype]'" (e.g. Edge Imp Frightfuloid treated as a "Frightfur" card) counts for that archetype's "if you have a [Archetype] in the GY" presence/count conditions, even though the archetype word is not in its printed name. https://db.ygoresources.com/data/qa/20694
- Red-Eyes Fusion verbatim text via YGOPRODeck API ("its name becomes 'Red-Eyes B. Dragon'", no GY clause) — field-only name change reverts in the GY, per the general rule that a monster in the GY is a distinct object from the field copy