I want to see my brackets!

My Mu* has exits like this:

Out <O>

I see them like this:

Out O>

How can I see them with the bracket < as it should be?

Thanks.

Ps: I use mushclient version 3.65

I'm pretty sure MUSHclient doesn't remove brackets like that. Maybe MXP is on, and is interpreting it as MXP? Try turning off MXP.

Yes. That is likely the issue. zMud's own standard says *very* clearly that < and > in normal text *must* be replaced with &lt and &gt, but.... zMud itself ignores this requirement. Since most people who add MXP to their muds use zMud as their test client, what should be an error, i.e. using < and > as text, not an MXP tag, is instead displayed as though nothing was wrong. Mushclient follows the spec and assumes that anything in between < and > that isn't a recognized command *must* be an error. You Mu* is obviously one of the many that incorrectly assumes that they can simply ignore the requirement, since it works fine in zMud.

I can't help but think of this like the way HTML developed. IE has the worst standards compliency in any browser, but until very recently everyone used it as a test platform for determining if a page worked anyway. Some fools still do, and as result, those pages don't work right in any other browsers, even though they often contain nothing specific to IE, they just don't follow standards. In this case, the irony is that the "original" client that supported the standard must be assumed to be screwing up, unless and until Zugg ever bothers to ammend his own specifications to say that invalid information should fall through (like your MU* apparently expects), or if Mushclient is in fact correctly handling the mistake.

I assume the MUD uses MXP? Otherwise you wouldn't have the problem.

It is amazing how many MUD developers have buggy MXP code, so that they are sending <O> when they should send:


<O>


... when MXP is enabled.


You could conceivably write a plugin that forces < to &lt; when it is not followed by a valid MXP name, but what about this:


Exits: <I>n <B>ank <U>ndertaker


All these are valid MXP codes:

• <I> - italics
• <B> - bold
• <U> - underscore

That means such lines will be rendered incorrectly and there is nothing the client can do to fix it.

I suggest you post a message to the admins of the MUD suggesting they fix up their MXP implementation.

I have a page describing how to do that here:


http://www.gammon.com.au/mushclient/addingservermxp.htm


Even if they don't want to change everything, they can at least fix the code that does exits to make them work properly.

You know what the strange thing here is? If the MUD was really in MXP mode MUSHclient would drop that altogether as an invalid tag. So you wouldn't see O> you would see nothing.

I would be interested to know what the MUD is so I could see for myself what they are actually sending.

This *will* happen in case like <<O>>. In such cases both < characters are lost, but the last > is preserved, since the testing for the tag resets after the second < is hit. No idea why it would be doing with only one pair though, assuming we clear up the clearification of what is correct behavior in the first place, as per my other post on the subject.

How do I try turning off the MXP thing?

By the way, I have tested with the new version of Zmud and Simplemu. Z-Mud has MPX enabled AND I can see the brackets just fine.

Nick, I think we have a friend in common, we used to RP at the same mu*.

In any case anyone interested in checking the mu*s I RP at, please e-mail me privatelly.

Thank you.

My test shows that in this case you only see the trailing >.



Can you tell me the ip/port of the MUD? I'd like to see for myself what is happening. You can send me a message through the forum if you don't want to say it here.



In MUSHclient, go to Configuration -> Appearance -> MXP/Pueblo. Alter the "Use MXP/Pueblo" setting.