This is the all purpose variable which gets the name of the triggering furre, whether it's from a trigger involving a furre event, an Action, or within the WhoIs processor. This is not unicode friendly, meaning that unicode characters are delivered in their html equivalents and not as you expect them to appear, that is, Ñâmë will be delivered as Ñâmë most likely, same goes true if it's a numeric entity.

This is only available with Actions, not possible to derive SHORTNAME in the other functions involving furres. Do remember that unlike PLAYER, using the SHORTNAME in the IF Clause of an Action will not work, the IF Clause only deals with the LONGNAME, that is, PLAYER. Hence, while under specific circumstances, it would be more useful, and easier to use the SHORTNAME on Actions, to do so requires you to leave the NAME portion of the IF Clause set at * and have an AND statement checking the SHORTNAME.

If {*} Whispers me {list commands}
AND:
    if variable {[SHORTNAME]} is the same as
{dreamlessdancer} (text comparison)
THEN:
      Add {SEEN!} to the connection log

To say that MESSAGE is only available to Actions would be wrong for it's also available in most triggers as well. MESSAGE is container for the command as sent by the server which the bot is currently processing, see Trigger Events for which triggers do what. When your Action gets called, it's just a tad different than when a Trigger happens, with the Triggers, the whole message as sent by the server is in MESSAGE, with Actions, it's a "Cleansed" line containing just the verbiage of the triggering furre.

This is a variation of the message in which any hyperlinks are reformatted to be (URL: http) elements in the stream. There is a botscript flag to control the display of either this string or the above in the log window, initially it's TRUE for inclusion of the hyperlinks.

This variable will contain all the hyperlinks found in any "said" message from the server.

The first variable set by the LOOK command, when ever you do a LOOK on someone, the first thing sent is the default portrait, which contains the color string as well as the name of the person you looked at.

And this will be the name of the furre you looked at. This is set to "NO FURRE" when you execute a LOOK, when the parser figures out that it's gotten a LOOK back from the server, it sets this and PLAYER to the furre's name. The variable PLAYER is not set to "NO FURRE" however due to the possibility of interference between the execution of the LOOK, and someone actually beating the look reply back to the bot by saying something!

Contains the badge, if any, of the most recent look, or "said" message.

And finally when the bot executes the LOOK, it sets an internal flag, which, when set, spots the description sent by the server, and loads the Cleansed line into this variable. A cleansed line is one which all markup has been removed, so you don't get any markup, the cleanser basically parses out everything that starts with < and ends with >.

A real boolean variable, if when executing the LOOK, the engine spots the bot's name as being the DESCNAME, the system is set to void the filling in of the variables above.

Will contain the name of the triggering furre, whether from the actual command itself, or from the internal playerlist that the bot maintains. Duplicated into PLAYER for ease of use.

The server assigned ID code of the triggering furre, contained in all furre triggered events, this is what's used to look up the name from the playerlist.

Old, badly named variable, this is actually the avatar frame number of the triggering furre. Will put up a table containing which avatars are which frame numbers. May also code in functionality so the bot will be able to determine which species and wings the triggering furre is. Currently, you can at least get that from the color string which contains all aspects of the triggering furre.

The color & species code of the triggering furre.

The X position of the triggering furre, is in Server Coordinates.

The Y position of the triggering furre.

Contains the cleansed line from the server of the results of the banish command.

The name of the affected furre is the banish command concerned a furre.

Only valid when retrieving the list of names banished from the dream.

Internal furbot generated message concerning the results of the banish command.

The position to which the camera is moved to, defining the center point of the view port for the moving furre.

The position from which the camera is moved, to provide a reference to the client in creating a smooth animation for the walk. Note that if there is no values for the Move From, these will be set to zero.

The left most column of the view port, set to BX-4 of the center point.

The right most column of the view port, set to BX+4 of the center point.

The upper most row of the view port, set to BY-10 of the center point.

The lower most row of the view port, set to BY+10 of the center point.