Skip to content
Battle.net (pre-2.0) chat bot written in Visual Basic 6
Visual Basic PHP Other
Find file
Latest commit 0f2956e May 3, 2016 @Davnit Davnit Sending SID_NOTIFYJOIN now leaves chat environment
The packet has similar behavior to SID_LEAVECHAT, but would only ever be
sent by scripts.

README.md

StealthBot

Battle.net (pre-2.0) chat bot written in Visual Basic 6

The non-development-focused wiki can be found here. Our forums can be found here.

If you'd like to explore or contribute to the project, I'd recommend reading the StealthBot Developer Guide. It's a little bit out of date, but it'll help you find your way around.

Debugging

You'll need Microsoft Visual Basic 6.0.

  1. Go into the project properties and set the compilation argument COMPILE_DEBUG = 1. If you don't do this, closing the program or encountering an error while debugging will cause the entire IDE to crash.

  2. While still in the project properties, set the command line to -ppath "C:\Path\To\Profile\" -addpath "C:\Path\To\Install\" with the quotes and ending slashes. This sets your profile and install location to some paths of your choosing.

    • Set the -ppath to a profile just for development (such as the path to %APPDATA%\StealthBot\DevProfile\, using the full path to your AppData StealthBot profiles location). If you don't do this, the development bot will expect files like commands.xml to be in your VB98 folder (the install directory for VB 6.0) instead of somewhere sane.

    • Set the -addpath to your install directory (such as C:\Program Files (x86)\StealthBot v2.7\). If you don't do this, the development bot will expect BNCSutil.dll, Warden.dll, and zlib1.dll in your VB98 folder also.

Visual Basic 6 Scroll Wheel Fix

The Visual Basic 6 IDE does not have built-in support for scrolling by using the mouse wheel. To fix this, you need to download and follow instructions from this KB article.

If you are on 64-bit Windows, you will need to use the 32-bit version of regsvr32, located in %systemroot%\SysWoW64\ (see this KB article).

Something went wrong with that request. Please try again.