playersmisdiagnoseissues foryouDMs fullof errorlogsworks forsomeplayers butnot othersserverdoesn'treceive inputfrom clientvisualbigerrorsplayersspeakover eachotheroptimizationissueshost can'tstartgameobject thatshould benetworkedisn'tforget tofix asimplebugplayersays "thisgamesucks"player testsbut doesn'tgive anyfeedbackplayer thinksyour badgame designas a bugrandomdisconnectsplayerscomplainabout lagplayerdiscovers non-networkedobject andpoints it outdesyncnew erroryou'venever seenbeforeindex outof boundserrornon-descriptnull errorlobbycrashessomeonehacks theclient authsomeoneafksduring thelive testplayercan'tconnect togameplayersmisdiagnoseissues foryouDMs fullof errorlogsworks forsomeplayers butnot othersserverdoesn'treceive inputfrom clientvisualbigerrorsplayersspeakover eachotheroptimizationissueshost can'tstartgameobject thatshould benetworkedisn'tforget tofix asimplebugplayersays "thisgamesucks"player testsbut doesn'tgive anyfeedbackplayer thinksyour badgame designas a bugrandomdisconnectsplayerscomplainabout lagplayerdiscovers non-networkedobject andpoints it outdesyncnew erroryou'venever seenbeforeindex outof boundserrornon-descriptnull errorlobbycrashessomeonehacks theclient authsomeoneafksduring thelive testplayercan'tconnect togame

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