Your Gundam TCG collection,
finally organised.

📋 Pending Manual Changes Log

🤖 Interactive Scraper Sync Cockpit

Trigger backend scrapers directly from this cockpit to download card databases, FAQ rules, or market prices. Compare the scraped data against your current database, edit details on the fly, and merge them into your local overrides.

📖 Moderator Audit Terminal User Manual

1. Reconciling Existing Cards

Use the Reconcile DB tab to search for cards by ID (e.g., GD01-001) or name. Click the zoom/inspect magnifying glass on any variant card to open the detail card override inspector. From there, you can adjust set sources, official image paths, rarities, or CardTrader blueprint links.

2. Creating a New Card Manually

Go to the Add Card Manually tab and fill out the details:

• Card ID: Must follow the official pattern, such as GD01-100 for standard cards, or GD01-100_p1 for parallel/alternate arts.
• Traits: Enter as a comma-separated list. They will be automatically parsed and indexed in the deck builder search filter dropdown.
• Image Override: Enter either the CDN key suffix (e.g. GD01-100_p5) to load it via the official Gundam Card Game assets proxy, or provide a full custom https://... web address to load the image.

3. Linking CardTrader Blueprint Pricing

Every card price is fetched on-demand from CardTrader using a blueprint mapping. To link pricing:

• Pasting URL: Paste the direct listing URL of the card from the CardTrader website (e.g., https://www.cardtrader.com/en/blueprints/341124-gundam-gd-01-newtype-rising). The parser will extract the ID 341124 and retrieve set details.
• Searching: Enter keywords (e.g. Tallgeese R+) and click "Search / Resolve". Select the matching blueprint from the list.

4. Saving & Deploying Changes

Saving any edits adds them to your local browser session (via localStorage overrides) for immediate local testing. To deploy changes:

1. Click the 🚀 Push to Server DB button at the top of the Reconcile DB tab.
2. This will trigger a server build script that compiles your modifications directly into the inlined database inside index.html, synchronizes the JSON export backups, and automatically creates a Git commit and pushes it to the repository.

5. Automated Scripts (Scraping, Auditing & Blueprints)

Use the backend automation scripts in the terminal to parse new data or update mapping files:

• Scrape new cards / sets: Run node api/scrape-cards.js (or invoke /api/scrape-cards). This crawls www.gundam-gcg.com/en/cards/ to extract card IDs, names, types, and traits, and updates them dynamically.
• Scrape FAQ rules / errata: Run node api/scrape-errata.js (or invoke /api/scrape-errata). This crawls www.gundam-gcg.com/en/rules/ to extract and format card-specific rulings and gameplay FAQs.
• Manage CardTrader blueprint mapping: To rebuild all blueprint bindings, set your authentication token and execute the mapping compiler:

  $env:CARDTRADER_TOKEN="your_api_token"
  node build-blueprint-map.js

  To fetch and append specific parallel/alternate art variant pricing blueprints, run:

  node run-blueprint-fetch.js your_api_token

• Fix blank blueprint versions: Run node fix-blank-version-blueprints.js to clean up database entries currently pointing to unresolved base pricing.
• Audit file syntax & validity: Before pushing modifications, run the validation utility to ensure no broken HTML or Javascript scripts: node C:/Users/conno/.gemini/antigravity/brain/e8a4411a-7163-4a2f-979e-4301894bdef7/scratch/verify_syntax.js