Troubleshooting

Use this page when DeckScope results do not match what you expected.

A bulk import did not match some cards

Check:

• whether the unmatched line is a set code on its own (e.g. LOB-EN005) — matching only ever works by card name or a bare passcode, so a set code by itself never resolves, no matter how it is formatted
• whether a set code was written in parentheses after the name (Dark Magician (LOB-005)) — that suffix is stripped and ignored before matching, so only the name in front of it needs to be correct
• whether the name uses the TCG spelling, including hyphens and apostrophes
• whether a quantity prefix was parsed as part of the name
• whether the line is an OCG-only card with no TCG printing

Unmatched lines are reported rather than silently dropped. Fix the line and re-paste only the failed rows — re-pasting the whole list creates duplicate quantities.

Quantities are wrong after importing

Re-pasting the same list adds copies rather than replacing them. If quantities doubled, the list was imported twice. Correct the quantity on the affected cards directly in the inventory grid rather than deleting and re-importing.

Quantities are load-bearing: every readiness result and every acquisition ranking is computed against them. Fix these before trusting anything downstream.

A deck says cards are missing, but I own them

Check:

• the card quantity in inventory
• whether copies are committed to another deck
• whether the card is in the correct location
• whether the target deck uses the same card identity or printing
• whether the deck format changes legal copy limits

Owning a card does not always mean it is available.

Acquisition recommends a card I do not want to buy

Check:

• which decks the card blocks
• the estimated price and price confidence
• whether the target decks are still active
• whether a deck should be archived
• whether you already plan to move copies from another location

Acquisition ranks operational value. You still decide what matches your budget and goals.

Analysis says the deck is weak, but it plays fine

Check:

• whether the inferred deck style matches your intent
• whether role tags are missing or inaccurate
• whether the deck depends on lines DeckScope cannot model yet
• whether local format expectations differ from the default assumptions

Use analysis as guidance, not as a final verdict.

A version comparison looks stale

Run analysis again after changing either deck. Comparison results depend on deck content hashes and can become stale when either side changes.

Prices look wrong

Check the price basis and confidence. Placeholder or low-confidence prices are useful for rough sorting, but they are not checkout prices.

The sidebar or page route fails during docs build

Every Starlight sidebar slug must match a real docs entry. For localized content, English source files live under src/content/docs/en/, but sidebar slugs should omit the locale prefix.