gamesbriefs
10:54in productionCh. 1 · What kind of game is it?/ 10:54 · ceiling 15 min
Shooter · Horror

Killing Floor (video game)

A co-op shooter that makes teamwork mandatory — not optional — by making you worse at staying alive than you are at keeping others alive.

Killing Floor is a co-op first-person shooter where players survive escalating waves of ZEDs using perks, door welding, and a between-wave trader. It launched on Steam on May 14, 2009. It began as a mod for Unreal Tournament 2004. It is Tripwire Interactive’s second game.

Chapters & takeaways4
  1. 1:04
    What kind of game is it?

    It is a co-op FPS first — not a survival horror, not a zombie sim, not a story game.

  2. 2:34
    What is the core loop?

    You choose a perk, level it up across matches, and fight escalating waves ending in a boss — every session.

  3. 5:08
    How does it enforce teamwork?

    Money, welding, and healing asymmetry force players to coordinate — not just shoot together.

  4. 6:45
    Where did its rough edges come from?

    Weapons spawn randomly, and the game grew from an Unreal Tournament 2004 mod — not a clean-sheet design.

Worth your time?

Yes. Play the whole thing.

3.5/ 5
What works
  • perk system gives players distinct roles that compound over time
  • welding doors creates tactical chokepoints
  • trader introduces resource management between waves
  • healing asymmetry forces cooperation
What does not
  • support solo play meaningfully
  • explain its systems in-game
  • scale difficulty dynamically
  • include voice chat by default
Play it if
  • players who enjoy co-op shooters where teamwork is enforced by design
  • those who prefer clear roles, wave-based pacing, and environmental control
Skip it if
  • players who want solo progression
  • those who expect narrative context or UI-guided onboarding
The written brief2 min read

What the game is

Killing Floor is a cooperative first-person shooter developed and published by Tripwire Interactive. It began as a mod for Unreal Tournament 2004. It released on Steam on May 14, 2009. It is Tripwire’s second game.

How it actually plays

Players pick one of seven perks at match start and between waves. Each perk grants bonuses to weapon types, armour, movement, or other factors. Players level up perks across sessions to increase those benefits. They fight successive waves of ZEDs in either Killing Floor mode or Objective mode. Killing Floor mode ends with a boss fight against the Patriarch. Objective mode requires completing challenges to earn in-game money. That money is spent at a trader between waves. The trader sells ammo, armour, and weapons — including katanas, pipe bombs, flamethrowers, and shotguns. Weapons also spawn randomly across the level. Players weld doors shut to control enemy flow. They trade items, drop money for teammates, and heal others more effectively than themselves.

What works

The perk system gives players distinct roles that compound over time. Welding doors creates tactical chokepoints. The trader introduces resource management between waves. Healing asymmetry forces cooperation. ZED waves escalate predictably, letting teams adapt. Objective mode adds goal variety without breaking the loop.

What does not

It does not support solo play meaningfully. Healing oneself is less effective than healing others. There is no single-player campaign. It does not explain its systems in-game. It does not scale difficulty dynamically. It does not feature voice chat by default. It does not include matchmaking beyond server browsers.

Who it is for, and who it is not

It is for players who enjoy co-op shooters where teamwork is enforced by design, not etiquette. It is for those who prefer clear roles, wave-based pacing, and environmental control over open arenas or story-driven missions. It is not for players who want solo progression, narrative context, or UI-guided onboarding.

Is it worth your time

It is worth your time if you want a co-op shooter built around scarcity, spatial control, and class-like perk progression — not narrative, polish, or solo viability. It asks for coordination, not reflexes alone. It rewards repetition, not discovery. It runs on Steam. It launched on May 14, 2009.

Same strand · Shooter4 of 77
11:39
Borderlands (video game)Gearbox Software · 2009Borderlands (2009) is a role-playing shooter developed by Gearbox Software. It combines first-person shooter action with RPG systems—including four distinct Vault Hunters, branching skill trees, mission-driven progression, and a procedural loot engine generating over 15 million weapon and gear variations. Its cell-shaded-like art style gives Pandora a comic-book appearance. Players fight hostile wildlife and human forces on the fictional planet while seeking a fabled Vault.
11:13
Crysis (video game)Crytek · 2007Crysis is a first-person shooter developed by Crytek and published by Electronic Arts. It was released on PC in November 2007. It casts the player as Delta Force soldier Nomad on a hostile tropical island. Its core design premise is 'adaptive tactics'—requiring players to shift between stealth, aggression, lethality and mobility based on terrain, enemy placement and Nanosuit energy state.
8:27
Destiny (video game)Bungie · 2014Destiny is a server-dependent first-person shooter that structures player time around repeated group activities — strikes, raids, patrols, and PvP matches — all governed by Light-level gating and tied to Bungie.net infrastructure. Its strength lies in rhythmic, communal combat execution. Its weakness is systemic opacity and narrative detachment. It asks for consistency, not curiosity.
10:12
Far Cry (video game)Crytek · 2004Far Cry (2004) is a first-person shooter set in a dynamic tropical archipelago. It uses environmental cover, sound, and optical tools to create a sensor-driven combat loop. Enemies react, coordinate, and communicate. Its open maps contrast with linear missions. It is Crytek’s debut AAA title, built on CryEngine, and the first Far Cry game.
Up next in Games

Mass Effect (video game)

BioWare · 2007 · 9:09

Mass Effect trades combat fluency for narrative consequence—and it works only if you’re willing to forgive its jank for the sake of its ambition.

9:09