card-blueprint-db-manager

Resolve slug collisions by filtering the SWCCG card blueprint database into side-specific JSON subsets, separating LIGHT and DARK cards to prevent mapping errors when duplicate slugs exist for same-named cards.

Exclude defensive shields from a card database by running jq commands that filter the blueprint JSON, removing shield entries before exporting the subset for cube-builder tools.

Duplicate slugs cause mapping errors because same-named cards exist on opposing sides, creating ambiguity. Generating a side-specific database subset isolates LIGHT or DARK cards to resolve the collision.

Generate a LIGHT-side only card database by applying jq filters to the blueprint, excluding DARK-side cards and defensive shields to produce a clean JSON subset for cube building.

Prepare SWCCG card data by using jq to create filtered JSON subsets that resolve slug collisions and exclude defensive shields, ensuring the blueprint maps correctly into cube-builder tools.

Split the card blueprint database by side when duplicate slugs from same-named cards on opposing sides cause mapping failures, requiring separate LIGHT and DARK JSON subsets for accurate processing.