Bot control is things which need to be done internally to the bot, they generally don't affect files, furres, or things of that nature. Do note that executing an external program is not a show stopper, bot will merrily continue executing commands after attempting to launch the program. Of all the commands, only this one would be considered something that affects something external to the bot.

Add {#0} to the connection log

0 Text to add Adds a message to the display window, handy for debugging a script.

Decrease variable {#0} by {#1} (numerical)

0 Variable Name 1 How much to decrease Does a subtraction on the named variable. If variable contained TEXT before the math, it will contain a number after the command has executed, with the result being Parameter 1. Note that it is possible to ADD with this, just subtract a negative offset.

Disconnect bot

0 Takes no parameters This needs explaining?

Execute external program {#0} with arguments {#1}

0 Program FileName and path 1 Arguments Runs an external program named in Parameter 0, with Parameter 1 Arguments. The function does NOT wait for the program to return, after starting the external program, the script continues to the next statement.

Execute Procedure {#0}

0 Procedure Name Executes a Procedure by name. Procedures reside in Triggers. You can currently only have one call into a procedure.

Increase variable {#0} by {#1} (numerical)

0 Variable Name 1 How much to increase Does an addition on the named variable. If variable contained TEXT before the math, it will contain a number after the command has executed, with the result being Parameter 1. Note that it is possible to SUBTRACT with this, just add a negative offset.

Remove variable {#0}

0 Name of the variable Weird technical function to "delete" a variable from the master list. After deletion, references to the variable will return "" or 0, depending on how you access the variable.

Set countdown timer {#0} to execute in {#1} seconds

0 Timer name, must be unique 1 Seconds till execution Sets the countdown timer named in {0} to go off in the number of seconds specified by parameter{1}. Note that timers now are able to have a resolution of 1/10 of a second, so setting a timer to go off in 0.1 seconds is legit, however, lag issues may find your timer triggering before the current script finishes executing. The engine will hunt through all the timers for the first matching timer function which is a countdown timer by the name specified, this will not tamper with regular timers or time of day timers. Setting a countdown timer to Zero seconds should disable it and prevent it from firing.

Set user button {#0} to run procedure {#1} with the caption of {#2} and tooltip of {#3}

0 0 Button number (0-7) 1 1 Procedure name 2 2 Button Caption (Avoid Wrapping) 3 3 Tooltip (Optional) Set user button {#0} to run procedure {#1} with the caption of {#2} and tooltip of {#3}

Special Store {#0} to Variable {#1}

0 Data to store 1 Variable Name Specialized variable creation / store routine. This runs the "FixText" routine on both the "variable" and the date you wish to store in the resulting variable. Ex: Special Store {[player]} to Variable {[colors]} Results: Variable named to whatever [colors] contained, with the contents being whatever was in [player].

Special Store 2 {#0} to Variable {#1}

0 Data to store 1 Variable Name Another specialized variable creation / store routine. This one runs "FixText" on the data twice before storing the results into the variable, which is created in "Raw" mode, what you enter is what you will end up with.

Store {#0} to variable {#1}

0 What to store 1 Name of the variable What would be considered a "Normal" variable creation / storage routine. Does a single "FixText" on the data, then stores it into the variable, which is created in "Raw" mode.

Turn Action/Timer/Trigger named {#0} off

0 Action/Timer/Trigger Name Turns off the named element (deactivates), very indiscriminate, will check all four sections for the name, and if found, disables it.

Turn Action/Timer/Trigger named {#0} on

0 Action/Timer/Trigger Name Turns on the named element (activates), very indiscriminate, will check all four sections for the name, and if found, enables it.

Turn all Actions, Timers and Triggers off

0 Takes no parameters Effectively will shut the bot down. You will notice that the WhoIs does not get affected by this action, so it is possible to use that to re-enable the bot.

Turn all Actions, Timers and Triggers on

0 Takes no parameters Turns everything on. Interesting note about timers, they will continue to "run" when disabled, they just will not "execute". So your timers will pick up where ever they happen to be in the timing cycle.