Eggdrop Bot Configuration Guide by Joey.
Created on February 9th, 2000.
Last updated on September 19th, 2003.
An Eggdrop Bot is basically a robot that sits on IRC and carries out commands either set by you or activated by a "trigger". They can give OPs to people, enforce bans and run hundreds of different scripts.
In the past IRC servers did not have Channel services like Chanserv (or X on Undernet) which now protect users from channel takeovers and provide them with Operator status etc. Since these additions to the IRC networks an Eggdrop bot has become pretty useless for in a protection type manner. However they are still very cool for setting up different types of services like Quizes and FAQ databases etc.
You can download the latest version of Eggdrop from http://www.eggheads.org/downloads/. At the time of this update the current release is 1.6.15
Please note that you do not want to be root when you install/run an
Eggdrop bot. Do this as your regular user or create a seperate user
for the Eggdrop to run as. I will base this guide on having the bot in
/home/user. With that said, once you download it and place the file in
/home/user, untar it by running:
tar -zxvf eggdrop1.4.2.tar.gz
That will create a directory called eggdrop-1.6.15, enter this directory
and type:
./configure
It will then check to see if you have everything installed that is
required to run an Eggdrop Bot, such as TCL. Hopefully you won't get any
errors. Now it's time to actually create the bot. Run the following
commands:
make
make install
The previous commands should take a couple of minutes to complete, depending on the speed of your system. Once it is done, your eggdrop will be installed into /home/user/eggdrop.
Now comes the hard part for most, which is actually configuring the bot. There will be one file that you will have to edit, it is called eggdrop.conf.dist. This file has a lot of comments to guide you through it but I will still go over some of them. So starting from the top, let's begin.
#! /path/to/eggdrop # ^- set that to the directory eggdrop is in ie "#! /users/lamest/egg/eggdrop"
You need to change this to #! /home/user/eggdrop/eggdrop
# what IRC network are you on? this is just info to share with others on # your botnet, for human curiosity only. set network "I.didnt.edit.my.config.file.net"
If you're on dalnet, then set the network type to "dalnet" etc.
# in 'eggdrop.log' put private msgs/ctcps, commands, misc info, and # errors from any channel: logfile mco * "eggdrop.log" # in 'lame.log' put joins, parts, kicks, bans, and mode changes from #lamest: logfile jk #lamest "lamest.log"
Here you need to change #lamest to whatever channel your bot is going to be on. You can also rename "lamest.log" to "channelname.log"
# if compiled with owner, the following user(s) will ALWAYS have the # owner (+n) flag (You really should change this default) set owner "MrLame, MrsLame"
Make sure you change this and set it to your nickname on IRC.
# You MUST remove this line for this config file to work. This has been # added to prevent you from starting up a bot that is not fully configured. # Bots that have not been fully configured may join the wrong IRC network, # the wrong channels, or generally do things that you do not want. Please # make sure that you have double-checked the settings you want. # There's also a similar line lower down, just to make sure you're reading :) die "Please edit your config file."
Make sure you comment or remove that die line or your bot wont start.
# the server list -- the bot will start at the first server listed, and cycle
# through them whenever it's disconnected
# (please note: you need to change these servers to YOUR network's servers)
set servers {
you.need.to.change.this:6667
}
You need to change this to the irc servers that your bot will be using. Make sure to check the MOTD on these servers to be sure they allow bots. You can list as many servers as you want here, each on a different line.
That is pretty much it for the configuration file. To start up the bot you will have to run eggdrop -m eggdrop.conf.dist. It should load up without any errors but if there are errors, normally the error messages are pretty distinct and you shouldn't have a problem figuring out how to fix them. After your bot has loaded up, to start it next time you wont have to use the -m flag. Just eggdrop eggdrop.conf.dist will work, or you can rename eggdrop.conf.dist to your botnick and chmod 755 to it and you will be able to start up the bot simply by running the conf file.
Once it gets online, /msg botnick hello to introduce yourself to it. Then run /msg botnick pass pick_a_password_now to set a password. Now you should be able to dcc chat it and get into its "party line". Once in the partyline, type .help to take a look at what you can do. Also /msg botnick help will give you some guidance.
Now that you have the eggdrop up and running, be sure to check out http://www.eggheads.org and browse their scripts section. Theres tons of different things you can configure the bot to do.
Having trouble? Got questions? Require further assistance? If so please feel free to visit our Help Forums and ask the experts!