// If MXP negotiation failed, prompt the user:
MXP is <not>being parsed!
Is MXP being parsed (y/n)?
// If they answer yes at this point, turn MXP on.
Welcome to the mud!
Automatically checking for MXP (this may permanently kill your local echo)…
MXP wasn't detected, so we'll ask instead. Does your client support MXP (y/n)? y
Sorry, the mud doesn't use MXP.
Enter your name:
Welcome to the mud!
Automatically checking for MXP (this may permanently kill your local echo)…
MXP wasn't detected, so we'll ask instead. Does your client support MXP (y/n)? y
Sorry, the mud doesn't use MXP.
Enter your name:
That makes sense, but surely that would be a huge problem for zMUD users? Using angled brackets for syntax is pretty common, while MXP support is relatively rare, so I could see many muds running into the same problem.
Perhaps it's just checking the login screen, but even that would cause problems with ASCII art and such. Unless it's checking the login screen for an alphanumeric sequence between angled brackets, or something wierd like that…
I'll have to try and find a player who uses zMUD and see if I can get them to repeat the problem.