Zugg Software :: View topic

Newbie Joined: 03 Feb 2003 Posts: 5 Location: Germany

I have a bunch of triggers that will capture different communication channels and tests, but had no luck to capture multiple lines of text, because the mud wraps the text if the first line is longer than 75 chars.

The mud output looks like this:

XXX tells you: blablablabla bla bla bla bla
bla bla bla bla bla bla bla bla

Same goes for all channels.
Is there a way to capture all the lines and place them in proper windows where they belong? (i have separate windows for each channels and for tells ...)
initial trigger #tr {^%w tells you:} {#capture Tell} works perfectly for the first line :)

Novice Joined: 30 Sep 2002 Posts: 32 Location: USA

Well this might help you out...

Most muds force a gramerical construct... so tells look like (in zmud speak)

%w tells you '*.'

If you check for that last quote and period at the end of the line you could chain it to a conditional. I.E. if I see the .' as the last two characters do nothing, if I DO execute the capture on the next line I see.... recurse it for multipule lines.

--Killfile

Newbie Joined: 03 Feb 2003 Posts: 5 Location: Germany

If i had those single quotes i wouldnt have asked this question :)
Thanks for the help in any case.
The output i guess has no quotes. Just the
%w tells you: *

Not even a dot in the end unless the one who tells you typed it

Magician Joined: 24 Feb 2001 Posts: 342 Location: USA

if theres absolutely no way to distinguish the second line from the rest of the mud output, then your best approach is is probably to count the characters:

#tr {(%w tells you: *)} {#if (%len(%1) = 75) {#capture Tell;#t+ getnextline}}
#class getnextline
#tr {*} {#capture Tell;#t- getnextline}
#class 0

of course, this will misfire whenever the message is exactly long enough to reach the end of the line but not long enough to wrap.

--------

moon.icebound.net:9000

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

The spaces at the start if the second line fail to display on the forum correctly, but I can see them. Anyway, you can use those spaces to figure out if you should capture that line too. Example:
#TRIGGER capTells {^%w tells you:} {#CAP Tell}
#COND {^(*)$} {#IF ("%1" =~ "^%s*$") {#CAP Tell} {#STATE capTells 0}} {manual}

Kjata

Newbie Joined: 03 Feb 2003 Posts: 5 Location: Germany

Works like a dream. Thank you very much.

Newbie Joined: 03 Feb 2003 Posts: 5 Location: Germany

I found a slight problem with this trigger that i dont know how to fix. If i get two short one line tells in a short time interval, only the first one is captured. the second one seems to be omitted. I think that the trigger actually waits for a line with blank spaces in front to return itself to state 0.
Any idea on how to fix that ?

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Change this:
("%1" =~ "^%s*$")

to:
(("%1" =~ "^%s*$") or ("%1" =~ "^%w tells you: *$"))

Kjata

Newbie Joined: 03 Feb 2003 Posts: 5 Location: Germany

Thanks. That did the trick