Here are some things to remember when making or testing your video game.


Sticky Data

Pick any function which has an output or sustained effect, such as having your player get poisoned, or changing a shield from fire to ice. Activate it and exit the game mode, then enter a different mode where the same output function can also occur. Sometimes a function's output isn't flushed properly on exiting the mode, and will affect the next mode (sticking to the player).  Your character could start a new game wounded and fatigued from the last one!”

Leaving the Scene

"Look for game environments where players on separate devices can see the same content. Let some interactive items go out of view while the other player modifies the content. Have the other player return and check the item, as sometimes updates do not run properly when prompted by non-local input. This also applies to menu screens which one player can back out of, then return to after their opponent has changed their selection."


Personal Settings

"While testing network or internet games which allow multiple players, have one user change personal settings (such as button configurations) and check if the other players also have their controls altered."


Wrong controller

"Try testing while using the wrong player's controller. It's generally a problem if you can. :)"


Peripheral Devices

"Be sure to identify unassociated peripheral devices which can be enabled or disabled during gameplay. An example of this is signing out of un-used controllers while someone is playing your Xbox 360 game. The game may be unable to handle sudden and unexpected changes in hardware configuration."