Order of alias execution
Order of alias execution
Is there a defined order of alias execution if multiple aliases match the input string? I would like to be able to create an "alias of last resort" that intercepts all input for processing before sending it out, but only if another alias hasn't processed it first. I can create an alias with pattern ".*+" to intercept all non-empty lines, but is there any way to guarantee that this alias will be executed after all others?
Re: Order of alias execution
Yes - aliases are processed in the order they are in the trigger editor, temp aliases are processed in chronological order of creation after them.
Have you looked at http://wiki.mudlet.org/w/Manual:Event_E ... endRequest, maybe that'll help?
Have you looked at http://wiki.mudlet.org/w/Manual:Event_E ... endRequest, maybe that'll help?
Re: Order of alias execution
Thanks for the info. I think I'll go with the first idea and make sure my catch-all is at the bottom of the alias list. The event doesn't seem to be the right solution. It seems I'd have to manage state so that I process user-input but ignore send()s generated by triggers or the event itself.
Re: Order of alias execution
You would - in a system, it'd not that difficult, just implement a custom send() method that sets it. With the first solution, you'd have the trouble of keeping it last if others create tempAliases after yours - more hassle I reckon.