Zugg Software :: View topic

Apprentice Joined: 06 Apr 2004 Posts: 173

sorry the forum stripped some of the escape codes, it's better now

Posted: Sun May 20, 2007 8:42 am

Well ANSI colors are a little frizzed right now.

I'm hoping the last of color quirks will be addressed in the next version. With the colors being frizzed said trigger probably won't fire properly.

Basically when an ANSI trigger fires, it's not firing on the original ANSI but the recreation of it based on CMUD colors but this is what's frizzed. It's high on the list, so I'm pretty sure it will be resolved in the next version.

Apprentice Joined: 06 Apr 2004 Posts: 173

eh... so let me get this right... cmud processes the text, alters it, then will alter it again depending on the trigger... suppose that the result of the trigger were a #GAG, or a color change... then it would in effect be processed 3 times...

sounds a bit convoluted?

my two cents.
(ps criticism doesn't mean I don't appreciate what you're doing)

Posted: Mon May 21, 2007 5:31 pm

CMUD (and zMUD) always processes triggers based upon the actual text displayed on the screen. This was decided many years ago to prevent MUDs from messing up your triggers by just inserting random control characters (stuff that didn't effect the text display, but only added control characters to the input stream). So yes, Tech is correct that when you use an ANSI trigger, CMUD has to try and reproduce the original ANSI color codes based upon how the text looks on the screen. It does not save the raw input from the MUD.

I don't know what you mean by "processed 3 times". That's not true. Normal triggers are processed when a newline is received from the MUD. So it doesn't matter if you #GAG or change the color.

In any case, the problem is that the #REGEX command doesn't seem to handle escape codes properly. You need to use a normal CMUD trigger syntax for this:

Apprentice Joined: 06 Apr 2004 Posts: 173

by processed I mean that the engine has to look at it 3 times.
1 in preprocess removing/altering display codes
1 in matching the trigger
1 rendering the output text

whereas I was assuming that an ansi trigger could look at the text before a preprocess.
1 in matching the trigger
1 rendering the output text

I guess my version of the trigger would require a rewrite of the whole trigger pipeline and priorities setup, so probably too hard to impliment easily.

Posted: Tue May 22, 2007 5:01 pm

Yep, it's not going to change. And there really isn't any way to remove step 1 (preprocess to remove display codes) because it would still need to preprocess to handle MXP, MCCP, telnet options, and all of the other possible "hidden" codes that the MUD can send. For example, #GAG shouldn't have any effect on telnet options. So there really wouldn't be much savings in performance.

I'm not sure why the #REGEX command broke. I took a quick look at the source code and it looks like it should still be working with ANSI triggers. Maybe it's something in how the \ character is being handled. It's on the bug list so I'll look into this more in a future version.