Hexdd.wad V1.1 Verified May 2026

Restoring the Music: Why You Need HEXDD.WAD v1.1 If you've recently picked up Hexen: Deathkings of the Dark Citadel on Steam or GOG, you might have noticed something eerily quiet—and not in a good way. Despite being a legendary expansion, the version often distributed digitally is the unpatched v1.0, which famously suffers from a bug where the music simply doesn't play in most source ports. The v1.1 Difference

The primary reason to track down HEXDD.WAD v1.1 is the music fix. While v1.0 contains all the levels, it fails to correctly associate the music tracks with the maps. The v1.1 update re-associates these tracks so you can finally hear the dark, atmospheric score while battling through the Citadel .

File Size Check: You can verify your version by checking the file size of your HEXDD.WAD. v1.0: ~4,429,700 bytes . v1.1: 4,440,584 bytes . How to Upgrade

Since many official digital releases still package the broken v1.0, the community has kept the fix alive:

Download the Patch: Look for dkpatch.zip on reputable community archives like the idgames archive at Doomworld .

Apply the Fix: If you are using a modern source port like GZDoom, you can often simply replace your old HEXDD.WAD in the game folder with the patched v1.1 version .

Steam Users: To find your file, right-click the game in your library, select Manage > Browse local files, and navigate to the base folder . Compatibility Note

Remember that Deathkings is an expansion. Even with the v1.1 WAD, you still need the original HEXEN.WAD (v1.1) in the same directory for the game to run correctly in most engines . Guide :: Fix missing music problem in Hexen: Deathkings

HEXDD.WAD v1.1 is the data file for Hexen: Deathkings of the Dark Citadel , the only official expansion for Hexen: Beyond Heretic.

While it is technically an IWAD (Internal WAD), it functions more like a PWAD because it requires the original HEXEN.WAD to run. Key Differences: v1.0 vs. v1.1 hexdd.wad v1.1

The primary reason version 1.1 is "interesting" is that it fixes a major flaw found in the version still commonly sold on digital storefronts like Steam. Feature v1.0 (Steam/Original) v1.1 (Patched) MIDI Music ❌ No music plays during gameplay ✅ Full music support File Size 4,429,700 bytes 4,440,584 bytes Technical Fix Missing SNDINFO lump Includes SNDINFO lump Music Source Relies on external CD audio Reuses original Hexen tracks Content Overview

Levels: Includes 26 new maps across 3 hubs, plus 6 deathmatch maps.

Gameplay Changes: Unlike the original game, Deathkings features monster respawning for enemies other than just Ettins.

Item Management: It relaxes the "use it or lose it" rule for rare artifacts like the Porkalator and Krater of Might, allowing you to carry them between hubs. How to Check Your Version

You can verify your version by looking at the file size or checking the loading screen. Note that the "v1.1" on the loading screen often refers to the Hexen engine version, not necessarily the HEXDD.WAD file itself. To fix a v1.0 file, fans typically use the dkpatch.zip utility available on community sites like the Doom Wiki.

If you are a modder or looking for a modern experience, projects like HXDD on GitHub allow you to merge these files into a single unified game structure. If you'd like, I can help you: Find the patch to fix the missing music. Locate cheats or walkthroughs for the expansion.

Set up a source port like GZDoom to run it on modern Windows. How would you like to proceed with your Hexen setup? Guide :: Fix missing music problem in Hexen: Deathkings

hexdd.wad v1.1 is the main data file for Deathkings of the Dark Citadel, the official expansion pack for the dark fantasy shooter Hexen: Beyond Heretic. Technical Profile File Name: hexdd.wad Version: 1.1 (Final official release) Original Release Date: 1996 Developer: Raven Software Publisher: id Software

Format: IWAD (Internal WAD), meaning it contains all the necessary data to run as a standalone game or extension, provided the original Hexen engine is present. Content Overview Restoring the Music: Why You Need HEXDD

This WAD adds significant content to the base game, focusing primarily on high-difficulty level design rather than new gameplay mechanics.

New Hubs: 3 brand new hubs (The Blight, The Cloister, and The Dark Citadel).

Level Count: 20 new single-player levels and 6 new deathmatch maps.

Difficulty: Significantly higher than the original Hexen. It is designed for veteran players, featuring complex switch-hunting puzzles and high enemy density.

Assets: It utilizes the original three character classes (Fighter, Cleric, Mage) and their existing weapons. It does not introduce new enemies or textures, instead reusing assets from the original hexen.wad. Common Issues & Solutions

Engine Compatibility: While it can run on the original DOS executable, it is most commonly played today using modern source ports like GZDoom or DSDA-Doom.

Setup: In most source ports, you must have both hexen.wad and hexdd.wad in the same folder. The engine typically recognizes hexdd.wad as the expansion and will prompt you to choose between the original game or Deathkings.

Steam/GOG Versions: If you purchased the game on Steam or GOG, the hexdd.wad file is located within the base or data subfolder of your Hexen installation.

The file HEXDD.WAD v1.1 is the data file for Hexen: Deathkings of the Dark Citadel, the only official expansion for the dark fantasy shooter Hexen: Beyond Heretic. The Official Story If you meant a different file (e

The narrative begins exactly where the original Hexen ends. After defeating the second Serpent Rider, Korax, the heroes discover the Chaos Sphere. Instead of bringing peace, the sphere's volatile energy whisks the heroes away to the Realm of the Dead.

To return to the world of the living, you must fight through three massive hubs—comprising 20 single-player levels—to reach and conquer the Dark Citadel, the only gateway back home. Why "v1.1" Matters

Version 1.1 was a critical technical update for the WAD file. The original v1.0 release suffered from a major bug where the music was improperly mapped, causing tracks to play on the wrong levels or not at all.

The Fix: v1.1 corrected the music associations and included a patch to ensure compatibility with Hexen v1.1, which added support for 8-player starts in multiplayer.

Identification: A genuine v1.1 HEXDD.WAD is approximately 4.23 MB (4,440,584 bytes) and contains 326 entries. How to Use It

Most modern players use source ports like GZDoom or ZDoom to run the WAD. If you have the Steam version and the music is missing, you likely need to replace your old HEXDD.WAD with the v1.1 version in your /base/ folder. Hexen: Deathkings of the Dark Citadel | Doom Wiki | Fandom

3. Co-op with Old Friends

Nothing ruins a LAN party or remote Zandronum session faster than a v1.0 hub portal glitch. V1.1 ensures that all players can move between maps 2, 5, and 8 in the “Cataclysm” book without one player getting stuck in a void.

If you don’t have it:

It's abandonware but still copyrighted – not freely redistributable. You’d need to acquire the expansion from a used copy or digital re-release (e.g., Steam/GOG's Hexen: Beyond Heretic often includes Deathkings as DLC).

If you meant a different file (e.g., a custom map called hexdd.wad), please provide more context (where you found it, file size, any readme). Otherwise, the above should answer your question.

Here is text written for hexdd.wad v1.1, formatted as if it were a release description for a modding archive or community forum.

4. Compatibility Matrix (how to determine)

  • If only vanilla lumps (MAPxx, PNAMES, TEXTURE1/2, PLAYPAL), compatible with Vanilla and Boom-era ports.
  • If DECORATE/ACS, require ZDoom-derivative (GZDoom) or compatibility layer.
  • If ZSCRIPT present, require GZDoom 4.x+.
  • If OGG/MP3 present for music, most modern ports support them; vanilla clients do not.
  • Recommendation: test with both a classic engine (DOSBox with legacy executable or Chocolate Doom) and a modern port (GZDoom/Eternity) and note behavior differences.

6. Testing & Validation Procedure

  1. Identify target source port(s) by scanning lumps for engine-specific scripts.
  2. Run automated lump-list inspection (SLADE or wadinfo) to list contents and detect malformed lumps.
  3. Test startup: load in target port; record startup errors/warnings in console.
  4. Walk each map fully in both vanilla and targeted modern port to detect:
    • Soft-locks, out-of-bounds areas, unreachable keys/doors.
    • Texture alignment/holes.
    • Lighting extremes or sector height mismatches.
    • Script/runtime errors (actor spawn problems, decorator errors).
  5. Playtest: note difficulty spikes, ammo/health balance, monster pathfinding.
  6. Audio/visual check: verify music and sound playback, sprite alignment.
  7. Regression test after each fix; update changelog.