protocol
Pueblo
The older HTML-in-a-MUD scheme, from the client of the same name. Still supported by MUSH-side clients, and routinely confused with MXP.
Measured adoption
0 of 886 listed games — 0.0%
The games not counted here are not games without the protocol. A game is counted when we observed its server offering the option in a handshake; the rest are servers that did not offer it to us and servers whose handshake we have not read, and we cannot tell you which.
| codebase | offered it | identified |
|---|---|---|
| AresMUSH | 0 | 18 |
| CircleMUD | 0 | 47 |
| CobraMUSH | 0 | 2 |
| CoffeeMUD | 0 | 32 |
| DikuMUD | 0 | 35 |
| Evennia | 0 | 11 |
| FluffOS | 0 | 28 |
| MUCK | 0 | 24 |
| PennMUSH | 0 | 34 |
| RhostMUSH | 0 | 40 |
| ROM | 0 | 55 |
| SMAUG | 0 | 20 |
| tbaMUD | 0 | 5 |
| TinyMUSH | 0 | 9 |
Pueblo came out of the client of the same name in the mid-nineties and took a direct approach to enhancing MUD text: let the server send HTML, and let the client render it. A server announces Pueblo support in a line at connect; the client replies, and from then on the stream may carry markup.
It reached the MUSH side of the hobby more than the MUD side, and MUSH servers that support it generally still do.
Not MXP
MXP is the later scheme and the more widely implemented one. They do a similar job and are not compatible, and reading a client's Pueblo support as MXP support — or the reverse — is the single easiest mistake to make when compiling a client comparison. The client pages in this section keep them separate for that reason, and where a project documents one and not the other, the other says unknown.
What we measure
Pueblo's handshake is not a telnet option in the usual sense, so what we observe is narrower than for the negotiated protocols, and a low figure here should be read as a statement about our visibility rather than about deployment.