Blizzhackers

Current version 1.2 Release

So, the old one was VB, this one is autoit, seems like I'm taking a step backwards! It works pretty nicely though, I made it for my use and some friends to use, releasing it to the public now, closed source because it's pretty messy.

Download:
http://www.speedyshare.com/files/226117 ... tapult.zip

D2Catapult loads multiple Diablo II windows, logs in to the game, and selects char. It supports Sandboxie, D2Multi, D2Loader, as well as sockscap.

Tested using 8 windows, 4 proxied, 4 not, using SocksCap and Sandboxie, worked like a charm every time on my 2.66Ghz Single Core CPU w/ 2 GB RAM.

Don't show sandboxie indicator in the window title must be selected in each sandbox's configuration. For your sanity's sake, you may also want to disable immediate recovery, else you'll get endless popups from Sandboxie.

Instructions:

Unzip and place in any folder you wish.

Configure launcher.ini

No quotes are used in any of the configuration entries.

Editing the Launcher.ini

[Global]
This setting is for how many total windows you want to load up:
Windows=8
1 to use Sandboxie, 0 not to use sandboxie:
Sandboxie=1
1 to use D2Multi, 0 not to use D2Multi:
D2Multi=0
1 to use D2Loader, 0 not to use D2Loader:
D2Loader=0
The location of D2Loader's .exe:
D2LoaderLoc=C:\Program Files\Diablo II\Diablo II.exe
The location of Sandboxie's .exe:
SandLoc=C:\Program Files\Sandboxie\Start.exe
The location of SocksCap's .exe:
SocksCap=C:\Program Files\SocksCapV2\sc32.exe
1 to run Dclone Hunter after windows are loaded, 0 if not:
UseDCHunter=0
The location of Dclone Hunter's .exe:
DCHunterLoc=C:\Documents and Settings\Owner\Desktop\Dclone Hunter\Dclone Hunter Starter.exe
1 to Show ToolTips at the top left of your screen so you know what's going on, 0 to disable Tooltips:
ToolTips=1
How many times to try selecting a char before moving on to the next window, anything between 10 and 50 is good, don't go below 10 though. This setting is here to help you keep the app working even through lag.
Retry=10





[Delays]
LoadWait: How long to wait in seconds for a window to be fully loaded:
LoadWait=4
ClickWait: How long to wait in seconds between the different login steps (Click Account box, type account name, etc):
ClickWait=1
PostWait: How long to wait in seconds after logging in to startup the next window:
PostWait=2
LoginWait: How long to wait in seconds after clicking the login button.
LoginWait=2

[Window1]
Which MPQ File to use - D2LOADER ONLY:
MPQ=timex40
Account Name:
Account=account01
Account Password:
Password=password
Which Charslot to use:
CharSlot=1

1 to use a Proxy, 0 to not:
UseProxy=0
Full IP Address of your SOCKS4 proxy:
ProxyIP=127.0.0.1
Port of your SOCKS4 Proxy:
ProxyPort=8080
UserID or Password to your SOCKS4 Proxy:
ProxyPass=awesome
Which sandbox, by name, to run this D2 window in:
SandBox=Diablo
Full Path to Diablo II.exe:
Box=C:\Program Files\DiabloII1\Diablo II.exe
Working DIR for this (same dir as above without DIablo II.exe:
BoxWorkDir=C:\Program Files\DiabloII1\

[Window2]
MPQ=timex41
Account=account02
Password=password
CharSlot=1
UseProxy=0
ProxyIP=127.0.0.1
ProxyPort=8080
ProxyPass=awesome
SandBox=Diablo2
Box=C:\Program Files\DiabloII2\Diablo II.exe
BoxWorkDir=C:\Program Files\DiabloII2\

New Launcher options, for use if a window fails to get to the lobby for whatever reason, you can use a different/backup copy of D2 to run it instead.

UseBackup=1 - 0 To turn off.
BackUpLimit=5 - How many times the Backup Plan can be used

It'll pull the proxy info, window name, etc, from the Window configuration of the window that failed to enter the lobby.

[BackUp1]
Box=C:\Program Files\DiabloII30\Diablo II.exe
BoxWorkDir=C:\Program Files\DiabloII30\

[BackUp2]
Box=C:\Program Files\DiabloII30\Diablo II.exe
BoxWorkDir=C:\Program Files\DiabloII31\

[BackUp3]
Box=C:\Program Files\DiabloII30\Diablo II.exe
BoxWorkDir=C:\Program Files\DiabloII32\

[BackUp4]
Box=C:\Program Files\DiabloII30\Diablo II.exe
BoxWorkDir=C:\Program Files\DiabloII33\

[BackUp5]
Box=C:\Program Files\DiabloII30\Diablo II.exe
BoxWorkDir=C:\Program Files\DiabloII34\

FAQ/Common Issues:

Q: I changed Sockscap settings, but my Diablo II windows are still being loaded on the old SocksCap settings.
A: Sandboxie sometimes will cache registry values and not care about what you are changing, to get rid of the registry settings cached by Sandboxie, open up the Sanboxie control, Right-Click the Sandbox you're having trouble with, and click Explore Contents. Once the folder pops up with the contents of your Sandbox, delete the file named RegHive, this file stores all the cached registry information.

Q: When my first window loads, the launcher just sits there, my window title doesn't change and nothing happens!
A: When your windows load, they have to be named Diablo II, make sure you have Sandboxie set to not show the Sandboxie Indicator, which usually looks like this: [#], you can do this by checking the box that says "Don't show sandboxie indicator.." in your sandbox settings, also make sure that the box that says Show sandbox name in the window title is NOT checked.

Q: Half of my windows are at char select, while the other half are in the lobby, what gives?
A: Increase the value for Retry under Global settings of your launcher.ini.

Q: An error pops up Titled "SocksCap Launcher Error" saying the System Cannot find the file specified?
A: You'll need to go into the registry for this one, run regedit and go here:
HKEY_CURRENT_USER\Software\Permeo Technologies\SocksCap32\AppProfiles\1001
Then find SocksCap profile that is used by that registry entry and name it Diablo II.

Q: Sandboxie Start is giving me an error saying "Could not invoke program", "The system cannot find the File specified"?
A: Check then line in launcher.ini under Global settings called "SocksCap=", make sure you have the full path to and including sc32.exe.

Setting up SocksCap from a fresh install:
Create 2 Profiles, one called whatever you want, and the 2nd called Diablo II, point the second at any Diablo II.exe.
Make sure your proxy settings are set to Socks4, the other information is unimportant.

Setting up SocksCap that's already installed/configured:
You'll need to go into the registry for this one, run regedit and go here:
HKEY_CURRENT_USER\Software\Permeo Technologies\SocksCap32\AppProfiles\1001
Then find SocksCap profile that is used by that registry entry and name it Diablo II.

Setting up SandBoxie:
For each of your sandboxes, in sandbox settings, you'll need to check the box that says "Don't show sandboxie indicator in the window title", and make sure that the box that says "Show sandbox name in window title" is UNCHECKED. When Diablo II loads initially, the windows MUST be named Diablo II.

Optionally, you may want to uncheck "Enable Immediate Recovery" for each of your sandboxes, this'll prevent you from getting a ton of popups from Sandboxie when you load windows.


That's about it, it's not very complex to run.

Report any bugs and I'll fixem when I can.