I fixed that problem I was having with my zMUD triggers echoing messages a couple of lines after the trigger.

Don't use #SHOW.

Going back and reading the zMUD helpfile, yeah, it says something I don't understand about %crlf being the difference, or something like that.

End result - using #SAY in a trigger puts it directly after the trigger line.
Using #SHOW (without any fancy business I don't know about) seems to stick it further down.

If anyone can clarify that into actual, coherent reasoning I'd be more than happy to listen

#show has a whole letter more, which takes -that- much longer to process. #say is shorter, so appears faster.

Also, #SHOW counts as coming from the MUD, for triggers, while #SAY doesn't. Also, #SHOW defaults to MUD output color, #SAY defaults to bright cyan.

#SA is also an abbreviated for #SAY....works for me

What Sylphas said.

In fact a good way to test triggers and such is to use #SHOW, so you can see what your system does when that trigger line happens.

don't totally know without looking but %crlf is a character return/line feed pair...i.e a windows new line. so if you were getting extra new lines, that could explain it. Maybe