Adult asksrefsquestionsafter beingtold not toNetworkingproblemsPhilipdevises“creative”technicalsolutionNoclawbotsat eventTM opmissesmatchcountdownRobotwith <4wheelsWindowssystemsoundsover PARefs chasegame objectsthat leavethe fieldLargesubsystemsummarilyremoved fromrobot mid-eventSharp robotcomponentdraws bloodNo robotsmove inautonPlacebostaticguardMultipleDQs inone matchTeamarrives 4+matchesearly“When dowe get ournotebooksback?”Microphonesnaps,cracklesand popsMatchno-showMemeonrobotTeamdoesn’tunderstandSPsAdultworkingon robotSame pineeds to berebootedmultipletimesTeam withno licenseplatesSomeonetrips overa cableRef closelyexaminesfieldelements orrobotSister teams inthe same matchaccidentallyswitchcontrollersStudent runsaway from thefield to avoidwearing thegoggles ofshameParentasks howrankingsworkInexplicableTournamentManagerproblemUpsetin elimsRyan or Johndescribesrobottroubleshootingover the mic“Whatmatch arewe on?”Someonegets hit byan unfoldingtraybotSomeone saysVia isn’tworking but isjust looking atthe wrong eventMatchstarts 10+minuteslateMexicanfood fordinnerPi hasto beresetSomeone fallsoff achair/bleachersSomeonewalks infront of theprojectorEveryteamposts askills runTMAudiobugsTeampickssisterteamRobotBreaksRobotrebuildover lunchStudentleavesfield mid-matchTeam withwrong colorlicenseplatesLast minuterobotbatteryswap“Is theskills fieldopen?”ScoringtablelosespowerTMlags“I need asingle studentrepresentativefrom eachteam”Scorekeeperdistracted byphone / food“Fieldstatic”MatchDQ“Have youprinted thematchschedule?”Team forgetsto connectbattery, turnon robot, orstart program<50% ofteamspost skillsrunsRyansummonsJohn overloudspeakerAutonconsistingof randommovements“Whydidn’t wewin [awardx]?”AutomaticWindowsupdatebreaks thingsVenue-providedAV breaksRyangetsdistractedMusic stopsplaying andno onenoticesNo staff atscoringtableWaterspilledon fieldAdultcryingTie ineliminationsToddgoesmissingRyan getsirritated andshuts offmic to ventSomeonehas to callDillonVenuelosespowerHead refand MC arethe samepersonTeamstealsfieldelementsPhilip’strackballfalls outTeam doesn’tunderstandhow allianceselectionworksBothalliancescross theline in autonDroppedcontrollerTeam setsup onwrongfieldMemeonrobotTeam usesfreezespray/cannedair“Is there apracticefield?”PapertestVenueroofleaksCoachswearingTeam triesto scoreSPs butlosesMatchstarts tooearlySomeoneother thanRyan or Johnhead refsRobotparts lefton fieldRobot builtthe nightbefore theeventTeamforgetsnotebookMatchsequencebreakCortexrobot inQF orlaterRefsearchesQ&ATeam saysthey’re ready,then reachesin to adjustrobotWallbotAwardwinnersaccidentallyrevealedearlyAdultupset atevent staffHelicoptercoachRobotthrowsgameelementsAdultwon’t letthe kidstalkTeambrakes afieldelementSpeakertakes toolong atawardsRealstaticguardRyan andJohnswitchrolesMatchstarts 10+minutesearlyAudienceboosstrategicalliancedeclinePrintermisbehavesRyan hasa “word ofthe day”Audiencecheers athead refrulingPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeam failsfieldcontrolcheckVolunteersstay inhotel withteam(s)VenueinternetblockssomethingMultipleteams withidenticalnamesEntireteam intearsAdult asksrefsquestionsafter beingtold not toNetworkingproblemsPhilipdevises“creative”technicalsolutionNoclawbotsat eventTM opmissesmatchcountdownRobotwith <4wheelsWindowssystemsoundsover PARefs chasegame objectsthat leavethe fieldLargesubsystemsummarilyremoved fromrobot mid-eventSharp robotcomponentdraws bloodNo robotsmove inautonPlacebostaticguardMultipleDQs inone matchTeamarrives 4+matchesearly“When dowe get ournotebooksback?”Microphonesnaps,cracklesand popsMatchno-showMemeonrobotTeamdoesn’tunderstandSPsAdultworkingon robotSame pineeds to berebootedmultipletimesTeam withno licenseplatesSomeonetrips overa cableRef closelyexaminesfieldelements orrobotSister teams inthe same matchaccidentallyswitchcontrollersStudent runsaway from thefield to avoidwearing thegoggles ofshameParentasks howrankingsworkInexplicableTournamentManagerproblemUpsetin elimsRyan or Johndescribesrobottroubleshootingover the mic“Whatmatch arewe on?”Someonegets hit byan unfoldingtraybotSomeone saysVia isn’tworking but isjust looking atthe wrong eventMatchstarts 10+minuteslateMexicanfood fordinnerPi hasto beresetSomeone fallsoff achair/bleachersSomeonewalks infront of theprojectorEveryteamposts askills runTMAudiobugsTeampickssisterteamRobotBreaksRobotrebuildover lunchStudentleavesfield mid-matchTeam withwrong colorlicenseplatesLast minuterobotbatteryswap“Is theskills fieldopen?”ScoringtablelosespowerTMlags“I need asingle studentrepresentativefrom eachteam”Scorekeeperdistracted byphone / food“Fieldstatic”MatchDQ“Have youprinted thematchschedule?”Team forgetsto connectbattery, turnon robot, orstart program<50% ofteamspost skillsrunsRyansummonsJohn overloudspeakerAutonconsistingof randommovements“Whydidn’t wewin [awardx]?”AutomaticWindowsupdatebreaks thingsVenue-providedAV breaksRyangetsdistractedMusic stopsplaying andno onenoticesNo staff atscoringtableWaterspilledon fieldAdultcryingTie ineliminationsToddgoesmissingRyan getsirritated andshuts offmic to ventSomeonehas to callDillonVenuelosespowerHead refand MC arethe samepersonTeamstealsfieldelementsPhilip’strackballfalls outTeam doesn’tunderstandhow allianceselectionworksBothalliancescross theline in autonDroppedcontrollerTeam setsup onwrongfieldMemeonrobotTeam usesfreezespray/cannedair“Is there apracticefield?”PapertestVenueroofleaksCoachswearingTeam triesto scoreSPs butlosesMatchstarts tooearlySomeoneother thanRyan or Johnhead refsRobotparts lefton fieldRobot builtthe nightbefore theeventTeamforgetsnotebookMatchsequencebreakCortexrobot inQF orlaterRefsearchesQ&ATeam saysthey’re ready,then reachesin to adjustrobotWallbotAwardwinnersaccidentallyrevealedearlyAdultupset atevent staffHelicoptercoachRobotthrowsgameelementsAdultwon’t letthe kidstalkTeambrakes afieldelementSpeakertakes toolong atawardsRealstaticguardRyan andJohnswitchrolesMatchstarts 10+minutesearlyAudienceboosstrategicalliancedeclinePrintermisbehavesRyan hasa “word ofthe day”Audiencecheers athead refrulingPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeam failsfieldcontrolcheckVolunteersstay inhotel withteam(s)VenueinternetblockssomethingMultipleteams withidenticalnamesEntireteam intears

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