(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
“Is the skills field open?”
Both alliances cross the line in auton
Every team posts a skills run
Adult crying
Multiple DQs in one match
Ref searches Q&A
“Is there a practice field?”
Robot parts left on field
Paper test
“I need a single student representative from each team”
Robot throws game elements
Upset in elims
Student runs away from the field to avoid wearing the goggles of shame
Ryan gets irritated and shuts off mic to vent
Water spilled on field
Team uses freeze spray/canned air
Placebo static guard
Team tries to score SPs but loses
Speaker takes too long at awards
Team fails field control check
Team with no license plates
Team brakes a field element
Someone other than Ryan or John head refs
Team says they’re ready, then reaches in to adjust robot
Networking problems
Same pi needs to be rebooted multiple times
Parent asks how rankings work
Pi has to be reset
Windows system sounds over PA
Philip’s trackball falls out
<50% of teams post skills runs
Entire team in tears
Team sets up on wrong field
Venue internet blocks something
Ref closely examines field elements or robot
Match DQ
Venue-provided AV breaks
Sister teams in the same match accidentally switch controllers
Someone falls off a chair/bleachers
Robot Breaks
“When do we get our notebooks back?”
Ryan and John switch roles
Match starts 10+ minutes late
Robot built the night before the event
Ryan or John describes robot troubleshooting over the mic
Multiple teams with identical names
Dropped controller
No clawbots at event
Team forgets to connect battery, turn on robot, or start program
Sharp robot component draws blood
Scoring table loses power
No robots move in auton
No staff at scoring table
Team forgets notebook
Adult asks refs questions after being told not to
Coach swearing
“Field static”
Someone trips over a cable
Team picks sister team
Microphone snaps, crackles and pops
Helicopter coach
Someone walks in front of the projector
Someone says Via isn’t working but is just looking at the wrong event
Wall bot
Automatic Windows update breaks things
Student leaves field mid-match
Auton consisting of random movements
Venue roof leaks
Music stops playing and no one notices
Team doesn’t understand how alliance selection works
Match starts 10+ minutes early
Adult won’t let the kids talk
Match no-show
Venue loses power
Printer misbehaves
Meme on robot
Robot rebuild over lunch
Last minute robot battery swap
Ryan gets distracted
Presenter asked to bs and make time for technical difficulties goes on far longer than it takes to resolve the difficulties
Team doesn’t understand SPs
Meme on robot
Someone gets hit by an unfolding traybot
Large subsystem summarily removed from robot mid-event