Setting up an Eggdrop (the short version)

SSH into your KIRE shell. Not telnet. Tcl and OpenSSL are already on the box. Current Eggdrop is the 1.9 / 1.10 tree from geteggdrop.com / ftp.eggheads.org. Git is an unstable snapshot — do not run that as your production bot.

If you want someone else to run it, order a managed eggdrop. Need a shell first? Shells.

Compile and install

wget https://geteggdrop.com -O eggdrop-latest.tar.gz
tar zxvf eggdrop-latest.tar.gz
cd eggdrop-1.*
./configure
make config
make
make install DEST=~/botdir
cd ~/botdir
cp eggdrop.conf botnick.conf

Edit botnick.conf. Remove both die lines. Set nick, owner, ident (set username), vhost (set vhost4 / set vhost6), listen port, and servers. Bind the IP you were given.

First start, then persist

First time only, create the userfile:

./eggdrop -m botnick.conf

It daemonizes. Later starts are ./eggdrop botnick.conf. Do not park the bot in screen or tmux — those are for irssi/weechat. Persist with autobotchk:

./scripts/autobotchk botnick.conf

That writes crontab. Details: botchk / autobotchk and first start.

AUP: max 2 IRC connections per shell to a given network.

Optional keyed channel in the conf (mode +k):

channel add #mychan {
  chanmode "+ntk thekey"
}
  • 2 Users Found This Useful
Was this answer helpful?

Related Articles

Getting the Eggdrop Source Code

Get current Eggdrop from the Eggheads project. That is geteggdrop.com or ftp.eggheads.org. The...

Detailed Installation Instructions (Manual Install Method)

SSH into the shell. Tcl and OpenSSL are already there. Current Eggdrop is 1.9 / 1.10 from...

How to configure your eggdrop bot

Work in the install dir (~/botdir). Copy the sample, do not edit eggdrop.conf in place: cp...

Editing the botchk file to automatically restart your bot

Eggdrop daemonizes. Screen/tmux are for irssi/weechat, not the bot. Persist with crontab via...

Starting your eggdrop bot for the first time

Conf edited, die gone, installed to ~/botdir. SSH in. Do not start this from screen/tmux. First...