MXP: no <support> tag

[xtian]

In MXP it is required for the Client to respond to a <SUPPORT> query from the server with a <SUPPORTS> response, listing the actively supported tags.

A server would use this information to only display supported tags to the client. You need to implement this, as you are not implementing some other standard tags as of now (namely the text formatting stuff).

Unfortunately there is no standard way of naming the items in the response, so for comparison ...

this is what Mushclient sends back:
Unterstuetzte Tags (MXP SUPPORT):
  +c, +v, +u, +b, +p, +a, +h, +i, +br, +ol, +em, +li, +ul, +hr, +pre, +afk,
+mxp, +img, +var, +html, +head, +send, +user, +samp, +high, +font, +pass,
+bold, +body, +title, +color, +reset, +strong, +option, +c.fore, +italic,
+c.back, +a.href, +version, +mxp.off, +img.src, +support, +password,
+username, +xch_page, +a.xch_cmd, +send.hint, +font.back, +send.href,
+underline, +color.back, +color.fore, +a.xch_hint, +font.color,
+send.prompt, +font.bgcolor, +font.fgcolor, +img.xch_mode, +send.xch_cmd,
+send.xch_hint, +recommend_option

and this is what CMUD3 sends back:
Unterstuetzte Tags (MXP SUPPORT):
  +dl, +sbr, +h, +color, +dest, +i, +user, +font, +var, +relocate, +br, +v,
+h4, +em, +bold, +u, +a, +h2, +h3, +style, +high, +nobr, +tt, +ul,
+reported, +h5, +h1, +image, +password, +version, +strong, +dd, +li,
+music, +xch_page, +c, +frame, +s, +username, +ol, +xch_mudtext,
+strikeout, +support, +b, +p, +stat, +sound, +h6, +small, +send, +gauge,
+expire, +underline, +strike, +report, +hr, +dt, +xch_pane, +pre, +pass,
+img, +italic

[xtian (xtian-avalon)]

I don't want to annoy you, but I don't think this should be 'whishlist', but will lead to real compatability problems. I find, it is a real error.

[Stephen Lyons (slysven)]

I came across this when looking for another report and the OP's comment SOME YEARS AGO is correct and as the reference document {http://www.zuggsoft.com/zmud/mxp.htm} pronounces:

"It is very important to implement the <SUPPORT> tag in your MUD server. This is the only way to determine what tags are really supported by the client. The MXP version number isn't enough information to determine this, and using <SUPPORT> is easier and better defined than trying to decide based upon what MUD client is being used."

We don't currently support the <SUPPORT> tag and I note that the <VERSION> tag is one place where the Mudlet version reported back has not been set to the APP_VERSION #define which is currently 3.0.0 (for the 3.0.0-delta preview) - it is still hard-coded to "2.0"

[Stephen Lyons (slysven)]

This really needs fixing IMHO...

[Vadim Peretokin (vperetokin)]

Closing the bug just to see how bug migration to Github will work - sorry.