lobbycrashessomeonehacks theclient authplayercan'tconnect togamehost can'tstartgameforget tofix asimplebugdesyncworks forsomeplayers butnot othersplayersmisdiagnoseissues foryouplayer testsbut doesn'tgive anyfeedbackoptimizationissuesserverdoesn'treceive inputfrom clientnew erroryou'venever seenbeforenon-descriptnull errorplayersays "thisgamesucks"object thatshould benetworkedisn'tplayerdiscovers non-networkedobject andpoints it outplayerscomplainabout lagvisualbigerrorsplayer thinksyour badgame designas a bugindex outof boundserrorrandomdisconnectsplayersspeakover eachotherDMs fullof errorlogssomeoneafksduring thelive testlobbycrashessomeonehacks theclient authplayercan'tconnect togamehost can'tstartgameforget tofix asimplebugdesyncworks forsomeplayers butnot othersplayersmisdiagnoseissues foryouplayer testsbut doesn'tgive anyfeedbackoptimizationissuesserverdoesn'treceive inputfrom clientnew erroryou'venever seenbeforenon-descriptnull errorplayersays "thisgamesucks"object thatshould benetworkedisn'tplayerdiscovers non-networkedobject andpoints it outplayerscomplainabout lagvisualbigerrorsplayer thinksyour badgame designas a bugindex outof boundserrorrandomdisconnectsplayersspeakover eachotherDMs fullof errorlogssomeoneafksduring thelive test

Multiplayer Dev 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
  1. lobby crashes
  2. someone hacks the client auth
  3. player can't connect to game
  4. host can't start game
  5. forget to fix a simple bug
  6. desync
  7. works for some players but not others
  8. players misdiagnose issues for you
  9. player tests but doesn't give any feedback
  10. optimization issues
  11. server doesn't receive input from client
  12. new error you've never seen before
  13. non-descript null error
  14. player says "this game sucks"
  15. object that should be networked isn't
  16. player discovers non-networked object and points it out
  17. players complain about lag
  18. visual big errors
  19. player thinks your bad game design as a bug
  20. index out of bounds error
  21. random disconnects
  22. players speak over each other
  23. DMs full of error logs
  24. someone afks during the live test