(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
“What match are we on?”
Mexican food for dinner
Someone walks in front of the projector
Adult upset at event staff
Robot built the night before the event
Match starts 10+ minutes early
Match starts 10+ minutes late
Adult won’t let the kids talk
Music stops playing and no one notices
Multiple DQs in one match
Team brakes a field element
“Is there a practice field?”
Team fails field control check
Team with no license plates
Team says they’re ready, then reaches in to adjust robot
Someone has to call Dillon
Same pi needs to be rebooted multiple times
Team with wrong color license plates
Multiple teams with identical names
TM Audio bugs
Team picks sister team
Helicopter coach
Every team posts a skills run
“Field static”
Someone gets hit by an unfolding traybot
Team forgets notebook
Match no-show
Venue-provided AV breaks
Scorekeeper distracted by phone / food
Venue internet blocks something
Ryan or John describes robot troubleshooting over the mic
Parent asks how rankings work
Robot with <4 wheels
Scoring table loses power
Someone falls off a chair/bleachers
Ryan has a “word of the day”
Last minute robot battery swap
Water spilled on field
Microphone snaps, crackles and pops
Team tries to score SPs but loses
“I need a single student representative from each team”
Robot rebuild over lunch
Cortex robot in QF or later
Team doesn’t understand SPs
Robot parts left on field
<50% of teams post skills runs
Meme on robot
Team uses freeze spray/canned air
Both alliances cross the line in auton
Audience boos strategic alliance decline
Pi has to be reset
Someone trips over a cable
Someone other than Ryan or John head refs
TM op misses match countdown
Sharp robot component draws blood
Ryan gets irritated and shuts off mic to vent
Philip devises “creative” technical solution
“When do we get our notebooks back?”
Tie in eliminations
Match starts too early
Adult working on robot
Automatic Windows update breaks things
Volunteers stay in hotel with team(s)
Meme on robot
Adult crying
Ryan and John switch roles
Venue loses power
Upset in elims
Presenter asked to bs and make time for technical difficulties goes on far longer than it takes to resolve the difficulties
Ref closely examines field elements or robot
Auton consisting of random movements
No staff at scoring table
Windows system sounds over PA
Real static guard
Team arrives 4+ matches early
Refs chase game objects that leave the field
Team steals field elements
Ryan gets distracted
Audience cheers at head ref ruling
Team forgets to connect battery, turn on robot, or start program
Match sequence break
Head ref and MC are the same person
Team sets up on wrong field
Todd goes missing
“Why didn’t we win [award x]?”
Dropped controller
No clawbots at event
Speaker takes too long at awards
Ryan summons John over loudspeaker
Robot throws game elements
Someone says Via isn’t working but is just looking at the wrong event
Sister teams in the same match accidentally switch controllers
Team doesn’t understand how alliance selection works
No robots move in auton
“Is the skills field open?”
Paper test
Award winners accidentally revealed early
Coach swearing
Adult asks refs questions after being told not to
Venue roof leaks
Large subsystem summarily removed from robot mid-event
TM lags
Match DQ
Student runs away from the field to avoid wearing the goggles of shame
