View source for Event Policy

''This policy refers to Administrators and Curators, Unless otherwise specified.''

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. '''<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.
</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>

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>

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>

10. '''Do not test unknown commands on the game servers.''' <small>All testing of Console commands, VVwrites, and other “Unused” aGhost powers should take place on a personal dev environment, not on the game servers.</small>

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. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.</small>

= Event Categories = 

* '''<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:
  * Do not interact with players in a meaningful way
  * Are a direct response to a player request or interaction, and do not affect the round to a greater degree 
 -> Such as responding to faxes or answering prayers

* '''<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
 * Considerable affect players or the round without derailing the round, round-removing
 players, or taking significant resources and manpower from departments.
 * Add a new gamerule unlikely to cause significant effect on players or the round
 * Are a direct response to a player request or interaction that affects the round to a considerable degree.
 -> Such as adding a Clown Spider spawn or adding a single round ending antag

* '''<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:
 * Heavily affect players or the round, possibly derailing the round, round-removing 
 players, or taking significant resources and manpower from departments
 * Add a new gamemode, causing significant effect on players or the round
 * Are a direct response to a player request or interaction that results in a High Impact event.
 -> 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 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 ==

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>

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>

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>

[[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 after 10 minutes, you may call gamma and resolve the situation without violence.