Just reading over Murphy's log against Thorgal, I notice his messages to himself, like when he knocks someone down, or soulless is activated - all seem to appear exactly after the (I am guessing) triggered line.

Now.. My #SHOW's get triggered and often end up appearing after another line or two of text from the MUD.

eg. My target gets entangled, which triggers the #SHOW IS ENTANGLED!

But that #SHOW tends to appear after my next prompt.

Is it connection speed? Or is there some way to make sure your echoes get placed where they should be?
zMUD, by the way.

Thanks!

best way to do it is have the trigger go like this

#SA TARGET-IS-WEBBED-KILL-THE-BITCH
#CO 202 <--- thats the colour command which will highlight it nicely, change the numbers however you like

it should happen right after it, its got nothing to do with connection speed

The #SHOW text appearing after your prompt is because more text came in with that same packet that you just triggered on, so it's actually because you have a fast connection, not a slow one as some people tend to think.

You can color text all in one command with the %ansi function.

#SHOW {%ansi(blue, white)Target is webbed!}

Works for me.

Oh, and if you really want to try something to make the text appear sooner, try throwing #PRIORITY around your #SHOW command so it'll execute before processing anything else. Not a guaranteed, but the only think I could think of to recommend for this.

Hmm...
That must be what is happening? Any way to avoid the prompt getting mashed in like that? I'd rather not put in Priorty's...

You could CONFIG PROMPT ADD LINEBREAK, to try and force the prompt onto its own line, but that has the (spammy) side effect of making lots of unneeded blank lines. You could gag the blank lines, but then you're covering a side effect with more side effects...

A silver torc cracks and crumbles to dust.
The end of your cudgel forms a knotty burl and you point it at a serpentine
starsucker. The burl pops and ruptures, shooting a barrage of splinters into
his flesh.
2874h, 846m, 3289e, 10p xkdb-
---YOUR TORC IS EXHAUSTED, DRUID!

First bolded point is my trigger line, the second is the #show that is triggered.
Does anyone else get it this far out of whack?

I've never, ever seen that.

Maybe try #sub instead, and make a multi-line substitution?

#trigger {^A silver torc cracks and crumbles to dust.$} {#sub { A silver torc cracks and crumbles to dust. %cr ---YOUR TORC IS EXHAUSTED, DRUID!}} "" {prompt}

Edit: forgot one of the closing }.

you should try #SA

#SHOW and #SAY are the same, according to the helpfiles.

Yeah, I'll have a look at that Drago. Just didn't want to make things overly complex when I thought it wasn't needed

Mayby try #echo command.

You need to use only one window cose it will appear in your active window, but it works for me all the time.
I never had any problems with it.

I use Echo.

This is a question to Echo, but I've noticed on a few of my Echo's that, if it has a wait, say 5 seconds, and the same message appears 4 seconds later (before the 5 seconds is up), it re-starts the 5 seconds.

Anyway around this?

Don't use waits

Waits are evil and they suck.

I like waits, like timing how long until a summon goes through.

The help files specifically said not to use waits, I think they may have given an alternative though, don't remember exactly.

#ALA +x {//Everything after the #WAIT}
Where x is the number of seconds you wanna wait.

zMUD is not a multi-threaded program. #WAIT pauses everything. It's ok in aliases, but triggering it can lead to problems. Use #ALARM instead.

If you use an alarm and you want the time to continue without resetting on your trigger (which is what I'm hearing), then give the alarm a name. zMUD won't create more than one alarm with that name, so until it expires and is deleted, you will just have the one alarm.

Oh, really? Then is there any way to reset a timer when you actually want to? Making a new timer wouldn't do the trick, I'd think.

If you want to time, use the time feature to just display the time in hours, minutes, and seconds next to your prompt when you want to time something. Wait stops all your triggers from working while under the duration, Zmud helpfile warned highly against using it for that reason.