Sponsored By

Understand and improve game controls

Understand and improve game controls

Game Developer, Staff

September 27, 2011

4 Min Read
Game Developer logo in a gray background | Game Developer

Overview

If the controls don't feel right, players might hate the game, even if the rest is amazing. During the past 10 years, I've realized that a lot of game developers still struggle at designing game controls that are optimized, feel intuitive or natural. It's even more surprising that many game studios are already eager to work on motion controls when they barely master or understand the classic controllers of the current console generation (360 and PS3), but I understand the excitement.

 

Actions and priorities

In order to design greater controls for a more traditional model such as the Xbox 360 game controller, it's important to understand that there are different layers of actions.

An illustration of the different layers of actions

Different layers of actions

The primary actions are the fastest, the most important. Those are the actions that a player can perform while moving his character and camera at the same time. The primary actions would usually involve:

  • Primary fire such as ''Shoot''

  • Secondary fire such as ''Grenade''

  • Melee

  • Jump

  • Move character

  • Crouch

  • Iron sight or zoom

  • Use/ Interact (First-Person perspective)

  • Etc.

The secondary actions are slower and doesn't allow the player to move his camera, but he could still move in the environment, hide or avoid attacks. The secondary actions would usually involve:

  • Use/ Interact (3rd person perspective)

  • Reload

  • Cycle through weapons

  • Cycle through grenades

  • Etc.

The tertiary actions would be the ones on the D-Pad and would even be slower, because the player can't move his character while doing it, but could still move his camera. Similar to the secondary actions, but just a little bit slower.

The quaternary actions are the ones that are usually located on the Select or back buttons and start. Usually, those buttons aren't gameplay related.

 

The creation of shortcuts

Sometimes designers struggle when it comes to complicated actions. Fortunately, game controllers might not be a keyboard, but there are ways to offer shortcuts. A good example of that can be found in the Rainbow Six: Vegas franchise in which the player can hold down the reload button and point his left thumbstick in one direction to add or remove a weapon attachment such as a sound suppressor or laser sight.


Logical layout

Sometimes, designers have the opportunity to create more natural button layouts; something that makes more sense. A good example could be Tekken, a fighting game.

X (left): Left punch

Y (right): Right punch

A (left): Left kick

B (right): Right kick

 

If the front leg of your boxer is left, you might connect the dots and expect that the left punch is going to be used to jab.

 

The power of the HUD

The HUD can help you make the controls feel more natural. If the player uses his grenade with the left trigger, it would make sense if that information was displayed on the left side of the screen. If he uses the right trigger to use his weapon, that information should be on the right side of the screen.

HUD of Halo Reach

HUD of Halo Reach

Image of Halo Reach, developed by Bungie and published by Microsoft Game Studios.


The Gears of War syndrome

A lot of current games suffer from the Gears of War syndrome, one button for too many things. By example, we are playing a shooter game and players need to arm an objective. Everyone will try to arm or disarm the objective and die around it. The problem is that they have to use the ''B'' (reload) button to arm/ disarm an objective, but the same button is also used to pickup a weapon. How hard will it be to actually arm or disarm the objective?

That situation can be avoid quite easily, if the players would instead have to hold ''B'' (reload) to arm/ disarm and hold ''Y'' (switch weapon) to pickup a weapon. Make sure while designing the controls of your game that you aren't adding more problems or creating conflicts. Sometimes, it's better to remove a feature.

Read more about:

Blogs
Daily news, dev blogs, and stories from Game Developer straight to your inbox

You May Also Like