[project @ 2005-06-23 06:20:44 by unknown_lamer]

[clinton/bobotpp.git] / NEWS

(-*- text -*-)
User Visible Changes In Bobot++

IMPORTANT NOTES: 
  As of version 1.98 unknown_lamer is the new maintainer.  Also as of
  version 1.98, you must have Guile 1.5.6+ or 1.6.x in order to
  compile scripting support.

=====================================================================
====== The News =====================================================
=====================================================================

Version 2.1.8: 
- Added bot:protection/[none|ban|kick|deop] and bot:aop/[yes|no]
  constants to the Scheme scripting interface

Version 2.1.7:
- Fixed a number of small bugs and corner cases
- Should compile without warnings (GCC 3.4)

Version 2.1.6:
- The String class implementation has been redone and replaced by one
  based on std::string (eventually String will be gone entirely, but
  it a lot of work)
- Patches from Jos Hulzink <josh@stack.nl> were applied which fix a
  few major bugs in the StringTokenizer (thanks)

Version 2.1.5: Cleanups
- A DCC CHAT with the bot may now only be initiated if the user is a
  Friend of the bot
- Implemented bot:ctcp-quote
- The Bot Configuration section of the manual has been completed.
- Fixed a potential (but unlikely) buffer overflow in Utils::strToTime
  (if there were more than 512 digits in part of the string form of
  the time the buffer would overflow)
- Misc. Bugfixes

Version 2.1.4: DCC Support Enhancements
- Internal Change: DCCConnection is now an abstract class
- Internal Change: DCCChatConnection provides the functionality of
  the old DCCConnection so that DCC FILE support can be added
- New Scheme Procedure: (bot:sent-to-me? message), checks to see if a
  message was addressed to the bot. This is better than using
  bot:match-to-me because the hook will continue to function if the
  bot's nick changes. The only downside to using it is that there may
  be an increased overhead of calling more hooks than could be called,
  but that shouldn't be much of a problem.
- New Scheme Procedure: (bot:change-command-level command level),
  changes the level a user command to allow a user of `level' level or
  above to run it.

Version 2.1.3: Something
- The flood rate can now be set using !setfloodrate INTEGER. The
default is two messages per second before the bot will ignore