Thief's Dark Engine Was Basically Quake in a Cloak - and That's Good News for the Remaster
Nightdive dug into Thief's original source and found an ancient repo, unhinged code comments and a renderer that borrows its lighting straight from Quake. Here's why that engine archaeology makes me optimistic about how the remaster will actually run.
Rene Sjeverac
Monday, August 24, 2026

Every stealth game made since 1998 owes something to Thief's light gem. I always assumed the tech feeding that little diamond was some exotic one-off, a bespoke shadow simulator cooked up by people who were three years ahead of everyone else. Turns out it was Quake wearing a cloak.
That's the takeaway from Nightdive engineer Josh Dowell talking about Thief: The Dark Project Remastered, as reported by PC Gamer. Per Dowell, Thief's rendering and the technology driving its levels is essentially a clone of Quake - the lighting model works the same way, and even the logic for switching lights on and off comes from the same place. The Dark Engine, the thing PC players have mythologised for nearly three decades, was standing on id Software's shoulders the whole time.
I love this, and not because it diminishes Looking Glass. The opposite. It means Thief's genius was never in the pixels, it was in what the designers decided to *do* with a lighting system that everyone else was using to render rocket trails. Same math, wildly different intent. Quake used light to show you the room; Thief used light to make the room dangerous. That's a design win, not a tech win, and honestly that's the more impressive kind.
The rest of the archaeology is just as good. Dowell described getting access to a very, very out-of-date version control repository, and code comments with, let's say, strong opinions about the state of the codebase. The picture that emerges is a game that was still being actively wrestled with as it walked out the door, with much of the original team having rotated off partway through development and a new crew inheriting the mess. Anyone who has shipped anything will recognise the shape of that story immediately.
Why the plumbing matters for frame times
Here's the part I actually care about as a PC player. When a remaster team starts from real source code instead of reverse-engineering a black box, you get a port that behaves like a native PC game rather than a museum exhibit running in a wrapper. Nightdive's KEX engine has a track record here: uncapped frame rates, sane mouse input, modern resolutions, and crucially a lightweight runtime that isn't dragging a gigantic modern engine's shader pipeline behind it.
Compare that to the standard 2020s remaster playbook, where a beloved old game gets rebuilt in a megaengine and ships with traversal hitches and 1% lows that look like an EKG. I've benchmarked enough of those to be permanently suspicious of any "remaster" announcement that leads with ray tracing instead of frame pacing. A 1998 stealth game does not need path-traced global illumination. It needs consistent frame times, low input latency and mouse movement that isn't filtered through three layers of compatibility shims.
The feature I keep circling back to is built-in support for community fan missions on PC. Thief's mod scene has been producing campaigns for longer than some of you have been alive, and pulling that into the game's own menus is worth more than any texture pass. That is the difference between a remaster you play for a nostalgic weekend and one that replaces the original in your library permanently.
Thief: The Dark Project Remastered is due this winter on PC and consoles, bundling the original campaign plus the Thief Gold missions. If it lands with clean frame pacing and the fan mission pipeline working out of the box, Nightdive will have done the thing almost nobody manages: made the old version obsolete without sanding off what made it good.
And the next time someone tells you a classic was built by geniuses who never compromised, remember there's a repo somewhere with a comment calling the whole thing a disaster.
Image: Martin Vorel / CC BY-SA 4.0, source: https://commons.wikimedia.org/wiki/File:Programming_code.jpg