Trouble with the '&' symbol

Posted by Kywyn on Tue 02 Jan 2007 08:21 PM — 6 posts, 18,954 views.

#0
After the '&' symbol on any line of text I see on the mud, nothing is visible after on that line.
Ex.

say test & test

shows: You say, "test "

I'm sure this problem has a simple solution that I can't see, mind helping a mushclient newb out?

-Thanks
USA #1
This probably isn't a problem with MUSHclient, but the MUD you are playing.

Or does this not happen on telnet/another client?
#2
This problem does not occur while using Telnet, I asked another mushclient user on the mud I was playing, who did not have that problem and was unable to assist me.

Anything else that could help me out here?
-Thanks again
USA #3
Do you have any scripts/triggers/etc? I can't think of anything else that would strip your output.

[EDIT] So not just sending it, but if you see & in the MUD it stops display too?
Amended on Tue 02 Jan 2007 08:34 PM by Zeno
#4
This is a bit bizarre.
I was looking through my script, triggers, aliases, macros, and etc. and I set my note colour [in the script configuration] to [default] and the problem disappeared.

Well, it's fixed.

How did it happen? I didn't have any triggers or anything set up besides the note colour. I want to make sure that something like this does not happen again.

-Cheers.
Australia Forum Administrator #5
I can't explain about the note colour, that sounds very strange. However until I read that bit, it seems to me that you have enabled MXP processing, and if that is enabled, MUSHclient tries to process something like &amp; as an ampersand (and &lt; as a < symbol, and so on).

Now if the MUD sends something that is not valid, like:

this & that

Then MUSHclient tries to interpret "&that" as an MXP entity, fails, and raises an error.


Try going to the MXP / Pueblo configuration window and setting MXP debug level to "errors", and then see if another window appears reporting errors when the problem occurs.

If you are not intentionally using MXP, or if the MUD is not sending MXP correctly, then you might want to set Use MXP/Pueblo to "No - never". That should stop it trying to interpret MXP characters.