mrhappyasthma / d2r-multibox

A helper utility to streamline launching of D2R multibox

D2R-Multibox

A helper utility to streamline launching of D2R multibox.

NOTE: This only works on Windows.

Background

In order to support multi-boxing (i.e. multiple instances of D2R running simultaneously), you need to kill the following \Sessions\3\BaseNamedObjects\DiabloII Check For Other Instances.

Many folks are doing this manually using tools like Process Explorer:

This script looks to automate that process, by iterating through all the processes and closing this handle.

Dependencies

Required installations:

• Python 3
• The following python modules:

python -m pip install pywin32
python -m pip install ctypes

Optional installations:

To make a fresh exe, also install pyinstaller:

python -m pip install pyinstaller

Internal Deps

• https://github.com/yihleego/pywinhandle

Run

Downloading the standalone EXE

You can download the latest release here: https://github.com/mrhappyasthma/D2R-Multibox/releases/tag/Latest

Running the script manually

To run the script, simply run:

python multibox_d2r.py

d2r-multibox's Issues

App crashes sometimes

The app crashes sometimes. I need to run the script for a while and try to repro to make the code more fault tolerant.

[Feature Request] Add logging

It would be great to get some better logs shown to the user.

[Feature Request] Add a 'stop' and 'start' feature.

This doesn't consume much processing power, but it could be nice to have a stop button in case someone wants to pause the process iteration logic to make it even more lightweight.

[Feature Request] Create an executable version that runs in the background

This script still has to be run manually every time you open a new D2R. Ideally this should be a background process that triggers whenever a new D2R is launched and automatically closes that file handle.

Then you can just have this run on startup and run in the background, and it will just auto-magically allow you to seamlessly launch multiple clients.

Occasionally the tool fails to close the handle

I'm not sure how to repro, but I've had a few instances where after running for a while and closing the game to jump between regions, the tool is running but doesn't find any handle.

However if I open Process Explorer, I see the D2R.exe and the handle and can still close it manually.

There must be some subtle bug in the logic.

One theory I had was that this may occur if you keep D2R running but exit out of the Battle.net application? Maybe in that instance my process iteration logic won't find it.