Skip to content

Determine if a challenger has completed the steak challenge #5

@TimLChan

Description

@TimLChan

summary

Record the number of times a steak challenge is won so that a "win rate" tracker can be measured and reported on. Unfortunately, the Big Texan's winner tracker hasn't been updated since late Nov 2025, meaning that it is hard to see who has won the challenge.

user story

as a steak challenge enjoyer
i want to be notified when someone wins the steak challenge
so that i can tune in to see them claim their prize

conversation notes

When someone wins a steak challenge, the staff stop the timer countdown for the contestant. When the timer stays the same on the 2nd run (and isn't at 00:00 or 60:00), it can be inferred that someone has won the challenge.

technical considerations / scope

technical considerations

  • "winning" the challenge when the timer stays the same across 2 continuous iterations of the loop
    • loop 1: timer shows 3221, loop 2: timer shows 3221 -> count as a win
    • loop 1: timer shows 3221, loop 2: timer shows 6000 -> not a win
    • loop 1: timer shows 3221, loop 2: timer shows 0000 -> not a win
    • loop 1: timer shows 3221, loop 2: timer shows 3110 -> not a win
  • a blank OCR / invalid timer number does not factor into the continuous iterations
    • loop 1: timer shows 3221, loop 2: timer failed to be OCRed, loop 3: timer shows 3221 -> count as a win
    • loop 1: timer shows 3221, loop 2: 0000, loop 3: timer shows 3221 -> not a win
  • a "win" should be stored as a unique record in the database

in scope

  • adding this as a feature flag in the config
  • calculation of a winner based on the timer staying the same across 2 continuous iterations
  • creation of a new database table to store winners and their times
  • addition of the winners to the daily wrap up discord message as a beta
  • updating tests for the scenarios

out of scope

  • sending a discord message when a contestant wins the steak challenge

acceptance criteria

tbc

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions