Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to "verify" your details, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Entire forum ➜ MUSHclient ➜ Bug reports ➜ MXP issue with Materia Magica

MXP issue with Materia Magica

It is now over 60 days since the last post. This thread is closed. Refresh page

Pages: 1 2 3

Posted by Deacla USA (42 posts) Bio

Date Tue 17 Aug 2010 06:22 AM (UTC)

Message

I'm getting MXP errors upon connection to Materia Magica ever since it's last reboot when it's 'MXP vX enabled!' message was slightly updated to now display after the connection sequence is complete. I'm posting this here because I've already had some communications with MM's coder's and they are unable to reproduce my error's using v4.56 of MUSHclient. I continue to get the same errors regardless of changing any combination of MUSH version, fresh install's, and fresh world files.
The error occur's whenever a lessthan symbol is received for output. Somehow the MXP parser is reading this as a command and removes the lessthan plus all characters following it to the next open space. It then outputs the rest of the line and sends an MXP error to the log. I've been assuming that possibly the MM coder's left out a > somewhere in their MXP code but not everyone is getting the errors. I can't seem to diagnose if it's a setting I'm using and how to get rid of it so that MXP works. here are some examples of the errors.
The prompt string is as follows:

<863hp 649sp 844st>

but becomes the following with the error:

863hp 649sp 844st>
E  1001: (16658) Unterminated MXP element:  (got <ESC>)

another example from a in-game help file:

NAME
 write - write something on a page of parchment using a quill pen

SYNOPSIS
 write <parchment name>
 write <parchment name> title <title of parchment>
 write <parchment name> title none

becomes:

NAME
 write - write something on a page of parchment using a quill pen

SYNOPSIS
 write 
 write  title 
 write  title none

with these error codes logged:

A 20000: (16778) MXP element: <parchment name>
E  1023: (16778) Unknown MXP element: <parchment>
A 20000: (16779) MXP element: <parchment name>
E  1023: (16779) Unknown MXP element: <parchment>
A 20000: (16779) MXP element: <title of parchment>
E  1024: (16779) Secure MXP tag ignored when not in secure mode: <title>
A 20000: (16780) MXP element: <parchment name>
E  1023: (16780) Unknown MXP element: <parchment>
A 20000: (16789) MXP element: <parchment name>
E  1023: (16789) Unknown MXP element: <parchment>
A 20000: (16789) MXP element: <title of parchment>
E  1024: (16789) Secure MXP tag ignored when not in secure mode: <title>
A 20000: (16795) MXP element: <parchment name>
E  1023: (16795) Unknown MXP element: <parchment>

thanks for your help in advance. and if you need more info just ask.

--

working way to hard to play

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #1 on Tue 17 Aug 2010 06:24 AM (UTC)

Amended on Tue 17 Aug 2010 06:26 AM (UTC) by Twisol

Message

< characters that are not part of MXP tags are supposed to be sent by the server as < instead. If the MUD doesn't do this, you'll probably have the issues you're describing.

[EDIT] Alternatively, if MM lets you disable MXP, do so and disable it in MUSHclient too (in Game -> Configure -> MXP/Pueblo). You won't have any MXP benefits (because you've totally disabled it), but you won't have errors and your output will look right.

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by

Deacla USA (42 posts) Bio

Date

Reply #2 on Tue 17 Aug 2010 06:31 AM (UTC)

Message

As of now, I do have MXP disabled to make the game playable. I could deal with this normally as I don't use any of the MXP features. My problem is I'm also using the 'convert IAC EOR/GA to newline' feature in the Output menu to have real-time tracking of the prompt. This seems to rely on MXP somehow as it's now disabled too. Without it my vital stat bars are always one round behind because the prompt does not have a newline to trigger from. If i could find a workaround for that i could forget MXP altogether.

--

working way to hard to play

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #3 on Tue 17 Aug 2010 06:37 AM (UTC)

Message

Deacla said:
My problem is I'm also using the 'convert IAC EOR/GA to newline' feature in the Output menu to have real-time tracking of the prompt. This seems to rely on MXP somehow as it's now disabled too.

Hmm, that shouldn't be. I use it with Achaea, and I have MXP disabled. I think it's just a side-effect of the update you said MM did. If it was working before, fixing it should be pretty trivial.

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by

Deacla USA (42 posts) Bio

Date

Reply #4 on Tue 17 Aug 2010 06:54 AM (UTC)

Message

Any other thoughts on if it's my fault somehow in a plugin I wrote or a variable i may have changed somehow? Am I able to effect the way MXP is parsed or wether IAC EOR/GA is available for conversion to newline? The same error is also occurring with other MUSH/MM players that I have distributed plugins to. But, it all started happening after MM's last update, which also may have coincided with my last MUSH update...

--

working way to hard to play

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #5 on Tue 17 Aug 2010 06:56 AM (UTC)

Message

Well, you said you tried earlier versions. If you were messing with the MXP input you'd have hit weird behavior a lot sooner. And the only other way to tinker with the raw incoming data is OnPluginPacketReceived, which I doubt you're using because it has very little general use.

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by Deacla USA (42 posts) Bio

Date Reply #6 on Tue 17 Aug 2010 07:09 AM (UTC)

Message

looking at packet debug i get this for the same example from above with the 'write' command help file:

.[1;34m[.[0m1382   1b 5b 31 3b 33 34 6d 5b 1b 5b 30 6d 31 33 38 32
 .[1;34m] .[33mW   20 1b 5b 31 3b 33 34 6d 5d 20 1b 5b 33 33 6d 57
RITE.[0m..NAME..   52 49 54 45 1b 5b 30 6d 0a 0d 4e 41 4d 45 0a 0d
 write - write s   20 77 72 69 74 65 20 2d 20 77 72 69 74 65 20 73
omething on a pa   6f 6d 65 74 68 69 6e 67 20 6f 6e 20 61 20 70 61
ge of parchment    67 65 20 6f 66 20 70 61 72 63 68 6d 65 6e 74 20
using a quill pe   75 73 69 6e 67 20 61 20 71 75 69 6c 6c 20 70 65
n....SYNOPSIS..    6e 0a 0d 0a 0d 53 59 4e 4f 50 53 49 53 0a 0d 20
write <parchment   77 72 69 74 65 20 3c 70 61 72 63 68 6d 65 6e 74
 name>.. write <   20 6e 61 6d 65 3e 0a 0d 20 77 72 69 74 65 20 3c
parchment name>    70 61 72 63 68 6d 65 6e 74 20 6e 61 6d 65 3e 20
title <title of    74 69 74 6c 65 20 3c 74 69 74 6c 65 20 6f 66 20
parchment>.. wri   70 61 72 63 68 6d 65 6e 74 3e 0a 0d 20 77 72 69
te <parchment na   74 65 20 3c 70 61 72 63 68 6d 65 6e 74 20 6e 61
me> title none..

does this mean that the is in fact sending leesthan symbols instead of < ?

--

working way to hard to play

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #7 on Tue 17 Aug 2010 07:16 AM (UTC)

Message

Yes.

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by

Nick Gammon Australia (23,070 posts) Bio Forum Administrator

Date

Reply #8 on Tue 17 Aug 2010 07:32 AM (UTC)

Message

Every. Couple. Of. Months.

This question arises again and again, because Materia Magica (in this case) are not implementing the MXP spec correctly. From the spec here:

http://www.zuggsoft.com/zmud/mxp.htm

It says:

MXP spec said:

Since a normal < symbol is interpreted as the start of an element tag, you must use < to refer to a less-than symbol directly.

(my emphasis on the "must").

The MUD has not implemented the MXP spec correctly, and thus you are getting undefined behaviour at the client end. In fact, if you set "MXP debugging" to some level other than "none" , you will see errors scrolling by about "Unknown tag: <parchment name>".

The situation is made worse because certain other clients (you know who you are) don't implement the spec also, and thus the MUD developers "get away" with not following the spec, if they only test using a certain client.

Search this forum <sigh> there are various plugins around that try to work around this behaviour.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Nick Gammon Australia (23,070 posts) Bio Forum Administrator

Date

Reply #9 on Tue 17 Aug 2010 07:36 AM (UTC)

Message

Quote:

with these error codes logged:
A 20000: (16778) MXP element: <parchment name>
E 1023: (16778) Unknown MXP element: <parchment>
A 20000: (16779) MXP element: <parchment name>
E 1023: (16779) Unknown MXP element: <parchment>

Lol. I see you got those errors. I was so infuriated by the problem rearing its head again I skipped some of your post.

Well, you have something concrete to tell the devs at Materia Magica: "follow the MXP spec, please".

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Nick Gammon Australia (23,070 posts) Bio Forum Administrator

Date

Reply #10 on Tue 17 Aug 2010 07:41 AM (UTC)

Message

Deacla said:

As of now, I do have MXP disabled to make the game playable. I could deal with this normally as I don't use any of the MXP features. My problem is I'm also using the 'convert IAC EOR/GA to newline' feature in the Output menu to have real-time tracking of the prompt. This seems to rely on MXP somehow as it's now disabled too.

It shouldn't. In MUSHclient there is no connection.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Nick Gammon Australia (23,070 posts) Bio Forum Administrator

Date

Reply #11 on Tue 17 Aug 2010 07:45 AM (UTC)

Message

Do a packet debug on when it is waiting for input. See if you get an IAC EOR (0xFF 0xEF) or IAC GA (0xFF 0xF9).

If not, you have, ah, another bug report to submit to the MUD.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Deacla USA (42 posts) Bio

Date

Reply #12 on Tue 17 Aug 2010 07:45 AM (UTC)

Message

Thanks for your input guys. The one thing I don't understand is why it only recently started happening? I can only figure they left something open in the MXP change to trigger this.

--

working way to hard to play

Posted by

Nick Gammon Australia (23,070 posts) Bio Forum Administrator

Date

Reply #13 on Tue 17 Aug 2010 08:06 AM (UTC)

Message

Possibly. I haven't fiddled with MXP or the IAC/GA stuff, as far as I recall.

Especially if they claim 'MXP vX enabled!' (whatever that is). Sounds like they have been making changes. Not fully tested ones, perhaps.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by Deacla USA (42 posts) Bio

Date Reply #14 on Tue 17 Aug 2010 08:16 AM (UTC)

Message

When you log on it displays a message in the output 'MXP v0.5 enabled!' or 'MXP v1.0 enabled!'. That message doesn't display anymore for me after the change.
And, here is an example of the prompt packet:

Incoming packet: 614 (74 bytes) at Tuesday, August 17, 2010, 4:10:55 AM

...[1;34m[*].[34   0a 0d 1b 5b 31 3b 33 34 6d 5b 2a 5d 1b 5b 33 34
m<.[0m863.[1;34m   6d 3c 1b 5b 30 6d 38 36 33 1b 5b 31 3b 33 34 6d
hp .[0m649.[1;34   68 70 20 1b 5b 30 6d 36 34 39 1b 5b 31 3b 33 34
msp .[0m839.[1;3   6d 73 70 20 1b 5b 30 6d 38 33 39 1b 5b 31 3b 33
4mst>.[0m          34 6d 73 74 3e 1b 5b 30 6d 20

--

working way to hard to play

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

86,112 views.

This is page 1, subject is 3 pages long: 1 2 3

It is now over 60 days since the last post. This thread is closed. Refresh page

Go to topic: Search the forum

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.