[CaptainJack] Battlefields, Chosen Champion, and Legend not counted in collection tracking
George Jabbour
## Problem Statement
Collection tracking in the deck builder does not count cards of type Battlefield, Chosen Champion, and Legend. This means users cannot see ownership status for these card types when building decks, breaking the collection tracking feature for a subset of cards.
## Steps to Reproduce
- Add Battlefield, Chosen Champion, or Legend cards to your collection
- Navigate to the Deck Builder for CaptainJack
- Create or edit a deck containing these card types
- Observe the collection tracking indicators for these cards
## Expected Behavior
- All card types should show collection ownership status (owned/not owned counts)
- Deck builder should indicate how many copies the user owns vs. needs
- Collection tracking should work consistently across all card types
## Actual Behavior
- Battlefield, Chosen Champion, and Legend cards do not show collection tracking
- These cards appear as if user owns 0 copies regardless of actual collection
- Users cannot determine if they need to acquire these cards
## Technical Notes
This is likely related to ticket #692d038142ef1ad26204ed00 (foil selection issue for same card types). Both issues suggest these card types may be misconfigured or missing from certain database queries/filters.
Investigate:
- Card type enumeration/filtering logic
- Collection tracking query to ensure these types are included
- Data model for these card types
## Acceptance Criteria
- [ ] Battlefield cards show accurate collection count in deck builder
- [ ] Chosen Champion cards show accurate collection count in deck builder
- [ ] Legend cards show accurate collection count in deck builder
- [ ] Collection tracking totals include these card types
- [ ] "Cards needed" calculations account for these card types
## Questions to Clarify
- Are these card types stored differently in the database?
- Is there a card type filter that may be excluding them?
---
Area:
Deck Builder / CollectionGame:
CaptainJackType:
BugRelated:
#692d038142ef1ad26204ed00