TL;DR
During Quake's 1996 crunch the team constrained level size and polygon budgets to ensure performance on early hardware and internet distribution. Designer John Carmack reduced the player's running speed to make smaller maps feel longer and get more gameplay from limited file- and polygon-budget levels.
What happened
In 1996 the Quake development team imposed strict limits on level size and on rendered geometry to keep frame rates acceptable and downloadable map sizes small. Each compiled map had to fit under a 1.4 megabyte BSP limit; if a level exceeded that size the team removed geometry to bring it back under the cap. The engine also flagged scenes where world polygon counts rose above 350 by showing a red flicker; designers used this signal to locate costly views and then added occluding geometry to reduce visible polygons. Levels were constructed in a purpose-built editor called QuakeEd that relied on rectangular "brushes," three views (top-down, side/Z, and a small textured 3D preview) and a two-point slicing technique to create diagonal surfaces. Because those technical constraints produced relatively compact maps, John Carmack elected to slow player movement so traversing a level took longer and the game yielded more playtime.
Why it matters
- Shows how technical constraints (file size and polygon budgets) directly influenced core gameplay pacing.
- Illustrates a trade-off: smaller, performance-friendly maps versus player movement speed to extend playtime.
- Provides an example of early real-time performance debugging (visual polygon budget alerts) shaping level design.
- Highlights how tool limitations (a primitive level editor) affected production workflows and map scale.
Key facts
- Development was in crunch in 1996 when these decisions were made.
- Compiled map files (BSP) were limited to 1.4 megabytes.
- The engine signaled when world polygon counts exceeded 350 by showing a red flicker.
- The team reduced visible polygons by blocking off sightlines with added geometry.
- QuakeEd used rectangular "brushes" as the basic building block for all map geometry.
- QuakeEd offered three views: top-down line view, a sideways Z-line view, and a small textured 3D preview.
- Diagonal surfaces were created by placing two cutting points and slicing brushes, then rotating and adjusting them.
- John Carmack reduced the player's running speed to make smaller maps take longer to traverse and increase gameplay time.
What to watch next
- Whether other Quake-era design choices were similarly driven by file-size or polygon constraints: not confirmed in the source.
- Any follow-up accounts or technical postmortems from the team describing alternative options considered: not confirmed in the source.
- How modern remasters or source ports handle original polygon and map-size limits: not confirmed in the source.
Quick glossary
- BSP file: A compiled map format that stores a game's level geometry and visibility information for efficient rendering.
- Brush: A primitive solid (typically a rectangular prism) used in many level editors as the basic building block of map geometry.
- Polygon: A flat surface made of vertices and edges; polygon count is a key factor in rendering complexity and performance.
- QuakeEd: The in-house level editor used to create Quake maps, employing brush-based construction and multiple orthographic/3D views.
- Occlusion / blocking geometry: Additional geometry added to a level to prevent the engine from rendering distant or unseen parts of a scene, reducing visible polygons.
Reader FAQ
Why was the player's running speed slowed in Quake?
John Carmack reduced run speed so smaller, size-constrained maps would take longer to traverse, increasing playtime.
What file-size limit did Quake maps have during development?
The team capped compiled map (BSP) files at 1.4 megabytes.
How did the team detect expensive views during playtesting?
The engine produced a red flicker whenever the world polygon count exceeded 350, which helped locate costly views.
Was QuakeEd an advanced 3D editor?
No — QuakeEd was intentionally simple and brush-based, with three views and manual slicing to create angled surfaces.
Did the source mention multiplayer or network effects on speed decisions?
not confirmed in the source
Quake's Player Speed IN 1996… We were in crunch mode working to get Quake finished. We had to establish a few guidelines to make sure the levels were next-gen, fast,…
Sources
- Quake's Player Speed (2017)
- How do people in speed-runs move so fast? :: Quake …
- Episode Three: Stroggification – by Chris Mumola – Game Sense
- Bunnyhopping from the Programmer's Perspective (2015)
Related posts
- TOPS-10 in a Box: Ready-to-run PDP-10 TOPS-10 image with Adventure
- Tell HN: Merry Christmas — a reminder to rest, connect, and show compassion
- Show HN: Just Fucking Use Cloudflare — A satirical guide to CF stack