MUSH

, which was fundamentally a social game.

MUSH has forked over the years and there are now different varieties with different features, although most have strong similarities and one who is fluent in coding one variety can switch to coding for the other with only a little effort. The source code for most widely-used MUSH servers is open source and available from its current maintainers.

A primary feature of MUSH codebases that tends to distinguish it from other multi-user environments is the ability, by default, of any player to extend the world by creating new rooms or objects and specifying their behavior in the MUSH's internal scripting language. Another is the default lack of much player or administrative hierarchy imposed by the server itself. Over the years, both of these traits have become less pronounced, as many server administrators choose to eliminate or heavily restrict player-controlled building, and several games have custom coded systems to restore more of a hierarchal system.

The programming language for MUSH, usually referred to as "MUSHcode" or "softcode" (to distinguish it from "hardcode" - the language in which the MUSH server itself is written) was developed by Larry Foard. TinyMUSH started life as a set of enhancements to the original TinyMUD code. "MUSHcode" is similar in syntax to Lisp. It is fairly easy to learn. Most custom coding, for the sake of simplicity, security, and stability, is done in softcode rather than by directly modifying the hardcode.

Roleplay on MUSHes

Traditionally, roleplay consists of a series of 'poses'. Each character makes a 'pose' - that is, writes a description of speech actions, etc. which the character performs. Special commands allow players to print OOC messages, distinguished by a prefixed tag from IC action. This medium borrows traits from both improvisational stage acting and writing. Roleplaying is one of the primary activities of MUSHes, along with socializing.

There is nothing in the code base that restricts a new MUSH from being a traditional hack-and-slash MUD-style game. However, the earliest uses of MUSH servers were for roleplaying and socializing, and these early trends have largely governed their descendants. In addition, due to this pressure, code updates have tended to emphasize improvements of value to the roleplayer. MUSH servers have one combat command out of the box, aptly called 'kill'. Despite the name, it simply gives a player a chance of killing another player dependent on how much OOC currency that player put into the effort. If successful, the 'killed' player is sent to his home and given some money for his trouble. If unsuccessful, nothing interesting occurs. This command is frequently disabled by server administrators as it is in practice notconducive to roleplay or theme.

A large number of roleplaying MUSHes have custom combat systems coded by their administrators. However, these are usually intended to provide a vehicle for roleplayed combat, and not as the main objective of the game. Many MUSHes with combat systems in fact discourage their players from using them.

Administration of MUSHes

All MUSH servers provide a flag that, when set on a player, bestows the ability to view and modify nearly everything in the game's database. Such players are usually called Wizards, and typically form the basis for the MUSH administration.

Although MUSH servers do not impose strong administrative hierarchies, most MUSH games establish additional levels of management besides Wizards. Some do so on a purely organizational basis, naming some Wizards "Head Wizards" or "Junior Wizards" or assigning sphere of responsibility to Wizards, despite the technical equality of their abilities in the game world. Others provide finer-grained control over capabilities that can be assigned to players so that some players can be granted the ability to view, but not modify, the entire game world, or to perform limited modifications. Other levels of power can include added control over one's own character, or fewer limits on resources. PennMUSH, TinyMUSH, and TinyMUX include the "Royalty" flag, which gives a player the powers to do most anything that doesn't involve modifying the database. RhostMUSH has a wide array of staff flags that differ in many ways from its sister servers.

Popular MUSH Software

Maintainers and developers of MUSH servers have traditionally shared ideas with one another, so most MUSH servers include concepts or code developed originally in other servers. There is particular interest in ensuring that common MUSHcode features work similarly across servers.

* [http://www.pennmush.org/ PennMUSH] developed from TinyMUD and PernMUSH at University of Pennsylvania, and later at University of California, Berkeley and University of Illinois at Chicago.
* [http://tinymush.sourceforge.net/ TinyMUSH] 3.0 through 3.1 derive from a merger of TinyMUSH 2.2.5 and TinyMUX 1.6, both of which ultimately derive from TinyMUD.
* [http://www.tinymux.org TinyMUX] 2.0 through 2.6 derive from TinyMUX 1.6. TinyMUX 1.0 through 1.6 were developed from a fork of TinyMUSH 2.0 10p6 and ultimately from TinyMUD.
* [http://btech.sourceforge.net/ BattletechMUX] A TinyMUX 1.6 derived codebase with real-time Battletech extensions.
* [http://svn.rhostmush.org/ RhostMUSH] developed from TinyMUD, then TinyMUSE. Its source is not publicly available, but can obtained on request subject to accepting a non-disclosure agreement.

PennMUSH, TinyMUSH, and TinyMUX are open-source. Rhost is free, but not open-source. Some enthusiasts may exclude one or more of the above on the basis of distribution method, name, or parentage, but all are free-form MUSH servers. There are differences, but they are well-understood. Few players can tell them apart.

ee also

*TinyMUD - the ancestor to MUSH servers
*MOO - also descended from TinyMUD, but radically different in both nature and intent from its cousins
*MUCK
*MUD
*Online creation

External links