← All Essays
History 12 min read

How Valve Built Half-Life

A Microsoft millionaire, a university research group, and a mod of Quake that became one of the most influential first-person shooters ever made

From Microsoft to Valve

Gabe Newell joined Microsoft in 1983 and spent eleven years working on Windows, eventually as a producer on Windows 1, 2, and 3. He became wealthy through Microsoft's growth. When he and Mike Harrington left in 1996 to found Valve Software in Kirkland, Washington, they did so with resources that allowed them to self-fund development without publisher pressure and to build a team by recruiting from universities and the games industry simultaneously. They licensed the Quake engine from id Software — paying approximately $1 million for the rights — and began work on a game that would demonstrate what the engine could do when applied to a coherent narrative design rather than the abstract corridor shooting that Quake itself had offered.

The design philosophy Valve brought to the project was unusual for a first-person shooter in 1996 and 1997. Most FPS games presented the player as an anonymous soldier moving through levels that existed to be cleared of enemies; narrative existed in between-level text screens or brief cutscenes. Valve's team — which included Ken Birdwell, who contributed significantly to the engine's extension for Half-Life's requirements, and Marc Laidlaw, a science fiction author hired as the project's writer — wanted the game's story delivered through the gameplay itself: through events that happened in the player's presence and that the player experienced as a participant rather than as an audience for cutscenes.

The Black Mesa incident

Half-Life's opening — eighteen minutes of riding a tram through the Black Mesa Research Facility, watching scientists and security personnel go about their routines — was a design statement before a single enemy appeared. Players were introduced to the world as Gordon Freeman, a theoretical physicist arriving for work. The facility was populated with characters who had dialogue, who acknowledged the player's presence, who communicated that this was a world with normal operations rather than a pre-configured combat zone. When the experiment went wrong — the resonance cascade that opened a portal to an alien dimension and filled Black Mesa with hostile creatures — the players were inside an established world when it collapsed, rather than arriving after the collapse had already occurred.

The design approach — environmental storytelling, integrated narrative delivery without cutscene interruption, a protagonist present in every scene rather than cut away for cinematics — was not entirely without precedent. System Shock (1994) had delivered its narrative through environmental audio logs without interrupting gameplay. Marathon (1994) had delivered narrative through computer terminals. But Half-Life's execution was more seamless and more dramatic than these predecessors, and its commercial success — 8 million copies sold by 2008, with a peak reception that included 51 awards of game of the year — made it the reference implementation of narrative integration that subsequent FPS designers cited and emulated.

Counter-Strike, mods, and the shift

Counter-Strike began as a modification of Half-Life made by Minh Le and Jess Cliffe in 1999. The mod — a two-team game in which counter-terrorists and terrorists competed over bomb-planting and hostage-rescue objectives — was not the product of Valve's design team but of players who had access to Half-Life's game engine and software development kit and had used those tools to make a different game from Valve's original. Valve acquired the mod and its developers in 2000 and published Counter-Strike as a commercial product that became the most-played online PC game in the world for much of the following decade.

Counter-Strike's success from a mod established the importance of the modding community as a game development resource — a pattern that Valve institutionalised through Steam Workshop and that became standard practice across the industry. But Counter-Strike also illustrated a specific commercial dynamic: the modding community could produce games of greater commercial value than the studio's own subsequent products, and a publisher's relationship with that community was a competitive asset that needed cultivation rather than exploitation. Valve's approach — acquiring rather than simply distributing the Counter-Strike team's work — was the commercial realisation of this insight.

Steam and what followed

Steam launched in September 2003 as a mandatory update delivery system for Counter-Strike — players who wanted to continue playing the game online were required to use Steam, which handled patches and anti-cheat updates. The reception from Counter-Strike players was hostile: the requirement to use a new software layer for a game they had been playing without it felt like an imposition, and Steam's early version was unstable. Newell's response was to continue developing Steam and to make it useful enough that the hostility dissipated as the platform matured.

Steam's expansion from a mandatory update client to a commercial digital distribution platform changed the games industry's retail structure more completely than any single company's decision had since Nintendo's lockout chip had changed the cartridge era's software economics. By 2013, Steam controlled approximately 75 percent of the PC game digital distribution market. Independent developers who had been unable to reach retail shelves could distribute through Steam to a global audience. Publishers who had depended on physical distribution relationships could reach players directly. The platform Valve built to deliver Counter-Strike patches became the infrastructure on which the modern PC game market runs.