@database "AmiMUD" @master "amigamud.doc" @$VER: AmiMUD.guide 2.1 (1.12.96) @author "Gabriele Greco" @wordwrap @(c) 1996 Gabriele Greco @index MAIN @node MAIN "AmiMUD manual" AmiMUD 2.10 by Gabriele Greco ---------------------------- @{" Introduction " link intro} @{" Distribution " link dist} @{" Requirements " link req} @{" Installation " link inst} @{" Features " link features} @{" Configuration " link config} @{" Using the program " link use} @{" ARexx interface " link arexx} (REGISTERED) @{" Registration " link reg} @{" Author " link author} @{" Thanks " link thanx} @{" To Do " link todo} @{" History " link hist} @endnode @node arexx "AmiMUD ARexx interface" AmiMUD ARexx interface ---------------------- Please note that the Arexx port is available only in the registered version of AmiMUD. Actually the command's arguments have to be included in double quotes if they contains spaces, single quotes if the case is important and may be passed also without quote if the case is not important. Examples: am_connect medievia.com 4000 The arguments that AmiMUD will receive will be: MEDIEVIA.COM, 4000 and this will work because addresses aren't case sensitive. am_addtrigger 'you are hungry' 'rem bag\\nget bread bag\\neat bread\\nwear bag\\n' This will not work. The correct use is: am_addtrigger '"you are hungry"' '"rem bag\\nget bread bag\\neat bread\\nwear bag\\n"' This because the arexx interpreter will send you, are, hungry, rem, bag\\nget.... as different arguments. You can also use: 'am_addtrigger "you are hungry" "rem bag\\nget bread bag\\neat bread\\nwear bag\\n"' Also this syntax is correct. You can use single quotes when you need to use only a word. Look at the example script for more examples. These are the commands actually supported by AmiMUD, if you need a particular command for a script send me a mail, and (if useful) I'll implement it. @{" am_addmacro " link am_addmacro } @{" am_addtrigger " link am_addtrigger} @{" am_connect " link am_connect} @{" am_disconnect " link am_disconnect} @{" am_echo " link am_echo} @{" am_getscreen " link am_getscreen} @{" am_getvar " link am_getvar} @{" am_log " link am_log} @{" am_quit " link am_quit} @{" am_send " link am_send} @{" am_setvar " link am_setvar} @{" am_waitfor " link am_waitfor} @{" am_waittriggers " link am_waittriggers} See example.amud and example2.amud for more infos. Remeber to use: address 'AmiMUD.1' ...in your arexx script to tell ARexx interpreter to send the commands to amimud! (Obviously you can send the scripts also to AmiMUD.2, .3, .4...) Hint: if you want to assign an hotkey to an ARexx script just insert the #rx command in a macro: macro=myscript hotkey=F3 #rx myscript.amud\\n @endnode @node am_addmacro "AmiMUD ARexx commands" Command: am_addmacro Syntax: am_addmacro NAME/A,MACRO/A,HOTKEY Use --- This command will add a macro to the AmiMUD session you have adressed the command to, like the @{"macro" link macro} configuration keyword. NAME will be the name of the macro, MACRO the text (use double quotes) and HOTKEY the hotkey the macro is assigned to (not required). Example: am_addmacro '"getbag $0"' '"rem bag\\nget $0 bag\\nwear bag\\n"' @endnode @node am_addtrigger "AmiMUD ARexx commands" Command: am_addtrigger Syntax: am_addtrigger TEXT/A,ACTION/A,REXXTRIGGER/S Use --- This command will add a trigger to the amimud session you have addressed the command to, like the @{"trigger" link trigger} configuration keyword. TEXT is the text that active the trigger, ACTION is the action to perform, REXXTRIGGER is a switch to use with the REXXONLY switch of @{"am_waittriggers" link am_waittriggers}. Example: am_addtrigger '"you are hungry"' '"rem bag\\nget bread bag\\neat bread\\nwear bag\\n"' @endnode @node am_connect "AmiMUD ARexx commands" Command: am_connect Syntax: am_connect HOST/A,PORT/N Use --- If not connected this command will let you connect to the specified HOST, PORT will be the port to connect to, it's optional, if not specified the default value is 23. Example: am_connect medievia.com 4000 @endnode @node am_disconnect "AmiMUD ARexx commands" Command: am_disconnect Syntax: am_disconnect Use --- This command will disconnect you from the mud you are connected to. Example: am_disconnect @endnode @node am_echo "AmiMUD ARexx commands" Command: am_echo Syntax: am_echo TEXT/A Use --- This command is very useful for complex script (look at example.amud to see how it's used). It print the TEXT specified to the output window without sending it to the mud. Example: am_echo '"This text will be printed only on the output window!"' @endnode @node am_getscreen "AmiMUD ARexx commands" Command: am_getscreen Syntax: am_getscreen Use --- This command is very useful if you want to know the screenname of AmiMUD. It will return in the ARexx variable screenname the value. Example: am_getscreen say 'AmiMUD is opened on:' screenname @endnode @node am_getvar "AmiMUD ARexx commands" Command: am_getvar Syntax: am_getvar NUMBER/A/N,VARIABLE/A Use --- With this command you will copy the contents of @{"variable" link variables} $NUMBER to the ARexx variable VARIABLE. NUMBER must be 0..9. Example: am_getvar 0 myvar say 'Variable $0 contains:' myvar @endnode @node am_log "AmiMUD ARexx commands" Command: am_log Syntax: am_log LINES/A/N,VARIABLE/A,WAITFOR/K Use --- This command let you put in a variable the contents of the next LINES lines. The contents are stored in a stem, the base variable is the one named VARIABLE. If you use the WAITFOR keyword the log will start from the line after the one where is found, otherwise it will start at the first line received from the mud after the command is performed. Please note that the command will return the control to the script only when it receives the specified number of lines or if amimud is terminated. Please note that if a script is logging already with the command am_log another call to this command will cause an error (the command will return with code 5). Please note that sometimes due to the division in TCP packets a line may be splitted it two parts. Example: am_log 5 BUFFER do i=0 to 4 say "line" i "is" BUFFER.i end @endnode @node am_quit "AmiMUD ARexx commands" Command: am_quit Syntax: am_quit Use --- This command will quit AmiMUD. Example: (from a shell) rx "address 'AmiMUD.1' am_quit" @endnode @node am_send "AmiMUD ARexx commands" Command: am_send Syntax: am_send TEXT/A Use --- This will send the text TEXT to the mud. It can contains also multiple lines use @{"separator" link separator} character to divide them. Example: am_send '"rem bag;get sword bag;wear bag;wield sword"' @endnode @node am_setvar "AmiMUD ARexx commands" Command: am_setvar Syntax: am_setvar NUMBER/A/N,TEXT/A Use --- This command will put TEXT in the @{"variable" link variables} $NUMBER. NUMBER must be 0..9. Example: am_setvar 1 '"Hello world!"' @endnode @node am_waitfor "AmiMUD ARexx commands" Command: am_waitfor Syntax: am_waitfor STRING/A Use --- This command is very useful in scripts. It HANGS the script until the text STRING is received from the mud or via the @{"#send" link sendsym} command. If the text TEXT is found the command will also return the line containing TEXT in the variable LINEBUFFER. If AmiMUD is terminated all waitfor commands will be replied. Example: am_waitfor 'death' say 'Someone is dead, this is the line:' linebuffer @endnode @node am_waittriggers "AmiMUD ARexx commands" Command: am_waittriggers Syntax: am_waittriggers REXXONLY/S Use --- This command will HANG the arexx script until one of the trigger defined is actived by the mud or via the command @{"#send" link sendsym}. AmiMUD will put the actived trigger number in the ARexx variable TRIGGER and the line that actived the trigger in the variable LINEBUFFER. If the REXXONLY switch is specified the command will be satisfacted ONLY if the trigger actived has been defined through the rexx command @{"am_addtrigger" link am_addtrigger} with the switch REXXTRIGGER. This can be useful if you want that your script reacts only to SOME triggers. If AmiMUD is terminated all am_waittriggers commands will be replied. Example: am_waittriggers say 'The trigger actived is N.' TRIGGER ' and the string is ' LINEBUFFER For an example of REXXTRIGGER/REXXONLY look at the example.amud example script. @endnode @node dist Distribution ------------ AmiMUD is shareware, the shareware version may be distributed everywere through internet, bbs, cd-rom, cover disk provided that the archive is distributed in his original form and that the price of the cd-rom/cover disk isn't too high. The shareware version isn't crippled in any way. It opens only a "reminder" requester when you launch the program. Probably future versions may be crippled, I think that the planned arexx port available in the next major upgrade will work only in the registered version of AmiMUD. Starting from 1.10 some features of AmiMUD are only available if you register the program. Actually these features are @{"speedwalking" link speed} and @{"multiple commands on a line" link scommands} @{" How to register " link reg} @endnode @node req "Requirements" Requirements ------------ AmiMUD needs to work: - an Amiga with at least OS 2.0 and 1MB of RAM (some features work only with OS 3.0+). - reqtools.library (included in the archive) - a TCP stack installed and active (tested with Miami, AS225, AmiTCP and MLink) - if the TCP stack is amitcp (<4.3) or miami it requires socket.library (included in the archive) Not required but useful: - the file amimud.prefs to keep all the configuration settings of the program, must be kept in the program directory (also s: is searched for backward compatibility). - KingCON to have a review buffer on the output window. (you can find KCON on aminet util/shell/kingcon13.lha) @endnode @node intro "Introduction" Introduction ------------ AmiMUD is a MUD client. It runs using socket and can be used to play nearly every text-only mud on the internet or on other TCP/IP based networks. I wrote this because I saw that there wasn't any decent MUD client for amiga, since I enjoy myself playing muds and I don't like using term or the amitcp telnet to do that I decide that writing a MUD client was a good Idea :) It was thought for DIKU-type muds because that's the kind of mud I play, but can be used with nearly any type of mud without any problem, obviously some of the features (for instance @{"tickcounter" link tickcounter}) are not useful on some types of mud, but I don't think this is a big problem, if you have suggestions for features you'll like to see in AmiMUD mail @{"me" link author} them. My initial thought was to make it freeware, but I spent many time (and money in phone bills :) ) on it so I decide to make it @{"shareware" link registration}, so if you like it and you use it regularly please register, you will make @{"future improvements" link todo} being possible. @endnode @node features "AmiMUD Features..." These are some of the features of AmiMUD: - Works with any TCP stack (tested with AmiTCP, Miami, IW225, Mlink) - Input and Output on two windows. - Command history buffer on output window. - Possibility to log to file what you do. - Can be opened on Workbench, Public screens or on a custom screen... - ANSI color support (on custom screen). - Macros (with or without arguments) and with hotkeys. - Numeric Keypad walking. - Autologin. - Triggers. - Variables. - Gags. - Highlights. - Aliases. (NEW) - Many internal commands to use in triggers and macros. - Dynamical tick length counter (for DIKU muds). - Nearly all function may be used by menu. - AmiMUD is not a unix porting! - Multiple config capability. - Possibility to edit / use custom palettes. - Very little (60k) and doesn't need fast cpus. - Commodity interface. - Send a file or clipboard to the mud. - Speedwalking. (NEW) (REGISTERED) - ARexx, the most powerful script language in ANY mud client! (NEW) (REGISTERED) - Multiple commands on a line. (NEW) (REGISTERED) - Great configurability. - Graphics board support. - Localization. ...and many other features! @endnode @node inst "Installation" Automatic installation ---------------------- Simply click on the Install_AmiMUD icon in the AmiMUD drawer. Manual installation ------------------- To install amimud simply copy the file AmiMUD (and optionally the icon AmiMUD.info) on your HD (or on a disk). To use all the features of the program you'll need also to copy the file AmiMUD.prefs to the same directory where AmiMUD is located. If it does exists a directory it means that there is an amimud translation in your language, so copy it to locale:catalogs// and then (if you have AmigaOS 2.1+) AmiMUD will be in your favourite language. Then you'll need to edit the prefs file as you like (see @{"Configuration" link config} section for more info) then you can launch the program from WB or CLI. If you don't have already installed reqtools.library and socket.library you'll need to install them: To install reqtools simply copy amimud/libs/reqtools.library to your libs: assignment. Reqtools has also a prefs program, if you want it get the last version of the library from aminet (util/libs/reqtools*). The installation of the socket library is needed only if you are using amitcp. Actually you DON'T need to install socket library if you use AS/I-Net225, Mlink or AmiTCP 4.3+. To install the library follow these steps (please note that if you have already Grapevine or Thor running you have already the socket.library installed): makedir amitcp:libs (if the directory doesn't already exists) copy amimud/libs/socket.library amitcp:libs/ echo >envarc:SOCKETCONFIG "UID=200 GID=200 USER=ggreco DOMAIN=tn.village.it UMASK=022" echo >env:SOCKETCONFIG "UID=200 GID=200 USER=ggreco DOMAIN=tn.village.it UMASK=022" (you have to substitute ggreco and tn.village.it with your login and your domain) assign inet: amitcp: (better if you put this line also in your user-startup) Please note that if you launch the program from CLI you can specify some parameters not (yet) available if launched from WB. See the @{"Program usage" link use} section for more infos... @endnode @node config "Configuration" Configuration ------------- When you launch AmiMUD the program will look for the file amimud.prefs in the directory where the program is located (or in s: for backward compatibility) to found the settings to use. AmiMUD has many configuration parameters, so I suggest you to copy the example configuration file and then edit it to your needs. @{"Configuration keywords" link keywords} @endnode @node keywords "Configuration keywords" Configuration keywords ---------------------- The configuration keywords ARE case sensitive, must be written lowercase and without spaces, tabs or other characters before or after the keyword. Example of correct use: userprompt=name? Examples of WRONG use: userprompt=name? Userprompt=name? userprompt =name? Remember also that you can place comments and blank lines everywhere, but you can't place a comment on the same line of a command. The lines beginning with the character ";" are considered comments. Available keywords: ------------------- General keywords @{" host " link host} @{" port " link port} @{" output " link output} @{" variable " link variable} @{" command " link command} @{" history " link history} @{" crmode " link crmode} @{" verbose " link verbose} @{" speedwalk " link speedwalk} @{" separator " link separator} @{" rx_path " link rx_path} @{" echo_input " link echo_input} @{" globalkeys " link globalkeys} @{" include " link include} @{" max_retries " link max_retries} Autologin keywords @{" user " link user} @{" userprompt " link userprompt} @{" password " link password} @{" passwdprompt " link passwdprompt} @{" afterpasswd " link afterpasswd} @{" relogin " link relogin} Ticks related keywords @{" ticks " link ticks} @{" mark " link mark} @{" tickseconds " link tickseconds} @{" minimum_ticklength " link minimum_tl} @{" prompt " link prompt} @{" beforetick " link beforetick} @{" tickmacro " link tickmacro} @{" aftertick " link aftertick} Screen menagement keywords @{" customscreen " link customscreen} @{" displayid " link displayid} @{" screenwidth " link screenwidth} @{" screenheight " link screenheight} @{" screendepth " link screendepth} @{" screenfont " link screenfont} @{" screenfontsize " link screenfontsize} @{" palette " link palette} @{" input_window_y " link input_window_y} @{" ansi " link ansi} Advanced features @{" alias " link alias} @{" gag " link gag} @{" gagline " link gagline} @{" highlight " link highlight} @{" highline " link highline} @{" macro " link macro} @{" trigger " link trigger} @{" crypt_password " link crypt_password} @endnode @node echo_input "Configuration keywords" Keyword: echo_input=(yes|no) Usage ----- With this keyword you can disable the input echoing of amimud. By default amimud copies the string you typed in the input window to the output window when you press return, if you don't like this behaviour you can disable it. Example: echo_input=no (disable the input window echoing) Default value: yes See also: @endnode @node max_retries "Configuration keywords" Keyword: include Usage ----- This keyword introduce the possibility to make complex modular configurations in AmiMUD. You can separate the triggers you use with all your characters and put this stuff in a single file for instance that will be included by the single character configurations. Example: include=modules/crypt will include the alias and macros to use the crypt feature in your configuration. See also: @endnode @node max_retries "Configuration keywords" Keyword: max_retries Usage ----- This keyword let you choose how many times AmiMUD will try to connect to a MUD before the "connection timeup", this is very useful if the mud you are playing crashes or if it is rebooting. Example: max_retries=5 AmiMUD will try to connect to the mud 6 times (5 retries), so it will try for about 6 minutes (1 minute per attempt). Default value: 0 See also: @endnode @node alias "Configuration keywords" Keyword: alias Usage ----- Alias let you make shortcuts for your macros or also for commands. An alias is recognised ONLY if it's the first word you type in the input gadget, alias can be also nested, so don't make alias as "gt"->"gtell" because this will hang AmiMUD, use for instance "gt "->"gtell ". Example: alias=ft gt (if it founds ft it will substitute it with gt) alias=heal cast 'heal' (you can substitute simple macros without hotkeys with aliases) Rememer for very simple hotkeys to put a space after the definition: alias=h cast 'heal' Otherwise all the works beginning with "h" will be substituted... See also: @endnode @node globalkeys "Configuration keywords" Keyword: globalkeys Usage ----- Usually the @{"macro" link macro} hotkeys are local, they works only if the active window is the amimud one. Sometimes (for instance when playing two muds at once) may be useful to be able to send a command to one mud when you are working on the other one window. In these cases you can use this keyword. Your hotkeys will be global, so you have to define different hotkeys for each mud. They will works also if you are using IRC or IBrowse, so be careful when using this option. Default value: No Example: globalkeys (enable global hotkeys) See also: @endnode @node variable "Configuration keywords" Keyword: variable Usage ----- This character identify variables in trigger and macros. You must pay attention using a character you doesn't need to specify in the text of macro/triggers, otherwise you can have strange problems. Example: variable=% (set the variable char to "%", like tinyfugue) Default value: $ See also: @{"variable character" link variablechar}, @{"keyword command" link command}, @{"use of variables" link variables} @endnode @node rx_path "Configuration keywords" Keyword: rx_path Usage ----- To execute rexx script AmiMUD needs to know where "rx" is located, it's by default in sys:rexxc/, if you have changed this position in your sistem in order to use @{"#rx" link rx} command you need to configure properly this keyword. Example: rx_path=work:rexxc/ (the rx executable will be searched in work:rexxc/) Default value: sys:rexxc/ See also: @{"AmiMUD ARexx interface" link arexx} @endnode @node command "Configuration keywords" Keyword: command Usage ----- @{"Internal commands" link commands} and @{"macros" link macro} to be recognised have to be preceded by a char, the command char. The default value of this character is "#" (so you can for instance call the command @{"cycle" link cycle} with "#cycle"), but this can be changed if you prefer to use another character. The command character is recognised {b}only{/b} if specified at the beginning of a line, so you can give commands with the command character inside without problems (eg. gossip hello!#!#!#?). If you have to use the command character as the first character of the command you can simply substitute it with a double command (eg ##\\n will send #\\n to the mud). Example: command=/ (set the command/macro character to "/", like tinyfugue) Default value: # See also: @{"use of command" link commandchar}, @{"keyword variable" link variable} @endnode @node input_window_y "Configuration keywords" Keyword: input_window_y Usage ----- With this keyword you can specify WHERE the input window will appear on the screen you select for AmiMUD. It works both on public screens and custom screens. By default the input window will be opened on the bottom of the screen, but if you like with this keyword you can also make it open on the top or in the middle. Example: input_window_y=10 (this opens the input window on the top of the screen) Default value: bottom of the screen See also: @endnode @node separator "Configuration keywords" Keyword: separator Usage ----- This keyword let you define the character to use to separe different commands to be sent to the mud with a single RETURN keypress. The default is ';' like in tintin++, remember if you want to include this character in you text to use ';;', otherwise it will be interpreted like a separator... Example: separator=| (set the separator character to "|") Default value: ; See also: @{"Send commands to the mud" link scommands} @endnode @node speedwalk "Configuration keywords" Keyword: speedwalk Usage ----- This keyword can be used to change the character used to identify a speedwalk. Example: speedwalk=& (set the speedwalk character to "&") Default value: % See also: @{"use of speedwalk" link speed} @endnode @node screenfont "Configuration keywords" Keyword: screenfont Usage ----- Using this keyword and the screenfontsize one you can choose the font amimud will use if opened on a custom screen. If the size is not specified this will be 8 by default, so remember to use always @{"screenfontsize" link screenfontsize} in conjunction with this keyword. Please remember also that the output window is a console window, so if you want to modify the font of this window you need to change the "default system font" in the system preferences. Example: screenfont=times.font (set the screen font to times, use @{"screenfontsize" link screenfontsize} to specify the size of the font to use) Default value: default workbench screen font See also: @{"screenfontsize" link screenfontsize} @endnode @node screenfontsize "Configuration keywords" Keyword: screenfontsize Usage ----- Use this to specify the size of the font to use in amimud (in conjunction with @{"screenfont" link screenfont}) if you open it on a custom screen. Example: screenfontsize=11 (set the font size to 11, if it doesn't exist the font will be scaled) Default value: default workbench screen font See also: @{"screenfont" link screenfont} @endnode @node host "Configuration keywords" Keyword: host Usage ----- This define the host to automatically call when amimud is launched. This option can be overridden if you specify the host to contact through command line or if you specify the NOCONNECT switch. Probably you'll need also to specify a valid @{"port" link port} because the large majority of the muds doesn't run on the default telnet port (23). Example: host=realms.community.net See also: @{"port" link port} @endnode @node port "Configuration keywords" Keyword: port Usage ----- The port (tcp service) to connect to. Usually MUDS don't run on the default telnet port (23), but on higher port numbers. So if you want AmiMUD be able to connect your favourite MUD you'll need to set this keyword to the right value. This keyword is ignored if you specified a valid port number through command line. If no port is specified the default value of the port AmiMUD will try to connect to is 23. Example: port=7777 Default value: 23 See also: @{"host" link host} @endnode @node relogin "Configuration keywords" Keyword: relogin=(yes|no) Usage ----- If this keyword is specified in the configuration file the @{"autologin" link autologin} procedure will be attempted each time you connect to a mud, otherwise it will be active only when you connect for the first time. This is useful expecially in lag condition when you may need to disconnect and then reconnect. It's not active by default because often one disconnect himself to reconnect with another character. Example: relogin=yes (do autologin each time you connect to a mud) Default value: no See also: @{"user" link user}, @{"use of the autologin" link autologin} @endnode @node output "Configuration keywords" Keyword: output Usage ----- This option let you specify dimensions and title of the window in which will be displayed the texts coming from the mud. Actually this window is a standard amiga console, you can improve it for instance using KingCON that add a review buffer to the window and some useful menus for things like blocking the output (useful to examine an important text without problems dued to other texts coming from the MUD). Example: output=con:5/15/635/420/Output window/CLOSE (For a 1:1 WB) output=kcon:5/15/635/200/Output window/CLOSE (If you use kcon without replacing original handler) Default: output=con:5/15/635/200/Output window/CLOSE You can find KingCON on aminet (util/shell/kingcon13.lha). See also: @endnode @node history "Configuration keywords" Keyword: history Usage ----- This command let you choose how many commands will be remembered. AmiMUD offers you an history buffer (you can access it with curs up and curs down keys), the default dimension of this buffer is 20 commands, after the 20th command AmiMUD will begin to delete the older ones. You can change this limit using this keyword. Example: history=50 (remembers 50 commands) Default value: 20 See also: @endnode @node speed "Use of speedwalking" Speedwalking (REGISTERED) ------------------------- The speedwalking is a way to send to the mud long path quickly. AmiMUD recognise as speedwalk a line beginning with '%' you can change this character using the @{"speedwalk" link speedwalk) keyword in the configuration. The character accepted as valid directions are n,w,s,e,u,d. You can for instance write a speedwalk like this: %esesuwwn This will make your character move east, south, east, south, up.... For long path you can also use numbers in a speedwalk. The number you specify refers to the direction that follow the number: %s13en2u This will move your character south, then 13 times to east then north and finally 2 times up. Speedwalk are very useful in macros to move to a place quickly. Warning: the speedwalk path is sent to the mud after you press return, so there is no way to stop it. @endnode @node crmode "Configuration keywords" Keyword: crmode=(crlf|lf|cr) Usage ----- This command let you choose the type of lines the mud send to you. Actually every mud uses the "crlf" mode (default value), so you probably will never need to use this keyword. Some strange telnet services may require to use "cr" or "lf" mode, I've included this feature for future telnet compatibility... Example: crmode=cr (expects that carriage returns are sent as CR character) Default value: crlf See also: @endnode @node verbose "Configuration keywords" Keyword: verbose=(yes|no) Usage ----- This keyword is very important. Many AmiMUD commands can create output messages on the output window, if verbose is disabled none of the not strictly needed output will be displayed. This can be useful for an expert user, but isn't suited for a beginner or if you are testing new trigger/macros... Example: verbose=no (Disable verbose outputs) Default value: yes See also: @endnode @node user "Configuration keywords" Keyword: user Usage ----- This is the first of the four keyword used to define @{"autologin" link autologin}. In user you have to specify the name of character you want to login automatically when you start AmiMUD. IMPORTANT: To enable @{"autologin" link autologin} you MUST specify user, password, userprompt and passwdprompt. If one of these is not specified in the configuration @{"autologin" link autologin} will not work. Example: See @{"userprompt" link userprompt} See also: @{"userprompt" link userprompt} @{"password" link password} @{"passwdprompt" link passwdprompt} @{"afterpasswd" link afterpasswd} @{"relogin" link relogin} @endnode @node userprompt "Configuration keywords" Keyword: userprompt Usage ----- This keyword tell AmiMUD when it have to send the character name (@{"user" link user}) to the mud. It must be a part of the string received from the mud after the banner. Example: userprompt=name? (for shadowdale and similar muds) See also: @{"user" link user} @endnode @node password "Configuration keywords" Keyword: password Usage ----- In password you have to specify the password of the character you specify in @{"user" link user} keyword. Example: See @{"userprompt" link userprompt} See also: @{"user" link user} @endnode @node passwdprompt "Configuration keywords" Keyword: passwdprompt Usage ----- Here you have to specify the prompt received by the mud before typing the password. Example: passwdprompt=assword: (for nearly every mud) See @{"userprompt" link userprompt} See also: @{"user" link user} @endnode @node afterpasswd "Configuration keywords" Keyword: afterpasswd Usage ----- Usually after the password you'll need to send to the mud other text to complete the login operation. For instance on diku muds you'll need to confirm the MOTD (message of the day) with RETURN and to select option 1 from the menu. With afterpasswd you can do this automatically. This feature is only used if @{"autologin" link autologin} is enabled. Example: afterpasswd=1\\n1\\n (afterpasswd for a dikumud) See also: @{"user" link user} @endnode @node ticks "Configuration keywords" Keyword: ticks=(yes|no) Usage ----- This keyword is useful if you use AmiMUD to play LPMud or other mud types that don't use ticks. Example: ticks=no (disable tickcounter) Default value: ticks=yes See also: @{"Use of tickcounter" link tickcounter} @endnode @node mark "Configuration keywords" Keyword: mark Usage ----- If you want to use the tick counter properly and to see your prompt in the title of the input window you need to modify your prompt (or the mark) making AmiMUD able to detect it in the incoming text from the mud. If you can modify the prompt (in many mud you can do it with the command "prompt") you can simply use the default mark and modify your prompt as follow: prompt ##[your old prompt]> The prompt must begin with ## (or another mark you can configure with the mark keyword) and end with ">" (this cannot be changed). I made this choice because I see that the way TinyFugue recognises the prompt (a line without the final CR) has many troubles in lag condition... This way is a bit more complex but works always :) Example: mark=** (identify the prompt as the line that begin with "**" and ends with a ">") Default value: mark=## See also: @{"Use of tickcounter" link tickcounter} @endnode @node tickseconds "Configuration keywords" Keyword: tickseconds Usage ----- Use this if you know the length of the tick of the mud you are playing. For DIKU type muds it's usually 75seconds, for other mud types 90 and 120, this may not be true if the mud has many players online and then the ticks will be longer. Example: tickseconds=90 (set tick length to 90 seconds) Default value: 75 See also: @{"Use of tickcounter" link tickcounter} @endnode @node minimum_tl "Configuration keywords" Keyword: minimum_ticklength Usage ----- Set a minimum value to accept as tick length in the automatical tick calculation process, very useful if you have not defined triggers for heals, refresh, etc... Example: minimum_ticklength=20 (set the minimum accepted tick length to 20 seconds) Default value: 60 See also: @{"use of the tickcounter" link tickcounter} @endnode @node crypt_password "Configuration keywords" Keyword: crypt_password Usage ----- This password can be set in the configuration or during the use of the program with the @{"#password" link password} command. If not defined you will not be able to use the @{"crypt" link cryptuse} feature of AmiMUD (and Elf for Windows). Example: crypt_password=W Genoa The password is "W Genoa", only the users of AmiMUD or Elf that know the password can @{"decrypt" link decrypt} your text. See also: @{"use of crypt" link cryptuse} @endnode @node beforetick "Configuration keywords" Keyword: beforetick Usage ----- A simple macro to be executed before the tick, useful to recover mana and hp more quickly. Use it in conjunction with @{"aftertick" link aftertick}. Example: beforetick=rest\\nsleep\\n (make your character rest and sleep 3-5 seconds before the tick) Default value: not enabled See also: @{"use of the tickcounter" link tickcounter} @endnode @node tickmacro "Configuration keywords" Keyword: tickmacro Usage ----- A macro to be executed when the tick occurs. Example: Default value: not enabled See also: @{"use of the tickcounter" link tickcounter} @endnode @node aftertick "Configuration keywords" Keyword: aftertick Usage ----- Simple macro that will be executed after the tick, very useful in conjunction with @{"beforetick" link beforetick}. Example: aftertick=wake\\nstand\\n (make your character wake and stand up right after the tick) Default value: not enabled See also: @{"beforetick" link beforetick} @{"use of the tickcounter" link tickcounter} @endnode @node prompt "Configuration keywords" Keyword: prompt Usage ----- Very useful keyword. If you want to use the tick counter with the automatical tick length calculation you'll NEED to specify a correct value for this one. If the ticks of your mud are fixed length then you have to delete this keyword from your config (this will disable automatical tick calculation) and specify the right @{"tick length" link tickseconds}. Example: if the prompt of the mud is: ##HP:3049 MA:2020 MV:111 (------) * -*> You have to set: prompt=HP:%ld MA:%ld MV:%ld (recognise a prompt with 3 variables) Default value: not enabled See also: @{"use of the tickcounter" link tickcounter} @endnode @node customscreen "Configuration keywords" Keyword: customscreen Usage ----- AmiMUD will open as default on Workbench screen, if you want to make it opens on a custom screen you need to specify this keyword. Note that ANSI mode is available only if amimud is opened on a custom screen (or on a public screen with ansi colors :) ). Example: customscreen (will popup a requester if the other @{"screen parameters" link screenpars} are not defined) Default value: not enabled See also: @{"AmiMUD on custom screen" link screenpars} @endnode @node displayid "Configuration keywords" Keyword: displayid Usage ----- This keyword specify the displayid to use for the screen, if you want to specify it you'll need to specify it as a DECIMAL number. It is considered only if also @{"screenwidth" link screenwidth}, @{"screenheight" link screenheight} and @{"screendepth" link screendepth} are correctly specified in the configuration. Example: Default value: not enabled See also: @{"AmiMUD on custom screen" link screenpars} @endnode @node screenwidth "Configuration keywords" Keyword: screenwidth Usage ----- The width of the custom screen to open. It is considered only if also @{"displayid" link displayid}, @{"screenheight" link screenheight} and @{"screendepth" link screendepth} are correctly specified in the configuration. Example: screenwidth=640 Default value: not enabled See also: @{"AmiMUD on custom screen" link screenpars} @endnode @node screenheight "Configuration keywords" Keyword: screenheight Usage ----- The height of the custom screen to open. It is considered only if also @{"displayid" link displayid}, @{"screenwidth" link screenwidth} and @{"screendepth" link screendepth} are correctly specified in the configuration. Example: screenheight=512 Default value: not enabled See also: @{"AmiMUD on custom screen" link screenpars} @endnode @node screendepth "Configuration keywords" Keyword: screendepth Usage ----- The depth of the custom screen to open. It is considered only if also @{"displayid" link displayid}, @{"screenheight" link screenheight} and @{"screenwidth" link screenwidth} are correctly specified in the configuration. Example: screendepth=3 (the minimum depth for for ANSI mode) Default value: not enabled See also: @{"AmiMUD on custom screen" link screenpars} @endnode @node ansi "Configuration keywords" Keyword: ansi Usage ----- If you specify this keyword (and you open AmiMUD on a @{"custom screen" link customscreen}) you'll be able to see muds in ANSI colors (if the mud you are playing supports them). Example: ansi (this will enable ansi colors) Default value: Not enabled See also: @{"palette" link palette} @endnode @node palette "Configuration keywords" Keyword: palette Usage ----- If you want to use a particular palette with AmiMUD you can. You can edit it with the menu option Prefs->Edit palette.. and then save it to a suitable file (for example progdir:amimud.palette) and then add the keyword palette=amimud.palette to your configuration. Please note that the palette keyword works only if AmiMUD is opened on a custom screen. Important: This feature works only with OS 3.0+ Example: palette=work:pictures/mypic.iff (load in the amimud screen the palette of mypic.iff) Default value: Not enabled See also: @{"Open AmiMUD on a custom screen" link screenpars} @endnode @node macro "Configuration keywords" Keyword: macro Usage ----- Macro are very useful in muds, expecially if you need to do things very quickly... A macro is a way to send many commands to the mud in a quick way. Macros can be defined in the configuration file, with the command @{"#macro" link macro} or through the menus. You can also see a list of all the defined macros with the command @{"#list" link list} or through menus. Macro may require arguments or not and the macro text may contain variables. Actually if you want your macro have two parameters you have to add after the macro name $0 $1. Actually macro parameters MUST be in crescent order 0..4. macro=givefb $0 $1 rem bag\\nget $0 bag\\nwear bag\\ngive $0 to $1\\n This is a correct definition for macro with arguments, the following one instead will NOT work: macro=givefb $1 $2 rem bag\\nget $1 bag\\nwear bag\\ngive $1 to $2\\n From version 1.1 also macro with parameters can have hotkeys but they works in a different way. When you press the hotkey the macro name will be shown in the input window and the cursor will be placed after the last character of the macro name. Then you need only to type the macro argument(s) and press return. This is useful expecially with macros with only one argument. Macro can also use variables. The only difference between a macro with parameters and a macro that contains variables is that the second can be launched with an hotkey. You can set the variables with @{"triggers" link trigger} or with the @{"#set" link set} command. See below for some examples. Hotkeys: The macro hotkeys use the standard Amiga hotkey format (chapter 10-25 of OS 3.1 Workbench manual) here is a short summary: alt, lalt, ralt - alt keys shift, lshift, rshift - shift keys lamiga, ramiga - amiga keys ctrl, control - control key leftbutton, middlebutton, rightbutton - mouse buttons F1..F10 - function keys Examples of hotkeys: hotkey=shift F1 hotkey=lamiga ctrl 5 hotkey=leftbutton F1 Important: The macro text must always end with a carriage return (\\n) otherwise the macro execution will not be confirmed... Warning the hotkeys defined in AmiMUD are GLOBALS, this means that if you assign F1 to a macro and you press F1 the macro will be executed also if the amimud window/screen is not the active one! This is dued to the way commodities handles hotkeys, if you need an hotkey you can simply disable AmiMUD commodity interface with Exchange or similar programs. Example: (These examples are thought for diku-like muds) macro=hungry hotkey=lamiga h rem bag\\nget bread bag\\neat bread\\nwear bag\\n (Macro without parameters, useful if your character is hungry (may be activated also with the hotkey amiga+h...) macro=getbag $0 rem bag\\nget $0 bag\\nwear bag\\n (Get an object from the bag) macro=hun&thir #hungry\\n#thirsty\\n (You can also call macros in a macro) macro=disint hotkey=alt 3 cast 'disintergrate' $7\\n macro=meteor hotkey=alt 2 cast 'meteor swarm' $7\\n macro=dispel hotkey=alt 1 cast 'dispel magic' $7\\n These macros are targeted, using the command @{"#set" link set} you can specify what does the variable $7 contents (example: #set 7 dracolich) and then you can call them with hotkey or typing the macro name without the need to specify the target each time. Examples of macro defined through the command macro: #macro "hungry" "rem bag\\nget bread bag\\neat bread\\nwear bag\\n" (a macro defined with this command can NOT have hotkeys). See also: @{"Add a macro" link triggermacro}, @{"Advanced use" link advanced} @endnode @node trigger "Configuration keywords" Keyword: trigger Usage ----- Triggers are the most powerful feature of a mud client over a normal telnet connection. Triggers may make automatic many actions that have to been performed quickly or that have to be done very often. Triggers may contains @{"variables" link variables}, this can be useful in two different ways. The first (and obvious) way is to use part of the text that activate the trigger in the trigger body, for instance to split some coins through the group members (see examples below). If you put a variable in the trigger definition (obviously with some other text, otherwise ANY line willl match that trigger) if the trigger is found the variable will contain the text between the words that make the trigger match. trigger=A $1 C #echo trigger found, $1 is between A and C\\n if the mud sends to the player "A B C" the trigger will be activated and the phrase: trigger found, B is between A and C Will be printed in the output window. The second way to use triggers is an alternative to @{"#set" link set}. You can set variables with a trigger without using them. For instance if you need (on a diku-type mud) to know who is the group leader and keep the value in a variable for future use you can make a trigger to get the name from the text the mud sends in some cases: trigger=now member of $7's group #echo Put groupleader name ($7) in variable 7\\n Remember that macros and trigger must always end with a carriage return (\\n) otherwise the text will be send to the mud, but not confirmed! Example: trigger=ou are hungry #hungry\\n (See the section @{"macro" link macro} to see how #hungry is defined.) trigger=as you hear $0m$1's get all.coins $1\\n trigger=as you hear $1's get all.coins $1\\n (These two macros make the same thing, the first works if you are playing in ansi mode, the second in plain mode, please note the use of the $0 variable to strip the ansi code) trigger=here were $1 coins split $1\\n (This macro split the coins you get from a corpse to the members of your group) See also: @{"Add a macro" link triggermacro}, @{"Advanced use" link advanced} @endnode @node gag "Configuration keywords" Keyword: gag Usage ----- This keyword let you define some text you want to be displayed. It can be useful to make output of some commands cleaner. Example: gag=is in excellent condition. (Will be useful to make the output of command "equip" on diku-mud shorter) See also: @{"gagline" link gagline"}, @{"highlight" link highlight} @endnode @node gagline "Configuration keywords" Keyword: gagline Usage ----- With this command you can tell amimud to not display a line of text. This is useful for instance in fightning with many fighters. You can disable gagline you have defined or add a new gagline in any moment through menus. Example: gagline=misses you (You will see only the hit of enemies if they hit you) See also: @{"gag" link gag"}, @{"highlight" link highlight} @endnode @node highlight "Configuration keywords" Keyword: highlight Usage ----- Highlight may be used to make some text be highlighted ( :-) ). This can be useful in many cases. Highlights can be inserted in the configuration file or through the menu option, you can enable/disable them through menus or with the command @{"#high" link disable}. The syntax of the command is: highlight=type text The difference between @{"highline" link highline} and highlight is that the first highlight the whole line where "text" is find (works better if ANSI colors are disabled) and the second only the specified "text". These are the actually defined highlights: BOLD 0 UNDERLINE 1 ITALICS 2 REVERSE 3 BOLD_UNDERLINE 4 CLEAR_SCREEN 5 COLOUR_0 10 COLOUR_1 11 COLOUR_2 12 COLOUR_3 13 COLOUR_4 14 COLOUR_5 15 COLOUR_6 16 COLOUR_7 17 Example: highlight=0 extemely well highlight=1 massacres highlight=4 devastates (these three will highlight in different ways different hits) Default value: See also: @{"highline" link highline} @endnode @node highline "Configuration keywords" Keyword: highline Usage ----- Highline may be used to make some text be highlighted ( :-) ). This can be useful in many cases. Highlights can be inserted in the configuration file or through the menu option, you can enable/disable them through menus or with the command @{"#highline" link disable}. The syntax of the command is: highline=type text The difference between highline and @{"highlight" link highlight} is that the first highlight the whole line where "text" is find (works better if ANSI colors are disabled) and the second only the specified "text". These are the actually defined types of highlight: BOLD 0 UNDERLINE 1 ITALICS 2 REVERSE 3 BOLD_UNDERLINE 4 CLEAR_SCREEN 5 COLOUR_0 10 COLOUR_1 11 COLOUR_2 12 COLOUR_3 13 COLOUR_4 14 COLOUR_5 15 COLOUR_6 16 COLOUR_7 17 Example: highline=0 extemely well highline=1 massacres highline=4 devastates (these three will highlight the whole lines where the text "extremely well", "massacres" and "devastates" appear in different ways) Default value: See also: @{"highlight" link highlight} @endnode @node screenpars "AmiMUD on custom screen" Open AmiMUD on a custom screen ------------------------------ There are two ways to make AmiMUD open a custom screen. 1 - Using the CS or CUSTOMSCREEN command line switch if you launch AmiMUD from a shell. 2 - Specifying @{"customscreen" link customscreen} keyword in the configuration file. These two option will pop up a screenmode requester, if you use AmiMUD always on the same screen you may like to select the mode once for all. You can do this in two ways: 1 - (Easy way) Select the mode as usual in the screenmode requester then save the preferences of AmiMUD with the "Save Prefs" menu option. 2 - (Tricky way) Edit @{"displayid" link displayid}, @{"screenwidth" link screenwidth}, @{"screenheight" link screenheight}, @{"screendepth" link screendepth}. These FOUR parameters (and @{"customscreen" link customscreen}) have to be specified if you want to skip the screenmode requester. Optionally you can also specify @{"ansi" link ansi} (that init the screen with the default ANSI palette), @{"palette" link palette} that let you load an IFF palette (also from a picture) in the screen and @{"screenfont/screenfontsize" link screenfont} to specify the font to use in the custom screen. @endnode @node scommands "Send Commands to the MUD" Send Command to the MUD ----------------------- To send commands to the mud you simply need to write in the input window gadget and then press return. The text you have typed will be sent to the MUD. Please note that the input gadget will be activated also if you type a character on the output window, if you want to avoid this (for instance because you want to copy to the clipboard some text from the output window) you need to disable the commodity interface of AmiMUD through the program exchange (distributed with WB since 2.0), the side effect is that also hotkeys will be disabled. From V1.10 AmiMUD have the possibility to send multiple commands on a single line. The commands have to been separated by ';' (if you want to change the separator character you can use the configuration keyword @{"separator" link separator}), I have to use this instead of "\n" as separator because some internal commands support \n in the arguments... Anyway tintin users will be happy with this choice (and the others can change it through the config keyword) :) Example: open door;n;backstab drow Will performs these operations in sequence avoiding the risk of type error in a time critical situation. The multiple commands feature is available only in the registered version. @endnode @node use "Using the program" Using the program ----------------- @{" Start AmiMUD " link start} @{" Connect to a MUD " link connect} @{" Send commands to the MUD " link scommands} @{" Builtin commands " link commands} @{" Log to file " link log} @{" Use the numeric keyboard to move " link keymap} @{" Use of the autologin " link autologin} @{" Add a macro or a trigger " link triggermacro} @{" Use of gags and highlights " link gaghigh} @{" Send text to the MUD " link send} @{" Enable/Disable triggers/macros... " link disable} @{" Crypt some text... " link cryptuse} @{" Use of the tick counter " link tickcounter} @{" Use of the speedwalking " link speed} (REGISTERED) @{" Advanced use of triggers/macros..." link advanced} @{" Run multiple AmiMUDs " link multiple} @{" Iconify the program " link iconify} @{" Quit the program " link quit} @endnode @node iconify "Iconify the program" Iconify ------- From version 2.1 AmiMUD may be iconified, you can do it with the menu option or with the "Hide Interface" command of commodities exchange. To uniconify it you have to use commodities exchange "Show Interface" command. @endnode @node autologin "Use of the autologin" Autologin --------- To connect to your favourite mud in a quicker way you can use the autologin facility of AmiMUD. To active this feature you need to specify in the configuration file the keywords: @{"userprompt" link userprompt}, @{"user" link user}, @{"password" link password} and @{"passwdprompt" link passwdprompt}. If one of them isn't found in the configuration file autologin will NOT be available. There are also two other autologin optional keywords, @{"afterpasswd" link afterpasswd} and @{"relogin" link relogin}. With the first you can specify which characters send to the mud to bypass the initial menus and banners usually shown after the login. The second give you the possibility to do autologin not only the first time you connect. @endnode @node multiple "Multiple connections..." Multiple connections? --------------------- Often mud players like to play more than one mud at once, so unix clients often supports multiple connections, some guys that try the beta of AmiMUD asks me if I will implement multiple connections on future versions, I don't think I'll do it because actually is already possible to run multiple copies of AmiMUD, also on the same screen. Follows some suggestions to do "multiple connections" with AmiMUD (remember that the program executable is very little, so running multiple copies of the program is not a waste of memory). 1) Run many amimud (on different MUDs) on the WB screen: Simply make two configurations with the right host,port,name,password... obviously without the key @{"customscreen" link customscreen} and @{"run" link start} amimud from shell with the following parameters: run amimud CFG mud1.prefs run amimud CFG mud2.prefs You will have two connections opened on wb :) 2) Run many amimud (on different MUDS) on the same customscreen: Put @{"customscreen" link customscreen} in the first configuration (and @{"ansi" link ansi} if you want) and remove customscreen from the other configurations then run AmiMUD: run AmiMUD cfg mud1.prefs run AmiMUD cfg mud2.prefs SCREEN AmiMUD.1 run AmiMUD cfg mud3.prefs SCREEN AmiMUD.1 [...] With a proper configuration of the position of the windows with the config keywords @{"input_window_y" link input_window_y} and @{"output" link output} you can also make the windows opens without being overlapping. @endnode @node connect "Connecting..." Connect to a MUD ---------------- To connect a mud you usually need to specify TWO parameters. Address: May be an IP (192.106.166.6) or a mnemonic name (mclmud.mclink.it). The first one works also if you don't configure properly the DNS (name server) on your tcp stack. You have to write the address calling the menu item "Set Address..." in the menu "File" if you have not already defined them in the @{"configuration" link config} file. Port: Usually muds don't run on the default telnet port (23). So if you want to connect a mud generally you have to specify also the port number the mud runs on. To do this use the "Set Port..." menu item in the menu "File". The port may also be specified in the @{"configuration" link config} file. Once you have specified the address and the port and obviously you have already the TCP stack running you can connect to the mud. Use the "Connect" menu item or the shortcut RightAMIGA+C. The "tick" near the "Connect" menu item means you are connected. @endnode @node keymap "Use of the keymap" Keymap Movement --------------- One intresting feature of AmiMUD is the "keymap movement", AmiMUD remaps the classic cardinal directions on the numeric keypad, so you can move using it, without need of hitting return for each keystroke... This is how the directions are remapped: 7 8 9 - nw n ne d 4 5 6 + w exits e u 1 2 3 sw s se Actually this is a fixed setup, in the future I may insert some editing on this. Please note that this may not work on every mud (expecially diagonal directions). I suggest everyone to use keypad to move it's very quickly and handy if you use it often. @endnode @node variablechar "Variable character" Variable character ------------------ The variable char is a character that identify a variable inside a trigger or a macro, so you have to use a character you don't need in the text, otherwise you will get an error if you will use it. Dafault value: $ Example: (in the configuration file) variable=% macro=hello %0 gossip Hello %0!\\n (This will change the variable char from '$' to '%', like tinyfugue) @endnode @node commandchar "Commmand character" Command character ----------------- Actually all AmiMUD internal @{"commands" link commands} and all macros are detected through a special character at the beginning of the line. The default command character is '#' but may be changed through the config keyword @{"command" link command}. @endnode @node beep "AmiMUD internal commands" Command: beep Usage ----- If you call beep the screen will blink and/or a sample will be sound (it depends from your system preferences). This command may be very useful to make a trigger that call you if you are away from keyboard and someone wants to talk to you. Example: (in the configuration file if your name is Exodus) trigger=xodus @{"#" link commandchar}beep\\n (will perform a display beep if someone on the mud gossips says or tell "xodus" the first letter of the name is not specified to avoid lower/upper case problems). @endnode @node echo "AmiMUD internal commands" Command: echo Usage ----- echo is a small and very useful command for @{"complex triggers" link advanced}. It simply prints to the output window the contents of the line after his invocation. This sometimes may not be very useful, but often can be very handy (expecially if @{"verbose" link verbose}=no in your configuration file!). Example: @{"#" link commandchar}echo hello (will print hello in the output window) @{"#" link commandchar}echo @{"$" link variablechar}1 (will print the contents of @{"variable" link variables} "1" to the output window, a bit more useful than the previous example) @endnode @node cycle "AmiMUD internal commands" Command: cycle Usage ----- The cycle command let you repeat times a macro or some commands. It can be used also into a trigger. Syntax: #cycle Examples: #cycle 5 buy bread\\n Buys 5 peaces of bread #cycle 20 kick $9\\n Kicks 20 times the guy in variable $9 #cycle 2 #eat\\n Executes 2 times the macro #eat. @endnode @node variables "AmiMUD variables" Variables --------- Actually AmiMUD supports variables in a limited way. You can use variables from 0 to 9. These are used by triggers/macros and all the other commands. A variable is identified by the @{"variable char" link variablechar} (default '$') followed by a number from 0 to 9. The maximum length of the text in a variable is 30 characters. A variable is keep in memory until it's replaced by another value, this can be done through @{"macros" link macro}, @{"triggers" link trigger} or the @{"#set" link set} command. See also: @{"Advanced use of variables" link advanced}, @{"Variable char" link variablechar}, @{"variable keyword" link variable} @endnode @node commands "AmiMUD internal commands" Commands -------- All these command may be used directly through the input window or in triggers and macros. All the commands must be used with the following syntax: @{"#" link commandchar}commandname @{" action " link action} @{" alias " link defalias} @{" beep " link beep} @{" clip " link send} @{" crypt " link crypt} @{" cycle " link cycle} @{" decrypt " link decrypt} @{" echo " link echo} @{" file " link send} @{" gag " link disable} @{" gagline " link disable} @{" help " link help} @{" high " link disable} @{" highline " link disable} @{" list " link list} @{" log " link log} @{" macro " link macro} @{" password " link password} @{" rx " link rx_cmd} @{" send " link sendsym} @{" set " link set} @{" skiptick " link tickcounter} @{" separator " link separcommand} @{" stoplog " link log} @{" sync " link tickcounter} @{" trigger " link disable} @{" wait " link wait} @endnode @node rx_cmd "AmiMUD internal commands" Command: rx Usage ----- Syntax: #rx