NickServ

There are several ways you can automatically authenticate your bot to NickServ

Config File Authentication

At the bottom of your config file, you'll see a section that looks like this:

# This is a Tcl script to be run immediately after connecting to a server. If
# you want to authenticate Eggdrop with NickServ, uncomment and edit the middle
# line below.
bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
  global botnick
  putquick "MODE $botnick +i-ws"
#  putserv "PRIVMSG NickServ :identify <password>"
}

Locate "# putserv "PRIVMSG NickServ :identify <password>""; insert your password and uncomment the line (remove the # at the beginning of the line) and restart Eggdrop. The next time it joins a server, it will authenticate with NickServ via a message command.

SASL Authentication

For additional protection, some Eggdrop users want the host of their Eggdrop to be hidden at all times, to include that small portion of time between joining a server and authenticating with NickServ. This is where SASL authentication comes in to play. SASL is a mechanism that allows Eggdrop (or anyone) to authenticate BEFORE joining an IRC server, so that the Eggdrop will join already authenticated (and host-hidden). For this method, you're probably best off reading the official Eggdrop SASL docs , it is explained thoroughly there.

Manual Authentication

From the partyline, you can use the .msg command to send a message to NickServ. For example, '.msg NickServ identify mypassword' would message the identify command to NickServ.