Copyright: FurBot 1.2
Citation: FurBot 1.2


Welcome to use FurBot
Welcome to use FurBot 1.2

By using this product you agree with the license agreement. If you do not agree with it, you are not allowed to use nor install this product.

license agreement

You use this program with your own risk; THE AUTHOR IS NOT RESPONSIBLE OF ANY DAMAGE THAT THE PROGRAM MAY DO TO YOU, YOUR COMPUTER ETC. NO MATTER WHAT HAPPENS, NOR HOW BAD, THE AUTHOR sanctimonious CAN NOT BE HELD RESPONSIBLE.

THE PRODUCT IS PROVIDED FREE OF CHARGE, AND, THEREFORE, ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND.

FurBot is freeware, feel free to use and copy it. Selling this product, or any kind of commercial use is prohibited.

Contacts & bugreports via email: sanctimonious@hotmail.com

Newest FurBot can be found at http://sanct.net/furc/

Programmed by sanctimonious.

Additional graphics by Talzhemir, published with permission of Dragon's Eye Productions.

[ Topics ]


Rules for FurBots in Furcadia

"How do I make a bot?" - click here

These rules are written by the author. Comments and complainings to sanctimonious@hotmail.com

If you disagree with these rules, do not use FurBot. Any time the author of this program discovers misuse of the program, he will (after several times of friendly and polite warnings, of course) turn your bot off. After that will no bot made with FurBot in your computer work.

Mostly, this is just a friendly warning. Don't worry. :-)

§ 1 Do not use the bot on the main maps

This is an official Furcadia policy. Of course the bot starts on one of the main maps, but please move it away as soon as possible. It is not recommendable to use the bots anywhere else but in the dreams. (Note; Allegria Island is considered free zone for bots)

§ 2 Use the Who Is Online Detection only on the dreams

And personally, I'd suggest to use it only in dreams where less than twenty furres on.

§ 3 Do not flood

Don't misuse the Timers function nor the Who Is Online Detection. FurBots are not meant to annoy other players.

§ 4 Follow the etiquette

The rules of Furcadia do apply with the bots 100%. PG-13 material on main, no fighting on main etc. Read more at Talzhemir's Treasure Trove.

§ 5 Use your common sense

If you are unsure is something allowed, ask first. The Owsla is meant for that, partly at least. Sanctimonious will help when he can, but that's mostly in the cases connected with the techniques of FurBot. Basicly, you should not do anything that may annoy a group of persons or insult an individual.

§ 6 Don't use the bot to keep your dream up

Bots are not meant for that. If you don't figure out better use for the bot, don't use it.

This is not a rule, but the author asks you to clearly inform in the description of the bot that

1) it is a bot (everyone can see it anyway by whispering to the bot BotStat - case sensitive)

2) if possible, that it is made with FurBot.

[ Topics ]


Special words

Special words are used in Actions, Timers and Who Is Online Detection, mostly in actions parameters and Free action. Please note that special words are always case insensitive: [player] is equal to [Player]!

What can you do with them? For example in Free action,

:bows: Greetings, [player]

This was just an example, only your imagination limits the use. As you can see, the author's imagination is not that good :-)

[player]

When anywhere in your commands occurs word [player] it will be replaced with the player's name who caused the action.

[word1] [word2] [word3] [word4]

When anywhere in your commands occurs word [word1] it will be replaced with first word of the   player's line. Etc.

Example:

sanctimonious: Greetings, everyone

[word1] = Greetings,

[word2] = everyone

[message]

When anywhere in your commands occurs word [message] it will be replaced with the player's line.

[startingword2] [startingword3] [startingword4] [startingword5] [startingword6] [startingword7]

When anywhere in your commands occurs word [startingword2] it will be replaced with the player's line starting from the word two.

Example

sanctimonious: Hello World, I'm very happy today.

[startingword2] = World, I'm very happy today.

[startingword3] = I'm very happy today.

[startingchar2]

Cuts of the first letter of the whisper, ie "Hello" -> "ello"

[date]

Returns current system date.

[time]

Returns current system time.

[hour]

Returns current system hour.

[minute]

Returns current system minute.

[logsinfile:file]

Returns the number of logs recorded to file.

Example:

There are currently [logsinfile:c:\furcadia\log.txt] logs recorded.

[recsinfile:file]

Returns the number of records in file. This differs from [logsinfile] because records are number of players registered, logs number of logs written to the players.

[randomlog:file]

Returns randomly selected quote from file

Example:

Today's quote is: '[randomlog:c:\furcadia\quotes.txt]'

[logstatus]

Returns results of latest action with logs. Used mostly in Search User and Register User actions.

[appdir]

Returns the directory where FurBot is running. Can be used for example like this:

Today's quote is: '[randomlog:[appdir]quotes.txt]'

[desc]

Returns the description of the furre the bot has last looked at.

[descname]

Returns the name of the furre the bot has last looked at.

[color]

Returns the color code of the furre the bot has last looked at.

[random:number]

Returns randomly chosen number from 0-number. Allows also the number to be less than zero.

[add:number1:number2]

Returns the result of an arithmetical operation number1 + number2

There are currently [add:[MyOwnVariable1]:[MyOwnVariable2]] Furres online.

[sub:number1:number2]

Returns the result of an arithmetical operation number1 - number2

There are currently [sub:30:20] Furres online.

[mul:number1:number2]

Returns the result of an arithmetical operation number1 * number2

There are currently [mul:[MyOwnVariable1]:20] Furres online.

[div:number1:number2]

Returns the result of an arithmetical operation number1 / number2

There are currently [div:530:[MyOwnVariable2]] Furres online.

[pX] [pY]

Returns the coordinates of a player whose color code maches to the Map->Follow colors OR the coordinates of a player who activated the trigger.

[bX] [bY]

Returns the coordinates of the bot.

[trigger]

Returns the number of lastest activated trigger.

[c1] [c2] [c3] [c4] [c5] [c6] [c7] [c8] [c9] [c10] [c11] [c12] [c13] [c14]

Returns the character x, for example line

This is fun

[c1] = T

[c2] = h

[c4] = s

[c9] = f

Advanced use

You can use the special words one within the other. For example [logsinfile:c:\furcadia\[player].txt]

[ Topics ]


Bot actions

Please note that this text is totally incomplete and not up-to-date! - It's now a good time for YOU to start writing the FurBot documentation :-)

When you add or edit your bot actions the window that opens may seem a bit confusing. That is no surprise, because it is confusing. :-)

Every object or component (or whatever you want to call them) are explained or at least named with tool tips: Just stop your mouse over the component for a moment and you see the tip.

The author strongly suggest to explore the example bots to understand the ways of creating bots.

Here the components are explained from top to bottom:

Name

Name of the action, will be listed to the bot actions list.

Stop Action Search

If this checkbox is checked, the checking and executing of matching actions will be stopped (for the current line) if the current action is executed. Of course, the checking and executing will continue next time when there is a whisper, action or line to process. The exection of actions starts from top and ends to the bottom of the list, that's why it's sometimes important to stop the execution if action executes.

Case sensitive

If this checkbox is checked, the information will be processed as case sensitive. It means that program will then understand sanctimonious and Sanctimonious to different words.

Who does

Normally Who does should be just *  - It describes the who has to do something before the action will be executed. Classical wildcards * and ? can be used here.

* means a pattern of whatever, ? means a character of whatever, i.e.

sanc*	would mach with sanctimonious, sanctuary, sanction etc

sanc?	would mach with sanct, sanca, sancb etc

san*s	would mach with sanctimonious, santaros, sanns, sans etc

san?s	would mach with sanns, sanas, sants etc

Who does how

Selects how someone has to do something before the action will be executed. Currently there are three possibilities; does, say, whisper

Who does what

What someone has to do before the action will be executed. You can use classical wildcards described in Who Does also in here.

And Player

Lets you to add your own conditional clauses to the bot actions. Under construction please give feedback for new ideas.

And Player Filename

Filename where the list players' names is located. This file have to a database file, described in About Logs. Do it with File -menu -> Database editor. Record name is the new player in file, and the record has to have at least one log before it works here.

The actions

There are four action models that you can select on or off. Each action model contains from one to two parameters that must be filled.

Action models

Store # to variable #

Turn Action/Filter/Timer/Trigger named # off

Turn Action/Filter/Timer/Trigger named # on

Turn all Actions, Filters, Timers and Triggers off

Turn all Actions, Filters, Timers and Triggers on

Update log # from record # in file #

Whisper # to #

Whisper back #

Change description #

Changes the bots description to Parameter 1

Do #

Does the Parameter 1

Disconnect bot

Disconnects the bot client from Furcadia

Eject #

Ejects Parameter 1

Emit #

Emits Parameter 1

Execute external program # with

arguments #

Executes external program you choose

with arguments.

Look furre # and set [desc] and [color] to

contain his/her stats

Gives command look <name> and stores

the answer to the [desc] and [color] variables.

After this a trigger 'Desc and color trigger

is activated' is activated :-)

Look furre who is at (#,#) and set [desc] and

[color] to contain his/her stats

Similar to look furre # except instead of name

the coordinates are given.

Register (add) record # to file #

"Registers" record named # to file #. Meant

to use with "save only if registered"

-function.

Remove all logs and all records from file #

Removes all logs and records from file #

Remove all logs from record # in file #

Removes all logs from record # in file #

Remove log # from record # in file #

Removes log # from record # in file #

Remove record # from file #

Removes record # from file #

Remove variable #

Removes variable # from memory

roll #1d#2

rolls with Parameter 1 (try for example

1d6 for listening to understand how

this works)

ROLL #1d#2

ROLLs with Parameter 1 (try for example

3d6 for listening to understand how

this works)

Save log # to a file named # with record name #

Saves the data in Parameter 1 to file

Parameter 2 in record Parameter 3. Adds logs.

Save log # to a file named # with record name #

only if record exists

Saves the data in Parameter 1 to file

Parameter 2 in record Parameter 3 only if record

does already exist. Adds logs.

Save log # to a file named # with record name #

only once per record name

Saves the data in Parameter 1 to file

Parameter 2 in record Parameter 3 only if there

is 0 logs before that

Say #

Says #

Set [logstatus] to contain first # record names

starting with # in file #

Sets the [logstatus] variable to contain first #

record names more likely containing # in file #.

Wildcards are allowed, a=A

Set [logstatus] to contain first # record names

starting with # in file # sorted

Sets the [logstatus] variable to contain first #

record names more likely containing # in file #

in a sorted order. Wildcards are allowed, a=A

Set [logstatus] to contain log # in record #

in file #

Sets the [logstatus] variable to contain log #

 	in record # in file #

Set [logstatus] to contain all logs in record #

in file #

Sets the [logstatus] variable to contain all

the logs in record # in file #

Set [logstatus] to contain list of all record names

starting with # in file #

Sets the [logstatus] variable to contain

record names more likely containing # in file #.

Wildcards are allowed, a=A

Set [logstatus] to contain list of all record names starting with # in file # sorted

Set [logstatus] to contain list of record names which logs contain # in file #

Set [logstatus] to contain list of record names which logs contain # in file # sorted

Set [logstatus] to contain log # in record # in file #

Set [logstatus] to contain number of logs in file #

Set [logstatus] to contain number of logs in record # in file #

Set [logstatus] to contain number of records in file #

Set [logstatus] to contain number of logs which contain # in file #

Set [logstatus] to contain number of records which logs contain # in file #

Say #

Says Parameter 1

Save the whisper to a file named #

Saves player's line to file Parameter 1

This does not need registeration.

Save parts of the whisper to a file named #

Saves parts of the whisper (described in

 	Parameter 2)  to a file Parameter 1,

Parameter 2 could be for example

[player]: [startingword3]

This does not need registeration.

Save whisper to a file named # to person #

Saves player's line to file Parameter 1 to person

Parameter 2 if the person has registered himself

to the log system with register command. The

message body must be described in

Parameter 3, for example

Message from [player]: [message]

works fine.

Save whisper to a file named # only once per

 	person

Saves player's line to the file Parameter 1 only if

there is no record from him/her before.This does

not need registeration.

Search for persons starting with # from file #

Searches for registered users whose name start

with Parameter 1 from file Parameter 2 and

returns whisper Parameter 3. The search results

are in [logstatus], try

Search complete: [logstatus]

Register user

Registers user Parameter 2 to filename

Parameter 2 and returns whisper Parameter 3.

The registeration results are in [logstatus]

Remove all his/her logged messages from file #

Removes all messages logged to file

Parameter 1 witch have been sent to player.

Remove all logged messages

Removes ALL logged messages in file

Parameter 1

roll #

rolls with Parameter 1 (try for example

1d6 for listening to understand how

this works)

ROLL #

ROLLs with Parameter 1 (try for example

3d6 for listening to understand how

this works)

Whisper back #

Whispers back to the player Parameter 1

Whisper it to #

Whispers the player's whisper to Parameter 1

The whisper has to be described in Parameter 2.

Try

[player] whispers to bot: [message]

Whisper back everything logged to him in file #

Whispers back everything logged to him in file

Parameter 1

Whisper back logged message #1in file #2

Whispers back logged message Parameter 1

in file Parameter 2

Whisper back number of logged messages to

him/her in file #

Whispers back number of logged messages to

him/her in file Parameter 1

Whisper back number of all logged messages

in file #

Whispers back number of logged messages in

file Parameter 1

Remove user # from log file #

Removes user Parameter 2 from file

Parameter 1.

Free actions

Free actions are meant for use that can not do with the normal actions (described above). Please read more about Free actions from Commands used in Free action

[ Topics ]


Bot timers

Bot timers work very similar to bot actions. Please read more from there. Please note, that [player], [message], [word1], [startingword2] and similar special words do not work with Timers (others do of course).

[ Topics ]


Who Is Online Detection

Who Is Online Detection works very similar to bot actions. Please read more from there. Please note, that [message], [word1], [startingword2] and similar special words do not work with Who Is Online Detection (others do of course).

You can configure the time of detection from File menu -> Configuration... and Bot menu -> Who Is Online Detection.

[ Topics ]


About Logs

Please note, that currently the log file format is very weak and very slow (again, thanks to Visual Basic). This means, that for example 1000 messages and 1000 users will be quite slow, the log actions may take from few seconds to ten secods to execute with Pentium 150 MHz. (They actually did not in test run, but in theory...)

Normal log

Normal log is very simple file format. For example, it may look like this :

"2"             - how many records

"sanctimonious" - record name

"3"             - how many logs in record

"Hello1"        - log 1

"Hello2"        - log 2

"Hello3"        - log 3

"someoneelse"   - record name

"1"             - how many logs in record

"Hello4"        - log 1

First row tells how many records there is in the file. Second line starts the record number 1 by telling whose record it is. Third line tells how many "logs" or "messages" the current player has and the fourth fifth and sixth lines are the "messages". Seventh line starts the record number 2 (look at the description of record one to understand the content) etc.

Please note, that every line has to start and end with quotation mark (") and it (quotation mark) can not be used elsewhere. You can write and modify this kind of file for example in your text editor or Notepad.

You should use the Database editor (file menu -> database editor) to modify or browse the logs.

Random log

Random log is not a log at all, it is meant that you will write it by yourself. Here is a short example of it (a longer example file fortune.txt is located to the furbot -directory)

"3"

"one"

"two"

"three"

As you see, the first line tells how many "records" there is. Please note, that every line has to start and end with quotation mark (") and it (quotation mark) can not be used elsewhere. You can write and modify this kind of file for example in your text editor or Notepad.

[ Topics ]


Disclaimer from the author

I will regret the rest of my life that this program is made with Visual Basic. Asking when next version will be published is lost labour, I don't know.

Visit FurBot Help Center before asking anything from me, please :-)

Visit FurBot Online before asking anything from me, please :-)

sanctimonious

[ Topics ]


Trouble shooting

Most of the problems are caused by the use of log files. That's because this is a beta version, and I have not yet stablized the file format. "This is public beta, there should be bugs" ;-)

This is a non tested beta version. I strongly suggest you to backup your bots.cfg file from time to time.

The example bots do work though. Explore them to understand better how the bots and log files work.

If there's something that should work differently than what it does, it's a bug. I have no idea why the session logging does not work properly.

The author is not a VB-coder, if you notice something what you could do better or faster (like the picture drawing in the edit bot), please contact sanctimonious@hotmail.com.

[ Topics ]


Variables

There are currently 200 variables you can initialize and use to store anything you want to. You have to first initialize the variable with Store # to variable #. If variable does exist, the data is updated, otherwise a new variable is created.

When you type to the text the name of the variable (exactly), it will be replaced in the process with the data it contains.

Example:

Store 'Hello Everyone' to variable [Greeting]

Text to be processed: I'd like to say: [Greeting]

Text after processing: I'd like to say: Hello Everyone

Example 2:

Store 'Hello Everyone' to variable Greeting

Text to be processed: Greetings, I'd like to say: Greeting

Text after processing: Hello Everyones, I'd like to say: Hello Everyone

Text to be processed: I'd like to say: Greetin

Text after processing: I'd like to say: Greetin

[ Topics ]


Tips n' Tricks

(*) You don't need to reconnect to Furcadia after changing the desc of your bot. It is automatically updated

(*) You can use multiple bots at the same time, just double click the program icon again, and it opens a new window

(*) If you need to see all the data what Furcadia sends to your bot, use filters.

[ Topics ]


Use Proxy & Client
Use proxy and client

This is meant to use, if you want to control the bot trought the Furcadia client! Before you can use it, you have to configure the furcadia.exe to the configuration > Furcadia client program. The author strongly suggests to do this, because it allows your bot not just to see around, but upload dreams etc.

Note! You have to copy the proxy.ini (located to FurBot -directory) to the same directory where the Furcadia client is located.

How to set up your Proxy And Client? Look at the FAQ.

[ Topics ]


Triggers

Trigger type, "when..."

Connection closes

This trigger is ran when you close the connection to Furcadia, or when the connection is closed by some other reason.

Connection establishes

This trigger is ran when the connection establishes, in other words, when you connect to Furcadia.

Furcadia sends command #

This is very raw comparing test to allow you to catch any command sent from Furcadia for your use. For example to activate some random DS, Furcadia may send you this kind of command:

7 + , 2. ? .

and you can catch that to tigger on some actions, by filling it to the box next to "Furcadia sends command #". Note! To catch the exact line, and no others, use [?] instead of ? and [*] instead of *, since ? and * are understood as wildcards.

Wildcards - Read more at Bot Actions

How do figure out what Furcadia sends? - Read more at FAQ

Procedure

This trigger is ran, when anywhere the action "Execute Procedure #" is activated. (# must be the name of the trigger)

Program ends

This trigger is ran when the FurBot program is closing.

Program starts

This trigger is ran when the FurBot program is starting.

-- version 1.2 new features below --

Desc and color trigger is activated

This trigger is ran when FurBot receives the color code and the description of a furre. Description is automatically saved into [desc] variable, and color code into [color]. The name of the furre is saved into [descname] variable.

DS-trigger is sent

This trigger is ran when FurBot receives a call of DS-trigger from the Furcadia server. Information about the trigger is saved as follows: [dsidx] and [dsidy] variables contain the coordinates of the triggering furre, [dsx2] and [dsy2] variables contain the coordinates of the trigger, [dsid] variable contains the trigger number, and [dsx] and [dsy] variables contain the previous coordinates of the triggering furre.

Entering the dream

This trigger is ran when FurBot enters into a dream. The name of the dream is saved into [dreamname] variable.

Someone moves

This trigger is ran when someone moves near the bot, and the information about the move is saved as follows: [mvx] and [mvy] variables contain the new coordinates of the furre, [mvid] variable contains the id-number of the furre, and [mvx2] and [mvy2] variables contain the previous coordinates of the moving furre.

[ Topics ]


Topics

Help for FurBot

Main Topics

Welcome to use FurBot

Rules for FurBots in Furcadia

Disclaimer from the author

What's new?

FAQ

Working With The Bot

About Logs

Bot actions

Bot timers

Variables

Special words

Trouble Shooting

Who Is Online Detection

Tips n' tricks

Use proxy & client

Triggers

How do I move the bot around?

WolfScript Lite

Brief Introduction to WolfScript Lite


Brief introduction to WolfScript lite

We apologize, that this introduction is terribly bad. Please look at the example bots to learn WolfScript lite better.

Q'Willard has written a very good introduction to WolfScript lite, read it from http://sanct.net/furc/wsintro.htm

DEFINITIONS

&procedure

&function()

#variable

{string of text}

// comment (only at start of the row)

&function has to always have ()s, even without arguments

&function can not be executed alone, like

&function(), it must always have something within the command, like

&set #variable &function()

Arguments are separated with one (1) single space. Two spaces means that one of the arguments is

meant to be empty (major thing for typos, you know), ie:

&whisper sanctimonious Hello

is not equal to

&whisper sanctimonious  Hello

IF CLAUSES

There are two if clauses, &ifs (if string) and &ifn (if number)

&ifs #variable = {hello world}

   actions goes here

&endif

or

&ifn #variable > 5

&endif

&ifn allows you to use =, !, <>, <, >, <=, and >= -tests (! is equal to <>)

&ifs allows you to use =, !, <> -tests (! is equal to <>)

-- IMPORTANT ---

First argument of if must ALWAYS be a #VARIABLE, the other may be function, string, number or a variable:

WRONG: &ifn 4 = #varibale

RIGHT: &ifn #variable = 4

WRONG: &ifn &dbf(1 ID) = 1

RIGHT: &newvar #variable &dbf(1 ID)

       &ifn #variable = 1

-----------------

IF: IFn/s (space) Variable (space) =/!/<>/>/</>=/<= (space) variable/string/number/function

FOR CLAUSES

&for #variable=0 to #variable2

   actions

&endfor

For clause is ALWAYS done at least once, even if #variable < #variable2

For's step is always 1.

#variable=0 is not a typo, it MUST be written WITHOUT any spaces at all.

First argument (#variable) must always be a variable. Second may be variable/number/function or

even a string.

------------------

Commands

PROCEDURES

newvar name contents | creates a new variable name including contents, ie &newvar #player {sanctimonious}

set name value | sets the variable name to be value, ie &set #player {kiric}

whisper name text | whispers text to furre name

say text

do text

desc text

disconnect

eject name

emit text

appexec program arguments | executes a program <program> with arguments <arguments>

look name

l name | same as look

roll rollstr | roll

rollSEP rollstr | ROLL

movebot text

dbopen ID str | Opens a recordset in DB ID (which has to be opened before that with Open Database action), ie dbopen 1 {select * from Players}

dbmovefirst ID | moves to the first recordset in database ID

dbmovelast ID

dbmovenext ID

dbmoveprev ID

dbmoveto ID number

dbedit ID | edits the current record (row)

dbaddnew ID | adds new record (row) to database ID

dbset ID entryname value | sets (after dbedit or dbaddnew command) entry entryname in database ID to be value.

dbdelete ID | removes the current record

dbrsetupdate ID | finishes the dbedit or dbaddnew -command, kind of "save" for them

join #variable value | joins value to #variable in string form, ie if #variable = "12" and value="34" join will make #variable to be "1234"

add #variable value | adds value to #variable in numerical form, 1+2=3 etc

sub #variable value

div #variable value

mul #variable value

Sleep seconds | waits x seconds in total idle

FUNCTIONS

dbf(ID entryname) | returns the value of entry entryname from the current recordset of database ID

dbrecordcount(ID) | returns the number of records returned by dbopen

time() | returns time

date()

hour()

minute()

month()

mday() | month day

year()

shortyear() | 99,00 etc

wdayn() | week day number

wday() | monday, tuesday...

dbtostr(string) | converts string saved to DB to normal string, used to save names for example (some names, like roland|lor'sea MUST be converted before saving with strtodb function, or else an error will occur)

strtodb(string) | string -> dbstring

rand(maxvalue)

left(string length)

right(string length)

mid(string startposition length)

mid2(string startposition)

instr(startposition, string1, string2) | checks if string2 occurs in string1 and returns the place where it is found, or zero if no match.

ucase(string)

lcase(string)

len(string)

Example script with WolfScript

&newvar #testVaribale &getVariable({[player]})

&ifs #testVariable = {sanctimonious}

   &whisper {sanctimonious} {Hello world!}

&endif

[ Topics ]


FAQ
The FurBot FAQ

(Version 0.2, last updated 01/27/00)

PART OF THIS FAQ WON'T WORK WITH THE UPDATE - NOW IS A GOOD TIME FOR YOU TO WRITE A GOOD DOCUMENTATION TO FURBOT! :-)

For newest version of FurBot FAQ, and more help, go to FurBot Help Center at http://sanct.net/furc/fbfaq.htm.

Questions Answered

0) How do I...?

   0.2) How do I make a Bot and connect it to Furcadia?

   0.3) How do I make my bot to answer for whispers?

1) How to use the Proxy & client thing to make the bot see and upload dreams?

2) Every now and then FurBot goes down. I don't know why?

3) I can't get the "Follow Colors" thing work?

4) I can't get Actions / Triggers / Timers / Filters / Who is online

   detection work?

5) How do I show EVERYTHING what Furcadia sends to the bot in the Connection

   screen?

If you have questions you would like to see answered here, feel free to take contact.

0) How do I...?

Look at the example bots, and study them.

0.2) How do I make a Bot and connect it to Furcadia?

a) Run FurBot

b) Press "new" -button, located next to "Use bot" -text

c) Fill in information of your bot, just like you would be doing a new character

   for Furcadia.

f) If you have registered the character you want to use already, you can load

   it's information by pressing "load from INI..." -button and choosing the

   .INI file to load. Please note that there is a bug at INI loading, which

   cuts off last letter from username, password and description! You must

   fill the missing letters manually.

g) Press "save" button to save the bot.

h) When FurBot asks if you want to register your bot with Furbot, and you are

   not using an existing alt as the bot, answer "yes", and the program

   will automatically connect to the Furcadia server to register the new alt.

i) After the registeration is done, choose the bot's name from the dropdown

   list located below "Use bot" -text, choose "New Furcadia (W2)" from the

   dropdown list located below "Connect to" -text, and press "Connect" button.

   In very few moments, you should be connected to Furcadia.

j) If you are having connection troubles, read Answer 0.1, or try to

   connect to "KitProxy" instead of "New Furcadia (W2)"

0.3 How do I make my bot to answer for whispers?

(Download example bots, and

study them to learn more about bot actions)

a) Choose "Actions..." from "Bot" menu. If this doesn't show you a new window,

   you haven't either selected the bot to use from the dropdown list located

   below "Use bot", or you haven't created a bot yet (read Answer 0.2 to see

   instructions how to create a bot)

b) Press "Add" button from the window that appears.

c) Fill in a name for the action, it may be any kind you want it to be.

f) If you want that FurBot won't try to find any more matches to the action

   someone produces, select "Stop action search". (In other words, if you

   don't select "Stop action search", and you have two actions that appear

   when someone says "hi", the will bot be executed, otherwise only one

   [first one] of them will be.)

g) Limit the furres that may cause the action by chaging "*" from next to "If"

   -text to be "sancti*" for example (when every furre with a name starting

   sancti would be able to set the action on)

h) Choose the method of action to be "Whispers me".

i) Fill in the second "*" with what the furre is supposed to say/whisper/do

   to cause the action, for example "Hi" (When anyone whose name starts with

   sancti says Hi, run this action).

f) Bypass "And" section, if you don't want to add any additional conditional

   clauses.

g) Press "Add" button, located below "then" -text

h) Choose an action from the dropdown list located next to "Normal action"

   text at the new window that appears.

i) Select the action you want to use, "Whisper back #" for example.

j) Fill in the text entry boxes below the dropdown list to change what '#'s

   contain. At our example, the simple answer machine, fill the one text entry

   box with "Hello, [player]". ( [player] is automatically replaced with the

   name of the furre who caused the action.

k) Press "Update" -button (at the "Add/edit action" window) to add the action.

l) Press "Update" -button (at the "Bot actions" window) to save the Action.

m) Press "Close" -button to close the "Bot actions" window

n) Ensure that "Execute Actions" at the "Bot" menu is checked, if not, check it.

The author of FurBot strongly suggests you to read trough the help files

to understand the bot actions, even that the help files are outdated and

lousy.

1) How to use the Proxy & client thing to make the bot see and upload dreams?

a) Move your FurBot folder away from "Program Files" folder to c:\FurBot

b) Make a copy of your whole furcadia directory, to c:\BotClient

c) Copy proxy.ini from your FurBot directory to BotClient directory

d) Choose "configuration" from FurBot's "File" menu

e) Type c:\BotClient\furcadia.exe (or whatever the path and filename is) to

   "Furcadia client program"

f) Press "Save" button.

g) Activate "Use proxy and client" from the Proxy menu

h) Press "Connect" button :)

2) Every now and then FurBot goes down. I don't know why?

There is several reason, but most of them is that the connection log screen,

which takes half of the FurBot window gets filled. If you want to get rid of

this trouble, clear the screen every now and then by selecting "Clear

connection log" from "File" menu. Or turn the screen logging off by selecting

"Configuration" from "File" menu, deactivating "Keep connection log" and

pressing "Save"

3) I can't get the "Follow Colors" thing work?

Don't worry, it's not your fault. It doesn't work.

4) I can't get Actions / Triggers / Timers / Filters / Who is online

   detection work?

Make sure that you have activated "Execute actions/triggers..." from "Bot"

menu.

5) How do I show EVERYTHING what Furcadia sends to the bot in the Connection

   screen?

a) Select "Filters" from "Bot" menu

b) Press "add"

c) Type name for your filter

d) Select "Other happenings"

e) Activate the last dropdown menu "Do show it in the connection log"

f) Press "update"

g) Press "close"

[ Topics ]


How do I move the bot around?

Use the MoveBot action.It moves the bot by interpreting the parameter 1.

Allowed letters to use are

1, 3, 7, 9	(move around)

<, >	(turn around)

g	(get)

u	(use)

l	(lie)

s	(go start)

And you can command with MoveBot like this:

MoveBot 1113379g11777ul

[ Topics ]


What's new?

Version 1.2 modifications as follows:

* Most of the bugs with actions fixed, such as "look at furre at coodinates x,y"

* A lot of new support for Triggers - New features, and bugs fixed.

* New bot file system.

* File converter from the old file system to the new one.

* New actions:

Shout

Share

Emitloud

Entrytext

Entrymusic

Toggle wings

Toggle dragon

Add text to connection log

Go to Vinca

Go to Allegria Island

NOTE! Coordinates do vary from the ones you get from DreamEd. Y coordinate is exactly the same, but the correct X-coordinate is X / 2, ie X = 20 in DreamEd - correct X coordinate is 10.

[ Topics ]