InexplicableTournamentManagerproblemVolunteersstay inhotel withteam(s)Everyteamposts askills runAdultworkingon robotLast minuterobotbatteryswapTeambrakes afieldelementRefsearchesQ&ASomeonewalks infront of theprojectorMemeonrobotRobot builtthe nightbefore theeventTwo teamsfrom the sameorg playtogether in thefinalsTeam saysthey’re ready,then reachesin to adjustrobotTeamarrives 4+matchesearlyMatchDQKit robot istoo big forstartingsizeStudentleavesfield mid-matchScoringtablelosespowerTie forfirst infinalsPhilipdevises“creative”technicalsolution“I need asingle studentrepresentativefrom eachteam”Matchstarts tooearlySomeoneother thanRyan or Johnhead refs<50% ofteamspost skillsrunsWaterspilledon fieldRefs chasegame objectsthat leavethe fieldNetworkingproblemsPi hasto beresetRobotthrowsgameelementsChildrensteppingon a fieldTeamstealsfieldelementsVenue-providedAV breaksRobotgets stuckon fieldpegsMemeonrobotAdultupset atevent staffRobotBreaksWindowssystemsoundsover PATM opmissesmatchcountdown“When dowe get ournotebooksback?”Adultwon’t letthe kidstalkHead refand MC arethe samepersonSomeonehas to callDillonRobotwith <4wheelsTMlagsMatchno-showSomeone fallsoff achair/bleachersTMAudiobugsTeam withno licenseplatesDroppedcontrollerEntireteam intearsPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSame pineeds to berebootedmultipletimesRyan andJohnswitchrolesHelicoptercoachRyan hasa “word ofthe day”Mexicanfood fordinnerParentasks howrankingsworkScorekeeperdistracted byphone / foodMusic stopsplaying andno onenoticesTeamforgetsnotebookRef closelyexaminesfieldelements orrobotPhilip’strackballfalls out“Whatmatch arewe on?”“Is there apracticefield?”ToddgoesmissingAdult asksrefsquestionsafter beingtold not toAdultcryingRyan getsirritated andshuts offmic to ventPrintermisbehavesPapertestMultipleteams withidenticalnamesMatchsequencebreakSpeakertakes toolong atawardsCoachswearingRyan or Johndescribesrobottroubleshootingover the mic“Is theskills fieldopen?”RyansummonsJohn overloudspeakerSister teams inthe same matchaccidentallyswitchcontrollersEvent winnerdeterminedby matchstop timeVenueroofleaksSomeone saysVia isn’tworking but isjust looking atthe wrong eventNo staff atscoringtableMatchstarts 10+minutesearlyTeamcontinues todrive afterbuzzersoundsRyangetsdistracted“Have youprinted thematchschedule?”AutomaticWindowsupdatebreaks thingsTeam setsup onwrongfieldMatchstarts 10+minuteslateTeam forgetsto connectbattery, turnon robot, orstart program“Whydidn’t wewin [awardx]?”VenueinternetblockssomethingMicrophonesnaps,cracklesand popsAwardwinnersaccidentallyrevealedearlyAudiencecheers athead refrulingRobotparts lefton fieldSomeonetrips overa cableInexplicableTournamentManagerproblemVolunteersstay inhotel withteam(s)Everyteamposts askills runAdultworkingon robotLast minuterobotbatteryswapTeambrakes afieldelementRefsearchesQ&ASomeonewalks infront of theprojectorMemeonrobotRobot builtthe nightbefore theeventTwo teamsfrom the sameorg playtogether in thefinalsTeam saysthey’re ready,then reachesin to adjustrobotTeamarrives 4+matchesearlyMatchDQKit robot istoo big forstartingsizeStudentleavesfield mid-matchScoringtablelosespowerTie forfirst infinalsPhilipdevises“creative”technicalsolution“I need asingle studentrepresentativefrom eachteam”Matchstarts tooearlySomeoneother thanRyan or Johnhead refs<50% ofteamspost skillsrunsWaterspilledon fieldRefs chasegame objectsthat leavethe fieldNetworkingproblemsPi hasto beresetRobotthrowsgameelementsChildrensteppingon a fieldTeamstealsfieldelementsVenue-providedAV breaksRobotgets stuckon fieldpegsMemeonrobotAdultupset atevent staffRobotBreaksWindowssystemsoundsover PATM opmissesmatchcountdown“When dowe get ournotebooksback?”Adultwon’t letthe kidstalkHead refand MC arethe samepersonSomeonehas to callDillonRobotwith <4wheelsTMlagsMatchno-showSomeone fallsoff achair/bleachersTMAudiobugsTeam withno licenseplatesDroppedcontrollerEntireteam intearsPresenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesSame pineeds to berebootedmultipletimesRyan andJohnswitchrolesHelicoptercoachRyan hasa “word ofthe day”Mexicanfood fordinnerParentasks howrankingsworkScorekeeperdistracted byphone / foodMusic stopsplaying andno onenoticesTeamforgetsnotebookRef closelyexaminesfieldelements orrobotPhilip’strackballfalls out“Whatmatch arewe on?”“Is there apracticefield?”ToddgoesmissingAdult asksrefsquestionsafter beingtold not toAdultcryingRyan getsirritated andshuts offmic to ventPrintermisbehavesPapertestMultipleteams withidenticalnamesMatchsequencebreakSpeakertakes toolong atawardsCoachswearingRyan or Johndescribesrobottroubleshootingover the mic“Is theskills fieldopen?”RyansummonsJohn overloudspeakerSister teams inthe same matchaccidentallyswitchcontrollersEvent winnerdeterminedby matchstop timeVenueroofleaksSomeone saysVia isn’tworking but isjust looking atthe wrong eventNo staff atscoringtableMatchstarts 10+minutesearlyTeamcontinues todrive afterbuzzersoundsRyangetsdistracted“Have youprinted thematchschedule?”AutomaticWindowsupdatebreaks thingsTeam setsup onwrongfieldMatchstarts 10+minuteslateTeam forgetsto connectbattery, turnon robot, orstart program“Whydidn’t wewin [awardx]?”VenueinternetblockssomethingMicrophonesnaps,cracklesand popsAwardwinnersaccidentallyrevealedearlyAudiencecheers athead refrulingRobotparts lefton fieldSomeonetrips overa cable

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