Teamdoesn’tunderstandSPsAwardwinnersaccidentallyrevealedearlyAudiencecheers athead refrulingRobot builtthe nightbefore theeventNetworkingproblemsTeam forgetsto connectbattery, turnon robot, orstart programTeam saysthey’re ready,then reachesin to adjustrobotNo robotsmove inautonMatchDQRobotwith <4wheelsRobotthrowsgameelementsRyangetsdistractedSpeakertakes toolong atawardsRealstaticguard“Fieldstatic”Matchstarts 10+minutesearlyTeam withwrong colorlicenseplatesTM opmissesmatchcountdownScorekeeperdistracted byphone / foodToddgoesmissingPlacebostaticguardMusic stopsplaying andno onenoticesAutonconsistingof randommovementsMatchno-showMexicanfood fordinnerRobotBreaks“Is theskills fieldopen?”Tie ineliminationsTMAudiobugsTeam failsfieldcontrolcheckTeam withno licenseplatesRobotparts lefton fieldSomeonetrips overa cableVenue-providedAV breaksWaterspilledon field“Whydidn’t wewin [awardx]?”Philip’strackballfalls outTeamstealsfieldelementsCoachswearingPapertestPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesMatchsequencebreakScoringtablelosespowerCortexrobot inQF orlaterPhilipdevises“creative”technicalsolutionPrintermisbehaves“When dowe get ournotebooksback?”<50% ofteamspost skillsrunsUpsetin elimsRobotrebuildover lunchRyan andJohnswitchrolesTeam usesfreezespray/cannedairRyan hasa “word ofthe day”AudienceboosstrategicalliancedeclineLargesubsystemsummarilyremoved fromrobot mid-eventPi hasto beresetRef closelyexaminesfieldelements orrobotHead refand MC arethe samepersonHelicoptercoachDroppedcontrollerVenueinternetblockssomethingMemeonrobotBothalliancescross theline in autonAutomaticWindowsupdatebreaks thingsRyansummonsJohn overloudspeakerTeam doesn’tunderstandhow allianceselectionworksAdultworkingon robotSomeonegets hit byan unfoldingtraybotSame pineeds to berebootedmultipletimesSomeone fallsoff achair/bleachersLast minuterobotbatteryswapRyan or Johndescribesrobottroubleshootingover the micRyan getsirritated andshuts offmic to ventAdult asksrefsquestionsafter beingtold not toAdultwon’t letthe kidstalkMultipleDQs inone matchStudentleavesfield mid-matchTeampickssisterteam“Is there apracticefield?”Adultupset atevent staffSomeonehas to callDillonTeam setsup onwrongfieldParentasks howrankingsworkEntireteam intearsMicrophonesnaps,cracklesand popsSister teams inthe same matchaccidentallyswitchcontrollersSomeoneother thanRyan or Johnhead refsNo staff atscoringtable“Have youprinted thematchschedule?”Refs chasegame objectsthat leavethe fieldMemeonrobotNoclawbotsat eventVenuelosespowerInexplicableTournamentManagerproblemMatchstarts tooearly“I need asingle studentrepresentativefrom eachteam”RefsearchesQ&ATMlagsVolunteersstay inhotel withteam(s)Team triesto scoreSPs butlosesStudent runsaway from thefield to avoidwearing thegoggles ofshameMatchstarts 10+minuteslateWallbotVenueroofleaksWindowssystemsoundsover PATeambrakes afieldelementMultipleteams withidenticalnamesTeamarrives 4+matchesearlyAdultcryingTeamforgetsnotebook“Whatmatch arewe on?”Someone saysVia isn’tworking but isjust looking atthe wrong eventEveryteamposts askills runSharp robotcomponentdraws bloodSomeonewalks infront of theprojectorTeamdoesn’tunderstandSPsAwardwinnersaccidentallyrevealedearlyAudiencecheers athead refrulingRobot builtthe nightbefore theeventNetworkingproblemsTeam forgetsto connectbattery, turnon robot, orstart programTeam saysthey’re ready,then reachesin to adjustrobotNo robotsmove inautonMatchDQRobotwith <4wheelsRobotthrowsgameelementsRyangetsdistractedSpeakertakes toolong atawardsRealstaticguard“Fieldstatic”Matchstarts 10+minutesearlyTeam withwrong colorlicenseplatesTM opmissesmatchcountdownScorekeeperdistracted byphone / foodToddgoesmissingPlacebostaticguardMusic stopsplaying andno onenoticesAutonconsistingof randommovementsMatchno-showMexicanfood fordinnerRobotBreaks“Is theskills fieldopen?”Tie ineliminationsTMAudiobugsTeam failsfieldcontrolcheckTeam withno licenseplatesRobotparts lefton fieldSomeonetrips overa cableVenue-providedAV breaksWaterspilledon field“Whydidn’t wewin [awardx]?”Philip’strackballfalls outTeamstealsfieldelementsCoachswearingPapertestPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesMatchsequencebreakScoringtablelosespowerCortexrobot inQF orlaterPhilipdevises“creative”technicalsolutionPrintermisbehaves“When dowe get ournotebooksback?”<50% ofteamspost skillsrunsUpsetin elimsRobotrebuildover lunchRyan andJohnswitchrolesTeam usesfreezespray/cannedairRyan hasa “word ofthe day”AudienceboosstrategicalliancedeclineLargesubsystemsummarilyremoved fromrobot mid-eventPi hasto beresetRef closelyexaminesfieldelements orrobotHead refand MC arethe samepersonHelicoptercoachDroppedcontrollerVenueinternetblockssomethingMemeonrobotBothalliancescross theline in autonAutomaticWindowsupdatebreaks thingsRyansummonsJohn overloudspeakerTeam doesn’tunderstandhow allianceselectionworksAdultworkingon robotSomeonegets hit byan unfoldingtraybotSame pineeds to berebootedmultipletimesSomeone fallsoff achair/bleachersLast minuterobotbatteryswapRyan or Johndescribesrobottroubleshootingover the micRyan getsirritated andshuts offmic to ventAdult asksrefsquestionsafter beingtold not toAdultwon’t letthe kidstalkMultipleDQs inone matchStudentleavesfield mid-matchTeampickssisterteam“Is there apracticefield?”Adultupset atevent staffSomeonehas to callDillonTeam setsup onwrongfieldParentasks howrankingsworkEntireteam intearsMicrophonesnaps,cracklesand popsSister teams inthe same matchaccidentallyswitchcontrollersSomeoneother thanRyan or Johnhead refsNo staff atscoringtable“Have youprinted thematchschedule?”Refs chasegame objectsthat leavethe fieldMemeonrobotNoclawbotsat eventVenuelosespowerInexplicableTournamentManagerproblemMatchstarts tooearly“I need asingle studentrepresentativefrom eachteam”RefsearchesQ&ATMlagsVolunteersstay inhotel withteam(s)Team triesto scoreSPs butlosesStudent runsaway from thefield to avoidwearing thegoggles ofshameMatchstarts 10+minuteslateWallbotVenueroofleaksWindowssystemsoundsover PATeambrakes afieldelementMultipleteams withidenticalnamesTeamarrives 4+matchesearlyAdultcryingTeamforgetsnotebook“Whatmatch arewe on?”Someone saysVia isn’tworking but isjust looking atthe wrong eventEveryteamposts askills runSharp robotcomponentdraws bloodSomeonewalks infront of theprojector

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