This manual is for MOZ (MOO in Oz) version 1.0.

Copyright © 2002 Robin Lee Powell

     Permission is granted to distribute and modify as long as credit is given.  See the file license.txt in the main MOZ distribution for full copyright information.

This is the Administrator's Gudie for MOZ (Moo in OZ). MOO is Mud Object Oriented.  MUD is Multi-User Dungeon or Dimension.  In general, a MUD is a multi-user text-based virtual environment.  For information on MUDs in general, see http://www.godlike.com/muds/ or your local search engine.  For information on MOOs, see http://www.moo.mud.org/moo-faq/.

Oz is a multi-paradigmatic language that happens not to suck.  See http://www.mozart-oz.org/.

Programs
********

new_moz
=======

*** Unfinished

NEW_MOZ creates an entirely new MOZ database, destroying anything that was there before.

moz
===

*** Unfinished

MOZ is the normal MOZ program.

Command Line Arguments
======================

Both MOZ and NEW_MOZ take the same command line arguments, except that only NEW_MOZ takes the --QUIET argument.

 -- Argument: --debug
     Specifies the level of debugging.  Values are DEBUG, INFO, WARN, ERROR, and CRITICAL.

     The default is warn.  For whatever level is selected, that level of log message and above (above meaning "less verbose" or "more severe") are printed.

 -- Argument: --port
     Specifies the port to make available for player connections.

 -- Argument: --rootdir
     Specifies the directory to find the MOZ data files in, i.e. the directory above db/ and classes/ and functors/.

 -- Argument: --quiet
     Used only by NEW_MOZ, causes NEW_MOZ to not complain about how you're about to destroy everything.

Administration Commands
***********************

 -- Command: reload all [classes]
     Re-reads all of the .class files and runs upgrade on every object in the MOZ except the Storage object.  So, basically, refreshes all of the running MOZ's code.  Used after upgrades and such.

 -- Command: bless type object
     Used to bless an object with special capabilities, generally on the Storage object.

     Possible Types

     Gate
          Gives a Gate the ability to take tickets from URLs and use them.

     Terminus
          Gives a Terminus the ability to write a pickle file for itself. Note that to be useful, the pickle file will have to be web-accessible in some fashion.

Unsorted
********

  * How to find players and objects.

  * About object file numbers?

  * How to kick players.