D2BS does not try to exploit any bugs in the Diablo 2 code, the Battle.net protocol or game servers; it only simulates a real player.
As of this release, D2BS will be undergoing a new phase of development. We are discontinuing development on the 1.x line and focusing all of our attention on the 2.x line.
This means that 1.3.2 is probably the last release in the 1.x line, barring a major security hole. We will not be fixing bugs or otherwise doing any real work on the 1.x line. We will, however, accept patches to fix bugs and post releases with these bugs fixed, should anyone be so inclined.
We hope you understand and appreciate that we have put this off for far too long, and the 1.x line is good and dead.
We will be developing a whole new API for D2BS 2.0, and documenting it properly as we go, instead of trying to document it after the fact. If you want to be a part of this new api discussion, more details will be available soon.
Now, onto the reason you came here:
Visual Studio 2008 Runtime
(necessary for loading the D2BS runtime): here
.NET 3.5 Runtime
(necessary for loading the D2BS loader): here
Version 1.3.2 -
. Changed the internal unit finding code to use an internal list instead of room searching.
. Fixed sendDDE (multiple bugs, the least of which was an unused parameter...)
. Fixed me.cancel once again to detect scrolling text ("summoner bug")
. Fixed a rather large memory leak with Script::GetFilename (d'oh!)
. Removed some of the strictness checks for getBaseStat (got sick of trying to debug it).
. Fixed an issue where getScript could return a script that had no valid parameters, meaning
it would just error when you tried to use it.
. Added "param2" parameter to the "gameevent" event. You may now detect what kind of party
message you just got (hostile vs. invite vs. accept, etc.)