Moonridden:Staff Sandbox: Difference between revisions

From Nova Sector 13
Jump to navigation Jump to search
(fills in events section, describes teams, proposes the Story Event Committee)
(i dont know what all i did but i did stuff)
Line 4: Line 4:
== Meet The Staff ==
== Meet The Staff ==
=== Staff Hierarchy ===
=== Staff Hierarchy ===
For a description of titles, please see the Staff Hierarchy page.
For a description of Titles, please see the Staff Hierarchy page.
{| class="wikitable"
{| class="wikitable"
|+
|+
Line 35: Line 35:
|}
|}
=== Staff Roster ===
=== Staff Roster ===
Head over to the Staff Roster page for the current list of Staff.
Please see the Staff Roster page for the current list of Staff.


== Staff Fundamentals ==
== Staff Fundamentals ==


=== Historical Primer & Core Knowledge ===
=== 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 SS13
*A 'Brief' History of Skyrat
*A 'Brief' History of Skyrat
Line 45: Line 53:
*Nova Sector, Month by Month
*Nova Sector, Month by Month


=== Philosophy ===
==== Philosophy ====
To establish and maintain cultural tenets among Staff.
 
These documents, in combination with the SOP and
*Core Philosophy
*Core Philosophy
*Antagonism in Nova Sector
*Antagonism in Nova Sector
*Game Mastering in Nova Sector
*Game Mastering in Nova Sector


== Core Staff Documents ==
==== Procedure ====
Please refer to the Staff Operations Policy.
 
== Staff Documents ==


=== SOP - Staff Operations Policy ===
=== SOP - Staff Operations Policy ===
Line 87: Line 101:
Should request assistance from the Roleplay Event Committee and the Action Event Committee to lessen mechanical load from larger events.
Should request assistance from the Roleplay Event Committee and the Action Event Committee to lessen mechanical load from larger events.


''See the SEC Guide for more information.''
''See the Story Event Committee Handbook for more information.''


==== Roleplay Event Committee ====
==== Roleplay Event Committee ====
Line 94: Line 108:
Works with the Lore Committee to create meaningful Story Events.
Works with the Lore Committee to create meaningful Story Events.


''See the REC Guide for more information.''
''See the Roleplay Event Committee Handbook for more information.''


==== Action Event Committee ====
==== Action Event Committee ====
Line 101: Line 115:
Works with the Lore Committee to create meaningful Story Events.
Works with the Lore Committee to create meaningful Story Events.


''See the AEC Guide for more information.''
''See the Action Event Committee Handbook for more information.''


=== Event Scaling ===
=== Event Scaling ===

Revision as of 11:40, 27 March 2025

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

  • Story Events
  • Roleplay Events
  • Action Events
  • Admin Events