randomdisconnectsindex outof boundserrorplayercan'tconnect togamehost can'tstartgamelobbycrashessomeoneafksduring thelive testdesyncnew erroryou'venever seenbeforeplayersays "thisgamesucks"playersspeakover eachotherplayerscomplainabout lagplayersmisdiagnoseissues foryouplayer thinksyour badgame designas a bugsomeonehacks theclient authvisualbigerrorsobject thatshould benetworkedisn'tworks forsomeplayers butnot othersnon-descriptnull errorplayerdiscovers non-networkedobject andpoints it outforget tofix asimplebugoptimizationissuesserverdoesn'treceive inputfrom clientDMs fullof errorlogsplayer testsbut doesn'tgive anyfeedbackrandomdisconnectsindex outof boundserrorplayercan'tconnect togamehost can'tstartgamelobbycrashessomeoneafksduring thelive testdesyncnew erroryou'venever seenbeforeplayersays "thisgamesucks"playersspeakover eachotherplayerscomplainabout lagplayersmisdiagnoseissues foryouplayer thinksyour badgame designas a bugsomeonehacks theclient authvisualbigerrorsobject thatshould benetworkedisn'tworks forsomeplayers butnot othersnon-descriptnull errorplayerdiscovers non-networkedobject andpoints it outforget tofix asimplebugoptimizationissuesserverdoesn'treceive inputfrom clientDMs fullof errorlogsplayer testsbut doesn'tgive anyfeedback

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