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