Server Policy

This article is a stub, and will be expanded in the future.

This page's contents are being migrated to their respective pages. Contents may be outdated.

Staff Roles

This section is out of date. Review the specific page for the role.

Administrative Staff

Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.

Head Administrator

Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. If credible concerns of administrative bias are made, for example, a Head Administrator may assign a different admin to an unban appeal, or in rare cases handle it themselves. Head administrators also instruct Staff Heads on the direction the server should take.

While strongly discouraged when other staff are available, Head Administrators have the authority to step into any other role when the situation calls for it.

Administrator

Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.

Administrators are additionally responsible for the continued integrity of the in-game persistency, both by retroactively declaring incidents non-canon, or by accepting requests from players for permission to break major rules.

Moderator

Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone, but also first to grant exceptions to players for performing actions that would otherwise be minor rule violations.

Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.

As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them. If an administrator is unavailable, members of Oversight may enact their judgements as well.

Development Staff

Supporting staff handle all things to do with the server's state and development.

Staff Head

Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.

An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.

Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.

Staff Writer

A member of development staff, empowered with access to more sensitive pages on the Wiki, and tasked with organizing contributions within a certain subsection of Lore. Coordinates their particular interests with Lore Staff Heads.

Staff Coder

A member of development staff, empowered with access to debug utilities on the Server, and tasked with organizing code contributions. Coordinates their particular development focus with Code Staff Heads.

Showrunning Staff

Game Master

Game Masters are responsible for the bureaucratic elements of running events, as well as their scheduling. The GM is responsible for receiving event proposals, reviewing them with other GMs and relevant members of Oversight to ensure they cause no issues with existing lore or code, and approving them - either for singular use, or as a recurring event. The GM is also responsible for scheduling and overseeing events, and for granting permissions to Operators to participate in the event process.

GMs may allow Operators to independently run a minor event without directly being present to oversee them, however the Operator assumes some of the GM's responsibilities in doing so.

Event Operator

Event Operators are members of staff who are capable with the various buttons, panels and features of the Server, supporting the GM in running an event by actually enacting the various steps of the event.

Special Staff

Host

Not an official role, but nevertheless the foundation of the server, from which all roles are delegated. Has final authority over the server, but reserves such power only for emergencies and for the highest levels of bureaucracy.

Liaison

A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.

Regular Staff

A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.

Oversight

While not a formal branch of the staff, Oversight consists of Head Administrators, Staff Heads and Game Masters. These roles receive roughly equal permissions, and a separate set of channels to coordinate among each other.

Player Guidelines

This section details how players should interact with the administration in certain situations.

Appeals

Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.

Feature Issues, Development Complaints & Bug Reports

• Complaints should only be directed at Head Administrators.
• Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
• Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.

The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.

Administration Policies

Admin Exclusion Policy

The roles in Oversight, and Game Administrator, cannot be held by anyone holding a position roughly at or above Administrator on any other server.

Development and Staff Head Policies

Staff Head Overruling

Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways for them to overrule each other.

• If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
• If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
• With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
• Finally, a 66% supermajority of headmins may make a final decision on a matter.

On-Server Powers

Sounds

• Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.