MUD, Object-Oriented, Pythonic

What is MOOP?

MOOP is a Python program which operates similar to a MOO. A MOO is an object-oriented, live-coding MUD. A MUD is a multi-user dimension...

Let's start again. MOOP implements a multi-user network virtual environment. Users connect to the server via TCP/IP, and can interact with other users in a fashion similar to any network MUD-type game. But the neat thing about a MOO is that all the coding which makes gadgets and gizmos and ordinary objects work is right there, available to the remote users. It can be viewed, changed, and extended in real time, without restarting the system. MOOP is the same way, but it is written entirely in Python, and all the code which makes the objects work is (of course) Python as well.

MOOP software Version 1.1 and prior and old versions of these web pages are all (c) 1999 by AccesSoft. Please see the license for details. The newer versions of the software and web-pages are (c) 2001 by me, Joshua Macy, and released under a Pythonic License (essentially the BeOpen License modulo my name and without the choice-of-law provision that raised GPL compatibility heebie-jeebies), under the terms of the AccesSoft License.

MOOP is open source, free software and will always remain that way. Please use and support free, open software whenever/wherever/however you can!

Getting the Software

Download the most recent release of the software from SourceForge.

Where can I discuss MOOP with other MOOP users/developers?

The following MOOP mailing lists are hosted by eGroups.com (a great site using Python!) Go to eGroups to subscribe to the mailing lists below and/or to view the archives.

moop-users

This mailing list is for all MOOP users -- players, implementors, coders, and innocent bystanders.

moop-imps

This mailing list is for MOOP implementors -- those actually running a MOOP server of their very own. It is expected that this list will have a smaller volume and be focussed on implementation details not of interest to general users. Most implementers should probably subscribe to moop-users as well.

moop-announce

When you want to be notified of software releases and related announcements (low traffic, moderated.) As of February, 2001, this list seems to be dead; an announcement of Moop's move to SourceForge was sent to the moderator, but never posted. You should probably watch the SourceForge project page instead.

Participating in the MOOP Project

There are several ways to participate in the development of MOOP:

• Moop Project Pages on Sourceforge: See what's up with Moop
• Submit bugs: buglists maintained on SourceForge
• Forums: Read and Post messages in the ongoing discussion forums
• Support: Request support in implementing or developing a MOOP
• CVS: Check out the latest development

How closely does this follow MOO?

The earliest versions of MOOP were mostly a proof-of-concept, built to demonstrate the key features of MOO, but without consciously copying its conventions. Since then, it's been decided to follow conventions described in the LambdaMOO Programmer's Manual (e.g., for function and variable names) wherever reasonable. This will make it easier for MOO programmers to migrate to MOOP, and vice versa.)

For more details, see the MOOP vs. MOO page.

What about using Moop under Python 2.0, and other support questions?

Moop works under Python 2.0, but the moop.dat that ships with version 1.1 was pickled with Python 1.5.2, so it needs to be recreated. Delete it and run moopdirect.py and an empty database will be created for you; you can then import bootstrap.txt (option 3 on the menu) to get back to the basic functionality. These and other support questions should be submitted on SourceForge.

How do I get started?

Getting Started

Will there ever be a real FAQ?

If enough questions get asked so that some of them stand out as frequent, yes.

Credits

MOOP continues to be a group-effort by many contributors.

Moop Home

Getting Started