StormBot

From BotHouse MediaWiki

StormBot was originally created in 1997 by Xone, CyberMac, and later Domino of chatnet.org in order to ensure ability to properly manage channels with an easy-to-use interface. This allowed channel owners to add and remove users without having to know the cryptic commands of most channel protection systems as well as channel/nickname services. StormBot has been around many years and encompassed a large user base. Its major revision, even in use today, was version 3.2 which allowed users and bot administrators to provide all their commands from a public setting. This revolutionized eggdrop bot administration as users no longer had to rely on DCC access to administer their bots.

New revisions and updates to the script can be found at http://www.stormbot.net or by joining #bothouse on irc://chat.bothouse.net and typing "!SB5"

StormBot has been in constant development, not many users know about the newer versions nor the ease-of-updates the StormBot creators have incorporated. While the constant development of the script and the upgrades it requires drives users away from using the script, BotHouse has been diligent in creating methods to allow users the ease of updating without any user intervention. They have allowed users to connect to their botnet and receive updates dynamically as they're distributed.

The script provides an easy to use interface and its success even duplicated by some mIRC scripts in an attempt to capitalize on its success. StormBot, while being an advanced user's script also provides the novice user with the ability to administer their bot with no more than a novice level of bot management knowledge and the intricacies of inner workings.

While its competitors have been unable to keep up, StormBot has matured in its development and even provided easy-to-report bugs in the script. If a user should (unlikely) run into a bug, the script will automatically provide the information the developers require in order to rectify the issue. As well, developers are working constantly to make the script more robust and evenly accessible to all users on all networks.