Explore the snowy homeland of the Barbarians, face fiendish new monsters, and arm yourself with thousands of new weapons, armor, and magical items in the fight against the last of the Prime Evils.

Post tutorial RSS Turning a -direct -txt mod into a Mac & Win compatible D2 patch

Turning a -direct -txt mod into a Mac & Win compatible D2 patch

Posted by on - Basic Installers

First of all, to make a Diablo 2 patch, you need to use Windows. Once we are done, the resulting file will be compatible with Mac nontheless.

In this tutorial, we will make a mod patch for Diablo 2 LOD version 1.13 and 1.14.


  • Relatively basic knowledge of Windows
  • Being familiar with the concept of a Diablo 2 "-direct -txt" mod
  • An unedited Diablo 2 Lord of Destruction 1.13 or 1.14 installed
  • A "-direct -txt" mod

Note: In this tutorial, when I refer to "your Diablo 2 directory" I always mean a vanilla LOD 1.13 or 1.14 install with no mods.

Step 1. Extracting an unedited 1.14 (or 1.13) patch

1. Download an MPQ extractor. In this tutorial we will be using mpqediten32 with updated filelist for Diablo 2 1.13-14.

2. Open MPQEditor.exe

3. Select "File" -> "Open MPQ (s)"

4. Still in the "Open MPQ(s)" window, go to your Diablo 2 LOD directory and select "patch_d2.mpq", and then open it.

Note: Select a clean unedited patch, not a mod file. Make sure it comes from a vanilla Diablo 2 install of either LOD 1.13 or 1.14.

6. Make sure "Diablo II LOD.txt" is selected under "additional listfile" and make sure the checkboxes are unchecked. Click "OK".

7. In the left panel, double-click on "patch_d2.mpq" to see the content (if not visible already)

8. Right-click on the "data" folder

9. Select "Extract" from the menu and click "OK". By default it should extract the contents in the "mpqediten32\work" directory

You will notice the "data" directory you just extracted has the same file structure as any "data" folder from a Diablo 2 -direct -txt mod.

Before you do anything, make sure the mod you downloaded is compatible with version 1.13 or 1.14. All -direct -txt mods compatible with version 1.13 are compatible with version 1.14 and vice versa.

I've seen someone say their "-direct -txt" mod is only compatible with 1.13c, this is false if the mod has no .dll files and is a "-direct -txt" mod (meaning everything is contained in one "data" folder).

Step 2. Merging the mod with the extracted patch 1.14 (or 1.13) files

1. Open both data folders. Make sure you know which side is the mod and which side is the extracted unedited patch.

Let's say I opened the mod "data" folder on the left side and the unedited patch "data" folder on the right.
You should see the different folders and files on both sides (for instance: "global", "local", etc)

2. Select all files and folders from the window on the left side and drag and drop them on the window on the right side.

3. A window opens saying something like "This destination already contains a folder named 'global'
Check the box "Do this for all current items" and click "Yes"

4. A window opens saying "There is already a file with the same name in this location"
Check the box "Do this for the next X conflicts"
Click "Move and replace" (the first option)

Step 3. Generating .bin files

This step is easy if you are familiar with how to run "-direct -txt" Diablo 2 mods.
This step is essentially the same as installing and playing a -direct -txt mod.

1. Make a shortcut of Diablo 2, add " -direct -txt" in the path.

2. Drag your new merged "data" folder we did at "Step 2." in your Diablo 2 directory

3. Start Diablo 2 with the shortcut

4. Enter a game to make sure it works

5. Exit Diablo 2

6. Open the data folder and look inside "data\global\excel\"
You should see a lot of .bin files. If not, search a tutorial on how to play "Diablo 2 -direct -txt" mods.

7. Put the data folder back where it was before so you don't get confused in the next step. For this tutorial we will put it in "mpqediten32\Work\"

Step 4. Creating the new MPQ Diablo 2 patch file for the mod

1. Go back to MPQeditor.exe (open it again if you closed the program)

2. Select "File" -> "New MPQ ..."

3. Enter a name, the mod title for instance

4. Click "Next >"

5. Click on the button to select "Build the MPQ archive from a file or directory"

6. Click on the "..." button and select a directory that is one step before your new merged data folder.

This is very important. For instance, in this tutorial we placed the "data" folder in the "MPQEditor\Work" directory, so we need to select the "Work" directory, not the "data" directory. Never select the "data" directory directly. You want to select a directory that only contains the "data" directory and nothing else.

7. Click "Next >"

8. A "Max. number of files in the MPQ" is automatically generated. Don't touch it and click "Next >"

9. Click "Finish"

10. If you selected your file right, in the left panel, you should be able to see "your_mod_name.mpq" (whatever title you gave it) and inside the folder you should see a "data" folder.

11. Exit MPQEditor

12. Remember where you saved the new patch file (if you didn't change the location it's probably in the "mpqediten32" directory)

13. Remove ".mpq" in the patch file name you created so that people using systems with hidden file extentions by default won't make any mistake when renaming the mod to install it on their computer. Windows will warn you but click "Yes" anyways.

Note: For maximum cross-platform compatibility, I recommend using .zip archives when uploading a mod. I've come across a Mac compatible mod that was in a .exe archive, that's not very Mac friendly...

Step 5. Making sure it works

1. Take the mod patch file you just created. Let's say we called it "mod_patch_file"

2. Go to your Diablo 2 directory

3. Make a backup of your "patch_d2.mpq" vanilla unedited file

4. Rename "mod_patch_file" to "patch_d2.mpq"

5. Put the mod patch file you just renamed in your Diablo 2 directory

5. Start "Diablo II.exe" and not a shorcut with "-direct -txt" in it

6. Try the mod

To try the mod on a Mac, it's the same patch replace thing you just did on Windows but the file name must be renamed to something different. See the list of patch file names below.

With this method, you should get the same mod experience on Mac and Windows given you are using the same Diablo 2 version on both computers. LAN games between Mac and Windows computers will also work given you use the same Diablo 2 LOD version on all computers.

Diablo 2 patch file names

Mac OS 10.10 to 10.14
Diablo II Patch

Mac OS 10.4 to 10.6 (Rosetta)
Diablo II Patch (Carbon)

Mac OS 9 (classic)
Diablo II Patch

Windows 98 to Windows 10

Post a comment
Sign in or join with:

Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.

Follow Profile
Diablo II: Lord of Destruction
Windows, Mac
Developer & Publisher
Blizzard Entertainment
Send Message
Release date
Game watch
Related Games
Related Groups
Blizzard Entertainment
Blizzard Entertainment Developer & Publisher