Gammon Forum

Quote:
------ world.Execute processing starts here ------>

c. The "command execution depth" is incremented by one. If it exceeds the limit (currently 20) the execution terminates with an error status (which can be detected in a script).

d. The start of the command is checked for the "scripting prefix" - default is the "/" character (this is only done if scripting is active). If it is detected the result of the line(s) are passed to the script engine for execution. Then the "command execution depth" is decremented again, and processing is complete.

***

e. Otherwise the command is now broken into individual lines at the command-stack character, excepting that two command stack characters in a row are replaced with a single command stack character. For example, if the command stack character is ";" and assuming \n represents a new line, this might happen:

command: south ; east ; say I go;; I eat; drink \n sigh
replacement: south \n east \n say I go; I eat\n drink \n sigh

Note that you can put multiple lines into a command by simply using the newline character (eg. typing Ctrl+Enter). Using the command stack character is simply another way of achieving the same result.

f. The resulting command (with command-stack characters replaced by newlines) is then broken into individual lines. Note that there is always considered to be at least one line, so entering a blank command will result in one newline being sent to the MUD. Each line is then processed in the following way ...

----- Start of processing for each individual command line ----->

g. Each plugin (if any) is given a chance to evaluate the command line ("OnPluginCommand" script subroutine). If it chooses to reject that line, then processing for that line terminates.

h. If the line is totally empty a blank line is sent to the world.

i. Otherwise, if the speedwalk prefix applies to this line, then the speedwalk is evaluated and sent to the world.

j. If no speedwalk prefix was detected the line is scanned for global aliases. If one matches the action specified is done (ie. the "send" text is sent to the "send to" location). If "keep evaluating" was set for that alias then further aliases will be scanned (for the same text, not the output from the previous alias).

k. This process is repeated for the aliases in all plugins.

l. If no alias was found at all, then the text is sent to the world "as is" - note this is the normal case where something you type is just an ordinary command for the MUD.

m. If one or more aliases were found, the alias scripts are now executed. Note that the scripts are executed after the alias "send" text has been sent.

<----- End of processing for each individual command line -----
!!!