client
Potato MUSHclient
A cross-platform Tcl/Tk client written for MUSH players. Good encoding support, and a documentation set that says nothing at all about most protocols.
https://www.potatomushclient.com/ · Windows, Linux, macOS
Capabilities
3 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 | unknown | we did not find one |
| TLS | yes | github.com |
| UTF-8 | yes | github.com |
| MCCP | unknown | we did not find one |
| GMCP | unknown | we did not find one |
| MSDP | unknown | we did not find one |
| 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 |
Potato is a Tcl/Tk client built for MUSH play — multiple worlds, spawn windows, and a set of defaults that assume you are typing poses rather than combat commands. It runs on Windows, Linux and macOS from the same source, with the macOS builds usually a version or two behind.
It negotiates character encoding and speaks full Unicode, which for the MUSH side of the hobby is the capability that matters most in practice.
Note one documented limitation: it supports connecting to a port that is SSL from the start, and its own configuration page says STARTTLS-style negotiated SSL is not supported.
Why six rows say unknown
We searched the project's home page, its downloads page, all 103 of its wiki help files and its entire source tree for GMCP, MSDP, MCCP, MXP, MSP and ATCP. There is no documented statement about any of them. There is code that touches some of them, and this section does not turn code into a capability claim — a table that says "yes" on the strength of a constant in a header is making a promise the project never made.
The screen-reader row is the same answer reached the same way: a case-insensitive sweep for "screen reader", "text-to-speech", NVDA, JAWS, VoiceOver, "accessibility", "visually impaired" and "blind" across everything the project publishes returned nothing at all. That is not a finding about the software.
See also
- BeipMU A Windows client aimed at the MUSH side of the hobby, with screen-reader support in the output window and Pueblo rather than MXP.
- MUSHclient The long-established Windows client. Five scripting languages, a plugin architecture that most of its protocol support lives in, and a release history that has slowed.
- You want collaborative roleplay If what you are after is writing scenes with other people, this is the short path — the codebases to look for, a client that will not fight you, and what to expect on your first night.