host can'tstartgameobject thatshould benetworkedisn'tplayerscomplainabout lagindex outof boundserrorplayersmisdiagnoseissues foryoudesyncplayersays "thisgamesucks"someonehacks theclient authplayersspeakover eachotherworks forsomeplayers butnot othersserverdoesn'treceive inputfrom clientplayercan'tconnect togamenew erroryou'venever seenbeforeplayer thinksyour badgame designas a bugoptimizationissueslobbycrashesrandomdisconnectsforget tofix asimplebugsomeoneafksduring thelive testplayer testsbut doesn'tgive anyfeedbacknon-descriptnull errorDMs fullof errorlogsvisualbigerrorsplayerdiscovers non-networkedobject andpoints it outhost can'tstartgameobject thatshould benetworkedisn'tplayerscomplainabout lagindex outof boundserrorplayersmisdiagnoseissues foryoudesyncplayersays "thisgamesucks"someonehacks theclient authplayersspeakover eachotherworks forsomeplayers butnot othersserverdoesn'treceive inputfrom clientplayercan'tconnect togamenew erroryou'venever seenbeforeplayer thinksyour badgame designas a bugoptimizationissueslobbycrashesrandomdisconnectsforget tofix asimplebugsomeoneafksduring thelive testplayer testsbut doesn'tgive anyfeedbacknon-descriptnull errorDMs fullof errorlogsvisualbigerrorsplayerdiscovers non-networkedobject andpoints it out

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