[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 has been removed and replaced by std::string
- 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
Commit	Line	Data
91dddabd	1	(-- text --)
91dddabd	2	User Visible Changes In Bobot++
be3612f3	3
91dddabd	4	IMPORTANT NOTES:
	5	As of version 1.98 unknown_lamer is the new maintainer. Also as of
	6	version 1.98, you must have Guile 1.5.6+ or 1.6.x in order to
	7	compile scripting support.
be3612f3	8
	9	=====================================================================
	10	====== The News =====================================================
	11	=====================================================================
2e20c3e1	12
af8c61fe	13	Version 2.1.8:
	14
	15	- Added bot:protection/[none\|ban\|kick\|deop] and bot:aop/[yes\|no]
	16	constants to the Scheme scripting interface
	17
980ce0f4	18	Version 2.1.7:
cf8ea873	19	- Fixed a number of small bugs and corner cases
cf8ea873	20	- Should compile without warnings (GCC 3.4)
980ce0f4	21
2e18045a	22	Version 2.1.6:
	23	- The String class has been removed and replaced by std::string
	24	- Patches from Jos Hulzink <josh@stack.nl> were applied which fix a
980ce0f4	25	few major bugs in the StringTokenizer (thanks)
2e18045a	26
c8f13c06	27	Version 2.1.5: Cleanups
	28	- A DCC CHAT with the bot may now only be initiated if the user is a
	29	Friend of the bot
	30	- Implemented bot:ctcp-quote
c7d9fb19	31	- The Bot Configuration section of the manual has been completed.
a6339323	32	- Fixed a potential (but unlikely) buffer overflow in Utils::strToTime
	33	(if there were more than 512 digits in part of the string form of
	34	the time the buffer would overflow)
6b59e728	35	- Misc. Bugfixes
c7d9fb19	36
4edefeb6	37	Version 2.1.4: DCC Support Enhancements
	38	- Internal Change: DCCConnection is now an abstract class
	39	- Internal Change: DCCChatConnection provides the functionality of
	40	the old DCCConnection so that DCC FILE support can be added
	41	- New Scheme Procedure: (bot:sent-to-me? message), checks to see if a
	42	message was addressed to the bot. This is better than using
	43	bot:match-to-me because the hook will continue to function if the
	44	bot's nick changes. The only downside to using it is that there may
	45	be an increased overhead of calling more hooks than could be called,
	46	but that shouldn't be much of a problem.
	47	- New Scheme Procedure: (bot:change-command-level command level),
	48	changes the level a user command to allow a user of `level' level or
	49	above to run it.
	50
e171dcce	51	Version 2.1.3: Something
	52	- The flood rate can now be set using !setfloodrate INTEGER. The
	53	default is two messages per second before the bot will ignore
	54