Ryan andJohnswitchrolesRobotwith <4wheelsTeamstealsfieldelementsPrintermisbehavesRobotBreaksTeamarrives 4+matchesearlyMatchDQAwardwinnersaccidentallyrevealedearlyTeam withno licenseplates“Whydidn’t wewin [awardx]?”Windowssystemsoundsover PASomeone fallsoff achair/bleachersTeam saysthey’re ready,then reachesin to adjustrobotMatchno-showSomeoneother thanRyan or Johnhead refsSomeonewalks infront of theprojectorRyan hasa “word ofthe day”Teamcontinues todrive afterbuzzersoundsTeamforgetsnotebookPapertestVolunteersstay inhotel withteam(s)Microphonesnaps,cracklesand popsEvent winnerdeterminedby matchstop timeMatchstarts 10+minutesearlyCoachswearingAdultupset atevent staffTeambrakes afieldelementSame pineeds to berebootedmultipletimesMultipleteams withidenticalnamesHelicoptercoachSister teams inthe same matchaccidentallyswitchcontrollersTeam forgetsto connectbattery, turnon robot, orstart programVenue-providedAV breaksWaterspilledon fieldSpeakertakes toolong atawards“Is there apracticefield?”Presenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeam setsup onwrongfieldMemeonrobotRobot builtthe nightbefore theeventAdultworkingon robotTMAudiobugsTwo teamsfrom the sameorg playtogether in thefinals<50% ofteamspost skillsrunsStudentleavesfield mid-matchNo staff atscoringtableMexicanfood fordinnerTie forfirst infinalsAudiencecheers athead refrulingPhilipdevises“creative”technicalsolutionKit robot istoo big forstartingsizeMusic stopsplaying andno onenoticesInexplicableTournamentManagerproblemMatchstarts tooearlyRobotparts lefton fieldAdultcryingVenueroofleaks“When dowe get ournotebooksback?”DroppedcontrollerEntireteam intearsToddgoesmissingParentasks howrankingsworkScoringtablelosespowerVenueinternetblockssomethingRyan or Johndescribesrobottroubleshootingover the micTMlagsRyangetsdistractedRyan getsirritated andshuts offmic to ventPhilip’strackballfalls outRobotgets stuckon fieldpegsRobotthrowsgameelementsAutomaticWindowsupdatebreaks thingsChildrensteppingon a field“Whatmatch arewe on?”Adultwon’t letthe kidstalkSomeone saysVia isn’tworking but isjust looking atthe wrong event“Have youprinted thematchschedule?”RyansummonsJohn overloudspeakerEveryteamposts askills runScorekeeperdistracted byphone / food“I need asingle studentrepresentativefrom eachteam”Head refand MC arethe samepersonRefsearchesQ&AMatchsequencebreakMatchstarts 10+minuteslateSomeonetrips overa cable“Is theskills fieldopen?”Adult asksrefsquestionsafter beingtold not toNetworkingproblemsMemeonrobotRefs chasegame objectsthat leavethe fieldSomeonehas to callDillonRef closelyexaminesfieldelements orrobotPi hasto beresetTM opmissesmatchcountdownLast minuterobotbatteryswapRyan andJohnswitchrolesRobotwith <4wheelsTeamstealsfieldelementsPrintermisbehavesRobotBreaksTeamarrives 4+matchesearlyMatchDQAwardwinnersaccidentallyrevealedearlyTeam withno licenseplates“Whydidn’t wewin [awardx]?”Windowssystemsoundsover PASomeone fallsoff achair/bleachersTeam saysthey’re ready,then reachesin to adjustrobotMatchno-showSomeoneother thanRyan or Johnhead refsSomeonewalks infront of theprojectorRyan hasa “word ofthe day”Teamcontinues todrive afterbuzzersoundsTeamforgetsnotebookPapertestVolunteersstay inhotel withteam(s)Microphonesnaps,cracklesand popsEvent winnerdeterminedby matchstop timeMatchstarts 10+minutesearlyCoachswearingAdultupset atevent staffTeambrakes afieldelementSame pineeds to berebootedmultipletimesMultipleteams withidenticalnamesHelicoptercoachSister teams inthe same matchaccidentallyswitchcontrollersTeam forgetsto connectbattery, turnon robot, orstart programVenue-providedAV breaksWaterspilledon fieldSpeakertakes toolong atawards“Is there apracticefield?”Presenter askedto bs and maketime for technicaldifficulties goes onfar longer than ittakes to resolvethe difficultiesTeam setsup onwrongfieldMemeonrobotRobot builtthe nightbefore theeventAdultworkingon robotTMAudiobugsTwo teamsfrom the sameorg playtogether in thefinals<50% ofteamspost skillsrunsStudentleavesfield mid-matchNo staff atscoringtableMexicanfood fordinnerTie forfirst infinalsAudiencecheers athead refrulingPhilipdevises“creative”technicalsolutionKit robot istoo big forstartingsizeMusic stopsplaying andno onenoticesInexplicableTournamentManagerproblemMatchstarts tooearlyRobotparts lefton fieldAdultcryingVenueroofleaks“When dowe get ournotebooksback?”DroppedcontrollerEntireteam intearsToddgoesmissingParentasks howrankingsworkScoringtablelosespowerVenueinternetblockssomethingRyan or Johndescribesrobottroubleshootingover the micTMlagsRyangetsdistractedRyan getsirritated andshuts offmic to ventPhilip’strackballfalls outRobotgets stuckon fieldpegsRobotthrowsgameelementsAutomaticWindowsupdatebreaks thingsChildrensteppingon a field“Whatmatch arewe on?”Adultwon’t letthe kidstalkSomeone saysVia isn’tworking but isjust looking atthe wrong event“Have youprinted thematchschedule?”RyansummonsJohn overloudspeakerEveryteamposts askills runScorekeeperdistracted byphone / food“I need asingle studentrepresentativefrom eachteam”Head refand MC arethe samepersonRefsearchesQ&AMatchsequencebreakMatchstarts 10+minuteslateSomeonetrips overa cable“Is theskills fieldopen?”Adult asksrefsquestionsafter beingtold not toNetworkingproblemsMemeonrobotRefs chasegame objectsthat leavethe fieldSomeonehas to callDillonRef closelyexaminesfieldelements orrobotPi hasto beresetTM opmissesmatchcountdownLast minuterobotbatteryswap

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