Controllers Control Everything

Does the controller put a limit on the imagination of game designers? This odd cluster of buttons, sticks, triggers, and bumpers does not merely sit between the player and the game. It affects what kinds of games are easy to make, easy to explain, and easy to play.

The history of game controllers shows what each input device has evolved to support. Arcade games could ship with bespoke controls that suited one machine perfectly. Pong used dials. Dig Dug only needed a joystick. Robotron needed two sticks for twin-stick chaos. Marble Madness used a trackball because rolling a marble with a ball made immediate physical sense.

Consoles had a different problem. They needed one controller that could work with every game on the system. The Atari 2600 joystick and the less graceful Atari 5200 phone pad were early attempts, but the NES controller set the standard. It was ideal for moving characters around a 2D plane in games like Mario and Zelda. It also made some other games awkward or unrealistic. Marble Madness and the Robotron sequel Smash TV did not fit the NES pad naturally, and anything close to twin-stick play had to wait for controllers with more buttons.

When games moved into 3D, the d-pad stopped being enough. Early PlayStation games like Tomb Raider show how clumsy 3D movement could feel when the controller was still carrying habits from 2D play. Nintendo again changed the standard with the analog stick on the N64 controller, which made moving Mario through a 3D world feel effortless.

Sony answered with the Dual Analog controller, quickly followed by the DualShock, which added a second analog stick. For a while, that second stick had no obvious universal job beyond oddities like swinging a net in Ape Escape. Then developers realized it could control the camera. That insight led toward fluid console first-person shooters such as Medal of Honor Underground and Alien Resurrection, even if players needed time to adjust. A 2000 review famously treated the now-standard twin-stick scheme in Alien Resurrection as almost impossibly difficult to control.

That is how modern pads arrived at their current shape. They carry a fossil record of the problems games kept asking them to solve: moving a character through space, aiming a view or crosshair, and doing both with enough precision that combat can work. That last part still depends on help from the game, such as generous auto-aim and enemies that move slowly enough for analog sticks to keep up.

Many other interactions simply do not work well on a standard controller. Real-time strategy games need lightning-fast access to any part of the screen, so they have often felt awkward on consoles. The exceptions tend to prove the point. Games like Overlord and Pikmin make the player move a character around a space, bringing the genre back toward what the pad already does well.

Fine motor control is another weak spot. Trying to draw on a whiteboard with an analog stick, as in Duke Nukem Forever, quickly reveals how crude that input can be for small hand movements. Take a game like Trauma Center, which is about making quick, precise surgical incisions, and put it on an Xbox controller. The result would likely feel less like surgery and more like clumsy slapstick.

Trauma Center belongs on hardware with a more direct input method, such as the Wii remote or the DS touchscreen. Those devices are full of games that would be much weaker, or impossible, on a traditional pad because the interaction itself depends on the input device.

The DS touchscreen enabled games like Elite Beat Agents, Kirby Canvas Curse, Cooking Mama, and Drawn to Life. Later touch devices produced games such as Fruit Ninja, Flight Control, Blek, Eliss, and Cut the Rope. These games are not just existing controller games with a different pointer. Their core actions come from touching, slicing, dragging, drawing, and manipulating the screen directly.

The Wii created another kind of directness. Its games let players hold a sword, swing a tennis racket, point a flashlight, swig a drink, or perform another physical action by moving the remote in a similar way to the character on screen. The connection between the player's body and the on-screen action is immediate enough that people can understand the idea before they understand the whole rule set.

That is the power of direct input. It can be intuitive because the player is not first learning an arbitrary mapping. They are doing something that resembles the intended action. A touchscreen can make cutting fruit or pulling a lever feel self-explanatory. A motion controller can make tennis feel playable before the player has memorized a diagram of buttons.

Traditional controllers are abstract input devices. To swing a tennis racket in a conventional controller game, the player might press a green button. Every game that uses a pad has to teach the player what each button means, and that has major consequences for design.

First, developers are pulled toward games and genres where the control language is already familiar. When so many first-person shooters share the same basic layout for aim, fire, crouch, reload, sprint, and melee, it is not surprising that consoles have so many first-person shooters. The controller, the genre, and the player's memory reinforce one another.

That expectation can also be useful. Portal uses the conventions of a first-person shooter to deliver a non-violent puzzle game. The player already understands looking, moving, and aiming, so the game can spend its energy teaching portals instead of teaching the entire interface from scratch.

The second consequence is that abstract controls can only support deep mechanical sophistication across a small number of actions. Otherwise, the game needs a tutorial every time the player does anything new, and the player has to remember a pile of special-case commands.

Call of Duty can give the player a remarkable level of precision when aiming and firing a gun, yet in the infamous cemetery scene the player can only hold one button to pay respects. That does not mean the scene would improve if the player had to manually move a hand onto a coffin. There is real elegance in games built around one mechanic or a tight pair of verbs.

But those one or two interactions must usually be repeated thousands of times across the whole game. Some verbs can survive that repetition better than others. Punching, slashing, shooting, driving, and jumping have become game-design staples because they are easy to repeat, easy to vary, and easy to make expressive through timing, movement, and challenge.

Other games feature characters who do many small interactions. In Life is Strange, Max can play a guitar, water a plant, or take a photo. But when those actions are all handled by simple contextual button prompts, they lose some of the tactile playfulness, challenge, and mastery that can come from direct control.

Games such as Monument Valley and The Room show the difference on a touchscreen. Poking, pulling, prodding, and twisting parts of the world can be satisfying because the player is directly manipulating the object, not merely choosing an option from the controller's limited vocabulary.

This is why VR controllers are so interesting. Devices such as Oculus Touch, the Vive controller, and PlayStation Move can support interactions that would feel clumsy on a pad. In Giant Cop, the player can pluck criminals off the street. In I Expect You to Die and Job Simulator, the player can reach out, grab, pull, and poke objects without relying on contextual prompts or a list of memorized buttons.

But a new input method is not an automatic solution. VR controllers are excellent for hands, objects, and nearby physical manipulation. They are much less naturally suited to moving a character through a large space. Many VR games built around those controllers are about sitting in one place or physically walking within a small tracked area because the controller's strengths and limits push the design in that direction.

Different controllers are good at different things. The job of the designer is to build around those strengths and avoid fighting the limits of the device. That does not mean obeying every convention. Some of the most interesting games come from questioning what a familiar input can do.

Skate rejects button-combo trick inputs and makes the player wiggle the right analog stick to perform ollies and flick tricks. That choice supports the grounded realism of the series because both the player and the character are performing a tricky motor movement. It also creates genuine skill: advanced tricks require practiced input, not just remembering a button sequence.

Grow Home uses the triggers to mimic grabbing with left and right hands. The Fight Night games let the player throw punches with the analog stick. Katamari Damacy uses both analog sticks at once to mimic pushing a giant ball with two hands. Brothers lets the player control two characters at the same time, one with each analog stick, and then uses that controller relationship to tell a story about siblings.

That last example shows how deeply input can carry meaning. The controller is not just a convenience layer. It can become part of the game's theme, its emotion, and its structure. The awkwardness of a touchscreen joystick port can damage that relationship because the original game was built around what the pad made possible.

Controllers do dictate what kinds of games are possible. The abstract nature of the traditional pad narrows imagination further because it encourages familiar mappings, repeatable verbs, and genres that already fit the hardware. But designers are not trapped. Plenty of games find new forms of play by reinventing the wheel, or the analog stick.

If a game is not suitable for the traditional pad, another input method may work better: a motion-sensing remote, a multi-touch touchscreen, Valve's mouse-like Steam Controller, or some future platform holder experiment. The question is not which controller is best in the abstract. The question is what kind of play the game actually needs.

Good control design starts with the player's hands. What should they do repeatedly? What should feel direct? What should require mastery? What should be reduced to a simple prompt because the game is really about something else? Once those questions are clear, the controller stops being an afterthought and becomes part of the design itself.