That did the trick, thanks!

Turns out this was likely a cut and paste error that has gone unnoticed for 15 years because Mudlet was the first client to care about the difference.

Hi.. Yes, I did try the latest version. I can probably work around anything else if I can just know that mudlet is connecting. Here is a summary of the telnet negotiation going on. You can see that the subnegotiation is sent.... twice, in fact. However, it doesn't appear that a response is ever rece...

Not sure this is the right place, but I would like to request that a future version of mudlet respond to the Telnet TERMTYPE sub-negotiation request. "mudlet" would be a suitable response, imho. But, anything, really, is fine so long as it's unique. This would allow server developers, such...

Hi!
You are correct, if, in Step 2, the Client responds with DONT MXP, then not only is MXP turned off on the server side, but it is also ignored in the user profile when they log in. If the Client says DONT MXP, it is respected.

So, MXP has a telnet handshake to turn it on and off. After it is turned on, MXP has another special negotiation to set its Mode (Open, Secure, or Locked). CoffeeMud turns MXP on immediately after connection (if the client allows) in order to show fancy pictures and stuff. Then later, after login, C...

Dude, I just noticed that mudlet is on git and is open source. I'm an idiot for not knowing this. By perusing the code, I've already come up with the server-side fix for the MXP problem: Tell the client to go into MXP Locked mode. This is basically what the client should do anyway as soon as Mudlet ...

Hi, As I mentioned before, I did try doing the WILL/DO TTYPE handshake before sending the TTYPE sub-negotiation, but that also had no effect on Mudlet 3.0.0delta. The client never responded. And why would the server need to send " IAC SB TTYPE SEND IAC SE" multiple times? Is the client har...

Thanks for your response SlySven! Are you sure about the TTYPE thing? I have a wireshark pcap showing the server sending the following bytes: 0000 8c 89 a5 c6 d8 07 00 24 1d 1d e8 86 08 00 45 00 .......$ ......E. 0010 00 5e 36 c2 40 00 40 06 80 36 c0 a8 01 0a c0 a8 .^6.@.@. .6...... 0020 01 47 00 17...

So the Server is given permission to turn MXP ON by Mudlet during Telnet Sub-option negotiation - after all, the server MUST treat the setting, like ALL sub-options, as being OFF until it and the client agree to it and then enable it ...! I'm not too familiar with MXP but I am aware that Mudlet's i...

... Please provide all feedback and problem reports on 3.0.0-delta here! Feature requests can be done in our dedicated thread . Bug report in 3.0-delta Less-Than-Signs are confused with the beginning of MXP tags in the following situation: 1. MXP is activated through handshake (server sends WILL MX...