Mexicanfood fordinnerTeam forgetsto connectbattery, turnon robot, orstart programPhilipdevises“creative”technicalsolutionMicrophonesnaps,cracklesand popsTeampickssisterteamSomeonetrips overa cableRealstaticguardAdultcryingRefsearchesQ&ASomeonegets hit byan unfoldingtraybotMatchsequencebreakTeamforgetsnotebookPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesLast minuterobotbatteryswapMatchstarts 10+minuteslateMultipleDQs inone matchVolunteersstay inhotel withteam(s)<50% ofteamspost skillsrunsRobot builtthe nightbefore theeventAwardwinnersaccidentallyrevealedearlyRobotBreaksRyan andJohnswitchrolesSomeonehas to callDillon“When dowe get ournotebooksback?”Robotwith <4wheelsRyan getsirritated andshuts offmic to ventVenue-providedAV breaksTeam setsup onwrongfieldSharp robotcomponentdraws bloodTeam doesn’tunderstandhow allianceselectionworksStudent runsaway from thefield to avoidwearing thegoggles ofshameLargesubsystemsummarilyremoved fromrobot mid-eventMatchDQ“Have youprinted thematchschedule?”Refs chasegame objectsthat leavethe fieldCoachswearingScorekeeperdistracted byphone / foodRyan hasa “word ofthe day”Everyteamposts askills runVenueinternetblockssomethingBothalliancescross theline in autonHelicoptercoachTeam withno licenseplatesRef closelyexaminesfieldelements orrobotParentasks howrankingsworkScoringtablelosespowerSpeakertakes toolong atawardsTM opmissesmatchcountdownSomeoneother thanRyan or Johnhead refs“I need asingle studentrepresentativefrom eachteam”WallbotAdultwon’t letthe kidstalkPi hasto bereset“Is there apracticefield?”TeamstealsfieldelementsWaterspilledon field“Whydidn’t wewin [awardx]?”Someone fallsoff achair/bleachersRyan or Johndescribesrobottroubleshootingover the micTeamarrives 4+matchesearlyMemeonrobotRobotrebuildover lunchRyansummonsJohn overloudspeakerVenuelosespowerPrintermisbehavesRobotparts lefton fieldMemeonrobotSomeone saysVia isn’tworking but isjust looking atthe wrong eventAutonconsistingof randommovementsUpsetin elimsTeambrakes afieldelementRyangetsdistractedNo robotsmove inautonSister teams inthe same matchaccidentallyswitchcontrollersNo staff atscoringtableEntireteam intearsSomeonewalks infront of theprojectorHead refand MC arethe samepersonPapertestStudentleavesfield mid-matchInexplicableTournamentManagerproblemVenueroofleaksTeam withwrong colorlicenseplatesAdult asksrefsquestionsafter beingtold not toNoclawbotsat eventNetworkingproblemsAdultupset atevent staffCortexrobot inQF orlaterPlacebostaticguardMatchno-showTeam failsfieldcontrolcheckAudienceboosstrategicalliancedeclineRobotthrowsgameelementsToddgoesmissing“Whatmatch arewe on?”Adultworkingon robotTMlagsTeamdoesn’tunderstandSPsMultipleteams withidenticalnamesAutomaticWindowsupdatebreaks thingsTie ineliminations“Fieldstatic”Matchstarts tooearlyTeam saysthey’re ready,then reachesin to adjustrobotTeam triesto scoreSPs butlosesTMAudiobugsSame pineeds to berebootedmultipletimesMusic stopsplaying andno onenoticesMatchstarts 10+minutesearly“Is theskills fieldopen?”Windowssystemsoundsover PAAudiencecheers athead refrulingPhilip’strackballfalls outDroppedcontrollerTeam usesfreezespray/cannedairMexicanfood fordinnerTeam forgetsto connectbattery, turnon robot, orstart programPhilipdevises“creative”technicalsolutionMicrophonesnaps,cracklesand popsTeampickssisterteamSomeonetrips overa cableRealstaticguardAdultcryingRefsearchesQ&ASomeonegets hit byan unfoldingtraybotMatchsequencebreakTeamforgetsnotebookPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesLast minuterobotbatteryswapMatchstarts 10+minuteslateMultipleDQs inone matchVolunteersstay inhotel withteam(s)<50% ofteamspost skillsrunsRobot builtthe nightbefore theeventAwardwinnersaccidentallyrevealedearlyRobotBreaksRyan andJohnswitchrolesSomeonehas to callDillon“When dowe get ournotebooksback?”Robotwith <4wheelsRyan getsirritated andshuts offmic to ventVenue-providedAV breaksTeam setsup onwrongfieldSharp robotcomponentdraws bloodTeam doesn’tunderstandhow allianceselectionworksStudent runsaway from thefield to avoidwearing thegoggles ofshameLargesubsystemsummarilyremoved fromrobot mid-eventMatchDQ“Have youprinted thematchschedule?”Refs chasegame objectsthat leavethe fieldCoachswearingScorekeeperdistracted byphone / foodRyan hasa “word ofthe day”Everyteamposts askills runVenueinternetblockssomethingBothalliancescross theline in autonHelicoptercoachTeam withno licenseplatesRef closelyexaminesfieldelements orrobotParentasks howrankingsworkScoringtablelosespowerSpeakertakes toolong atawardsTM opmissesmatchcountdownSomeoneother thanRyan or Johnhead refs“I need asingle studentrepresentativefrom eachteam”WallbotAdultwon’t letthe kidstalkPi hasto bereset“Is there apracticefield?”TeamstealsfieldelementsWaterspilledon field“Whydidn’t wewin [awardx]?”Someone fallsoff achair/bleachersRyan or Johndescribesrobottroubleshootingover the micTeamarrives 4+matchesearlyMemeonrobotRobotrebuildover lunchRyansummonsJohn overloudspeakerVenuelosespowerPrintermisbehavesRobotparts lefton fieldMemeonrobotSomeone saysVia isn’tworking but isjust looking atthe wrong eventAutonconsistingof randommovementsUpsetin elimsTeambrakes afieldelementRyangetsdistractedNo robotsmove inautonSister teams inthe same matchaccidentallyswitchcontrollersNo staff atscoringtableEntireteam intearsSomeonewalks infront of theprojectorHead refand MC arethe samepersonPapertestStudentleavesfield mid-matchInexplicableTournamentManagerproblemVenueroofleaksTeam withwrong colorlicenseplatesAdult asksrefsquestionsafter beingtold not toNoclawbotsat eventNetworkingproblemsAdultupset atevent staffCortexrobot inQF orlaterPlacebostaticguardMatchno-showTeam failsfieldcontrolcheckAudienceboosstrategicalliancedeclineRobotthrowsgameelementsToddgoesmissing“Whatmatch arewe on?”Adultworkingon robotTMlagsTeamdoesn’tunderstandSPsMultipleteams withidenticalnamesAutomaticWindowsupdatebreaks thingsTie ineliminations“Fieldstatic”Matchstarts tooearlyTeam saysthey’re ready,then reachesin to adjustrobotTeam triesto scoreSPs butlosesTMAudiobugsSame pineeds to berebootedmultipletimesMusic stopsplaying andno onenoticesMatchstarts 10+minutesearly“Is theskills fieldopen?”Windowssystemsoundsover PAAudiencecheers athead refrulingPhilip’strackballfalls outDroppedcontrollerTeam usesfreezespray/cannedair

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