# Typology ## What's a typology? A **typology** is a layout design pattern, a class system that helps us think about layouts. It *abstracts* the layout -- it simplifies and generalizes the structure. {% hint style="info" %} **Why say "typology" instead of "type"?** It's not just academics being pretentious. Adding the "-ology" part reminds us that it is a big field of study, a system of ideas connected to other ideas. "Types" is too general. {% endhint %} ![architectural diagram "formal typologies of dense residential architectures", by Maja Baldea (via Density Architecture blog)](https://1666186240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtVT8pJjInrrHVCovzy%2Fuploads%2FxfRLuQ0NNUImorA77zDE%2FLDB_Typology_DensityArchitecture_MajaBaldea.jpg?alt=media\&token=8ead8433-3018-4e24-8ca9-7da4fa4cf55e) In the real world architecture diagram above, Maja Baldea thinks about different ways to organize apartment buildings. She *abstracts* (simplifies, generalizes) these buildings as windowless blocks because she's not interested in little details, she's thinking about the overall shape, [massing](https://book.leveldesignbook.com/process/blockout/massing), and [composition](https://book.leveldesignbook.com/process/blockout/massing/composition), to **classify different types** of residential buildings. Typologies are useful for: * classifying different types of level design * reasoning about map [balance](https://book.leveldesignbook.com/process/combat/balance) and [encounter](https://book.leveldesignbook.com/process/combat/encounter) design * open world / battle royale type projects, since a variety of typologies will usually lead to a variety of game content * shared design language, aids collaboration and teamwork ## Elements Beyond walls, floors, and ceilings, there's also some common *gameplay elements* frequently found in most levels: * [**Cover**](https://book.leveldesignbook.com/process/combat/cover). Half cover vs. full cover, hard cover vs. soft cover. * [**Gates**](https://book.leveldesignbook.com/process/layout/typology/gates). Hard gate vs. soft gate, lock and key, forward gating vs. backward gating. ## Room typologies **Room typologies** are generalized patterns for a single area / "chunk" of the level. {% hint style="info" %} We use "room" as a generic term for "space." A room could be a garden, cave, etc. This dates back to 90s game engines, where outdoor spaces were rooms with sky ceilings. {% endhint %} ### Corridor ![](https://1666186240-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtVT8pJjInrrHVCovzy%2F-Lv6YGpBQxsQzANptpRi%2F-Lv6vQsjMSxXDUp7QepP%2Fleveldesignbook_corridor.png?alt=media\&token=678486bc-d308-4500-8c74-74f2506d5ed5) Straight-on linear progression through the space, like a hallway, river, or canyon. Anything with a one-way trajectory through a predictable sequence of spaces could be considered a corridor. * High degree of authorship, control, and certainty. You know where the player must go and how much time the player will likely take. * To speed it up, add downward slopes, one-way drops, and bright lighting * To slow it down, add side areas, alcoves, and spotty lighting #### Corridor example: house in P.T The first person horror game P.T. (2014) made players walk down the same hallways over and over, with a looping mechanic that teleports the player back to the start once they open the door at the end. It is a powerful use of the corridor, and would've suffered with a more open layout. ![Floorplan and critical path for P.T. (2014) by Kojima Productions; to complete the game, the player must solve hidden puzzles and loop through the same set of hallways at least 12 times](https://1666186240-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtVT8pJjInrrHVCovzy%2F-Lv6YGpBQxsQzANptpRi%2F-Lv6tE3LQLOrPYmjcvan%2Fleveldesignbook_pt.png?alt=media\&token=e21be228-d0c9-4173-bfb3-1c214543a816) Note the strong control of sightlines, forcing the player to stare through a window at the corner, or to detour into the bathroom to notice the mirror and sink. Horror tropes and ominous alcoves discourage players from moving too quickly, while linearity and familiarity culminate in a sense of foreboding, dread, and doom. All we can do is go deeper, and there is no escape. ### Switchback / Hairpin A dead-end corridor with a visible exit when you backtrack. * Similar to corridor, offers a lot of control and authorship * Obscuring the exit encourages the player to explore the dead-end first * Brief confusion, mild sense of exploration and navigation Switchback example: cave in Dear Esther ### Ring Around The Rosie / Combat Bowl Small open area with [cover](https://book.leveldesignbook.com/process/combat/cover) in the middle, usually full cover like a pillar or column, resulting in a spinning / rotating flow. Especially common in fast-paced combat games, where players can "dance" / circle-strafe around the central cover while blocking enemy attacks. * Add a one-way drop to force a specific flow, and/or introduce some verticality ### Arena / Point of Interest (POI) ![](https://1666186240-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtVT8pJjInrrHVCovzy%2F-LvCPUfM6ZFrYpR7MOEF%2F-LvCPYN0y1Fy8Bw47a79%2Fleveldesignbook_arena_simpler2.png?alt=media\&token=ac70f80e-5481-403e-8f8a-685407cf7fac) An **arena** is an open area with several lanes of [circulation](https://book.leveldesignbook.com/process/layout/flow/circulation) and some [cover](https://book.leveldesignbook.com/process/combat/cover) in the middle. * open world and battle royale designers use **points of interest (POIs)**, big arenas anchored by a large landmark with multiple entrances and exits * in single player, arenas usually need [gating](https://book.leveldesignbook.com/process/layout/typology/gates); gate players from leaving the arena early, but also gate the entrance to prevent players from pulling all the enemies into a chokepoint #### Example: Dead Simple in Doom 2 (TODO: draw Dead Simple floorplan and critical path) ## Level typologies **Level typologies** are generalized layout patterns for multiple rooms / entire levels. ### Hub-and-spoke A larger multi-area pattern with a central area (hub) and several smaller areas / passages extending off of it (spokes). To explore different spokes, the player must return to the hub. * Gives unifying identity to different spokes, conveys logic to the structure * Needs lots of work to update the hub with each visit, or else it'll feel like backtracking * Can be a useful pacing tool, returning to a hub can feel like a relaxing reward * Gated hubs block off most spokes at the start, the player gradually unlocks shortcuts * #### Example: Medical Pavilion in BioShock 1 BioShock 1 features multiple hub-and-spokes. In the beginning Medical Pavilion chapter 1 ### Loopback (TODO: diagram) A linear progression that loops back on itself, most common in open world dungeons. * Similar to Corridor: lots of control and certainty with less player indecision * Helps an area feel structurally non-linear and plausible, even if progression is initially linear * Subtle loopbacks feel like closing the loop of a natural inevitable circuit * Overly convenient loopbacks can feel like contrived shortcuts that plead for the player's gratitude, and thus feel artificial or implausible #### Example: (some dungeon) in Skyrim (example: skyrim layout and screenshot) The open world fantasy RPG Skyrim features many dungeons where the player must return to the overworld after completing the dungeon. However, backtracking often feels monotonous or rote after an area has been cleared out... (TODO: finish) ### Branching chokepoints / string of pearls ### Pass-through ### Time cave ## Multiplayer typologies Multiplayer layouts tend to be more nonlinear, circuitous, and bidirectional, emphasizing high replay value with reusable areas. Many team-based games feature bases / spawn rooms where players can safely join the game, as well as capture points for the teams to attack and defend. ### Base / spawn room ### No man's land ### Sniper nest / sniper alley ### Figure 8 most common in classic CTF maps, Blood Gulch, etc ### Connector / Pivot In multiplayer team games with bases and routes toward capture points Example: CS:GO ### Three lane Example: League of Legends, DOTA, Call of Duty: Modern Warfare... also common in CS:GO (1 lane for each bomb site, and middle connector lane) ## Against typology? Once you classify something, you're potentially trapping yourself within the limits of those classifications. Sometimes it may be more helpful to ignore typologies and refuse categorization. ## To review\... A **typology** is a way to classify different categories of level layouts. These words and labels help us talk and think about layout. **Room typologies** are patterns for designing single areas, like corridors, switchbacks, ring-around-the-rosies / combat bowls, and arenas / POIs. **Level typologies** are patterns arranging multiple rooms in sequence, like loopback, pass-through, branch and bottleneck, hub-and-spoke, and time cave. ## Further reading / sources * ["A Pattern Language"](https://en.wikipedia.org/wiki/A_Pattern_Language) (1977) by architect Christopher Alexander et al. is the classic typology manual of modern architecture and urban planning today, pioneering the New Urbanism movement. * ["On the ‘Three Typologies’"](https://medium.com/@tlukejones/on-the-three-typologies-ed0b5747fd9c) (2017) by architect Luke Jones is a wonderful essay about how architects still aren't quite sure how to classify architecture.