The Full Wiki

MOO: Wikis
  
  
  

Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.

Encyclopedia

Updated live from Wikipedia, last check: June 03, 2012 01:13 UTC (43 seconds ago)

From Wikipedia, the free encyclopedia

For other uses, see Moo (disambiguation).

A MOO (MUD, object oriented[1]) is a text-based online virtual reality system to which multiple users (players) are connected at the same time.

The term MOO is used in two distinct, but related, senses. One is to refer to those programs descended from the original MOO server, and the other is to refer to any MUD that uses object oriented techniques to organize its database of objects, particularly if it does so in a similar fashion to the original MOO or its derivatives. Most of this article refers to the original MOO and its direct descendants, but see Non-Descendant MOOs for a list of MOO-like systems.

The original MOO server was authored by Stephen White, based on his experience from creating the programmable TinyMUCK system. There was additional later development and maintenance from LambdaMOO administrator, and former Xerox PARC employee, Pavel Curtis.

One of the most distinguishing features of a MOO is that its users can perform object oriented programming within the server, ultimately expanding and changing how the server behaves to everyone. Examples of such changes include authoring new rooms and objects, creating new generic objects for others to use, and changing the way the MOO interface operates. The programming language used for extension is the MOO programming language, and many MOOs feature convenient libraries of verbs that can be used by programmers in their coding known as Utilities. The MOO programming language is a domain-specific programming language.

Contents

Background

MOOs are network accessible, multi-user, programmable, interactive systems well-suited to the construction of text-based adventure games, conferencing systems, and other collaborative software. Their most common use, however, is as multi-participant, low-bandwidth virtual realities. They are often used in academic environments for distance education or collaboration such as Diversity University; but others are primarily social in nature, or used for role-playing games (RPGs), or simply to take advantage of the programming possibilities.

Most commonly, MOOs are connected to by users using a client which speaks the telnet protocol, which provides a stay-alive connection with the host, to relay output and send commands. Some however have developed web interfaces, or other such methods; however this commonly limits interaction that the user can have, usually to the point they have no interaction, but instead can browse objects and discover typical information. Developments in cross-MOO networking have also lead to the creation of SunNET, a hubless network allowing cross-MOO communication and add extra possibilities to cross-MOO development, including networked channels.

Every MOO stores the content and state of all its objects within a persistent object database, which keeps objects from being lost by a reset of the MOO server software or the computer hosting it.

New MOOs have to choose a starting database from which to set their MOO up, or they can use a very minimal one which contains only the necessary objects to start a MOO. There are a handful of such MOO "core" databases which serve as foundations of code and utilities from which to start your MOO, including LambdaCore (from LambdaMOO), MinimalDB (considered the minimum necessary code and utilities to work usefully in a MOO), JHCore (from Jay's House Moo), and enCore (from LinguaMOO).

Every object in the MOO is assigned a number, and may be referred to by this number, prefixed with a #, as well as its name when the user is in the object's presence. Administrators, also known as Wizards, who are able to manage the MOO, and assign certain global names to these objects, which are prefixed with $, a process known as corifying. They also feature parenting systems, and every object will have a parent, commonly eventually leading to Root Class, otherwise known as #1. #0 is also reserved as a special system object which is responsible for managing the list of global names, incoming network connections, and other information related to the operation of the system.

History

MOO, along with all of its nephews, started out with text based adventure games. With the advent of the internet, MUD was formed as a networked version of one of those games. Eventually it developed into a tree of different types of MUD, with MOO becoming one of them.

Stephen White (also known by the handles "Ghondahrl" and "ghond") wrote the first version of the MOO server, which was released on May 2, 1990, and used for the operation of a server called "AlphaMOO". Pavel Curtis, an employee of Xerox PARC and also known by his handles "Lambda", and "Haakon", took the basic design, language, and code, fixed bugs and added features to release the first version, called "LambdaMOO" on October 30th, 1990.

According to Jill Serpentelli in her paper Conversational Structure and Personality Correlates of Electronic Communication:

Curtis went on to explain how the transition occurred from AlphaMOO to LambdaMOO. After fixing bugs in the system, rewriting some of the code, adding more programming capability, and writing documentation, he had created what he termed "a truly separate entity" from the original AlphaMOO. He dubbed this new system LambdaMOO, after one of his names on the system and, according to Curtis, "because it's a key word in some of the other non-mud research that I do." The new system was announced as open for public access on UseNet (a world-wide bulletin board system) in February of 1991 (Curtis, personal communication).

MOO was originally developed as a MUD server in the same general style (sharing much of the command syntax and community conventions) as TinyMUD.

There are currently two distributions of the MOO server code. The more popular of the two, the LambdaMOO server, is named such as indication of the close historical and continuing association of the MOO server code with the first public MOO, LambdaMOO, which is still popular today.

It is this LambdaMOO version of MOO that gained popularity in the early 90s, and it remains the most widely-used distribution of MOO. Pavel Curtis continued to maintain the server for several years. Other early contributors to the LambdaMOO server included users Tim Allen ("Gemba"), "Gary_Severn", Roger Crew ("Rog"), Judy Anderson ("yduJ"), and Eric Ostrom (known as "Joe Feedback"). Later, Eric Ostrom maintained the server, and the server is now maintained by Ben Jackson and Jay Carlson and has a LambdaMOO SourceForge.net project.

Current Projects Based on MOO

  • GammaMOO server is a fork with the goal of being a testing ground for new features not yet qualified for inclusion in the main MOO distribution (which has very strict standards for any changes). It can be seen as a the equivalent of a "development branch" that most other projects have.
  • Codepoint is an effort to extend LambdaMOO to support Unicode characters. Originally the project was started by H. Peter Anvin using libucd, a small library that implements features of the Unicode Character Database without being unwieldy. The project is now being developed by James C. Deikun, Robert Leslie, and Kenny Root with the goal of eventually integrating it into the main LambdaMOO distribution.

Non-descendant MOOs

Some servers use "MOO" style object oriented characteristics without being descended from the original MOO server, in the sense that they use little or none of that server's source code and use internal languages that are more or less incompatible with the MOO programming language. None of them have attained the popularity of LambdaMOO or its relatives.

Stephen White went on to write a new and similar system called CoolMUD, although it never obtained the same wide userbase as MOO. Another, later, attempt at a programmable object-oriented MUD server was ColdMUD, written by Greg Hudson and later maintained by Brandon Gillespie under the name "Genesis".

One unusual MOO with no real relationship to the original MOO is called mooix. mooix is unique among MUDs in that it uses the underlying UNIX operating system to handle all of the multitasking and networking issues. Several unique side effects result from this, one of which is that the MOO can be programmed in any language. mooix was written after a failed attempt by Joey Hess to write a MOO entirely in Perl, called perlmoo.

There are a number of MOOs written in Python, including POO, MOOP and ErisMUD.

MOO is often used in programming games, such as PointSet.

MOO access

Participants (usually referred to as users) connect to a MOO using telnet or some other, more specialized, client program. Upon connection, they are usually presented with a welcome message explaining how to either create a new character or connect to an existing one.

Having connected to a character, users then give one-line commands that are parsed and interpreted by the MOO as appropriate. Such commands may cause changes in the virtual reality, such as the location of a character, or may simply report on the current state of that reality, such as the appearance of some object.

The job of interpreting those commands is shared between the two major components in the MOO system: the server and the database. The server is a program, written in a standard programming language, that manages the network connections, maintains queues of commands and other tasks to be executed, controls all access to the database, and executes other programs written in the MOO programming language. The database contains representations of all the objects in the virtual reality, including the MOO programs that the server executes to give those objects their specific behaviours.

Almost every command is parsed by the server into a call on a MOO procedure, or verb, which actually does the work. Thus, programming in the MOO programming language is a central part of making non-trivial extensions to the database and hence the virtual reality.

MOO administration

All MOOs provide a flag called Wizard; when set on a player, the player gains the ability to view and modify nearly everything in the MOOs database. Such players are called Wizards, and usually form the basis for MOO administration. Designated owners of a MOO are sometimes referred to as Archwizards.

These wizards are able to restrict access to the MOO, as well as make news postings and monitor logs. Wizard permissions are needed for modification and even execution of verbs and properties for which the user does not own, or is not publicly readable/writable. All verbs and properties within objects have the appropriate flags, with the user can change to determine its current state. They are also able to assign global names to any object.

Builders are players who are given the limited ability to create objects and areas in a MOO, whereas programmers are also able to program on the MOO.

Outline of well-known MOOs

  • LambdaMOO was created alongside the server, and has continued despite server development having slowed. It was the first public MOO, and is still one of the most active MOOs to date. [1]
  • JaysHouseMOO was a social MOO started by Jay Carlson at Minnesota State University at Mankato in 1992. It had the first gopher server implemented in MOO language.[2] It was also noted by Netscape as having a web server as well.[3] During the 90's, it was considered the hangout of the MOO programmer elite.[4] Notable among them were former and current LambdaMOO code maintainers Roger Crew, Erik Ostrom, Jay Carlson, and Ben Jackson.
  • LinguaMOO is an educational MOO dedicated to general studies of arts and humanities, created in 1995 by Cynthia Haynes of the University of Texas at Dallas and Jan Rune Holmevik of the University of Bergen. Many educational MOOs use the enCore system, derived from LinguaMOO, for their MOO database core. [2]
  • MediaMOO is designed for professional media researchers now hosted at Northern Illinois University's Department of English. It was originally created in 1993 by Amy Bruckman at the Epistemology and Learning Group at the MIT Media Lab. In its heyday around 1996, MediaMOO had over 1000 members, was governed by an elected council, and hosted frequent meetings, including the Tuesday Cafe, a weekly discussion of members of the Computers and Writing community. [3]
  • Rupert is a social MOO based on The Hitchhiker's Guide to the Galaxy by Douglas Adams. It is spread out over several planets, the main being Rupert. Created by Jason R. Mills (aka SunRay), this MOO is also the home of the SunNET network, and all developments are conducted here. [4]
  • De digitale metro (The Digital Subway) founded in 1994 as part of De Digitale Stad (The Digital City of Amsterdam) and one of the first Dutch MOOs. [5]
  • MOOsaico created on 7 January 1994 was the first true multilingual MOO. Hosted in the Computer Science department of University of Minho. [6]
  • Medieval opened in April 1999 and revolves round a loose Fantasy/Medieval theme and has a very strong social cohesion. [7]
  • schMOOze University is considered the first MOO created for the express purpose of language learning. It was established by Julie Falsetti and Eric Schweitzer in July, 1994 and is hosted at CUNY-Hunter College. [8]
  • BioMOO was a professional MOO started by Gustavo Glusman and Jaime Prilusky at the Weizmann Institute of Science in 1993. It was a virtual place for Biology researchers to meet to brainstorm, hold colloquia and conferences, and explore the serious side of MOOs as a medium.[5] It sported a VR web interface.[6] During its eight years of activity, BioMOO hosted many professional activities including the Virtual School of Natural Sciences' courses on BioComputing and Principles of Protein Structure.[7] Prilusky and Glusman also released in 1994 the File Utilities Package, a MOO server modification enabling direct but controlled access to the underlying file system. [8]
  • BayMOO is a social MOO founded in October 1993. It is based on loosely on San Francisco and its surrounding areas. For part of its life it was hosted at SFSU. [9]
  • ATHEMOO was created in 1995 by the Association for Theatre in a Higher Education (ATHE) to provide global access to their national conference; plays have been staged there, and it continues to be active today. [9]
  • HellMOO is a post-apocalyptic role-playing game created in 2004. While not the first game created on the MOO platform, it is the most successful, and is currently the MOO with the most active players. [10]

See also

References

  1. ^ Shah, Rawn; Romine, James (1995). Playing MUDs on the Internet. John Wiley & Sons, Inc.. pp. 238. ISBN 0-471-11633-5. "For example, the MOO (Muds Object-Oriented) is a direct result of work in this area." 
  2. ^ Riddle, Prentiss (1993-04-13). "GopherCon '93: Internet Gopher Workshop and Internet Gopher Conference". PrentissRiddle.com. http://prentissriddle.com/trips/gophercon1993.html. Retrieved 2008-05-20. 
  3. ^ "What's New! June 1993". Netscape Corporation. 1993-06-24. http://wp.netscape.com/home/whatsnew/whats_new_0693.html. Retrieved 2008-05-20. 
  4. ^ Hand, Chris (1994). "meet me in cyberspace". http://www.ibiblio.org/cmc/mag/1994/sep/meetme.html. 
  5. ^ Flusfeder, Helena (1996-11-08). "Life mutates in MOO dimension". http://www.timeshighereducation.co.uk/story.asp?storyCode=91378&sectioncode=26. Retrieved 2008-12-16. 
  6. ^ "BioMOO announce VR web interface". 1995-04-30. http://www.bio.net/bionet/mm/bio-www/1995-April/000280.html. Retrieved 2008-12-16. 
  7. ^ Fuellen, Georg. "GNA's Virtual School of Natural Sciences". http://www.techfak.uni-bielefeld.de/bcd/Vsns/index.html. 
  8. ^ "FUP server builtin functions". 1997-04-17. http://tecfa.unige.ch/moo/book2/node147.html. Retrieved 2008-12-16. 
  9. ^ Burk, Juli, "ATHEMOO and the Future Present: Shaping Cyberspace into a Theatre Working Place", Theatre in Cyberspace Issues of Teaching, ACting, and Directing: 109-134 

External links

Essays and documentation

MOO directories

Cores and programming guides


Study guide

Up to date as of January 14, 2010
(Redirected to MOO (MUD object oriented) article)

From Wikiversity

Welcome to the MOO (MUD object oriented) learning project. This project allows Wikiversity participants to learn about the text-based virtual reality environments known as MOOs.

Contents

What is a MOO?

"MOO" means "MUD, Object Oriented".

What is a MUD?

MUD is an acronym for Multi-User Dungeon (or Domain), based on the Dungeon and Dragons board game. The board is a world divided into various sized rooms with interconnecting exits. The world is inhabitted by several monsters and contains many items like armour, weapons, potions, hearbs, scrolls, poisons, containers, and furniture. Each player creates their own character and tries to advance it as far as possible by moving around the world and 'interacting', usually by killing or getting killed by, monsters with the help of other characters.

Most MUDs use several point systems: Experience, Hit, Mana, Move, and Gold being the most common. Characters also have attributes, such as strength, intelligence, wisdom, dexterity, and constitution. These are defined by the character's race and modified by class. The class defines what skills and spells a character can learn, but race decides how well they can do them. In some MUDs, it is possible to multi-class and in others to remortalise.

The game is played over a network, using a telnet client to connect to the MUD server, and logging in as your character, typing commands, and reading the response. Each room has a name, description, and exit list. By carefully reading the description you can figure out where you are and what surprises the room contains. Other players, monsters, and items currently in the room are listed by name and title (or item description), and their current position (standing, resting, fighting, incapacitated, or corpse).

You can use several communication channels to talk, say, shout, yell, auction, and whisper to others. This variety enables players to remain in contact throughout the world. Players can turn off channels to avoid channel spam. Unlike direct channels, notice boards provide discussions, questions, bug-reports, and advice, regardless of whether players are logged in or not.

Because the MUD simulates a world and people have the choice to become someone else, MUD culture has undergone some academic scrutiny. Four player types have been identified:

  • Killer - Likes to kill players, the easier the better.
  • Achiever - Likes to win, accept all challenges, and work hard.
  • Explorer - Likes to map the world and discover how it works.
  • Socialiser - Likes to talk, and talk, and talk.

These four types interact with each other as follows:

  • Killers like Socialisers, ignore Explorers, but dislike Achievers. Socialisers are wimps and the aftermath of whining and complaing is the best. Explorers are damn tough, but don't care, so leave them alone. Achievers just won't lie down and die, sooner or later they'll get you.
  • Socialisers like Explorers, ignore Achievers, and dislike Killers. "Explorers just know ever so much you have simply got to have one around when conversation falters. Achievers are too boring, you can't imagine, always after something, and have nothing but their own ego. Killers are so rude and impolite, they should be banned for good. Like yesterday three of us were talking when ...." yes, thank you, moving to
  • Explorers like Achievers, ignore Killers, and dislike Socialisers. Achievers want to know stuff, which is great to see them use it well. Killers are just one more hazard to exploring, initially fun, but one dimensional. Socialisers are just plain ignorant.
  • Achievers like Killers, ignore Socialisers, and dislike Explorers. Killers are good challenge and you can always beat them in the end. Socialisers are no competition, but tell the world who the best of the best is. Explorer's have no competitive spirit and a waste of time.

Successful MUDs have a mix of all four types, as each contributes to the mud culture. Setting up the world to provide interest for all types is more an art than science. Ensuring that killers don't drive out socialisers, achievers the killers, socialisers the explorers, or explorers the achievers, takes careful balancing between interest, difficulty, challenge, and oppotunity. A major factor is building unique, rather than using stock, areas. Builders are designated players who have to bring the world alive with interesting descriptions and colourful words. But more than that, the layout and quests must be well tested for difficulty and interest. Coders define the game play, the skills, races, classes, and available items. Angels are special players who spend their time helping others and mediating conflicts. Immortals run the MUD, make policy, are forbidden to play, and lurk in the background, just so you know they're watching.

Object programming

Putting it all together

A MOO is a MUD that makes use of an explicitly object-oriented programming language for constructing the MUD. See: MOO programming language.

Mooversity can help Wikiversity participants learn about object-oriented programming.

Activities and discussion

If you have participated in a MOO, please provide a description and a link.

External resources

See also


Wiktionary

Up to date as of January 14, 2010

Definition from Wiktionary, a free dictionary

See also moo, moʻo, and Moʻo

English

Initialism

MOO

  1. matter of opinion
  2. (video games) Master of Orion
  3. (video games) MUD, Object Oriented







Got something to say? Make a comment.
Your name
Your email address
Message
Please enter the solution to case below
5-2=