The RFC initially included a draft Yu-Gi-Oh! profile, but it was removed: the editor does not know the game well enough to stand behind it, and a wrong profile is worse than no profile.
The known challenge for whoever picks this up: unlike MTG and Pokemon, rarity variants in Yu-Gi-Oh! share the same card code, so set plus number cannot distinguish printings. One candidate model is rarity tokens as finish values (common, rare, super_rare, ultra_rare, secret_rare, ...), since rarity is the surface treatment there, but this needs someone who knows the game and its tooling to confirm or replace.
If you collect Yu-Gi-Oh! or build tools for it and want to own this profile, comment here. See the Governance section in the README.
The RFC initially included a draft Yu-Gi-Oh! profile, but it was removed: the editor does not know the game well enough to stand behind it, and a wrong profile is worse than no profile.
The known challenge for whoever picks this up: unlike MTG and Pokemon, rarity variants in Yu-Gi-Oh! share the same card code, so
setplusnumbercannot distinguish printings. One candidate model is rarity tokens asfinishvalues (common, rare, super_rare, ultra_rare, secret_rare, ...), since rarity is the surface treatment there, but this needs someone who knows the game and its tooling to confirm or replace.If you collect Yu-Gi-Oh! or build tools for it and want to own this profile, comment here. See the Governance section in the README.