putserv <text>
sends text to the server, like 'dump' (intended for direct server commands); output is queued so that you won't flood yourself off the server
returns: nothingputhelp <text>
sends text to the server like 'putserv', but uses a different queue (intended for sending messages to channels or people)
returns: nothingdumpfile <nick> <filename>
dumps out a file from the help/text directory to a user on IRC via msg (one line per msg); the user has no flags, so the flag bindings won't work within the file.jump [server [port [password]]]
jumps to the server specified, or (if none is specified) the next server in the list
returns: nothing
botnick
current nickname the bot is using, ie 'Sisko' or 'Sisko0', etcbotname
current nick!user@host that the server sees, ie 'Sisko!ikaney@uk.defiant.org'server
current server the bot is using, ie 'irc.math.ufl.edu:6667'
MSGbind msg <flags> <command> <proc>used for /msg commands; the first word of the user's msg is the command, and everything else becomes the argument string
proc-name <nick> <user@host> <handle> <args>MSGM (stackable)
bind msgm <flags> <mask> <proc>matches the entire line of text from a /msg with the mask; this is more useful for binding Tcl procs to words or phrases spoken anywhere within a line of text
proc-name <nick> <user@host> <handle> <text>NOTC (stackable)
bind notc <flags> <mask> <proc>matches the entire line of text from a /notice with the mask; it is considered a breach of protocol to respond to a /notice on IRC, so this is intended for internal use (ie, logging, etc) only
proc-name <nick> <user@host> <handle> <text>CTCP
bind ctcp <flags> <keyword-mask> <proc>destination will be a nickname (the bot's nickname, obviously) or a channel name; keyword is the ctcp command and args may be empty; if the proc returns 0, the bot will attempt its own processing of the ctcp command
proc-name <nick> <user@host> <handle> <dest> <keyword> <args...>CTCR
bind ctcr <flags> <keyword-mask> <proc>just like ctcp, but this is triggered for a ctcp-reply (ie, ctcp embedded in a notice instead of a privmsg)
proc-name <nick> <user@host> <handle> <dest> <keyword> <args...>RAW (stackable)
bind raw <flags> <keyword-mask> <proc>previous versions of eggdrop required a special compile option to enable this binding, but it's now standard; the mask is checked against the keyword (either a numeric like "368" or a keyword like "PRIVMSG"); from will be the server name or the source user (depending on the keyword); flags are ignored; the order of the arguments is identical to the order that the IRC server sends to the bot -- the pre-processing only splits it apart enough to determine the keyword; if the proc returns 1, eggdrop will not process the line any further (THIS COULD CAUSE YOUR BOT TO BEHAVE ODDLY IN SOME CASES)
proc-name <from> <keyword> <args...>FLUD (stackable)
bind flud <flags> <type> <proc>any floods detected through the flood control settings (like 'flood-ctcp') are sent here before processing; if the proc returns 1, no further action is taken on the flood; if the proc returns 0, the bot will do its normal "punishment" for the flood; the flood type is "pub", "msg", "join", or "ctcp" (and can be masked to "*" for the bind); flags is ignored
proc-name <nick> <user@host> <handle> <type> <channel>WALL (stackable)
bind wall <flags> <mask> <proc>when the bot receives a wallops, it invokes this binding; flags is ignored; the mask is checked against the text of the wallops msg
proc-name <nick> <msg>