List of MUD clients

A MUD client is a game client, a computer application used to connect to a MUD, a type of multiplayer online game. Generally, a MUD client is a very basic telnet client that lacks VT100 terminal emulation and the capability to perform telnet negotiations. On the other hand, MUD clients are enhanced with various features designed to make the MUD telnet interface more accessible to users, and enhance the gameplay of MUDs,[1] with features such as syntax highlighting, keyboard macros, and connection assistance.[2][3]

Standard features seen in most MUD clients include ANSI color support, aliases, triggers and scripting. The client can often be extended almost indefinitely with its built-in scripting language. Most MUDs restrict the usage of scripts because they give an unfair advantage, as well as the fear that the game will end up being played by fully automated clients instead of human beings.[4]

Prominent clients include TinyTalk, TinyFugue, TinTin++, and zMUD.[5][6]

  1. ^ Levine, John R. (1997). More Internet for Dummies. IDG Books. p. 199. ISBN 0-7645-0135-6. A better way to connect to a MUD is by using a MUD client program: a program specifically designed for MUDding. A MUD program is really a telnet program that has had various MUD-related commands added.
  2. ^ Shah & Romine 1995, p. 257, "Features include regular expression hilites and gags, auto-login, macros, line editing, screen mode, triggers, cyberportals, logging, file and command uploading, shells, and multiple connects."
  3. ^ Busey 1995, p. 200, "The TinyFugue system has long been a popular client interface for players of MOO, MUCK, and many TinyMUD-derivative systems. With a robust feature list supporting multiple sessions, macros, triggers and automation, command history and other functions, TinyFugue offers users maximum control over their environment. Although more recent programs such as Tintin++ have gained large followings, many MUD players continue to use TinyFugue because of its power and flexibility in the hands of an experience client programmer."
  4. ^ Raph Koster (2008). "A brief history of botting". Everyone's advice to a newbie was "get a client", followed by the lengthy caveat that a given mud had specific rules about what was permissible. In other words, the third-party tools were seen as something that added invaluable interface enhancements, but that also afforded a bit too much power.
  5. ^ Cheong 1996, p. 256.
  6. ^ Bartle 2003, p. 481.