Game Master: Difference between revisions

From Sojourn
No edit summary
No edit summary
Line 10: Line 10:
; Persistent : These GMs focus on the more complicated single-shot events that need more specific approvals without the benefit of an overarching Arc approval.
; Persistent : These GMs focus on the more complicated single-shot events that need more specific approvals without the benefit of an overarching Arc approval.
; Mini : These GMs focus on approving small events with few lore or code consequences that can be used to spice up a round on short notice.
; Mini : These GMs focus on approving small events with few lore or code consequences that can be used to spice up a round on short notice.
== Event Oversight ==
Game Masters take custody of an event once the event begins. Unlike [[Event Operator|Event Operators]], they do not directly run the event through the game's tools. Instead, it is their responsibility to ensure that the playerbase has a fun time experiencing the event, coordinating with the creator of the event to keep it on track while directing Operators to make changes as they see fit.
GMs are expected to oversee the event from start to finish, but have the discretion to allow an Operator to handle an event in their place if it's minor enough to not need oversight. Trusting the operator, however, does not suffice to justify this exception for a larger event.
A single Game Master should suffice for most events, but if additional oversight is needed, another Master can join in and help. The event remains the responsibility of the GM who approved it. If none are available, an Administrator can also help.
== Deputizing ==
Event Operators should be used and prioritized when help is needed for the event. However, if more hands are needed than are available, the Game Master can deputize certain willing staff, in this order of priority:
# Other Game Masters
# Administrators
# Moderators
# Code Staff
# General Staff

Revision as of 13:39, 5 December 2024

Game Masters are responsible for the validation and subsequent approval of events. They work closely in the event creation process to ensure that the event follows the Event Checklist. An event requires approval from a Game Master to proceed.

Mandates

Game Masters have a range of powers depending on how capable they are. In general, they fall into one of a few categories.

Broad
These GMs can support and approve the whole gamut of events from the simplest to the most intricate of arcs and their constituent events.
Arc
These GMs are specifically dedicated to reviewing and overseeing Arcs and its events. They don't concern themselves with smaller or single shot events.
Persistent
These GMs focus on the more complicated single-shot events that need more specific approvals without the benefit of an overarching Arc approval.
Mini
These GMs focus on approving small events with few lore or code consequences that can be used to spice up a round on short notice.

Event Oversight

Game Masters take custody of an event once the event begins. Unlike Event Operators, they do not directly run the event through the game's tools. Instead, it is their responsibility to ensure that the playerbase has a fun time experiencing the event, coordinating with the creator of the event to keep it on track while directing Operators to make changes as they see fit.

GMs are expected to oversee the event from start to finish, but have the discretion to allow an Operator to handle an event in their place if it's minor enough to not need oversight. Trusting the operator, however, does not suffice to justify this exception for a larger event.

A single Game Master should suffice for most events, but if additional oversight is needed, another Master can join in and help. The event remains the responsibility of the GM who approved it. If none are available, an Administrator can also help.

Deputizing

Event Operators should be used and prioritized when help is needed for the event. However, if more hands are needed than are available, the Game Master can deputize certain willing staff, in this order of priority:

  1. Other Game Masters
  2. Administrators
  3. Moderators
  4. Code Staff
  5. General Staff