Event Operator: Difference between revisions
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
== Event Composition == | == Event Composition == | ||
Operators | Beyond simply running an event, Operators also are the primary contact point of any denizens who want to create an event. They're responsible for guiding the denizen through the [[Event Checklist]] and making sure all the steps are followed to produce a great event. Once the event is ready, the Operator is also responsible for submitting it for review, along with an assurance that the denizen's event was built correctly. | ||
Given their intimate relationship with the event process, Operators themselves receive extra privileges: | |||
* They are not restricted to following the [[Event Checklist]] step by step, and may submit an event plan for approval without any prior communication. | * They are not restricted to following the [[Event Checklist]] step by step, and may submit an event plan for approval without any prior communication. | ||
* They may fast-track their event's approval process by having relevant development staff pre-approve lore and code elements or changes, allowing the Game Master to simply verify the approval once submitted. | * They may fast-track their event's approval process by having relevant development staff pre-approve lore and code elements or changes, allowing the Game Master to simply verify the approval once submitted. | ||
* For their own events, they both advise the active GM and can also directly operate the event as it happens. This provides no benefit beyond fitting a single person to two roles during the event. | |||
<!--* For simple events that do not warrant direct GM oversight, a Game Master can preemptively approve the event, allowing the Operator to run it independently with only administrative assent. (commented because the process isn't ready on the admin side) --> | <!--* For simple events that do not warrant direct GM oversight, a Game Master can preemptively approve the event, allowing the Operator to run it independently with only administrative assent. (commented because the process isn't ready on the admin side) --> | ||
Latest revision as of 07:11, 19 December 2024
| Administration | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Server Policy | ||||||||||||
| Staff Ranks | ||||||||||||
|
||||||||||||
| Policies | ||||||||||||
|
||||||||||||
Event Operators are staff trained to handle the game's tools. They're capable of running approved events single-handedly, as well as helping other event operators with their events when more than one pair of hands is needed. Event Operators answer to Game Masters and receive in-game permissions from them alongside event approval.
Event Running
Formally, events are run by the Game Master that approves the event, with the assistance of the creator of the event. This leaves the role of the Operator primarily in the mechanical running of the event as described in the event plan, and following any other instructions.
In practice, the event team communicates to run the event smoothly and make any necessary adjustments as needed. More often than not, an event will be run by the Operator who created it, and will have extra flexibility in adjusting the event to suit their intentions.
Event Composition
Beyond simply running an event, Operators also are the primary contact point of any denizens who want to create an event. They're responsible for guiding the denizen through the Event Checklist and making sure all the steps are followed to produce a great event. Once the event is ready, the Operator is also responsible for submitting it for review, along with an assurance that the denizen's event was built correctly.
Given their intimate relationship with the event process, Operators themselves receive extra privileges:
- They are not restricted to following the Event Checklist step by step, and may submit an event plan for approval without any prior communication.
- They may fast-track their event's approval process by having relevant development staff pre-approve lore and code elements or changes, allowing the Game Master to simply verify the approval once submitted.
- For their own events, they both advise the active GM and can also directly operate the event as it happens. This provides no benefit beyond fitting a single person to two roles during the event.
