Welcome to the official site for the unofficial hacked versions of D2Loader v1.10! Here you will find information and safe downloads for the hacked D2Loader which is designed to work with Diablo 2 patch v1.12 and future revisions.
2008-06-18
D2Loader for 1.12 patch.
NOTE: Old plugins will not work, they need to be updated for 1.12 by the plugin author; D2Loader only loads the DLL file. Unless they are updated by the author plugins will not work.
2006-12-29
Fix -ns crash on act change (at last).
2006-11-14
Improve compatibility with some anti virus or anti spyware software. Also new contact email, .
2005-11-11
Added -altcolor option for changing monster hp bar color for better accessibility.
2005-10-04
New build. Fixed a bug with -sleepy (thanks to SV for report).
2005-10-02
Looking for translators for the website, especially into Chinese as almost half the hits are from .cn domains. If you can help, please email . I've also changed the dates on the site to ISO 8601.
2005-09-22
New build released. D2Lang patches updated, few small fixes, new command line options available (see the .txt file for detailed changes).
Please see the included .txt file inside the .zip for installation instructions, detailed version history, command line options, etc.
Q. I get 'STORM.DLL not found' error.
A. You need to install the .exe like the instructions tell you to. Put the .exe into your Diablo II directory and run it from there, don't try and run it from the .zip or anywhere else or it simply won't work. If using a shortcut, make sure the 'working directory' is your Diablo II directory.
Q. I get a message saying 'Can't load Diablo 2 MPQ files'.
A. You need to either put your Diablo 2 CD in the drive or make sure you do a full install of both classic and expansion and ALSO copy the d2xvideo.mpq, d2xmusic.mpq and d2xtalk.mpq to your Diablo II directory.
Q. I get 'Hey guys we got a big error here :('.
A. First, make sure you aren't trying to use any old v1.10 plugins or hacks. This error comes from the very top level of the structured exception handler, meaning ANYTHING that causes a crash in Diablo II (even D2 itself) will show this message. As such, it's impossible to really figure out what causes it. Usually though you will find a crash log (D2XXXXXXX.txt) in your Diablo II directory, go to the end of the file and copy all the debug information and maybe post it on some forum to see if anyone is able to make sense of it. A few things are known to cause this message, including use of -ns command line option, using -resXXX in fullscreen mode, using -locale with missing locale files.
Q. Will I get banned for using D2Loader / is D2Loader detectable?
A. Ask Blizzard. So far to my knowledge, no one has ever been banned for using D2Loader by itself. However, it is a 3rd party modification and thus against the EULA to use. D2Loader is trivial for Blizzard to detect with their new hack detection system in v1.11 (Warden), so they could very easily detect and ban anyone using it. It's really up to them, I have no idea. You take a risk as with any 3rd party hacks. I assume no responsibility for any lost accounts, cdkeys, etc.
Q. I have another question / feature suggestion / bug report not listed here. Who do I contact?
A. E-Mail . Note that ANY requests for support or getting help using D2Loader will be ignored - please use the BlizzSector forums for support questions. If you're reporting a bug, please include your crash dump (D2XXXXXX.txt).
Q. When I log on to Battle.Net it says 'Unable to identify application version'. What's wrong?
A. You are running D2Loader from outside your Diablo II directory. Check that the D2Loader .exe is in your Diablo II directory and that your shortcut to Diablo II has the correct 'Start In' directory. If you continue to get this error, your Game.exe is likely damaged or the wrong version.
