A Practical Guide to the Darksiders The Abomination Vault Audio
I first ran into this back in 2016 when the Darksiders community was digging through the game files for Darksiders II: Deathly Hallows. The Abomination Vault is essentially an unused audio and dialogue vault that was originally built into the game's development kits. It contains voice lines, ambient textures, and some cut narration material that Ari Marmell wrote during the early chapters of Darksiders II's production. Nothing flashy. Just raw audio assets that never made it into the final build. The file structure inside the vault is organized by character and scene type. You have Fury-related dialogue tracks, enemy taunts, environmental ambience loops, and a handful of narrative snippets that reference characters who were cut during development. Ari Marmell's writing notes are sometimes embedded as metadata in the Wwise project files that accompany the vault. That metadata is where the most interesting material lives.
Darksiders The Abomination Vault Audio Ari Marmell
Here is how you actually get your hands on it and make use of it. The vault is not distributed as a single download. It was released in fragments across community preservation efforts over several years. The most complete collection I know of lives on the Darksiders modding forums and has been indexed on sites like Darkspire.net and the Steam Community Guide archives. If you want the full Wwise project package, the path is through the PC version of Darksiders II. The game uses Epic Games' middleware for audio. You need to have Wwise installed first, which is free from Audiokinetic's website. Once Wwise is running, you locate the game's BAK files in the Data directory and use ww2ogg or a similar Wwise extraction tool to pull the audio banks out. From there you can browse the vault directly. I hit a problem early on that took me about three hours to resolve. The Wwise project files in the vault had hardcoded paths referencing internal Stride Engine directories that no longer exist on a standard PC setup. Wwise would load the project but show every audio event as missing. The workaround was simple once I figured it out. You create dummy folder structures matching the original internal paths and point Wwise's search directory to your extracted game files. The events populate correctly after that. Without that step the entire vault looks broken even though nothing is actually damaged.
The audio quality is variable. Some tracks were recorded at professional session rates and sound clean. Others are placeholder recordings or early concept work that was never mixed down. The Fury dialogue tracks are generally the most polished since those carried through to the final game in some form. The Abomination-themed ambient loops are rougher and often contain artifacts from early mixing experiments. What people miss when they first look at this vault is that it contains design documentation encoded in the audio labels. Every .wwa file name follows a specific convention that reveals the intended placement in the game world. For example, tracks prefixed with ENV_ABYSS correspond to the Abyss region maps. Tracks with FURY_COMBAT variants map to specific boss encounters. This is not obvious unless you already know the Stride Engine's naming conventions. I spent weeks mapping these labels against the actual in-game locations by cross-referencing the HUD event triggers in the binary. Another detail beginners consistently overlook is the metadata sidecar files. Ari Marmell's original notes are stored separately from the audio. They are in plain text .txt files that live alongside the Wwise project. These notes contain scene descriptions, character motivation annotations, and alternate dialogue branches that were never voiced. Reading only the audio gives you maybe thirty percent of what is actually in there.
There are limitations worth stating plainly. The vault is incomplete. Multiple characters who were cut from Darksiders II have partial audio but no narrative closure. Some tracks are corrupted from the original export process. The Wwise project references middleware versions that are no longer supported, which means you cannot easily rebuild the audio pipeline without using legacy software versions. If you need the audio for modern game integration or streaming purposes, you will spend time converting and remastering regardless of how careful you are with extraction. Ari Marmell has spoken publicly about some of this material in interviews, confirming that certain Abomination-themed tracks were written for a proposed DLC that was canceled before production. The vault preserves those plans in audio form. That context matters if you are studying the writing or narrative design decisions behind Darksiders II rather than just pulling sound clips. For anyone doing archival or preservation work with this vault, my recommendation is straightforward. Back up the extracted files immediately after unpacking. Use the original Wwise project without modifying it. Document every path correction you make. The community thread on the Darksiders forums has a detailed walkthrough from 2018 that covers the extraction and path-mapping process step by step. I followed that thread when I started and it saved me from making mistakes that would have required restarting the whole project.
The audio itself runs about forty minutes of usable material. Most of it is ambient texture. A smaller portion contains actual spoken dialogue. If you are expecting a full narrated story or cinematic experience, it is not there. It is game audio leftovers. Useful for study, useful for mod projects, not useful as entertainment content on its own. I also want to note that some hosts have packaged the vault contents with promotional blurbs that overstate what is inside. Several YouTube videos claim to offer rare Ari Marmell narration or unreleased cutscenes. That is not accurate. The vault contains dialogue lines and ambient audio. Nothing more. The actual narrative expansions that existed in Marmell's scripts are text documents, not voice recordings. If you want to explore this further, start with the Wwise project on a clean install. Do not skip the path correction step. Read the metadata files before listening to the audio. Map the file names to their in-game locations. Then decide what you actually want from it. The material is there. It just requires patience to work with properly.
Get the Full Details
