Zugg Software :: View topic

Newbie Joined: 08 Mar 2004 Posts: 1

okay I've been trying to color in different channels with this trigger:

#TRIGGER {city} {#COLOR red}

so I get...

(city): blah blah blah blah...

but when it is

{city): blah blah blah blah blah blah blah blah blah blah blah blah
blah blah blah blah blah blah...

then I only get

(city): blah blah blah blah blah blah blah blah blah blah blah blah
blah blah blah blah blah blah...

is there some way to make both lines (or more lines, some people say a lot over channels...) all change color?

Thank you...

Novice Joined: 30 Jul 2003 Posts: 36

http://www.zuggsoft.com/forum/topic.asp?TOPIC_ID=15298

Same type of problem I am having with mine.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

The solution is fairly obvious, but usually not worth doing.

1. When you receive the desired pattern, enable a trigger which #COLORs everything.
2. Use another pattern to disable that trigger when you detect something which indicates the end of the communication.

#TR {city} {#T+ citycolor}
#TR citycolor {*} {#COL red}
#TR {...$} {#T- citycolor}

You'll have to find the necessary patterns yourself. I used the three .'s that your examples end with but I doubt that you'll find them in actual communications.

These usually don't work very well. Most MUDs have commands of their own for setting channel colors, and it's much simpler to let them do it.

Beginner Joined: 21 Oct 2003 Posts: 21 Location: USA

Speaking of this trigger..I just want to confirm that I am setting this up right (and get guidance if I am not).

If I want to change the color of tells to me, my thought is:

#TRIGGER {tells you} {#COLOR red}

I'm at work, so can't test it...but my question is: does it just look for the "tells you" language, and colors everything after it, or will I need to do some kind of variable before it to account for different people...like "Bob tells you blah" or "Cathy tells you hello".

Thanks!

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

#COLOR affects the entire line. That includes words which come before the pattern and words which come after the pattern, as well as the pattern itself. There's no need for any wildcards, "tells you" will work fine by itself.

Beginner Joined: 21 Oct 2003 Posts: 21 Location: USA

perhaps a dumb question...unless it's the MUD itself that's preventing the coloration...

but I've tried the following combinations:

Pattern: #TRIGGER {gossips} #COLOR {red}
value:
(this didn't result in any change)

Pattern: #TRIGGER {gossips}
value: #COLOR {red}

(I believe that's not right, but wanted to mention that i tried it)

What am I doing wrong..or could it be the mud itself?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

You are trying to force the command-line syntax into the settings editor. When you create a trigger in the settings editor, you've already defined it as a trigger, so there is no need for the #TRIGGER command to define it as a trigger. All that's needed is to supply the remaining parts of the command.

Pattern: gossips
Value: #COLOR red

Beginner Joined: 21 Oct 2003 Posts: 21 Location: USA

ahh ha..

works like a charm now ;)

many, many thanks :)