Skip to content

Bug: Bracket view inconsistent — “Double elimination” + LIVE + Bye placement vs QF results (Mario Kart Tourney) #82

@Yuxiang-Huang

Description

@Yuxiang-Huang

Environment

  • Tournament: Mario Kart Tourney (example URL from UI):
    https://match-point-8820.onrender.com/t/f474d8f5-2f20-44f5-80e3-0e2731e32480/bracket
  • Logged-in session, 2026-04-21

Summary

The bracket page shows inconsistent progression and labeling relative to quarter-final results and the advertised format.

Observed issues

  1. Format mismatch: Header/subtitle indicates Double elimination and Prize pool $5,000, but the visible layout is a single tree; no losers bracket is shown.
  2. Quarter final vs semi final: QF Match 4 is Player_23 vs yuh (yuh wins). A later semi slot still references “(Match 4 winner)” next to a Bye, which does not match the actual QF 4 outcome.
  3. Grand finals: Championship shows Bye vs Player_2 with a scheduled time — a grand final should not include a Bye if seeding completed; winners from semis (e.g. Player_18 after winning a semi) do not align with the GF pairing shown in the UI.
  4. Status tag: A QF match shows LIVE while also displaying a final score (0–2) and a selected winner — status should likely be completed, not live.

Expected

  • Bracket structure matches double elimination if that is selected (winners + losers paths), or the UI should not label the event as double elimination.
  • Each round’s feed should show the correct previous-match references; Bye lines should only appear when mathematically correct.
  • Match status (LIVE vs final) should be mutually consistent with scores and locked seeding.

Notes

Reproduce on the deployed bracket URL above; inspect bracket generation / progression logic for this tournament size (6 entrants listed on tournament page vs “5 players” / byes in bracket — also worth reconciling).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions