Version 1.52p1:

Patch release. Bug fixes only.

  + eliminated some redundant code, and the duplicate auto-login messages
    when a user DCC chats the bot.

Version 1.52:

Bug fixes, new features, added a bit for people wanting to add code to my
script... No specific part of the script has been fixed in this release.

  + added a more secure auto op system: login, and the bot ops you on all
    channels you're on where you have op access, unless auto ops are
    disabled via the global flag +O.. if you join a channel and
    you are already logged in, you will be auto opped there. don't forget
    that the login system should be very secure, and if anyone finds any
    bugs I would *VERY MUCH* like to be told about them, please email to
    vulture@abac.com!
  + changed above auto op system to support voices too :) so set your chans
    -autovoice with your bot.. global flag +V disables it
  + subnet bugfixes, not in the subnet code itself, but in some of the subnet
    commands (subnet rehash, restart, mass join, and mass say, and maybe
    some others I've forgotten ;), because they weren't working with the new
    protocol (still were checking for the subnet ID themselves!)
  + .+ban bans for a hostmask!!!! see below.
  + the uh2mask proc will return a *!*ident@*.domain.com hostmask for a
    n!u@h as the first and only parameter to it... have fun ;)
  + .adduser in the channel can now take only one parameter, as well as two,
    if the user you are trying to add is on the channel. (in which case the
    bot generates a hostmask for the user)
  + added a .math dcc/msg/channel command that easily and quickly evaluates
    a mathematical expression (spaces allowed)
  + .ctime bugfix; it was 28800 seconds behind (0 = sometime late on dec 31,
    1969); if it's SUPPOSED to be this way please let me know because I thought
    that time_t of 0 is Jan 1 1970, 00:00:00.
  + included a vQOTD script, also made by me, that does a few interesting
    things...
  + warning about no password can now be disabled, both globally and for
    individual channels (commands: .nwp, .lnwp, .rnwp)
  + explainban command in /msg will explain why a user is banned (the user who
    sent the command) on any given channels, by any matching bans, or 0 for the
    global channel
  + when you successfully DCC chat the bot and login (and don't change your
    nick before finishing that), you'll be authorized to use all the public
    commands, as if you did a /msg <bot> login. (it saves the n!u@h of the
    user that sends the DCC request, and if it's the same when they login
    they get authed, let me know if there are any bugs with this!)
  + enhanced DCC .whochan and /MSG WHO command (toggleable), very cool looking
    if I do say so myself :) (looks ugly without a fixed width font though)
  + the /MSG PASS command will now replace your password (no parameters will
    give you the syntax...)

Version 1.51:

This is basically a release to fix and add to the .+ban, .-ban, and .bans
channel commands.  Lots has been added to those...

  + added creator/ban matching to the public .bans command, as the parameter.
    examples (in all cases, it's case insensitive):
      .bans dejective	: lists any bans created by "dejective"
      .bans *aol*	: lists any bans matching "*aol*"
      .bans *get*	: lists any ban descriptions matching "*get*" (like
			  "GET OUT")
    note that it should work fine if your specification matches both the
    creator and the ban, but this should never happen.
  + changed .+ban so that if you give no reason for a ban the reason will
    include how long it is (or if it is permanent, that it is permanent ;)
  + fixed the .+ban bug where it simply truncates a ban reason longer than
    63 bytes; this will now generate an error
  + made the .+ban lifetime parameter optional; if you don't give a lifetime,
    it'll be set to the variable ban-time in your eggdrop.conf; if you don't
    give a reason it'll set a lame default reason, to which anything compares
    favorably :) you can basically give either, or, none, or both.. all four
    combinations have been tested, but if you find a problem with this
    relatively picky and probably a bit unstable code, please email me your
    bug reports at vulture@abac.com!
  + made the .+ban syntax description (when you just type .+ban in the chan)
    a bit clearer (the lifetime parameter is explained a bit more)
  + fixed a lame .+ban bug where it showed the number of "seconds" when you
    made a timed ban -- actually it's minutes..
  + .-ban now yells at people who try to use it to remove global bans (which
    never worked, but in the past it acted as if everything went fine)
  + removed the botnet ping feature, it is obsoleted by the .trace command
  + .+ban in the channel is now capable of banning by nick instead of
    user@host (so ".+ban dejective" will work just fine), but it won't make a
    mask of it, so if the person reconnects with a different ident and/or IP
    address on the same subnet, they won't be banned anymore (eggdrop
    extensions was capable of this a long time ago, but it was in a C program,
    which isn't portable, and this code has yet to be rewritten in Tcl...
    would you like to? :)

Version 1.5:

  + added lots of documentation!!!
  + turned the whole thing into more than one file, so now it's a .tar.gz
    instead, which is easier to install anyway
  + more secure subnet system, see README.SUBNET
  + added ability to do mathematical expressions in the .+ban command:
    <Vulture> .+ban lamer!lame@lame.org 60*3 3 hr ban
    will add a 3 hour ban for lamer!lame@lame.org
  + split the config from the main .tcl file, making life a bit easier..
