Overview
Most commands work with resources such as expansions and cards. Each resource is represented by a separate JSON file with a unique file suffix per resource type.
| Resource type | File suffix | File example |
|---|---|---|
| Expansion | expansion | international/base-set.expansion.json |
| Expansion price | expansion-price | international/base-set.usd.tcgplayer.expansion-price.json |
| Card | card | international/base-set/1-102.card.json |
| Card price | card-price | international/base-set/1-102.usd.tcgplayer.card-price.json |
| Card variant price | card-variant-price | international/base-set/1-102/standard-set-foil.usd.tcgplayer.card-variant-price.json |
| Card mapping | card-mapping | japan/star-birth/001-100.card-mapping.json |
| Image | image | international/base-set/1-102.image.json |
All resources follow the TCG Collector card database conventions. These conventions are needed in order to understand how to create or edit resources.
A lot of commands require other resource files as an argument. As an alternative to creating your own resource files, the cms export command can be used to export various resources from TCG Collector if you have the proper access rights.
If you decide to manually create or edit resource files, it's recommended to run the appropriate analyze command in order to detect potential errors, e.g., analyze cards.