[cvslog] Module eggdrop1.6: Change committed

cvslog cvs at tsss.org
Thu Dec 13 23:44:02 CST 2001


CVSROOT    : /usr/local/cvsroot
Module     : eggdrop1.6
Commit time: 2001-12-14 05:43:21 UTC
Commited by: Jeff Fisher <guppy at techmonkeys.org>

Modified files:
     eggdrop.advanced.conf eggdrop.complete.conf eggdrop.simple.conf
     doc/UPDATES1.6 doc/settings/core.settings doc/settings/mod.assoc
     doc/settings/mod.blowfish doc/settings/mod.compress
     doc/settings/mod.console doc/settings/mod.ctcp
     doc/settings/mod.dns doc/settings/mod.filesys
     doc/settings/mod.irc doc/settings/mod.notes doc/settings/mod.seen
     doc/settings/mod.server doc/settings/mod.share
     doc/settings/mod.transfer doc/settings/mod.uptime
     doc/settings/mod.wire doc/settings/mod.woobie doc/settings/tricks
     src/patch.h

Log message:

applied both configdocs (rev2) and doc_settings (rev4) .. lets go over the files now and look for more problems related to spelling and confusing lines of text

---------------------- diff included ----------------------
Index: eggdrop1.6/doc/UPDATES1.6
diff -u eggdrop1.6/doc/UPDATES1.6:1.246 eggdrop1.6/doc/UPDATES1.6:1.247
--- eggdrop1.6/doc/UPDATES1.6:1.246	Thu Dec 13 23:38:12 2001
+++ eggdrop1.6/doc/UPDATES1.6	Thu Dec 13 23:43:10 2001
@@ -1,10 +1,11 @@
-$Id: UPDATES1.6,v 1.246 2001/12/14 05:38:12 guppy Exp $
+$Id: UPDATES1.6,v 1.247 2001/12/14 05:43:10 guppy Exp $
 
 Changes in eggdrop: (since v1.6.0)
 ----------------------------------
 
 1.6.8
 Found by  Fixed by  What...
+          Wcc       major cleanup of config files and related documents
           BarkerJr  updated doc/MODULES a bit
           Wcc       show the user port as users instead of telnet and the bot port
                     as a bot port instead of a relay port
Index: eggdrop1.6/doc/settings/core.settings
diff -u eggdrop1.6/doc/settings/core.settings:1.8 eggdrop1.6/doc/settings/core.settings:1.9
--- eggdrop1.6/doc/settings/core.settings:1.8	Sun Nov 11 14:24:46 2001
+++ eggdrop1.6/doc/settings/core.settings	Thu Dec 13 23:43:11 2001
@@ -1,19 +1,17 @@
---------------------------------------------
-|Eggdrop Config File Settings Documentation|
---------------------------------------------
-
-This file describes syntax and all settings for your eggdrop configuration
-file. Please note, that you don't need to set all those var to make your
-bot work properly.
+##### EGGDROP CORE SETTINGS #####
 
+This file describes the syntax and all the settings of your eggdrop
+configuration file. Please note that you don't need to set all of these
+variables to make your bot work properly.
 
 
 ##### EGGDROP CORE SETTINGS #####
 
 
-The first line in eggdrop configuration file should contain a full qualified
-path to eggdrop executable. It has to be implemented in the way the example
-shows to make the config file work as a shell script
+The first line in an eggdrop configuration file should contain
+a fully qualified path to your eggdrop executable. It has to be
+implemented in the way the example shows to make the config file
+work as a shell script.
 
 Example:
 
@@ -22,85 +20,84 @@
 
 ##### BASIC STUFF #####
 
-You can change the basic eggdrop appearance and behaviour in this section.
+You can change the basic eggdrop appearance and behavior in this section.
 
 
 set username "lamest"
-    This setting defines the username the bot uses.
-    Note that his setting is working only if no ident daemon is running on
-    the machine your bot is on
+    This setting defines the username the bot uses on irc. This setting has 
+    no effect if an ident daemon is running on your bot's machine.
 
 
 set admin "Lamer <email: lamer at lamest.lame.org>"
     This setting defines which contact person should be shown in .status,
-    /msg help and other places. You really should include this info.
+    /msg help, and other places. You really should include this information.
 
 
 set network "SomeIrcNetwork"
-    This setting is used only for info to share with others on your botnet
+    This setting is used only for info to share with others on your botnet.
+    Set this to the irc network your bot is connected to.
 
 
 set timezone "EST"
     This setting defines the timezone is your bot in. It's used for internal
-    routines as well as for logfile timestamping or scripting purposes.
+    routines as well as for logfile timestamping and scripting purposes.
     The timezone string specifies the name of the timezone and must be three
     or more alphabetic characters.
-    ex. Central European Time(UTC+1) could be "CET"
+    E.x. Central European Time(UTC+1) should be "CET".
 
 
 set offset "5"
-    offset specifies the time value to be added to the local time to get
-    Coordinated Universal Time (UTC aka GMT). The offset is positive if the
-    local timezone is west of the Prime Meridian and negative if it is east.
-    The value(hours) must be between 0 and 24
-    ex. if the timezone is UTC+1 the offset is -1
+    The offset setting specifies the time value to be added to the local time
+    to get Coordinated Universal Time (UTC aka GMT). The offset is positive if
+    the local timezone is west of the Prime Meridian and negative if it is east.
+    The value (in hours) must be between -23 and 23.
+    E.x. If the timezone is UTC+1, the offset is -1.
 
 
 set env(TZ) "$timezone $offset" (disabled by default)
-    If you don't want to use the timezone setting for scripting purpose only
-    but instead everywhere possible then use this setting.
+    If you don't want to use the timezone setting for scripting purposes only,
+    but instead everywhere possible, then use this setting.
 
 
 addlang "english"
-    if you want to have your eggdrop messages displayed in another language
-    change the below command to match your preferences. An alternative would
-    be to set the environment variable EGG_LANG to that value.
+    If you want to have your eggdrop messages displayed in another language,
+    change this command to match your preferences. An alternative would be
+    to set the environment variable EGG_LANG to that value.
 
 
 
 ##### LOG FILES #####
 
-Eggdrop is capable of logging various stuff, from channel chatter to
-commands people use on the bot or file transfers.
+Eggdrop is capable of logging various things, from channel chatter to
+partyline commands and file transfers.
 
-Logfiles are kept for 24 hours normally. Afterwards they'll be renamed
-to "(logfilename).yesterday". After 48 hours they'll get overwritten by the
-logfile of the next day.
+Logfiles are normally kept for 24 hours. Afterwards, they will be renamed
+to "(logfilename).yesterday". After 48 hours, they will be overwritten by
+the logfile of the next day.
 
 
 set max-logs 5
-    maximum number of logfiles to allow - this can be increased if needed
-    (don't decrease this)
+    This is the maximum number of logfiles allowed. This setting can be 
+    increased; however, don't decrease it.
 
 
 set max-logsize 0
-    maximum size of your logfiles, set this to 0 to disable.
-    This value is in KiloBytes, so '550' would mean cycle logs when it
-    reaches the size of 550 KiloBytes.
-    Note that this only works if you have keep-all-logs 0 (OFF)
+    This is the maximum size of your logfiles. Set it to 0 to disable.
+    This value is in kilobytes, so '550' would mean cycle logs when it
+    reaches the size of 550 kilobytes.
+    Note that this only works if you have keep-all-logs set to 0 (OFF).
 
 
 set quick-logs 0
-    Defaultly, eggdrop writes every 5 minutes its logfiles to disk. You can
-    change this behaviour by turning this setting to 1 (ON). Eggdrop will
-    write and check the logfiles for size every minute.
-    Note that this setting might increase the cpu usage of your bot (on the
-    other hand it will decrease your mem usage)
-
+    This could be good if you have had a problem with logfiles filling
+    your quota/hard disk or if you log +p and publish it to the web, and
+    you need more up-to-date info.
+    Note that this setting might increase the CPU usage of your bot (on
+    the other hand it will decrease your RAM usage).
 
 logfile <logflags> <channel> "logs/logfile"
-    This setting actually tells the bot what should be logged from where in
-    which file. (duh!).
+    This setting tells the bot what should be logged, from where, and to
+    which file.
 
     The most common log file flags are:
       m  private msgs/ctcps to the bot
@@ -114,8 +111,9 @@
       r  (if use-console-r enabled) EVERYTHING sent to the bot by the server
       o  other: misc info, errors -- IMPORTANT STUFF
       w  wallops: msgs between IRCops (be sure to set the bot +w in init-server)
+
     There are others, but you probably shouldn't log them, it'd be
-    rather unethical ;). There are also five user-defined levels ('1'..'5') which
+    rather unethical ;). There are also eight user-defined levels (1-8) which
     are used by Tcl scripts.
 
     Each logfile belongs to a certain channel. Events of type 'k', 'j', and 'p'
@@ -128,10 +126,11 @@
     logfile mco * "logs/eggdrop.log"
     logfile jpk #lamest "logs/lamest.log"
 
-    In 'eggdrop.log' put private msgs/ctcps, commands, misc info, and errors
-    from any channel
-    In 'lame.log' put joins, parts, kicks, bans, public chatter and mode changes
-    from #lamest
+    In 'eggdrop.log', put private msgs/ctcps, commands, misc info, and errors
+    from any channel.
+
+    In 'lamest.log', log all joins, parts, kicks, bans, public chatter, and
+    mode changes from #lamest.
 
 
 set log-time 1
@@ -140,23 +139,23 @@
 
 
 set keep-all-logs 0
-    If you want to keep your logfiles forever turn this setting on. All
-    logfiles will get suffix ".[day, 2 digits][month, 3 letters][year, 4 digits]"
-    Note that your quota might get full by this, so check your logfiles often and
-    download them.
+    If you want to keep your logfiles forever, turn this setting on. All
+    logfiles will get suffix ".[day, 2 digits][month, 3 letters][year, 4 digits]".
+    Note that your quota/hard-disk might be filled by this, so check your logfiles 
+    often and download them.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set switch-logfiles-at 300
-    You can specify in this setting, when eggdrop should switch the logfiles
-    and started fresh.
-    You have to use military time in here. 300 is default and describes 00:00.
+    You can specifiy when eggdrop should switch logfiles and start fresh. 
+    You must use military time for this setting. 300 is default and 
+    describes 00:00.
     Note that a leading 0 will make Tcl think this is an octal value,
     something you probably don't want.
 
 
 set quiet-save 0
-    Those nasty "Writing user file..." and "Writing channel file ..." messages
+    Those nasty "Writing user file..." and "Writing channel file..." messages
     wont be logged anymore if this option is enabled.
     Valid settings are 0 for OFF and 1 ON.
 
@@ -164,7 +163,7 @@
 set logfile-suffix ".%d%b%Y"
     If keep-all-logs is 1, this setting will define the suffix of the logfiles.
     The default will result in a suffix like "04May2000". "%Y%m%d" will produce
-    the often used yyyymmdd format. Read the strtime manpages for more options.
+    the often used yyyymmdd format. Read the strftime manpages for more options.
     NOTE: On systems which don't support strftime, the default format will
     be used _always_.
 
@@ -172,40 +171,41 @@
 ##### FILES AND DIRECTORIES #####
 
 set userfile "LamestBot.user"
-    Specify here how your userfile should be called
+    Specify here the filename your userfile should be saved as.
 
 set pidfile "pid.LamestBot"
-    Specify here what filename eggdrop will save its pid under
+    Specify here the filename eggdrop will save its pid to.
 
 set sort-users 0
-    If  you want your userfile to be sorted on save, turn this feature on.
-    Note that this takes a bit more cpu
+     If you want your userfile to be sorted upon saving, enable this setting. 
+     This causes the bot to use bit more CPU when saving the userfile.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set help-path "help/"
     Specify here where eggdrop should look for help files.
-    Don't modify this setting until you know what you're doing!
+    Don't modify this setting unless you know what you're doing!
 
+set text-path "text/"
+     Specify here where eggdrop should look for text files. This is
+     used for certain Tcl and DCC commands.
 
 set temp-path "/tmp"
-    Set here a place to store temporarily files
+    Set here a place to store temporary files.
 
 
 set motd "text/motd"
-    The MOTD (motto of the day) is displayed when people dcc chat or telnet
-    to the bot.
-    Look into doc/settings.motd or type '.help set motd' in DCC CHAT or
-    telnet connection for options.
+    The MOTD (Message Of The day) is displayed when people dcc chat or telnet
+    to the bot. Look at doc/settings.motd or type '.help set motd' in DCC 
+    CHAT or telnet connection for options.
 
 
 set telnet-banner "text/banner"
-    This banner will be displayed on telnet connections
+    This banner will be displayed on telnet connections.
 
 
 set userfile-perm 0600
-    Specifies what permissions the user, channel and notes (if notes module
-    is loaded) files should be set to.
+    This specifies what permissions the user, channel, and notes files should be set to.
     The octal values are the same as for the chmod system command.
 
     To remind you:
@@ -221,28 +221,34 @@
 
 
 set mod-path "modules/"
-    This path specifies the path were eggdrop should look for its modules
+    This path specifies the path were eggdrop should look for its modules.
+    If you run the bot from the compilation directory, you will want to set
+    this to "". If you use 'make install' (like all good kiddies do ;), this
+    is a fine default. Otherwise, use your head :).
 
 
 
 ##### BOTNET, DCC AND NETWORK #####
 
-Settings in this section should be unimportant fur you until you deal
+Settings in this section should be unimportant for you until you deal
 with botnets (multiple eggdrops connected together to maximize efficiency).
 You should read doc/BOTNET before modifying these settings.
 
 
 set botnet-nick "LlamaBot" (disabled by default)
     If you want to use a different nickname on the botnet than you use on
-    IRC (i.e. if you're in an un-trusted botnet) set it here.
+    IRC (i.e. if you're on an un-trusted botnet), un-comment this line
+    and set it to the nick you would like to use.
 
 
 listen <port> <mode>
     The listen command opens a telnet port by which you or other bots can
     interact with the eggdrop by telneting in.
 
-    Valid ports are (as long as you aren't root) >1024.
-    Valid modes are 'all', 'bots' and 'users'. You can assign special ports
+    Valid ports are typically anything between 1025 and 65535 assuming the 
+    port is not already in use.
+
+    Valid modes are 'all', 'bots', and 'users'. You can assign special ports
     for users and bots, or one for all.
 
     Examples:
@@ -254,14 +260,14 @@
 
     listen 3333 all
 
-    There are more options for the listen command in doc/tcl-commands.doc
+    There are more options for the listen command in doc/tcl-commands.doc.
     Note, if you are running more than one bot on the same machine, you will
-    want to space the telnet ports at LEAST 5 apart... 10 is even better
+    want to space the telnet ports at LEAST 5 apart. 10 is even better.
 
 
 set remote-boots 2
-    This setting defines if people can boot users on the eggdrop from other
-    bots in your botnet. Valid settings are:
+    This setting defines whether or not people can boot users on the eggdrop
+    from other bots in your botnet. Valid settings are:
      0 - allow *no* outside boots
      1 - allow boots from sharebots
      2 - allow any boots
@@ -273,38 +279,38 @@
 
 
 set telnet-flood 5:60
-    Define here how many telnet connection attempt in how many seconds from
-    the same host constitute a flood.
-    Attempts:Seconds
+    Define here how many telnet connection attempts in how many seconds from
+    the same host constitute a flood. The correct format is Attempts:Seconds.
 
 
 set paranoid-telnet-flood 1
-    If you telnet-flood to apply even to +f users, set this setting to 1
+    If you want telnet-flood to apply even to +f users, set this setting to 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set open-telnets 0
     If you want people allow to telnet in and type 'NEW' to become a new user,
-    set this to 1. This is similar to 'hello'
+    set this to 1. This is similar to the 'hello' msg command. The protect-telnet
+    setting must be set to 0 to use this.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set protect-telnet 0
     This setting will drop telnet connections not matching a known host. It
-    greatly improves protection from IRCOPs, but makes it impossible for NOIRC
+    greatly improves protection from IRCOps, but makes it impossible for limbo
     bots to add hosts or have NEW as a valid login.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set stealth-telnets 0
-    If you don't want eggdrop to identify itself on a telnet connection, set
-    this setting to 1. Eggdrop will display its nickname instead.
+    If you don't want eggdrop to identify itself as an eggdrop on a telnet connection, 
+    set this setting to 1. Eggdrop will display 'Nickname' instead.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set use-telnet-banner 0
-    If you want eggdrop to display a banner when telneting in set this setting
-    to 1. The telnet banner is set by 'telnet-banner'.
+    If you want eggdrop to display a banner when telneting in, set this setting
+    to 1. The telnet banner is set by 'set telnet-banner'.
 
 
 set dcc-sanitycheck 1
@@ -315,42 +321,34 @@
     the connect wouldn't work anyway.  It's suggested that you turn this on.
     Valid settings are 0 for OFF and 1 ON.
 
-
-set quiet-reject 1
-    If turned to 1, the bot will squelch the error message when rejecting a
-    DCC CHAT or SEND.
-    Normally eggdrop tells the DCC user that the CHAT or SEND has been
-    rejected because they don't have access, but sometimes IRC server
-    operators detect bots that way.
-
-
 set max-dcc 50
-    Set here the maximum number of dcc connections you will allow - you can
+    Set here the maximum number of dcc connections you will allow. You can
     increase this later, but never decrease it.
 
 
 set require-p 0
-    Define here if +o user still need the +p flag to dcc the bot.
+    Define here whether or not a +o user still needs the +p flag to dcc the bot.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set dcc-flood-thr 3
-    Specify here the number of lines from a user on the partyline (dcc, telnet)
-    before they are considered to be flooding (and therefore get booted)
+    Specify here the number of lines to accept from a user on the partyline
+    within 10 seconds before they are considered to be flooding and therefore
+    get booted.
 
 
 set resolve-timeout 15
     Set here the amount of seconds before giving up on hostname/address
-    lookup. (you might want to increase this if you are on a slow network).
+    lookup (you might want to increase this if you are on a slow network).
 
 
 set ident-timeout 5
-    Set a timeout in seconds how long to wait on ident-lookups
+    et the time in seconds to wait before an ident-lookup times out.
 
 
 set connect-timeout 15
-    This settings defines a timeout in seconds how long the bot should wait for
-    a dcc chat, telnet, relay, etc connection.
+    This settings defines a time in seconds that the bot should wait before
+    a dcc chat, telnet, or relay connection times out.
 
 
 set my-hostname "virtual.host.com"
@@ -362,7 +360,7 @@
 
 
 set firewall "host:port"
-    Set this to your socks host if your eggdrop sits behind a firewall
+    Set this to your socks host if your eggdrop sits behind a firewall.
 
     Example:
 
@@ -379,10 +377,10 @@
     If you have a NAT firewall (you box has an IP in one of the following
     ranges: 192.168.0.0-192.168.255.255, 172.16.0.0-172.31.255.255,
     10.0.0.0-10.255.255.255 and your firewall transparently changes your
-    address to a unique address for your box.) or you have IP masquerading
+    address to a unique address for your box) or you have IP masquerading
     between you and the rest of the world, and /dcc chat,/ctcp chat or
-    userfile sharing aren't working. Enter your outside IP here.
-    Do not enter anything for my-ip or my-hostname if you use this setting.
+    userfile sharing aren't working, enter your outside IP here. Do not 
+    enter anything for my-ip or my-hostname if you use this setting.
 
 
 set reserved-portrange 2010:2020
@@ -390,13 +388,11 @@
     because you're behind a firewall, or for other security reasons, set it
     here.
 
-
 set dupwait-timeout 5
     If your eggdrop rejects bots that actually have already disconnected from
     another hub, but the disconnect information has not yet spread over the
-    botnet due to lag, use this setting.
-    The bot will wait dupwait-timeout seconds before it checks again and then
-    finally reject the bot.
+    botnet due to lag, use this setting. The bot will wait dupwait-timeout 
+    seconds before it checks again and then finally reject the bot.
 
 
 
@@ -404,82 +400,98 @@
 
 set console "mkcobxs"
     This is the default console mode. It uses the same event flags as the log
-    files do.
-    Note that the console channel is automatically set to your "primary" channel
-    (the one you defined first in config file)
-    Masters can change their console channel and modes with the '.console' command
+    files do. The console channel is automatically set to your "primary" channel,
+    which is set in the modules section of the config file. Masters can change
+    their console channel and modes with the '.console' command.
 
 
 
 ##### COMMON STUFF #####
 
 set ignore-time 15
-    Set the time in minutes how long temp. ignores should last
+    Set the time in minutes that temporary ignores should last.
 
 
 set hourly-updates 00
-    Define here what eggdrop calls 'hourly'. All calls to it, including such things
-    as note notifying or userfile saving are affected by this.
+    Define here what eggdrop considers 'hourly'. All calls to it, including such
+    things as note notifying or userfile saving are affected by this.
 
     Example:
 
     set hourly-updates 15
 
-    Bot will save 15 minutes past every hour its userfile
+    The bot will save its userfile 15 minutes past every hour.
 
 
 set owner "MrLame, MrsLame"
-    Put all permanent owner into this variable
+    Un-comment this line and set the list of owners of the bot.
+    You NEED to change this setting.
+
+set must-be-owner 0
+    If you enable this setting, only permanent owners (owner setting) will be
+    able to use .tcl and .set. Moreover, if you want only let permanent owners 
+    use .dump, then set this to 2.
+    Valid settings are 0, 1 and 2
+
+unbind dcc n tcl *dcc:tcl
+unbind dcc n set *dcc:set
+    Comment these two lines if you wish to enable the .tcl and .set commands.
+    If you select your owners wisely, you should be okay enabling these.
+
+unbind dcc n simul *dcc:simul
+    Comment out this line to add the 'simul' partyline command (owners
+    can manipulate other people on the party line). Please select owners
+    wisely, and use this command ethically!
+
+
+set notify-newusers "$owner"
+    Who should a note be sent to when new users are learned?
 
 
 set default-flags "hp"
-    Enter all flags that new users should get as a default.
+    Enter the flags that all new users should get by default.
+    See '.help whois' on the partyline for a list of flags and
+    their descriptions.
 
 
 set whois-fields "url birthday"
-    Enter all user-defined fields that should be displayed in a '.whois'
-    This will only be shown if the user has one of these xtra fields.
+    Enter all user-defined fields that should be displayed in a '.whois'.
+    This will only be shown if the user has one of these extra fields.
     You might prefer to comment this out and use the userinfo1.0.tcl script
     which provides commands for changing all of these.
 
 
 set die-on-sighup 0
-    Enable this setting if you want your eggdrop on receiving a SIGHUP.
-    Otherwise eggdrop will just rehash.
+    Enable this setting if you want your eggdrop to die upon receiving a SIGHUP
+    kill signal. Otherwise, the eggdrop will just save its userfile and rehash.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set die-on-sigterm 0
-    Enable this setting if you want your eggdrop on receiving a SIGTERM.
-    Otherwise eggdrop will just save its userfile.
+    Enable this setting if you want your eggdrop to die upon receiving a SIGTERM
+    kill signal. Otherwise, the eggdrop will just save its userfile and rehash.
     Valid settings are 0 for OFF and 1 ON.
 
 
-set must-be-owner 0
-    If you enable this setting, only permanent owners (owner setting) will be
-    able to use .tcl and .set
-    moreover if you want only let permanent owners use .dump, then set it to 2
-    Valid settings are 0, 1 and 2
-
-
 set enable-simul 1
-    Enable this setting, if you want to enable the 'dccsimul' Tcl command
+    Enable this setting if you want to enable the 'dccsimul' Tcl command.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set allow-dk-cmds 1
-    Enable this setting, if you want +d & +k users to use commands bound as -|-
+    Enable this setting if you want +d & +k users to use commands bound as -|-.
     Valid settings are 0 for OFF and 1 ON.
 
 
 ##### MODULES #####
 
-After those core settings you should start loading up any modules. Modules are
-loaded by the command "loadmodule module". Eggdrop looks for modules in the
-directory you specified by the module-path setting in the path section.
-Documentation and a list of all modules can be found in doc/modules directory
+After those core settings you should start loading up modules. Modules are
+loaded by the command "loadmodule <module>". Eggdrop looks for modules in the
+directory you specified by the module-path setting in the files and directories
+section. Documentation and a list of all modules can be found in the doc/settings
+directory.
 
-Please note, that for different configurations different modules are needed.
+Please note that for different configurations, different modules are needed.
 Four examples:
 
 - Channel Security Bot
@@ -491,34 +503,33 @@
 - Limbo Bot
 
 Channel Security Bot:
-This bot needs channel, console, dns, irc and if you like ctcp module loaded.
-More is not needed and makes the bot slower.
+This bot needs channels, blowfish, console, dns, irc, and (if you like) ctcp
+modules loaded. More is not needed and makes the bot slower.
 
-Public Bot:
+Public IRC Bot:
 A public bot should have all modules available loaded since they provide all
-functions for everybody.
+functions for everyday use.
 
 Secure Filesys Bot:
-This bot needs all normal irc operating modules but not notes, seen, ctcp or
-share module.
+This bot needs all normal irc operating modules, but not notes, seen, ctcp or
+share modules.
 
 Limbo Bot:
 A limbo bot (bot serves as a botnet hub outside irc) just needs channels, console,
-dns and maybe notes or share module loaded. Of course blowfish needs to be loaded
+dns, and maybe notes or share module loaded. Of course blowfish needs to be loaded
 here, too.
 
 
 
 ##### SCRIPTS #####
 
-Script section should be placed at the end of the config file. All modules should be
-loaded and their variables should be set at this point.
-
+The scripts section should be placed at the end of the config file. All modules
+should be loaded and their variables should be set at this point.
 
 source scripts/script.tcl
-    This line loads script.tcl in the scripts directory of your eggdrop. All
-    script should be put there, although you can place them where you like as
-    long as you can supply a fully qualified path to them.
+    This line loads script.tcl from the scripts directory inside your eggdrop's
+    directory. All scripts should be put there, although you can place them where
+    you like as long as you can supply a fully qualified path to them.
 
     Some commonly loaded scripts are alltools.tcl and action.fix.tcl. The
     appropriate source lines are looking so:
Index: eggdrop1.6/doc/settings/mod.assoc
diff -u eggdrop1.6/doc/settings/mod.assoc:1.3 eggdrop1.6/doc/settings/mod.assoc:1.4
--- eggdrop1.6/doc/settings/mod.assoc:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.assoc	Thu Dec 13 23:43:11 2001
@@ -1,7 +1,9 @@
 ##### ASSOC MODULE #####
 
-This module provides assoc support, i.e. naming channels on the botnet
+This module provides assoc support, i.e. naming channels on the botnet.
 
-Put this line into your eggdrop configuration file file to load assoc module:
+This module requires: none
+
+Put this line into your eggdrop configuration file to load the assoc module:
 
 loadmodule assoc
Index: eggdrop1.6/doc/settings/mod.blowfish
diff -u eggdrop1.6/doc/settings/mod.blowfish:1.3 eggdrop1.6/doc/settings/mod.blowfish:1.4
--- eggdrop1.6/doc/settings/mod.blowfish:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.blowfish	Thu Dec 13 23:43:11 2001
@@ -1,15 +1,15 @@
 ##### BLOWFISH MODULE #####
 
 Eggdrop can encrypt your userfile, so users can have secure passwords.
-Please note, that when you change your encryption method later (i.e.
-using other modules like a md5 module) you can't use your current
-userfile anymore.
-Attention, eggdrop will not start without a chosen encryption method.
+Please note that when you change your encryption method later (i.e.
+using other modules like a md5 module), you can't use your current
+userfile anymore. Eggdrop will not start without an encryption module.
 
-Put this line into your eggdrop configuration file file to load blowfish module:
+This module requires: none
 
-checkmodule blowfish
+Put this line into your eggdrop configuration file to load the blowfish module:
 
+checkmodule blowfish
 
-This is checkmodule, because during .restart the module will already
-be loaded
\ No newline at end of file
+This is checkmodule because during .restart the module will already
+be loaded.
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.compress
diff -u eggdrop1.6/doc/settings/mod.compress:1.3 eggdrop1.6/doc/settings/mod.compress:1.4
--- eggdrop1.6/doc/settings/mod.compress:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.compress	Thu Dec 13 23:43:11 2001
@@ -4,16 +4,17 @@
 bot to transfer compressed user files and therefore save a significant amount
 of bandwidth.
 
-Put this line into your eggdrop configuration file file to load compress module:
+This module requires: share
 
-loadmodule compress
+Put this line into your eggdrop configuration file to load the compress module:
 
+loadmodule compress
 
 There are also some variables you can to set in your config file:
 
 set share-compressed 1 (Disabled by default)
-# [0/1] allow compressed sending of user files. The user files
-# are compressed with the compression level defined in `compress-level'.
+    Allow compressed sending of user files? The user files are
+    compressed with the compression level defined in `compress-level'.
 
 set compress-level 9
-    Set here the gzip compression level you want to use
\ No newline at end of file
+   This is the default compression level used.
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.console
diff -u eggdrop1.6/doc/settings/mod.console:1.3 eggdrop1.6/doc/settings/mod.console:1.4
--- eggdrop1.6/doc/settings/mod.console:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.console	Thu Dec 13 23:43:11 2001
@@ -1,24 +1,25 @@
 ##### CONSOLE MODULE #####
 
 This module provides storage of console settings when you exit the
-bot (or .store)
+bot or type .store on the partyline.
 
-Put this line into your eggdrop configuration file file to load console module:
+This module requires: none
 
-loadmodule console
+Put this line into your eggdrop configuration file to load the console module:
 
+loadmodule console
 
 There are also some variables you can to set in your config file:
 
 set console-autosave 1
-    save users console settings automatically? (otherwise they have
-    to use .store)
+    Save users console settings automatically? Otherwise, they have
+    to use the .store command.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set force-channel 0
     If a user doesn't have any console settings saved, which channel
-    do you want them automatically put on.
+    do you want them automatically put on?
     Valid settings are 0-99999
 
 
Index: eggdrop1.6/doc/settings/mod.ctcp
diff -u eggdrop1.6/doc/settings/mod.ctcp:1.3 eggdrop1.6/doc/settings/mod.ctcp:1.4
--- eggdrop1.6/doc/settings/mod.ctcp:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.ctcp	Thu Dec 13 23:43:11 2001
@@ -1,25 +1,26 @@
 ##### CTCP MODULE #####
 
-This module provides the normal ctcp replies that you'd expect
-This module requires the channels, irc & server modules loaded
+This module provides the normal ctcp replies that you'd expect.
+Without it loaded, CTCP CHAT will not work.
 
-Put this line into your eggdrop configuration file file to load ctcp module:
+This module requires: server
 
-loadmodule ctcp
+Put this line into your eggdrop configuration file to load the ctcp module:
 
+loadmodule ctcp
 
 There are also some variables you can to set in your config file:
 
 set ctcp-mode 0
-    Set here, how the ctcp module should work. There are 3 possible
+    Set here how the ctcp module should answer ctcps. There are 3 possible
     operating modes:
-     0: normal behavior.
-     1: bot ignores all CTCPs, except for CTCP CHATs & PINGs requested
-        by +o flag users.
-     2: bot doesn't answer more than C CTCPs in S seconds. C/S are
-        defined by the set flood-ctcp C:S
+      0: Normal behavior is used.
+      1: The bot ignores all ctcps, except for CHAT and PING requests
+         by users with the +o flag.
+      2: Normal behavior is used, however the bot will not answer more
+         than X ctcps in Y seconds (defined by 'set flood-ctcp').
     Valid settings are 0-2
 
-There are also several variables to better blend your egg in. they are
-ctcp-version, ctcp-finger, and ctcp-userinfo. You can use set to set
-them to values you like.
\ No newline at end of file
+There are also several variables to help make your bot less noticeable.
+They are: ctcp-version, ctcp-finger, and ctcp-userinfo. You can use set to set
+them to values you'd like.
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.dns
diff -u eggdrop1.6/doc/settings/mod.dns:1.3 eggdrop1.6/doc/settings/mod.dns:1.4
--- eggdrop1.6/doc/settings/mod.dns:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.dns	Thu Dec 13 23:43:11 2001
@@ -2,8 +2,10 @@
 
 This module provides asynchronous dns support. This will avoid long
 periods where the bot just hangs there, waiting for a hostname to
-resolve, which often let it timeout on all other connections.
+resolve, which will often let it timeout on all other connections.
 
-Put this line into your eggdrop configuration file file to load dns module:
+This module requires: none
+
+Put this line into your eggdrop configuration file to load the dns module:
 
 loadmodule dns
Index: eggdrop1.6/doc/settings/mod.filesys
diff -u eggdrop1.6/doc/settings/mod.filesys:1.3 eggdrop1.6/doc/settings/mod.filesys:1.4
--- eggdrop1.6/doc/settings/mod.filesys:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.filesys	Thu Dec 13 23:43:11 2001
@@ -1,47 +1,48 @@
 ##### FILESYSTEM MODULE #####
 
 This module provides an area within the bot where users can store
-files. With this module the bot is useable as a file server.
+files. With this module, the bot is usable as a file server.
 
-Put this line into your eggdrop configuration file file to load filesys module:
+This module requires: transfer
 
-loadmodule filesys
+Put this line into your eggdrop configuration file to load the filesys module:
 
+loadmodule filesys
 
 There are also some variables you can to set in your config file:
 
 set files-path "/home/mydir/eggdrop/filesys"
-    Set here hie 'root' directory for the file system
+    Set here the 'root' directory for the file system.
 
 
 set incoming-path "/home/mydir/eggdrop/filesys/incoming"
     If you want to allow uploads, set this to the directory uploads
-    should be put into.
-    Set this to "" if you don't want people to upload files to your bot.
+    should be put into. Set this to "" if you don't want people to
+    upload files to your bot.
 
 
 set upload-to-pwd 0
-    If you don't want to have a central incoming directory but uploads
-    should go to the current directory that a user is in, set this
-    setting to 1.
+    If you don't want to have a central incoming directory, but instead
+    want uploads to go to the current directory that a user is in, set
+    this setting to 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set filedb-path ""
-    Eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
-    to keep track of its own file system info -- if you can't do that (like
-    if the dcc path isn't owned by yours) or you just don't want it to do
-    that, specify a path here where you'd like all the database files to
-    be stored instead (otherwise, just leave it blank)
+    Eggdrop creates a '.filedb' file in each subdirectory of your file area
+    to keep track of its own file system information. If you can't do that (for
+    example, if the dcc path isn't owned by you, or you just don't want it to do
+    that) specify a path here where you'd like all of the database files to be
+    stored instead.
 
 
 set max-file-users 20
-    Set here maximum number of people that can be in the file area at once
-    (0 to make it effectively infinite)
-    Valid settings are 0-unlimited
+    Set here the maximum number of people that can be in the file area at once.
+    Setting this to 0 makes it effectively infinite.
+    Valid settings are 0-unlimited.
 
 
 set max-filesize 1024
-    Set here the maximum allowable file size that will be received, in K
-    (default is 1024K = 1M)
-    Valid settings are 0-unlimited
\ No newline at end of file
+    Set here the maximum allowable file size that will be received (in kb).
+    Setting this to 0 makes it effectively infinite.
+    Valid settings are 0-unlimited.
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.irc
diff -u eggdrop1.6/doc/settings/mod.irc:1.5 eggdrop1.6/doc/settings/mod.irc:1.6
--- eggdrop1.6/doc/settings/mod.irc:1.5	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.irc	Thu Dec 13 23:43:11 2001
@@ -1,132 +1,147 @@
 ##### IRC MODULE #####
 
-This module provides basic irc support for your bot.  You have to
-load this if you want your bot to come on irc.
+This module provides basic IRC support for your bot.  You have to
+load this if you want your bot to come on IRC.
 
-Put this line into your eggdrop configuration file file to load irc module:
+This module requires: server, channels
 
-loadmodule irc
+Put this line into your eggdrop configuration file to load the irc module:
 
+loadmodule irc
 
 There are also some variables you can to set in your config file:
 
 set bounce-bans 1
-    Set this to 1 if you want to bounce all server bans
+    Set this to 1 if you want to bounce all server bans.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set bounce-modes 0
-    Set this to 1 if you want to bounce all the server modes
+    Set this to 1 if you want to bounce all the server modes.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set max-modes 30
-    Set here the global limit for +b/+e/+I modes on your irc server. This
-    limit is set to 30 on 2.10 ircd servers.
+    Set here the global limit for +b/+e/+I modes on your IRC server. This
+    limit is set to 30 on 2.10 IRCd servers.
 
 
 set max-bans 20
-    Set here the maximum number of bans you want eggdrop to put
-    in a channel. Eggdrop wont place any more bans if this limit
-    is reached.
+    Set here the maximum number of bans you want the bot to set on a channel.
+    Eggdrop will not place any more bans if this limit is reached.
 
 
 set kick-fun 0
     Set this to 1 if you want the bot to kick for control character/ctcp
-    avalanches to a channel. Remember that if it does, as it won't ban
-    them, it can be at the origin of a nice kick-flood.
+    avalanches to a channel. Remember that if it does, it won't ban them.
+    This can start kick floods.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set ban-fun 0
     Set this to 1 if you want the bot to ban for control character/ctcp
-    avalanches to a channel. Can prevent the above described kick-flood,
-    but can also fill the banlist.
+    avalanches to a channel. Can prevent kick floods, but also fill the
+    banlist.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set learn-users 0
-    If you want people to introduce themselves to eggdrop via 'hello',
-    set this to 1.
+    If you want people to be able to add themselves to the bot's userlist
+    with the default userflags (defined above in the config file) via the
+    'hello' msg command, set this to 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set wait-split 600
     Set here the time (in seconds) to wait for someone to return from
-    a netsplit (i.e. wasop will expire afterwards).
-    Hint: Set this to 1500 on IRCNet, since it's nick delay stops after
-          30 minutes.
+    a netsplit (i.e. wasop will expire afterwards). Set this to 1500
+    on IRCnet since it's nick delay stops after 30 minutes.
 
 
 set wait-info 180
     Set here the time (in seconds) that someone must have been off-channel
-    before re-displaying their info
+    before re-displaying their info line.
 
 
 set mode-buf-length 200
     Set this to the maximum number of bytes to send in the arguments
-    to mode's sent to the server, most servers default this to 200,
-    so it should be sufficient.
+    of modes sent to the server. Most servers default this to 200.
+
+
+unbind msg - hello *msg:hello
+bind msg - myword *msg:hello
+    Many IRCops find bots by seeing if they reply to 'hello' in a msg. 
+    You can change this to another word by un-commenting the following
+    two lines, and changing "myword" to the word wish to use instead of
+    'hello'. It must be a single word.
+
+
+unbind msg - ident *msg:ident
+unbind msg - addhost *msg:addhost
+    Many takeover attempts occur due to lame users blindly /msg ident'ing to
+    the bot and attempting to guess passwords. We now unbind this command by
+    default to discourage them. You can enable this command by un-commenting
+    the following two lines.
 
 
 set no-chanrec-info 0
     If you are so lame you want the bot to display peoples info lines, even
-    when you are too lazy to add their chanrecs to a channel, set this to 1
+    when you are too lazy to add their chanrecs to a channel, set this to 1.
     *NOTE* This means *every* user with an info line will have their info
     display on EVERY channel they join (provided they have been gone longer
-    than wait-info)
+    than wait-info).
     Valid settings are 0 for OFF and 1 ON.
 
 
-
-These were the core irc module settings. There are more settings for
+Those were the core IRC module settings. There are more settings for
 'net-type' 1 and 5. net-type has to be set in the server module config
 section.
 
 
-##### IRC MODULE - net-type 1 specific features (IRCNET) #####
+### IRC MODULE - IRCnet SPECIFIC FEATURES ####
 
-Attention: Use this settings *only* if you set 'net-type' to 1!
+Attention: Use these settings *only* if you set 'net-type' to 1!
 
 set bounce-exempts 0
-    Set this to 1 if you want to bounce all server exemptions (+e modes)
+    Set this to 1 if you want to bounce all server exemptions (+e modes).
     Valid settings are 0 for OFF and 1 ON.
 
 
 set bounce-invites 0
-    Set this to 1 if you want to bounce all server invitations (+I modes)
+    Set this to 1 if you want to bounce all server invitations (+I modes).
     Valid settings are 0 for OFF and 1 ON.
 
 
 set max-exempts 20
-    Set here the maximum number of exempts you want eggdrop to put
-    in a channel. Eggdrop wont place any more exempts if this limit
-    is reached.
+    Set here the maximum number of exempts you want eggdrop to set
+    on a channel. Eggdrop will not place any more exempts if this
+    limit is reached.
 
 
 set max-invites 20
-    Set here the maximum number of invites you want eggdrop to put
-    in a channel. Eggdrop wont place any more invites if this limit
-    is reached.
-    Valid settings are 0 for OFF and 1 ON.
+    Set here the maximum number of invites you want eggdrop  to set
+    on a channel. Eggdrop will not place any more invites if this
+    limit is reached.
 
 
-set use-exempts 0 (Disabled by Default)
+set use-exempts 0
     If you set this feature to 0 in your eggdrop config file, the bot
-    wont use any exempts. This setting is set to 1 as a default in nettype 1
+    will not use any exempts. This setting is set to 1 as a default in
+    nettype 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
-set use-invites 0 (Disabled by Default)
+set use-invites 0
     If you set this feature to 0 in your eggdrop config file, the bot
-    wont use any invites. This setting is set to 1 as a default in nettype 1
+    wont use any invites. This setting is set to 1 as a default in
+    nettype 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set prevent-mixing 1
-    At the moment the current ircd version (2.10) doesn't support the mix
-    of b,o and v modes with e and I modes. This might be changed in the
-    future, so use 1 at the moment for this flag
+    At the moment, the current IRCnet IRCd version (2.10) doesn't support the mixing
+    of b,o and v modes with e and I modes. This might be changed in the future, so
+    use 1 at the moment for this setting.
     Valid settings are 0 for OFF and 1 ON.
 
 
@@ -135,25 +150,28 @@
 Attention: Use this settings *only* if you set 'net-type' to 5!
 
 set kick-method 1
-    If your network supports more users per kick command then 1, you change
-    this behaviour here: Set X for x users at once or 0 for all at once
+    If your network supports more users per kick command then 1, you can
+    change this behavior here. Set this to the number of users to kick at
+    once, or set this to 0 for all at once.
 
 
 set modes-per-line 3
     Some networks allow you to stack lots of channel modes into one line.
-    They're all guaranteed to support at least 3, so that's the default,
-    but if you know your network supports more, you may want to adjust
-    this value.
+    They're all guaranteed to support at least 3, so that's the default.
+    If you know your network supports more, you may want to adjust this.
     Valid settings are 3-6
 
+set include-lk 1
+    Some networks don't include the +l limit and +k or -k key modes
+    in the modes-per-line (see above) limitation. Set include-lk to 0 for
+    these networks.
 
 set use-354 0
-    Set this to 1 if your network uses ircu2.10.01 specific /who requests,
-    eggdrop can therefore ask only for exactly what's needed.
+    Set this to 1 if your network uses IRCu2.10.01 specific /who requests.
+    Eggdrop can, therefore, ask only for exactly what's needed.
     Valid settings are 0 for OFF and 1 ON.
 
 
-set rfc-compliant 1 (Disabled by default)
+set rfc-compliant 1
     If your network doesn't use rfc 1459 compliant string matching routines,
-    turn this to 0. All networks apart from Dalnet comply with rfc 1459, so
-    you should only disable it on Dalnet or networks which use Dalnet's code.
+    set this to 0.
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.notes
diff -u eggdrop1.6/doc/settings/mod.notes:1.2 eggdrop1.6/doc/settings/mod.notes:1.3
--- eggdrop1.6/doc/settings/mod.notes:1.2	Sun May 28 13:59:24 2000
+++ eggdrop1.6/doc/settings/mod.notes	Thu Dec 13 23:43:11 2001
@@ -1,30 +1,29 @@
 ##### NOTES MODULE #####
 
 This module provides support for storing of notes for users from each
-other notes between currently online users is supported in the core,
-this is only for storing the notes for later retrieval, direct
-user->user notes are built-in
+other. Note sending between currently online users is supported in the core,
+this is only for storing the notes for later retrieval.
 
-Put this line into your eggdrop configuration file file to load notes module:
+This module requires: none
 
-loadmodule notes
+Put this line into your eggdrop configuration file to load the notes module:
 
+loadmodule notes
 
 There are also some variables you can to set in your config file:
 
 set notefile "LamestBot.notes"
-    Enter here the filename where private notes between users are
-    stored
+    Set here the filename where private notes between users are stored.
 
 
 set max-notes 50
     Set here the maximum number of notes to allow to be stored for
-    each user (to prevent flooding)
+    each user (to prevent flooding).
     Valid settings are 0-99999
 
 
 set note-life 60
-    Set here how long (in days) to store notes before expiring them
+    Set here how long (in days) to store notes before expiring them.
     Valid settings are 0-99999
 
 
@@ -36,11 +35,11 @@
 
 set notify-users 1
     Set this to 1 if you want the bot to let people know hourly if they
-    have any notes
+    have any notes.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set notify-onjoin 1
     Set this to 1 if you want the bot to let people know on join if they
-    have any notes
+    have any notes.
     Valid settings are 0 for OFF and 1 ON.
Index: eggdrop1.6/doc/settings/mod.seen
diff -u eggdrop1.6/doc/settings/mod.seen:1.3 eggdrop1.6/doc/settings/mod.seen:1.4
--- eggdrop1.6/doc/settings/mod.seen:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.seen	Thu Dec 13 23:43:11 2001
@@ -1,12 +1,12 @@
 ##### SEEN MODULE #####
 
 This module provides very basic seen commands via msg, on channel or via dcc.
-Note that this module works only for users in the bot's config file.
+This module works only for users in the bot's userlist. If you are looking for
+a better and more advanced seen module, try the gseen module by G'Quann. You
+can find it at http://www.visions-of-fantasy.de/gseen.mod/.
 
-Put this line into your eggdrop configuration file file to load seen module:
+This module requires: none
 
-loadmodule seen
+Put this line into your eggdrop configuration file to load the seen module:
 
-
-If you are looking for a better and more advanced seen module, try gseen module
-by G'Quann. You can find it at http://mupfel.infra.de/~gquann/gseen.mod/
\ No newline at end of file
+loadmodule seen
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.server
diff -u eggdrop1.6/doc/settings/mod.server:1.10 eggdrop1.6/doc/settings/mod.server:1.11
--- eggdrop1.6/doc/settings/mod.server:1.10	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.server	Thu Dec 13 23:43:11 2001
@@ -1,51 +1,54 @@
 ##### SERVER MODULE #####
 
 This module provides the core server support. You have to load this
-if you want your bot to come on irc.
+if you want your bot to come on IRC. Not loading this is equivalent
+to the old NO_IRC define.
 
-Put this line into your eggdrop configuration file file to load server module:
+This module requires: none
 
-loadmodule server
+Put this line into your eggdrop configuration file to load the server module:
 
+loadmodule server
 
 There are also some variables you can to set in your config file:
 
 set net-type 0
-    Define here the network you use. There are six settings:
-     0 = Efnet (non +e/+I hybrid)
+    What is your network?
+      0 = EFnet (non +e/+I hybrid)
      1 = IRCnet
      2 = Undernet
-     3 = Dalnet
-     4 = Efnet +e/+I hybrid
+      3 = DALnet
+      4 = EFnet +e/+I hybrid
      5 = Others
-    Valid settings are 0-5
+    Valid settings are 0-5.
 
 
 set nick "LamestBot"
-    Set here the nick of the bot, that which it uses on IRC, and
-    on the botnet unless you specify a separate botnet-nick
+    Set the nick the bot uses on IRC, and on the botnet
+    unless you specify a separate botnet-nick, here.
 
 
 set altnick "L?m?stB?t"
-    Set here an alternative nick to use if the nick specified by 'nick'
-    is unavailable. All '?' characters will be replaced by a random number.
+    Set the alternative nick which the bot uses on IRC if the nick specified
+    by 'set nick' is unavailable. All '?' characters will be replaced by random
+    numbers.
 
 
 set keep-nick 1
-    This setting makes the bot try to get his original nickname back (for
-    example, if the intended nickname is already in use).
+    This setting makes the bot try to get his original nickname back if its
+    primary nickname is already in use.
 
 
 set realname "/msg LamestBot hello"
-    Set here what to display in the real-name field for the bot
+    Set here what to display in the real-name field for the bot.
 
 
 set init-server { putserv "MODE $botnick +i-ws" }
-    Set here a script to run (if any) when first connecting to a server
+    Set here a script to run (if any) when first connecting to a server.
 
 
 set servers { IRCSERVER1:PORT IRSERVER2:PORT ... }
-    Set here the list of irc servers you want your bot to connect to. You can
+    Set here the list of IRC servers you want your bot to connect to. You can
     add an optional port for the server.
 
     Example:
@@ -61,77 +64,73 @@
 
 
 set default-port 6667
-    Set the default port which should be used if no one is specified at
-    '.jump' or in 'server'
+    Set the default port which should be used if none is specified with
+    '.jump' or in 'set servers'.
 
 
 set strict-servernames 0
-    Often irc servers call themselves in another way then there dns is. If
-    you want eggdrop to replace your entry in the config file with this
-    name, set this to 1. If you turn this setting to 0, eggdrop will keep
-    a separate list of the names irc servers call themselves
+    Often, IRC servers call themselves a name other than their actual
+    hostname. If you want eggdrop to replace your entry in the config
+    file with this name, set this to 1. If you set this setting to 0,
+    eggdrop will keep a separate list of what IRC servers call themselves.
     Valid settings are 0 for OFF and 1 ON.
 
 set server-cycle-wait 60
     This setting defines how long eggdrop should wait before moving from one
-    server to another on disconnect.
-    If you set 0 here, eggdrop wont wait at all and connect instantly.
-    Please note, that a too low setting could result in k-line for your host,
-    since many ircops don't like being flooded with connects.
+    server to another on disconnect. If you set 0 here, eggdrop will not wait
+    at all and will connect instantly. Setting this too low could result in
+    your bot being K:Lined.
     Valid settings are 0-infinite
 
 set never-give-up 1
-    This settings makes the bot cycle forever and keep trying to connect to
-    all irc servers in it's current list if they're down.
+    This settings makes the bot cycle forever through the server list until
+    it successfully connects to one.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set server-timeout 60
-    Set here the timeout how long eggdrop should wait for a response when
-    connecting to a server before giving up and moving on to next server
-    in list.
+    Set here how long eggdrop should wait for a response when connecting to a
+    server before giving up and moving on to next server.
 
 
 set servlimit 0
-    If the number of servers on the net gets below this number, it will
-    jump to a new server (i.e., it will assume it's on the losing end of
-    a netsplit) -- set to 0 to turn off
-    Note that most irc networks use Time Stamping or Nick Delay now, so
-    it's to your advantage to turn this off.
+    If the number of servers on the net gets below this number, the bot
+    will jump to a new server (it will assume it's on the losing end of
+    a netsplit). Set this to 0 to turn off. If your bot is running on
+    any major IRC network, this should probably be turned off.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set check-stoned 1
-    Set this to 1 if eggdrop should check for stoned servers? (i.e.
-    Where the server connection has died, but eggdrop hasn't been
-    notified yet).
+    Set this to 1 if eggdrop should check for stoned servers? (where the
+    server connection has died, but eggdrop hasn't been notified yet).
     Valid settings are 0 for OFF and 1 ON.
 
 
 set serverror-quit 1
-    If you want your bot to exit the server if it receives a error msg set
-    this to 1
+    If you want your bot to exit the server if it receives an ERROR message,
+    set this to 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set max-queue-msg 300
     Set here the maximum number of lines to queue to the server. If you're
-    going to dump large chunks of text to people over irc, you will probably
-    want to raise this -- most people are fine at 300 though
+    going to dump large chunks of text to people over IRC, you will probably
+    want to raise this. 300 is fine for most people though.
 
 
 set use-console-r 0
-    This setting allows you the logging of all information got from a server,
-    via console mode 'r'
-    NOTE: This is a large security hole, allowing people to see passwords.
+    This setting allows you the logging of all information received from the
+    server via console mode 'r'.
+    NOTE: This is a large security hole, allowing people to see user passwords.
     This is now restricted to +n users only. Please choose your owners with
     care.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set debug-output 0
-    This setting allows you the logging of all information sent to a server,
-    via console mode 'v'
+    This setting allows you the logging of all information sent to the server
+    via console mode 'v'.
     NOTE: This is a large security hole, allowing people to see passwords.
     This is now restricted to +n users only. Please choose your owners with
     care.
@@ -140,7 +139,7 @@
 
 set strict-host 0
     Set this to 1 if you don't want your the bot to strip a leading '~'
-    on user at hosts
+    on user at hosts.
     Valid settings are 0 for OFF and 1 ON.
 
 
@@ -153,63 +152,63 @@
 
 
 set flood-msg 5:60
-     Set here how many msgs in how many seconds from one host are
-     recognized as a flood. Not specifying or using number = 0
-     will not check against msg floods
+     Set here how many msgs in how many seconds from one host constitutes
+     a flood. If you set this to 0:0, msg flood protection will be disabled.
 
 set flood-ctcp 3:60
      Set here how many ctcps in how many seconds from one host are
      recognized as a flood. Not specifying or using number = 0
-     will not check against ctcp floods
+     will not check against ctcp floods.
 
 
 set answer-ctcp 3
-    Set how many ctcps should be answered at once
+    Set how many ctcps should be answered at once.
 
 
 set lowercase-ctcp 0
-    If you want your bot to answer lower case ctcp request (non rfc
-    compliant) set this setting to 1.
-    Please note: mIRC will do this, most other clients will not
+    If you want your bot to answer lower case ctcp requests (non rfc-
+    compliant), set this setting to 1. mIRC will do this, most other
+    clients will not.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set trigger-on-ignore 0
-    If you want eggdrop to trigger binds for ignored users, set this to 1
+    If you want eggdrop to trigger binds for ignored users, set this to 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set double-mode 0
-    Allow a msg being twice in mode queue?
+    Allow identical messages in the mode queue?
     Valid settings are 0 for OFF and 1 ON.
 
 
 set double-server 0
-    Allow a msg being twice in server queue?
+    Allow identical messages in the server queue?
     Valid settings are 0 for OFF and 1 ON.
 
 
 set double-help 0
-    Allow a msg being twice in help queue?
+    Allow identical messages in the help queue?
     Valid settings are 0 for OFF and 1 ON.
 
 set use-penalties 1 (default on net-type 1)
     This enables eggdrop's penalty calculation. Every command eggdrop sends to
-    the irc server raises it's penalty points. If eggdrop reaches a server limit,
+    the IRC server raises it's penalty points. If eggdrop reaches a server limit,
     it gets disconnected with "excess flood" message. Eggdrop is able to count
     internal those penalty points, too and take measures against excess flooding.
     Note: it's highly advised to turn this on!
 
 
-
 set optimize-kicks 1
-    Optimize kicks optimizes kick queue. It also traces nick changes and parts in
-    channel and changes the kick queue respectively.
-    There are three different options for this setting:
-     0 = turn it off
-     1 = optimize kick queue by summarizing kicks.
-     2 = trace nick changes and channel parts and change the queue respectively. For
-         example, bot wont try to kick users who have already parted the channel.
+    This optimizes the kick queue. It also traces nick changes and parts in
+    the channel and changes the kick queue accordingly. There are three
+    different options for this setting:
+      0 = Turn it off.
+      1 = Optimize the kick queue by summarizing kicks.
+      2 = Trace nick changes and parts on the channel and change the queue
+          accordingly. For example, bot will not try to kick users who have
+          already parted the channel.
+    ATTENTION: Setting 2 is very CPU intensive.
     Valid settings are 0-2
 
 
@@ -223,16 +222,16 @@
 
 set check-mode-r 1
     This settings defines how umode +r is understood by eggdrop. Some
-    networks use +r to mean a restricted connection. If this is your
-    case, and you want your bot to leave restricted servers and jump
-    to the next one on his server list, then set it to 1.
+    networks use +r to indicate a restricted connection. If this is your
+    case, and you want your bot to leave restricted servers and jump to
+    the next server on its list, then set it to 1.
     Please note, this setting is automatically set to 0 for net-type 0/2/3/4,
     and set to 1 for net-type 1.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set nick-len 9
-    This setting enables you to use different nick lengths then the ircd's
-    default 9 (Dalnet uses 32 imo). The maximum supported length by eggdrop is 32.
+    This setting allows you to specify the maximum nick-length supported by
+    your network. The default setting is 9. The maximum supported length by
+    eggdrop is 32.
     Valid settings are 9-32
-
Index: eggdrop1.6/doc/settings/mod.share
diff -u eggdrop1.6/doc/settings/mod.share:1.3 eggdrop1.6/doc/settings/mod.share:1.4
--- eggdrop1.6/doc/settings/mod.share:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.share	Thu Dec 13 23:43:11 2001
@@ -2,56 +2,53 @@
 
 This module provides userfile sharing support between two directly
 linked bots.
-This module requires the channels & transfer modules loaded
 
-Put this line into your eggdrop configuration file file to load share module:
+This module requires: transfer, channels
 
-loadmodule share
+Put this line into your eggdrop configuration file to load the share module:
 
+loadmodule share
 
 There are also some variables you can to set in your config file:
 
-set allow-resync 0 (disabled by default)
-    When two bots get disconnected this setting allows them to create a
+set allow-resync 0
+    When two bots get disconnected, this setting allows them to create a
     resync buffer which saves all changes done to the userfile during
-    the disconnect. So, when they reconnect, they will not have to
-    transfer the complete user file, but instead, just send the resync
-    buffer.
-    This feature is a bit buggy at the moment, but it may be fixed soon.
+    the disconnect. When they reconnect, they will not have to transfer 
+    the complete user file, but, instead, just send the resync buffer.
     Valid settings are 0 for OFF and 1 ON.
 
 
-set resync-time 900 (disabled by default)
+set resync-time 900
     This setting specifies how long to hold another bots resync data
     before flushing it.
-    This is a setting for allow-resync
+    This is a setting for allow-resync.
 
 
-set private-global 0 (disabled by default)
+set private-global 0
     When sharing user lists, DON'T ACCEPT global flag changes from other bots?
-    NOTE: the bot will still send changes made on the bot, it just wont accept
+    NOTE: The bot will still send changes made on the bot, it just wont accept
     any global flag changes from other bots.
     Valid settings are 0 for OFF and 1 ON.
 
 
-set private-globals "mnot" (disabled by default)
+set private-globals "mnot"
     When sharing user lists, if private-global isn't set, which global flag
-    changes from other bots should be ignored ?
-    Valid settings are all global flags including private flags (A-Z)
+    changes from other bots should be ignored?
+    Valid settings are all global flags including private flags (A-Z).
 
 
-set private-user 0 (disabled by default)
-    When sharing user lists, DON'T ACCEPT any userfile changes from other
-    bots?
-    NOTE: paranoid people should use this feature on their hub bot - this
-    will force all +host/+user/chpass/etc. changes to be made via the hub
+set private-user 0
+    When sharing user lists, don't accept ANY userfile changes from other
+    bots? Paranoid people should use this feature on their hub bot. This
+    will force all userlist changes to be made via the hub.
     Valid settings are 0 for OFF and 1 ON.
 
 
-set override-bots 0 (disabled by default)
+set override-bots 0
     This setting makes the bot discard it's own bot records in favor of
     the ones sent by the hub.
-    Please note, that no passwords or botflags are shared, only ports and
-    address are added to sharing procedure.
-    Note: This only works with hubs that are v1.5.1 or higher.
+    NOTE: No passwords or botflags are shared, only ports and
+    address are added to sharing procedure. This only works with hubs that
+    are v1.5.1 or higher.
     Valid settings are 0 for OFF and 1 ON.
Index: eggdrop1.6/doc/settings/mod.transfer
diff -u eggdrop1.6/doc/settings/mod.transfer:1.3 eggdrop1.6/doc/settings/mod.transfer:1.4
--- eggdrop1.6/doc/settings/mod.transfer:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.transfer	Thu Dec 13 23:43:11 2001
@@ -1,38 +1,40 @@
 ##### TRANSFER MODULE #####
 
-the transfer module provides dcc send/get support and bot userfile
-transfer support (not sharing).
+The transfer module provides dcc send/get support and userfile transfer
+support for userfile sharing. Un-comment the next line to load it if you 
+need this functionality.
 
-Put this line into your eggdrop configuration file file to load transfer module:
+This module requires: none
 
-loadmodule transfer
+Put this line into your eggdrop configuration file to load the transfer module:
 
+loadmodule transfer
 
 There are also some variables you can to set in your config file:
 
 set max-dloads 3
     Set here the maximum number of simultaneous downloads to allow for
-    each user
+    each user.
     Valid settings are 0-infinite
 
 
 set dcc-block 1024
-    Set here the block size for dcc transfers (ircII uses 512 bytes,
-    but admits that may be too small -- 1024 is standard these days)
-    set this to 0 to use turbo-dcc (recommended)
-    Valid settings are 0 for OFF and 1 ON.
+    Set here the block size for dcc transfers. ircII uses 512 bytes,
+    but admits that may be too small. 1024 is standard these days.
+    Set this to 0 to use turbo-dcc (recommended).
+    Valid settings are 0-infinite.
 
 
 set copy-to-tmp 1
-    Enable this setting, if you want to copy files into the /tmp directory
+    Enable this setting if you want to copy files into the /tmp directory
     before sending them. This is useful on most systems for file stability,
     but if your directories are NFS mounted, it's a pain, and you'll want
-    to set this to 0. If you are low on disk space, you may want to set this
-    to 0, too.
+    to set this to 0. If you are low on disk space, you may also want to
+    set this to 0.
     Valid settings are 0 for OFF and 1 ON.
 
 
 set xfer-timeout 30
-    Set here the time (in seconds) how long a dcc file transfer can remain
-    inactive before being timed out.
-    Valid settings are 0-infinite
\ No newline at end of file
+    Set here the time (in seconds) to wait before an inactive transfer
+    times out.
+    Valid settings are 0-infinite.
\ No newline at end of file
Index: eggdrop1.6/doc/settings/mod.uptime
diff -u eggdrop1.6/doc/settings/mod.uptime:1.1 eggdrop1.6/doc/settings/mod.uptime:1.2
--- eggdrop1.6/doc/settings/mod.uptime:1.1	Mon Nov  5 08:14:23 2001
+++ eggdrop1.6/doc/settings/mod.uptime	Thu Dec 13 23:43:11 2001
@@ -1,8 +1,18 @@
 ##### UPTIME MODULE #####
 
-This module reports uptime statistics to http://uptime.energymech.net.
-Go look and see what your uptime is! (it will show up after 9 hours or so)
+This module reports uptime statistics to http://uptime.eggheads.org.
+Go look and see what your uptime is! It takes about 9 hours to show up,
+so if your bot isn't listed, try again later.
 
-Put this line into your eggdrop configuration file file to load uptime module:
+Information sent to the server includes the bot's uptime, botnet-nick,
+server, version, and IP address. This information is stored in a temporary 
+logfile for debugging purposes only. The only publicly available information
+will be the bot's botnet-nick, version and uptime. If you do not wish for this
+information to be sent, comment out the 'loadmodule uptime' line in your bot's
+config file.
+
+This module requires: server
+
+Put this line into your eggdrop configuration file to load the uptime module:
 
 loadmodule uptime
Index: eggdrop1.6/doc/settings/mod.wire
diff -u eggdrop1.6/doc/settings/mod.wire:1.3 eggdrop1.6/doc/settings/mod.wire:1.4
--- eggdrop1.6/doc/settings/mod.wire:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.wire	Thu Dec 13 23:43:11 2001
@@ -1,8 +1,10 @@
 ##### WIRE MODULE #####
 
-This module provides all the standard .wire commands via dcc.
-It's an encrypted partyline communication tool, compatible with wire.tcl
+This module provides all the standard .wire commands via dcc. It is an 
+encrypted partyline communication tool, compatible with wire.tcl.
 
-Put this line into your eggdrop configuration file file to load wire module:
+This module requires: encryption
+
+Put this line into your eggdrop configuration file to load the wire module:
 
 loadmodule wire
Index: eggdrop1.6/doc/settings/mod.woobie
diff -u eggdrop1.6/doc/settings/mod.woobie:1.3 eggdrop1.6/doc/settings/mod.woobie:1.4
--- eggdrop1.6/doc/settings/mod.woobie:1.3	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/mod.woobie	Thu Dec 13 23:43:11 2001
@@ -1,8 +1,10 @@
 ##### WOOBIE MODULE #####
 
-this serves absolutely no purpose and is for demonstrative purposes only. If
-you are looking for starting point in writing modules, woobie is the right thing.
+This is for demonstrative purposes only. If you are looking for starting
+point in writing modules, woobie is the right thing.
 
-Put this line into your eggdrop configuration file file to load wire module:
+This module requires: none
+
+Put this line into your eggdrop configuration file to load the woobie module:
 
 loadmodule woobie
Index: eggdrop1.6/doc/settings/tricks
diff -u eggdrop1.6/doc/settings/tricks:1.2 eggdrop1.6/doc/settings/tricks:1.3
--- eggdrop1.6/doc/settings/tricks:1.2	Sun Nov  4 22:08:27 2001
+++ eggdrop1.6/doc/settings/tricks	Thu Dec 13 23:43:11 2001
@@ -1,23 +1,24 @@
-tweaking tips for your config file
+This document contains tweaking tips for your config file.
 
-As your botnet grows bigger and you have to maintain more and more bots
-with their config files, you might render those little tweaking tips useful,
-since they can make your life configuring, maintaining and adding of bots
-lot's of easier.
+As your botnet grows bigger, and you have to maintain more and more bots
+with their config files, you might render these little tweaking tips useful.
+They can make your life configuring, maintaining and adding of bots a lot
+easier.
 
-well, here we go:
+- Config file split:
+    You can export parts of your config file to separate files. For example,
+    if you have several config files which differ from themselves only by 
+    the nickname and the used servers, you can export them to an own file 
+    and link it with the 'source' Tcl command, similar to a script. The 
+    advantage of this is that you have to edit/upload only the small file 
+    instead of the big one. This technique is also useful if you want to 
+    maintain the same channel settings, etc.
 
-- config file split
-  You can export parts of your config file to separate files. For example, if
-  you have several config files which differ from themselves only by the
-  nickname and the used servers, you can export them to an own file and link
-  it with the 'source' command, similar to a script.
-  The advance of this trick is, that you have to edit / upload only the small
-  file instead of the big one. This technique is also useful if you want to
-  maintain always the same channel settings, etc.
+- Variable usage in the config file:
+  You can use variables in your config file, since it's really just a plain 
+  Tcl file. For example, you can set 'userfile' and 'chanfile' to "yourbot.user" 
+  and "yourbot.chan" using the following method:
 
-- variable usage in the config file
-  you can use variables in your config file since it's a plain tcl file. For
-  example, you can set 'userfile' and 'chanfile' to "$myvar" and define $myvar
-  in the first line by 'set myvar "yourbotname"'. By this way, you can maintain
-  your files by changing just one line.
\ No newline at end of file
+  set myvar "yourbot"
+  set userfile "$myvar.user"
+  set chanfile "$myvar.chan"
\ No newline at end of file
Index: eggdrop1.6/eggdrop.advanced.conf
diff -u eggdrop1.6/eggdrop.advanced.conf:1.36 eggdrop1.6/eggdrop.advanced.conf:1.37
--- eggdrop1.6/eggdrop.advanced.conf:1.36	Sat Dec  8 12:16:03 2001
+++ eggdrop1.6/eggdrop.advanced.conf	Thu Dec 13 23:43:10 2001
@@ -1,11 +1,10 @@
 #! /path/to/executable/eggdrop
-# ^- Set that to the directory eggdrop is in, i.e. "#! /home/lamest/egg/eggdrop"
+# ^- This should contain a fully qualified path to your eggdrop executable.
 #
-# $Id: eggdrop.advanced.conf,v 1.36 2001/12/08 18:16:03 guppy Exp $
+# $Id: eggdrop.advanced.conf,v 1.37 2001/12/14 05:43:10 guppy Exp $
 #
-# This is a sample configuration file for your bot.  You will definitely
-# want to edit this to set up your bot. Right now, it creates a bot called
-# "LamestBot" which sits on the channel #lamest.
+# This is a sample eggdrop configuration file which includes many
+# settings that can be used to configure your bot.
 #
 # PLEASE EDIT THIS FILE COMPLETELY! YOUR BOT WILL NOT FUNCTION PROPERLY IF
 # YOU DO NOT CONFIGURE IT CORRECTLY! WE CAN NOT STRESS THIS ENOUGH!
@@ -13,63 +12,61 @@
 # NOTE: Please choose your +n (owner) users carefully! They have COMPLETE
 # access to your bot *AND* account! Only pick ones you trust!
 #
-# More options can be found in files in doc/settings/.
+# More options can be found in the files in doc/settings/.
 
 ##### GENERAL STUFF #####
 
-# the username the bot uses, this is only used if identd isn't working
-# on the machine the bot is running on.
+# This setting defines the username the bot uses on IRC. This setting has 
+# no effect if an ident daemon is running on your bot's machine.
 set username "lamest"
 
-# who's running this bot?
-set admin "Lamer <email: lamer at lamest.lame.org>"
-
-# what IRC network are you on?  this is just info to share with others on
-# your botnet, for human curiosity only.
-set network "I.didnt.edit.my.config.file.net"
-
-# what timezone is your bot in? The timezone string specifies the name of
-# the timezone and must be three or more alphabetic characters.
-#
-# ex. Central European Time(UTC+1) would be "CET"
+# This setting defines which contact person should be shown in .status,
+# /msg help, and other places. You really should include this information.
+set admin "Lamer <email: lamer at lamest.lame.org)"
+
+# This setting is used only for info to share with others on your botnet.
+# Set this to the IRC network your bot is connected to.
+set network "I.didn't.edit.my.config.file.net"
+
+# This setting defines the timezone is your bot in. It's used for internal
+# routines as well as for logfile timestamping and scripting purposes.
+# The timezone string specifies the name of the timezone and must be three
+# or more alphabetic characters.
+# E.x. Central European Time(UTC+1) should be "CET".
 set timezone "EST"
 
-# offset specifies the time value to be added to the local time to get
-# Coordinated Universal Time (UTC aka GMT).  The offset is positive if the
-# local timezone is west of the Prime Meridian and negative if it is east.
-# The value(hours) must be between 0 and 24.
-#
-# ex. if the timezone is UTC+1 the offset is -1
+
+# The offset setting specifies the time value to be added to the local time
+# to get Coordinated Universal Time (UTC aka GMT). The offset is positive if
+# the local timezone is west of the Prime Meridian and negative if it is east.
+# The value (in hours) must be between -23 and 23.
+# E.x. If the timezone is UTC+1, the offset is -1.
 set offset "5"
 
-# If you don't want to use the timezone setting for scripting purpose
-# only, but instead, everywhere possible (new), then un-comment the next line.
-#set env(TZ) "$timezone $offset"
-
-# if you're using virtual hosting (your machine has more than 1 IP), you
-# may want to specify a particular IP to bind to.  you can specify
-# either by hostname or by IP.  you may also want to set the hostname
-# here if eggdrop has trouble detecting it when it starts up.  (it will
-# let you know if it has trouble -- trust me.)
+# If you're using virtual hosting (your machine has more than 1 IP), you
+# may want to specify the particular IP to bind to. You can specify either
+# by hostname or by IP. You may also want to set the hostname here if
+# eggdrop has trouble detecting it when it starts up.
 #set my-hostname "virtual.host.com"
 #set my-ip "99.99.0.0"
 
-# if you want to have your eggdrop messages displayed in another language
-# change the below command to match your preferences. An alternative would
-# be to set the environment variable EGG_LANG to that value.
+# If you want to have your eggdrop messages displayed in a language other
+# than English, change this setting to match your preference. An alternative
+# would be to set the environment variable EGG_LANG to that value.
 #addlang "english"
 
 
 ##### LOG FILES #####
 
-# You can specify a limit on how many log files you can have.
-# At midnight every day, the old log files are renamed and a new log file begins.
-# By default, the old one is called "(logfilename).yesterday",
-# and any logfiles before yesterday are erased.
-
-# Events are logged by certain categories -- this way you can specify
-# exactly what kind of events you want sent to various logfiles.  the
-# events are:
+# Eggdrop is capable of logging various things, from channel chatter to
+# partyline commands and file transfers. Logfiles are normally
+# kept for 24 hours. Afterwards, they will be renamed to "(logfile).yesterday".
+# After 48 hours, they will be overwritten by the logfile of the next day.
+# 
+# Events are logged by certain categories. This way, you can specify
+# exactly what kind of events you want sent to various logfiles.
+# 
+# The most common log file flags are:
 #   m  private msgs/ctcps to the bot
 #   k  kicks, bans, mode changes on the channel
 #   j  joins, parts, netsplits on the channel
@@ -78,303 +75,309 @@
 #   b  information about bot linking and userfile sharing
 #   c  commands people use (via msg or dcc)
 #   x  file transfers and file-area commands
-#   r  (if use-console-r defined) EVERYTHING sent to the bot by the server
+#      r  (if use-console-r enabled) EVERYTHING sent to the bot by the server
 #   o  other: misc info, errors -- IMPORTANT STUFF
 #   w  wallops: msgs between IRCops (be sure to set the bot +w in init-server)
+#
 # There are others, but you probably shouldn't log them, it'd be rather
-# unethical ;)
+# unethical. ;) There are also eight user-defined levels (1-8) which
+# are used by Tcl scripts.
+# 
+# Each logfile belongs to a certain channel. Events of type 'k', 'j', and 'p'
+# are logged to whatever channel they happened on. Most other events are
+# currently logged to every channel. You can make a logfile belong to all
+# channels by assigning it to channel "*".
 
-# maximum number of logfiles to allow - this can be increased if needed
-# (don't decrease this)
+# This is the maximum number of logfiles allowed. This setting can be 
+# increased; however, don't decrease it.
 set max-logs 5
 
-# maximum size of your logfiles, set this to 0 to disable.
-# this only works if you have keep-all-logs 0 (OFF)
-# this value is in KiloBytes, so '550' would mean cycle logs when
-# it reaches the size of 550 KiloBytes.
+# This is the maximum size of your logfiles. Set it to 0 to disable.
+# This value is in kilobytes, so '550' would mean cycle logs when it
+# reaches the size of 550 kilobytes.
+# Note that this only works if you have keep-all-logs 0 (OFF).
 set max-logsize 0
 
-# write the logfiles and check the size every minute
-# (if max-logsize is enabled) instead of every 5minutes as before.
-# This could be good if you have had problem with the
-# logfile filling your quota or hdd or if you log +p
-# and publish it on the web and wants more up-to-date info.
-# If you are concerned with resources keep the default setting 0.
-# (although I haven't noticed anything)
+# This could be good if you have had problem with the logfile filling
+# your quota/hard disk or if you log +p and publish it to the web and
+# need more up-to-date info.
+# Note that this setting might increase the CPU usage of your bot (on
+# the other hand it will decrease your mem usage).
 set quick-logs 0
 
-# each logfile also belongs to a certain channel.  events of type 'k', 'j',
-# and 'p' are logged to whatever channel they happened on.  most other
-# events are currently logged to every channel.  you can make a logfile
-# belong to all channels by assigning it to channel "*".  there are also
-# five user-defined levels ('1'..'5') which are used by Tcl scripts.
-
-# in 'eggdrop.log' put private msgs/ctcps, commands, misc info, and
-# errors from any channel:
+# This creates a logfile named eggdrop.log containing private msgs/ctcps,
+# commands, errors, and misc. info from any channel.
 logfile mco * "logs/eggdrop.log"
-# in 'lame.log' put joins, parts, kicks, bans, and mode changes from #lamest:
-logfile jk #lamest "logs/lamest.log"
 
-# [0/1] timestamp entries in the log file? (generally a good idea)
+# This creates a logfile named lamest.log containing joins, parts,
+# netsplits, kicks, bans, mode changes, and public chat on the
+# channel #lamest. 
+logfile jpk #lamest "logs/lamest.log"
+
+# Use this feature to timestamp entries in the log file.
 set log-time 1
 
-# [0/1] keep logfiles for more than 48 hours -- instead of being called
-# "(logfilename).yesterday", the log files are named by the current date,
-# and kept around forever (eventually your directory might get full, so
-# be careful with this!)
+# If you want to keep your logfiles forever, turn this setting on. All
+# logfiles will get suffix ".[day, 2 digits][month, 3 letters][year, 4 digits]".
+# Note that your quota/hard-disk might be filled by this, so check your logfiles
+# often and download them.
 set keep-all-logs 0
 
-# if keep-all-logs is 1, this setting will define the suffix of the logfiles.
+# If keep-all-logs is 1, this setting will define the suffix of the logfiles.
 # The default will result in a suffix like "04May2000". "%Y%m%d" will produce
-# the often used yyyymmdd format. Read the strtime manpages for more options.
+# the often used yyyymmdd format. Read the strftime manpages for more options.
 # NOTE: On systems which don't support strftime, the default format will
 # be used _always_.
 set logfile-suffix ".%d%b%Y"
 
-# once a day the logfiles are switched out and started fresh --
-# this specifies when that should happen (in military time)
-# [note that a leading 0 will make Tcl think this is an octal value,
-# something you probably don't want.]
+# You can specifiy when eggdrop should switch logfiles and start fresh. You must
+# use military time for this setting. 300 is the default, and describes 00:00.
+# Note that a leading 0 will make Tcl think this is an octal value,
+# something you probably don't want.
 set switch-logfiles-at 300
 
-# [0/1] enable quiet saves? "Writing user file..." and "Writing channel file ..."
-# will not be logged if this option is enabled.
+# "Writing user file..." and "Writing channel file..." messages
+# won't be logged anymore if this option is enabled.
 set quiet-save 0
 
-# this is the default console mode -- what masters will see automatically
-# when they dcc chat with the bot (masters can alter their own console
-# flags once they connect, though) -- it uses the same event flags as
-# the log files
-# (note that the console channel is automatically set to your "primary"
-# channel -- the one you defined first in this file.  masters can change
-# their console channel with the '.console' command, however.)
+
+##### CONSOLE #####
+
+# This is the default console mode. It uses the same event flags as the log
+# files do. The console channel is automatically set to your "primary" channel,
+# which is set in the modules section of the config file. Masters can change
+# their console channel and modes with the '.console' command.
+
 set console "mkcobxs"
 
 
 ##### FILES AND DIRECTORIES #####
 
-# the userfile: where user records are stored
+# Specify here the filename your userfile should be saved as.
 set userfile "LamestBot.user"
 
-# [0/1] do you want the userlist to be sorted when saving
+# If you want your userfile to be sorted upon saving, enable this setting.
+# This causes the bot to use bit more CPU when saving the usefile.
 set sort-users 0
 
-# where the help files can be found (and there are plenty)
+# Specify here where eggdrop should look for help files.
+# Don't modify this setting unless you know what you're doing!
 set help-path "help/"
 
-# where the text files can be found (used with various dump commands)
+# Specify here where eggdrop should look for text files. This is
+# used for certain Tcl and DCC commands.
 set text-path "text/"
 
-# a good place to temporarily store files (i.e.: /tmp)
+# Set here a place to store temporary files.
 set temp-path "/tmp"
 
-# the MOTD is displayed when people dcc chat to the bot.
-# type '.help set motd' in DCC CHAT for tons of motd options.
+# The MOTD (Message Of The day) is displayed when people dcc chat or telnet
+# to the bot. Look at doc/settings.motd or type '.help set motd' in DCC 
+# CHAT or telnet connection for options.
 set motd "text/motd"
 
-# holds the banner displayed on telnet connections
+# This banner will be displayed on telnet connections.
 set telnet-banner "text/banner"
 
-##### BOTNET #####
 
-# you probably shouldn't deal with this until reading 'botnet.doc' or
-# something.  you need to know what you're doing.
+##### BOTNET/DCC/TELNET #####
 
-# if you want to use a different nickname on the botnet than you use on
-# IRC, set it here:
+# Settings in this section should be unimportant for you until you deal
+# with botnets (multiple eggdrops connected together to maximize efficiency).
+# You should read doc/BOTNET before modifying these settings.
+
+# If you want to use a different nickname on the botnet than you use on
+# IRC (i.e. if you're on an un-trusted botnet), un-comment the next line
+# and set it to the nick you would like to use.
 #set botnet-nick "LlamaBot"
 
-# what telnet port should this bot answer?
-# NOTE: if you are running more than one bot on the same machine, you will
-#   want to space the telnet ports at LEAST 5 apart... 10 is even better
-# if you would rather have one port for the botnet, and one for normal
-#   users, you will want something like this instead:
-#listen 3333 bots
-#listen 4444 users
-# NOTE: there are more options listed for the listen command in
-#   doc/tcl-commands.doc
+# This opens a telnet port by which you and other bots can
+# interact with the eggdrop by telneting in.
+# 
+# There are more options for the listen command in doc/tcl-commands.doc.
+# Note, if you are running more than one bot on the same machine, you will
+# want to space the telnet ports at LEAST 5 apart. 10 is even better.
+# 
+# Valid ports are typically anything between 1025 and 65535 assuming the 
+# port is not already in use.
+#
+# If you would like the bot to listen for users and bots in separate ports,
+# use the following format.
+# 
+# listen 3333 bots
+# listen 4444 users
+#
+# If you wish to use only one port, use this format:
 listen 3333 all
 
-# [0/1] This setting will drop telnet connections not matching a known host
-# It greatly improves protection from IRCOPs, but makes it impossible
-# for NOIRC bots to add hosts or have NEW as a valid login
+# This setting defines whether or not people can boot users on the eggdrop
+# from other bots in your botnet. Valid settings are:
+#    0 - allow *no* outside boots
+#    1 - allow boots from sharebots
+#    2 - allow any boots
+set remote-boots 2
+
+# This setting prohibits remote bots from telling your eggdrop to unlink from 
+# share bots.
+set share-unlinks 1
+
+ This setting will drop telnet connections not matching a known host. It
+# greatly improves protection from IRCOps, but makes it impossible for limbo
+# bots to add hosts or have NEW as a valid login.
 set protect-telnet 0
 
-# [0/1] This setting will make the bot ignore DCC chat requests which appear to
+# This setting will make the bot ignore DCC chat requests which appear to
 # have bogus information on the grounds that the user may have been trying
 # to make the bot connect to somewhere that will get it into trouble, or
 # that the user has a broken client (like mIRC tends to do), in which case
 # the connect wouldn't work anyway.  It's suggested that you turn this on.
 set dcc-sanitycheck 0
 
-# and a timeout value for ident lookups would help (seconds)
+# This settings defines a time in seconds that the bot should wait before
+# a dcc chat, telnet, or relay connection times out.
 set ident-timeout 5
 
-# [0/1] users with the +o (global or channel op) flag will still need the +p
-# (party line) flag to join the dcc chat party line?
+# Define here whether or not a +o user still needs the +p flag to dcc the bot.
 set require-p 0
 
-# [0/1] allow people to telnet in, type 'NEW', and become a new user?
-# (If you set this to 1, you must set protect-telnet 0)
-set open-telnets 0
-
-# [0/1] Display 'Nickname.' instead of identifying ourselves when people
-# telnet in. Set to 1 to only display Nickname.
-# (useful if someone portscans your machine, they wont know we're here)
+# If you don't want eggdrop to identify itself as an eggdrop on a telnet connection, 
+# set this setting to 1. Eggdrop will display 'Nickname' instead.
 set stealth-telnets 0
 
-# [0/1] Display a banner when people telnet in.
+# If you want eggdrop to display a banner when telneting in, set this setting
+# to 1. The telnet banner is set by 'set telnet-banner'.
 set use-telnet-banner 0
 
-# How long (in seconds) should I wait for a connect (dcc chat, telnet,
-# relay, etc) before it times out?
+# This settings defines a time in seconds that the bot should wait before
+# a dcc chat, telnet, or relay connection times out.
 set connect-timeout 15
 
-# number of messages / lines from a user on the partyline (dcc, telnet)  before
-# they are considered to be flooding (and therefore get booted)
+# Specify here the number of lines to accept from a user on the partyline
+# within 10 seconds before they are considered to be flooding and therefore
+# get booted.
 set dcc-flood-thr 3
 
-# how many telnet connection attempt in how many seconds from the same
-# host constitutes a flood?
+# Define here how many telnet connection attempts in how many seconds from
+# the same host constitute a flood. The correct format is Attempts:Seconds.
 set telnet-flood 5:60
 
-# [0/1] apply telnet flood protection for everyone?
-# set this to 0 if you want to exempt +f users from telnet flood protection
+# If you want telnet-flood to apply even to +f users, set this setting to 1.
 set paranoid-telnet-flood 1
 
-# how long should I wait (seconds) before giving up on hostname/address
-# lookup? (you might want to increase this if you are on a slow network).
+# Set here the amount of seconds before giving up on hostname/address
+# lookup (you might want to increase this if you are on a slow network).
 set resolve-timeout 15
 
 
 ##### MORE ADVANCED STUFF #####
 
-# temporary ignores will last how many minutes?
+# Set the time in minutes that temporary ignores should last.
 set ignore-time 15
 
-# this setting affects what part of the hour the 'hourly' calls occur
-# on the bot, this includes such things as note notifying,
-# You can change that here (for example, "15" means to
-# notify every hour at 15 minutes past the hour)
-# this now includes when the bot will save its userfile
+# Define here what eggdrop considers 'hourly'. All calls to it, including such
+# things as note notifying or userfile saving are affected by this. For example:
+# 
+# set hourly-updates 15
+# 
+# The bot will save its userfile 15 minutes past every hour.
 set hourly-updates 00
 
-# the following user(s) will ALWAYS have the owner (+n) flag (You really
-# should change this default value)
+# Un-comment the next line and set the list of owners of the bot.
+# You NEED to change this setting.
 #set owner "MrLame, MrsLame"
 
-# who should I send a note to when I learn new users?
+# Who should a note be sent to when new users are learned?
 set notify-newusers "$owner"
 
-# what flags should new users get as a default?
-# check '.help whois' on the partyline (dcc chat, telnet) for tons of
-# options.
+# Enter the flags that all new users should get by default.
+# See '.help whois' on the partyline for a list of flags and
+# their descriptions.
 set default-flags "hp"
 
-# [0/1/2] allow people from other bots (in your bot-net) to boot people off
-# your bot's party line?
-# values:
-#   0 - allow *no* outside boots
-#   1 - allow boots from sharebots
-#   2 - allow any boots
-set remote-boots 2
-
-# [0/1] if you don't want people to unlink your share bots from remote bots
-# set this to 0
-set share-unlinks 1
-
-# to enable the 'tcl' and 'set' command (let owners directly execute
-# Tcl commands)? - a security risk!!
+# Comment these two lines if you wish to enable the .tcl and .set commands.
 # If you select your owners wisely, you should be okay enabling these.
-# to enable, comment these two lines out
-# (In previous versions, this was enabled by default in eggdrop.h)
 unbind dcc n tcl *dcc:tcl
 unbind dcc n set *dcc:set
 
-# [0/1/2] only let permanent owners use .tcl/.set if bound? then set it to 1
-# moreover only let permanent owners use .dump? then set it to 2
-# (the people must set the $owner variable)
+# If you enable this setting, only permanent owners (owner setting) will be
+# able to use .tcl and .set. Moreover, if you want only let permanent owners 
+# use .dump, then set this to 2.
 set must-be-owner 1
 
-# maximum number of dcc connections you will allow - you can increase this
-# later, but never decrease it, 50 seems to be enough for everybody
+# Set here the maximum number of dcc connections you will allow. You can
+# increase this later, but never decrease it.
 set max-dcc 50
 
-# this setting is so that people can't send fake ports to your bot when
-# they try to dcc it. irc clients should never use a port below 1024 and
-# well 65535 is the highest port possible. this setting is used for telnet
-# too.
-set dcc-portrange 1024:65535
-
-# If a bot connects which already seems to be connected, I wait
-# dupwait-timeout seconds before I check again and then finally reject
-# the bot. This is useful to stop hubs from rejecting bots that actually
-# have already disconnected from another hub, but the disconnect information
-# has not yet spread over the botnet due to lag.
+# If your eggdrop rejects bots that actually have already disconnected from
+# another hub, but the disconnect information has not yet spread over the
+# botnet due to lag, use this setting. The bot will wait dupwait-timeout 
+# seconds before it checks again and then finally reject the bot.
 set dupwait-timeout 5
 
 
-
 ########## MODULES ##########
 
-# below are various settings for the modules available with eggdrop,
-# PLEASE EDIT THEM CAREFULLY, READ THEM, even if you're an old hand
-# at eggdrop, lots of things have changed slightly
-
-# this is the directory to look for the modules in, if you run the
-# bot in the compilation directories you will want to set this to ""
-# if you use 'make install' (like all good kiddies do ;) this is a fine
-# default, otherwise, use your head :)
+# Below are various settings for the modules available with eggdrop.
+# PLEASE READ AND EDIT THEM CAREFULLY, even if you're an old hand at
+# eggdrop, things change.
+
+# This path specifies the path were eggdrop should look for its modules.
+# If you run the bot from the compilation directory, you will want to set
+# this to "". If you use 'make install' (like all good kiddies do ;), this
+# is a fine default. Otherwise, use your head :)
 set mod-path "modules/"
 
 
-#### DNS MODULE #####
+#### DNS MODULE ####
 
-# this module provides asynchronous dns support. This will avoid long
+# This module provides asynchronous dns support. This will avoid long
 # periods where the bot just hangs there, waiting for a hostname to
-# resolve, which often let it timeout on all other connections.
+# resolve, which will often let it timeout on all other connections.
 loadmodule dns
 
-##### CHANNELS MODULE #####
+#### CHANNELS MODULE ####
 
-# this next module provides channel related support for the bot, without
-# it, it will just sit on irc, it can respond to msg & ctcp commands, but
-# that's all
+# This module provides channel related support for the bot. Without it,
+# you wont be able to make the bot join a channel or save channel
+# specific userfile information.
 loadmodule channels
 
-# the chanfile: where dynamic channel settings are stored
+# Enter here the filename where dynamic channel settings are stored.
 set chanfile "LamestBot.chan"
 
-# temporary bans will last how many minutes? if set to 0, bot never removes
-# them.
+# Set here how long temporary bans will last (in minutes). If you
+# set this setting to 0, the bot will never remove them.
 set ban-time 120
 
-# temporary exemptions (+e modes) will last how many minutes? if set to 0,
-# bot never removes them. This is an IRCNET feature. The bot will check the
-# exempts every X minutes, but will not remove the exempt if a ban is set on
-# the channel that matches that exempt. Once the ban is removed then the
-# exempt will be removed the next time the bot checks.
+# Set here how long temporary exempts will last (in minutes). If you
+# set this setting to 0, the bot will never remove them. The bot will
+# check the exempts every X minutes, but will not remove the exempt if
+# a ban is set on the channel that matches that exempt. Once the ban is
+# removed, then the exempt will be removed the next time the bot checks.
+# Please note that this is an IRCnet feature.
 set exempt-time 60
 
-# temporary invitations (+I modes) will last how many minutes? if set to
-# 0, bot never removes them. This is an IRCNET feature. The bot will check the
-# invites every X minutes, but will not remove them if the channel is +i. Once
-# the channel is -i then the bot will remove then invite mode next time it
-# checks this counter
+# Set here how long temporary invites will last (in minutes). If you
+# set this setting to 0, the bot will never remove them.
+# The bot will check the invites every X minutes, but will not remove
+# the invite if a channel is set to +i. Once the channel is -i then
+# the invite will be removed the next time the bot checks.
+# Please note that this is an IRCnet feature.
 set invite-time 60
 
-# [0/1] expire bans/exempts/invites set by other opped bots on the channel?
-# set force-expire 0
+# Set this setting to 1 if you want your bot to expire bans/exempts/invites set
+# by other opped bots on the channel.
+set force-expire 0
 
-# [0/1] share user greets with other bots on the channel if sharing user data?
+# Set this setting to 1 if you want your bot to share user greets with other
+# bots on the channel if sharing user data.
 set share-greet 0
 
-# [0/1] allow users to store an info line?
+# Set this setting to 1 if you want to allow users to store an info line.
 set use-info 1
 
-# these settings are used as default values when you
-# .+chan #chan or .tcl channel add #chan
-# look in the section above for explanation on every option
+# The following settings are used as default values when you .+chan #chan or .tcl
+# channel add #chan. Look in the section below for explanation of every option.
 
 set global-flood-chan 10:60
 set global-flood-deop 3:10
@@ -382,9 +385,7 @@
 set global-flood-join 5:60
 set global-flood-ctcp 3:60
 set global-flood-nick 5:60
-
 set global-aop-delay 5:30
-
 set global-idle-kick 0
 set global-chanmode "nt"
 set global-stopnethack-mode 0
@@ -405,9 +406,9 @@
         +userinvites
 }
 
-# do this for each channel you wish to sit on:
-# NOTE: for some reason Tcl won't let you put comments inside { } -- so
-#   don't try it, cos it'll mess up your channel definition
+# Add each static channel you want your bot to sit in using this command.
+# There are many different possible settings you can insert into this
+# command, which are explained below.
 
 channel add #lamest {
   chanmode "+nt-likm"
@@ -428,678 +429,788 @@
   flood-nick 5:60
 }
 
-# the things inside the { } are CHANNEL OPTIONS -- they can be set within
-# the "channel add" command, or by using a "channel set" command as in the
-# examples below.  they list all the options you can set for a channel.
-
-# chanmode
-#   what modes will be enforced?  '+' modes will always be kept on, '-' modes
-#   will always be kept off
-# idle-kick
-#   kick channel members after how many minutes of being idle?
-#   (leave out to disable, or set to 0)
-
-#   stopnethack-mode
-#     de-op anyone who enters the channel with serverops
+# chanmode +/-<modes>
+#    This setting makes the bot enforce channel modes. It will always add
+#    the +<modes> and remove the -<modes> modes.
+# idle-kick 0
+#    This setting will make the bot check every minute for idle
+#    users. Set this to 0 to disable idle check.
+#
+# stopnethack-mode 0
+#    This setting will make the bot de-op anyone who enters the channel
+#    with serverops. There're seven different modes for this settings:
 #       0 turn off,
-#       1 isoptest (allow serverop if registered op),
+#      1 isoptest (allow serverop if registered op)
 #       2 wasoptest (allow serverop if op before split)
 #       3 allow serverop if isop or wasop
-#       4 allow serverop if isop and wasop
-#       5 if channel -bitch: see stopnethack-mode 3
-#         if channel +bitch: see stopnethack-mode 1
-#       6 if channel -bitch: see stopnethack-mode 2
-#         if channel +bitch: see stopnethack-mode 4
-
-#   revenge-mode
-#     defines how the bot should punish bad users when revenging.
-#     default is 1.
-#       0 for deop 
-#       1 for deop and +d 
-#       2 for deop, +d and kick
-#       3 for deop, chattr +d, kick and ban
-
+#      4 allow serverop if isop and wasop.
+#      5 If the channel is -bitch, see stopnethack-mode 3
+#        If the channel is +bitch, see stopnethack-mode 1
+#      6 If the channel is -bitch, see stopnethack-mode 2
+#        If the channel is +bitch, see stopnethack-mode 4
+#
+# revenge-mode 1
+#   This settings defines how the bot should punish bad users when
+#   revenging. There are four possible settings:
+#     0 Deop the user.
+#     1 Deop the user and give them the +d flag for the channel.
+#     2 Deop the user, give them the +d flag for the channel, and kick them.
+#     3 Deop the user, give them the +d flag for the channel, kick, and ban them.
+#
 # aop-delay (minimum:maximum)
-# for autoop and autovoice
-# aop-delay 0                   no autoopdelay
-# aop-delay x or aop-delay x:x  x sec. autoopdelay
-# aop-delay x:y                 random delay
-# if a autoopped user joined during a other delayed autoop is pending,
-# the bot will sent both autoop based on the last-joined-user-delay-time,
-# probable in only one line.
-
-# need-op
-#   script to run (if any) when the bot needs to be op'd on this channel
-# need-invite
-#   script to run (if any) when the bot gets locked out of the channel
-#   because the channel is +i
-# need-key
-#   script to run (if any) when the bot gets locked out of the channel
-#   because it doesn't have the channel key
-# need-unban
-#   script to run (if any) when the bot gets banned from this channel
-# need-limit
-#   script to run (if any) when the bot gets locked out of the channel
-#   because the channel limit is full
-# flood-chan (number:seconds)
-#   how many channel messages in how many seconds is a flood
-#   not specifying or using number = 0 will not check chan floods!
-# flood-ctcp (number:seconds)
-#   how many channel messages in how many seconds is a flood
-#   not specifying or using number = 0 will not check ctcp floods!
-# flood-deop (number:seconds)
-#   how many deops in how many seconds is a mass de-op
-#   not specifying or using number = 0 will not check de-op floods!
-# flood-kick (number:seconds)
-#   how many kicks in how many seconds is a mass kick?
-#   not specifying or using number = 0 will not check mass kicks!
-# flood-join (number:seconds)
-#   how many joins/nick changes in how many seconds is a join flood?
-#   not specifying or using number = 0 will not check join floods!
-
-# note that "need-op", "need-invite", etc, are limited to 120 characters,
-# so if you want to so something more complicated, just write a proc,
-# and make them call your proc.
-
-# there are also a lot of options that can be turned on or off for each
-# channel.  to turn an option on, put a + in front of it.  to turn it off,
-# put a - in front of it.  i.e., to have auto-op, put:
-#   +autoop
-# to turn it off, put:
-#   -autoop
+# This is used for autoop and autovoice. If an op or voice joins a channel
+# while another op or voice is pending, the bot will attempt to put both
+# modes on one line.
+#   aop-delay 0   No delay is used.
+#   aop-delay X   An X second delay is used.
+#   aop-delay X:Y A random delay between X and Y is used.
+#
+# need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it does not have ops. This must be shorter than 120 characters.
+#    If you use scripts like getops.tcl or botnetop.tcl, you don't need
+#    to set this setting.
+#
+# need-invite { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs an invite to the channel. This must be shorter than 120
+#    characters. If you use scripts like getops.tcl or botnetop.tcl, you
+#    don't need to set this setting.
+#
+# need-key { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs the key to the channel. This must be shorter than 120
+#    characters. If you use scripts like getops.tcl or botnetop.tcl, you
+#    don't need to set this setting
+#
+# need-unban { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs to be unbanned on the channel. This must be shorter than
+#    120 characters. If you use scripts like getops.tcl or botnetop.tcl,
+#    you don't need to set this setting
+#
+# need-limit { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs the limit to be raised on the channel. This must be
+#    shorter than 120 characters. If you use scripts like getops.tcl or
+#    botnetop.tcl, you don't need to set this setting
+#
+# flood-chan 10:60
+#    Set here how many channel messages in how many seconds from one
+#    host constitutes a flood. Setting this to 0 or 0:0 disables
+#    flood protection for the channel.
+#
+# flood-deop 3:10
+#    Set here how many deops in how many seconds from one host constitutes
+#    a flood. Setting this to 0 or 0:0 disables deop flood protection for
+#    the channel.
+#
+# flood-kick 3:10
+#    Set here how many kicks in how many seconds from one host constitutes
+#    a flood. Setting this to 0 or 0:0 disables kick flood protection for
+#    the channel.
+#
+# flood-join 5:60
+#    Set here how many joins in how many seconds from one host constitutes
+#    a flood. Setting this to 0 or 0:0 disables join flood protection for
+#    the channel.
+#
+# flood-ctcp 3:60
+#    Set here how many channel ctcps in how many seconds from one host
+#    constitutes a flood. Setting this to 0 or 0:0 disables ctcp flood
+#    protection for the channel.
+#
+# flood-nick 5:60
+#    Set here how many nick changes in how many seconds from one host
+#    constitutes a flood. Setting this to 0 or 0:0 disables nick flood
+#    protection for the channel.
+#
 
-#   when a ban is set, kick people who are on the channel and match the
-#   new ban?  (i.e., they were on the channel before the ban)
-channel set #lamest +enforcebans
+# There are many different options for channels which you can
+# define. They can be enabled or disabled by a plus or minus
+# in front of them.
+#
+# A complete list of all available channel settings:
+#
+# enforcebans
+#    When a ban is set, kick people who are on the channel and match
+#    the ban?
+#
+# dynamicbans
+#    Only activate bans on the channel when necessary? This keeps
+#    the channel's ban list from getting excessively long. The bot
+#    still remembers every ban, but it only activates a ban on the
+#    channel when it sees someone join who matches that ban.
+#
+# userbans
+#    Allow bans to be made by users directly? If turned off, the bot
+#    will require all bans to be made through the bot's console.
+#
+# dynamicexempts
+#    Only activate exempts on the channel when necessary? This keeps
+#    the channel's exempt list from getting excessively long. The bot
+#    still remembers every exempt, but it only activates a exempt on
+#    the channel when it sees a ban set that matches the exempt. The
+#    exempt remains active on the channel for as long as the ban is
+#    still active.
+#
+# userexempts
+#    Allow exempts to be made by users directly? If turned off, the
+#    bot will require all exempts to be made through the bot's console.
+#
+# dynamicinvites
+#    Only activate invites on the channel when necessary? This keeps
+#    the channel's invite list from getting excessively long. The bot
+#    still remembers every invite, but the invites are only activated
+#    when the channel is set to invite only and a user joins after
+#    requesting an invite. Once set, the invite remains until the
+#    channel goes to -i.
+#
+# userinvites
+#    Allow invites to be made by users directly? If turned off, the
+#    bot will require all invites to be made through the bot's console.
+#
+# autop
+#    Op users with the +o flag as soon as they join the channel?
+#    This is insecure and not recommended.
+#
+# bitch
+#    Only let users with +o) flag be opped on the channel?
+#
+# greet
+#    Say a user's info line when they join the channel?
+#
+# protectops
+#    Re-op a user with the +o flag if they get deopped?
+#
+# protectfriends
+#    Re-op a user with the +f flag if they get deopped?
+#
+# statuslog
+#    Log the channel status line every 5 minutes? This shows the bot's
+#    status on the channel (op, voice, etc.), The channel's modes, and
+#    the number of +m/+o/+v/+n/+b/+e/+I users on the channel. A sample 
+#    status line follows:
+#      
+#    [01:40] @#lamest (+istn) : [m/1 o/1 v/4 n/7 b/1 e/5 I/7]
+#
+# revenge
+#    Remember people who deop/kick/ban the bot, valid ops, or friends
+#    and punish them? Users with the +f flag are exempt from revenge.
+#
+# revengebot
+#    This is similar to to the 'revenge' option, but it only triggers
+#    if a bot gets deopped, kicked or banned.
+#
+# autovoice
+#    Voice users with the +v flag when they join the channel?
+#
+# secret
+#    Prevent this channel from being listed on the botnet?
+#
+# shared
+#    Share channel-related user info for this channel?
+#
+# cycle
+#    Cycle the channel when it has no ops?
+#
+# dontkickops
+#    Do you want the bot not to be able to kick users who have the +o 
+#    flag, letting them kick-flood for instance to protect the channel
+#    against clone attacks.
+#
+# inactive
+#    This prevents the bot from joining the channel (or makes it leave
+#    the channel if it is already there). It can be useful to make the
+#    bot leave a channel without loosing it's settings, channel-specific
+#    user flags, channel bans, and without affecting sharing.
+#
+# seen
+#    Respond to seen requests in the channel?  The seen module must be
+#    loaded for this to work.
+#
+# nodesynch
+#    Allow non-ops to perform channel modes? This can stop the bot from
+#    fighting with services such as ChanServ, or from kicking IRCops when
+#    setting channel modes without having ops.
 
-#   Only activate bans on the channel when necessary?  (This keeps the
-#   channel's ban list from getting excessively long.
-#   The bot still remembers every ban, but it only activates a ban on
-#   the channel when it sees someone join who matches that ban.)
+channel set #lamest +enforcebans
 channel set #lamest +dynamicbans
-
-#   allow bans to be made by users directly?  (if turned off, the bot will
-#   require all bans to be made through the bot's console)
 channel set #lamest +userbans
-
-#   only activate exempts on the channel when necessary?  (this keeps the
-#   channel's exempt list from getting excessively long.  the bot still
-#   remembers every exempt, but it only activates a exempt on the channel
-#   when it sees a ban set matching the exempt. The exempt remains active
-#   on the channel for as long as the ban is still active.
 channel set #lamest +dynamicexempts
-
-#   allow exempts to be made by users directly?  (if turned off, the bot will
-#   require all exempts to be made through the bot's console)
 channel set #lamest +userexempts
-
-#   only activate invites on the channel when necessary?  (this keeps the
-#   channel's invite list from getting excessively long.  the bot still
-#   remembers every invite, but the invites are only activated when the
-#   channel is set to invite only and a user joins after requesting an
-#   invite. Once set the invite remains until the channel goes to -i
 channel set #lamest +dynamicinvites
-
-#   allow invites to be made by users directly?  (if turned off, the bot will
-#   require all invites to be made through the bot's console)
 channel set #lamest +userinvites
-
-#   op users with the +o (op) flag as soon as they join the channel?
-#   (hint: this is a BAD IDEA)
-channel set #lamest -autoop
-
-#   only let users with +o (op) flag be channel ops?
-channel set #lamest -bitch
-
-#   say a user's info line when they join the channel?
 channel set #lamest +greet
-
-#   re-op a user with the +o (op) flag if they get deopped?
 channel set #lamest +protectops
-
-#   re-op a user with the +f (friend) flag if they get deopped?
 channel set #lamest +protectfriends
-
-#   log the channel status line every 5 minutes? (some people think
-#   it's annoying; I think it's neat)
 channel set #lamest +statuslog
-
-#   remember people who deop/kick/ban bots, valid ops or friends, and punish them?
-#   users with +f (friend) flag are exempt from revenge
 channel set #lamest +revenge
-
-#   this works similar to revenge, but it triggers only for valid bots and
-#   allows the deop or kick of an op
 channel set #lamest +revengebot
-
-#   voice users with +v (voice) flag when they join the channel?
 channel set #lamest +autovoice
-
-#   prevent this channel from being listed on the botnet?  (for paranoid
-#   people)
-channel set #lamest -secret
-
-#   share user channel info for this channel?
-channel set #lamest -shared
-
-#   cycle the channel when it becomes op-less?
 channel set #lamest +cycle
-
-#   do you want the bot not to be able to kick +o flag users ?
-#   letting them kick-flood for instance, to protect the channel against
-#   clone attacks
 channel set #lamest +dontkickops
+channel set #lamest -autoop
+channel set #lamest -bitch
+channel set #lamest -secret
+channel set #lamest -shared
 
-#   prevents the bot from joining the channel (or makes it leave the channel
-#   if it is already there).
-#   Can be useful to make the bot leave a channel without loosing it's
-#   settings (flood settings, all these "channel set" settings), user flags
-#   for this channel, bans for this channel, and without affecting any
-#   sharing
-channel set #lamest -inactive
-
-#   respond to seen requests in the channel?  (seen module must be loaded)
-channel set #lamest -seen
-
-#   allow non-ops to perform channel modes?  (Stops bot from
-#   fighting with services such as ChanServ)
-channel set #lamest +nodesynch
-
+# Here is a shorter example:
+#
+#  channel add #botcentral {
+#    chanmode "+mntisl 1"
+#    idle-kick 1
+#  }
+#  channel set #botcentral +bitch +enforcebans -greet +revenge
 
-##### SERVER MODULE #####
 
-# this provides the core server support (removing this is equivalent to
-# the old NO_IRC define)
+#### SERVER MODULE ####
+
+# This module provides the core server support. You have to load this
+# if you want your bot to come on IRC. Not loading this is equivalent
+# to the old NO_IRC define.
 loadmodule server
 
-# [0/1/2/3/4/5] What is your network?
-# 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
-# 4 = Efnet +e/+I hybrid, 5 = Others
+# What is your network?
+#   0 = EFnet (non +e/+I hybrid)
+#   1 = IRCnet
+#   2 = Undernet
+#   3 = DALnet
+#   4 = EFnet +e/+I hybrid
+#   5 = Others
 set net-type 0
 
-##### variables:
-# the nick of the bot, that which it uses on IRC, and on the botnet
-# unless you specify a separate botnet-nick
+# Set the nick the bot uses on IRC, and on the botnet
+# unless you specify a separate botnet-nick, here.
+
 set nick "Lamestbot"
 
-# an alternative nick to use if the nick specified by 'set nick' is
-# unavailable. All '?' characters will be replaced by a random number.
-set altnick "Llamabot"
+# Set the alternative nick which the bot uses on IRC if the nick specified
+# by 'set nick' is unavailable. All '?' characters will be replaced by random
+# numbers.
+
+set altnick "Llamab?t"
 
-# what to display in the real-name field for the bot
+# Set what should be displayed in the real-name field for the bot on IRC.
 set realname "/msg LamestBot hello"
 
-# script to run (if any) when first connecting to a server
+# Set here a script to run (if any) when first connecting to a server.
 set init-server { putserv "MODE $botnick +i-ws" }
 
-# if no port is specified on a .jump, which port should I use?
+# Set the default port which should be used if none is specified with
+# '.jump' or in 'set servers'.
 set default-port 6667
 
-# the server list -- the bot will start at the first server listed, and cycle
-# through them whenever it's disconnected
-# (please note: you need to change these servers to YOUR network's servers)
+# This is the bot's server list. The bot will start at the first server listed, 
+# and cycle through them whenever it gets disconnected. You need to change these 
+# servers to YOUR network's servers.
 set servers {
   you.need.to.change.this:6667
+  another.example.com:7000
 }
 
-# [0/1] if the bot's nickname is changed (for example, if the intended
-# nickname is already in use) keep trying to get the nick back?
+# This setting makes the bot try to get his original nickname back if its
+# primary nickname is already in use.
 set keep-nick 1
 
-# [0/1] if this is set, a leading '~' on user at hosts WON'T be stripped off
+# Set this to 1 if you don't want your the bot to strip a leading '~'
+# on user at hosts.
 set strict-host 0
 
-# [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
-# Normally it tells the DCC user that the CHAT or SEND has been rejected
-# because they don't have access, but sometimes IRC server operators
-# detect bots that way.
+# This setting makes the bot squelch the error message when rejecting a DCC
+# CHAT or SEND. Normally it tells the DCC user that the CHAT or SEND has
+# been rejected because they don't have access.
+# Please note, sometimes IRC server operators detect bots that way.
 set quiet-reject 1
 
-# [0/1] answer lower case ctcps (non rfc compliant)
-# mIRC will do this, most other clients will NOT
+# If you want your bot to answer lower case ctcp requests (non rfc-
+# compliant), set this setting to 1. mIRC will do this, most other
+# clients will not.
 set lowercase-ctcp 0
 
-# answer HOW MANY stacked ctcps at once
+# Set how many ctcps should be answered at once.
 set answer-ctcp 3
 
-# setting any of the following with how many == 0 will turn them off
-# how many msgs in how many seconds from the same host constitutes a flood?
+# Set here how many msgs in how many seconds from one host constitutes
+# a flood. If you set this to 0:0, msg flood protection will be disabled.
 set flood-msg 5:60
-# how many CTCPs in how many seconds?
+
+# Set here how many ctcps in how many seconds from one host constitutes
+# a flood. If you set this to 0:0, ctcp flood protection will be disabled.
 set flood-ctcp 3:60
 
-# [0/1] even if all the servers are down, cycle forever and keep trying to
-# connect?
+# This settings makes the bot cycle forever through the server list until
+# it successfully connects to one.
 set never-give-up 1
 
-# [0/1] If this setting is 0 then the eggdrop keeps a separate list of the names
-# irc servers call themselves, retaining what you entered in the config file.
-# setting it to 1 will cause the bot to replace your entry with what
-# the server actually calls itself
+# Often, IRC servers call themselves a name other than their actual
+# hostname. If you want eggdrop to replace your entry in the config
+# file with this name, set this to 1. If you set this setting to 0,
+# eggdrop will keep a separate list of what IRC servers call themselves.
 set strict-servernames 0
 
-# number of seconds to wait between each server connect (0 = no wait)
-# useful for preventing ircu throttling
-# setting this too low could make your server admins *very* unhappy
+# This setting defines how long eggdrop should wait before moving from one
+# server to another on disconnect. If you set 0 here, eggdrop will not wait
+# at all and will connect instantly. Setting this too low could result in
+# your bot being K:Lined.
 set server-cycle-wait 60
 
-# how many seconds to wait for a response when connecting to a server
-# before giving up and moving on?
+# Set here how long eggdrop should wait for a response when connecting to a
+# server before giving up and moving on to next server.
 set server-timeout 60
 
-# if the number of servers on the net gets below this number, it will
-# jump to a new server (i.e., it will assume it's on the losing end of a
-# netsplit) -- set to 0 to turn off
-# [most irc networks use TS or ND now, so it's to your advantage to turn
-# this off]
+# If the number of servers on the net gets below this number, the bot
+# will jump to a new server (it will assume it's on the losing end of
+# a netsplit). Set this to 0 to turn off. If your bot is running on
+# any major IRC network, this should probably be turned off.
 set servlimit 0
 
-# [0/1] check for stoned servers? (i.e. Where the server connection has
-# died, but eggdrop hasn't been notified yet).
+# Set this to 1 if eggdrop should check for stoned servers? (where the
+# server connection has died, but eggdrop hasn't been notified yet).
 set check-stoned 1
 
-# [0/1] enable console mode 'r'?  this mode shows every raw message from the
-# server to owners with console 'r' selected -- will take a bit more CPU.
-# NOTE: This is a large security hole, allowing people to see mis-sent
-#       messages to the bot containing passwords
-# This is now restricted to +n users only. Please choose your owners with care.
+# This setting allows you the logging of all information received from the
+# server via console mode 'r'.
+# NOTE: This is a large security hole, allowing people to see user passwords.
+# This is now restricted to +n users only. Please choose your owners with
+# care.
 set use-console-r 0
 
-# [0/1] enable logging of all information sent *to* a server, via console mode 'v'
+# This setting allows you the logging of all information sent to the server
+# via console mode 'v'.
 # NOTE: This is a large security hole, allowing people to see passwords.
-# This is now restricted to +n users only. Please choose your owners with care.
+# This is now restricted to +n users only. Please choose your owners with
+# care.
 set debug-output 0
 
-# [0/1] exit if the server sends a ERROR message?
+# If you want your bot to exit the server if it receives an ERROR message,
+# set this to 1.
 set serverror-quit 1
 
-# maximum number of lines to queue to the server.
-# if you're going to dump large chunks of text to people over irc,  you
-# will probably want to raise this -- most people are fine at 300 though
+# Set here the maximum number of lines to queue to the server. If you're
+# going to dump large chunks of text to people over IRC, you will probably
+# want to raise this. 300 is fine for most people though.
 set max-queue-msg 300
 
-# [0/1] trigger bindings for ignored users?
+# If you want eggdrop to trigger binds for ignored users, set this to 1.
 set trigger-on-ignore 0
 
-# [0/1] allow a msg being twice in a queue?
+# Allow identical messages in the mode queue?
 set double-mode 0
+
+# Allow identical messages in the server queue?
 set double-server 0
+
+# Allow identical messages in the help queue?
 set double-help 0
 
-# [0/1/2] do you want the bot to optimize the kicking queues? Set to 2 if you
-# want the bot to change queues if somebody parts or changes nickname.
-# ATTENTION: Setting 2 is very CPU intensive
+# This optimizes the kick queue. It also traces nick changes and parts in
+# the channel and changes the kick queue accordingly. There are three
+# different options for this setting:
+#   0 = Turn it off.
+#   1 = Optimize the kick queue by summarizing kicks.
+#   2 = Trace nick changes and parts on the channel and change the queue
+#       accordingly. For example, bot will not try to kick users who have
+#       already parted the channel.
+# ATTENTION: Setting 2 is very CPU intensive.
 set optimize-kicks 1
 
-##### SERVER MODULE - net-type 5 specific features (other networks) #####
+### SERVER MODULE - OTHER NETWORKS (net-type 5) ###
 
-# [0/1] some nets use umode +r to mean a restricted connection. If this is your
-# case, and you want your bot to leave restricted servers and jump to the
-# next one on his server list, then set it to 1.
-# Automatically set to 0 for net-type 0/2/3/4, set to 1 for net-type 1.
-# Only use this if you set net-type 5
+# This settings defines how umode +r is understood by eggdrop. Some
+# networks use +r to indicate a restricted connection. If this is your
+# case, and you want your bot to leave restricted servers and jump to
+# the next server on its list, then set it to 1.
 #set check-mode-r 1
 
-# This variable sets the maximum nick length allowed on the network. Most
-# only support 9. The maximum supported by eggdrop is 32.
+# This setting allows you to specify the maximum nick-length supported by
+# your network. The default setting is 9. The maximum supported length by
+# eggdrop is 32.
 #set nick-len 9
 
-##### CTCP MODULE #####
+#### CTCP MODULE ####
 
-# this provides the normal ctcp replies that you'd expect *RECOMMENDED*
+# This module provides the normal ctcp replies that you'd expect.
+# Without it loaded, CTCP CHAT will not work. The server module
+# is required for this module to function.
 loadmodule ctcp
 
-# several variables exist to better blend your egg in.  they are
-# ctcp-version, ctcp-finger, and ctcp-userinfo.  you can use set
-# to set them to values you like.
-
-# [0/1/2] 0: normal behavior. 1: bot ignores all CTCPs, except for CTCP
-# CHATs & PINGs requested by +o flag users. 2: bot doesn't answer more
-# than C CTCPs in S seconds.
-# C/S are defined by the set flood-ctcp C:S (cf. server module)
+# Set here how the ctcp module should answer ctcps. There are 3 possible
+# operating modes:
+#   0: Normal behavior is used.
+#   1: The bot ignores all ctcps, except for CHAT and PING requests
+#      by users with the +o flag.
+#   2: Normal behavior is used, however the bot will not answer more
+#      than X ctcps in Y seconds (defined by 'set flood-ctcp').
 set ctcp-mode 0
 
+# There are also several variables to help make your bot less noticeable.
+# They are: ctcp-version, ctcp-finger, and ctcp-userinfo. You can use set to set
+# them to values you'd like.
 
-##### IRC MODULE #####
 
-# this module provides ALL NORMAL IRC INTERACTION, if you want the normal
-# join & maintain channels stuff, this is the module.
+#### IRC MODULE ####
+
+# This module provides basic IRC support for your bot. You have to
+# load this if you want your bot to come on IRC. The server and channels
+# modules must be loaded for this module to function.
 loadmodule irc
 
-# [0/1] define this if you want to bounce all server bans
+# Set this to 1 if you want to bounce all server bans.
 set bounce-bans 1
 
-# [0/1] define this if you want to bounce all the server modes
+# Set this to 1 if you want to bounce all the server modes.
 set bounce-modes 0
 
-# If there are more than max-bans active bans on a channel, then the
-# bot won't try to put more bans. Thus it won't flood the irc server.
-# ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
+# Set here the maximum number of bans you want the bot to set on a channel.
+# Eggdrop will not place any more bans if this limit is reached. Undernet
+# and IRCnet currently allow 30 bans, EFnet allows 20, and DALnet allows 100.
 set max-bans 20
 
-# There is a global limit for +b/+e/+I modes. This limit is set to 30 on
-# 2.10 irc servers.
+# There is a global limit for +b/+e/+I modes. This limit is currently set to
+# 30 on IRCu 2.10 servers.
 set max-modes 30
 
-# [0/1] Do you want the bot to kick for control character/ctcp avalanches
-# to a channel?
-# Remember that if it does, as it won't ban them, it can be at the origin
-# of a nice kick-flood
+# Set this to 1 if you want the bot to kick for control character/ctcp
+# avalanches to a channel. Remember that if it does, it won't ban them.
+# This can start kick floods.
 set kick-fun 0
 
-# [0/1] Do you want the bot to ban for control character/ctcp avalanches
-# to a channel?
-# Can prevent the above described kick-flood, but can also fill the banlist
+# Set this to 1 if you want the bot to ban for control character/ctcp
+# avalanches to a channel. Can prevent kick floods, but also fill the
+# banlist.
 set ban-fun 0
 
-# [0/1] let users introduce themselves to the bot via 'hello'?
+# If you want people to be able to add themselves to the bot's userlist
+# with the default userflags (defined above in the config file) via the
+# 'hello' msg command, set this to 1.
 set learn-users 0
 
-# time (in seconds) to wait for someone to return from a netsplit
+# Set here the time (in seconds) to wait for someone to return from
+# a netsplit (i.e. wasop will expire afterwards). Set this to 1500
+# on IRCnet since it's nick delay stops after 30 minutes.
 set wait-split 600
 
-# time (in seconds) that someone must have been off-channel before
-# re-displaying their info
+# Set here the time (in seconds) that someone must have been off-channel
+# before re-displaying their info line.
 set wait-info 180
 
-##### IRC MODULE - net-type 1 specific features (IRCnet) #####
+# Set this to the maximum number of bytes to send in the arguments
+# of modes sent to the server. Most servers default this to 200.
+set mode-buf-length 200
+
+# Many IRCops find bots by seeing if they reply to 'hello' in a msg. 
+# You can change this to another word by un-commenting the following
+# two lines, and changing "myword" to the word wish to use instead of
+# 'hello'. It must be a single word.
+#unbind msg - hello *msg:hello
+#bind msg - myword *msg:hello
+
+# Many takeover attempts occur due to lame users blindly /msg ident'ing to
+# the bot and attempting to guess passwords. We now unbind this command by
+# default to discourage them. You can enable this command by un-commenting
+# the following two lines.
+unbind msg - ident *msg:ident
+unbind msg - addhost *msg:addhost
+
+# If you are so lame you want the bot to display peoples info lines, even
+# when you are too lazy to add their chanrecs to a channel, set this to 1.
+# *NOTE* This means *every* user with an info line will have their info
+# display on EVERY channel they join (provided they have been gone longer
+# than wait-info).
+set no-chanrec-info 0
+
+### IRC MODULE - IRCnet SPECIFIC FEATURES (net-type 1) ###
 
-# Don't modify the following settings if you don't use IRCnet. The defaults following
-# values are harmless for you.
+# Attention: Use these settings *only* if you set 'net-type' to 1!
 
-# [0/1] define this if you want to bounce all server exemptions (+e modes)
-#  * This is an IRCNET feature
+# Set this to 1 if you want to bounce all server exemptions (+e modes).
 set bounce-exempts 0
 
-# [0/1] define this if you want to bounce all server invitations (+I modes)
-#  * This is an IRCNET feature
+# Set this to 1 if you want to bounce all server invitations (+I modes).
 set bounce-invites 0
 
-# If there are more than max-exempts active +e modes on a channel, then
-# the bot won't try to put more exemptions. Thus it won't flood the irc
-# server. Only 2.10 servers are concerned by these +e modes.
-#  * This is an IRCNET feature
+# Set here the maximum number of exempts you want eggdrop to set
+# on a channel. Eggdrop will not place any more exempts if this
+# limit is reached.
 set max-exempts 20
 
-# If there are more than max-invites active +I modes on a channel, then
-# the bot won't try to put more invitations. Thus it won't flood the irc
-# server. Only 2.10 irc servers are concerned by these +I modes.
-#  * This is an IRCNET feature
+# Set here the maximum number of invites you want eggdrop  to set
+# on a channel. Eggdrop will not place any more invites if this
+# limit is reached.
 set max-invites 20
 
-# The following lines should be left un-commented unless the default values
-# are being over-ridden. By default exempts and invites are on for IRCnet
-# and hybrid EFnet, but off for all other networks. This behavior can be
-# modified by the following 2 flags. If you're network doesn't support e/I
-# modes then you'll be unable to use these features.
-#
-# [0/1] Do you want to enable exempts?
-# set use-exempts 0
-
-# [0/1] Do you want to use invites?
-# set use-invites 0
-
-# [0/1] Prevent mixing normal modes and +I/+e invite modes?
-# At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
-# so leave this flag set to 1. The servers will probably change their
-# behavior in the future, so you should first check before accepting the
-# default.
+# The following settings should be left commented unless the default values
+# are being overridden. By default, exempts and invites are on for IRCnet,
+# but off for all other large networks. This behavior can be modified with
+# the following 2 flags. If your network doesn't support +e/+I modes then you
+# will be unable to use these features.
+#
+# Do you want to enable exempts?
+#set use-exempts 0
+
+# Do you want to use invites?
+#set use-invites 0
+
+# At the moment, the current IRCnet IRCd version (2.10) doesn't support the mixing
+# of b,o and v modes with e and I modes. This might be changed in the future, so
+# use 1 at the moment for this setting.
 set prevent-mixing 1
 
-##### IRC MODULE - net-type 5 specific features (other networks) #####
+### IRC MODULE - OTHER NETWORKS (net-type 5) ###
 
-# kick-method defines how kicks (when enforcing bans) should be made:
-#    0 = kick all nicks at once in one command
-#    X = kick X users at a time
-#
-# Automatically set by net-type:
-#  net-type 0, 2, 3 & 4 sets this to 1
-#  net-type 1 sets this to 4
-#
-# If you use net-type 5, you must set this yourself (default is 1)
+# Attention: Use these settings *only* if you set 'net-type' to 5!
+
+# If your network supports more users per kick command then 1, you can
+# change this behavior here. Set this to the number of users to kick at
+# once, or set this to 0 for all at once.
 #set kick-method 1
 
-# some networks allow you to stack lots of channel modes into one
-# line.
-# they're all guaranteed to support at least 3, so that's the default,
-# but if you know your network supports more, you may want to adjust
-# this value. this value must be less than or equal to 6.
-# Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
-# 6 for net-type 2/3.
-# Only use this if you set net-type 5
+# Some networks allow you to stack lots of channel modes into one line.
+# They're all guaranteed to support at least 3, so that's the default.
+# If you know your network supports more, you may want to adjust this.
 #set modes-per-line 3
 
-# [0/1] Some networks don't include the +l limit and +k or -k key modes
+# Some networks don't include the +l limit and +k or -k key modes
 # in the modes-per-line (see above) limitation. Set include-lk to 0 for
-# those networks.
-# Automatically set to 1 for net-type 1/2/3, set to 0 for net-type 0/4.
-# Only use this if you set net-type 5.
+# these networks.
 #set include-lk 1
 
-# [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
-# exactly what's needed
-# Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
-# Only use this if you set net-type 5
-#set use-354 0
-
-# [0/1] use rfc 1459 compliant string matching routines?
-# All networks apart from Dalnet comply with rfc 1459, so you should only
-# disable it on Dalnet or networks which use Dalnet's code.
+# If your network doesn't use rfc 1459 compliant string matching routines,
+# set this to 0.
 #set rfc-compliant 1
 
 
-##### TRANSFER MODULE #####
+#### TRANSFER MODULE ####
 
-# un-comment this line to load the transfer module, this provides
-# dcc send/get support and bot userfile transfer support (not sharing)
+# The transfer module provides dcc send/get support and userfile transfer
+# support for userfile sharing. Un-comment the next line to load it if you 
+# need this functionality.
 #loadmodule transfer
 
-##### variables:
-# set maximum number of simultaneous downloads to allow for each user
+# Set here the maximum number of simultaneous downloads to allow for
+# each user.
 set max-dloads 3
 
-# set the block size for dcc transfers (ircII uses 512 bytes, but admits
-# that may be too small -- 1024 is standard these days)
-# set this to 0 to use turbo-dcc (recommended)
+# Set here the block size for dcc transfers. ircII uses 512 bytes,
+# but admits that may be too small. 1024 is standard these days.
+# Set this to 0 to use turbo-dcc (recommended).
 set dcc-block 1024
 
-# [0/1] copy files into the /tmp directory before sending them?  this is
-# useful on most systems for file stability.  (someone could move a file
-# around while it's being downloaded, and mess up the transfer.)  but if
-# your directories are NFS mounted, it's a pain, and you'll want to set
-# this to 0. If you are low on disk space, you may want to set this to 0.
+# Enable this setting if you want to copy files into the /tmp directory
+# before sending them. This is useful on most systems for file stability,
+# but if your directories are NFS mounted, it's a pain, and you'll want
+# to set this to 0. If you are low on disk space, you may also want to
+# set this to 0.
 set copy-to-tmp 1
 
-# time (in seconds) that a dcc file transfer can remain inactive
-# before being timed out
+# Set here the time (in seconds) to wait before an inactive transfer
+# times out.
 set xfer-timeout 30
 
 
-##### SHARE MODULE #####
+#### SHARE MODULE ####
 
-# this provides the userfile sharing support
-# (this requires the channels & transfer modules)
+# This module provides userfile sharing support between two directly
+# linked bots. The transfer and channels modules are required for this
+# module to correctly function. Un-comment the following line to load
+# the share module.
 #loadmodule share
 
-# [0/1] when sharing user lists, DON'T ACCEPT global flag changes from other bots?
-# NOTE: the bot will still send changes made on the bot, it just wont accept
-# any global flag changes from other bots
+# Settings in this section must be un-commented before setting.
+
+# When sharing user lists, DON'T ACCEPT global flag changes from other bots?
+# NOTE: The bot will still send changes made on the bot, it just wont accept
+# any global flag changes from other bots.
 #set private-global 0
 
-# when sharing user lists, if private-global isn't set, which global flag
-# changes from other bots should be ignored ?
+# When sharing user lists, if private-global isn't set, which global flag
+# changes from other bots should be ignored?
 #set private-globals "mnot"
 
-# [0/1] when sharing user lists, DON'T ACCEPT any userfile changes from other
-# bots?
-# NOTE: paranoid people should use this feature on their hub bot - this
-# will force all +host/+user/chpass/etc. changes to be made via the hub
+# When sharing user lists, don't accept ANY userfile changes from other
+# bots? Paranoid people should use this feature on their hub bot. This
+# will force all userlist changes to be made via the hub.
 #set private-user 0
 
-# [0/1] this setting makes the bot discard it's own bot records in favor of
-# the ones sent by the hub. Note: This only works with hubs that are v1.5.1
-# _or higher_.
+# This setting makes the bot discard it's own bot records in favor of
+# the ones sent by the hub.
+# NOTE: No passwords or botflags are shared, only ports and
+# address are added to sharing procedure. This only works with hubs that
+# are v1.5.1 or higher.
 #set override-bots 0
 
 
-##### COMPRESS MODULE #####
+#### COMPRESS MODULE ####
 
-# The compress module provides support for file compression. This allows the
-# bot to transfer compressed user files and therefore save a significant
-# amount of bandwidth, especially on very active hubs.
+# This module provides provides support for file compression. This allows the
+# bot to transfer compressed user files and therefore save a significant amount
+# of bandwidth. The share module must be loaded to load this module. Un-comment
+# the following line to the compress module.
 #loadmodule compress
 
-# [0/1] allow compressed sending of user files. The user files
-# are compressed with the compression level defined in `compress-level'.
-#set share-compressed 1
+# Allow compressed sending of user files? The user files are
+# compressed with the compression level defined in `compress-level'.
+set share-compressed 1
 
-# [0-9] default compression level used.
+# This is the default compression level used.
 #set compress-level 9
 
 
-##### FILESYSTEM MODULE #####
+#### FILESYSTEM MODULE ####
 
-# un-comment this line to load the file system module, this provides
-# an area within the bot where you can store files
+# This module provides an area within the bot where users can store
+# files. With this module, the bot is usable as a file server. The
+# transfer module is required for this module to function. Un-comment
+# the following line to load the filesys module.
 #loadmodule filesys
 
-# this is the 'root' directory for the file system (set it to "" if you
-# don't want a file system)
+# Set here the 'root' directory for the file system.
 set files-path "/home/mydir/filesys"
 
-# if you want to allow uploads, set this to the directory uploads should be
-# put into
+# If you want to allow uploads, set this to the directory uploads
+# should be put into. Set this to "" if you don't want people to
+# upload files to your bot.
 set incoming-path "/home/mydir/filesys/incoming"
 
-# [0/1] alternately, you can set this, and uploads will go to the current
-# directory that a user is in
+# If you don't want to have a central incoming directory, but instead
+# want uploads to go to the current directory that a user is in, set
+# this setting to 1.
 set upload-to-pwd 0
 
-# eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
-# to keep track of its own file system info -- if you can't do that (like
-# if the dcc path isn't owned by yours) or you just don't want it to do
-# that, specify a path here where you'd like all the database files to
-# be stored instead (otherwise, just leave it blank)
+# Eggdrop creates a '.filedb' file in each subdirectory of your file area
+# to keep track of its own file system information. If you can't do that (for
+# example, if the dcc path isn't owned by you, or you just don't want it to do
+# that) specify a path here where you'd like all of the database files to be
+# stored instead.
 set filedb-path ""
 
-# set maximum number of people that can be in the file area at once
-# (0 to make it effectively infinite)
+# Set here the maximum number of people that can be in the file area at once.
+# Setting this to 0 makes it effectively infinite.
 set max-file-users 20
 
-# maximum allowable file size that will be received, in K
-# (default is 1024K = 1M). 0 makes it effectively infinite.
+# Set here the maximum allowable file size that will be received (in kb).
+# Setting this to 0 makes it effectively infinite.
 set max-filesize 1024
 
 
-##### NOTES MODULE #####
+#### NOTES MODULE ####
 
-# this provides support for storing of notes for users from each other
-# notes between currently online users is supported in the core, this is
-# only for storing the notes for later retrieval, direct user->user notes
-# are built-in
+# This module provides support for storing of notes for users from each
+# other. Note sending between currently online users is supported in the
+# core, this is only for storing the notes for later retrieval.
 loadmodule notes
 
-# the notefile: where private notes between users are stored
+# Set here the filename where private notes between users are stored.
 set notefile "LamestBot.notes"
 
-# maximum number of notes to allow to be stored for each user
-# (to prevent flooding)
+# Set here the maximum number of notes to allow to be stored for
+# each user (to prevent flooding).
 set max-notes 50
 
-# time (in days) to let stored notes live before expiring them
+# Set here how long (in days) to store notes before expiring them.
 set note-life 60
 
-# [0/1] allow users to specify a forwarding address for forwarding notes
-# to another bot
+# Set this to 1 if you want to allow users to specify a forwarding
+# address for forwarding notes to another account on another bot.
 set allow-fwd 0
 
-# [0/1] set this to 1 if you want the bot to let people know hourly if they
-# have any notes
+# Set this to 1 if you want the bot to let people know hourly if they
+# have any notes.
 set notify-users 1
 
-# [0/1] set this to 1 if you want the bot to let people know on join if they
-# have any notes
+# Set this to 1 if you want the bot to let people know on join if they
+# have any notes.
 set notify-onjoin 1
 
-# comment out this next line, otherwise your bot won't start
+# Comment out this next line. Otherwise, your bot won't start.
 die "You didn't edit your config file like you were told, did you?"
 
 
-##### CONSOLE MODULE #####
+#### CONSOLE MODULE ####
 
-# this module provides storage of console settings when you exit the bot
-# (or .store)
+# This module provides storage of console settings when you exit the
+# bot or type .store on the partyline.
 loadmodule console
 
-##### variables:
-# [0/1] save users console settings automatically? (otherwise they have to use
-# .store)
-set console-autosave 0
+# Save users console settings automatically? Otherwise, they have
+# to use the .store command.
+set console-autosave 1
 
-# [0-99999] if a user doesn't have any console settings saved, which channel
+# If a user doesn't have any console settings saved, which channel
 # do you want them automatically put on?
 set force-channel 0
 
-# [0/1] display a user's global info line when they join a botnet channel?
+# Enable this setting if a user's global info line should be displayed
+# when they join a botnet channel.
 set info-party 0
 
 
-##### SEEN MODULE #####
+#### SEEN MODULE ####
 
-# this module provides seen commands via msg, on channel or via
-# dcc, similar to the various scripts
+# This module provides very basic seen commands via msg, on channel or via dcc.
+# This module works only for users in the bot's userlist. If you are looking for
+# a better and more advanced seen module, try the gseen module by G'Quann. You
+# can find it at http://www.visions-of-fantasy.de/gseen.mod/.
 #loadmodule seen
 
 
-##### BLOWFISH MODULE #####
+#### BLOWFISH MODULE ####
 
-##### IF YOU DON'T READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
-
-# Choose your encryption method now, 'cause once you do, it ain't
-# changing 'til you get a new userfile, capish?  At the moment, there
-# is only one encryption option: blowfish
-
-# un-comment this line to load blowfish, the encryption module
-# for the bot. the bot will not start without it loaded. it is 
-# commented out to make sure you read the whole config file.
-# this is checkmodule, because during .restart the module will 
-# already be loaded.
+# IF YOU DON'T READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
+# Eggdrop encrypts its userfile, so users can have secure passwords.
+# Please note that when you change your encryption method later (i.e.
+# using other modules like a md5 module), you can't use your current
+# userfile anymore. Eggdrop will not start without an encryption module.
 #checkmodule blowfish
 
 
-##### ASSOC MODULE #####
+#### ASSOC MODULE ####
 
-# un-comment this line to load assoc support, i.e. naming channels on
-# the botnet
+# This module provides assoc support, i.e. naming channels on the botnet.
+# You can load it by un-commenting the following line.
 #loadmodule assoc
 
+#### WIRE MODULE ####
 
-##### WIRE MODULE #####
-
-# this module provides all the standard .wire commands via dcc.
-# it's an encrypted partyline communication tool, compatible with wire.tcl
-# un-comment this line to load it
+# This module provides all the standard .wire commands via dcc. It is an 
+# encrypted partyline communication tool, compatible with wire.tcl. An
+# encryption module must be loaded to use this module. Un-comment the
+# following line to load the wire module.
 #loadmodule wire
 
-##### UPTIME MODULE #####
+#### UPTIME MODULE ####
 
-# this module reports uptime statistics to http://uptime.eggheads.org
-# go look and see what your uptime is! (it will show up after 9 hours or so)
-# (this requires the server module)
+# This module reports uptime statistics to http://uptime.eggheads.org.
+# Go look and see what your uptime is! It takes about 9 hours to show up,
+# so if your bot isn't listed, try again later.
+# 
+# Information sent to the server includes the bot's uptime, botnet-nick,
+# server, version, and IP address. This information is stored in a temporary 
+# logfile for debugging purposes only. The only publicly available information
+# will be the bot's botnet-nick, version and uptime. If you do not wish for this
+# information to be sent, comment out the following line.
 loadmodule uptime
 
 ##### SCRIPTS #####
 
-# these are some commonly loaded (and needed) scripts.
+# This is a good place to load scripts to use with your bot.
+
+# This line loads script.tcl from the scripts directory inside your eggdrop's
+# directory. All scripts should be put there, although you can place them where
+# you like as long as you can supply a fully qualified path to them.
+#
+# source scripts/script.tcl
+
 source scripts/alltools.tcl
 source scripts/action.fix.tcl
 
-# use this for Tcl and eggdrop downwards compatibility
+# Use this script for Tcl and eggdrop downwards compatibility.
+# NOTE: This can also cause problems with some newer scripts.
 source scripts/compat.tcl
 
-# This script provides many useful minor informational commands
-# (like setting user's URLs, email address, etc). You can modify
-# it to add extra entries, you might also want to modify help/userinfo.help
-# and help/msg/userinfo.help to change the help files.
+# This script provides many useful informational functions, like setting 
+# users' URLs, e-mail address, ICQ numbers, etc. You can modify it to add
+# extra entries
 source scripts/userinfo.tcl
 loadhelp userinfo.help
Index: eggdrop1.6/eggdrop.complete.conf
diff -u eggdrop1.6/eggdrop.complete.conf:1.41 eggdrop1.6/eggdrop.complete.conf:1.42
--- eggdrop1.6/eggdrop.complete.conf:1.41	Sat Dec  8 12:16:03 2001
+++ eggdrop1.6/eggdrop.complete.conf	Thu Dec 13 23:43:10 2001
@@ -1,11 +1,10 @@
 #! /path/to/executable/eggdrop
-# ^- Set that to the directory eggdrop is in, i.e. "#! /home/lamest/egg/eggdrop"
+# ^- This should contain a fully qualified path to your eggdrop executable.
 #
-# $Id: eggdrop.complete.conf,v 1.41 2001/12/08 18:16:03 guppy Exp $
+# $Id: eggdrop.complete.conf,v 1.42 2001/12/14 05:43:10 guppy Exp $
 #
-# This config file includes all possible options you can
-# use to configure your bot properly.
-# Be sure that you know what you are doing!
+# This is a sample eggdrop configuration file which includes all possible
+# settings that can be used to configure your bot.
 #
 # More detailed descriptions of all those settings can be found in
 # doc/settings/.
@@ -13,59 +12,60 @@
 
 ##### GENERAL STUFF #####
 
-# the username the bot uses, this is only used if identd isn't working
-# on the machine the bot is running on.
+# This setting defines the username the bot uses on IRC. This setting has 
+# no effect if an ident daemon is running on your bot's machine.
 set username "lamest"
 
-# who's running this bot?
-set admin "Lamer <email: lamer at lamest.lame.org>"
-
-# what IRC network are you on?  this is just info to share with others on
-# your botnet, for human curiosity only.
-set network "I.didnt.edit.my.config.file.net"
-
-# what timezone is your bot in? The timezone string specifies the name of
-# the timezone and must be three or more alphabetic characters.
-#
-# ex. Central European Time(UTC+1) would be "CET"
+# This setting defines which contact person should be shown in .status,
+# /msg help, and other places. You really should include this information.
+set admin "Lamer <email: lamer at lamest.lame.org)"
+
+# This setting is used only for info to share with others on your botnet.
+# Set this to the IRC network your bot is connected to.
+set network "I.didn't.edit.my.config.file.net"
+
+# This setting defines the timezone is your bot in. It's used for internal
+# routines as well as for logfile timestamping and scripting purposes.
+# The timezone string specifies the name of the timezone and must be three
+# or more alphabetic characters.
+# E.x. Central European Time(UTC+1) should be "CET".
 set timezone "EST"
 
-# offset specifies the time value to be added to the local time to get
-# Coordinated Universal Time (UTC aka GMT).  The offset is positive if the
-# local timezone is west of the Prime Meridian and negative if it is east.
-# The value(hours) must be between 0 and 24.
-#
-# ex. if the timezone is UTC+1 the offset is -1
+# The offset setting specifies the time value to be added to the local time
+# to get Coordinated Universal Time (UTC aka GMT). The offset is positive if
+# the local timezone is west of the Prime Meridian and negative if it is east.
+# The value (in hours) must be between -23 and 23.
+# E.x. If the timezone is UTC+1, the offset is -1.
 set offset "5"
 
-# If you don't want to use the timezone setting for scripting purpose
-# only, but instead, everywhere possible (new), then un-comment the next line.
+# If you don't want to use the timezone setting for scripting purposes only,
+# but instead everywhere possible, un-comment the following line.
 #set env(TZ) "$timezone $offset"
 
-# if you're using virtual hosting (your machine has more than 1 IP), you
-# may want to specify a particular IP to bind to. you can specify
-# either by hostname or by IP.  you may also want to set the hostname
-# here if eggdrop has trouble detecting it when it starts up.  (it will
-# let you know if it has trouble -- trust me.)
+# If you're using virtual hosting (your machine has more than 1 IP), you
+# may want to specify the particular IP to bind to. You can specify either
+# by hostname or by IP. You may also want to set the hostname here if
+# eggdrop has trouble detecting it when it starts up.
 #set my-hostname "virtual.host.com"
 #set my-ip "99.99.0.0"
 
-# if you want to have your eggdrop messages displayed in another language
-# change the below command to match your preferences. An alternative would
-# be to set the environment variable EGG_LANG to that value.
+# If you want to have your eggdrop messages displayed in a language other
+# than English, change this setting to match your preference. An alternative
+# would be to set the environment variable EGG_LANG to that value.
 #addlang "english"
 
 
 ##### LOG FILES #####
 
-# You can specify a limit on how many log files you can have.
-# At midnight every day, the old log files are renamed and a new log file begins.
-# By default, the old one is called "(logfilename).yesterday",
-# and any logfiles before yesterday are erased.
-
-# Events are logged by certain categories -- this way you can specify
-# exactly what kind of events you want sent to various logfiles.  the
-# events are:
+# Eggdrop is capable of logging various things, from channel chatter to
+# commands people use on the bot and file transfers. Logfiles are normally
+# kept for 24 hours. Afterwards, they will be renamed to "(logfile).yesterday".
+# After 48 hours, they will be overwritten by the logfile of the next day.
+# 
+# Events are logged by certain categories. This way, you can specify
+# exactly what kind of events you want sent to various logfiles.
+# 
+# The most common log file flags are:
 #   m  private msgs/ctcps to the bot
 #   k  kicks, bans, mode changes on the channel
 #   j  joins, parts, netsplits on the channel
@@ -74,371 +74,386 @@
 #   b  information about bot linking and userfile sharing
 #   c  commands people use (via msg or dcc)
 #   x  file transfers and file-area commands
-#   r  (if use-console-r defined) EVERYTHING sent to the bot by the server
+#      r  (if use-console-r enabled) EVERYTHING sent to the bot by the server
 #   o  other: misc info, errors -- IMPORTANT STUFF
 #   w  wallops: msgs between IRCops (be sure to set the bot +w in init-server)
+#
 # There are others, but you probably shouldn't log them, it'd be rather
-# unethical ;)
+# unethical. ;) There are also eight user-defined levels (1-8) which
+# are used by Tcl scripts.
+# 
+# Each logfile belongs to a certain channel. Events of type 'k', 'j', and 'p'
+# are logged to whatever channel they happened on. Most other events are
+# currently logged to every channel. You can make a logfile belong to all
+# channels by assigning it to channel "*".
 
-# maximum number of logfiles to allow - this can be increased if needed
-# (don't decrease this)
+# This is the maximum number of logfiles allowed. This setting can be 
+# increased; however, don't decrease it.
 set max-logs 5
 
-# maximum size of your logfiles, set this to 0 to disable.
-# this only works if you have keep-all-logs 0 (OFF)
-# this value is in KiloBytes, so '550' would mean cycle logs when
-# it reaches the size of 550 KiloBytes.
+# This is the maximum size of your logfiles. Set it to 0 to disable.
+# This value is in kilobytes, so '550' would mean cycle logs when it
+# reaches the size of 550 kilobytes.
+# Note that this only works if you have keep-all-logs 0 (OFF).
 set max-logsize 0
 
-# write the logfiles and check the size every minute
-# (if max-logsize is enabled) instead of every 5minutes as before.
-# This could be good if you have had problem with the
-# logfile filling your quota or hdd or if you log +p
-# and publish it on the web and wants more up-to-date info.
-# If you are concerned with resources keep the default setting 0.
-# (although I haven't noticed anything)
+# This could be good if you have had problem with the logfile filling
+# your quota/hard disk or if you log +p and publish it to the web and
+# need more up-to-date info.
+# Note that this setting might increase the CPU usage of your bot (on
+# the other hand it will decrease your mem usage).
 set quick-logs 0
 
-# each logfile also belongs to a certain channel.  events of type 'k', 'j',
-# and 'p' are logged to whatever channel they happened on.  most other
-# events are currently logged to every channel.  you can make a logfile
-# belong to all channels by assigning it to channel "*".  there are also
-# five user-defined levels ('1'..'5') which are used by Tcl scripts.
-
-# in 'eggdrop.log' put private msgs/ctcps, commands, misc info, and
-# errors from any channel:
+# This creates a logfile named eggdrop.log containing private msgs/ctcps,
+# commands, errors, and misc. info from any channel.
 logfile mco * "logs/eggdrop.log"
-# in 'lame.log' put joins, parts, kicks, bans, and mode changes from #lamest:
-logfile jk #lamest "logs/lamest.log"
 
-# [0/1] timestamp entries in the log file? (generally a good idea)
+# This creates a logfile named lamest.log containing joins, parts,
+# netsplits, kicks, bans, mode changes, and public chat on the
+# channel #lamest. 
+logfile jpk #lamest "logs/lamest.log"
+
+# Use this feature to timestamp entries in the log file.
 set log-time 1
 
-# [0/1] keep logfiles for more than 48 hours -- instead of being called
-# "(logfilename).yesterday", the log files are named by the current date,
-# and kept around forever (eventually your directory might get full, so
-# be careful with this!)
+# If you want to keep your logfiles forever, turn this setting on. All
+# logfiles will get suffix ".[day, 2 digits][month, 3 letters][year, 4 digits]".
+# Note that your quota/hard-disk might be filled by this, so check your logfiles
+# often and download them.
 set keep-all-logs 0
 
-# if keep-all-logs is 1, this setting will define the suffix of the logfiles.
+# If keep-all-logs is 1, this setting will define the suffix of the logfiles.
 # The default will result in a suffix like "04May2000". "%Y%m%d" will produce
-# the often used yyyymmdd format. Read the strtime manpages for more options.
+# the often used yyyymmdd format. Read the strftime manpages for more options.
 # NOTE: On systems which don't support strftime, the default format will
 # be used _always_.
 set logfile-suffix ".%d%b%Y"
 
-# once a day the logfiles are switched out and started fresh --
-# this specifies when that should happen (in military time)
-# [note that a leading 0 will make Tcl think this is an octal value,
-# something you probably don't want.]
+# You can specifiy when eggdrop should switch logfiles and start fresh. You must
+# use military time for this setting. 300 is the default, and describes 00:00.
+# Note that a leading 0 will make Tcl think this is an octal value,
+# something you probably don't want.
 set switch-logfiles-at 300
 
-# [0/1] enable quiet saves? "Writing user file..." and "Writing channel file ..."
-# will not be logged if this option is enabled.
+# "Writing user file..." and "Writing channel file..." messages
+# won't be logged anymore if this option is enabled.
 set quiet-save 0
 
-# this is the default console mode -- what masters will see automatically
-# when they dcc chat with the bot (masters can alter their own console
-# flags once they connect, though) -- it uses the same event flags as
-# the log files
-# (note that the console channel is automatically set to your "primary"
-# channel -- the one you defined first in this file.  masters can change
-# their console channel with the '.console' command, however.)
+
+##### CONSOLE #####
+
+# This is the default console mode. It uses the same event flags as the log
+# files do. The console channel is automatically set to your "primary" channel,
+# which is set in the modules section of the config file. Masters can change
+# their console channel and modes with the '.console' command.
+
 set console "mkcobxs"
 
 
 ##### FILES AND DIRECTORIES #####
 
-# the userfile: where user records are stored
+# Specify here the filename your userfile should be saved as.
 set userfile "LamestBot.user"
 
-# the pidfile: where eggdrop saves its pid file to
-# set pidfile "pid.${botnet-nick}"
+# Specify here the filename eggdrop will save its pid to. If no
+# pidfile is specified, pid.(botnet-nick) will be used.
+#set pidfile "pid.${botnet-nick}"
 
-# [0/1] do you want the userlist to be sorted when saving
+# If you want your userfile to be sorted upon saving, enable this setting.
+# This causes the bot to use bit more CPU when saving the usefile.
 set sort-users 0
 
-# where the help files can be found (and there are plenty)
+# Specify here where eggdrop should look for help files.
+# Don't modify this setting unless you know what you're doing!
 set help-path "help/"
 
-# where the text files can be found (used with various dump commands)
+# Specify here where eggdrop should look for text files. This is
+# used for certain Tcl and DCC commands.
 set text-path "text/"
 
-# a good place to temporarily store files (i.e.: /tmp)
+# Set here a place to store temporary files.
 set temp-path "/tmp"
 
-# the MOTD is displayed when people dcc chat to the bot.
-# type '.help set motd' in DCC CHAT for tons of motd options.
+# The MOTD (Message Of The day) is displayed when people dcc chat or telnet
+# to the bot. Look at doc/settings.motd or type '.help set motd' in DCC 
+# CHAT or telnet connection for options.
 set motd "text/motd"
 
-# holds the banner displayed on telnet connections
+# This banner will be displayed on telnet connections.
 set telnet-banner "text/banner"
 
-# Specifies what permissions the user, channel and notes files should be set
-# to.  The octal values are the same as for the chmod system command.
+# This specifies what permissions the user, channel, and notes files should be set to.
+# The octal values are the same as for the chmod system command.
+# 
+# To remind you:
 #
 #          u  g  o           u  g  o           u  g  o
 #    0600  rw-------   0400  r--------   0200  -w-------    u - user
 #    0660  rw-rw----   0440  r--r-----   0220  -w--w----    g - group
 #    0666  rw-rw-rw-   0444  r--r--r--   0222  -w--w--w-    o - others
 #
-# Most users will want to leave the permissions set to 0600, to ensure
-# maximum security.
+# Note that the default 0600 is the most secure one and should only be
+# changed if you need your files for shell scripting or other external
+# applications.
 set userfile-perm 0600
 
-##### BOTNET #####
 
-# you probably shouldn't deal with this until reading 'botnet.doc' or
-# something.  you need to know what you're doing.
+##### BOTNET/DCC/TELNET #####
 
-# if you want to use a different nickname on the botnet than you use on
-# IRC, set it here:
+# Settings in this section should be unimportant for you until you deal
+# with botnets (multiple eggdrops connected together to maximize efficiency).
+# You should read doc/BOTNET before modifying these settings.
+
+# If you want to use a different nickname on the botnet than you use on
+# IRC (i.e. if you're on an un-trusted botnet), un-comment the next line
+# and set it to the nick you would like to use.
 #set botnet-nick "LlamaBot"
 
-# what telnet port should this bot answer?
-# NOTE: if you are running more than one bot on the same machine, you will
-#   want to space the telnet ports at LEAST 5 apart... 10 is even better
-# if you would rather have one port for the botnet, and one for normal
-#   users, you will want something like this instead:
-#listen 3333 bots
-#listen 4444 users
-# NOTE: there are more options listed for the listen command in
-#   doc/tcl-commands.doc
+# This opens a telnet port by which you and other bots can
+# interact with the eggdrop by telneting in.
+# 
+# There are more options for the listen command in doc/tcl-commands.doc.
+# Note, if you are running more than one bot on the same machine, you will
+# want to space the telnet ports at LEAST 5 apart. 10 is even better.
+# 
+# Valid ports are typically anything between 1025 and 65535 assuming the
+# port is not already in use.
+#
+
+# If you would like the bot to listen for users and bots in separate ports,
+# use the following format.
+# 
+# listen 3333 bots
+# listen 4444 users
+#
+# If you wish to use only one port, use this format:
 listen 3333 all
 
-# [0/1] This setting will drop telnet connections not matching a known host
-# It greatly improves protection from IRCOPs, but makes it impossible
-# for NOIRC bots to add hosts or have NEW as a valid login
+# This setting defines whether or not people can boot users on the eggdrop
+# from other bots in your botnet. Valid settings are:
+#    0 - allow *no* outside boots
+#    1 - allow boots from sharebots
+#    2 - allow any boots
+set remote-boots 2
+
+# This setting prohibits remote bots from telling your eggdrop to unlink from 
+# share bots.
+set share-unlinks 1
+
+# This setting will drop telnet connections not matching a known host. It
+# greatly improves protection from IRCOps, but makes it impossible for NOIRC
+# bots to add hosts or have NEW as a valid login.
 set protect-telnet 0
 
-# [0/1] This setting will make the bot ignore DCC chat requests which appear to
+# This setting will make the bot ignore DCC chat requests which appear to
 # have bogus information on the grounds that the user may have been trying
 # to make the bot connect to somewhere that will get it into trouble, or
 # that the user has a broken client (like mIRC tends to do), in which case
 # the connect wouldn't work anyway.  It's suggested that you turn this on.
 set dcc-sanitycheck 0
 
-# and a timeout value for ident lookups would help (seconds)
+# This settings defines a time in seconds that the bot should wait before
+# a dcc chat, telnet, or relay connection times out.
 set ident-timeout 5
 
-# [0/1] users with the +o (global or channel op) flag will still need the +p
-# (party line) flag to join the dcc chat party line?
+# Define here whether or not a +o user still needs the +p flag to dcc the bot.
 set require-p 0
 
-# [0/1] allow people to telnet in, type 'NEW', and become a new user?
-# (If you set this to 1, you must set protect-telnet 0)
+# If you want people allow to telnet in and type 'NEW' to become a new user,
+# set this to 1. This is similar to the 'hello' msg command. The protect-telnet
+# setting must be set to 0 to use this.
 set open-telnets 0
 
-# [0/1] Display 'Nickname.' instead of identifying ourselves when people
-# telnet in. Set to 1 to only display Nickname.
-# (useful if someone portscans your machine, they wont know we're here)
+# If you don't want eggdrop to identify itself as an eggdrop on a telnet connection, 
+# set this setting to 1. Eggdrop will display 'Nickname' instead.
 set stealth-telnets 0
 
-# [0/1] Display a banner when people telnet in.
+# If you want eggdrop to display a banner when telneting in, set this setting
+# to 1. The telnet banner is set by 'set telnet-banner'.
 set use-telnet-banner 0
 
-# How long (in seconds) should I wait for a connect (dcc chat, telnet,
-# relay, etc) before it times out?
+# This settings defines a time in seconds that the bot should wait before
+# a dcc chat, telnet, or relay connection times out.
 set connect-timeout 15
 
-# number of messages / lines from a user on the partyline (dcc, telnet)  before
-# they are considered to be flooding (and therefore get booted)
+# Specify here the number of lines to accept from a user on the partyline
+# within 10 seconds before they are considered to be flooding and therefore
+# get booted.
 set dcc-flood-thr 3
 
-# how many telnet connection attempt in how many seconds from the same
-# host constitutes a flood?
+# Define here how many telnet connection attempts in how many seconds from
+# the same host constitute a flood. The correct format is Attempts:Seconds.
 set telnet-flood 5:60
 
-# [0/1] apply telnet flood protection for everyone?
-# set this to 0 if you want to exempt +f users from telnet flood protection
+# If you want telnet-flood to apply even to +f users, set this setting to 1.
 set paranoid-telnet-flood 1
 
-# how long should I wait (seconds) before giving up on hostname/address
-# lookup? (you might want to increase this if you are on a slow network).
+# Set here the amount of seconds before giving up on hostname/address
+# lookup (you might want to increase this if you are on a slow network).
 set resolve-timeout 15
 
 
 ##### MORE ADVANCED STUFF #####
 
-# are you behind a firewall?  un-comment this and specify your socks host
-#set firewall "proxy:178"
-# or, for a Sun "telnet passthru" firewall, set it this way
-# (does anyone besides Sun use this?)
+# Set this to your socks host if your eggdrop sits behind a firewall.
+# If you use a Sun "telnet passthru" firewall, use this setting:
 #set firewall "!sun-barr.ebay:3666"
 
-# if you have a NAT firewall (you box has an IP in one of the following
+# If you have a NAT firewall (you box has an IP in one of the following
 # ranges: 192.168.0.0-192.168.255.255, 172.16.0.0-172.31.255.255,
 # 10.0.0.0-10.255.255.255 and your firewall transparently changes your
-# address to a unique address for your box.) or you have IP masquerading
+# address to a unique address for your box) or you have IP masquerading
 # between you and the rest of the world, and /dcc chat,/ctcp chat or
-# userfile sharing aren't working. Enter your outside IP here.
-# Do not enter anything for my-ip or my-hostname.
+# userfile sharing aren't working, enter your outside IP here. Do not 
+# enter anything for my-ip or my-hostname if you use this setting.
 #set nat-ip "127.0.0.1"
 
-# if you want all dcc file transfers to use a particular portrange either
+# If you want all dcc file transfers to use a particular portrange either
 # because you're behind a firewall, or for other security reasons, set it
 # here.
 #set reserved-portrange 2010:2020
 
-# temporary ignores will last how many minutes?
+# Set the time in minutes that temporary ignores should last.
 set ignore-time 15
 
-# this setting affects what part of the hour the 'hourly' calls occur
-# on the bot, this includes such things as note notifying,
-# You can change that here (for example, "15" means to
-# notify every hour at 15 minutes past the hour)
-# this now includes when the bot will save its userfile
+# Define here what eggdrop considers 'hourly'. All calls to it, including such
+# things as note notifying or userfile saving are affected by this. For example:
+# 
+# set hourly-updates 15
+# 
+# The bot will save its userfile 15 minutes past every hour.
 set hourly-updates 00
 
-# the following user(s) will ALWAYS have the owner (+n) flag (You really 
-# should change this default value)
+# Un-comment the next line and set the list of owners of the bot.
+# You NEED to change this setting.
 #set owner "MrLame, MrsLame"
 
-# who should I send a note to when I learn new users?
+# Who should a note be sent to when new users are learned?
 set notify-newusers "$owner"
 
-# what flags should new users get as a default?
-# check '.help whois' on the partyline (dcc chat, telnet) for tons of
-# options.
+# Enter the flags that all new users should get by default.
+# See '.help whois' on the partyline for a list of flags and
+# their descriptions.
 set default-flags "hp"
 
-# what user-defined fields should be displayed in a '.whois'?
-# this will only be shown if the user has one of these xtra fields
-# you might prefer to comment this out and use the userinfo1.0.tcl script
+# Enter all user-defined fields that should be displayed in a '.whois'.
+# This will only be shown if the user has one of these extra fields.
+# You might prefer to comment this out and use the userinfo1.0.tcl script
 # which provides commands for changing all of these.
 set whois-fields "url birthday"
 
-# [0/1/2] allow people from other bots (in your bot-net) to boot people off
-# your bot's party line?
-# values:
-#   0 - allow *no* outside boots
-#   1 - allow boots from sharebots
-#   2 - allow any boots
-set remote-boots 2
-
-# [0/1] if you don't want people to unlink your share bots from remote bots
-# set this to 0
-set share-unlinks 1
-
-# [0/1] die on receiving a SIGHUP?
-# The bot will save it's userfile when it receives a SIGHUP signal
-# with either setting.
+# Enable this setting if you want your eggdrop to die upon receiving a SIGHUP
+# kill signal. Otherwise, the eggdrop will just save its userfile and rehash.
 set die-on-sighup 0
 
-# [0/1] die on receiving a SIGTERM?
-# The bot will save it's userfile when it receives a SIGTERM signal
-# with either setting.
+# Enable this setting if you want your eggdrop to die upon receiving a SIGTERM
+# kill signal. Otherwise, the eggdrop will just save its userfile and rehash.
 set die-on-sigterm 1
 
-# to enable the 'tcl' and 'set' command (let owners directly execute
-# Tcl commands)? - a security risk!!
+# Comment these two lines if you wish to enable the .tcl and .set commands.
 # If you select your owners wisely, you should be okay enabling these.
-# to enable, comment these two lines out
-# (In previous versions, this was enabled by default in eggdrop.h)
 unbind dcc n tcl *dcc:tcl
 unbind dcc n set *dcc:set
 
-# [0/1/2] only let permanent owners use .tcl/.set if bound? then set it to 1
-# moreover only let permanent owners use .dump? then set it to 2
-# (the people must set the $owner variable)
+# If you enable this setting, only permanent owners (owner setting) will be
+# able to use .tcl and .set. Moreover, if you want only let permanent owners 
+# use .dump, then set this to 2.
 set must-be-owner 1
 
-# comment the following line out to add the 'simul' command (owners can
-# manipulate other people on the party line).
-# Please select owners wisely! Use this command ethically!
+# Comment out this line to add the 'simul' partyline command (owners
+# can manipulate other people on the party line). Please select owners
+# wisely, and use this command ethically!
 unbind dcc n simul *dcc:simul
 
-# maximum number of dcc connections you will allow - you can increase this
-# later, but never decrease it, 50 seems to be enough for everybody
+# Set here the maximum number of dcc connections you will allow. You can
+# increase this later, but never decrease it.
 set max-dcc 50
 
-# [0/1] add the 'dccsimul' Tcl command (needed by certain scripts like
-# action.fix.tcl)
+# Enable this setting if you want to enable the 'dccsimul' Tcl command.
 set enable-simul 1
 
-# [0/1] allow +d & +k users to use commands bound as -|- ?
+# Enable this setting if you want +d & +k users to use commands bound as -|-.
 set allow-dk-cmds 1
 
-# If a bot connects which already seems to be connected, I wait
-# dupwait-timeout seconds before I check again and then finally reject
-# the bot. This is useful to stop hubs from rejecting bots that actually
-# have already disconnected from another hub, but the disconnect information
-# has not yet spread over the botnet due to lag.
+# If your eggdrop rejects bots that actually have already disconnected from
+# another hub, but the disconnect information has not yet spread over the
+# botnet due to lag, use this setting. The bot will wait dupwait-timeout 
+# seconds before it checks again and then finally reject the bot.
 set dupwait-timeout 5
 
-
-
-# You MUST remove this line for this config file to work.  This has been
-# added to prevent you from starting up a bot that is not fully configured.
-# Bots that have not been fully configured may join the wrong IRC network,
-# the wrong channels, or generally do things that you do not want.  Please
-# make sure that you have double-checked the settings you want.
-# There's also a similar line lower down, just to make sure you're reading :)
+# You MUST remove this line for your bot to start. This has been added to
+# prevent you from starting up a bot that is not fully configured. Bots
+# that have not been fully configured may join the wrong IRC network, the
+# wrong channels, or generally do things that you do not want. Please make
+# sure that you have double-checked every setting. There's also a similar line
+# lower down, just to make sure you're reading :)
 
 die "Please edit your config file."
 
 
+##### MODULES ##### 
 
-########## MODULES ##########
-
-# below are various settings for the modules available with eggdrop,
-# PLEASE EDIT THEM CAREFULLY, READ THEM, even if you're an old hand
-# at eggdrop, lots of things have changed slightly
-
-# this is the directory to look for the modules in, if you run the
-# bot in the compilation directories you will want to set this to ""
-# if you use 'make install' (like all good kiddies do ;) this is a fine
-# default, otherwise, use your head :)
+# Below are various settings for the modules available with eggdrop.
+# PLEASE READ AND EDIT THEM CAREFULLY, even if you're an old hand at
+# eggdrop, things change.
+
+# This path specifies the path were eggdrop should look for its modules.
+# If you run the bot from the compilation directory, you will want to set
+# this to "". If you use 'make install' (like all good kiddies do ;), this
+# is a fine default. Otherwise, use your head :)
 set mod-path "modules/"
 
 
-#### DNS MODULE #####
+#### DNS MODULE ####
 
-# this module provides asynchronous dns support. This will avoid long
+# This module provides asynchronous dns support. This will avoid long
 # periods where the bot just hangs there, waiting for a hostname to
-# resolve, which often let it timeout on all other connections.
+# resolve, which will often let it timeout on all other connections.
 loadmodule dns
 
-##### CHANNELS MODULE #####
+#### CHANNELS MODULE ####
 
-# this next module provides channel related support for the bot, without
-# it, it will just sit on irc, it can respond to msg & ctcp commands, but
-# that's all
+# This module provides channel related support for the bot. Without it,
+# you wont be able to make the bot join a channel or save channel
+# specific userfile information.
 loadmodule channels
 
-# the chanfile: where dynamic channel settings are stored
+# Enter here the filename where dynamic channel settings are stored.
 set chanfile "LamestBot.chan"
 
-# temporary bans will last how many minutes? if set to 0, bot never removes
-# them.
+# Set here how long temporary bans will last (in minutes). If you
+# set this setting to 0, the bot will never remove them.
 set ban-time 120
 
-# temporary exemptions (+e modes) will last how many minutes? if set to 0,
-# bot never removes them. This is an IRCNET feature. The bot will check the
-# exempts every X minutes, but will not remove the exempt if a ban is set on
-# the channel that matches that exempt. Once the ban is removed then the
-# exempt will be removed the next time the bot checks.
+# Set here how long temporary exempts will last (in minutes). If you
+# set this setting to 0, the bot will never remove them. The bot will
+# check the exempts every X minutes, but will not remove the exempt if
+# a ban is set on the channel that matches that exempt. Once the ban is
+# removed, then the exempt will be removed the next time the bot checks.
+# Please note that this is an IRCnet feature.
 set exempt-time 60
 
-# temporary invitations (+I modes) will last how many minutes? if set to
-# 0, bot never removes them. This is an IRCNET feature. The bot will check the
-# invites every X minutes, but will not remove them if the channel is +i. Once
-# the channel is -i then the bot will remove then invite mode next time it
-# checks this counter
+# Set here how long temporary invites will last (in minutes). If you
+# set this setting to 0, the bot will never remove them.
+# The bot will check the invites every X minutes, but will not remove
+# the invite if a channel is set to +i. Once the channel is -i then
+# the invite will be removed the next time the bot checks.
+# Please note that this is an IRCnet feature.
 set invite-time 60
 
-# [0/1] expire bans/exempts/invites set by other opped bots on the channel?
-# set force-expire 0
+# Set this setting to 1 if you want your bot to expire bans/exempts/invites set
+# by other opped bots on the channel.
+set force-expire 0
 
-# [0/1] share user greets with other bots on the channel if sharing user data?
+# Set this setting to 1 if you want your bot to share user greets with other
+# bots on the channel if sharing user data.
 set share-greet 0
 
-# [0/1] allow users to store an info line?
+# Set this setting to 1 if you want to allow users to store an info line.
 set use-info 1
 
-# these settings are used as default values when you
-# .+chan #chan or .tcl channel add #chan
-# look in the section above for explanation on every option
+# The following settings are used as default values when you .+chan #chan or .tcl
+# channel add #chan. Look in the section below for explanation of every option.
 
 set global-flood-chan 10:60
 set global-flood-deop 3:10
@@ -446,9 +461,7 @@
 set global-flood-join 5:60
 set global-flood-ctcp 3:60
 set global-flood-nick 5:60
-
 set global-aop-delay 5:30
-
 set global-idle-kick 0
 set global-chanmode "nt"
 set global-stopnethack-mode 0
@@ -469,9 +482,9 @@
         +userinvites
 }
 
-# do this for each channel you wish to sit on:
-# NOTE: for some reason Tcl won't let you put comments inside { } -- so
-#   don't try it, cos it'll mess up your channel definition
+# Add each static channel you want your bot to sit in using this command.
+# There are many different possible settings you can insert into this
+# command, which are explained below.
 
 channel add #lamest {
   chanmode "+nt-likm"
@@ -492,738 +505,811 @@
   flood-nick 5:60
 }
 
-# the things inside the { } are CHANNEL OPTIONS -- they can be set within
-# the "channel add" command, or by using a "channel set" command as in the
-# examples below.  they list all the options you can set for a channel.
-
-# chanmode
-#   what modes will be enforced?  '+' modes will always be kept on, '-' modes
-#   will always be kept off
-# idle-kick
-#   kick channel members after how many minutes of being idle?
-#   (leave out to disable, or set to 0)
-
-#   stopnethack-mode
-#     de-op anyone who enters the channel with serverops
+# chanmode +/-<modes>
+#    This setting makes the bot enforce channel modes. It will always add
+#    the +<modes> and remove the -<modes> modes.
+# idle-kick 0
+#    This setting will make the bot check every minute for idle
+#    users. Set this to 0 to disable idle check.
+#
+# stopnethack-mode 0
+#    This setting will make the bot de-op anyone who enters the channel
+#    with serverops. There're seven different modes for this settings:
 #       0 turn off,
-#       1 isoptest (allow serverop if registered op),
+#      1 isoptest (allow serverop if registered op)
 #       2 wasoptest (allow serverop if op before split)
 #       3 allow serverop if isop or wasop
-#       4 allow serverop if isop and wasop
-#       5 if channel -bitch: see stopnethack-mode 3
-#         if channel +bitch: see stopnethack-mode 1
-#       6 if channel -bitch: see stopnethack-mode 2
-#         if channel +bitch: see stopnethack-mode 4
-
-#   revenge-mode
-#     defines how the bot should punish bad users when revenging.
-#     default is 1.
-#       0 for deop
-#       1 for deop and +d
-#       2 for deop, +d and kick
-#       3 for deop, chattr +d, kick and ban
-
+#      4 allow serverop if isop and wasop.
+#      5 If the channel is -bitch, see stopnethack-mode 3
+#        If the channel is +bitch, see stopnethack-mode 1
+#      6 If the channel is -bitch, see stopnethack-mode 2
+#        If the channel is +bitch, see stopnethack-mode 4
+#
+# revenge-mode 1
+#   This settings defines how the bot should punish bad users when
+#   revenging. There are four possible settings:
+#     0 Deop the user.
+#     1 Deop the user and give them the +d flag for the channel.
+#     2 Deop the user, give them the +d flag for the channel, and kick them.
+#     3 Deop the user, give them the +d flag for the channel, kick, and ban them.
+#
 # aop-delay (minimum:maximum)
-# for autoop and autovoice
-# aop-delay 0                   no autoopdelay
-# aop-delay x or aop-delay x:x  x sec. autoopdelay
-# aop-delay x:y                 random delay
-# if a autoopped user joined during a other delayed autoop is pending,
-# the bot will sent both autoop based on the last-joined-user-delay-time,
-# probable in only one line.
-
-# need-op
-#   script to run (if any) when the bot needs to be op'd on this channel
-# need-invite
-#   script to run (if any) when the bot gets locked out of the channel
-#   because the channel is +i
-# need-key
-#   script to run (if any) when the bot gets locked out of the channel
-#   because it doesn't have the channel key
-# need-unban
-#   script to run (if any) when the bot gets banned from this channel
-# need-limit
-#   script to run (if any) when the bot gets locked out of the channel
-#   because the channel limit is full
-# flood-chan (number:seconds)
-#   how many channel messages in how many seconds is a flood
-#   not specifying or using number = 0 will not check chan floods!
-# flood-ctcp (number:seconds)
-#   how many channel messages in how many seconds is a flood
-#   not specifying or using number = 0 will not check ctcp floods!
-# flood-deop (number:seconds)
-#   how many deops in how many seconds is a mass de-op
-#   not specifying or using number = 0 will not check de-op floods!
-# flood-kick (number:seconds)
-#   how many kicks in how many seconds is a mass kick?
-#   not specifying or using number = 0 will not check mass kicks!
-# flood-join (number:seconds)
-#   how many joins/nick changes in how many seconds is a join flood?
-#   not specifying or using number = 0 will not check join floods!
-
-# note that "need-op", "need-invite", etc, are limited to 120 characters,
-# so if you want to so something more complicated, just write a proc,
-# and make them call your proc.
-
-# there are also a lot of options that can be turned on or off for each
-# channel.  to turn an option on, put a + in front of it.  to turn it off,
-# put a - in front of it.  i.e., to have auto-op, put:
-#   +autoop
-# to turn it off, put:
-#   -autoop
+# This is used for autoop and autovoice. If an op or voice joins a channel
+# while another op or voice is pending, the bot will attempt to put both
+# modes on one line.
+#   aop-delay 0   No delay is used.
+#   aop-delay X   An X second delay is used.
+#   aop-delay X:Y A random delay between X and Y is used.
+#
+# need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it does not have ops. This must be shorter than 120 characters.
+#    If you use scripts like getops.tcl or botnetop.tcl, you don't need
+#    to set this setting.
+#
+# need-invite { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs an invite to the channel. This must be shorter than 120
+#    characters. If you use scripts like getops.tcl or botnetop.tcl, you
+#    don't need to set this setting.
+#
+# need-key { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs the key to the channel. This must be shorter than 120
+#    characters. If you use scripts like getops.tcl or botnetop.tcl, you
+#    don't need to set this setting
+#
+# need-unban { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs to be unbanned on the channel. This must be shorter than
+#    120 characters. If you use scripts like getops.tcl or botnetop.tcl,
+#    you don't need to set this setting
+#
+# need-limit { putserv "PRIVMSG #lamest :let me in!" }
+#    This setting will make the bot run the script enclosed in brackets
+#    if it needs the limit to be raised on the channel. This must be
+#    shorter than 120 characters. If you use scripts like getops.tcl or
+#    botnetop.tcl, you don't need to set this setting
+#
+# flood-chan 10:60
+#    Set here how many channel messages in how many seconds from one
+#    host constitutes a flood. Setting this to 0 or 0:0 disables
+#    flood protection for the channel.
+#
+# flood-deop 3:10
+#    Set here how many deops in how many seconds from one host constitutes
+#    a flood. Setting this to 0 or 0:0 disables deop flood protection for
+#    the channel.
+#
+# flood-kick 3:10
+#    Set here how many kicks in how many seconds from one host constitutes
+#    a flood. Setting this to 0 or 0:0 disables kick flood protection for
+#    the channel.
+#
+# flood-join 5:60
+#    Set here how many joins in how many seconds from one host constitutes
+#    a flood. Setting this to 0 or 0:0 disables join flood protection for
+#    the channel.
+#
+# flood-ctcp 3:60
+#    Set here how many channel ctcps in how many seconds from one host
+#    constitutes a flood. Setting this to 0 or 0:0 disables ctcp flood
+#    protection for the channel.
+#
+# flood-nick 5:60
+#    Set here how many nick changes in how many seconds from one host
+#    constitutes a flood. Setting this to 0 or 0:0 disables nick flood
+#    protection for the channel.
+#
 
-#   when a ban is set, kick people who are on the channel and match the
-#   new ban?  (i.e., they were on the channel before the ban)
-channel set #lamest +enforcebans
+# There are many different options for channels which you can
+# define. They can be enabled or disabled by a plus or minus
+# in front of them.
+#
+# A complete list of all available channel settings:
+#
+# enforcebans
+#    When a ban is set, kick people who are on the channel and match
+#    the ban?
+#
+# dynamicbans
+#    Only activate bans on the channel when necessary? This keeps
+#    the channel's ban list from getting excessively long. The bot
+#    still remembers every ban, but it only activates a ban on the
+#    channel when it sees someone join who matches that ban.
+#
+# userbans
+#    Allow bans to be made by users directly? If turned off, the bot
+#    will require all bans to be made through the bot's console.
+#
+# dynamicexempts
+#    Only activate exempts on the channel when necessary? This keeps
+#    the channel's exempt list from getting excessively long. The bot
+#    still remembers every exempt, but it only activates a exempt on
+#    the channel when it sees a ban set that matches the exempt. The
+#    exempt remains active on the channel for as long as the ban is
+#    still active.
+#
+# userexempts
+#    Allow exempts to be made by users directly? If turned off, the
+#    bot will require all exempts to be made through the bot's console.
+#
+# dynamicinvites
+#    Only activate invites on the channel when necessary? This keeps
+#    the channel's invite list from getting excessively long. The bot
+#    still remembers every invite, but the invites are only activated
+#    when the channel is set to invite only and a user joins after
+#    requesting an invite. Once set, the invite remains until the
+#    channel goes to -i.
+#
+# userinvites
+#    Allow invites to be made by users directly? If turned off, the
+#    bot will require all invites to be made through the bot's console.
+#
+# autop
+#    Op users with the +o flag as soon as they join the channel?
+#    This is insecure and not recommended.
+#
+# bitch
+#    Only let users with +o) flag be opped on the channel?
+#
+# greet
+#    Say a user's info line when they join the channel?
+#
+# protectops
+#    Re-op a user with the +o flag if they get deopped?
+#
+# protectfriends
+#    Re-op a user with the +f flag if they get deopped?
+#
+# statuslog
+#    Log the channel status line every 5 minutes? This shows the bot's
+#    status on the channel (op, voice, etc.), The channel's modes, and
+#    the number of +m/+o/+v/+n/+b/+e/+I users on the channel. A sample 
+#    status line follows:
+#      
+#    [01:40] @#lamest (+istn) : [m/1 o/1 v/4 n/7 b/1 e/5 I/7]
+#
+# revenge
+#    Remember people who deop/kick/ban the bot, valid ops, or friends
+#    and punish them? Users with the +f flag are exempt from revenge.
+#
+# revengebot
+#    This is similar to to the 'revenge' option, but it only triggers
+#    if a bot gets deopped, kicked or banned.
+#
+# autovoice
+#    Voice users with the +v flag when they join the channel?
+#
+# secret
+#    Prevent this channel from being listed on the botnet?
+#
+# shared
+#    Share channel-related user info for this channel?
+#
+# cycle
+#    Cycle the channel when it has no ops?
+#
+# dontkickops
+#    Do you want the bot not to be able to kick users who have the +o 
+#    flag, letting them kick-flood for instance to protect the channel
+#    against clone attacks.
+#
+# inactive
+#    This prevents the bot from joining the channel (or makes it leave
+#    the channel if it is already there). It can be useful to make the
+#    bot leave a channel without loosing it's settings, channel-specific
+#    user flags, channel bans, and without affecting sharing.
+#
+# seen
+#    Respond to seen requests in the channel?  The seen module must be
+#    loaded for this to work.
+#
+# nodesynch
+#    Allow non-ops to perform channel modes? This can stop the bot from
+#    fighting with services such as ChanServ, or from kicking IRCops when
+#    setting channel modes without having ops.
 
-#   Only activate bans on the channel when necessary?  (This keeps the
-#   channel's ban list from getting excessively long.
-#   The bot still remembers every ban, but it only activates a ban on
-#   the channel when it sees someone join who matches that ban.)
+channel set #lamest +enforcebans
 channel set #lamest +dynamicbans
-
-#   allow bans to be made by users directly?  (if turned off, the bot will
-#   require all bans to be made through the bot's console)
 channel set #lamest +userbans
-
-#   only activate exempts on the channel when necessary?  (this keeps the
-#   channel's exempt list from getting excessively long.  the bot still
-#   remembers every exempt, but it only activates a exempt on the channel
-#   when it sees a ban set matching the exempt. The exempt remains active
-#   on the channel for as long as the ban is still active.
 channel set #lamest +dynamicexempts
-
-#   allow exempts to be made by users directly?  (if turned off, the bot will
-#   require all exempts to be made through the bot's console)
 channel set #lamest +userexempts
-
-#   only activate invites on the channel when necessary?  (this keeps the
-#   channel's invite list from getting excessively long.  the bot still
-#   remembers every invite, but the invites are only activated when the
-#   channel is set to invite only and a user joins after requesting an
-#   invite. Once set the invite remains until the channel goes to -i
 channel set #lamest +dynamicinvites
-
-#   allow invites to be made by users directly?  (if turned off, the bot will
-#   require all invites to be made through the bot's console)
 channel set #lamest +userinvites
-
-#   op users with the +o (op) flag as soon as they join the channel?
-#   (hint: this is a BAD IDEA)
-channel set #lamest -autoop
-
-#   only let users with +o (op) flag be channel ops?
-channel set #lamest -bitch
-
-#   say a user's info line when they join the channel?
 channel set #lamest +greet
-
-#   re-op a user with the +o (op) flag if they get deopped?
 channel set #lamest +protectops
-
-#   re-op a user with the +f (friend) flag if they get deopped?
 channel set #lamest +protectfriends
-
-#   log the channel status line every 5 minutes? (some people think
-#   it's annoying; I think it's neat)
 channel set #lamest +statuslog
-
-#   remember people who deop/kick/ban bots, valid ops or friends, and punish them?
-#   users with +f (friend) flag are exempt from revenge
 channel set #lamest +revenge
-
-#   this works similar to revenge, but it triggers only for valid bots and
-#   allows the deop or kick of an op
 channel set #lamest +revengebot
-
-#   voice users with +v (voice) flag when they join the channel?
 channel set #lamest +autovoice
-
-#   prevent this channel from being listed on the botnet?  (for paranoid
-#   people)
-channel set #lamest -secret
-
-#   share user channel info for this channel?
-channel set #lamest -shared
-
-#   cycle the channel when it becomes op-less?
 channel set #lamest +cycle
-
-#   do you want the bot not to be able to kick +o flag users ?
-#   letting them kick-flood for instance, to protect the channel against
-#   clone attacks
 channel set #lamest +dontkickops
+channel set #lamest -autoop
+channel set #lamest -bitch
+channel set #lamest -secret
+channel set #lamest -shared
 
-#   prevents the bot from joining the channel (or makes it leave the channel
-#   if it is already there).
-#   Can be useful to make the bot leave a channel without loosing it's
-#   settings (flood settings, all these "channel set" settings), user flags
-#   for this channel, bans for this channel, and without affecting any
-#   sharing
-channel set #lamest -inactive
-
-#   respond to seen requests in the channel?  (seen module must be loaded)
-channel set #lamest -seen
-
-#   allow non-ops to perform channel modes?  (Stops bot from
-#   fighting with services such as ChanServ)
-channel set #lamest +nodesynch
-
-# here's a shorter example:
-channel add #botcentral {
-  chanmode "+mntisl 1"
-  idle-kick 1
-}
-channel set #botcentral +bitch +enforcebans -greet +revenge
-
+# Here is a shorter example:
+#
+#  channel add #botcentral {
+#    chanmode "+mntisl 1"
+#    idle-kick 1
+#  }
+#  channel set #botcentral +bitch +enforcebans -greet +revenge
 
-##### SERVER MODULE #####
 
-# this provides the core server support (removing this is equivalent to
-# the old NO_IRC define)
+#### SERVER MODULE ####
+
+# This module provides the core server support. You have to load this
+# if you want your bot to come on IRC. Not loading this is equivalent
+# to the old NO_IRC define.
 loadmodule server
 
-# [0/1/2/3/4/5] What is your network?
-# 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
-# 4 = Efnet +e/+I hybrid, 5 = Others
+# What is your network?
+#   0 = EFnet (non +e/+I hybrid)
+#   1 = IRCnet
+#   2 = Undernet
+#   3 = DALnet
+#   4 = EFnet +e/+I hybrid
+#   5 = Others
 set net-type 0
 
-##### variables:
-# the nick of the bot, that which it uses on IRC, and on the botnet
-# unless you specify a separate botnet-nick
+# Set the nick the bot uses on IRC, and on the botnet
+# unless you specify a separate botnet-nick, here.
+
 set nick "Lamestbot"
 
-# an alternative nick to use if the nick specified by 'set nick' is
-# unavailable. All '?' characters will be replaced by a random number.
-set altnick "Llamabot"
+# Set the alternative nick which the bot uses on IRC if the nick specified
+# by 'set nick' is unavailable. All '?' characters will be replaced by random
+# numbers.
 
-# what to display in the real-name field for the bot
+set altnick "Llamab?t"
+
+# Set what should be displayed in the real-name field for the bot on IRC.
 set realname "/msg LamestBot hello"
 
-# script to run (if any) when first connecting to a server
+# Set here a script to run (if any) when first connecting to a server.
 set init-server { putserv "MODE $botnick +i-ws" }
 
-# if no port is specified on a .jump, which port should I use?
+# Set the default port which should be used if none is specified with
+# '.jump' or in 'set servers'.
 set default-port 6667
 
-# the server list -- the bot will start at the first server listed, and cycle
-# through them whenever it's disconnected
-# (please note: you need to change these servers to YOUR network's servers)
+# This is the bot's server list. The bot will start at the first server listed, 
+# and cycle through them whenever it gets disconnected. You need to change these 
+# servers to YOUR network's servers.
 set servers {
   you.need.to.change.this:6667
+  another.example.com:7000
 }
 
-# [0/1] if the bot's nickname is changed (for example, if the intended
-# nickname is already in use) keep trying to get the nick back?
+# This setting makes the bot try to get his original nickname back if its
+# primary nickname is already in use.
 set keep-nick 1
 
-# [0/1] if this is set, a leading '~' on user at hosts WON'T be stripped off
+# Set this to 1 if you don't want your the bot to strip a leading '~'
+# on user at hosts.
 set strict-host 0
 
-# [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
-# Normally it tells the DCC user that the CHAT or SEND has been rejected
-# because they don't have access, but sometimes IRC server operators
-# detect bots that way.
+# This setting makes the bot squelch the error message when rejecting a DCC
+# CHAT or SEND. Normally it tells the DCC user that the CHAT or SEND has
+# been rejected because they don't have access.
+# Please note, sometimes IRC server operators detect bots that way.
 set quiet-reject 1
 
-# [0/1] answer lower case ctcps (non rfc compliant)
-# mIRC will do this, most other clients will NOT
+# If you want your bot to answer lower case ctcp requests (non rfc-
+# compliant), set this setting to 1. mIRC will do this, most other
+# clients will not.
 set lowercase-ctcp 0
 
-# answer HOW MANY stacked ctcps at once
+# Set how many ctcps should be answered at once.
 set answer-ctcp 3
 
-# setting any of the following with how many == 0 will turn them off
-# how many msgs in how many seconds from the same host constitutes a flood?
+# Set here how many msgs in how many seconds from one host constitutes
+# a flood. If you set this to 0:0, msg flood protection will be disabled.
 set flood-msg 5:60
-# how many CTCPs in how many seconds?
+
+# Set here how many ctcps in how many seconds from one host constitutes
+# a flood. If you set this to 0:0, ctcp flood protection will be disabled.
 set flood-ctcp 3:60
 
-# [0/1] even if all the servers are down, cycle forever and keep trying to
-# connect?
+# This settings makes the bot cycle forever through the server list until
+# it successfully connects to one.
 set never-give-up 1
 
-# [0/1] If this setting is 0 then the eggdrop keeps a separate list of the names
-# irc servers call themselves, retaining what you entered in the config file.
-# setting it to 1 will cause the bot to replace your entry with what
-# the server actually calls itself
+# Often, IRC servers call themselves a name other than their actual
+# hostname. If you want eggdrop to replace your entry in the config
+# file with this name, set this to 1. If you set this setting to 0,
+# eggdrop will keep a separate list of what IRC servers call themselves.
 set strict-servernames 0
 
-# number of seconds to wait between each server connect (0 = no wait)
-# useful for preventing ircu throttling
-# setting this too low could make your server admins *very* unhappy
+# This setting defines how long eggdrop should wait before moving from one
+# server to another on disconnect. If you set 0 here, eggdrop will not wait
+# at all and will connect instantly. Setting this too low could result in
+# your bot being K:Lined.
 set server-cycle-wait 60
 
-# how many seconds to wait for a response when connecting to a server
-# before giving up and moving on?
+# Set here how long eggdrop should wait for a response when connecting to a
+# server before giving up and moving on to next server.
 set server-timeout 60
 
-# if the number of servers on the net gets below this number, it will
-# jump to a new server (i.e., it will assume it's on the losing end of a
-# netsplit) -- set to 0 to turn off
-# [most irc networks use TS or ND now, so it's to your advantage to turn
-# this off]
+# If the number of servers on the net gets below this number, the bot
+# will jump to a new server (it will assume it's on the losing end of
+# a netsplit). Set this to 0 to turn off. If your bot is running on
+# any major IRC network, this should probably be turned off.
 set servlimit 0
 
-# [0/1] check for stoned servers? (i.e. Where the server connection has
-# died, but eggdrop hasn't been notified yet).
+# Set this to 1 if eggdrop should check for stoned servers? (where the
+# server connection has died, but eggdrop hasn't been notified yet).
 set check-stoned 1
 
-# [0/1] enable console mode 'r'?  this mode shows every raw message from the
-# server to owners with console 'r' selected -- will take a bit more CPU.
-# NOTE: This is a large security hole, allowing people to see mis-sent
-#       messages to the bot containing passwords
-# This is now restricted to +n users only. Please choose your owners with care.
+# This setting allows you the logging of all information received from the
+# server via console mode 'r'.
+# NOTE: This is a large security hole, allowing people to see user passwords.
+# This is now restricted to +n users only. Please choose your owners with
+# care.
 set use-console-r 0
 
-# [0/1] enable logging of all information sent *to* a server, via console mode 'v'
+# This setting allows you the logging of all information sent to the server
+# via console mode 'v'.
 # NOTE: This is a large security hole, allowing people to see passwords.
-# This is now restricted to +n users only. Please choose your owners with care.
+# This is now restricted to +n users only. Please choose your owners with
+# care.
 set debug-output 0
 
-# [0/1] exit if the server sends a ERROR message?
+# If you want your bot to exit the server if it receives an ERROR message,
+# set this to 1.
 set serverror-quit 1
 
-# maximum number of lines to queue to the server.
-# if you're going to dump large chunks of text to people over irc,  you
-# will probably want to raise this -- most people are fine at 300 though
+# Set here the maximum number of lines to queue to the server. If you're
+# going to dump large chunks of text to people over IRC, you will probably
+# want to raise this. 300 is fine for most people though.
 set max-queue-msg 300
 
-# [0/1] trigger bindings for ignored users?
+# If you want eggdrop to trigger binds for ignored users, set this to 1.
 set trigger-on-ignore 0
 
-# [0/1] allow a msg being twice in a queue?
+# Allow identical messages in the mode queue?
 set double-mode 0
+
+# Allow identical messages in the server queue?
 set double-server 0
+
+# Allow identical messages in the help queue?
 set double-help 0
 
-# [0/1/2] do you want the bot to optimize the kicking queues? Set to 2 if you
-# want the bot to change queues if somebody parts or changes nickname.
-# ATTENTION: Setting 2 is very CPU intensive
+# This optimizes the kick queue. It also traces nick changes and parts in
+# the channel and changes the kick queue accordingly. There are three
+# different options for this setting:
+#   0 = Turn it off.
+#   1 = Optimize the kick queue by summarizing kicks.
+#   2 = Trace nick changes and parts on the channel and change the queue
+#       accordingly. For example, bot will not try to kick users who have
+#       already parted the channel.
+# ATTENTION: Setting 2 is very CPU intensive.
 set optimize-kicks 1
 
-##### SERVER MODULE - net-type 5 specific features (other networks) #####
+### SERVER MODULE - OTHER NETWORKS (net-type 5) ###
 
-# [0/1] some nets use umode +r to mean a restricted connection. If this is your
-# case, and you want your bot to leave restricted servers and jump to the
-# next one on his server list, then set it to 1.
-# Automatically set to 0 for net-type 0/2/3/4, set to 1 for net-type 1.
-# Only use this if you set net-type 5
+# This settings defines how umode +r is understood by eggdrop. Some
+# networks use +r to indicate a restricted connection. If this is your
+# case, and you want your bot to leave restricted servers and jump to
+# the next server on its list, then set it to 1.
 #set check-mode-r 1
 
-# This variable sets the maximum nick length allowed on the network. Most
-# only support 9. The maximum supported by eggdrop is 32.
+# This setting allows you to specify the maximum nick-length supported by
+# your network. The default setting is 9. The maximum supported length by
+# eggdrop is 32.
 #set nick-len 9
 
-##### CTCP MODULE #####
+#### CTCP MODULE ####
 
-# this provides the normal ctcp replies that you'd expect *RECOMMENDED*
+# This module provides the normal ctcp replies that you'd expect.
+# Without it loaded, CTCP CHAT will not work. The server module
+# is required for this module to function.
 loadmodule ctcp
 
-# several variables exist to better blend your egg in.  they are
-# ctcp-version, ctcp-finger, and ctcp-userinfo.  you can use set
-# to set them to values you like.
-
-# [0/1/2] 0: normal behavior. 1: bot ignores all CTCPs, except for CTCP
-# CHATs & PINGs requested by +o flag users. 2: bot doesn't answer more
-# than C CTCPs in S seconds.
-# C/S are defined by the set flood-ctcp C:S (cf. server module)
+# Set here how the ctcp module should answer ctcps. There are 3 possible
+# operating modes:
+#   0: Normal behavior is used.
+#   1: The bot ignores all ctcps, except for CHAT and PING requests
+#      by users with the +o flag.
+#   2: Normal behavior is used, however the bot will not answer more
+#      than X ctcps in Y seconds (defined by 'set flood-ctcp').
 set ctcp-mode 0
 
+# There are also several variables to help make your bot less noticeable.
+# They are: ctcp-version, ctcp-finger, and ctcp-userinfo. You can use set to set
+# them to values you'd like.
+
 
-##### IRC MODULE #####
+#### IRC MODULE ####
 
-# this module provides ALL NORMAL IRC INTERACTION, if you want the normal
-# join & maintain channels stuff, this is the module.
+# This module provides basic IRC support for your bot. You have to
+# load this if you want your bot to come on IRC. The server and channels
+# modules must be loaded for this module to function.
 loadmodule irc
 
-# [0/1] define this if you want to bounce all server bans
+# Set this to 1 if you want to bounce all server bans.
 set bounce-bans 1
 
-# [0/1] define this if you want to bounce all the server modes
+# Set this to 1 if you want to bounce all the server modes.
 set bounce-modes 0
 
-# If there are more than max-bans active bans on a channel, then the
-# bot won't try to put more bans. Thus it won't flood the irc server.
-# ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
+# Set here the maximum number of bans you want the bot to set on a channel.
+# Eggdrop will not place any more bans if this limit is reached. Undernet
+# and IRCnet currently allow 30 bans, EFnet allows 20, and DALnet allows 100.
 set max-bans 20
 
-# There is a global limit for +b/+e/+I modes. This limit is set to 30 on
-# 2.10 irc servers.
+# There is a global limit for +b/+e/+I modes. This limit is currently set to
+# 30 on IRCu 2.10 servers.
 set max-modes 30
 
-# [0/1] Do you want the bot to kick for control character/ctcp avalanches
-# to a channel?
-# Remember that if it does, as it won't ban them, it can be at the origin
-# of a nice kick-flood
+# Set this to 1 if you want the bot to kick for control character/ctcp
+# avalanches to a channel. Remember that if it does, it won't ban them.
+# This can start kick floods.
 set kick-fun 0
 
-# [0/1] Do you want the bot to ban for control character/ctcp avalanches
-# to a channel?
-# Can prevent the above described kick-flood, but can also fill the banlist
+# Set this to 1 if you want the bot to ban for control character/ctcp
+# avalanches to a channel. Can prevent kick floods, but also fill the
+# banlist.
 set ban-fun 0
 
-# [0/1] let users introduce themselves to the bot via 'hello'?
+# If you want people to be able to add themselves to the bot's userlist
+# with the default userflags (defined above in the config file) via the
+# 'hello' msg command, set this to 1.
 set learn-users 0
 
-# time (in seconds) to wait for someone to return from a netsplit
+# Set here the time (in seconds) to wait for someone to return from
+# a netsplit (i.e. wasop will expire afterwards). Set this to 1500
+# on IRCnet since it's nick delay stops after 30 minutes.
 set wait-split 600
 
-# time (in seconds) that someone must have been off-channel before
-# re-displaying their info
+# Set here the time (in seconds) that someone must have been off-channel
+# before re-displaying their info line.
 set wait-info 180
 
-# this is the maximum number of bytes to send in the arguments to mode's
-# sent to the server, most servers default this to 200, so it should
-# be sufficient
+# Set this to the maximum number of bytes to send in the arguments
+# of modes sent to the server. Most servers default this to 200.
 set mode-buf-length 200
 
-# many irc ops check for bots that respond to 'hello'.  you can change this
-# to another word by un-commenting the following two lines, and changing
-# "myword" to the word you want to use instead of 'hello' (it must be a
-# single word)
-# novice users are not expected to understand what these two lines do; they
-# are just here to help you.  for more information on 'bind', check the file
-# 'tcl-commands.doc'
+# Many IRCops find bots by seeing if they reply to 'hello' in a msg. 
+# You can change this to another word by un-commenting the following
+# two lines, and changing "myword" to the word wish to use instead of
+# 'hello'. It must be a single word.
 #unbind msg - hello *msg:hello
 #bind msg - myword *msg:hello
 
-# Many takeover attempts occur due to lame users blindly /msg ident'n to
-# the bot without checking if the bot is the bot.
-# We now unbind this command by default to discourage them
+# Many takeover attempts occur due to lame users blindly /msg ident'ing to
+# the bot and attempting to guess passwords. We now unbind this command by
+# default to discourage them. You can enable this command by un-commenting
+# the following two lines.
 unbind msg - ident *msg:ident
 unbind msg - addhost *msg:addhost
 
-# If you or your users use many different hosts and wants to
-# be able to add it by /msg'ing you need to remove the
-# unbind ident line above or bind it to another word.
-#bind msg - myidentword *msg:ident
-
-# [0/1] If you are so lame you want the bot to display peoples info lines, even
-# when you are too lazy to add their chanrecs to a channel, set this to 1
+# If you are so lame you want the bot to display peoples info lines, even
+# when you are too lazy to add their chanrecs to a channel, set this to 1.
 # *NOTE* This means *every* user with an info line will have their info
-# display on EVERY channel they join (provided they have been gone longer than
-# wait-info)
+# display on EVERY channel they join (provided they have been gone longer
+# than wait-info).
 set no-chanrec-info 0
 
-##### IRC MODULE - net-type 1 specific features (IRCnet) #####
+### IRC MODULE - IRCnet SPECIFIC FEATURES (net-type 1) ###
 
-# Don't modify the following settings if you don't use IRCnet. The defaults following
-# values are harmless for you.
+# Attention: Use these settings *only* if you set 'net-type' to 1!
 
-# [0/1] define this if you want to bounce all server exemptions (+e modes)
-#  * This is an IRCNET feature
+# Set this to 1 if you want to bounce all server exemptions (+e modes).
 set bounce-exempts 0
 
-# [0/1] define this if you want to bounce all server invitations (+I modes)
-#  * This is an IRCNET feature
+# Set this to 1 if you want to bounce all server invitations (+I modes).
 set bounce-invites 0
 
-# If there are more than max-exempts active +e modes on a channel, then
-# the bot won't try to put more exemptions. Thus it won't flood the irc
-# server. Only 2.10 servers are concerned by these +e modes.
-#  * This is an IRCNET feature
+# Set here the maximum number of exempts you want eggdrop to set
+# on a channel. Eggdrop will not place any more exempts if this
+# limit is reached.
 set max-exempts 20
 
-# If there are more than max-invites active +I modes on a channel, then
-# the bot won't try to put more invitations. Thus it won't flood the irc
-# server. Only 2.10 irc servers are concerned by these +I modes.
-#  * This is an IRCNET feature
+# Set here the maximum number of invites you want eggdrop  to set
+# on a channel. Eggdrop will not place any more invites if this
+# limit is reached.
 set max-invites 20
 
-# The following lines should be left un-commented unless the default values
-# are being over-ridden. By default exempts and invites are on for IRCnet
-# and hybrid EFnet, but off for all other networks. This behavior can be
-# modified by the following 2 flags. If you're network doesn't support e/I
-# modes then you'll be unable to use these features.
-#
-# [0/1] Do you want to enable exempts?
-# set use-exempts 0
-
-# [0/1] Do you want to use invites?
-# set use-invites 0
-
-# [0/1] Prevent mixing normal modes and +I/+e invite modes?
-# At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
-# so leave this flag set to 1. The servers will probably change their
-# behavior in the future, so you should first check before accepting the
-# default.
+# The following settings should be left commented unless the default values
+# are being overridden. By default, exempts and invites are on for IRCnet,
+# but off for all other large networks. This behavior can be modified with
+# the following 2 flags. If your network doesn't support +e/+I modes then you
+# will be unable to use these features.
+#
+# Do you want to enable exempts?
+#set use-exempts 0
+
+# Do you want to use invites?
+#set use-invites 0
+
+# At the moment, the current IRCnet IRCd version (2.10) doesn't support the mixing
+# of b,o and v modes with e and I modes. This might be changed in the future, so
+# use 1 at the moment for this setting.
 set prevent-mixing 1
 
-##### IRC MODULE - net-type 5 specific features (other networks) #####
+### IRC MODULE - OTHER NETWORKS (net-type 5) ###
 
-# kick-method defines how kicks (when enforcing bans) should be made:
-#    0 = kick all nicks at once in one command
-#    X = kick X users at a time
-#
-# Automatically set by net-type:
-#  net-type 0, 2, 3 & 4 sets this to 1
-#  net-type 1 sets this to 4
-#
-# If you use net-type 5, you must set this yourself (default is 1)
+# Attention: Use these settings *only* if you set 'net-type' to 5!
+
+# If your network supports more users per kick command then 1, you can
+# change this behavior here. Set this to the number of users to kick at
+# once, or set this to 0 for all at once.
 #set kick-method 1
 
-# some networks allow you to stack lots of channel modes into one
-# line.
-# they're all guaranteed to support at least 3, so that's the default,
-# but if you know your network supports more, you may want to adjust
-# this value. this value must be less than or equal to 6.
-# Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
-# 6 for net-type 2/3.
-# Only use this if you set net-type 5
+# Some networks allow you to stack lots of channel modes into one line.
+# They're all guaranteed to support at least 3, so that's the default.
+# If you know your network supports more, you may want to adjust this.
 #set modes-per-line 3
 
-# [0/1] Some networks don't include the +l limit and +k or -k key modes
+# Some networks don't include the +l limit and +k or -k key modes
 # in the modes-per-line (see above) limitation. Set include-lk to 0 for
-# those networks.
-# Automatically set to 1 for net-type 1/2/3, set to 0 for net-type 0/4.
-# Only use this if you set net-type 5.
+# these networks.
 #set include-lk 1
 
-# [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
-# exactly what's needed
-# Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
-# Only use this if you set net-type 5
+# Set this to 1 if your network uses IRCu2.10.01 specific /who requests.
+# Eggdrop can, therefore, ask only for exactly what's needed.
 #set use-354 0
 
-# [0/1] use rfc 1459 compliant string matching routines?
-# All networks apart from Dalnet comply with rfc 1459, so you should only
-# disable it on Dalnet or networks which use Dalnet's code.
+# If your network doesn't use rfc 1459 compliant string matching routines,
+# set this to 0.
 #set rfc-compliant 1
 
 
-##### TRANSFER MODULE #####
+#### TRANSFER MODULE ####
 
-# un-comment this line to load the transfer module, this provides
-# dcc send/get support and bot userfile transfer support (not sharing)
+# The transfer module provides dcc send/get support and userfile transfer
+# support for userfile sharing. Un-comment the next line to load it if you 
+# need this functionality.
 #loadmodule transfer
 
-##### variables:
-# set maximum number of simultaneous downloads to allow for each user
+# Set here the maximum number of simultaneous downloads to allow for
+# each user.
 set max-dloads 3
 
-# set the block size for dcc transfers (ircII uses 512 bytes, but admits
-# that may be too small -- 1024 is standard these days)
-# set this to 0 to use turbo-dcc (recommended)
+# Set here the block size for dcc transfers. ircII uses 512 bytes,
+# but admits that may be too small. 1024 is standard these days.
+# Set this to 0 to use turbo-dcc (recommended).
 set dcc-block 1024
 
-# [0/1] copy files into the /tmp directory before sending them?  this is
-# useful on most systems for file stability.  (someone could move a file
-# around while it's being downloaded, and mess up the transfer.)  but if
-# your directories are NFS mounted, it's a pain, and you'll want to set
-# this to 0. If you are low on disk space, you may want to set this to 0.
+# Enable this setting if you want to copy files into the /tmp directory
+# before sending them. This is useful on most systems for file stability,
+# but if your directories are NFS mounted, it's a pain, and you'll want
+# to set this to 0. If you are low on disk space, you may also want to
+# set this to 0.
 set copy-to-tmp 1
 
-# time (in seconds) that a dcc file transfer can remain inactive
-# before being timed out
+# Set here the time (in seconds) to wait before an inactive transfer
+# times out.
 set xfer-timeout 30
 
 
-##### SHARE MODULE #####
+#### SHARE MODULE ####
 
-# this provides the userfile sharing support
-# (this requires the channels & transfer modules)
+# This module provides userfile sharing support between two directly
+# linked bots. The transfer and channels modules are required for this
+# module to correctly function. Un-comment the following line to load
+# the share module.
 #loadmodule share
 
-##### variables:
-# [0/1] When two bots get disconnected this flag allows them to create
-# a resync buffer which saves all changes done to the userfile during
-# the disconnect. So, when they reconnect, they will not have to transfer
-# the complete user file, but instead, just send the resync buffer.
-# If you have problems with this feature please tell us. Take a look at
-# doc/BUG-REPORT first though.
+# Settings in this section must be un-commented before setting.
+
+# When two bots get disconnected, this setting allows them to create a
+# resync buffer which saves all changes done to the userfile during
+# the disconnect. When they reconnect, they will not have to transfer 
+# the complete user file, but, instead, just send the resync buffer.
 #set allow-resync 0
 
-# this specifies how long to hold another bots resync data for before
-# flushing it
+# This setting specifies how long to hold another bots resync data
+# before flushing it.
 #set resync-time 900
 
-# [0/1] when sharing user lists, DON'T ACCEPT global flag changes from other bots?
-# NOTE: the bot will still send changes made on the bot, it just wont accept
-# any global flag changes from other bots
+# When sharing user lists, DON'T ACCEPT global flag changes from other bots?
+# NOTE: The bot will still send changes made on the bot, it just wont accept
+# any global flag changes from other bots.
 #set private-global 0
 
-# when sharing user lists, if private-global isn't set, which global flag
-# changes from other bots should be ignored ?
+# When sharing user lists, if private-global isn't set, which global flag
+# changes from other bots should be ignored?
 #set private-globals "mnot"
 
-# [0/1] when sharing user lists, DON'T ACCEPT any userfile changes from other
-# bots?
-# NOTE: paranoid people should use this feature on their hub bot - this
-# will force all +host/+user/chpass/etc. changes to be made via the hub
+# When sharing user lists, don't accept ANY userfile changes from other
+# bots? Paranoid people should use this feature on their hub bot. This
+# will force all userlist changes to be made via the hub.
 #set private-user 0
 
-# [0/1] this setting makes the bot discard it's own bot records in favor of
-# the ones sent by the hub. Note: This only works with hubs that are v1.5.1
-# _or higher_.
+# This setting makes the bot discard it's own bot records in favor of
+# the ones sent by the hub.
+# NOTE: No passwords or botflags are shared, only ports and
+# address are added to sharing procedure. This only works with hubs that
+# are v1.5.1 or higher.
 #set override-bots 0
 
 
-##### COMPRESS MODULE #####
+#### COMPRESS MODULE ####
 
-# The compress module provides support for file compression. This allows the
-# bot to transfer compressed user files and therefore save a significant
-# amount of bandwidth, especially on very active hubs.
+# This module provides provides support for file compression. This allows the
+# bot to transfer compressed user files and therefore save a significant amount
+# of bandwidth. The share module must be loaded to load this module. Un-comment
+# the following line to the compress module.
 #loadmodule compress
 
-# [0/1] allow compressed sending of user files. The user files
-# are compressed with the compression level defined in `compress-level'.
-#set share-compressed 1
+# Allow compressed sending of user files? The user files are
+# compressed with the compression level defined in `compress-level'.
+set share-compressed 1
 
-# [0-9] default compression level used.
+# This is the default compression level used.
 #set compress-level 9
 
 
-##### FILESYSTEM MODULE #####
+#### FILESYSTEM MODULE ####
 
-# un-comment this line to load the file system module, this provides
-# an area within the bot where you can store files
+# This module provides an area within the bot where users can store
+# files. With this module, the bot is usable as a file server. The
+# transfer module is required for this module to function. Un-comment
+# the following line to load the filesys module.
 #loadmodule filesys
 
-# this is the 'root' directory for the file system (set it to "" if you
-# don't want a file system)
+# Set here the 'root' directory for the file system.
 set files-path "/home/mydir/filesys"
 
-# if you want to allow uploads, set this to the directory uploads should be
-# put into
+# If you want to allow uploads, set this to the directory uploads
+# should be put into. Set this to "" if you don't want people to
+# upload files to your bot.
 set incoming-path "/home/mydir/filesys/incoming"
 
-# [0/1] alternately, you can set this, and uploads will go to the current
-# directory that a user is in
+# If you don't want to have a central incoming directory, but instead
+# want uploads to go to the current directory that a user is in, set
+# this setting to 1.
 set upload-to-pwd 0
 
-# eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
-# to keep track of its own file system info -- if you can't do that (like
-# if the dcc path isn't owned by yours) or you just don't want it to do
-# that, specify a path here where you'd like all the database files to
-# be stored instead (otherwise, just leave it blank)
+# Eggdrop creates a '.filedb' file in each subdirectory of your file area
+# to keep track of its own file system information. If you can't do that (for
+# example, if the dcc path isn't owned by you, or you just don't want it to do
+# that) specify a path here where you'd like all of the database files to be
+# stored instead.
 set filedb-path ""
 
-# set maximum number of people that can be in the file area at once
-# (0 to make it effectively infinite)
+# Set here the maximum number of people that can be in the file area at once.
+# Setting this to 0 makes it effectively infinite.
 set max-file-users 20
 
-# maximum allowable file size that will be received, in K
-# (default is 1024K = 1M). 0 makes it effectively infinite.
+# Set here the maximum allowable file size that will be received (in kb).
+# Setting this to 0 makes it effectively infinite.
 set max-filesize 1024
 
 
-##### NOTES MODULE #####
+#### NOTES MODULE ####
 
-# this provides support for storing of notes for users from each other
-# notes between currently online users is supported in the core, this is
-# only for storing the notes for later retrieval, direct user->user notes
-# are built-in
+# This module provides support for storing of notes for users from each
+# other. Note sending between currently online users is supported in the
+# core, this is only for storing the notes for later retrieval.
 loadmodule notes
 
-# the notefile: where private notes between users are stored
+# Set here the filename where private notes between users are stored.
 set notefile "LamestBot.notes"
 
-# maximum number of notes to allow to be stored for each user
-# (to prevent flooding)
+# Set here the maximum number of notes to allow to be stored for
+# each user (to prevent flooding).
 set max-notes 50
 
-# time (in days) to let stored notes live before expiring them
+# Set here how long (in days) to store notes before expiring them.
 set note-life 60
 
-# [0/1] allow users to specify a forwarding address for forwarding notes
-# to another bot
+# Set this to 1 if you want to allow users to specify a forwarding
+# address for forwarding notes to another account on another bot.
 set allow-fwd 0
 
-# [0/1] set this to 1 if you want the bot to let people know hourly if they
-# have any notes
+# Set this to 1 if you want the bot to let people know hourly if they
+# have any notes.
 set notify-users 1
 
-# [0/1] set this to 1 if you want the bot to let people know on join if they
-# have any notes
+# Set this to 1 if you want the bot to let people know on join if they
+# have any notes.
 set notify-onjoin 1
 
-# comment out this next line, otherwise your bot won't start
+# Comment out this next line. Otherwise, your bot won't start.
 die "You didn't edit your config file like you were told, did you?"
 
 
-##### CONSOLE MODULE #####
+#### CONSOLE MODULE ####
 
-# this module provides storage of console settings when you exit the bot
-# (or .store)
+# This module provides storage of console settings when you exit the
+# bot or type .store on the partyline.
 loadmodule console
 
-##### variables:
-# [0/1] save users console settings automatically? (otherwise they have to use
-# .store)
-set console-autosave 0
+# Save users console settings automatically? Otherwise, they have
+# to use the .store command.
+set console-autosave 1
 
-# [0-99999] if a user doesn't have any console settings saved, which channel
+# If a user doesn't have any console settings saved, which channel
 # do you want them automatically put on?
 set force-channel 0
 
-# [0/1] display a user's global info line when they join a botnet channel?
+# Enable this setting if a user's global info line should be displayed
+# when they join a botnet channel.
 set info-party 0
 
 
-##### WOOBIE MODULE #####
+#### WOOBIE MODULE ####
 
-# this serves absolutely no purpose and is for demonstrative
-# purposes only
+# This is for demonstrative purposes only. If you are looking for starting
+# point in writing modules, woobie is the right thing.
 #loadmodule woobie
 
 
-##### SEEN MODULE #####
+#### SEEN MODULE ####
 
-# this module provides seen commands via msg, on channel or via
-# dcc, similar to the various scripts
+# This module provides very basic seen commands via msg, on channel or via dcc.
+# This module works only for users in the bot's userlist. If you are looking for
+# a better and more advanced seen module, try the gseen module by G'Quann. You
+# can find it at http://www.visions-of-fantasy.de/gseen.mod/.
 #loadmodule seen
 
 
-##### BLOWFISH MODULE #####
-
-##### IF YOU DON'T READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
+#### BLOWFISH MODULE ####
 
-# Choose your encryption method now, 'cause once you do, it ain't
-# changing 'til you get a new userfile, capish?  At the moment, there
-# is only one encryption option: blowfish
-
-# un-comment this line to load blowfish, the encryption module
-# for the bot. the bot will not start without it loaded. it is 
-# commented out to make sure you read the whole config file.
-# this is checkmodule, because during .restart the module will 
-# already be loaded.
+# IF YOU DON'T READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
+# Eggdrop encrypts its userfile, so users can have secure passwords.
+# Please note that when you change your encryption method later (i.e.
+# using other modules like a md5 module), you can't use your current
+# userfile anymore. Eggdrop will not start without an encryption module.
 #checkmodule blowfish
 
 
-##### ASSOC MODULE #####
+#### ASSOC MODULE ####
 
-# un-comment this line to load assoc support, i.e. naming channels on
-# the botnet
+# This module provides assoc support, i.e. naming channels on the botnet.
+# You can load it by un-commenting the following line.
 #loadmodule assoc
 
 
-##### WIRE MODULE #####
+#### WIRE MODULE ####
 
-# this module provides all the standard .wire commands via dcc.
-# it's an encrypted partyline communication tool, compatible with wire.tcl
-# un-comment this line to load it
+# This module provides all the standard .wire commands via dcc. It is an 
+# encrypted partyline communication tool, compatible with wire.tcl. An
+# encryption module must be loaded to use this module. Un-comment the
+# following line to load the wire module.
 #loadmodule wire
 
-##### UPTIME MODULE #####
+#### UPTIME MODULE ####
 
-# this module reports uptime statistics to http://uptime.eggheads.org
-# go look and see what your uptime is! (it will show up after 9 hours or so)
-# (this requires the server module)
+# This module reports uptime statistics to http://uptime.eggheads.org.
+# Go look and see what your uptime is! It takes about 9 hours to show up,
+# so if your bot isn't listed, try again later. The server module must be
+# loaded for this module to function.
+# 
+# Information sent to the server includes the bot's uptime, botnet-nick,
+# server, version, and IP address. This information is stored in a temporary 
+# logfile for debugging purposes only. The only publicly available information
+# will be the bot's botnet-nick, version and uptime. If you do not wish for this
+# information to be sent, comment out the following line.
 loadmodule uptime
 
 ##### SCRIPTS #####
 
-# these are some commonly loaded (and needed) scripts.
+# This is a good place to load scripts to use with your bot.
+
+# This line loads script.tcl from the scripts directory inside your eggdrop's
+# directory. All scripts should be put there, although you can place them where
+# you like as long as you can supply a fully qualified path to them.
+#
+# source scripts/script.tcl
+
 source scripts/alltools.tcl
 source scripts/action.fix.tcl
 
-# use this for Tcl and eggdrop downwards compatibility
+# Use this script for Tcl and eggdrop downwards compatibility.
+# NOTE: This can also cause problems with some newer scripts.
 source scripts/compat.tcl
 
-# This script provides many useful minor informational commands
-# (like setting user's URLs, email address, etc). You can modify
-# it to add extra entries, you might also want to modify help/userinfo.help
-# and help/msg/userinfo.help to change the help files.
+# This script provides many useful informational functions, like setting 
+# users' URLs, e-mail address, ICQ numbers, etc. You can modify it to add
+# extra entries
 source scripts/userinfo.tcl
 loadhelp userinfo.help
Index: eggdrop1.6/eggdrop.simple.conf
diff -u eggdrop1.6/eggdrop.simple.conf:1.14 eggdrop1.6/eggdrop.simple.conf:1.15
--- eggdrop1.6/eggdrop.simple.conf:1.14	Thu Nov 29 17:25:36 2001
+++ eggdrop1.6/eggdrop.simple.conf	Thu Dec 13 23:43:10 2001
@@ -1,10 +1,10 @@
 #! /path/to/executable/eggdrop
 # ^- Set that to the directory eggdrop is in, i.e. "#! /home/lamest/egg/eggdrop"
 #
-# $Id: eggdrop.simple.conf,v 1.14 2001/11/29 23:25:36 guppy Exp $
+# $Id: eggdrop.simple.conf,v 1.15 2001/12/14 05:43:10 guppy Exp $
 #
 # This is a sample configuration file for your bot.  You will definitely
-# want to edit this, to set up your bot.  Right now, it creates a bot called
+# want to edit this to set up your bot. Right now, it creates a bot called
 # "LamestBot" which sits on the channel #lamest.
 #
 # More options can be found in files in doc/settings/.
@@ -15,8 +15,10 @@
 #
 # PLEASE EDIT THIS FILE COMPLETELY! YOUR BOT WILL NOT FUNCTION PROPERLY IF
 # YOU DO NOT CONFIGURE IT CORRECTLY! WE CAN NOT STRESS THIS ENOUGH!
+#
+# More options can be found in the files in doc/settings/.
 
-# don't edit these 12 lines!!
+# Don't edit the following 12 lines.
 set mod-path "modules/"
 set help-path "help/"
 set text-path "text/"
@@ -27,30 +29,32 @@
 loadmodule irc
 loadmodule notes
 loadmodule console
-loadmodule uptime
 checkmodule blowfish
 
-# start configuring here!
+# Start configuring here!
+
+##### Settings:
 
-##### variables:
+# Set the nick the bot uses on IRC, and on the botnet
+# unless you specify a separate botnet-nick, here.
 set nick "Lamestbot"
-# the nick of the bot, that which it uses on IRC, and on the botnet
-# unless you specify a separate botnet-nick
 
+# Set the alternative nick which the bot uses on IRC if the nick specified by 'set nick' 
+# is unavailable. All '?' characters will be replaced by random numbers.
 set altnick "Llamab?t"
-# an alternative nick to use if the nick specified by 'set nick' is
-# unavailable. All '?' characters will be replaced by a random number.
 
+# Set here what should be displayed in the real-name field for the bot on IRC.
 set realname "/msg LamestBot hello"
-# what to display in the real-name field for the bot
 
+# This is the bot's server list. The bot will start at the first server listed, 
+# and cycle through them whenever it gets disconnected. You need to change these 
+# servers to YOUR network's servers.
 set servers {
   you.need.to.change.this:6667
 }
-# the server list -- the bot will start at the first server listed, and cycle
-# through them whenever it's disconnected
-# (please note: you need to change these servers to YOUR network's servers)
 
+# This adds the channel #lamest to the bot's channel list. You should change
+# this to a channel you would like the bot to join.
 channel add #lamest {
   chanmode "+nt-likm"
   idle-kick 0
@@ -65,41 +69,69 @@
 channel set #lamest -secret -shared +cycle
 channel set #lamest -inactive -seen +nodesynch
 
-set net-type 0
-# set here your network
 # [0/1/2/3/4/5] What is your network?
-# 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
-# 4 = Efnet +e/+I hybrid, 5 = Others
-
-
-# various stuff...
+# 0 = EFnet (non +e/+I hybrid)
+# 1 = IRCnet
+# 2 = Undernet
+# 3 = DALnet
+# 4 = EFnet +e/+I hybrid
+# 5 = Others
+set net-type 0
 
+# Set here the port where the eggdrop should listen for telnet connections.
 listen 3333 all
-# set here the port where eggdrop should listen von telnet connections
 
+# Un-comment the next line and set the list of owners of the bot.
+# You NEED to change this setting.
 #set owner "MrLame, MrsLame"
-# set here the list of owners of the bot
 
+##### Files & Directories:
 
-# files & directories
-
+# The following two lines define where to store the bots user and
+# channel files.
 set userfile "LamestBot.user"
 set chanfile "LamestBot.chan"
+
+# This defines where the bot should store temp files.
 set temp-path "/tmp"
+
+# This creates a logfile named eggdrop.log containing private msgs/ctcps,
+# commands, errors, and misc. info from any channel.
 logfile msbxco * "logs/eggdrop.log"
-logfile jpk #lamest "logs/lamest.log"
 
+# This creates a logfile of joins, parts, netsplits, kicks, bans, 
+# mode changes, and public chat on the channel #lamest. 
+logfile jpk #lamest "logs/lamest.log"
 
-# default console flags
+# Set the default console flags here.
 set console "mkcobxs"
 
+##### Uptime module:
+
+# This module reports uptime statistics to http://uptime.eggheads.org.
+# Go look and see what your uptime is! It takes about 9 hours to show up,
+# so if your bot isn't listed, try again later.
+# 
+# Information sent to the server includes the bot's uptime, botnet-nick,
+# server, version, and IP address. This information is stored in a temporary 
+# logfile for debugging purposes only. The only publicly available information
+# will be the bot's botnet-nick, version and uptime. If you do not wish for this
+# information to be sent, comment out the following line.
+loadmodule uptime
 
-# you have to remove this line to make your bot work
+# You have to remove this line to make your bot start.
 die "you didn't edit your config file! that's a NO NO"
 
 ##### SCRIPTS #####
 
-# these are some commonly loaded (and needed) scripts.
+# This is a good place to load scripts to use with your bot.
+
+# This line loads script.tcl from the scripts directory inside your eggdrop's
+# directory. All scripts should be put there, although you can place them where
+# you like as long as you can supply a fully qualified path to them.
+#
+# source scripts/script.tcl
+
 source scripts/alltools.tcl
 source scripts/action.fix.tcl
 source scripts/compat.tcl
Index: eggdrop1.6/src/patch.h
diff -u eggdrop1.6/src/patch.h:1.622 eggdrop1.6/src/patch.h:1.623
--- eggdrop1.6/src/patch.h:1.622	Thu Dec 13 23:38:12 2001
+++ eggdrop1.6/src/patch.h	Thu Dec 13 23:43:11 2001
@@ -10,7 +10,7 @@
  * statement, leave the rest of the file alone, this allows better
  * overlapping patches.
  *
- * $Id: patch.h,v 1.622 2001/12/14 05:38:12 guppy Exp $
+ * $Id: patch.h,v 1.623 2001/12/14 05:43:11 guppy Exp $
  */
 /*
  * Copyright (C) 1997 Robey Pointer
@@ -41,12 +41,12 @@
  *
  *
  */
-patch("1008308251");		/* current unixtime */
+patch("1008308525");		/* current unixtime */
 /*
  *
  *
  */
-patch("modulesupdate");
+patch("doccleanups");
 /*
  *
  *
----------------------- End of diff -----------------------



More information about the Changes mailing list