Add variable names to nthread (#161)
Also inline some parameters that were just copied to local variables.
|1 year ago|
|.travis||1 year ago|
|3rdParty||1 year ago|
|DiabloUI||1 year ago|
|Source||1 year ago|
|Support||1 year ago|
|.editorconfig||1 year ago|
|.gitignore||1 year ago|
|.travis.yml||1 year ago|
|Diablo.dsp||1 year ago|
|Diablo.dsw||1 year ago|
|Diablo.ico||1 year ago|
|Diablo.rc||1 year ago|
|Diablo.sln||1 year ago|
|Diablo.vcxproj||1 year ago|
|Diablo.vcxproj.filters||1 year ago|
|LICENSE||1 year ago|
|Makefile||1 year ago|
|MakefileVC||1 year ago|
|README.md||1 year ago|
|appveyor.yml||1 year ago|
|defs.h||1 year ago|
|enums.h||1 year ago|
|resource.h||1 year ago|
|structs.h||1 year ago|
|types.h||1 year ago|
Diablo devolved - magic behind the 1996 computer game
Reverse engineered by GalaXyHaXz in 2018
While most titles from Blizzard receive years of love and support, Diablo stayed in the shadows. Abandoned in favor of a sequel, it remained full of bugs and unfinished potential. The game was last patched in 2001 before being discontinued altogether, a problem I wanted to fix. I played Diablo extensively as a teenager, but as time passed it became difficult to run the game on newer hardware. The lack of many improvements found in the sequel also kept it from aging well. At first the game appeared to be a lost cause, but thankfully a little oversight in 1997 made it not so.
With Diablo’s development team moving on the source code was given to Synergistic Software to handle the expansion. Less known however is that it was also given to Climax Studios to create a PlayStation port. Now Sony has long been known for letting things slide; especially in Japan. Anything from leaking prototypes to full source code and Diablo was no exception. Symbolic information was accidentally left on the Japanese port. Normally used for debugging, a symbol file contains a map of everything generated during compile time. This includes file names, functions, structures, variables, and more! To top it all off a special build is hidden on the PC release in
DIABDAT.MPQ -> D1221A.MPQ -> DIABLO.EXE! This build contains debug tools and assert strings further giving away code information.
After months of piecing these mistakes together, Devilution was born. I present to you a reconstructed form of Diablo’s original source code! Once more shall the heroes of Sanctuary return to the depths below!
Having the source code makes Diablo much easier to update and maintain. For years mod-makers had to rely on tedious code editing and memory injection. A few even went further and reversed most or all of the game. The problem is that they rarely shared their work. Usually being a one-person job, they move on with their lives due to the amount of time required or lack of interest. This brings us back to square one having to do countless hours of work all over again. Devilution aims to fix this by finally making the source code open to the community.
In order to ensure that everything is preserved, Devilution keeps everything as it was originally designed. This goes as far as bugs and badly written code in the original game. With that it serves as a base for developers to work with making it much easier than before to update, fix, and port the game to other platforms.
As a side goal Devilution tries to document the unused and cut content from the final game. Development of Diablo was rushed near the end--many ideas were scrapped and multiplayer was quickly hacked in. By examining the source, we can see various quirks of planned development.
Diablo was developed on Windows 95 using Visual C++ 4.20 and later 5.10 and 6 for newer patches. Devilution is optimized for the same tools originally used but is also compatible with modern setups.
Release, and then
If you aim to build a binary as close as possible to the original one you will also need Visual C++ 5 with Service Pack 3, since the original binary as linked with the older linker from that. Sadly, you cannot use the old linker right out of VC6, so you’ll need to link manually or via the
MakefileVC in the project root.
Release, and then
Make sure to disable Data Execution Prevention.
Storm.dll uses dynamic compilation to improve rendering performance but fails to mark the resulting memory page as executable, leading to a protection fault when trying to draw.
You will also need the following dependencies installed if you are using Visual Studio 2017. Make sure to enable these when installing (or modify your installation):
make MINGW32=1for MinGW32 or
makefor MinGW64. Optionally add
debugto build with debug features.
Once compiled, the Devilution binary will serve as a replacement for
Diablo.exe. The following files from the original game patched to 1.09(b) need to be present:
COPYPROT was defined when compiling, the Diablo CD will also be required.
Additionally, Strange Bytes’ DirectDraw patch is recommended to help fix compatibility issues and run the game in windowed mode.
Here are some screenshots of a few things I tinkered around with, to demonstrate the relative ease of improving the game:
Wow, does this mean I can download and play Diablo for free now?
No, you’ll need access to the data from the original game. Blizzard has discontinued Diablo, but there’s plenty of used copies floating around. (I’m still using an original 1996-disc in 2018 without problems)
Cool, so I fired your mod up, but there’s no 1080p or new features?
Devilution aims to keep the original code unaltered, for documentation purposes.
So will you ever add cross-platform support or new features in the future?
Yes! However, this will be a side project based on Devilution. I have yet to announce the project.
When and what can I expect from the upcoming project?
Honestly I have no idea. More than 1,200 hours went into creating Devilution, and I have other things going on right now. Maybe in 6-12 months? The goal is to create a native Linux port, convert to OpenGL, modernize the UI, etc. you get the drill. There has to be some surprises. ;)
Ok, so I’m playing Devilution now and all the sudden it crashed. NOW WHAT??
Open an issue and provide as much information as possible (OS version, etc.) including any crash logs.
I thought I’d fix the crash myself, but after looking at the code its a disaster. Do you speak v2-34-v8?
That is the result of decompiled code. Whenever a program is compiled, much of the source is optimized and stripped away, so it’s nearly impossible to decompile it back. Have patience. Everything will be cleaned up eventually. :)
Will you be reverse engineering Diablo II next? Ooooh please!
Absolutely not. Diablo II would require far more work and is still supported by Blizzard. Setting that aside, there are rumors that the game will be remastered which takes the point out of it.
Are you interested in working for me? I have this game I want you to reverse…
Sorry, but no. This project is time consuming enough as it is, and it’s just a hobby.
I think that’s about all, but is Devilution even legal?
That’s a tricky question. Under the DMCA, reverse-engineering has exceptions for the purpose of documentation and interoperability. Devilution provides the necessary documentation needed to achieve the latter. However, it falls into an entirely gray area. The real question is whether or not Blizzard deems it necessary to take action.
This software is being released to the Public Domain. No assets of Diablo are being provided. You must own a copy of Diablo and have access to the assets beforehand in order to use this software.
Battle.net® - Copyright © 1996 Blizzard Entertainment, Inc. All rights reserved. Battle.net and Blizzard Entertainment are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.
Diablo® - Copyright © 1996 Blizzard Entertainment, Inc. All rights reserved. Diablo and Blizzard Entertainment are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.
This software is in no way associated with or endorsed by Blizzard Entertainment®.