Blizzhackers

This is my own little (shitty) resolution hack, similar to all the previous resolution hacks, but by no means completed. There is still much work to be done, and yet, so little time...

REV 04/08/12 @ 3:10 PM EST

This is assuming you are developing for Closed Battle.net. A lot of things can be simplified if you only plan to use this for Single Player/Open Battle.net.

The first order of business is something you will need to do on your own: develop a system to auto-inject your DLL before SetDisplayMode is called. After you solve this little dilemma, it's all smooth sailing. You might also consider developing a system for auto-injecting when the Diablo II window gains the focus, in case you Alt+Tab.

Below is a simple DLL injector, but does not include either of the systems I mentioned above. I don't feel like I need to explain this, because I am lazy, and there are tons of explanations out there already. Plus, I'm just no good at commenting my code.

D2LoadDll.cpp



Before the WinMain function, there is the user-defined function, SetDebugPrivilege, which enables/disables the Debug privilege. This will allow D2LoadDll to open the Diablo II (Game.exe) process handle. For a more detailed explanation, take a look at this article, on MSDN. This step is skipped a lot because most processes don't require the Debug privilege to open the process handle. You can avoid this by creating your own launcher.



Again, for a more detailed explanation, take a look at this thread, by Darawk, or type "Dll Injection" into Google. You need only change the second strcat parameter to that of your DLL name for this to function. Unfortunately, without the systems I mentioned earlier, you will be required to inject after every game, which is a very tedious task.



I'd like to mention some (less than) valuable tips for making your own resolution hack before throwing unexplained code at you. If you want to make a fully functional resolution hack (DD/D3D/Glide/Win), you will need to find the functions and pointers on your own. To do this is relatively simple. First, set the mode you want by running the Video Test or setting -w as a command line parameter. Next, go into a game, search for your current resolution width, change it, refine your search using the new resolution width, and repeat; Game Hacking 101. Finally, break on Write and viola. Some of what you will find might be in D2DDraw.dll/D2Direct3D.dll/D2Glide.dll/D2Gdi.dll, but the main components are located in D2gfx.dll/D2Win.dll/D2Client.dll. For example, display mode for D3D is in D2Direct3D.dll, but the resolution is in D2Client.dll.

D2Direct3D.dll



D2Client.dll



A little helper function I developed to get the correct base for the specified module: GetModuleBase will attempt to get the base using GetModuleHandle; however, if the module isn't loaded (D2Client.dll, for example), it's loaded into the process with LoadLibrary. This is assuming the specified module is in the Diablo II directory. The great thing about this is that you don't have to worry about when you can access certain functions or pointers.

D2res.cpp



Changing the display mode without using "detours" (Microsoft or otherwise) requires a vtable hook; do the hooking inside the DLL_PROCESS_ATTACH routine (or a thread therein). You must remember to unhook the vtable after SetDisplayMode is called, and before you return from the hook. Also, clean up any other changes to the client in the DLL_PROCESS_DETACH routine. The code in its current state will not work. You must develop a system to unload the DLL after the hook is executed. An incomplete exampled is embedded in the code.

D2res.cpp



The SetDisplayMode hook is where the display mode and resolution are changed. Don't forget to declare the D2Client_dll global somewhere (D2Client.h, perhaps). You will probably want to find a different time to change the resolution, and is probably the source of a small bug I'll mention later.

D2Direct3D.h



Unfortunately, the screen is glitched until you bring up an inventory (inventory/stash/cube/etc.; press I, twice, and problem solved). If you can fix this, good for you. Everything should be self-explanatory at this point. I probably forgot to mention some things, so when/if I remember, I'll append them to this post.

Source: http://www.fileswap.com/dl/ZdvDml00fL/D2res.zip.html
Example: viewtopic.php?f=166&t=488658

good work m8

inv x, y offsets are in d2client.dll somewhere :/

to be more precise, the lines for the current resolution mode get copied into a global cache (which doesn't get refreshed, you'll need to edit it directly) which then gets used, so modifying the compiled txt at runtime will have no effect

yup, you have to change it then change resolution mode

finding the resolution offsets are pretty easy you can just search for hex 800/600 in w/e decompiler you are using but you have to actually try to interpret the code to figure out where the inventory drawing code is and so on

a more "lame" solution would be to edit the dc6 file and make it so it aligns up with whereever your inventory is spawning now

Don't just talk about it; be about it.

I personally made my resolution mode by porting from v1.10f edits, posted by Dav92 from the Phrozenkeep.
The only annoying things is that he shows edited code, so to see the original code, you have to use something like D2SE, run a clean v1.10f copy, and then port the edits to your version (v1.13c in my case)

You can find the offsets sheet there: http://snej.d2maniacs.org/forum/index.php?topic=34744.0
It has pretty much everything needed for a high-resolution mod.

Good luck.

thats pretty nice

that guy spent super amounts of time doing that it seems like

he organized it really well

Yes, it,s pretty useful. But like I said, the only inconvenient is that it shows some modified data, so you have to run a 1.10 copy to see the original code, then find it on your version. But it's very useful yes.