Pi hasto beresetRobotrebuildover lunchRefsearchesQ&ANo robotsmove inautonMemeonrobotMatchstarts tooearlyMatchstarts 10+minutesearlySharp robotcomponentdraws bloodRobot builtthe nightbefore theeventCoachswearingDroppedcontrollerAwardwinnersaccidentallyrevealedearlySomeonetrips overa cableLargesubsystemsummarilyremoved fromrobot mid-eventAudiencecheers athead refrulingRyan getsirritated andshuts offmic to ventRealstaticguardTeam triesto scoreSPs butlosesSpeakertakes toolong atawardsPlacebostaticguardRef closelyexaminesfieldelements orrobotAutomaticWindowsupdatebreaks thingsParentasks howrankingsworkAdultwon’t letthe kidstalk“Have youprinted thematchschedule?”Team usesfreezespray/cannedairWaterspilledon fieldRyan hasa “word ofthe day”Head refand MC arethe samepersonRyan or Johndescribesrobottroubleshootingover the micWallbotVenueinternetblockssomethingStudent runsaway from thefield to avoidwearing thegoggles ofshameWindowssystemsoundsover PATMAudiobugsSomeonegets hit byan unfoldingtraybotRobotwith <4wheelsEntireteam intearsToddgoesmissing“Is theskills fieldopen?”Papertest“Fieldstatic”Team failsfieldcontrolcheckUpsetin elimsPhilip’strackballfalls outCortexrobot inQF orlaterTeam saysthey’re ready,then reachesin to adjustrobotVenueroofleaksSame pineeds to berebootedmultipletimesTeamarrives 4+matchesearlyEveryteamposts askills runRyan andJohnswitchrolesSomeone fallsoff achair/bleachersTeam forgetsto connectbattery, turnon robot, orstart programScoringtablelosespowerAdultupset atevent staffAdult asksrefsquestionsafter beingtold not toStudentleavesfield mid-matchTeam withwrong colorlicenseplatesRobotthrowsgameelementsAudienceboosstrategicalliancedeclineBothalliancescross theline in autonSomeoneother thanRyan or Johnhead refsTeamforgetsnotebookInexplicableTournamentManagerproblemTie ineliminationsMusic stopsplaying andno onenoticesAdultcryingNoclawbotsat eventSomeonehas to callDillonMemeonrobotMultipleteams withidenticalnamesVenue-providedAV breaksTM opmissesmatchcountdownMatchsequencebreakPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficulties“I need asingle studentrepresentativefrom eachteam”VenuelosespowerMultipleDQs inone matchMexicanfood fordinnerSomeone saysVia isn’tworking but isjust looking atthe wrong eventAdultworkingon robotTeamdoesn’tunderstandSPsMatchstarts 10+minuteslateRefs chasegame objectsthat leavethe fieldRobotBreaks“Whatmatch arewe on?”Volunteersstay inhotel withteam(s)RyangetsdistractedAutonconsistingof randommovementsTeam setsup onwrongfieldNetworkingproblemsSister teams inthe same matchaccidentallyswitchcontrollersScorekeeperdistracted byphone / food“Is there apracticefield?”HelicoptercoachMicrophonesnaps,cracklesand popsRobotparts lefton field“When dowe get ournotebooksback?”“Whydidn’t wewin [awardx]?”PrintermisbehavesMatchDQTeam withno licenseplatesSomeonewalks infront of theprojector<50% ofteamspost skillsrunsTeamstealsfieldelementsLast minuterobotbatteryswapNo staff atscoringtableMatchno-showTeambrakes afieldelementPhilipdevises“creative”technicalsolutionTMlagsTeam doesn’tunderstandhow allianceselectionworksRyansummonsJohn overloudspeakerTeampickssisterteamPi hasto beresetRobotrebuildover lunchRefsearchesQ&ANo robotsmove inautonMemeonrobotMatchstarts tooearlyMatchstarts 10+minutesearlySharp robotcomponentdraws bloodRobot builtthe nightbefore theeventCoachswearingDroppedcontrollerAwardwinnersaccidentallyrevealedearlySomeonetrips overa cableLargesubsystemsummarilyremoved fromrobot mid-eventAudiencecheers athead refrulingRyan getsirritated andshuts offmic to ventRealstaticguardTeam triesto scoreSPs butlosesSpeakertakes toolong atawardsPlacebostaticguardRef closelyexaminesfieldelements orrobotAutomaticWindowsupdatebreaks thingsParentasks howrankingsworkAdultwon’t letthe kidstalk“Have youprinted thematchschedule?”Team usesfreezespray/cannedairWaterspilledon fieldRyan hasa “word ofthe day”Head refand MC arethe samepersonRyan or Johndescribesrobottroubleshootingover the micWallbotVenueinternetblockssomethingStudent runsaway from thefield to avoidwearing thegoggles ofshameWindowssystemsoundsover PATMAudiobugsSomeonegets hit byan unfoldingtraybotRobotwith <4wheelsEntireteam intearsToddgoesmissing“Is theskills fieldopen?”Papertest“Fieldstatic”Team failsfieldcontrolcheckUpsetin elimsPhilip’strackballfalls outCortexrobot inQF orlaterTeam saysthey’re ready,then reachesin to adjustrobotVenueroofleaksSame pineeds to berebootedmultipletimesTeamarrives 4+matchesearlyEveryteamposts askills runRyan andJohnswitchrolesSomeone fallsoff achair/bleachersTeam forgetsto connectbattery, turnon robot, orstart programScoringtablelosespowerAdultupset atevent staffAdult asksrefsquestionsafter beingtold not toStudentleavesfield mid-matchTeam withwrong colorlicenseplatesRobotthrowsgameelementsAudienceboosstrategicalliancedeclineBothalliancescross theline in autonSomeoneother thanRyan or Johnhead refsTeamforgetsnotebookInexplicableTournamentManagerproblemTie ineliminationsMusic stopsplaying andno onenoticesAdultcryingNoclawbotsat eventSomeonehas to callDillonMemeonrobotMultipleteams withidenticalnamesVenue-providedAV breaksTM opmissesmatchcountdownMatchsequencebreakPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficulties“I need asingle studentrepresentativefrom eachteam”VenuelosespowerMultipleDQs inone matchMexicanfood fordinnerSomeone saysVia isn’tworking but isjust looking atthe wrong eventAdultworkingon robotTeamdoesn’tunderstandSPsMatchstarts 10+minuteslateRefs chasegame objectsthat leavethe fieldRobotBreaks“Whatmatch arewe on?”Volunteersstay inhotel withteam(s)RyangetsdistractedAutonconsistingof randommovementsTeam setsup onwrongfieldNetworkingproblemsSister teams inthe same matchaccidentallyswitchcontrollersScorekeeperdistracted byphone / food“Is there apracticefield?”HelicoptercoachMicrophonesnaps,cracklesand popsRobotparts lefton field“When dowe get ournotebooksback?”“Whydidn’t wewin [awardx]?”PrintermisbehavesMatchDQTeam withno licenseplatesSomeonewalks infront of theprojector<50% ofteamspost skillsrunsTeamstealsfieldelementsLast minuterobotbatteryswapNo staff atscoringtableMatchno-showTeambrakes afieldelementPhilipdevises“creative”technicalsolutionTMlagsTeam doesn’tunderstandhow allianceselectionworksRyansummonsJohn overloudspeakerTeampickssisterteam

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