#Team fortress classic tropes tv

But ultimately, even that wasn’t enough to save the flames on its own it’s just very difficult to design a damage-over-time effect that’s worth applying when not-damage-over-time effects dominate the field. (As the Flamethrower was originally Pyro’s only source, this wasn’t a huge loss). In return, they removed its ability to ‘stack’ flame damage by applying it via multiple sources. When designing TF2, Valve clearly had the complete failure of the TFC Flamethrower in mind when they severely buffed its damage. In video games, flames usually can turn a bad situation into a hopeless situation, but that happens less without backup. Most of these flamethrowers operated somewhere in between TFC’s (incredibly minor afterburn damage) and They Hunger‘s (can’t ignite, instead each burst of flame deals ludicrously high damage, leaving range-of-effect as its main weakness).

The Flamethrower doesn’t appear in Half-Life, but it’s inclusion in Team Fortress Classic allowed modders to use one in their projects. Monolith Production’s Blood was the first game to have afterburn, and said afterburn killed its opponents extremely quickly. Early video game flamethrowers behaved like the torches on Egypt, only damaging entities as the entities were touching them.

#Team fortress classic tropes tv

You can read more about it on the TV Tropes page Video Game Flamethrowers Suck. In video games you generally want the players to still be functional and you want flamethrowers to fill the “close-range combat” role, so these aspects of flamethrowers are often toned down.

Also, real-life flamethrowers can shoot yards of deadly liquid flames that put every video-game flamethrower to shame. In real-life, they’re impossibly debilitating and would make continuing to do anything, much less fighting other people, an excruciating experience. Picture by ah-darnit.įlames are weird in video games.