Frank Tumminello
Founder
November 3, 2025
It's been three weeks of full-time development - and we shipped a f*@!k ton!
/record/beerdie[gameId]. It was still using our old system of fetching guest info embedded in the UUID. We now store this information in the backend and properly fetch it./tournament/beerdie/[gameId], we added a rules dropdown so all users can review the tournament rules.next query param... This allows users who receive shared links (but arenβt signed in) to be redirected directly to the shared page after authentication./tournament/beerdie/[gameId] sceen. When first creating your team there is a placeholder card that allows you to continue editing the players on the team. There was a bug where if you continue to edit the team from the teams dropdown the card would reappear. We removed the reappearing card./stat/overview, we load the activity information via query params. When loading a game with a parent game id (a game attached to a tournament) we needed to populate the parent game in the breadcrumb trail./stat/overview page. The switch has 3 tabs, information about the tournament, the bracket, and an analysis to review team/player performance across the tournament./stat/overview. This included the view along with delete and edit functionality./record/beerdie/[gameId]. After recording stats on a game and launching a new one in the same browser session the masterTimeline and statistics state was preserved (unkown cause). Added specific logic to reset state on fetch so that state cannot be preserved.Overall, a productive week for Beernerd. π This wraps up the final week of tournament work, clearing the way to start building core statting functionality next week. This will make the app more flexible for users customizing their Beerdie games. Once those features are complete, weβll begin demoing for frats at universities!
Thanks for reading :)