When I opened the Diablo II.exe with File -> Open in OllyDbg, the base address is the usual 00400000, and Entry address is: 004014E3. I'm not a beginner, but not pro either.įirst I scanned the exe with PEiD to see if it was packed, and PEiD just said "Microsoft Visual C++ 6.0", which from some research means that it doesn't have any packing, it was just built with MSVC6. I've been working and digging around the Diablo II.exe for 1.09b for about 10 hours now, also learning more about reverse engineering along the way. So hopefully this post doesn't get locked or deleted.Īnyways, on to the content.
Onyx and other mods said in other posts that since Blizzard introduced the "no-cd patch" in 1.12+, that basically means that we can also make our own no-cd modifications for previous versions. In order to run a mod, Diablo II needs to be patched correctly, or the mod will most likely not start at all.I've been trying to make modifications to Diablo II.exe for 1.09b in order for it not to use the CD. Might work with Patch 1.11 as well, but it is recommended to run on 1.10. Below is an incomplete list of mods and what patches they work with. Many popular mods for Diablo II require different patch versions to run properly. This guide aims to explain how to do that. Many players however wish to have one or more mods installed at the same time, as well as a regular, or "vanilla", installation of Diablo II intact so that they can play on. This is because most mods change many of the already existing game files, and they are often made for different patch versions of Diablo II as well.
While installing one of these might often be simple enough, removing the same mod or installing a new mod often causes problems. There are many different Mods available for Diablo II.
0 kommentar(er)
