Venue-providedAV breaksAdultcryingRobotgets stuckon fieldpegs“Whydidn’t wewin [awardx]?”TMAudiobugs“When dowe get ournotebooksback?”HelicoptercoachAwardwinnersaccidentallyrevealedearlyNo staff atscoringtablePresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeambrakes afieldelementTeam saysthey’re ready,then reachesin to adjustrobot“Is theskills fieldopen?”MatchDQChildrensteppingon a fieldToddgoesmissingVenueinternetblockssomethingLast minuterobotbatteryswap<50% ofteamspost skillsrunsMatchstarts 10+minutesearlyKit robot istoo big forstartingsizeEvent winnerdeterminedby matchstop timeRefsearchesQ&ARef closelyexaminesfieldelements orrobotMultipleteams withidenticalnamesHead refand MC arethe samepersonPapertestTwo teamsfrom the sameorg playtogether in thefinalsScorekeeperdistracted byphone / foodRyan andJohnswitchrolesTMlagsPrintermisbehavesMemeonrobotMatchno-showSomeoneother thanRyan or Johnhead refsMatchstarts tooearlyMexicanfood fordinnerScoringtablelosespowerMicrophonesnaps,cracklesand popsParentasks howrankingsworkTie forfirst infinalsWaterspilledon fieldPhilipdevises“creative”technicalsolutionAudiencecheers athead refrulingTM opmissesmatchcountdown“Whatmatch arewe on?”AutomaticWindowsupdatebreaks thingsRefs chasegame objectsthat leavethe fieldSomeone fallsoff achair/bleachersSomeonewalks infront of theprojectorRobotparts lefton fieldPhilip’strackballfalls outSomeonehas to callDillonRyan getsirritated andshuts offmic to ventRobotBreaksRobotwith <4wheelsRyangetsdistractedMusic stopsplaying andno onenoticesMatchstarts 10+minuteslateInexplicableTournamentManagerproblemAdultupset atevent staffMemeonrobotAdultworkingon robotAdultwon’t letthe kidstalkVenueroofleaksDroppedcontrollerSomeone saysVia isn’tworking but isjust looking atthe wrong eventStudentleavesfield mid-matchNetworkingproblemsTeam withno licenseplates“Is there apracticefield?”Volunteersstay inhotel withteam(s)Windowssystemsoundsover PARobotthrowsgameelementsTeamarrives 4+matchesearlyTeamforgetsnotebookSame pineeds to berebootedmultipletimes“I need asingle studentrepresentativefrom eachteam”“Have youprinted thematchschedule?”Someonetrips overa cablePi hasto beresetTeam forgetsto connectbattery, turnon robot, orstart programSpeakertakes toolong atawardsRobot builtthe nightbefore theeventRyan or Johndescribesrobottroubleshootingover the micTeamstealsfieldelementsMatchsequencebreakTeam setsup onwrongfieldEveryteamposts askills runEntireteam intearsRyan hasa “word ofthe day”Teamcontinues todrive afterbuzzersoundsAdult asksrefsquestionsafter beingtold not toSister teams inthe same matchaccidentallyswitchcontrollersCoachswearingRyansummonsJohn overloudspeakerVenue-providedAV breaksAdultcryingRobotgets stuckon fieldpegs“Whydidn’t wewin [awardx]?”TMAudiobugs“When dowe get ournotebooksback?”HelicoptercoachAwardwinnersaccidentallyrevealedearlyNo staff atscoringtablePresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeambrakes afieldelementTeam saysthey’re ready,then reachesin to adjustrobot“Is theskills fieldopen?”MatchDQChildrensteppingon a fieldToddgoesmissingVenueinternetblockssomethingLast minuterobotbatteryswap<50% ofteamspost skillsrunsMatchstarts 10+minutesearlyKit robot istoo big forstartingsizeEvent winnerdeterminedby matchstop timeRefsearchesQ&ARef closelyexaminesfieldelements orrobotMultipleteams withidenticalnamesHead refand MC arethe samepersonPapertestTwo teamsfrom the sameorg playtogether in thefinalsScorekeeperdistracted byphone / foodRyan andJohnswitchrolesTMlagsPrintermisbehavesMemeonrobotMatchno-showSomeoneother thanRyan or Johnhead refsMatchstarts tooearlyMexicanfood fordinnerScoringtablelosespowerMicrophonesnaps,cracklesand popsParentasks howrankingsworkTie forfirst infinalsWaterspilledon fieldPhilipdevises“creative”technicalsolutionAudiencecheers athead refrulingTM opmissesmatchcountdown“Whatmatch arewe on?”AutomaticWindowsupdatebreaks thingsRefs chasegame objectsthat leavethe fieldSomeone fallsoff achair/bleachersSomeonewalks infront of theprojectorRobotparts lefton fieldPhilip’strackballfalls outSomeonehas to callDillonRyan getsirritated andshuts offmic to ventRobotBreaksRobotwith <4wheelsRyangetsdistractedMusic stopsplaying andno onenoticesMatchstarts 10+minuteslateInexplicableTournamentManagerproblemAdultupset atevent staffMemeonrobotAdultworkingon robotAdultwon’t letthe kidstalkVenueroofleaksDroppedcontrollerSomeone saysVia isn’tworking but isjust looking atthe wrong eventStudentleavesfield mid-matchNetworkingproblemsTeam withno licenseplates“Is there apracticefield?”Volunteersstay inhotel withteam(s)Windowssystemsoundsover PARobotthrowsgameelementsTeamarrives 4+matchesearlyTeamforgetsnotebookSame pineeds to berebootedmultipletimes“I need asingle studentrepresentativefrom eachteam”“Have youprinted thematchschedule?”Someonetrips overa cablePi hasto beresetTeam forgetsto connectbattery, turnon robot, orstart programSpeakertakes toolong atawardsRobot builtthe nightbefore theeventRyan or Johndescribesrobottroubleshootingover the micTeamstealsfieldelementsMatchsequencebreakTeam setsup onwrongfieldEveryteamposts askills runEntireteam intearsRyan hasa “word ofthe day”Teamcontinues todrive afterbuzzersoundsAdult asksrefsquestionsafter beingtold not toSister teams inthe same matchaccidentallyswitchcontrollersCoachswearingRyansummonsJohn overloudspeaker

VIQC 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
  1. Venue-provided AV breaks
  2. Adult crying
  3. Robot gets stuck on field pegs
  4. “Why didn’t we win [award x]?”
  5. TM Audio bugs
  6. “When do we get our notebooks back?”
  7. Helicopter coach
  8. Award winners accidentally revealed early
  9. No staff at scoring table
  10. Presenter asked to bs and make time for technical difficulties goes on far longer than it takes to resolve the difficulties
  11. Team brakes a field element
  12. Team says they’re ready, then reaches in to adjust robot
  13. “Is the skills field open?”
  14. Match DQ
  15. Children stepping on a field
  16. Todd goes missing
  17. Venue internet blocks something
  18. Last minute robot battery swap
  19. <50% of teams post skills runs
  20. Match starts 10+ minutes early
  21. Kit robot is too big for starting size
  22. Event winner determined by match stop time
  23. Ref searches Q&A
  24. Ref closely examines field elements or robot
  25. Multiple teams with identical names
  26. Head ref and MC are the same person
  27. Paper test
  28. Two teams from the same org play together in the finals
  29. Scorekeeper distracted by phone / food
  30. Ryan and John switch roles
  31. TM lags
  32. Printer misbehaves
  33. Meme on robot
  34. Match no-show
  35. Someone other than Ryan or John head refs
  36. Match starts too early
  37. Mexican food for dinner
  38. Scoring table loses power
  39. Microphone snaps, crackles and pops
  40. Parent asks how rankings work
  41. Tie for first in finals
  42. Water spilled on field
  43. Philip devises “creative” technical solution
  44. Audience cheers at head ref ruling
  45. TM op misses match countdown
  46. “What match are we on?”
  47. Automatic Windows update breaks things
  48. Refs chase game objects that leave the field
  49. Someone falls off a chair/bleachers
  50. Someone walks in front of the projector
  51. Robot parts left on field
  52. Philip’s trackball falls out
  53. Someone has to call Dillon
  54. Ryan gets irritated and shuts off mic to vent
  55. Robot Breaks
  56. Robot with <4 wheels
  57. Ryan gets distracted
  58. Music stops playing and no one notices
  59. Match starts 10+ minutes late
  60. Inexplicable Tournament Manager problem
  61. Adult upset at event staff
  62. Meme on robot
  63. Adult working on robot
  64. Adult won’t let the kids talk
  65. Venue roof leaks
  66. Dropped controller
  67. Someone says Via isn’t working but is just looking at the wrong event
  68. Student leaves field mid-match
  69. Networking problems
  70. Team with no license plates
  71. “Is there a practice field?”
  72. Volunteers stay in hotel with team(s)
  73. Windows system sounds over PA
  74. Robot throws game elements
  75. Team arrives 4+ matches early
  76. Team forgets notebook
  77. Same pi needs to be rebooted multiple times
  78. “I need a single student representative from each team”
  79. “Have you printed the match schedule?”
  80. Someone trips over a cable
  81. Pi has to be reset
  82. Team forgets to connect battery, turn on robot, or start program
  83. Speaker takes too long at awards
  84. Robot built the night before the event
  85. Ryan or John describes robot troubleshooting over the mic
  86. Team steals field elements
  87. Match sequence break
  88. Team sets up on wrong field
  89. Every team posts a skills run
  90. Entire team in tears
  91. Ryan has a “word of the day”
  92. Team continues to drive after buzzer sounds
  93. Adult asks refs questions after being told not to
  94. Sister teams in the same match accidentally switch controllers
  95. Coach swearing
  96. Ryan summons John over loudspeaker