Codergets arulingwrongCoderanswersbeforeplayers evenask"Imissclicked"a clearmissplayFarfaCallMBTCallPlayerdoesn'tunderstandMeltdownAssembledNightingale &Recital StarlingDamage RulingPlayerinsults /curses atcoderRogueVSRogueBig DBGlitchMysticmine ison boardCoderDQsSomeoneMonkiFlipmirrormatchPlayerTries toappealCoderPlayerdidn'tdeclareDPE in GYSomeoneaddressesstream incallCoderChecksdatabase toconfirm smthTokenCollectorappearsSharkingWarningIssuedCoderRules anAcceptedGamestateCoderexplains aruling bycopy pastingCoder has tojoin a VC toresolve anissue3x callsin samematchPlayersays"Fizzle"Codergets arulingwrongCoderanswersbeforeplayers evenask"Imissclicked"a clearmissplayFarfaCallMBTCallPlayerdoesn'tunderstandMeltdownAssembledNightingale &Recital StarlingDamage RulingPlayerinsults /curses atcoderRogueVSRogueBig DBGlitchMysticmine ison boardCoderDQsSomeoneMonkiFlipmirrormatchPlayerTries toappealCoderPlayerdidn'tdeclareDPE in GYSomeoneaddressesstream incallCoderChecksdatabase toconfirm smthTokenCollectorappearsSharkingWarningIssuedCoderRules anAcceptedGamestateCoderexplains aruling bycopy pastingCoder has tojoin a VC toresolve anissue3x callsin samematchPlayersays"Fizzle"

PAK X LCS TOURNEY - 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
  1. Coder gets a ruling wrong
  2. Coder answers before players even ask
  3. "I missclicked" a clear missplay
  4. Farfa Call
  5. MBT Call
  6. Player doesn't understand Meltdown
  7. Assembled Nightingale & Recital Starling Damage Ruling
  8. Player insults / curses at coder
  9. Rogue VS Rogue
  10. Big DB Glitch
  11. Mystic mine is on board
  12. Coder DQs Someone
  13. MonkiFlip mirror match
  14. Player Tries to appeal Coder
  15. Player didn't declare DPE in GY
  16. Someone addresses stream in call
  17. Coder Checks database to confirm smth
  18. Token Collector appears
  19. Sharking Warning Issued
  20. Coder Rules an Accepted Gamestate
  21. Coder explains a ruling by copy pasting
  22. Coder has to join a VC to resolve an issue
  23. 3x calls in same match
  24. Player says "Fizzle"