AdultcryingRyan or Johndescribesrobottroubleshootingover the micPhilip’strackballfalls outRobotrebuildover lunchPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSomeonehas to callDillonVenueroofleaksNo robotsmove inautonUpsetin elimsTeamarrives 4+matchesearlyRyan andJohnswitchroles“Fieldstatic”Ryan hasa “word ofthe day”Printermisbehaves<50% ofteamspost skillsrunsAdult asksrefsquestionsafter beingtold not toHead refand MC arethe samepersonSomeoneother thanRyan or Johnhead refsAdultwon’t letthe kidstalkRobotthrowsgameelementsRefsearchesQ&ASpeakertakes toolong atawardsSomeonewalks infront of theprojectorSomeonegets hit byan unfoldingtraybotMatchno-showEntireteam intearsAutonconsistingof randommovementsMatchstarts 10+minuteslateEveryteamposts askills runPhilipdevises“creative”technicalsolutionRef closelyexaminesfieldelements orrobotCoachswearingMexicanfood fordinnerTeam saysthey’re ready,then reachesin to adjustrobotTMlagsTeam triesto scoreSPs butlosesMatchDQMatchstarts 10+minutesearlyVenueinternetblockssomethingLast minuterobotbatteryswapMemeonrobotRobotwith <4wheelsRobotBreaksSame pineeds to berebootedmultipletimesTeampickssisterteam“I need asingle studentrepresentativefrom eachteam”No staff atscoringtableCortexrobot inQF orlaterTeam doesn’tunderstandhow allianceselectionworksBothalliancescross theline in autonWallbotTeam forgetsto connectbattery, turnon robot, orstart programStudent runsaway from thefield to avoidwearing thegoggles ofshamePi hasto beresetSomeone fallsoff achair/bleachersStudentleavesfield mid-matchRyansummonsJohn overloudspeakerWindowssystemsoundsover PAToddgoesmissingTeam failsfieldcontrolcheck“When dowe get ournotebooksback?”Audiencecheers athead refrulingRealstaticguard“Have youprinted thematchschedule?”Awardwinnersaccidentallyrevealedearly“Is theskills fieldopen?”Sister teams inthe same matchaccidentallyswitchcontrollersRobotparts lefton fieldScoringtablelosespowerMicrophonesnaps,cracklesand popsAudienceboosstrategicalliancedeclineTM opmissesmatchcountdownInexplicableTournamentManagerproblemTMAudiobugsMatchstarts tooearlySomeonetrips overa cable“Whydidn’t wewin [awardx]?”MultipleDQs inone matchHelicoptercoachNetworkingproblemsRefs chasegame objectsthat leavethe field“Is there apracticefield?”PlacebostaticguardTeambrakes afieldelementDroppedcontrollerVenue-providedAV breaksTeamstealsfieldelementsSomeone saysVia isn’tworking but isjust looking atthe wrong eventAdultworkingon robotTeam withno licenseplatesNoclawbotsat eventTie ineliminationsLargesubsystemsummarilyremoved fromrobot mid-eventAdultupset atevent staffAutomaticWindowsupdatebreaks things“Whatmatch arewe on?”RyangetsdistractedTeam withwrong colorlicenseplatesVolunteersstay inhotel withteam(s)Sharp robotcomponentdraws bloodMultipleteams withidenticalnamesParentasks howrankingsworkPapertestVenuelosespowerRobot builtthe nightbefore theeventTeam usesfreezespray/cannedairWaterspilledon fieldTeamforgetsnotebookRyan getsirritated andshuts offmic to ventScorekeeperdistracted byphone / foodMatchsequencebreakMusic stopsplaying andno onenoticesTeam setsup onwrongfieldTeamdoesn’tunderstandSPsMemeonrobotAdultcryingRyan or Johndescribesrobottroubleshootingover the micPhilip’strackballfalls outRobotrebuildover lunchPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSomeonehas to callDillonVenueroofleaksNo robotsmove inautonUpsetin elimsTeamarrives 4+matchesearlyRyan andJohnswitchroles“Fieldstatic”Ryan hasa “word ofthe day”Printermisbehaves<50% ofteamspost skillsrunsAdult asksrefsquestionsafter beingtold not toHead refand MC arethe samepersonSomeoneother thanRyan or Johnhead refsAdultwon’t letthe kidstalkRobotthrowsgameelementsRefsearchesQ&ASpeakertakes toolong atawardsSomeonewalks infront of theprojectorSomeonegets hit byan unfoldingtraybotMatchno-showEntireteam intearsAutonconsistingof randommovementsMatchstarts 10+minuteslateEveryteamposts askills runPhilipdevises“creative”technicalsolutionRef closelyexaminesfieldelements orrobotCoachswearingMexicanfood fordinnerTeam saysthey’re ready,then reachesin to adjustrobotTMlagsTeam triesto scoreSPs butlosesMatchDQMatchstarts 10+minutesearlyVenueinternetblockssomethingLast minuterobotbatteryswapMemeonrobotRobotwith <4wheelsRobotBreaksSame pineeds to berebootedmultipletimesTeampickssisterteam“I need asingle studentrepresentativefrom eachteam”No staff atscoringtableCortexrobot inQF orlaterTeam doesn’tunderstandhow allianceselectionworksBothalliancescross theline in autonWallbotTeam forgetsto connectbattery, turnon robot, orstart programStudent runsaway from thefield to avoidwearing thegoggles ofshamePi hasto beresetSomeone fallsoff achair/bleachersStudentleavesfield mid-matchRyansummonsJohn overloudspeakerWindowssystemsoundsover PAToddgoesmissingTeam failsfieldcontrolcheck“When dowe get ournotebooksback?”Audiencecheers athead refrulingRealstaticguard“Have youprinted thematchschedule?”Awardwinnersaccidentallyrevealedearly“Is theskills fieldopen?”Sister teams inthe same matchaccidentallyswitchcontrollersRobotparts lefton fieldScoringtablelosespowerMicrophonesnaps,cracklesand popsAudienceboosstrategicalliancedeclineTM opmissesmatchcountdownInexplicableTournamentManagerproblemTMAudiobugsMatchstarts tooearlySomeonetrips overa cable“Whydidn’t wewin [awardx]?”MultipleDQs inone matchHelicoptercoachNetworkingproblemsRefs chasegame objectsthat leavethe field“Is there apracticefield?”PlacebostaticguardTeambrakes afieldelementDroppedcontrollerVenue-providedAV breaksTeamstealsfieldelementsSomeone saysVia isn’tworking but isjust looking atthe wrong eventAdultworkingon robotTeam withno licenseplatesNoclawbotsat eventTie ineliminationsLargesubsystemsummarilyremoved fromrobot mid-eventAdultupset atevent staffAutomaticWindowsupdatebreaks things“Whatmatch arewe on?”RyangetsdistractedTeam withwrong colorlicenseplatesVolunteersstay inhotel withteam(s)Sharp robotcomponentdraws bloodMultipleteams withidenticalnamesParentasks howrankingsworkPapertestVenuelosespowerRobot builtthe nightbefore theeventTeam usesfreezespray/cannedairWaterspilledon fieldTeamforgetsnotebookRyan getsirritated andshuts offmic to ventScorekeeperdistracted byphone / foodMatchsequencebreakMusic stopsplaying andno onenoticesTeam setsup onwrongfieldTeamdoesn’tunderstandSPsMemeonrobot

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