Local-file creator workflow

Game Data Integrity & Release QA

Catch broken rows, missing references, manifest drift, undocumented release changes, expansion conflicts, and composition-rule failures before they reach a prototype, playtest build, or production handoff.

Your files stay on your device. Every check runs in this browser tab. No CSV content is uploaded, stored, or sent to Tabletop Maker Lab.

One source of truth, six release decisions

Choose the check that matches the handoff.

Each tool answers a different question. They can use similar CSV data without reducing the workflow to six names for one generic validator.

Validator

CSV Schema Validator

Check required columns and values, unique IDs, numeric fields, row shape, quoting, and encoding.

 Checker

ID & Reference Integrity Checker

Verify that scenario, recipe, upgrade, and component references point to real master IDs.

 Checker

Component Manifest Reconciler

Compare expected and actual manifests for missing, extra, renamed, and quantity-mismatched components.

 Generator

Version Diff & Release Notes

Group added, removed, and modified records by stable ID and list the fields that changed.

 Validator

Expansion Compatibility Validator

Check creator-defined IDs, dependencies, replacements, and component types across base and expansion files.

 Validator

Deck / Set Composition Rules Checker

Apply your own total, copy-limit, allowed-category, and category-range rules to a component list.

Suggested release sequence

Structure → references → package → change → compatibility → composition

  1. Validate the source CSV before trusting downstream output.
  2. Resolve broken IDs between related datasets.
  3. Reconcile the component list used for handoff.
  4. Review exactly what changed since the prior version.
  5. Check expansion dependencies and replacements.
  6. Run creator-defined deck or set constraints.

What these tools do not decide

Integrity is not balance or production approval.

A passing report means the files satisfy the rules you supplied. It does not prove fun, balance, legal compliance, print quality, supplier acceptance, or physical completeness.

Prototype iteration

Use stable IDs so revised text and values can be compared without treating reordered rows as new cards.

Manufacturing handoff

Reconcile the approved component manifest against the file being handed to a supplier or assembly partner.

Expansion release

Declare dependencies and replacements explicitly instead of relying on memory or a prose-only change log.