Materia Magica - problem with the compass

Hello :)

I have a little 'cosmetic' problem with Materia Magica's compass (where it shows the visible exits in a compass format).

For example, I see this:

A Shady Inlet - - -
(------------------------------------*Forested*---) - --(M)---> E
SW S SE
Visible Exits: E S Sw Se

(...)

instead of this:

A Shady Inlet - - -
(------------------------------------*Forested*---) - <---(M)---> E
SW S SE
Visible Exits: E S Sw Se

(...)

This seems to happen when I enter a room via recall, flee, blink, warp, or any other non-walk method.

Not sure if it's a client setting. But I tried with a clean world file (standard, without importing settings from my current world file), and it's doing the same.

Thanks in advance,

R.

Sorry, my text capture didn't show very well :/

Here's a html capture:
http://d00m3d2di3.40gigs.com/captures/mm-compass.html

You need to disable MUSHclient's MXP support. Go to Game -> Configure -> MXP/Pueblo and make sure that the "Use MXP/Pueblo" dropdown is set to "No - never". (Also let me know what it was set to originally)

[EDIT]: For the record, you can use [code] and [/code] around your preformatted text to preserve the spaces. Like so:



(You can click the "quote" link to see how I did it.)

Oh, I see. MXP is on. Sadly I use it (scripts, etc.).

Thank you :). Also, for reminding how to paste code. I'd forgotten about it :x

Sounds like a bug in the MUD then, as all < and & that aren't used for MXP should be escaped as &lt; and &amp;.

No problem!

Sounds like the usual, "It worked in zMud, so we didn't bother to realize that zMud ignores its own specification when dealing with some cases of '<'."

Ah, Materia Magica again. :)



In that, I sigh and say:



Then there is a lengthy discussion about MXP.

You could try this:



In that is a plugin that tries to detect "valid" MXP and if it doesn't look like an MXP tag convert < to &lt; etc.

That might help you.

To be fair, I think the best behavior is to treat nonexistent/broken tags as visible text instead of hiding them. Browsers have all sorts of ways to deal with malformed HTML, even.

I don't know how zMUD or MUSHclient handle it (I didn't really explore that part of the code), but it seems like a sensible fallback.

[EDIT]: That's not to say that it's a good idea to exploit behavior that's not specced, and MM is still clearly at fault. :D

Hmm... the plugin is not working in this case, but you gave me an idea.

I made a trigger that "gags" (omit from output) the broken line and replaces it with a fixed one (using TriggerStyleRuns/ColourTell, etc.). Ugly but effective. :3

Thanks again ^^

Crude though it is, that plugin should work. I tested it on your example in your first post and it did indeed make the map appear OK.

Then I'm doing something wrong :/

Here's a sample output, with MXP_Tag_Fixer (2nd version):

Are you fixing the tags twice? Make sure you don't have two such plugins installed. If MXP is enabled then you shouldn't see the &lt; unless it got processed twice.