[MUD-Dev] Re: A little help

[Koster]

Legend uses a fairly different system from the traditional
single-hierarchy model, cribbed in part from "wizbits."

Basically, all our imms fall into one of four departments:

PR handles running events, in-game activities, etc. "Ways to make the
game fun that aren't part of the game."

ADMIN handles game admin issues such as rule infractions, character
archiving and restoration, website maintenance, etc.

CODING handles the mud's hardcode, implements new code features, handles
machine sysadmin duties, etc.

BUILDING handles the mud's databse, builds new areas, maintains old
ones, and creates as-needed database material for the other departments.

The heirarchy is fairly flat, consisting of five levels that are flatter
than they seem:

Inactive: immortals who are not currently actively working on a project.
These people can poof around and get access to the immort communication
channels, and that's about it.

Assistant: immortals who are given the basic commands needed for a given
department's duties.

Full: immortals who have all the commands for a given department's
duties.

Department head: there are only ever four of these. They have all the
power an imp does, basically, and serve as a committee that runs the day
to day of the mud.

Implementor: they pay for the server, hence the power, and make final
calls on things that the dept heads cannot.

Players must apply to join a specific department, and must submit a
proposal for a project of some significance. They must also have reached
a particular level (not maxxed out, however) in the game. The details
differ by department, but you can see them at
http://mud.sig.net/help.indexes.html if you are curious. New imms are
then immorted as "Full" members of that department.

After showing notable progress in a given department, with permission
from their department head, may pick up assistant duties in other
departments. All command access is done via these job flags, NOT by
level. Theoretically, an imp can (and should) go inactive if they are no
longer actively contributing.

Coordination and management of this group is done via mailing lists set
up for this purpose. Few items end up needing to go to the full imm
staff, so most issues are settled on departmental mailing lists. The
dept heads and the imps are on all lists; other than that, access to
them is largely restricted by department. Weekly reports are required,
and lack of activity in your department is grounds for losing your
wizbit and being dropped down to inactive status. The part-time imms who
cannot devote the required hours are encouraged to stay at assistant
level in the department of their choice.

The philosophy is, the powers go to those who contribute on an ongoing
basis. Those who do not contribute regularly are still imms, but they
don't get the cool stuff. To quote a webslinger, "with great power comes
great responsibility" right? ;)

This model has btw managed to greatly reduce the need for constant imp
involvement, which we used to have in a big way. Instead, the load
cascades down the tree. But it's flat enough that anyone can talk to
anyone, and it scales fairly nicely to larger staffs.

-Raph