Release date: Sun Nov 14 22:57:50 CET 1999 Patch: 1.4.0 -> 1.4.0+rtc1 Author: rtc@gmx.de Copyright: (c) 1999 rtc License: GPL DESCRIPTION The +rtc patch series contains changes that the mainstream eggdev rejects to include in the official release because it alters behaviour that has been traditional for eggdrop bots. However if you are new to eggdrop and/or like the changes that have been made, you are welcome to use this patch. CHANGES THAT HAVE BEEN MADE * '.chat' doesn't automatically put you on the party line anymore if you had chat mode turned off. It will show you your current chat status now. * A quite different alltools.tcl which contains bugfixes, is easier extensible and understandable (which make it a bit slower) and has been optimized significantly on several places. Both versions should be compatible to each other. INSTALLATION Be sure to make a backup of eggdrop1.4.0.tar.gz before you start. Type the following commands on your shell prompt in a directory that contains both eggdrop1.4.0.tar.gz and eggdrop1.4.0+rtc1.patch: gunzip eggdrop1.4.0.tar.gz tar xvf eggdrop1.4.0.tar cd eggdrop1.4.0 patch -p1 < ../eggdrop1.4.0+rtc1.patch If you have GNU tar, you should use 'tar xzvf' instead of the gunzip/tar combo (always works on Linux machines, but not on most Solaris boxes). Don't forget to rm the big 'eggrop1.4.0.tar' file if you used gunzip (you made a backup as I told you, didn't you?) Now compile as usual (./configure; make; make install) and restart the bot (telnet localhost 3333; (login); .die; scripts/botchk). Note that '.rehash' or '.restart' is *not* sufficient. The console command '.status' should now report that you are using version 1.4.0+rtc1. NOTE No protocol changes have been made. This means that no problems should occur linking to other 1.4.0 bots with or without the +rtc patch. However this might change either in future releases of eggdrop or another +rtc patch. REPORTING BUGS If you find a bug and are absolutely sure that it was caused by this patch (which is very unlikely), you can mail me a description of what goes wrong under which circumstances (use doc/BUG-REPORT as a template). Bug reports or questions not related to this patch should be reported/asked on the mailing list. Read the README file in your eggdrop distribution for details I am receiving many mails asking whether I can please write a config file for someone because it is soo difficult or whether I can lend my bot, maybe only for one day. Such mails will be ignored, you should understand why.