Level design

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Level design, Environment Design[1] or game mapping[citation needed] is a discipline of game development involving creation of video game levels—locales, stages, or missions.[2][3][4] This is commonly done using a level editor, a game development software designed for building levels; however, some games feature built-in level editing tools. Level design is both an artistic and technical process.[5]

History[edit]

In early days of video games, a single programmer would create the maps and layouts for a game, and a discipline or profession dedicated solely to level design did not exist.[4][5][6]

Early games often featured a level system of ascending difficulty as opposed to progression of story-line.[4]

The first game genre that required significant amounts of time to design areas were text-based games,[7] such as MUDs. Often, promoted users were assigned to create new paths, new rooms, new equipment, and new actions, often using the game interface itself. ZZT is another early game notable for its user-accessible mapping and event triggering/scripting[8]

1983's Lode Runner was one of the first titles to ship with a level editor,[9][10] and its designer, Douglas Smith, reputedly paid neighborhood children to design levels for the game.

Doom (1993) and Doom II (1994) were two of the first games to attract focused game modding activity, and many WAD level files were made for them.[7] One of the reasons was a clear separation between the level files and game engine itself.[7] Half-Life, Quake 3, and many other games have notable mapping tools and communities[citation needed] focusing on user-generated content.

In certain games, such as roguelike games, levels may be procedurally generated. In these cases, the original game programmer controls how the variations of rooms and tunnels are formed, by tweaking the randomly seeded algorithms.[11]


Process[edit]

The level editor of Warzone 2100.

Level design for each individual level in a modern game typically starts with concept art, sketches, renderings, and physical models.[12][13] Once completed, these concepts transform into extensive documentation, environment modeling, and the placing of game specific entities (actors), usually with the aid of a level editor.

A level editor may be distributed as a complete stand-alone package, at times, rivaling commercial 3D modelling software.[5] There are various steps involved in laying out a map and these steps may vary dramatically across the many different game genres that exist today.

General steps include:

  • Laying out the large-scale features of the map, such as hills, cities, rooms, tunnels, etc., for players and enemies to move around in;[14]
  • Determining environmental conditions and "ground rules" such as day/night, weather, scoring systems, allowable weapons or gameplay types, time limits, and starting resources.
  • Specifying certain regions where certain gameplay activities or behaviors occur, such as resource harvesting, base building, water travelling, etc.;
  • Specifying non-static parts of a level, such as doors, keys and buttons with associated mechanisms, teleporters, hidden passageways, etc.;
  • Specifying locations of various entities, such as player units, enemies, monster spawn points, ladders, coins, resource nodes, weapons, save points,[15] etc.;
  • Specifying the start and exit locations for one or more players;
  • Adding aesthetic details such as level-specific graphic textures, sounds, animation, lighting and music;
  • Introducing scripted event locations, where certain actions by the player can trigger specified changes;
  • Placing pathfinding nodes that non-player characters take as they walk around, the actions they will take in response to specific triggers, and any dialog they might have with the player.[5]

Cut scenes may be triggered by events in a level, but require distinctly different skills, and may be created by a different person or team.

The Level Design Process may be iterated several times before achieving the desired outcome.[5]

Level designers and/or concept artists may also be required to provide a pre-rendered map of the level (or entire game world) for the player.[16]

Level bugs[edit]

There are many map bugs that level designers try to avoid, but sometimes go unnoticed for some time.

A player might get stuck in map geometry with no way to escape or to die. A player might be able to find a specific spot where they do not have to move to gain experience, because monsters are constantly spawned but can be easily and immediately killed. In multiplayer maps, a player may be able to reach areas of the map designed to be inaccessible, for example, reaching an advantageous rooftop position and camping other players. In the worst case, a player might be able to fall out-of-bounds of a map where other players cannot reach them.

In some cases, specific mapping tools can be designed to automatically detect problems such as falling "outside" a level, and reaching "stuck" areas. Careful level designers run these tools as the last step before releasing a new version of a level.[17] In most cases, the best way to improve a map is by playtesting it with experienced players, and allowing them to try to exploit any problems.

Level designer[edit]

A level designer is a game designer who creates environments and scenarios using a level editor and other tools.[4][18] Level designers will usually work on a level from pre-production to completion; working with both incomplete and complete versions of the game. Game programmers usually produce level editors and design tools for the designers to use. This eliminates the need for designers to access or modify game code. As opposed to the level editing tools sometimes available to the community, level designers often work with placeholders and prototypes aiming for level consistency and clear layout before required artwork is produced by game artists. Many level designers have skills as both a visual artist and game designers,[5][18][19] although in recent years the responsibility for visual, structural and gameplay related tasks has been increasingly divided among several specialists.

Notable level designers[edit]

A number of individuals have made significant contributions to the field of PC first person shooter levels. These level designers include: John Romero, responsible for a great deal of the level design for Doom, and Richard "Levelord" Gray, creator of a number of levels for Duke Nukem 3D and SiN.[citation needed]

Design goals[edit]

Level design is necessary for two primary purposes - providing players with a goal[20] and providing players with enjoyable play experience. Good level design strives to produce quality gameplay, provide an immersive experience, and sometimes, especially in story-based games, to advance the storyline. Skilled use of textures and audio is necessary to produce immersive player experience.[citation needed]

Gameplay alteration[edit]

Maps' design can significantly impact the gameplay.[20] For example, the gameplay may be shifted towards a platformer (by careful placement of platforms) or a puzzle game[21][22] (by extensive use of buttons, keys, and doors). Some FPS maps may be designed to prevent sniping by not including any long hallways, while other maps may allow for a mix of sniping and closer combat.

Gimmick maps are sometimes created to explore selected features of gameplay, such as sniping or fist fighting.[23] While they are briefly useful to level designers and interesting to experienced players, they are usually not included in final list of levels of the game because of their limited replay value.

Player directing[edit]

Levels are generally constructed with flow control in mind,[24] that is directing the player towards the goal of the level and preventing confusion and idling. This can be accomplished by various means.

Often the level layouts features power-ups and items aligned in path and combinations that collecting them inevitably progresses the game and advances the story-line. This is one of the basic player direction technique and is most often seen in platformers.

Lighting and illumination, as well as distinctly coloured objects are often used to unambiguously steer the player towards the correct path. Similarly, clearly marked choke-points can be introduced.

Another method is strategic placement of obstacles and aesthetic environment props, that direct the player's attention to "clear" paths instead. This is often used in closed, "stuffed" environments.

Levels may be designed to force the players to explore the map and advance. Most RTS maps give each player a starting base, but will have resource distribution and terrain features designed to draw players out of their base and engage each other. Teamplay maps can provide noticeable advantages to one team over another, when designed poorly.

Hidden features[edit]

Level designers sometimes create hidden rooms and areas that usually require more tries to reach or to notice.[25] These usually give some additional rewards, such as ammo or powerups. Casual players usually do not discover these, but these areas are interesting enough to be discovered and documented by dedicated gamers. Sometimes, they serve as easter eggs,[25] containing messages such as the level designers' names or pictures, or political or humorous messages. One of the first games with a 3D engine to feature hidden features was Wolfenstein 3D, where certain walls could be "pushed" to reveal hidden passages.[25] For example, Quake has many secret areas that reward the player with ammo, weapons, quad damage powerups, and in one hard-to-reach secret area, Dopefish makes an appearance. In fact, the hardest difficulty level, titled "Nightmare", is only reachable through a secret portal in the fourth dimension's entrance hall.

Sometimes, a whole level may be designed as a secret level.

Tools[edit]

A wide variety of tools may be used by someone designing a level. Although it is faster to design models and textures with general purpose multimedia creation tools, games usually require the data to be in a unique format suited for that game's engine. For this, specific compilers and converters of models, textures, and audio data may be required to lay out a level.

Some level editors for Windows games include Bethesda Softworks's Construction Set, Valve's Hammer Editor, Epic's UnrealEd and UDK, Leadwerks 3D World Studio, BioWare's Aurora Toolset, id Software's Q3Radiant, Unity 3D and Grome outdoor editor. Multi engine, multi game editors include id Software's GtkRadiant, based on Q3Radiant, and the open source QuArK. Some games may have built-in level editors like Battlezone 2, Cube 2: Sauerbraten and Doom 3. An example of a console game with a level editor is TimeSplitters, developed by Free Radical Design. Sometimes, professional 3D editing software, such as 3D Studio Max, Blender, AutoCAD, Lightwave, Maya, Softimage XSI or Grome is used, usually customized with a special plugin developed for the specific game.[citation needed]

Notes[edit]

  1. ^ Oxland 2004, pp.21-22,126
  2. ^ Bates 2004, p.107
  3. ^ Brathwaite, Schreiber 2009, p.5
  4. ^ a b c d Shahrani 2006, part I
  5. ^ a b c d e f Bleszinski, Cliff (2000). "The Art and Science of Level Design". Archived from the original on 3 December 2002. Retrieved 29 March 2010. 
  6. ^ Bates 2004, p.162, "A few years ago, [level designer] position didn't exist. .. Now it's a key position on many teams."
  7. ^ a b c Shahrani 2006, part III
  8. ^ "ZZT". Everything2. April 25, 2003. Retrieved March 29, 2010. 
  9. ^ Lode Runner Contest, Computer Gaming World, August 1984: 22 
  10. ^ "Lock'n'Lode". IGN. February 17, 1999. Retrieved March 29, 2010. 
  11. ^ "classic.1up.com's Essential 50: Part 12. Rogue". 1UP.com. Retrieved March 29, 2010. 
  12. ^ Bates 2004, p.107-110
  13. ^ Oxland 2004, pp.132-135
  14. ^ Oxland 2004, pp.128-130
  15. ^ Oxland 2004, p.139
  16. ^ Oxland 2004, pp.140-141
  17. ^ Bates 2004, pp.117-118
  18. ^ a b Moore, Novak 2010, p.76
  19. ^ Bates 2004, p.118
  20. ^ a b Bates 2004, pp.111-112
  21. ^ Bates 2004, pp.116
  22. ^ Brathwaite, Schreiber 2009, p.48
  23. ^ Bates 2004, p.108
  24. ^ Bates 2004, pp.113-114
  25. ^ a b c Shahrani 2006, part II

References[edit]

See also[edit]