Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Get the latest Education e-news
 
  • The Importance Of Definitions In Game Design

    [08.08.19]
    - Louis McTague
  • The games industry is notorious for overloading arbitrary terms used throughout game development. This makes it very confusing when it comes communicating with others. In my personal experience in leadership roles, I've encountered the issue of communicating ideas with other designers. I would explain a design our game needed clearly and concisely, but upon receiving the fruits of the request I would realize that what I said was not nearly as clear and concise as I thought.

    The team sizes for the games I've worked on range from teams of three, up to larger scale teams of thirteen. Being in a leadership role required me to get better at communication with both other designers and other disciplines entirely. In doing this, I learned about the importance of defining terms, and how the more specific the definition is the easier it is to communicate with others.

    Imagine working on a team where you're asked to design a level. The instructions you're provided with are as follows:

    • Level occurs midway through game
    • Medium in length,
    • Focus on action-shooter gameplay.

     Hopefully this scenario is more extreme than most have experienced, but it's likely that many designers have dealt with vague instructions like this. I know that I have! Provide five designers with the above instructions and you'll get five fundamentally different levels. Although different levels from different designers should be expected, having levels that are fundamentally different is bad. Levels must be designed with their sequence in mind, so as to control the introduction of mechanics, rate of difficulty increase, and, hopefully, achieve flow.

    How could this happen when the designer was provided with specific criteria to create a level? This is because the criteria are not defined. Even more specific words that lack proper definitions cause issues. If asked to create a long-range combat engagement, the level designer wouldn't know if that means the level section should have long sight lines, or if placed enemies should rather have long-range weapons. Without specifically defining what a ‘long-range combat engagement' is, it can be difficult to properly communicate what is needed for the game.

    Defining terms early on ensures that all designers are on the same page and can create complementary designs. Once a designer knows that a long-range encounter includes long-range sight lines and long-range enemy types the constructed areas will more closely fit the intended vision. This improves the accuracy of preproduction and builds upon definitions, instead of later deconstructing what has been built and figuring out how to piece them together.

    To show an example of what I'm talking about, let's design a short level for a 1st-Person action shooter game. This game features cinematic narrative moments and areas that facilitate exploration with ammo, health, and lore pick-ups. Let's first create an intended level flow graph based on two axes: time and excitement.

    Time: Measured in minutes assuming the player is playing through an area for the first time and making correct decisions (finding lore pick-ups, not dying in new areas, following the path of progression when presented with forking paths, etc.).

    Excitement: Measured in number of enemies a player encounters at a specific time of play.

    Now that we know our intended difficulty, we have a metric to design our level around. Our level starts easy and reaches its climax 7-8 minutes in. We now have a strong starting point for our level. However, we can go further. Let's define different types of areas, such as combat areas, exploration areas and narrative areas:

    Combat areas: Encourage interesting encounters between players and enemy AI. Contain four or more enemies and prevent the player from progressing further in the level until defeating all enemies.

    Exploration areas: Encourage exploration through interesting layouts and prevalence of pickups. Contains three or less enemies, and at least one ammo and health pickup. May contain lore pickups.

    Narrative areas: Provide the player with exposition through NPC dialogue. If used to introduce a combat area, this area is considered half as ‘exciting' as the following combat area.

    The above definitions are only an example and should be elaborated upon to fit the specific needs of your game. Additionally, other aspects may be considered such as length (can a narrative area last longer than three minutes? Less than ten seconds?).

Comments

comments powered by Disqus