ot|o

-|-

-|-

m|m

t|-

m|-

   Command bindings:
     TYPE FLGS COMMAND              HITS BINDING (TCL)
     msg  -|-  rose                    0 msg_rose
     msg  -|-  go                      0 msg_go
     dcc  m|-  bind                    0 cmd_bind
     pub  -|-  gross                   0 pub_gross

The fields should be self-explanatory, except for HITS, which records the number of times that binding has been called. If not, go read the file 'tcl-commands.doc' for help on the Tcl bind command. Note that the built-in commands are now shown. You may also specify a type of binding to show (i.e., .binds msg) or you can specify a wild card match (i.e., .binds *seen*) if you want to narrow the field a bit. The wild card matches will match against the TYPE, COMMAND and BINDING fields.

t|-

t|-

t|-

t|-

Set Fred1 +share and -hub.

   .botattr Fred1 +s-h

Whether or not you change any flags, it will show you the bot's attributes afterwards. To get a list of the flags possible, do .help whois.

Note: This command is NOT used to replace .chattr, it modifies botflags such as +s, +h, +a, +u... bot specific flags only. Also note that you can't use this command on bots which are directly linked to your bot at the current moment.

t|-

-|-

   Bots: cEvin, ruthie, Killa1

There is no indication of which bots are directly connected to this one. Use .who or .bottree for that information.

t|-

t|-

-|-

Some channels may have assigned names if the assoc module is loaded. For those, you can specify the channel by name instead of number if you wish.

.chat off removes you from any channel at all. You can still use normal bot commands and see the console, but you can't talk to anyone except via .note.

.chat on returns you to the party line (channel 0) if you were elsewhere.

m|m

   .chattr Lamer +pf

Or to remove Denali from the global op list:

   .chattr Denali -o

You may also do any combination of the above:

   .chattr Fred1 -m+xj-o

You can also change the flags for Usagi on a specific channel by supplying the channel after the attributes:

   .chattr Usagi -m+dk-o #blah

Changing global and channel specific flags within the same command line is now possible! Example:

   .chattr Bill f|o #lamer (global +f, +o #lamer)

Whether or not you change any flags, it will show you the user's attributes afterwards.

To get a list of the flags possible, do .help whois.

Notes:
- Only the owner may add or remove the 'n' (owner), 'm' (master) and 't' (botnet master) flags.
- It is pointless to -n a permanent owner. You must remove the permanent owner in the config file.
- This command can no longer be used to change bot flags, they are a separated entity, changeable with the .botattr command.

t|-

   .chnick gavroche jamie

t|-

Note: In previous versions, setting a password to "nopass" would clear a user's password - with encrypted passwords, this no longer works!

m|-

ot|o

   m  display private msgs/ctcps to the bot
   p  display public talk and ctcps on the channel
   k  display kicks/bans/mode changes on the channel
   j  display joins/parts/nick changes/signoffs/etc on the channel
   b  display bot links/unlinks/userfile-sharing
   s  display server messages and connects/disconnects
   w  display msgs between IRCops (wallops)

Channel master only:
   c  display user commands (dcc and msg)
   o  display other bot notices [HIGHLY RECOMMENDED]

Master only:
   x  display file transfers and file-area commands
   d  display debug messages that only coders would care about

Owner only:
   r  display all raw text from the server (if enabled)
   v  display raw text SENT to the server (if enabled)
-- There are also 8 user-defined console modes '1' through '8' --

The mode can also be a modifier like '+p' or '-jk' or '+mp-b'. If you omit the channel and modes, it will show your current console channel and setting.

t|-

   SOCK  the socket of this connection (always unique)
   ADDR  the IP-number of the host the connection is to, if applicable
   PORT  the port number being used for communication
   NICK  the nickname of the user or bot, if it's a user or bot
   HOST  sometimes, the hostname corresponding to the IP address
   TYPE  the type of dcc connection (see below)

The types of connection currently possible are as follows (but more are being added literally all the time):

   chat  user in dcc-chat command mode
   pass  user entering dcc chat (being asked for her password)
   send  raw data connection: user sending a file
   get   raw data connection: sending a file to a user
   getp  pending get (waiting for the user to acknowledge)
   lstn  telnet listening port (in place of a hostname, it will show the proc to call, or mask of acceptable nicks)
   t-in  incoming telnet user (being asked for his nickname)
   file  user in dcc-chat file area
   bot   bot linked in (aka botnet connection)
   bot*  pending bot link (waiting for acknowledgement)
   rela  user in relay connection to another bot
   >rly  bot being relayed to (one for each "rela")
   conn  pending telnet connection (chat, relay, bot-link, etc)
   new   new user via telnet, entering a handle
   newp  new user via telnet, entering a password

In addition, 'chat' and 'bot' have flags listed for each connection. Capital letters mean the flag is on, and lower case letters mean the flag is off. For 'chat', the flags are:

   C  in file area, but allowed to return to party line
   P  party line access only (no +o access)
   T  telnet connection (instead of dcc chat)
   E  echo is on
   P  user is paging

For 'bot', the flags are:

   P  ping sent, waiting for reply
   U  user-file sharing is active
   C  this bot initiated the connection
   O  user-file offered, waiting for reply
   S  in the process of sending the user-file
   G  in the process of getting the user-file
   W  warned this bot to stop hubbing
   L  leafed bot (not allowed to hub)
   I  bot is currently in the 'linking' stage
   A  bot is being aggressively shared with

For 'chat' users, the party-line channel is also listed.

m|-

n|-

-|-

-|-

-|-

mt|m

-|-

m|-

m|-

m|-

   [ 1] *!onaji@* (perm)
        Xerxes: spamming me
        Started 18:38

This kind of ignore can only be stopped by using .-ignore. Xerxes is the one who added it, and his comment is "spamming me". He added it at about 18:38 today. A temporary ignore looks like this:

   [ 2] *!*@shellx.best.com (expires at 19:59)
        MyBot: msg/notice flood
        Started 18:59

That means the ignore was made automatically by the bot at 18:59, because someone flooded it. It can be removed with .-ignore, or it will expire an hour after it started (this is set in 'ignore-time').

If you use .ignores <wildcard> it will list all the ignores that match against your wildcard.

n|-

n|-

t|-

   .link newbot

then your bot must have a record for the new bot (see .+bot). You can either set a password on each end or they will negotiate one the first time they link. If you use the form

   .link somebot newbot

then the request will be sent to "somebot" for it to link to "newbot".

n|-

n|-

n|-

n|-

ot|o

<+/-><global>[&/|<channel>[&/|<bot>]]

Specifying & as the separator will cause AND style matching, | will cause OR style matching. Channel flags are matched against the specified channel (or your console channel), and bot is matched against the separate bot flags. Some examples:

   .match +o        will match any GLOBAL +o's
   .match -o&+o     will match anyone without a global +o AND with a channel +o on your console channel
   .match +f|+f     will match anyone with a global +f or a channel +f on your console channel
   .match |f #fred  will match anyone with +f on channel #fred

   .match *clemson.edu 15

To get the next 10 (if there are more than 15), you ask to list numbers 16 through 25:

   .match *clemson.edu 16 25

-|-

m|-

n|-

-|-

-|-

-|-

-|-

-|-

-|-

m|-

n|-

n|-

t|-

m|m

m|-

m|m

n|-

n|-

.simul dweeb .quit

Makes it just as if "dweeb" typed ".quit". This command will not work unless Eggdrop has simul enabled in the config file. Please use this command ethically.

m|m

   I am Snowbot, running eggdrop v1.1.1:  400 users (mem: 42k)
   Running on BSDI 2.5
   Admin: Robey <robey@wc130.residence.gatech.edu>
   #turtle   :  2 members, enforcing "+tn-mlk"  (greet, bitch)
   #gloom    :  3 members, enforcing "+tn-i"  (greet)
   Server minnie.cc.utexas.edu:6667
   Online for 4 days, 06:18  (background)  CPU 14:18  cache hit 55.3%

The first line tells you the bot's name, what version of eggdrop it's running, the number of users the bot has records of, and the amount of memory being used.

The second line tells you what operating system the bot is running under.

The third line, if present, is the contents of your 'admin' line in the config file.

Next is a line for each of the channels your bot is currently monitoring. For each channel, it lists the number of people on the channel ("members"), what channel modes it's trying to enforce, and which options are set for that channel.

If your bot is sharing user files with anyone, and is currently either transmitting or receiving the userfile from a bot, it will say so here, and tell how many users have been received so far, or how many more users need to be transmitted.

The next few lines show the current server, and if the helpbot is in use, its nickname and current server. To prevent server flooding, both the bot and its helpbot use queues to store replies to queries from users. If either queue has a significant amount of information in it, this status display will show how full (%) the queue is.

The next line tells you how long the bot has been online, and whether it is operating in the background or foreground. If it's in the foreground, it will tell you whether it's in terminal mode or channel display mode. Terminal mode makes the local console simulate a dcc chat connection, and channel display mode displays a .status and .channel output every few seconds. It will also give you an estimate of the amount of CPU time (minutes and seconds) the bot has used so far, and how well the cache is working (the cache is an attempt to keep the CPU time down, and anything over 50% or so is just great).

If you do .status all you will see another page of info, showing almost every internal setting as specified in the config file. It should be self-explanatory to anyone who needs to use it.

-|-

   b  remove all boldface codes
   c  remove all colour codes
   r  remove all reverse video codes
   u  remove all underline codes
   a  remove all ansi codes
   g  remove all ctrl-g (bell) codes

The mode can also be a modifier like '+c' or '-bu' or '+ru-c'. If you omit modes, it will show your current setting.

-|-

n|-

-|-

   Trace result -> Valis:Stonewall:NoBoty:SomeBoty

It's a list of the bots between you and the destination bot. It should also return the time in seconds it took for the trace to occur.

t|-

n|-

m|m

m|-

m|-

t|-

-|-

   *Robey telnet: nowhere.com

Owners will also see the user's dcc idx.

The next section is bots directly linked to this one:

   -> MagField (14 Oct 01:16) eggdrop v1.0j

(btw, if you're still using 1.0j, you need to upgrade ;)

The arrow indicates who initiated the connection - the right arrow means this bot connected to MagField. A left arrow means they connected to us. A '+' next to the arrow indicates that the bot is sharing userfiles with us. the connection time (14 Oct 01:16) and bot version are also shown. Nowadays it may also show the network the bot resides on. Owners will also see the bots dcc idx.

The final section is a list of users on this bot who are not on your channel (this section may be omitted if everyone is on the same channel as you). If you specify a bot's name, as in .who valis, the who request will be sent to that bot, as long as that bot is on the botnet. Masters may also see "(con)" after a user's entry. This shows that user's console modes (see the help for .console).

In the final section (users that aren't on this channel), masters will see the actual channel other users are on. Also, people in the file system will be listed (as being in channel "files") - a '+' next to the nickname here means the user has access to return to the party line.

ot|o

   HANDLE       the handle (nickname) of the user
   PASS         "yes" if she has a password set, "no" if not
   NOTES        number of notes stored waiting for the user
   FLAGS        the list of flags for this user (see below)
   LAST         the time or date that the user was last on the channel

The valid flags under FLAGS are:

   o  global op (bot will op this user on any channel)
   m  master (user is a bot master)
   n  owner (user is the bot owner)
   t  botnet master (user is a botnet master)
   x  xfer (user has file-area access)
   j  janitor (user is a file-area master)
   p  party-line (user has party-line access)
   c  common (user record is a common-access site) [see .help common]
   u  unshared (not sent to other share-bots)
   b  bot (user is another bot)
   d  global deop (user cannot get ops)
   k  global auto-kick (user kicked & banned automatically)
   f  global friend (user is not punished for doing bad things)
   v  global voice (user get +v automatically on +autovoice channels)
   a  global auto-op (always op this user on join)
   h  high-light flag, user sees highlighting in text output
   w  wasop-test (needs wasop test for +stopnethack procedure)
   g  give auto-voice (works as +a but for voice instead)
   (plus 26 user-defined flags, A-Z)

Each channel that the user has joined will have a specific record for it, with the channel-specific flags and possibly an info line. The channel-specific flags are:

   m  master (user is a master for the channel)
   n  owner (user is an owner for the channel)
   o  op (bot will give this user chanop)
   d  deop (bot will not allow this user to become a chanop)
   f  friend (user is not punished for doing bad things)
   k  kick (user is auto-kicked)
   v  voice (user gets +v automatically on +autovoice channels)
   q  quiet (user never gets +v on +autovoice channels)
   a  auto-op (always op this user on join)
   w  wasop-test (needs wasop test for +stopnethack procedure)
   g  give auto-voice (works as +a but for voice instead)
   (plus 26 user-defined flags, A-Z)

Hostmasks for the user are displayed on the following lines. If the user entry is for a bot, there will be a line below which says "ADDRESS:" and gives the bot's telnet address. Some user entries may have "EMAIL:" and "INFO:" entries too. There may be additional information displayed depending on the modules loaded.

For bots, there are additional flags seen under the "BOTATTR:" entry. These include:

   s  share (bot is sharing user records, aggressively)
   p  share (bot is sharing user records, passively)
   g  global share (share all channels)
   h  hub (bot is auto-linked at highest priority)
   a  alternate (bot is auto-linked if no hub bots can be linked)
   l  leaf (bot is not allowed to link in other bots)
   r  reject (bot will not be allowed on the net)
   i  isolate (isolate the party line across a botlink)
   (plus 10 user-defined flags, 0-9)

Bots may also have +s (share) settings for individual channels. If there is a comment, masters will see it under "COMMENT:".

-|-

If the user is away, the away message will be shown. Likewise, if they are idle, the idle time will be displayed.

If you are on a different channel than the party line (channel 0), then this will show the people on every bot who are on your current channel. You can also optionally give the "channel" option to list who is on a particular channel.