Zugg Software :: View topic - [2.24] - [2.26] Garbage characters appearing instead of color change

Magician Joined: 09 Oct 2003 Posts: 459 Location: USA

Intermittently, at various points where color changes should be happening, I'm getting the attached issue. I've only recently swapped to using Cmud fulltime, but I'd not seen this in zMud previously. It was doing this in 2.23 as well.

It usually shows the garbage characters (which I presume are probably ansi chars or some such) instead of doing a color change, however not always. It will do it several times in only a few lines and other times it will go hours without doing it again.

Edit: Updated Title to reflect still active in current version.

Posted: Fri May 09, 2008 3:48 pm

what about 2.25?

I used to see similar with mxp not being converted in time, but not for a few versions (that i noticed).

Posted: Fri May 09, 2008 4:13 pm

Also, turn on the raw input/ouput option in the script debugger and paste a bit from when it happens.

Magician Joined: 09 Oct 2003 Posts: 459 Location: USA

Yeah, I had this post partially written for two days. I just finished it this morning and saw that he'd updated versions between when I started and finished.

Yeah, it's still doing it in 2.25, but I didn't have raw format turned on when it did. I'll see if I can catch it again.

Posted: Wed May 21, 2008 7:55 pm

Sounds like a network packet boundary issue, so I'll definitely need a raw input capture to reproduce it and see what's happening.

Magician Joined: 09 Oct 2003 Posts: 459 Location: USA

Here is an example of this issue where I had the debugger log open. In 2.25 it was causing an error when these things happened and the script debugger was open (I sent you the crash logs of those) and as such, I didn't trust submitting those logs. However, those particular crashes no longer happen in 2.26 so here are the logs.

Posted: Fri Jun 06, 2008 5:27 pm

Thanks for the log information. I'll test that and see if I can reproduce it. CMUD is already supposed to handle packet breaks in ANSI codes, but if this happened in zMUD too, then there might be a hole in my algorithm for it.

Posted: Tue Jun 10, 2008 10:21 pm

OK, I was able to reproduce it and fix it for 2.27.

zMUD and CMUD *were* handling the packet boundary correctly in most cases. In your case it was very obscure. Because of the < character at the beginning, it was looking to see if "Mazer" was an MXP tag. When it got to the end of the packet and determined that it was not a valid tag, it tried to reset the line, but didn't save the partial ANSI code at the end of the packet.

So this really only happened in the very specific case that you mentioned and was not a widespread bug/problem. But thanks for reporting it since I never would have caught it myself.

Magician Joined: 09 Oct 2003 Posts: 459 Location: USA

Thanks. I'd just blamed packet drops and such in the past for the ansi codes messing up. I'll let you know how the new algorithm works out.

Edit:

And yeah, due to the way the channels on SWmud are labeled, I've gotten some interesting bugs with MXP (as I've posted in the past).