“When dowe get ournotebooksback?”Mexicanfood fordinnerEveryteamposts askills runStudent runsaway from thefield to avoidwearing thegoggles ofshameAutomaticWindowsupdatebreaks things“Fieldstatic”Someonetrips overa cableAdult asksrefsquestionsafter beingtold not toPlacebostaticguardTeampickssisterteamRyan or Johndescribesrobottroubleshootingover the micSame pineeds to berebootedmultipletimes“Whatmatch arewe on?”TeamstealsfieldelementsVenuelosespower“Is there apracticefield?”“Whydidn’t wewin [awardx]?”Team usesfreezespray/cannedairRobotrebuildover lunchSomeonewalks infront of theprojectorMemeonrobotRefsearchesQ&AMatchno-showAwardwinnersaccidentallyrevealedearlyWaterspilledon fieldTeam triesto scoreSPs butlosesRyan hasa “word ofthe day”Robot builtthe nightbefore theeventRef closelyexaminesfieldelements orrobotScoringtablelosespowerNo staff atscoringtableTeamarrives 4+matchesearlyTMAudiobugsMultipleDQs inone matchPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesToddgoesmissingCortexrobot inQF orlaterRyangetsdistractedMemeonrobot<50% ofteamspost skillsrunsMultipleteams withidenticalnamesWindowssystemsoundsover PAStudentleavesfield mid-matchRealstaticguardMatchstarts tooearlyDroppedcontrollerMicrophonesnaps,cracklesand popsRefs chasegame objectsthat leavethe fieldTeam withwrong colorlicenseplatesTeambrakes afieldelementRobotthrowsgameelementsNoclawbotsat eventEntireteam intearsTeam setsup onwrongfieldSomeonehas to callDillonSpeakertakes toolong atawardsTie ineliminationsSister teams inthe same matchaccidentallyswitchcontrollers“Is theskills fieldopen?”Ryan andJohnswitchrolesTeam doesn’tunderstandhow allianceselectionworksRyansummonsJohn overloudspeakerMatchsequencebreakMatchstarts 10+minuteslateLast minuterobotbatteryswapCoachswearingVenueroofleaksLargesubsystemsummarilyremoved fromrobot mid-eventPrintermisbehavesSharp robotcomponentdraws bloodAdultupset atevent staffAdultwon’t letthe kidstalkVolunteersstay inhotel withteam(s)Team failsfieldcontrolcheckPhilipdevises“creative”technicalsolutionMusic stopsplaying andno onenoticesTeamdoesn’tunderstandSPsSomeone fallsoff achair/bleachersMatchstarts 10+minutesearlyTM opmissesmatchcountdownRyan getsirritated andshuts offmic to ventAudiencecheers athead refrulingTeam forgetsto connectbattery, turnon robot, orstart programBothalliancescross theline in autonUpsetin elimsRobotBreaksHelicoptercoachScorekeeperdistracted byphone / foodAdultworkingon robotTeam withno licenseplatesSomeoneother thanRyan or Johnhead refs“I need asingle studentrepresentativefrom eachteam”Head refand MC arethe samepersonAudienceboosstrategicalliancedecline“Have youprinted thematchschedule?”PapertestVenueinternetblockssomethingRobotparts lefton fieldSomeonegets hit byan unfoldingtraybotSomeone saysVia isn’tworking but isjust looking atthe wrong eventTeam saysthey’re ready,then reachesin to adjustrobotTMlagsRobotwith <4wheelsInexplicableTournamentManagerproblemMatchDQParentasks howrankingsworkPi hasto beresetWallbotAdultcryingNo robotsmove inautonAutonconsistingof randommovementsTeamforgetsnotebookVenue-providedAV breaksPhilip’strackballfalls outNetworkingproblems“When dowe get ournotebooksback?”Mexicanfood fordinnerEveryteamposts askills runStudent runsaway from thefield to avoidwearing thegoggles ofshameAutomaticWindowsupdatebreaks things“Fieldstatic”Someonetrips overa cableAdult asksrefsquestionsafter beingtold not toPlacebostaticguardTeampickssisterteamRyan or Johndescribesrobottroubleshootingover the micSame pineeds to berebootedmultipletimes“Whatmatch arewe on?”TeamstealsfieldelementsVenuelosespower“Is there apracticefield?”“Whydidn’t wewin [awardx]?”Team usesfreezespray/cannedairRobotrebuildover lunchSomeonewalks infront of theprojectorMemeonrobotRefsearchesQ&AMatchno-showAwardwinnersaccidentallyrevealedearlyWaterspilledon fieldTeam triesto scoreSPs butlosesRyan hasa “word ofthe day”Robot builtthe nightbefore theeventRef closelyexaminesfieldelements orrobotScoringtablelosespowerNo staff atscoringtableTeamarrives 4+matchesearlyTMAudiobugsMultipleDQs inone matchPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesToddgoesmissingCortexrobot inQF orlaterRyangetsdistractedMemeonrobot<50% ofteamspost skillsrunsMultipleteams withidenticalnamesWindowssystemsoundsover PAStudentleavesfield mid-matchRealstaticguardMatchstarts tooearlyDroppedcontrollerMicrophonesnaps,cracklesand popsRefs chasegame objectsthat leavethe fieldTeam withwrong colorlicenseplatesTeambrakes afieldelementRobotthrowsgameelementsNoclawbotsat eventEntireteam intearsTeam setsup onwrongfieldSomeonehas to callDillonSpeakertakes toolong atawardsTie ineliminationsSister teams inthe same matchaccidentallyswitchcontrollers“Is theskills fieldopen?”Ryan andJohnswitchrolesTeam doesn’tunderstandhow allianceselectionworksRyansummonsJohn overloudspeakerMatchsequencebreakMatchstarts 10+minuteslateLast minuterobotbatteryswapCoachswearingVenueroofleaksLargesubsystemsummarilyremoved fromrobot mid-eventPrintermisbehavesSharp robotcomponentdraws bloodAdultupset atevent staffAdultwon’t letthe kidstalkVolunteersstay inhotel withteam(s)Team failsfieldcontrolcheckPhilipdevises“creative”technicalsolutionMusic stopsplaying andno onenoticesTeamdoesn’tunderstandSPsSomeone fallsoff achair/bleachersMatchstarts 10+minutesearlyTM opmissesmatchcountdownRyan getsirritated andshuts offmic to ventAudiencecheers athead refrulingTeam forgetsto connectbattery, turnon robot, orstart programBothalliancescross theline in autonUpsetin elimsRobotBreaksHelicoptercoachScorekeeperdistracted byphone / foodAdultworkingon robotTeam withno licenseplatesSomeoneother thanRyan or Johnhead refs“I need asingle studentrepresentativefrom eachteam”Head refand MC arethe samepersonAudienceboosstrategicalliancedecline“Have youprinted thematchschedule?”PapertestVenueinternetblockssomethingRobotparts lefton fieldSomeonegets hit byan unfoldingtraybotSomeone saysVia isn’tworking but isjust looking atthe wrong eventTeam saysthey’re ready,then reachesin to adjustrobotTMlagsRobotwith <4wheelsInexplicableTournamentManagerproblemMatchDQParentasks howrankingsworkPi hasto beresetWallbotAdultcryingNo robotsmove inautonAutonconsistingof randommovementsTeamforgetsnotebookVenue-providedAV breaksPhilip’strackballfalls outNetworkingproblems

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