Event Policy - Revision history

DV vapetastic at 17:46, 7 September 2026

2026-09-07T17:46:10Z

← Older revision		Revision as of 13:46, 7 September 2026
Line 58:		Line 58:
	1a. '''Staff are permitted to spawn in Central Command characters for the purposes of teaching or training new crew specifically on arrivals station (transit hub) .''' <sub>any character spawned, must be deleted when the "new player" leaves the arrivals station.</sub>		1a. '''Staff are permitted to spawn in Central Command characters for the purposes of teaching or training new crew specifically on arrivals station (transit hub) .''' <sub>any character spawned, must be deleted when the "new player" leaves the arrivals station.</sub>

	2. '''Staff are permitted to create ghost bars.''' <small>Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC</small>		2. '''Staff are permitted to create ghost bars.''' <small>Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC, all radio's must be removed.</small>

	3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>		3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>

DV vapetastic: /* Exceptions to event policy */

2026-09-07T17:44:42Z

Exceptions to event policy

← Older revision		Revision as of 13:44, 7 September 2026
Line 55:		Line 55:

	1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' <small>CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.</small>		1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' <small>CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.</small>

			1a. '''Staff are permitted to spawn in Central Command characters for the purposes of teaching or training new crew specifically on arrivals station (transit hub) .''' <sub>any character spawned, must be deleted when the "new player" leaves the arrivals station.</sub>

	2. '''Staff are permitted to create ghost bars.''' <small>Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC</small>		2. '''Staff are permitted to create ghost bars.''' <small>Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC</small>

DV vapetastic: Deathsquad change

2026-09-07T17:37:45Z

Deathsquad change

← Older revision		Revision as of 13:37, 7 September 2026
Line 10:		Line 10:
	4. '''Events must meet or exceed our MRP Standard.''' <small>Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.</small>		4. '''Events must meet or exceed our MRP Standard.''' <small>Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.</small>

	5. '''Events must not feature staff-level ghost roles such as ~~deathsquad~~ unless directly authorized by a Head of Staff.''' <small>These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.</small>		5. '''Events must not feature staff-level ghost roles such as SRT unless directly authorized by a Head of Staff.''' <small>These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.</small>

	6. '''Events should never portray ''<span style="color:cyan;">NanoTrasen'' or ''<span style="color:green;">Central Command'' as directly antagonistic to the crew.''' <small>While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.</small>		6. '''Events should never portray ''<span style="color:cyan;">NanoTrasen'' or ''<span style="color:green;">Central Command'' as directly antagonistic to the crew.''' <small>While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.</small>

DV disposablecrewmember42: Reverted edit by DV disposablecrewmember42 (talk) to last revision by Vape

2026-08-19T18:28:59Z

Reverted edit by DV disposablecrewmember42 (talk) to last revision by Vape

← Older revision		Revision as of 14:28, 19 August 2026
Line 60:		Line 60:
	3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>		3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>

	4. '''Staff are permitted to Spawn ERT following ~~[https://knowledge.deltav.gay/ingame/eventing/ERT.html#emergency-call this~~ chart].''' <small><span style="color:red;">Any exceptions require approval from a Senior Administrator/Senior Curator or above.</small>		4. '''Staff are permitted to Spawn ERT following the chart listed below.''' <small><span style="color:red;">Any exceptions require approval from a Senior Administrator/Senior Curator or above.</small>

			[[File:ERT chart.jpg\|thumb]]












	= Epsilon Procedure =		= Epsilon Procedure =

	<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.		<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

DV disposablecrewmember42: link chart in knowledgebase instead

2026-08-19T18:12:58Z

link chart in knowledgebase instead

← Older revision		Revision as of 14:12, 19 August 2026
Line 60:		Line 60:
	3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>		3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>

	4. '''Staff are permitted to Spawn ERT following ~~the~~ chart ~~listed below~~.''' <small><span style="color:red;">Any exceptions require approval from a Senior Administrator/Senior Curator or above.</small>		4. '''Staff are permitted to Spawn ERT following [https://knowledge.deltav.gay/ingame/eventing/ERT.html#emergency-call this chart].''' <small><span style="color:red;">Any exceptions require approval from a Senior Administrator/Senior Curator or above.</small>

	~~[[File:ERT chart.jpg\|thumb]]~~












	= Epsilon Procedure =		= Epsilon Procedure =

	<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.		<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

Vape: Updates to event policy

2026-06-09T23:19:54Z

Updates to event policy

← Older revision		Revision as of 19:19, 9 June 2026
Line 24:		Line 24:
	11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''		11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

	12. '''Any spawned CC character going to the station, must be armed by security on station.''' <small><span style="color:red;">If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them.</small>		12. '''Any spawned CC character going to the station, must be armed by security on station.''' <small><span style="color:red;">If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.</small>

	= Event Categories =		= Event Categories =

	* '''<span style="color:green;">Low Impact''' - ~~<small>These events may be run by</small>~~ '''<span style="color:green;">Trial-Game Administrators''' / '''<span style="color:orange;">Trial-Curators''' <small>or above without approval.</small>		* '''<span style="color:green;">Low Impact''' - '''<span style="color:green;">Trial-Game Administrators''' / '''<span style="color:orange;">Trial-Curators''' <small>or above without approval.</small>
	Low impact events either:		Low impact events either:
	* Do not interact with players in a meaningful way		* Do not interact with players in a meaningful way
Line 34:		Line 34:
	-> Such as responding to faxes or answering prayers		-> Such as responding to faxes or answering prayers

	* '''<span style="color:yellow;">Medium Impact''' - ~~<small>These events may be run by</small>~~ '''<span style="color:green;">Trial-Game Administrators''' / '''<span style="color:orange;">Trial-Curators''' <small>with approval from a ~~second (non-trial) Staff member~~.</small> '''<span style="color:green;">~~Senior~~ Administrators''' / '''<span style="color:orange;">Senior Curators''' <small>and above do not need approval.</small>		* '''<span style="color:yellow;">Medium Impact''' - '''<span style="color:green;">Trial-Game Administrators''' / '''<span style="color:orange;">Trial-Curators''' <small>with approval from a '''<span style="color:orange;">Curator'''.</small> '''<span style="color:green;">Game Administrators''' / '''<span style="color:orange;">Curators''' <small>without approval.</small> '''<span style="color:orange;">Senior Curators''' / '''<span style="color:green;">Senior Administrators''' <small>and above do not need approval.</small>
	Medium impact events either		Medium impact events either
	* Considerable affect players or the round without derailing the round, round-removing		* Considerable affect players or the round without derailing the round, round-removing
Line 42:		Line 42:
	-> Such as adding a Clown Spider spawn or adding a single round ending antag		-> Such as adding a Clown Spider spawn or adding a single round ending antag

	* '''<span style="color:red;">High Impact''' - <small>~~These events may be run following~~ the mandatory notice ~~(when applicable)~~ and when approved by a</small> '''<span style="color:orange;">Senior Curator~~''' / '''<span style="color:green;">Senior Administrator~~''' <small>or above.</small>		* '''<span style="color:red;">High Impact''' - <small>Following the mandatory notice and when approved by a</small> '''<span style="color:orange;">Senior Curator''' <small>or above.</small>
	High impact events either:		High impact events either:
	* Heavily affect players or the round, possibly derailing the round, round-removing		* Heavily affect players or the round, possibly derailing the round, round-removing
Line 50:		Line 50:
	-> Some Examples include setting the game mode or spawning multiple round ending antagonists		-> Some Examples include setting the game mode or spawning multiple round ending antagonists

	⚠️'''<span style="color:red;">High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory ~~two hour~~ notice must be posted in the event log prior to running these events, unless otherwise ~~authorised~~ by at least a Senior ~~Administrator, Senior Curator~~, or Head of Staff. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️		⚠️'''<span style="color:red;">High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory 30 minute notice must be posted & approved in the event log prior to running these events, unless otherwise authorized by at least 2 Senior Curators, or 1 Head of Staff. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

	== Exceptions to event policy ==		== Exceptions to event policy ==

Vape: Updates and grammatical / organizational maintenance

2026-06-09T23:01:46Z

Updates and grammatical / organizational maintenance

← Older revision		Revision as of 19:01, 9 June 2026
Line 77:		Line 77:
	= Epsilon Procedure =		= Epsilon Procedure =

	<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable~~, the agreement of <span style="color:orange;">2 Non-Trial Curators or Admins <span style="color:red;">can pass this only <span style="color:orange;">~~after 10 minutes without ~~answer''~~		<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

Vape at 20:09, 16 May 2026

2026-05-16T20:09:35Z

← Older revision		Revision as of 16:09, 16 May 2026
Line 63:		Line 63:

	[[File:ERT chart.jpg\|thumb]]		[[File:ERT chart.jpg\|thumb]]












			= Epsilon Procedure =

			<span style="color:red;">''In the event that Epsilon is or will be needed, Permission is required by a <span style="color:orange;">HEAD OF STAFF or SENIOR CURATOR. <span style="color:red;">If either of these options are unavailable, the agreement of <span style="color:orange;">2 Non-Trial Curators or Admins <span style="color:red;">can pass this only <span style="color:orange;">after 10 minutes without answer''

Vape: Protected "Event Policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2026-01-28T19:05:53Z

Protected "Event Policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 15:05, 28 January 2026
(No difference)

Vape: Added color, we are no longer in the stone age

2026-01-28T19:03:51Z

Added color, we are no longer in the stone age

← Older revision		Revision as of 15:03, 28 January 2026
Line 3:		Line 3:
	1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' <small>This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.</small>		1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' <small>This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.</small>

	2. '''Never use a “smite” against a player character that is in round.''' <small>This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.</small>		2. '''<span style="color:red;">Never''' '''use a “smite” against a player character that is in round.''' <small>This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.</small>

	3. '''Events should be allowed to play out at their own pace.''' <small>Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.		3. '''Events should be allowed to play out at their own pace.''' <small>Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.
	</small>		</small>

	4. '''Events must meet or exceed our MRP Standard.''' <small>Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.</small>		4. '''Events must meet or exceed our MRP Standard.''' <small>Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.</small>

	5. '''Events must not feature staff-level ghost roles such as deathsquad unless directly authorized by a Head of Staff.''' <small>These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.</small>		5. '''Events must not feature staff-level ghost roles such as deathsquad unless directly authorized by a Head of Staff.''' <small>These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.</small>

	6. '''Events should never portray NanoTrasen or Central Command as directly antagonistic to the crew.''' <small>While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.</small>		6. '''Events should never portray ''<span style="color:cyan;">NanoTrasen'' or ''<span style="color:green;">Central Command'' as directly antagonistic to the crew.''' <small>While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.</small>

	7. '''Events should not disrupt the balance of the round.''' <small>Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.</small>		7. '''Events should not disrupt the balance of the round.''' <small>Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.</small>

	8. '''Event roles should be reserved for players.''' <small>Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for more than 5 minutes, the eventing staff member may join the queue .</small>		8. '''Event roles should be reserved for players.''' <small>Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for '''<span style="color:yellow;">more than 5 minutes''', the eventing staff member may join the queue .</small>

	9. '''aGhosts are welcome to take any ghost roles.''' <small>Refer to the previous rule regarding roles you have spawned.</small>		9. '''aGhosts are welcome to take any ghost roles.''' <small>Refer to the previous rule regarding roles you have spawned.</small>
Line 23:		Line 24:
	11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''		11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

	12. '''Any spawned CC character going to the station, must be armed by security on station.''' <small>If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them.</small>		12. '''Any spawned CC character going to the station, must be armed by security on station.''' <small><span style="color:red;">If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them.</small>

	= Event Categories =		= Event Categories =

	* '''Low Impact''' - <small>These events may be run by</small> '''Trial-Game Administrators''' / '''Trial-Curators''' <small>or above without approval.</small>		* '''<span style="color:green;">Low Impact''' - <small>These events may be run by</small> '''<span style="color:green;">Trial-Game Administrators''' / '''<span style="color:orange;">Trial-Curators''' <small>or above without approval.</small>
	Low impact events either:		Low impact events either:
	* Do not interact with players in a meaningful way		* Do not interact with players in a meaningful way
Line 33:		Line 34:
	-> Such as responding to faxes or answering prayers		-> Such as responding to faxes or answering prayers

	* '''Medium Impact''' - <small>These events may be run by</small> '''Trial-Game Administrators/Trial-Curators''' <small>with approval from a second (non-trial) Staff member.</small> '''Senior Administrators/Senior Curators''' <small>and above do not need approval.</small>		* '''<span style="color:yellow;">Medium Impact''' - <small>These events may be run by</small> '''<span style="color:green;">Trial-Game Administrators''' / '''<span style="color:orange;">Trial-Curators''' <small>with approval from a second (non-trial) Staff member.</small> '''<span style="color:green;">Senior Administrators''' / '''<span style="color:orange;">Senior Curators''' <small>and above do not need approval.</small>
	Medium impact events either		Medium impact events either
	* Considerable affect players or the round without derailing the round, round-removing		* Considerable affect players or the round without derailing the round, round-removing
Line 41:		Line 42:
	-> Such as adding a Clown Spider spawn or adding a single round ending antag		-> Such as adding a Clown Spider spawn or adding a single round ending antag

	* '''High Impact''' - <small>These events may be run following the mandatory notice (when applicable) and when approved by a</small> '''Senior Curator/Senior Administrator''' <small>or above.</small>		* '''<span style="color:red;">High Impact''' - <small>These events may be run following the mandatory notice (when applicable) and when approved by a</small> '''<span style="color:orange;">Senior Curator''' / '''<span style="color:green;">Senior Administrator''' <small>or above.</small>
	High impact events either:		High impact events either:
	* Heavily affect players or the round, possibly derailing the round, round-removing		* Heavily affect players or the round, possibly derailing the round, round-removing
Line 49:		Line 50:
	-> Some Examples include setting the game mode or spawning multiple round ending antagonists		-> Some Examples include setting the game mode or spawning multiple round ending antagonists

	⚠️'''High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory two hour notice must be posted in the event log prior to running these events, unless otherwise authorised by at least a Senior Administrator, Senior Curator, or Head of Staff. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️		⚠️'''<span style="color:red;">High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory two hour notice must be posted in the event log prior to running these events, unless otherwise authorised by at least a Senior Administrator, Senior Curator, or Head of Staff. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

	== Exceptions to event policy ==		== Exceptions to event policy ==
Line 59:		Line 60:
	3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>		3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' <small>The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval</small>

	4. '''Staff are permitted to Spawn ERT following the chart listed below.''' <small>Any exceptions require approval from a Senior Administrator/Senior Curator or above.</small>		4. '''Staff are permitted to Spawn ERT following the chart listed below.''' <small><span style="color:red;">Any exceptions require approval from a Senior Administrator/Senior Curator or above.</small>

	[[File:ERT chart.jpg\|thumb]]		[[File:ERT chart.jpg\|thumb]]