Label - is a name for the alias, so you can use scripting to activate/deactivate it.
Script - is just what you think, it is the name of the script subroutine that is called when the alias is matched.
Group - is like name, except you can give a collection of related timers, aliases and triggers the same 'group', thus allowing you to enable/disable them all at once from in the script.
Variable - this is used to take the value of %1 and store it directly in a Mushclient variable. This only happens if you select 'send to variable'.
In any case, yes, you can both send commands and call a script to do other things in the same alias. If what you are trying to do is simple, then you can even set the alias to 'send to script', in which case you would do something like:
send "kill %1"
setvariable "last kill", "%1"
by placing that in the 'send' field instead. The 'send to script' option basically overrides the normal sending and instead feeds the contents to the script engine, where it is interpretted. That is why you have to use 'send' for the commands, instead of just using 'kill %1'.
It also makes creating plugins a bit easier, since the script for the trigger, alias, etc. is automatically copied into the plugin when created. Normally you would have to manually select which lines of your script need to be copied into the new plugin. However, for normal use, it is a matter of personal choice. It is sometimes easier to work on complex scripts that interconnect to each other, especially if you have an alias that just executes different functions. For example, a plugin I made uses a single alias to call a half dozen or more different functions, depending on what follows the main command. Exa: potions:list, potions:add, etc. In such a case it isn't practical (or maybe even possible) to have the whole script inside the alias, so editing it in the main script file is easier. For what you need though, it is just a matter of which one you are more comfortable using. |