I have some suggestions to make. First of all, aliases should evaluated in triggers, at least by option. For example, if I have a trigger, it would be nice if the trigger could send an alias without having to paste it all in the trigger again. Also, it would be nice if we could send text from one window to the others, to control characters. For example, using a customized string ("#" in our example) would send something to window 2. I.E. this string "#2 bow" would cause the command "bow" to be sent to the second window (aliases evaluated). Also, the text "# bow" would send "bow" to all windows.I have some suggestions to make. First of all, aliases should evaluated in triggers, at least by option. For example, if I have a trigger, it would be nice if the trigger could send an alias without having to paste it all in the trigger again. Also, it would be nice if we could send text from one window to the others, to control characters. For example, using a customized string ("#" in our example) would send something to window 2. I.E. this string "#2 bow" would cause the command "bow" to be sent to the second window (aliases evaluated). Also, the text "# bow" would send "bow" to all windows.
Alias/Trigger suggestions
Posted by Poromenos on Wed 10 Jul 2002 06:18 PM — 5 posts, 12,983 views.
All of that is possible if you are willing to implement scripting.
1. An alias and trigger can call the same script subroutine.
2. It is possible to use special script functions to send text to whichever window you want. It would not be too difficult to write a script to respond to a single alias, in the manner you suggested. In order to use the alias in any world, all of your worlds would have to have the same subroutine in thier script file. This is also easier to implement in the latest beta version, as a plugin.
1. An alias and trigger can call the same script subroutine.
2. It is possible to use special script functions to send text to whichever window you want. It would not be too difficult to write a script to respond to a single alias, in the manner you suggested. In order to use the alias in any world, all of your worlds would have to have the same subroutine in thier script file. This is also easier to implement in the latest beta version, as a plugin.
There is a simple solution to your first suggestion, that does not even require scripting.
First, set up the "shared" thing that the alias(es) and trigger(s) are going to do as a *variable*.
eg. variable: whattodo = "get golden wand"
The alias can then send: @whattodo
(with expand variables checked).
Similarly with the trigger. That way any common things can be defined once and used in many places.
First, set up the "shared" thing that the alias(es) and trigger(s) are going to do as a *variable*.
eg. variable: whattodo = "get golden wand"
The alias can then send: @whattodo
(with expand variables checked).
Similarly with the trigger. That way any common things can be defined once and used in many places.
That won't work, Nick... I have a 50 line speedwalk alias... Imagine getting it on a variable.
What is the problem with that, exactly? Variables can be multiple lines. However I think there might be a problem that variables are not evaluated as speedwalks, which is a bug. I'll fix that.