Zugg Software :: View topic

Novice Joined: 01 Dec 2007 Posts: 49

Problem: When utilising ATCP functions (IRE muds) and having telnet triggers, a problem that in the past has come randomly is that the normal prompt output can end up messed at times. I've never been able to catch it properly before.

In General, the prompt should look like:
H:272 M:372 E:1264 W:1761 <eb>

Using the telnet trigger, without the #SAY involved, it messes up randomly with:
37m E:1264 W:1761 <eb>

In the case of the #SAY, the problem kept occuring on every line.

SCRIPT BEING USED:

Posted: Mon Apr 20, 2009 5:34 pm

You should never output any text during a Telnet trigger. The problem happens because of network packet boundaries in the data received from the MUD. When processing a Telnet trigger, CMUD is in the middle of processing this network packet and any text that you output will interfere with the network data stream, preventing CMUD from handling packet breaks properly.

So, if the problem also happens when not using #SAY, I would need to see the full ATCP trigger that you are using to determine what might be interfering with the network packet boundary handling code.

Finally, when posting the output from the Script Debugger for problems like this, you must ensure that you have the "Show Raw Input/Output" message turned on in the debugger. That's the only way for me to see the network packet boundaries.