By 1997 the Build engine had already given the world Duke Nukem 3D. Blood took the same technology and pointed it somewhere much darker.
Monolith’s answer to Duke and Doom
Blood was developed by Monolith Productions and published by GT Interactive in 1997. You play as Caleb, a 19th century gunslinger betrayed and killed by the dark god Tchernobog. Resurrected by dark forces, Caleb seeks revenge against the Cabal, an occult organization serving his former master, across four episodes and 42 levels of haunted houses, carnival grounds, and hellish dimensions. Monolith was a young studio at the time, and Blood was one of its first major releases — a bold choice of tone for a debut, leaning all the way into horror at a moment when most of its Build engine competition, chiefly Duke Nukem 3D, was going for pulpy action-movie swagger instead. Caleb’s backstory as a resurrected 19th-century gunslinger also gives Blood a period flavor none of its contemporaries had, letting the game mix Old West iconography with occult horror in a way that feels distinct even now, decades into a crowded genre.
Caleb’s arsenal, weapon by weapon
Blood runs on the Build engine and pushes it to impressive extremes. Caleb’s arsenal is eccentric and brilliant: a pitchfork for melee, dynamite sticks that can be cooked and thrown, a flare gun that sets enemies on fire, a voodoo doll for ranged damage, and the Napalm Launcher for explosive crowd control, alongside more conventional options like a sawed-off shotgun and a tommy gun for when you just need to put bullets into something quickly. Enemy types include zombie cultists, gargoyles, hellhounds, and massive bosses, and the horror-movie references are pervasive — levels nod to The Evil Dead, The Shining, and Night of the Living Dead among others. Difficulty settings dramatically change the game, with higher settings bringing noticeably more aggressive enemy behavior. Cultists in particular are more willing to duck behind cover and pop back out than a lot of enemies from other Build engine games, which keeps firefights feeling a little less predictable even many levels in.
What makes Blood’s horror stick
Next to Duke Nukem 3D’s swagger and Doom’s sci-fi horror, Blood’s atmosphere is genuinely unsettling rather than cartoonish, closer to a B-horror movie than an action flick. Practically speaking, master cooking dynamite fuses instead of throwing them immediately — a well-timed cook-off clears a room that would otherwise chew through your health. Keep flares handy for enemies that come at you out of dark corners, since Blood’s levels lean heavily on ambush design. And explore fully before triggering boss encounters; secrets in Blood often hide better weapons than whatever you’re already carrying. Don’t sleep on the sawed-off shotgun for close-range crowd control either — its spread makes it more forgiving than the tommy gun when multiple cultists rush you at once, even though the tommy gun looks like the more obviously powerful option on paper.
Running Blood (and why NBlood is worth it)
Set up DOSBox via our complete installation guide if you haven’t already. Blood also runs excellently in NBlood, a source port that adds modern conveniences without losing the original’s feel. Sound Blaster configuration is worth getting right on the original DOS release specifically, since a lot of Blood’s horror atmosphere rides on its ambient sound design, and a botched audio setup flattens the experience more than it would in a more purely action-focused shooter.
A high point for the Build engine
Blood arguably has the best weapon design of any Build engine game. The dynamite mechanics alone — holding to cook the fuse, throw timing affecting explosion distance — are more nuanced than most shooters of the era attempted, and the atmosphere is dark, unsettling, and confident, with a real artistic vision behind it. My honest criticism: the difficulty can spike hard and unfairly on higher settings, and some level layouts prioritize atmosphere over clear navigation, so expect real confusion before Blood’s geography starts to click. It’s still a mature, distinctive game that holds up as one of the best things the Build engine produced. Next to Duke Nukem 3D’s one-liners and Shadow Warrior’s over-the-top comedy, Blood’s commitment to actually being unsettling is what makes it stand out in hindsight, and that commitment hasn’t dated the way a lot of period “edgy for its own sake” horror content has. Monolith would go on to bigger, better-remembered releases in the years that followed, but there’s a strong case that they never again matched the singular tone they nailed on their first real swing. A planned direct sequel, Blood II, did eventually arrive, though under different creative circumstances and to a noticeably more mixed reception, which only reinforces how much of the original’s specific character came from the team and moment that made it. Play the original first, on its own terms, before ever touching the sequel — the two are different enough in tone that treating them as a matched pair does the first game a disservice. This is the version of Blood that earned the reputation, and it’s the one worth experiencing before any of the follow-ups. Few shooters from 1997 have earned this much continued fan support, and playing it now makes it obvious why.
You might also like:
