gambit/gambit
1
0
Code Issues 534 Packages Projects Wiki

Dragon Ball Fusion World Story Booster (ST01) fails to match — set id collides with One Piece ST01 #616

New Issue
Open
opened 2026-09-05 01:17:09 +00:00 by gambit-admin · 1 comment
gambit-admin commented 2026-09-05 01:17:09 +00:00
Owner
Copy Link
Copy Source

Merged from #591 and #592 (both from @kris's 2026-09-03 report).

Scanning any card from the Dragon Ball Z Fusion World Story Booster returns no match. The booster's set id is st01, which is also a One Piece starter-deck set id, so a game-blind set lookup can resolve to the wrong game or fail.

Work

  • Confirm whether the set is missing from the catalog, mis-mapped, or present but shadowed by One Piece st01.
  • Namespace set ids per game everywhere they are used as a key (game code prefix or composite key).
  • Related alias mismatch: #482 (GAME_ALIASES says "dragon ball z" → fusion-world, external_scan says dragon-ball-z).

The general "new sets arrive late" problem is tracked separately in the automatic set-ingestion issue.

Merged from #591 and #592 (both from @kris's 2026-09-03 report). Scanning any card from the Dragon Ball Z Fusion World Story Booster returns no match. The booster's set id is `st01`, which is also a One Piece starter-deck set id, so a game-blind set lookup can resolve to the wrong game or fail. ## Work - Confirm whether the set is missing from the catalog, mis-mapped, or present but shadowed by One Piece `st01`. - Namespace set ids per game everywhere they are used as a key (game code prefix or composite key). - Related alias mismatch: #482 (`GAME_ALIASES` says "dragon ball z" → `fusion-world`, `external_scan` says `dragon-ball-z`). The general "new sets arrive late" problem is tracked separately in the automatic set-ingestion issue.
gambit-admin added the bugapi01 · scan & recognition labels 2026-09-05 01:17:09 +00:00
gambit-admin commented 2026-09-05 01:18:05 +00:00
Author
Owner
Copy Link
Copy Source

The general new-set ingestion problem referenced above is #615.

The general new-set ingestion problem referenced above is #615.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
01 · scan & recognition
User-flow fix order step 01 (beginning->end)
 02 · card detail sheet
User-flow fix order step 02 (beginning->end)
 03 · pricing & value
User-flow fix order step 03 (beginning->end)
 05 · inventory list
User-flow fix order step 05 (beginning->end)
 06 · inventory detail / rcn
User-flow fix order step 06 (beginning->end)
 07 · home / dashboard
User-flow fix order step 07 (beginning->end)
 08 · binders
User-flow fix order step 08 (beginning->end)
 09 · trade sheet
User-flow fix order step 09 (beginning->end)
 11 · sell / pos / marketplace
User-flow fix order step 11 (beginning->end)
 12 · analytics / trends
User-flow fix order step 12 (beginning->end)
 13 · cross-cutting
User-flow fix order step 13 (beginning->end)
 api
bug
claimed:Kelly
claimed:josh
claimed:kris
claimed:lucas
claimed:root
claimed:rudy
claimed:rudy2
crash
documentation
enhancement
export
feature
hardware
in progress (design)
Actively being worked on the design app (run.rtcg.app), not yet on production
 performance
security
someday
Parked wishlist — not scheduled, revisit when the roadmap has room
 ui
No Label 01 · scan & recognition api bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gambit-admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gambit/gambit#616
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?