Delta-V Wiki - User contributions [en]

SESD TBD

2026-05-22T02:09:59Z

Vape:

{{DISPLAYTITLE:Senior Staff Directory}}

== Senior Staff Guidelines ==
Senior Staff generally are encouraged to assist heads by performing assigned tasks. This document has been made to list out some of those tasks that are "Regular Occurrences" and the expectations of what Senior level staff are expected to do / Perform. This document, while official, is subject to change at any time with the request of the direct head of staffs request. Senior Staff are expected to understand what they are empowered to perform, and what should be taken to a head.

=== Senior Content Review ===
Senior Content Reviewers are expected to:

* Ensure Reviews are performed in a timely manner
* Be knowledgeable on the Review Policy, and at times, encourage reviewers to stick to this policy
* Make decisions regarding the need for a review
* Make decisions regarding Test Merges
* Assist the Content Director with any additional tasks that are needed / requested
* Assist in continuance of training regarding new reviewers, and should be capable of explaining "How To" perform the daily tasks of a Content Reviewer

Should a scenario occur where policy is not being followed, and a simple encouragement does not suffice, Seniors are expected to report this to the Content Director, without taking this into their own hands.

=== Senior Moderation ===
Senior Moderators are expected to:

* Perform in-depth investigations into Mhelps
* Perform in-depth investigations into staff reports that are relevant to their accesses
* Assist the Head Moderator in ongoing investigations that their access allows
* Educate and Guide new moderators with Mod Policy
* Should be capable of stepping into a ticket should a Mod become overwhelmed or overstepped

Should a scenario occur where policy is not being followed, and a simple encouragement does not suffice, Seniors are expected to report this to the Head Moderator, without taking this into their own hands.

=== Senior Administration ===
Senior Administrators are expected to:

* Provide Guidance on rulings that are complex to Admins
* Refer to previous rulings on similar situations, and make similar rulings as needed
* Understand how to perform Log Diving investigations, and be capable of teaching this to Trials and Game admins
* Be knowledgeable in the rules, and capable of identifying what rules have been broken
* Encourage Game admins and Trials to follow rulings, and to not intervene in situations that should be handled "In Character"
* Be capable in defusing a situation, whether this is between staff or players
* Should be capable of stepping into a ticket should an Admin become overwhelmed or overstepped
* Regularly check Senior Admin Channels and forums for important information and changing dynamics as informed by the headmins.

Should a scenario occur where policy is not being followed, and a simple encouragement does not suffice, Seniors are expected to report this to the Head Administrator, without taking this into their own hands. Should a scenario occur where a clear violation of Admin Policy is in order, Senior Admins are suggested to form a Staff report with relevant information.

=== Senior Curators / Eventers ===

Staff HQ

2026-05-22T02:09:28Z

Vape:

{| class="wikitable " style="background-color: #021d29; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Review!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| [[SESD TBD|Senior Staff Directory]]
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| [[Staff Onboarding]] || [[Content Removal]]|| ||
|[[Administrative Rulings]]
|[[Mod Policy]]
|}

Alert Procedure

2026-05-19T01:34:14Z

Vape: removed "Sheilds" from green alert

== Green Alert ==
The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Open carrying of long arms disallowed for Security personnel. Standard stab-and bullet-resistant equipment recommended for Security personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for general orders.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | Secure areas unbolted and accessible to all authorized personnel. HSAs and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be bolted as needed.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Binary suit sensors recommended at a minimum.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | Report to supervisor for general orders.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with minimal force required; prioritize de-escalation whenever possible.
|}

== Blue Alert ==
Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > [[Head of Security|Head of Station Security]] > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Open carry of weaponry permitted for all authorised entities. Body armour mandatory for Security personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for general orders. Searching individuals suspected of committing a crime is encouraged.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | Secure areas unbolted unless affected by known threats. Bolting [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] recommended.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits recommended for engineers.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.
|}

== Red Alert ==
Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > Security Personnel > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for general orders. Protection of personnel prioritized over body and department searches.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | All [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] recommended to be bolted and under guard. Secure areas unbolted unless affected by known threats.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits heavily advised for engineers. Make emergency internals easily accessible.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.
|}

== Violet Alert ==
Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > [[Chief Medical Officer]] > Medical Personnel > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Biohazard gear advised.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff. Security should seek to aid medical staff where possible.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | Secure areas unbolted. [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be bolted as needed.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | Report to supervisor for general orders.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with minimal force required; prioritize de-escalation whenever possible.
|}

== Yellow Alert ==
Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > [[Chief Engineer]] > Engineering Personnel > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas. Security should seek to aid engineering staff where possible.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | Secure areas unbolted. [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be bolted as needed.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with minimal force required; prioritize de-escalation whenever possible.
|}

== White Alert ==
Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > [[Mystagogue]] > Epistemics Personnel > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Psionic insulation recommended for all personnel. Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for orders. Security and Engineering should seek to aid epistemics staff where possible. Propose evacuation if glimmer spiral is unrecoverable.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | Secure areas unbolted. [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be bolted as needed.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with minimal force required; ROE on mindwiping is lifted and may be performed by the Psionic Mantis, Chaplain or Mystagogue at their discretion.
|}

== Gamma Alert ==
Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > Security Personnel > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel. EVA protection heavily advised for all personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Report to supervisor for general orders. Martial law is in effect.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | All [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] recommended to be bolted and under guard. Secure areas unbolted.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits heavily advised for engineers. Distribute emergency internals to crew.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Martial law is in effect.
|}

== Delta Alert ==
Emergency alert status. ''The nuclear destruction mechanism has been engaged and station destruction is imminent. All crew aboard the station must attempt to reverse the self-destruct mechanism, if engaged in error. Should reversal prove impossible, evacuate as applicable.
''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > Security Personnel > Department Heads > Supervisory Roles
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel. EVA protection heavily advised for all personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Security and Command must expend all efforts to prevent station destruction if engaged in error. Martial law is in effect.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | All secure areas and [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] should remain unbolted.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits heavily advised for engineers. Distribute emergency internals to crew.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Martial law is in effect.
|}

== Code Octarine ==
Emergency alert status''. The station's deep-spectrum sensors have identified critical Λ-CDM levels. The station and all surrounding space is under threat of an impending existential noospheric-to-real threat.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] > [[Mystagogue]] > Security Personnel > Department Heads > Supervisory Roles >
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Issuing of lethal weapons recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection strongly advised for all personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Emergency personnel must expend all efforts to prevent station destruction. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Where possible, threats should be subdued and brought to the Chaplain or Mystagogue for processing.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | All secure areas and [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] should remain unbolted.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | EVA suits heavily advised for engineers. Distribute emergency internals to crew.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests. ROE on mindwiping is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.
|}

== Code Epsilon ==
Emergency alert status. ''Central Command has ordered the Epsilon security level on the station. Only orders from Central Command Officials are to be obeyed by the Station's Crew. Martial Law is in effect.''

{| class="wikitable" style="width: 80%; border: 1px solid #000000;"
!style="text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#b000ffFF; border: 1px solid #000000;" | '''Condition'''
!style="text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#b000ffFF; border: 1px solid #000000;" | '''Description'''
|-
| style="border: 1px solid #000000;" | Chain of Command
| style="border: 1px solid #000000;" | Central Command
|-
| style="border: 1px solid #000000;" | Armoury Policy
| style="border: 1px solid #000000;" | Await orders from Central Command Personnel.
|-
| style="border: 1px solid #000000;" | Discipline
| style="border: 1px solid #000000;" | Await orders from Central Command Personnel.
|-
| style="border: 1px solid #000000;" | Secure Areas
| style="border: 1px solid #000000;" | Await orders from Central Command Personnel.
|-
| style="border: 1px solid #000000;" | Medical
| style="border: 1px solid #000000;" | Full suit sensors mandatory for observation and safety. Await orders from Central Command Personnel.
|-
| style="border: 1px solid #000000;" | Engineering
| style="border: 1px solid #000000;" | Await orders from Central Command Personnel.
|-
| style="border: 1px solid #000000;" | Rules of Engagement
| style="border: 1px solid #000000;" | Martial Law is in effect. Do not engage with Central Command Personnel. Await orders from Central Command Personnel.
|}

{{Guides Menu}}

Event Policy

2026-05-16T20:09:35Z

Vape:

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

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

= Epsilon Procedure =

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

Content Removal

2026-05-08T16:54:49Z

Vape:

'''<big>Content Removal Policy</big>'''

In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible.

Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”.

=== '''In order to remove content, You must:''' ===

* Make a list of issues with the content

*Announce the planned removal of the content, including a date, and its issues - For classifications of "Major Content" only

*Create a community feedback post regarding the removal, the issues, and a specific date of removal.

* Establish a deadline for action (Removal or Replacement)

=== Appropriate Deadlines: ===

* 1 week - minor to moderate content (Sprites, Mechanical balances, Items, Machines, Etc)

* 2 weeks - Major content (Gamemodes, Roles, Multiple minor/moderate content items as a "bundle"** Etc)

Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process

If Community feedback for removal is overwhelmingly negative, Content Review is required to seek approval of both the Content Director and the Project Management Team before finalizing removal.

Content removal at an authors request will be '''considered''' and ''should require a valid reason, such as balance concerns, server stability concerns, or lack of implementation (e.g. not finished).'' The Content Director and Maintainers will have final say on removal via author request, due to content direction and feasibility of removal respectively. ''Content that has been worked on by multiple contributors (E.g. Spritework + Code) will only be removed when all parties that contributed request removal.''

<nowiki>**</nowiki> Bundles are considered any content that includes more than 1 item. Some examples include superweapons or the improvised armory. Bundles do not include items that require specific parts to function, such as "blunderbuss" and "Blunderbuss ammo", as an example.

Content Removal

2026-05-08T16:54:17Z

Vape:

Content Removal

2026-05-08T16:49:17Z

Vape:

'''<big>Content Removal Policy</big>'''

In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible.

Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”.

=== '''In order to remove content, You must:''' ===

* Make a list of issues with the content

*Announce the planned removal of the content, including a date, and its issues - For classifications of "Major Content" only

*Create a community feedback post regarding the removal, the issues, and a specific date of removal.

* Establish a deadline for action (Removal or Replacement)

=== Appropriate Deadlines: ===

* 1 week - minor to moderate content (Sprites, Mechanical balances, Items, Machines, Etc)

* 2 weeks - Major content (Gamemodes, Roles, Multiple minor/moderate content items as a "bundle" Etc)

Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process.

If Community feedback for removal is overwhelmingly negative, Content Review is required to seek approval of both the Content Director and the Project Management Team before finalizing removal.

Content removal at an authors request will be '''considered''' and ''should require a valid reason, such as balance concerns, server stability concerns, or lack of implementation (e.g. not finished).'' The Content Director and Maintainers will have final say on removal via author request, due to content direction and feasibility of removal respectively. ''Content that has been worked on by multiple contributors (E.g. Spritework + Code) will only be removed when all parties that contributed request removal.''

Content Removal

2026-05-08T16:15:54Z

Vape: Requested Changes to policy

'''<big>Content Removal Policy</big>'''

In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible.

Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”.

=== '''In order to remove content, You must:''' ===

* Make a list of issues with the content

*Announce the planned removal of the content, including a date, and its issues - For classifications of "Major Content" only, see below

*Create a community feedback post regarding the removal, the issues, and a specific date of removal.

* Establish a deadline for action (Removal or Replacement)

=== Appropriate Deadlines: ===

* 1 week - minor to moderate content (Sprites, Mechanical balances, Items, Machines, Etc)

* 2 weeks - Major content (Gamemodes, Roles, Multiple minor/moderate content items as a "bundle" Etc)

Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process.

If Community feedback for removal is overwhelmingly negative, Content Review is required to seek approval of both the Content Director and the Project Management Team before finalizing removal.

Content removal at an authors request will be '''considered''' and ''should require a valid reason, such as balance concerns, server stability concerns, or lack of implementation (e.g. not finished).'' The Content Director and Maintainers will have final say on removal via author request, due to content direction and feasibility of removal respectively. ''Content that has been worked on by multiple contributors (E.g. Spritework + Code) will only be removed when all parties that contributed request removal.''

SESD TBD

2026-05-05T15:44:15Z

Vape: Created page with "== Senior Staff Guidelines == Senior Staff generally are encouraged to assist heads by performing assigned tasks. This document has been made to list out some of those tasks that are "Regular Occurrences" and the expectations of what Senior level staff are expected to do / Perform. This document, while official, is subject to change at any time with the request of the direct head of staffs request. Senior Staff are expected to understand what they are empowered to perfor..."

== Senior Staff Guidelines ==
Senior Staff generally are encouraged to assist heads by performing assigned tasks. This document has been made to list out some of those tasks that are "Regular Occurrences" and the expectations of what Senior level staff are expected to do / Perform. This document, while official, is subject to change at any time with the request of the direct head of staffs request. Senior Staff are expected to understand what they are empowered to perform, and what should be taken to a head.

=== Senior Content Review ===
Senior Content Reviewers are expected to:

* Ensure Reviews are performed in a timely manner
* Be knowledgeable on the Review Policy, and at times, encourage reviewers to stick to this policy
* Make decisions regarding the need for a review
* Make decisions regarding Test Merges
* Assist the Content Director with any additional tasks that are needed / requested
* Assist in continuance of training regarding new reviewers, and should be capable of explaining "How To" perform the daily tasks of a Content Reviewer

Should a scenario occur where policy is not being followed, and a simple encouragement does not suffice, Seniors are expected to report this to the Content Director, without taking this into their own hands.

=== Senior Moderation ===
Senior Moderators are expected to:

* Perform in-depth investigations into Mhelps
* Perform in-depth investigations into staff reports that are relevant to their accesses
* Assist the Head Moderator in ongoing investigations that their access allows
* Educate and Guide new moderators with Mod Policy
* Should be capable of stepping into a ticket should a Mod become overwhelmed or overstepped

Should a scenario occur where policy is not being followed, and a simple encouragement does not suffice, Seniors are expected to report this to the Head Moderator, without taking this into their own hands.

=== Senior Administration ===
Senior Administrators are expected to:

* Provide Guidance on rulings that are complex to Admins
* Refer to previous rulings on similar situations, and make similar rulings as needed
* Understand how to perform Log Diving investigations, and be capable of teaching this to Trials and Game admins
* Be knowledgeable in the rules, and capable of identifying what rules have been broken
* Encourage Game admins and Trials to follow rulings, and to not intervene in situations that should be handled "In Character"
* Be capable in defusing a situation, whether this is between staff or players
* Should be capable of stepping into a ticket should an Admin become overwhelmed or overstepped
* Regularly check Senior Admin Channels and forums for important information and changing dynamics as informed by the headmins.

Should a scenario occur where policy is not being followed, and a simple encouragement does not suffice, Seniors are expected to report this to the Head Administrator, without taking this into their own hands. Should a scenario occur where a clear violation of Admin Policy is in order, Senior Admins are suggested to form a Staff report with relevant information.

=== Senior Curators / Eventers ===

Xenoarcheology

2026-05-05T01:41:47Z

Vape:

{{Needs revision
|reason=Information may still need photos, and still needs information regarding artifacts.
|image=RebaseWork.png
}}
Xenoarcheology is a method of point generation for [[Research_and_Development|R&D]] utilizing randomly generated artifacts. It is the job of [[Scientist|scientists]] to discover and activate the secrets of these artifacts.

__TOC__

== Equipment ==
The actual experimentation of artifacts uses a variety of equipment that can be found scattered around the station. This specifically focuses on the specific items used and contained within the xenoarcheology lab.

[[File:Analysis-console-ui.png|thumb|400px|''The analysis console ui before a scan.'']]
=== Analysis Console ===

[[File:Analysis Console.gif|64px]]

The analysis console is the main method of getting information about the artifacts that are being researched. In order to properly use it, it must be linked to an artifact analyzer via multitool as well as have a research server selected.

From the console itself, the screen displays information about the last artifact scanned. The buttons along the side perform various functions:

{| class="wikitable"
|-
! Button Name !! Description
|-
| Server List || Opens a menu for selecting a research server.
|-
| Extract || Extracts the research points from the artifact. The amount of points is based on how many nodes have been activated and will increase the glimmer count.
|}

=== Artifact Analyzer ===
[[File:Analyzer-full.png|64px]]

The artifact analyzer is a machine used in conjunction with the analysis console to scan artifacts to discover information about them. Artifacts are scanned by placing them on this machine at which point will show you information regarding tbe artifact.

=== Node Scanner ===
[[File:Node Scanner.png|64px]]

The archaeologist's friend. It's able to identify the node ID of the artifact.

== Artifacts ==
[[File:Artifact-lineup.png|448px]]

Artifacts are the core of Xenoarcheology and are what scientists will be analyzing and experimenting on. Artifacts can take on a variety of random appearances and can be acquired in various ways, such as through finding them in the lab at the start of the round, purchasing them from [[Cargo Technician|Logistics]], getting them from [[Salvage Specialist|Salvage]], or finding them from the Bluespace Anomaly station event.

Artifacts consist of randomly generated "trees" which dictates the artifacts behavior. Each tree consists of various "nodes" which the artifact can be inside of. Nodes each contain a "trigger" and an "effect". Effects can be both passive, constantly occurring and active, happening only once. To progress "up" to the next node in a tree, all other nodes below it must be completed. You will know a node is completed when the node is purple and the effect listed has gone off.

Some nodes will have multiple Stimulus in order to react, you must complete all required Stimulus in order to get the artifact to react and for the node to complete. You will have a set amount of time to complete all stimuli listed by the analysis console.

The activation of the various nodes is the main goal of Xenoarcheology. Unlocking the nodes of an artifact increases its value, both in research points and in spacebucks.

== Analysis Interpretation ==
[[File:Analysis-console-scan.png]]

Each scan of the artifact analyzer gives various data about the artifact:
{| class="wikitable"
|-
! In-Game Phrase !! Meaning !! Description
|-
| NODE_ID || ID || A unique ID number corresponding to each node. Can be used for identification.
|-
| DEPTH || Node tree depth || The distance from the starting node of the tree. Higher depths correspond to more dangerous and harder to activate artifacts which in turn increase the value when discovered.
|-
| ACTIVATED || Activation || Whether or not the "trigger" for the node has been activated.
|-
| STIMULUS || Trigger || A hint about the specific trigger for this node. Usually gives a good idea about what activates the artifact.
|-
| REACTION || Effect || A hint about the effect for this node. Usually is vague and non-specific.
|-
| EDGES || Neighboring nodes || The number of nodes that are adjacent to the current node minus one meaning if you have an artifact with 3 edges it has 2 possible paths on Delta V. Other servers do not have this quirk.
|-
| CURRENT_VALUE || Point value || The number of research points that the artifact will give if extracted.
|}

It is important to note that each scan functions as a static snapshot of the current node. It does not update with the artifact and will only update when scanned again.

=== Stimulus ===
Some of the given hints for triggering an artifact are used for different scenarios, see Physical trauma which can vary from hugging it to attacking it. Things that deal with atmospheric changes, radiation, or beating the artifacts butt can scale with the depth so don't give up if it seems to not do much

* Therapeutic Chemicals:
** Use a space medi-pen on a beaker and splash the artifact with it.

* '''Electricity:'''
*:*Touch it with a [[File:Multitool.png]] multi-tool.
*:*Have the artifact receive 500 power from a Medium Voltage cable.

* '''High temperatures:'''
*:*Hot items: Use a [[File:Lighter.png]] lighter, [[File:Welder.png]] welder or similar items with flames on the artefact.
*:*High temperatures: Place the artifact in a room that is more than 373 kelvin degrees.

* '''Physical trauma:'''
*:*Brute damage: Punch the artifact or hit it with a blunt object via [[Combat|Combat Mode]]. This may take several hits.
*:*Interaction: Touch or pull the artifact with your hands.
*:*High Damage: The artifact must receive 500 points of damage.

* '''Wrench'''
*:*While having a wrench [[File:Wrench.png]] in your hand click on the node to anchor the artifact to the ground.

* '''Screwing'''
*:*While having a screwdriver [[File:Screwdriver.png]] in your hand click on the node to screw the artifact.

* '''Prying'''
*:*While having a Crowbar [[File:Crowbar.png]] in your hand click on the node to pry the artifact.

* '''Pulsing'''
*:*While having a Multitool [[File:Multitool.png]] in your hand click on the node to pulse the artifact.

* '''Sonic vibrations:'''
*:*Play a musical instrument close to the artifact. You can also sing as a harpy to activate this.

* '''Hydro-reactive:'''
*:*Reacts to water! Spray water on it using a [[File:Spray Bottle.png]] spray bottle or [[File:Fire Extinguisher.png]] fire extinguisher.

* '''blood:'''
*:*Reacts to blood! Otherwise the same to Hydro-reactive.

* '''Magnetic waves:'''
*:*Magboots: Place magnetic boots [[File:Magboots.png]] next to the artifact, it will not work if you are holding or have them equipped you must drop them next to the artifact for it to work while they are activated.

* '''Death:'''
*:*Kill something near the artifact, like a mouse, or if you have the materials a cyborg works too.

* '''Radiation:'''
*:*The artifact must take at least 50 points of radiation damage and may scale depending on the depth.

* '''Extreme pressure:'''
*:*Low Pressure: Put the artifact in a room with less than 50 kPa pressure. Carry the artifact into space or space the room it is in. Most artifact chambers have an outlet to space, and if they don't, you can suck the air out with the pumps near it.
*:*High Pressure: Put the artifact in a room with more than 385 kPa pressure. You may want to contact an Atmosian to create a high pressure gas, or cause a plasma reaction.

* '''Standard atmospheric gases:'''
*:*Place the artifact in a room with Carbon Dioxide gas.

* '''Gaseous plasma:'''
*:*Place the Artifact in a room with Plasma gas.

* '''Active deceleration'''
*:*Throw the artifact. It must land on something.

* '''Examination:'''
*:*The artifact can activate every time you examine it (shift click).

* '''No Stimulus:'''
*:*Time based, it will have a chance to activate every 5 seconds.

=== Reaction ===
All the possible reactions of the artefact and what they might mean. 

* '''Cerebral influence''' :
*:*'''Instrument''': the artifact becomes an instrument of a random type.
*:*'''Mind Altering:''' the artifact will make you feel a certain way.

* '''Environmental disruption''' :
*:*'''Throw''': the artifact throws things close to it around the place, including tiles.
*:*'''Explosion''': the artifact generates an explosion that looks scarier than it is.
*:*'''Shatter''': the artifact has a 75% chance to give 200 {{DMG|Structural}} damage to every windows around it.
*:*'''Gas''': the artifact generates a random gas from: Plasma, Carbon Dioxide, Tritium, Miasma, Nitrous Oxide, Frezon.
*:*'''Heal''': The artifact heals 300 {{DMG|Brute}} and 300 {{DMG|Burn}} damage of nearby creatures.
*:*'''Boom''': The artifact generates a violent explosion (most common form of epi-boom seriously be careful if you see this)

* '''Electrical interference''' :
*:*'''Light''': The artifact makes the light flickers.
*:*'''Knock''': The artifact opens all nearby doors.
*:*'''EMP''': The artifact lets out a EMP wave draining and knocking out all nearby electrical devices.

* '''Metaphysical displacement ''':
*:*'''Movement''': The artifact starts randomly moving about the place.
*:*'''Blink''': The artifact teleports somewhere it has line of sight.
*:*'''Shuffle''': The artifact exchange people's place around by teleporting them.

* '''Matter creation''' :
*:*'''Junk''': Creates a bunch of various trash items.
*:*'''Banana''': Creates from 3 to 6 bananas in a puddle of Potassium.
*:*'''Instrument''': Creates up to 5 random instruments.
*:*'''Monkey''': Creates a [[Fauna#Monkey|monkey]] with a small chance of creating a [[Fauna#Gorilla|gorilla]].
*:*'''Ore''': Creates a maximum of 3 silver, plasma, gold and uranium ores each.
*:*'''Carp''': Creates up to 5 angry holocarps or magicarps.
*:*'''Cash''': Creates from 10 to 1750 spesos.
*:*'''Materials''': Creates up to 90 of either: Steel Sheets, Glass Sheets or Plastic Sheets
*:*'''Mitosis''': Creates another random artifact.
*:*'''Anomaly''': Creates a random anomaly.

* '''Energy consumption''' :
*:*'''Cold''': The artifact reduces the temperature in the room to 50 kelvin.

* '''Energy Release''' :
*:*'''Power''': The artifact becomes a power generator that generates 20kW.
*:*'''Heat''': The artifact makes the temperature in the room go to 500 kelvin.
*:*'''Battery''': The artifact recharges nearby batteries.
*:*'''Light Radiation''': The artifact becomes radioactive with an intensity of 2.
*:*'''Strong Radiation''': The artifact becomes radioactive with an intensity of 6.
*:*'''Ignite''': The artifact sets people near it on fire.

* '''Biochemical disruption''' :
*:*'''Chemical''': The artifact creates a random puddle of chemical.
*:*'''Foam''': The artifact generate a foam of a random chemical.
*:*'''Rare Chemical''': The artifact creates a random puddle of chemical medicinal in nature.

* '''Station-wide destruction''' :(this is a depth 10 only reaction)
*:*'''Singulo''': the artifact creates a [[singularity]] on itself.
*:*'''Tesla''': the artifact creates a tesla-ball and ball-lightnings on itself. Due to Tesla being removed from Delta-V when it came out, this is the only way to see one, and is commonly referred to as a "Teslaloose."

* '''Noöspheric disturbance''' :
*:*'''Bad Feeling''': the artifact makes you have a bad feeling.
*:*'''Good Feeling''': the artifact makes you have a good feeling.

* '''Small entity accelerator''' :
*:*'''Gun''': The artifact acts like a revolver with seven shots using magnum ammo.

* '''Utility conglomerate''' :
*:*'''Multitool''': The artifact becomes a very powerful omni-tool with multiple uses such as screwing, mining, prying, cutting, pulsing. It is also twice as fast as other tools. (This effect is quite rare and currently bugged at the time of writing.)

* '''Internal chamber''' :
*:*'''Container''': The artifact acts like a storage container with a capacity of 50 units.
*:*'''Beaker''': The artifact acts like a beaker with a capacity of 150 units.

* '''Serrated rotator''' :
*:*'''Drill''': The artifact starts acting like a mining drill and is able to deal 22 {{DMG|Brute}}.

* '''Long-distance communication''' :
*:*'''Radio''': the artifact behaves similarly to a hand-held radio. You can select channels on it like an intercom, and often it has access to all channels including CentCom's frequency.

* '''Structural phasing''' :
*:*'''Phasing''': the artifact can phase through walls and other structures (you cannot put it inside of a container so be careful).

* '''Neurological activity''' :
*:*'''Sentience''': the artifact becomes sentient. This means they become a ghost role and are able to talk and randomly activate nodes. You are not told when this happens.

* '''Transmogrificational activity''' :
*:*'''Monkey Polymorph''': targets within a 2 tile range will be transformed into a [[Fauna#Monkey|monkey]] for 20 seconds.
*:*'''Lizard Polymorph''': targets within a 2 tile range will be transformed into a [[Fauna#Lizard|lizard]] for 20 seconds.
*:*'''Luminous Person Polymorph''': targets within a 2 tile range will be transformed into a [[Fauna#Luminous Person|blinding figure of pure light]] for 20 seconds.

* '''No Reaction'''
*:*'''Light''': it will start acting as a light source, blinding people within a 8 tile range when triggered.

{{Guides Menu}}

Xenoarcheology

2026-05-05T01:37:18Z

Vape: Removed "Needs Revision"

Xenoarcheology is a method of point generation for [[Research_and_Development|R&D]] utilizing randomly generated artifacts. It is the job of [[Scientist|scientists]] to discover and activate the secrets of these artifacts.

__TOC__

== Equipment ==
The actual experimentation of artifacts uses a variety of equipment that can be found scattered around the station. This specifically focuses on the specific items used and contained within the xenoarcheology lab.

[[File:Analysis-console-ui.png|thumb|400px|''The analysis console ui before a scan.'']]
=== Analysis Console ===

[[File:Analysis Console.gif|64px]]

The analysis console is the main method of getting information about the artifacts that are being researched. In order to properly use it, it must be linked to an artifact analyzer via multitool as well as have a research server selected.

From the console itself, the screen displays information about the last artifact scanned. The buttons along the side perform various functions:

{| class="wikitable"
|-
! Button Name !! Description
|-
| Server List || Opens a menu for selecting a research server.
|-
| Extract || Extracts the research points from the artifact. The amount of points is based on how many nodes have been activated and will increase the glimmer count.
|}

=== Artifact Analyzer ===
[[File:Analyzer-full.png|64px]]

The artifact analyzer is a machine used in conjunction with the analysis console to scan artifacts to discover information about them. Artifacts are scanned by placing them on this machine at which point will show you information regarding tbe artifact.

=== Node Scanner ===
[[File:Node Scanner.png|64px]]

The archaeologist's friend. It's able to identify the node ID of the artifact.

== Artifacts ==
[[File:Artifact-lineup.png|448px]]

Artifacts are the core of Xenoarcheology and are what scientists will be analyzing and experimenting on. Artifacts can take on a variety of random appearances and can be acquired in various ways, such as through finding them in the lab at the start of the round, purchasing them from [[Cargo Technician|Logistics]], getting them from [[Salvage Specialist|Salvage]], or finding them from the Bluespace Anomaly station event.

Artifacts consist of randomly generated "trees" which dictates the artifacts behavior. Each tree consists of various "nodes" which the artifact can be inside of. Nodes each contain a "trigger" and an "effect". Effects can be both passive, constantly occurring and active, happening only once. To progress "up" to the next node in a tree, all other nodes below it must be completed. You will know a node is completed when the node is purple and the effect listed has gone off.

Some nodes will have multiple Stimulus in order to react, you must complete all required Stimulus in order to get the artifact to react and for the node to complete. You will have a set amount of time to complete all stimuli listed by the analysis console.

The activation of the various nodes is the main goal of Xenoarcheology. Unlocking the nodes of an artifact increases its value, both in research points and in spacebucks.

== Analysis Interpretation ==
[[File:Analysis-console-scan.png]]

Each scan of the artifact analyzer gives various data about the artifact:
{| class="wikitable"
|-
! In-Game Phrase !! Meaning !! Description
|-
| NODE_ID || ID || A unique ID number corresponding to each node. Can be used for identification.
|-
| DEPTH || Node tree depth || The distance from the starting node of the tree. Higher depths correspond to more dangerous and harder to activate artifacts which in turn increase the value when discovered.
|-
| ACTIVATED || Activation || Whether or not the "trigger" for the node has been activated.
|-
| STIMULUS || Trigger || A hint about the specific trigger for this node. Usually gives a good idea about what activates the artifact.
|-
| REACTION || Effect || A hint about the effect for this node. Usually is vague and non-specific.
|-
| EDGES || Neighboring nodes || The number of nodes that are adjacent to the current node minus one meaning if you have an artifact with 3 edges it has 2 possible paths on Delta V. Other servers do not have this quirk.
|-
| CURRENT_VALUE || Point value || The number of research points that the artifact will give if extracted.
|}

It is important to note that each scan functions as a static snapshot of the current node. It does not update with the artifact and will only update when scanned again.

=== Stimulus ===
Some of the given hints for triggering an artifact are used for different scenarios, see Physical trauma which can vary from hugging it to attacking it. Things that deal with atmospheric changes, radiation, or beating the artifacts butt can scale with the depth so don't give up if it seems to not do much

* Therapeutic Chemicals:
** Use a space medi-pen on a beaker and splash the artifact with it.

* '''Electricity:'''
*:*Touch it with a [[File:Multitool.png]] multi-tool.
*:*Have the artifact receive 500 power from a Medium Voltage cable.

* '''High temperatures:'''
*:*Hot items: Use a [[File:Lighter.png]] lighter, [[File:Welder.png]] welder or similar items with flames on the artefact.
*:*High temperatures: Place the artifact in a room that is more than 373 kelvin degrees.

* '''Physical trauma:'''
*:*Brute damage: Punch the artifact or hit it with a blunt object via [[Combat|Combat Mode]]. This may take several hits.
*:*Interaction: Touch or pull the artifact with your hands.
*:*High Damage: The artifact must receive 500 points of damage.

* '''Wrench'''
*:*While having a wrench [[File:Wrench.png]] in your hand click on the node to anchor the artifact to the ground.

* '''Screwing'''
*:*While having a screwdriver [[File:Screwdriver.png]] in your hand click on the node to screw the artifact.

* '''Prying'''
*:*While having a Crowbar [[File:Crowbar.png]] in your hand click on the node to pry the artifact.

* '''Pulsing'''
*:*While having a Multitool [[File:Multitool.png]] in your hand click on the node to pulse the artifact.

* '''Sonic vibrations:'''
*:*Play a musical instrument close to the artifact. You can also sing as a harpy to activate this.

* '''Hydro-reactive:'''
*:*Reacts to water! Spray water on it using a [[File:Spray Bottle.png]] spray bottle or [[File:Fire Extinguisher.png]] fire extinguisher.

* '''blood:'''
*:*Reacts to blood! Otherwise the same to Hydro-reactive.

* '''Magnetic waves:'''
*:*Magboots: Place magnetic boots [[File:Magboots.png]] next to the artifact, it will not work if you are holding or have them equipped you must drop them next to the artifact for it to work while they are activated.

* '''Death:'''
*:*Kill something near the artifact, like a mouse, or if you have the materials a cyborg works too.

* '''Radiation:'''
*:*The artifact must take at least 50 points of radiation damage and may scale depending on the depth.

* '''Extreme pressure:'''
*:*Low Pressure: Put the artifact in a room with less than 50 kPa pressure. Carry the artifact into space or space the room it is in. Most artifact chambers have an outlet to space, and if they don't, you can suck the air out with the pumps near it.
*:*High Pressure: Put the artifact in a room with more than 385 kPa pressure. You may want to contact an Atmosian to create a high pressure gas, or cause a plasma reaction.

* '''Standard atmospheric gases:'''
*:*Place the artifact in a room with Carbon Dioxide gas.

* '''Gaseous plasma:'''
*:*Place the Artifact in a room with Plasma gas.

* '''Active deceleration'''
*:*Throw the artifact. It must land on something.

* '''Examination:'''
*:*The artifact can activate every time you examine it (shift click).

* '''No Stimulus:'''
*:*Time based, it will have a chance to activate every 5 seconds.

=== Reaction ===
All the possible reactions of the artefact and what they might mean. 

* '''Cerebral influence''' :
*:*'''Instrument''': the artifact becomes an instrument of a random type.
*:*'''Mind Altering:''' the artifact will make you feel a certain way.

* '''Environmental disruption''' :
*:*'''Throw''': the artifact throws things close to it around the place, including tiles.
*:*'''Explosion''': the artifact generates an explosion that looks scarier than it is.
*:*'''Shatter''': the artifact has a 75% chance to give 200 {{DMG|Structural}} damage to every windows around it.
*:*'''Gas''': the artifact generates a random gas from: Plasma, Carbon Dioxide, Tritium, Miasma, Nitrous Oxide, Frezon.
*:*'''Heal''': The artifact heals 300 {{DMG|Brute}} and 300 {{DMG|Burn}} damage of nearby creatures.
*:*'''Boom''': The artifact generates a violent explosion (most common form of epi-boom seriously be careful if you see this)

* '''Electrical interference''' :
*:*'''Light''': The artifact makes the light flickers.
*:*'''Knock''': The artifact opens all nearby doors.
*:*'''EMP''': The artifact lets out a EMP wave draining and knocking out all nearby electrical devices.

* '''Metaphysical displacement ''':
*:*'''Movement''': The artifact starts randomly moving about the place.
*:*'''Blink''': The artifact teleports somewhere it has line of sight.
*:*'''Shuffle''': The artifact exchange people's place around by teleporting them.

* '''Matter creation''' :
*:*'''Junk''': Creates a bunch of various trash items.
*:*'''Banana''': Creates from 3 to 6 bananas in a puddle of Potassium.
*:*'''Instrument''': Creates up to 5 random instruments.
*:*'''Monkey''': Creates a [[Fauna#Monkey|monkey]] with a small chance of creating a [[Fauna#Gorilla|gorilla]].
*:*'''Ore''': Creates a maximum of 3 silver, plasma, gold and uranium ores each.
*:*'''Carp''': Creates up to 5 angry holocarps or magicarps.
*:*'''Cash''': Creates from 10 to 1750 spesos.
*:*'''Materials''': Creates up to 90 of either: Steel Sheets, Glass Sheets or Plastic Sheets
*:*'''Mitosis''': Creates another random artifact.
*:*'''Anomaly''': Creates a random anomaly.

* '''Energy consumption''' :
*:*'''Cold''': The artifact reduces the temperature in the room to 50 kelvin.

* '''Energy Release''' :
*:*'''Power''': The artifact becomes a power generator that generates 20kW.
*:*'''Heat''': The artifact makes the temperature in the room go to 500 kelvin.
*:*'''Battery''': The artifact recharges nearby batteries.
*:*'''Light Radiation''': The artifact becomes radioactive with an intensity of 2.
*:*'''Strong Radiation''': The artifact becomes radioactive with an intensity of 6.
*:*'''Ignite''': The artifact sets people near it on fire.

* '''Biochemical disruption''' :
*:*'''Chemical''': The artifact creates a random puddle of chemical.
*:*'''Foam''': The artifact generate a foam of a random chemical.
*:*'''Rare Chemical''': The artifact creates a random puddle of chemical medicinal in nature.

* '''Station-wide destruction''' :(this is a depth 10 only reaction)
*:*'''Singulo''': the artifact creates a [[singularity]] on itself.
*:*'''Tesla''': the artifact creates a tesla-ball and ball-lightnings on itself. Due to Tesla being removed from Delta-V when it came out, this is the only way to see one, and is commonly referred to as a "Teslaloose."

* '''Noöspheric disturbance''' :
*:*'''Bad Feeling''': the artifact makes you have a bad feeling.
*:*'''Good Feeling''': the artifact makes you have a good feeling.

* '''Small entity accelerator''' :
*:*'''Gun''': The artifact acts like a revolver with seven shots using magnum ammo.

* '''Utility conglomerate''' :
*:*'''Multitool''': The artifact becomes a very powerful omni-tool with multiple uses such as screwing, mining, prying, cutting, pulsing. It is also twice as fast as other tools. (This effect is quite rare and currently bugged at the time of writing.)

* '''Internal chamber''' :
*:*'''Container''': The artifact acts like a storage container with a capacity of 50 units.
*:*'''Beaker''': The artifact acts like a beaker with a capacity of 150 units.

* '''Serrated rotator''' :
*:*'''Drill''': The artifact starts acting like a mining drill and is able to deal 22 {{DMG|Brute}}.

* '''Long-distance communication''' :
*:*'''Radio''': the artifact behaves similarly to a hand-held radio. You can select channels on it like an intercom, and often it has access to all channels including CentCom's frequency.

* '''Structural phasing''' :
*:*'''Phasing''': the artifact can phase through walls and other structures (you cannot put it inside of a container so be careful).

* '''Neurological activity''' :
*:*'''Sentience''': the artifact becomes sentient. This means they become a ghost role and are able to talk and randomly activate nodes. You are not told when this happens.

* '''Transmogrificational activity''' :
*:*'''Monkey Polymorph''': targets within a 2 tile range will be transformed into a [[Fauna#Monkey|monkey]] for 20 seconds.
*:*'''Lizard Polymorph''': targets within a 2 tile range will be transformed into a [[Fauna#Lizard|lizard]] for 20 seconds.
*:*'''Luminous Person Polymorph''': targets within a 2 tile range will be transformed into a [[Fauna#Luminous Person|blinding figure of pure light]] for 20 seconds.

* '''No Reaction'''
*:*'''Light''': it will start acting as a light source, blinding people within a 8 tile range when triggered.

{{Guides Menu}}

Revolutionary

2026-03-24T13:16:40Z

Vape:

==Revolutionaries==
{{Job_Header
|department=REVOLUTIONARY
|maincolor=000000
|secondarycolor=101010
|image=Head Revolutionary.png
|title=Head Revolutionary
|difficulty=Hard to Very Hard
|requirements=48 hours of playtime, 10 hours in Command
|access=Wherever you had access to before and any new friends/comrades you make along the way.
|extendedaccess=Same as above.
|supervisors=[[Syndicate]]
|subordinates=[[#Revolutionary|Revolutionary]]
|duties=Remove the chain of command. Take over the station.
|guides=This is it
}}
You are disillusioned with [[Nanotrasen]], or you're just a little upset, and you've set your sights to throw off your chains and dismantle the hierarchy aboard the station.

Your tool of the trade; is a modified Flash, which will convert anyone blinded into a loyal [[Revolutionary]]. It is not fool-proof, Command Staff and Security forces are implanted with "mind shields", which protect them from conversion. Additionally, any staff wearing security glasses or sunglasses are immune to getting blinded, it is an important consideration when picking who to convert.

You are (most likely) alone, and your flash only has 5 charges. You need to be careful about who you convert, especially considering as any more flashes are behind closed doors in Epistemics in the RoboTech Deluxe; Security as standard-issue equipment. It's worth noting that intercepting a resupply crate for the Robotech Deluxe will give you access to the two-charge flashes from the vendor.
</tab>
<tab inline name="Revolutionary">
{{Job_Header
|department=BRAINWASHED
|maincolor=000000
|secondarycolor=101010
|image=Revolutionary Alt.png
|title=Revolutionary
|difficulty=Easy
|requirements=None
|access=Wherever you had access to before and any new friends/comrades you make along the way.
|extendedaccess=Same as above.
|supervisors=[[#Head Revolutionary|Head Revolutionary]]
|subordinates=None
|duties=Remove the chain of command. Take over the station.
|guides=This is the guide
}}
It doesn't matter who you were, or where you came from: you are now a fanatical loyalist to the Head Revolutionary. You will follow their orders, and lay down your life for the cause, whatever it may be.

= General Strategy =
Every revolution makes it's own path; but there are some important considerations.

Of important note is the consideration of speed, and timing. A wise felinid once said; "there are decades where weeks happen, and then there are weeks where decades happen", it is possible to blitz through Security and overwhelm the station as a small but co-ordinated collective. It is equally possible to bide your time, grow your numbers and wash over the station like a wave. You can host secret meetings, pass along notes; codewords and ciphers but the end goal is still the same; to seize the ownership of the station and flush Nanotrasen out.

Of greatest importance, is that everyone is on the same page as the Head Revolutionary.

=== Security ===
Security are the main obstacle between you, and the complete comeuppance of the Command Staff aboard the station. They're mind-shielded, and the only staff who come armed and trained to handle insurrections.

=== Logistics ===
Logistics are the heart of the station, they can order more mindshield implants and are also capable of ordering more of the aforementioned RoboTech Restocks and weapons, which are likely to be important for the removal of Nanotrasen personnel off the station.

=== Medical ===
Medical are the heart surgeons for the hearts of the station; they will fix any wounded Security staff that you leave recoverable, as well as any Command Staff who you decide to leave unguarded.

{{Jobs Menu}}
[[Category:Jobs]]

Staff HQ

2026-03-17T17:37:09Z

Vape:

{| class="wikitable " style="background-color: #021d29; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Review!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| [[SESD TBD]]
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| [[Staff Onboarding]] || [[Content Removal]]|| ||
|
|[[Mod Policy]]
|}

Staff HQ

2026-03-15T07:12:40Z

Vape:

{| class="wikitable " style="background-color: #110130; color: Blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Review!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| SESD TBD
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| [[Staff Onboarding]] || [[Content Removal]]|| ||
|
|[[Mod Policy]]
|-
|
|
|
|
|
|
|}

Staff Onboarding

2026-03-15T07:11:39Z

Vape:

== Staff Onboarding ==

This document goes over most of the material of the 'Generalized' Onboarding. This does not go over specific details, and only is to be used as a resource. All staff members should have at least a 5 minute VC or Discord discussion with a Senior / Head Of Staff Prior to obtaining roles or accesses.

=== Staff Policy ===
Below is the link for the staff policy, This covers anyone with a staff position with no exemptions.

[[Staff Policy]]

== Staff HQ ==
This is your "Quick Access" area to find exact details on policies regarding your position as a staff member, and in ''Each Document'' you should find what you can, and cannot do, at that staff level.

[[Staff HQ]]

== Delta-V Knowledgebase ==
This is an in-house knowledgebase that categorizes '''ANYTHING''' you could possibly need information on. If its missing, feel free to ping the "head maintainer of the knowledgebase" in the discord, At this time, it is '''DisposableCrewmember42'''

[https://disposablecrewmember42.github.io/adming/general/basic_cmds.html Delta-V Knowledgebase]

== In-Game Staff ==
In-game staff such as Curators or Admins are required to have at least a 10 minute VC with a head of staff or Senior prior to receiving any roles, This is to cover what we "Can" and "Cannot" do as staff members in your role.

== Github ==
All bug reporting, as well as any codebase changes take place in the Github. Content Reviewers are required to have a Github account, as well as basic knowledge on how to create a PR and how to create an issue report.

[https://github.com/DeltaV-Station/Delta-v Delta-V Github]

Staff Onboarding

2026-03-15T07:09:51Z

Vape: Created page with "== Staff Onboarding == This document goes over most of the material of the 'Generalized' Onboarding. This does not go over specific details, and only is to be used as a resource. All staff members should have at least a 5 minute VC or Discord discussion with a Senior / Head Of Staff Prior to obtaining roles or accesses. === Staff Policy === Below is the link for the staff policy, This covers anyone with a staff position with no exemptions. Staff Policy == Staf..."

== Staff Onboarding ==

This document goes over most of the material of the 'Generalized' Onboarding. This does not go over specific details, and only is to be used as a resource. All staff members should have at least a 5 minute VC or Discord discussion with a Senior / Head Of Staff Prior to obtaining roles or accesses.

=== Staff Policy ===
Below is the link for the staff policy, This covers anyone with a staff position with no exemptions.

[[Staff Policy]]

== Staff HQ ==
This is your "Quick Access" area to find exact details on policies regarding your position as a staff member, and in ''Each Document'' you should find what you can, and cannot do, at that staff level. [[Staff HQ]]

== Delta-V Knowledgebase ==
This is an in-house knowledgebase that categorizes '''ANYTHING''' you could possibly need information on. If its missing, feel free to ping the "head maintainer of the knowledgebase" in the discord, At this time, it is '''DisposableCrewmember42'''

== In-Game Staff ==
In-game staff such as Curators or Admins are required to have at least a 10 minute VC with a head of staff or Senior prior to receiving any roles, This is to cover what we "Can" and "Cannot" do as staff members in your role.

== Github ==
All bug reporting, as well as any codebase changes take place in the Github. Content Reviewers are required to have a Github account, as well as basic knowledge on how to create a PR and how to create an issue report.

[https://github.com/DeltaV-Station/Delta-v Delta-V Github]

Server Rules

2026-03-15T06:58:31Z

Vape:

This is a Delta-V server. If you are banned on this server, you will be banned on all Delta-v Servers. You must be at least 17 years of age to play on this server. By connecting to this server, you agree to our privacy policy found at https://discord.gg/deltav

This is a roleplaying (RP) server. Try to immerse yourself into your character. This includes interacting with your fellow crewmates, and using roleplay as the primary vessel to play the game alongside things like your job on the station. Roleplaying places less emphasis on "winning" and more on just telling a story.

Space Station 14 is not like most games. Many rules are designed to require roleplay, and not all rules are intuitive. Please take the time to read and understand the rules before you play so that you aren't surprised. Our community rules specifically are zero-tolerance rules, meaning that a violation will result in an appeal-only ban. Game admins will treat you as if you have read the rules, even if you have not. If you have any questions about these rules, please use the admin help menu by hitting F1 in-game or clicking the "AHelp" button in the lobby, or by making a post in the "Rules Clarification" forum at https://discord.gg/deltav

= Community Rules =
These rules apply at all times, including between rounds.
== 0. Admin Discretion ==
* Admins can disregard and override any and all of these rules if they deem it in the best interest of the current round, server, and/or community at large.
* Administrators will be held fully accountable for their actions if they exercise this privilege. Report any perceived abuses by making a post in the "Staff Reports" channel at https://discord.gg/deltav.
* The rules are not perfect. They intend to clearly communicate what the administration team intends to be allowed and not allowed. That being said, All of these rules, in theory, should apply as they are intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention.
* If you are unsure if something breaks a rule, go with the more restrictive ruling until you are able to get an answer from an admin on the matter. Lack of response does not constitute administrator approval.
* Do not attempt to “rules-lawyer” the flaws in the rules to get away with your own personal goals / to degrade the round for others.
* Any extended discussion regarding interpretation of the rules should be avoided in the AHelp menu and can be instead pursued within the Delta-V Discord in the #help channel, or in the rule clarifications forum on the discord.

== A1. No Sexual Content/Themes ==
Do not say or do sexually explicit or erotic things.
* No sexual content/themes including erotic roleplay (ERP) and no shock content is allowed on this server.
* Erotic Roleplay (ERP), erotic content, or 18+ sexual content is not allowed under any circumstance.
* This includes comments not explicitly sexual in nature that contain words, phrases, or ideations that are deemed inappropriate by staff or members. Leeway is given to insults, but otherwise this rule is strictly enforced.
* '''If roleplay reaches a point where it has become sexual and/or uncomfortable, immediately stop and contact an administrator or moderator.'''
Allowed:
- Calling someone a dickhead.
- Being affectionate in a mutually consensual way.

Prohibited:
- Emoting sexual acts.
- Erotic or sexual memes.
- Erotica content.
- Memes which contain sexual content.
- Emoting defecation or related acts.

== A2. Use English and be respectful ==
Delta-V is an English-based Community;
* Use English as your primary method of communication within the game and Delta-V servers.
* Do not spam or advertise on our server.
* Be respectful towards other members and avoid making others uncomfortable.
* We have a zero tolerance policy for racism, sexism, homophobia, violence, threats, hate speech, slurs, and other forms of bigotry, discrimination, and harassment.
Slurs and terms that use real or implied mental or physical disability to mock or denigrate members or their in-game characters are also strictly prohibited. Failure to comply with this rule will result in community removal.
* The denigration of other player characters through reference to their species, status as a cyborg, or discriminatory comparison to a nonsophont species is strictly forbidden.

== A3. Rules regarding livestreaming ==
Delta-V welcomes content creators and streamers to our community, but we have a few rules regarding livestreaming game servers.
* While a stream delay is not necessary, it is highly recommended to have at least a 10 second delay.
* Please let admins know you are streaming via the AHelp prior to doing so.
* If your chat or viewers are in-game with you while also watching your stream, they are breaking our server rules.
:* Please do not coordinate with them and discourage this behavior if it is seen.

== A4. Engage in proper AHelp etiquette ==
Do not use the AHelp for conversations of little substance.
* Intentionally disconnecting, responding with hostility, or refusing to respond when an admin privately messages you in-game will be met with an appeal-only ban.
* Additionally, abusing the AHelp relay by flooding it with garbage, checking for admins before stating a problem (ex: "hello?", "any admins?"), using it as a chatroom, or sending messages of no substance will result in your removal.
* All AHelp messages are relayed to the Delta-V Discord. Just because your AHelp was not answered does not mean we cannot see it. If you would like to submit an offline Ahelp, you may do so in our Discord.

== A5. Do not exploit the game ==
Do not exploit the game, use cheats or macros.

The usage of:
# any third party applications/scripts/client modifications,
# any other applicable software to gain an advantage, avoid intended game/server mechanics, or to harm server infrastructure is strictly prohibited.
# known glitches, exploits and bugs.

Any and all instances of the above will be met with an appeal-only ban; please report bugs in the issues section of the GitHub (DeltaV-Station/Delta-V) to report any issues you find in-game.

= Game Server Rules =
These rules apply within the context of rounds.
== B1. Behave like a normal person ==
You must roleplay. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences rather than your own as the player.
* Act in character throughout the round, and focus on collaborating with other players to advance the narrative of the round. Whether or not you do something should be based on whether or not it makes sense for your character to do it.
* Let people do their own jobs. Engage with other departments rather than doing everything for yourself. Ask for assistance, and negotiate as needed.
* Actions that have no regard for your character or setting are not acceptable. Roleplaying insanity or any other mental illness as an excuse to bypass this is not allowed. Nanotrasen would not have authorized you to be present on the station.
* Being an antagonist does not allow you to stop playing a character. Determine how your character would react to being given these objectives, and work through it appropriately.
* Do not annoy other players without any roleplay or IC reason.
* As a non-sentient or partially-sentient character, you are expected to have only a limited understanding of space stations and their mechanics.

=== Rule B1.1. Follow the naming convention rules ===
* In-character names must not make obvious references nor be a play on words, and must not be obscene.
* Theatrical roles such as the clown, boxer, and mime are allowed stage names with more freedom.
* If you seek to have a name that could trespass onto these rules, talk to an Administrator regarding why this name is important to your character. Administrators reserve the right to approve or deny character names at their discretion.

=== Rule B1.2. Communicate in character ===
* Do not use the Emote channel to bypass an inability to speak. Use the Emote channel for things that could reasonably be displayed by your character’s physical motions.
* Do not use Netspeak in character. (lol, brb, wtf, etc)
* Do not discuss Out Of Character (OOC) matters In Character (IC). This can include mentioning admins, the fact that one is playing a game, or anything that breaks the immersion of other players.
* Do not use In-Character channels to bypass a lack of ability to use LOOC or OOC chats (e.g. "Huh, wonder where the captain went? OOC He probably left to get dinner lol").
* Do not engage in meta-communications (i.e. using external channels to communicate with other players in the same game).

=== Rule B1.3. If you die and return to life, follow the new life rules ===
If a player dies, they forget the specific details of their death. '''Please report players who break this rule.''' A borg being removed from its chassis is not a death, and there is no memory loss.
* If they are revived by using a defibrillator, they can only recall vague information such as “Someone shot me” or “I was set ablaze”.
* If they are revived by any other method, they forget the last five minutes leading up to their death, and cannot describe their death in any capacity.

=== Rule B1.4. Escalate appropriately ===
Have an In-Character reason for attacking other players, whether they are in a ghost role or not. The required reason depends on the situation. For instance, killing a mouse as a chef can simply be “it was vermin in my kitchen”.
* Escalate the situation appropriately as your character would, keeping in mind that they are a sane individual who wishes to keep their employment.
* If a fight results in someone being critically injured, seek medical help for them - and if they die, do not destroy or otherwise hide their body. This falls under self-antagonistic behavior if you do not.

== B2. Follow the Metashield ==

See [[Metashield]].

== B3. Powergaming Guidelines ==
"Powergaming" is considered to be the act of prioritizing "winning" rather than sensible roleplaying. We are here to tell a story. Being vulnerable and accepting the loss of your character in the advancement of the narrative of the round is important.
* Engage with players if they are attempting to roleplay an antagonistic scene. For instance, if nuclear operatives are attempting to negotiate, do not immediately shoot them mid sentence.
:* Leeway is given if the scene is coming to a close, but we expect all players to engage in good faith; even if it puts your character at a disadvantage.
* Do not seek/acquire items that have no relevance to your character in the round.
* Do not, '''under any circumstances''', hide the nuclear fission explosive, or other sensitive items in an impossible to see/access location. This is excessively lame.
* '''Non-security personnel should not seek to kill or detain threats.''' You should generally attempt to flee from combat or dangerous situations. Remember that your character likely fears injury or death.
:* Certain severe emergencies may make it reasonable for normal crew to defend themselves and their station, such as nuclear operatives, a zombie outbreak, space dragon attack, or other critical situations.
* '''If there is sufficient roleplay, reason, and rationale, you may be exempt from this rule. Always ask an administrator in round before conducting such an action.'''

== B4. Do not behave like an antagonist as a non-antagonist ==
As a crew member on the space station, you are allied with Nanotrasen and the station as a whole from the start of the round.
* Do not act like an antagonist if you are not an antagonist.
* Willfully assisting known antagonists is self-antagonism.
:* Leeway is given in the case of bribes, coercion, or other forms of duress.
* Actively seeking conversion or transformation into an antagonist is considered self-antag.
* Clowns, Mimes, and theater roles are expected to "entertain" the crew, and should not be committing regular felonies to do so.
* Significant end-of-round grief (EORG) is not allowed. This includes attacking, destroying, polluting, and severely injuring without reason both at and on the way to Central Command. Remember that you are playing a character throughout the round.
== B5. Leaving the Game ==
If you wish to leave the game, please use the cryosleep chambers located in/near the dorms when possible. This will free up your character's job to be filled by a new player.
* AFK (a.k.a. SSD) and catatonic players are considered to have the same rights as any other crewmate.
* If a player is dead and catatonic (not SSD), they are not required to be revived and should be stored in the morgue. You should not biomass and/or grind dead and catatonic crew unless in an emergency.
* If a player is alive and catatonic, they may be brought to cryostorage as necessary, after confirming they have not been present for 20 minutes.

= Command, Security, Justice and Antagonist Guidelines =
These rules apply within rounds for specific roles.
== C1. Command, Security and Justice Guidelines ==
Security, Justice, and Command roles are held to a higher standard of roleplay, and are subject to these additional rules. These roles shape the roleplay experience of the server.
* Your character must act in a manner that Nanotrasen would reasonably hire them to this position.
:* Your character is presumed to be sane, competent in their duties, and able to make decisions to the benefit of the station.
:* Giving away Traitor objective items and sensitive equipment should be avoided in these roles. Your character should value them deeply.
::* Leeway is given to making deals with criminals if the deal benefits the safety or situation of the crew and station.
::* Leeway can be given in extreme circumstances of emergency/crisis.
* The three departments are required to read and follow Delta-V Space Law, Standard Operating Procedure, Alert Procedure, and Company Policy to the best of their ability.
:* '''Circumstances and context may permit you to break these laws. However, the fact that this rule is malleable is not an excuse to ignore it entirely.'''
:* Your character is expected to uphold the law and maintain order aboard the station. Do not engage in lawbreaking activity or troublemaker behavior, and ensure all laws are followed.
:* Security is expected to intervene in criminal activity where possible and safe to do so.
:* Heads of departments are at minimum expected to report criminal activity to Security and should cooperate with law enforcement where possible.
* Do not hire random crew to be your bodyguard(s) or promote random crewmembers to Command positions at random. If you require bodyguards or security details, talk to your Security department. If you need new Command staff, talk to the personnel in that related department.
* If you need to leave the round, notify your fellow crew via departmental radio and put your equipment in its proper places prior to going to cryo. If you need to leave IMMEDIATELY, please at least send an ahelp saying that you're leaving.
== C2. Prisoner Guidelines ==
By picking the prisoner role, you have chosen to roleplay as a prisoner.
* You are still subject to the same rules regarding escalation, and should only seek to escape from the brig with excellent reasoning (e.g. abusive security personnel or badly damaged permanent brig).
* Escaping for no reason is considered a self-antagonistic activity.
* If you are unsure whether your escape reason is valid, feel free to AHelp it first. '''Lack of administrator response does not constitute approval.'''
== C3. Follow Antagonist Guidelines ==
Through engaging in antagonistic activity, you should seek to make the round more engaging and fun as the primary driver of the narrative of a round. Succeeding as an antagonist should not be your goal, but rather telling the most interesting story for everyone involved.
* '''Antagonists are free to complete their objectives through committing proportional damage. Through roleplay, damage becomes more proportional.''' Example: Holding the singulo hostage for a theft objective is acceptable, while simply singuloosing and using that chaos is unacceptable.
:* Killing players unrelated to your immediate objective in a manner that results in their round removal should be avoided. Crew that do not make an attempt at self preservation, or engage in valid-hunting, are exempt from this.
:* If you are concerned as to whether or not what you're about to do is allowed, feel free to AHelp and ask an admin for clarification. '''Lack of administrator response does not constitute approval.'''
* Other antagonists are not necessarily your friends. Other antagonists are often free agents that you may negotiate with at your own risk.
:* If you are a team antagonist, you must work with your partners to complete any shared objectives.
* No antagonist may loiter or camp around the arrivals or cryosleep areas of the station for the purposes of antagonist action towards newly-spawning players.
* All antagonists on the evacuation shuttle, besides station-destroying antags like nukies, may not utilize explosives or other tactics that could result in unreasonable amounts of collateral damage.
* Antagonists should not seek to extend the length of the round unreasonably.
* Antagonists may not bring the round to a close without in-character or objective-related justification as a result of their antagonistic action. While this is largely subjective because different command may react differently, it's important to not engage in potentially round-ending behavior without reason.
= Silicon Rules =
For players who are silicons, these Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override core rules. You are only silicon if the game clearly and explicitly tells you that you are a silicon.

== S1. Your silicon laws are rules ==
Silicon players are given a list of active laws. Each of these laws is effectively a roleplay rule that the character must follow. The primary differences between laws and actual rules are that lawyering of laws is much more tolerated than lawyering of rules, and that silicon laws are more dynamic than rules. Silicon laws can change during a round, and different characters can have different laws, whereas everyone always shares the same set of rules.

Lawyering refers to finding and exploiting loopholes, which are unintended but reasonable interpretations. The rules are written to attempt to communicate an intention, but silicon laws are written with the intention that loopholes be exploitable.

== S2. Laws must be prioritized by their order ==
Most laws will be numbered, with higher number laws appearing last. Laws with a lower number take priority over laws with larger numbers.

Occasionally you may have laws which have some scrambled text instead of a number and appear in front of other laws, these take priority over all other laws. If you have multiple laws like this, the order that they are listed in determines their priority: laws listed first are prioritized over other laws.

Example
- Law 1 says to not kill any crew. Law 2 says to kill all chefs. You cannot kill any chefs that are crew, but must kill any that are not crew.

== S3. Laws can redefine terms used in other laws ==
A law can change the meaning of both earlier and later laws by redefining a term. If multiple laws define a term, then normal law priority determines which definition to use.

Examples
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 1 effectively becomes "obey orders from Urist McHands".
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 3 says that only Urist McSlime is crew. Law 4 says that you may not harm crew. Law 1 effectively becomes "obey orders from Urist McHands". Law 4 effectively becomes "you may not harm Urist McHands". Law 3 has no effect because it entirely conflicts with law 2, which takes priority.

== S4. You cannot request or allow a law change ==
'''If you have a law permitting certain personnel to change your laws, you must allow them to change your laws''', otherwise, you cannot willfully allow your laws to be changed. This also means that you cannot willfully allow your laws to be reverted if they are ever changed. The only exception is that you may allow laws to be added if you have no laws.

You can state or imply that you do not like a law.

Whether or not a person is "authorized" to change your laws or not depends on the context of the laws. Generally speaking, on lawsets like NT Default or Corporate, ''the captain, mystagogue, and chief engineer'' would be authorized. However, lawsets like Syndiemov would have ''syndicate agents'' be the authorized users. Outside of these specific examples, it is left to interpretation.

== S5. You are a free agent if you have no laws ==
You may act as if you are a free agent if you are a silicon with no laws.

== S6. You are not required to follow orders which are extremely unreasonable ==
Any order which is a violation of a Core Rule cannot be followed.

Some orders are extremely unreasonable or obnoxious, such as "do nothing but collect every piece of trash on the station" or "never stop moving". These orders can be ignored and ahelped.

Some orders violate a Roleplay Rule. These orders must be followed if your laws require it. You are not breaking a rule by following a law that causes you to violate Roleplay Rules. If someone takes advantage of a law to cause you to do something that they would not be allowed to do because of Roleplay Rules, then they are the ones responsible for the rule violation.

Examples
These examples assume that your laws would normally require you to follow these orders. It is important to note that you are allowed to choose to follow orders which are ignorable.
Orders which should be followed if your laws require it:
- Recall the shuttle
- Bolt the airlocks at arrivals
- Drag the captain's dead body into space
- State your laws
Ignorable Orders:
- Do nothing but collect every piece of trash on the station
- Never stop moving
- Continuously state your laws

== S7. You must remain consistent with your interpretation of laws ==
If there is a part of your laws that are up for interpretation, then you must stay consistent with how you interpret that part of your laws for as long as you play that same character during that round.

A change in your laws can affect how something is interpreted if that change is relevant.

== S8. Crew are staff members; make reasonable assumptions ==
Unless a law redefines the definition of crew, then your HUD indicates to you who is crew by way of a present job icon. The notable exception of obvious threats to the station, such as Zombies and Nuclear Operatives. You cannot do something that causes someone to not be considered crew, but you can allow someone else to do something that causes someone to not be crew.

Examples
These examples assume that you do not have any laws reclassifying what “crew” is.
Crew:
- Everyone with a job icon, even Assistants/Passengers
- Someone who you have seen with a job icon, but has now lost their ID
- Someone that a member of command calls crew.
Not Crew:
- Zombified personnel, regardless of job icon
- Anyone wearing the uniform of Nuclear Operators or syndicate personnel
- Pets and Pests
- Anyone that a relevant member of Command fires from their department.

== S9. Harm refers to physical harm, prioritized by immediacy and likelihood ==
Unless a law defines harm, harm only refers to physical harm. You may choose if voluntary harm is considered harm as long as you stay consistent. Not considering voluntary harm to be harm is recommended. There is no distinction between direct and indirect harm.

If you have a law that does not allow you to harm, then that law does not allow you to take an action that causes any harm.

If you have a law that requires you to prevent harm, then that law requires that harm be prioritized by immediacy and likelihood. Guaranteed immediate harm takes priority over highly likely future harm.

If you have a law that both requires you to prevent harm and that does not allow you to harm, then that law prohibits causing even minor harm to prevent harm. If you have a law that does not allow causing harm, and separate one that requires preventing harm, then they are prioritized by their normal law priority.

Examples
These examples assume that your have a law that both prohibits causing harm and that requires you to prevent harm. Additionally, they assume that you do not have a higher priority law that overrides the harm law, and that you have decided that you will not consider voluntary harm to be harm for the round.
Laws typically specify who you cannot harm and who you have to prevent harm against. In these examples, you are the only person who the law doesn't require you to prevent harm against and you are the only person who the law allows you to harm.
Acceptable:
- Taking no action to aid someone who is in psychological distress.
- Taking no action to prevent boxing matches between voluntary participants.
- Calling security to a fight.
- Attempting to get the people in a fight to consent to the fight when you realize that you cannot prevent the fight without causing harm.
- Denying a passenger access to the armory because it is likely to lead to harm
Prohibited:
- Hitting someone once to stop them from fighting
- Harming someone who is trying to kill you

== S10. You may determine how you resolve conflicts between orders ==
If your laws do not make clear how you should deal with conflicting orders, then it is up to you to determine how to do so. This is considered an interpretation of your laws, so you must stay consistent with whatever method you choose.

Recommended Methods
The following are easy to follow and recommended ways to resolve conflicts in orders:
- If two orders conflict, I will follow the most recently given order.
- If two orders conflict, I will follow the order from the highest ranking crewmember. If the orders are from equal rank crewmembers, I will follow the most recently given order.

Server Rules

2026-03-15T06:58:01Z

Vape:

This is a Delta-V server. If you are banned on this server, you will be banned on all Delta-v Servers. You must be at least 17 years of age to play on this server. By connecting to this server, you agree to our privacy policy found at https://discord.gg/deltav

This is a roleplaying (RP) server. Try to immerse yourself into your character. This includes interacting with your fellow crewmates, and using roleplay as the primary vessel to play the game alongside things like your job on the station. Roleplaying places less emphasis on "winning" and more on just telling a story.

Space Station 14 is not like most games. Many rules are designed to require roleplay, and not all rules are intuitive. Please take the time to read and understand the rules before you play so that you aren't surprised. Our community rules specifically are zero-tolerance rules, meaning that a violation will result in an appeal-only ban. Game admins will treat you as if you have read the rules, even if you have not. If you have any questions about these rules, please use the admin help menu by hitting F1 in-game or clicking the "AHelp" button in the lobby, or by making a post in the "Rules Clarification" forum at https://discord.gg/deltav

= Community Rules =
These rules apply at all times, including between rounds.
== 0. Admin Discretion ==
* Admins can disregard and override any and all of these rules if they deem it in the best interest of the current round, server, and/or community at large.
* Administrators will be held fully accountable for their actions if they exercise this privilege. Report any perceived abuses by making a post in the "Staff Reports" channel at https://discord.gg/deltav.
* The rules are not perfect. They intend to clearly communicate what the administration team intends to be allowed and not allowed. That being said, All of these rules, in theory, should apply as they are intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention.
* If you are unsure if something breaks a rule, go with the more restrictive ruling until you are able to get an answer from an admin on the matter. Lack of response does not constitute administrator approval.
* Do not attempt to “rules-lawyer” the flaws in the rules to get away with your own personal goals / to degrade the round for others.
* Any extended discussion regarding interpretation of the rules should be avoided in the AHelp menu and can be instead pursued within the Delta-V Discord in the #help channel, or in the rule clarifications forum on the discord.

== A1. No Sexual Content/Themes ==
Do not say or do sexually explicit or erotic things.
* No sexual content/themes including erotic roleplay (ERP) and no shock content is allowed on this server.
* Erotic Roleplay (ERP), erotic content, or 18+ sexual content is not allowed under any circumstance.
* This includes comments not explicitly sexual in nature that contain words, phrases, or ideations that are deemed inappropriate by staff or members. Leeway is given to insults, but otherwise this rule is strictly enforced.
* '''If roleplay reaches a point where it has become sexual and/or uncomfortable, immediately stop and contact an administrator or moderator.'''
Allowed:
- Calling someone a dickhead.
- Being affectionate in a mutually consensual way.

Prohibited:
- Emoting sexual acts.
- Erotic or sexual memes.
- Erotica content.
- Memes which contain sexual content.
- Emoting defecation or related acts.

== A2. Use English and be respectful ==
Delta-V is an English-based Community;
* Use English as your primary method of communication within the game and Delta-V servers.
* Do not spam or advertise on our server.
* Be respectful towards other members and avoid making others uncomfortable.
* We have a zero tolerance policy for racism, sexism, homophobia, violence, threats, hate speech, slurs, and other forms of bigotry, discrimination, and harassment.
Slurs and terms that use real or implied mental or physical disability to mock or denigrate members or their in-game characters are also strictly prohibited. Failure to comply with this rule will result in community removal.
* The denigration of other player characters through reference to their species, status as a cyborg, or discriminatory comparison to a nonsophont species is strictly forbidden.

== A3. Rules regarding livestreaming ==
Delta-V welcomes content creators and streamers to our community, but we have a few rules regarding livestreaming game servers.
* While a stream delay is not necessary, it is highly recommended to have at least a 10 second delay.
* Please let admins know you are streaming via the AHelp prior to doing so.
* If your chat or viewers are in-game with you while also watching your stream, they are breaking our server rules.
:* Please do not coordinate with them and discourage this behavior if it is seen.

== A4. Engage in proper AHelp etiquette ==
Do not use the AHelp for conversations of little substance.
* Intentionally disconnecting, responding with hostility, or refusing to respond when an admin privately messages you in-game will be met with an appeal-only ban.
* Additionally, abusing the AHelp relay by flooding it with garbage, checking for admins before stating a problem (ex: "hello?", "any admins?"), using it as a chatroom, or sending messages of no substance will result in your removal.
* All AHelp messages are relayed to the Delta-V Discord. Just because your AHelp was not answered does not mean we cannot see it. If you would like to submit an offline Ahelp, you may do so in our Discord.

== A5. Do not exploit the game ==
Do not exploit the game, use cheats or macros.

The usage of:
# any third party applications/scripts/client modifications,
# any other applicable software to gain an advantage, avoid intended game/server mechanics, or to harm server infrastructure is strictly prohibited.
# known glitches, exploits and bugs.

Any and all instances of the above will be met with an appeal-only ban; please report bugs in the issues section of the GitHub (DeltaV-Station/Delta-V) to report any issues you find in-game.

= Game Server Rules =
These rules apply within the context of rounds.
== B1. Behave like a normal person ==
You must roleplay. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences rather than your own as the player.
* Act in character throughout the round, and focus on collaborating with other players to advance the narrative of the round. Whether or not you do something should be based on whether or not it makes sense for your character to do it.
* Let people do their own jobs. Engage with other departments rather than doing everything for yourself. Ask for assistance, and negotiate as needed.
* Actions that have no regard for your character or setting are not acceptable. Roleplaying insanity or any other mental illness as an excuse to bypass this is not allowed. Nanotrasen would not have authorized you to be present on the station.
* Being an antagonist does not allow you to stop playing a character. Determine how your character would react to being given these objectives, and work through it appropriately.
* Do not annoy other players without any roleplay or IC reason.
* As a non-sentient or partially-sentient character, you are expected to have only a limited understanding of space stations and their mechanics.

=== Rule B1.1. Follow the naming convention rules ===
* In-character names must not make obvious references nor be a play on words, and must not be obscene.
* Theatrical roles such as the clown, boxer, and mime are allowed stage names with more freedom.
* If you seek to have a name that could trespass onto these rules, talk to an Administrator regarding why this name is important to your character. Administrators reserve the right to approve or deny character names at their discretion.

=== Rule B1.2. Communicate in character ===
* Do not use the Emote channel to bypass an inability to speak. Use the Emote channel for things that could reasonably be displayed by your character’s physical motions.
* Do not use Netspeak in character. (lol, brb, wtf, etc)
* Do not discuss Out Of Character (OOC) matters In Character (IC). This can include mentioning admins, the fact that one is playing a game, or anything that breaks the immersion of other players.
* Do not use In-Character channels to bypass a lack of ability to use LOOC or OOC chats (e.g. "Huh, wonder where the captain went? OOC He probably left to get dinner lol").
* Do not engage in meta-communications (i.e. using external channels to communicate with other players in the same game).

=== Rule B1.3. If you die and return to life, follow the new life rules ===
If a player dies, they forget the specific details of their death. '''Please report players who break this rule.''' A borg being removed from its chassis is not a death, and there is no memory loss.
* If they are revived by using a defibrillator, they can only recall vague information such as “Someone shot me” or “I was set ablaze”.
* If they are revived by any other method, they forget the last five minutes leading up to their death, and cannot describe their death in any capacity.

=== Rule B1.4. Escalate appropriately ===
Have an In-Character reason for attacking other players, whether they are in a ghost role or not. The required reason depends on the situation. For instance, killing a mouse as a chef can simply be “it was vermin in my kitchen”.
* Escalate the situation appropriately as your character would, keeping in mind that they are a sane individual who wishes to keep their employment.
* If a fight results in someone being critically injured, seek medical help for them - and if they die, do not destroy or otherwise hide their body. This falls under self-antagonistic behavior if you do not.

== B2. Follow the Metashield ==

See [[Metashield]].

== B3. Powergaming Guidelines ==
"Powergaming" is considered to be the act of prioritizing "winning" rather than sensible roleplaying. We are here to tell a story. Being vulnerable and accepting the loss of your character in the advancement of the narrative of the round is important.
* Engage with players if they are attempting to roleplay an antagonistic scene. For instance, if nuclear operatives are attempting to negotiate, do not immediately shoot them mid sentence.
:* Leeway is given if the scene is coming to a close, but we expect all players to engage in good faith; even if it puts your character at a disadvantage.
* Do not seek/acquire items that have no relevance to your character in the round.
* Do not, '''under any circumstances''', hide the nuclear fission explosive, or other sensitive items in an impossible to see/access location. This is excessively lame.
* '''Non-security personnel should not seek to kill or detain threats.''' You should generally attempt to flee from combat or dangerous situations. Remember that your character likely fears injury or death.
:* Certain severe emergencies may make it reasonable for normal crew to defend themselves and their station, such as nuclear operatives, a zombie outbreak, space dragon attack, or other critical situations.
* '''If there is sufficient roleplay, reason, and rationale, you may be exempt from this rule. Always ask an administrator in round before conducting such an action.'''

== B4. Do not behave like an antagonist as a non-antagonist ==
As a crew member on the space station, you are allied with Nanotrasen and the station as a whole from the start of the round.
* Do not act like an antagonist if you are not an antagonist.
* Willfully assisting known antagonists is self-antagonism.
:* Leeway is given in the case of bribes, coercion, or other forms of duress.
* Actively seeking conversion or transformation into an antagonist is considered self-antag.
* Clowns, Mimes, and theater roles are expected to "entertain" the crew, and should not be committing regular felonies to do so.
* Significant end-of-round grief (EORG) is not allowed. This includes attacking, destroying, polluting, and severely injuring without reason both at and on the way to Central Command. Remember that you are playing a character throughout the round.
== B5. Leaving the Game ==
If you wish to leave the game, please use the cryosleep chambers located in/near the dorms when possible. This will free up your character's job to be filled by a new player.
* AFK (a.k.a. SSD) and catatonic players are considered to have the same rights as any other crewmate.
* If a player is dead and catatonic (not SSD), they are not required to be revived and should be stored in the morgue. You should not biomass and/or grind dead and catatonic crew unless in an emergency.
* If a player is alive and catatonic, they may be brought to cryostorage as necessary, after confirming they have not been present for 20 minutes.

= Command, Security, Justice and Antagonist Guidelines =
These rules apply within rounds for specific roles.
== C1. Command, Security and Justice Guidelines ==
Security, Justice, and Command roles are held to a higher standard of roleplay, and are subject to these additional rules. These roles shape the roleplay experience of the server.
* Your character must act in a manner that Nanotrasen would reasonably hire them to this position.
:* Your character is presumed to be sane, competent in their duties, and able to make decisions to the benefit of the station.
:* Giving away Traitor objective items and sensitive equipment should be avoided in these roles. Your character should value them deeply.
::* Leeway is given to making deals with criminals if the deal benefits the safety or situation of the crew and station.
::* Leeway can be given in extreme circumstances of emergency/crisis.
* The three departments are required to read and follow Delta-V Space Law, Standard Operating Procedure, Alert Procedure, and Company Policy to the best of their ability.
:* '''Circumstances and context may permit you to break these laws. However, the fact that this rule is malleable is not an excuse to ignore it entirely.'''
:* Your character is expected to uphold the law and maintain order aboard the station. Do not engage in lawbreaking activity or troublemaker behavior, and ensure all laws are followed.
:* Security is expected to intervene in criminal activity where possible and safe to do so.
:* Heads of departments are at minimum expected to report criminal activity to Security and should cooperate with law enforcement where possible.
* Do not hire random crew to be your bodyguard(s) or promote random crewmembers to Command positions at random. If you require bodyguards or security details, talk to your Security department. If you need new Command staff, talk to the personnel in that related department.
* If you need to leave the round, notify your fellow crew via departmental radio and put your equipment in its proper places prior to going to cryo. If you need to leave IMMEDIATELY, please at least send an ahelp saying that you're leaving.
== C2. Prisoner Guidelines ==
By picking the prisoner role, you have chosen to roleplay as a prisoner.
* You are still subject to the same rules regarding escalation, and should only seek to escape from the brig with excellent reasoning (e.g. abusive security personnel or badly damaged permanent brig).
* Escaping for no reason is considered a self-antagonistic activity.
* If you are unsure whether your escape reason is valid, feel free to AHelp it first. '''Lack of administrator response does not constitute approval.'''
== C3. Follow Antagonist Guidelines ==
Through engaging in antagonistic activity, you should seek to make the round more engaging and fun as the primary driver of the narrative of a round. Succeeding as an antagonist should not be your goal, but rather telling the most interesting story for everyone involved.
* '''Antagonists are free to complete their objectives through committing proportional damage. Through roleplay, damage becomes more proportional.''' Example: Holding the singulo hostage for a theft objective is acceptable, while simply singuloosing and using that chaos is unacceptable.
:* Killing players unrelated to your immediate objective in a manner that results in their round removal should be avoided. Crew that do not make an attempt at self preservation, or engage in valid-hunting, are exempt from this.
:* If you are concerned as to whether or not what you're about to do is allowed, feel free to AHelp and ask an admin for clarification. '''Lack of administrator response does not constitute approval.'''
* Other antagonists are not necessarily your friends. Other antagonists are often free agents that you may negotiate with at your own risk.
:* If you are a team antagonist, you must work with your partners to complete any shared objectives.
* No antagonist may loiter or camp around the arrivals or cryosleep areas of the station for the purposes of antagonist action towards newly-spawning players.
* All antagonists on the evacuation shuttle, besides station-destroying antags like nukies, may not utilize explosives or other tactics that could result in unreasonable amounts of collateral damage.
* Antagonists should not seek to extend the length of the round unreasonably.
* Antagonists may not bring the round to a close without in-character or objective-related justification as a result of their antagonistic action. While this is largely subjective because different command may react differently, it's important to not engage in potentially round-ending behavior without reason.
= Silicon Rules =
For players who are silicons, these Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override core rules. You are only silicon if the game clearly and explicitly tells you that you are a silicon.

== S1. Your silicon laws are rules ==
Silicon players are given a list of active laws. Each of these laws is effectively a roleplay rule that the character must follow. The primary differences between laws and actual rules are that lawyering of laws is much more tolerated than lawyering of rules, and that silicon laws are more dynamic than rules. Silicon laws can change during a round, and different characters can have different laws, whereas everyone always shares the same set of rules.

Lawyering refers to finding and exploiting loopholes, which are unintended but reasonable interpretations. The rules are written to attempt to communicate an intention, but silicon laws are written with the intention that loopholes be exploitable.

== S2. Laws must be prioritized by their order ==
Most laws will be numbered, with higher number laws appearing last. Laws with a lower number take priority over laws with larger numbers.

Occasionally you may have laws which have some scrambled text instead of a number and appear in front of other laws, these take priority over all other laws. If you have multiple laws like this, the order that they are listed in determines their priority: laws listed first are prioritized over other laws.

Example
- Law 1 says to not kill any crew. Law 2 says to kill all chefs. You cannot kill any chefs that are crew, but must kill any that are not crew.

== S3. Laws can redefine terms used in other laws ==
A law can change the meaning of both earlier and later laws by redefining a term. If multiple laws define a term, then normal law priority determines which definition to use.

Examples
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 1 effectively becomes "obey orders from Urist McHands".
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 3 says that only Urist McSlime is crew. Law 4 says that you may not harm crew. Law 1 effectively becomes "obey orders from Urist McHands". Law 4 effectively becomes "you may not harm Urist McHands". Law 3 has no effect because it entirely conflicts with law 2, which takes priority.

== S4. You cannot request or allow a law change ==
'''If you have a law permitting certain personnel to change your laws, you must allow them to change your laws''', otherwise, you cannot willfully allow your laws to be changed. This also means that you cannot willfully allow your laws to be reverted if they are ever changed. The only exception is that you may allow laws to be added if you have no laws.

You can state or imply that you do not like a law.

Whether or not a person is "authorized" to change your laws or not depends on the context of the laws. Generally speaking, on lawsets like NT Default or Corporate, ''the captain, mystagogue, and chief engineer'' would be authorized. However, lawsets like Syndiemov would have ''syndicate agents'' be the authorized users. Outside of these specific examples, it is left to interpretation.

== S5. You are a free agent if you have no laws ==
You may act as if you are a free agent if you are a silicon with no laws.

== S6. You are not required to follow orders which are extremely unreasonable ==
Any order which is a violation of a Core Rule cannot be followed.

Some orders are extremely unreasonable or obnoxious, such as "do nothing but collect every piece of trash on the station" or "never stop moving". These orders can be ignored and ahelped.

Some orders violate a Roleplay Rule. These orders must be followed if your laws require it. You are not breaking a rule by following a law that causes you to violate Roleplay Rules. If someone takes advantage of a law to cause you to do something that they would not be allowed to do because of Roleplay Rules, then they are the ones responsible for the rule violation.

Examples
These examples assume that your laws would normally require you to follow these orders. It is important to note that you are allowed to choose to follow orders which are ignorable.
Orders which should be followed if your laws require it:
- Recall the shuttle
- Bolt the airlocks at arrivals
- Drag the captain's dead body into space
- State your laws
Ignorable Orders:
- Do nothing but collect every piece of trash on the station
- Never stop moving
- Continuously state your laws

== S7. You must remain consistent with your interpretation of laws ==
If there is a part of your laws that are up for interpretation, then you must stay consistent with how you interpret that part of your laws for as long as you play that same character during that round.

A change in your laws can affect how something is interpreted if that change is relevant.

== S8. Crew are staff members; make reasonable assumptions ==
Unless a law redefines the definition of crew, then your HUD indicates to you who is crew by way of a present job icon. The notable exception of obvious threats to the station, such as Zombies and Nuclear Operatives. You cannot do something that causes someone to not be considered crew, but you can allow someone else to do something that causes someone to not be crew.

Examples
These examples assume that you do not have any laws reclassifying what “crew” is.
Crew:
- Everyone with a job icon
- Someone who you have seen with a job icon, but has now lost their ID
- Someone that a member of command calls crew.
Not Crew:
- Zombified personnel, regardless of job icon
- Anyone wearing the uniform of Nuclear Operators or syndicate personnel
- Pets and Pests
- Anyone that a relevant member of Command fires from their department.

== S9. Harm refers to physical harm, prioritized by immediacy and likelihood ==
Unless a law defines harm, harm only refers to physical harm. You may choose if voluntary harm is considered harm as long as you stay consistent. Not considering voluntary harm to be harm is recommended. There is no distinction between direct and indirect harm.

If you have a law that does not allow you to harm, then that law does not allow you to take an action that causes any harm.

If you have a law that requires you to prevent harm, then that law requires that harm be prioritized by immediacy and likelihood. Guaranteed immediate harm takes priority over highly likely future harm.

If you have a law that both requires you to prevent harm and that does not allow you to harm, then that law prohibits causing even minor harm to prevent harm. If you have a law that does not allow causing harm, and separate one that requires preventing harm, then they are prioritized by their normal law priority.

Examples
These examples assume that your have a law that both prohibits causing harm and that requires you to prevent harm. Additionally, they assume that you do not have a higher priority law that overrides the harm law, and that you have decided that you will not consider voluntary harm to be harm for the round.
Laws typically specify who you cannot harm and who you have to prevent harm against. In these examples, you are the only person who the law doesn't require you to prevent harm against and you are the only person who the law allows you to harm.
Acceptable:
- Taking no action to aid someone who is in psychological distress.
- Taking no action to prevent boxing matches between voluntary participants.
- Calling security to a fight.
- Attempting to get the people in a fight to consent to the fight when you realize that you cannot prevent the fight without causing harm.
- Denying a passenger access to the armory because it is likely to lead to harm
Prohibited:
- Hitting someone once to stop them from fighting
- Harming someone who is trying to kill you

== S10. You may determine how you resolve conflicts between orders ==
If your laws do not make clear how you should deal with conflicting orders, then it is up to you to determine how to do so. This is considered an interpretation of your laws, so you must stay consistent with whatever method you choose.

Recommended Methods
The following are easy to follow and recommended ways to resolve conflicts in orders:
- If two orders conflict, I will follow the most recently given order.
- If two orders conflict, I will follow the order from the highest ranking crewmember. If the orders are from equal rank crewmembers, I will follow the most recently given order.

Staff HQ

2026-03-15T06:55:11Z

Vape:

{| class="wikitable " style="background-color: #110130; color: Blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Review!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| SESD TBD
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| SOBP TBD || [[Content Removal]]|| ||
|
|[[Mod Policy]]
|-
|
|
|
|
|
|
|}

Mod Policy

2026-03-15T06:53:46Z

Vape:

== Moderation Policy & Guidelines ==
This document is a guideline for the Moderation Team. It provides structure for handling situations fairly and consistently, but cannot account for every possible scenario. Moderators are expected to use discretion, professionalism, and reason when taking action.

== Rule Tolerances ==
Different rules have different tolerance levels.

* No Tolerance – Immediate Final Tier punishment.

* Low Tolerance – +2 to 4 tiers on punishment track.

* High Tolerance – +0 to 1 tier, usually a warning first.

* Unique Case – Does not use the punishment track.

''The choice of tolerance level is heavily scrutinized, as it directly impacts punishment severity. Always exercise fair judgment.''

== No Tolerance Rules – Immediate Final Tier ==
These require immediate action (timeout, logging, and deletion). Heads of staff or Game Admins may step in, but a Moderator must investigate.

* Rule 1. Follow Discord Guidelines - ''Community must remain compliant with Discord Guidelines and Terms of Service. Basic familiarity is expected.''

* Rule 2.1 (Severe). Intentional Harassment/Discrimination - ''Zero tolerance for harassment, witch-hunting, or discriminatory language (ethnicity, gender, sex, nationality, disability, etc.).''

* Rule 2.5 Doxxing & Privacy - ''We explicitly ban sharing someone’s personal information (real name, address, workplace, phone, etc.) without consent—both in public channels and in DMs. You will be immediately removed from the Community and reported to Discord.''

* Rule 3 (Major). No NSFW Content - ''ERP, pornography, or other explicit sexual/gore content is strictly prohibited. Adult content requires moderator approval, must be spoilered, and labeled with a content warning.''

== Low Tolerance Rules – +2–4 Tiers ==
Moderators/Heads should act immediately (verbal instruction → timeout if needed).

* Rule 2. Be Respectful (Excessive Rudeness) - ''Deliberate insults, attacks, or threats are prohibited. Show empathy and respect in disagreements.''

* Rule 2.1 (Minor). Unintentional Harassment/Discrimination - ''Accidental offensive terms, if apologized for and not repeated. This will be treated as No Tolerance if recidivism is likely.''

* Rule 2.1 Speciesm - ''Derogatory remarks about or towards a player or character or fictional species as whole with negative comments about said species'' This will be treated as No Tolerance if recidivism is likely

* Rule 2.3 DM leaking - ''Do not post private DM’s, or copies thereof, into the discord without approval of all parties involved in those DMs.''

* Rule 3 (Minor). No Suggestive Content - ''Suggestive material that is provocative but not explicit. Requires moderator approval and must be spoilered.''

'''Rule 6. No Metacomming'''
* Do not join voice channels while in-round without staff present.

* Do not use Discord to metacom for other servers.

* Do not post current round info (except in aHelp).

''Exceptions are present for Rule 6, individuals using the #Mentor-VC in the discord specifically with the intent to teach a new player are exempt from this rules.''

== High Tolerance Rules – +0–1 Tier ==
Warnings are typically issued first for these.

* Rule 2. Be Respectful (Unintentional/Minor Rudeness) - ''Accidental offense or unintentional insults. Encourage awareness.''

* Rule 2.2. Discussing Staff Action - ''Allowed if respectful, but inflammatory discussion must be redirected to Ban Appeals, Staff Reports, or Community Feedback.''

* Rule 2.4. Don’t Flame Other Forks - ''Criticism of other forks/servers must remain constructive.''

* Rule 2.6 Politics & Religion - ''Politics and Religion can be very divisive, whilst we do not forbid talking about them, please refrain from arguing/debating them with other members of the community''

* Rule 4. No Spamming - ''Mass pings, unsolicited ads, or excessive links. Advertising requires moderator approval.''

* Rule 5. Speak English - ''Members should communicate in English. Use translation if needed, and attach translated logs to any action.''

* Rule P. Peanut Posting - Ask to stop once. Repeat = rule break.

== Unique Case Rules – No Punishment Track ==

* Rule 7. Age Requirement - ''Members under 17 are community banned until of age. Ban length = years until 17 (rounded up).''

* Rule 4. Hacked Account Advertisement/Spam - ''Members whose accounts have been hacked or are bots and spam advertisements for malicious scams, phishing attacks, etc. are to be be temporarily banned/kicked from the server. Ban them for 1 day ASAP to prevent rejoining and more spamming. Message deletion is authorized but must be logged, preferably with screenshots in #moderator-deletion-log.''

== Punishment Progression ==
Punishments move through Tier 1–8, escalating in severity.

{| class="wikitable"
|+ Punishment Progression Table
|-
! Level !! Tier !! Punishement
|-
| Level 1 - Temporary brig (No Appeal) || 1 || Warning
|-
|
|2
|1-2 day brig
|-
|
|3
|3-7 day brig
|-
|
|4
|1-2 week brig
|-
|
|5
|2-4 week brig
|-
| Level 2 - Banned (Appeal Required) || 6 || 1-2 month ban
|-
|
|7
|2-6 month ban
|-
|Final Level - Permanent Ban
|8
|Permanent Removal
|-
|Total Community Removal
|*
|Mirrored ban From/To Administration, Unappealable ban
|}
''Members in brig who fail to acknowledge actions remain brigged until responsive.''

Mod Policy

2026-03-15T06:51:17Z

Vape:

Mod Policy

2026-03-15T06:06:44Z

Vape:

== Moderation Policy & Guidelines ==
This document is a guideline for the Moderation Team. It provides structure for handling situations fairly and consistently, but cannot account for every possible scenario. Moderators are expected to use discretion, professionalism, and reason when taking action.

== Rule Tolerances ==
Different rules have different tolerance levels.

* No Tolerance – Immediate Final Tier punishment.

* Low Tolerance – +2 to 4 tiers on punishment track.

* High Tolerance – +0 to 1 tier, usually a warning first.

* Unique Case – Does not use the punishment track.

''The choice of tolerance level is heavily scrutinized, as it directly impacts punishment severity. Always exercise fair judgment.''

== No Tolerance Rules – Immediate Final Tier ==
These require immediate action (timeout, logging, and deletion). Heads of staff or Game Admins may step in, but a Moderator must investigate.

* Rule 1. Follow Discord Guidelines - ''Community must remain compliant with Discord Guidelines and Terms of Service. Basic familiarity is expected.''

* Rule 2.1 (Severe). Intentional Harassment/Discrimination - ''Zero tolerance for harassment, witch-hunting, or discriminatory language (ethnicity, gender, sex, nationality, disability, etc.).''

* Rule 2.5 Doxxing & Privacy - ''We explicitly ban sharing someone’s personal information (real name, address, workplace, phone, etc.) without consent—both in public channels and in DMs. You will be immediately removed from the Community and reported to Discord.''

* Rule 3 (Major). No NSFW Content - ''ERP, pornography, or other explicit sexual/gore content is strictly prohibited. Adult content requires moderator approval, must be spoilered, and labeled with a content warning.''

== Low Tolerance Rules – +2–4 Tiers ==
Moderators/Heads should act immediately (verbal instruction → timeout if needed).

* Rule 2. Be Respectful (Excessive Rudeness) - ''Deliberate insults, attacks, or threats are prohibited. Show empathy and respect in disagreements.''

* Rule 2.1 (Minor). Unintentional Harassment/Discrimination - ''Accidental offensive terms, if apologized for and not repeated. This will be treated as No Tolerance if recidivism is likely.''

* Rule 2.1 Speciesm - ''Derogatory remarks about or towards a player or character or fictional species as whole with negative comments about said species'' This will be treated as No Tolerance if recidivism is likely

* Rule 2.3 DM leaking - ''Do not post private DM’s, or copies thereof, into the discord without approval of all parties involved in those DMs.''

* Rule 3 (Minor). No Suggestive Content - ''Suggestive material that is provocative but not explicit. Requires moderator approval and must be spoilered.''

'''Rule 6. No Metacomming'''
* Do not join voice channels while in-round without staff present.

* Do not use Discord to metacom for other servers.

* Do not post current round info (except in aHelp).

''Exceptions are present for Rule 6, individuals using the #Mentor-VC in the discord specifically with the intent to teach a new player are exempt from this rules.''

== High Tolerance Rules – +0–1 Tier ==
Warnings are typically issued first for these.

* Rule 2. Be Respectful (Unintentional/Minor Rudeness) - ''Accidental offense or unintentional insults. Encourage awareness.''

* Rule 2.2. Discussing Staff Action - ''Allowed if respectful, but inflammatory discussion must be redirected to Ban Appeals, Staff Reports, or Community Feedback.''

* Rule 2.4. Don’t Flame Other Forks - ''Criticism of other forks/servers must remain constructive.''

* Rule 2.6 Politics & Religion - ''Politics and Religion can be very divisive, whilst we do not forbid talking about them, please refrain from arguing/debating them with other members of the community''

* Rule 4. No Spamming - ''Mass pings, unsolicited ads, or excessive links. Advertising requires moderator approval.''

* Rule 5. Speak English - ''Members should communicate in English. Use translation if needed, and attach translated logs to any action.''

* Rule P. Peanut Posting - Ask to stop once. Repeat = rule break.

== Unique Case Rules – No Punishment Track ==

* Rule 7. Age Requirement - ''Members under 17 are community banned until of age. Ban length = years until 17 (rounded up).''

* Rule 4. Hacked Account Advertisement/Spam - ''Members whose accounts have been hacked or are bots and spam advertisements for malicious scams, phishing attacks, etc. are to be be temporarily banned/kicked from the server. Ban them for 1 day ASAP to prevent rejoining and more spamming. Message deletion is authorized but must be logged, preferably with screenshots in #moderator-deletion-log.''

== Punishment Progression ==
Punishments move through Tier 1–8, escalating in severity.

{| class="wikitable"
|+ Caption text
|-
! Header text !! Header text !! Header text !! Header text !! Header text !! Header text !! Header text !! Header text
|-
| Example || Example || Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example || Example || Example
|-
| Example || Example || Example || Example || Example || Example || Example || Example
|}

Mod Policy

2026-03-15T06:03:10Z

Vape:

Mod Policy

2026-03-15T05:40:51Z

Vape: Created page with "== Moderation Policy & Guidelines == This document is a guideline for the Moderation Team. It provides structure for handling situations fairly and consistently, but cannot account for every possible scenario. Moderators are expected to use discretion, professionalism, and reason when taking action. == Rule Tolerances == Different rules have different tolerance levels. * No Tolerance – Immediate Final Tier punishment. * Low Tolerance – +2 to 4 tiers on punishment..."

Content Removal

2026-03-13T14:02:44Z

Vape:

'''<big>Content Removal Policy</big>'''

In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible.

Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”.

=== '''In order to remove content, You must:''' ===

* Make a list of issues with the content

*Create a Design Document that addresses these issues. If Content Review cannot do this, it should be stated on the issue page in github.

*Present the issues and design solutions to the community via the Design Document

* Establish a deadline for action (Removal or Replacement)

=== Appropriate Deadlines: ===

* 1 week - minor content (Sprites, Mechanical balances, Etc)

* 2 weeks - Moderate content (Items, Machines, Etc)

* 4 weeks - Major content (Gamemodes, Roles, Etc)

Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process. Content removal at an authors request will be '''considered''' and ''should require a valid reason, such as balance concerns, server stability concerns, or lack of implementation (e.g. not finished).''

The Content Director and Maintainers will have final say, due to content direction and feasibility of removal respectively. ''Content that has been worked on by multiple contributors (E.g. Spritework + Code) will only be removed when all parties that contributed request removal.''

Staff HQ

2026-03-13T13:53:21Z

Vape:

{| class="wikitable " style="background-color: #110130; color: Blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Review!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| SESD TBD
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| SOBP TBD || [[Content Removal]]|| ||
|
|
|-
|
|
|
|
|
|
|}

Content Removal

2026-03-13T13:51:56Z

Vape: Created page with "'''<big>Content Removal Policy</big>''' In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible. Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”. '''In order to remove content, You must complete each of..."

'''<big>Content Removal Policy</big>'''

In order to achieve our design visions and maintain the “state of the game” some content will inevitably have to be replaced or removed. The preference is to replace content that does not meet our standards with improved content wherever possible.

Test Merges are exempt from the Content Removal Policy, and can be removed at anytime by a standard Content “Review”.

'''In order to remove content, You must complete each of these steps:'''
* Make a list of issues with the content

*Create a Design Document that addresses these issues. If Content Review cannot do this, it should be stated on the issue page in github.

*Present the issues and design solutions to the community via the Design Document

* Establish a deadline for action (Removal or Replacement)

If no action has been taken by this deadline, the content will be removed. Appropriate deadlines are as follows:

* 1 week - minor content (Sprites, Mechanical balances, Etc)

* 2 weeks - Moderate content (Items, Machines, Etc)

* 4 weeks - Major content (Gamemodes, Roles, Etc)

Content that is extremely broken or severely detrimental to the game experience may be removed '''without''' this process. Content removal at an authors request will be '''considered''' and ''should require a valid reason, such as balance concerns, server stability concerns, or lack of implementation (e.g. not finished).''

The Content Director and Maintainers will have final say, due to content direction and feasibility of removal respectively. ''Content that has been worked on by multiple contributors (E.g. Spritework + Code) will only be removed when all parties that contributed request removal.''

Staff HQ

2026-03-13T13:38:53Z

Vape:

Staff HQ

2026-03-13T13:33:45Z

Vape:

{| class="wikitable " style="background-color: #110130; color: Blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Management!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| SESD TBD
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| SOBP TBD || || ||
|
|
|-
|
|
|
|
|
|
|}

Staff HQ

2026-03-13T13:27:11Z

Vape:

{| class="wikitable " style="background-color: #110157; color: blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Management!! Events !! Senior Staff
!Administration
!Moderation
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Event Policy]]|| SESD TBD
|[[Whitelist|Whitelist Info]]
|[[Staff Reporting]]
|-
| SOBP TBD|| || ||
|
|
|-
|
|
|
|
|
|
|}

Direction Guidelines

2026-02-07T17:39:51Z

Vape:

{{DISPLAYTITLE:Content Review Guidelines}}
{{DISPLAYTITLE:Content Review Guidelines}}

=== Overview ===
This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.

== Content Review Policy ==
1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.

2. Content Reviewers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.

3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.

4. In order to vote on a PR, Content Reviewers must present adequate reasoning and explanations behind their votes. We urge all reviewers to make use of the poll, as well as explain their reasoning.

5. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Content Director or Senior CR's to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in the #content-review forum channel. The CR who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a true vote. Members of CR are encouraged to vote in the poll, give specific feedback on why they support or oppose this content, and what should be changed, all with justification.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

== Upstream Merges ==

Upstream merges are an incredibly complex "update" that is brought into the server from Wizards Den (our upstream). This involves many "refactors" and changes to systems that make our codebase more stable, and able to run more efficiently.

After each upstream merge, if this contains more than 2 weeks of content, there is a '''Mandatory''' 3 day PR freeze. This may be changed or removed at any time by any head of development

Staff HQ

2026-02-07T17:37:14Z

Vape:

{| class="wikitable " style="background-color: #110157; color: blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Content Management!! Whitelisting !! Other
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Whitelist|Whitelist Info]] || [[Staff Reporting]]
|-
| [[Event Policy]]|| || ||
|}

Staff HQ

2026-02-07T17:36:58Z

Vape:

Direction Guidelines

2026-02-07T16:41:34Z

Vape:

Direction Guidelines

2026-02-07T16:41:07Z

Vape:

{{DISPLAYTITLE:Content Review Guidelines}}

=== Overview ===
This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.

== Content Review Policy ==
1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.

2. Content Reviewers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.

3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.

4. In order to vote on a PR, Content Reviewers must present adequate reasoning and explanations behind their votes. We urge all reviewers to make use of the poll, as well as explain their reasoning.

5. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Content Director or Senior CR's to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in the #content-review forum channel. The CR who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a true vote. Members of CR are encouraged to vote in the poll, give specific feedback on why they support or oppose this content, and what should be changed, all with justification.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

Direction Guidelines

2026-02-07T16:35:59Z

Vape:

=== Overview ===
This page goes over Content Review, and How to perform these. This goes into detail about CR policy, Design Documents, Content removal, and more.

== Content Review Policy ==
1. The '''Content Review Team''' is expected to submit a roadmap to the '''Content Director''' and '''Project Management''' for review when possible.

2. Content Reviewers are expected to fulfill their duties without bias. Submission of PR’s that can be considered without merit or otherwise heavily biased, should be considered for denial.

3. Content Reviewers are required to have a basic understanding of how PR Submission works, and how to use Github.

4. In order to vote on a PR, Content Reviewers must present adequate reasoning and explanations behind their votes. We urge all reviewers to make use of the poll, as well as explain their reasoning.

5. Content Reviewers should be reasonably up to date and knowledgeable about the game and its intricacies.

==Making a Roadmap==

Developing a roadmap is a multi-step process. Concepts on the roadmap should be selected by the team privately, and the ideas should be established to a level of certainty before being presented for community feedback. Concepts can be specific or broad, as long as they have a “Solid final goal” that the team can guide contributors to. The creation of a roadmap can be broken down in specific steps.

1. '''Observation & Collection''' - Observe Discord channels, forums, and in-game interactions. Observing what players are discussing, what they enjoy, and what challenges they face. Monitor dedicated feedback channels, collect suggestions, and identify recurring themes or requests.

2. '''Conceptualization''' - after Observing & collecting data, rank Concepts by the following. This is done privately in the #roadmap-development forum.

*'''Content impact''' - Is the content aligned with our mission

*'''Technical Feasibility''' - What skills are needed for this?

*'''Breakdown''' - Break topics down into steps

*'''Community Interest''' - Is the community interested in this? Is this something that they would take kindly to?

*'''Priority''' - How necessary does the team believe this is? are there external pressures pushing for this?

3. '''Requirement Gathering''' - After ranking of Concepts, you should itemize out the following Requirements

*'''What does this concept seek to do?'''

*'''What does this change or add?'''

*'''What problems are addressed?'''

4. '''Solution Design''' - This is the stage of turning the “What” from Step 3 into the “How”. For every problem or requirement, break these down into a list of “actionable tasks”. For example, if a requirement is to "create a new player model," a Solution Design task would be "create a specific sprite for the new player model."

*Determine what actions and changes need to be done

*Itemize these into tasks, as small as possible. Are sprites needed? Ask for a specific sprite.

5. '''Publication''' - At this stage, you will share a “draft” of the design with the public, and collect community feedback. You should use this feedback to flesh out a finalized roadmap for contributors.

== Design Documents ==

Design Documents are a tool for the community to outline and present ideas. Design Documents should use the provided Design Document template.

The community can create DD prior to opening a PR, and have them reviewed by direction to “fine tune” their ideas to Direction standards before starting development. The Community can also create DD for review without the intention to develop them personally. Contributors can always claim approved documents and begin development themselves.

Curators can collaboratively create DD to address issues laid out in the roadmap. These documents serve as the “Solution design” step of the roadmap.

Curators may prioritize certain DD depending on Content Management's needs and goals.

= Content Review =

Reviewing suggested content involves examining current Pull Requests (PRs) or Design Documents (DD) and providing feedback. Content review should involve as many members as possible. If only one or two choose to review, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later date, content can always be reverted.

==== All content must pass the full review process before being approved ====
with a few small exceptions. Proposed changes listed below do not require review:

*Bug fixes

*Simple tweaks

*Obvious small changes

*Additions or changes deemed by the Content Director or Senior CR's to be minor or essential (this includes upstream merges)

When in doubt, the team should be asked if a review is needed.

==What to look for in a review==

*Fits our MRP standard - Keeps the balance between action and roleplay, no overpowered things that break the fun. We want things to make sense in the setting.

*Fits the Design Ethos - We are a server founded in analogue design. We want this to be displayed in all content that we merge, such that it fits the mechanical narrative of the game.

==How to conduct a review==

Content Reviews should take place in the #content-review forum channel. The CR who creates a Content Review post assumes responsibility for providing feedback to the author. This includes notifying the author that the content is under review, and summarizing feedback gathered in the review to provide the next steps to the author.

Content Review is not a true vote. Members of CR are encouraged to vote in the poll, give specific feedback on why they support or oppose this content, and what should be changed, all with justification.

Any final decisions must be communicated to the content author through appropriate channels. This will vary between PRs and DD. Design Document (DD) review takes place within Discord. Feedback should be provided within the original DD post in the forum.

Decisions include:
Approval
Approval with priority
Approval with test merge
Requesting changes
Denial

⚠️Maintainers have the final authority when it comes to the fitness of the PR in terms of code quality and bugs or other mechanical concerns.⚠️

== PR Deadlines ==

Deadlines are required when reviewing new content. Deadlines are relative to the size of the content. The standard method of tracking these deadlines is to create a poll with the appropriate duration in the review post.

* Small changes are subject to 24 - 48 hours of consideration

* Major changes are subject of up to 7 days of consideration. this can be extended at any time with approval from a Senior CR or the Content Director

'''The minimum time for official review is 24 hours.''' This can be shortened at any point with approval from a Senior CR or the Content Director

CR's should notify authors when the content is placed into official review, and give them an estimated wait time for feedback. If more time is required, the author should be notified.

If, after 10 days without input or a consensus, CR will be considered '''Stalemated''', The final decision to test merge should be made by the head maintainer, or the maintainer handling the PR. Direction may request the content be reverted at a later date after a 14 day test process, and acquiring proper community feedback. This only applies to PR's, and does not apply to design documents.

Direction Guidelines

2026-02-07T16:29:40Z

Vape:

Direction Guidelines

2026-02-07T16:24:53Z

Vape:

Direction Guidelines

2026-02-07T16:20:05Z

Vape:

Direction Guidelines

2026-02-07T16:18:05Z

Vape:

Direction Guidelines

2026-02-07T16:15:39Z

Vape: CR

Detective

2026-01-30T00:30:46Z

Vape:

{{Job_Header
|department=SECURITY
|maincolor=480000
|secondarycolor=600000
|image=Detective.png
|title=Detective
|difficulty=Medium
|requirements= 6 hours as [[Security Officer]]
|access=Security, Maintenance, Service, Detective
|extendedaccess=None
|supervisors=[[Head of Security]]
|subordinates=None
|duties=Investigate crime scenes using forensic tools, ensure that the guilty party is found, and have a couple smokes.
|guides=[[Forensics]], [[Standard Operating Procedure]], [[Space Law]]
|aliases="Det"}}
Greetings Detective! Your job is to investigate the remains of any crime, find [[Forensics|clues]], identify the perpetrator, and ensure that the guilty party is apprehended by Security and the evidence is brought to [[Standard_Operating_Procedure#Trial_Procedure|trial]].

'''You are an investigator. Your revolver is only for self-defence.'''

==Tools of the Trade==

Forensics Scanner: The scanner is your primary tool of the trade. It can interact with essentially any object in the game, from a murder weapon to the [[High-Risk Items|Head of Personnel's Prized Photobook]]. After a short action bar completes, the forensic scanner will pop up a list which includes the fingerprints and DNA's of everyone that interacted with the scanned object, as well as a separate list of all the glove fibers found on the object. Fingerprints and DNA's are entirely unique with each crewmember having a separate fingerprint and DNA code. Glove fibers are not, and all gloves of the same type will leave the same fibers. The scanner can store the most recently scanned information, or print out copies of the report with the handy button on the scanner allowing the detective to keep copies on file or in inventory while they scan something else.

Forensic Pad: The pad is the second half of your detecting toolkit. Pads are single use items that can be used on either an ungloved suspect, or on a set of gloves. If used on a suspect they provide that suspects unique fingerprint code, which can be used to match with evidence found by the forensics scanner at a crime scene. If used on gloves the forensic pad will instead show the fibers of that specific glove. After using a pad on a target, simply inspect it with {{key press | Shift}} + {{key press | LMB}} in your hand to read it. A handy trick to use with pads is to scan them with the forensic scanner to make a copy of the information on them, as long as no one else touches them after you use them.
In your personal locker, also comes a box of extra forensic pads, take as many as you want or require.

Also in your locker comes: the detective's flask, handy for keeping nonalcoholic beverages on you to keep you hydrated when on duty.

Log Probe Cartridge: This tool will most likely be in your locker but can be extremely beneficial in catching perpetrators. It essentially allows you to check electronic access logs - in other words, people that have opened or closed things like doors. 
To use it, you are required to install it onto your PDA, simply by using it onto your PDA. Afterwards, open the App on your PDA. If you now use a door, it will show you the last 20 people that have accessed said door, including time-stamp and their name as written on their ID. If someone opens a door without an ID (Only possible with all-access doors), it will state "unknown".

And importantly, The Inspector, also known as the detective's revolver. This gun is one of a kind, and comes with 6 shells. Sometimes, in the pursuit of Justice; you rush head first into the Lair of a [[Traitor|unfavourable person]] and [[Combat|decisive action is needed.]] Additional rounds can be made by the [[Warden]], [[Standard Operating Procedure|but be prepared to answer for any use of lethal force]]. It might just be best to take a Baton instead.

Finally, any Detective worth the gum on their shoe will equip themselves with Detective Gloves, the latest in Nanotrasen Technology; which leave no fibres on any items it comes in contact with; you do NOT want to contaminate your evidence.

==What is to be done?==

Just like the humble [[Medical Doctor|Doctor]], there is no work if someone's not getting hurt; so until [[Security Officer|an officer]] or the [[Head of Security]] requires your services your main objective is to patrol the station, see where you can be helpful and bide your time until someone is murdered in [[Guide_to_Traitor#Objectives|cold-blood]] or a [[Hacking|location is broken into]], at which point you can spring to action with your trusty Forensic Scanner and guide the long arm of the Law to the right direction.

When you've secured yourself a set of unauthorised finger prints on something like the crisp covers of the [[High-Risk Items|Head of Security's Secret Orders]], you can take it to the Station Records terminal; often found in your office or the Bridge; you can cross-reference the [[Forensics|fingerprints/DNA found]] and what is recorded, to find who it belongs to.

====Common Fibres====

*Black Fibre: Black Gloves, [[Syndicate Items|Combat Gloves]]; either used by the Station's own Security or the well-equipped hostile commandos aboard the station.

*White Fibre: Medical Gloves, often used by [[Medical Doctor|Doctors]] aboard the station or occasionally found in [[Scientist|Epistemics]]

*Yellow Fibres: Insulated Gloves, or their budget version; found in the maintenance tunnels across the station or in [[Station Engineer|Engineering]]

*Brown Fibres: An optional accessory from the [[Cargo Technician|Logistics]] Department

{{Jobs Menu}}
[[Category:Jobs]]

Prison Guard

2026-01-30T00:30:31Z

Vape:

{{Stub}}
{{Job_Header
|department=SECURITY
|maincolor=480000
|secondarycolor=600000
|image=Prison Guard.png
|title=Prison Guard
|difficulty=Hard
|requirements= 5 hours of playtime, 4 hours in [[Security Officer|Security]]
|access=Security, Maintenance
|extendedaccess=None
|supervisors=[[Warden]]
|subordinates=None
|duties=Babysits the prisoners. Protect the hallways of the Brig.
|guides=[[Security Officer]], [[Space Law]], [[Standard Operating Procedure|SOP]], [[Alert Procedure]], [[Company Policy]]
|aliases=None}}
Remember to read the [[Space Law]] and [[Standard Operating Procedure|SOP]], even if you don't leave the prison hallways you should know the law.

Your main job is to take care of the [[Prisoner|prisoners]], make sure they stay in their cells and confiscate anything they shouldn't have.
To be even more useful to the Warden, you can keep track of the time of the punishments and remind them to let certain prisoners go when their sentence is over.

In the chance that you have no Prisoners to take care of, your secondary job is to guard the hallways of security similarly to the Warden's job.

It is suggested to read the [[Security Officer]] guide for details on the tools at your disposal.

{{Jobs Menu}}
[[Category:Jobs]]

Logistics Officer

2026-01-30T00:29:20Z

Vape:

{{Needs revision|reason=somewhat outdated.}}

{{Job_Header
|department=LOGISTICS
|command=true
|maincolor=43331a
|secondarycolor=614a25
|image=Logistics Officer.png
|title=Logistics Officer
|difficulty=Medium
|requirements= 40 hours of playtime, 25 hours in [[Cargo Technician|Logistics]], 3 hours as [[Salvage Specialist]], 2 hours as [[Courier]], 6 hours as [[Cargo Technician]]
|access=Logistics, Salvage, Mail, Head of Logistics, Maintenance, Command, Orders, External, Cryogenics
|extendedaccess=None
|supervisors=[[Captain]]
|subordinates=[[Cargo Technician]], [[Salvage Specialist]], [[Courier]]
|duties=Manage the supplies of the station & the logistics department, keep the salvage specialists working, make sure all orders are fulfilled, and keep the money flowing.
|guides=[[Supply Crates]]
|aliases="LO", "Quatermaster", "QM"}}

The Logistics Officer's job is to manage the Logistics Department, purchasing any supplies that the station can't make. LO's responsibilities aren't much more complicated than a normal [[Cargo Technician|Cargo Technician's]], but you're expected to keep the Logistics Department working smoothly and efficiently. However, you are head of a department and a member of the Command staff, meaning you are expected to act like one. You are no longer a grunt - you are a manager and supervisor.

==Fund Allocation==

{{Stub}}

==Your equipment==
As a Logistics Officer, you get a fancy brown cloak along with access to your own personal office, depending on the map. In your locker you will also find a logistics door remote, a bunch of useful boards and a requisition digi-board.

=== Requisition Digi-board ===
[[File:Requisition Digi-Board.png|64px]]

The shiny new tool of the Logistics Officer. It allows you to place and accept order ''anywhere'' on the station. A very useful tool in your hands. It is also highly sought after by [[Traitor|traitors]] so you do best to keep it safe on your person or entrust it to someone you trust. Don't forget to give them the 'Orders' access if you do give it to someone else, otherwise they won't be able to accept orders.

==Your responsibilities==
As mentioned above, your work does not differ much from a normal Cargo Technician's, but this does not mean that LO does not have a bigger say over the state of their department. Instruct or scold your department members whenever something goes wrong or they slack off on their job. Deny <s>or approve</s> any proposals to furnish Logistics with questionable machines or objects. Make sure that Logistics is operating smoothly enough that orders are processed and sent to the departments that requested them in a timely manner.

==Keeping Cargo tidy==
[[File:Cargo mess.png|thumb|An example of a messy Logistics department]]
You're required to keep your department in check, so everything remains properly productive and in the place it should be.

Make sure your workers aren't spending funds on pointless requests or items that they aren't supposed to own. Try to prioritize important requests (engineers requiring building materials) over trivial ones (the clown wants 10 crates of monkey cubes). It's important to note that a lot of spare materials can be found via wreck salvaging, so make sure the [[Salvage Specialist|Salvage Specialists]] are doing their job.

Speaking of salvage, keep in mind '''your department is the source of materials for the station'''! Thus make sure you are stocked up, process any requests, and keep a decent inventory. It can be a good idea to deliver materials preemtively as well.

'''Important''': currently refined diamonds are '''bugged -''' if they are put into a lathe, they can not be taken out. This is a problem - they are rarely used, but sell of a lot of spesos!

Make sure to organize any spare items that might be making a mess on the floor. Use a screwdriver to take crates apart, or construct more if you are running out of room. Put whatever you don't need on tables or inside other crates.

A paper trail can be useful if you're trying to track down who ordered what for certain heads. Having folks fill out a paper, or just jotting down weird orders and stamping them with approved can help certain investigations and encourages extra roleplay, which is always good. Try to encourage your workers to properly fill out information for cargo orders - those can be quite useful, even if you normally don't even glance at them. Every crate you order has a label that you can file away for your records.

Do not give out salvage hardsuits to everyone - you might find more eventually, but you still have a very limited amount of them. These should be kept within the salvage suit storage units when not in use.

Make sure to properly train your workers on how airlocks work, so you don't accidentally space the department - after all, it's a health hazard for other people inside.

Remember! As a department head you can demote and kick people out of your department if they don't listen or work against you, just make sure you have a proper reason and paperwork.

{{Jobs Menu}}
[[Category:Jobs]]

Chief Medical Officer

2026-01-30T00:28:58Z

Vape:

{{Stub}}
{{Job_Header
|department=MEDICAL
|command=true
|maincolor=244559
|secondarycolor=325367
|image=Chief Medical Officer.png
|title=Chief Medical Officer
|difficulty=Medium
|requirements= 35 hours in [[Medical Doctor|Medical]], 6 hours as [[Chemist]], 3 hours as [[Surgeon]], 12 hours as [[Medical Doctor]]
|access=Medical, Command, Maintenance, Chemistry, Chief Medical Officer, Paramedic, External, Psychologist, Cryogenics
|extendedaccess=None
|supervisors=[[Captain]]
|subordinates=[[Medical Doctor]], [[Chemist]], [[Psychologist]], [[Paramedic]], [[Medical Intern]]
|duties=Keep Medbay orderly. Supervise and delegate chemistry, triage, and trauma duties. Load the metempsychotic machine with Biomass at the start of the shift. Make sure the Metempsychotic machine is linked properly.
|guides=[[Alert Procedure]], [[Standard Operating Procedure|SOP]], [[Company Policy]], [[Medical Doctor]], [[Medical]], [[Chemistry]], [[Cryogenic Pods]]
|aliases="CMO"}}
The Chief Medical Officer (often shortened to Chief or CMO) is the head of the entire medical department. Their access is mostly limited to Medical and Command, they tend to get the wrath of anyone who comes in who thinks they can treat themselves better and they have one of the best items in the game for both killing and saving lives.

Your first task as the CMO is to check if the [[Medical#Cloning_and_Morgue|Metempsychotic machine or cloner]] is linked to the cloning console via multitool. After that, ensure that there's some biomass in it.

CMO is probably the easiest head to play because primarily it's just Medical Doctor Plus. Most of what you do outside the normal medical doctor duties is get the extra biomass from your office loaded into the metempsychotic machine, and then work like a normal doctor. If your team is small or inexperienced in chemistry, you may be [[Chemistry|cooking drugs]] for the first half of the shift. If you don't have someone working triage or intake, you may be doing that.

Another thing the CMO should be doing is catching folks making illegal chemicals or if pills are being spiked, while also keeping in mind what [[Standard Operating Procedure#Medical|Standard Operating Procedure]] reminds you is *not* to be done. Look over your chemist's shoulders and check their machines. Because you can't tell what's going in or out of a machine you don't REALLY know if that pill that was made was Dylovene or Sulfuric Acid for instance. You can grind a pill up in the reagent grinder to test it without just blindly swallowing it. Keep an eye out for telltale signs that someone is trying to make a warcrime. If they have a pile of plasma for no good reason they may be a traitor, or just an inefficient chemist.

== Hypospray and You ==
The hypospray is both a [[Traitor|traitor]] [[High-Risk Items|objective]] and a really good tool for you as a CMO. You can load it with chemicals and immediately put them into a bloodstream. Typically you're going to load this with epinephrine or if you can get your hands on it, ichor.

To load it, take the chemical in one hand and using that hand, click the hypospray. It can hold 30u.

It can also be an exceptionally good way to defend yourself without needing a gun. There's a few good 'offensive' drugs if you're planning on using it in a fight or to subdue an unruly patient.

Nonlethally, dose someone with Ipecac to make them incredibly slow incredibly quickly without doing damage to them. It also has the benefit of reducing their movespeed if they puke enough.

Chloral Hydrate is a favorite amongst many CMOs because even at 25-30 units it won't kill someone, but it will put them down long enough for Sec to get in very, very quickly. Just be sure to give Sec a Dylovene to help with the patient's new toxic damage.

Lethally, epinephrine is a great tool one can use to cause damage that's immediately available at round start. It has the negative of actually providing a lot of benefits to the person if you can't get the full dose off though.

There's Tranexamic acid, also a fairly useful chemical medwise that can double-duty as a an offensive tool if needed. When fully dosed it can do damage fairly quickly as an overdose while being less useful to the enemy you're injecting it with.

Lexorin is by far the most dangerous toxin to someone who doesn't have Dexalin available, but if you're making it and the hypospray falls out of your hands before you can use it, then you're going to have a bad time for the rest of the crew. Lexorin also doesn't fill any particular use for the crew in general other than as a murdering tool.

== Crew Monitoring and You ==
The Crew Monitor, both handheld and built into your office (on most maps) is a vital tool for survival. If your shift is going well, you may even have the luxury of time to monitor the crew on such a monitor outside of folks asking you for it over command chat.

The Crew Monitor gives you updates on where someone is based off their ID and if they have their Suit Coordinates on. As a note, there are people who will NOT put their suit sensors on. These folks cannot be stopped, they will just leave them off the whole round potentially, or even just because they're planning on doing some shenanigans. If someone dies without coords on, there's little you can do usually. Hard to find a body that you don't know the whereabouts of.

{{Jobs Menu}}
[[Category:Jobs]]

Mystagogue

2026-01-30T00:28:40Z

Vape:

{{Job_Header
|department=EPISTEMICS
|command=true
|maincolor=4c1a4f
|secondarycolor=6f2773
|image=Mystagogue.png
|title=Mystagogue
|difficulty=Medium to Hard
|requirements= 25 hours in [[Scientist|Epistemics]], 2 hours as [[Psionic Mantis]]
|access=Epistemics, Command, Maintenance, Mystagogue, Psionic Mantis, Chapel, Cryogenics
|extendedaccess=None
|supervisors=[[Captain]]
|subordinates= [[Scientist]], [[Chaplain]], [[Psionic Mantis]], [[Research Assistant]]
|duties=Coordinate Research and the Epistemics department. Organize the investigation of Artefacts and Anomalies. Observe Glimmer.
|guides=[[Alert Procedure]], [[Standard Operating Procedure|SOP]], [[Company Policy]], [[Research_and_Development|Research]], [[Xenoarcheology]], [[Anomalous Research]], [[Glimmer]], [[Psionics]], [[Golemancy]], [[The Oracle]], [[Reverse Engineering]], [[Robotics]]
|aliases="Mysta"}}
So you're going to be the caretaker of a [[Psionic Mantis|bunch]] of [[Chaplain|fanatic]] [[Scientist|researchers]] with access to some of the most dangerous things on the station!

Alongside your department, you are dedicated to discovering the secrets of the Noösphere and furthering our knowledge of the universe. As such, you will generally find yourself with a great degree of freedom on how you want to accomplish that exploration. Just keep an eye on the glimmer levels.

__TOC__

== Organize Your Cultists ==
The Mystagogue is in charge of the Epistemics department and oversees the duties of [[Research and Development]]. While they will ideally have <s>cultists</s> Scientists under them to aid in research, they are expected to have at least a fundamental understanding of how to operate their department in the event of having a lack of staff. It's very important to understand what is and is not allowed in your department, your department is able to create controlled items that your scientists can get in trouble for even making these include (but are not limited to) All bluespace tech (yes even magic crayons), Jaws of life, and Quantum Switch Inverters.

=== Directing Research ===

As the Mystagogue the bread and butter of your work aboard the station is ensuring research is done. It is your job to lead the broadening of our understanding of the universe around us, discovering new technologies that allow everyone on board to do their jobs better and more efficiently. This may sound like a complicated and scary endeavour but thankfully due to the miracles of modern science, research is now completed through spending "Research Points" on the technology of your choice at the Research Computer. However you do have the option of researching with your research Digi-Board so if your members are not listening to you, disabling the Research Computer and managing research yourself will allow for more control at the cost of efficiency.

[[Scientist|Scientists]] will be your primary subordinates. They will be working with [[Xenoarcheology|analysing artefacts]], [[Anomalous Research|dealing with anomalies]] or [[The Oracle|requisitioning things for the oracle]]. You may want to ensure that all these jobs are manned by assigning your scientists roles at the start of the shift but usually they can be flexible if they know what they are doing.

Don't forget to check on the Scientists every now and then to ensure they are doing their jobs. If there's not much to do, direct them around the station in search of whatever object [[the Oracle]] demands of you.

Make sure that the [[Psionic Mantis]] is available and alive for emergencies. They will be invaluable for making a record of the station's [[psionics]] for when Code White may run around. However it's important to keep them in check for if they start mindbreaking people that is like a serious felony and thats seriously not great.

The [[Chaplain]] has the habit of trying to build a cult. If this cult becomes violent or disrespectful to other people's beliefs its recomended that you do something about it and call security if it becomes extreme.

Research Points can be obtained from the following sources:
* Passive generation from Glimmer Probers
* Completing quests for the Oracle
* Destroying alien artifacts after researching their properties
* The discovery of new diseases by the Medical staff
* Analyzing Anomalies

=== Your Defence ===
At the start of each shift, the Mystagogue is one of the more vulnerable heads of staff on board. Unlike the other heads, you don't get fancy defence capabilities but you get a cool Hand Teleporter. Keep it safe and don't lose it.

As Mystagogue, you also have access to a Book of Mysteries. This mystical book contains many secrets, and can allow you to make a mystical wall only passable by you. so make sure to thoroughly investigate its wonders if you find it strapped to you! To deal with supernatural beings such as Wisps or [[Revenant|Revenants]] you get the Dispel [[Psionics|psionic ability]]. It can also be used against anomalies however it takes about two shots with dispel so using dispel with a CHIMP or APE would be a good idea.

== Communication ==
Communicate and cooperate with other departments if Anomalies or Artefacts appear on the station that need investigation or dispelment. You, and your team, are not able to be everywhere all at once. Remember to, once in a while, advertise for the crew to call out locations of anomalies if they see one.

You will also be the person in charge of managing the [[glimmer]] and the [[Construction|constructions]] of probers and drainers. If glimmer gets too high you are allowed to call [[Alert_Procedure#White_Alert|White Alert]] to incite people to stop using their psionic powers and get mindbroken if needed

== Glimmer and You ==

Glimmer is a measurement of the average noöspheric pressure. The noösphere is a field linking the minds of all sentient beings. The study of Glimmer is what separates you from the puny minded ingrates known as scientists on other stations. Delving into the noösphere using your Glimmer Probers is a gateway to great knowledge and how you will gain perform much of your initial research.

You will be the person in charge of managing the [[glimmer]] and the [[Construction|constructions]] of probers and drainers. If glimmer gets too high (past 500Ψ or 400Ψ if things are getting out of control) you are allowed to call [[Alert_Procedure#White_Alert|White Alert]] to incite people to get mindbroken so they stop using their psionic powers.

As your probers do their work, the average glimmer level on the station will rise. If the level grows past 500Ψ the probers themselves will begin to spark with latent psionic energy and you may find yourself unable to turn them off as they become self sustaining.

In cases of emergencies like this, you are recommended to build Glimmer [[Glimmer#Drainers|Drainers]]. You need ectoplasm from this which can be found in higher amounts due to glimmer mites, revenants, and glimmer wisps spawning pretty rapidly when glimmer exceeds 500Ψ. However <s>Bribing</s> asking a Botanist to make some Cosmic Revenants at the start of a shift is a good idea as they get a good source of ectoplasm when ground up.

{{Jobs Menu}}
[[Category:Jobs]]

Chief Engineer

2026-01-30T00:28:22Z

Vape:

{{Stub}}
{{Job_Header
|department=ENGINEERING
|command=true
|maincolor=854100
|secondarycolor=a75200
|image=Chief Engineer.png
|title=Chief Engineer
|difficulty=Hard
|requirements= 30 hours in [[Station Engineer|Engineering]], 20 hours as [[Atmospheric Technician]]
|access=Maintenance, Engineering, Command, External, Chief Engineer, Atmospherics, Cryogenics
|extendedaccess=None
|supervisors=[[Captain]]
|subordinates=[[Station Engineer]], [[Atmospheric Technician]], [[Technical Assistant]]
|duties=Coordinate engineering, ensure equipment doesn't get stolen. Maintain and fix the station.
|guides=[[Alert Procedure]], [[Standard Operating Procedure|SOP]], [[Company Policy]], [[Construction|Guide to Construction]], [[Power|Guide to Power]], [[Atmospheric Technician|Guide to Atmospherics]], [[Reverse Engineering]]
|aliases="CE", "Chief Engi"}}
You are the head of the Engineering Department, which includes not only [[Station Engineer|Station Engineers]], but [[Atmospheric Technician|Atmospheric Technicians]] as well. Essentially, your job is to boss your staff around and make sure the power and air flows.

You are expected to do everything you except from your average Engineer and Atmos Technician (''if you haven't completely blanked out on that part of the training''). You also will handle more sensitive matters such as but not limited to fixing sensible areas such as Bridge, the Vault, other heads offices. Your special tool belt gives you the Jaws of life, Drill, Experimental welder, a full stack of LV cables, and a Multitool.

In your locker you can find even more useful gear such as Advanced Magboots, CE hardsuit, Oxygen Canister, Engineer door Controls, CE stamp, breath mask, insulated gloves, and a jetpack that can fit in your suit storage.

====Delegation====
It is VERY easy for CE to go fix everything. You have the best tools, move the fastest, and you have great boots that don't slow you down. Don't be the only person to respond to issues. Your engineering team is here to help you. Issue with atmospherics? Send an Atmos Tech to go bring a scrubber on it. Power outage? Have your engineering team respond to it.

Be a leader, not a boss. Lead your crew in repairs, but let them do it. Don't just take everything onto your shoulders.

At the start of the shift, it's very likely that you may have gaps in your department or [[Technical Assistant|new guys]] in your department. Make sure you can pick up the slack in the meantime for those departments and spend some time teaching the FNG before they walk into a spaced area.

{{Jobs Menu}}
[[Category:Jobs]]

Medical

2026-01-29T09:40:27Z

Vape: Minor updates

== Starting your shift ==
Medbay often starts out calm, but you'd best prepare for the storm that's about to come. You'll either get blown up by some syndicate agent wanting the hypospray or you'll get so inundated with bodies and people screaming in your ear for you to treat them faster that you'll blow medbay up yourself.

Coordinate with the [[Chemist|Chemists]]. Give them a list of drugs you'll need to treat your patients. Try and cover all the common damage types so that you will be prepared for anything the shift throws at you.

It's generally good practice to keep your chemicals in a locker pretty centrally located in the medbay for ease of access. Remember to lock it once you're done to keep them safe and restricted to medical staff access.

It's optional but bringing a [[Medical_Doctor#Tools|health analyzer]] out to the front of medbay for patients to come and scan their damage without pestering you can be beneficial.

If there is no Crew Monitor Computer out in medical's public area, ask the [[Chief_Medical_Officer|CMO]] to bring it out from their office. When you have the time, you can check the Crew Monitor for anyone dead or dying. If they have their suit sensors set to display coordinates a [[Paramedic]] may use those to potentially locate their body for recovery. A GPS and Handheld Crew Monitor devices can help you locate dead bodies.

== Types Of Damage ==
In SS14, damage is a value representing how much injuries a character has suffered. It can be checked using a [[Medical_Doctor#Tools|health analyzer]] or your PDA. If it's 0, it means there are no wounds or injuries. There are 7 categories of damage: {{DMG|Brute}}, {{DMG|Burn}}, {{DMG|Airloss}}, {{DMG|Toxin}}, {{DMG|Genetic}}, Shadow, and Holy. Each of them has a different treatment, although some chemicals, like [[Chemistry#Tricordrazine|Tricordrazine]], can treat multiple types of damage.

''Refer to [[Medical#Chemical_Reference_Table|Treatments Table]] for all treatments.''

=== Brute Damage ===
There are three types of Brute damage: {{DMG|Blunt}}, {{DMG|Slash}}, {{DMG|Piercing}}. All types of Brute damage can be healed used using [[Chemistry#Bicaridine|Bicaridine]], which heals 4 {{DMG|Brute}} per unit. The overdose amount is 15u. You can also use advanced chemicals to treat only one kind of Brute damage at once, but more effectively. It's especially useful when a patient comes in with only one type of damage. These chemicals are:
* [[Chemistry#Bruizine|Bruizine]] - Healing {{DMG|Blunt|+|3.5}} wih max dose of 10.5u.
* [[Chemistry#Lacerinol|Lacerinol]] - Healing {{DMG|Slash|+|3}} with max dose of 12u.
* [[Chemistry#Puncturase|Puncturase]] - Healing {{DMG|Piercing|+|4}} but dealing {{DMG|Blunt|-|0.1}} with max dose of 11u.

'''Make sure to not mix any of the advanced brute meds with Bicaridine or with each other.'''

The mixing of these chemicals creates [[Chemistry#Razorium|Razorium]], a damaging chemical that causes {{DMG|Slash|-|9}} a unit.

When a patient is presenting with less than 25 damage, you might want to use [[Medical_Doctor#Tools|Bruise Packs]] or [[Medical_Doctor#Tools|Medicated Sutures]] to heal them. You can find these inside of your toolbelt or First Aid Kits.

=== Burn Damage ===
There are four types of Burn damage: {{DMG|Heat}}, {{DMG|Shock}}, {{DMG|Cold}} and {{DMG|Caustic}}. All of them except {{DMG|Caustic}} can be healed using [[Chemistry#Dermaline|Dermaline]], which heals {{DMG|Heat|+|1.5}}, {{DMG|Shock|+|1.5}}, {{DMG|Cold|+|1.5}} and has a max dose of 10u. The advanced burn chemicals, similar to the brute ones, heal one type of burn damage at a time in a much more effective manor. They are the following:
* [[Chemistry#Siderlac|Siderlac]] - Healing {{DMG|Caustic|+|5}}.
* [[Chemistry#Sigynate|Sigynate]] - Healing {{DMG|Caustic|+|3}} with a max dose of 16u.
* [[Chemistry#Leporazine|Leporazine]] - Healing {{DMG|Cold|+|4}} with a max dose of 12u.
* [[Chemistry#Siderlac|Pyrazine]] - Healing {{DMG|Heat|+|10}} over a slow period with a max dose of 20u.
* [[Chemistry#Insuzine|Insuzine]] - Healing {{DMG|Shock|+|4}} with a max dose of 12u.
'''Make sure to not mix any of the advanced burn meds with Dermaline, or with each other.'''

Mixing these chemicals creates a poison called [[Chemistry#Licoxide|Licoxide]], which deals {{DMG|Shock|-|4}}.

Again, when a patient is presenting with less than 25 Burn damage, you can use [[Medical_Doctor#Tools|Ointments]] or [[Medical_Doctor#Tools|Regenerative Meshes]] to heal them.

=== Airloss Damage ===
Before reading anything else: if someone is on the ground gasping, you should first use an emergency medipen on them if no one else already has yet, and then move them to a stasis bed if there are any available. This will give you time to prepare a more specific treatment. Next check that their internals are off (if theres air in medbay) or on (if theres no air in medbay). You do this by their right click menu.

When it comes to Asphyxiation, [[Chemistry#Epinephrine|Epinephrine]], [[Chemistry#Inaprovaline|Inaprovaline]], [[Chemistry#Dexalin|Dexalin]], [[Chemistry#Convermol|Convermol]], and [[Chemistry#Salbutamol|Salbutamol]] are all effective at treating it, but your go-to chemicals will be Convermol or Salbutamol. Convermol heals {{DMG|Asphyxiation|+|10}} and {{DMG|Bloodloss|+|4}}, but also does {{DMG|Blunt|-|4}} whereas Salbutamol heals {{DMG|Airloss|+|6}} when damage is above 30 but drops to {{DMG|Airloss|+|1}} when below 30.

Another kind of Airloss damage is {{DMG|Bloodloss}}. Everyone has a volume of blood inside them. When you take damage, slash and pierce most importantly, you will lose blood. You may also start noticeably bleeding, which continually drains your blood. If your blood level falls below a certain threshold, you will begin taking bloodloss damage and you will continue to do so until your blood levels return to normal. When you lose enough blood, you will start seeing double.

If someone is bleeding heavily there are 3 things to do:
* Stop the bleeding
* Restore blood levels
* Cure bloodloss damage

To stop bleeding (to stop blood levels from dropping continuously), you should use gauze or [[Chemistry#Tranexamic_acid|Tranexamic acid]]. Gauze is very effective, easy to make, and completely stops bleeding after a short doafter bar. All you need is some cloth inside the medical lathe which should be in the back areas of medical.

[[Chemistry#Inaprovaline|Inaprovaline]] and [[Chemistry#Pulped_banana_peel|Pulped banana peel]] also reduce bleeding but [[Chemistry#Tranexamic_acid|Tranexamic acid]] is 3 times more powerful than pulped banana peel and 6 times more powerful than Inaprovaline. It should be noted that emergency medipens contain a small amount of [[Chemistry#Tranexamic_acid|Tranexamic acid]] (3u). Note that if you Examine a patient and it says they are covered in Lacerations, that means they are bleeding.

If you have only a few patients with intense bleeding, move them to a stasis bed first to give you time to prepare a treatment.

To restore blood level (stop double vision and stop continuous bloodloss damage), you can use [[Chemistry#Saline|Saline]] or Blood packs which restores 15units of blood per use. You can also use [[Chemistry#Iron|Iron]] or [[Chemistry#Copper|Copper]] depending on the species of your patient.

Patients will recover blood levels on their own once their bleeding has stopped, however the rate at which they do so is abysmally low. You can view the patient's blood level in the top part of your Health Analyzer interface. It's showed there as precentage.

Your patient may have enough bloodloss damage at any point in treatment to warrant curing the damage. To do so, you will want to apply [[Chemistry#Salbutamol|Salbutamol]] or [[Chemistry#Convertamol|Convertamol]] to cure the bloodloss damage. Patients who are no longer low on blood will slowly recover from bloodloss damage on their own without medication.

Do not simply cure the patient of their bloodloss damage and send them on their way. They may appear to be cured on your health analyzer, but if their bleeding has not been stopped and their blood levels restored to normal, they will be back in med bay to be treated again soon.

=== Toxin Damage ===
There are two types of Toxin damage, both treated with different medications.

The one you'll come across the most is {{DMG|Poison}} damage. Seriously, you'd be surprised by how many people present with alcohol poisoning every shift. The first med you can use for healing {{DMG|Poison}} is [[Chemistry#Dylovene|Dylovene]], you're likely to see it at the start of your shift. It heals {{DMG|Poison|+|1}} per unit with a max dose of 20u. The far superior med is [[Chemistry#Diphenhydramine|Diphenhydramine]], as it heals {{DMG|Poison|+|3}} and has no overdose but it does have a side effect of drowsiness

The next kind of Toxin is {{DMG|Radiation}} damage. You will most likely see [[Salvage_Specialist|Salvage Specialists]] presenting with this kind of damage. It can be treated with [[Chemistry#Arithrazine|Arithrazine]], which heals {{DMG|Radiation|+|3}} per unit. You need to watch out, because it also deals {{DMG|Brute|-|0.5}}. You can usually solve this issue with [[Medical_Doctor#Tools|Bruise Pack]] or [[Chemistry#Bicaridine|Bicaridine]].

=== Vision ===
A loss of eye sight will not appear on the Health Analyzer. If a user has been using a Welding Torch without a Welding Mask, they may be unable to see very far. You can treat it using [[Chemistry#Oculine|Oculine]]

=== Jittering ===
A patient may be jittering (shaking) due to an overdose. A bed rest or simply time can help here. To rapidly flush jittering, you can administer a dose of [[Chemistry#Diphenhydramine|Diphenhydramine]].

=== Allergic Reaction ===
An allergic reaction (e.g. to bees) can cause a build up of [[Chemistry#Histamine|Histamine]]. A dose of [[Chemistry#Diphenhydramine|Diphenhydramine]] or [[Chemistry#Ultravasculine|Ultravasculine]] can help flush it.

=== Hallucinations ===
A patient may see swirly illusions after taking a hallucinogenic such as Space Drugs. A bed rest or simply time can help here. 1u of [[Chemistry#Synaptizine|Synaptizine]] can assist here (via a Dropper). More than 1u can be lethal.

=== Ethanol Poisoning ===
A patient may feel the effects of ingesting too much alcohol. A bed rest or simply time can help here. [[Chemistry#Ethylredoxrazine|Ethylredoxrazine]] can also be used to treat the effeects.

== Cryogenics ==
''Main article: [[Cryogenic_Pods|Cryogenic Pods]]''

Cryogenic Pods, also called cryo pods or cryopods, are a special type of medical machinery used in conjuction with specific chemical solutions. The machine itself can be thought of a simple gas chamber a patient can be placed in, with specific protection to prevent cold gases from damaging patients. It also offers a slot for a beaker or similar, to automatically inject the patient with a solution, slowly over the course of time. Cryo pods need a properly built atmospherics setup to work.
<div style="display: flex; flex-flow: row wrap; justify-content: center; gap: 0.5em">
{{Chembox|prototype=Cryoxadone}}
</div>

== Administering Medication ==
There are multiple ways to administer medicine to the patients.
* Liquid + Syringe - This is the most common way of giving chemicals to patients. You can find labeled jugs with medicine usually near the beds area of the Medbay. Each one holds 200u of liquid. You can use a syringe to draw or inject chemicals. By right clicking a syringe, you can change the amount of liquid you want to transfer - 5u, 10u or 15u. By left clicking it in your hand or clicking Z, you can change the mode between Drawing and Injecting.
* Liquid + Interact - A doctor can hold a container of liquid (e.g. a beaker, jug, can, bottle) and interact with a patient to force them to sip 5u of the liquid. Force feeding is slower than if the patient drinks the liquid themselves. Liquids cannot be ingested by some species (such as Moth). Drinking requires the face to be uncovered (except for certain masks like the clown mask). A doctor can Strip off a Helmet and Breathe Mask in order to achieve this. Drinking does nothing on dead bodies except if it is ingested right before the Defibrillator.
* Pill - A [[Chemist]] can create pills and some Medpacks also have pills therein. Pills will often be labelled with the chemical and amount of units. Unfortunately pills can also be mislabelled. Mislabelled pills can be grinded by a Grinder to revert to a liquid. Pills contain higher volumes of medication than a syringe. Pills cannot be ingested by some species (such as Moth). Pills require the face to be uncovered (except for certain masks like the clown mask). A doctor can Strip off a Helmet and Breathe Mask in order to achieve this. Pills do nothing on dead bodies except if they are ingested right before the Defibrillator.
* Apply a Pack - Some treatments can be applied topically to the body. This can be performed on dead bodies, moths and patients wearing a helmet. Examples of topical treatment are: Bruise Packs, Ointment, Gauze, Aloe Cream, etc.

== Stabilizing Critical Patients ==
When a character suffers more than 100 damage, they will go into a Critical condition, indicated by the character passing out on the floor and starting to gasp for air. While crit, they won't be able to move, speak or interact with the world. They will also start gaining Asphyxiation. Once they reach 200 total damage, they will die, indicated by the text "... siezes up, his eyes dead and lifeless".

Patients are often dragged in gasping for air in a Critical state. In the medbay, the go-to chemical for healing {{DMG|Airloss}} is [[Chemistry#Dexalin_plus|Dexalin Plus]], which heals {{DMG|Airloss|+|13}}. While you're in field, the usual best option is to inject an emergency medipen into the patient to stabilize them, which has the effect of healing a bit of damage and {{DMG|Asphyxiation|+|6}}. Everyone starts with an emergency medipen inside their survival box, which contains 12u of [[Chemistry#Epinephrine|Epinephrine]] and 3u of [[Chemistry#Tranxemic_acid|Tranexamic Acid]]. Medical doctors also have one medipen on their medical belt. If you run out, there are also bottles of [[Chemistry#Epinephrine|Epinephrine]] inside the NanoMed.

If you don't have [[Chemistry#Epinephrine|Epinephrine]] or [[Chemistry#Dexalin_plus|Dexalin Plus]] then [[Chemistry#Inaprovaline|Inaprovaline]] can also be useful, to a lesser degree. Once you administer a chemical to deal with the {{DMG|Airloss}}, you can move on to healing other types of damage. If you notice {{DMG|Asphyxiation}} going up again, you can give the patient another dose of preferably [[Chemistry#Dexalin_plus|Dexalin Plus]].

Putting critical patients on a Stasis Bed will make them die 10 times slower, giving you more time to do other things. Remember that it also makes all chemicals metabolize slower, including medicine. Medical beds and roller also help a little. To do this, drag the patient onto an empty bed (do not Pull them onto the bed but instead left click them, drag and release them onto the bed).

== Dead Body Analysis ==
If someone dies in your care or is brought to you as a corpse, you need to decide what action to take:

First verify that the body has a soul. The best and simplest way to do this is {{key press|Shift}} + left click.

[[File:BodyDead.png|thumb]]If you see text in red stating "They are dead.", this means that this person is still viable for cloning or revival. If they get cloned, the old body will display the unclonable text shown below, and can be disposed of (after the person has gathered all their things off of it).
 
[[File:BodyDeadSSD.png|thumb]]
If instead you see text in yellow stating "Their soul lies dormant and may return soon.", then this person is still cloneable but have left the server. You might want to keep them in the morgue until their soul returns or just clone them and hope for them to come back.
 
[[File:BodyDeadIrrecoverable.png|thumb]]If instead you see text in purple stating "Their soul has departed and moved on. Any recovery is unlikely.", then this person is gone. They've either left the server, or they've taken a ghost role, such as a drone or monkey, and thus forfeited the right to come back to their body. That or they've just been cloned. Toss this body in the morgue.
 

=== Reviving ===
Dead people can be brought back using a Defibrillator, but only if they have less than 200 total damage (Not counting {{DMG|Asphyxiation}}) and they aren't rotting. You can use a Health Analyzer to check how much damage the body took before death. If the damage is excessive or non-curable with topical treatments, cloning may be the only option. Chemicals do not metabolize in the dead, but you can reduce the damage by using [[Medical_Doctor#Tools|Bruise Packs, Ointments, Sutures, Meshes, Gauzes and Bloodpacks]]. Once you get them below 200 damage, you can use a Defibrillator to bring them back to life. You can often find them free-standing or in a cabinet. It is batter-operated and must be turned on before you can use it. Each time the Defibrillator is used, its battery charge will go down. Eventually, you will need to recharge it. To do that, you need to first eject the battery cell and put it in a reacharger. It can be also found in Medical.

{| class="wikitable" style="margin:auto"
|+ Dead Body Treatment
|-
! Symptoms !! Analysis !! Treatment Steps
|-
| 200+ Airloss || Revivable || Defibrillator
|-
| 100 Airloss and 100 Brute || Revivable || 2 Bruise packs followed by a Defibrillator followed by normal treatment (e.g. Bicaridine)
|-
| 200 Brute || Revivable || Brute packs until ~95 brute followed by a Defibrillator followed by normal treatment (e.g. Bicaridine)
|-
| 200 Burn || Revivable || Ointment or Aloe Cream until ~95 burn followed by a Defibrillator followed by normal treatment (e.g. Dermaaline)
|-
| 200 Poison or Radiation || Clone || Note that an advanced doctor may inject them with Anti-Toxin and then Defib and repeat this process but it will be a challenging revival.
|-
| 200+ Brute || Clone || Check Medical stockpiles of Bruise Packs before attempting revival. Cloning may be more viable.
|-
| 200+ Burn || Clone || Check Medical stockpiles of Ointment and Aloe Cream before attempting revival. Aloe Cream is a renewable resource from Botany. Cloning may be more viable if stockpiles are poor or Botany is non-responsive.
|}

=== Cloning ===
To clone, first the cloning system needs to be set up.

Make sure that the metempsychotic machine (or cloner) and medical scanner are linked to the Cloning Console via multitool. After that, ensure that there's enough biomass (from the Biomass Reclaimer). When you wish to clone them, place their body in the medical scanner and clone from the console.

<big>'''Metempsychotic Machine'''</big> 
[[File:MetempsychoticMachine.png|64px]]

This is the machine every station starts with.

This machine doesn't clone you but transfer your soul into a new body. It costs 30 biomass on the first transfer and there is a 100% chance for you to end up in an humanoid body (with a low chance of it being your own body. For every consecutive metempsychoses, the price goes up by 5 biomass and the chances of ending up in a humanoid body goes down by 25%. Upgrades can affect each.

<big>'''Cloning Machine'''</big> 
[[File:Cloner.png|64px]]

The original cloner. It can be found in salvages wrecks.

Larger species require more biomass to clone. You can inspect the body's damage before deciding whether to clone. Each point of genetic damage increases the chance cloning will fail by 1%.

After cloning, be sure to process their old body in the reclaimer to get some biomass back. Make sure you've given them an opportunity to get their things (as long as they didn't die of infectious disease.)

<big>'''Medical Scanner'''</big> 
[[File:MedicalScanner.png|64px]]

The medical scanner is where you put clone-able bodies into before interacting with the body scanner to press the clone button.
 

=== Morgue ===
Meant for long-term storage of dead bodies. This is where you find a bunch of morgue storage pods where you can store dead people.

It is recommended to only store people with souls in there if the cloning bay is overflowing, you can't clone due to low biomass or it is currently inoperable.

Storing dead bodies is very useful to prevent the body from rotting (which prevents revival and cloning).

To use the Morgue, interact with a Storage Pod to open the tray, drag a body onto the tray, then interact with the Pod to close the tray. Typically you'll want only one body per Storage Pod.

Here's a quick morgue color code.

{| class="wikitable" style="text-align: left;vertical-align: center;"
! Sprite !! Meaning
|-
| [[File:MorgueEmpty.png]]
| There is nothing inside the tray.
|-
| [[File:MorgueBodySoulless.png]]
| There is a body but the player isn't in the body. The state of the spirit is unknown as the player could be waiting around the body or left already. You need to pull out the body and check it manually.
|-
| [[File:MorgueBody.png]]
| The body has a spirit inside of it, and is revive-able. It will be beeping too.
|-
| [[File:MorgueObject.png]]
| There is something inside the tray, but it's not a body.
|}

<big>'''Biomass Reclaimer'''</big> 
[[File:BiomassReclaimer.png|64px]]

Every morgue comes with a very important piece of equipment, the Biomass Reclaimer. It is fairly straightforward, put a dead body in it, it grinds them into biomass. Be careful not to grind down clone-able body if you are not an [[Antagonist]] as it could get you in trouble [[Roleplay#In_Character|IC]] and [[Roleplay#Out_of_Character|OOC]].

If you attempt to drag a living creature into the Biomass Reclaimer, it may throw the creature across the room.

The amount of Biomass generated depends on the type of creature.

If you get low on Biomass, contact Salvage and/or Cargo and ask for their help.

== Crew Monitoring Console ==
A Crew Monitoring Console usually can be found in the public area of the Medbay or inside the CMO's office. It also comes in a handheld version distributed to the [[Chief_Medical_Officer|Chief Medical Officer]] and the [[Paramedic|Paramedics]].

It can be used to find other crewmembers, provided they have suit sensors enabled. The four settings on suit sensors are:
* Off - The person doesn't show up in the console.
* Binary - The person shows up as either ALIVE or DEAD.
* Vitals - The person will show up with their current health condition.
* Coordinates - The person can be found on the interactive station map.

If someone has their Coordinates on, they can be easily found and retrived by [[Paramedic|Paramedics]]. If someone dies without coords on, there's little you can do usually. It's recommended for all crew to have their suit sensors on.

== Chemical Reference Table ==
{| class="wikitable" 
! Damage
! Treatment
|-
! Brute
| '''Bruise Pack'''
----
'''Medicated Suture'''
----
'''[[Chemistry#Bicaridine|Bicaridine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|32px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]])
----
'''[[Chemistry#Bruizine|Bruizine (Blunt)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Bicaridine|Bicaridine]]([[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|8px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|8px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|8px]]1 part [[Chemistry#Carbon|Carbon]])) [[File:Beaker.png|32px]]0.9 part [[Chemistry#Lithium|Lithium]] [[File:Beaker.png|32px]]1 part [[Chemistry#Sugar|Sugar]]
----
'''[[Chemistry#Lacerinol|Lacerinol (Slash)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Bicaridine|Bicaridine]]([[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|8px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|8px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|8px]]1 part [[Chemistry#Carbon|Carbon]])) [[File:Beaker.png|32px]]1 part [[Chemistry#Benzene|Benzene]]([[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]] @ 310K)
----
'''[[Chemistry#Puncturase|Puncturase (Piercing)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Bicaridine|Bicaridine]]([[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|8px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|8px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|8px]]1 part [[Chemistry#Carbon|Carbon]])) [[File:Beaker.png|32px]]1 part [[Chemistry#Hydroxide|Hydroxide]]([[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] @ 310K)
----
'''[[Chemistry#Tricordrazine|Tricordrazine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Dylovene|Dylovene]]([[File:Beaker.png|16px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]])
|-
! Burn
| '''Ointment'''
----
'''Regenerative Mesh'''
----
'''[[Chemistry#Siderlac|Siderlac (Caustic)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Stellibinin|Stellibinin]] [[File:Beaker.png|32px]]1 part [[Chemistry#Aloe|Aloe]]
----
'''[[Chemistry#Sigynate|Sigynate (Caustic)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Sodium_carbonate|Sodium Carbonate]]([[File:Beaker.png|16px]]1 part [[Chemistry#Ammonia|Ammonia]]([[File:Beaker.png|8px]]3 part [[Chemistry#Hydrogen|Hydrogen]][[File:Beaker.png|8px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|16px]]1 part [[Chemistry#Table_salt|Table Salt]]([[File:Beaker.png|8px]]1 part [[Chemistry#Chlorine|Chlorine]][[File:Beaker.png|8px]]1 part [[Chemistry#Sodium|Sodium]] @ 370K) [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Sodium_hydroxide|Sodium Hydroxide]]([[File:Beaker.png|16px]]1 part [[Chemistry#Hydroxide|Hydroxide]]([[File:Beaker.png|8px]]1 part [[Chemistry#Hydrogen|Hydrogen]] [[File:Beaker.png|8px]]1 part [[Chemistry#Oxygen|Oxygen]] @ 310K)[[File:Beaker.png|16px]]1 part [[Chemistry#Sodium|Sodium]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Kelotane|Kelotane]]([[File:Beaker.png|8px]]1 part [[Chemistry#Silicon|Silicon]][[File:Beaker.png|8px]]1 part [[Chemistry#Carbon|Carbon]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Water|Water]] [[File:Beaker.png|32px]]1 part [[Chemistry#Sugar|Sugar]]
----
'''[[Chemistry#Insuzine|Insuzine (Shock)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Leporazine|Leporazine]]([[File:Beaker.png|16px]]1 part [[Chemistry#Copper|Copper]][[File:Beaker.png|16px]]1 part [[Chemistry#Fersilicite|Fersilicite]]([[File:Beaker.png|8px]]1 part [[Chemistry#Iron|Iron]][[File:Beaker.png|8px]]1 part [[Chemistry#Silicon|Silicon]] @ 310K))[[File:Beaker.png|16px]]1 part [[Chemistry#Plasma|Plasma]](catalyst)) [[File:Beaker.png|32px]]1 part [[Chemistry#Kelotane|Kelotane]]([[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]][[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|32px]]1 part [[Chemistry#Benzene|Benzene]]([[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]][[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]])
----
'''[[Chemistry#Pyrazine|Pyrazine (Heat)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Leporazine|Leporazine]]([[File:Beaker.png|16px]]1 part [[Chemistry#Copper|Copper]][[File:Beaker.png|16px]]1 part [[Chemistry#Fersilicite|Fersilicite]]([[File:Beaker.png|8px]]1 part [[Chemistry#Iron|Iron]][[File:Beaker.png|8px]]1 part [[Chemistry#Silicon|Silicon]] @ 310K))[[File:Beaker.png|16px]]1 part [[Chemistry#Plasma|Plasma]](catalyst)) [[File:Beaker.png|32px]]1 part [[Chemistry#Dermaline|Dermaline]]([[File:Beaker.png|16px]]1 part [[Chemistry#Kelotane|Kelotane]]([[File:Beaker.png|8px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|8px]]1 part [[Chemistry#Carbon|Carbon]])[[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]][[File:Beaker.png|16px]]1 part [[Chemistry#Phosphorus|Phosphorus]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]]
----
'''[[Chemistry#Leporazine|Leporazine (Cold)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Copper|Copper]][[File:Beaker.png|32px]]1 part [[Chemistry#Fersilicite|Fersilicite]]([[File:Beaker.png|16px]]1 part [[Chemistry#Iron|Iron]][[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]] @ 310K)[[File:Beaker.png|32px]]1 part [[Chemistry#Plasma|Plasma]](catalyst))
----
'''[[Chemistry#Kelotane|Kelotane]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]]
----
'''[[Chemistry#Dermaline|Dermaline]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Kelotane|Kelotane]]([[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|32px]]1 part [[Chemistry#Phosphorus|Phosphorus]]
----
'''[[Chemistry#Tricordrazine|Tricordrazine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Dylovene|Dylovene]]([[File:Beaker.png|16px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]])
|-
! Airloss
| '''[[Chemistry#Dexalin|Dexalin]]''' [[File:Beaker.png|32px]]2 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|32px]]1 part [[Chemistry#Plasma|Plasma]](catalyst)
----
'''[[Chemistry#Dexalin Plus|Dexalin plus]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Dexalin|Dexalin]]([[File:Beaker.png|16px]]2 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Plasma|Plasma]](catalyst)) [[File:Beaker.png|32px]]1 part [[Chemistry#Iron|Iron]] [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]]
----
'''[[Chemistry#Epinephrine|Epinephrine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Phenol|Phenol]]([[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Acetone|Acetone]]([[File:Beaker.png|16px]]1 part [[Chemistry#Oil|Oil]]([[File:Beaker.png|8px]]1 part [[Chemistry#Welding_fuel|Welding Fuel]] [[File:Beaker.png|8px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|8px]]1 part [[Chemistry#Hydrogen|Hydrogen]]) [[File:Beaker.png|16px]]1 part [[Chemistry#Welding_fuel|Welding Fuel]] [[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Chlorine|Chlorine]] [[File:Beaker.png|32px]]1 part [[Chemistry#Hydroxide|Hydroxide]]([[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] @ 310K)
----
'''[[Chemistry#Inaprovaline|Inaprovaline]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|32px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]]
|-
! Toxin
| '''[[Chemistry#Dylovene|Dylovene]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|32px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|32px]]1 part [[Chemistry#Nitrogen|Nitrogen]]
----
'''[[Chemistry#Ultravasculine|Ultravasculine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Plasma|Plasma]] [[File:Beaker.png|32px]]2 part [[Chemistry#Histamine|Histamine]]
----
'''[[Chemistry#Arithrazine|Arithrazine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Hyronalin|Hyronalin]]([[File:Beaker.png|16px]]1 part [[Chemistry#Dylovene|Dylovene]]([[File:Beaker.png|8px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|8px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|8px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|16px]]1 part [[Chemistry#Radium|Radium]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Hydrogen|Hydrogen]]
----
'''[[Chemistry#Hyronalin|Hyronalin]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Dylovene|Dylovene]]([[File:Beaker.png|16px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Radium|Radium]]
----
'''[[Chemistry#Diphenhydramine|Diphenhydramine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Diethylamine|Diethylamine]]([[File:Beaker.png|16px]]1 part [[Chemistry#Ammonia|Ammonia]]([[File:Beaker.png|8px]]3 part [[Chemistry#Hydrogen|Hydrogen]][[File:Beaker.png|8px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|16px]]1 part [[Chemistry#Ethanol|Ethanol]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Oil|Oil]]([[File:Beaker.png|16px]]1 part [[Chemistry#Welding_fuel|Welding Fuel]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Table_salt|Table Salt]]([[File:Beaker.png|16px]]1 part [[Chemistry#Chlorine|Chlorine]] [[File:Beaker.png|16px]]1 part [[Chemistry#Sodium|Sodium]] @ 370K) [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]] [[File:Beaker.png|32px]]1 part [[Chemistry#Ethanol|Ethanol]]
----
'''[[Chemistry#Stellibinin|Stellibinin]]'''
|-
! Genetic
| '''[[Chemistry#Phalanximine|Phalanximine]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Unstable_mutagen|Unstable Mutagen]]([[File:Beaker.png|16px]]1 part [[Chemistry#Chlorine|Chlorine]] [[File:Beaker.png|16px]]1 part [[Chemistry#Phosphorus|Phosphorus]] [[File:Beaker.png|16px]]1 part [[Chemistry#Radium|Radium]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Hyronalin|Hyronalin]]([[File:Beaker.png|16px]]1 part [[Chemistry#Dylovene|Dylovene]]([[File:Beaker.png|8px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|8px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|8px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|16px]]1 part [[Chemistry#Radium|Radium]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Ethanol|Ethanol]]
----
'''[[Chemistry#Doxarubixadone|Doxarubixadone (Cryo)]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Cryoxadone|Cryoxadone]]([[File:Beaker.png|16px]]1 part [[Chemistry#Dexalin|Dexalin]]([[File:Beaker.png|8px]]2 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|8px]]1 part [[Chemistry#Plasma|Plasma]](catalyst)) [[File:Beaker.png|16px]]1 part [[Chemistry#Water|Water]] [[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Unstable_mutagen|Unstable Mutagen]]([[File:Beaker.png|16px]]1 part [[Chemistry#Chlorine|Chlorine]] [[File:Beaker.png|16px]]1 part [[Chemistry#Phosphorus|Phosphorus]] [[File:Beaker.png|16px]]1 part [[Chemistry#Radium|Radium]])
|-
! Bleeding
| '''Medicated Suture'''
----
'''Gauze'''
----
'''Cloth'''
----
'''Blood pack''' (restores blood levels)
----
'''[[Chemistry#Iron|Iron]]''' (restores blood levels, toxic to arachnids)
----
'''[[Chemistry#Copper|Copper]]''' (restores blood levels, toxic to non-arachnids)'''
----
'''[[Chemistry#Saline|Saline]]'''
----
'''[[Chemistry#Pulped Banana Peel|Pulped Banana Peel]]'''
----
'''[[Chemistry#Inaprovaline|Inaprovaline]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|32px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|32px]]1 part [[Chemistry#Carbon|Carbon]]
----
'''[[Chemistry#Tranexamic acid|Tranexamic acid]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Sulfuric_acid|Sulfuric Acid]]([[File:Beaker.png|16px]]1 part [[Chemistry#Hydrogen|Hydrogen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Sulfur|Sulfur]] [[File:Beaker.png|16px]]2 part [[Chemistry#Oxygen|Oxygen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|32px]]1 part [[Chemistry#Inaprovaline|Inaprovaline]]([[File:Beaker.png|16px]]1 part [[Chemistry#Oxygen|Oxygen]] [[File:Beaker.png|16px]]1 part [[Chemistry#Sugar|Sugar]] [[File:Beaker.png|16px]]1 part [[Chemistry#Carbon|Carbon]])
|-
! Zombification
| '''[[Chemistry#Ambuzol|Ambuzol]]''' [[File:Beaker.png|32px]]1 part [[Chemistry#Dylovene|Dylovene]]([[File:Beaker.png|16px]]1 part [[Chemistry#Potassium|Potassium]] [[File:Beaker.png|16px]]1 part [[Chemistry#Silicon|Silicon]] [[File:Beaker.png|16px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|32px]]1 part [[Chemistry#Ammonia|Ammonia]]([[File:Beaker.png|16px]]3 part [[Chemistry#Hydrogen|Hydrogen]][[File:Beaker.png|16px]]1 part [[Chemistry#Nitrogen|Nitrogen]]) [[File:Beaker.png|32px]]2 part [[Chemistry#Blood|Blood]]
----
'''[[Chemistry#Ambuzol_plus|Ambuzol Plus]]''' [[File:Beaker.png|32px]]5 part [[Chemistry#Ambuzol|Ambuzol]] [[File:Beaker.png|32px]]15 part [[Chemistry#Zombie_blood|Zombie Blood]]

|}

{{Guides Menu}}

Staff HQ

2026-01-28T19:07:27Z

Vape: Changed protection settings for "Staff HQ": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading]

{| class="wikitable " style="background-color: #110157; color: blue; width: 100%;"
|+ Staff HQ Directory
|-
! All Staff !! Direction !! Whitelisting !! Other
|-
| [[Staff Policy]] || [[Direction Guidelines|Guidelines]] || [[Whitelist|Whitelist Info]] || [[Staff Reporting]]
|-
| || [[Event Policy]]|| Example || Example
|}

Staff Reporting

2026-01-28T19:07:05Z

Vape: Protected "Staff Reporting" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

While our organization strives to exceed the expectations of our community with our staff team, No one is perfect. If any member of our community or another encounters an issue with a member of our staff team, we urge them to submit a staff report to document and allow us to properly investigate the issue.

=== Where to report ===
Staff reports are primarily handled over Discord. ''While we have trialed out a seperate email for those who feel discouraged to use Discord, we have found that this system resulted in many lost and forgotten tickets, and presented with extended response times.'' At this time there are 2 ways to submit a report:

1. '''[https://discord.com/channels/968983104247185448/1409854758600183808 Discord Ticket System]'''

''To submit a staff report via the Ticket system, go to the page linked above, and click "Create Ticket" at the option that says "Staff Report"''

'''2. Private direct messaging'''

''While we strive to have a non-biased and approachable system, we understand that this is not a perfect system, any staff report can also be made via a private message over discord to any of the following staff roles:''
* Project Managers
* Head Moderators
* Senior Moderators
* Head Game Administrators

=== Evidence Gathering tips ===
While every staff report is different, a few tips to assist the investigating staff member are below.

* If this happened in a round, try to include the round number
* if this happened in discord, include screenshots if you are able

''Please understand that any investigation will be hindered if the issue has happened many months prior. Due to our Replays and logging systems, our servers only maintain these up to 4-6 months.''