TM opmissesmatchcountdown“Fieldstatic”Ryan getsirritated andshuts offmic to ventMicrophonesnaps,cracklesand popsMemeonrobotMultipleteams withidenticalnamesSharp robotcomponentdraws bloodTeam withno licenseplatesTeam withwrong colorlicenseplatesTeamarrives 4+matchesearlyMemeonrobotSpeakertakes toolong atawardsVenuelosespowerTeam triesto scoreSPs butlosesTMAudiobugsAdult asksrefsquestionsafter beingtold not toHead refand MC arethe samepersonAdultupset atevent staffTeam forgetsto connectbattery, turnon robot, orstart programRyan hasa “word ofthe day”RefsearchesQ&AVenue-providedAV breaksRobot builtthe nightbefore theeventPhilip’strackballfalls outTeamdoesn’tunderstandSPsAdultworkingon robotMusic stopsplaying andno onenoticesAutomaticWindowsupdatebreaks thingsVenueroofleaksMatchno-showVenueinternetblockssomethingTeampickssisterteamScoringtablelosespowerStudent runsaway from thefield to avoidwearing thegoggles ofshamePlacebostaticguardRyan or Johndescribesrobottroubleshootingover the micRef closelyexaminesfieldelements orrobotAdultcryingVolunteersstay inhotel withteam(s)Scorekeeperdistracted byphone / foodDroppedcontrollerTeamstealsfieldelementsRyangetsdistractedUpsetin elimsTie ineliminationsAdultwon’t letthe kidstalkAudienceboosstrategicalliancedeclineMultipleDQs inone matchRobotBreaksRobotthrowsgameelementsNetworkingproblemsSomeonehas to callDillonPi hasto bereset“When dowe get ournotebooksback?”TeamforgetsnotebookAudiencecheers athead refrulingMexicanfood fordinnerSame pineeds to berebootedmultipletimesPhilipdevises“creative”technicalsolution“Whatmatch arewe on?”Largesubsystemsummarilyremoved fromrobot mid-eventTeam failsfieldcontrolcheck<50% ofteamspost skillsrunsRealstaticguardTMlagsSomeone saysVia isn’tworking but isjust looking atthe wrong eventNo staff atscoringtableParentasks howrankingsworkSomeonewalks infront of theprojectorWaterspilledon fieldCoachswearingBothalliancescross theline in autonSomeonetrips overa cableMatchstarts tooearly“Whydidn’t wewin [awardx]?”Everyteamposts askills runTeambrakes afieldelementMatchstarts 10+minutesearlyInexplicableTournamentManagerproblem“Is theskills fieldopen?”Team setsup onwrongfieldTeam usesfreezespray/cannedairStudentleavesfield mid-matchRobotparts lefton fieldSomeoneother thanRyan or Johnhead refs“Have youprinted thematchschedule?”Team saysthey’re ready,then reachesin to adjustrobotRobotwith <4wheelsSomeonegets hit byan unfoldingtraybotRobotrebuildover lunchWindowssystemsoundsover PALast minuterobotbatteryswap“I need asingle studentrepresentativefrom eachteam”HelicoptercoachToddgoesmissingSister teams inthe same matchaccidentallyswitchcontrollersWallbotRyan andJohnswitchrolesNoclawbotsat eventNo robotsmove inautonEntireteam intearsPapertestMatchstarts 10+minuteslate“Is there apracticefield?”RyansummonsJohn overloudspeakerAutonconsistingof randommovementsSomeone fallsoff achair/bleachersPrintermisbehavesMatchDQAwardwinnersaccidentallyrevealedearlyTeam doesn’tunderstandhow allianceselectionworksMatchsequencebreakPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesCortexrobot inQF orlaterRefs chasegame objectsthat leavethe fieldTM opmissesmatchcountdown“Fieldstatic”Ryan getsirritated andshuts offmic to ventMicrophonesnaps,cracklesand popsMemeonrobotMultipleteams withidenticalnamesSharp robotcomponentdraws bloodTeam withno licenseplatesTeam withwrong colorlicenseplatesTeamarrives 4+matchesearlyMemeonrobotSpeakertakes toolong atawardsVenuelosespowerTeam triesto scoreSPs butlosesTMAudiobugsAdult asksrefsquestionsafter beingtold not toHead refand MC arethe samepersonAdultupset atevent staffTeam forgetsto connectbattery, turnon robot, orstart programRyan hasa “word ofthe day”RefsearchesQ&AVenue-providedAV breaksRobot builtthe nightbefore theeventPhilip’strackballfalls outTeamdoesn’tunderstandSPsAdultworkingon robotMusic stopsplaying andno onenoticesAutomaticWindowsupdatebreaks thingsVenueroofleaksMatchno-showVenueinternetblockssomethingTeampickssisterteamScoringtablelosespowerStudent runsaway from thefield to avoidwearing thegoggles ofshamePlacebostaticguardRyan or Johndescribesrobottroubleshootingover the micRef closelyexaminesfieldelements orrobotAdultcryingVolunteersstay inhotel withteam(s)Scorekeeperdistracted byphone / foodDroppedcontrollerTeamstealsfieldelementsRyangetsdistractedUpsetin elimsTie ineliminationsAdultwon’t letthe kidstalkAudienceboosstrategicalliancedeclineMultipleDQs inone matchRobotBreaksRobotthrowsgameelementsNetworkingproblemsSomeonehas to callDillonPi hasto bereset“When dowe get ournotebooksback?”TeamforgetsnotebookAudiencecheers athead refrulingMexicanfood fordinnerSame pineeds to berebootedmultipletimesPhilipdevises“creative”technicalsolution“Whatmatch arewe on?”Largesubsystemsummarilyremoved fromrobot mid-eventTeam failsfieldcontrolcheck<50% ofteamspost skillsrunsRealstaticguardTMlagsSomeone saysVia isn’tworking but isjust looking atthe wrong eventNo staff atscoringtableParentasks howrankingsworkSomeonewalks infront of theprojectorWaterspilledon fieldCoachswearingBothalliancescross theline in autonSomeonetrips overa cableMatchstarts tooearly“Whydidn’t wewin [awardx]?”Everyteamposts askills runTeambrakes afieldelementMatchstarts 10+minutesearlyInexplicableTournamentManagerproblem“Is theskills fieldopen?”Team setsup onwrongfieldTeam usesfreezespray/cannedairStudentleavesfield mid-matchRobotparts lefton fieldSomeoneother thanRyan or Johnhead refs“Have youprinted thematchschedule?”Team saysthey’re ready,then reachesin to adjustrobotRobotwith <4wheelsSomeonegets hit byan unfoldingtraybotRobotrebuildover lunchWindowssystemsoundsover PALast minuterobotbatteryswap“I need asingle studentrepresentativefrom eachteam”HelicoptercoachToddgoesmissingSister teams inthe same matchaccidentallyswitchcontrollersWallbotRyan andJohnswitchrolesNoclawbotsat eventNo robotsmove inautonEntireteam intearsPapertestMatchstarts 10+minuteslate“Is there apracticefield?”RyansummonsJohn overloudspeakerAutonconsistingof randommovementsSomeone fallsoff achair/bleachersPrintermisbehavesMatchDQAwardwinnersaccidentallyrevealedearlyTeam doesn’tunderstandhow allianceselectionworksMatchsequencebreakPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesCortexrobot inQF orlaterRefs chasegame objectsthat leavethe field

VRC Bingo - Call List

(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
  1. TM op misses match countdown
  2. “Field static”
  3. Ryan gets irritated and shuts off mic to vent
  4. Microphone snaps, crackles and pops
  5. Meme on robot
  6. Multiple teams with identical names
  7. Sharp robot component draws blood
  8. Team with no license plates
  9. Team with wrong color license plates
  10. Team arrives 4+ matches early
  11. Meme on robot
  12. Speaker takes too long at awards
  13. Venue loses power
  14. Team tries to score SPs but loses
  15. TM Audio bugs
  16. Adult asks refs questions after being told not to
  17. Head ref and MC are the same person
  18. Adult upset at event staff
  19. Team forgets to connect battery, turn on robot, or start program
  20. Ryan has a “word of the day”
  21. Ref searches Q&A
  22. Venue-provided AV breaks
  23. Robot built the night before the event
  24. Philip’s trackball falls out
  25. Team doesn’t understand SPs
  26. Adult working on robot
  27. Music stops playing and no one notices
  28. Automatic Windows update breaks things
  29. Venue roof leaks
  30. Match no-show
  31. Venue internet blocks something
  32. Team picks sister team
  33. Scoring table loses power
  34. Student runs away from the field to avoid wearing the goggles of shame
  35. Placebo static guard
  36. Ryan or John describes robot troubleshooting over the mic
  37. Ref closely examines field elements or robot
  38. Adult crying
  39. Volunteers stay in hotel with team(s)
  40. Scorekeeper distracted by phone / food
  41. Dropped controller
  42. Team steals field elements
  43. Ryan gets distracted
  44. Upset in elims
  45. Tie in eliminations
  46. Adult won’t let the kids talk
  47. Audience boos strategic alliance decline
  48. Multiple DQs in one match
  49. Robot Breaks
  50. Robot throws game elements
  51. Networking problems
  52. Someone has to call Dillon
  53. Pi has to be reset
  54. “When do we get our notebooks back?”
  55. Team forgets notebook
  56. Audience cheers at head ref ruling
  57. Mexican food for dinner
  58. Same pi needs to be rebooted multiple times
  59. Philip devises “creative” technical solution
  60. “What match are we on?”
  61. Large subsystem summarily removed from robot mid-event
  62. Team fails field control check
  63. <50% of teams post skills runs
  64. Real static guard
  65. TM lags
  66. Someone says Via isn’t working but is just looking at the wrong event
  67. No staff at scoring table
  68. Parent asks how rankings work
  69. Someone walks in front of the projector
  70. Water spilled on field
  71. Coach swearing
  72. Both alliances cross the line in auton
  73. Someone trips over a cable
  74. Match starts too early
  75. “Why didn’t we win [award x]?”
  76. Every team posts a skills run
  77. Team brakes a field element
  78. Match starts 10+ minutes early
  79. Inexplicable Tournament Manager problem
  80. “Is the skills field open?”
  81. Team sets up on wrong field
  82. Team uses freeze spray/canned air
  83. Student leaves field mid-match
  84. Robot parts left on field
  85. Someone other than Ryan or John head refs
  86. “Have you printed the match schedule?”
  87. Team says they’re ready, then reaches in to adjust robot
  88. Robot with <4 wheels
  89. Someone gets hit by an unfolding traybot
  90. Robot rebuild over lunch
  91. Windows system sounds over PA
  92. Last minute robot battery swap
  93. “I need a single student representative from each team”
  94. Helicopter coach
  95. Todd goes missing
  96. Sister teams in the same match accidentally switch controllers
  97. Wall bot
  98. Ryan and John switch roles
  99. No clawbots at event
  100. No robots move in auton
  101. Entire team in tears
  102. Paper test
  103. Match starts 10+ minutes late
  104. “Is there a practice field?”
  105. Ryan summons John over loudspeaker
  106. Auton consisting of random movements
  107. Someone falls off a chair/bleachers
  108. Printer misbehaves
  109. Match DQ
  110. Award winners accidentally revealed early
  111. Team doesn’t understand how alliance selection works
  112. Match sequence break
  113. Presenter asked to bs and make time for technical difficulties goes on far longer than it takes to resolve the difficulties
  114. Cortex robot in QF or later
  115. Refs chase game objects that leave the field