[cvslog] (2003-11-27 01:07:57 UTC) Module eggdrop1.6: Change committed

cvslog cvs at tsss.org
Wed Nov 26 19:07:57 CST 2003


CVSROOT    : /usr/local/cvsroot
Module     : eggdrop1.6
Commit time: 2003-11-27 01:07:57 UTC
Commited by: Will Buckner <wcc at techmonkeys.org>

Modified files:
     doc/BOTNET doc/BUG-REPORT doc/tricks doc/html/botnet.html
     help/cmds1.help help/cmds2.help language/core.danish.lang
     language/core.english.lang language/core.french.lang src/patch.h
     src/mod/channels.mod/help/channels.help
     src/mod/channels.mod/help/set/channels.help
     src/mod/share.mod/help/share.help
     src/mod/transfer.mod/help/set/transfer.help

Log message:

* More doc and help file cleanups. More coming.

---------------------- diff included ----------------------
Index: eggdrop1.6/doc/BOTNET
diff -u eggdrop1.6/doc/BOTNET:1.15 eggdrop1.6/doc/BOTNET:1.16
--- eggdrop1.6/doc/BOTNET:1.15	Mon Dec 23 20:30:02 2002
+++ eggdrop1.6/doc/BOTNET	Wed Nov 26 19:07:46 2003
@@ -133,7 +133,7 @@
     linking two bots. Before you start, you need to know the address and
     port of each bot you wish to link.
 
-    Here is an example senario:
+    Here is an example scenario:
 
       BotA is on lame.org listening on port 3333, and BotB is on irc.org
       listening on port 4444. First, you have to add each Bot to the other's
Index: eggdrop1.6/doc/BUG-REPORT
diff -u eggdrop1.6/doc/BUG-REPORT:1.16 eggdrop1.6/doc/BUG-REPORT:1.17
--- eggdrop1.6/doc/BUG-REPORT:1.16	Tue Mar  4 22:32:24 2003
+++ eggdrop1.6/doc/BUG-REPORT	Wed Nov 26 19:07:46 2003
@@ -20,16 +20,18 @@
 =====================================================================
 1) INFORMATION ABOUT YOUR EGGDROP
 
-1.1) version:
+1.1) Eggdrop version:
      1.6.__
 
-1.2) make type:
+1.2) Make type:
      ( ) dynamic
      ( ) static
      ( ) debug
      ( ) sdebug
 
-1.3) list of patches and/or modules you use:
+1.3) List of any options passed to ./configure:
+
+1.4) List of patches and/or modules you use:
 
 =====================================================================
 2) INFORMATION ABOUT TCL
Index: eggdrop1.6/doc/html/botnet.html
diff -u eggdrop1.6/doc/html/botnet.html:1.13 eggdrop1.6/doc/html/botnet.html:1.14
--- eggdrop1.6/doc/html/botnet.html:1.13	Mon Dec 23 20:30:02 2002
+++ eggdrop1.6/doc/html/botnet.html	Wed Nov 26 19:07:46 2003
@@ -1,5 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<!-- $Id: botnet.html,v 1.13 2002/12/24 02:30:02 wcc Exp $ -->
+<!-- $Id: botnet.html,v 1.14 2003/11/27 01:07:46 wcc Exp $ -->
 
 <html>
   <head>
@@ -227,7 +227,7 @@
 
     <p>With the common terms out of the way, we can start with the process of
     linking two bots. Before you start, you need to know the address and
-    port of each bot you wish to link. Here is an example senario:</p>
+    port of each bot you wish to link. Here is an example scenario:</p>
 
     <blockquote>
       <p>BotA is on lame.org listening on port 3333, and BotB is on irc.org
Index: eggdrop1.6/doc/tricks
diff -u eggdrop1.6/doc/tricks:1.12 eggdrop1.6/doc/tricks:1.13
--- eggdrop1.6/doc/tricks:1.12	Mon Dec 23 20:30:02 2002
+++ eggdrop1.6/doc/tricks	Wed Nov 26 19:07:46 2003
@@ -1,11 +1,5 @@
 Here are some little tricks that you may or may not know about.
 
--  You can "lock" a user's info line by putting an '@' as the first letter.
-   They won't be able to change it any more.
-
--  '.status all' will dump out virtually everything you have configured on
-   your bot.
-
 -  Tcl has a command 'info body <proc>' that will list the contents of a
    proc. 'info args <proc>' shows what you have defined as the parameters
    for the proc.
@@ -29,9 +23,6 @@
 
 -  You can unlink all bots and clear out the botnet info from memory by
    using '.unlink *'. It erases all channel assoc's and everything.
-
--  You can automatically make a ban sticky by adding a * as the first
-   character in the ban reason.
 
 -  You can add a user with a static hostmask when using .adduser by prefixing
    their nick with '!'.
Index: eggdrop1.6/help/cmds1.help
diff -u eggdrop1.6/help/cmds1.help:1.16 eggdrop1.6/help/cmds1.help:1.17
--- eggdrop1.6/help/cmds1.help:1.16	Sat Aug 16 16:26:57 2003
+++ eggdrop1.6/help/cmds1.help	Wed Nov 26 19:07:46 2003
@@ -6,16 +6,11 @@
    for bots and users they should be separated with a slash (/).
 
 See also: -bot
-%{help=+host}
-###  %b+host%b <hostmask>
-   Adds a hostmask to your user record. Hostmasks are used to identify your
-   handle on IRC.
- 
-%{+m|m}
-###  %b+host%b <handle> <hostmask>
-   Adds a hostmask to a user's user record. Usually, you will not need to use
-   this command, since a user can add hostmasks to his or her own record via
-   the %b/MSG IDENT%b command.
+%{help=+host}%{+t|m}
+###  %b+host%b [handle] <hostmask>
+   Adds a hostmask to a user's user record. Hostmasks are used to identify your
+   handle on IRC. If a handle is not specified, the hostmask will be added to
+   YOUR user record.
 
 See also: -host
 %{help=+ignore}%{+m}
@@ -33,15 +28,15 @@
 See also: -user, +host, -host
 %{help=-bot}%{+t}
 ###  %b-bot%b <bot>
-   This is exactly the same as %b'-user'%b (it removes a user record). It is
+   This is exactly the same as %b'.-user'%b (it removes a user record). It is
    included for convenience.
 
 See also: +bot, +user, -user
 %{help=-host}
 ###  %b-host%b <hostmask>
    Removes a host from your handle.
-
 %{+m|m}
+
 ###  %b-host%b <handle> <hostmask>
    Removes a hostmask from a user's user record.
 %{-}
@@ -78,6 +73,14 @@
    This marks you as no longer away on the party line.
 
 See also: away
+%{help=backup}%{+m|m}
+###  %bbackup%b
+   This makes the bot write a backup of its entire user list to the disk. If
+   the channels module is loaded, this will also write a backup of the channels
+   file. This is useful if you feel the need to backup the userfile and channel
+   settings.
+
+See also: reload, rehash, save
 %{help=banner}%{+t}
 ###  %bbanner%b <text>
    Displays a message to everyone currently using the bot's party line or file
@@ -95,7 +98,7 @@
    number of times that binding has been called. If not, go read the file
    %b'doc/tcl-commands.doc'%b for help on the Tcl bind command. Note that the
    builtin commands are now shown. You may also specify a type of binding to
-   show (i.e., %b'.binds msg'%b) or you can specify a wild card match (i.e.,
+   show (i.e. %b'.binds msg'%b) or you can specify a wild card match (i.e.,
    %b'.binds *seen*'%b) if you want to narrow the field a bit. The wild card
    matches will match against the TYPE, COMMAND and BINDING fields. You can
    view more binds by adding 'all' to the end of the command.
@@ -113,7 +116,7 @@
    "Fred1" +share and -hub, you would do '.botattr Fred1 +s-h.'
 
    Whether or not you change any flags, it will show you the bot's flags
-   afterwards. To get a list of the flags possible, see %b'help whois'%b.
+   afterwards. To get a list of the flags possible, see %b'.help whois'%b.
 
    %bNOTE:%b This command is NOT used to replace .chattr. It modifies bot flags,
          such as s, h, a, u, etc.
@@ -136,7 +139,7 @@
       Bots: cEvin, ruthie, Killa1
 
    There is no indication of which bots are directly connected to this current
-   bot. Use %b'who'%b%{+t} or %b'bottree'%b%{-} for that information.
+   bot. Use %b'.who'%b%{+t} or %b'.bottree'%b%{-} for that information.
 
 See also: bottree, vbottree, botinfo
 %{help=bottree}
@@ -163,9 +166,9 @@
    these, you can specify the channel by name instead of channel number if
    you wish.
 
-   %b'chat off'%b removes you from all channels, including the main party line.
+   %b'.chat off'%b removes you from all channels, including the main party line.
    You can still use bot commands and see the console, but you can't talk to
-   anyone except via %b'.note'%b. %b'chat on'%b returns you to the main party
+   anyone except via %b'.note'%b. %b'.chat on'%b returns you to the main party
    line (channel 0) if you were elsewhere.
 
    If you prefix the channel with a '*', you will join a local channel.
@@ -193,7 +196,7 @@
       .chattr Bill f|o #lamer
 
    Whether or not you change any flags, it will show you the user's attributes
-   afterwards. To get a list of all possible flags, see %b'help whois'%b.
+   afterwards. To get a list of all possible flags, see %b'.help whois'%b.
 
    %bNOTES:%b Only the owner may add or remove the 'n' (owner), 'm' (master) or
           't' (botnet master) flags. It is pointless to -n a permanent owner.
Index: eggdrop1.6/help/cmds2.help
diff -u eggdrop1.6/help/cmds2.help:1.16 eggdrop1.6/help/cmds2.help:1.17
--- eggdrop1.6/help/cmds2.help:1.16	Tue Jan 28 23:48:40 2003
+++ eggdrop1.6/help/cmds2.help	Wed Nov 26 19:07:46 2003
@@ -1,456 +1,469 @@
 %{help=fixcodes}
 ### %bfixcodes%b
-     use this in those situations where the bot gets mixed up about your
-     type of connect, eg: when you /ctcp chat the bot & it thinks you're
-     telnetting, and you're actually using dcc, it effectively switches
-     telnet on and off.
+     This is for use in situations where the bot gets mixed up about the type
+     of connection you have with it. For example, you /CTCP CHAT the bot and
+     it thinks you are connecting via telnet, and you see text displayed as
+     "Local time is now 17:17" for example instead of "Local time is
+     now 17:17". Use this to turn telnet codes on or off/change the display
+     mode.
 %{help=ignores}%{+m}
 ###  %bignores%b [wildcard]
-   lists the hostmasks that the bot is currently discarding msgs,
-   etc from.  the ignores are numbered, so they can be easily
-   removed with %b'-ignore'%b by number.  a permanent ignore looks
-   like this:
-      [  1] *!onaji@* (perm)
-            Xerxes: spamming me
-            Started 18:38
-   this kind of ignore can only be stopped by using %b'-ignore'%b.
-   Xerxes is the one who added it, and his comment is "spamming
-   me".  he added it at about 18:38 today.  a temporary ignore
-   looks like this:
-      [  2] *!*@shellx.best.com (expires at 19:59)
-            MyBot: msg/notice flood
-            Started 18:59
-   that means the ignore was made automatically by the bot at
-   18:59, because someone flooded it.  it can be removed with
-   %b'-ignore'%b, or it will expire an hour after it started (this
-   is set in %b'ignore-time'%b).
+   Shows a list of hostmasks from which the bot is currently ignoring msgs,
+   notices, etc. There are two types of ignores: permanent and temporary.
+   Permanent ignores never automatically expire. You must use %b'.-ignore'%b
+   to remove them.
+
+   Here is a sample permanent ignore:
+      [  1] *!*@217.156.44.184 (perm)
+            Wcc: go away
+            Started 523 days ago
+
+   The number (1) can be used to reference the ignore if you wish to remove it
+   (see %b'.help -ignore'%b). Next is the actual hostmask being ignored. The
+   "(perm)" means that the ignore is "permanent": that is, it doesn't
+   automatically expire. The second line of the ignore entry is the comment
+   ("go away"), and who set the ban (Wcc). The last line shows when the ignore
+   was added.
+
+   Here is a sample temporary ignore:
+      [ 10] blah!blah at blah.cc (expires in 1 day)
+            Wcc: requested
+            Started 18:02
+
+   Here, you see the "perm" in the parentheses next to the hostmask is instead
+   an expire time. This means that the ignore will expire automatically in one
+   day.
 
-   if you use %b'ignores <wildcard>'%b it will list all the ignores
+   If you use %b'.ignores <wildcard>'%b, it will list all the ignores
    that match against your wildcard.
 
-see also: +ignore, -ignore, set ignore-time
+See also: +ignore, -ignore
 %{help=link}%{+t}
-###  %blink%b [some-bot] <new-bot>
-   tries to link in a new bot.  if you use the form
-      .link newbot
-   then your bot must have a record for the new bot (see %b'.+bot'%b).
-   you can either set a password on each end or they will negotiate
-   one the first time they link.  if you use the form
-      .link somebot newbot
-   then the request will be sent to "somebot" for it to link to
-   "newbot".
+###  %blink%b [via-bot] <bot-to-link>
+   Attempts to link a bot to the botnet. The local bot must have a bot record
+   for the remote bot in order for it to be linked (see %b'.help +bot'%b). If
+   you do not set a password on both bots, one will be automatically negotiated
+   the first time they link. If you specify a "via-bot", a request will be sent
+   to that bot to link to "bot-to-link".
+
+See also: unlink, +bot, -bot
 %{help=loadmod}%{+n}
 ###  %bloadmod%b <module>
-   Loads a module.
+   Loads the specified module.
+
+See also: modules, module, unloadmod
 %{help=match}%{+o|o}
 ###  %bmatch%b <attr> [channel] [[start] limit]
-   shows you user records with the attributes requested:
-   <attr> is of the form:  <+/-><global>[&/|<channel>[&/|<bot>]]
-    specifying & as the separator, will cause AND style matching,
-    | will cause OR style matching, channel flags are match vs
-    the specified channel (or your console channel), and bot
-    is match vs the separate bot flags.
-    some examples:
-       .match +o     will match any GLOBAL +o's
-       .match -o&+o  will match anyone without a global +o AND
-                          with a channel +o on your console channel
-       .match +f|+f  will match anyone with a global +f or a
-                          channel +f on your console channel
-       .match |f #fred will match anyone with +f on channel #fred
+   This displays all user records with the attributes requested.
+
+   "attr" is of the form:  <+/-><global>[&/|<channel>[&/|<bot>]]
+
+   Specifying "&" as the separator will cause AND style matching.
+
+   For example:
+      .match p&o
+
+   This will match all users with both the "p" global flag and the "o" channel
+   flag on your current console channel.
+
+   Specifying "|" as the separator will cause OR style matching.
+
+   For example:
+     .match p|o
+
+   This will match all users with either the "p" global flag or the "o" channel
+   flag on your current console channel. If you specify a channel, it will be
+   used instead of the current console channel.
+
+   For example:
+     .match p|o #eggdrop
+
+   This will match all users with either the "p" global flag or the "o" channel
+   flag on the channel #eggdrop. You can also match bot flags.
+
+   For example:
+     .match o|o|h
+
+   This will match all bots with either the "o" global flag, the "o" channel
+   flag on the current console channel, or the "h" botflag. You can also limit
+   the number of total results returned by specifying a limit at the end of the
+   command. A starting point can also be specified.
+
+   For example:
+     .match p&o #eggdrop 16 25
+
+   This would show results 16 through 25 matching any users with the "p" global
+   flag or the "o" channel flag on #eggdrop.
+
 ###  %bmatch%b <wildcard-string> [[start] limit]
-   shows you user records where the nickname or any of the hostmasks
-   match the wildcard string shown.
+   This displays all user records where the user's handle or any of the user's
+   hostmasks match the specified wildcard string. You can also limit the number
+   of total results returned by specifying a limit at the end of the command. A
+   starting point can also be specified.
 
-   the default limit is 20, meaning that if more than 20 user records
-   match your requirements, only the first 20 will be shown.  you can
-   change this limit by specifying one on the command line, though.
-   if you include a limit, you may also include a starting place (the
-   default is 1).  for example, to list the first 15 users who have
-   hostmasks from clemson.edu:
-      .match *clemson.edu 15
-   to get the next 10 (if there are more than 15), you ask to list
-   numbers 16 through 25:
-      .match *clemson.edu 16 25
+   For example:
+     .match *.edu 16 25
+
+   This would show results 16 through 25 matching any users with a hostmask
+   that ends with ".edu".
 %{help=me}
 ###  %bme%b <text>
-   performs an action on the party line.
+   Performs an action on the party line. This appears as "* Wcc is leaving",
+   etc.
 %{help=module}%{+n}
 ###  %bmodule%b [modulename]
-   Reports the names of currently loaded modules, including
-   dependencies & status report, you can get info only on a
-   specific module by specifying it.
+   Reports the names of currently loaded modules, including dependencies and a
+   status report. If you specify a module name, only information on that module
+   will be displayed.
+
+See also: modules, loadmod, unloadmod
 %{help=modules}%{+n}
 ###  %bmodules%b [botname]
-   requests a listing of the modules loaded on the remote bot or your
-   bot if no botname is specified.
+   Displays a list of currently loaded modules. If a botname is specified, the
+   modules currently loaded on that bot will be displayed instead.
+
+See also: module, loadmod, unloadmod
 %{help=motd}
 ###  %bmotd%b [botname]
-   will redisplay the party-line message of the day, which was
-   shown when you first joined. If the name of a remote bot is
-   given as parameter, the respective motd will be displayed.
+   This redisplays the partyline Message Of The Day, which was shown when you
+   first joined the partyline. If the name of a remote bot is specified, that
+   bot's motd will be displayed instead.
 %{help=newpass}
 ###  %bnewpass%b <password>
-   changes your password on the bot, just like the /msg command
-   'pass', except you don't need to type your old password.
+   Changes your password on the bot. This is similar to the '/msg <bot> pass'
+   command, except you don't need to specify your old password.
+%{+t}
+
+See also: chpass
 %{help=handle}
 ###  %bhandle%b <new-handle>
-   changes your handle on the bot. That's the handle(nickname) that the
-   bot will know you as forever and ever, and what you have to use when
-   telnetting in or IDENT'ing yourself, so remember it.
-%{help=nick}
-###  %bnick%b
-   Please note, that this command has been superceded by
-   'handle'. If you still want to use 'nick', load compat.tcl
-   into your bot.
+   Changes your handle on the bot. This is the handle (nickname) that the
+   bot will know you as from this point forward. It is used to log into the
+   bot, and for the /msg IDENT command, etc.
+
+See also: newpass%{+t}, chhand, chpass
 %{help=note}
 ###  %bnote%b <nickname[@bot]> <message>
-   sends a private note to a user on the party line.  if that user
-   is currently on the party line, and not marked as away, she will
-   receive the message immediately.  otherwise it may be stored
-   and displayed the next time that user joins the party line.  if
-   you join the channel, and have notes stored for you on the bot,
-   it will tell you.  to send a note to someone on a different bot,
-   use "nick at bot" for the nickname.
+   Sends a private note to a user on the partyline. If that user is currently
+   logged in and not marked as away, the message will be received immediately.
+   Otherwise, it will be stored and displayed the next time that user joins the
+   partyline. To send a note to someone on a different bot, add "nick at bot" to
+   the nickname.
 
-see also: whom, notes
+See also: whom, notes
 %{help=page}
-### %bpage%b <# or off>
-     allows you to slow down the number of lines the bot sends to you
-     at once while you're in chat mode.  with this on, any commands
-     that send greater than the specified number of lines will stop
-     when the number is reached, and wait for you to type another
-     command (or press enter) to continue. if you have to many
-     lines waiting to be seen you may be booted off the bot.
+### %bpage%b <number/off>
+   This allows you to slow down the number of lines the bot sends you at once
+   via the partyline. When enabled, any commands that send greater than the
+   specified number of lines will stop when that number is reached and wait for
+   you to type another command (or press enter) to continue. If you have too
+   many pending lines, you may be booted off the bot.
 %{help=quit}
 ###  %bquit%b [comment]
-   removes you from the party line and disconnects your dcc chat
-   session with the bot.  if you specify a comment, it will be
-   displayed to other users as you leave.
+   This disconnects you from the partyline. If you specify a comment, it will
+   be displayed to other partyline users as you leave.
 %{help=rehash}%{+m}
 ###  %brehash%b
-   reloads the config file for the bot, which resets all the %b'set'%b
-   variables and reloads any Tcl scripts your config loads.  it
-   also saves and reloads the user file from disk, just to give
-   your disk a little extra wear.
+   Reloads the bot's config file, which resets all changes made via the
+   %b'.set'%b command and reloads any Tcl scripts your config loads. It also
+   saves and reloads the user file from disk, just to give it some exercise.
 
-see also: save, reload, restart
+See also: save, reload, restart%{+n}, rehelp, relang
 %{help=rehelp}%{+n}
 ###  %brehelp%b
-   This command gets the bot to recheck all it's help files for new
-   commands that have been added.
+   This command forces the bot to recheck all of its help files for changes.
+
+See also: save, reload, restart, relang
 %{help=relay}%{+o}
 ###  %brelay%b <botname>
-   will relay you via telnet to another bot that your bot knows of,
-   whether or not they are currently connected.  your dcc-chat/telnet
-   connection to this bot will be relayed to the other bot until the
-   other bot drops your relay, or until you send "*bye*" on a line by
-   itself.
+   Relays you via telnet to another bot, whether or not it is currently linked.
+   The local bot must, however, have a bot record for the bot you wish to
+   relay to. Typing .quit or "*bye*" on a line by itself will end the relay.
 
-see also: bots
+See also: bots%{+t}, +bot, -bot
 %{help=reload}%{+m|m}
 ###  %breload%b
-   reloads the user file of the bot, discarding any changes made
-   since the last %b'.save'%b or hourly user file save.  sharebots
-   should probably not ever do this.
+   Reloads the bot's user file, discarding any changes made since the last
+   %b'.save'%b command or hourly user file save. Sharebots should probably
+   never do this.
 
-see also: rehash, save
+See also: save%{+m}, rehash
 %{help=traffic}%{+m|m}
 ###  %btraffic%b
-   shows total and daily net traffic stats since last %b'.restart'%b.
-   stats groups are IRC, Botnet, Partyline, Transfer.mod and Misc.
+   Shows total and daily net traffic stats since the last %b'.restart'%b.
+   Stats groups are IRC, Botnet, Partyline, Transfer.mod and Misc.
+%{+m}
 
-see also: restart
+See also: restart
 %{help=whoami}
 ###  %bwhoami%b
-   Shows your handle and to what bot you are connected.
+   Shows your current handle and to what bot you are connected.
+
+See also: whom
 %{help=restart}%{+m}
 ###  %brestart%b
-   restarts the Tcl interpreter, wipes all timers and utimers, and
-   reloads the config file for the bot, which resets all the %b'set'%b
-   variables and reloads any Tcl scripts your config loads.  it
-   also saves and reloads the user file from disk, just to give
-   your disk a little extra wear. it's also the most risky command
-   to run, because it's never ever really worked properly.
+   Restarts the Tcl interpreter, wipes all timers, reloads all modules, and
+   reloads the config file for the bot (which resets any changes made via the
+   %b'.set'%b command and reloads any Tcl scripts your config loads). As with
+   the %b'.rehash'%b command, it also saves and reloads the user file from disk.
 
-see also: rehash, reload, save
+See also: rehash, reload, save
 %{help=save}%{+m|m}
 ###  %bsave%b
-   makes the bot write its entire user list to the disk.  this is
-   useful if you think the bot is about to crash or something, since
-   the user file is only written to disk about once an hour.
-
-see also: reload, rehash
-%{help=backup}%{+m|m}
-###  %bbackup%b
-   makes the bot write a backup of its entire user list to the disk.
-   if the channels module is loaded, this also write a backup of the
-   channels file.
-   this is useful if you feel the need to backup the user list and
-   the channels settings.
+   This makes the bot write its entire userfile to disk. This is useful if you
+   think the bot is about to crash or something, since the user file is only
+   written to disk about once an hour.
 
-see also: reload, rehash
+See also: reload, rehash, backup
 %{help=simul}%{+n}
-###  %bsimul%b <nickname> <text>
-   if the user is on the party line, the bot will simulate them typing
-   the text you specify.  example:
+###  %bsimul%b <handle> <text>
+   This allows you to simulate the specified handle typing the given text.
+
+   For example:
       .simul dweeb .quit
-   makes it just as if "dweeb" typed ".quit". this command will not work
-   unless eggdrop has simul enabled in the config file. Please use this
+
+   This would appear just as if "dweeb" typed ".quit". This command will not
+   work unless eggdrop has simul enabled in the config file. Please use this
    command ethically.
 %{help=strip}
 ###  %bstrip%b [modes]
-   enables you to remove embedded 'attribute' codes from within a
-   section of text. Valid options are:
-      b  remove all boldface codes
-      c  remove all color codes
-      r  remove all reverse video codes
-      u  remove all underline codes
-      a  remove all ansi codes
-      g  remove all ctrl-g (bell) codes
-   the mode can also be a modifier like '+c' or '-bu' or '+ru-c'.  if
+   Allows you to remove embedded 'attribute' codes your partyline output. Valid
+   options are:
+      %bb%b  remove all boldface codes
+      %bc%b  remove all color codes
+      %br%b  remove all reverse video codes
+      %bu%b  remove all underline codes
+      %ba%b  remove all ANSI codes
+      %bg%b  remove all ctrl-g (bell) codes
+
+   The mode can also be a modifier like '+c' or '-bu' or '+ru-c'. If
    you omit modes, it will show your current setting.
+
+See also: fixcodes
 %{+m}
+
 ###  %bstrip%b <user> [modes]
-   is used to set the strip level of another user, a master can't
-   set their own strip flags without starting the modes with a +/-
+   Set the strip level of another user. A master can't set their own strip
+   flags without prefixing the modes with a '+' or '-'.
+
+
 %{help=su}
 ###  %bsu%b <user>
-   changes your username to that of another. If you
-   are an owner this does not require a password
-   otherwise, you must enter the password of <user>.
-
-   %b.quit%b returns you to your original user.
+   Lets you assume the identity of another user. If you are a global owner,
+   this does not require a password. Otherwise, you will be asked for the
+   user's password. %b.quit%b returns you to your original handle.
 %{help=trace}
 ###  %btrace%b <bot>
-   sends out a trace signal to another bot.  if that trace signal
-   returns (and it should!) you will get an output something like
-   this:
+   Sends out a trace signal to another bot. If/when the trace signal returns,
+   (and it should!) you will get an output that looks something like this:
       Trace result -> Valis:Stonewall:NoBoty:SomeBoty
-   it's a list of the bots between you and the destination bot.
-   it should also return the time in seconds it took for the
-   trace to occur.
 
-see also: bots, bottree
+   This is a list of the bots connected between you and the destination bot.
+   It should also return the time in seconds taken for the trace to occur.
+
+See also: bots, bottree, vbottree
 %{help=unlink}%{+t}
-###  %bunlink%b <bot>
-   disconnects the named bot from the botnet, assuming it was
-   connected in the first place. some bots (sharebots in
-   particular) might not allow you to unlink them.
-###  %bunlink%b *
-   disconnects from all bots
+###  %bunlink%b <bot/*>
+   This disconnects the specified bot from the botnet (assuming it was linked
+   in the first place). Some bots (sharebots in particular) might not allow you
+   to unlink them. If "*" is specified as the parameter, all bots will be
+   unlinked.
 
-see also: link, bots, bottree
+See also: link, +bot, -bot, bots, bottree
 %{help=unloadmod}%{+n}
 ###  %bunloadmod%b <module>
-   Unloads a module.
+   Unloads the specified module.
+
+See also: modules, module, loadmod
 %{help=whom}
-###  %bwhom%b [channel]
-   will display a table of the users currently on the joint party
-   line (formed when you have two or more bots linked together).
-   it will show each user's nickname, preceded by a "*" if they
-   are the owner of their bot, "+" if they are a master, "%%" if
-   they are a botnet master or "@" if they are an op.  in other
-   columns it will show which bot the user is on, and his or her host.
-
-   if the user is away, the away message will be shown.  likewise,
-   if they are idle, the idle time will be displayed.
-
-   if you are on a different channel than the party line (channel
-   0), then this will show the people on every bot who are on
-   your current channel.  you can also optionally give the "channel"
-   option to list who is on a particular channel.
+###  %bwhom%b [channel/*]
+   Displays a list of users on the current partyline channel.
+
+   For example:
+      [23:12] #Wcc# whom
+       Nick        Bot        Host
+      ----------   ---------  --------------------
+      *Wcc         Anakha     telnet at xxx.atlaga.adelphia.net [idle 8m]
+      *BitchSmack  Anakha     telnet at xxx.atlaga.adelphia.net
+      Total users: 2
+
+   Each user's nickname will be listed in the first column, preceded by a "*"
+   if they are a bot owner, "+" if they are a master, "%%" if they are a botnet
+   master, or "@" if they are an op. In the next column, the bot the user is
+   connected to will be displayed. In the third column, the host is shown. If
+   the user is away, the away message will be shown. Likewise, if they are
+   idle, their idle time will be displayed.
+
+   To see what users are on a different channel, you may specify a channel
+   number/name. If you specify "*" as the channel, all users on all botnet
+   channels will be shown.
 
-see also: who, bots, chat
+See also: who, bots, chat
 %{help=who}
 ###  %bwho%b [bot]
-   lists people on this bot, or bots connected to this bot.  the
-   first section is people on your current channel (the party
-   line, if you haven't changed channels) who are on the bot.
-   a '*' next to the nickname means that user is an owner; '+'
-   means they're a master; '@' means they're an op, '%%' means
-   they are a botnet master. the user's nickname, hostname, and
-   possibly an idle time and/or away message will be displayed:
-%{+n}
-   Owners will also see the users dcc idx
-%{-}
-      *Robey      telnet: nowhere.com
-
-   the next section is bots directly linked to this one:
-      -> MagField   (14 Oct 01:16) eggdrop v1.0j
-   (btw, if you're still using 1.0j, you need to upgrade ;)
-   the arrow indicates who initiated the connection -- the right
-   arrow means this bot connected to MagField.  a left arrow
-   means they connected to us.  a '+' next to the arrow indicates
-   that the bot is sharing userfiles with us.  the connection
-   time (14 Oct 01:16) and bot version are also shown.
-   Nowadays it may also show the network the bot resides on.
-%{+n}
-   Owners will also see the bots dcc idx
-%{-}
-
-   the final section is a list of users on this bot who are not
-   on your channel.  (this section may be omitted if everyone is
-   on the same channel as you.)
+   Displays a list of users on the local bot.
 
-   if you specify a bot's name, as in %b'.who valis'%b, the who request
-   will be sent to that bot, as long as that bot is on the botnet.
+   For example:
+      [23:21] #Wcc# who
+      Party line members:  (* = owner, + = master, @ = op)
+      *Wcc       telnet at xxx.atlaga.adelphia.net (idle 17m)
+      *Wcc       telnet at xxx.atlaga.adelphia.net
+      Bots connected:
+      -> wortel (05 Dec 16:32) eggdrop v1.6.15 <efnet>
+
+   The first section is people on your current channel (the party line, if you
+   haven't changed channels) who are on the bot. A '*' will precede the handle
+   if they are a bot owner, "+" if they are a master, "%%" if they are a botnet
+   master, or "@" if they are an op. The user's nickname, hostname, and
+   possibly an idle time and/or away message will be displayed.%{+n} Owners
+   will also see the user's dcc idx.%{-}
+
+   The next section is bots directly linked to the current bot. The arrow
+   indicates which bot initiated the connection. The right arrow means this bot
+   connected to wortel. A left arrow means the remote bot linked to this bot. A
+   '+' next to the arrow indicates that the bot is sharing userfiles with us.
+   The connection time (05 Dec 16:32) and bot version are also shown, as well
+   as what is specified under "network" in the config file.%{+n} Owners will
+   also see the bot's dcc idx.%{-}
+
+   The final section (not shown in example above) is a list of users on the
+   local bot who are not on your channel. This will be omitted if there are no
+   users on other channels. If you specify the name of a remote bot, for
+   example %b'.who valis'%b, the who request will be sent to that bot instead.
+   The remote bot must be linked to the botnet.
 %{+m}
 
-   masters may also see "(con)" after a user's entry, this shows that
-   user's console modes (see the %b'.console'%b help page).
+   Masters may also see "(con <flags>)" after a user's entry, which shows the
+   user's console flags/modes (see %b'.help console'%b).
 
-   in the final section (users that aren't on this channel), masters
-   will see the actual channel other users are on.  also, people in
-   the file system will be listed (as being in channel "files") --
-   a '+' next to the nickname here means the user has access to return
-   to the party line.
+   In the final section (users that aren't on the current channel), masters
+   will see the actual channels other users are on. Also, people in the
+   filesystem will be listed (as being in channel "files") if the filesys
+   module is loaded. A '+' next to the nickname here means the user has
+   access to return to the party line.
 %{-}
 
-see also: whom
+See also: whom
 %{help=whois}%{+o|o}
 ###  whois <nickname>
-   will show you the bot information about a user record.  there are
-   five headings:
-      HANDLE       the handle (nickname) of the user
-      PASS         "yes" if she has a password set, "no" if not
-      NOTES        number of notes stored waiting for the user
-      FLAGS        the list of flags for this user (see below)
-      LAST         the time or date that the user was last on the
-                      channel
-
-   the valid flags under FLAGS are:
-      a   global auto-op (user is opped automatically upon joining a channel)
-      b   bot (user is a bot)
-      c   common (see 'help common')
-      d   global deop (user cannot gain ops on any of the bot's channels)
-      e   global nethack-exempt (user is exempted from stopnethack protection)
-      f   global friend (user is not punished for flooding, etc)
-      g   global auto-voice (user is voiced automatically upon joining a channel)
-      h   highlight (use bold text in help/text files)
-      j   janitor (user is a file-area master)
-      k   global auto-kick (user is kicked and banned automatically)
-      l   global halfop (user has halfop access to all of the bot's channels)
-      m   global master (user has access to almost every feature of the bot)
-      n   global owner (user has absolute control)
-      o   global op (user has op access to all of the bot's channels)
-      p   party-line (user has access to the partyline)
-      q   global quiet (user does not get voice on +autovoice channels.)
-      r   global dehalfop (user cannot gain halfops on any of the bot's channels)
-      t   botnet master (user has access to all features dealing with the botnet.)
-      u   unshared (user record is not sent to other bots.)
-      v   global voice (user get +v automatically on +autovoice channels)
-      w   global wasop-test (needs wasop test for +stopnethack procedure)
-      x   xfer (user has file-area access)
-      y   global auto-halfop (user is halfopped automatically upon joining a channel)
-      z   global washalfop-test (needs washalfop test for +stopnethack procedure)
-
-      (plus 26 user-defined flags, A-Z)
-
-   each channel that the user has joined will have a specific record
-   for it, with the channel-specific flags and possibly an info
-   line.  the channel-specific flags are:
-
-      a   auto-op (user is opped automatically upon joining the channel)
-      d   deop (user cannot gain ops on the channel)
-      e   nethack-exempt (user is exempted from stopnethack protection)
-      f   friend (user is not punished for flooding, etc)
-      g   auto-voice (user is voiced automatically upon joining the channel)
-      k   auto-kick (user is kicked and banned automatically)
-      l   halfop (user has halfop access to the channel)
-      m   master (user is a channel master)
-      n   owner (user is a channel owner)
-      o   op (user has op access to the channel)
-      q   quiet (user does not get voice on the channel.)
-      r   dehalfop (user cannot gain halfops on the channel)
-      v   voice (user get +v automatically if the channel is +autovoice)
-      w   wasop-test (needs wasop test for +stopnethack procedure)
-      y   auto-halfop (user is halfopped automatically upon joining the channel)
-      z   washalfop-test (needs washalfop test for +stopnethack procedure)
-
-      (plus 26 user-defined flags, A-Z)
-
-   hostmasks for the user are displayed on the following lines.
-   if the user entry is for a bot, there will be a line below which
-   says "ADDRESS:" and gives the bot's telnet address.  some user
-   entries may have "EMAIL:" and "INFO:" entries too.
-   There may be additional information displayed depending on the
-   modules loaded.
-
-   for bots, there are additional flags seen under the BOTATTR:
-   entry, these include:
-      s   share (bot is sharing user records, aggressively)
-      p   share (bot is sharing user records, passively)
-      g   global share (share all channels)
-      h   hub (bot is auto-linked at highest priority)
-      a   alternate (bot is auto-linked if no hub bots can be linked)
-      l   leaf (bot is not allowed to link in other bots)
-      r   reject (bot will not be allowed on the net)
-      i   isolate (isolate the party line across a botlink)
-      (plus 10 user-defined flags, 0-9)
-   bots may also have +s (share) settings for individual channels
+   Shows you stored information about a user record. Five headings are
+   displayed:
+      %bHANDLE%b - the handle (nickname) of the user
+      %bPASS%b   - "yes" if she has a password set; "no" otherwise
+      %bNOTES%b  - number of stored notes waiting for the user
+      %bFLAGS%b  - the list of flags for this user (see below)
+      %bLAST%b   - the time or date that the user was last on the channel
+
+   Valid global flags:
+      %ba%b - autoop (user is opped automatically upon joining any channel)
+      %bb%b - bot (user is a bot)
+      %bc%b - common (see %b'.help common'%b)
+      %bd%b - deop (user cannot gain ops in any channel)
+      %be%b - nethack-exempt (user is exempted from stopnethack protection)
+      %bf%b - friend (user is not punished for flooding, etc on any channel)
+      %bg%b - autovoice (user is voiced automatically upon joining any channel)
+      %bh%b - highlight (use bold text in help/text files)
+      %bj%b - janitor (user is a file-area master)
+      %bk%b - autokick (user is kicked and banned automatically)
+      %bl%b - halfop (user has halfop access to all of the bot's channels)
+      %bm%b - master (user has access to almost every feature of the bot)
+      %bn%b - owner (user has absolute control over the bot)
+      %bo%b - op (user has op access to all of the bot's channels)
+      %bp%b - party-line (user has access to the partyline)
+      %bq%b - quiet (user cannot gain voice on any channel)
+      %br%b - dehalfop (user cannot gain halfops on any channel)
+      %bt%b - botnet master (user has access to features related to the botnet)
+      %bu%b - unshared (user's user record is not sent to other bots)
+      %bv%b - voice (user gets +v automatically on +autovoice channels)
+      %bw%b - wasop-test (needs wasop test for +stopnethack procedure)
+      %bx%b - xfer (user has filesystem access)
+      %by%b - autohalfop (user is auto-halfopped upon joining any channel)
+      %bz%b - washalfop-test (needs washalfop test for +stopnethack procedure)
+
+      There are also 26 user-defined global flags (A-Z).
+
+   Users can also have flags specific to a channel:
+
+      %ba%b - autoop (user is opped automatically upon joining the channel)
+      %bd%b - deop (user cannot gain ops on the channel)
+      %be%b - nethack-exempt (user is exempted from stopnethack protection)
+      %bf%b - friend (user is not punished for flooding, etc)
+      %bg%b - autovoice (user is voiced automatically upon joining the channel)
+      %bk%b - autokick (user is kicked and banned automatically)
+      %bl%b - halfop (user has halfop access to the channel)
+      %bm%b - master (user is a channel master)
+      %bn%b - owner (user is a channel owner)
+      %bo%b - op (user has op access to the channel)
+      %bq%b - quiet (user cannot gain voice on the channel)
+      %br%b - dehalfop (user cannot gain halfops on the channel)
+      %bv%b - voice (user gets +v automatically if the channel is +autovoice)
+      %bw%b - wasop-test (needs wasop test for +stopnethack procedure)
+      %by%b - autohalfop (user is auto-halfopped upon joining the channel)
+      %bz%b - washalfop-test (needs washalfop test for +stopnethack procedure)
+
+      There are also 26 user-defined channel flags (A-Z).
+
+   Hostmasks for the user are displayed on the following lines. If the user is
+   a bot, there will be a line below which says "ADDRESS:" and gives the bot's
+   telnet address. Some user entries may have "EMAIL:" and "INFO:" entries too.
+   There may be additional information displayed depending on the modules
+   loaded, such as filesys and console.
+
+   For bots, there are additional flags seen under the "BOTATTR:" section.
+   Valid botflags include:
+      %bs%b - passive share (bot is sharing user records, aggressively)
+      %bp%b - agressive share (bot is sharing user records, passively)
+      %bg%b - global share (bot is sharing all channels)
+      %bh%b - hub (bot is autolinked at highest priority)
+      %ba%b - alternate (bot is autolinked if no hub bots can be linked)
+      %bl%b - leaf (bot is not allowed to link other bots onto the botnet)
+      %br%b - reject (bot will not be allowed to link to the botnet)
+      %bi%b - isolate (isolate the party line across a botlink)
+
+      There are also 10 user-defined bot flags (0-9). Bots may also have +s
+      (share) settings for individual channels.
 %{+m}
-   masters: if there is a comment, you will see it under "COMMENT:"
-%{-}
 
-see also: match
+   Masters: if the user has a comment, you will see it under "COMMENT:".%{-}
+
+See also: match, who, whom%{+m|m}, chattr%{+t}, botattr
 %{help=status}%{+m|m}
 ###  %bstatus%b
 ###  %bstatus all%b
-   displays a condensed block of information about how the bot
-   is running.  here's an example from Snowbot:
-      I am Snowbot, running eggdrop v1.1.1:  400 users (mem: 42k)
-      Running on BSDI 2.5
-      Admin: Robey <robey at wc130.residence.gatech.edu>
-      #turtle   :  2 members, enforcing "+tn-mlk"  (greet, bitch)
-      #gloom    :  3 members, enforcing "+tn-i"  (greet)
-      Server minnie.cc.utexas.edu:6667
-      Online for 4 days, 06:18  (background)  CPU 14:18  cache hit 55.3%%
-
-   the first line tells you the bot's name, what version of eggdrop
-   it's running, the number of users the bot has records of, and the
-   amount of memory being used.
-
-   the second line, tell what operating system the bot is running
-   under.
-
-   the third line, if present, is the contents of your 'admin'
-   line in the config file.
-
-   next is a line for each of the channels your bot is currently
-   monitoring.  for each channel, it lists the number of people on
-   the channel ("members"), what channel modes it's trying to enforce,
-   and which options are set for that channel.
-
-   if your bot is sharing user files with anyone, and is currently
-   either transmitting or receiving the userfile from a bot, it will
-   say so here, and tell how many users have been received so far,
-   or how many more users need to be transmitted.
-
-   the next few lines show the current server, and if the helpbot is
-   in use, its nickname and current server.  to prevent server
-   flooding, both the bot and its helpbot use queues to store replies
-   to queries from users.  if either queue has a significant amount
-   of information in it, this status display will show how full (%%)
-   the queue is.
-
-   the next line tells you how long the bot has been online, and
-   whether it is operating in the background or foreground.  if it's
-   in the foreground, it will tell you whether it's in terminal mode
-   or channel display mode.  (terminal mode makes the local console
-   simulate a dcc chat connection, and channel display mode displays
-   a '.status' and '.channel' output every few seconds.)  it will
-   also give you an estimate of the amount of CPU time (minutes and
-   seconds) the bot has used so far, and how well the cache is
-   working.  (the cache is an attempt to keep the CPU time down, and
-   anything over 50%% or so is just great.)
-
-   if you do %b'.status all'%b you will see another page-full of info,
-   showing every internal setting as specified in the config file.
-   it should be self-explanatory to anyone who needs to use it.
+   Displays a condensed block of status information about the bot.
+   is running. For example:
+      [01:15] #Wcc# status
+      I am Anakha, running eggdrop v1.6.16+stripping:  171 users (mem: 315k)
+      Online for 14 days, 02:50  (background)  CPU 71:29  cache hit 40.3%
+      Admin: Wcc
+      Config file: eggdrop.conf
+      OS: FreeBSD 4.8-RELEASE-p1
+      Tcl library: /usr/local/lib/tcl8.4
+      Tcl version: 8.4.2 (header version 8.4.2)
+      Loaded module information:
+          Channels: #|DAWG|Net, #|DAWG|Tcl
+          Online as: D|Anakha!wcc at cia.nu (|DAWG|Anakha - |DAWG|Net)
+          Server irc.inet.tele.dk:6667 (connected for 11 days)
+          #|DAWG|Net:  6 members, enforcing "+istn" (lurking)
+          #|DAWG|Tcl: 42 members, enforcing "+tn" (lurking)
+
+
+   The first line tells you the bot's name, what version of Eggdrop it's
+   running, the number of users the bot has records of, and the amount of
+   memory being used by the userfile. The second line tells you the uptime of
+   the bot, CPU time, and cache hit. The third shows the bot's admin, and the
+   forth shows its current config file. The fifth line shows what operating
+   system the bot is running on. The next two lines show Tcl information. If
+   debug mode is enabled, additional info may be shown. Sharing information
+   will also be shown if it's being used.
+
+   Select information from modules will be displayed after the core
+   information. If you use %b'.status all'%b instead, you will see all status
+   information available from loaded modules.
 
-see also: set, channel, debug
+See also: channel%{+n}, set%{+m}, debug
 %{help=uptime}%{+m|m}
 ###  %buptime%b
-   displays the bot's current uptime like .status would show.
+   Displays the bot's current uptime.
 
-see also: status
+See also: status
Index: eggdrop1.6/language/core.danish.lang
diff -u eggdrop1.6/language/core.danish.lang:1.5 eggdrop1.6/language/core.danish.lang:1.6
--- eggdrop1.6/language/core.danish.lang:1.5	Wed Mar 19 18:04:48 2003
+++ eggdrop1.6/language/core.danish.lang	Wed Nov 26 19:07:46 2003
@@ -1,7 +1,7 @@
 # core.danish.lang
 #   core language messages for eggdrop
 #
-# $Id: core.danish.lang,v 1.5 2003/03/20 00:04:48 wcc Exp $
+# $Id: core.danish.lang,v 1.6 2003/11/27 01:07:46 wcc Exp $
 
 # General stuff
 0x001,Brug
@@ -116,7 +116,7 @@
 0x52b,status mode
 0x52c,log dump mode
 0x52d,Online for
-0x52e,cache hit
+0x52e,Cache hit
 0x52f,Tcl bibliotek:
 0x530,Nye brugere for flags
 0x531,underrette
Index: eggdrop1.6/language/core.english.lang
diff -u eggdrop1.6/language/core.english.lang:1.37 eggdrop1.6/language/core.english.lang:1.38
--- eggdrop1.6/language/core.english.lang:1.37	Sun May  4 17:04:32 2003
+++ eggdrop1.6/language/core.english.lang	Wed Nov 26 19:07:46 2003
@@ -1,7 +1,7 @@
 # core.english.lang
 #   core language messages for eggdrop
 #
-# $Id: core.english.lang,v 1.37 2003/05/04 22:04:32 wcc Exp $
+# $Id: core.english.lang,v 1.38 2003/11/27 01:07:46 wcc Exp $
 
 # General stuff
 0x001,Usage
@@ -116,7 +116,7 @@
 0x52b,status mode
 0x52c,log dump mode
 0x52d,Online for
-0x52e,cache hit
+0x52e,Cache hit
 0x52f,Tcl library:
 0x530,New users get flags
 0x531,notify
Index: eggdrop1.6/language/core.french.lang
diff -u eggdrop1.6/language/core.french.lang:1.28 eggdrop1.6/language/core.french.lang:1.29
--- eggdrop1.6/language/core.french.lang:1.28	Mon Mar 10 19:22:25 2003
+++ eggdrop1.6/language/core.french.lang	Wed Nov 26 19:07:46 2003
@@ -1,7 +1,7 @@
 # core.french.lang
 #   core language messages for eggdrop
 #
-# $Id: core.french.lang,v 1.28 2003/03/11 01:22:25 wcc Exp $
+# $Id: core.french.lang,v 1.29 2003/11/27 01:07:46 wcc Exp $
 
 
 # General stuff
@@ -117,7 +117,7 @@
 0x52b,mode statut
 0x52c,mode log
 0x52d,En ligne depuis
-0x52e,cache hit
+0x52e,Cache hit
 0x52f,librairie Tcl:
 0x530,Les nouveaux utilisateurs obtiennent les drapeaux
 0x531,annonce
Index: eggdrop1.6/src/mod/channels.mod/help/channels.help
diff -u eggdrop1.6/src/mod/channels.mod/help/channels.help:1.12 eggdrop1.6/src/mod/channels.mod/help/channels.help:1.13
--- eggdrop1.6/src/mod/channels.mod/help/channels.help:1.12	Sat Nov  1 14:00:31 2003
+++ eggdrop1.6/src/mod/channels.mod/help/channels.help	Wed Nov 26 19:07:46 2003
@@ -58,7 +58,7 @@
 %{help=-chan}%{+n}
 ### %b-chan%b <channel>
      This removes ALL information about a channel from the bot. It's not made
-     permanent unless the channel file has been saved.  If you remove a channel
+     permanent unless the channel file has been saved. If you remove a channel
      by accident, you can undo your changes with the 'chanload' command. Note
      that you will lose any other changed made since the last save.
 
@@ -93,14 +93,14 @@
            Created 15:10
 
    The number (5) can be used to reference the ban if you wish to remove it
-   (see '.-ban'). Next is the actual hostmask being banned.  The "(perm)" means
-   that the ban is "permanent": that is, it doesn't automatically expire. If
-   there is an elapsed time showing instead, the time displayed is how long the
-   ban has been active. Those kinds of bans expire after two hours. The second
-   line of the ban entry is the comment ("revolving check policy"), and who set
-   the ban (paulie). The last line shows when the ban was added, and possibly
-   the last time the ban was activated on the channel (if it's different from
-   the creation time).
+   (see %b'-ban'%b). Next is the actual hostmask being banned. The "(perm)"
+   means that the ban is "permanent": that is, it doesn't automatically expire.
+   If there is an elapsed time showing instead, the time displayed is how long
+   the ban has been active. These types of bans expire after two hours. The
+   second line of the ban entry is the comment ("revolving check policy"), and
+   who set the ban (paulie). The last line shows when the ban was added, and
+   possibly the last time the ban was activated on the channel (if it's
+   different from the creation time).
 
    Sometimes there will be a "!" or "*" right before the number. A "!" means
    the ban is in the bot's ban list, but is not currently on the channel. A "*"
@@ -130,10 +130,10 @@
              Created 01:15
 
    The number (3) can be used to reference the invite if you wish to remove it
-   (see '.-invite'). Next is the actual hostmask being invited.  The "(perm)"
+   (see %b'-invite'%b). Next is the actual hostmask being invited. The "(perm)"
    means that the invite is "permanent": that is, it doesn't automatically
    expire. If there is an elapsed time showing instead, the time displayed is
-   how long the invite has been active. Those kinds of invites expire after one
+   how long the invite has been active. These types of invites expire after one
    hour. The second line of the invite entry is the comment ("requested"), and
    who set the invite (Wcc). The last line shows when the invite was added, and
    possibly the last time the invite was activated on the channel (if it's
@@ -169,10 +169,10 @@
              Created 01:15
 
    The number (3) can be used to reference the exempt if you wish to remove it
-   (see '.-exempt'). Next is the actual hostmask being exempted.  The "(perm)"
+   (see %b'-exempt'%b). Next is the actual hostmask being exempted. The "(perm)"
    means that the exempt is "permanent": that is, it doesn't automatically
    expire. If there is an elapsed time showing instead, the time displayed is
-   how long the exempt has been active. Those kinds of exempts expire after one
+   how long the exempt has been active. These types of exempts expire after one
    hour. The second line of the exempt entry is the comment ("requested"), and
    who set the exempt (Wcc). The last line shows when the exempt was added, and
    possibly the last time the exempt was activated on the channel (if it's
@@ -202,7 +202,7 @@
    setting. This allows you to return to a previous setting if you've really
    messed things up.
 
-See also:%{+n} +chan, -chan,%{+n|n} chansave, chanset, chaninfo
+See also: %{+n}+chan, -chan, %{+n|n}chansave, chanset, chaninfo
 %{help=chanset}%{+n|n}
 ###  %bchanset%b <channel> <settings>
    Allows you to change the channel settings (see %b'chaninfo'%b for the
@@ -211,13 +211,13 @@
    Changes are used until the next rehash/chanload/restart, and are saved
    whenever the channel settings are saved.
 
-See also: %{+n}+chan, -chan%{+n|n} chanload, chansave, chaninfo
+See also: %{+n}+chan, -chan %{+n|n}chanload, chansave, chaninfo
 %{help=chansave}%{+n|n}
 ###  %bchansave%b
    Saves the channel settings to the file defined by the %b"chanfile"%b
    setting. This file is reloaded during rehash and restarting the bot.
 
-See also: %{+n}+chan, -chan%{+n|n} chanload, chanset, chaninfo
+See also: %{+n}+chan, -chan %{+n|n}chanload, chanset, chaninfo
 %{help=chinfo}%{+m|m}
 ###  %bchinfo%b <user> [channel] [info-line/none]
    Sets the information line for a user. This line is shown via the /msg
Index: eggdrop1.6/src/mod/channels.mod/help/set/channels.help
diff -u eggdrop1.6/src/mod/channels.mod/help/set/channels.help:1.5 eggdrop1.6/src/mod/channels.mod/help/set/channels.help:1.6
--- eggdrop1.6/src/mod/channels.mod/help/set/channels.help:1.5	Sat Feb  1 22:20:44 2003
+++ eggdrop1.6/src/mod/channels.mod/help/set/channels.help	Wed Nov 26 19:07:46 2003
@@ -1,16 +1,14 @@
 %{help=set share-greet}%{+n}
 ###  %bset share-greet%b 0/1
-   if on (1) then share-bots will share their user's info lines
-   with other share bots.
+   Share user's info lines with other sharebots?
 %{help=set use-info}
 %{+n}
 ###  %bset use-info%b <0/1>
-   specifies whether to activate the info system.  if this is off,
-   the bot will not accept changes to any user's "info line" (the
-   line shown for '/msg whois' and '/msg who' requests, and shown
-   when a user joins the channel is you have set 'greet' on).
-   this disables '/msg whois' and '/msg who' obviously, and makes
-   the setting of 'greet' meaningless.
+   This activates or deactivates the info system. If this is off, the bot will
+   not accept changes to any user's "info line" (the line shown for '/msg
+   whois' and '/msg who' requests, and shown when a user joins the channel is
+   you have set 'greet' on). This disables '/msg whois' and '/msg who', and
+   makes the 'greet' setting meaningless.
 %{help=set chanfile}
 %{+n}
 ###  %bset chanfile%b
@@ -18,6 +16,6 @@
    for the bot.  it can only be set in the config file.
 %{help=set quiet-save}
 %{+n}
-###  %bset quiet-save%b 0/1
+###  %bset quiet-save%b <0/1>
    this sets if "Writing user file..." & "Writing channel file..."
    are logged.
Index: eggdrop1.6/src/mod/share.mod/help/share.help
diff -u eggdrop1.6/src/mod/share.mod/help/share.help:1.5 eggdrop1.6/src/mod/share.mod/help/share.help:1.6
--- eggdrop1.6/src/mod/share.mod/help/share.help:1.5	Tue Jan 28 23:48:42 2003
+++ eggdrop1.6/src/mod/share.mod/help/share.help	Wed Nov 26 19:07:46 2003
@@ -1,10 +1,10 @@
 %{help=flush}%{+n}
 ###  %bflush%b <bot>
-   clears the resync buffer for a share-bot.  this is useful if you
-   want to start over with a userfile transfer: you can unlink the
-   sharebots, flush the resync buffer, and relink.
+   This clears the resync buffer for a share-bot. This is useful if you want to
+   start over with a userfile transfer. You can unlink the sharebots, flush the
+   resync buffer, and relink.
 
-see also: link, chattr, unlink
+See also: link, chattr, unlink
 %{help=set allow-resync}%{+n}
 ###  %bset allow-resync%b 0/1
    This setting determines if the bot will re-send the userfile every
@@ -25,7 +25,7 @@
 ###  %bset private-global%b 0/1
    If you are sharing userfiles with someone else, and you don't
    want %bany%b global flags on the other bots propagated to your bot,
-   set this.  It overrides the setting of private-globals.
+   set this. It overrides the setting of private-globals.
 
 see also: set private-globals
 %{help=set private-globals}%{+n}
Index: eggdrop1.6/src/mod/transfer.mod/help/set/transfer.help
diff -u eggdrop1.6/src/mod/transfer.mod/help/set/transfer.help:1.3 eggdrop1.6/src/mod/transfer.mod/help/set/transfer.help:1.4
--- eggdrop1.6/src/mod/transfer.mod/help/set/transfer.help:1.3	Wed Jan 22 20:13:29 2003
+++ eggdrop1.6/src/mod/transfer.mod/help/set/transfer.help	Wed Nov 26 19:07:46 2003
@@ -12,7 +12,7 @@
    ircII client defaults to 512, but admits that it may be too small.
    1024 is the most common setting.
 
-   You can set this to 0, which turns on "turbo dcc".  In turbo dcc
+   You can set this to 0, which turns on "turbo dcc". In turbo dcc
    mode, the bot will dump transfers as fast as possible, only
    stopping to count acks after it's finished.  This can dramatically
    improve the speed of file transfers, and is recommended.
Index: eggdrop1.6/src/patch.h
diff -u eggdrop1.6/src/patch.h:1.1011 eggdrop1.6/src/patch.h:1.1012
--- eggdrop1.6/src/patch.h:1.1011	Wed Nov 26 10:01:10 2003
+++ eggdrop1.6/src/patch.h	Wed Nov 26 19:07:46 2003
@@ -10,7 +10,7 @@
  * statement, leave the rest of the file alone, this allows better
  * overlapping patches.
  *
- * $Id: patch.h,v 1.1011 2003/11/26 16:01:10 wcc Exp $
+ * $Id: patch.h,v 1.1012 2003/11/27 01:07:46 wcc Exp $
  */
 /*
  * Copyright (C) 1997 Robey Pointer
@@ -41,12 +41,12 @@
  *
  *
  */
-patch("1069862390");            /* current unixtime */
+patch("1069895249");            /* current unixtime */
 /*
  *
  *
  */
-patch("getdesc-crash");
+patch("help-and-docs1");
 /*
  *
  *
----------------------- End of diff -----------------------


More information about the Changes mailing list