HamBot FAQ Copyright © 1998 by Prototech, Inc. Written by Nelson Crowle AKA HamFon
Edited and parts re-written by John Shipley AKA Talisan, Copyright © 2008 by Darkestdestiny.com
  1. How do I start HamBot?
  2. How do I create my first Bot?
  3. How do I move my Bot?
  4. Why can't my Bot go near Ground Zero?
  5. How do I change the name of my Bot?
  6. Can I have my Bot log in as a citizen or a tourist?
  7. How do I start another Bot at the same time?

How do I start HamBot?

  1. Download the latest copy of Hambot from www.myawo.com to your PC.
  2. Create a folder to install/unzip Hambot into. An example might be c:\hambot
  3. Unzip the archive you downloaded into the folder you created.
  4. Run Hambot by double clicking on hambot.exe or by right clicking once and selecting Run
  5. Log in to HamBot using your AW citizen number and priviledge password
  6. HamBot will login to the universe and determine what abilities are allowed
  7. To do more, you will need to run a script from within Hambot that will allow your bots to login to world servers

How do I create my first Bot?

How do I move my Bot?

  1. Start by making a copy of botworldbeta.txt and giving it a name of your choice.
      An example might be:
    • copy botworldbeta.txt botworldmine.txt
  2. Edit your copied script file and locate the beta world and change it to the world you want the script to be used in
  3. Start Hambot, start AW, then teleport to the world you selected in the script. Start the script.
  4. From the HamBot menu, select Bot/Teleport
  5. Enter new coordinates or a different world in the dialog - you can also change the avatar or gesture here

Why can't my Bot go near Ground Zero?

HamBot does not allow you to take Bots within 200 meters (20 dekameters or degrees) of the restricted radius of a world, unless you have Public Speaker or Eminent Domain rights. The reason for this is that world owners can keep Bots away from their Ground Zero entry point, unless the Bot owner is specifically allowed by the world owner. Bots can be annoying or obnoxious, and by enforcing this rule, HamBot attempts to limit the negative impact of Bots in "public" areas. As an example, the "restricted radius" (which is the distance from Ground Zero where building is not allowed by normal citizens or tourists) for Alpha World is 80 meters. Therefore, HamBot will not allow Bots within 200+80 = 280 meters (28 dekameters - i.e., 28N 28W) or Alpha World's Ground Zero.

How do I change the name of my Bot?


HamBot comes with several example scripts ending with the .txt entension. Open one, and look for the StartBot command. This command has several parameters separated by slashes. The first parameter is the bot number(0..19). The second parameter is the Bot name. Change this to the name you like without over writing the parameters after it. When you run that script, the bot will use that name for that bot numbers instance.

Can I have my Bot log in as a citizen or a tourist?


No. With the introduction of Activeworlds v2.1, the protocol of messages between the browser(or HamBot) and the world and universe servers is now encrypted. HamBot no longer supports "Native" mode which allowed you to send telegrams, or have contact lists, or log in as a tourist or a citizen. Now, your only option is to log in as a [BotName] type of avatar

How do I start another Bot at the same time?


HamBot supports up to twenty simultaneous Bots(although ActiveWorlds.com currently limits you to three simultaneous bots on one citizen number). They may be run in the same world, in different worlds, or even in different galaxies. HamBot script commands work on the "current selected" Bot - that way you don't have to specify which Bot you want to change each time you provide a script command. To start a second Bot, copy a block of script code from the first Bot, including all from the StartBot command, thru all the lines that tell the Bot where to move, etc. Then paste it, change the 0 to a 1 in the StartBot =0/Bot//beta line, and change the WaitFor=0 to WaitFor=1, and add a SelectBot=1 after the WaitFor. The SelectBot line causes Bot #1 to be the "current selected" Bot until another SelectBot line occurs. So all script commands (NS, SAY, etc.) will be directed to this Bot. You can get both Bots talking by interspersing SelectBot in your script, e.g.,
SelectBot=1
Say Hi, I'm Bot 1
SelectBot=0
Say Hi, I'm Bot 0
(etc)