Hallo,
I'm now coding for my mud some things like client recognition via the <version> command.
I tried this with ZMud and MushClient and all gone well.
Then I began to implement the handling of the <support> tag, which response should be <supports ..> where .. is the list of tags supported by the client.
Some tags "supported" (because I find them in the line of <supports ..> sended my mushclient make me think.
This is what I get from mushclient's <support>:
Log: <SUPPORTS +head +body +afk +title +username +pass +samp +h +high +i +option +bold +image +image.url +xch_page +reset +strong +recommend_option +support +ul +em +send +send.href +send.hint +send.xch_cmd +send.xch_hint +send.prompt +p +hr +html +user +password +a +a.href +a.xch_cmd +a.xch_hint +underline +b +img +img.src +img.xch_mode +pre +li +ol +c +c.fore +c.back +color +color.fore +color.back +font +font.color +font.back +font.fgcolor +font.bgcolor +u +mxp +mxp.off +version +br +var +italic >
Please, notice that it says it supports "IMAGE", "IMAGE.URL", "IMG", "IMG.SRC" among other things.
Now, on my mud I added some "bools" like has_mxp_images or has_mxp_bold on the descr_data in order to know if I can send those tags to the client. I mean, if the client can handle them.
This works with zmud: if I get "+IMAGE" on the supports line I know I can send images, else not.
On mushclient it says it handles +image tag, but I know that no support for the image tag is given for mushclient.
So I ask why mushclient says +IMAGE on the response, when it doesn't really handle the image tag.
Or am I missing something?
-marco-
Okram@AnacroniAMUD.
I'm now coding for my mud some things like client recognition via the <version> command.
I tried this with ZMud and MushClient and all gone well.
Then I began to implement the handling of the <support> tag, which response should be <supports ..> where .. is the list of tags supported by the client.
Some tags "supported" (because I find them in the line of <supports ..> sended my mushclient make me think.
This is what I get from mushclient's <support>:
Log: <SUPPORTS +head +body +afk +title +username +pass +samp +h +high +i +option +bold +image +image.url +xch_page +reset +strong +recommend_option +support +ul +em +send +send.href +send.hint +send.xch_cmd +send.xch_hint +send.prompt +p +hr +html +user +password +a +a.href +a.xch_cmd +a.xch_hint +underline +b +img +img.src +img.xch_mode +pre +li +ol +c +c.fore +c.back +color +color.fore +color.back +font +font.color +font.back +font.fgcolor +font.bgcolor +u +mxp +mxp.off +version +br +var +italic >
Please, notice that it says it supports "IMAGE", "IMAGE.URL", "IMG", "IMG.SRC" among other things.
Now, on my mud I added some "bools" like has_mxp_images or has_mxp_bold on the descr_data in order to know if I can send those tags to the client. I mean, if the client can handle them.
This works with zmud: if I get "+IMAGE" on the supports line I know I can send images, else not.
On mushclient it says it handles +image tag, but I know that no support for the image tag is given for mushclient.
So I ask why mushclient says +IMAGE on the response, when it doesn't really handle the image tag.
Or am I missing something?
-marco-
Okram@AnacroniAMUD.