A total conversion replaces a game’s art, sound, levels and often its rules, keeping only the engine. The result plays as a different game entirely. The genre produced some of the most ambitious amateur work of the period, and also some of the most fragile.
The fragility is worth examining, because it explains why so many of these projects are difficult to run now, and why some vanished completely while their more modest contemporaries survived.
The dependency that never went away
However complete a total conversion was, it still needed the original game installed. The engine executable was the one thing that could not be replaced, because it was the commercial product being modified rather than data being loaded by it.
For most of the 1990s this was a reasonable expectation. The base games were popular and widely owned. A project could assume its audience already had a copy, and distribute only the replacement content.
The assumption aged badly. Two decades on, the modification is downloadable and the game it needs may not be, or may be available only in a rereleased form with a different file layout, a different executable and different behaviour. The mod survived; its host did not survive unchanged.
Version pinning made it worse
Engines changed across patches. A conversion built against one point release frequently misbehaved on another, because it depended on specifics of how that build handled a particular entity, sound or rendering path.
Readme files from the era are full of instructions to install a specific patch level and no higher. Those instructions were sound advice at the time and are close to unusable now, because the patch in question was distributed from a publisher’s server that stopped existing years ago.
- Check whether a source port supports the conversion directly. Many ports have absorbed compatibility handling for well-known projects.
- Read the original documentation before assuming a failure is a bug. A large share of problems are the documented version requirement, unmet.
- Note which files the conversion actually replaces. Where it only replaces data, options are broader than where it also ships a modified executable.
The distribution problem
Total conversions were large by the standards of the connections available. A project could run to tens or hundreds of megabytes at a time when that was an overnight download. Distribution therefore concentrated on a handful of hosts, mirrors and cover discs.
Concentration is efficient and fragile in equal measure. When a host closed, everything it uniquely held went with it. Projects that were mirrored widely survived; projects that lived on one enthusiast’s server generally did not, regardless of quality.
This is a genuinely poor filter for what should have been preserved. Survival correlates with how well-connected the team was, not with how good the work was.
Modified executables and the legal grey
Some conversions went further and shipped patched executables, either to change engine behaviour or to remove the dependency on the original data files. This solved the installation problem and created a distribution problem, because the result contained modified commercial code.
Projects in that position tended to be circulated quietly, which is precisely the opposite of what preservation requires. The more self-contained a conversion was, the less openly it could be shared.
The situation improved substantially where engines were later released under free licences. A conversion could then target a legitimately redistributable engine, and several long-running projects made exactly that migration. Where no such release happened, the original constraints still apply.
What made a conversion durable
Looking across the projects that are still straightforwardly playable, the pattern is consistent and unglamorous. They kept content and engine strictly separate. They documented their requirements precisely. They were mirrored in more than one place. They targeted an engine that later became freely available.
None of that has anything to do with the quality of the design, the writing or the art. Durability was a distribution and architecture property, decided early, usually without anyone thinking of it as a preservation decision at all.
That is a useful lesson for anyone building on someone else’s engine today. The work that survives is the work that can be moved.