Salta ai contenuti
Pegasus Docs

Add and maintain cards

Questi contenuti non sono ancora disponibili nella tua lingua.

What you’ll accomplish

Adding cards isn’t data entry — it’s how Pegasus learns what’s available for deck building. By the end of this workflow you can add cards from any source (search, paste, YDK file), keep quantities current, and avoid the maintenance debt that turns inventories into ghosts after three months.

Before you start

  • Locations set up — see Organize inventory if you haven’t yet.
  • A list of new cards to add (or an existing inventory state you want to clean up).

Steps

  1. Search to add one or two cards

    The fastest path for ad-hoc adds. Open Inventory → Add card. Search by card name, set code (e.g. LOB-005), or partial. Card art appears inline so you confirm before committing.

    This path is the right tool when you’re adding a single hand-trap you traded for, not when you’re importing 60 cards from a sealed product.

    Search matches partial strings and set codes — `monster reborn` and `LOB-070` both land.

  2. Get the quantity right the first time

    Quantity is load-bearing. Three copies of a staple versus one changes every readiness score, every acquisition recommendation, and every cross-deck conflict flag downstream. The default is 1 — bump it before saving.

    If you’re not sure of the count (a binder you haven’t recounted), set the quantity to your best estimate and put it in the inbox location so future-you knows it needs verification.

    Off-by-one quantities are the most common inventory bug — and the hardest to spot later.

  3. Bulk-paste from a YDK or text list

    For a fresh deck import or a bulk purchase, the bulk-paste tool eats:

    • Raw YDK files (with #main/#extra/!side markers)
    • Newline-separated card names
    • Quantity-prefixed lists (3 Pot of Greed)
    • Set-code lists (LOB-070 x3)

    Pegasus parses, deduplicates, and shows you a preview before committing. If a name is ambiguous (multiple reprints with the same English text), you pick the printing during the preview.

    If the preview shows 0 cards, your file probably has BOM or encoding artifacts. Re-export and retry.

  4. Triage the inbox weekly

    Cards added without an explicit location land in the Unsorted inbox. This is intentional — it lets you add quickly during gameplay or when packages arrive without breaking flow.

    The cost is that the inbox accumulates. Run a 5-minute pass weekly:

    • Assign each inbox card to its real location.
    • Mark cards committed to active decks.
    • Verify uncertain quantities.
    • Drop low-confidence prices if you’ve since seen real seller numbers.
    The inbox is a feature, not a failure mode — as long as you triage it.

What success looks like

The inbox count is under 20. Card quantities match physical reality on a recount. Active decks show green availability. The last reconciliation pass was within the last 7 days.

If you bought cards a month ago and the inbox still has them, that’s the signal — not the noise.

Going deeper

Quantity, location, and availability flags feed directly into the scoring model’s buildability check. Price confidence is documented in Data sources and affiliation — Pegasus does NOT auto-buy from any platform; we only ingest public price feeds.

For the field-by-field reference of the inventory surface and the import dialog, see Inventory (reference).

For tricky imports (CSV with non-standard columns, ambiguous reprints, edition mismatches), see Troubleshooting.

Next steps

Build decks With inventory honest, build target decks against it.
Readiness and acquisition Turn shortages into a prioritized buy list.