This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
This template, {{CardTable2}}, is only meant for use in the main content namespace. Including it elsewhere can cause technical problems. Please remove the template from this page.
Historically, the template has been used for cards from all Yu-Gi-Oh! games and still contains support for a number of video games, which need to be given their own dedicated template.
summoned_by: Card used to Summon the monster, if a Monster Token.
source_card: The non-Skill Card that the Skill Card is based on.
lore: The text printed on the card, either a card description or effect text. If the card was printed without any lore, this should be set to none (which will add the page to Category:Cards printed without a lore).
pendulum_effect: The text printed on the card, describing its Pendulum Monster effect.
skill_activation: The activation requirement, printed on Skill Cards.
use: The purpose of the card, if a non-game card whose purpose is not otherwise clear. All pages using this parameter are added to Category:Card table parameter tracking (use).
tcg_status: The card's status in the TCGAdvanced Format. Defaults to the card's status in the current TCG Forbidden & Limited List; this parameter should only be added if the card is not yet released or legal.
tcg_speed_duel_status: The card's status in TCGSpeed Duel. This parameter should be used for all Speed Duel-legal cards.
Search categories
Each of these should be a bulleted list of page names:
supports_archetypes: archetypes that the card directly supports.
anti-supports_archetypes: archetypes that the card directly works against.
related_to_archseries: archetypes that the card is connected to without being a member or directly supporting. e.g. it supports an individual member of the archetype.
name, lore, pendulum_effect, skill_activation can be prefixed with a language code to specify its text in other languages. e.g. ja_lore for the Japanese lore. If lore is set to none, none of the other lore parameters should be used. Applicable prefixes are as follows ("romanized" prefixes only work for the "name" parameter):
trans_: Japanese translated into English. These should only be used if they differ non-trivially from the English name or lore. Using trans_lore adds the page to Category:Card table transclusions using trans_lore.
ja_alt_romaji: Romanization of the second Japanese name.
ja_alt_trans: English translation of the second Japanese name.
Links should generally only be added to the English lore, pendulum_effect, and skill_activation parameters (name parameters should never contain links, in any language). Each term should only be linked once, when it first appears in the lore. Where the text is clear, brevity is preferred over avoiding redirects; e.g. [[monster]] instead of [[Monster Card|monster]], [[sent]] instead of [[Send|sent]], [[GY]] instead of [[Graveyard|GY]], [[Life Points]] instead of [[LP|Life Points]], etc (see also wikipedia:WP:NOPIPE). However, note cases where a full link is clearer: [[Add a card|add]] instead of [[add]], [[Main Deck|Deck]] instead of [[Deck]], etc. Piped links to redirects should always be avoided: [[field]] instead of [[Playing Field|field]], etc. Note, though, that pages should not be edited only to change link targets to or from redirects; some other change must be made in the same edit (e.g. updating the search categories or adding a name).
Sets
The values for all sets are to be entered using the following syntax and ordered by release date, from oldest to newest.
Card number 1; Set page name 1; Rarity 1
Card number 2; Set page name 2; Rarity 2
For example:
| na_sets =
LOB-001; Legend of Blue Eyes White Dragon; Ultra Rare
DDS-001; Yu-Gi-Oh! Dark Duel Stories promotional cards; Prismatic Secret Rare
SDK-001; Starter Deck: Kaiba; Ultra Rare
If a card was printed in multiple rarities, all in the same set and with the same card number, the rarities should be included on the same line, separated with commas. For example:
If a card's rarity is unknown, or if a card has no card number, the value should be left blank, but the semicolon should be included. Similarly, if the card number is unknown, the known portion of the card number may be included, with unknown portions represented with question marks. For example:
| na_sets =
; Legend of Blue Eyes White Dragon; Common
SDK-001; Starter Deck: Kaiba;
CHIM-EN0??; Chaos Impact;
????-EN???; Eternity Code;
There are different parameters for different languages/regions:
The logic for determining the color scheme is as follows. If a condition is met, that color scheme is used. If not, the next condition is checked.
If the cardclass parameter is used, it will dictate the color scheme. Any value from the "Name" column in the table below can be used for this parameter. Cards using this parameter are tracked in Category:CardTable2 parameter tracking (cardclass).
If the card is a Monster Card with "Token" at the end of its name, the token color scheme will be used.
If the card_type parameter is used, the color scheme associated with the card type will be used. (See the "Use" column in the table below to find the card type.)
If the second item in the types parameter is any of "Normal", "Effect", "Fusion", "Link", "Ritual", "Synchro", "Token", or "Xyz", the color scheme associated with the monster type will be used. (See the "Use" column.)
If a third item is used in the types parameter, the color scheme associated with its value is used. (See the "Use" column.)
If the template identifies the card as a Monster Card and the effect_types parameter is used or the card has an Ability in its types parameters, the effect color scheme will be used. Cards will be added to the Category:Colors assumed without using the Type string category, in this scenario.
The pendulum color scheme is used on top of one of the other color schemes, if the pendulum_scale, pendulum_effect or pendulum_effect_types parameters or any of their localized equivalents are used.