Teamstealsfieldelements“Whydidn’t wewin [awardx]?”Team withwrong colorlicenseplatesRobotrebuildover lunchTeam setsup onwrongfieldSomeonewalks infront of theprojectorAudienceboosstrategicalliancedeclineMultipleteams withidenticalnamesSharp robotcomponentdraws blood“Is there apracticefield?”Someone fallsoff achair/bleachers“Have youprinted thematchschedule?”RyangetsdistractedEveryteamposts askills runPhilip’strackballfalls outMatchDQHead refand MC arethe samepersonVenuelosespowerScorekeeperdistracted byphone / foodTMAudiobugsTeam failsfieldcontrolcheckMicrophonesnaps,cracklesand popsRobotparts lefton fieldInexplicableTournamentManagerproblemAdult asksrefsquestionsafter beingtold not toMatchsequencebreak“Whatmatch arewe on?”Ryan andJohnswitchrolesPrintermisbehavesAudiencecheers athead refruling<50% ofteamspost skillsrunsCoachswearingAutonconsistingof randommovementsAdultcryingAwardwinnersaccidentallyrevealedearlyMusic stopsplaying andno onenoticesUpsetin elimsTie ineliminationsRobot builtthe nightbefore theeventMatchno-showPlacebostaticguardRyan or Johndescribesrobottroubleshootingover the micSame pineeds to berebootedmultipletimesPapertestMemeonrobotLargesubsystemsummarilyremoved fromrobot mid-eventLast minuterobotbatteryswapNo staff atscoringtableParentasks howrankingsworkSomeone saysVia isn’tworking but isjust looking atthe wrong eventToddgoesmissingSister teams inthe same matchaccidentallyswitchcontrollersRyan hasa “word ofthe day”Robotwith <4wheelsMatchstarts 10+minutesearlyTMlagsHelicoptercoachVenueroofleaksTeam saysthey’re ready,then reachesin to adjustrobotMemeonrobotSomeonegets hit byan unfoldingtraybotMatchstarts tooearlyTeamarrives 4+matchesearlyRefs chasegame objectsthat leavethe fieldPi hasto bereset“Fieldstatic”Team doesn’tunderstandhow allianceselectionworksRyansummonsJohn overloudspeakerDroppedcontrollerWaterspilledon fieldStudentleavesfield mid-matchVolunteersstay inhotel withteam(s)Matchstarts 10+minuteslateTeam withno licenseplatesRef closelyexaminesfieldelements orrobotSpeakertakes toolong atawardsPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeambrakes afieldelementRobotBreaksVenue-providedAV breaksMexicanfood fordinnerTeamforgetsnotebookRealstaticguardStudent runsaway from thefield to avoidwearing thegoggles ofshameSomeonehas to callDillonScoringtablelosespowerAdultworkingon robotWindowssystemsoundsover PABothalliancescross theline in autonTeam triesto scoreSPs butlosesPhilipdevises“creative”technicalsolution“I need asingle studentrepresentativefrom eachteam”NetworkingproblemsAutomaticWindowsupdatebreaks thingsMultipleDQs inone matchRyan getsirritated andshuts offmic to ventSomeonetrips overa cableTeam forgetsto connectbattery, turnon robot, orstart programTM opmissesmatchcountdownRefsearchesQ&ACortexrobot inQF orlaterEntireteam intearsNo robotsmove inautonVenueinternetblockssomethingWallbotAdultupset atevent staffTeampickssisterteamTeamdoesn’tunderstandSPs“When dowe get ournotebooksback?”Noclawbotsat eventRobotthrowsgameelements“Is theskills fieldopen?”Someoneother thanRyan or Johnhead refsTeam usesfreezespray/cannedairAdultwon’t letthe kidstalkTeamstealsfieldelements“Whydidn’t wewin [awardx]?”Team withwrong colorlicenseplatesRobotrebuildover lunchTeam setsup onwrongfieldSomeonewalks infront of theprojectorAudienceboosstrategicalliancedeclineMultipleteams withidenticalnamesSharp robotcomponentdraws blood“Is there apracticefield?”Someone fallsoff achair/bleachers“Have youprinted thematchschedule?”RyangetsdistractedEveryteamposts askills runPhilip’strackballfalls outMatchDQHead refand MC arethe samepersonVenuelosespowerScorekeeperdistracted byphone / foodTMAudiobugsTeam failsfieldcontrolcheckMicrophonesnaps,cracklesand popsRobotparts lefton fieldInexplicableTournamentManagerproblemAdult asksrefsquestionsafter beingtold not toMatchsequencebreak“Whatmatch arewe on?”Ryan andJohnswitchrolesPrintermisbehavesAudiencecheers athead refruling<50% ofteamspost skillsrunsCoachswearingAutonconsistingof randommovementsAdultcryingAwardwinnersaccidentallyrevealedearlyMusic stopsplaying andno onenoticesUpsetin elimsTie ineliminationsRobot builtthe nightbefore theeventMatchno-showPlacebostaticguardRyan or Johndescribesrobottroubleshootingover the micSame pineeds to berebootedmultipletimesPapertestMemeonrobotLargesubsystemsummarilyremoved fromrobot mid-eventLast minuterobotbatteryswapNo staff atscoringtableParentasks howrankingsworkSomeone saysVia isn’tworking but isjust looking atthe wrong eventToddgoesmissingSister teams inthe same matchaccidentallyswitchcontrollersRyan hasa “word ofthe day”Robotwith <4wheelsMatchstarts 10+minutesearlyTMlagsHelicoptercoachVenueroofleaksTeam saysthey’re ready,then reachesin to adjustrobotMemeonrobotSomeonegets hit byan unfoldingtraybotMatchstarts tooearlyTeamarrives 4+matchesearlyRefs chasegame objectsthat leavethe fieldPi hasto bereset“Fieldstatic”Team doesn’tunderstandhow allianceselectionworksRyansummonsJohn overloudspeakerDroppedcontrollerWaterspilledon fieldStudentleavesfield mid-matchVolunteersstay inhotel withteam(s)Matchstarts 10+minuteslateTeam withno licenseplatesRef closelyexaminesfieldelements orrobotSpeakertakes toolong atawardsPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeambrakes afieldelementRobotBreaksVenue-providedAV breaksMexicanfood fordinnerTeamforgetsnotebookRealstaticguardStudent runsaway from thefield to avoidwearing thegoggles ofshameSomeonehas to callDillonScoringtablelosespowerAdultworkingon robotWindowssystemsoundsover PABothalliancescross theline in autonTeam triesto scoreSPs butlosesPhilipdevises“creative”technicalsolution“I need asingle studentrepresentativefrom eachteam”NetworkingproblemsAutomaticWindowsupdatebreaks thingsMultipleDQs inone matchRyan getsirritated andshuts offmic to ventSomeonetrips overa cableTeam forgetsto connectbattery, turnon robot, orstart programTM opmissesmatchcountdownRefsearchesQ&ACortexrobot inQF orlaterEntireteam intearsNo robotsmove inautonVenueinternetblockssomethingWallbotAdultupset atevent staffTeampickssisterteamTeamdoesn’tunderstandSPs“When dowe get ournotebooksback?”Noclawbotsat eventRobotthrowsgameelements“Is theskills fieldopen?”Someoneother thanRyan or Johnhead refsTeam usesfreezespray/cannedairAdultwon’t letthe kidstalk

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