Pueblo Tags

Posted by Crystal Wolf on Sun 12 Aug 2001 09:27 PM — 5 posts, 18,432 views.

Crystal Wolf Sun 12 Aug 2001 09:27 PM #0

Perhaps I'm doing something wrong but...
No matter what I try to do to turn OFF the Pueblo/MXP recognition, I cannot get it to leave out tags that aren't actually ON the game. For example, with everything off, I still see NUMEROUS html/Pueblo tags. The exit names in the rooms in question, for example, contain the standard angle brackets for the exit aliases. With the "Detect Pueblo Initiation String" turned on, the formatting is only mildly incorrect: ">Nerat Hold <NH>
With the "Detect Pueblo Initation String" turned off, the formatting is COMPLETELY out of whack. The MUSH itself does have Pueblo support, but it is not being used actively. Is there something I'm missing? I've tried selecting "No Never", "On Command", et cetera, and I cannot make the formatting return to normal.
Help?

Nick Gammon Australia Forum Administrator Sun 12 Aug 2001 09:36 PM #1

Please tell me the MUSH address/port so I can test it for myself.

Turning off Pueblo detection does not guarantee that the MUSH won't send the tags, that is up to it.

Also, try setting the combo box "Use MXP/Pueblo" to "no - never".

Crystal Wolf Mon 13 Aug 2001 03:36 AM #2

The game address? threadfall.firstmagic.com 4201
I've heard from other players that the same thing has been happening to them - but only since they've downloaded 3.15. I'm running an earlier version at home (this is a borrowed computer) and it still works fine.
I've tried every configuration I can think of with regards to "Yes - always", "No - never", etc. It just makes it look weird in different ways each time.

Nick Gammon Australia Forum Administrator Tue 14 Aug 2001 02:55 AM #3

There is a problem on this MUSH with their implementation of Pueblo.

If you turn on the MXP "debug level" to "warnings" you will see a whole lot of warnings.

By turning on the packet debug we can see the problem ...


[0m..Obvious exi   5b 30 6d 0d 0a 4f 62 76 69 6f 75 73 20 65 78 69
ts:..<a xch_cmd=   74 73 3a 0d 0a 3c 61 20 78 63 68 5f 63 6d 64 3d
"OOC Room.[0m">O   22 4f 4f 43 20 52 6f 6f 6d 1b 5b 30 6d 22 3e 4f
OC Room.[0m</a>    4f 43 20 52 6f 6f 6d 1b 5b 30 6d 3c 2f 61 3e 20
 <a xch_cmd="Tut   20 3c 61 20 78 63 68 5f 63 6d 64 3d 22 54 75 74
orial.[0m">Tutor   6f 72 69 61 6c 1b 5b 30 6d 22 3e 54 75 74 6f 72
ial.[0m</a>..      69 61 6c 1b 5b 30 6d 3c 2f 61 3e 0d 0a

I have highlighted the problem parts in bold. They are sending ANSI "escape codes" in the middle of an MXP/Pueblo tag, which MUSHclient does not allow. To make it clearer, this is what they are sending, where ESC is the "escape" character hex 1B:



<a xch_cmd="Tutorial ESC[0m">Tutorial ESC[0m</a>

In the example above I have underlined the ANSI escape code. ESC [0m means "go back to default colours" - however it is not meaningful to put that inside a tag - the xch_cmd tag - because that tag is a command to the client to underline the next word and provide a hyperlink. You don't colour commands.

Thus it should look like this:



<a xch_cmd="Tutorial">ESC[0mTutorial ESC[0m</a>

Notice how in my corrected version the ANSI codes are now around the text itself, not inside the Pueblo tag.

I suggest you contact your friendly Wizard on the MUSH, and draw their attention to the problem, perhaps quoting this web page as a reference.

It would probably only be a very minor change to their code to fix it.

Nick Gammon Australia Forum Administrator Tue 14 Aug 2001 02:59 AM #4

Quote:

No matter what I try to do to turn OFF the Pueblo/MXP recognition, I cannot get it to leave out tags that aren't actually ON the game. For example, with everything off, I still see NUMEROUS html/Pueblo tags. The exit names in the rooms in question, for example, contain the standard angle brackets for the exit aliases.

It worked OK for me if I turned off "detect Pueblo initiation string" before connecting. It is too late to do it afterwards, because the MUSH has decided to send the Pueblo tags, and it isn't about to change its mind. Thus, uncheck "detect Pueblo initiation string", then connect, and everything should be fine.