MUSHClient 3.42

Yes, I know, I have a very old version of MUSHClient. But I'm not really looking to upgrade.

I actually don't know if this is a bug or not, but I wanted to report it anyway. While on one of my MUSHes, an odd output appeared in the window:

\
]'/;HJK]
]'/;HJK]

I don't know what this is, or what it might mean. Does anybody else know what this could mean?

~*Dari

WHy?

Well upgrading usually offers you this:

• Fixes old bugs
  
• Adds new features
  
• Fixes the occasional crash
  
• Works faster and fixes possible memory leaks
  
• Is backwards compatible
  
• Is free, naturally

Having said that the characters you see are probably something like the 256-colour ANSI codes that were introduced quite a while back. The MUSH may assume that the client supports them without checking.

Of course, now you have reported the "bug" all I can say is that it is probably fixed in newer versions.

What you could do is download and install the latest version into a new directory (choose a different installation directory). Then copy your world file(s) and any relevant other files like plugins from your old directory to the new one (copy, not move).

Then try the new version and see if you have any problems with backwards compatibility. If not, stick to that.

If so, and you don't want to resolve them, if you paste here a "packet debug" of the sort of message from the MUD that causes it, it might be possible to make a plugin that works around it.

I'm not looking to upgrade because the last time I did, I found that the new version didn't support accented characters, which a MU* that I play on utilizes. It didn't show a square, or something weird. It just didn't register a letter as being there.

I also don't like to change. XD

All I was really worried about is that these weird characters might have been indicative of an attack on my computer. Now that I'm sure they're not, I feel a lot better. Thank you! <3

~*Dari

Oh OK, although that should be fixable by some combination of fonts and configuration options.

As I said, it is quite likely some kind of query from the MUD, or unsupported output method, but to be sure (if you know when it will happen) turn on "Debug Packets" (Edit menu), capture the offending text, and turn off "Debug Packets" afterwards. Then paste the relevant packet here.

I haven't had the strange output pop up again, and I'm not really sure when -- or if -- it will happen again. I sent a @mail to the coding staff on the MUSH and asked if they know what might have caused it. When/if I get a reply, I'll let you know what they said.

~*Dari