When discussing game mechanics we need to remember that there is more to gameplay than just the on-screen interactions. There is a real-life interaction happening during every single game you play, and it occurs between you and the controller. When designing a game you can’t just take this for granted, and it is actually an interaction which deserves a lot of thought. How you want your player to interact with the game world can determine exactly what system your game should be released for as well as whether or not you will need an extensive controls tutorial to educate your players.
Before getting started on your game you should ask yourself, “What control systems do I have access to?” This is an important question because each controller type places hard limits on potential player actions. By this I mean that every controller has a different number of buttons which players can press (or nobs/joysticks to fiddle with, but we can pretend they are just a bunch of buttons), and that number of buttons acts as a ceiling value for how many actions you can offer to the player. On one end of the spectrum we have the single-button, single-joystick Atari, with the Xbox 360 controller being somewhere in the current middle, and near the end the current rendition of the computer keyboard. To be more specific: A Nintendo controller has eight buttons (A, B, Select, Start, four directions on the D-Pad) while a computer keyboard can have around 84-102 buttons. This means that if you were to assign a single action to a single button that the Nintendo can support eight individual actions where the computer can support at least 80 different individual actions.
