The Complete Guide to hexdd.wad v1.1 : Unlocking the Lost Expansion for Hexen In the pantheon of 1990s first-person shooters, Hexen: Beyond Heretic holds a unique place. It replaced the rapid-fire spell-slinging of Heretic with a slower, puzzle-heavy, class-based approach. However, the experience many players remember today was not the vanilla release. It was an unofficial, community-crafted masterpiece: hexdd.wad v1.1 . If you’ve browsed classic Doom engine forums, searched for “Hexen Deathkings,” or tried to get the Deathkings of the Dark Citadel expansion working correctly on a modern source port, you have encountered this file. But what exactly is hexdd.wad v1.1 ? Why are there so many versions? And how do you get it running in 2025? This article is your definitive guide.
What is hexdd.wad ? A Quick History First, let’s clear up a common confusion. Hexdd.wad is not a fan-made total conversion. It is the official data file for Hexen: Deathkings of the Dark Citadel , the 1996 expansion pack developed by Raven Software and published by id Software.
Vanilla Hexen: Uses hexen.wad Deathkings Expansion: Uses hexdd.wad
The expansion adds 3 new hubs (Portals of Chaos, The Viscera, and The Temple of the Ancients) comprising 20 new levels, new monsters (like the Venomous Hydra), and a significantly higher difficulty curve. However, the original release (v1.0) had bugs—crashes related to save files, broken scripted sequences, and compatibility issues with the final official patch for Hexen (v1.1). Enter hexdd.wad v1.1 . hexdd.wad v1.1
Why Version 1.1 Matters Raven Software never released an official patch for Deathkings alone. Instead, when they released Hexen v1.1 (the patch that fixed the main game’s networking and savegame bugs), they also recompiled the Deathkings data. The result was hexdd.wad v1.1 . The critical difference: The v1.0 version of hexdd.wad is 26,399,184 bytes. The v1.1 version is 26,405,872 bytes. Those extra kilobytes fix:
A teleporter bug in Hub 2 (The Viscera) where a key door would fail to open. A fatal crash when playing as the Cleric using the Wraithverge on specific enemies. Netcode desyncs in cooperative multiplayer. Scripting errors in the final boss arena of Hub 3.
If you try to play Deathkings on a modern source port like GZDoom or Zandronum using the older v1.0 WAD, you will likely find yourself stuck, unable to progress. v1.1 is the gold standard. The Complete Guide to hexdd
How to Identify a Genuine hexdd.wad v1.1 Because the file is distributed as part of a commercial product, you cannot legally download it for free from random “WAD archives.” You must acquire it from an original CD or an authorized digital retailer (like Steam or GOG.com). However, even legitimate sources sometimes distribute the wrong version. The Checksum Test To verify you have the correct v1.1, calculate the file’s MD5 checksum. Use a tool like CertUtil (Windows) or md5sum (Linux/Mac).
Correct v1.1 MD5: 0b5588c3c1bcb3604e2e536ecd039cf1 Size: 26,405,872 bytes
If your file does not match this, you have the buggy v1.0 version. Where to Get the Correct File It was an unofficial, community-crafted masterpiece: hexdd
Steam: The Hexen: Deathkings of the Dark Citadel DLC on Steam includes v1.1. Look in steamapps/common/Hexen/ . GOG.com: The Hexen: Beyond Heretic package includes Deathkings. GOG’s version is almost always the corrected v1.1. Original CD: If you own the Hexen: Deathkings jewel case CD, check the disc’s README.TXT . If it references “Version 1.1,” you are safe. Otherwise, you can patch v1.0 using fan-made utilities (search for “Deathkings v1.1 patcher”).
Playing hexdd.wad v1.1 in 2025: A Setup Guide Vanilla DOS Hexen cannot run hexdd.wad v1.1 without the main hexen.wad . Here is how to experience Deathkings the right way today. Method 1: Modern Source Ports (Recommended) You need both hexen.wad (from the original game) and hexdd.wad v1.1 . Then, use one of these source ports: