Teambrakes afieldelementHelicoptercoachMatchstarts 10+minutesearlyTeam saysthey’re ready,then reachesin to adjustrobotLast minuterobotbatteryswapEveryteamposts askills runTMAudiobugsTeamstealsfieldelementsDroppedcontrollerPhilip’strackballfalls outMultipleteams withidenticalnamesNetworkingproblemsTwo teamsfrom the sameorg playtogether in thefinals“I need asingle studentrepresentativefrom eachteam”TM opmissesmatchcountdownMicrophonesnaps,cracklesand pops“Whydidn’t wewin [awardx]?”Same pineeds to berebootedmultipletimesAdultcryingTeam withno licenseplatesRobot builtthe nightbefore theeventInexplicableTournamentManagerproblemEntireteam intearsToddgoesmissingAudiencecheers athead refrulingParentasks howrankingsworkTeamarrives 4+matchesearly“Is theskills fieldopen?”“When dowe get ournotebooksback?”Presenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesAdultupset atevent staffScoringtablelosespowerTeamcontinues todrive afterbuzzersoundsMatchstarts tooearlyScorekeeperdistracted byphone / foodEvent winnerdeterminedby matchstop timeMatchsequencebreakNo staff atscoringtableSomeonewalks infront of theprojectorStudentleavesfield mid-matchRobotthrowsgameelementsRobotBreaksAdult asksrefsquestionsafter beingtold not toWindowssystemsoundsover PASomeone saysVia isn’tworking but isjust looking atthe wrong eventMemeonrobotVolunteersstay inhotel withteam(s)AutomaticWindowsupdatebreaks thingsVenue-providedAV breaks<50% ofteamspost skillsrunsAdultworkingon robotPi hasto beresetRyangetsdistractedSpeakertakes toolong atawardsRyansummonsJohn overloudspeakerTeam setsup onwrongfieldMexicanfood fordinnerTeamforgetsnotebookTeam forgetsto connectbattery, turnon robot, orstart programPrintermisbehavesSomeonehas to callDillonCoachswearingPapertestRyan andJohnswitchrolesRobotwith <4wheelsSomeone fallsoff achair/bleachersTie forfirst infinalsRefsearchesQ&ARobotgets stuckon fieldpegsSomeonetrips overa cableHead refand MC arethe samepersonMatchstarts 10+minuteslateMemeonrobotRef closelyexaminesfieldelements orrobotMusic stopsplaying andno onenoticesChildrensteppingon a fieldMatchno-showAdultwon’t letthe kidstalkVenueinternetblockssomethingKit robot istoo big forstartingsizePhilipdevises“creative”technicalsolutionSister teams inthe same matchaccidentallyswitchcontrollersRobotparts lefton fieldRyan hasa “word ofthe day”“Is there apracticefield?”TMlagsVenueroofleaks“Have youprinted thematchschedule?”Waterspilledon fieldAwardwinnersaccidentallyrevealedearlyRefs chasegame objectsthat leavethe fieldRyan or Johndescribesrobottroubleshootingover the micMatchDQ“Whatmatch arewe on?”Ryan getsirritated andshuts offmic to ventSomeoneother thanRyan or Johnhead refsTeambrakes afieldelementHelicoptercoachMatchstarts 10+minutesearlyTeam saysthey’re ready,then reachesin to adjustrobotLast minuterobotbatteryswapEveryteamposts askills runTMAudiobugsTeamstealsfieldelementsDroppedcontrollerPhilip’strackballfalls outMultipleteams withidenticalnamesNetworkingproblemsTwo teamsfrom the sameorg playtogether in thefinals“I need asingle studentrepresentativefrom eachteam”TM opmissesmatchcountdownMicrophonesnaps,cracklesand pops“Whydidn’t wewin [awardx]?”Same pineeds to berebootedmultipletimesAdultcryingTeam withno licenseplatesRobot builtthe nightbefore theeventInexplicableTournamentManagerproblemEntireteam intearsToddgoesmissingAudiencecheers athead refrulingParentasks howrankingsworkTeamarrives 4+matchesearly“Is theskills fieldopen?”“When dowe get ournotebooksback?”Presenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesAdultupset atevent staffScoringtablelosespowerTeamcontinues todrive afterbuzzersoundsMatchstarts tooearlyScorekeeperdistracted byphone / foodEvent winnerdeterminedby matchstop timeMatchsequencebreakNo staff atscoringtableSomeonewalks infront of theprojectorStudentleavesfield mid-matchRobotthrowsgameelementsRobotBreaksAdult asksrefsquestionsafter beingtold not toWindowssystemsoundsover PASomeone saysVia isn’tworking but isjust looking atthe wrong eventMemeonrobotVolunteersstay inhotel withteam(s)AutomaticWindowsupdatebreaks thingsVenue-providedAV breaks<50% ofteamspost skillsrunsAdultworkingon robotPi hasto beresetRyangetsdistractedSpeakertakes toolong atawardsRyansummonsJohn overloudspeakerTeam setsup onwrongfieldMexicanfood fordinnerTeamforgetsnotebookTeam forgetsto connectbattery, turnon robot, orstart programPrintermisbehavesSomeonehas to callDillonCoachswearingPapertestRyan andJohnswitchrolesRobotwith <4wheelsSomeone fallsoff achair/bleachersTie forfirst infinalsRefsearchesQ&ARobotgets stuckon fieldpegsSomeonetrips overa cableHead refand MC arethe samepersonMatchstarts 10+minuteslateMemeonrobotRef closelyexaminesfieldelements orrobotMusic stopsplaying andno onenoticesChildrensteppingon a fieldMatchno-showAdultwon’t letthe kidstalkVenueinternetblockssomethingKit robot istoo big forstartingsizePhilipdevises“creative”technicalsolutionSister teams inthe same matchaccidentallyswitchcontrollersRobotparts lefton fieldRyan hasa “word ofthe day”“Is there apracticefield?”TMlagsVenueroofleaks“Have youprinted thematchschedule?”Waterspilledon fieldAwardwinnersaccidentallyrevealedearlyRefs chasegame objectsthat leavethe fieldRyan or Johndescribesrobottroubleshootingover the micMatchDQ“Whatmatch arewe on?”Ryan getsirritated andshuts offmic to ventSomeoneother thanRyan or Johnhead refs

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