Zugg Software :: View topic

Novice Joined: 01 Jun 2005 Posts: 47

Hello!

Cmud color recognition on triggers is a great feature, but I have found already 2 colors with which it will not work.

Here are the colors:

http://i33.tinypic.com/wttzs5.png

http://i33.tinypic.com/rw0y10.png

What I mean by not recognizing is that on the pattern, the color code is this one:

%e[0m

For both, which actually cant be, and triggers dont work with thoose patterns.

Is there any other way to go with thoose?

Thankyou.

Edit:

For example, when I set an ansi trigger, and copy/paste a line with some of thoose colors, trigger will be:

%e[1;36m %e[1;36mConjuro: 'presencia' modifica%e[0m

And trigger wont work when that same line goes out on the mud, while other ones do.

Posted: Sun Nov 09, 2008 2:20 pm

Open the Script Debugger (it's on the Window menu) and enable i messages - the "Show raw session input/output" option. Then do whatever it is that makes these lines appear, and paste whatever shows up in the script debugger here, preferably inside code tags.

Novice Joined: 01 Jun 2005 Posts: 47

Cant get any results yet (no time) but ill research more on this and post my conclussions and what i get to do.
Thankyou.

Novice Joined: 01 Jun 2005 Posts: 47

Still dont understand very well how this works, but worked for me this way:

Line appeared on the debug window:

<9><ESC>[0;1;36mAfected by blabla<LF><CR><LF><CR>

Line used in the pattern:

%e[1;36mAfected by blabla

And dont ask me how or why that works ^^

In fact, a little question more:

where to find about the exact syntax of colors??

%e[1;36m means a color is starting there?

Can I use that again to start another color on the same line? For example %e[1;37m ??

What does %e[0;36m (with the 0 instead of 1) mean?

Btw, the topic question is already answered, this is just for the little smartass. (not sure if thats the word).

Thankyou.

Posted: Sun Nov 09, 2008 11:24 pm

CMUD's ANSI triggers don't use the actual ANSI codes the MUD is sending. This sounds a bit perverse, I know, but MUDs often send incorrect or invalid or unnecessary codes, which can cause problems. For example, in the text you posted, the incorrect code <LF><CR> is used to represent a new line. The correct code is <CR><LF> - a small distinction, sure, but an important one.

What this means is that making you trigger off the codes the MUD is sending can be unreliable. What CMUD does instead is clean up the codes that the MUD has sent and then pass these cleaned-up codes to the ANSI trigger engine. This is somewhat unfortunate, because you never really know exactly how CMUD is going to clean up the codes - the only truly reliable way to create an ANSI trigger is to check the "ANSI Trigger" box and then paste in something you copied from the buffer. Doing this will produce a pattern with the correct ANSI codes.

In short, as long as you copy your text from the buffer and paste it into a trigger with the "ANSI Trigger" option checked, your codes will be correct.

As for your question about continuing ANSI colours, ANSI colours continue until they're changed. The 0 colour code resets the colour to the client's default. All lines should end with a 0 code, something else your MUD isn't doing.

Novice Joined: 01 Jun 2005 Posts: 47

Thankyou Fang Xianfu.
Learned a lot hehe.

Newbie Joined: 07 Nov 2009 Posts: 6 Location: Washington

Oh goody! finally I will be able to reliably trigger and insert mxp tags for the mapper and other things like redirect! I don't know why IRE muds aren't taking advantage of them, but they're not.

Posted: Tue Nov 17, 2009 5:47 pm

I know that IRE is looking into MXP, so definitely send them email to let them know that you are interested in seeing these features implemented. The more they hear from their actual players, to more likely they are to add those features.