MXP problems

Sorry to bother again, but when trying to use MXP with a certain world, I ran into trouble.
Most of it works perfectly fine, however it seems that each and every < will get interpreted as a tag opener.
This means if I e. g. issue command say lalala <blah> lala, i will get an MXP error and the <blah> part will never be displayed on my screen. From what little I know of MXP, I think this should not be the case, since certain escape codes must be in the stream before a < to be interpreted as an MXP tag?
The world in question also has channel messages like
<-<login>->: Khosan has left Islands of Myth.
etc. so with the issues I'm having, I will error sort of permanently as long as MXP is turned on, based on what other people do... also triggers can get "broken" since I'm trying to capture such channel messages to different windows/notepads.
I have no idea whether this is the fault of the mud or whether it's a bug in mushclient. Unfortunately I think I lack capabilities to track things down either since I don't know the protocol well and the MUSHclient source for MXP is probably not easy to follow just on the fly either.
I'm using 4.45 and the world in question is islandsofmyth.org 3000.
It would rock if somebody could have a look into this and tell me what I'm doing wrong (maybe there are possibilities to configure things that I don't know of) or what's the problem.

Thanks

From what little I know of MXP, only MXP tags with a certain escape sequence before it are recognized as MXP; if it's a raw <, it should be interpreted as a normal <. It sounds like either the server is sending <'s that have been accidentally MXP-escaped, or the client is treating all <'s as MXP regardless of circumstance.

I can't say which it is one way or another, myself.

This is a long-standing problem. Basically some MUDs do not implement MXP properly, because things like <blah> should be sent to you as &lt;blah&gt; because the < and > symbols are used for MXP tags.

However because zMUD just displays tags it doesn't recognise, MUD developers have got away with doing it improperly, and don't notice if they test with zMUD.

However MUSHclient treats such things as an error, which you can see if you turn on "MXP debugging" in the MXP configuration screen.

There is another post about this:



And quite a few more. :-)

I think there was a plugin a while ago that might detect MXP tags that don't exist and convert them back into &lt;blah&gt; (for example).

You could try discussing it with the MUD in question, however past experience has shown you may not get much sympathy.