Menu Items

File menu

Open Macros
Loads a .udf file. See here for information on UDF's.

Configuration (.INI)

Save Configuration
Saves the current configuration to the .INI file. This will save the default bot name, user ID, privilege password, port and universe, the Options menu settings, and the positions and sizes of the various MB windows. See the comments in the .ini file itself for a list of all the parameters that it can control.

Auto save configuration on close
When checked, causes the current configuration to be saved to the .INI file automatically when MB quits.

Behavior

Open Behaviors...
Merge Behaviors...
Save Behaviors!
Save Behaviors As...
Loads, Merges or Saves the Behaviors table. These menu items have the same effect as the Load, Merge and Save buttons on the Behaviors form.

Action Buttons

Open Action Buttons...
Merge Action Buttons...
Save Action Buttons!
Save Action Buttons As...
Loads, Merges or Saves the user-defined buttons on the Actions page.

Variable List

Open Var List...
Merge Var List...
Save Var List!
Save Var List As...
Clear Var List!
Loads, Merges, Saves or Clears the list of variables in memory. Variables are created by various script commands which are explained in the Actions section.

Auto Save Var List on close
When checked, causes variables in memory to automatically be saved to a file when MB quits, and automatically loaded when MB starts.

Save All!
Saves Behavior Table, Action Buttons, Variable List immediately. The configuration is not saved by this button.

Logging

Log File Name
This allows you to specify a log file. Note that you also have to select "Log Chat" and/or "Log Events" for any messages to be saved in the log that you specify here.

Note: Both event and chat messages are always displayed in the log window. The Log Chat and Log Events items (see below) only control whether those messages are also printed in the log file.

Log Chat
Toggle logging of chat messages on/off.

Log Events
Toggle logging of event messages on/off.

Log Time of each message
Adds the date and time to each message in the log window.

Use VRT
Use VRT rather than the computer's local time for time displayed in the log.

Exit
Exit the program normally.

Options menu

Behavior Table Active
When this is unchecked, the Behavior Table is deactivated.

Handlers...
Handlers are functions in an AW SDK program (like Magsbot) that are called by the SDK when certain events occur. The program then responds to those events within the handler functions. The handler dialog in Magsbot allows you to deactivate certain handlers that you don't expect to be needing in a particular Magsbot application, so that Magsbot won't be receiving and taking time to respond to irrelevant events. For instance, if you're sure that you don't want Magsbot to respond to any chat text, you could deactivate the HearChat handler. Note however that you should be certain that you know what you're doing when you deactivate a handler! The handlers dialog is provided mainly for unusual situations where you might expect a very large number of irrelevant events that might slow down Magsbot to an unacceptable level. For most situations, you shouldn't need to use the handlers dialog.

The selections on the handlers dialog are saved in the .INI file when you click File/Configuration/Save configuration.

In Magbot 7.0 (AW 4.1), handlers can be set globally (for all instances) or individually. Check the "Selected Instance Only" box to set handlers for a single instance.

Note the Create callback handler cannot be activated...Magsbot doesn't use the callback version of the aw_create function. (I admit, I can't get it to work. Does it work??)

Include Tilt, Roll in Build
When this is checked, then tilt and roll values will be expected in propdump files and will be used with the BUILD and LOAD commands.
(Removed, see ObjList Format.)

Track Nearby Avatar Movements
While this is checked, nearby avatar information is continually updated and saved and can be accessed using the @avz, @avx, @avy, @avyaw, @avtype and @avgesture functions. These functions are necessary since the value of AW Attributes such as AVATAR_X, AVATAR_Y, etc.may not always be available during all Events. Instead, you can use the "last known location" information maintained by avatar tracking. However, avatar tracking may not be practical (or necessary) in a situation where many avatars (50+) are nearby; therefore, tracking can be turned off using this menu item or the TRACKING Action.

Check Avatar Zone
When this is checked, ZONEENTER and ZONEEXIT events are generated when an avatar enters or leaves a zone.

Object List Format
Allows you to select the format to use when building from an obj list, or when saving an object list as a propdump.  If this is set incorrectly for the format of the object list, the objects may not be created properly. The @olversion function returns a 2, 3 or 4 depending on how this menu item is set.

Note: when building from a propdump file, Magsbot 7.0 will automatically use the correct version of the propdump according to what is specified in the first line of the propdump file. The ObjList Format menu item only affects the use of object lists.

Fonts
So you say you really hate Comic Sans MS?  Well I think it's cute! :P  But okay, okay, I've added this option to allow you to change most of the fonts used by Magsbot.

Monitor Bar Visible
While this is checked, a bar at the bottom of the window becomes visible that indicates some information about what Magsbot is doing. The first (blue) light indicates when MBot is waiting for AW server messages (events), the second (yellow) light indicates when MBot is processing messages and the third (red) light indicates certain error conditions (useful mainly to me for debugging). The bars to the right of the three lights indicate the Events and Actions that Magsbot has yet to process. Events are messages that Magsbot receives from the world server; Actions in the queue are commands that you entered using an ENQUEUE command.
 

Beep on error
While this is checked, MB will sound a beep when an error occurs. (Note that the beep might be preempted by another program like the AW Browser!)

Verbose Event Messages
While this is checked, extra event messages are reported.

Connection

Auto Connect
While this is checked, MB will automatically create a bot instance on startup. When this is not checked, you will need to click on menu item Connection/New Instance to create an initial instance.

Auto Enter
While this is checked, the bot will automatically enter the world given in the Location Panel when a bot instance is created. When not checked, you will need to click on menu item Connection/Enter World, or the Set button on the Location Panel to enter a world.

Auto Appear
While this is checked, the bot will automatically go to the coordinates given on the Location Panel when entering a world. When not checked, you will need to click on the Set button on the Location Panel to appear at specific coordinates in a world.

Restart on Disconnect
(New in 6.8.10.) When this is checked, a disconnection will cause the bot instance to be destroyed and recreated using the same name, location and other information. It's not really necessary, it's a holdover from earlier versions where recovery from disconnections was always done that way, but auto-recovery itself was option. In 6.8.10 and higher, Magsbot always tries to reconnect automatically, but this menu item determines the method. Usually best left turned off. (Removed in 7.10. Bot will now always try to recover unless ejected or unwelcome.)

Global Mode
Determines the default setting for the Global Mode option on the New Instance dialog. (Note that you cannot change from normal to global mode once the bot has entered a world, except by leaving the world and re-entering in global mode.)

Auto Connect to Bot Bone Server
While this is checked, MB will automatically connect to Imatowns' Bot Bone server on startup. When not checked, you will need to click on menu item Connection/Log in to Bot Bone Server  before sending Bot Bone telegrams.

Show in Log...

Show Messages for Active Instance Only
While this is checked, only events and chat messages directed at the active instance (i.e., the bot instance showing on the control panel) will appear in the log window. When not checked, all events and chat for each bot instance will be shown in the log window, prefaced by the instance ID in brackets. (When multiple instances are running, the latter format of log message will always appear in the log file, if a log file is opened, regardless of the setting of this menu item.)

Show Nearby Avatar Movements
While this is checked, nearby avatar movements will be reported in the log window.

Show Avatars Arrivaling & Departing
While this is checked, AVATARADD and AVATARDELETE events will be reported in the log window.

Show Bot Movements
While this is checked, the bot's movements will be reported in the log window.

Show Build Events
While this is checked, OBJECTADD, OBJECTDELETE and OBJECTCHANGE events will be reported in the log window. NOTE: build events won't be reported until after you perform a survey in that area! It's the way the SDK works, don't blame me. :) Note: this is not true of instances in global mode (new in Magsbot version 3.0).

Show Clicks
While this is checked, AVATARCLICK, OBJECTCLICK and OBJECTSELECT events will be reported in the log window.

Show BotGrams
While this is checked, BOTGRAM events will be reported in the log window.

Show URL Events
While this is checked, URL and URLCLICK events will be reported in the log window.

Show Name for Session
While this is checked, the name of the avatar is shown in the log instead of the session number, when the ANNOUNCE_ command is used.

Show Name for Instance
While this is checked, the name of the avatar is shown in the log instead of the instance number, in each log message.

Client/Server

Show Client/Server Messages
When this is checked, messages received from a client application are displayed in the log window. (See the Server Mode item in the Connection menu.)

Broadcast Log to Clients
When this checked, everything that appears in the log window will also be broadcast to all connected client applications (such as AWScoreboard). (See the Clients item in the Actions menu, and the Server Mode item in the Connection menu.)

Restrict to Listed Clients
When this is checked, only clients in the valid client list are allowed to connect to Magsbot running in server mode. (See the Clients item in the Actions menu, and the Server Mode item in the Connection menu.) If this is unchecked, then any clients are allowed to connect, and clients not deliberately added to the list will be shown in blue.

Auto Start Server
When this is checked, Magsbot automatically enters server mode when it starts up.

Connection menu

New Instance...

Create a new bot instance. A dialog will appear allowing you to enter bot name, citizen ID, privilege password, and the port and address to use. (Default values will already be present in the dialog so you don't need to reenter them each time.) Note that this allows you to run different bot instances in different universes, or even with different owners! You may also choose whether or not you want the new instance to automatically enter and/or automatically appear in the world and at the location given in the Location Panel when started; these settings override the default Auto Enter/Auto Appear settings on the Option/Connection menu, for the new instance only.

New in Magsbot version 3.0:
You can also check the Global Mode box to have the bot enter the world in global mode. In global mode, the bot will be able to detect the chat and movements of all avatars in the world, however distant from the bot. However, global mode will only apply if the bot's owner is a caretaker in that world.

New Admin Instance...
New in version 6.6.3, you can create an administrative instance that can connect to your world server, if you are a caretaker.

Admin instances can use the special admin commands to control worlds on your server.

Abort Login
Cancels a New Instance request.

Enter World
Causes the active instance to enter the world shown on the Location Panel, if not already in a world.

Delete Instance!
Destroy the active bot instance. (This can also be done from the Instance List window.)

Delete All Instances!
Destroy all bot instances.

Set Default for new instances...
Allows you to specify the default information (name, ID, password, port and universe for new instances.

Log in to Bot Bone Server
Log out of to Bot Bone Server
Log in or out from Imatowns' Bot Bone Server in order to send telegrams.

Server Mode
Turns on Server Mode. While in server mode, TCP/IP client applications can connect to Magsbot to receive and send messages. The server can send messages to clients using the SVRSEND or SVRBROADCAST commands. Also see the various server-related items in the Options menu, above.

Client Mode
Allows Magsbot to connect to another Magsbot session running in Server Mode. You can send messages to the server using the CLIENTSEND command.

Instance

This menu item toggles the appearance of the Instance List window. The Instance List shows the ID, name, port, universe, world and state of visibility for each instance. To designate an instance as the active instance, simply select it on the Instance List. The active instance is the one affected by the control panel.

As of version 1.7, the instance window also shows a status light to the left of the ID, indicating the state of that instance's connection. An unlit yellow indicates that the instance is waiting to connect to the AW server, lit yellow means the instance is connected and waiting to enter the world, and a green light indicates that the connection is completed. A red light shows when the instance is disconnected from the server, and a gray unlit light means that reconnection has failed. In the last case (failed reconnection), the instance must be deleted and restarted.

As of version 2.0, the owner of the bot instance is also displayed.

You can also set a note for each instance using the INSTNOTE command. The $instnote function retrieves the note. (A handy use of the instance note is to find instances that have been temporarily disconnected and had their instance handle change. For example, if you are using a weather bot, you can set its note to read "WeatherBot", and if it gets disconnected, your script can find the new instance handle by searching the list for the instance that has "WeatherBot" for it's note.)

In 3.0, the Global Mode state of the instance is also shown on the Instance List window.

Chat menu

Toggle Nearby List
Toggles the window that shows the names of nearby avatars. Note that each bot instance has its own Nearby List and no Nearby List can be shown when there are no instances existing.When the "Nearby" window is visible, then any text you enter on the Chat page will be whispered to individuals on the list whose names are selected. When whispering is active, the text you enter in the chat box will be blue. Closing the "Nearby" form turns off whispering, although minimizing it does not.

In Magsbot 3.0, you can also use the Nearby List to select individuals whom you want to receive Announcements.

Certain commands (specifically TAG, SHOWTAGS, and TAGALL) can also cause checkboxes or "tags" to appear next to the names in the Nearby List. These checkboxes have no effect on whispering or anything else, except as you choose to use them with the TAG et al commands and functions.

Nearby List, tag visible and checked.

Clear Log Window
Clears all text from the log window.

Mute Log
When this is checked, no messages whatsoever appear in the log window. Not recommended, I put this here for debugging purposes mainly.

Scroll Lock
When this is checked, the chat log window won't scroll automatically when new chat appears at the bottom. You must have menu item Advanced/Anti-Flicker checked for scroll lock to be available, and the chat window should not have the focus (i.e., don't click it) when scroll lock is on, or the scroll lock will be deactivated.  (Note this feature is a little quirky: clicking on the log window after turning on scroll lock will effectively turn it off again.)

Behavior menu

This causes the Behavior Table window to appear.

View menu

Variables...

Toggles the appearance of the Variable List window. This window shows you the entire list of Global Variables in memory. You can Edit or Delete the highlighted variable by clicking the appropriate buttons.

Database...
Toggles the database window. Here you can directly view the currently opened database, change the provider or connect strings, select a table in the current database, or enter an SQL statement. See here for general information about database use in Magsbot. Click the Set button after making changes to put the changes into effect. The navigation bar at the top of the window allows you to move through the database.

Navigation buttons on Database window:

First : Moves database pointer to the first record in the current table.

Prior : Moves database pointer to the previous record in the current table.

Next : Moves database pointer to the next record in the current table.

Last : Moves database pointer to the last record in the current table.

Insert : Inserts a new, blank record before the current record, and sets the database into Edit state.

Delete : Deletes the current record and makes the next record the current record.

Edit : Puts the dataset into Edit state so that the current record can be modified.

Post : Writes changes in the current record to the database.

Cancel : Cancels edits to the current record, restores the record display to its condition prior to editing, and turns off Edit states if they are active.

Refresh : Refreshes the buffered data in the associated database.

Avatar Tracking...
Displays a window showing avatar tracking data.

Memory status...
Displays a window showing memory usage.

Terrain Buffer

Buffer...
Toggles the appearance of the Terrain Buffer window. This allows you to see the data in the heights and textures buffers, for the current instance. The grid is read-only. Use the SETHEIGHT_ and SETTEXTURE_ commands to make changes in the buffers.

Flush Terrain Buffer
Flush All Terrain Buffers
When a terrain query is performed, the data from the query is preserved for each bot instance as long as that instance exists, until another terrain query is performed. You can release that data from memory by clicking these menu items. Flush Terrain Buffer frees the memory used for terrain data by the active instance, and Flush All Terrain Buffers frees the terrain data for all instances.

Clients...
Toggles the appearance of the Clients window. Use the Clients window to add the IP's of clients whom you want to allow to connect to Magsbot when it's running in Server Mode. (See the server-related items in the Options menu, and the Server Mode item in the Connection menu.)

Actions menu

Evaluate an expression

This is just a little built-in calculator. It allows you to enter a numeric or string expression for MB to report the result. String expressions must be quoted or be a string function (starting with $, e.g. $botname).You can also use Evaluate to quickly find the value of a global variable or AW SDK Attribute (e.g. you could enter $atr[world_name] or @atr[avatar_y]). The result shows in the white memo box, errors show the yellow memo box below. The arrow button allows you to select conditions, functions or attributes to insert.

Do… (Perform a command)

Allows you to enter an immediate mode command (i.e., an Action) that MB will perform as soon as you click Ok to close the Edit Box that appears. (This is the same Edit Box used for entering Actions in the Behavior Table.)
 

Survey...
The survey dialog, as of version 2.0, lets you begin a survey, specifying all the relevant settings from one dialog. You can also do a survey using the SURVEY command.

Also new in version 2.0 is the capability for each bot instance to run a survey independently. In previous versions, only one survey could be run at a time.

In Magsbot version 7 (AW version 4.1), you set the propdump version number.

Description of Survey dialog elements:

• Status: Describes the survey activity for the active instance.
• Start at: Specifies the coordinates to start the survey at. The default is the bot's own coordinates. You can use the "AW coords" button to enter coordinates in the style used in the AW brower, such as 15n 775e, etc.
• Area: Defines the area of the survey, either Local (everything within 120m of the starting location) or Local 5x5 (a 5 cell wide area, meaning everything within 200m of the starting location) or World (the entire world). You could reduce the area of the survey by using the Conditional expression setting (see below).
• Relative to origin: When the is checked, then the object coordinates returned by the survey will be adjusted relative to the starting position of the survey, as if the starting position were "ground zero." By using this setting, you can rebuild the surveyed objects at another location simply by using the bot's location at the rebuild site as the offset for rebuilding.
• Consider altitude: The starting location for a survey doesn't consider altitude when performing the survey; however, if you wish to survey something and rebuild it at another height, then you would check this box as well as "Relative to origin".
• Conditional expression: This expression is used as a filter to define what surveyed objects will actually be listed. For example, if you only wanted the work of citizen 28777 to be surveyed, you could put @atr[object_owner]=28777 as the condition. If you wanted only tree7m.rwx objects to be surveyed, you could put @eq[$atr[object_model],"tree7m.rwx"]. Or if you only wanted to survey objects with the word "foobar" in the description field, you could put @ipos["foobar",$atr[object_description]] as the conditional expression. Any valid Magsbot numeric expression can be used, so you could combine restrictions using the "and" && or "or" || operators. For instance, to survey only objects that are underground and have "create url" in the action field: @atr[object_y]<0&&@ipos["create url",$atr[object_action]]. The arrow button to the right of the conditional expression text box lets you insert condition and function templates much the same at the "Insert..." buttons on the edit box.
• High speed: In high speed mode, Magsbot's  synch timer  is temporarily set to a timing mode more suitable to performing a survey or terrain query; that is, a long time fetching data from the server, and a relatively short processing interval. When the survey or terrain query completes, the normal synch timing is automatically restored. You might not want to use high speed mode if you expect your bot to be doing a lot of other things at the same time as it is doing the survey or terrain query, since the high-speed survey or terrain query can slow down other processing. Also see Send to Behavior Table, below.
• Send to Behavior Table: When this is checked, survey events (such as QUERY,  CELLOBJECT, SURVEYDONE, etc.) are sent to the Behavior Table for processing. This is necessary only if you want to use any of the Object List buttons on the Survey tab of the Actions panel, such as Log from Survey, Log Objects by Click, Resolve Click Log, Log One Object, etc. (Note however, that the "Log from..." buttons are outmoded in version 6.0a14; see Send To List, below.) If you are doing a survey using the Survey dialog and built-in functionality, then you don't need to send the survey results through the behavior table, and doing so can slow down the survey considerably. So, unchecking the Send to Behavior Table box can greatly speed up the survey. Also see High speed, above. In version 6.0 a14 and greater, the Send to Behavior Table button no longer needs to be checked for most surveys.
• Use Object ID: When this is checked, the object ID will be stored instead of the object number, in CSV format lists. Should not be used for propdump format surveys.
  
• Propdump format: If checked, the survey items are listed in the familiar format used in propdumps. If unchecked, a long form is used. The long form can be useful if you are looking for one particular object in an area, and have set the conditional expression (see above) so that you only expect that one object to be listed. (Replaced in version 6.0 a14 by Format, see below.)
• Format: Selects the survey output format. Detailed is useful if you are looking for a few particular objects in an area, and have set the conditional expression (see above) so that you only expect those objects to be listed. Propdump is the familiar format used in propdumps. CSV (comma separated values) or "comma-delimited" is the form used by Magsbot object logs. Note: the CSV format is mandatory when sending output to a list. (New in version 6.0 a14.)(Replaced in version 7.0  by Version, see below.)
• Version: set the propdump version to use, when saving in propdump format. The versions roughly correspond to AW versions. Version 2 is the oldest supported version. Version 3 adds tilt and roll,and Version 4 supports special objects (Zone objects, Particle emitters, Movers and Cameras).
• Send to List: allows you to send survey output to an object list in memory, either a Global list $objlog, or a VList that is automatically created when the survey is performed. If the vlist option is selected, the handle to the list will be stored in the global variable @survey:instance, where instance is the instance number of the bot that did the survey. You are responsible for freeing the vlist when you're done with it, either by using the FREEVLIST command, or the "Free Selected VLists" button on the VList tab of the Actions panel. This method is intended to replace the use of the "Log from Survey" and "Log from World Survey" buttons on the Survey tab of the Actions panel. The new method is fast since the data is processed and sent to the list within the program itself, rather than being sent to the Behavior Table. (New in version 6.0 a14.)
• Clear list: when Send to List is set to Global or Vlist and Clear List is checked, the list will be freed when the survey begins; otherwise the new survey will be appended to the existing list. Note that if you survey the same area, the new survey items will have the same object numbers and overwrite the existing list; thus the list may not get any larger even if you are appending to it.(New in version 6.0 a14.)
• Survey to separate log file: When this is checked, the results of the survey are sent to the file specified below. Otherwise the results appear in the log/chat window. NOTE: In version 2.0 the survey results will NOT appear in the chat window when "Survey to separate log file" is checked!
• Append: When this is checked, the survey results are appended to the specified file. Otherwise the file is overwritten.
• Filename: The name of the file that the survey results will be sent to.
• Save a new default settings: The settings currently in the survey dialog are saved to be used as the default settings for new surveys.

Note that you can also perform survey operations using object lists, with "Log from Survey", "Log objects by click", "Log one object" and various other buttons on the Actions panel. See here for details.

Seed

Allows you to manually create an object. A dialog will appear allowing you to enter the information for the object, with the default coordinates (the bot's coordinates) already entered. The AW coords button lets you enter coordinates in the AW Browser format, if you're uncomfortable with SDK-style coordinates. New in version 3.0: Note that the Tilt and Roll values are disabled unless you have Propdump version 2 checked on the Options menu.
 

Terrain...
The terrain dialog, new in version 3.0, lets you begin a terrain query, specifying all the relevant settings from one dialog. You can also do a terrain query using the QUERYTERRAIN command.

Description of Terrain dialog elements:

• Status: Describes the terrain query activity for the active instance.
• Start at: Specifies the coordinates to start the survey at. The default is the bot's own coordinates. You can use the "AW coords" button to enter coordinates in the style used in the AW brower, such as 15n 775e, etc.
• High speed: In high speed mode, Magsbot's synch timer  is temporarily set to a timing mode more suitable to performing a survey or terrain query; that is, a long time fetching data from the server, and a relatively short processing interval. When the survey or terrain query completes, the normal synch timing is automatically restored. You might not want to use high speed mode if you expect your bot to be doing a lot of other things at the same time as it is doing the survey or terrain query, since the high-speed survey or terrain query can slow down other processing. Also see Send to Behavior Table, below.
• Send to Behavior Table: When this is checked (the default), terrain events (such as TERRAINDATA and TERRAINDONE, etc.) are sent to the Behavior Table for processing. Unchecking the Send to Behavior Table box can greatly speed up the query. Also see High speed, above.
• Send to separate log file: When this is checked, the results of the survey are sent to the file specified below. Otherwise the results appear in the log/chat window. The terrain data will NOT appear in the chat window when "Send to separate log file" is checked!
• Append: When this is checked, the terrain data is appended to the specified file. Otherwise the file is overwritten.
• Filename: The name of the file that the terrain data will be sent to.

Save a new default settings: The settings currently in the terrain dialog are saved to be used as the default settings for new terrain querys.

Queues

Empty Event Queue
Empy Action Queue
If either the Event or Action queue gets overfull or seems to be jammed, you can use these menu items to "flush" the contents of a queue, removing all pending Events or Actions without processing them.

Important!
Break Loop!
If an Action that you've entered in the Behavior Table causes MB to get stuck in an infinite loop, clicking this will terminate the loop. (Pressing F12 will have the same effect.)

Reset from Break Loop!
After clicking Break Loop! (above) you sometimes might need to click this to reset the "break loop" flag . You can also use Shift-F12.
 

Debug Messages
Toggles some extra debug messages.

Anti-Flicker
Prevents flickering on the log window that occurs when the log window becomes full of text and has to delete lines from the top. I made this optional because the anti-flicker is not yet entirely perfected.

Supress "Not Yet" Errors
Version 4.1 of the AW SDK causes an error message to occur if messages are sent to the server too quickly. When this is checked, these errors will not be shown in Magsbot.

Allow irregular object numbers
Allows non-integer numbers or strings to be used in object lists for the SAVEOBJLIST and GETOBJLIST commands.

Performance

Dynamic synch
Toggles "dynamic synch", which adjusts the event processing and server polling phases automatically according to how may events are pending in the queue. Normally keep this checked.

Floodproof
Toggles "floodproofing", causing the bot to ignore chat and clicks on avatars or objects that occur in too rapid succession, if from the same source. You can also set this using the FLOODPROOF command. The time limit is set using the FLOODLIMIT command, which specifies the minimum interval between events; if the same event from the same person occurs in less time than the specified limit, then the event is ignored. The time limit is in milliseconds. (Prior to version 7.0, the limit was in Delphi time units, where 1=one day. Thus a time limit of one fifth of a second, for example, would be 1/24/60/60/5 or about .00000231481.) Also see Filter AvatarChange, below.

Filter AvatarChange
This can also be set using the AVCHANGEFILTER command. It's similar to the floodproofing concept (see above), except that it only affects AVATARCHANGE events (whereas Floodproofing affects chat and clicks). The limit for filtering AVATARCHANGE events is set using the AVCHANGELIMIT command.

Event Queuing

Clocktick
When checked, causes CLOCKTICK events to be queued the same as other events, rather than interrupting actions already in progress. Keep this checked.

Survey
When checked, survey data is send through the events queue as with earlier versions of Magsbot. Sending the survey data through the events queue may slightly speed up the time it takes the bot to do the actual survey, but it also creates a long waiting period after the survey is done, before the data is actually processed. This is true even if you aren't sending the data to the behavior table. (You can tell when the survey data is completely processed by looking at the monitor bar, Ctrl-M.) When "Use Queue in Survey" is not checked, the survey itself may take slightly longer, but there is no wait after the survey is done, and the entire process (surveying and processing) will be somewhat faster.

Other
All other events are queued or unqueued depending on this setting. This is purely experimental and unchecking it is not recommended.

Threads
Settings that affect how threads function.  (Mainly for my own debugging purposes.)

APM in loops
When checked, Application.ProcessMessages is called within empty WHILE and FOR loops.

APM in Wait
When checked, Application.ProcessMessages is called within THREADWAIT.

APM in Synchronize
When checked, Application.ProcessMessages is called for each Synchronize function that performs an action within the main program thread.

Pack Lists
Removes empty space from the global variable list, to recover some memory.

Kickstart Main Timer
Restarts the main program timer. (You'll probably never need to do this.)

Clear button click buffer
Button clicks are queued so that they won't interrupt actions already in progress. This clears the buffer. (You'll probably never need to do this.)

Clear object results list
When an object is created or changed by the bot, an OBJECTRESULT event is generated. Within the OBJECTRESULT event, the AW SDK only provides the object number of the new or changed object, so Magsbot stores the object information when the object is created, and then puts that information in the attribute list within OBJECTRESULT.  Under some circumstances this information might not be properly freed from memory, so the "Clear object results list" menu item is provided to do this. However you don't usually need to worry about this.

Clear objects result list
When the SDK sends an OBJECTRESULT event, the only AW attribute it sends is OBJECT_NUMBER. Since it is useful to have other information about the object that was created or deleted, Magsbot stores all the object attributes (OBJECT_X, OBJECT_Y, OBJECT_Z, OBJECT_YAW, OBJECT_ROLL, OBJECT_TILT, OBJECT_MODEL, OBJECT_DESCRIPTION, OBJECT_ACTION, OBJECT_OWNER, OBJECT_BUILD_TIMESTAMP) temporarily when an @objectadd or @objectdelete, etc. function is called, and makes that information available within the context of the corresponding OBJECTRESULT event. Immediately after OBJECTRESULT the data is normally freed, but if an error condition causes the data to remain in memory, the "Clear objects result list" menu item frees that memory. If you've been doing a lot of building and memory seems low, you can try this.

Terrain File Format
Lets you change the format of "raw" terrain data files. I take no responsibility for the results if you mess with it. :D

Exit!
Under rare circumstances, an error may interrupt the normal shut down procedure, preventing Magsbot from closing. If this happens, you can use this menu item to force Magsbot to close, ignoring any errors and discarding all data. Note you should use this ONLY if Magsbot can't be closed normally, because your data, including any changes to the custom buttons or behavior table since the last save, will be lost!

Window menu

Show All
Hide All
Chat
Location
Actions
Telegram
Announce
These menu items allow you to toggle the visibility of the panels (Chat, Location, Actions, Telegram and Announce) of the main window. If you drag a panel of the main window to make it become a separate window and then click on the "x" in the upper right to make it disappear, you can make that panel reappear by clicking its name on this menu.

Show/Hide Action Tabs...
Causes a dialog to appear that allows you to check or uncheck the names of Action Panel tabs (categories) to make them visible or invisible. When invisible, the buttons on an Action panel tab can still be called using the CLICKBTN and FTN commands.

Find Action Tab
Lets you search for an Action panel tab (category) by name. A text box appears, and as you type into it, the tab with a name that matches will be selected. Press Enter or Escape to close the text box.

Find Button
Lets you search for an Action button. Enter a button name or part of a name into the text box that appears and press Enter, and a list of tabs containing buttons with matching names will be displayed.

Stay On Top
When checked, Magsbot will remain on top of other program windows.

System Tray
When clicked, the main Magsbot window will be minimized to the system tray. (Subwindows such as the Behavior Table or Database dialog will remain on the desktop.)

Help menu

Calls this help file. If you'd rather have the help files on your hard drive instead of accessing them via the Internet, download them into the MB folder and add this to your .ini file:

[Help]
URL=mh_contents.htm