View Single Post
Old 06-30-2007, 07:20 PM   #2 (permalink)
Chris
[F-Zero Fanatic]
 
Chris's Avatar
 
Join Date: May 2003
Location: Phantom Road
Age: 22
Posts: 15,863
The Really "Fun' part: Installing Mousepad.

As you all know, Mousepad is an old maphack that has spanned all the way back from the days of 1.08. But there will be some tinkering that needs to be done before you can operate it.

First, let's install the maphack.
  1. Download the Mousepad zip from here. I am using 4.7j, which is the latest version it has that will operate.
  2. Create a folder called maphack in your Zy-el directory, and extract all the files from the zip folder to it.
  3. Run the maphack when you run Diablo II.

Your outcome should be this:


Oh wait, now we have two problems. One, we are using D2Loader, which conflicts with the coding of Mousepad. And even if you do the below with your shortcut, you will get an error message saying "Undetected Game Version". when you try to install it. And even if you get away with it, the moment you load up your character screen, the game crashes. The reason is there is a feature that comes with PlugY that conflicts with it, and if you remove the Plugy.dll, your mod will fail to start up.

Time to remedy D2Loader situation!
  1. Create a shortcut to D2Loader 1.09 and place it on your desktop
  2. Right click on the shortcut and go to "Properties"
  3. Modify the shortcut's target by doing this:

Basically, you have modified the way your shortcut works with the following parameters:
-w - Runs Diablo II in Window mode (optional)
-title "Diablo II" - Changes the title of the window to Diablo II. If you didn't do this, it will replace it with the Date and Time you activated this window. Which is the reason why Mousepad conflicts.
-skiptobnet - As the name implies, auto-connects to the Realm you have selected. If its D2 Maniacs, it will connect to it. Saves two clicks .
-nonotify - A great option for Hardcore players. If Diablo II should crash, there won't be a notification window where you have to click OK and it closes Diablo II. D2Loader will still do one, but it only appears when the program shuts off. Why is this helpful? Cause before the log is set and the game is closed, the game is still running. IF you are surrounded, you could die while you are doing the process. This could kill your character unknowingly. Although these errors are rare for well-maintained PCs, it doesnt hurt to be safe.

Now, time to remedy the PluGy problem. Just be careful with this file, it can be diastrous.
  1. Download the Plugy.ini file from this page.
  2. Move the Plugy.ini to the Zy-el directory, where Plugy.dll is.
  3. Open Plugy.ini in Notepad and go to this line:
    Code:
    [INTERFACE]
    ActiveNewStatsInterface=1
    SelectMainPageOnOpenning=1
  4. Change the ActiveNewStats Interface from 1 to 0. This is the reason why Mousepad is conflicting with Plugy. This feature is found in your Stats interface (C). There will be 2 arrows that will cycle through your total bonuses. And it isn't really necessary cause you can really just check your own equipment the old fashion way.

This is a sample of what I was talking about:


And now that you have solved the bugs, you should be able to run D2Loader and Maphack together. If you want help tinkering the Mousepad, a tutorial will be explained later. And if you still get a message about D2Loader checking for a CD when you already copiued the files from the CD, just hit Cancel or Ignore and it should bypass it and run Zy-el. To remedy this, install D2Loader of the proper version to teh original directory for D2.
__________________


The Purpose of DTD is not to show off how good you are.
But to do an insane flying move and landing at 3000 km/h.
Hopefully, without crashing into something or flying off in the process.


Kurisu - Zy-el Sorceress - Level 46 of 10000

My Personal Blog Page - Updated every Friday
Join the Phantasy Star Online sensation - ChrisH36

Last edited by Chris; 07-06-2008 at 05:28 PM.
Chris is offline