Yes. That is likely the issue. zMud's own standard says *very* clearly that < and > in normal text *must* be replaced with < and >, 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. |