There is quite a few things directly implemented on the main interface for the bot which are needed when you're running the bot clientless, like moving the bot, picking up and using things, and some specialized buttons which are user programmable. While I should not need to explain them, here goes. From left to right, top to bottom.

• Move NW
• Move NE
• Move SW
• Move SE
• Turn Counter Clockwise, left
• Turn Clockwise, right
• Get Item
• Use Item
• Sit / Lie / Stand
• Who the map

There, that's out the way, now for the rest  of them. For historical reasons, the Go Vinca and Allegria Isle buttons remain, but then I add 8 more buttons to which you can assign your own button text, and attach a proceedure to them which will execute when the button is clicked.

The user programmable buttons are new to Furbot, they are set by the command:

Set user button {N} with the label {LABEL} to execute the proceedure {PROCEEDURE} with the optional tool tip of {TOOLTIP}.  

So for a more extensive example now that they're working:

TTrigger Name: Start Up
Program starts
No Additional Conditions.
THEN:
Set user button {0} to run procedure {Enable Triggers}
with the caption of {Start DS}
and tooltip of {Enable DS Trigger Details}

Trigger Name: Enable Triggers
Procedure
   No Additional Conditions.
THEN:
      Store {TRUE} to variable {[triggers]}
      Set user button {0} to run procedure {Disable Triggers}
with the caption of {Stop DS}
and tooltip of {Disable DS Trigger Details}

Trigger Name: Disable Triggers
Procedure
   No Additional Conditions.
THEN:
      Store {FALSE} to variable {[triggers]}
      Set user button {0} to run procedure {Enable Triggers}
with the caption of {Start DS}
and tooltip of {Enable DS Trigger Details}

Most likely you will want to set them at program start, but there's no reason to dynamically change them when the program is connected to the server either. These are born from the fact that I got a few bots which I would turn things on and off via a procedure, but had to bring up the Debug Execute dialog, selecting the Trigger I wanted to execute, then pressing trigger. That function is still available in the Debug Execute, but this is so you can avoid the need to use a menu, select the trigger from the dropdown, trigger it, select another, trigger that one as well, and so forth.

The scrollbar needs to be considered a control for if you "lift" the scroll button off the bottom of the scrollbar, you get the scrollback buffer. The textbuffer is limited internally to about 200 lines, don't hold me fast to that, it may vary slightly depending on how much is going on at the time. The scrollback buffer remains active, holding the contents that it captured at the time it was activated until you reseat the button to the bottom of the scrollbar. During the time that the buffer is active, text which is received by the bot is still visible at the bottom where the split window shows the received buffer. And you can still use the send buffer to send text to the server. Please note that to avoid problems at this point, using the cursor keys in the scrollback buffer does not  update the scroll button. So it is possible to go to the top of the buffer with the home key, and the button will remain at the bottom. However, the button will affect the text in the scrollback when you move it, just don't expect it to be accurate unless you bring it all the way up to the top.

The Send to Furcadia is designed to be a multiline control as well, as you type it will resize up to about 5 lines of text, at which point you can use the scrollbar there to see what the heck it is that requires so much text, or use the cursor keys to navigate the control. Pressing Enter will send the text to the server, and pressing Escape will clear it. CTRL+Z does not undo the erasing of the control with Escape. You can send emotes and whispers, along with commands (like `which) just like you would with the client. For historical reasons, the # is still used to indicate a command so #which and `which are equivalent.

And then there's another frame called "Connection". At this point, all it contains is the full path to the botscript file that you're using, in addition to the Connect button. Once connected, the caption changes to Disconnect, and if you have Autoconnect enabled in a botscript, it will display Abort # where # is the number of seconds until the bot executes the connect command.