Event Policy - Revision history

Moonridden: /* Who can run a Disaster Event? */

2026-04-28T23:26:24Z

Who can run a Disaster Event?

← Older revision		Revision as of 23:26, 28 April 2026
Line 162:		Line 162:

	==== Who can run a Disaster Event? ====		==== Who can run a Disaster Event? ====
	All intentional Disaster Events must be approved by an [[Staff_Policy#Staff_Hierarchy\|Event Curator or Class 3 Staff]]~~. Large Disasters must be announced two shifts in advance~~.		All intentional Disaster Events must be approved by an [[Staff_Policy#Staff_Hierarchy\|Event Curator or Class 3 Staff]].

	==== What is a Disaster Event? ====		==== What is a Disaster Event? ====

Moonridden: /* Event Operations */ Clarifies targeted event player consent. This got cut at some point.

2026-04-25T00:13:30Z

Event Operations: Clarifies targeted event player consent. This got cut at some point.

← Older revision		Revision as of 00:13, 25 April 2026
Line 41:		Line 41:

	A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.		A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.

			If Staff wish to run an event that solos out a Character in a high profile fashion, they should get consent for participation from the Player by Admin Help.

	Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.		Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.

GreytideSkye: adding crosslinks to get moon's attention and elaborate what a C3 staff is. speaking of, hi moon. do u c3 light at 3 end of 3 tunnel

2026-03-28T17:09:48Z

adding crosslinks to get moon's attention and elaborate what a C3 staff is. speaking of, hi moon. do u c3 light at 3 end of 3 tunnel

Moonridden: Throws a bone to people that either dont, wont, havent, or cant, read discord announcements regarding event time scheduling by obligating staff to inform them about event plans across multiple platforms, instead of in the designated spot at the top of our channel list.

2026-03-20T21:26:42Z

Throws a bone to people that either dont, wont, havent, or cant, read discord announcements regarding event time scheduling by obligating staff to inform them about event plans across multiple platforms, instead of in the designated spot at the top of our channel list.

← Older revision		Revision as of 21:26, 20 March 2026
Line 52:		Line 52:

	You must inquire with the Event Leaders to add, modify, or contribute content in their event. Issues regarding an event should be directed to the Event Leaders, or Staff Manager.		You must inquire with the Event Leaders to add, modify, or contribute content in their event. Issues regarding an event should be directed to the Event Leaders, or Staff Manager.

			If a planned Event needs the shift prior to be cut short or extended to meet scheduling demands, Staff should update the Title Screen Notice.

	=== Crew Events ===		=== Crew Events ===

Moonridden: english is my first language bee tee dubs

2026-01-05T15:54:55Z

english is my first language bee tee dubs

← Older revision		Revision as of 15:54, 5 January 2026
Line 36:		Line 36:

	=== Core ===		=== Core ===
	Events must be logged in the Event Log thread. It is recommended you post your log with your plans ~~when you being an~~ Event, and then ~~edit it to add~~ details or ~~results~~.		Events must be logged in the Event Log thread. It is recommended you post your log with your plans prior to starting your Event, and then update or reply with additional details later or after the event.

	All Staff are permitted to run Events. Trial-Staff may run Events if they first get permission from a C3 or higher by explaining their plans in a Staff visible channel, not DMs.		All Staff are permitted to run Events. Trial-Staff may run Events if they first get permission from a C3 or higher by explaining their plans in a Staff visible channel, not DMs.

Moonridden: more adjustments

2026-01-04T20:36:52Z

more adjustments

← Older revision		Revision as of 20:36, 4 January 2026
Line 36:		Line 36:

	=== Core ===		=== Core ===
	~~All~~ Events ~~are to~~ be logged ~~no matter~~ the ~~intensity~~.		Events must be logged in the Event Log thread. It is recommended you post your log with your plans when you being an Event, and then edit it to add details or results.

	All Staff are permitted to run Events. Trial Staff may ~~not~~ run ~~events, but~~ they ~~may participate.~~		All Staff are permitted to run Events. Trial-Staff may run Events if they first get permission from a C3 or higher by explaining their plans in a Staff visible channel, not DMs.

	~~Well administered events are considered~~ Staff ~~Labor~~.

	A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.		A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.
Line 46:		Line 44:
	Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.		Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.

	Events that use Central Command characters must respect ~~CentCom Policy limitation~~ on ~~their use~~. <!-- CentCom Policy does not currently exist, use the established rank structure in Lore:Nanotrasen for now. -->		Events that use Central Command characters must respect the Rank structure found on [[Lore:Nanotrasen]]. Crew may only play characters that are Privates / Interns. <!-- CentCom Policy does not currently exist, use the established rank structure in Lore:Nanotrasen for now. -->

	=== Event Operations ===		=== Event Operations ===
Line 60:		Line 58:
	Ensure that you are able to authorize the Event in its entirety before showing public interest in running the Event. If you have concerns, ask senior Staff for input in Staff channels.		Ensure that you are able to authorize the Event in its entirety before showing public interest in running the Event. If you have concerns, ask senior Staff for input in Staff channels.

	When supporting a Crew Event, you have an Obligation to make sure the Event meets all our usual expectations, and that the Event does not interfere with any other prepared events in ~~#staff-events, the #events-forum, or #staff-happenings~~.		When supporting a Crew Event, you have an Obligation to make sure the Event meets all our usual expectations, and that the Event does not interfere with any other prepared events you can find in Staff categories.

	Any Crew Events that you support and run must be logged separately in the Events Log thread. Cover your ass, document what you do as you do it.		Any Crew Events that you support and run must be logged separately in the Events Log thread. Cover your ass, document what you do as you do it.

Moonridden: details

2026-01-04T19:18:18Z

details

← Older revision		Revision as of 19:18, 4 January 2026
Line 56:		Line 56:

	=== Crew Events ===		=== Crew Events ===
	Crew may post Event ideas in the #~~crew~~-events channel on our Discord. You may engage with and support these Events at your discretion. Follow the current Staff expectations in the Crew Events Forum Information thread.		Crew may post Event ideas in the #public-events channel on our Discord. You may engage with and support these Events at your discretion. Follow the current Staff expectations in the Crew Events Forum Information thread.

	Ensure that you are able to authorize the Event in its entirety before showing public interest in running the Event. If you have concerns, ask senior Staff for input in Staff channels.		Ensure that you are able to authorize the Event in its entirety before showing public interest in running the Event. If you have concerns, ask senior Staff for input in Staff channels.

Moonridden: Crew Events Policy

2026-01-04T18:26:44Z

Crew Events Policy

← Older revision		Revision as of 18:26, 4 January 2026
Line 46:		Line 46:
	Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.		Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.

	Events that use Central Command characters must respect CentCom Policy limitation on their use.		Events that use Central Command characters must respect CentCom Policy limitation on their use. <!-- CentCom Policy does not currently exist, use the established rank structure in Lore:Nanotrasen for now. -->

	=== Event Operations ===		=== Event Operations ===
Line 54:		Line 54:

	You must inquire with the Event Leaders to add, modify, or contribute content in their event. Issues regarding an event should be directed to the Event Leaders, or Staff Manager.		You must inquire with the Event Leaders to add, modify, or contribute content in their event. Issues regarding an event should be directed to the Event Leaders, or Staff Manager.

			=== Crew Events ===
			Crew may post Event ideas in the #crew-events channel on our Discord. You may engage with and support these Events at your discretion. Follow the current Staff expectations in the Crew Events Forum Information thread.

			Ensure that you are able to authorize the Event in its entirety before showing public interest in running the Event. If you have concerns, ask senior Staff for input in Staff channels.

			When supporting a Crew Event, you have an Obligation to make sure the Event meets all our usual expectations, and that the Event does not interfere with any other prepared events in #staff-events, the #events-forum, or #staff-happenings.

			Any Crew Events that you support and run must be logged separately in the Events Log thread. Cover your ass, document what you do as you do it.

	=== Lore Team Obligations ===		=== Lore Team Obligations ===

Moonridden: Disaster event policy update

2025-12-05T00:15:33Z

Disaster event policy update

← Older revision		Revision as of 00:15, 5 December 2025
Line 151:		Line 151:

	==== Who can run a Disaster Event? ====		==== Who can run a Disaster Event? ====
	All intentional Disaster Events must be approved by an Event Curator or Staff ~~Manager~~.		All intentional Disaster Events must be approved by an Event Curator or Class 3 Staff. Large Disasters must be announced two shifts in advance.

	Large Disasters

	==== What is a Disaster Event? ====		==== What is a Disaster Event? ====

Moonridden: Establishes player and staff expectations around event interaction utilizing Antag Opt-In status as a basis.

2025-11-26T02:18:00Z

Establishes player and staff expectations around event interaction utilizing Antag Opt-In status as a basis.

← Older revision		Revision as of 02:18, 26 November 2025
Line 42:		Line 42:
	Well administered events are considered Staff Labor.		Well administered events are considered Staff Labor.

	~~An event should keep in mind~~ the ~~players participating, or being made~~ to participate.		A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.

	Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.		Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.

← Older revision		Revision as of 17:09, 28 March 2026
Line 22:		Line 22:
	''The writer(s) jointly provide a statement on the policy.''		''The writer(s) jointly provide a statement on the policy.''

	Event Policy is one of the few fully new and meaningful bits of Staff Policy that has come about with the changing of hands and player base over time. We're all learning together, and this document exists to help keep our silly events a reality.		Event Policy is one of the few fully new and meaningful bits of [[Staff_Policy\|Staff Policy]] that has come about with the changing of hands and player base over time. We're all learning together, and this document exists to help keep our silly events a reality.

	'''Writer 1 - Moonridden/Moonridden'''		'''Writer 1 - Moonridden/Moonridden'''
Line 38:		Line 38:
	Events must be logged in the Event Log thread. It is recommended you post your log with your plans prior to starting your Event, and then update or reply with additional details later or after the event.		Events must be logged in the Event Log thread. It is recommended you post your log with your plans prior to starting your Event, and then update or reply with additional details later or after the event.

	All Staff are permitted to run Events. Trial-Staff may run Events if they first get permission from a C3 or higher by explaining their plans in a Staff visible channel, not DMs.		All Staff are permitted to run Events. Trial-Staff may run Events if they first get permission from a [[Staff_Policy#Staff_Hierarchy\|C3 or higher]] by explaining their plans in a Staff visible channel, not DMs.

	A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.		A Player's Antag Opt-In Status is used to decide the depth to which the Player wishes to participate in Event-based Antagonism or Threat, and should be respected unless there are extenuating circumstances.
Line 44:		Line 44:
	Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.		Characters that are normally station crew should not suddenly be in extremely important positions or flip-flopping into roles that break suspension of disbelief.

	Events that use Central Command characters must respect the Rank structure found on [[Lore:Nanotrasen]]. Crew may only play characters that are Privates / Interns. <!-- CentCom Policy does not currently exist, use the established rank structure in Lore:Nanotrasen for now. -->		Events that use Central Command characters must respect the Rank structure found on [[Lore:Nanotrasen]]. Crew may only play characters that are Privates / Interns. <!-- CentCom Policy does not currently exist, use the established rank structure in Lore:Nanotrasen's comments (use Edit/View Source to see) for now. -->

	=== Event Operations ===		=== Event Operations ===
Line 51:		Line 51:
	Large Events create a lockout for all other Staff on usage running other Events, or 'loud' usage of Staff tools such as the Aux Cord.		Large Events create a lockout for all other Staff on usage running other Events, or 'loud' usage of Staff tools such as the Aux Cord.

	You must inquire with the Event Leaders to add, modify, or contribute content in their event. Issues regarding an event should be directed to the Event Leaders, or Staff Manager.		You must inquire with the Event Leaders to add, modify, or contribute content in their event. Issues regarding an event should be directed to the Event Leaders, or [[Staff_Policy#Staff_Hierarchy\|Staff Manager]].

	If a planned Event needs the shift prior to be cut short or extended to meet scheduling demands, Staff should update the Title Screen Notice.		If a planned Event needs the shift prior to be cut short or extended to meet scheduling demands, Staff should update the Title Screen Notice.
Line 160:		Line 160:

	==== Who can run a Disaster Event? ====		==== Who can run a Disaster Event? ====
	All intentional Disaster Events must be approved by an Event Curator or Class 3 Staff. Large Disasters must be announced two shifts in advance.		All intentional Disaster Events must be approved by an [[Staff_Policy#Staff_Hierarchy\|Event Curator or Class 3 Staff]]. Large Disasters must be announced two shifts in advance.

	==== What is a Disaster Event? ====		==== What is a Disaster Event? ====