OOC Game Administration
From WNOHGB Wiki
The OOC Game Administration handles multiple areas of the Where No One Has Gone Before behind the scenes. Each administrator has specific responsibilities on the game, ranging from Codewizards, creating and maintaining the game's code, to Org Wizards, handling the needs of the individual orgs, and Royals, also known as Q.
Contents |
Administration Members
Wizards
| Name | Rank | Responsibilities |
| Cochrane | Ensign Bearer | Archwizard, Starfleet / Romulan Star Empire Org Wizard |
| Randal | Head Codewizard | Head Codewizard |
| Armstrong | Wizard | Independents / Cardassian Union Org Wizard |
| Collins | Wizard | Wizard Emeritus |
| Daystrom | Wizard | Codewizard, Galaxy Alliance Org Wizard |
Retired Wizards
The administration would like to acknowledge and show gratitude for the contributions and efforts of the following retired wizards on the game:
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Royals
| Name | Rank | Responsibilities |
| Behr | Q | Democratic Republic of Bajor, Foreground Events Workshop Administrator |
| Clarke | Q | Galaxy Alliance, Independents |
| Huxley | Q | Archroyal, Romulan Star Empire |
| L'Engle | Q | Starfleet |
| Poe | Q | Starfleet |
| Rowling | Q | Galaxy Alliance, Independents |
| Templar | Q | Starfleet |
| Wilde | Q | Guide Royal, Building, Player Assistance |
| Wrede | Q | Starfleet |
Retired Royals
The administration would like to acknowledge and show gratitude for the contributions and efforts of the following retired royals on the game:
- Asimov, Moxy, Nix, Reaves, and Taylor.
Administration Policies
Wizard Ethics
"Wizards on a MOO have a considerable amount of power. With that power comes the responsibility to use it wisely, for the actions of an administrator reflect not only on himself, but on the MOO as a whole. Because a Wizard is in a position of power, he or she should attempt to set a positive example in all dealings, whether in-character (IC) or out-of-character (OOC), Common sense will usually suggest a decent solution to a given problem; there are, however, some situations where the ethical and "correct" thing to do is not immediately obvious."
- (Paraphrased from Amberyl's Wizard Lecture)
The Wizard Code of Ethics
The Can'ts:
- Wizards will not disrespect the player's right to privacy.
- Wizards will not use the @summon or @move command to teleport a player without prior consent from the player.
- Wizards will not use the @join or @move command to teleport themselves in a room in where IC play is occuring.
- Wizards will not misuse the power to see private information, such as sites, or email addresses.
- Wizards will not 'port' or copy code that is not their own.
- Wizards will not modify or destroy descriptions, objects, verbs, and other miscellaneous $things that are not considered public property.
- Wizards will not allow regular players to have Wizard powers.
The Cans:
- With the most notable exception of #4 and #7, at any time, on behalf of multiple player complaints, will the above be circumvented to take corrective action against a player in gross violation of the player etiquette policy.
- Wizards have the right to remove or modify objects which may be considered illegal for IC play.
All of the above are subject to intrepretation based on case-by-case predicaments. Obviously, in cases where players may be inadherent to the etiquette policy, wizards will carry out swift justice in accordance with the above code. As stated in the preamble, common sense prevails in our judgement of issue that arise in the course of this game's existance.
Request Handling
In an effort to expediate request processing, the Administration of this game has set up a series of mailers to be used when making a request for something that your character cannot obtain or accomplish via IC means. This might include information, items, or physical changes to the MOO itself.
The mailer to which you should send a request is dependent upon which Org you belong. Always send the request to YOUR Org mailer and Org Admin will determine if the request needs to be forwarded to another mailer or if they need to get information for you from a different Org Admin. This prevents miscommunication and delays in fulfilling requests. Note that even though you might be in a Suborg, such as a company, your request should still go to the mailer of the Org
Org Mailers
The following is the list of Org mailers to use:
| Organization | Name and Alias of Mailer |
| Galaxy Alliance | *galaxy-alliance.requests (*ga-r) |
| Starfleet | *starfleet.requests (*sf-r) |
| Independents | *independents.requests (*ind-r) |
| Cardassian Union | *cardassian.requests (*cu-r) |
| Romulan Star Empire | *rse.requests (*rse-r) |
In addition, we have other request mailers for more specific needs:
| Type | Name and Alias of Mailer |
| Tinyplot Ideas and Requests | *rp.tinyplot-submissions (*tp-ideas) |
| Planetary Real Estate | *century-25.real-estate (*real-estate) |
| Code Requests | *code.requests (*code-r) |
Requests should NEVER be directed to a specific Wizard, as the wizzen work as a team and may cover for one another if a problem can be handled in a more efficent and timely manner.
Requests for additions or changes to ships should be handled in an IC matter by contacting a character who would be able to answer those questions.
Bug notifications or problems with pieces of the game, including ships, PADDs, cargo consoles, etc. should be sent using @bug.
See Also
