Release 27
----------

 > Fixed a spelling mistake in the channel protection ban.
 > Fixed a bug OnOps() where the bot wouldn't auto-designate if autodes was enabled.
 > Added hex edit protection in the hedit.dll file.  Doesn't protect 100% but if someone 
   tries to change more than a few bytes they get screwed.  And, the idle string is
   preprotected.
 > Fixed a CPU resource eater bug when hammering channel to get back in after ban 
   (or if channel is full.)
 > Verified that bot reconnects on dupe
 > Find bugs, cause I think this is the final alpha where I'm adding features.

Release 26
----------
 
 > Fixed !learn and !forget so DSHR users can't use it.  As a matter of fact, if someone
   tries to axs the bot with DSHR it doesn't work at all.  This way if someone gets your
   bot passwd, you should still be safe.
 > Alpha testers:  Find me bugs, and request more features.  Give me feedback on a passwd 
   command?  Would allow operators to remotely change their bot passwd to something else?
 > Figured out the problem with the colors.  All you Windows 9x users are shit out of
   luck.  Colors work perfect on WinNT/2000.  I'll look into the 9x problem in the 
   future.
 > Fixed case insensitive !forget.
 > Fixed crash possible by people with diablo-bot.

Release 25
----------

 > Moved triggers out of hard coding into the cfg file format is as follows:
	trig=<triggername> <adder> <info>
   For example:
	trig=join WoLF`Azure~{RC} For the requirements to join wolf ...
   Adder is just kept for tracking of who is doing stuff to your bot.
 > Triggers work in the following way:
	Anyone can request a trigger.
	Only people in the axs list can add or remove triggers.
 > To add a trigger use the !learn command.  !forget to delete a trigger.
	Ie: !learn join For the entry requirements etc...
	Ie: !forget join
 > Possible problem using DSHR to add triggers.  Release 26 will include any bugfixes
   Alpha testers can find, will include channel bans, and will autoignore !learn and !forget
   from DSHR.

Release 24
----------

 > Fixed some problems with the queue that would allow it to flood on connect.
 > Fixed a problem where when the bot got disconnected any commands in the queue would
   still try to get sent.
 > Fixed some other coding problems with the sending queue.  Much improved now.

Release 23
----------

 > Fixed ?? /exploit - It now shitlists and bans anyone who tries it.
 > Fixed safeadd adding to shitlist.

WoLF`C`BoT v2.0.x
-----------------

	Welcome to the second generation of WoLF`C`BoT.  This version is a total code
rewrite from the original, so the only things that have remained the same are the remote
user controls.  This documentation will probably also be more in depth than the docs 
included with v1.0 Beta.  If anyone is interested in writing in depth docs, or a portion
thereof, contact me WoLF`Azure~{RC} on battle.net, or on email at madiver_RC@hotmail.com.

Release 22
----------

 > Semi-public alpha release (limited distribution)
 > If you alpha testers let this out, I'll hunt you down and kill you all.
 > No documentation at this point.
 > Triggers don't work yet.


Configuration file:
	
	The configuration file format has changed entirely.  It now uses a more standard
windows based configuration file, and also tracks all the changes made to it by remote users.
All the settings are now combined into 1 file (wolfbot.cfg), which lives in the same directory
as the executable.  The configuration file is now divided into 8 sections:

[general]
username=<enter the bots username here> (ie; username=WoLF`Azure~{RC})
password=<password to login to b.net> (ie; password=usuck)
server=<server to login to (IP ONLY)> (ie; server=209.67.136.170)
channel=<home channel> (ie; channel=dark realm)

[idle info]
idle=<string to idle with> (ie; idle=WoLF`C`BoT is backdoor free baby.)
idleint=<# of ms between idles> (ie; idleint=120000)

[flood settings]
floodint=<# of ms between messages to prevent flooding> (ie; floodint=3700)

[safelist]
protect=<off or on, whatever setting you want protect to start with> (ie; protect=on)
safe=<tag who-added> (ie; safe=WoLF WoLF`Azure~{RC}) (this means WoLF is safe and I added them)

[shitlist]
shit=<tag who-added> (ie; shit=PooClan WoLF`Azure~{RC})

[designate list]
designate=<on of orr, whatever setting you want autodes to start with> (ie; designate=on)
des=<who who-added> (ie; des=WoLF`Azure WoLF`Azure~{RC} (meaning WoLF`Azure is on des list added by me))

[access list]
access=<who password who-added> (ie; access=WoLF`Azure~{RC} uwish WoLF`Azure~{RC})

[trigger list]
triggers=<off or on> (ie; triggers=on)
trig=<trigger> <user who added> <data-to-send> (ie; trig=winters WoLF`Azure~{RC} I don't wanna grow up, I'm a backdoor kid!)

** NOTE TO ALPHA TESTERS:  I really need someone to explain the .cfg file format better
if you can't figure it out.. tough shit.  I'm going to be making a utility to convert
the old format to the new format, but not for a while now.  Also, since this is alpha, 
I wouldn't have it guarding your channel(s) until we get a good enough testbed to find
some of the bugs and squash them.  (Bug reporting; find me *ALIVE* on b.net)
