Gaming Mechanics & Design Codexery

Level (video games)

A defined space for player objectives in video games.

Level (video games)

In video games, a level (also referred to as a map, mission, stage, course, zone, area, or round, depending on context) is any space available to the player during the course of completion of an objective. Video game levels generally have progressively increasing difficulty to appeal to players with different skill levels, and each level may present new concepts and challenges to keep a player's interest high. Level design, or environment design, is a discipline of game development involving the making of these locales, stages, or missions, commonly done using a level editor.

field
Video game design
known_for
Providing players with goals and enjoyable play experience through structured spaces
related_concepts
Level editor, level streaming, player directing
first_game_with_level_editor
Lode Runner (1983)

Lore & Background

In the early days of video games (1970s–1980s), a single programmer would develop the maps and layouts for a game, and a discipline or profession dedicated solely to level design did not exist. Early games often featured a level system of ascending difficulty as opposed to progression of storyline. An example of the former approach is the arcade shoot 'em up game Space Invaders (1978), where each level looks the same, repeating endlessly until the player loses all their lives. An example of the latter approach is the arcade platform game Donkey Kong (1981), which uses multiple distinct levels to progress a storyline; as Mario (originally called Jumpman) tries to rescue Pauline from Donkey Kong, each level ends with Kong fleeing with Pauline and then Mario having to complete a different level each time, until he finally confronts Kong.

1983's Lode Runner was one of the first titles to ship with a level editor. Its designer, Doug Smith, reputedly paid neighborhood children to design levels for the game. The same year, the multiplayer dungeon crawl Dandy was released, and it also shipped with a level editor which was documented in the manual. ZZT (1991) is a later game with user-accessible mapping and scripting. A game genre that required significant amounts of time to design areas were text-based games, such as MUDs. Often, promoted users were assigned to make new paths, new rooms, new equipment, and new actions, often using the game interface itself.

3D first-person shooters 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. One of the reasons was a clear separation between the level files and game engine itself. Half-Life, Quake 3, and many other games have notable mapping tools and communities focusing on user-generated content.

Reader's Guide

Level design is necessary for two primary purposes: providing players with a goal 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. Levels are generally constructed with flow control in mind, directing the player towards the goal and preventing confusion and idling. This can be accomplished by various means, such as positioning power-ups and items so that collecting them inevitably moves the player in the correct direction, using lighting and distinctly-colored objects to guide the player, or strategic placement of obstacles and aesthetic props.

Level streaming, enabled by faster hardware such as optical drives, hard disk drives, solid-state drives, and larger amounts of memory, allows continuous loading of new level assets as the player approaches the edge of one level and the start of a new one, making transitions appear seamless and avoiding loading screens. This is often used for open world games. Tricks such as reducing player speed, presenting story cues, or requiring entry into areas with restricted views (sometimes called 'loading tunnels') give hardware time to load assets. Newer consoles with special SSD arrays and high-throughput software libraries can eliminate the need for loading tunnels in a seamless world.

Did You Know?

The Architecture of Play: What Game Mechanics Actually Are

Game mechanics form the foundational architecture through which any game—whether played on a tabletop or rendered on a screen—communicates its possibilities to the player. At their core, they are the rules and ludemes that both constrain and enable action: a rule tells you what you may do, while a ludeme is a specific element of play, like the distinctive L-shaped path a knight traces across a chessboard. The interplay among these individual mechanics is what generates a game's overall complexity and shapes how players engage with the system. Every game, without exception, relies on mechanics, though scholars remain divided on how central they are to what makes a game a game. The discipline of game design is, in large part, the iterative craft of building and refining these mechanics so that they hold a player's attention and invite meaningful decision-making.

Where Mechanics End and Theme Begins

A game's mechanical structure and its thematic skin are fundamentally separate layers, even though they often appear fused in a finished product. In Monopoly, for instance, the underlying mechanics involve buying and selling properties, but the theme dresses that exchange in the language of real estate and wealth. Two titles can share nearly identical mechanical systems while telling completely different stories, or conversely, wear similar thematic costumes over entirely different rule engines. When the mechanical logic and the narrative framing pull in opposite directions, the result is what scholars call ludonarrative dissonance—a creative tension that can either undermine a game's coherence or, in skilled hands, produce unexpected depth. At the other extreme, abstract games such as Go dispense with theme altogether; their pieces and moves are not meant to represent anything beyond the geometry of the board itself.

Drawing the Line Between Mechanics and Gameplay

Within game studies, a persistent debate concerns where mechanics stop and gameplay begins. Some researchers treat gameplay as the lived, interactive process that emerges when a player engages with the underlying mechanical systems—essentially, the experience that arises from the rules in motion. Others frame it more cognitively, as the performance of mental tasks within a designed environment. Carlo Fabricatore offers a two-part definition: gameplay encompasses both what the player is able to do and what other entities in the game do in response. Ernest Adams and Andrew Rollings take a broader view, describing gameplay as the combination and interaction of many game elements working together. Despite these academic distinctions, everyday usage frequently collapses the two terms, with sites and communities using "gameplay" to mean the core mechanics that define a title's character. This ambiguity reflects a genuine difficulty in separating the static rule set from the dynamic experience it produces.

A Working Taxonomy: How Mechanics Get Sorted

Scholars have long sought orderly ways to sort the vast landscape of game mechanics into manageable categories, and the results feed directly into how games are classified and compared. Geoffrey Engelstein and Isaac Shalev, in their work on tabletop design, propose a framework that groups mechanisms along axes such as game structure, turn order, available actions, resolution methods, victory conditions, sources of uncertainty, economic systems, auction formats, worker placement, movement, area control, set collection, and card-based interactions. Beyond this structural taxonomy, individual mechanics take many concrete forms. Action points give each player a finite budget per turn to spend on movement, card draws, or resource gathering. Alignment systems in role-playing titles tie a character's moral orientation to which abilities or companions are available. Auction and bidding mechanics let players compete for the right to act, sometimes paying in-game currency and other times staking a promise of future performance. Capture and elimination mechanics, found in games from chess to Go, define how a player's strength on the board is reduced through displacement, jumping, surrounding, or declared attacks.

Frequently Asked Questions

What is a level in video games?

A level is any defined space a player inhabits while working toward a specific objective, whether that's called a map, stage, zone, or mission depending on the genre. It serves as the fundamental structural unit that organizes a game's progression and content.

What is level design and who does it?

Level design (also called environment design) is the game-development discipline focused on crafting the locales, stages, and missions players interact with. Designers typically build these spaces using a dedicated level editor tool provided by the engine or studio.

Why do video game levels usually get harder as you progress?

Progressive difficulty is a core design choice meant to match a player's growing skill while keeping engagement high. Each successive level often introduces new mechanics or challenges so the experience stays fresh rather than repetitive.

What was the first video game to ship with a level editor?

Lode Runner, released in 1983, is credited as the first game to include a level editor, letting players construct and share their own custom stages. This feature became a major part of its lasting appeal and influenced countless later titles.

What are some related concepts to levels in game design?

Level streaming (loading in/out chunks of a world seamlessly), player directing (guiding the player's attention and path through spatial cues), and level editors (tools for building or modifying stages) are all closely tied to how levels function in practice.

More in Gaming Mechanics & Design 1-17

Spotted an error? Know more?

This is a living reference — every entry is fact-audited, and reader corrections feed straight into our audit queue. Suggest an edit · See this site's audit record

Comments

Loading…
Open in the interactive codex →