|
kjaerhus Magician
Joined: 18 Dec 2006 Posts: 317 Location: Denmark
|
Posted: Sat Apr 19, 2008 2:12 pm
Trigger priority |
I have two triggers both dynamically set up through scripts. Idea is that one trigger tells me that I am done doing something and the other trigger wants to gag some output from the mud. Problem is that in situations where they trigger on the same text the trigger that gags seem to win the race to first execution and the trigger that should tell me that I am done will never fire. I've tried setting priority on the triggers but the outcome is the same. Any good advice?
I have the same problem another place where I have to trigger to highlight names and another to gag certain output to another window. Sometimes the moved text is highlighted - sometimes it is not... |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Sat Apr 19, 2008 7:57 pm |
The only thing I can think of that does this is the the "stop further processing" option - that stops further processing (obviously) on that line. Check that whichever trigger has the smaller priority number (or both just to be on the safe side) doesn't have it checked.
A gag command won't stop other triggers being executed. I tested this like so in the untitled session:
#trig "one" {something} {#gag}
#trig "two {something} {#say omg lol}
#say something
You'll notice that the gagging trigger has a higher priority but "omg lol" is still displayed. |
|
|
|
kjaerhus Magician
Joined: 18 Dec 2006 Posts: 317 Location: Denmark
|
Posted: Sat Apr 19, 2008 8:43 pm |
I'll have to dig more into it then to find a more specific description of my problem. How is it by the way that the gagging trigger has higher priority? And what is the highest priority of 1 and 2?
EDIT: just read your reply a little closer. I suppose 1 is higher then. As I thought but it's not documented - if I may suggest this for the manual... :-) |
|
|
|
|
|