client
Mudlet
Cross-platform, Lua-scripted, and the client with the most thoroughly documented screen-reader support in this section.
https://www.mudlet.org/ · Windows, macOS, Linux
Capabilities
9 of 10 established from the project's own documentation
Read off each project's own documentation, not measured by us — a client has no handshake for us to observe. "unknown" means we looked and did not establish it. It never means no.
| capability | documented | source |
|---|---|---|
| screen reader | yes | wiki.mudlet.org |
| TLS | yes | wiki.mudlet.org |
| UTF-8 | yes | wiki.mudlet.org |
| MCCP | unknown | we did not find one |
| GMCP | yes | wiki.mudlet.org |
| MSDP | yes | wiki.mudlet.org |
| ATCP | yes | wiki.mudlet.org |
| MXP | yes | wiki.mudlet.org |
| MSP | yes | wiki.mudlet.org |
| scripting | yes | github.com |
Mudlet is a graphical client with a mapper, a package system and a Lua API that most of its own feature set is written against. It is GPL, actively released, and the usual recommendation for someone starting on a modern combat MUD.
Accessibility
This is the client with the strongest documented case in this section, and it is worth spelling out what "documented" means here, because it is unusual.
Mudlet has a manual chapter on screen readers, per-operating-system pages naming Narrator, NVDA
and JAWS on Windows, Orca on Linux and VoiceOver on macOS, an in-client mudlet access on command,
and an option to announce incoming game text through the reader. It also has a setting that
advertises screen-reader use to the server over MTTS, so a game can adapt if it wants to.
It is also candid about where it does not work well: its own Windows page says JAWS does not read the output window the way other readers do, and recommends Narrator or NVDA instead. A project that publishes the case where its accessibility support is impractical is giving you better information than one that publishes a tick.
Where the table says unknown
MCCP. Mudlet's source implements MCCP v1 and v2, but the manual's supported-protocols page does not list it, and this section's rule is that a capability claim cites the project's own documentation. Reading a constant out of a header is not the same act, so the cell says unknown.
Note on encoding
Mudlet's default server-data encoding is ASCII rather than UTF-8, and CHARSET negotiation arrived in 4.10. If a game's text comes out wrong on a fresh profile, that setting is the first place to look.
See also
- Blightmud A modern terminal client in Rust, with Lua scripting, built-in text-to-speech and a screen-reader mode that announces itself to the server.
- TinTin++ A terminal client with its own scripting language, on every platform including phones, and a documented screen-reader mode.
- GMCP The Generic Mud Communication Protocol — structured JSON messages alongside the text, and the out-of-band channel most modern clients build against.
- How to connect A host, a port, and telnet. What the address on a game page means and what to do with it.