Free irc bot software for linux

IRCBotNET is a Botnet. It is a network of IRC bots that communicate with one another. They share a means of communication whereby all bots speak to one another and exchange information. They are useful for keeping and maintaining a channel by acting as a group of channel bots that work together with a common goal.

Say, for instance, you have one IRC bot keeping a channel and a netsplit occurs or the bot dies for some reason. Immediately the channel becomes chaotic and anarchic without an IRC bot keeping the peace. With a Botnet, even if an IRC bot dies, here still remains the rest of the bots on the Botnet to continue maintaining the channel and the loss of the one bot means nothing as the other bots do its exact same job.

BotNET is an extremely powerful IRC BOT and has many features.
BotNET doesnt necessarily have to run as a Botnet, it can run as a normal IRC bot and in fact does this by default. It has a massive collection of functions that can be seen in the BotNET man pages. When run as a Botnet, BotNET has supreme capabilities that have never been attempted before in Botnets. When a BotNET bot is run in Botnet mode, it connects to a BotNET Communication Stream Server (botserv) that is included in this package.

It uses this server to communicate with the other bots on the Botnet. The difference here is that not only can it do whatever any other Botnet can do, but it also uses this stream of communication with its added IRC Stand-alone bot functionality. For instance, if you add a user to the bot, immediately, all other bots connected to the database add this user to their local databases and a global-wide Botnet database is maintained. So you can use any one of the bots on the Botnets for anything that you so desire. This powerful feature makes BotNET very predominant over other Botnets.

RockBot is a fully functional multi-channel bot for IRC. It has hundreds of usefull commands for managing channels, amusing your friends, and protecting ownership. It is a good alternitive to an eggdrop type bot.
DCC model of rockbox is different like eggdrop. In RockBot YOU NEVER initiate a DCC chat with the bot. In all cases the bot will send you a DCC chat request when it needs one due to the type of data its returning. If you have trouble with DCCs it may be the bot cannotdetermine its true IP address on the machine. Try playing with "#define PPP" in config.h.
Enhancements:
- The data files and memory model were totally re-written. RockBot now uses a multiple-channel scheme for keeping track of users, and also allows one user to store multiple hostmasks under one "handle". There is also a "global" config that controls the default settings for channels and high level bot users. In order to diferentiate
- between global commands and local channel commands the following syntax has been implimented:
- (Note: This example assumes CMDCHAR is !)
- Sent to a channel -> !userlist = userlist of the channel typed in
- Sent to a channel -> !#mychannel userlist = userlist of #mychannel
- Sent to a channel -> !!userlist = global userlist
- ---
- Privmsg to bot -> #mychan userlist = userlist of #mychan
- Privmsg to bot -> !userlist = global userlist
- ---
- When you use JOIN a data file will be created to contain the new channels users, settings, topic etc. The LEAVE command parts the bot but does NOT remove the datafiles, however REMCHAN does.

nagircbot (Nagios IRC bot) announces the Nagios status on an IRC channel.
Type:
./nagircbot -h
for a list of options.
Enhancements:
- A switch for letting nagircbot use a password when entering a channel was added.
- Code which implements a keep alive was added.

IRC::Bot::Help is a module to dispatch help for IRC::Bot.

SYNOPSIS

use IRC::Bot::Help;
my $seen = IRC::Bot::Help->new();

# later on...

# User asks for help in DCC CHAT
sub on_dcc_chat {
my ( $kernel, $id, $who, $msg ) = @_[ KERNEL, ARG0, ARG1, ARG3 ];

my $nick = ( split /!/, $who )[0];

# Do Stuff...
if ( $msg =~ m/^.help/i ) {

my $topic = $help->ask_help(all);
$kernel->post( NICK, dcc_chat, $id, $topic );

}

}

Basically holds a list of help topics and dispatches them on demand.

NickBot is an IRC bot framework written in Perl. It is designed such that all of the user modules that do the actual data processing are located in an external file. Each module is run individually inside of Perls eval function to keep rouge modules from crashing the entire bot; plus this gives the user the ability to add/remove/change modules in the bot without restarting it every time.

NickBots main program consists of a large number of generic handlers. Each handler takes the information that the Net::IRC module gives it and either responds appropriately (like with a ping request), or it processes it into a generic format. This generic format then goes through a couple more steps to determine things like was the bot addressed, and what type of message came in. At that point, the collected data is passed off to the user modules.

The user modules are what really give NickBot its flexibility, the user can go into the modules file and make any number of modules to make the bot actually do something. Included in the distribution is a sample modules file that Ive created during development to test out the interface. The bot doesnt do anything spectacular out of the box, but you can implement your own functions.

CWBot is an IRC bot to provide online services in Morse usable with the CWirc client. It can broadcast world news in Morse and Hellschreiber, RAC ham news, act as a MorseMail to CWirc repeater, or send fortune cookies in Morse, over an IRC channel or throught DCC chat, with adjustable keying speed and Farnsworth spacing. The project is easily extendable with scripts or external programs to provide additional services in Morse.
Architecture of the bot
CWBot is really composed of two parts : the bot core (the "cwbot" program itself) and the external chat engines.
The bot core
The bot core is a very basic IRC bot that maintains a connection to an IRC server, stays on a channel and replies to "Hello" and "Help". It doesnt do anything else by itself. To interact with users, it relies on external programs (the chat engines) that handle the chatting itself.
The core uses 2 types of chat engines : the channel chat engine, which does the chatting on the IRC channel the bot is on, and the DCC CHAT engine, which chats with individual DCC CHAT requestors. It spawns one instance of the
channel chat engine, and as many instances of the DCC CHAT engine as there are DCC CHAT sessions open. The core handles the translation between IRC or DCC CHAT messages and the chat engines, and takes care of starting/stopping
them transparently.
The chat engines
The chat engines (channel chat engine or DCC CHAT engine) are external programs that read and write plain text messages throught their standard inputs and standard outputs. The channel chat engine is meant to be spawned once and run forever. Should it stop for whatever reason however, the bot core will try to respawn it. The DCC CHAT engine is spawned whenever a DCC CHAT connection opens, and either runs until it decides to stop, provoking the termination of the DCC CHAT session, or until the bot itself terminates the session and kills it. Since there can be more than one DCC CHAT engine running at any given time,
they must be careful not writing to the same files or sharing resouces without talking to each other, if they need to share things.
Enhancements:
- The parser in the news broadcast scripts has been corrected to process the BBCs XML newsfeed properly.

rbot is a ruby IRC bot. Think of him as a ruby bot framework with a highly modular design based around plugins. It is somekind of a infobot. See more RbotFeatures, or perhaps an ExampleSession.
Main features:
- Runtime configuration via irc chat
- User authentication and access levels for using different bot features
- Built in infobot-style keywords. See example session below.
- Support for underlying fact database (infobot fact files), which can be overridden or supplemented by runtime keyword controls
- Multi-language support - comes with english, dutch and german definitions so far - more translations welcome
- Powerful plugin architecture, comes with plugins for:
- DNS queries
- Babelfish translation
- Google searching
- Excuse generation
- Insult generation
- Karma
- Checking the weather
- Querying slashdot
- Doing Math
- Per-channel quote storage, searching and retrieval
- Reminders
- rot13 translation
- Check the spelling of a word
- Webserver Server: header examination
- RPG dice rolling
- larting people
- conversation stats
- more...
Enhancements:
- Many new and updated plugins, including one to poll RSS feeds.
- A first step towards a better auth system (total revamp due in 0.9.11).
- Improvements to network and server code, which should provide greater stability.
- A new message queueing mechanism with bit rate throttling.
- A new logging framework for debugging and tracing the activities of the bot.
- A new split-db registry system for better performance and transactional usage of bdb for resilience.
- More integration with Nickserv where available, including optional automatic ghost-killing.

Ofnibot is a reincarnation of Kevin Lenzos Infobot in minimalist form. Kevin Lenzos Infobot program (http://www.infobot.org/) is an awesome IRC bot that is used on many IRC channels around the world.

Unfortunately, Infobot has become somewhat large in its old age. Since I maintain a number of IRC channels that require an information bot, my goal was to create an Infobot-compatible bot from the ground up. This bot is fast, secure, and modern.

The core function of the Infobot is to store a knowledge base of "factoids" or facts about things. The knowledge base can then be accessed and updated using common English phrases.

Ofnibot (Ofni = Info spelled backwards) is meant to provide that same core functionality without the bloat of the Infobot code. Ofnibot uses the modern POE::Component::IRC module to interface with IRC and, more importantly, it uses commands and files that are fully compatible with the original Infobot. The entire program comes in at just over 300 lines of Perl.

Because Ofnibot was programmed from the ground up and does not use any of the Infobot code, I cannot guarantee it behaves exactly the same when responding to users. It does, however, provide an exact subset of Infobot commands and can use the exact same database files as the Infobot. It can easily work as a drop-in replacement.