RyangetsdistractedTeam forgetsto connectbattery, turnon robot, orstart programTeam triesto scoreSPs butlosesTie ineliminationsRef closelyexaminesfieldelements orrobotStudentleavesfield mid-matchUpsetin elimsCoachswearingMatchno-showInexplicableTournamentManagerproblem“When dowe get ournotebooksback?”Sharp robotcomponentdraws bloodVenueroofleaksSister teams inthe same matchaccidentallyswitchcontrollersScoringtablelosespowerAutomaticWindowsupdatebreaks thingsRobotrebuildover lunchRyan or Johndescribesrobottroubleshootingover the micMexicanfood fordinnerTeamstealsfieldelementsMusic stopsplaying andno onenoticesVolunteersstay inhotel withteam(s)Ryan getsirritated andshuts offmic to ventVenuelosespowerPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSpeakertakes toolong atawardsVenueinternetblockssomethingToddgoesmissingMicrophonesnaps,cracklesand popsSomeone saysVia isn’tworking but isjust looking atthe wrong eventMemeonrobotNetworkingproblemsTeampickssisterteamCortexrobot inQF orlaterTMlagsMemeonrobotMultipleteams withidenticalnamesMatchstarts 10+minuteslateTeam withno licenseplatesAdult asksrefsquestionsafter beingtold not toPapertest“Is there apracticefield?”Printermisbehaves“Have youprinted thematchschedule?”Adultupset atevent staffAdultworkingon robotTeam usesfreezespray/cannedairHead refand MC arethe sameperson“Is theskills fieldopen?”Pi hasto beresetWaterspilledon fieldRobotthrowsgameelementsMultipleDQs inone matchStudent runsaway from thefield to avoidwearing thegoggles ofshameRyan hasa “word ofthe day”Team doesn’tunderstandhow allianceselectionworksAdultcryingSomeonehas to callDillonBothalliancescross theline in autonAutonconsistingof randommovementsVenue-providedAV breaksRobotwith <4wheelsMatchDQPhilipdevises“creative”technicalsolutionAwardwinnersaccidentallyrevealedearlyTM opmissesmatchcountdownNoclawbotsat event“I need asingle studentrepresentativefrom eachteam”Same pineeds to berebootedmultipletimesRyan andJohnswitchrolesDroppedcontroller“Fieldstatic”HelicoptercoachMatchsequencebreakLargesubsystemsummarilyremoved fromrobot mid-eventWallbotPhilip’strackballfalls out“Whydidn’t wewin [awardx]?”Teamarrives 4+matchesearlySomeone fallsoff achair/bleachers“Whatmatch arewe on?”Someonegets hit byan unfoldingtraybotNo robotsmove inautonScorekeeperdistracted byphone / foodRobotBreaksSomeonetrips overa cableRobotparts lefton fieldTMAudiobugsMatchstarts 10+minutesearly<50% ofteamspost skillsrunsRyansummonsJohn overloudspeakerTeam withwrong colorlicenseplatesMatchstarts tooearlyNo staff atscoringtableParentasks howrankingsworkTeambrakes afieldelementTeam failsfieldcontrolcheckEntireteam intearsTeam saysthey’re ready,then reachesin to adjustrobotRobot builtthe nightbefore theeventRefsearchesQ&APlacebostaticguardAudienceboosstrategicalliancedeclineAudiencecheers athead refrulingTeamdoesn’tunderstandSPsSomeonewalks infront of theprojectorRealstaticguardAdultwon’t letthe kidstalkRefs chasegame objectsthat leavethe fieldWindowssystemsoundsover PALast minuterobotbatteryswapTeam setsup onwrongfieldTeamforgetsnotebookEveryteamposts askills runSomeoneother thanRyan or Johnhead refsRyangetsdistractedTeam forgetsto connectbattery, turnon robot, orstart programTeam triesto scoreSPs butlosesTie ineliminationsRef closelyexaminesfieldelements orrobotStudentleavesfield mid-matchUpsetin elimsCoachswearingMatchno-showInexplicableTournamentManagerproblem“When dowe get ournotebooksback?”Sharp robotcomponentdraws bloodVenueroofleaksSister teams inthe same matchaccidentallyswitchcontrollersScoringtablelosespowerAutomaticWindowsupdatebreaks thingsRobotrebuildover lunchRyan or Johndescribesrobottroubleshootingover the micMexicanfood fordinnerTeamstealsfieldelementsMusic stopsplaying andno onenoticesVolunteersstay inhotel withteam(s)Ryan getsirritated andshuts offmic to ventVenuelosespowerPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSpeakertakes toolong atawardsVenueinternetblockssomethingToddgoesmissingMicrophonesnaps,cracklesand popsSomeone saysVia isn’tworking but isjust looking atthe wrong eventMemeonrobotNetworkingproblemsTeampickssisterteamCortexrobot inQF orlaterTMlagsMemeonrobotMultipleteams withidenticalnamesMatchstarts 10+minuteslateTeam withno licenseplatesAdult asksrefsquestionsafter beingtold not toPapertest“Is there apracticefield?”Printermisbehaves“Have youprinted thematchschedule?”Adultupset atevent staffAdultworkingon robotTeam usesfreezespray/cannedairHead refand MC arethe sameperson“Is theskills fieldopen?”Pi hasto beresetWaterspilledon fieldRobotthrowsgameelementsMultipleDQs inone matchStudent runsaway from thefield to avoidwearing thegoggles ofshameRyan hasa “word ofthe day”Team doesn’tunderstandhow allianceselectionworksAdultcryingSomeonehas to callDillonBothalliancescross theline in autonAutonconsistingof randommovementsVenue-providedAV breaksRobotwith <4wheelsMatchDQPhilipdevises“creative”technicalsolutionAwardwinnersaccidentallyrevealedearlyTM opmissesmatchcountdownNoclawbotsat event“I need asingle studentrepresentativefrom eachteam”Same pineeds to berebootedmultipletimesRyan andJohnswitchrolesDroppedcontroller“Fieldstatic”HelicoptercoachMatchsequencebreakLargesubsystemsummarilyremoved fromrobot mid-eventWallbotPhilip’strackballfalls out“Whydidn’t wewin [awardx]?”Teamarrives 4+matchesearlySomeone fallsoff achair/bleachers“Whatmatch arewe on?”Someonegets hit byan unfoldingtraybotNo robotsmove inautonScorekeeperdistracted byphone / foodRobotBreaksSomeonetrips overa cableRobotparts lefton fieldTMAudiobugsMatchstarts 10+minutesearly<50% ofteamspost skillsrunsRyansummonsJohn overloudspeakerTeam withwrong colorlicenseplatesMatchstarts tooearlyNo staff atscoringtableParentasks howrankingsworkTeambrakes afieldelementTeam failsfieldcontrolcheckEntireteam intearsTeam saysthey’re ready,then reachesin to adjustrobotRobot builtthe nightbefore theeventRefsearchesQ&APlacebostaticguardAudienceboosstrategicalliancedeclineAudiencecheers athead refrulingTeamdoesn’tunderstandSPsSomeonewalks infront of theprojectorRealstaticguardAdultwon’t letthe kidstalkRefs chasegame objectsthat leavethe fieldWindowssystemsoundsover PALast minuterobotbatteryswapTeam setsup onwrongfieldTeamforgetsnotebookEveryteamposts askills runSomeoneother thanRyan or Johnhead refs

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