Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, 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.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ MXP and Pueblo
➜ Telnet negotiation
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Nick Gammon
Australia (23,158 posts) Bio
Forum Administrator |
| Date
| Tue 05 Jun 2001 01:35 AM (UTC) Amended on Wed 06 Jun 2001 02:48 AM (UTC) by Nick Gammon
|
| Message
| The MXP spec defines a telnet negotiation sequence for determining if a client supports MXP or not.
MUSHclient extends that slightly by also recognising a sequence to "turn on MXP" in addition to one that queries whether or not it supports MXP.
For the benefit of MUD implementors, here are the relevant sequences. Sequence like <IAC> are not literally sent, they represent a single byte from the telnet negotiation protocol. The equivalents in hex are given underneath.
Do you support MXP?
(Sent from server to client)
<IAC><WILL><MXP>
which in hex is: 0xFF 0xFB 0x5B
Client supports MXP (and player wants to use it)
(Sent from client to server)
<IAC><DO><MXP>
which in hex is: 0xFF 0xFD 0x5B
Note - if you have MUSHclient's "Use MXP" option set to "On MXP Query" it starts expecting MXP tags from this point on, to be compliant with MUDs that don't implement the "turn on MXP" negotiation described below.
Client does not support MXP (or player does not want to use it)
(Sent from client to server)
<IAC><DONT><MXP>
which in hex is: 0xFF 0xFE 0x5B
Note - if you have MUSHclient's "Use MXP" option set to "No" it will send the <IAC><DONT><MXP> sequence described here.
Server is ready to start sending MXP
(Sent from server to client)
<IAC><SB><MXP><IAC><SE>
which in hex is: 0xFF 0xFA 0x5B 0xFF 0xF0
Following this sequence the server can then start sending MXP tags.
Note - if you have MUSHclient's "Use MXP" option set to "On MXP Command" it starts expecting MXP tags from this point onwards.
Stop using MXP
MUSHclient also supports the MXP tag
<MXP OFF>
... which tells it to stop interpreting MXP codes. The server should send this if the player types in a command to stop using MXP codes.
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
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.
10,109 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top