Someone fallsoff achair/bleachersAdult asksrefsquestionsafter beingtold not toRyansummonsJohn overloudspeakerNetworkingproblemsVenuelosespowerAudiencecheers athead refrulingRyangetsdistractedTeam saysthey’re ready,then reachesin to adjustrobotSomeonetrips overa cableTeam doesn’tunderstandhow allianceselectionworksLast minuterobotbatteryswapTie ineliminationsMatchsequencebreakPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesAutonconsistingof randommovementsTeampickssisterteamCoachswearingPapertestTM opmissesmatchcountdownTeamarrives 4+matchesearlyPi hasto beresetAdultwon’t letthe kidstalkPhilipdevises“creative”technicalsolutionWindowssystemsoundsover PACortexrobot inQF orlater“Is there apracticefield?”Teamstealsfieldelements<50% ofteamspost skillsrunsMemeonrobotPlacebostaticguardWallbotTMlagsVenueroofleaksRobotthrowsgameelementsHelicoptercoachDroppedcontrollerUpsetin elimsTeam forgetsto connectbattery, turnon robot, orstart programRealstaticguardRobotwith <4wheelsRyan or Johndescribesrobottroubleshootingover the micMatchstarts 10+minuteslateTeamforgetsnotebookTeambrakes afieldelementHead refand MC arethe samepersonAudienceboosstrategicalliancedeclineSharp robotcomponentdraws bloodSister teams inthe same matchaccidentallyswitchcontrollers“I need asingle studentrepresentativefrom eachteam”Everyteamposts askills runStudentleavesfield mid-matchMatchDQRyan getsirritated andshuts offmic to ventMatchno-showRobotrebuildover lunchInexplicableTournamentManagerproblem“Fieldstatic”Largesubsystemsummarilyremoved fromrobot mid-eventNoclawbotsat eventVenue-providedAV breaksRefsearchesQ&A“Whydidn’t wewin [awardx]?”“Is theskills fieldopen?”Bothalliancescross theline in autonScorekeeperdistracted byphone / foodRyan andJohnswitchrolesRefs chasegame objectsthat leavethe fieldStudent runsaway from thefield to avoidwearing thegoggles ofshameSomeonegets hit byan unfoldingtraybotTeam usesfreezespray/cannedairRyan hasa “word ofthe day”Team withno licenseplatesTMAudiobugsPhilip’strackballfalls outNo robotsmove inautonMicrophonesnaps,cracklesand popsMexicanfood fordinnerScoringtablelosespowerSame pineeds to berebootedmultipletimesAdultupset atevent staffTeam triesto scoreSPs butlosesWaterspilledon fieldSpeakertakes toolong atawardsEntireteam intearsRobot builtthe nightbefore theeventTeam withwrong colorlicenseplatesPrintermisbehavesRobotBreaksToddgoesmissingVenueinternetblockssomethingSomeoneother thanRyan or Johnhead refsVolunteersstay inhotel withteam(s)Parentasks howrankingsworkSomeonehas to callDillonNo staff atscoringtable“Have youprinted thematchschedule?”“When dowe get ournotebooksback?”Ref closelyexaminesfieldelements orrobotMusic stopsplaying andno onenoticesMemeonrobotTeam failsfieldcontrolcheckSomeonewalks infront of theprojectorMultipleteams withidenticalnamesMultipleDQs inone matchMatchstarts 10+minutesearlyAwardwinnersaccidentallyrevealedearly“Whatmatch arewe on?”AdultcryingTeam setsup onwrongfieldAdultworkingon robotTeamdoesn’tunderstandSPsAutomaticWindowsupdatebreaks thingsSomeone saysVia isn’tworking but isjust looking atthe wrong eventMatchstarts tooearlyRobotparts lefton fieldSomeone fallsoff achair/bleachersAdult asksrefsquestionsafter beingtold not toRyansummonsJohn overloudspeakerNetworkingproblemsVenuelosespowerAudiencecheers athead refrulingRyangetsdistractedTeam saysthey’re ready,then reachesin to adjustrobotSomeonetrips overa cableTeam doesn’tunderstandhow allianceselectionworksLast minuterobotbatteryswapTie ineliminationsMatchsequencebreakPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesAutonconsistingof randommovementsTeampickssisterteamCoachswearingPapertestTM opmissesmatchcountdownTeamarrives 4+matchesearlyPi hasto beresetAdultwon’t letthe kidstalkPhilipdevises“creative”technicalsolutionWindowssystemsoundsover PACortexrobot inQF orlater“Is there apracticefield?”Teamstealsfieldelements<50% ofteamspost skillsrunsMemeonrobotPlacebostaticguardWallbotTMlagsVenueroofleaksRobotthrowsgameelementsHelicoptercoachDroppedcontrollerUpsetin elimsTeam forgetsto connectbattery, turnon robot, orstart programRealstaticguardRobotwith <4wheelsRyan or Johndescribesrobottroubleshootingover the micMatchstarts 10+minuteslateTeamforgetsnotebookTeambrakes afieldelementHead refand MC arethe samepersonAudienceboosstrategicalliancedeclineSharp robotcomponentdraws bloodSister teams inthe same matchaccidentallyswitchcontrollers“I need asingle studentrepresentativefrom eachteam”Everyteamposts askills runStudentleavesfield mid-matchMatchDQRyan getsirritated andshuts offmic to ventMatchno-showRobotrebuildover lunchInexplicableTournamentManagerproblem“Fieldstatic”Largesubsystemsummarilyremoved fromrobot mid-eventNoclawbotsat eventVenue-providedAV breaksRefsearchesQ&A“Whydidn’t wewin [awardx]?”“Is theskills fieldopen?”Bothalliancescross theline in autonScorekeeperdistracted byphone / foodRyan andJohnswitchrolesRefs chasegame objectsthat leavethe fieldStudent runsaway from thefield to avoidwearing thegoggles ofshameSomeonegets hit byan unfoldingtraybotTeam usesfreezespray/cannedairRyan hasa “word ofthe day”Team withno licenseplatesTMAudiobugsPhilip’strackballfalls outNo robotsmove inautonMicrophonesnaps,cracklesand popsMexicanfood fordinnerScoringtablelosespowerSame pineeds to berebootedmultipletimesAdultupset atevent staffTeam triesto scoreSPs butlosesWaterspilledon fieldSpeakertakes toolong atawardsEntireteam intearsRobot builtthe nightbefore theeventTeam withwrong colorlicenseplatesPrintermisbehavesRobotBreaksToddgoesmissingVenueinternetblockssomethingSomeoneother thanRyan or Johnhead refsVolunteersstay inhotel withteam(s)Parentasks howrankingsworkSomeonehas to callDillonNo staff atscoringtable“Have youprinted thematchschedule?”“When dowe get ournotebooksback?”Ref closelyexaminesfieldelements orrobotMusic stopsplaying andno onenoticesMemeonrobotTeam failsfieldcontrolcheckSomeonewalks infront of theprojectorMultipleteams withidenticalnamesMultipleDQs inone matchMatchstarts 10+minutesearlyAwardwinnersaccidentallyrevealedearly“Whatmatch arewe on?”AdultcryingTeam setsup onwrongfieldAdultworkingon robotTeamdoesn’tunderstandSPsAutomaticWindowsupdatebreaks thingsSomeone saysVia isn’tworking but isjust looking atthe wrong eventMatchstarts tooearlyRobotparts lefton 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. Someone falls off a chair/bleachers
  2. Adult asks refs questions after being told not to
  3. Ryan summons John over loudspeaker
  4. Networking problems
  5. Venue loses power
  6. Audience cheers at head ref ruling
  7. Ryan gets distracted
  8. Team says they’re ready, then reaches in to adjust robot
  9. Someone trips over a cable
  10. Team doesn’t understand how alliance selection works
  11. Last minute robot battery swap
  12. Tie in eliminations
  13. Match sequence break
  14. Presenter asked to bs and make time for technical difficulties goes on far longer than it takes to resolve the difficulties
  15. Auton consisting of random movements
  16. Team picks sister team
  17. Coach swearing
  18. Paper test
  19. TM op misses match countdown
  20. Team arrives 4+ matches early
  21. Pi has to be reset
  22. Adult won’t let the kids talk
  23. Philip devises “creative” technical solution
  24. Windows system sounds over PA
  25. Cortex robot in QF or later
  26. “Is there a practice field?”
  27. Team steals field elements
  28. <50% of teams post skills runs
  29. Meme on robot
  30. Placebo static guard
  31. Wall bot
  32. TM lags
  33. Venue roof leaks
  34. Robot throws game elements
  35. Helicopter coach
  36. Dropped controller
  37. Upset in elims
  38. Team forgets to connect battery, turn on robot, or start program
  39. Real static guard
  40. Robot with <4 wheels
  41. Ryan or John describes robot troubleshooting over the mic
  42. Match starts 10+ minutes late
  43. Team forgets notebook
  44. Team brakes a field element
  45. Head ref and MC are the same person
  46. Audience boos strategic alliance decline
  47. Sharp robot component draws blood
  48. Sister teams in the same match accidentally switch controllers
  49. “I need a single student representative from each team”
  50. Every team posts a skills run
  51. Student leaves field mid-match
  52. Match DQ
  53. Ryan gets irritated and shuts off mic to vent
  54. Match no-show
  55. Robot rebuild over lunch
  56. Inexplicable Tournament Manager problem
  57. “Field static”
  58. Large subsystem summarily removed from robot mid-event
  59. No clawbots at event
  60. Venue-provided AV breaks
  61. Ref searches Q&A
  62. “Why didn’t we win [award x]?”
  63. “Is the skills field open?”
  64. Both alliances cross the line in auton
  65. Scorekeeper distracted by phone / food
  66. Ryan and John switch roles
  67. Refs chase game objects that leave the field
  68. Student runs away from the field to avoid wearing the goggles of shame
  69. Someone gets hit by an unfolding traybot
  70. Team uses freeze spray/canned air
  71. Ryan has a “word of the day”
  72. Team with no license plates
  73. TM Audio bugs
  74. Philip’s trackball falls out
  75. No robots move in auton
  76. Microphone snaps, crackles and pops
  77. Mexican food for dinner
  78. Scoring table loses power
  79. Same pi needs to be rebooted multiple times
  80. Adult upset at event staff
  81. Team tries to score SPs but loses
  82. Water spilled on field
  83. Speaker takes too long at awards
  84. Entire team in tears
  85. Robot built the night before the event
  86. Team with wrong color license plates
  87. Printer misbehaves
  88. Robot Breaks
  89. Todd goes missing
  90. Venue internet blocks something
  91. Someone other than Ryan or John head refs
  92. Volunteers stay in hotel with team(s)
  93. Parent asks how rankings work
  94. Someone has to call Dillon
  95. No staff at scoring table
  96. “Have you printed the match schedule?”
  97. “When do we get our notebooks back?”
  98. Ref closely examines field elements or robot
  99. Music stops playing and no one notices
  100. Meme on robot
  101. Team fails field control check
  102. Someone walks in front of the projector
  103. Multiple teams with identical names
  104. Multiple DQs in one match
  105. Match starts 10+ minutes early
  106. Award winners accidentally revealed early
  107. “What match are we on?”
  108. Adult crying
  109. Team sets up on wrong field
  110. Adult working on robot
  111. Team doesn’t understand SPs
  112. Automatic Windows update breaks things
  113. Someone says Via isn’t working but is just looking at the wrong event
  114. Match starts too early
  115. Robot parts left on field