Aug 27, 2016, 1:05 am UTC
header image
Cheezy Install Verification System
Written by Dream Dancer   
Oct 11, 2015 at 11:57 AM

Cheezy Installation Verification System is a mini-program which scans a selected folder in program files, (or any location), and generates a simple manifest of the contents of that folder.

Runs as is, no dependencies nor any packaging or installer.

Simple to use, only has a half dozen menu items to work with.

Last Updated ( Oct 11, 2015 at 01:00 PM )
Does Your Version Contains Command X?
Written by Dream Dancer   
Jan 25, 2011 at 09:55 PM

There is a quick and easy check for any command in your version of Furbot, if you have the Special menu selection under the Help. That opens the botclipboard containing a list of all triggers, additional conditions, commands, and wolfscript contained in your version of Furbot.

Teaching Furbot To Conduct Trades
Written by Dream Dancer   
Jan 15, 2011 at 03:47 PM

Hoi, new content? Why yes!

To begin in with, conducting unattended trades with furbot, you first have to understand, it's a program, and what it does with a trading session is only as good as how well you take advantages of the available commands and construct a script which does what you expect it to do. Next thing to take into consideration is that a trade action from the server is an emit, and is handled by triggers, not actions. This gives you a bit more security in constructing a trade automation because you don't have to do extensive syntax checking and parsing, you just need to ensure that the emiticon is the one for trading, and test OTHER stuff for the bot to do it's thing.

Trigger Name: Trade Start
 Stop Action Search if TRUE
An emit is seen
    if variable {[emiticon]} is equal to {100} (numeric comparison)
    if variable {[message]} contains text _
{asks you to have a trading session} (case insensitive)
      Store {[word2]} to variable {[trade-name]}
      $LOG: Save entry {[message]} to file _
{[scriptdir]logs\trades-[year]-[month].log} _
under record {[trade-name]-[time]}
      Say {trade-start}
      Whisper {[trade-name]} the message {You have started a trading _
session with an automation, as such, the wording has to be exact for the _
script to follow through and there be a successful trade. This session is _
for the purpose of trading one GD to the bot for entry into the gaming _
session which is now open. Please add one GD to the trade session and _
follow the prompts which will be whispered to complete the trade.}

Last Updated ( Jan 15, 2011 at 04:52 PM )
Running FurBot under WINE
Contributed by Calite   
Mar 22, 2009 at 07:24 PM

The quickest and least painful way to get FurBot running under WINE. Though, it's still not entirely painless...

Last Updated ( Mar 22, 2009 at 08:23 PM )
Furbot Dependencies - A List For Implementators
Written by Dream Dancer   
Mar 22, 2009 at 08:28 AM

I figured I'd post the process monitor list of DLL's and other things Furbot depends on when running, perhaps this will help some people get a handle on why Furbot doesn't run under some situations, and also help people maybe get Furbot running under Wine.

Who knows.

List in the More

Last Updated ( Mar 22, 2009 at 08:30 AM )
Bug Fix 2.4.250
Written by Dream Dancer   
Feb 27, 2009 at 07:54 PM

Really, really, minor fix to the bot which involved the MONTH variable in the time setting system. It seems that for the past several years, there was a reset of the month buried in the code which cleared the month variable, but only if you triggered the use of Furcadia time. Oh go figure. I think my intention was to have the date follow convention with the rolling over of the midnight, then saw the issue of right below that, it would reset the date back to the current date, and may have had intentions to do something fancy, but didn't, and forgot to clean up the code before heading to work on another part of the bot.

No need to download this UNLESS you need the MONTH when using Furcadia time.

New Stuff Up Till 2.4.242
Written by Dream Dancer   
Jun 22, 2008 at 07:10 AM

Well, a list of new stuff since I last worked up such a list:

Last Updated ( Mar 22, 2009 at 06:25 PM )
Finally, 2.4
Written by Dream Dancer   
Jun 15, 2008 at 11:58 AM

Got a documentation page up for how to use the WebServer access functions in Furbot, and made a couple of minor adjustments to the coding of the system.

There was apparently a bug, or quirk, in the server command parsing switch where if you got a command from the server in which there was no native means of decoding, you were out of luck. Well that's been fixed, however, it's OFF by default. You can turn it on either with the special variable [$PROCESS_OTHER_COMMANDS], just set that to TRUE, or you can enable it under the advanced bot settings. Note that I do NOT recommand that you run the bot with that enabled all the time, hence it's OFF by default, because all the unhandled commands are passed to the trigger processor, like sounds, play music, the Eight triggers, ...

Last Updated ( Mar 22, 2009 at 06:26 PM )
So You Want To Make A Bot Program?
Written by Dream Dancer   
Mar 17, 2008 at 09:46 PM

Well, I got interested in what I've put into Furbot WX so far, and constructed a quick and dirty tally program to peek into it's guts:

Last Updated ( Mar 22, 2009 at 06:27 PM )
Interesting Bug Fix
Written by Dream Dancer   
Mar 08, 2008 at 07:20 AM

This is a minor update in which while the main focus of the update was to permit the ability to "recurse" procedures, that is, you can have procedures call other procedures, just not have any procedure call a calling procedure, it also address's a couple of bugs in the code.

For example, a gift will either shut the bot down, render it unable to reconnect, or crash, depending on when and how it saw the gift.

The portrait select command was not permitting the user to enter a value for which portrait they wanted.

And a Furcadia installation where the settings was not in an expected default location would cause the bot to fail in making a proper connection.

Last Updated ( Mar 08, 2008 at 08:21 AM )
header image