MatchDQTeamdoesn’tunderstandSPsWaterspilledon fieldNo staff atscoringtableSomeonetrips overa cableTeampickssisterteamRyan andJohnswitchrolesTeamarrives 4+matchesearlyPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesMicrophonesnaps,cracklesand popsSomeonewalks infront of theprojectorTM opmissesmatchcountdownMatchsequencebreakMatchno-showSharp robotcomponentdraws bloodInexplicableTournamentManagerproblemAdult asksrefsquestionsafter beingtold not to“Is theskills fieldopen?”Robotwith <4wheels<50% ofteamspost skillsrunsRobotthrowsgameelementsDroppedcontroller“Have youprinted thematchschedule?”Tie ineliminationsHead refand MC arethe samepersonVenuelosespowerBothalliancescross theline in autonRef closelyexaminesfieldelements orrobotTeam usesfreezespray/cannedairAdultcryingNo robotsmove inautonRobotBreaksTeam doesn’tunderstandhow allianceselectionworksRyangetsdistractedStudent runsaway from thefield to avoidwearing thegoggles ofshameRobot builtthe nightbefore theeventPapertestSomeone fallsoff achair/bleachersParentasks howrankingsworkWallbotPi hasto beresetPhilipdevises“creative”technicalsolutionTeam withno licenseplatesSister teams inthe same matchaccidentallyswitchcontrollersHelicoptercoachStudentleavesfield mid-matchRealstaticguardLargesubsystemsummarilyremoved fromrobot mid-eventRobotrebuildover lunchTeam saysthey’re ready,then reachesin to adjustrobotRyansummonsJohn overloudspeakerMemeonrobotMusic stopsplaying andno onenotices“I need asingle studentrepresentativefrom eachteam”Team setsup onwrongfieldVolunteersstay inhotel withteam(s)Speakertakes toolong atawardsAudienceboosstrategicalliancedeclineCortexrobot inQF orlaterTeam failsfieldcontrolcheckNoclawbotsat event“Whatmatch arewe on?”Matchstarts 10+minuteslateRyan getsirritated andshuts offmic to ventTeamstealsfieldelementsVenueinternetblockssomethingWindowssystemsoundsover PAEveryteamposts askills runSomeonegets hit byan unfoldingtraybotScorekeeperdistracted byphone / foodSomeonehas to callDillonTeam forgetsto connectbattery, turnon robot, orstart programAdultworkingon robotTeambrakes afieldelementRyan or Johndescribesrobottroubleshootingover the micMultipleteams withidenticalnamesRobotparts lefton fieldSame pineeds to berebootedmultipletimesTeam withwrong colorlicenseplatesMexicanfood fordinnerAutomaticWindowsupdatebreaks thingsNetworkingproblemsAdultwon’t letthe kidstalkPrintermisbehavesUpsetin elimsRefs chasegame objectsthat leavethe fieldAutonconsistingof randommovementsTMlagsVenueroofleaksMultipleDQs inone matchTeamforgetsnotebookAdultupset atevent staffToddgoesmissingMatchstarts 10+minutesearly“When dowe get ournotebooksback?”Ryan hasa “word ofthe day”Someoneother thanRyan or Johnhead refsEntireteam intearsTeam triesto scoreSPs butlosesPlacebostaticguard“Fieldstatic”“Is there apracticefield?”ScoringtablelosespowerPhilip’strackballfalls outTMAudiobugsAwardwinnersaccidentallyrevealedearly“Whydidn’t wewin [awardx]?”RefsearchesQ&AMemeonrobotCoachswearingVenue-providedAV breaksSomeone saysVia isn’tworking but isjust looking atthe wrong eventMatchstarts tooearlyAudiencecheers athead refrulingLast minuterobotbatteryswapMatchDQTeamdoesn’tunderstandSPsWaterspilledon fieldNo staff atscoringtableSomeonetrips overa cableTeampickssisterteamRyan andJohnswitchrolesTeamarrives 4+matchesearlyPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesMicrophonesnaps,cracklesand popsSomeonewalks infront of theprojectorTM opmissesmatchcountdownMatchsequencebreakMatchno-showSharp robotcomponentdraws bloodInexplicableTournamentManagerproblemAdult asksrefsquestionsafter beingtold not to“Is theskills fieldopen?”Robotwith <4wheels<50% ofteamspost skillsrunsRobotthrowsgameelementsDroppedcontroller“Have youprinted thematchschedule?”Tie ineliminationsHead refand MC arethe samepersonVenuelosespowerBothalliancescross theline in autonRef closelyexaminesfieldelements orrobotTeam usesfreezespray/cannedairAdultcryingNo robotsmove inautonRobotBreaksTeam doesn’tunderstandhow allianceselectionworksRyangetsdistractedStudent runsaway from thefield to avoidwearing thegoggles ofshameRobot builtthe nightbefore theeventPapertestSomeone fallsoff achair/bleachersParentasks howrankingsworkWallbotPi hasto beresetPhilipdevises“creative”technicalsolutionTeam withno licenseplatesSister teams inthe same matchaccidentallyswitchcontrollersHelicoptercoachStudentleavesfield mid-matchRealstaticguardLargesubsystemsummarilyremoved fromrobot mid-eventRobotrebuildover lunchTeam saysthey’re ready,then reachesin to adjustrobotRyansummonsJohn overloudspeakerMemeonrobotMusic stopsplaying andno onenotices“I need asingle studentrepresentativefrom eachteam”Team setsup onwrongfieldVolunteersstay inhotel withteam(s)Speakertakes toolong atawardsAudienceboosstrategicalliancedeclineCortexrobot inQF orlaterTeam failsfieldcontrolcheckNoclawbotsat event“Whatmatch arewe on?”Matchstarts 10+minuteslateRyan getsirritated andshuts offmic to ventTeamstealsfieldelementsVenueinternetblockssomethingWindowssystemsoundsover PAEveryteamposts askills runSomeonegets hit byan unfoldingtraybotScorekeeperdistracted byphone / foodSomeonehas to callDillonTeam forgetsto connectbattery, turnon robot, orstart programAdultworkingon robotTeambrakes afieldelementRyan or Johndescribesrobottroubleshootingover the micMultipleteams withidenticalnamesRobotparts lefton fieldSame pineeds to berebootedmultipletimesTeam withwrong colorlicenseplatesMexicanfood fordinnerAutomaticWindowsupdatebreaks thingsNetworkingproblemsAdultwon’t letthe kidstalkPrintermisbehavesUpsetin elimsRefs chasegame objectsthat leavethe fieldAutonconsistingof randommovementsTMlagsVenueroofleaksMultipleDQs inone matchTeamforgetsnotebookAdultupset atevent staffToddgoesmissingMatchstarts 10+minutesearly“When dowe get ournotebooksback?”Ryan hasa “word ofthe day”Someoneother thanRyan or Johnhead refsEntireteam intearsTeam triesto scoreSPs butlosesPlacebostaticguard“Fieldstatic”“Is there apracticefield?”ScoringtablelosespowerPhilip’strackballfalls outTMAudiobugsAwardwinnersaccidentallyrevealedearly“Whydidn’t wewin [awardx]?”RefsearchesQ&AMemeonrobotCoachswearingVenue-providedAV breaksSomeone saysVia isn’tworking but isjust looking atthe wrong eventMatchstarts tooearlyAudiencecheers athead refrulingLast minuterobotbatteryswap

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