Druid WW slvl 33+ Playerdrop and Drop Hack Fix
Diablo II LoD v1.09d Druid Drop Fix + D2HackIt/Drop 1.0 Crash Prevention
NOTE: STARTING WITH THE RELEASE OF V1.10 IN 2003, ALL THE DIABLO II BUGS THIS
PATCH WAS INTENDED TO WORK AROUND HAVE BEEN OFFICIALLY FIXED. THE
INFORMATION AND THE EXECUTABLES BELOW ARE KEPT HERE FOR HISTORICAL
PURPOSES ONLY, AND FOR THOSE WHO STILL PLAY V1.09.
This patch should fix the infamous Druid Drop / Werewolf lvl 33 bug, which has
claimed so many lives in Hardcore by now. The patch was tested and has proven
to work in Single Player/Open Battle.net already - and should work in Closed as
well, since the same .DLL is used. However, unpredictable outcomes are possible.
What this thing does is disable assertion failure trapping in D2Client.dll, thus
allowing the game to continue like nothing happened even if assert() has failed
in D2Client.dll. This can potentially result in invalid page fault crashes
("The program has performed an illegal operation and will be shut down") or
gameplay irregularities occuring. As well as I might have messed up something
which will cause a new glitch or crash - and claim your Hardcore character's
life as well. USE THIS THING AT YOUR OWN RISK - the best thing for you to do is
wait for the official Blizzard fix.
ADDED: As of 01/31/2002, people report that druid drop bug is still in place.
Also, because the executables were modified (hex edited), they did not work with
NT based systems (Not a valid Win32 application). This release has all affected
executables rebuilt with ProcDump, so they should now be all valid and working
in Windows NT/2000/XP
ADDED: As of 01/22/2002, Blizzard has reported that they implemented a
serverside fix for the druid drop. I haven't had a chance to test if it really
is gone from the realms or not - but if it is, the way they probably did it is
by blocking the erroneous info that causes the crash from being sent to clients,
thus preventing the crash. However, no clientside patch was released, so in the
single player, TCP/IP and Open Battle.net games (which are hosted on the game
maker's machine) the crash will still occur.
ADDED: Now this patch, in most cases, also fixes the crash caused by some client
using the D2HackIt/Drop 1.0 plugin, which also exploits an assertion failure, in
a different module. This exploit is much more evil than the druid drop bug, does
not require any skills to work, and allows one to drop every visible player
besides oneself. The way drop hack works is, its user will type something at the
console, then drop an item on the ground. The testing has shown that this part
of the patch is not 100% effective. Even when it does prevent a crash (which
happens in most cases) from thus dropped corrupted item, other crashes (with
different error messages) might still occur later on. Needless to say, IF YOU
PLAY HARDCORE AND SEE A PLAYER DROPPING A SUSPICIOUS LOW QUALITY ITEM,
ESPECIALLY AFTER A CONSIDERABLE PAUSE (required to type in the necessary
D2HackIt commands), or else wearing some apparently low quality weapon not
suited for his/her characher level, LEAVE THE GAME OR TAKE A PORTAL TO TOWN AT
BACK UP THE FILE CALLED D2Common.dll. THE PATCH OVERWRITES THIS FILE WITH AN
UPDATED VERSION. YOU WILL NEED TO RESTORE THE ORIGINAL FILE IN ORDER TO APPLY
THE OFFICIAL BLIZZARD PATCH WHEN IT COMES OUT.
Then unzip this archive into your Diablo II Lord of Destriction game folder, and
run DLOAD.EXE to launch the fixed version of the game. To run the fixed version
of the game, YOU HAVE TO RUN DLOAD.EXE - otherwise, if you just run the game by
using main menu/desktop shortcuts, only the (possible) D2HackIt/Drop plugin fix
will be in effect, but not the Druid Drop fix. If you don't want the Druid Drop
fix, just the Drop Hack fix, you may run the game as usual.
Full Readme/More Info
Druid Drop Fix Only