client
TinTin++
A terminal client with its own scripting language, on every platform including phones, and a documented screen-reader mode.
https://tintin.mudhalla.net/ · Linux, macOS, Windows, Android, iOS
Capabilities
7 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 | tintin.mudhalla.net |
| TLS | yes | github.com |
| UTF-8 | yes | github.com |
| MCCP | yes | tintin.mudhalla.net |
| GMCP | yes | tintin.mudhalla.net |
| MSDP | yes | tintin.mudhalla.net |
| ATCP | unknown | we did not find one |
| MXP | unknown | we did not find one |
| MSP | unknown | we did not find one |
| scripting | yes | github.com |
TinTin++ is a command-line client, GPL 3, actively released, and it runs in more places than
anything else here — including Android and iOS. Its scripting language is its own, terse, and
capable of a great deal; a substantial amount of what other clients do in the GUI is a #config
line here.
The same author maintains the protocol specifications for MSSP and MSDP, which is why so many of the protocol pages in this section cite the same site.
Accessibility
TinTin++ has a dedicated manual page for screen reader mode (#config screen reader on, or
-s at startup). Enabling it does two things: it removes or alters visual elements that make no
sense read aloud, and it reports screen-reader use to the server through
MTTS, so a game can adapt its own output.
That is a documented mode, not a claim of testing with a particular reader — no product is named on the page. It is meaningfully weaker evidence than a client that names the readers it works with, and meaningfully stronger than nothing.
Where the table says unknown
MXP and MSP both have community scripts on the project's site, and a script is not the client supporting a protocol — the MXP one says outright that it may not work on every MUD. Native support for either was not established. ATCP we found nothing on either way; note that ATCP is largely superseded by GMCP, which TinTin++ does support.
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.
- Mudlet Cross-platform, Lua-scripted, and the client with the most thoroughly documented screen-reader support in this section.
- MSDP The Mud Server Data Protocol — the same job as GMCP, done with a compact binary encoding and a discovery mechanism GMCP lacks.
- TTYPE and MTTS How a client tells a server what it is and what it can do — including, if the client chooses to say so, that a screen reader is in use.