Zugg Software :: View topic - [3.04] Ansi colors from mud occasionally get messed up.

Wizard Joined: 22 Mar 2007 Posts: 2320

I see that 3.04 is doing something different with ansi colors. Among other things, it isn't inserting an %e[0S at the beginning of every normal line. Hopefully it's some silly bug in this change which is causing the following problem. In certain large blocks of ansi-colored text from the mud, one ansi code gets messed up. Here is an extact from the debugger window showing the messed up line:

Posted: Tue Mar 10, 2009 7:25 pm

Looks like a bug with the ESC [2z code. Somehow the ESC is being dropped. The ESC [2z code puts the line into "MXP locked" mode, which prevents MXP tags from being parsed. In 3.04, MXP was changed so that only MUDs that specifically have MXP enabled via Telnet option negotiation get parsed as MXP. The way CMUD implements this is to insert the ESC [2z code at the beginning of the line to turn off MXP parsing for that line.

You can turn this off by going into the MXP Preferences and turn on the "Force MXP on server" option. This should remove the ESC[2z and you can check to see if this is responsible for the ANSI problems. That should make the debug output for 3.04 look the same as 3.03.

Let me know if this fixes the problem. But I'll add this to the bug list to determine why the ESC is being dropped before the [2z code.

Posted: Tue Mar 10, 2009 7:34 pm

Also, can you please turn on the "Raw input/output" message option in the Script Debugger so that I can see the exact data that the MUD is sending that is causing this problem? According to my code, the ESC should be getting sent, so I cannot reproduce this. So I think this is being caused by a network packet boundary in the text from the MUD.

Wizard Joined: 22 Mar 2007 Posts: 2320

If you mean the "Force remote MXP" option, yes, that does seem to fix it. I turned on that option, and the problem disappeared. I turned the option off again, but the problem did not reappear. When I closed the session and reopened it, with the option turned off, the problem reappeared.

Here is the debugger info with all message options turned on, including raw input/output. I should have realized that would be helpful. You are right, there's a packet break right at that point in the block of text, in fact right in the middle of the ansi code.

[edited--adding the right block of text]

Posted: Wed Mar 11, 2009 4:41 pm

Yep, definitely a packet break problem. Should already be fixed now for v3.05. Thanks for catching this one.