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