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

2. Never use a “smite” against a player character that is in round. This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.

3. Events should be allowed to play out at their own pace. 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.

4. Events must meet or exceed our MRP Standard. 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.

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

6. Events should never portray NanoTrasen or Central Command as directly antagonistic to the crew. 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.

7. Events should not disrupt the balance of the round. 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.

8. Event roles should be reserved for players. 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 .

9. aGhosts are welcome to take any ghost roles. Refer to the previous rule regarding roles you have spawned.

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

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. If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them.

Event Categories

• Low Impact - These events may be run by Trial-Game Administrators / Trial-Curators or above without approval.

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

• Medium Impact - These events may be run by Trial-Game Administrators / Trial-Curators with approval from a second (non-trial) Staff member. Senior Administrators / Senior Curators and above do not need approval.

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

• High Impact - These events may be run following the mandatory notice (when applicable) and when approved by a Senior Curator / Senior Administrator or above.

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

⚠️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

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

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

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. The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval

4. Staff are permitted to Spawn ERT following the chart listed below. Any exceptions require approval from a Senior Administrator/Senior Curator or above.