|
The mud client occurs as software used to connect to the MUD. Typically the mud client occurs as super basic telnet client that lacks VT100 terminal emulation and a capability to perform telnet negotations. Then again it is enhanced by using features designed to specifically function swell by using mudding.
Standard features seen inside virtually all mud clients include ANSI color support, aliases, triggers and scripting. A client may typically exist as extended about indefinitely by owning its built-inherent scripting language. Virtually all muds limit a usage of scripts because it gives an unfair benefit, also when a fear that a game may prevent higher existence played by fully machine-controlled clients instead of individual beings.
A foremost mud client by using any important total of features was Tinytalk by Anton Rang around 1990, for Unix-like systems. This was followed in the equivalent season by TinyFugue, originally by Greg Hudson and taken across by Ken Keys within 1991. TinyFugue has continued to develop & remains one of a virtually all popular clients now for Unix-like systems, and the Microsoft Windows version is also available.
A second early client was [http://tintin.sourceforge.net TinTin++] by Bill Reiss witharound 1993, which successively was according to TinTin III, written by Peter Unold in 1992. From either that point ahead mud clients slowly evolved, introducing construct prefer information compression & machine mapping.
2 of the virtually all popular clients for Microsoft Windows are zMUD and Portal, both of which are then commercial computer program.
Mud Client Support Table
A MUD client support table gives an overview of various mud clients and their capabilities. a big however there is no elongated maintained trend lines table is available at the [http://www.cryosphere.org/telnet Cryopshere] home page.
|