RyansummonsJohn overloudspeakerTeam setsup onwrongfieldAdultcryingRobotBreaksTeam withno licenseplatesDroppedcontrollerSomeone fallsoff achair/bleachersRobot builtthe nightbefore theeventVenueroofleaksAwardwinnersaccidentallyrevealedearlySomeone saysVia isn’tworking but isjust looking atthe wrong eventTeamforgetsnotebookSomeoneother thanRyan or Johnhead refsTeamstealsfieldelementsSame pineeds to berebootedmultipletimesPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesMemeonrobotTeam saysthey’re ready,then reachesin to adjustrobotEveryteamposts askills runParentasks howrankingsworkRefs chasegame objectsthat leavethe field“When dowe get ournotebooksback?”Music stopsplaying andno onenotices“I need asingle studentrepresentativefrom eachteam”MatchDQMicrophonesnaps,cracklesand popsRobotwith <4wheels“Whydidn’t wewin [awardx]?”Studentleavesfield mid-matchEntireteam intearsRyan or Johndescribesrobottroubleshootingover the micMatchsequencebreakAutomaticWindowsupdatebreaks thingsLast minuterobotbatteryswapEvent winnerdeterminedby matchstop timeMatchstarts 10+minuteslateHelicoptercoachWindowssystemsoundsover PATeambrakes afieldelementChildrensteppingon a fieldTMAudiobugsRyan getsirritated andshuts offmic to ventSister teams inthe same matchaccidentallyswitchcontrollersRobotthrowsgameelementsTie forfirst infinalsSomeonetrips overa cableMatchno-showScorekeeperdistracted byphone / foodTM opmissesmatchcountdownKit robot istoo big forstartingsizeSpeakertakes toolong atawardsToddgoesmissingHead refand MC arethe sameperson<50% ofteamspost skillsruns“Is theskills fieldopen?”“Have youprinted thematchschedule?”CoachswearingPapertestAdultworkingon robotSomeonewalks infront of theprojectorInexplicableTournamentManagerproblemSomeonehas to callDillonScoringtablelosespowerRobotparts lefton fieldMemeonrobotNo staff atscoringtableAdult asksrefsquestionsafter beingtold not toPrintermisbehavesAudiencecheers athead refrulingTMlagsRyan hasa “word ofthe day”VenueinternetblockssomethingAdultupset atevent staffTeamcontinues todrive afterbuzzersoundsWaterspilledon fieldRyan andJohnswitchrolesRefsearchesQ&ARef closelyexaminesfieldelements orrobotPhilip’strackballfalls outRyangetsdistractedPi hasto beresetPhilipdevises“creative”technicalsolutionMatchstarts 10+minutesearlyAdultwon’t letthe kidstalkNetworkingproblemsTeamarrives 4+matchesearlyMultipleteams withidenticalnames“Whatmatch arewe on?”Volunteersstay inhotel withteam(s)Team forgetsto connectbattery, turnon robot, orstart program“Is there apracticefield?”Venue-providedAV breaksMexicanfood fordinnerMatchstarts tooearlyTwo teamsfrom the sameorg playtogether in thefinalsRobotgets stuckon fieldpegsRyansummonsJohn overloudspeakerTeam setsup onwrongfieldAdultcryingRobotBreaksTeam withno licenseplatesDroppedcontrollerSomeone fallsoff achair/bleachersRobot builtthe nightbefore theeventVenueroofleaksAwardwinnersaccidentallyrevealedearlySomeone saysVia isn’tworking but isjust looking atthe wrong eventTeamforgetsnotebookSomeoneother thanRyan or Johnhead refsTeamstealsfieldelementsSame pineeds to berebootedmultipletimesPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesMemeonrobotTeam saysthey’re ready,then reachesin to adjustrobotEveryteamposts askills runParentasks howrankingsworkRefs chasegame objectsthat leavethe field“When dowe get ournotebooksback?”Music stopsplaying andno onenotices“I need asingle studentrepresentativefrom eachteam”MatchDQMicrophonesnaps,cracklesand popsRobotwith <4wheels“Whydidn’t wewin [awardx]?”Studentleavesfield mid-matchEntireteam intearsRyan or Johndescribesrobottroubleshootingover the micMatchsequencebreakAutomaticWindowsupdatebreaks thingsLast minuterobotbatteryswapEvent winnerdeterminedby matchstop timeMatchstarts 10+minuteslateHelicoptercoachWindowssystemsoundsover PATeambrakes afieldelementChildrensteppingon a fieldTMAudiobugsRyan getsirritated andshuts offmic to ventSister teams inthe same matchaccidentallyswitchcontrollersRobotthrowsgameelementsTie forfirst infinalsSomeonetrips overa cableMatchno-showScorekeeperdistracted byphone / foodTM opmissesmatchcountdownKit robot istoo big forstartingsizeSpeakertakes toolong atawardsToddgoesmissingHead refand MC arethe sameperson<50% ofteamspost skillsruns“Is theskills fieldopen?”“Have youprinted thematchschedule?”CoachswearingPapertestAdultworkingon robotSomeonewalks infront of theprojectorInexplicableTournamentManagerproblemSomeonehas to callDillonScoringtablelosespowerRobotparts lefton fieldMemeonrobotNo staff atscoringtableAdult asksrefsquestionsafter beingtold not toPrintermisbehavesAudiencecheers athead refrulingTMlagsRyan hasa “word ofthe day”VenueinternetblockssomethingAdultupset atevent staffTeamcontinues todrive afterbuzzersoundsWaterspilledon fieldRyan andJohnswitchrolesRefsearchesQ&ARef closelyexaminesfieldelements orrobotPhilip’strackballfalls outRyangetsdistractedPi hasto beresetPhilipdevises“creative”technicalsolutionMatchstarts 10+minutesearlyAdultwon’t letthe kidstalkNetworkingproblemsTeamarrives 4+matchesearlyMultipleteams withidenticalnames“Whatmatch arewe on?”Volunteersstay inhotel withteam(s)Team forgetsto connectbattery, turnon robot, orstart program“Is there apracticefield?”Venue-providedAV breaksMexicanfood fordinnerMatchstarts tooearlyTwo teamsfrom the sameorg playtogether in thefinalsRobotgets stuckon fieldpegs

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