Someone saysVia isn’tworking but isjust looking atthe wrong eventEvent winnerdeterminedby matchstop timeAdultcryingTMlagsTM opmissesmatchcountdownPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSame pineeds to berebootedmultipletimesPrintermisbehavesEntireteam intears“Is theskills fieldopen?”Adult asksrefsquestionsafter beingtold not toTeamforgetsnotebookMemeonrobotRyan getsirritated andshuts offmic to ventVolunteersstay inhotel withteam(s)AutomaticWindowsupdatebreaks thingsTeam forgetsto connectbattery, turnon robot, orstart programEveryteamposts askills runMultipleteams withidenticalnamesTie forfirst infinalsScoringtablelosespowerScorekeeperdistracted byphone / foodMatchstarts 10+minutesearlySpeakertakes toolong atawards“I need asingle studentrepresentativefrom eachteam”Ryan andJohnswitchrolesTeam saysthey’re ready,then reachesin to adjustrobotVenue-providedAV breaksTeamcontinues todrive afterbuzzersoundsMemeonrobotHead refand MC arethe samepersonAdultworkingon robotTeamarrives 4+matchesearlyCoachswearing<50% ofteamspost skillsrunsMexicanfood fordinnerToddgoesmissingTeam withno licenseplatesNetworkingproblemsHelicoptercoachLast minuterobotbatteryswapMatchstarts tooearlyRefs chasegame objectsthat leavethe field“When dowe get ournotebooksback?”Teambrakes afieldelementVenueroofleaks“Is there apracticefield?”Someoneother thanRyan or Johnhead refsPhilipdevises“creative”technicalsolutionMatchsequencebreakRobotwith <4wheelsWaterspilledon fieldMusic stopsplaying andno onenoticesNo staff atscoringtableKit robot istoo big forstartingsizeVenueinternetblockssomethingRyangetsdistractedMatchstarts 10+minuteslateSister teams inthe same matchaccidentallyswitchcontrollersSomeonehas to callDillonSomeone fallsoff achair/bleachersRef closelyexaminesfieldelements orrobotPi hasto bereset“Whatmatch arewe on?”Parentasks howrankingsworkInexplicableTournamentManagerproblemStudentleavesfield mid-matchDroppedcontrollerMatchDQTwo teamsfrom the sameorg playtogether in thefinalsRobotgets stuckon fieldpegsRyan hasa “word ofthe day”Matchno-show“Whydidn’t wewin [awardx]?”RefsearchesQ&ARyan or Johndescribesrobottroubleshootingover the micTeamstealsfieldelementsRyansummonsJohn overloudspeakerWindowssystemsoundsover PAPapertestAwardwinnersaccidentallyrevealedearlyRobot builtthe nightbefore theeventRobotBreaksRobotthrowsgameelementsChildrensteppingon a fieldAdultwon’t letthe kidstalkPhilip’strackballfalls outTeam setsup onwrongfieldMicrophonesnaps,cracklesand popsAudiencecheers athead refrulingRobotparts lefton fieldSomeonetrips overa cable“Have youprinted thematchschedule?”Someonewalks infront of theprojectorAdultupset atevent staffTMAudiobugsSomeone saysVia isn’tworking but isjust looking atthe wrong eventEvent winnerdeterminedby matchstop timeAdultcryingTMlagsTM opmissesmatchcountdownPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSame pineeds to berebootedmultipletimesPrintermisbehavesEntireteam intears“Is theskills fieldopen?”Adult asksrefsquestionsafter beingtold not toTeamforgetsnotebookMemeonrobotRyan getsirritated andshuts offmic to ventVolunteersstay inhotel withteam(s)AutomaticWindowsupdatebreaks thingsTeam forgetsto connectbattery, turnon robot, orstart programEveryteamposts askills runMultipleteams withidenticalnamesTie forfirst infinalsScoringtablelosespowerScorekeeperdistracted byphone / foodMatchstarts 10+minutesearlySpeakertakes toolong atawards“I need asingle studentrepresentativefrom eachteam”Ryan andJohnswitchrolesTeam saysthey’re ready,then reachesin to adjustrobotVenue-providedAV breaksTeamcontinues todrive afterbuzzersoundsMemeonrobotHead refand MC arethe samepersonAdultworkingon robotTeamarrives 4+matchesearlyCoachswearing<50% ofteamspost skillsrunsMexicanfood fordinnerToddgoesmissingTeam withno licenseplatesNetworkingproblemsHelicoptercoachLast minuterobotbatteryswapMatchstarts tooearlyRefs chasegame objectsthat leavethe field“When dowe get ournotebooksback?”Teambrakes afieldelementVenueroofleaks“Is there apracticefield?”Someoneother thanRyan or Johnhead refsPhilipdevises“creative”technicalsolutionMatchsequencebreakRobotwith <4wheelsWaterspilledon fieldMusic stopsplaying andno onenoticesNo staff atscoringtableKit robot istoo big forstartingsizeVenueinternetblockssomethingRyangetsdistractedMatchstarts 10+minuteslateSister teams inthe same matchaccidentallyswitchcontrollersSomeonehas to callDillonSomeone fallsoff achair/bleachersRef closelyexaminesfieldelements orrobotPi hasto bereset“Whatmatch arewe on?”Parentasks howrankingsworkInexplicableTournamentManagerproblemStudentleavesfield mid-matchDroppedcontrollerMatchDQTwo teamsfrom the sameorg playtogether in thefinalsRobotgets stuckon fieldpegsRyan hasa “word ofthe day”Matchno-show“Whydidn’t wewin [awardx]?”RefsearchesQ&ARyan or Johndescribesrobottroubleshootingover the micTeamstealsfieldelementsRyansummonsJohn overloudspeakerWindowssystemsoundsover PAPapertestAwardwinnersaccidentallyrevealedearlyRobot builtthe nightbefore theeventRobotBreaksRobotthrowsgameelementsChildrensteppingon a fieldAdultwon’t letthe kidstalkPhilip’strackballfalls outTeam setsup onwrongfieldMicrophonesnaps,cracklesand popsAudiencecheers athead refrulingRobotparts lefton fieldSomeonetrips overa cable“Have youprinted thematchschedule?”Someonewalks infront of theprojectorAdultupset atevent staffTMAudiobugs

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