See Also:  topic
Return to Index

See Also:  console
Return to Index

If the user is using a different nickname than the bot normally knows her by, you can specify her "handle" (the nickname that the bot remembers).

See Also:  +host ,  -host ,  +user ,  -user
Return to Index

assoc <channel #> <name>
Creates a name for a channel. The name will propagate across your botnet (if you're hooked into one) and can be used instead of the channel # when changing chat channels (see chat). If you omit the channel # and name, it will just dump a list of the current named channels.

assoc <*channel #> <name>
Creates a name for a local channel. These channels are local to the bot itself.

assoc <[*]channel #>
Wipes out the name for a channel, if there was one.
Return to Index

See Also:  bans ,  -ban ,  stick ,  unstick
Return to Index

See Also:  bans ,  +ban ,  stick ,  unstick
Return to Index

       [ 5] *!*habib@*frys.com (perm)
            paulie: revolving check policy
            Created 15:10 

Sometimes there will be a ! or * right before the number. A ! means the ban is in the bot's permban list, but is not currently on the channel. A * marks a ban which is NOT in the permban list but IS on the channel.

bans all
If you use bans it will show you only the bans which are currently in action on the channel. If you use bans all it will show you every ban in memory (with 'perm-bans' on, these are identical).

bans <wildcard>
If you use bans <wildcard> it will list all the bans (active or not) that match against your wildcard. Consider it a bans all list matched against your wildcard.

The ban list may change according to which channel you're currently viewing in the console. Different bans may be active on different channels. If you specify a channel name, that channel will be used instead of your current console channel.

See Also:  -ban ,  +ban ,  console ,  stick ,  unstick ,   set ban-time
Return to Index

     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 

binds [type] all
Displays all the Tcl bindings of every type (or the specified type), including the bindings for built in commands such as:

     msg  -    op                   *msg:op 

bf none         Clears your boyfriend.
Return to Index

This command should ONLY be used in cases of complete frustration due to a lack compatable partners.... OR after the bars are closed on a weekend night.
Return to Index

See Also: +bot, +user, -user
Return to Index

         Bot Flags:

           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
   For Masters, if there is a comment, you will see it under "COMMENT:"

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

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

Use vbottree if you want to see know bot versions. See Also: bots, botinfo
Return to Index

See Also:  pending
Return to Index

See Also:  pwd
Return to Index

See Also: link ,   +bot
Return to Index

*** IMPORTANT ***
This erases ALL information about the channel, including channel settings and channel records for users -- EVERYTHING.

DO NOT use it to have the bot temporarily leave a channel. This command is for abandoning a channel (e.g. the channel will have to be redefined and all user flags for that channel will have to be redone.
Even if you don't have chanfile defined, it will still erase all the channel records for users on the next userfile save.

See Also: +chan , chansave , chanload , chanset , chaninfo
Return to Index

      chanmode     Which modes are enforced on the channel, both + and
                   - modes can be enforced
      idle-kick    Kick idle users (non +f's anyway) on the channel
                   after how many minutes (use 0, or no-idle-kick
                   to turn this off)

      clearbans    Clear all the channel bans when
                   the bot joins the channel?
      enforcebans  Kicks people who match channel bans?
      dynamicbans  Only activate bans on channel when they are needed
      userbans     Allow other users to place bans on the channl
      autoop       Automatically op users when they join the channel
      bitch        Only allow users with the +o flag
                   to be ops on the channel
      greet        Say a users info line when they join the channel
      protectops   Re-op a +o user who gets deopped?
      statuslog    Log the channel status every 5 minutes
      stopnethack  De-op anyone who enters the channel with server ops
      revenge      Take revenge on anyone who deops, kicks
                   or bans the bot or any valid user
      secret       Don't provide info about the channel over the botnet
      shared       Share user settings for this channel
                   (NOTE: this can only be set in the config file)
      autovoice    This causes the bot to also monitor channel
                   voice settings, using the +v/+q settings. 

      flood-chan   this defines the flood level for public chatter
                   & actions
      flood-ctcp   this defines the flood level for ctcp's to the
                   channel (include PING & VERSION), except for ACTION's
      flood-join   this defines the number of joins from a give
                   user@host that constituts a flood
      flood-kick   how many kicks in the given time are a flood
      flood-deop   deops in the given time 

The first line will look like:
    Channel #hiya, 8 members, 45 users, mode +tn:
This means that the bot is sitting on channel #hiya, where 8 other irc'ers are. There are 45 people that the bot knows by hostmask, and the channel mode is +tn. If the bot isn't on the channel it is supposed to be on, it will say "Desiring channel #hiya" instead. Next is a list of the users on the channel, with each entry looking like this:

                  NICKNAME  HANDLE    JOIN   IDLE  USER@HOST
                  @kantSF   kantSF    14:53 o  6m  josh@random.edu 

          n - bot owner                 o - can get ops (+o)
          m - bot master or owner       f - channel friend
          b - another bot               d - cannot get ops (+d)

See also:  status ,  whois
Return to Index

See Also: +chan , -chan
Return to Index

See Also: +chan , -chan
Return to Index

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.

chat <*channel# or name>

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' (bot master) flags. It is pointless to -n a permanant owner. You must remove the permanant owner in the config file. This command can no longer be used to change bot flags, they are a seprated entity, changeable with the .botattr command.

chinfo <user> [channel] none Erases a user's info line.

See Also:  +info
Return to Index

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

See Also:  chattr
Return to Index

See Also:  chattr
Return to Index

In such cases, create a user record for the account, and mark it +c, or "common access". Marking it as "common access" means that it shouldn't be used as a definitive address. When someone introduces themself to the bot (ie, by /msg'ing "hello")and matches as a +c user, they will be given a new user record which identifies them BY NICKNAME.

Obviously people with that kind of user record shouldn't be given much special access, as when they change nicknames the bot will identify them as someone else.
Return to Index

     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 connect/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

console <user> [channel] [modes]
Is used to set the console level of another user. This can even be used on users who normally would not be able to set their own console mode.
Return to Index

See Also:  mv
Return to Index

The headings of the table are:

     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)

     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 relay'd 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    

     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   use 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 agressively shared with    

See Also:  adduser,  +user ,  -user
Return to Index

See Also:  op ,  console
Return to Index

The description is restricted to 3 lines of 60 characters each, and is broken up between words. You can force a line break by putting a | in the comment.
Return to Index

dob none         Clears your date of birth. (woah, no more showing ID ;)
Return to Index

email none          Clears your email address with the bot.
Return to Index

See Also:  link ,  chattr ,  unlink
Return to Index

There is a limit to the number of transfers you can have going simultaneously, so if you go over this limit, the remainder of your file requests will be queued. As the first files finish transferring, the queued files will be sent.

See Also:  pending , cancel
Return to Index

gf none         Clears your girlfriend.
Return to Index

See Also:  unhide, lsa
Return to Index

See Also: +host
Return to Index

See Also:  -ignore ,  ignores
Return to Index

See Also:  +ignore ,  ignores
Return to Index

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

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

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

See Also:  +ignore ,  -ignore
Return to Index

info [channel] none removes your info line.
Return to Index

See Also:  console
Return to Index

irl none         Clears your real life name.
Return to Index

See Also:  kickban ,  console
Return to Index

See Also:  +ban ,  bans ,  stick
Return to Index

Example: ln Snowbot:/gifs/uglyman.gif ugly.gif

See Also:  share, unshare , get
Return to Index

See Also:  cd, pwd, get
Return to Index

See Also:  hide, share
Return to Index

        .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 

The default limit is 20, meaning that if more than 20 user records match your requirements, only the first 20 will be shown. You can change this limit by specifying one on the command line, though. If you include a limit, you may also include a starting place (the default is 1).

For example, to list the first 15 users who have hostmasks from clemson.edu: .match *clemson.edu 15

To get the next 10 (if there are more than 15), you ask to list numbers 16 thru 25: .match *clemson.edu 16 25
Return to Index

See Also:  rmdir
Return to Index

See Also:  cp
Return to Index

See Also: whom, notes
Return to Index

notes index gives a listing of all the notes stored up: who they are from, and when they were left.
notes read <# or ALL> lets you read some or all notes, according to a list of numbers and/or intervals separated by semicolon.
notes erase <# or ALL> erases notes after you are done with them.
Example: notes erase 2-4;8;16-

See Also:  note,  whom
Return to Index

See Also:  deop ,  console
Return to Index

See Also:  cancel
Return to Index

See Also:  cd
Return to Index

See Also:  save ,  reload,  restart
Return to Index

See Also: bots
Return to Index

See Also:  rehash ,   save
Return to Index

See Also:  bans ,  reset ,  console
Return to Index

See Also:  rehash ,  reload ,   save
Return to Index

See Also:  mkdir
Return to Index

See Also: reload ,   rehash
Return to Index

See Also:  Set Commands - Bot Configuration Variables
Return to Index

See Also:  unshare, lsa, ln
Return to Index

    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 second line, tell 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 pageful of info, showing every internal setting as specified in the config file. It should be self-explanatory to anyone who needs to use it.

See Also:  set,  channel,  debug
Return to Index

See Also:  bans,  +ban
Return to Index

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

See Also:  console
Return to Index

Trace result -> Valis:Stonewall:NoBoty:SomeBoty

See Also: bots, bottree
Return to Index

See Also:  hide, lsa
Return to Index

See Also:   link ,  bots ,   bottree
Return to Index

See Also:  share, lsa, ln
Return to Index

See Also:   bans ,  stick ,   -ban
Return to Index

url none         Clears your url address.
Return to Index

    A * next to the nickname means that user is an Owner.
          + means they're a Master.       @ means they're an Op.
          % means they are a Bot Master.
    

      HANDLE  The handle (nickname) of the user
      PASS    Yes if they has a password set
              No if they do not have a password set
      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 

     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  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
        (plus 26 user-defined flags, A-Z)    

     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)
        (plus 26 user-defined flags, A-Z)    

     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)    

    examples:
      set flood-msg 10        (10 msgs in 60 seconds is a flood)
      set flood-msg 5:15      (5 msgs in 15 seconds is a flood)
      set flood-msg 0         (turns off msg flood protection)
    

      %b   display bold
      %v   display inverse
      %_   display underline
      %f   display flashing via telnet, bold underline via irc
      %B   bot's nickname
      %V   current eggdrop version (ie, "eggdrop v1.3.19")
      %E   long form of %V (ie, "Eggdrop v1.3.19  (c)1997 Robey Pointer")
      %C   channels the bot is on
      %A   whatever is set in 'admin' (see 'set admin')
      %T   the current time (ie, "17:37")
      %N   the current user's nickname
      %U   the current operating system the bot is on
      %%   a percent sign ("%")

      %{+m}Only masters would see this.%{-}
      %{+1}Only people with user flag #1 see this.%{-}
      %{+b}This is only displayed to users doing a remote
           .motd from another bot.%{-}
      %{+|m}Only channel masters would see this.%{-} 

      %{cols=N}     Start splitting output into N columns
      %{cols=N/W}   Same, but use a screen width of W
      %{end}        End columnated or restricted (ie %{+m}) block
      %{centre}     Center the following text (70 columns) 

       set servers {  goblin.irc.com:6667
                      dragon.irc.org
                   }