Moonridden:Staff Sandbox
Staff Nexus
New Landing Page for Public Staff Documents
Meet The Staff
Staff Hierarchy
For a description of Titles, please see the Staff Hierarchy page.
| Community Staff Hierarchy | Discord Staff Hierarchy | Maintenance Staff |
|---|---|---|
| Head Admins
Staff Managers Administrators Game Assistants Trial Mods |
Head Admins
Head Chat Moderator All Community Staff, by Rank Chat Moderator |
Development Overseer
Sysadmin Maintainer |
Staff Roster
Please see the Staff Roster page for the current list of Staff.
Staff Fundamentals
Core Knowledge
All Staff should have a shared understanding to work from.
The following documents set that standard.
History
Acknowledging the past prepares us to avoid mistakes in the future.
You should know who we are, how we got to where we are today, and the history that you are inheriting and will end up representing.
- A 'Brief' History of SS13
- A 'Brief' History of Skyrat
- The Schism - Nova's Split from Skyrat
- Nova Sector, Month by Month
Philosophy
To establish and maintain cultural tenets among Staff.
These documents, in combination with the SOP and
- Core Philosophy
- Antagonism in Nova Sector
- Game Mastering in Nova Sector
Procedure
Please refer to the Staff Operations Policy.
Staff Documents
SOP - Staff Operations Policy
(There is no 'Private SOP', there are 'Private Standing Rulings')
ARM - Access Request Management
(Public Version)
VET - Veteran Policy
(Public Version)
CHAT - Discord Chat Policy
(Public Version)
CIA - Content Injection Assurance
Handbook and guidance for performing CIA.
Standing Rulings
A running list of situational rulings we have previously provided, for posterity.
Event Documents
See the Events page for full information.
Event Committees
Complex or impactful events are regulated by three Committee groups to ensure quality.
Content Injection Assurance is not an Event Committee. See the CIA Handbook for more details.
Story Event Committee
Has control on all events that utilize the Lore in some way. The Lore Team has the final say on how their work is used and represented by Staff.
Design, propose, and run events that advance or engage with the Lore, or Server Story, in a way that is respectful to the Lore.
Works with the Lore Team directly to ensure that Lore details are represented accurately.
Should request assistance from the Roleplay Event Committee and the Action Event Committee to lessen mechanical load from larger events.
See the Story Event Committee Handbook for more information.
Roleplay Event Committee
Oversees events that focus on generating Roleplay Opportunities, where combat and game mechanics are not a focus.
Works with the Lore Committee to create meaningful Story Events.
See the Roleplay Event Committee Handbook for more information.
Action Event Committee
Oversees events that focus on generating Mechanical Opportunities, where combat or engagement with game mechanics are a focus.
Works with the Lore Committee to create meaningful Story Events.
See the Action Event Committee Handbook for more information.
Event Scaling
See the Events page and Event Types for more information.
Big
These events affect the station at large. This is typically something that will garner a large response from the station and will affect the ongoing round in a massive way. Large scale events need to be authorized by an administrator or higher.
Small
These events do not affect the station at large. This is something that will typically affect a small group/faction and would not create waves for the station in the running of the round.
Event Types
Events are broken up into four varieties.
Story Events
Utilizes the Lore to further or reinforce the Story.
See Story Event Committee.
Roleplay Events
Creates an opportunity for players to mingle and roleplay by providing a unique situation or setting for them to engage with and congregate around.
Action Events
Creates an opportunity for players to express mechanical skill.
Admin Events
Encompasses all other Admin powers used within an IC context that is directly visible to players.