Introduce variants_detailed in V2 (to replace variants in V3)

[Aviortheking]

A new field, variants_detailed, is introduced in V2 to better describe the different physical and visual versions a card can have. This field will coexist with variants in V2 and fully replace it in V3.

New Field Structure

	variants_detailed?: Array<{
		/**
		 * define the variant type
		 * - normal: no holographic elements
		 * - holo: the illustration has a foil
		 * - reverse: everything but the illustration is foiled
		 */
		type: 'normal' | 'holo' | 'reverse'
		/**
		 * define the size of the card
		 * - standard: the classic size of a card
		 * - jumbo: also said oversized, big card.
		 */
		size?: 'standard' | 'jumbo'
		/**
		 * indicate that this variant has a stamp
		 * - 1st edition: a 1st edition card (mostly for the first serie of the game)
		 * - w-promo:
		 * - pre-release:
		 */
		stamp?: '1st edition' | 'w-promo' | 'pre-release'
		/**
		 * for the holo & reverse, **optionnnal** indicate which foil is used on the card
		 */
		foil?: 'pokeball' | 'ultraball'
	}>

⚠️ The listed values are examples only and do not represent the final exhaustive list. They are subject to change and expansion.

Why This Matters

The existing variants field is too limited. variants_detailed provides more precise definitions, supporting richer combinations like:

• holo, jumbo — jumbo-sized holo card
• reverse, 1st edition — reverse foil with 1st edition stamp

This structure allows better representation of how a card was actually printed and distributed.

[JHarrowell]

This looks great and fits the use case I'm going for.

I'm not too sure how comprehensive you're going to be, but other stamps could include "Retail" (Unless it's possible to specify "GameStop" for example), "Pokemon-Centre" (for PC ETB promo).

I know variation images are hard to source, but an optional image field could be added and then if the data isn't available, developers could fall back to using the base card image.

[immewnity]

I assume the values listed are just examples - else it's missing quite lot!

[Aviortheking]

yep that's examples based on recent questions, the other values will be filled with time :D

[immewnity]

May want to use ultraball instead of hyperball

[Aviortheking]

yep, xd I keep forgetting that hyperball is french exclusiv

[thomas-bassett]

Is there an idea of when this will be added to v2? I can see in the to-do there's some validation of variants, would it make sense for when people validate the variants to also add the detailed part?