Matchstarts 10+minutesearlyWindowssystemsoundsover PAPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesRyansummonsJohn overloudspeakerTM opmissesmatchcountdownNetworkingproblemsTeambrakes afieldelementRef closelyexaminesfieldelements orrobotMemeonrobotTeam withwrong colorlicenseplatesVenueroofleaksMexicanfood fordinnerMatchno-show“Whatmatch arewe on?”Same pineeds to berebootedmultipletimesLargesubsystemsummarilyremoved fromrobot mid-eventPhilip’strackballfalls outTeam failsfieldcontrolcheckRyangetsdistractedRealstaticguardTie ineliminationsSomeonegets hit byan unfoldingtraybotInexplicableTournamentManagerproblemWallbotTMAudiobugsSomeonewalks infront of theprojectorNo staff atscoringtableSomeonehas to callDillonTeam triesto scoreSPs butlosesScoringtablelosespowerTeam doesn’tunderstandhow allianceselectionworks“I need asingle studentrepresentativefrom eachteam”MatchDQVenuelosespowerMatchsequencebreakMultipleteams withidenticalnamesAdultwon’t letthe kidstalkStudentleavesfield mid-matchMultipleDQs inone matchRyan getsirritated andshuts offmic to ventPlacebostaticguardHead refand MC arethe samepersonNoclawbotsat eventTMlagsNo robotsmove inautonPhilipdevises“creative”technicalsolutionAdultworkingon robotVenueinternetblockssomethingTeampickssisterteamAutomaticWindowsupdatebreaks things“Is there apracticefield?”Entireteam intearsRobotwith <4wheelsAutonconsistingof randommovementsSomeone fallsoff achair/bleachersUpsetin elimsMatchstarts tooearlyRobotparts lefton fieldRyan andJohnswitchrolesVenue-providedAV breaksRyan or Johndescribesrobottroubleshootingover the micTeam forgetsto connectbattery, turnon robot, orstart programPi hasto beresetCoachswearingBothalliancescross theline in autonRobotrebuildover lunchToddgoesmissingDroppedcontrollerSpeakertakes toolong atawardsRobotBreaksHelicoptercoachWaterspilledon fieldSomeoneother thanRyan or Johnhead refsCortexrobot inQF orlaterLast minuterobotbatteryswapSomeonetrips overa cableRobot builtthe nightbefore theeventTeamarrives 4+matchesearlyMusic stopsplaying andno onenoticesTeamforgetsnotebookParentasks howrankingswork<50% ofteamspost skillsrunsVolunteersstay inhotel withteam(s)Microphonesnaps,cracklesand pops“Fieldstatic”Adult asksrefsquestionsafter beingtold not toTeam setsup onwrongfieldStudent runsaway from thefield to avoidwearing thegoggles ofshameRyan hasa “word ofthe day”RefsearchesQ&AMatchstarts 10+minuteslateTeam withno licenseplatesRobotthrowsgameelementsAdultcryingRefs chasegame objectsthat leavethe field“Have youprinted thematchschedule?”“When dowe get ournotebooksback?”Teamdoesn’tunderstandSPsAdultupset atevent staffSharp robotcomponentdraws bloodScorekeeperdistracted byphone / food“Is theskills fieldopen?”AudienceboosstrategicalliancedeclineEveryteamposts askills runPrintermisbehavesSister teams inthe same matchaccidentallyswitchcontrollersAudiencecheers athead refrulingTeam usesfreezespray/cannedairTeam saysthey’re ready,then reachesin to adjustrobotAwardwinnersaccidentallyrevealedearly“Whydidn’t wewin [awardx]?”PapertestSomeone saysVia isn’tworking but isjust looking atthe wrong eventMemeonrobotTeamstealsfieldelementsMatchstarts 10+minutesearlyWindowssystemsoundsover PAPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesRyansummonsJohn overloudspeakerTM opmissesmatchcountdownNetworkingproblemsTeambrakes afieldelementRef closelyexaminesfieldelements orrobotMemeonrobotTeam withwrong colorlicenseplatesVenueroofleaksMexicanfood fordinnerMatchno-show“Whatmatch arewe on?”Same pineeds to berebootedmultipletimesLargesubsystemsummarilyremoved fromrobot mid-eventPhilip’strackballfalls outTeam failsfieldcontrolcheckRyangetsdistractedRealstaticguardTie ineliminationsSomeonegets hit byan unfoldingtraybotInexplicableTournamentManagerproblemWallbotTMAudiobugsSomeonewalks infront of theprojectorNo staff atscoringtableSomeonehas to callDillonTeam triesto scoreSPs butlosesScoringtablelosespowerTeam doesn’tunderstandhow allianceselectionworks“I need asingle studentrepresentativefrom eachteam”MatchDQVenuelosespowerMatchsequencebreakMultipleteams withidenticalnamesAdultwon’t letthe kidstalkStudentleavesfield mid-matchMultipleDQs inone matchRyan getsirritated andshuts offmic to ventPlacebostaticguardHead refand MC arethe samepersonNoclawbotsat eventTMlagsNo robotsmove inautonPhilipdevises“creative”technicalsolutionAdultworkingon robotVenueinternetblockssomethingTeampickssisterteamAutomaticWindowsupdatebreaks things“Is there apracticefield?”Entireteam intearsRobotwith <4wheelsAutonconsistingof randommovementsSomeone fallsoff achair/bleachersUpsetin elimsMatchstarts tooearlyRobotparts lefton fieldRyan andJohnswitchrolesVenue-providedAV breaksRyan or Johndescribesrobottroubleshootingover the micTeam forgetsto connectbattery, turnon robot, orstart programPi hasto beresetCoachswearingBothalliancescross theline in autonRobotrebuildover lunchToddgoesmissingDroppedcontrollerSpeakertakes toolong atawardsRobotBreaksHelicoptercoachWaterspilledon fieldSomeoneother thanRyan or Johnhead refsCortexrobot inQF orlaterLast minuterobotbatteryswapSomeonetrips overa cableRobot builtthe nightbefore theeventTeamarrives 4+matchesearlyMusic stopsplaying andno onenoticesTeamforgetsnotebookParentasks howrankingswork<50% ofteamspost skillsrunsVolunteersstay inhotel withteam(s)Microphonesnaps,cracklesand pops“Fieldstatic”Adult asksrefsquestionsafter beingtold not toTeam setsup onwrongfieldStudent runsaway from thefield to avoidwearing thegoggles ofshameRyan hasa “word ofthe day”RefsearchesQ&AMatchstarts 10+minuteslateTeam withno licenseplatesRobotthrowsgameelementsAdultcryingRefs chasegame objectsthat leavethe field“Have youprinted thematchschedule?”“When dowe get ournotebooksback?”Teamdoesn’tunderstandSPsAdultupset atevent staffSharp robotcomponentdraws bloodScorekeeperdistracted byphone / food“Is theskills fieldopen?”AudienceboosstrategicalliancedeclineEveryteamposts askills runPrintermisbehavesSister teams inthe same matchaccidentallyswitchcontrollersAudiencecheers athead refrulingTeam usesfreezespray/cannedairTeam saysthey’re ready,then reachesin to adjustrobotAwardwinnersaccidentallyrevealedearly“Whydidn’t wewin [awardx]?”PapertestSomeone saysVia isn’tworking but isjust looking atthe wrong eventMemeonrobotTeamstealsfieldelements

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