Ancillary or client protocol

MSP

MUD Sound Protocol

Legacy compatibility Documented current use Legacy

Lets a server request sound or music playback, historically with optional web downloads.

Protocol overview

First seen: Documented by 2001
Present-day status: Legacy compatibility
In use today?: Yes, with documented current use.
Legacy?: Yes. It may still matter for compatibility or historical systems.
Layer: Ancillary or client protocol
Transport: Telnet option 90 plus line-oriented SOUND and MUSIC triggers
Telnet option: 90
Research validated: 2026-08-29

Current use and fit

Still supported for compatibility, but MCMP is a cleaner choice for new media features.

Implementation essentials

Offer WILL MSP and wait for DO before sending triggers.
Place legacy triggers at the start of their own line.
Restrict media origins, paths, types, and download sizes.

Compatibility and safety notes

Reject absolute and traversal paths.
Treat filenames and URLs as untrusted active content.
Users must retain control over playback and downloads.

Original specifications and sources

Original Zuggsoft specification Original
MUD Standards preservation Preservation

Where an original site has disappeared, a preservation archive is linked and identified as such. MUDVerse does not claim authorship of the original protocol.