mu*index
reading
theme
BEIPMU  [client]
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/
Runs on: Windows

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

  screen reader    yes
      https://github.com/BeipDev/BeipMU/blob/master/Assets/Changes.txt
  TLS              yes
      https://beipdev.github.io/BeipMU/
  UTF-8            yes
      https://beipdev.github.io/BeipMU/
  MCCP             unknown
  GMCP             yes
      https://github.com/BeipDev/BeipMU/blob/master/Documentation/GMCP.md
  MSDP             unknown
  ATCP             unknown
  MXP              unknown
  MSP              unknown
  scripting        yes
      https://beipdev.github.io/BeipMU/

  5 of 10 rows are unknown: we did not find the project's own documentation
  saying either way. A short honest table beats a long guessed one.

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 — /reference/clients/mushclient
  Potato MUSHclient — /reference/clients/potato
  You want collaborative roleplay — /reference/collaborative-roleplay