Pueblo exit links - work in one screen, but not in the other, same MUSH.

Hi,

I nearly put this on the Pueblo section but I think it's a bug so I'm putting it here.

I've been on the OGR eccles.tzo.net 670 for years, my world file has seen many MushClient updates. I wanted to test something and so I logged onto the OGR as a Guest (using the Quick Connect feature). I was surprised to see that the OGR was, in fact, using Pueblo tags for objects and exits. That wasn't the case for my old world file.

So, sure enough, I dig up the correct settings and active Pueblo on my normal world file. I match the Pueblo settings (and other Output settings too) with the newly created guest screen with my old world file.

The two windows are rendered differently though.
Everything works fine on the Guest screen. All hyperlinks appear as they should be. On my usual screen it nearly works - only the exits appear as " ">Gaming (W) ">Discussions (N) ">Lecture Room (E) ">Consultation Room (U) ">Crossroads (S) "

I don't think it's the OGR's problem since everything works fine when I connect in the new screen. Is there a problem in turning Pueblo on in old world files?

There is a problem in some Pueblo implementations - some of them put ANSI codes inside tags, eg. something like this:


<send ESC ]0m > North </send>


The ANSI code (ESC ]0m) is not supposed to be inside a tag, it doesn't make sense there.

Probably what you are observing is because for one character you have ANSI colour turned on, and not for the other, so the extra codes are being output, which is corrupting the processing of the exits.

Turn the MXP "debug level" to "warnings" and you will see warning messages about this.

To fix the problem properly the MUSH should be changed slightly so the ANSI code is not inside the tag, eg. like this:


<send> ESC ]0m North </send>


I'm really pretty sure that I'd matched both worlds. I've just been playing around with the ansi - but with little luck.

I'll note that it is just the exits - people Pueblo correctly.

I've given the local coder a heads up and included the URL to here. I do recall saying he'd been unable to test it himself (I'm sure I mentioned he should consider upgrading to MushClient :) ) and so it'll be interesting to see what effect might be achieved if the code on the exits is given a brush down.