Zugg Software :: View topic

Posted: Wed Feb 20, 2008 10:48 pm

Okay, so I'm trying to make a trigger that replaces colored text with text and a number. For example.

Your slash wounds a wombat.

to

Your slash wounds (19-23) a wombat.

Now that's very easy to do with #SUB, and I get the desired results.

However, if anything else says "wounds" then I get the (19-23) beside it, and that's just not going to work.

I am trying to use ANSI Trigger and followed the instructions for it, copying and pasting the red wounds message into the pattern box, but it never works.
It looks like this:

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Try putting a ~ before the ['s in your pattern.

Posted: Thu Feb 21, 2008 1:29 am

Well it makes the test pattern happy but it doesn't actually trigger in game. Very strange.

Wizard Joined: 17 Jun 2006 Posts: 1201

I'm curious why you are using an ansi trigger if you don't want it to trigger on any other "wounds" anyway and are just subbing that specific trigger pattern? The numbers you are including are damage done? Can't you just sub your attack message and then include the number in the sub?

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Hrm... Try putting another ~ before the ;

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

Um, no. You shouldn't be using ~ inside the escape codes.

I have a colour trigger that works under cmud to grab comm lines.
It is:

#TRIGGER {%e[35m(%x)} {#CAP comms;#GAG}

which grabs lines of a specific colour that is only used by comm lines.

and yeah, under the test pattern, I see '35m' as well. still works fine.
And .. no, I cannot cut and paste to test the trigger either, because the colouring doesn't carry across.
Maybe something that needs fixing in a future version.

You probably don't need the '%e[0m' as that is just a code to change the colour back to normal.
Try checking to see what gets actually sent from the mud ...
You can do this by turning on the Script Debugger, or logging with ansi codes on to a file.
If all combat messages are similar to the example, it might be easier writing something like:

#TRIGGER {^Your {slash|slice|dice|cut} wounds} {do trigger stuff}

Finally, a few ppl (me included) have problems with ansi triggers in that sometimes the escape sequence comes in as a '%e[OS' instead of the proper escape sequence. Hopefully fixed in the next version.

Posted: Thu Feb 21, 2008 11:23 am