Zugg Software :: View topic - #capture, Multi-Line, #cond, Colour...

Newbie Joined: 22 Feb 2006 Posts: 9

Hello again ;)

I would like to start off saying I've been scanning the past posts on the subject(s) for several hours now in total and can't seem to find just the solution I need, nor parts of it that I can combine myself then...

I might be overlooking it, if so, I'm sorry and being pointed to the right post would be very welcome :)

But, in case the solution is simple enough to be posted here, don't let me stop you :D

My problem is that my MUD does line-wrapping (and I really don't want to turn that off and let zMud do it), so I am now trying to capture tells and channels that are on multiple lines

They have no clear defined endings, except that the colour changes on different messages...

Some sample MUD output might help:
CHAT:Bendario: That IS a scary thought :) Why no bosses? Meetings?
CHAT:Bendario: What would cause Dex to go down?
CHAT:Elastica: they quit cos Grommet is the uber boss.
CHAT:Bendario: Ah
CHAT:Elastica: Grommet = David Brent
Eureka tells you: no prob
You tell Grump: it's very simple, just keep going onwards and when the npc starts blabbing nonsense, wear the helmet and
it will make sense again :)

(columns is set to 120 in my case)

After a channel or tell or anything, there is no guaranteed prompt to show up, or anything indicating the msg has ended, except that the next line either has a different colour (my tells a green, my chats are cyan), or the next line starts again with one of those msgs of course, another tell, etc...

I figure using #cond is needed here, but I'm just not sure how to say: when this pattern happens (You tell (%1)), capture everything until you get either a msg in a different colour (no longer green) or if it's another tell (in which case the same trigger can grab that)

Sorry for such a long drawn out post, it seems to be my way... I truly hope some solution can be made for this...

Many thanks in advance :D

Posted: Wed Mar 08, 2006 5:27 pm

Try something along the lines of

Newbie Joined: 22 Feb 2006 Posts: 9

Phew :)

I managed to refind the post I initially got the hint from, the post pointed here http://www.zuggsoft.com/library/trigadv.htm to the section about resetting triggers, the example about the Inventory capture trigger almost does exactly what I need :)

My one search now is brought back to finding a way to put in that #temp trigger that fires when a line is NOT a certain colour (green in my case)...

So right now I just need a solution for:

Newbie Joined: 22 Feb 2006 Posts: 9

Hello :)

For all the people that happen to care how this goes... I actually managed to get something myself with some effort... Still not fully there, but now I have:

Novice Joined: 20 Jul 2004 Posts: 38 Location: Australia

I have a similar situation on the mud I play.

Due to some items and monsters generating text in various colours, and me being too lazy to generate an exception list, I set the mud to send all tells in underlined and chat lines in reverse video as that is not used for anything. Next I capture any lines of reverse video or underlined from the mud and send that to my comm window.
Then, in the comm window, I recolour and highlight the different chat lines and tells, which all works nicely. One little bit of fiddling I have to do is to set the colour for the current chat line, and when a new chat line appears, change the colour accordingly, so as to allow for multiple lines.
This works because each line has the escape code at the begining of the line.

Chat lines on my mud have a header at the start like:

[SM] Luggage: Hello
[<Newbie>] Luggage jiggles his foot.

Anyways, what I have is a seperate window labelled 'comms'

I put all my comm stuff in a seperate class called 'XTRAWindows'

Firstly, capture any tells from the mud and recolour them bold red, gag the original...

#TRIGGER {%e[7;32m} {
#COL bold,red
#CAP comms
#GAG
} "XTRAWindows" {color}

Next, for the comm lines. I use a variable for the current colour..
Then I check to see if a chat line header is present at the beginning of the line, and reset the colour accordingly. If no chat line header is present, then the line is part of a multiple line chat message, so keep the same colour. For some reason, I need to add in a variable that I called 'comm_check' to match up the comm line headers instead of being able to use %1. I think it is because %1 is stored differently than a text string, but... this works fine, and I'm too lazy to rewrite it.

#VAR cur_colour {blue,bold} {_nodef} "XTRAWindows"
#VAR comm_check {[sale]} {_nodef} "XTRAWindows"
#TRIGGER {%e[4;32m(%x)} {
#VA comm_check %1
#IF (@comm_check = "[SM]") {#VAR cur_colour "blue,bold"}
#IF (@comm_check = "[<Newbie>]") {#VAR cur_colour green}
#IF (@comm_check = "[sale]") {#VAR cur_colour grey}
#COL @cur_colour
#CAP comms
#GAG
} "XTRAWindows" {notrig|color}

Finally, a check to see if the line started with a space (as the space character is not included in the %x). In this case, the line is definately the next part from a multiple line chat message.

#TRIGGER {%e[7;32m} {#COL bold,red;#CAP comms;#GAG} "XTRAWindows" {color}

And that is basically it. If you have other text generated by your mud in the same colour as your tells or chat lines, use an exception list, something like #IF %x in {list of strings}, then ingore..

Hope this helps,

Luggage

--