Game Master - Revision history

K5: /* Event Oversight */

2025-03-03T07:46:25Z

Event Oversight

← Older revision		Revision as of 07:46, 3 March 2025
Line 38:		Line 38:

	== Event Oversight ==		== 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.		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 players have 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. Simply trusting the operator, however, does not suffice to justify this exception for a larger event.		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. Simply trusting the operator, however, does not suffice to justify this exception for a larger event.

			While the GM should not directly be running most events, if an event is sufficiently simple and there are no Operators available, or if an extra pair of hands are needed beyond the staff already involved, the GM may also run the event.

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

K5: /* Event Validation */

2025-03-03T07:40:51Z

Event Validation

← Older revision		Revision as of 07:40, 3 March 2025
Line 12:		Line 12:

	== Event Validation ==		== Event Validation ==
	Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details.		Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details. The GM may seek to approve an event for a single run, multiple, or to have it permanently added to the [[List of Approved Events]] for frequent use as a midround event.

	While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.		While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.
	* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.		* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.
	* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.		* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.
	* In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 96 hours (4 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications.		* In extraordinary cases, events that need temporary rule amendments may skip getting approval from the administration. The premise of the event isn't enough to justify this exception: the amendment should either be strongly unforeseen or have such a small risk as to justify surprise when it happens.

			Once an event is approved, it is available to use as soon as round interference approval is granted.

			== Round Interference ==
			Before running an event, the GM is expected to contact the administration to ensure the round is available for interference. If a significant player-driven event is occurring, or other circumstances (such as midround events) are taking too much of the playerbase's attention, the administration may refuse to open the round to the event.

			Administrators may add the following conditions before the event may take place:
			* The event must be postponed until later, or to the next round, due to current events.
			** This may not be done two rounds in a row for the same event, or if the event has already been announced, voted on or telegraphed after all other set conditions are met.
			* The event must be announced in advance by some amount of time, up to 7 days.
			* The event must pass a vote of some threshold, no greater than 75%.
			* The event must be telegraphed in some way before it begins.
			* The event must be openly announced at the beginning of the round in which it will be run.
			* The event must be openly announced when it begins.
			* The event must be kept secret from the playerbase before it is launched.
			If conditions conflict with each other, the GM has the authority to determine which conditions to ignore, to remove conflict.

			In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 48 hours (2 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications, but may be used in response to radio silence on that matter as well.

	== Event Oversight ==		== Event Oversight ==

K5: /* Event Validation */

2025-02-18T07:38:33Z

Event Validation

← Older revision		Revision as of 07:38, 18 February 2025
Line 16:		Line 16:
	While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.		While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.
	* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.		* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.
	* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.		* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.
	* In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 96 hours (4 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications.		* In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 96 hours (4 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications.

	== Event Oversight ==		== Event Oversight ==

K5: /* Event Validation */ The GM's discretion has been codified.

2025-02-18T07:38:14Z

Event Validation: The GM's discretion has been codified.

← Older revision		Revision as of 07:38, 18 February 2025
Line 14:		Line 14:
	Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details.		Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details.

	While ~~admin approval is~~ generally required to run an event, GMs are ~~empowered~~ to ~~schedule [i]finalized[/i] events~~, ~~bypassing~~ the ~~need for~~ round interference approval, so long as the event is ~~scheduled~~ no less than ~~four~~ days ~~into~~ the ~~future~~.		While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.
			* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.
			* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.
			* In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 96 hours (4 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications.

	== Event Oversight ==		== Event Oversight ==

K5 at 07:02, 18 February 2025

2025-02-18T07:02:21Z

← Older revision		Revision as of 07:02, 18 February 2025
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 Validation ==
			Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details.

			While admin approval is generally required to run an event, GMs are empowered to schedule [i]finalized[/i] events, bypassing the need for round interference approval, so long as the event is scheduled no less than four days into the future.

	== Event Oversight ==		== Event Oversight ==

K5: /* Event Oversight */

2024-12-05T13:41:05Z

Event Oversight

← Older revision		Revision as of 13:41, 5 December 2024
Line 14:		Line 14:
	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.		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.		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. Simply 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.		A single Game Master should suffice for most events, but if additional oversight is needed, another Master can ease some of the burden. The event remains the responsibility of the GM who approved it. If none are available, an Administrator can also help.

	== Deputizing ==		== Deputizing ==

K5 at 13:39, 5 December 2024

2024-12-05T13:39:56Z

← Older revision		Revision as of 13:39, 5 December 2024
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

K5 at 02:22, 26 November 2024

2024-11-26T02:22:56Z

← Older revision		Revision as of 02:22, 26 November 2024
Line 1:		Line 1:
	{{SidebarStaff}}		{{SidebarStaff}}

	~~== Overview ==~~		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.

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

	~~== Dispute Resolution ==~~		; 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.
	~~== Administrative Duty ==~~		; 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.

K5: Created page with "{{SidebarStaff}} == Overview == == Personnel Management == == Dispute Resolution == == Administrative Duty =="

2024-10-29T04:23:12Z

Created page with "{{SidebarStaff}} == Overview == == Personnel Management == == Dispute Resolution == == Administrative Duty =="

New page

{{SidebarStaff}}

== Overview ==

== Personnel Management ==

== Dispute Resolution ==

== Administrative Duty ==