mu*index
reading
plain text
theme

client

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.

https://beipdev.github.io/BeipMU/ · Windows

Capabilities

5 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.

Client capabilities, each read off the project's own documentation. Unknown means we did not establish it, and never that the client lacks it.
capability documented source
screen reader yes github.com
TLS yes beipdev.github.io
UTF-8 yes beipdev.github.io
MCCP unknown we did not find one
GMCP yes github.com
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 beipdev.github.io

BeipMU is a MIT-licensed Windows client, actively released, and one of the few built with MUSH-style play in mind rather than combat MUDs — multiple input windows, spawn windows, and a text engine that expects long paragraphs. Scripting is JavaScript by default, with other ActiveScript engines available.

Accessibility

The output window implements Windows' IAccessible interface, added deliberately as a step toward usability for visually impaired players, and there is a Speak trigger action for text-to-speech. No particular screen reader is named anywhere, and there is no accessibility chapter in the documentation.

One caution if you go looking: a page in the project's own documentation still says BeipMU cannot use speech synthesis. That page is out of date — the changelog and the maintainer's own issue comments both post-date it.

Two easy mistakes about this client

BeipMU implements MCMP, not MSP. They are different protocols with similar names and similar purposes, and reading one as the other would put a claim in this table that nobody made. The MSP row therefore says unknown.

It supports Pueblo, not MXP. Pueblo is the older HTML-in-a-MUD scheme and MXP is the later one; BeipMU documents basic Pueblo styles and clickable links. MXP was not established either way.

See also

  • 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.
  • 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.
  • 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.