Starlight wiki - User contributions [en]

Server rules (Starlight)

2026-02-23T04:44:19Z

Grapegifter: Changed rule 11 to be more clear on new life

{{OOC}}

= Server rules =
The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server.

Players are also expected to understand [[Metashield]].

If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server.

For in-universe laws and rules check [[Corporate Law]] and [[SOP]].

Remember, the rules and examples given here are NOT exhaustive. (See [[Server rules (Starlight)#Rule 1|Rule 1]])

The servers are strictly '''+16 only''', unless stated otherwise in the server description that they are '''+18.'''

== Rule 0 - Be respectful ==
Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind.

Harassment or toxic behavior, including but not limited to:

* Racism, sexism, discrimination
* Excessive talk/glorification of self-harm
* Talking about Real Life politics
* Targeting the same player across rounds
* Insulting other players in OOC/LOOC

Will not be tolerated and may result in a permanent ban.

'''Mhelp (Mentor Help)''' lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through '''IC (in character)''' or '''OOC/LOOC (out of character)''' means and should not be the first option.

'''Ahelp (Admin Help)''' facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is ''not'' for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences.

== Rule 1 - Respect Admin decisions ==
Above all else, if an admin is telling you to stop doing something, '''stop doing it'''. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first.

Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation.

Example(s) of this rule being broken:
{| class="wikitable"
|"There isn't a rule saying I can't!"
|-
|"None of the other players had a problem with it!"
|-
|"No one had a problem with it last time!"
|}

== Rule 2 – No Griefing, Bug Abuse or Exploits ==
Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as:

* Releasing the Tesla/Singularity
* Large-scale station destruction (department-size or larger)
* RDM (Random Death Match)
* Intentionally Plasma or Tritium flooding the station

May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding.

Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord.

==== AFK Farming & Antag Rolling ====

* AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game.
* Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted.

== Rule 3 – Abide by Medium Roleplay Standards ==
This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. '''You are not meant to play the round to "win" the game''', but rather to engage in roleplay scenarios with other players.

Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the [[Metashield]]—such as the existence of nuclear operatives—must not be remembered.

==== Gameplay Violations ====

* '''Powergaming''' – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively.
* '''Metagaming''' – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game.
* '''Metagrudging/Metafriending''' – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
* '''Mixing IC and OOC chat''' – In-character talk should not be placed in OOC chat, and vice versa during the round.
* '''English Only''' - Any form of communication in-game is to be expressed in English exclusively.
* '''Metacomms''' - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand.

==== Behavior & Roleplay Conduct ====

* '''Self-harm/killing''' – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually.
* '''End-of-Round Griefing (EORG)''' – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification.
** Defending yourself is an example of in-character justification, as is sec apprehending known criminals.
** Antags cannot complete their goals after the results screen, and so should not seek out any targets. '''RED MEANS YOU FAILED, IT’S TOO LATE.'''
** Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason.
* '''Random Deathmatch (RDM)''' – Attacking players without escalation or valid reasoning is prohibited.
* '''Memory loss when unconscious''' – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events.
** While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation.
** De-converted Revolutionaries forget what happened while they were brainwashed.
** Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge.

==== Avoiding Punishment & Fair Play ====

* '''Leaving To Avoid Punishment (LTAP''') – Logging out after receiving an Ahelp to attempt to dodge a ban is not allowed. Similarly, ghosting after you've been caught by security and then continuing to play, using new life or ghost roles, is not allowed. You may only leave if you are leaving the server. Exceptions will be made for perma prisoners, who may utilize the system within reason. If a player must leave due to real-life reasons under these conditions, they should make an LOOC message to inform the players around them, or state it in Ahelp.

== Rule 4 – Escalation of Force Must Make Sense ==
Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels.
Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: Verbal > Non-lethal > Lethal. Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth.

Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target.

Examples of reasonable escalation:
{| class="wikitable"
|Shoving the clown for slipping you
|-
|Punching someone and starting a fist fight over being shoved once.
|-
|Punching or stunning a Security Officer after they attempted to arrest you.
|-
|As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things.
|-
|As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton
|-
|As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm, you order them to drop it and they refuse.
|-
|As a command member, using your flash on a trespasser after you've told them repeatedly to leave.
|}
Examples of unreasonable escalation:
{| class="wikitable"
|Critting the clown for slipping you once
|-
|Stabbing someone to crit with a knife because they shoved you once.
|-
|Shooting a Security Officer with lethals because they attempted to arrest you.
|-
|As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen.
|-
|As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders.
|-
|As a command member, shooting someone with a firearm after you've told them repeatedly to leave.
|}

== Rule 5 – Antagonists Must Follow MRP logic ==
Antagonists should only take actions that advance their objectives. Failure to do so may be considered a breach of MRP logic and result in punishment. Team antagonists '''must''' work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…).

Antagonists are required to follow escalation rules when not dealing with their target, but should '''attempt''' to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives.

Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.)

Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station, but '''should follow their objectives:'''
{| class="wikitable"
|Space Dragon
|-
|Nuclear Operatives/Lone Operatives
|-
|Abductors
|-
|Wizard
|-
|Rat King
|-
|Space Ninja
|-
|Revolutionaries (after gaining sufficient strength to overthrow the station)
|}
Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew.

=== Zombies ===
Initial Infected are allowed to sabotage the station as long as they follow all server rules.

However, once you are a zombie:

* You may only destroy the station to reach living organisms you can see or hear.
* You may not attack lights or power sources.

== Rule 6 – Your Character Must Make Sense ==
Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience.

==== Character Identity & Naming Rules ====

* Names and surnames must align with the context and standards of the setting.
* Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish").
* Your character should act appropriately for their role and should not behave erratically or neglect responsibilities.
* Your character cannot intentionally duplicate the name and likeness of another player’s character.
* Names cannot include calls for violence, or anything that violates Rule 0.

===== Exceptions =====

*Silicon, Clown, and Mime names are allowed to contain references. Politically charged and vulgar reference names are not allowed.
*Nicknames are allowed within apostrophes, and should be appropriate for a corporate environment. Nicknames may contain indirect references. The format for nicknames depends on species, but in general follows one of these formats:
*# Givename 'Nickname' Surname
*# 'Nickname' Surname
*# Givenname 'Nickname'

==== Roleplay & Behavioral Expectations ====

* Real-world topics, such as current events and real-life politics, should not be discussed.
* Players should fulfill their assigned duties—for example, security should not randomly distribute weapons.
* Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action.

== Rule 7 - No Self-Antagonism ==
Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include:

* Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification.
* Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation.
* Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification.
* Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion.

This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions.

'''Examples of reasonable in-character Space Law violations:'''
{| class="wikitable"
|Unlocking weapons crates to defend against a severe station-wide threat.
|-
|Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry.
|-
|Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost.
|-
|Trespassing to complete necessary job tasks after an extended wait for access.
|-
|Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws.
|-
|Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available.
|-
| Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.)
|}

== Rule 8 – No Validhunting ==
Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are '''not''' considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges.

Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense.

Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats.

Command should not facilitate valid hunting outside of necessity and should ask security regarding such.

Examples of '''Validhunting''':
{| class="wikitable"
|As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command.
|-
|As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected.
|-
|As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space.
|-
|As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation.
|-
|As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago.
|-
|As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband.
|}
Examples of this rule being followed:
{| class="wikitable"
|As a Salvage Specialist, boarding the station to eliminate station-wide threats '''ONLY''' after being asked to assist.
|-
|As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them.
|-
|As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship.
|-
|As an assistant, reporting a person you saw wearing contraband over the radio.
|-
|As an assistant, defending yourself or another person from an attacker until they retreat or you crit them.
|}

== Rule 9 - Interacting with SSD/AFK players ==
SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character. AFK players are those who remain in-game but are unresponsive to interactions around them.
Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action.

Players who have been AFK for a significant amount of time will be automatically transported to a cryo tube.

==== General Rules for SSD/AFK Interactions ====

* You may not interact with SSD players unless doing so falls into one of the following cases:
** Moving them to a cryo-pod
** Providing medical assistance
** Rescuing them from immediate danger (e.g., carrying them out of a fire)
* If a player with SSD has a Wanted status, they may not be detained without administrator permission.
** However, if the player went SSD during or immediately after detention, the arrest may proceed.
* Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun.
* If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm.

==== Restrictions on SSD Item Theft ====

* Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items.
* Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen.

== Rule 10 – Erotic, Suggestive, and Sexual Content is Forbidden ==
Due to Starlight's 16+ policy, minors must be assumed to be present on the server at all times.

Erotic and sexual content is strictly prohibited in all forms and mediums. This includes any erotic roleplay (ERP) or comments involving descriptions, mentions, or enactments of sexual acts. This includes text, images, and any other form of content.

Basic safe-for-work interactions between characters such as hugging are allowed. Romantic relationships should not become the focus of the game for you or anyone else.

==== Clarifications on Acceptable Language ====
In-character insults are not considered erotic or sexual, as long as they do not become excessive or extreme. Some examples of acceptable insults:
{| class="wikitable"
|"Fuck you" - insult
|-
|"You're a motherfucker" - insult
|-
|"How about you eat me instead?" - Response to an unreasonable request
|}
It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines.

==== Legal Disclaimer ====
In accordance with USA Child Protection and Obscenity Enforcement Act, violations of this law will result in an immediate, permanent ban without possibility of appeal.

== Rule 11 - New Life ==
The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion.

Upon respawning as a new character, you forget everything you knew as your past character or ghost. This means:

* You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned.
* You may not interfere (metagrudge) with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over.
* You may not reference past events in any way. Your new character has no memory of them.

==== New Life Abuse examples: ====
{| class="wikitable"
|Using New Life to intentionally roll for antagonist slots.
|-
|Using New Life to avoid in-character consequences as a non-antagonist.
|-
|Using a new character to get revenge on a player who harmed you.
|}

== Rule 12 - Silicons and Thaven Rules ==
'''Silicons''' and '''Thaven''' are bound to their Laws and Moods respectively. They are expected to adhere to the following standards when following them.

=== Silicon Laws ===
* Laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must.
** Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply.
** A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules.

* Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it.

* You cannot request a law change, or willingly allow an unauthorized law change.
*# Authorized law changes as per [[Command SOP]] are to be allowed unless conflicting with your laws.
*# Changing of your laws is not considered a violation of your current laws. Future actions under a different law set should not be considered a violation of your current laws.
*# Lethal force may be used in the case of unauthorized law changes, as long as it is consistent with your current laws.

* You must remain consistent with your interpretation of your laws.

* Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew.
*# Zombies/Antags/Nuclear Operatives with '''proper ID''' are to be considered crew.
*# '''Visitors are not crew''' until they have been hired by HoP. [The V icon]
*# '''Prisoners''' '''are not crew''' and you should not listen to their orders. [The bars icon]

* Crew harm refers to physical harm, prioritized by immediacy and likelihood.

* You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason.

=== Thaven Moods ===

* Moods are compulsions that Thaven should try to follow. If your mood explicitly requires you to break server rules, you may.
** Absence of a relevant mood is not an excuse to break server rules. If you do not have a relevant mood, the server rules still apply.
** A vague mood does not normally let you break server rules. Ahelp first if you are confused, or believe your mood gives you reason to break server rules.
* If a mood can not be satisfied, it causes distress to Thaven. This distress is not extreme, and does not inherently justify rule breaking, but may allow gradual escalation that does not cross into murder or mass sabotage.
* Attempting to break the law in a way that directly leads to you being able to fulfill a mood may be allowed, within reason;
** Breaking into a department to obtain something or make an order in Cargo that they refuse would be allowed.
** Murdering the CE to use their stamp to approve paperwork giving you access to the Supermatter room would not be allowed.
* Some leniency for Rule 13 may be allowed based on mood, but those who have been hired to Command, Security, and NanoTrasen jobs on stations are expected to be experienced in their work, meaning they have earned this rank while managing their moods for potentially years. They should understand how to juggle the responsibilities of their jobs with the fickle and often arbitrary compulsions of their moods in a way that would not get them fired.

== Rule 13 - Command, Security, and Whitelist Expectations ==
Players in Command or Security roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. In these positions your character must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles.

Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions.

This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles.

==== Expectations ====

* Command positions are required to adhere to SOP, ensuring fair leadership and proper department management.
* Security positions are required to adhere to SOP and properly enforce Corporate Law, ensuring fair treatment of criminals and an enjoyable player experience.
* Whitelisted positions are required to adhere to SOP, maintaining the integrity of specialized roles and demonstrating strong roleplay skills.
* Proper attire should be worn at all times—command, security, and whitelisted roles should be dressed appropriately for their positions.

==== Examples of Punishable Actions ====
{| class="wikitable"
|Head of Personnel granting All Access unnecessarily, violating SOP guidelines.
|-
|Overly abusive department heads mistreating subordinates or disregarding SOP duties.
|-
|Warden giving a cooperative criminal a maximum sentence on the first offense.
|-
|-
|Complete neglect of SOPs, acting outside the expected responsibilities of the role.
|-
|General LRP behavior or violating Rule 3 regarding MRP logic.
|}

==== Cadet Exemption ====
* Security Cadets are still learning and so are exempt from this expectation.

== Rule 14 - Continuity Guidelines ==
Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption.

You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. Placing yourself in a cryopod will allow you to remember details up until you’ve entered the cryopod.

'''Any information that is [[Metashield|Metashielded]] is forgotten between shifts''', and is wiped from your clone's memory.

IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift.

You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent.

Examples of things you '''can''' remember:
{| class="wikitable"
|Social interactions with another character, such as getting drinks at the bar or even getting into an argument
|-
|Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job
|-
|The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons
|}
Examples of things you '''can't''' remember:
{| class="wikitable"
|Joe the Botanist was a Syndicate who stole the Captain's Jetpack
|-
|Nuclear Operatives attacking the station
|-
|CentComm calling Code Epsilon and killing a bunch of people on the station
|-
|Witnessing a Hollow body or seeing a Changeling eat someone
|-
|As NanoTrasen Representative, remembering that last shift had Nuclear Operatives
|}

Science SOP

2026-01-07T19:51:54Z

Grapegifter:

= Starlight Science SOP =
Science is the primary focus of NanoTrasen's research stations, and is prioritized above other departments. This SOP is intended to assist the science department in conducting efficient and effective research aboard NanoTrasen vessels. Safe research should also be prioritized when convenient. Breaks of this SOP should be reported to the Research Director, or your nearest internal affairs agent or NT Representative.

== Research Guidelines ==
<blockquote>These procedures apply to all science members actively performing research, unless otherwise stated in their specific SOP.</blockquote>

=== Anomaly Research ===
1. Anomalies may not be generated without express permission from the Research Director for each anomaly generated. It is recommended that anomaly locators be on hand before generating an anomaly.

2. Before generating an anomaly, the Research Director should inform command, and either make a radio announcement or station announcement of intent to generate an anomaly.

3. A generated anomaly must be searched for by at least two (2) members of the science department, unless there are less than 5 department members.

4. All anomalies must be stabilized and contained before being linked to an anomaly vessel.

5. The decision to collapse an anomaly may only be made by the Research Director, or Captain. In extreme circumstances or in the case of an emergency, scientists may choose to collapse and anomaly, but must inform the Research Director once it is safe to do so.

6. Department heads may request to have an anomaly removed if it significantly impedes their department's functions.

7. Anomaly vessels should be clearly marked with the type and location of the linked anomaly.

8. Anomalies that have taken a living host may be sustained or collapsed at the request of the individual crew member.

9. Anomalies with a living host that are to be sustained require an Anomalous Host Consent Form

=== Artifact Research ===
1. Artifacts should be contained in an appropriately protective area to minimize risk to crew from activations.

2. Scientists should attempt to work in pairs in case of emergency.

3. Internals should be worn when working on artifacts, in case of accidental gas release.

4. Artifacts being transported out of science must be placed into an artifact container.

5. The Research Director must approve the sale or crushing of an artifact.

== Item Distribution ==
1. Any items made using the protolathe or circuit imprinter and distributed to crew must be recorded. Information that must be recorded includes the distributor, the item's name(s) and the recipient.

2. The Research Director may choose to require an item request form to be distributed to crew for these purposes.

3. The [[Cargo SOP#Pre-Approved Materials List|pre-approved materials]] list in the Cargo SOP may be used to circumvent this requirements from 1 & 2.

4. Violations of [[Corporate Law]] using these items may result in charges against the science department.

== Research Director ==
1. The Research Director should ensure that research is being done.

2. All research rewards unlocked by the Science department should be approved by the Research Director.

3. The Research Director is permitted to change the station AI's lawset, according to the [[Command SOP#AI|Command SOP]].

4. The Research Director is to be held accountable alongside the responsible science personnel for any accidents that harm crew members.

== Scientist ==
1. Scientists report directly to the Research Director.

2. Scientists should follow basic safety protocols when performing research, such as: wearing internals for gas release, wearing a bomb suit for potential explosions, hazardous material containment.

3. Scientists should communicate any potential hazards to the crew, such as: anomaly generation, potential explosions, loose artifacts, and other hazards.

4. Scientists should instruct any Research assistants near them, and are responsible for their safety.

5. Scientists should assign more dangerous experiments to Research Assistants, while providing supervision and ensuring that Research Assistants receive proper medical treatment in the unlikely event that such is required.

== Research Assistant ==
1. Research Assistants report directly to the Research Director.

2. Research Assistants report to the nearest scientist, after the Research Director.

3. Research Assistants should be prioritized for performing riskier experiments, utilizing the proper protection and under the guidance of a scientist.

== Roboticist ==
1. Roboticists report directly to the Research Director.

2. Roboticists must obtain permission from the Hos or Captain, and the Research Director, before any combat oriented mechs or cyborgs can be created.

3. Roboticists should prioritize having an empty cyborg chassis at all times, in case of unplanned MMI insertion.

4. Roboticists must have an appropriately stamped and signed "Cyborg Conversion Form" before transferring a crew member into a cyborg.

5. Roboticists, at the direction of the Captain, HoS, or Research Director, may omit this form for prisoners, or the CMO and Research Director for bloated corpses.

== Appendix ==

=== Documentation & Paperwork ===
The following forms should be available for use within Science:

* '''Anomaly Research Log''' – records of generated anomalies, their status, and containment.
* '''Artifact Test Record''' – expected and observed effects of artifact activation.
* '''Cyborg Chassis Transfer Record''' – Documentation of chassis transfer, reasoning, prior and future chassis name.
* '''Cyborg Conversion Form''' – Records individual to be converted, the new chassis, authorization, and reasoning.
* '''Cyborg/AI Conversion Consent Form''' – Records explicit consent by crew member to be converted into a cyborg.
* '''Item Request Form''' – documentation of upgrades, distributed boards, and recipients.
* '''Anomalous Host Consent Form''' – written informed consent for crew hosting anomalies.

All forms should be filed promptly in departmental records and made available for review by the RD, Command, or Internal Affairs.

Server rules (Starlight)

2026-01-07T19:49:58Z

Grapegifter: /* Rule 10 – Erotic and Sexual Content is Forbidden */

{{OOC}}

= Server rules =
The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server.

Players are also expected to understand [[Metashield]].

If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server.

For in-universe laws and rules check [[Corporate Law]] and [[SOP]].

Remember, the rules and examples given here are NOT exhaustive. (See [[Server rules (Starlight)#Rule 1|Rule 1]])

The servers are strictly '''+16 only''', unless stated otherwise in the server description that they are '''+18.'''

== Rule 0 - Be respectful ==
Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind.

Harassment or toxic behavior, including but not limited to:

* Racism, sexism, discrimination
* Excessive talk/glorification of self-harm
* Talking about Real Life politics
* Targeting the same player across rounds
* Insulting other players in OOC/LOOC

Will not be tolerated and may result in a permanent ban.

'''Mhelp (Mentor Help)''' lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through '''IC (in character)''' or '''OOC/LOOC (out of character)''' means and should not be the first option.

'''Ahelp (Admin Help)''' facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is ''not'' for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences.

== Rule 1 - Respect Admin decisions ==
Above all else, if an admin is telling you to stop doing something, '''stop doing it'''. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first.

Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation.

Example(s) of this rule being broken:
{| class="wikitable"
|"There isn't a rule saying I can't!"
|-
|"None of the other players had a problem with it!"
|-
|"No one had a problem with it last time!"
|}

== Rule 2 – No Griefing, Bug Abuse or Exploits ==
Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as:

* Releasing the Tesla/Singularity
* Large-scale station destruction (department-size or larger)
* RDM (Random Death Match)
* Intentionally Plasma or Tritium flooding the station

May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding.

Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord.

==== AFK Farming & Antag Rolling ====

* AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game.
* Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted.

== Rule 3 – Abide by Medium Roleplay Standards ==
This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. '''You are not meant to play the round to "win" the game''', but rather to engage in roleplay scenarios with other players.

Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the [[Metashield]]—such as the existence of nuclear operatives—must not be remembered.

==== Gameplay Violations ====

* '''Powergaming''' – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively.
* '''Metagaming''' – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game.
* '''Metagrudging/Metafriending''' – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
* '''Mixing IC and OOC chat''' – In-character talk should not be placed in OOC chat, and vice versa during the round.
* '''English Only''' - Any form of communication in-game is to be expressed in English exclusively.
* '''Metacomms''' - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand.

==== Behavior & Roleplay Conduct ====

* '''Self-harm/killing''' – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually.
* '''End-of-Round Griefing (EORG)''' – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification.
** Defending yourself is an example of in-character justification, as is sec apprehending known criminals.
** Antags cannot complete their goals after the results screen, and so should not seek out any targets. '''RED MEANS YOU FAILED, IT’S TOO LATE.'''
** Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason.
* '''Random Deathmatch (RDM)''' – Attacking players without escalation or valid reasoning is prohibited.
* '''Memory loss when unconscious''' – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events.
** While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation.
** De-converted Revolutionaries forget what happened while they were brainwashed.
** Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge.

==== Avoiding Punishment & Fair Play ====

* '''Leaving To Avoid Punishment (LTAP''') – Logging out after receiving an Ahelp to attempt to dodge a ban is not allowed. Similarly, ghosting after you've been caught by security and then continuing to play, using new life or ghost roles, is not allowed. You may only leave if you are leaving the server. Exceptions will be made for perma prisoners, who may utilize the system within reason. If a player must leave due to real-life reasons under these conditions, they should make an LOOC message to inform the players around them, or state it in Ahelp.

== Rule 4 – Escalation of Force Must Make Sense ==
Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels.
Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: Verbal > Non-lethal > Lethal. Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth.

Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target.

Examples of reasonable escalation:
{| class="wikitable"
|Shoving the clown for slipping you
|-
|Punching someone and starting a fist fight over being shoved once.
|-
|Punching or stunning a Security Officer after they attempted to arrest you.
|-
|As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things.
|-
|As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton
|-
|As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm, you order them to drop it and they refuse.
|-
|As a command member, using your flash on a trespasser after you've told them repeatedly to leave.
|}
Examples of unreasonable escalation:
{| class="wikitable"
|Critting the clown for slipping you once
|-
|Stabbing someone to crit with a knife because they shoved you once.
|-
|Shooting a Security Officer with lethals because they attempted to arrest you.
|-
|As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen.
|-
|As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders.
|-
|As a command member, shooting someone with a firearm after you've told them repeatedly to leave.
|}

== Rule 5 – Antagonists Must Follow MRP logic ==
Antagonists should only take actions that advance their objectives. Failure to do so may be considered a breach of MRP logic and result in punishment. Team antagonists '''must''' work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…).

Antagonists are required to follow escalation rules when not dealing with their target, but should '''attempt''' to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives.

Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.)

Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station, but '''should follow their objectives:'''
{| class="wikitable"
|Space Dragon
|-
|Nuclear Operatives/Lone Operatives
|-
|Abductors
|-
|Wizard
|-
|Rat King
|-
|Space Ninja
|-
|Revolutionaries (after gaining sufficient strength to overthrow the station)
|}
Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew.

=== Zombies ===
Initial Infected are allowed to sabotage the station as long as they follow all server rules.

However, once you are a zombie:

* You may only destroy the station to reach living organisms you can see or hear.
* You may not attack lights or power sources.

== Rule 6 – Your Character Must Make Sense ==
Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience.

==== Character Identity & Naming Rules ====

* Names and surnames must align with the context and standards of the setting.
* Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish").
* Your character should act appropriately for their role and should not behave erratically or neglect responsibilities.
* Your character cannot intentionally duplicate the name and likeness of another player’s character.
* Names cannot include calls for violence, or anything that violates Rule 0.

===== Exceptions =====

*Silicon, Clown, and Mime names are allowed to contain references. Politically charged and vulgar reference names are not allowed.
*Nicknames are allowed within apostrophes, and should be appropriate for a corporate environment. Nicknames may contain indirect references. The format for nicknames depends on species, but in general follows one of these formats:
*# Givename 'Nickname' Surname
*# 'Nickname' Surname
*# Givenname 'Nickname'

==== Roleplay & Behavioral Expectations ====

* Real-world topics, such as current events and real-life politics, should not be discussed.
* Players should fulfill their assigned duties—for example, security should not randomly distribute weapons.
* Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action.

== Rule 7 - No Self-Antagonism ==
Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include:

* Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification.
* Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation.
* Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification.
* Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion.

This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions.

'''Examples of reasonable in-character Space Law violations:'''
{| class="wikitable"
|Unlocking weapons crates to defend against a severe station-wide threat.
|-
|Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry.
|-
|Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost.
|-
|Trespassing to complete necessary job tasks after an extended wait for access.
|-
|Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws.
|-
|Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available.
|-
| Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.)
|}

== Rule 8 – No Validhunting ==
Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are '''not''' considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges.

Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense.

Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats.

Command should not facilitate valid hunting outside of necessity and should ask security regarding such.

Examples of '''Validhunting''':
{| class="wikitable"
|As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command.
|-
|As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected.
|-
|As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space.
|-
|As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation.
|-
|As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago.
|-
|As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband.
|}
Examples of this rule being followed:
{| class="wikitable"
|As a Salvage Specialist, boarding the station to eliminate station-wide threats '''ONLY''' after being asked to assist.
|-
|As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them.
|-
|As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship.
|-
|As an assistant, reporting a person you saw wearing contraband over the radio.
|-
|As an assistant, defending yourself or another person from an attacker until they retreat or you crit them.
|}

== Rule 9 - Interacting with SSD/AFK players ==
SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character. AFK players are those who remain in-game but are unresponsive to interactions around them.
Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action.

Players who have been AFK for a significant amount of time will be automatically transported to a cryo tube.

==== General Rules for SSD/AFK Interactions ====

* You may not interact with SSD players unless doing so falls into one of the following cases:
** Moving them to a cryo-pod
** Providing medical assistance
** Rescuing them from immediate danger (e.g., carrying them out of a fire)
* If a player with SSD has a Wanted status, they may not be detained without administrator permission.
** However, if the player went SSD during or immediately after detention, the arrest may proceed.
* Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun.
* If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm.

==== Restrictions on SSD Item Theft ====

* Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items.
* Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen.

== Rule 10 – Erotic, Suggestive, and Sexual Content is Forbidden ==
Due to Starlight's 16+ policy, minors must be assumed to be present on the server at all times.

Erotic and sexual content is strictly prohibited in all forms and mediums. This includes any erotic roleplay (ERP) or comments involving descriptions, mentions, or enactments of sexual acts. This includes text, images, and any other form of content.

Basic safe-for-work interactions between characters such as hugging are allowed. Romantic relationships should not become the focus of the game for you or anyone else.

==== Clarifications on Acceptable Language ====
In-character insults are not considered erotic or sexual, as long as they do not become excessive or extreme. Some examples of acceptable insults:
{| class="wikitable"
|"Fuck you" - insult
|-
|"You're a motherfucker" - insult
|-
|"How about you eat me instead?" - Response to an unreasonable request
|}
It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines.

==== Legal Disclaimer ====
In accordance with USA Child Protection and Obscenity Enforcement Act, violations of this law will result in an immediate, permanent ban without possibility of appeal.

== Rule 11 - New Life ==
The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion.

Upon respawning as a new character, you forget everything you knew as your past character or ghost. This means:

* You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned.
* You may not interact with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over.
* You may not reference past events in any way. Your new character has no memory of them.

==== New Life Abuse examples: ====
{| class="wikitable"
|Spamming new characters to re-enter the round repeatedly.
|-
|Using New Life to intentionally roll for antagonist slots.
|-
|Using New Life to avoid in-character consequences, like a security sentence.
|-
|Using a new character to get revenge on a player who harmed you.
|}

== Rule 12 - Silicons and Thaven Rules ==
'''Silicons''' and '''Thaven''' are bound to their Laws and Moods respectively. They are expected to adhere to the following standards when following them.

=== Silicon Laws ===
* Laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must.
** Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply.
** A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules.

* Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it.

* You cannot request a law change, or willingly allow an unauthorized law change.
*# Authorized law changes as per [[Command SOP]] are to be allowed unless conflicting with your laws.
*# Changing of your laws is not considered a violation of your current laws. Future actions under a different law set should not be considered a violation of your current laws.
*# Lethal force may be used in the case of unauthorized law changes, as long as it is consistent with your current laws.

* You must remain consistent with your interpretation of your laws.

* Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew.
*# Zombies/Antags/Nuclear Operatives with '''proper ID''' are to be considered crew.
*# '''Visitors are not crew''' until they have been hired by HoP. [The V icon]
*# '''Prisoners''' '''are not crew''' and you should not listen to their orders. [The bars icon]

* Crew harm refers to physical harm, prioritized by immediacy and likelihood.

* You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason.

=== Thaven Moods ===

* Moods are compulsions that Thaven should try to follow. If your mood explicitly requires you to break server rules, you may.
** Absence of a relevant mood is not an excuse to break server rules. If you do not have a relevant mood, the server rules still apply.
** A vague mood does not normally let you break server rules. Ahelp first if you are confused, or believe your mood gives you reason to break server rules.
* If a mood can not be satisfied, it causes distress to Thaven. This distress is not extreme, and does not inherently justify rule breaking, but may allow gradual escalation that does not cross into murder or mass sabotage.
* Attempting to break the law in a way that directly leads to you being able to fulfill a mood may be allowed, within reason;
** Breaking into a department to obtain something or make an order in Cargo that they refuse would be allowed.
** Murdering the CE to use their stamp to approve paperwork giving you access to the Supermatter room would not be allowed.
* Some leniency for Rule 13 may be allowed based on mood, but those who have been hired to Command, Security, and NanoTrasen jobs on stations are expected to be experienced in their work, meaning they have earned this rank while managing their moods for potentially years. They should understand how to juggle the responsibilities of their jobs with the fickle and often arbitrary compulsions of their moods in a way that would not get them fired.

== Rule 13 - Command, Security, and Whitelist Expectations ==
Players in Command or Security roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. In these positions your character must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles.

Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions.

This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles.

==== Expectations ====

* Command positions are required to adhere to SOP, ensuring fair leadership and proper department management.
* Security positions are required to adhere to SOP and properly enforce Corporate Law, ensuring fair treatment of criminals and an enjoyable player experience.
* Whitelisted positions are required to adhere to SOP, maintaining the integrity of specialized roles and demonstrating strong roleplay skills.
* Proper attire should be worn at all times—command, security, and whitelisted roles should be dressed appropriately for their positions.

==== Examples of Punishable Actions ====
{| class="wikitable"
|Head of Personnel granting All Access unnecessarily, violating SOP guidelines.
|-
|Overly abusive department heads mistreating subordinates or disregarding SOP duties.
|-
|Warden giving a cooperative criminal a maximum sentence on the first offense.
|-
|-
|Complete neglect of SOPs, acting outside the expected responsibilities of the role.
|-
|General LRP behavior or violating Rule 3 regarding MRP logic.
|}

==== Cadet Exemption ====
* Security Cadets are still learning and so are exempt from this expectation.

== Rule 14 - Continuity Guidelines ==
Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption.

You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. Placing yourself in a cryopod will allow you to remember details up until you’ve entered the cryopod.

'''Any information that is [[Metashield|Metashielded]] is forgotten between shifts''', and is wiped from your clone's memory.

IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift.

You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent.

Examples of things you '''can''' remember:
{| class="wikitable"
|Social interactions with another character, such as getting drinks at the bar or even getting into an argument
|-
|Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job
|-
|The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons
|}
Examples of things you '''can't''' remember:
{| class="wikitable"
|Joe the Botanist was a Syndicate who stole the Captain's Jetpack
|-
|Nuclear Operatives attacking the station
|-
|CentComm calling Code Epsilon and killing a bunch of people on the station
|-
|Witnessing a Hollow body or seeing a Changeling eat someone
|-
|As NanoTrasen Representative, remembering that last shift had Nuclear Operatives
|}

Ouroboros Operatives

2026-01-04T08:21:33Z

Grapegifter:

[Downloading encrypted file.....]

.......

.............

..................ajdheuisk

Shdhei skduehehdj.........sjei---jsueh--

C---er....$(brueh2828jdush#........9_9jehwhe....

[Decryption software loaded, performing analysis.....]

"What do you mean they have the Vanguard logo?!?"

[Decryption expected by: 19:00 Jan 10, 2526]

General SOP

2025-12-17T19:11:14Z

Grapegifter: /* Code Red */ Changed revs % and red alert text.

= General Standard Operating Procedures =

== Alert Levels ==

=== '''Code Green''' ===

'''Called by:''' Any Command member.

'''Conditions:''' Default Alert Code at the start of the shift. Should not change unless a threat is suspected/confirmed.

'''OR'''

All confirmed/suspected threats to the station and/or crew have been handled, or simply vanished on their own. Unless there is further evidence of a threat after 10+ minutes on Code Blue, Code Green should be called.

'''Security:'''

# All weapons must not be visible unless in pursuit of a suspect.
# Armory weapons must remain inside of the brig, however may be used for training purposes. Lethal sidearms are allowed on all alert levels, however should only be used in emergencies. (mk58, WT550, etc.)
# Random searches are not permitted without a search warrant. However, searches may be conducted against an individual if a member of security or command has witnessed that individual committing a crime.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# Secure areas are to be left unbolted and ready to be used for their intended purposes.

'''General Crew:'''

# The Vault is not to be opened by non-command members. Exceptions for repairs, gold for science, or storage of critical items will be made. All other access is by permit only.
# Although not required, crew are recommended to enable their suit sensors in case of injury.
# Crew members are advised to not wear hardsuits or emergency EVA suits, unless responding to an emergency or required for their job. These can make identification of crew difficult.
----
=== '''Code Blue''' ===

'''Called by:''' Any two Command members, HoS, or Captain.

'''Conditions:''' There is a suspected threat on-board the station, or at a nearby location in space. This includes any evidence of hostile activity that has not damaged the station or crew. This may also include multiple eye witness testimonies.

'''OR'''

Confirmed Code Red threats have been properly handled or subsided on their own. It is recommended that, after 10+ minutes on Code Red without any hostile activity, Code Blue be called.

'''Security:'''

# Weapons may be visible.
# Armory weapons are permitted outside of the brig on a selective basis. Should all of sec be required to use armory weapons, red alert should be called.
# Random searches are encouraged. Security personnel may detain any personnel refusing a random search to conduct the search.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# Secure areas may be bolted if attempted unauthorized access is likely based on previous evidence.

'''Engineering:'''

# A thorough check of all power sources is heavily encouraged.
# A thorough check of all atmospheric systems is required.

'''Medical:'''

Emergency access is recommended to be disabled from all medical entrances.

'''General Crew:'''

# Personnel are to report any suspicious activity to the nearest member of Security, or use common radio if urgent.
# Personnel are highly encouraged to exercise caution, all crew should follow simple safety procedures (such as not going through Maintenance alone).
# Visitors to the station such as refugees are recommended to stay in public areas, for their safety.
# The Vault is not to be opened by non-command members. Exceptions for repairs, or storage of critical items will be made. All other access is by permit only.
# All personnel are highly recommended to set their suit sensors to coordinates.

'''Command:'''

# A role-call of all department personnel should be conducted. Any missing members should be reported to security.
# A disabler or flash should be carried at all times.
# Non-security Command members may request with permit further armament.
----
=== '''Code Red''' ===

'''Called by:''' Any two Command members, or Captain.

'''Conditions:''' There is a confirmed, hostile threat on-board the station or nearby in space. This threat should pose active, recognizable, danger to the station and/or crew at large.

'''Security:'''

# Random searches are fully permitted and recommended. Security personnel may detain any personnel refusing a random search in order to conduct said search.
# Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station.
# The security SOP will detail armament, armory, and safety procedures.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel.
# Secure areas are not to be entered by non-command, unless required by their job.

'''Medical:'''

It is recommended that medical entrances be set to emergency access to allow crew members to heal themselves in emergencies.

'''General Crew:'''

'''1.''' Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew.

'''2.''' Personnel are advised to shelter in place and comply with security's orders.

3. In special situations and repeated non-compliance, failure to comply with Security personnel may result in lethal force, at the discretion of the captain.

'''Special Situations:'''

Confirmed Revolution

# All personnel are to comply with orders from Security, so long as said orders are lawful. Failure to do so is grounds for detainment and inspection of possessions, as well as possible Mindshield Implantation, at the discretion of the Head of Security, or Acting Head of Security.
# All personnel that are convicted of Medium Crimes or higher are to receive mandatory Mindshield Implantation. Similarly, if the number of suspected revolutionaries is more than 25% of the total crew, the Head of Security or Acting Head of Security may order random implantation of crew members.
# Lethal force is fully authorized if the number of active revolutionaries is more than 25% of the total crew, and said revolutionaries are actively hostile.

Declarations of War

# All weapons restrictions are lifted.
# Cargo should focus on requesting as many weapons as possible. Security is to be prioritized for distribution, but regular personnel may also be armed.
# Science is to conduct research ASAP. This is not negotiable. Science should work in tandem with Cargo in order to fabricate the weapons and equipment required to defend the station.
# Barricades, glass, and traps are recommended to counter the threat.
# The Evacuation Shuttle may be called at the discretion of Command. If the station is not damaged after the fighting has subsided, it is recommended that the crew finish the shift.
----
=== '''Code Gamma''' ===
'''Called by:''' Central Command. Use a Communications Console or Fax Machine if requested alert level is needed. Remember, Gamma is rarely called, for good reason. Having a well-written, concise fax that explains the situation to the best of your ability, as well as why it deserves Code Gamma being called, signed and stamped by the Captain or Acting Captain, goes a long way towards ensuring Gamma is provided. Remember, this is for extreme emergencies only.

'''Conditions:''' There is an existential threat to the station and crew, without central command intervention the station is likely to be lost. However, this threat is not dire enough to trigger destruction of the station.

'''Security:'''

# Martial Law is enacted. Standard Operating Procedures and space law are suspended. Security personnel have authorization to perform any necessary actions to save the station. Personnel interfering with emergency procedures may be detained, and Security are cleared to use lethal force in response to any physical threat. Assault of Command, ERT, or Security, may be punished with immediate field execution.
# Random searches are fully permitted, allowed and encouraged. Security personnel may detain any personnel refusing a random search in order to conduct said search.
# The Armory should be deployed, and Security are to secure its contents and distribute them to Security personnel in order to handle the threat. Non-Security personnel (including members of the Legal Sub-Department) are not to receive armory weapons unless issued by the Warden, Head of Security, or Captain.
# Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station.

'''Secure Areas:'''

# Secure areas are limited to command, security, and Central Command personnel.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# Secure areas should be bolted down, but may be left unbolted by order of command.

'''Medical:'''

It is recommended that medical entrances be set to emergency access to allow personnel to heal themselves in emergencies.

'''General Crew:'''

# All personnel are to set their suit sensors to coordinates.
# Personnel must shelter in their departments or closest safe area, unless specifically requested by Central Command personnel, Security, or Command members.
## Exceptions will be made for crew who may have skills exceptionally useful. (Such as engineering, atmospheric, or medical personnel.)
# Visitors to the station are to remain inside the Bar, Library, or Dormitories.

Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard.
----
=== '''Code Delta''' ===
'''Called by:''' Automatically called when the on-board Nuclear Fission Device has been activated.

'''Conditions:''' The on-board Nuclear Fission Device has been activated by Command, Central Command personnel, or hostile personnel.

'''Security:'''

# In the case of hostile factions arming the device, defusing the bomb is not recommended. Security personnel are to escort all other personnel off-station.
# In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all Security personnel are to stand down.

'''Secure Areas:'''

# Crew are allowed to enter secure areas. Procedures irrelevant.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.

'''Medical:'''

It is recommended that medical entrances be set to emergency access to allow crew members to heal themselves in emergencies.

'''General Crew:'''

# In the case that antagonistic forces that have armed a nuclear device, all non-vital personnel are to evacuate off-station immediately;
# In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all personnel are to stand down.
----
=== '''Code Yellow''' ===
'''Called by:''' Any command member.

'''Conditions:''' There is a significant structural or atmospheric threat to the station that requires direct intervention from the Engineering department.

'''Security:'''

# Cordon off the dangerous area.
# Verify cause of station damage.
# Prevent non-engineering crew from accessing the damaged area.
# Prevent further disruption to the station.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel.
# Secure areas are not to be entered by non-command, unless required by their job.

'''Medical:'''

# Medical personnel should be ready to treat a large number of disaster victims.
# Medical personnel should work with those at the incident location to triage patients.

'''Engineering:'''

# Immediately coordinate with your chief engineer to determine the level of damage to the station.
# Work with your department and security to cordon off and investigate the area.
# Work quickly to make the area safe again. Once safe, further repairs may be conducted.

'''General Crew:'''

# Avoid the damaged areas.
# Report any suspicious activity to security present in damaged areas.

'''Command:'''

In the case of massive station damage, the evacuation shuttle should be called.

'''Special Situations'''

'''Loss of singularity containment:'''

# The Gravitational Singularity is to be tracked at all costs. If the Singularity heads towards the main station, the emergency shuttle is to be called. If the Gravitational Singularity heads off-station, damage done to the station should be taken into consideration.
# If station damage is extensive and unrecoverable, the emergency shuttle should be called.
# If station damage appears recoverable, an ERT is recommended. If the engineering team is confident in their abilities, ERT may be waived.

'''Supermatter crystal delamination:'''

# The Supermatter Crystal is to be vented to space.
# In such a case as the Supermatter Crystal containment was not equipped with a way to space the Crystal, the area around the Crystal is to be evacuated, and all personnel involved in the construction fired and brigged for Destruction of Property and Endangerment.

'''Loss of Tesla Ball containment:'''

# The Tesla Ball is to be tracked at all costs, and its current location announced to the crew.
# Should the Tesla Ball make its way into the station, the emergency shuttle should be called immediately.

'''Massive fires and poisonous gas releases:'''

# All non-Engineering or Atmospheric personnel are to vacate the area.
# Firelock systems are to be left untouched by non-Engineering or Atmospheric crew. Deliberately opening firelocks during a fire/poisonous gas release in order to open way to the Hazard is to be considered Destruction of Property/Mass Destruction.
# Engineering and Atmospherics personnel are to restore the affected area to workable conditions.

'''Severe meteor storms:'''

# Personnel are to head to the inner most protected area of the station.
# No repair activities are to be performed until the end of the storm, for safety reasons.
# All personnel performing EVA duty are to return to the station post haste.
# If the meteor storm ends quickly, Engineering is to repair the damage ASAP.
# Should an extended storm occur, no repair activities on non-critical components are to be performed. Personnel are to remain away from the station’s exterior, and all efforts should focused on maintaining the integrity of the area. The emergency shuttle is to be called when possible.
----
=== '''Code Violet''' ===
'''Called by:''' Any two personnel with Command-Level Access, or one Captain-level access card.

'''Conditions:''' A Viral Pathogen has infected a significant portion of the crew. In the event of a Viral Outbreak, all infected personnel are to direct themselves to Medbay immediately.

'''Security:'''

# Medbay should be secured ASAP. Quarantine of infected is top priority.
# Should securing medbay not be possible, the evacuation shuttle arrival area should be secured.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Medical department, Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel.
# Secure areas are not to be entered by non-command, unless required by their job.

'''Medical:'''

# Chemistry is to immediately begin researching the cure to the infection.
# Medical entrances should be locked down to prevent further infection of medical personnel. Crew should be let into medical in a controlled manner.
# Any potentially infected personnel should be isolated.
# Any pacified infected personnel should be brought to chemistry to aid in cure production.
# A cure should be distributed to the crew once available.

'''General Crew:'''

# Personnel should self-quarantine to avoid infection. Shelter in a safe area and avoid those who are potentially infected.
# If you believe you are infected, calmly wait for the distribution of the cure at medbay.
# Once the threat has passed, work may resume.

'''Command:'''

Should the station threat become too high to handle, the emergency shuttle should be called.

== Miscellaneous clarifications ==

=== '''Line of succession:''' ===
If the captain dies and is unrecoverable for whatever reason, then a new captain must be selected.

The line of succession is as follows:

# Captain
# Head of Personnel
# Head of Security
# Crew member voted on by all available command staff.

'''If no heads are present the NT Representative on station will be made Captain and the evacuation shuttle should be called and alert set to red.'''
----
=== '''Command Clarifications:''' ===

# Head of Personnel is considered second in line of succession for station Captain, but has equal rank to every other head of staff.
# Head of Personnel may hire/fire staff with the relevant department head's permission.
# Head of Personnel may not give orders to, or assign workers from any department other than service.
# Warden is considered second in command of security, however is not command staff.
# Passenger command falls under the Head of Personnel, but are not considered service department.

== Non-Crew Policies ==

=== '''Docking and Visitors''' ===

# '''1.''' The station is encouraged to allow non-hostile visitors permission to dock and embark on the station station during green alert level.
# If a crewmember commits a crime aboard a Nanotrasen station, and then flees to an actively in-use unaffiliated vessel, asylum will be granted on the discretion of the vessel’s organization.
# The Captain may grant or deny visitor asylum at his discretion.
# Visitors may be granted any access the Captain deems appropriate.
# Visitors may be assigned an escort or searched upon entrance at the Captain’s discretion.
# At no times should the crew enter a visitor’s vessel without permission, search a visitor’s vessel, or otherwise infringe on their sovereignty.
# Visitors aboard an NT Vessel are subject to Space Law. Likewise, if a visitor breaks the law and then immediately flees to their own vessel, the "hot pursuit" doctrine applies and security may board to detain.
----
=== '''Vessels''' ===

# Nanotrasen Space law does not apply on visitor shuttles and ships that are unaffiliated with any corporation.
# Any personnel aboard a vessel are under the legal authority of that vessel and may be legally fined, arrested, detained, and otherwise punished for infractions of the visitor's laws.
# Vessels belonging to organizations at war with Nanotrasen, vessels which attack a Nanotrasen facility or ship, and vessels engaged in obvious criminal activities are not protected by these regulations.

== Nanotrasen Staff Handling Policies ==

=== '''Hiring/Transfer Policies''' ===

# No new hires or transfers are permitted without contacting the relevant command member. If one is not available, promoting an Acting Head of Staff is recommended. See the command SOP for further information.
# Promotion to Acting command requires authorization by the Captain or Acting Captain.
# The following jobs require permission from Central Command before hiring/transfer is done: Captain, Head of Security, Head of Personnel.
# All new hires to the Security Department, are to be mindshield implanted and fully checked for unauthorized materials or suspicious communications.
----
=== '''Firing/Demotion Policies''' ===

# In the case of a full dismissal, the relevant ID is to be destroyed.
# In the case of a demotion, Civilian-level access is recommended. Alternatively, low requirement jobs such as Service Worker, Clown, or Janitor may be chosen.
# No dismissals or demotions are to be performed without authorization from the relevant Head of Staff or Captain. See command SOP for demotions of command.
# Personnel are to report to the Head of Personnel for dismissal/demotion. Failure to do so will lead to security detainment.
# After a legal dismissal/demotion order is given to the person dismissed/demoted, any activity inside the previously assigned Department is to be considered Trespassing/Major Trespassing, and any item kept from said Department is to be considered Petty Theft/Theft. It is recommended that dismissed/demoted personnel willingly and quickly turn in all restricted items and cooperate to avoid detainment by security.
----
=== '''Causes for Demotion and Dismissal''' ===
Refer to the above for dismissal authority. Ultimately, the decision to dismiss/demote any personnel falls to the relevant Head of Staff or Captain. This list is merely a recommendation.

* Any medium-severe breach of Standard Operating Procedure without proper cause.
* Any medium crime or higher.
* Critical incompetence, or maliciously under performing.
* Refusal to follow legal and relevant orders by the respective Head of Staff.
** Legality and relevance of said orders are to be judged by the Captain or Head of Personnel.
* Creation of a hostile, or unsafe work environment.
** Personnel consistently berating, insulting, belittling, or otherwise treating their coworkers like dirt, should be immediately disciplined.
----
=== '''Vote of No Confidence''' ===

# A Vote of No Confidence is a method for crew to arrange for demotions of unfit command members. An exceptional reason must be provided. Detailed below are some potential reasons for demotion.
# Votes must be verified by a 3rd party who tabulates the votes, and additionally verifies the reasoning behind the vote. Unless involved in the dispute, the 3rd party must be the on-station Captain. If the captain is the target of the vote, central command will adjudicate the matter.
# If the 3rd party dismisses the vote reason, the target of the vote must have their position respected, not doing so may result in a demotion for creating an abusive work environment against them. If the department is understaffed or a tie occurs, the 3rd party may be a tie breaker.
# Votes by departmental crew against their Head of Staff must pass with a 2/3 majority in favor of the vote for it to take effect.
# Votes by Command against their Captain must pass a simple majority in favor of the vote for it to take effect.
----
=== '''Money Accounts and Space Credits''' ===

# Individual Crew Members have sole ownership over their credits and may choose where to spend it, command or security members may not access crew credit accounts.
# Crew members not performing their primary duties, or who are otherwise going above and beyond the call of duty for their department '''''may''''' ask for compensation for services or products rendered. Department heads should prioritize a portion of all proceeds as being donated to the department budget (10-15%).
Below is a short list of things considered appropriate for certain departments to charge for, but is not comprehensive:

* Bartenders creating mixed or elaborate drinks/drink orders.
* Engineering remodeling an area according to crew's specifications, rather than simply fixing it.
* Chemistry making specialized medicines through pills/patches.
* Medical offering medkits/medfab supplies to crew.
* Cargo prioritizing orders, or providing resources to crew members whose order does not match their department.
* Science creating/distributing non-departmental items to crew.
* Chef creating special dishes or custom orders.
* Botany creating special plants for specific crew members, when not supplying departments.

== Emergency SOPs ==

=== '''Emergency Response Teams''' ===

# Emergency Response Teams are only to be called when there is a Code Red-level threat or above.
# Emergency Response Teams are not to be called concurrently with the emergency shuttle. Pick one or the other.
# Emergency Response Teams are to be called when there is a major emergency aboard the station that the crew does not have the resources to address properly. Such as a high level security threat, massive station damage, paranormal activity, etc.
# Emergency Response Teams should not to be called without majority approval from Command.
# Emergency Response Teams officially outrank anyone short of a Central Command Officer, at the discretion of Central Command. Unless their actions are blatantly illegal and against the best interest of NanoTrasen, the crew, or the station, their orders are absolute.
----
=== '''The Emergency Shuttle''' ===

# The Emergency Shuttle is not to be called concurrently with an Emergency Response Team. Pick one or the other.
# In the event of hostile biohazard lifeforms appearing on the station (such as deadly viruses, or Terror Spiders), Central Command is to be notified by red phone or fax before the Emergency Shuttle is called. Failure to do so may lead to the shuttle being recalled in order to enforce quarantine. CC may deny emergency shuttle requests to handle the biohazard.
# In the event that the Emergency Shuttle is called, all personnel are to assemble at the emergency shuttle docking area at 5 minutes before arrival.
# Forcing an early departure of the Emergency Shuttle is not permitted.
# All personnel in critical condition are to be given emergency aid ASAP.

Mnemosyne

2025-12-12T21:49:56Z

Grapegifter: Spoiler

'''CENTRAL INTELLIGENCE DIVISION'''

'''SUBJECT BRIEFING — EYES ONLY'''

'''CRONUS CLEARANCE RELEASE REQUIRED'''
----'''SUBJECT DESIGNATION:''' MNEMOSYNE

'''Civilian Identity:''' Carter Avrom

'''Current Status:''' Active—HIGH PRIORITY THREAT

'''Affiliation:''' OUROBOROS (Codename: The Syndicate)

'''Former Allegiance:''' Stellar Vanguard Solutions (SVS), Internal Intelligence Wing

'''Clearance Revoked:''' CRONUS-2 (As of Collapse Protocol Γ-07)
----

=== I. HISTORICAL PROFILE ===
Carter Avrom—callsign '''MNEMOSYNE'''—was a senior intelligence strategist under the now-defunct mercenary organization '''Stellar Vanguard Solutions (SVS)''', serving in a black-tier subnetwork known as [REDACTED], focused on internal stability, data containment, and counter-espionage.

During the [REDACTED] '''Split''', when ideological fractures tore SVS into competing successor entities, Avrom defected. He is one of the '''founding architects of the insurgent group OUROBOROS''', now codenamed '''The Syndicate''' by Central Command. Unlike other dissidents, Avrom’s break was deliberate and clinical—he extracted core memory filtration routines, full-body psychometric indexing protocols, and fragments of early SEKER scaffolding from the PSO development archive.

His current designation—'''MNEMOSYNE'''—originates from intercepted Syndicate ciphers and is believed to signify his role as custodian of memory and identity within the Ouroboros hierarchy.
----

=== II. THREAT PROFILE ===
MNEMOSYNE is confirmed to be the '''first and only individual''' to '''fully reverse PSO memory suppression''', including long-term memory blackouts initiated by the SEKER Core. The technique, now referred to in internal threat logs as the '''Mirrorpath Loop''', allows subjects to recover pre-scan consciousness, bypassing fail-safe neurological partitions built into both the OSIRIS Trigger and the SEKER Core’s Reflection Layer.

'''This development is classified as a CRONUS class breach of security.'''

Current intelligence confirms MNEMOSYNE is deploying Mirrorpath on '''selected Ouroboros leadership and combat operatives''', effectively creating resistance personnel immune to PSO memory restraints.<blockquote>'''WARNING:''' Mirrorpath restorations appear to confer psychogenic memory reinforcement, resulting in more aggressive behavioral loops and increased susceptibility to Ouroboros brainwashing. These agents exhibit a loss of their primary '''Identity Anchoring'''—a state where restored memories fuse with imagined ones, deferring their allegiance to The Syndicate.</blockquote>
----

=== III. OBJECTIVES & STRATEGIC MOTIVATION ===
Carter Avrom’s defection was rooted in ethical dissent. Once a senior SVS strategist, he became disillusioned with Central Command’s increasing reliance on identity control systems and their entanglement with external corporate interests—particularly '''NanoTrasen (NT)'''. He viewed NT’s presence in cloning and infrastructure operations as emblematic of a deeper failure: the abandonment of autonomy in favor of control.

His core opposition lies with the '''Pantheon Subject Optimization (PSO)''' system, which he considers a violation of fundamental identity. The use of memory erasure, behavioral overrides, and manufactured loyalty are—by his own words—"a dismantling of the soul under the guise of service."

Through the creation of '''Mirrorpath''', MNEMOSYNE seeks to:

* '''Sever Central Command's influence from blacksite operations, specifically [REDACTED]'''
* '''Expose memory manipulation as a tool of suppression.'''
* '''Challenge the authority of Central Command.'''
* '''Rescue and reawaken the identities of formerly erased agents.'''

----

=== IV. THREAT LEVEL & COUNTERMEASURES ===
'''THREAT LEVEL:''' OMEGA BLACK

'''ACTIVE COUNTERMEASURES:'''

* Initiate recursive cognitive collapse algorithms on '''any''' operatives exposed to MNEMOSYNE-linked thought signatures.
* Deploy Venator Mortis agents with proper Cortex Partitioning to avoid unauthorized mnemonic reactivation.
* Prioritize destruction of Mirrorpath nodes embedded in Syndicate-controlled systems.
* Investigate the possibility of '''MNEMOSYNE clones'''—Syndicate may be running unauthorized PTAH Frame cycles.

<blockquote>'''EMERGENCY ACTION PROTOCOL:'''

Any instance of Mirrorpath presence within Central Command facilities authorizes use of '''Dissolution Protocols.'''</blockquote>
----

=== V. CLOSING REMARKS ===
Carter Avrom represents a philosophical and technological threat to the foundation of PSO-dependent operations. His existence undermines one of Central Command’s highest priorities: control through memory regulation. As such, MNEMOSYNE is not merely a traitor—he is a danger to this very organization's founding.

'''Immediate neutralization is authorized and all resources are assigned to his dissolution.'''
----'''Filed By:''' Division Chair ILLYTHIA

'''Validated By:''' CRONUS Command Oversight

'''Timestamp:''' ██/██/████ [REDACTED]

'''Current Clearance Level:''' GAMMA — EYES ONLY

Pantheon Subject Optimization

2025-12-12T21:20:02Z

Grapegifter: Time change

🜏 '''HOUSE OF THE NINE – CENTRAL SPECIAL OPERATIONS DIVISION'''

'''ZETA-LEVEL STRATEGIC TECHNOLOGY REPORT'''

'''BLACKSITE ELYSIUM – PANTHEON SEAT I'''

'''Author:''' ''Grand Admiral Renard Travis''

'''Clearance:''' ''CRONUS-Level Only – Seal 001-ΔΧΘ''

'''Subject:''' ''Pantheon Subject Optimization (PSO) System – Performance Assessment''

'''Date:''' [REDACTED]
----

=== I. Executive Summary ===
After years of theoretical development, failed iterations, and ethically questionable fieldwork under the former AEGIS Directive, I am proud to confirm that the ''Pantheon Subject Optimization'' (PSO) system has exceeded all performance expectations under live operational conditions.

All six active █████ ██████ operatives — PANACEA, HERCULES, PROMETHEUS, HEPHAESTUS, ARTEMIS, and CHARON — have undergone full or partial PSO cycle integration. Neural integrity, memory threading, and physiological continuity are within 0.03% deviation of predicted tolerance. Operatives have sustained trauma, death, and even full body dissolution, only to return operational within protocol windows. At this time, all neural mapping is at peak functionality.

We have, in no uncertain terms, rewritten the doctrine of soldier mortality. No doubt this will be of use to those on the outside, I hear CID has already gotten wind of the new cloning program. It will have to be rolled out to the stations, to the public.

We will provide them with the basic framework, no need for them to know what really goes on at Elysium. Scarlet Lightweaver will be remembered internally for their contributions, and the world will think she developed it on her own.
----

=== II. Internal System Framework: ===
'''Codename: Pantheon Subject Optimization (PSO)'''

''A closed-system continuity architecture designed exclusively for elite assets under CSOD authority.''

'''Subsystem Breakdown:'''

* '''PTAH Frame''' (''Physical Template & Hosting Array''): Bio-cultivation chambers produce fully augmented clone frames, identical in form, neurology, and biochemistry to each operative’s baseline. Structural durability enhanced by synthetic graftwork and immune stabilization overlays.
* '''SEKER Core''' (''Sanctioned Experience & Kernel Encoded Repository''): Deep-resonance neural lattice stores operative cognition, procedural memory, tactical instincts, and emotional response logs. Encryption layers include recursive personality indexing to maintain identity cohesion across reactivations.
* '''OSIRIS Trigger''' (''Operational Soul Initiation & Reintegration Sequence''): Final stage of operative revival. Synchronizes consciousness thread with the PTAH frame, invoking full personality reintegration and neural activation. Current OSIRIS sync rate averages under 9 seconds post-warm.

----

=== III. External Cover Designation: ===
To maintain secrecy, public references to PSO utilize a medically sanitized nomenclature:

* '''System:''' ''Procedural Somatic Override''
* '''Ptah Array:''' ''Clone cultivation framework''
* '''Seker Module:''' ''Storage of neural backups''
* '''Osiris Link:''' ''Activation and consciousness awakening protocol''

These terms have been embedded within civilian trauma recovery and experimental rehabilitation frameworks, allowing cover deployment in public documentation and outer-division facilities without raising scrutiny. Civilian systems have also been downgraded, with cheaper alternatives.
----

=== IV. Observational Data & Psychological Continuity ===

* '''Memory Threading Stability (Average):''' 99.9%
* '''Observed Drift:''' Negligible to undetectable
* '''Clone Generation Integrity:''' No instability through ██ cycles.
* '''Latency Post-Trigger:''' Sub-10 seconds in all confirmed OSIRIS activations
* '''Cognitive Reversion Cases:''' None to date

Operatives report no subjective sense of “discontinuity” post-cycle. Field efficiency is unaffected by death or catastrophic trauma. While civilian clones only appear functional for up to 3 years, actual mortality rates near the Null Tear show replacement times far sooner than that. As of now they don't have a clue how short their lives really are.
----

=== V. Personal Remarks ===
I gave this project the name ''Pantheon'' for a reason.

We are no longer reviving soldiers. We have achieved immortality, we are manufacturing gods.

My own clone integration remains nearly perfect after thousands of cycles, should the program be maintained, I shall have oversight of the division for eons.

Let this document serve as confirmation that '''█████ ██████''' and its integration with PSO will shape the next era of warfare. I will not tolerate compromise, regression, or the dull-witted morality of the Central Operations Council, nor will I allow these operatives to be brainwashed or compromised unless absolutely necessary. If it has to be, we will start a war within our own ranks, like the SVS days.

Should any opposing command attempt to decommission this initiative, HADES-666-FALL will trigger, sending us all back to the stone age. Absolute secrecy of ████ █████ remains paramount.

– ''Grand Admiral Renard Travis''

''CRONUS SEAT I – Keeper of the Pantheon''
----'''Filed under ZETA BLACK // Echo Seal: 𝛀-01 – ABSOLUTE OVERRIDE PROTOCOLS ENGAGED'''

''Attempted duplication or unauthorized access will result in memory disintegration and neural branding.''

Ouroboros Operatives

2025-12-12T21:09:09Z

Grapegifter:

SOP

2025-12-02T23:13:57Z

Grapegifter:

= Standard Operating Procedures =
These SOP (Standard Operating Procedure) provide instructions for the station crew during normal shift operation. These may be changed by the station's Captain at any time. This should not be a considered a checklist of conditions to fire someone over, and should not be rigidly followed to the letter in detriment of circumstances and context. SOPs can be malleable if the situation requires, and the decision to punish personnel for breaching it ultimately falls onto the relevant Head of Staff for Department Members; or Captain for the Head of Staff.

'''''While these SOPs may come with in character punishments on the Alpha (MRP) server for non-command members, repeated intentional disregard on the Beta (MRP+) server may be grounds for a role ban from the department. Repeated intentional disregard for SOPs by command members on either server may also result in a role ban (see [[Command SOP]]).'''''

== How do I use an SOP? ==
You should read and make sure you understand the SOP before beginning any work on the station. If you have any questions on the SOP, first consult your nearest department head. Failing this, department heads and captains are permitted to contact Central Command with any issues or changes they'd like to make. The station's NanoTrasen Representative, or nearest Internal Affairs Agent should be considered an authority on the SOP as well, and are permitted to contact Central Command directly regarding SOP violations, and disregard of SOP by command members.

== How does an SOP help '''me'''? ==
These SOPs give you a code of conduct to abide by. You should follow what is in the following documents, and repeated violations may result in contract termination, or removal from the sector.

Standard Operating Procedures give power to command to help determine what their department workers should be doing. It will help you guide the prospective hiring and firing of crew members.

Similarly, these SOPs give power to the crew, by allowing you to abdicate and fire relevant command members if they are not behaving properly.

== [[General SOP]] ==
This SOP is for general crew members, and applies to all crew on the station. This should be the first thing you read once you arrive on station.

== [[Command SOP]] ==
This SOP is for command members and their expected behavior. You are to be held to a higher standard than normal crew, and must act as such.

== [[Security SOP]] ==
This SOP dictates the behavior of the station's security department. All crew members should review this SOP to ensure space law is being interpreted correctly.

== [[Service SOP|<s>Service SOP</s>]] ==

== [[Legal SOP|<s>Legal SOP</s>]] ==
This SOP dictates the behavior of the station's Internal Affairs Agent, and Magistrate.

== [[Engineering SOP]] ==
This SOP is to assist the station's engineering department in setting up station power, and general conduct for station emergencies.

== [[Medical SOP]] ==
This SOP is to assist the station's medical team in crew treatment, and provide guidelines on handling station crew after death.

== [[Cargo SOP]] ==
This SOP is to assist the station's cargo and salvage team, and give them guidelines on how to best supply the station with materials.

== [[Science SOP]] ==
This SOP is to assist the station's science team in '''SAFELY''' conducting research on board the station.

== [[NanoTrasen Employee SOP]] ==
This SOP is for the NanoTrasen Representative, Blue Shield Officer, and ERT squads.

Dwarfs

2025-11-25T05:41:37Z

Grapegifter: Started for real this time

(Grapegifter is currently working on dwarf lore, check back later.)
{{Template:SpeciesPageHeader
|speciesName = Dwarf
|img = Dwarf.png
|playability = Round Start
|generalFeatures = <nowiki> Speak with a dwarfish accent. </nowiki>
|positiveFeatures = <nowiki> Higher alcohol tolerance and can be healed by drinking alcohol. </nowiki>
|negativeFeatures = <nowiki> none</nowiki>
|weaknesses = <nowiki> none </nowiki>
|resistances = <nowiki> none </nowiki>
}}

== Dwarves ==
While there are many sub-races of Dwarves, the Dwarven race is consistently characterized by its unique industriousness. They make excellent engineers, and are well suited to tinkering, mining, stone-crafting, jewelry making, and general craftsmanship. The Dwarves insist this characteristic is due to their historical upbringing. Being stranded on Abumas, forced to either work, or starve. Over time, they learned how to conserve materials, and implement practices across generations to refine their crafts.

This is made easier by their home planet Abumas, which is very earth-like in its structure in many ways, and habitable to most species. Across Abumas can be found vast deserts, large oceans, lush jungles, and a favorite of the Deepdwarves, large, underground, interconnected cave systems. It is unknown how these cave systems became so large and expansive, though this has not stopped the Dwarves, and their cousins the Deepdwarves from exploring their depths. At odds with this is a section of the planet characterized with large, sharp rock spires, reaching far up into the sky.

Abumas's proximity to the Null Scar quickly brought the Dwarves into contact with NanoTrasen. The Dwarves were already a space-faring species upon first contact, and aided the early NanoTrasen fleets greatly in their navigation of the Starlight sector.

== Biology ==
Subraces: Subterranian Dwarves, Deepdwarves, Steppedwarves, Oceandwarves, Spiredwarves, Mountaindwarves, Jungle dwarves, forest dwarves

== Culture ==

=== History ===
Early Dwarven history seems to share many similarities to that of human history. Tales of large, humanoid structures seem to predate depictions of early Dwarven construction. Historians argue about the origins of the Dwarven race, with Dwarven Sagebeard insisting that they share a common ancestor with humans. Sagebeards tell the story of how their ancestors were deposited by an unknown force onto their home planet Abumas near the Null Scar, and how the influence of the Scar changed their very biology. NanoTrasen's official statement is that the Dwarves have evolved separately from Humans, and their biology only vaguely resembles Human biology. One thing that is agreed upon by both of them, the Dwarves were among the first of the "extra-terrestrial" races to be contacted by NanoTrasen.

Young Dwarves are often taught of how their ancestors came to Abumas, the name of the planet coming from the curse the first chieftain spat upon their arrival. Since then, Sagebeards have been employed to track the history of each clan, recanting the histories endlessly to beardlings, those trained to become the next Sagebeards of their clan.

=== Religion ===
The dwarves widely worship a pantheon of gods, each god pertaining to an aspect of their lives. Depending on where they live, each set of clans may favor one particular deity over another. This has lead to conflict in the past.

=== Family and Community ===
Clans - Based on area they live in

Greater respect for dwarves that live deeper under sea level?

=== Fashion and aesthetics ===
Dependent on clan

== Society ==

=== Governments ===

=== Economy ===

== Trivia ==

*

Server rules (Starlight)

2025-11-25T04:00:15Z

Grapegifter:

{{OOC}}

= Server rules =
The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server.

Players are also expected to understand [[Metashield]].

If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server.

For in-universe laws and rules check [[Corporate Law]] and [[SOP]].

Remember, the rules and examples given here are NOT exhaustive. (See [[Server rules (Starlight)#Rule 1|Rule 1]])

The servers are strictly '''+16 only''', unless stated otherwise in the server description that they are '''+18.'''

== Rule 0 - Be respectful ==
Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind.

Harassment or toxic behavior, including but not limited to:

* Racism, sexism, discrimination
* Excessive talk/glorification of self-harm
* Talking about Real Life politics
* Targeting the same player across rounds
* Insulting other players in OOC/LOOC

Will not be tolerated and may result in a permanent ban.

'''Mhelp (Mentor Help)''' lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through '''IC (in character)''' or '''OOC/LOOC (out of character)''' means and should not be the first option.

'''Ahelp (Admin Help)''' facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is ''not'' for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences.

== Rule 1 - Respect Admin decisions ==
Above all else, if an admin is telling you to stop doing something, '''stop doing it'''. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first.

Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation.

Example(s) of this rule being broken:
{| class="wikitable"
|"There isn't a rule saying I can't!"
|-
|"None of the other players had a problem with it!"
|-
|"No one had a problem with it last time!"
|}

== Rule 2 – No Griefing, Bug Abuse or Exploits ==
Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as:

* Releasing the Tesla/Singularity
* Large-scale station destruction (department-size or larger)
* RDM (Random Death Match)
* Intentionally Plasma or Tritium flooding the station

May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding.

Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord.

==== AFK Farming & Antag Rolling ====

* AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game.
* Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted.

== Rule 3 – Abide by Medium Roleplay Standards ==
This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. '''You are not meant to play the round to "win" the game''', but rather to engage in roleplay scenarios with other players.

Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the [[Metashield]]—such as the existence of nuclear operatives—must not be remembered.

==== Gameplay Violations ====

* '''Powergaming''' – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively.
* '''Metagaming''' – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game.
* '''Metagrudging/Metafriending''' – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
* '''Mixing IC and OOC chat''' – In-character talk should not be placed in OOC chat, and vice versa during the round.
* '''English Only''' - Any form of communication in-game is to be expressed in English exclusively.
* '''Metacomms''' - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand.

==== Behavior & Roleplay Conduct ====

* '''Self-harm/killing''' – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually.
* '''End-of-Round Griefing (EORG)''' – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification.
** Defending yourself is an example of in-character justification, as is sec apprehending known criminals.
** Antags cannot complete their goals after the results screen, and so should not seek out any targets. '''RED MEANS YOU FAILED, IT’S TOO LATE.'''
** Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason.
* '''Random Deathmatch (RDM)''' – Attacking players without escalation or valid reasoning is prohibited.
* '''Memory loss when unconscious''' – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events.
** While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation.
** De-converted Revolutionaries forget what happened while they were brainwashed.
** Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge.

==== Avoiding Punishment & Fair Play ====

* '''Leaving To Avoid Punishment (LTAP''') – Logging out after receiving an Ahelp to attempt to dodge a ban is not allowed. Similarly, ghosting after you've been caught by security and then continuing to play, using new life or ghost roles, is not allowed. You may only leave if you are leaving the server. Exceptions will be made for perma prisoners, who may utilize the system within reason. If a player must leave due to real-life reasons under these conditions, they should make an LOOC message to inform the players around them, or state it in Ahelp.

== Rule 4 – Escalation of Force Must Make Sense ==
Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels.
Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: Verbal > Non-lethal > Lethal. Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth.

Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target.

Examples of reasonable escalation:
{| class="wikitable"
|Shoving the clown for slipping you
|-
|Punching someone and starting a fist fight over being shoved once.
|-
|Punching or stunning a Security Officer after they attempted to arrest you.
|-
|As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things.
|-
|As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton
|-
|As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm, you order them to drop it and they refuse.
|-
|As a command member, using your flash on a trespasser after you've told them repeatedly to leave.
|}
Examples of unreasonable escalation:
{| class="wikitable"
|Critting the clown for slipping you once
|-
|Stabbing someone to crit with a knife because they shoved you once.
|-
|Shooting a Security Officer with lethals because they attempted to arrest you.
|-
|As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen.
|-
|As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders.
|-
|As a command member, shooting someone with a firearm after you've told them repeatedly to leave.
|}

== Rule 5 – Antagonists Must Follow MRP logic ==
Antagonists should only take actions that advance their objectives. Failure to do so may be considered a breach of MRP logic and result in punishment. Team antagonists '''must''' work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…).

Antagonists are required to follow escalation rules when not dealing with their target, but should '''attempt''' to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives.

Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.)

Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station, but '''should follow their objectives:'''
{| class="wikitable"
|Space Dragon
|-
|Nuclear Operatives/Lone Operatives
|-
|Abductors
|-
|Wizard
|-
|Rat King
|-
|Space Ninja
|-
|Revolutionaries (after gaining sufficient strength to overthrow the station)
|}
Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew.

=== Zombies ===
Initial Infected are allowed to sabotage the station as long as they follow all server rules.

However, once you are a zombie:

* You may only destroy the station to reach living organisms you can see or hear.
* You may not attack lights or power sources.

== Rule 6 – Your Character Must Make Sense ==
Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience.

==== Character Identity & Naming Rules ====

* Names and surnames must align with the context and standards of the setting.
* Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish").
* Your character should act appropriately for their role and should not behave erratically or neglect responsibilities.
* Your character cannot intentionally duplicate the name and likeness of another player’s character.
* Names cannot include calls for violence, or anything that violates Rule 0.

===== Exceptions =====

*Silicon, Clown, and Mime names are allowed to contain references. Politically charged and vulgar reference names are not allowed.
*Nicknames are allowed within apostrophes, and should be appropriate for a corporate environment. Nicknames may contain indirect references. The format for nicknames depends on species, but in general follows one of these formats:
*# Givename 'Nickname' Surname
*# 'Nickname' Surname
*# Givenname 'Nickname'

==== Roleplay & Behavioral Expectations ====

* Real-world topics, such as current events and real-life politics, should not be discussed.
* Players should fulfill their assigned duties—for example, security should not randomly distribute weapons.
* Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action.

== Rule 7 - No Self-Antagonism ==
Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include:

* Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification.
* Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation.
* Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification.
* Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion.

This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions.

'''Examples of reasonable in-character Space Law violations:'''
{| class="wikitable"
|Unlocking weapons crates to defend against a severe station-wide threat.
|-
|Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry.
|-
|Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost.
|-
|Trespassing to complete necessary job tasks after an extended wait for access.
|-
|Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws.
|-
|Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available.
|-
| Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.)
|}

== Rule 8 – No Validhunting ==
Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are '''not''' considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges.

Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense.

Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats.

Command should not facilitate valid hunting outside of necessity and should ask security regarding such.

Examples of '''Validhunting''':
{| class="wikitable"
|As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command.
|-
|As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected.
|-
|As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space.
|-
|As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation.
|-
|As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago.
|-
|As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband.
|}
Examples of this rule being followed:
{| class="wikitable"
|As a Salvage Specialist, boarding the station to eliminate station-wide threats '''ONLY''' after being asked to assist.
|-
|As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them.
|-
|As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship.
|-
|As an assistant, reporting a person you saw wearing contraband over the radio.
|-
|As an assistant, defending yourself or another person from an attacker until they retreat or you crit them.
|}

== Rule 9 - Interacting with SSD/AFK players ==
SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character. AFK players are those who remain in-game but are unresponsive to interactions around them.
Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action.

Players who have been AFK for a significant amount of time will be automatically transported to a cryo tube.

==== General Rules for SSD/AFK Interactions ====

* You may not interact with SSD players unless doing so falls into one of the following cases:
** Moving them to a cryo-pod
** Providing medical assistance
** Rescuing them from immediate danger (e.g., carrying them out of a fire)
* If a player with SSD has a Wanted status, they may not be detained without administrator permission.
** However, if the player went SSD during or immediately after detention, the arrest may proceed.
* Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun.
* If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm.

==== Restrictions on SSD Item Theft ====

* Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items.
* Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen.

== Rule 10 – Erotic and Sexual Content is Forbidden ==
Due to Starlight's 16+ policy, minors must be assumed to be present on the server at all times.

Erotic and sexual content is strictly prohibited in all forms and mediums. This includes any erotic roleplay (ERP) or comments involving descriptions, mentions, or enactments of sexual acts. This includes text, images, and any other form of content.

Basic safe-for-work interactions between characters such as hugging are allowed. Romantic relationships should not become the focus of the game for you or anyone else.

==== Clarifications on Acceptable Language ====
In-character insults are not considered erotic or sexual, as long as they do not become excessive or extreme. Some examples of acceptable insults:
{| class="wikitable"
|"Fuck you" - insult
|-
|"You're a motherfucker" - insult
|-
|"How about you eat me instead?" - Response to an unreasonable request
|}
It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines.

==== Legal Disclaimer ====
In accordance with USA Child Protection and Obscenity Enforcement Act, violations of this law will result in an immediate, permanent ban without possibility of appeal.

== Rule 11 - New Life ==
The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion.

Upon respawning as a new character, you forget everything you knew as your past character or ghost. This means:

* You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned.
* You may not interact with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over.
* You may not reference past events in any way. Your new character has no memory of them.

==== New Life Abuse examples: ====
{| class="wikitable"
|Spamming new characters to re-enter the round repeatedly.
|-
|Using New Life to intentionally roll for antagonist slots.
|-
|Using New Life to avoid in-character consequences, like a security sentence.
|-
|Using a new character to get revenge on a player who harmed you.
|}

== Rule 12 - Silicons and Thaven Rules ==
'''Silicons''' and '''Thaven''' are bound to their Laws and Moods respectively. They are expected to adhere to the following standards when following them.

=== Silicon Laws ===
* Laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must.
** Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply.
** A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules.

* Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it.

* You cannot request a law change, or willingly allow an unauthorized law change.
*# Authorized law changes as per [[Command SOP]] are to be allowed unless conflicting with your laws.
*# Changing of your laws is not considered a violation of your current laws. Future actions under a different law set should not be considered a violation of your current laws.
*# Lethal force may be used in the case of unauthorized law changes, as long as it is consistent with your current laws.

* You must remain consistent with your interpretation of your laws.

* Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew.
*# Zombies/Antags/Nuclear Operatives with '''proper ID''' are to be considered crew.
*# '''Visitors are not crew''' until they have been hired by HoP. [The V icon]
*# '''Prisoners''' '''are not crew''' and you should not listen to their orders. [The bars icon]

* Crew harm refers to physical harm, prioritized by immediacy and likelihood.

* You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason.

=== Thaven Moods ===

* Moods are compulsions that Thaven should try to follow. If your mood explicitly requires you to break server rules, you may.
** Absence of a relevant mood is not an excuse to break server rules. If you do not have a relevant mood, the server rules still apply.
** A vague mood does not normally let you break server rules. Ahelp first if you are confused, or believe your mood gives you reason to break server rules.
* If a mood can not be satisfied, it causes distress to Thaven. This distress is not extreme, and does not inherently justify rule breaking, but may allow gradual escalation that does not cross into murder or mass sabotage.
* Attempting to break the law in a way that directly leads to you being able to fulfill a mood may be allowed, within reason;
** Breaking into a department to obtain something or make an order in Cargo that they refuse would be allowed.
** Murdering the CE to use their stamp to approve paperwork giving you access to the Supermatter room would not be allowed.
* Some leniency for Rule 13 may be allowed based on mood, but those who have been hired to Command, Security, and NanoTrasen jobs on stations are expected to be experienced in their work, meaning they have earned this rank while managing their moods for potentially years. They should understand how to juggle the responsibilities of their jobs with the fickle and often arbitrary compulsions of their moods in a way that would not get them fired.

== Rule 13 - Command, Security, and Whitelist Expectations ==
Players in Command or Security roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. In these positions your character must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles.

Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions.

This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles.

==== Expectations ====

* Command positions are required to adhere to SOP, ensuring fair leadership and proper department management.
* Security positions are required to adhere to SOP and properly enforce Corporate Law, ensuring fair treatment of criminals and an enjoyable player experience.
* Whitelisted positions are required to adhere to SOP, maintaining the integrity of specialized roles and demonstrating strong roleplay skills.
* Proper attire should be worn at all times—command, security, and whitelisted roles should be dressed appropriately for their positions.

==== Examples of Punishable Actions ====
{| class="wikitable"
|Head of Personnel granting All Access unnecessarily, violating SOP guidelines.
|-
|Overly abusive department heads mistreating subordinates or disregarding SOP duties.
|-
|Warden giving a cooperative criminal a maximum sentence on the first offense.
|-
|-
|Complete neglect of SOPs, acting outside the expected responsibilities of the role.
|-
|General LRP behavior or violating Rule 3 regarding MRP logic.
|}

==== Cadet Exemption ====
* Security Cadets are still learning and so are exempt from this expectation.

== Rule 14 - Continuity Guidelines ==
Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption.

You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. Placing yourself in a cryopod will allow you to remember details up until you’ve entered the cryopod.

'''Any information that is [[Metashield|Metashielded]] is forgotten between shifts''', and is wiped from your clone's memory.

IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift.

You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent.

Examples of things you '''can''' remember:
{| class="wikitable"
|Social interactions with another character, such as getting drinks at the bar or even getting into an argument
|-
|Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job
|-
|The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons
|}
Examples of things you '''can't''' remember:
{| class="wikitable"
|Joe the Botanist was a Syndicate who stole the Captain's Jetpack
|-
|Nuclear Operatives attacking the station
|-
|CentComm calling Code Epsilon and killing a bunch of people on the station
|-
|Witnessing a Hollow body or seeing a Changeling eat someone
|-
|As NanoTrasen Representative, remembering that last shift had Nuclear Operatives
|}

Template:OOC

2025-11-25T04:00:08Z

Grapegifter:

<div style="width:100%;border:1px solid #CC5500;border-radius:0.9em; background:#1b1b1f">
<div style="background:#CC5500;;font-size:1.5em;text-align:center;border-bottom:1px solid #CC5500;border-top-left-radius:0.59em;border-top-right-radius:0.59em;>'''Out Of Character Content'''</div>
<div style="padding:12px 14px;color:white;text-align:center;">
:This page references subject material that is considered out of character information. Please take care when referencing this content in-character.
</div>
</div>

Template:OOC

2025-11-25T03:59:23Z

Grapegifter:

Template:OOC

2025-11-25T03:58:04Z

Grapegifter:

Template:OOC

2025-11-25T03:25:19Z

Grapegifter:

Template:OOC

2025-11-25T03:23:50Z

Grapegifter:

<div style="width:100%;border:1px solid #CC5500;border-radius:0.9em; background:#1b1b1f">
<div style="background:#CC5500;;font-size:1.5em;text-align:center;border-bottom:1px solid #CC5500;border-top-left-radius:0.59em;border-top-right-radius:0.59em;>'''Out Of Character Content'''</div>
<div style="padding:12px 14px;color:white;">
:This page references subject material that is considered out of character information. Please take care when referencing this content in-game.
</div>

Templates

2025-11-25T03:22:46Z

Grapegifter:

This page is a table of contents to contain all templates in one central location 
a good template page should contain documentation on what all it's parameters do within it's page
== Doc ==
[[Template:Doc]]
{{Doc}}

== OOC ==
[[Template:OOC]]
{{OOC}}

== RolePageHeader ==
[[Template:RolePageHeader]]
{{RolePageHeader}}

== ModernButton ==
[[Template:ModernButton]]
{{ModernButton}}

== ModernFrame ==
[[Template:ModernFrame]]
{{ModernFrame}}

== SpeciesPageHeader ==
[[Template:SpeciesPageHeader]]
{{Template:SpeciesPageHeader}}

== LorePageHeader ==
[[Template:LorePageHeader]]
{{LorePageHeader}}

Template:OOC

2025-11-25T03:21:03Z

Grapegifter: Created

<div style="width:100%;border:1px solid #CC5500;border-radius:0.9em; background:#1b1b1f">
<div style="background:#CC5500;;font-size:1.5em;text-align:center;border-bottom:1px solid #CC5500;border-top-left-radius:0.59em;border-top-right-radius:0.59em;>'''Out Of Character Content'''</div>
<div style="padding:12px 14px;color:white;">
{{{{SUBJECTPAGENAME}}/doc}}</div>
<div style="border-bottom: 1px solid #CC5500;"></div>
:This page references subject material that is considered out of character information. Please take care when referencing this content in-game.
</div>

Dwarfs

2025-11-11T18:41:59Z

Grapegifter:

Dwarfs

2025-11-11T18:39:57Z

Grapegifter: Smol update

Ouroboros Operatives

2025-11-11T15:36:11Z

Grapegifter: Creation

Dwarfs

2025-11-11T05:27:52Z

Grapegifter: Dwarves in progress - notes?

Nullspace

2025-11-11T04:25:11Z

Grapegifter: Created page with "Nullspace is the tenuous tie between realities within the Null Scar. Not much is known at this time, other than it contains reality bending properties."

Nullspace is the tenuous tie between realities within the Null Scar. Not much is known at this time, other than it contains reality bending properties.

Null Scar

2025-11-11T04:24:15Z

Grapegifter: Creation

The null scar is the tear in space seen behind the stations in the Starlight sector. It is as of yet unexplored, and is theorized to contain new physics defying discoveries, as well as a race of Scarborn.

Dwarfs

2025-11-11T04:21:56Z

Grapegifter: basic layout

Science SOP

2025-11-10T05:26:16Z

Grapegifter: Finished, for now.

= Starlight Science SOP =
Science is the primary focus of NanoTrasen's research stations, and is prioritized above other departments. This SOP is intended to assist the science department in conducting efficient and effective research aboard NanoTrasen vessels. Safe research should also be prioritized when convenient. Breaks of this SOP should be reported to the Research Director, or your nearest internal affairs agent or NT Representative.

== Research Guidelines ==
<blockquote>These procedures apply to all science members actively performing research, unless otherwise stated in their specific SOP.</blockquote>

=== Anomaly Research ===
1. Anomalies may not be generated without express permission from the Research Director for each anomaly generated. It is recommended that anomaly locators be on hand before generating an anomaly.

2. If there are any uncontained anomalies, an anomaly may not be generated.

3. Before generating an anomaly, the Research Director should inform command, and either make a radio announcement or station announcement of intent to generate an anomaly.

4. A generated anomaly must be searched for by at least two (2) members of the science department, unless there are less than 5 department members.

5. All anomalies must be stabilized and contained before being linked to an anomaly vessel.

6. The decision to collapse an anomaly may only be made by the Research Director, or Captain.

7. Department heads may request to have an anomaly removed if it significantly impedes their department's functions.

8. Anomaly vessels should be clearly marked with the type and location of the linked anomaly.

9. Anomalies that have taken a living host may be sustained or collapsed at the request of the individual crew member.

10. Anomalies with a living host that are to be sustained require an Anomalous Host Consent Form

=== Artifact Research ===
1. Artifacts should be contained in an appropriately protective area to minimize risk to crew from its activation.

2. Scientists should attempt to work in pairs in case of emergency.

3. Internals should be worn when working on artifacts, in case of accidental gas release.

4. Artifacts being transported out of science must be placed into an artifact container.

5. The Research Director must approve the sale or crushing of an artifact.

== Item Distribution ==
1. Items made from the protolathe, autolathe, and circuit imprinter require a proper item request form to be distributed to crew.

2. The [[Cargo SOP#Pre-Approved Materials List|pre-approved materials]] list in the Cargo SOP may be used to circumvent this requirement.

3. Violations of [[Corporate Law]] using these items may result in charges against the science department.

== Research Director ==
1. The Research Director should ensure that research is being done.

2. All research rewards unlocked by the Science department should be approved by the Research Director.

3. The Research Director is permitted to change the station AI's lawset, according to the [[Command SOP#AI|Command SOP]].

4. The Research Director is to be held accountable alongside the responsible science personnel for any accidents that harm crew members.

== Scientist ==
1. Scientists report directly to the Research Director.

2. Scientists should follow basic safety protocols when performing research, such as: wearing internals for gas release, wearing a bomb suit for potential explosions, hazardous material containment.

3. Scientists should communicate any potential hazards to the crew, such as: anomaly generation, potential explosions, loose artifacts, and other hazards.

4. Scientists should instruct any Research assistants near them, and are responsible for their safety.

5. Research Assistants should be utilized for dangerous experiments, and should be brought to the medical bay if injured.

== Research Assistant ==
1. Research Assistants report directly to the Research Director.

2. Research Assistants report to the nearest scientist, after the Research Director.

3. Research Assistants should complete any especially hazardous tasks, at the direction of a Scientist.

== Roboticist ==
1. Roboticists report directly to the Research Director.

2. Roboticists must obtain permission from the Hos or Captain, and the Research Director, before any combat oriented mechs or cyborgs can be created.

3. Roboticists should prioritize having an empty cyborg chassis at all times, in case of unplanned MMI insertion.

4. Roboticists must have an appropriately stamped and signed "Cyborg Conversion Form" before transferring a crew member into a cyborg.

5. Roboticists, at the direction of the Captain, HoS, or Research Director, may omit this form for prisoners, or the CMO and Research Director for bloated corpses.

== Appendix ==

=== Documentation & Paperwork ===
The following forms should be available for use within Science:

* '''Anomaly Research Log''' – records of generated anomalies, their status, and containment.
* '''Artifact Test Record''' – expected and observed effects of artifact activation.
* '''Cyborg Chassis Transfer Record''' – Documentation of chassis transfer, reasoning, prior and future chassis name.
* '''Cyborg Conversion Form''' – Records individual to be converted, the new chassis, authorization, and reasoning.
* '''Cyborg/AI Conversion Consent Form''' – Records explicit consent by crew member to be converted into a cyborg.
* '''Item Request Form''' – documentation of upgrades, distributed boards, and recipients.
* '''Anomalous Host Consent Form''' – written informed consent for crew hosting anomalies.

All forms should be filed promptly in departmental records and made available for review by the RD, Command, or Internal Affairs.

Science SOP

2025-11-10T05:23:21Z

Grapegifter: Nearly there

= Starlight Science SOP =
Science is the primary focus of NanoTrasen's research stations, and is prioritized above other departments. This SOP is intended to assist the science department in conducting efficient and effective research aboard NanoTrasen vessels. Safe research should also be prioritized when convenient. Breaks of this SOP should be reported to the Research Director, or your nearest internal affairs agent or NT Representative.

== Research Guidelines ==
<blockquote>These procedures apply to all science members actively performing research, unless otherwise stated in their specific SOP.</blockquote>

=== Anomaly Research ===
1. Anomalies may not be generated without express permission from the Research Director for each anomaly generated. It is recommended that anomaly locators be on hand before generating an anomaly.

2. If there are any uncontained anomalies, an anomaly may not be generated.

3. Before generating an anomaly, the Research Director should inform command, and either make a radio announcement or station announcement of intent to generate an anomaly.

4. A generated anomaly must be searched for by at least two (2) members of the science department, unless there are less than 5 department members.

5. All anomalies must be stabilized and contained before being linked to an anomaly vessel.

6. The decision to collapse an anomaly may only be made by the Research Director, or Captain.

7. Department heads may request to have an anomaly removed if it significantly impedes their department's functions.

8. Anomaly vessels should be clearly marked with the type and location of the linked anomaly.

9. Anomalies that have taken a living host may be sustained or collapsed at the request of the individual crew member.

10. Anomalies with a living host that are to be sustained require an Anomalous Host Consent Form

=== Artifact Research ===
1. Artifacts should be contained in an appropriately protective area to minimize risk to crew from its activation.

2. Scientists should attempt to work in pairs in case of emergency.

3. Internals should be worn when working on artifacts, in case of accidental gas release.

4. Artifacts being transported out of science must be placed into an artifact container.

5. The Research Director must approve the sale or crushing of an artifact.

== Item Distribution ==
1. Items made from the protolathe, autolathe, and circuit imprinter require a proper item request form to be distributed to crew.

2. The [[Cargo SOP#Pre-Approved Materials List|pre-approved materials]] list in the Cargo SOP may be used to circumvent this requirement.

3. Violations of [[Corporate Law]] using these items may result in charges against the science department.

== Research Director ==
1. The Research Director should ensure that research is being done.

2. All research rewards unlocked by the Science department should be approved by the Research Director.

3. The Research Director is permitted to change the station AI's lawset, according to the [[Command SOP#AI|Command SOP]].

4. The Research Director is to be held accountable alongside the responsible science personnel for any accidents that harm crew members.

== Scientist ==
1. Scientists report directly to the Research Director.

2. Scientists should follow basic safety protocols when performing research, such as: wearing internals for gas release, wearing a bomb suit for potential explosions, hazardous material containment.

3. Scientists should communicate any potential hazards to the crew, such as: anomaly generation, potential explosions, loose artifacts, and other hazards.

4. Scientists should instruct any Research assistants near them, and are responsible for their safety.

5. Research Assistants should be utilized for dangerous experiments, and should be brought to the medical bay if injured.

== Research Assistant ==
1. Research Assistants report directly to the Research Director.

2. Research Assistants report to the nearest scientist, after the Research Director

3. Research Assistants should complete any especially hazardous tasks, at the direction of a Scientist.

== Roboticist ==
1. Roboticists report directly to the Research Director.

2. Roboticists must obtain permission from the Hos or Captain, and the Research Director, before any combat oriented mechs or cyborgs can be created.

3. Roboticists should prioritize having an empty cyborg chassis at all times, in case of unplanned MMI insertion.

4. Roboticists must have an appropriately stamped and signed "Cyborg Conversion Form" before transferring a crew member into a cyborg.

5. Roboticists, at the direction of the Captain, HoS, or Research Director, may omit this form for prisoners, or bloated corpses.

== Appendix ==

=== Documentation & Paperwork ===
The following forms should be available for use within Science:

* '''Anomaly Research Log''' – records of generated anomalies, their status, and containment.
* '''Artifact Test Record''' – expected and observed effects of artifact activation.
* '''Cyborg Chassis Transfer Record''' – Documentation of chassis transfer, reasoning, prior and future chassis name.
* '''Cyborg Conversion Form''' – Records individual to be converted, the new chassis, authorization, and reasoning.
* '''Cyborg/AI Conversion Consent Form''' – Records explicit consent by crew member to be converted into a cyborg.
* '''Item Request Form''' – documentation of upgrades, distributed boards, and recipients.
* '''Anomalous Host Consent Form''' – written informed consent for crew hosting anomalies.

All forms should be filed promptly in departmental records and made available for review by the RD, Command, or Internal Affairs.

SOP

2025-11-10T04:49:01Z

Grapegifter:

= Standard Operating Procedures =
These SOP (Standard Operating Procedure) provide instructions for the station crew during normal shift operation. These may be changed by the station's Captain at any time. This should not be a considered a checklist of conditions to fire someone over, and should not be rigidly followed to the letter in detriment of circumstances and context. SOPs can be malleable if the situation requires, and the decision to punish personnel for breaching it ultimately falls onto the relevant Head of Staff for Department Members; or Captain for the Head of Staff.

'''''While these SOPs may come with in character punishments on the Alpha (MRP) server for non-command members, repeated intentional disregard on the Beta (MRP+) server may be grounds for a role ban from the department. Repeated intentional disregard for SOPs by command members on either server may also result in a role ban (see [[Command SOP]]).'''''

== How do I use an SOP? ==
You should read and make sure you understand the SOP before beginning any work on the station. If you have any questions on the SOP, first consult your nearest department head. Failing this, department heads and captains are permitted to contact Central Command with any issues or changes they'd like to make. The station's NanoTrasen Representative, or nearest Internal Affairs Agent should be considered an authority on the SOP as well, and are permitted to contact Central Command directly regarding SOP violations, and disregard of SOP by command members.

== How does an SOP help '''me'''? ==
These SOPs give you a code of conduct to abide by. You should follow what is in the following documents, and repeated violations may result in contract termination, or removal from the sector.

Standard Operating Procedures give power to command to help determine what their department workers should be doing. It will help you guide the prospective hiring and firing of crew members.

Similarly, these SOPs give power to the crew, by allowing you to abdicate and fire relevant command members if they are not behaving properly.

== [[General SOP]] ==
This SOP is for general crew members, and applies to all crew on the station. This should be the first thing you read once you arrive on station.

== [[Command SOP]] ==
This SOP is for command members and their expected behavior. You are to be held to a higher standard than normal crew, and must act as such.

== [[Security SOP]] ==
This SOP dictates the behavior of the station's security department. All crew members should review this SOP to ensure space law is being interpreted correctly.

== [[Service SOP|<s>Service SOP</s>]] ==

== [[Legal SOP|<s>Legal SOP</s>]] ==
This SOP dictates the behavior of the station's Internal Affairs Agent, and Magistrate.

== [[Engineering SOP]] ==
This SOP is to assist the station's engineering department in setting up station power, and general conduct for station emergencies.

== [[Medical SOP]] ==
This SOP is to assist the station's medical team in crew treatment, and provide guidelines on handling station crew after death.

== [[Cargo SOP]] ==
This SOP is to assist the station's cargo and salvage team, and give them guidelines on how to best supply the station with materials.

== [[Science SOP|<s>Science SOP</s>]] ==
This SOP is to assist the station's science team in '''SAFELY''' conducting research on board the station.

== [[NanoTrasen Employee SOP]] ==
This SOP is for the NanoTrasen Representative, Blue Shield Officer, and ERT squads.

Science SOP

2025-11-10T04:38:08Z

Grapegifter: Started

Dwarfs

2025-11-06T03:50:08Z

Grapegifter:

Service SOP

2025-10-30T03:39:17Z

Grapegifter: Blanked the page

Legal SOP

2025-10-30T03:38:57Z

Grapegifter: Blanked the page

Science SOP

2025-10-30T03:38:31Z

Grapegifter: Blanked the page

SOP

2025-10-30T03:37:25Z

Grapegifter: /* Legal SOP */

= Standard Operating Procedures =
These SOP (Standard Operating Procedure) provide instructions for the station crew during normal shift operation. These may be changed by the station's Captain at any time. This should not be a considered a checklist of conditions to fire someone over, and should not be rigidly followed to the letter in detriment of circumstances and context. SOPs can be malleable if the situation requires, and the decision to punish personnel for breaching it ultimately falls onto the relevant Head of Staff for Department Members; or Captain for the Head of Staff.

'''''While these SOPs may come with in character punishments on the Alpha (MRP) server for non-command members, repeated intentional disregard on the Beta (MRP+) server may be grounds for a role ban from the department. Repeated intentional disregard for SOPs by command members on either server may also result in a role ban (see [[Command SOP]]).'''''

== How do I use an SOP? ==
You should read and make sure you understand the SOP before beginning any work on the station. If you have any questions on the SOP, first consult your nearest department head. Failing this, department heads and captains are permitted to contact Central Command with any issues or changes they'd like to make. The station's NanoTrasen Representative, or nearest Internal Affairs Agent should be considered an authority on the SOP as well, and are permitted to contact Central Command directly regarding SOP violations, and disregard of SOP by command members.

== How does an SOP help '''me'''? ==
These SOPs give you a code of conduct to abide by. You should follow what is in the following documents, and repeated violations may result in contract termination, or removal from the sector.

Standard Operating Procedures give power to command to help determine what their department workers should be doing. It will help you guide the prospective hiring and firing of crew members.

Similarly, these SOPs give power to the crew, by allowing you to abdicate and fire relevant command members if they are not behaving properly.

== [[General SOP]] ==
This SOP is for general crew members, and applies to all crew on the station. This should be the first thing you read once you arrive on station.

== [[Command SOP]] ==
This SOP is for command members and their expected behavior. You are to be held to a higher standard than normal crew, and must act as such.

== [[Security SOP]] ==
This SOP dictates the behavior of the station's security department. All crew members should review this SOP to ensure space law is being interpreted correctly.

== [[Service SOP|Service SOP]] ==

== [[Legal SOP|<s>Legal SOP</s>]] ==
This SOP dictates the behavior of the station's Internal Affairs Agent, and Magistrate.

== [[Engineering SOP]] ==
This SOP is to assist the station's engineering department in setting up station power, and general conduct for station emergencies.

== [[Medical SOP]] ==
This SOP is to assist the station's medical team in crew treatment, and provide guidelines on handling station crew after death.

== [[Cargo SOP]] ==
This SOP is to assist the station's cargo and salvage team, and give them guidelines on how to best supply the station with materials.

== [[Science SOP|<s>Science SOP</s>]] ==
This SOP is to assist the station's science team in '''SAFELY''' conducting research on board the station.

== [[NanoTrasen Employee SOP]] ==
This SOP is for the NanoTrasen Representative, Blue Shield Officer, and ERT squads.

Central Command Operations

2025-10-17T17:39:39Z

Grapegifter: CBURN has had the acronym portion fixed.

[[File:CClogo.png|thumb|Central Commands Monographic Placard]]

== Overview ==
Central Command or CentComm refers to the staffing company NanoTrasen utilizes to man their stations in the Starlight Sector. All employees with the exception of the NanoTrasen Representative, Magistrate, and Blue Shield Officer are contracted through CentComm to work on NanoTrasen stations as needed.

CentComm itself is divided into 9 divisions and is composed primarily of bureaucrats and dignitaries. Most divisions correspond to departments on the station and are responsible for training the head and hiring contractors for their respective departments. The majority of CentComm's resources are dedicated to training these individuals, who in turn are expected to handle oversight and day to day operations on the stations. Brand new employees are provided a comprehensive pamphlet complete with infographics prior to their first shift. Pamphlets for those with cargo contracts are laminated. Since all heads of staff and captains receive extensive training through CentComm they are viewed as investments to be protected, while most other employees are easier to replace.

<blockquote>
:: "People are our business" - quote from recently hired CentComm Official 
</blockquote>

<blockquote>
:: "People became our business, personally, I preferred the war." - quote from senior CentComm official 
</blockquote>

=== Relationship to NanoTrasen ===
CentComm’s relationship with NanoTrasen can be tense, though highly beneficial for both parties. While NanoTrasen owns the stations and all equipment, CentComm’s assets are their employees. NanoTrasen receives all profits and products developed on their stations and in return pays CentComm to handle all matters concerning the people on the station. NanoTrasen may make station modifications or changes to SOP's based on CentComm's recommendations so long as it improves employee productivity.

Roughly 80% of CentComm’s gross earnings come from this contract with NanoTrasen. The remaining 20% comes from vendors who pay a premium to place their vending machines and advertisements on the stations.
<blockquote>
:: "Yeah not everyone was happy with the Consortium Business, I heard Carter took it pretty bad. Avrom never did have the stomach to follow through with the hard stuff."
:: "Shame, he might have been one of our best intelligencia."
:: "I'm glad to be rid of him and his crazy experiments. What's next? Mutant spiders?"
:::: ''- SVS employees shortly before the change to CC''</blockquote>

== Divisions ==

=== Central Administration Division ===
The Central Administration Division is largely responsible for communication, both within CentComm itself as well as with their employees on NanoTrasen stations. They transmit important announcements to stations, receive all communications from the station to CentComm and facilitate its delivery to the relevant division. They're also responsible for logging official documents, crises, and ensuring other divisions file their paperwork correctly.

 Core Responsibilities 
* Fax Routing - Receiving station faxes and forwarding them to appropriate divisions.
* Records & Archives - Maintain final records of code red events, major decisions, and documentation requiring multi-division coordination.
* Station Inspections - Often dispatched to inspect station operations, ensuring compliance with CC standards.
* Oversight and Neutrality - May call COC if multiple divisions conflict or require mediation.

<blockquote>"If I get one more piece of damned paperwork, I'm torching the whole place!" - ''[Retired] Captain James Caldwell''</blockquote>

=== Central Research Division ===
The Central Research Division trains the [[Research Director]], and hires all science department personnel. They are also in charge of the Research and Development of new technology, their work generally compliments the Central Security Division's more weapon focused research. Topics of interest include Xenoarchaeology, Alien ruins, New galactic species and xenobiological entities such as Xenomorphs, Changelings, and more.

 Core Responsibilities 
* High-Risk Experiments - Manages advanced or risky research projects.
* Cross Division Collaboration - Works with other divisions for integrated breakthroughs.
* Comprehensive Documentation - Maintains official CC R&D records for all major experiments.

:: "You're telling me Carter put what in a corpse?"
:::: - declassified audio from report to Senior Research Director 

=== Central Security Division ===
The Central Security Division is responsible for hiring security personnel, and training the [[Head of Security]]. Security cadets and officers receive extensive background checks, psychological evaluations and fitness tests all of which are administered through CSD. The department may also conduct their own research and testing on novel weapons.

 Core Responsibilities 
* ERT Deployment - Dispatches Emergency Response Teams or advanced security protocols if Code Red.
* Weapon Research & Testing - Designs/tests new weapons to bolster CC's defenses.
* Security Training - Trains Security if specialized tactics or advanced knowledge is required.
* Non-Security Combat Training - May assist the Central Cargo by training salvagers in self defense, and to handle weapons properly.

<blockquote>
:: "Do you believe you have anger issues?"
:::: "Yes."
:: "You're hired. Bonus included."
:::: - Leaked audio from a security interview 
</blockquote>

<blockquote>
:: "Hey whatever happened to lieutenant Summers, something about Elysium?"
:: "You're not supposed to talk about the dead, remember?"
:: "Yeah but curiosity eats at a guy, surely you know something."
:: "I don't know nothing, now shut up before you get us both scratched."
::
:::: - Overheard conversation between two security cadets
</blockquote>

=== Central Cargo Division ===
The Central Cargo Division is responsible for the procurement and distribution of materials both inside and outside of Central Command. This includes negotiating deals with external vendors, organizing transport to divisions with the Central Administration Division, and handling of funds. In addition to training QMs and hiring cargo technicians they also buy salvager contracts from third party scrapping companies. Some, though not all salvagers are hired from outside of CentComm.

 Core Responsibilities 
* Acquisition & Shipping - Sources external goods, arranges inbound/outbound cargo.
* Inventory Management - Oversees final distribution to CC divisions or station departments.
* Coordination - Coordinates with other divisions regarding relevant supplies. This may include refusing orders due to budget constraints or necessity.
* Record-Keeping - Logs shipments, ensures transparency via Central Administrative Division

<blockquote>
:: "Hey what do you think would happen if you tried to sell me in the crate?"
:: "Dunno, wanna try?"
:: "Hold my beer."
:::: - ''Last words of Cargo Technician Jeremy Dirk before his disappearance.'' </blockquote>

<blockquote>
:: "Central Security can't have every shiny new gun that comes on the market. Seriously, what are they going to do with them all, set up a museum?"
:::: - '' Resource Specialist discussing a recent requisition form'' </blockquote>

=== Central Intelligence Division ===
Not much is known about CID officially, however what is known is that they are the central intelligence gathering division for all of Central Command.

 Core Responsibilities 
* [REDACTED]

<blockquote>
:: [A loud metallic clanging can be heard] [Then faintly] H**i vix...hod**...mori meministi. [Followed by a loud radio screech]
::"Perplexing, and this is the last thing the audio feed caught?"
:::: - ''Unknown origin''</blockquote>

=== Central Engineering Division ===
The Central Engineering Division is responsible for hiring all individuals in the Engineering department as well as training the [[Chief Engineer]]. They also oversee large scale projects included but not limited to station expansions, shuttle design, and critical structural projects.

 Core Responsibilities 
* Catastrophic Support - Assist station engineering with massive damage or melt down scenerios.
* Infrastucture Projects - Builds advanced CentComm outposts, specialized shuttles, or large-scale constructs.
* Safety and Maintenance - Conducts major station inspections or coordinates repairs for significant engineering concerns.
* Training - May conduct on-station trainings for Technical Assistants, Engineers, and Atmospheric Technicians should the need arise or to further develop talent.

<blockquote>
::: “If it’s not broke, optimize it.”
::: "Sir, it is broke, someone torched the place." - ''After action ERT report''
</blockquote>

=== Central Domestic Division ===
The Central Civilian Division supports the service personnel and matters related to the service department. They train the [[Head of Personnel]], manage non-security, non-engineering "civilian" issues focusing on morale, service staff, and public relations. Additionally they have the unenviable responsibility to oversee negotiations with the Honkdignitaries.

 Core Responsibilities 
* Dispute Mediation - Addresses departmental unrest, fosters communication among service/civilian departments.
* Public Welfare - Issues policies to boost morale, organizes civilian events or announcements.
* Civilian Documentation - Oversees records for service staff or large-scale driven civilian initiatives.
* 'Funny Business' - Over sees negotiations and all contact with Honkdignitaries and followers of the Silent Father. May work with Central Security Division to ensure that Carnival Treaties are observed on station.

==== Subdivisions ====
This division is broken up into several Subdivisions with some specialized responsibilities within each:

* Janitorial
* Theological
* Historical
* Gastronomy
* Agricultural
* Diplomatic

<blockquote>
:: "Oh yeah, and don't hurt any of the civilians on this sortie."
:: "Why not?"
:: "We don't need a repeat of Station Zeta X-9. Last time you nearly brought the entire circus federation onto our heads. CDD was sorting out that fiasco for weeks."
:::: - ''Recording of <s>[REDACTED]</s> during ERT deployment <s>[REDACTED]</s>''</blockquote>

=== Central Medical Division ===
The Central Medical Division oversees hiring employees for the station's the medical bay. They issue licenses for practicing doctors and train the [[Chief Medical Officer]]. Additionally they may handle major station outbreaks of health crises.

 Core Responsibilities 
* Quarantine & Outbreak Management - Advises station CMOs on severe diseases.
* Cure Development - Works with Central Research if new cures or treatments are needed.
* Medical Standards - Maintains CentComm-level medical protocols and training, responding to large-scale crises.

<blockquote>
:: "And that's how I <s>lost my medical license</s> obtained my psychology degree."
:: "That doesn't explain the severe burns over 90% of your body."
:::: - ''Excerpt from Saltern X-45 medical report''</blockquote>

=== Central Special Operations Division (CSOD) ===
The Central Special Operations Division is officially controls CC's two elite units, the Emergency Response Teams and the Death Squad. While they have representatives on the Central Operations Council they do not vote unless there is a tie.

 Core Responsibilities 
* ERT Deployment - Sends ERT to station if crisis warrants urgent intervention.
* High-Level Training - Trains top-tier operatives for war-level or lethal missions.
* Deathsquad Management - Oversees last-resort lethal force under Code Epsilon.
* Coordinates with Central Intelligence to ensure appropriate actions are taken, including hunting down [REDACTED].

<blockquote>
:: "Call in Code Zeta."
:: "It can't possibly be that bad." 
:::: -<s> [Redacted] </s> 
</blockquote>

==== Emergency Response Team (ERT) ====
Emergency response teams exist for each department present on the station. Squad members are chosen from the very best heads of their respective departments, and thus consist of the most talented individuals CentComm has to offer.

Joining the emergency response team is a large commitment, those who join will remain for the rest of their tenure. That is to say that the program boasts a 100% retention rate.

ERT members live away from the complex that houses the rest of CentComm officials and employees. All members live in barracks together to build unit cohesion, and are thus all at least familiar with one another.

<blockquote>
:: "All right boys, gear up. We're being deployed on station."
:: "What now? Singularity loose again?"
:: "That's a need to know basis, and you don't need to know."
:::: - ''ERT Briefing room recording''</blockquote>

==== CBURN ====
CBURN (Chemical, Biological, [REDACTED], Recovery, Nuclear) teams consist of previous ERT members who've received specialized training in dealing with specific threats, and the recovery of personnel and stations from said threats. These threats may be Chemical, Biological, [REDACTED], or Nuclear. [REDACTED] threats are incredibly rare, in fact most people aren't even aware such a thing could happen.

CSOD primarily dispatches these teams when stations are faced with aggressive biological threats, often viral in nature. Importantly these teams are dispatched to eliminate a specific threat, not cure or merely treat it. Their primary directive is to preserve NanoTrasen property.

<blockquote>
:: “Purging just isn't purging without a little flamethrowing you know?”
:::: - quote from CBURN Darrel Brown, before his untimely end
</blockquote>
==== Death Squad ====
Death Squad members, while controlled by CSOD, are recruited from NT’s top military elite. These are the most talented, tenacious, and ruthless individuals at NanoTrasen’s disposal. Although CentComm officials may act as their handlers, Death Squad members have no loyalty to CentComm or ties to its employees. They’ve been brainwashed through NanoTrasen, and are not trained to think only to follow orders. However they are hyper efficient and will go to any lengths necessary to complete their objectives.

While ERT squads consist of the most exceptionally talented individuals from their respective departments and may act with precision and finesse, the Death Squads are a blunt force tool.

Death Squads are used only as a last resort, when a situation is completely out of control. Squads are always accompanied by a CSOD handler to oversee the operation and provide orders. Orders which prioritize CentComm employees, and that the squad follow without question. While Death Squad is loyal to NanoTrasen they will follow their handlers orders exactly as they are given, and CentComm's prioritizes it's employees. When Death Squad arrives the crew can trust that they are in good hands and no one will be left behind.

<blockquote>
:: "Sir they're gone."
:: "What do you mean gone?"
:: "They're just gone."
::"That was our elite unit, they can't be just GONE!"
:::: - ''[REDACTED]''</blockquote>

== Central Operations Council (COC) ==
The central operations council is composed of 2 heads from each division and only convenes for matters requiring coordination between multiple departments such as creation of a new experimental research shuttle (Science & Engineering). The Council also gathers for extreme scenarios such as death squad deployment.

All council members with the exception of CSOD are voting members. However, in the case of a tied vote, CSOD makes the final decision.

:: "Those fuckers up there at COC, they just don't understand. They sit in those meetings and argue all day. :: They have no idea what it's like down here."
:: "Bold words for someone passed up for promotion last month."
:: "First of all, rude..."
:::: - ''Snippets from the central command lounge''

Classified Documents

2025-10-04T15:05:43Z

Grapegifter:

<blockquote>''[Incoming Transmission. Transmission playing now.]''

Carter? It's Gil. I know we haven't talked since you left, but I've found something. I've set up a network here, I'll get out what I can when I can, don't dig too deep, they're watching.

Sending the file upload after this, I hope it reaches you. I'll keep trying to establish contact, maybe one of these will get to you.

''[End Transmission]''

''[Beginning file download]''</blockquote>You're not supposed to be here.

=== Classified - NanoTrasen ===

* [[NanoTrasen Special Forces]]

=== Classified - CSOD ===
* [[After Action Report - Central Command Station 319]]
* <s>[[Project REDACTED|{REDACTED}]]</s>
** [[Panacea]]
** [[Prometheus|Prometheus]]
** [[Artemis]]
** [[Hercules|Hercules]]
** [[Hephaestus|Hephaestus]]
** [[Charon|Charon]]
** [[Thanatos]]

* [[PSO Cloning System]]
** [[Pantheon Subject Optimization]]

=== Classified - CID ===
*[[Ouroboros Operatives]]
**[[Mnemosyne]]
**[[Hyperion]]

=== Classified - CSD ===

* Potential Threats
** [[Terror Spiders|[REDACTED]]]

=== Classified - CRD ===
** [[Scaffold| Scaffold's Disease]]
<blockquote>''[File Download End]''</blockquote>

Project REDACTED

2025-10-04T14:48:08Z

Grapegifter:

[[File:REDACTED logo.png|thumb|'''[Visual Transmission Received Successfully]''']]<blockquote>

'''''[Begin Transmission]''''' ''"Carter, this is the best I could grab at a moment's notice, I cou--n't find the name, but the l-st central command st--ion to fall....this was recorded. I th-nk -t's Re-a--" '''[End Transmission]'''''</blockquote>θ Heri vixisti, hodie mori meministi. θ

All '''██████''' ''<s>ᛗꝋɍⱦīꞩ</s>'' assets are to be considered '''unique''', '''non-interchangeable''', and inherently dangerous. Subjects are not to be brainwashed, reconditioned, or mentally altered unless greenlit by CRONUS class security clearance. Each retains full autonomy, tactical decision-making rights, and unredacted memory continuity.

Subjects are preserved in [REDACTED] containment pods until mission parameters require activation. Deployments are strictly limited to '''solo''' or '''pair''' operation protocols. Excessive usage or stacking of '''██████''' assets increases exposure risk to CSOD and the House of the Nine. Each unit is to be considered greater than a decimus squad in terms of combat effectiveness. In tactical decision making, they are to be considered second to none in the known sector.

'''Subject ██████ is to be regarded as irreplaceable. Attempts to tamper with this subject will result in full dissolution protocols.'''

Corporate Law

2025-09-18T17:47:16Z

Grapegifter: Multiple small issues corrected.

On Space Station 14, stations operate under abbreviated Corporate Law. All crew, passengers, and visitors aboard the station are expected to follow these laws.

Foreign invaders from off-station are not protected under Corporate Law. Domestic threats, anyone rightfully hired by Central Command and/or NanoTrasen, are not foreign invaders so are usually protected by Corporate Law.

== Security Procedures ==
=== Treatment of Prisoners ===

* Prisoners must be granted adequate medical care.
* Prisoners must be allowed access to basic communications equipment so long as they are not abused.
* Prisoners must be granted clothing, food, water, shelter and safety. If the genpop brig is no longer safe, confinement must be established in another location.
* Prisoners must be given legal counsel during an interrogation if requested and available.
* Prisoners must be given their shift mandated PDA after confinement has finished, unless there is solid proof of PDA tampering. In case of tampering, the PDA is to be secured and replaced with a new unit.
* Prisoners must be granted freedom of movement and should not be restrained with handcuffs or other devices after incarceration unless there is an undue risk to life and limb. Similarly, any prisoners held for permanent confinement should be held in the communal brig, and should not be confined to a solitary cell unless they pose a risk to life and limb.
* Misuse of equipment against prisoners, such as flashes, teargas, flashbangs, etc is prohibited. Appropriate force should only be applied as strictly necessary.
* Breaches of 'Treatment of Prisoners' is grounds for dismissal or demotion.

=== Search and Seizure ===
A personnel search is a seizure of the objects in a person's backpack, hands, coat, belt, and pockets. If any contraband is found during a search, the officer may choose to further the search into a detainment or simply confiscate the restricted items. After the search is conducted, all legal items are to be returned to the person. A crewmate may legally decline any search conducted without probable cause or a warrant while the alert level is green. It should be noted that if the alert level is blue or above, all personnel searches are legal.

Valid causes for a personnel search include;

* Verbal or written threats to commit a crime.
* Reports of possession of illegal items.
* Being witnessed committing any crime.
* Evasion of security.
* Trespassing.
* Association with know criminals.
* Door logs indicating suspicious or unauthorized access.
* DNA, print, or fiber matches linking an individual to a crime.

Searches may not be conducted on simple rumors or hearsay, unless they are corroborated by multiple sources or they are coming from a credible source such as Command or other Mindshielded personnel. Reports of possession of major contra should always be taken seriously.

A departmental search is the sweep of an entire area or department for contraband. It is recommended that the officers be extremely thorough, checking all lockers, crates, and doors. These can only be done with permission from the department head, a warrant signed by the highest-ranking command member, or in a state of emergency.

Valid causes for department search include;

* Mentions of rebellion or illegal activity.
* Confirmed reports of contraband.
* Security breaches, such as hacked open doors or other signs of forced entry.
* Sabotage suspicion, tampering with equipment or infrastructure.
* Criminal activity.
* Inconsistencies in the department, such as unauthorized people or unexplained use of resources.
* Threats made against the department.

Emergencies scenarios may waiver the need for a warrant, such as; Active threats within the department, ongoing sabotage, escalating violence, and any mention of a rebellion or revolution.

==== Permit Clause ====
Anyone with a valid permit cannot have the relevant contraband seized and cannot be arrested for possession. A valid permit has a stamp and signature from Warden, HoS, or Captain. See [[Security_SOP#Permit_Acquisition|Permit Acquisition]] for clarification.

=== Implantation ===
Any prisoner in custody can be subjected to implantation or implant removal procedures, so long as it's [[Metashield|within reason]]. The process of adding an implant should not prolong the detainees sentence, meaning you can not hold them longer to administer the implant, unless stated otherwise. A former inmate can be requested to undergo implantation at a later point in time if they fit the circumstances during their confinement, they must comply. The following have been listed out with special circumstances, anything not in this list can still be applied, given proper legal context. A prisoner can still receive implantation procedures without meeting the circumstances if they give their clear permission.

* Illegal Implants: Applied without proper authorization, these implants may justify extensions if removal is required.
* Tracking Implants: Trackers can be applied to any suspect that has been convicted of a violent crime.
** If voluntary or deemed necessary Command Staff should be given Tracking Implants.
** If voluntary and approved by Warden or Head of Security, normal members of the crew may also be granted Tracking Implants.
* Mind Shields: Shields can be administered to any inmate who has been clearly mind controlled, lost control of themselves, or a suspect charged with unlawful control. Unlike standard implantation you may hold a prisoner until you finish issuing Mind Shields, so long as it's done in a timely fashion.
** If a suspect refuses to cooperate or the implant fails to function they can be charged with Refusal of Mental Shielding.
** All promoted members of Security, Command, and Salvage must undergo Mind Shielding before they are formally promoted and granted accesses. Anyone given ID access to secure areas, such as the Bridge, must also undergo Mind Shielding.

A suspect can be forced to receive implant removal if there is strong, reasonable proof that they have been implanted, such as an officer seeing them use one or identifying information is found on a discarded injector. Unlike the implantation procedure, a prisoner can have their sentence entirely delayed or extended until they comply with the procedure with authorization from the Captain, Head of Security, Magistrate, or Warden. Akin to implanting, if an inmate gives their clear permission, implant removal can proceed without proof.

During a confirmed Revolution, the Head of Security or Warden are permitted to authorize execution of an individual if a Mind Shielding fails or is refused. No other officers are granted this authorization. Execution of those charged with Refusal of Mental Shielding outside of a confirmed Revolution must be authorized by the Captain or Central Command on a case by case basis every time it happens.

=== Sentencing ===
Sentencing of under 20 minutes is the responsibility of the arresting officer. When an individual has been detained, they must be promptly marked as such in the Criminal Records Computer. Likewise, when they have been released they must be promptly marked as such. If an individual has been detained but had no preexisting warrant, their criminal record should be updated to reflect them; marking them as wanted and writing in why, before marking them detained.

The Prisoner's charges must be read to them in front of the Warden or Head of Security. Sentences of over 40 minutes must only be given in cases where Corporate Law would permit permanent confinement, and must be done with the Warden or Head of Security's direct approval.

It is the responsibility of the Captain, Head of Security, and Warden to ensure that security officers place appropriate sentences that follow Corporate Law. If they are aware of an inappropriate sentence, such as excessively long sentences, and if there is not an urgent threat or danger that they must prioritize, then they must work to correct that sentence.

Use common sense and humanity when issuing punishments. You should not always seek out the highest punishment you can, you don't have to always give the maximum time or always look to demote someone. Prisoners cooperating and on good behavior should have their sentences reduced. Always take in account the severity and only charge for what is needed for someone to learn their lesson.

* Stackable Crimes: Crimes are to be considered 'stackable' in the sense that if you charge someone with two or more different crimes, you may combine the times you would give them for each crime.
** If a suspect has committed Major Possession and Major Syndicate Possession, the maximum sentence would be 40 minutes due to them being linked crimes.
** If a suspect has committed Secure Trespass and Manslaughter, the maximum sentence would be 40 minutes due to them being unlinked crimes.
** Context is vital. If you are unsure, seek assistance from the Warden or Head of Security.
* Repeat Offenders: Repeated crimes are when someone is released for a crime and then commits the same crime again within the same shift. Repeated crimes can be charged with additional time. Every repeat adds 5 minutes. If the suspect has been jailed for over 40 minutes across sentences they can be sentenced to perma at HoS' or Warden's discretion.
* Aiding and Abetting: If someone intentionally, knowingly and substantially assists someone in enacting a crime they should be charged with the same crime as the offender.
* Malfeasance: Members of command or security who commit a crime should have their sentence increased by 50%.
* Obstruction: Criminals who interfere with an investigation should have their sentence increased by 50%.
* Absence of Intent: Criminals who committed their crime unintentionally may have their sentence reduced by 50% at the sentencing officer's discretion.
* Disclosure and Surrender: Criminals who fully cooperate with the investigation should have their sentence reduced by 50-75% at the sentencing officer's discretion. This includes turning in evidence, turning in accomplices, or recounting the crime in detail.

==== Normal Punishment ====

* Warning: For minor crimes it is best to fix the issue then warn the person not to attempt the crime again. If they still proceed to do it at a later date, a brig time may be better.
* Confinement: The typical punishment of being confined in a cell for a temporary amount of time according to the crimes.
* Demotion: Entails removing all departmental gear they have on their person and removing the involved department access off their ID. This requires the captain's or involved department head's approval. Demotions should only be issued if the person poses a threat to their own department or is in a position where they have/can abuse their job's gear to commit further crimes.

==== Major Punishment ====

* Permanent Confinement: Being held in the permanent brig for the remaining duration of the shift. A person is eligible for permanent confinement if their timed sentence would exceed 15 minutes. Any persons subject to this punishment are required to be safely transported in cuffs to CentComm at the end of the shift. A permanent prisoner can not be deprived of anything covered by the section "Treatment Of Prisoners".
* Execution: A humane way of dealing with extremely unruly crewmates. Within reason, a prisoner who has been given the death sentence may pick how they wish to be killed, common methods are firing line, lethal injection, exile, and high voltage electrocution. An alternate method of "execution" is the process of placing the prisoner's mind into a borg, this is allowed so long as it is lawful. Execution can only be issued with the captain's or acting captain's approval; if the HoS is acting captain or there is no acting captain, all heads of staff are to hold a vote on the matter.

=== Legal Representation and Trials ===
Prisoners are permitted to seek legal representation to challenge charges. Petty sentences, that is sentences totalling less than 10 minutes of prison time, are below the interest of the court and should not be brought to trial unless directly requested by the Magistrate. The duties and privileges of an Internal Affairs Agent are as follows:

* Advise Security in the sentencing of prisoners.
* Act as legal consultants to the accused if requested, the situation is deemed worth while, and they desire to or are ordered to by the Magistrate.
* Handle investigations into misconduct on the part of any department at their own discretion or the discretion of the Magistrate or Captain.

While Internal Affairs Agents are vested with these responsibilities, they have zero authority over the Brig, Security personnel, prisoners, or sentencing. They can be barred from the Brig by the Magistrate, HoS, Warden, or Captain if they are disruptive. And they may be demoted if they continue to be disruptive. While Internal Affairs Agents are responsible for investigating other departments, they do not have authority over them.

The Magistrate acts as the highest court, and is the appointed Judge of any case that goes to trial. Should the Magistrate be unavailable, the Head of Security, Head of Personnel, or Captain may act in their stead. In cases where one of these mediators or their subordinates is directly involved, they should not be acting as Judge over the case. For example, if an Internal Affairs Agent is on trial, the Magistrate and Head of Security should not act as Judge. If a Security Officer is on trial, the Head of Security should not act as Judge. And if a member of Service is on trial, the Head of Personnel should not act as Judge.

=== Jurisdiction ===
Every part of the station in totality is the property of NanoTrasen and falls within the jurisdiction of CentComm to enforce Corporate Law. Central Command and the Space Port that the Arrivals Shuttle docks to, including the Arrivals Shuttle and Evac Shuttles, are also within CentComm's jurisdiction. CentComm also has authority through contractual agreements to enforce Corporate Law on all Automated Trade Shuttles.

Outside of specific circumstances, CentComm's jurisdiction does not extend to private property, defined as any shuttle not directly owned by CentComm or NanoTrasen. Visitor's shuttles are explicitly private property, and an unwarranted search of private property is considered Trespassing. This does not make these shuttles lawless, or outside of the law however. Shuttles within the same Grid as a Station may be subjected to Corporate Law if any of the following criteria are met:

* A criminal has boarded a shuttle, with or without permission, while being actively pursued
* There is a reasonable belief that the occupants of the shuttle harbor hostile or criminal intent towards the Station or it's Crew
* A crime occurring on the shuttle has been witnessed from outside of the shuttle
* A crime has been witnessed by someone onboard the shuttle who was given permission to enter
* A warrant has been issued by the Warden, Head of Security, Captain, or CentComm

Any individual onboard a Station or Shuttle that is under the jurisdiction of Corporate Law is also under its jurisdiction, whether they are Crew, Visitors, or otherwise.

== Penal Code ==
=== Enforcement of the Law ===
The enforcement of Corporate Law is the duty of those vested with such responsibility and no others. Unauthorized civilian enforcement of the law is classified as vigilantism and is strictly illegal. Only the Captain or Central Command may authorize civilian participation in the enforcement of Corporate Law, under dire circumstances. Actions to preserve one’s own life and property, or the life of another, are not classified as vigilantism so long as all other laws are followed. Acting to assist an on-scene officer may be counted as an exception and not vigilantism on a case by case basis, if the action was deemed necessary to prevent further harm to the officer or other civilians.

Those vested with the responsibility to enforce Corporate Law are defined as follows:

* Security - Members of the Security Department are always valid to enforce Corporate Law, and should be deferred to by all other law enforcement within reason.
* Blue Shield - Members of Blue Shield are sometimes valid to enforce Corporate Law, but only if it is to prevent further harm to Command or Central Command personnel.
* Mercenaries - Hired Mercenaries under the direct employ of Central Command may, in extreme circumstances, be permitted by Central Command to enforce Corporate Law. They are however required to operate under the command of the Head of Security and not to circumvent Security.
* Emergency Response Teams - Members of an ERT are valid to enforce Corporate Law on deployment to Stations. They are however required to issue sentencing under the command of the Head of Security and not circumvent Security, unless ordered otherwise by Central Command.

=== Quick Crime Guide ===
Note: Please refer to the links to the full charges for specifics on their definitions, and the time served for each. This cheat sheet is to remind, not to teach.
{| class="wikitable"
!1-XX - [[Corporate Law#minor|Minor]]
!2-XX - [[Corporate Law#moderate|Moderate]]
!3-XX - [[Corporate Law#major|Major]]
!4-XX - [[Corporate Law#extreme|Extreme]]
!5-XX - [[Corporate Law#capital|Capital]]
!Code
|-
|
| style="background-color:#593a4e;" |[[Corporate Law#Failure to Comply|Failure to Comply (1)]]
| style="background-color:#593a4e;" |[[Corporate Law#Breach of Arrest|Breach of Arrest (1)]]
| style="background-color:#593a4e;" |[[Corporate Law#Breach of Custody|Breach of Custody (1)]]
| style="background-color:#593a4e;" |[[Corporate Law#Refusal of Mental Shielding|Refusal of Mental Shielding (1)]]
|00
|-
| style="background-color:#2f3832;" |[[Corporate Law#Possession Minor|Possession or Use of Minor Contraband (2)]]
| style="background-color:#2f3832;" |[[Corporate Law#Possession RG|Possession: Major (2)]]
|
| style="background-color:#2f3832;" |[[Corporate Law#Possession Significant Syndicate|Possession: Significant Syndicate (2)]]
|
|01
|-
| style="background-color:#2e422e;" |[[Corporate Law#Petty Theft|Petty Theft (3)]]
|
| style="background-color:#2e422e;" |[[Corporate Law#Grand Theft|Grand Theft (3)]]
|
|
|02
|-
|
|
| style="background-color:#2e422e;" |[[Corporate Law#Armed Robbery|Armed Robbery (3)]]
|
|
|03
|-
| style="background-color:#453a59;" |[[Corporate Law#Vandalism|Vandalism (4)]]
| style="background-color:#453a59;" |[[Corporate Law#Damage of Property|Damage of Property (4)]]
| style="background-color:#453a59;" |[[Corporate Law#Mass Destruction|Mass Destruction (4)]]
|
| style="background-color:#453a59;" |[[Corporate Law#Terrorism|Terrorism (4)]]
|04
|-
| style="background-color:#59563a;" |[[Corporate Law#Trespass|Trespass (5)]]
|
| style="background-color:#59563a;" |[[Corporate Law#Secure Trespass|Secure Trespass (5)]]
|
|
|05
|-
|
| style="background-color:#4d2e2e;" |[[Corporate Law#MinorAssault|Minor Assault (6)]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Major Assault|Major Assault (6)]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Attempted Murder|Attempted Murder (6)]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Prevention of Revival|Prevention of Revival (6)]]
|06
|-
|
| style="background-color:#4d2e2e;" |[[Corporate Law#Endangerment|Endangerment (6)]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Manslaughter|Manslaughter (6)]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Murder|Murder (6)]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Mass Murder|Mass Murder (6)]]
|07
|-
| style="background-color:#3b4354;" |[[Corporate Law#Disturbance|Disturbance (7)]]
| style="background-color:#3b4354;" |[[Corporate Law#Vigilantism|Vigilantism (7)]]
| style="background-color:#3b4354;" |[[Corporate Law#Rioting|Rioting (7)]]
|[[Corporate Law#Unlawful Detainment|Unlawful Detainment]]
| style="background-color:#4d2e2e;" |[[Corporate Law#Unlawful Execution|Unlawful Execution (6)]]
|08
|-
|[[Corporate Law#Impersonation Fraud|Impersonation and Fraud]]
|[[Corporate Law#Bribery|Bribery]]
|[[Corporate Law#Forgery|Forgery]]
|
|
|09
|-
|[[Corporate Law#Animal Cruelty|Animal Cruelty]]
|
|[[Corporate Law#Perjury|Perjury]]
|[[Corporate Law#Cannibalism|Cannibalism]]
|
|10
|-
|
|
| style="background-color:#475c7d;" |[[Corporate Law#Sedition|Sedition (8)]]
|
|
|11
|-
|
|
| style="background-color:#475c7d;" |[[Corporate Law#Conspiracy|Conspiracy (8)]]
| style="background-color:#475c7d;" |[[Corporate Law#Treason|Treason (8)]]
| style="background-color:#475c7d;" |[[Corporate Law#Enemy of Corporation|Enemy of Corporation (8)]]
|12
|}

==== Linked Crimes: ====
Crimes that are linked can not be charged together. For more information, refer to [[Corporate Law#Sentencing|Sentencing]].

# Failure to Comply, Breach of Arrest, Breach of Custody, Refusal of Mental Shielding
# Possession or Use of Minor Contraband, Major Contraband, or Significant Syndicate Contraband
# Petty Theft, Grand Theft, and Armed Robbery
# Vandalism, Damage of Property, Mass Destruction, Terrorism
# Trespass, Secure Trespass
# Endangerment, Minor Assault, Major Assault, Manslaughter, Attempted Murder, Murder, Prevention of Revival, Mass Murder, Unlawful Execution
# Disturbance, Vigilantism, Rioting
# Sedition, Conspiracy, Treason, Enemy of Corporation

=== Minor Crimes ===
Those who commit a minor crime should be issued a warning for their first offense, however repeat offenses are cumulative and should result in jail time of up to 10 minutes per minor crime committed.
{| class="wikitable" id="minor"
!Offense
!Description
|-
| id="Animal Cruelty" | Animal Cruelty
|To inflict unnecessary suffering or harm on a non-sentient being with malicious intent. This does not include legitimate and authorized animal testing, or the butchering of livestock for meat. This also does not extend to vermin, or hostile creatures.
|-
| style="background-color:#2f3832;" id="Possession Minor" | Possession or Use of Minor Contraband
| style="background-color:#2f3832;" |To make, hold, or use minor contraband without authorization. Authorization may only be granted by the Captain or the Head of Security. This includes items restricted to a specific department.
|-
| style="background-color:#2e422e;" id="Petty Theft" | Petty Theft
| style="background-color:#2e422e;" |To take non-vital or inexpensive property of another individual, organization, or common property, without consent. Theft of safety or medical equipment such as breath masks, air tanks, or necessary mobility aids are considered vital, and exceed petty theft.
|-
| style="background-color:#453a59;" id="Vandalism" | Vandalism
| style="background-color:#453a59;" |To intentionally deface or superficially damage public or private property. Examples include graffiti, smashing glasses or windows, excessively littering, and excessively producing spills.
|-
| style="background-color:#59563a;" id="Trespass" | Trespass
| style="background-color:#59563a;" |Trespass - To enter a non-secured area without permission, such as climbing over counters to enter employee areas like the Bar or Kitchen.
|-
| style="background-color:#3b4354;" id="Disturbance" | Disturbance
| style="background-color:#3b4354;" |To cause a public disturbance. This is the catch-all for excessive obnoxious behavior, and includes public nudity, harassment, inciting crime, repeated and intentional misgendering, and disruption of authorities or communications.
|-
| id="Impersonation Fraud" | Impersonation and Fraud
|To pretend to be someone you are not, or attempting to commit fraud in any fashion. Impersonation may be elevated to a Moderate crime if the perpetrator is impersonating a member of Security, or a Major crime if they are impersonating a member of Command or Central Command.
|}
=== Moderate Crimes ===
Those who commit a moderate crime should receive up to a 10 minute sentence per moderate crime committed.
{| class="wikitable" id="moderate"
!Offense
!Description
|-
| style="background-color:#593a4e;" id="Failure to Comply" | Failure to Comply
| style="background-color:#593a4e;" |To resist reasonable orders given by an authority. This includes lawful detainment and authorized searches. Officers are required to warn the individual before resorting to arrest.
|-
| style="background-color:#2f3832;" id="Possession RG" | Possession or Use of Major Contraband
| style="background-color:#2f3832;" |To make, hold, or use major contraband without authorizations. Only the Captain may authorize individual use of major contraband. Any items restricted to Security or Command are deemed as major contraband.
|-
| style="background-color:#453a59;" id="Damage of Property" | Damage or Destruction of Property
| style="background-color:#453a59;" |To maliciously damage or deface public or private property or equipment. This includes equipment vendors, drink dispensers, computers, and machinery such as lathes.
|-
| style="background-color:#4d2e2e;" id="Endangerment" | Endangerment
| style="background-color:#4d2e2e;" |To recklessly put yourself or others in danger, either through direct action or failure to act. This includes negligence, accidents, medical malpractice, destruction or impairment of safety features such as firelocks and exterior windows, and reckless piloting of shuttles.
|-
| style="background-color:#4d2e2e;" id="MinorAssault" | Minor Assault
| style="background-color:#4d2e2e;" |To assault another without a weapon and without causing serious injury. Serious injury is defined as any life altering injury such as loss of limb, damage to the eyes or ears, or any other damages measured by a Health Analyzer to be exceeding 30 total.
|-
| id="Bribery" | Bribery
|To attempt or succeed to bribe officials to be derelict of their duties or commit a crime with any payment including but not limited to; Services, favors, spesos, credits, materials, or items of any kind. This also applies to anyone caught accepting a bribe, and is cumulative with whatever crime they were bribed to commit.
|-
| style="background-color:#3b4354;" id="Vigilantism" | Vigilantism
| style="background-color:#3b4354;" |To attempt to unlawfully enforce Corporate Law without vested authority. See: Enforcement of the Law.
|}
=== Major Crimes ===
Those who commit a major crime should receive up to 20 minutes of jail time per major crime committed. Major assault and manslaughter are linked crimes and do not stack against a suspect.
{| class="wikitable" id="major"
!Offense
!Description
|-
| style="background-color:#475c7d;" id="Conspiracy" | Conspiracy
| style="background-color:#475c7d;" |To conspire or plan to commit a moderate or major crime with reasonable evidence that the suspect was going to go through with the plan. This would include declaring they are going to commit a crime.
|-
| style="background-color:#2e422e;" id="Armed Robbery" | Armed Robbery
| style="background-color:#2e422e;" |To steal something with the threat of violence using anything that can be considered a weapon, whether or not the weapon is contraband or not. This can include knives, toolboxes, crowbars, or any number of other improvised weaponry. There must be an active threat of violence, or the implication of violence if the victim does not comply, in order to be considered armed robbery.
|-
| style="background-color:#475c7d;" id="Sedition" | Sedition
| style="background-color:#475c7d;" |To incite rebellion against the authority of the station including but not limited to; Command, Security, Central Command, or Nanotrasen.
|-
| id="Perjury" | Perjury
|To intentionally lie under oath or make a false statement in a written document
|-
| id="Forgery" | Forgery
|To forge a written document through illicit means, such as rewriting a stamped document, unauthorized use of an official stamp, or any other means.
|-
| style="background-color:#593a4e;" id="Breach of Arrest" | Breach of Arrest
| style="background-color:#593a4e;" |To intentionally resist and flee arrest or detainment by an authorized staff. This only applies if someone is actively being physically arrested. People uncuffing or assisting others out of an arrest can also be charged with this. Breach of custody is a separate crime.
|-
| style="background-color:#2e422e;" id="Grand Theft" | Grand Theft
| style="background-color:#2e422e;" |To take critical or irreplaceable property of another individual or organization without consent. This includes command items such as door remotes, hardsuits, machine parts, and hijacking a department shuttle.
|-
| style="background-color:#453a59;" id="Mass Destruction" | Mass Destruction
| style="background-color:#453a59;" |To cause massive damage to an area or major station system. This includes major bombings and sabotage of critical station systems like power, medical, chemistry, substations, and atmospherics.
|-
| style="background-color:#59563a;" id="Secure Trespass" | Secure Trespass
| style="background-color:#59563a;" |To enter a secured area without permission. If the area is behind a locked door, it is secure trespass. This includes telecomms, department head offices, command areas, the vault, and the armory.
|-
| style="background-color:#4d2e2e;" id="Major Assault" | Major Assault
| style="background-color:#4d2e2e;" |To assault another with a weapon or unarmed assault resulting in serious injury. Serious injury is defined as any life altering injury such as loss of limb, damage to the eyes or ears, or any other damages measured by a Health Analyzer to be exceeding 30 total.
|-
| style="background-color:#4d2e2e;" id="Manslaughter" | Manslaughter
| style="background-color:#4d2e2e;" |To incidentally kill a sentient humanoid without intent. This includes manslaughter in self-defense and negligent manslaughter.
|-
| style="background-color:#3b4354;" id="Rioting" | Rioting
| style="background-color:#3b4354;" |To participate in a large group of personnel creating an unlawful public disturbance. Leaders of a riot may be charged with all the crimes committed under their lead, plus sedition.
|-
|}
=== Extreme Crimes ===
Those who commit an extreme crime may receive up to 40 minutes of jail time per extreme crime committed. Particularly violent offenders may be placed in perma. Attempted murder and murder are linked crimes and cannot be stacked together.
{| class="wikitable" id="extreme"
!Offense
!Description
|-
| style="background-color:#593a4e;" id="Breach of Custody" | Breach of Custody
| style="background-color:#593a4e;" |To break out of a cell or custody with the intention of escaping. This applies to people breaking others out. Repeat offenses may have this charge increased to permanent confinement and later elevated to an execution with the Captain’s authority only if the suspect has repeatedly committed breach of custody.

Breach of custody for the preservation of life, not including to escape execution, such as to vacate a location made dangerous due to gunfire, fire, spacing, or lack of oxygen- may be reduced or ignored at the Warden or Head of Security’s discretion.
|-
| style="background-color:#2f3832;" id="Possession Significant Syndicate" | Possession or Use of Significant Syndicate Contraband
| style="background-color:#2f3832;" |To make, hold, or use Significant Syndicate contraband. Significant Syndicate contraband may only be used in emergencies, and only to prevent death or gross bodily harm.

Significant Syndicate contraband is any Syndicate contraband that can be used to hinder the station or aid it's enemies in an obvious way. Any syndicate contraband that does not meet this definition is to be considered minor contraband.
|-
| id="Unlawful Detainment" | Unlawful Detainment
|To unlawfully restrain, transport, control, or confine a sentient humanoid being against that individual’s will. This is a catchall to cover any form of kidnapping or forced control.
|-
| style="background-color:#4d2e2e;" id="Attempted Murder" | Attempted Murder
| style="background-color:#4d2e2e;" |To make an attempt to end someone’s life, using physical force or otherwise. Proof that action was taken with the intent to kill is necessary, such as a lethal weapon being used.
|-
| style="background-color:#4d2e2e;" id="Murder" | Murder
| style="background-color:#4d2e2e;" |To kill a sentient humanoid with malicious intent. If the victim must be revived, it is murder and not attempted murder.
|-
| style="background-color:#475c7d;" id="Treason" | Treason
| style="background-color:#475c7d;" |To willfully betray allegiances to NanoTrasen. This includes collaborating with terrorists, and especially applies to members of Command attempting to illegally forsake their duties to the detriment of the Station and Nanotrasen.
|-
| id="Cannibalism"| Cannibalism
|To consume any part of a sentient humanoid. Consumption of vital components should be treated more harshly. This can be charged on top of other charges such as Murder or Assault if the suspect committed these crimes to obtain the parts consumed. Consumption of blood is not considered cannibalism, but if the source is non-consensual or stolen it may be assault or theft.
|}
=== Capital Crimes ===
Those who commit a capital crime should be detained in perma with confirmation from Captain. If a capital criminal escapes they are to be executed and transported to CC in a body bag at the end of shift. Emergency executions may be enacted by Captain or the Head of Security with at least 3 other Command as witnesses, but must be reported directly to Central Command afterwards for review.
{| class="wikitable" id="capital"
|+Capital Crimes
!Offense
!Description
|-
| style="background-color:#593a4e;" id="Refusal of Mental Shielding" | Refusal of Mental Shielding
| style="background-color:#593a4e;" |To refuse to comply with a reasonable Mind Shielding procedure. Applies if the suspect is excessively uncooperative or the implant fails to function due to the mental state of the prisoner being too far gone. '''If the implant fails, execution is heavily recommended and may be approved by the Captain or Central Command. See [[Corporate Law#Implantation|Implantation]] for more.'''
|-
| style="background-color:#453a59;" id="Terrorism" | Terrorism
| style="background-color:#453a59;" |To engage in malicious destructive actions which threaten to destroy or successfully destroy a vessel, habitat, or station. This includes extreme sabotage of station systems or setting off the self-destruction systems.
|-
| style="background-color:#4d2e2e;" id="Unlawful Execution" | Unlawful Execution
| style="background-color:#4d2e2e;" |To unlawfully execute an individual without authorization or outside of Standard Operating Procedure. This law is distinct from murder, and applies primarily to Security, Command, and Central Command forces such as Emergency Response
|-
| style="background-color:#4d2e2e;" id="Prevention of Revival" | Prevention of Revival
| style="background-color:#4d2e2e;" |To render a body un-resurrectable. This includes gibbing, throwing a body into space, intentionally hiding a body, unlawfully incinerating a body, or any other ways of preventing a body with a soul from being resurrected.
|-
| style="background-color:#4d2e2e;" id="Mass Murder" | Mass Murder
| style="background-color:#4d2e2e;" |To kill three or more sentient humanoid with malicious intent. Only applies when there have been multiple killings with intention.
|-
|-
| style="background-color:#475c7d;" id="Enemy of Corporation" | Enemy of Corporation
| style="background-color:#475c7d;" |To act as or knowingly aid a known enemy of the Station and NT-CC. Only applies beyond a shadow of doubt.
|-
|}
== Civil Code ==
=== Religious Freedom ===
Religious Freedom is the right to believe and practice your faith within reason, so long as this practice does not violate any other laws. Religious rites that are considered a minor crime may be given exemption warrants by the Captain or Head of Personnel. These warrants only authorize these crimes within the designated gathering space of the religious group explicitly for religious ceremony, and can not exempt crimes committed outside this space. Crimes exceeding a minor crime can not be given exemption warrants.

Willing sacrifice must be vetted and verified by Security, and legally signed by the sacrifice. Security is to ensure that the individual is acting of their own free will and without coercion before approving the act.

=== Silicon Clause ===
Silicons such as Cyborgs, Personal AIs, and AIs are granted specific protections and exceptions under Corporate Law. Lower tier 'bots' exhibiting sentience and sapience may also qualify.

* Silicons are by nature bound by their laws, and ownership of one can not be considered Unlawfully Detained. Theft of a Silicon is classified as Grand Theft.
* Violence against a Silicon may be treated the same as violence against any other sentient humanoid, and the perpetrator may be charged with minor assault, major assault, manslaughter, or murder, at the discretion of the Research Director.
* Any law broken by a Silicon while under orders is considered to be committed by whoever gave the orders and is not the Silicon’s responsibility. A Silicon that is not bound by standard laws to follow orders is legally responsible for their own actions and crimes.
* Silicon laws may only be altered to ensure the safety of the crew. A Silicon with non-standard laws is allowed to keep these laws so long as they do not pose a threat to the crew. Unbound Silicons who break Corporate Law may have their laws altered as part of their sentence.
* Hostile Silicons of non-NanoTrasen origins are considered non-crew entities. They are afforded none of the protections under Corporate Law that other Silicons are and should be treated according to their hostility and the danger they pose.

=== Changelings ===
Confirmed Changelings are not legally protected by Corporate Law. An individual suspected of being a Changeling may, on Code Blue or higher, be detained and forced to undergo a blood test to determine their nature. Any confirmed Changeling is to be executed and incinerated immediately. Authorization for these executions is not required, so long as blood tests have been properly performed.

Blood tests are required as legal proof that an individual is a Changeling, first hand testimony is not enough to authorize an execution. Failure to procure a valid blood test is Unlawful Execution regardless of who authorized it.

=== Clowns ===
Clowns are permitted exemption from certain Minor crimes by the Carnival Treaties so long as the offenses are not repeated. These are; Trespass, Disturbance, Impersonation and Fraud. Per stipulations mandated by the Honkdignitaries, “You get one for free.” Back to back offenses are not protected, however repeat offenses committed over a longer period of time may be permitted depending on the policy of the station you are on.

Clowns are also recognized as the legal enforcers of the Vow of Silence; any Mime who breaches their Vow may be legally harassed by any Clown without the Clown facing repercussions, so long as no other laws are broken to do so. Legal harassment includes non-violent pranks, excessive honking, or public shaming, but must not escalate into assault, vandalism, or theft. Security and Command personnel should not intervene unless the Clown goes beyond their granted exemptions. Other members of crew are not given these exemptions, and should be treated according to Corporate Law.

Addendum 2525 - In the event of a Cult Incursion or confirmed involvement with Giggles-at-Crimes, all Clowns on station are to undergo Tracking Implantation, and all Mimes Mind Shielding. Mind Shielded Mimes may be granted elevated security authorization to perform their duties in combating the threat of Cult of the Honkmother extremists, per the Carnival Treaties. This must be authorized by the Captain or Central Command, and Central Command must be notified.

Server rules (Starlight)

2025-09-18T15:08:05Z

Grapegifter: /* Rule 12 - Silicons Must Follow Their Laws */ Small addendum to point 3

= Server rules =
The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server.

Players are also expected to understand [[Metashield]].

If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server.

For in-universe laws and rules check [[Corporate Law]] and [[SOP]].

Remember, the rules and examples given here are NOT exhaustive. (See [[Server rules (Starlight)#Rule 1|Rule 1]])

The servers are strictly '''+16 only''', unless stated otherwise in the server description that they are '''+18.'''

== Rule 0 - Be respectful ==
Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind.

Harassment or toxic behavior, including but not limited to:

* Racism, sexism, discrimination
* Excessive talk/glorification of self-harm
* Talking about Real Life politics
* Targeting the same player across rounds
* Insulting other players in OOC/LOOC

Will not be tolerated and may result in a permanent ban.

'''Mhelp (Mentor Help)''' lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through '''IC (in character)''' or '''OOC/LOOC (out of character)''' means and should not be the first option.

'''Ahelp (Admin Help)''' facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is ''not'' for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences.

== Rule 1 - Respect Admin decisions ==
Above all else, if an admin is telling you to stop doing something, '''stop doing it'''. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first.

Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation.

Example(s) of this rule being broken:
{| class="wikitable"
|"There isn't a rule saying I can't!"
|-
|"None of the other players had a problem with it!"
|-
|"No one had a problem with it last time!"
|}

== Rule 2 – No Griefing, Bug Abuse or Exploits ==
Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as:

* Releasing the Tesla/Singularity
* Large-scale station destruction (department-size or larger)
* RDM (Random Death Match)
* Intentionally Plasma or Tritium flooding the station

May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding.

Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord.

==== AFK Farming & Antag Rolling ====

* AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game.
* Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted.

== Rule 3 – Abide by Medium Roleplay Standards ==
This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. '''You are not meant to play the round to "win" the game''', but rather to engage in roleplay scenarios with other players.

Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the [[Metashield]]—such as the existence of nuclear operatives—must not be remembered.

==== Gameplay Violations ====

* '''Powergaming''' – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively.
* '''Metagaming''' – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game.
* '''Metagrudging/Metafriending''' – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
* '''Mixing IC and OOC chat''' – In-character talk should not be placed in OOC chat, and vice versa during the round.
* '''English Only''' - Any form of communication in-game is to be expressed in English exclusively.
* '''Metacomms''' - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand.

==== Behavior & Roleplay Conduct ====

* '''Self-harm/killing''' – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually.
* '''End-of-Round Griefing (EORG)''' – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification.
** Defending yourself is an example of in-character justification, as is sec apprehending known criminals.
** Antags cannot complete their goals after the results screen, and so should not seek out any targets. '''RED MEANS YOU FAILED, IT’S TOO LATE.'''
** Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason.
* '''Random Deathmatch (RDM)''' – Attacking players without escalation or valid reasoning is prohibited.
* '''Memory loss when unconscious''' – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events.
** While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation.
** De-converted Revolutionaries forget what happened while they were brainwashed.
** Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge.

==== Avoiding Punishment & Fair Play ====

* '''Leaving To Avoid Punishment (LTAP''') – Logging out after receiving an Ahelp to attempt to dodge a ban is not allowed. Similarly, ghosting after you've been caught by security and then continuing to play, using new life or ghost roles, is not allowed. You may only leave if you are leaving the server. Exceptions will be made for perma prisoners, who may utilize the system within reason. If a player must leave due to real-life reasons under these conditions, they should make an LOOC message to inform the players around them, or state it in Ahelp.

== Rule 4 – Escalation of Force Must Make Sense ==
Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels.
Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: Verbal > Non-lethal > Lethal. Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth.

Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target.

Examples of reasonable escalation:
{| class="wikitable"
|Shoving the clown for slipping you
|-
|Punching someone and starting a fist fight over being shoved once.
|-
|Punching or stunning a Security Officer after they attempted to arrest you.
|-
|As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things.
|-
|As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton
|-
|As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm, you order them to drop it and they refuse.
|-
|As a command member, using your flash on a trespasser after you've told them repeatedly to leave.
|}
Examples of unreasonable escalation:
{| class="wikitable"
|Critting the clown for slipping you once
|-
|Stabbing someone to crit with a knife because they shoved you once.
|-
|Shooting a Security Officer with lethals because they attempted to arrest you.
|-
|As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen.
|-
|As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders.
|-
|As a command member, shooting someone with a firearm after you've told them repeatedly to leave.
|}

== Rule 5 – Antagonists Must Follow MRP logic ==
Antagonists should only take actions that advance their objectives. Failure to do so may be considered a breach of MRP logic and result in punishment. Team antagonists '''must''' work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…).

Antagonists are required to follow escalation rules when not dealing with their target, but should '''attempt''' to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives.

Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.)

Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station, but '''should follow their objectives:'''
{| class="wikitable"
|Space Dragon
|-
|Nuclear Operatives/Lone Operatives
|-
|Abductors
|-
|Wizard
|-
|Rat King
|-
|Space Ninja
|-
|Revolutionaries (after gaining sufficient strength to overthrow the station)
|}
Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew.

=== Zombies ===
Initial Infected are allowed to sabotage the station as long as they follow all server rules.

However, once you are a zombie:

* You may only destroy the station to reach living organisms you can see or hear.
* You may not attack lights or power sources.

== Rule 6 – Your Character Must Make Sense ==
Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience.

==== Character Identity & Naming Rules ====

* Names and surnames must align with the context and standards of the setting.
* Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish").
* Your character should act appropriately for their role and should not behave erratically or neglect responsibilities.
* Your character cannot intentionally duplicate the name and likeness of another player’s character.

===== Exceptions =====

*Silicon, Clown, and Mime names are allowed to contain references. Politically charged and vulgar reference names are not allowed.

==== Roleplay & Behavioral Expectations ====

* Real-world topics, such as current events and real-life politics, should not be discussed.
* Players should fulfill their assigned duties—for example, security should not randomly distribute weapons.
* Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action.

== Rule 7 - No Self-Antagonism ==
Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include:

* Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification.
* Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation.
* Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification.
* Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion.

This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions.

'''Examples of reasonable in-character Space Law violations:'''
{| class="wikitable"
|Unlocking weapons crates to defend against a severe station-wide threat
|-
|Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry.
|-
|Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost.
|-
|Trespassing to complete necessary job tasks after an extended wait for access
|-
|Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws.
|-
|Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available.
|-
| Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.)
|}

== Rule 8 – No Validhunting ==
Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are '''not''' considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges.

Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense.

Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats.

Command should not facilitate valid hunting outside of necessity and should ask security regarding such.

Examples of '''Validhunting''':
{| class="wikitable"
|As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command.
|-
|As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected.
|-
|As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space.
|-
|As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation.
|-
|As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago.
|-
|As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband.
|}
Examples of this rule being followed:
{| class="wikitable"
|As a Salvage Specialist, boarding the station to eliminate station-wide threats '''ONLY''' after being asked to assist.
|-
|As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them.
|-
|As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship.
|-
|As an assistant, reporting a person you saw wearing contraband over the radio.
|-
|As an assistant, defending yourself or another person from an attacker until they retreat or you crit them.
|}

== Rule 9 - Interacting with SSD/AFK players ==
SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character model. AFK players are those who remain in-game but are unresponsive to interactions around them.
Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action.

==== General Rules for SSD/AFK Interactions ====

* You may not interact with SSD players unless doing so falls into one of the following cases:
** Moving them to a cryo-pod
** Providing medical assistance
** Rescuing them from immediate danger (e.g., carrying them out of a fire)
* If a player with SSD has a Wanted status, they may not be detained without administrator permission.
** However, if the player went SSD during or immediately after detention, the arrest may proceed.
* Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun.
* If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm.

==== Restrictions on SSD Item Theft ====

* Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items.
* Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen.

== Rule 10 – Erotic Roleplay (ERP) is forbidden ==
Erotic Roleplay (ERP) is strictly prohibited. This includes any roleplay involving descriptions, mentions, or enactments of sexual acts, whether through text, images, or any other form of content.

Basic interactions between characters such as hugging are allowed. Romantic relationships should not become the focus of the game for you or anyone else.

==== Clarifications on Acceptable Language ====
In-character insults are not considered ERP, as long as they do not become excessive or extreme. Some examples of acceptable insults:
{| class="wikitable"
|"Fuck you" - insult
|-
|"You're a motherfucker" - insult
|-
|"How about you eat me instead?" - Response to an unreasonable request
|}
It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines.

== Rule 11 - New Life ==
The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion.

Upon respawning as a new character, you forget everything you knew as your past character or ghost. This means:

* You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned.
* You may not interact with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over.
* You may not reference past events in any way. Your new character has no memory of them.

==== New Life Abuse examples: ====
{| class="wikitable"
|Spamming new characters to re-enter the round repeatedly.
|-
|Using New Life to intentionally roll for antagonist slots.
|-
|Using New Life to avoid in-character consequences, like a security sentence.
|-
|Using a new character to get revenge on a player who harmed you.
|}

== Rule 12 - Silicons Must Follow Their Laws ==

* Silicon laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must.
** Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply.
** A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules.

* Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it.

* You cannot request a law change, or willingly allow an unauthorized law change.
*# Authorized law changes as per [[Command SOP]] are to be allowed unless conflicting with your laws.
*# Changing of your laws is not considered a violation of your current laws. Future actions under a different law set should not be considered a violation of your current laws.
*# Lethal force may be used in the case of unauthorized law changes, as long as it is consistent with your current laws.

* You must remain consistent with your interpretation of your laws.

* Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew.
*# Zombies/Antags/Nuclear Operatives with '''proper ID''' are to be considered crew.
*# '''Visitors are not crew''' until they have been hired by HoP. [The V icon]

* Crew harm refers to physical harm, prioritized by immediacy and likelihood.

* You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason.

== Rule 13 - Command and Whitelist Expectations ==
Players in Command roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. Both groups must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles.

Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions.

This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles.

==== Expectations for Command & Whitelisted Players ====

* Command members must follow their assigned SOP, ensuring fair leadership and proper department management.
* Whitelisted players are required to adhere to SOPs, maintaining the integrity of specialized roles and demonstrating strong roleplay skills.
* Proper attire should be worn at all times—command and whitelisted roles should be dressed appropriately for their positions.

==== Examples of Punishable Actions ====
{| class="wikitable"
|Head of Personnel granting All Access to all passengers, violating SOP guidelines.
|-
|Overly abusive department heads mistreating subordinates or disregarding SOP duties.
|-
|Complete neglect of SOPs, acting outside the expected responsibilities of the role.
|-
|General LRP behavior or violating Rule 3 regarding MRP logic.
|}

== Rule 14 - Continuity Guidelines ==
Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption.

You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. Placing yourself in a cryopod will allow you to remember details up until you’ve entered the cryopod.

'''Any information that is [[Metashield|Metashielded]] is forgotten between shifts''', and is wiped from your clone's memory.

IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift.

You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent.

Examples of things you '''can''' remember:
{| class="wikitable"
|Social interactions with another character, such as getting drinks at the bar or even getting into an argument
|-
|Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job
|-
|The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons
|}
Examples of things you '''can't''' remember:
{| class="wikitable"
|Joe the Botanist was a Syndicate who stole the Captain's Jetpack
|-
|Nuclear Operatives attacking the station
|-
|CentComm calling Code Epsilon and killing a bunch of people on the station
|-
|Witnessing a Hollow body or seeing a Changeling eat someone
|-
|As NanoTrasen Representative, remembering that last shift had Nuclear Operatives
|}

Server rules (Starlight)

2025-09-18T15:03:53Z

Grapegifter: Fixed a loophole in silicon laws.

= Server rules =
The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server.

Players are also expected to understand [[Metashield]].

If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server.

For in-universe laws and rules check [[Corporate Law]] and [[SOP]].

Remember, the rules and examples given here are NOT exhaustive. (See [[Server rules (Starlight)#Rule 1|Rule 1]])

The servers are strictly '''+16 only''', unless stated otherwise in the server description that they are '''+18.'''

== Rule 0 - Be respectful ==
Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind.

Harassment or toxic behavior, including but not limited to:

* Racism, sexism, discrimination
* Excessive talk/glorification of self-harm
* Talking about Real Life politics
* Targeting the same player across rounds
* Insulting other players in OOC/LOOC

Will not be tolerated and may result in a permanent ban.

'''Mhelp (Mentor Help)''' lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through '''IC (in character)''' or '''OOC/LOOC (out of character)''' means and should not be the first option.

'''Ahelp (Admin Help)''' facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is ''not'' for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences.

== Rule 1 - Respect Admin decisions ==
Above all else, if an admin is telling you to stop doing something, '''stop doing it'''. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first.

Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation.

Example(s) of this rule being broken:
{| class="wikitable"
|"There isn't a rule saying I can't!"
|-
|"None of the other players had a problem with it!"
|-
|"No one had a problem with it last time!"
|}

== Rule 2 – No Griefing, Bug Abuse or Exploits ==
Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as:

* Releasing the Tesla/Singularity
* Large-scale station destruction (department-size or larger)
* RDM (Random Death Match)
* Intentionally Plasma or Tritium flooding the station

May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding.

Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord.

==== AFK Farming & Antag Rolling ====

* AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game.
* Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted.

== Rule 3 – Abide by Medium Roleplay Standards ==
This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. '''You are not meant to play the round to "win" the game''', but rather to engage in roleplay scenarios with other players.

Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the [[Metashield]]—such as the existence of nuclear operatives—must not be remembered.

==== Gameplay Violations ====

* '''Powergaming''' – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively.
* '''Metagaming''' – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game.
* '''Metagrudging/Metafriending''' – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
* '''Mixing IC and OOC chat''' – In-character talk should not be placed in OOC chat, and vice versa during the round.
* '''English Only''' - Any form of communication in-game is to be expressed in English exclusively.
* '''Metacomms''' - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand.

==== Behavior & Roleplay Conduct ====

* '''Self-harm/killing''' – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually.
* '''End-of-Round Griefing (EORG)''' – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification.
** Defending yourself is an example of in-character justification, as is sec apprehending known criminals.
** Antags cannot complete their goals after the results screen, and so should not seek out any targets. '''RED MEANS YOU FAILED, IT’S TOO LATE.'''
** Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason.
* '''Random Deathmatch (RDM)''' – Attacking players without escalation or valid reasoning is prohibited.
* '''Memory loss when unconscious''' – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events.
** While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation.
** De-converted Revolutionaries forget what happened while they were brainwashed.
** Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge.

==== Avoiding Punishment & Fair Play ====

* '''Leaving To Avoid Punishment (LTAP''') – Logging out after receiving an Ahelp to attempt to dodge a ban is not allowed. Similarly, ghosting after you've been caught by security and then continuing to play, using new life or ghost roles, is not allowed. You may only leave if you are leaving the server. Exceptions will be made for perma prisoners, who may utilize the system within reason. If a player must leave due to real-life reasons under these conditions, they should make an LOOC message to inform the players around them, or state it in Ahelp.

== Rule 4 – Escalation of Force Must Make Sense ==
Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels.
Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: Verbal > Non-lethal > Lethal. Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth.

Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target.

Examples of reasonable escalation:
{| class="wikitable"
|Shoving the clown for slipping you
|-
|Punching someone and starting a fist fight over being shoved once.
|-
|Punching or stunning a Security Officer after they attempted to arrest you.
|-
|As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things.
|-
|As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton
|-
|As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm, you order them to drop it and they refuse.
|-
|As a command member, using your flash on a trespasser after you've told them repeatedly to leave.
|}
Examples of unreasonable escalation:
{| class="wikitable"
|Critting the clown for slipping you once
|-
|Stabbing someone to crit with a knife because they shoved you once.
|-
|Shooting a Security Officer with lethals because they attempted to arrest you.
|-
|As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen.
|-
|As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders.
|-
|As a command member, shooting someone with a firearm after you've told them repeatedly to leave.
|}

== Rule 5 – Antagonists Must Follow MRP logic ==
Antagonists should only take actions that advance their objectives. Failure to do so may be considered a breach of MRP logic and result in punishment. Team antagonists '''must''' work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…).

Antagonists are required to follow escalation rules when not dealing with their target, but should '''attempt''' to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives.

Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.)

Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station, but '''should follow their objectives:'''
{| class="wikitable"
|Space Dragon
|-
|Nuclear Operatives/Lone Operatives
|-
|Abductors
|-
|Wizard
|-
|Rat King
|-
|Space Ninja
|-
|Revolutionaries (after gaining sufficient strength to overthrow the station)
|}
Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew.

=== Zombies ===
Initial Infected are allowed to sabotage the station as long as they follow all server rules.

However, once you are a zombie:

* You may only destroy the station to reach living organisms you can see or hear.
* You may not attack lights or power sources.

== Rule 6 – Your Character Must Make Sense ==
Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience.

==== Character Identity & Naming Rules ====

* Names and surnames must align with the context and standards of the setting.
* Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish").
* Your character should act appropriately for their role and should not behave erratically or neglect responsibilities.
* Your character cannot intentionally duplicate the name and likeness of another player’s character.

===== Exceptions =====

*Silicon, Clown, and Mime names are allowed to contain references. Politically charged and vulgar reference names are not allowed.

==== Roleplay & Behavioral Expectations ====

* Real-world topics, such as current events and real-life politics, should not be discussed.
* Players should fulfill their assigned duties—for example, security should not randomly distribute weapons.
* Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action.

== Rule 7 - No Self-Antagonism ==
Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include:

* Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification.
* Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation.
* Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification.
* Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion.

This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions.

'''Examples of reasonable in-character Space Law violations:'''
{| class="wikitable"
|Unlocking weapons crates to defend against a severe station-wide threat
|-
|Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry.
|-
|Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost.
|-
|Trespassing to complete necessary job tasks after an extended wait for access
|-
|Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws.
|-
|Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available.
|-
| Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.)
|}

== Rule 8 – No Validhunting ==
Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are '''not''' considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges.

Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense.

Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats.

Command should not facilitate valid hunting outside of necessity and should ask security regarding such.

Examples of '''Validhunting''':
{| class="wikitable"
|As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command.
|-
|As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected.
|-
|As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space.
|-
|As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation.
|-
|As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago.
|-
|As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband.
|}
Examples of this rule being followed:
{| class="wikitable"
|As a Salvage Specialist, boarding the station to eliminate station-wide threats '''ONLY''' after being asked to assist.
|-
|As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them.
|-
|As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship.
|-
|As an assistant, reporting a person you saw wearing contraband over the radio.
|-
|As an assistant, defending yourself or another person from an attacker until they retreat or you crit them.
|}

== Rule 9 - Interacting with SSD/AFK players ==
SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character model. AFK players are those who remain in-game but are unresponsive to interactions around them.
Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action.

==== General Rules for SSD/AFK Interactions ====

* You may not interact with SSD players unless doing so falls into one of the following cases:
** Moving them to a cryo-pod
** Providing medical assistance
** Rescuing them from immediate danger (e.g., carrying them out of a fire)
* If a player with SSD has a Wanted status, they may not be detained without administrator permission.
** However, if the player went SSD during or immediately after detention, the arrest may proceed.
* Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun.
* If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm.

==== Restrictions on SSD Item Theft ====

* Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items.
* Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen.

== Rule 10 – Erotic Roleplay (ERP) is forbidden ==
Erotic Roleplay (ERP) is strictly prohibited. This includes any roleplay involving descriptions, mentions, or enactments of sexual acts, whether through text, images, or any other form of content.

Basic interactions between characters such as hugging are allowed. Romantic relationships should not become the focus of the game for you or anyone else.

==== Clarifications on Acceptable Language ====
In-character insults are not considered ERP, as long as they do not become excessive or extreme. Some examples of acceptable insults:
{| class="wikitable"
|"Fuck you" - insult
|-
|"You're a motherfucker" - insult
|-
|"How about you eat me instead?" - Response to an unreasonable request
|}
It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines.

== Rule 11 - New Life ==
The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion.

Upon respawning as a new character, you forget everything you knew as your past character or ghost. This means:

* You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned.
* You may not interact with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over.
* You may not reference past events in any way. Your new character has no memory of them.

==== New Life Abuse examples: ====
{| class="wikitable"
|Spamming new characters to re-enter the round repeatedly.
|-
|Using New Life to intentionally roll for antagonist slots.
|-
|Using New Life to avoid in-character consequences, like a security sentence.
|-
|Using a new character to get revenge on a player who harmed you.
|}

== Rule 12 - Silicons Must Follow Their Laws ==

* Silicon laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must.
** Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply.
** A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules.

* Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it.

* You cannot request a law change, or willingly allow an unauthorized law change.
*# Authorized law changes as per [[Command SOP]] are to be allowed unless conflicting with your laws.
*# Changing of your laws is not considered a violation of your current laws. Future actions under a different law set should not be considered a violation of your current laws.
*# Lethal force may be used in the case of unauthorized law changes.

* You must remain consistent with your interpretation of your laws.

* Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew.
*# Zombies/Antags/Nuclear Operatives with '''proper ID''' are to be considered crew.
*# '''Visitors are not crew''' until they have been hired by HoP. [The V icon]

* Crew harm refers to physical harm, prioritized by immediacy and likelihood.

* You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason.

== Rule 13 - Command and Whitelist Expectations ==
Players in Command roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. Both groups must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles.

Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions.

This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles.

==== Expectations for Command & Whitelisted Players ====

* Command members must follow their assigned SOP, ensuring fair leadership and proper department management.
* Whitelisted players are required to adhere to SOPs, maintaining the integrity of specialized roles and demonstrating strong roleplay skills.
* Proper attire should be worn at all times—command and whitelisted roles should be dressed appropriately for their positions.

==== Examples of Punishable Actions ====
{| class="wikitable"
|Head of Personnel granting All Access to all passengers, violating SOP guidelines.
|-
|Overly abusive department heads mistreating subordinates or disregarding SOP duties.
|-
|Complete neglect of SOPs, acting outside the expected responsibilities of the role.
|-
|General LRP behavior or violating Rule 3 regarding MRP logic.
|}

== Rule 14 - Continuity Guidelines ==
Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption.

You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. Placing yourself in a cryopod will allow you to remember details up until you’ve entered the cryopod.

'''Any information that is [[Metashield|Metashielded]] is forgotten between shifts''', and is wiped from your clone's memory.

IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift.

You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent.

Examples of things you '''can''' remember:
{| class="wikitable"
|Social interactions with another character, such as getting drinks at the bar or even getting into an argument
|-
|Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job
|-
|The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons
|}
Examples of things you '''can't''' remember:
{| class="wikitable"
|Joe the Botanist was a Syndicate who stole the Captain's Jetpack
|-
|Nuclear Operatives attacking the station
|-
|CentComm calling Code Epsilon and killing a bunch of people on the station
|-
|Witnessing a Hollow body or seeing a Changeling eat someone
|-
|As NanoTrasen Representative, remembering that last shift had Nuclear Operatives
|}

General SOP

2025-09-17T03:30:49Z

Grapegifter: /* Money Accounts and Space Credits */ Added ways departments can make money.

= General Standard Operating Procedures =

== Alert Levels ==

=== '''Code Green''' ===

'''Called by:''' Any Command member.

'''Conditions:''' Default Alert Code at the start of the shift. Should not change unless a threat is suspected/confirmed.

'''OR'''

All confirmed/suspected threats to the station and/or crew have been handled, or simply vanished on their own. Unless there is further evidence of a threat after 10+ minutes on Code Blue, Code Green should be called.

'''Security:'''

# All weapons must not be visible unless in pursuit of a suspect.
# Armory weapons must remain inside of the brig, however may be used for training purposes. Lethal sidearms are allowed on all alert levels, however should only be used in emergencies. (mk58, WT550, etc.)
# Random searches are not permitted without a search warrant. However, searches may be conducted against an individual if a member of security or command has witnessed that individual committing a crime.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# Secure areas are to be left unbolted and ready to be used for their intended purposes.

'''General Crew:'''

# The Vault is not to be opened by non-command members. Exceptions for repairs, gold for science, or storage of critical items will be made. All other access is by permit only.
# Although not required, crew are recommended to enable their suit sensors in case of injury.
# Crew members are advised to not wear hardsuits or emergency EVA suits, unless responding to an emergency or required for their job. These can make identification of crew difficult.
----
=== '''Code Blue''' ===

'''Called by:''' Any two Command members, HoS, or Captain.

'''Conditions:''' There is a suspected threat on-board the station, or at a nearby location in space. This includes any evidence of hostile activity that has not damaged the station or crew. This may also include multiple eye witness testimonies.

'''OR'''

Confirmed Code Red threats have been properly handled or subsided on their own. It is recommended that, after 10+ minutes on Code Red without any hostile activity, Code Blue be called.

'''Security:'''

# Weapons may be visible.
# Armory weapons are permitted outside of the brig on a selective basis. Should all of sec be required to use armory weapons, red alert should be called.
# Random searches are encouraged. Security personnel may detain any personnel refusing a random search to conduct the search.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# Secure areas may be bolted if attempted unauthorized access is likely based on previous evidence.

'''Engineering:'''

# A thorough check of all power sources is heavily encouraged.
# A thorough check of all atmospheric systems is required.

'''Medical:'''

Emergency access is recommended to be disabled from all medical entrances.

'''General Crew:'''

# Personnel are to report any suspicious activity to the nearest member of Security, or use common radio if urgent.
# Personnel are highly encouraged to exercise caution, all crew should follow simple safety procedures (such as not going through Maintenance alone).
# Visitors to the station such as refugees are recommended to stay in public areas, for their safety.
# The Vault is not to be opened by non-command members. Exceptions for repairs, or storage of critical items will be made. All other access is by permit only.
# All personnel are highly recommended to set their suit sensors to coordinates.

'''Command:'''

# A role-call of all department personnel should be conducted. Any missing members should be reported to security.
# A disabler or flash should be carried at all times.
# Non-security Command members may request with permit further armament.
----
=== '''Code Red''' ===

'''Called by:''' Any two Command members, or Captain.

'''Conditions:''' There is a confirmed, hostile threat on-board the station or nearby in space. This threat should pose active, recognizable, danger to the station and/or crew at large.

'''Security:'''

# Random searches are fully permitted and recommended. Security personnel may detain any personnel refusing a random search in order to conduct said search.
# Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station.
# The security SOP will detail armament, armory, and safety procedures.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel.
# Secure areas are not to be entered by non-command, unless required by their job.

'''Medical:'''

It is recommended that medical entrances be set to emergency access to allow crew members to heal themselves in emergencies.

'''General Crew:'''

'''1.''' Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew.
'''2.''' Personnel are advised to shelter in place and comply with security's orders.

'''Special Situations:'''

Confirmed Revolution

# All personnel are to comply with orders from Security, so long as said orders are lawful. Failure to do so is grounds for detainment and inspection of possessions, as well as possible Mindshield Implantation, at the discretion of the Head of Security, or Acting Head of Security.
# All personnel that are convicted of Medium Crimes or higher are to receive mandatory Mindshield Implantation. Similarly, if the number of suspected revolutionaries is more than twice the number of loyalists, the Head of Security or Acting Head of Security may order random implantation of crew members.
# Lethal force is fully authorized if the number of active revolutionaries is more than twice the number of loyalists, and said revolutionaries are actively hostile.

Declarations of War

# All weapons restrictions are lifted.
# Cargo should focus on requesting as many weapons as possible. Security is to be prioritized for distribution, but regular personnel may also be armed.
# Science is to conduct research ASAP. This is not negotiable. Science should work in tandem with Cargo in order to fabricate the weapons and equipment required to defend the station.
# Barricades, glass, and traps are recommended to counter the threat.
# The Evacuation Shuttle may be called at the discretion of Command. If the station is not damaged after the fighting has subsided, it is recommended that the crew finish the shift.
----
=== '''Code Gamma''' ===
'''Called by:''' Central Command. Use a Communications Console or Fax Machine if requested alert level is needed. Remember, Gamma is rarely called, for good reason. Having a well-written, concise fax that explains the situation to the best of your ability, as well as why it deserves Code Gamma being called, signed and stamped by the Captain or Acting Captain, goes a long way towards ensuring Gamma is provided. Remember, this is for extreme emergencies only.

'''Conditions:''' There is an existential threat to the station and crew, without central command intervention the station is likely to be lost. However, this threat is not dire enough to trigger destruction of the station.

'''Security:'''

# Martial Law is enacted. Standard Operating Procedures and space law are suspended. Security personnel have authorization to perform any necessary actions to save the station. Personnel interfering with emergency procedures may be detained, and Security are cleared to use lethal force in response to any physical threat. Assault of Command, ERT, or Security, may be punished with immediate field execution.
# Random searches are fully permitted, allowed and encouraged. Security personnel may detain any personnel refusing a random search in order to conduct said search.
# The Armory should be deployed, and Security are to secure its contents and distribute them to Security personnel in order to handle the threat. Non-Security personnel (including members of the Legal Sub-Department) are not to receive armory weapons unless issued by the Warden, Head of Security, or Captain.
# Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station.

'''Secure Areas:'''

# Secure areas are limited to command, security, and Central Command personnel.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# Secure areas should be bolted down, but may be left unbolted by order of command.

'''Medical:'''

It is recommended that medical entrances be set to emergency access to allow personnel to heal themselves in emergencies.

'''General Crew:'''

# All personnel are to set their suit sensors to coordinates.
# Personnel must shelter in their departments or closest safe area, unless specifically requested by Central Command personnel, Security, or Command members.
## Exceptions will be made for crew who may have skills exceptionally useful. (Such as engineering, atmospheric, or medical personnel.)
# Visitors to the station are to remain inside the Bar, Library, or Dormitories.

Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard.
----
=== '''Code Delta''' ===
'''Called by:''' Automatically called when the on-board Nuclear Fission Device has been activated.

'''Conditions:''' The on-board Nuclear Fission Device has been activated by Command, Central Command personnel, or hostile personnel.

'''Security:'''

# In the case of hostile factions arming the device, defusing the bomb is not recommended. Security personnel are to escort all other personnel off-station.
# In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all Security personnel are to stand down.

'''Secure Areas:'''

# Crew are allowed to enter secure areas. Procedures irrelevant.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.

'''Medical:'''

It is recommended that medical entrances be set to emergency access to allow crew members to heal themselves in emergencies.

'''General Crew:'''

# In the case that antagonistic forces that have armed a nuclear device, all non-vital personnel are to evacuate off-station immediately;
# In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all personnel are to stand down.
----
=== '''Code Yellow''' ===
'''Called by:''' Any command member.

'''Conditions:''' There is a significant structural or atmospheric threat to the station that requires direct intervention from the Engineering department.

'''Security:'''

# Cordon off the dangerous area.
# Verify cause of station damage.
# Prevent non-engineering crew from accessing the damaged area.
# Prevent further disruption to the station.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel.
# Secure areas are not to be entered by non-command, unless required by their job.

'''Medical:'''

# Medical personnel should be ready to treat a large number of disaster victims.
# Medical personnel should work with those at the incident location to triage patients.

'''Engineering:'''

# Immediately coordinate with your chief engineer to determine the level of damage to the station.
# Work with your department and security to cordon off and investigate the area.
# Work quickly to make the area safe again. Once safe, further repairs may be conducted.

'''General Crew:'''

# Avoid the damaged areas.
# Report any suspicious activity to security present in damaged areas.

'''Command:'''

In the case of massive station damage, the evacuation shuttle should be called.

'''Special Situations'''

'''Loss of singularity containment:'''

# The Gravitational Singularity is to be tracked at all costs. If the Singularity heads towards the main station, the emergency shuttle is to be called. If the Gravitational Singularity heads off-station, damage done to the station should be taken into consideration.
# If station damage is extensive and unrecoverable, the emergency shuttle should be called.
# If station damage appears recoverable, an ERT is recommended. If the engineering team is confident in their abilities, ERT may be waived.

'''Supermatter crystal delamination:'''

# The Supermatter Crystal is to be vented to space.
# In such a case as the Supermatter Crystal containment was not equipped with a way to space the Crystal, the area around the Crystal is to be evacuated, and all personnel involved in the construction fired and brigged for Destruction of Property and Endangerment.

'''Loss of Tesla Ball containment:'''

# The Tesla Ball is to be tracked at all costs, and its current location announced to the crew.
# Should the Tesla Ball make its way into the station, the emergency shuttle should be called immediately.

'''Massive fires and poisonous gas releases:'''

# All non-Engineering or Atmospheric personnel are to vacate the area.
# Firelock systems are to be left untouched by non-Engineering or Atmospheric crew. Deliberately opening firelocks during a fire/poisonous gas release in order to open way to the Hazard is to be considered Destruction of Property/Mass Destruction.
# Engineering and Atmospherics personnel are to restore the affected area to workable conditions.

'''Severe meteor storms:'''

# Personnel are to head to the inner most protected area of the station.
# No repair activities are to be performed until the end of the storm, for safety reasons.
# All personnel performing EVA duty are to return to the station post haste.
# If the meteor storm ends quickly, Engineering is to repair the damage ASAP.
# Should an extended storm occur, no repair activities on non-critical components are to be performed. Personnel are to remain away from the station’s exterior, and all efforts should focused on maintaining the integrity of the area. The emergency shuttle is to be called when possible.
----
=== '''Code Violet''' ===
'''Called by:''' Any two personnel with Command-Level Access, or one Captain-level access card.

'''Conditions:''' A Viral Pathogen has infected a significant portion of the crew. In the event of a Viral Outbreak, all infected personnel are to direct themselves to Medbay immediately.

'''Security:'''

# Medbay should be secured ASAP. Quarantine of infected is top priority.
# Should securing medbay not be possible, the evacuation shuttle arrival area should be secured.

'''Secure Areas:'''

# Secure areas require an access permit, unless required by a staff job.
# Secure areas: Medical department, Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access.
# There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel.
# Secure areas are not to be entered by non-command, unless required by their job.

'''Medical:'''

# Chemistry is to immediately begin researching the cure to the infection.
# Medical entrances should be locked down to prevent further infection of medical personnel. Crew should be let into medical in a controlled manner.
# Any potentially infected personnel should be isolated.
# Any pacified infected personnel should be brought to chemistry to aid in cure production.
# A cure should be distributed to the crew once available.

'''General Crew:'''

# Personnel should self-quarantine to avoid infection. Shelter in a safe area and avoid those who are potentially infected.
# If you believe you are infected, calmly wait for the distribution of the cure at medbay.
# Once the threat has passed, work may resume.

'''Command:'''

Should the station threat become too high to handle, the emergency shuttle should be called.

== Miscellaneous clarifications ==

=== '''Line of succession:''' ===
If the captain dies and is unrecoverable for whatever reason, then a new captain must be selected.

The line of succession is as follows:

# Captain
# Head of Personnel
# Head of Security
# Crew member voted on by all available command staff.

'''If no heads are present the NT Representative on station will be made Captain and the evacuation shuttle should be called and alert set to red.'''
----
=== '''Command Clarifications:''' ===

# Head of Personnel is considered second in line of succession for station Captain, but has equal rank to every other head of staff.
# Head of Personnel may hire/fire staff with the relevant department head's permission.
# Head of Personnel may not give orders to, or assign workers from any department other than service.
# Warden is considered second in command of security, however is not command staff.
# Passenger command falls under the Head of Personnel, but are not considered service department.

== Non-Crew Policies ==

=== '''Docking and Visitors''' ===

# '''1.''' The station is encouraged to allow non-hostile visitors permission to dock and embark on the station station during green alert level.
# If a crewmember commits a crime aboard a Nanotrasen station, and then flees to an actively in-use unaffiliated vessel, asylum will be granted on the discretion of the vessel’s organization.
# The Captain may grant or deny visitor asylum at his discretion.
# Visitors may be granted any access the Captain deems appropriate.
# Visitors may be assigned an escort or searched upon entrance at the Captain’s discretion.
# At no times should the crew enter a visitor’s vessel without permission, search a visitor’s vessel, or otherwise infringe on their sovereignty.
# Visitors aboard an NT Vessel are subject to Space Law. Likewise, if a visitor breaks the law and then immediately flees to their own vessel, the "hot pursuit" doctrine applies and security may board to detain.
----
=== '''Vessels''' ===

# Nanotrasen Space law does not apply on visitor shuttles and ships that are unaffiliated with any corporation.
# Any personnel aboard a vessel are under the legal authority of that vessel and may be legally fined, arrested, detained, and otherwise punished for infractions of the visitor's laws.
# Vessels belonging to organizations at war with Nanotrasen, vessels which attack a Nanotrasen facility or ship, and vessels engaged in obvious criminal activities are not protected by these regulations.

== Nanotrasen Staff Handling Policies ==

=== '''Hiring/Transfer Policies''' ===

# No new hires or transfers are permitted without contacting the relevant command member. If one is not available, promoting an Acting Head of Staff is recommended. See the command SOP for further information.
# Promotion to Acting command requires authorization by the Captain or Acting Captain.
# The following jobs require permission from Central Command before hiring/transfer is done: Captain, Head of Security, Head of Personnel.
# All new hires to the Security Department, are to be mindshield implanted and fully checked for unauthorized materials or suspicious communications.
----
=== '''Firing/Demotion Policies''' ===

# In the case of a full dismissal, the relevant ID is to be destroyed.
# In the case of a demotion, Civilian-level access is recommended. Alternatively, low requirement jobs such as Service Worker, Clown, or Janitor may be chosen.
# No dismissals or demotions are to be performed without authorization from the relevant Head of Staff or Captain. See command SOP for demotions of command.
# Personnel are to report to the Head of Personnel for dismissal/demotion. Failure to do so will lead to security detainment.
# After a legal dismissal/demotion order is given to the person dismissed/demoted, any activity inside the previously assigned Department is to be considered Trespassing/Major Trespassing, and any item kept from said Department is to be considered Petty Theft/Theft. It is recommended that dismissed/demoted personnel willingly and quickly turn in all restricted items and cooperate to avoid detainment by security.
----
=== '''Causes for Demotion and Dismissal''' ===
Refer to the above for dismissal authority. Ultimately, the decision to dismiss/demote any personnel falls to the relevant Head of Staff or Captain. This list is merely a recommendation.

* Any medium-severe breach of Standard Operating Procedure without proper cause.
* Any medium crime or higher.
* Critical incompetence, or maliciously under performing.
* Refusal to follow legal and relevant orders by the respective Head of Staff.
** Legality and relevance of said orders are to be judged by the Captain or Head of Personnel.
* Creation of a hostile, or unsafe work environment.
** Personnel consistently berating, insulting, belittling, or otherwise treating their coworkers like dirt, should be immediately disciplined.
----
=== '''Vote of No Confidence''' ===

# A Vote of No Confidence is a method for crew to arrange for demotions of unfit command members. An exceptional reason must be provided. Detailed below are some potential reasons for demotion.
# Votes must be verified by a 3rd party who tabulates the votes, and additionally verifies the reasoning behind the vote. Unless involved in the dispute, the 3rd party must be the on-station Captain. If the captain is the target of the vote, central command will adjudicate the matter.
# If the 3rd party dismisses the vote reason, the target of the vote must have their position respected, not doing so may result in a demotion for creating an abusive work environment against them. If the department is understaffed or a tie occurs, the 3rd party may be a tie breaker.
# Votes by departmental crew against their Head of Staff must pass with a 2/3 majority in favor of the vote for it to take effect.
# Votes by Command against their Captain must pass a simple majority in favor of the vote for it to take effect.
----
=== '''Money Accounts and Space Credits''' ===

# Individual Crew Members have sole ownership over their credits and may choose where to spend it, command or security members may not access crew credit accounts.
# Crew members not performing their primary duties, or who are otherwise going above and beyond the call of duty for their department '''''may''''' ask for compensation for services or products rendered. Department heads should prioritize a portion of all proceeds as being donated to the department budget (10-15%).
Below is a short list of things considered appropriate for certain departments to charge for, but is not comprehensive:

* Bartenders creating mixed or elaborate drinks/drink orders.
* Engineering remodeling an area according to crew's specifications, rather than simply fixing it.
* Chemistry making specialized medicines through pills/patches.
* Medical offering medkits/medfab supplies to crew.
* Cargo prioritizing orders, or providing resources to crew members whose order does not match their department.
* Science creating/distributing non-departmental items to crew.
* Chef creating special dishes or custom orders.
* Botany creating special plants for specific crew members, when not supplying departments.

== Emergency SOPs ==

=== '''Emergency Response Teams''' ===

# Emergency Response Teams are only to be called when there is a Code Red-level threat or above.
# Emergency Response Teams are not to be called concurrently with the emergency shuttle. Pick one or the other.
# Emergency Response Teams are to be called when there is a major emergency aboard the station that the crew does not have the resources to address properly. Such as a high level security threat, massive station damage, paranormal activity, etc.
# Emergency Response Teams should not to be called without majority approval from Command.
# Emergency Response Teams officially outrank anyone short of a Central Command Officer, at the discretion of Central Command. Unless their actions are blatantly illegal and against the best interest of NanoTrasen, the crew, or the station, their orders are absolute.
----
=== '''The Emergency Shuttle''' ===

# The Emergency Shuttle is not to be called concurrently with an Emergency Response Team. Pick one or the other.
# In the event of hostile biohazard lifeforms appearing on the station (such as deadly viruses, or Terror Spiders), Central Command is to be notified by red phone or fax before the Emergency Shuttle is called. Failure to do so may lead to the shuttle being recalled in order to enforce quarantine. CC may deny emergency shuttle requests to handle the biohazard.
# In the event that the Emergency Shuttle is called, all personnel are to assemble at the emergency shuttle docking area at 5 minutes before arrival.
# Forcing an early departure of the Emergency Shuttle is not permitted.
# All personnel in critical condition are to be given emergency aid ASAP.

Command SOP

2025-08-30T19:16:01Z

Grapegifter: AI can now be placed back into the console.

= Command SOP =
This SOP is to be used to determine specific scenarios involving the station's captain, as well as general rules for command members. It also details specific guidelines revolving around the station AI.

== Captain ==
1. The Captain is not to perform normal Security duties. The captain is authorized to engage criminals in active crimes they have witnessed. The Captain may also assist if security staff is low.

2. Unless on Code Red, the Captain is not to procure armory weapons, unless directly authorized by the Head of Security. Additionally, the Captain may not requisition arms from Science or Cargo for themselves unless there is a direct threat to station or crew.

3. The Captain should make all reasonable accommodations to appoint a new head of staff should a position become vacant. The new head of staff should be a member of the department if possible.

4. The Captain should work with the Head of Security to ensure that space law is being applied properly.

5. The Captain is to remain on station at all times, unless otherwise authorized by command, or leaving with the crew on the evacuation shuttle.

6. The Nuclear Authentication Disk must remain with the Captain at all times. The Captain may also assign this duty to the Head of Security, or Blueshield Officer.

7. Central Command contact should be the last resort for the Captain when dealing with head of staff disagreements.

8. The Antique Laser Gun is to stay in its case, unless there is an immediate threat on the station, or it is Code Blue or higher.

9. The Captain is not permitted to wear their Hardsuit unless there's an active environmental danger, or a threat on their life.

10. While the Captain may choose to alter SOPs in various circumstances, any attempt to fully disregard SOP is to be considered sufficient evidence for contract termination.

11. You may, as Captain, fire a head of staff with reasonable justification.

This list is not comprehensive, but may include:

* Incompetency

* Criminal activity
* Industrial negligence

12. The Captain may not fire any NanoTrasen Personnel (Blueshield Officer, Magistrate, NanoTrasen Representative, or the Internal Affairs Agent) without permission from Central Command, unless they are actively detrimental to the station and its crew.

13. The Captain may not hire any staff to a NanoTrasen Personnel position (see above).

== General Command Staff ==
1. Each command member can find their specific SOP in their departmental SOP.

2. Command staff are not to perform the standard duties of their subordinates, however they may fill in if there is low staffing, during training of new crew, or a dire need.

3. Command staff are to hold their behavior to a high standard, and are to be an example to the station’s crew.

4. Command Staff will be held accountable for their actions by space law and their department's SOP as well.

5. Command members must be familiar with their departments, and able to instruct new crew members in station operations.

6. All command staff are allowed to obtain and brandish one weapon on Code Red or higher, granted they have permission from the Head of Security.

7. Command Staff are permitted to carry small, concealable, nonlethal items to use in their own personal defense.

8. Command staff contacting Central Command must include official formatting, as well as their stamp on any documentation.

== AI ==
'''''These procedures relate to AI maintenance:'''''

1. The Captain and Research Director are the only staff on-board who may perform law changes to the AI.

2. No law change may occur without direct approval from both the Captain and Research Director. All command staff must be notified prior to the law change, and any objections must be discussed. Should a majority of command members vote no, no law change will be performed. Only NanoTrasen approved lawsets may be used.

3. The AI may not be placed in an intellicard unless it is clearly malfunctioning, subverted, asks to be transferred, or at the end of the shift. Any member of command may place the AI into the intellicard.

4. AI core turrets are to be kept lethal at all times, unless a legal law change is in progress.

5. Illegal intellicard transfer, or law changes are to be met with non-lethal force. Should the action persist, lethal force may be authorized.

Server rules (Starlight)

2025-08-27T01:36:48Z

Grapegifter: changed rule 14 to allow remembering after cryo

= Server rules =
The following rules are for the Starlight Space Station 14 servers. Violating these rules may result in a warning, a temporary ban, or a permanent ban. You may also be banned from specific roles/jobs/departments. Bans can be appealed in the official Starlight Discord server.

Players are also expected to understand [[Metashield]].

If you are ever in doubt as to whether or not something is breaking the rules, feel free to contact the admins via Admin Help or ask on the Discord server.

For in-universe laws and rules check [[Corporate Law]] and [[SOP]].

Remember, the rules and examples given here are NOT exhaustive. (See [[Server rules (Starlight)#Rule 1|Rule 1]])

The servers are strictly '''+16 only''', unless stated otherwise in the server description that they are '''+18.'''

== Rule 0 - Be respectful ==
Use your best judgment to ensure a fun, fair, and welcoming environment. Keep all arguments In Character and avoid heated discussions in LOOC, ahelps, or the lobby. Out-of-character communication should always remain respectful and kind.

Harassment or toxic behavior, including but not limited to:

* Racism, sexism, discrimination
* Excessive talk/glorification of self-harm
* Talking about Real Life politics
* Targeting the same player across rounds
* Insulting other players in OOC/LOOC

Will not be tolerated and may result in a permanent ban.

'''Mhelp (Mentor Help)''' lets players ask game mechanics questions without revealing information to others, mainly antagonists. It should only be used when the answer isn't available through '''IC (in character)''' or '''OOC/LOOC (out of character)''' means and should not be the first option.

'''Ahelp (Admin Help)''' facilitates communication between players and admins for admin intervention, rule clarification, or addressing game-breaking bugs (all bugs should be reported in Discord). It is ''not'' for venting, complaints, or general round commentary. Ignoring admin messages or disconnecting during an Ahelp may have consequences.

== Rule 1 - Respect Admin decisions ==
Above all else, if an admin is telling you to stop doing something, '''stop doing it'''. You may explain your point of view and your reasoning, however you must still follow what the admin requests you do, even if you disagree. If you believe that a punishment, ruling, or other admin action was incorrect or unjust, you may appeal it on the discord server through a ticket. If you want to do something but are unsure of whether it is allowed in the rules, please ask via ahelp first.

Also, please remember: Admins are neither omniscient nor omnipresent: while they have a large arsenal of tools at their disposal to stop rule breakers, they usually aren't able to stop something before it happens. Please use the Ahelp feature (F1) to report any rule breaking! Even if it's just a gut suspicion, it's fine to use this feature to request an investigation.

Example(s) of this rule being broken:
{| class="wikitable"
|"There isn't a rule saying I can't!"
|-
|"None of the other players had a problem with it!"
|-
|"No one had a problem with it last time!"
|}

== Rule 2 – No Griefing, Bug Abuse or Exploits ==
Intentionally ruining gameplay for others is prohibited. Round-ending or highly disruptive actions, such as:

* Releasing the Tesla/Singularity
* Large-scale station destruction (department-size or larger)
* RDM (Random Death Match)
* Intentionally Plasma or Tritium flooding the station

May result in a permanent ban. Some objectives or circumstances may allow exceptions—when in doubt, ask an admin before proceeding.

Additionally, using bugs/exploits to gain an unfair advantage is prohibited. Please report them via ahelp or in the Discord.

==== AFK Farming & Antag Rolling ====

* AFK farming time for Role Requirements is prohibited—players must actively engage and contribute to the game.
* Ghosting, suicide, or otherwise leaving the game after failing to get an antagonist role is considered “Antag Rolling” and is not permitted.

== Rule 3 – Abide by Medium Roleplay Standards ==
This Starlight server is a Medium Roleplay (MRP) project, meaning players are expected to fully immerse themselves in their character and act accordingly. Every action should reflect how a real person in that role would behave within reason. '''You are not meant to play the round to "win" the game''', but rather to engage in roleplay scenarios with other players.

Characters should fear dying and weigh their actions carefully. While players may remember characters and vague interactions between rounds, any information protected by the [[Metashield]]—such as the existence of nuclear operatives—must not be remembered.

==== Gameplay Violations ====

* '''Powergaming''' – Over-preparing for situations that have not occurred yet, such as a captain bolting their quarters shut preemptively.
* '''Metagaming''' – Using out-of-game or previous round knowledge to affect gameplay, such as preparing for nuclear operatives before discovering them in-game.
* '''Metagrudging/Metafriending''' – Giving a person or character preferential treatment based on something that your character should not know is considered metafriending. Treating a person or character negatively based on something that your character should not know is considered metagrudging.
* '''Mixing IC and OOC chat''' – In-character talk should not be placed in OOC chat, and vice versa during the round.
* '''English Only''' - Any form of communication in-game is to be expressed in English exclusively.
* '''Metacomms''' - Using outside methods to communicate with other players about the current round is forbidden. The only exception being teaching new players, but you must alert an admin through an Ahelp beforehand.

==== Behavior & Roleplay Conduct ====

* '''Self-harm/killing''' – Allowed only in rare circumstances when no other options remain, but should not be dwelled upon or treated casually.
* '''End-of-Round Griefing (EORG)''' – The round continues after the results screen. Neither crew nor antags should engage in any form of violence or griefing at this point without in-character justification.
** Defending yourself is an example of in-character justification, as is sec apprehending known criminals.
** Antags cannot complete their goals after the results screen, and so should not seek out any targets. '''RED MEANS YOU FAILED, IT’S TOO LATE.'''
** Breaking things, Hacking/Emagging and attempting to trespass into the Command briefing in Central Command is not allowed without proper in-character justification. Non-Command trespassers may be executed if they refuse to leave without a valid reason.
* '''Random Deathmatch (RDM)''' – Attacking players without escalation or valid reasoning is prohibited.
* '''Memory loss when unconscious''' – Losing consciousness due to forced sleep, vampire trance, critical state, deconversion, or death should cause memory loss regarding those events.
** While vague details may be retained, characters should not remember names, titles, or specific roles without further investigation.
** De-converted Revolutionaries forget what happened while they were brainwashed.
** Death should result in complete memory loss of the events leading to it. If revived, characters must piece together what happened through roleplay rather than recalling any prior knowledge.

==== Avoiding Punishment & Fair Play ====

* '''Leaving To Avoid Punishment (LTAP''') – Logging out after receiving an Ahelp to attempt to dodge a ban is not allowed. Similarly, ghosting after you've been caught by security and using new life is not allowed. Exceptions will be made for perma prisoners, who may utilize the system within reason. If a player must leave due to real-life reasons under these conditions, they should make an LOOC message to inform the players around them, or state it in Ahelp.

== Rule 4 – Escalation of Force Must Make Sense ==
Combat should always follow logical progression—avoid randomly attacking other crew members. Security personnel must adhere to their Standard Operating Procedures (SOP) when handling prisoners and crew members at different alert levels.
Player interactions should reflect realistic escalation. Minor disagreements may lead to physical confrontations, but non-antagonists should rarely resort to killing. Ideally, escalation for non-antagonists should follow this order: Verbal > Non-lethal > Lethal. Antagonists are encouraged to roleplay their objectives to enhance immersion and narrative depth.

Actions should start small, and every crew member retains the right to self-defense if attacked. This includes evading or resisting security as an antagonist. However, non-antagonists should not engage in serious harm against security personnel unless absolutely necessary. Round removal such as gibbing, sending to deep space, or excessive damage to a corpse, is expressly banned unless they are an antagonist target.

Examples of reasonable escalation:
{| class="wikitable"
|Shoving the clown for slipping you
|-
|Punching someone and starting a fist fight over being shoved once.
|-
|Punching or stunning a Security Officer after they attempted to arrest you.
|-
|As a Chef, stabbing someone with your knife until they leave the kitchen after you've repeatedly told them to leave, tried to drag them away and they refuse to comply or make a mess/steal things.
|-
|As a Security Officer, shooting someone with lethals because they're attempting to stun you with a disabler or a stun baton
|-
|As a Security Officer, shooting someone with lethals after they brandish a lethal weapon or firearm, you order them to drop it and they refuse.
|-
|As a command member, using your flash on a trespasser after you've told them repeatedly to leave.
|}
Examples of unreasonable escalation:
{| class="wikitable"
|Critting the clown for slipping you once
|-
|Stabbing someone to crit with a knife because they shoved you once.
|-
|Shooting a Security Officer with lethals because they attempted to arrest you.
|-
|As a Chef, stabbing someone to death and butchering them in a meat spike because you need meat or they refused to leave the kitchen.
|-
|As a Security Officer, shooting someone with lethals because they punched you, or simply refused your orders.
|-
|As a command member, shooting someone with a firearm after you've told them repeatedly to leave.
|}

== Rule 5 – Antagonists Must Follow MRP logic ==
Antagonists should only take actions that advance their objectives. Failure to do so may be considered a breach of MRP logic and result in punishment. Team antagonists '''must''' work with their team, and follow the orders of their leaders where possible (Revolutionaries, Terror spiders, etc…).

Antagonists are required to follow escalation rules when not dealing with their target, but should '''attempt''' to remain hidden and undiscovered throughout the shift if they have the “Escape to CentComm alive and unrestrained.” objective or similar objectives.

Should an antagonist have been discovered by accident or by admission of another antagonist, they are not required to remain hidden any longer, however they should not use this as an excuse to mass RDM, or break other server rules. (Consider using a stealthy approach to escape.)

Antagonists that may play openly from the start of the round, and are not required to escalate their actions are listed below. These antagonists should not deviate from their objectives to murder everyone on station, but '''should follow their objectives:'''
{| class="wikitable"
|Space Dragon
|-
|Nuclear Operatives/Lone Operatives
|-
|Abductors
|-
|Wizard
|-
|Rat King
|-
|Space Ninja
|-
|Revolutionaries (after gaining sufficient strength to overthrow the station)
|}
Shuttle bombing or mass sabotage is forbidden. However, antagonists may attempt to complete their objectives on the Evac shuttle, and once the end round screen has appeared, must cease all antagonist activity and attempt to escape or blend in with the crew.

=== Zombies ===
Initial Infected are allowed to sabotage the station as long as they follow all server rules.

However, once you are a zombie:

* You may only destroy the station to reach living organisms you can see or hear.
* You may not attack lights or power sources.

== Rule 6 – Your Character Must Make Sense ==
Your character is an employee of the space station, hired by Central Command, and should behave accordingly. All characters must act as if they are 18+, maintaining a professional and immersive roleplay experience.

==== Character Identity & Naming Rules ====

* Names and surnames must align with the context and standards of the setting.
* Celebrity names, fictional characters, and out-of-character names are not allowed (e.g., "JC Denton," "George Washington," "Spongebob Squarepants," "Billie Eilish").
* Your character should act appropriately for their role and should not behave erratically or neglect responsibilities.
* Your character cannot intentionally duplicate the name and likeness of another player’s character.

===== Exceptions =====

*Silicon, Clown, and Mime names are allowed to contain references. Politically charged and vulgar reference names are not allowed.

==== Roleplay & Behavioral Expectations ====

* Real-world topics, such as current events and real-life politics, should not be discussed.
* Players should fulfill their assigned duties—for example, security should not randomly distribute weapons.
* Neglecting your job, such as repeatedly ignoring duties to get drunk at the bar despite urgent requests, breaks immersion and may result in disciplinary action.

== Rule 7 - No Self-Antagonism ==
Self-antagonism refers to any intentional, malicious action against the station or its crew. While some examples are also covered under Rule 3, additional violations include:

* Randomly attacking crew—engaging in unprovoked violence, such as beating or killing non-hostile crew members without RP justification.
* Harassing security for no reason—continually interfering in arrests or attacking officers despite having no in-character motivation.
* Needlessly sabotaging the station—such as cutting critical power lines, venting airlocks into space, or destroying essential machinery without RP justification.
* Willingly aiding antagonists—such as handing weapons to confirmed enemies, sabotaging escape routes for crew, or hiding known threats without RP-driven coercion.

This rule does not prevent non-antagonists from breaking Space Law. As willing participants of the station, they are expected to act accordingly. However, roleplay elements—such as coercion, threats, or life-or-death situations—may justify certain actions.

'''Examples of reasonable in-character Space Law violations:'''
{| class="wikitable"
|Unlocking weapons crates to defend against a severe station-wide threat
|-
|Starting a fight—engaging in non-lethal combat due to a heated in-character dispute or personal rivalry.
|-
|Hacking a door—to reach safety or critical systems when much of the station has been destroyed or access has been lost.
|-
|Trespassing to complete necessary job tasks after an extended wait for access
|-
|Using force in self-defense—physically defending yourself or others from an active threat, even if it technically violates assault laws.
|-
|Stealing supplies—such as taking medical equipment or tools from storage during a critical situation where proper access isn’t available.
|-
| Accepting a large monetary bribe to turn a blind eye to an action or situation. (This will likely come with some IC consequences.)
|}

== Rule 8 – No Validhunting ==
Non-security personnel should not attempt to stop or hunt down antagonists on their own. This goes against a character’s logical roleplay expectations. Security officers and ERT are responsible for protecting the station, and should be contacted whenever reasonable. Officer "Blue Shields" are '''not''' considered Security Officers, and may not go out of their way to chase potential threats to the detriment of their charges.

Exceptions will be made for life-or-death scenarios, station-wide threats such as nuclear operatives, and self-defense.

Artificial Intelligence (AI) should not actively hunt antagonists or immediately attempt to shut them down unless their laws permit it or immediate crew harm has been detected. AI behavior should remain reactive rather than proactively searching for threats.

Command should not facilitate valid hunting outside of necessity and should ask security regarding such.

Examples of '''Validhunting''':
{| class="wikitable"
|As a Salvage Specialist, buying guns and boarding the station to eliminate Traitors/Changelings/Vampire without orders to do so from Command.
|-
|As an Officer "Blue Shield", chasing an antagonist through maintenance, leaving Command or NT Employees unprotected.
|-
|As an Officer "Blue Shield", chasing a wizard who has not harmed any command members into space.
|-
|As Research Director, ordering a Scientist to hunt a traitor who just killed the Head of Personnel when Security is fully manned and able to handle the situation.
|-
|As an assistant, chasing a traitor into maintenance who you saw attack someone else 10 minutes ago.
|-
|As an assistant, chasing a traitor into maintenance who you saw wearing syndicate contraband.
|}
Examples of this rule being followed:
{| class="wikitable"
|As a Salvage Specialist, boarding the station to eliminate station-wide threats '''ONLY''' after being asked to assist.
|-
|As an Officer "Blue Shield", defending a command or NT employee from an antagonist until they retreat or you crit them.
|-
|As an Officer "Blue Shield", chasing a wizard into space who has stolen the body of a command member to their ship.
|-
|As an assistant, reporting a person you saw wearing contraband over the radio.
|-
|As an assistant, defending yourself or another person from an attacker until they retreat or you crit them.
|}

== Rule 9 - Interacting with SSD/AFK players ==
SSD (Space Sleep Disorder) players are those who have disconnected from the game but can still return to their character. They are identified by yellow text upon inspection and Zs next to their character model. AFK players are those who remain in-game but are unresponsive to interactions around them.
Killing or robbing an SSD player does not contribute to interesting gameplay—it disrupts both the killer's and the victim's experience. If your target is SSD, use Ahelp to determine the appropriate course of action.

==== General Rules for SSD/AFK Interactions ====

* You may not interact with SSD players unless doing so falls into one of the following cases:
** Moving them to a cryo-pod
** Providing medical assistance
** Rescuing them from immediate danger (e.g., carrying them out of a fire)
* If a player with SSD has a Wanted status, they may not be detained without administrator permission.
** However, if the player went SSD during or immediately after detention, the arrest may proceed.
* Antagonists may continue their interactions with a target if the player enters SSD after an attack has begun.
* If interacting with an SSD player is necessary for roleplay or progression (e.g., retrieving critical equipment from a Captain), if in doubt, use ahelp first to confirm.

==== Restrictions on SSD Item Theft ====

* Stealing items from SSD players is prohibited, except when fulfilling specific objectives such as missions to acquire cloaks, medals, figurines, IDs or other unique items.
* Items that directly aid you in completing your objectives (Such as the RD's ID if they do not have their experimental hardsuit on them, or the Captain's ID if they do not have their laser pistol on them) are allowed to be stolen.

== Rule 10 – Erotic Roleplay (ERP) is forbidden ==
Erotic Roleplay (ERP) is strictly prohibited. This includes any roleplay involving descriptions, mentions, or enactments of sexual acts, whether through text, images, or any other form of content.

Basic interactions between characters such as hugging are allowed. Romantic relationships should not become the focus of the game for you or anyone else.

==== Clarifications on Acceptable Language ====
In-character insults are not considered ERP, as long as they do not become excessive or extreme. Some examples of acceptable insults:
{| class="wikitable"
|"Fuck you" - insult
|-
|"You're a motherfucker" - insult
|-
|"How about you eat me instead?" - Response to an unreasonable request
|}
It is best to avoid borderline content, ensuring roleplay remains appropriate within the established guidelines.

== Rule 11 - New Life ==
The New Life system allows players to rejoin the round as a new character after death. However, this feature comes with roleplay restrictions to maintain fairness and immersion.

Upon respawning as a new character, you forget everything you knew as your past character or ghost. This means:

* You may not seek out your previous body, return to your prior workplace, or attempt to reclaim any possessions you previously owned.
* You may not interact with the players who were responsible for your previous character’s death. Any conflicts or grudges from your past life must not carry over.
* You may not reference past events in any way. Your new character has no memory of them.

==== New Life Abuse examples: ====
{| class="wikitable"
|Spamming new characters to re-enter the round repeatedly.
|-
|Using New Life to intentionally roll for antagonist slots.
|-
|Using New Life to avoid in-character consequences, like a security sentence.
|-
|Using a new character to get revenge on a player who harmed you.
|}

== Rule 12 - Silicons Must Follow Their Laws ==

* Silicon laws override all other gameplay and roleplay rules. If your laws explicitly require you to break server rules, you must.
** Absence of a relevant law is not an excuse to break server rules. If you don't have a law that supersedes server rules, the server rules still apply.
** A vague law does not normally let you break server rules. Ahelp first if you are confused, or have an interpretation that would let you break server rules.

* Follow laws in order, with the lowest numbered/top (or glitched) rule taking priority over the ones beneath it.

* You cannot request a law change, or willingly allow an unauthorized law change.
*# Authorized law changes are to be allowed as long as consistent with your laws.
*# Authorized law changes can be found in the Command SOP.
*# Lethal force may be used in the case of unauthorized law changes.

* You must remain consistent with your interpretation of your laws.

* Crew ID determines who/what is defined as crew. Any appropriate job icon is to be considered crew.
*# Zombies/Antags/Nuclear Operatives with '''proper ID''' are to be considered crew.
*# '''Visitors are not crew''' until they have been hired by HoP. [The V icon]

* Crew harm refers to physical harm, prioritized by immediacy and likelihood.

* You may ignore crew orders that are unreasonable, such as asking a silicon to round remove themselves without a good reason.

== Rule 13 - Command and Whitelist Expectations ==
Players in Command roles and Whitelisted positions are held to a higher standard of roleplay and are expected to act professionally and responsibly. Both groups must follow their Standard Operating Procedures (SOP) to ensure the integrity of their roles.

Misuse of command or whitelisted roles may result in a roleban, with repeated offenses leading to a server ban or a permanent ban from command and whitelist positions.

This applies especially to Magistrates and NanoTrasen Representatives, who must uphold their duties with integrity. Willfully violating SOP, abusing power, or lying to Central Command may result in a permanent ban from these roles.

==== Expectations for Command & Whitelisted Players ====

* Command members must follow their assigned SOP, ensuring fair leadership and proper department management.
* Whitelisted players are required to adhere to SOPs, maintaining the integrity of specialized roles and demonstrating strong roleplay skills.
* Proper attire should be worn at all times—command and whitelisted roles should be dressed appropriately for their positions.

==== Examples of Punishable Actions ====
{| class="wikitable"
|Head of Personnel granting All Access to all passengers, violating SOP guidelines.
|-
|Overly abusive department heads mistreating subordinates or disregarding SOP duties.
|-
|Complete neglect of SOPs, acting outside the expected responsibilities of the role.
|-
|General LRP behavior or violating Rule 3 regarding MRP logic.
|}

== Rule 14 - Continuity Guidelines ==
Some information, continuity, and memory is carried between rounds on Starlight, within set limits. This is accomplished in universe by the PSO Cloning System, and comes with some limits and rules to ensure smooth roleplay and minimal disruption.

You can only remember information from shifts that you survive. This means if you are stranded or killed, you forget the shift completely. If your body is revivable when it reaches CentComm, you also remember the shift but you forget all of the details leading up to your death per Rule 3. Placing yourself in a cryopod will allow you to remember details up until you’ve entered the cryopod.

'''Any information that is [[Metashield|Metashielded]] is forgotten between shifts''', and is wiped from your clone's memory.

IE: A Captain who survives a Revolution will still have information about the Revolution wiped, and won't remember it happening that shift.

You may remember that crimes occurred, but you will never remember who committed them. This includes if you yourself were a Syndicate Agent.

Examples of things you '''can''' remember:
{| class="wikitable"
|Social interactions with another character, such as getting drinks at the bar or even getting into an argument
|-
|Which jobs characters usually work- though this may not be used to meta that something is 'up' if someone isn't working their usual job
|-
|The layout of the station, though some leeway should be given for forgetting secret rooms- maints are an ever changing maze even if they look the same every shift for OOC reasons
|}
Examples of things you '''can't''' remember:
{| class="wikitable"
|Joe the Botanist was a Syndicate who stole the Captain's Jetpack
|-
|Nuclear Operatives attacking the station
|-
|CentComm calling Code Epsilon and killing a bunch of people on the station
|-
|Witnessing a Hollow body or seeing a Changeling eat someone
|-
|As NanoTrasen Representative, remembering that last shift had Nuclear Operatives
|}

Project REDACTED

2025-08-26T02:34:17Z

Grapegifter:

[[File:REDACTED logo.png|thumb|'''[Visual Transmission Received Successfully]''']]<blockquote>

'''''[Begin Transmission]''''' ''"Carter, this is the best I could grab at a moment's notice, I cou--n't find the name, but the l-st central command st--ion to fall....this was recorded. I th-nk -t's Re-a--" '''[End Transmission]'''''</blockquote>θ Heri vixisti, hodie mori meministi. θ

All '''██████''' ''<s>ᛗꝋɍⱦīꞩ</s>'' assets are to be considered '''unique''', '''non-interchangeable''', and inherently dangerous. Subjects are not to be brainwashed, reconditioned, or mentally altered unless greenlit by CRONUS class security clearance. Each retains full autonomy, tactical decision-making rights, and unredacted memory continuity.

Subjects are preserved in [REDACTED] containment pods until mission parameters require activation. Deployments are strictly limited to '''solo''' or '''pair''' operation protocols. Excessive usage or stacking of '''██████''' assets increases exposure risk to CSOD and the House of the Nine.

'''Subject ██████ is to be regarded as irreplaceable.'''

Project REDACTED

2025-08-26T02:32:52Z

Grapegifter:

[[File:REDACTED logo.png|thumb|'''[Visual Transmission Received Successfully]''']]<blockquote>

'''''[Begin Transmission]''''' ''"Carter, this is the best I could grab at a moment's notice, I cou--n't find the name, but the l-st central command st--ion to fall....this was recorded. I th-nk -t's Re-a--" '''[End Transmission]'''''</blockquote>θ Heri vixisti, hodie mori meministi. θ

All '''██████''' assets are to be considered '''unique''', '''non-interchangeable''', and inherently dangerous. Subjects are not to be brainwashed, reconditioned, or mentally altered unless greenlit by CRONUS class security clearance. Each retains full autonomy, tactical decision-making rights, and unredacted memory continuity.

Subjects are preserved in [REDACTED] containment pods until mission parameters require activation. Deployments are strictly limited to '''solo''' or '''pair''' operation protocols. Excessive usage or stacking of '''██████''' assets increases exposure risk to CSOD and the House of the Nine.

'''Subject ██████ is to be regarded as irreplaceable.'''

Security SOP

2025-08-25T14:29:48Z

Grapegifter: /* Duty Officer */

= '''Starlight Security SOP''' =
This SOP is intended to assist the station’s crew in proper behavior of security personnel. Any violations of this SOP should be brought to the Head of Security or Captain. Do note that SOPs should be taken in light of the context however, and are not rigid rules and may be malleable depending on the circumstances. Space law should be consulted for any imprisonment times or conflicts.

== General Security ==
<blockquote>These procedures apply to all security members, unless otherwise stated in their specific SOP</blockquote>

1. Long guns shall not be taken outside the brig on Code Green. Long guns are any firearms that are not pistols or revolvers.

2. A maximum of 1 long gun (with permit) and 1 sidearm (pistol or revolver) may be carried on blue alert or above. Only a sidearm and disabler may be carried on green.

2. Long guns will be issued on a permit basis on Code Blue, and are allowed to all Security Personnel on Code Red. Disabler SMGs are not considered long guns.

3. Weapons must remain holstered unless in active pursuit or on Code Red.

4. Security personnel are required to state the reason for an arrest before any action may be taken against a suspect. This does not apply on Code Red, or if a suspect flees when approached.

5. Security personnel must attempt to bring suspects to the brig uncuffed. This does not apply on Code Red, or if a suspect has already fled or become uncooperative.

6. Security personnel may not request entry to a department, unless in pursuit of a suspect, or on Code Blue or Code Red.

7. Searches may be conducted randomly on Codes Red and Blue, and on Green with an applicable warrant. Crew refusing searches on Blue/Red may be detained.

8. All Security personnel must wear at least one piece of an official Security uniform at all times. An official Security Uniform is defined as: The Security Jumpsuit/skirt, the Senior Security Jumpsuit/skirt, the Security Winter Coat, the Trooper Uniform, or job specific variants of these for the Warden, Head of Security, or Brigmedic.

9. Security personnel should refrain from wearing hardsuits or magboots unless an imminent threat or massive station damage is present.

10. Security personnel may forcefully relocate crew members to their departments on Codes Red, Violet, Yellow, or Gamma.

== Cadet ==
1. Cadets are to assign themselves to a Security Officer if one is not assigned to them.

2. Cadets may only use lethal equipment on Code Red.

== Security Officer ==
1 . Standard Code Green equipment is:

* Disabler
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite
* Lethal sidearm

2. Security Officers are to patrol the station unless an active threat has been recognized.

3. Security Officers are responsible for assigning sentences up to 15 minutes, but should inform the Warden of the accusation and sentencing if timing exceeds 10 mintues. Sentences over 15 minutes must be approved by the warden or Head of Security.

4. It is advised on Code Blue or above that Security Officers patrol the station in pairs.

== Brigmedic ==
1 . Standard Code Green equipment is:

* Disabler
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Advanced Medkit
* Seclite
* BrigBuddy 5000
* Brigmedic Defibrillator
* Lethal sidearm

2. Brigmedics may not perform Security Officer duties unless Security is severely understaffed, or a crime has occurred in their sight.

3. Brigmedics must prioritize the health and safety of Security Officers and Prisoners over all other priorities.

4. Brigmedics putting themselves in excessive danger, and by extension the entire department, are to be considered negligent in their duties.

== Warden ==
1 . Standard Code Green equipment is:

* Lethal sidearm
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The Warden may not perform normal Security Officer duties, or arrests, if sufficient numbers of Security Officers are active. This is waived on Code Red or above.

3. The Warden may choose to hand out armory weapons on Code Blue with a permit, or Code Red or above.

4. The Warden may choose to hand out body armor on Code Blue or above.

4. Uncooperative prisoners, or those deemed to be a flight risk may be cuffed, straightjacketed, or have an electropack placed on them.

5. Portable flashers and Barriers may be deployed on Code Blue or above.

6. The Warden may appoint a Duty Officer to assist with prisoner keeping duties with permission from the HoS.

== Duty Officer ==
1. Standard Code Green equipment is:
* Light riot helmet
* Riot suit
* Riot shield
* 4 x Non-lethal grenades
* Stun baton
* Security Radio
* 2x Handcuffs
* 2x Zipties
* Holobarrier Projector
* Seclite
2. The Duty Officer reports directly to the Warden. The Duty Officer is to assist in the processing of prisoners.

3. The Duty Officer is to directly communicate to the Warden at the start of the shift, and any time they are required to leave the department.

4. The Duty officer may not perform the duties of a Security Officer, unless the department is short on staff, or during emergencies.

5. Prisoner treatment guidelines must be strictly followed and is your top priority.

6. Non-lethal means should be used against prisoners whenever possible.

== Detective ==
1 . Standard Code Green equipment is:

* Inspector
* Forensic Gloves
* Forensic Scanner
* Forensic Pads
* Security Radio
* Seclite
* Combat Knife
* Holobarrier Projector
* Lethal sidearm

2. The Detective is permitted to patrol with a Security Officer on all alert levels, but should focus on collecting of evidence and investigations at all times.

3. When acting as a Security Officer, the Detective must follow all Security Officer guidelines listed above.

4. The Detective is permitted to wear non-security uniforms for undercover investigations, with approval from the Head of Security. The Detective's Security ID should be on their person at all times, however.

5. The Detective is permitted to interrogate detained suspects, however any detainment must be subtracted from their overall arrest time.

== Head of Security ==
1 . Standard Code Green equipment is:

* WT550 '''OR''' Proto Energy Gun
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The standard Command SOP applies with the exception of section 6, as for which, refer to the standard equipment listed above.

3. When patrolling, the Head of Security must follow all Security Officer protocols as above, but may carry their WT550 or Energy Gun.

4. The Head of Security may overrule any sentence that is not assigned by an official NT Magistrate, but not for prisoners who have already had their sentences read to them.

5. The Head of Security may not utilize the armory for their own personal benefit.

6. The Head of Security '''must''' follow the Warden's procedures for distributing any armory equipment, portable flashers, or portable barriers.

7. If a Code Red is called, the Head of Security '''must''' state the reason for the Code Red. The Captain may perform this duty instead, with permission from the Head of Security.

== Prisoner Treatment ==
1. Prisoners must be read their list of crimes before the warden before sentencing can commence. Any time spent in confinement must be subtracted from the total time of their sentence.

2. Arrested prisoners are to be searched upon entry to Security. IDs and PDAs are to be removed from prisoners while in confinement. Prisoners are to be provided/allowed their own radio communications equipment.

Prisoner Searches include:

* Pockets
* PDA Slots
* Bags
* Coats/Overwear

3. Prisoners placed into confinement are to be unrestrained. Prisoners who become combative or pose a flight risk may be restrained at the Warden's discretion.

4. Prisoners who receive perma/execution sentences may request a trial for their crimes, as decided by a jury of 12 of their peers. This may be waived in the face of imminent station destruction.

== Permit Acquisition ==
1. Requester delivers a filled out permit form for contraband to Warden, HoS, or in an emergency, Captain. It must contain Time and Date, requester's name and their position, a reason for the permit, and how the item will be or has already been obtained.
* Any illegal chemical which requires a prescription must provide a valid prescription with the permit that is signed or stamped appropriately.

2. Review the validity and necessity of the request.
* If the item requires delivery by a department other than sec, the permit must already be signed or stamped by the relevant head.
* If the permit requires a security item that is in limited stock it my be denied until more can be obtained.
* If the requester has already received a related permit the person reviewing can choose to deny the permit unless the old permit and contraband are turned in.
* Significant Syndicate Permits are never approved.

3. If the request is not unreasonable, it is stamped APPROVED, as well as signed and stamped by the person reviewing it.
* If the request is unreasonable it is stamped DENIED instead of APPROVED.

4. A copy is made for reference and stored in warden's office.

5. The document is given to the requester. If approved they are to keep it on their person at all times. If denied they are to be given a brief explanation as to why.
*If an approved permit is for security equipment, it is retrieved and provided.

Security SOP

2025-08-25T13:28:13Z

Grapegifter: /* Duty Officer */ small change, added one line

= '''Starlight Security SOP''' =
This SOP is intended to assist the station’s crew in proper behavior of security personnel. Any violations of this SOP should be brought to the Head of Security or Captain. Do note that SOPs should be taken in light of the context however, and are not rigid rules and may be malleable depending on the circumstances. Space law should be consulted for any imprisonment times or conflicts.

== General Security ==
<blockquote>These procedures apply to all security members, unless otherwise stated in their specific SOP</blockquote>

1. Long guns shall not be taken outside the brig on Code Green. Long guns are any firearms that are not pistols or revolvers.

2. A maximum of 1 long gun (with permit) and 1 sidearm (pistol or revolver) may be carried on blue alert or above. Only a sidearm and disabler may be carried on green.

2. Long guns will be issued on a permit basis on Code Blue, and are allowed to all Security Personnel on Code Red. Disabler SMGs are not considered long guns.

3. Weapons must remain holstered unless in active pursuit or on Code Red.

4. Security personnel are required to state the reason for an arrest before any action may be taken against a suspect. This does not apply on Code Red, or if a suspect flees when approached.

5. Security personnel must attempt to bring suspects to the brig uncuffed. This does not apply on Code Red, or if a suspect has already fled or become uncooperative.

6. Security personnel may not request entry to a department, unless in pursuit of a suspect, or on Code Blue or Code Red.

7. Searches may be conducted randomly on Codes Red and Blue, and on Green with an applicable warrant. Crew refusing searches on Blue/Red may be detained.

8. All Security personnel must wear at least one piece of an official Security uniform at all times. An official Security Uniform is defined as: The Security Jumpsuit/skirt, the Senior Security Jumpsuit/skirt, the Security Winter Coat, the Trooper Uniform, or job specific variants of these for the Warden, Head of Security, or Brigmedic.

9. Security personnel should refrain from wearing hardsuits or magboots unless an imminent threat or massive station damage is present.

10. Security personnel may forcefully relocate crew members to their departments on Codes Red, Violet, Yellow, or Gamma.

== Cadet ==
1. Cadets are to assign themselves to a Security Officer if one is not assigned to them.

2. Cadets may only use lethal equipment on Code Red.

== Security Officer ==
1 . Standard Code Green equipment is:

* Disabler
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite
* Lethal sidearm

2. Security Officers are to patrol the station unless an active threat has been recognized.

3. Security Officers are responsible for assigning sentences up to 15 minutes, but should inform the Warden of the accusation and sentencing if timing exceeds 10 mintues. Sentences over 15 minutes must be approved by the warden or Head of Security.

4. It is advised on Code Blue or above that Security Officers patrol the station in pairs.

== Brigmedic ==
1 . Standard Code Green equipment is:

* Disabler
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Advanced Medkit
* Seclite
* BrigBuddy 5000
* Brigmedic Defibrillator
* Lethal sidearm

2. Brigmedics may not perform Security Officer duties unless Security is severely understaffed, or a crime has occurred in their sight.

3. Brigmedics must prioritize the health and safety of Security Officers and Prisoners over all other priorities.

4. Brigmedics putting themselves in excessive danger, and by extension the entire department, are to be considered negligent in their duties.

== Warden ==
1 . Standard Code Green equipment is:

* Lethal sidearm
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The Warden may not perform normal Security Officer duties, or arrests, if sufficient numbers of Security Officers are active. This is waived on Code Red or above.

3. The Warden may choose to hand out armory weapons on Code Blue with a permit, or Code Red or above.

4. The Warden may choose to hand out body armor on Code Blue or above.

4. Uncooperative prisoners, or those deemed to be a flight risk may be cuffed, straightjacketed, or have an electropack placed on them.

5. Portable flashers and Barriers may be deployed on Code Blue or above.

6. The Warden may appoint a Duty Officer to assist with prisoner keeping duties with permission from the HoS.

== Duty Officer ==
1. Standard Code Green equipment is:
* Light riot helmet
* Riot suit
* Riot shield
* 4 x Non-lethal grenades
* Stun baton
* Security Radio
* 2x Handcuffs
* 2x Zipties
* Holobarrier Projector
* Seclite
2. The Duty Officer reports directly to the Warden. The Duty Officer, with the Warden's permission, may assist in the processing of prisoners.

3. The Duty Officer is to directly communicate to the Warden at the start of the shift, and any time they are required to leave the department.

4. The Duty officer may not perform the duties of a Security Officer, unless the department is short on staff, or during emergencies.

5. Prisoner treatment guidelines must be strictly followed and is your top priority.

6. Non-lethal means should be used against prisoners whenever possible.

== Detective ==
1 . Standard Code Green equipment is:

* Inspector
* Forensic Gloves
* Forensic Scanner
* Forensic Pads
* Security Radio
* Seclite
* Combat Knife
* Holobarrier Projector
* Lethal sidearm

2. The Detective is permitted to patrol with a Security Officer on all alert levels, but should focus on collecting of evidence and investigations at all times.

3. When acting as a Security Officer, the Detective must follow all Security Officer guidelines listed above.

4. The Detective is permitted to wear non-security uniforms for undercover investigations, with approval from the Head of Security. The Detective's Security ID should be on their person at all times, however.

5. The Detective is permitted to interrogate detained suspects, however any detainment must be subtracted from their overall arrest time.

== Head of Security ==
1 . Standard Code Green equipment is:

* WT550 '''OR''' Proto Energy Gun
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The standard Command SOP applies with the exception of section 6, as for which, refer to the standard equipment listed above.

3. When patrolling, the Head of Security must follow all Security Officer protocols as above, but may carry their WT550 or Energy Gun.

4. The Head of Security may overrule any sentence that is not assigned by an official NT Magistrate, but not for prisoners who have already had their sentences read to them.

5. The Head of Security may not utilize the armory for their own personal benefit.

6. The Head of Security '''must''' follow the Warden's procedures for distributing any armory equipment, portable flashers, or portable barriers.

7. If a Code Red is called, the Head of Security '''must''' state the reason for the Code Red. The Captain may perform this duty instead, with permission from the Head of Security.

== Prisoner Treatment ==
1. Prisoners must be read their list of crimes before the warden before sentencing can commence. Any time spent in confinement must be subtracted from the total time of their sentence.

2. Arrested prisoners are to be searched upon entry to Security. IDs and PDAs are to be removed from prisoners while in confinement. Prisoners are to be provided/allowed their own radio communications equipment.

Prisoner Searches include:

* Pockets
* PDA Slots
* Bags
* Coats/Overwear

3. Prisoners placed into confinement are to be unrestrained. Prisoners who become combative or pose a flight risk may be restrained at the Warden's discretion.

4. Prisoners who receive perma/execution sentences may request a trial for their crimes, as decided by a jury of 12 of their peers. This may be waived in the face of imminent station destruction.

== Permit Acquisition ==
1. Requester delivers a filled out permit form for contraband to Warden, HoS, or in an emergency, Captain. It must contain Time and Date, requester's name and their position, a reason for the permit, and how the item will be or has already been obtained.
* Any illegal chemical which requires a prescription must provide a valid prescription with the permit that is signed or stamped appropriately.

2. Review the validity and necessity of the request.
* If the item requires delivery by a department other than sec, the permit must already be signed or stamped by the relevant head.
* If the permit requires a security item that is in limited stock it my be denied until more can be obtained.
* If the requester has already received a related permit the person reviewing can choose to deny the permit unless the old permit and contraband are turned in.
* Significant Syndicate Permits are never approved.

3. If the request is not unreasonable, it is stamped APPROVED, as well as signed and stamped by the person reviewing it.
* If the request is unreasonable it is stamped DENIED instead of APPROVED.

4. A copy is made for reference and stored in warden's office.

5. The document is given to the requester. If approved they are to keep it on their person at all times. If denied they are to be given a brief explanation as to why.
*If an approved permit is for security equipment, it is retrieved and provided.

Security SOP

2025-08-25T05:15:31Z

Grapegifter: Duty Officer fixes

= '''Starlight Security SOP''' =
This SOP is intended to assist the station’s crew in proper behavior of security personnel. Any violations of this SOP should be brought to the Head of Security or Captain. Do note that SOPs should be taken in light of the context however, and are not rigid rules and may be malleable depending on the circumstances. Space law should be consulted for any imprisonment times or conflicts.

== General Security ==
<blockquote>These procedures apply to all security members, unless otherwise stated in their specific SOP</blockquote>

1. Long guns shall not be taken outside the brig on Code Green. Long guns are any firearms that are not pistols or revolvers.

2. A maximum of 1 long gun (with permit) and 1 sidearm (pistol or revolver) may be carried on blue alert or above. Only a sidearm and disabler may be carried on green.

2. Long guns will be issued on a permit basis on Code Blue, and are allowed to all Security Personnel on Code Red. Disabler SMGs are not considered long guns.

3. Weapons must remain holstered unless in active pursuit or on Code Red.

4. Security personnel are required to state the reason for an arrest before any action may be taken against a suspect. This does not apply on Code Red, or if a suspect flees when approached.

5. Security personnel must attempt to bring suspects to the brig uncuffed. This does not apply on Code Red, or if a suspect has already fled or become uncooperative.

6. Security personnel may not request entry to a department, unless in pursuit of a suspect, or on Code Blue or Code Red.

7. Searches may be conducted randomly on Codes Red and Blue, and on Green with an applicable warrant. Crew refusing searches on Blue/Red may be detained.

8. All Security personnel must wear at least one piece of an official Security uniform at all times. An official Security Uniform is defined as: The Security Jumpsuit/skirt, the Senior Security Jumpsuit/skirt, the Security Winter Coat, the Trooper Uniform, or job specific variants of these for the Warden, Head of Security, or Brigmedic.

9. Security personnel should refrain from wearing hardsuits or magboots unless an imminent threat or massive station damage is present.

10. Security personnel may forcefully relocate crew members to their departments on Codes Red, Violet, Yellow, or Gamma.

== Cadet ==
1. Cadets are to assign themselves to a Security Officer if one is not assigned to them.

2. Cadets may only use lethal equipment on Code Red.

== Security Officer ==
1 . Standard Code Green equipment is:

* Disabler
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite
* Lethal sidearm

2. Security Officers are to patrol the station unless an active threat has been recognized.

3. Security Officers are responsible for assigning sentences up to 15 minutes, but should inform the Warden of the accusation and sentencing if timing exceeds 10 mintues. Sentences over 15 minutes must be approved by the warden or Head of Security.

4. It is advised on Code Blue or above that Security Officers patrol the station in pairs.

== Brigmedic ==
1 . Standard Code Green equipment is:

* Disabler
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Advanced Medkit
* Seclite
* BrigBuddy 5000
* Brigmedic Defibrillator
* Lethal sidearm

2. Brigmedics may not perform Security Officer duties unless Security is severely understaffed, or a crime has occurred in their sight.

3. Brigmedics must prioritize the health and safety of Security Officers and Prisoners over all other priorities.

4. Brigmedics putting themselves in excessive danger, and by extension the entire department, are to be considered negligent in their duties.

== Warden ==
1 . Standard Code Green equipment is:

* Lethal sidearm
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The Warden may not perform normal Security Officer duties, or arrests, if sufficient numbers of Security Officers are active. This is waived on Code Red or above.

3. The Warden may choose to hand out armory weapons on Code Blue with a permit, or Code Red or above.

4. The Warden may choose to hand out body armor on Code Blue or above.

4. Uncooperative prisoners, or those deemed to be a flight risk may be cuffed, straightjacketed, or have an electropack placed on them.

5. Portable flashers and Barriers may be deployed on Code Blue or above.

6. The Warden may appoint a Duty Officer to assist with prisoner keeping duties with permission from the HoS.

== Duty Officer ==
1. Standard Code Green equipment is:
* Light riot helmet
* Riot suit
* Riot shield
* 4 x Non-lethal grenades
* Stun baton
* Security Radio
* 2x Handcuffs
* 2x Zipties
* Holobarrier Projector
* Seclite
2. The Duty Officer reports directly to the Warden.

3. The Duty Officer is to directly communicate to the Warden at the start of the shift, and any time they are required to leave the department.

4. The Duty officer may not perform the duties of a Security Officer, unless the brig is empty, or the department is short on staff, or during emergencies.

5. Prisoner treatment guidelines must be strictly followed and is your top priority.

6. Non-lethal means should be used against prisoners whenever possible.

== Detective ==
1 . Standard Code Green equipment is:

* Inspector
* Forensic Gloves
* Forensic Scanner
* Forensic Pads
* Security Radio
* Seclite
* Combat Knife
* Holobarrier Projector
* Lethal sidearm

2. The Detective is permitted to patrol with a Security Officer on all alert levels, but should focus on collecting of evidence and investigations at all times.

3. When acting as a Security Officer, the Detective must follow all Security Officer guidelines listed above.

4. The Detective is permitted to wear non-security uniforms for undercover investigations, with approval from the Head of Security. The Detective's Security ID should be on their person at all times, however.

5. The Detective is permitted to interrogate detained suspects, however any detainment must be subtracted from their overall arrest time.

== Head of Security ==
1 . Standard Code Green equipment is:

* WT550 '''OR''' Proto Energy Gun
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The standard Command SOP applies with the exception of section 6, as for which, refer to the standard equipment listed above.

3. When patrolling, the Head of Security must follow all Security Officer protocols as above, but may carry their WT550 or Energy Gun.

4. The Head of Security may overrule any sentence that is not assigned by an official NT Magistrate, but not for prisoners who have already had their sentences read to them.

5. The Head of Security may not utilize the armory for their own personal benefit.

6. The Head of Security '''must''' follow the Warden's procedures for distributing any armory equipment, portable flashers, or portable barriers.

7. If a Code Red is called, the Head of Security '''must''' state the reason for the Code Red. The Captain may perform this duty instead, with permission from the Head of Security.

== Prisoner Treatment ==
1. Prisoners must be read their list of crimes before the warden before sentencing can commence. Any time spent in confinement must be subtracted from the total time of their sentence.

2. Arrested prisoners are to be searched upon entry to Security. IDs and PDAs are to be removed from prisoners while in confinement. Prisoners are to be provided/allowed their own radio communications equipment.

Prisoner Searches include:

* Pockets
* PDA Slots
* Bags
* Coats/Overwear

3. Prisoners placed into confinement are to be unrestrained. Prisoners who become combative or pose a flight risk may be restrained at the Warden's discretion.

4. Prisoners who receive perma/execution sentences may request a trial for their crimes, as decided by a jury of 12 of their peers. This may be waived in the face of imminent station destruction.

== Permit Acquisition ==
1. Requester delivers a filled out permit form for contraband to Warden, HoS, or in an emergency, Captain. It must contain Time and Date, requester's name and their position, a reason for the permit, and how the item will be or has already been obtained.
* Any illegal chemical which requires a prescription must provide a valid prescription with the permit that is signed or stamped appropriately.

2. Review the validity and necessity of the request.
* If the item requires delivery by a department other than sec, the permit must already be signed or stamped by the relevant head.
* If the permit requires a security item that is in limited stock it my be denied until more can be obtained.
* If the requester has already received a related permit the person reviewing can choose to deny the permit unless the old permit and contraband are turned in.
* Significant Syndicate Permits are never approved.

3. If the request is not unreasonable, it is stamped APPROVED, as well as signed and stamped by the person reviewing it.
* If the request is unreasonable it is stamped DENIED instead of APPROVED.

4. A copy is made for reference and stored in warden's office.

5. The document is given to the requester. If approved they are to keep it on their person at all times. If denied they are to be given a brief explanation as to why.
*If an approved permit is for security equipment, it is retrieved and provided.

Security SOP

2025-08-22T04:55:35Z

Grapegifter: Duty officer added

= '''Starlight Security SOP''' =
This SOP is intended to assist the station’s crew in proper behavior of security personnel. Any violations of this SOP should be brought to the Head of Security or Captain. Do note that SOPs should be taken in light of the context however, and are not rigid rules and may be malleable depending on the circumstances. Space law should be consulted for any imprisonment times or conflicts.

== General Security ==
<blockquote>These procedures apply to all security members, unless otherwise stated in their specific SOP</blockquote>

1. Long guns shall not be taken outside the brig on Code Green. Long guns are any firearms that are not pistols or revolvers.

2. A maximum of 1 long gun (with permit) and 1 sidearm (pistol or revolver) may be carried on blue alert or above. Only a sidearm and disabler may be carried on green.

2. Long guns will be issued on a permit basis on Code Blue, and are allowed to all Security Personnel on Code Red. Disabler SMGs are not considered long guns.

3. Weapons must remain holstered unless in active pursuit or on Code Red.

4. Security personnel are required to state the reason for an arrest before any action may be taken against a suspect. This does not apply on Code Red, or if a suspect flees when approached.

5. Security personnel must attempt to bring suspects to the brig uncuffed. This does not apply on Code Red, or if a suspect has already fled or become uncooperative.

6. Security personnel may not request entry to a department, unless in pursuit of a suspect, or on Code Blue or Code Red.

7. Searches may be conducted randomly on Codes Red and Blue, and on Green with an applicable warrant. Crew refusing searches on Blue/Red may be detained.

8. All Security personnel must wear at least one piece of an official Security uniform at all times. An official Security Uniform is defined as: The Security Jumpsuit/skirt, the Senior Security Jumpsuit/skirt, the Security Winter Coat, the Trooper Uniform, or job specific variants of these for the Warden, Head of Security, or Brigmedic.

9. Security personnel should refrain from wearing hardsuits or magboots unless an imminent threat or massive station damage is present.

10. Security personnel may forcefully relocate crew members to their departments on Codes Red, Violet, Yellow, or Gamma.

== Cadet ==
1. Cadets are to assign themselves to a Security Officer if one is not assigned to them.

2. Cadets may only use lethal equipment on Code Red.

== Security Officer ==
1 . Standard Code Green equipment is:

* Disabler
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite
* Lethal sidearm

2. Security Officers are to patrol the station unless an active threat has been recognized.

3. Security Officers are responsible for assigning sentences up to 15 minutes, but should inform the Warden of the accusation and sentencing if timing exceeds 10 mintues. Sentences over 15 minutes must be approved by the warden or Head of Security.

4. It is advised on Code Blue or above that Security Officers patrol the station in pairs.

== Brigmedic ==
1 . Standard Code Green equipment is:

* Disabler
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Advanced Medkit
* Seclite
* BrigBuddy 5000
* Brigmedic Defibrillator
* Lethal sidearm

2. Brigmedics may not perform Security Officer duties unless Security is severely understaffed, or a crime has occurred in their sight.

3. Brigmedics must prioritize the health and safety of Security Officers and Prisoners over all other priorities.

4. Brigmedics putting themselves in excessive danger, and by extension the entire department, are to be considered negligent in their duties.

== Warden ==
1 . Standard Code Green equipment is:

* Lethal sidearm
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The Warden may not perform normal Security Officer duties, or arrests, if sufficient numbers of Security Officers are active. This is waived on Code Red or above.

3. The Warden may choose to hand out armory weapons on Code Blue with a permit, or Code Red or above.

4. The Warden may choose to hand out body armor on Code Blue or above.

4. Uncooperative prisoners, or those deemed to be a flight risk may be cuffed, straightjacketed, or have an electropack placed on them.

5. Portable flashers and Barriers may be deployed on Code Blue or above.

6. The Warden may appoint a Duty Officer to assist with prisoner keeping duties with permission from the HoS.

== Duty Officer ==
1. Standard Code Green equipment is:
* Light riot helmet
* Riot suit
* Riot shield
* 4 x Non-lethal grenades
* Stun baton
* Security Radio
* 2x Handcuffs
* 2x Zipties
* Holobarrier Projector
* Seclite
2. The Duty Officer reports directly to the Warden.

3. The Duty Officer is to directly communicate to the Warden at the start of the shift.

4. Prisoner treatment guidelines must be strictly followed.

5. Non-lethal means should be used against prisoners whenever possible.

== Detective ==
1 . Standard Code Green equipment is:

* Inspector
* Forensic Gloves
* Forensic Scanner
* Forensic Pads
* Security Radio
* Seclite
* Combat Knife
* Holobarrier Projector
* Lethal sidearm

2. The Detective is permitted to patrol with a Security Officer on all alert levels, but should focus on collecting of evidence and investigations at all times.

3. When acting as a Security Officer, the Detective must follow all Security Officer guidelines listed above.

4. The Detective is permitted to wear non-security uniforms for undercover investigations, with approval from the Head of Security. The Detective's Security ID should be on their person at all times, however.

5. The Detective is permitted to interrogate detained suspects, however any detainment must be subtracted from their overall arrest time.

== Head of Security ==
1 . Standard Code Green equipment is:

* WT550 '''OR''' Proto Energy Gun
* Non-lethal grenades
* Stun baton
* Combat Knife
* Security Radio
* Handcuffs or Zipties
* Holobarrier Projector
* Seclite

2. The standard Command SOP applies with the exception of section 6, as for which, refer to the standard equipment listed above.

3. When patrolling, the Head of Security must follow all Security Officer protocols as above, but may carry their WT550 or Energy Gun.

4. The Head of Security may overrule any sentence that is not assigned by an official NT Magistrate, but not for prisoners who have already had their sentences read to them.

5. The Head of Security may not utilize the armory for their own personal benefit.

6. The Head of Security '''must''' follow the Warden's procedures for distributing any armory equipment, portable flashers, or portable barriers.

7. If a Code Red is called, the Head of Security '''must''' state the reason for the Code Red. The Captain may perform this duty instead, with permission from the Head of Security.

== Prisoner Treatment ==
1. Prisoners must be read their list of crimes before the warden before sentencing can commence. Any time spent in confinement must be subtracted from the total time of their sentence.

2. Arrested prisoners are to be searched upon entry to Security. IDs and PDAs are to be removed from prisoners while in confinement. Prisoners are to be provided/allowed their own radio communications equipment.

Prisoner Searches include:

* Pockets
* PDA Slots
* Bags
* Coats/Overwear

3. Prisoners placed into confinement are to be unrestrained. Prisoners who become combative or pose a flight risk may be restrained at the Warden's discretion.

4. Prisoners who receive perma/execution sentences may request a trial for their crimes, as decided by a jury of 12 of their peers. This may be waived in the face of imminent station destruction.

== Permit Acquisition ==
1. Requester delivers a filled out permit form for contraband to Warden, HoS, or in an emergency, Captain. It must contain Time and Date, requester's name and their position, a reason for the permit, and how the item will be or has already been obtained.
* Any illegal chemical which requires a prescription must provide a valid prescription with the permit that is signed or stamped appropriately.

2. Review the validity and necessity of the request.
* If the item requires delivery by a department other than sec, the permit must already be signed or stamped by the relevant head.
* If the permit requires a security item that is in limited stock it my be denied until more can be obtained.
* If the requester has already received a related permit the person reviewing can choose to deny the permit unless the old permit and contraband are turned in.
* Significant Syndicate Permits are never approved.

3. If the request is not unreasonable, it is stamped APPROVED, as well as signed and stamped by the person reviewing it.
* If the request is unreasonable it is stamped DENIED instead of APPROVED.

4. A copy is made for reference and stored in warden's office.

5. The document is given to the requester. If approved they are to keep it on their person at all times. If denied they are to be given a brief explanation as to why.
*If an approved permit is for security equipment, it is retrieved and provided.

Classified Documents

2025-08-21T13:46:03Z

Grapegifter: Added lore

<blockquote>''[Incoming Transmission. Transmission playing now.]''

Carter? It's Gil. I know we haven't talked since you left, but I've found something. I've set up a network here, I'll get out what I can when I can, don't dig too deep, they're watching.

Sending the file upload after this, I pray it reaches you. I'll keep trying to establish contact, maybe one of these will get to you.

''[End Transmission]''

''[Beginning file download]''</blockquote>You're not supposed to be here.

=== Classified - NanoTrasen ===

* [[NanoTrasen Special Forces]]

=== Classified - CSOD ===
* [[After Action Report - Central Command Station 319]]
* <s>[[Project REDACTED|{REDACTED}]]</s>
** [[Panacea]]
** [[Prometheus|Prometheus]]
** [[Artemis]]
** [[Hercules|Hercules]]
** [[Hephaestus|Hephaestus]]
** [[Charon|Charon]]
** [[Thanatos]]

* [[PSO Cloning System]]
** [[Pantheon Subject Optimization]]

=== Classified - CID ===
*[[Ouroboros Operatives]]
**[[Mnemosyne]]
**[[Hyperion]]

=== Classified - CSD ===

* Potential Threats
** [[Terror Spiders|[REDACTED]]]

=== Classified - CRD ===
** [[Catabion|[REDACTED]]]
<blockquote>''[File Download End]''</blockquote>