member badge
George Jabbour
## Description
Investigate what additional Riftbound-specific data and features need to be supported in Nexlog. The attached screenshot shows some Riftbound-related data or UI that may need implementation.
## Current Riftbound Support
Nexlog already has partial Riftbound support:
  • Battlefield tracking
    on Game model (
    our_battlefield
    ,
    opponent_battlefield
    fields)
  • Card autocomplete
    via Flexslot.gg API for Riftbound cards
  • Conditional UI
    in match recording for Riftbound-specific fields
## Investigation Needed
  1. Review the attached screenshot
    to understand what specific data/feature is being requested
  2. Assess current gaps
    in Riftbound support
  3. Determine scope
    of work needed
## Potential Areas for Enhancement
Based on Riftbound game mechanics, potential areas that may need work:
  • Legend/Champion tracking
  • Battlefield effects and interactions
  • Riftbound-specific win conditions
  • Format-specific deck validation rules
  • Riftbound card metadata (if different from MTG)
## Next Steps
  1. Review the screenshot attachment
  2. Clarify requirements with stakeholder
  3. Create specific implementation tickets based on findings
## Type
Spike/Investigation
- This ticket requires research before implementation can be scoped
## Questions for Stakeholder
  1. What does the attached screenshot show? What specific feature is being requested?
  2. Are there Riftbound-specific statistics that need tracking?
  3. Do we need to support Riftbound-specific formats?
  4. Is the battlefield field currently being used in match recording UI?
## Estimated Complexity
TBD
- Depends on investigation findings. Could range from S (small UI tweak) to L (new game-specific features)