Finally, after a long time in development and re-coding, I've put a version of WX onto the website for you to download and try out. This is the first edition of the WX available for public use, and as such, there might be quirks in how it operates. As a software developer, the biggest worry is something critical is overlooked, but also as a small solo developer, I only have access to X number of machines, and so far, this program runs on them all. Without me having to install additional components which InnoScript determines that I should install to make the program work. Time will tell if it all hangs together for everyone.

This edition of InnoScript also sticks things into the installer which should make the install work properly with Vista, ugh. Oh well, guess I should support non-os computers as well.

Some of the things which do seem to be working properly is that the Who Is detection can now be used again, either with a Who Is, or by selecting the correct combination of settings to force the Who Is to be processed when a Furre Enters or Exits a dream. One of the biggest changes the new protocol has done to the bot is suddenly, Furre's who are moving have their name available to the botscript, that is, you can code:

Trigger Name: Whisper Specific Names
Someone comes into view
AND:
    $DATABASE: if there is a record in table {messages} in database {4}

where ID is {[player]}
    $DATABASE: if field {messagecount} in database {4} in table {messages}

is greater than {0} from ID {[player]}
THEN:
      Whisper back {Psst, you got mail!}

Woot! I will have to add all the additional information tables to this site for you to get the most from your bot. Some of you may notice that the size of the program is larger, however, this is actually due to more efficient coding, and there's something strange to read about a larger version of a program. See, some of the code used to not be in the bot, but was run from support files, those infamous OCX files. But in the process of ridding myself of the need to use those, I had to code into the bot the functions which used to exist in them, hence, the program is larger. But it is less dependent on external libraries which might not run on all machines. For example, MsWinSck is 122kb, I no longer rely on it, but needed to have all the functionality of WinSock to be able to connect to the game server and the client. Hence, I had to code my own wrapper for WinSock.

Some of the additional coding is into the new "chrome" for the bot, redesigned the user interface, did attempt to make it more user friendly, you'll let me know if I succeeded there, won't you. Plus there's lots of hook routines to permit me to keep expanding this version with more functionality without the extensive core hacks that SK would of required. So expect some interesting new toys to play with in Furbot, like those user programmable buttons which you see on the user interface. Plus I'll code in a system where you can use the client to trigger an action in the bot. A web interface system is on the drawing board as well. Might even throw in whisper windows. Who knows. I do.

Well, there you go, download, install, and you will note that the program installs into its own folder, not the old furbot folder, this is a complete break from the old furbot with that. If it runs, you're good. If not, let me know what is causing the issue with your machine and we will work to getting the program parts it needs for windows to have to run properly.

Now, a word of warning on using botscripts. This program will change the file format of the botscript if you make changes to the script, otherwise it should run all the old botscripts without program. The new file format is completely incompatible with SK, the old bot will not open them. So if you make changes to take advantage of the new functionality of the bot, you should consider saving as a different filename to preserve your old script just in case you need to refer back to it and see how it worked in the old bot.