Mudlet mxsp software#

Lines sent from the MUD are also marked as The core of MXP involves tagging text lines sent by the MUD.Įach MXP command is marked as either 'Open' or

Provides compatibility with MSP, it does not add any additional sound support of its own. The MUD Sound Protocol (MSP) is a separate specification, and while MXP Two additional Client/Server protocols are not discussed in thisĭocument. MXP handles this by grouping the various tags and commands into secureĪnd open categories, and preventing the secure tags from being used by MUD players. For example, while it might be desirable toĪllow players to change the font or color of their chat messages, you would not want toĪllow them to display a large graphics image, or execute script commands on the client of Certain HTML functions need to be restricted While support for HTML tags within a line is desired, players on a MUD canĮxploit this power and cause problems. In addition, there are additional security concerns to worry about Use on a MUD where text efficiency is important.

Also, the existing standards are needlessly verbose for It is only 'loosely' based upon these standardsīecause MUDs require dynamic, streaming text, rather than the page-oriented view MXP is based loosely on the HTML and XML standards supported by modern webīrowsers.

Mudlet mxsp software#

Zugg Software willĬoordinate the documentation of MXP in the Developer's Forum at the web site: Send all proposed changes to get them incorporated into this spec. To use and extend this specification as desired. Will still lead the development of MXP, but any MUD client or server is welcome Has been removed by Zugg Software as of MXP version 0.1.

The MXP specification will be public-domain.

MXP will be easy to implement for both the MUD Server and Clients.

MXP will be small and efficient since MUDs send a great deal of text.

MXP will be based upon existing standards when possible.

The MUD eXtension Protocol (MXP) attempts to fill this gapīy providing a markup language based loosely upon HTML and XML that allows better communication between the However, there is no higher-level command protocol used by MUDs toĮnhance the game session. MUD sessions haveīeen enhanced using standard terminal protocols, such as ANSI and VT100 to add color andĬursor control. Traditionally, MUDs have used raw Telnet.

Transferring files via the Telnet socket connection. For example, FTP adds a command language for Of these protocols enhance Telnet with their own higher-level protocol in order to provide While Telnet is the basis of most Internet protocols (FTP, HTML, SMTP, etc), most MUD Servers communicate with MUD Clients via the Telnet Protocol. Implementation Details A Detailed Example Conclusions Introduction MUD Servers Images File Filters Outdated Tags Server-side Scripting Using Entities Frames Cursor Control Cross-linking Multiple Version 1.0 (12-Mar-03) Contents Introduction Overview of MXP MXP Line Tags MXP Reference Elements Attributes Entities User-defined Line Tags Tag Properties MXP Tags Text Formatting On MXP specification List of MUDs with MXP support List of MUD Clients with The MUD eXtension Protocol (MXP) is an open specification for enhancing theĬommunication between MUD servers and clients. MUD eXtension Protocol MUD eXtension Protocol (MXP)