Zugg Software :: View topic

Posted: Wed Nov 12, 2008 2:58 pm

You need to open the Script Debugger and turn on the Raw Input/output message and then try to capture this happening in the debugger so that I can see exactly what control codes the MUD is sending and exactly where the network packet boundaries are. My guess is that it's a network package boundary.

Wizard Joined: 17 Jun 2006 Posts: 1201

Posted: Wed Nov 12, 2008 8:23 pm

Hmm, I don't see anything in that example that would cause the line break that you mentioned in the original post. Are you sure the line break after the "35e" happened with that specific debugger output?

The only thing unusual that I see is that you have a command #input trigger that is firing. You might try disabling that to see if it has any effect.

Wizard Joined: 17 Jun 2006 Posts: 1201

Well in that example the prompt ended up just like it shows there as the following:

3500h, 3850m, 16394e, e
16400w cexkdb-

It's just random. Here it put the "e for east" toward the end and cut the rest of the prompt and put it on the next line of display.

The input trigger is for when I move it resets some stuff. I'm not sure else how to do that. If you have an idea on how I could reset something only when I move let me know.

Posted: Thu Nov 13, 2008 5:15 am

OK, looking at the debug output more closely, I can see that there definitely was a network packet break between the 16394e, and the 16400w. In fact, it was a packet break in the middle of the ANSI color sequence.

So this is normal. CMUD cannot tell the difference between a packet break and a MUD prompt. On your specific MUD, the MUD is using the IAC EOR to mark the end of a prompt, but many MUDs do not send anything at all at the end of a prompt. So CMUD allows any output generated by your script or command echo to be displayed between packets. As far as CMUD can tell, it is adding the "e" movement echo to the end of a prompt.

While a future version might add more support for IAC EOR/GA codes to better handle the end of prompts, the current version is working as designed.

There might be ways to mess around with your network buffer sizes to reduce packet splitting, but I'm no expert on that. I don't believe the MUD itself is splitting the packets, so it's something between the server and your computer. Anything is allowed to break packets, but most network devices are set with large enough buffers that it's not that common. So it might be something your ISP is doing, or something in your Windows network settings. Somebody else might be able to offer more help for that.