https://wiki.deltav.gay/api.php?action=feedcontributions&feedformat=atom&user=Lyndomen 2026-04-10T02:53:50Z User contributions MediaWiki 1.43.0 https://wiki.deltav.gay/index.php?title=Standard_Operating_Procedure&diff=4154 2025-06-22T16:35:36Z

<p>Lyndomen: /* Treatment of Prisoners */</p> <hr /> <div>This page covers the standardized guidelines and procedures aboard the station, but are not written in law; be aware that in cases of dire emergency the commanding officer or certain individuals are authorized to temporarily alter current SOP as they see fit, at the risk of criminal penalties in the case of misuse or abuse! Make sure to look at [[Alert Procedure]] for guidelines that change based on the current alert level.<br /> =General Regulations=<br /> <br /> == '''Definitions''' ==<br /> The terms specified below are defined for further use within the procedures.<br /> :*Captain: The officer legally appointed by Nanotrasen as Commanding Officer of the station. This title is only transferable by Central Command.<br /> :*Commanding Officer / CO: An officer appointed to lead the station and its Command department, whether it be the Captain by Nanotrasen, or an Acting CO by Station Command.<br /> :* Command Staff/Station Command: Members of the Command department who lead a department aboard the station.<br /> :* Crew: All sophonts employed by Station Command, or by NT to reside on the station and perform an established function therein. This includes any sophont listed on the Crew Manifest or issued a functional NT identification and access card. Individuals imprisoned by NT, along with those imprisoned during the course of a shift for violations of Space Law, are considered Crew.<br /> :* Judge: An indivudal legally appointed to preside over a criminal or civil trial, as specified within Trial Procedure.<br /> :* Detainee: Any sophont whose free movement has been curtailed by law enforcement on suspicion of criminal activity. They have not, however, been officially charged with a crime.<br /> :* Arrestee: Any sophont who has been formally charged with a crime.<br /> :* Prisoner: Any sophont who has been sentenced for the commission of a crime, or awaiting trial for a capital offense.<br /> :* Permanent Brig/Permabrig/Brig: A secure location for the long-term confinement of Prisoners. Typically outfitted to sustain the basic survival needs of the Prisoners within.<br /> ==Right to Refuse Service==<br /> All crew operating within their designated job locations are given the right to refuse service at any time for disorderly or abusive conduct. Additionally, all crew members are permitted to use nonlethal force to remove noncompliant or disorderly individuals only when such persons pose a threat to the safety of staff members, or disrupt the orderly functioning of the station. Service may not be refused to first responders acting to address or mitigate an emergency or crisis situation, unless such conduct is egregiously disorderly or abusive.<br /> <br /> ==Hiring Procedure==<br /> While Nanotrasen handles the staffing and recruiting needs of the station, Station Command is additionally authorized to hire any sophont into their respective department, as well as terminate the employment of any crew in their respective department per company policy. For a member of Station Command to personally employ a sophont into their department, a contract must be written stating the name of the employee, the department of employment, the position, and finally bearing the stamp of the Station Command member.<br /> =Controlled Items, Substances, &amp; Areas=<br /> <br /> == Controlled Items ==<br /> Controlled Items include any item that is restricted from general possession and use. Additionally, any equipment or technology providing insight into the development, production, or procurement of a controlled item is also controlled in and of itself. A list of such items follows:<br /> <br /> * Any Controlled Substances, as listed below.<br /> * Any Controlled Armaments, as listed below.<br /> * Electromagnetic pulsing and/or disturbance technology.<br /> * Cryptographic systems, software, or technology.<br /> * Nuclear materials, weapons, and technology.<br /> * Long-range telecommunications and broadcasting technology.<br /> * Astronavigational guidance equipment or technology.<br /> * Telecommunication or signal jamming technology.<br /> * Telecommunications encryption technology.<br /> * Hypodermic spray tools and injectors.<br /> * Cloaking, chameleon, and IFF-inhibiting technology.<br /> * Technology utilizing bluespace as an integral part of its function.<br /> * Teleportation and portal technology.<br /> * Hydraulic or powered equipment designed for the electronic or mechanical bypass of secure-access systems.<br /> <br /> Any individual requiring any above item in the course of their job, or for regular function, may request a document of authorization from the relevant departmental head. Such a document must have an itemized list of the approved Controlled Items, the name and position of the holder, and a signed and stamped statement by the authorizing party.<br /> <br /> Should the holder commit crimes through the use of such authorized items, the authorizing party may be found guilty of Accessory to said crimes, in addition to Endangerment and Abuse of Power where applicable. The Commanding Officer is also authorized to supervise the approval and revocation of documentation as they see fit.<br /> <br /> == Controlled Substances ==<br /> Any individual requiring a Controlled Substance in the course of their job, or for regular function, must request access to a perscription or special dispensation from the Chief Medical Officer. The Psychologist is also permitted to grant prescriptions for psychoactive drugs. Any such document must state the substance(s) being prescribed, the amount(s) where applicable, and the stamp and signature of the authorizing party.<br /> <br /> A list of such Substances follow:<br /> <br /> * Mindbreaker Toxin and other psionically altering agents.<br /> * Romerol, and other rapid acting biological or chemical agents.<br /> * Desoxyephedrine, and similar stimulants.<br /> * Nocturine, and similar sedatives.<br /> * Phlogiston, and other explosive and/or pyrotechnic compounds.<br /> * Amatoxin, and other toxic and/or poisonous compounds.<br /> * Blissifylovene, Soretizone, Tranquinase, and all similar psychoactives used to aid in mental wellbeing.<br /> <br /> == Controlled Armaments ==<br /> <br /> <br /> Controlled Armaments are grouped into categories of increasing severity.<br /> <br /> '''Category A:''' ''Illegal possession of Cat. A controlled armaments may incur a sentence of up to 5min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed, adapted, or used to cause physical harm in close combat<br /> * Any object or equipment specifically designed or adapted to protect against physical harm caused by weapons, projectiles, or other forms of direct assault<br /> * Any object or instrument specifically designed or adapted to incapacitate or disorient by using light or sound without causing permanent injury<br /> * Any object or equipment specifically designed or adapted for explicitly training purposes that would otherwise fall under another category<br /> <br /> '''Category B:''' ''Illegal possession of Cat. B controlled armaments may incur a sentence of up to 10min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed or adapted to cause physical harm in close combat, which employs a powered system to enhance performance<br /> * Any manually-operated ballistic arms that possess an internal magazine or feeding system, or lack an internal magazine or feeding system altogether<br /> <br /> '''Category C:''' ''Illegal possession of Cat. C controlled armaments may incur a sentence of up to 15min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any manually-operated ballistic arms that use an external magazine or feeding system<br /> * Any semi-automatic ballistic arms not easily concealable within a pocket or coat<br /> * Any object or instrument specifically designed or adapted for explicitly less-lethal purposes that would otherwise fall under another category<br /> <br /> '''Category D:''' ''Illegal possession of Cat. D controlled armaments may incur a sentence of up to 20min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any semi-automatic ballistic arms that are easily concealable<br /> * Any fully-automatic ballistic arms<br /> * Any laser, plasma, or energy based arms, including ones designed, intended, or used for melee combat.<br /> * Any object or device specifically designed or adapted to cause physical harm through detonation of an explosive charge<br /> * Any object or equipment specifically designed or adapted to protect against both a space environment and physical harm caused by weapons, projectiles, or other forms of direct assault<br /> <br /> '''Category E:''' ''Illegal possession of Cat. E controlled armaments may incur a sentence of up to 25min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any crew-served or emplaced weapon<br /> * Any object or instrument specifically designed or adapted to launch large-calibre explosives or projectiles for offensive or defensive purposes<br /> * Any object or instrument specifically designed or adapted to employ chemical, biological, esoteric, radiological, or nuclear hazards for offensive or defensive purposes<br /> <br /> Armaments licenses may be issued by the Commanding Officer, Warden, or Head of Security. The license must include the name of the holder, a list of allowed armaments, and a stamped signature from the issuer.<br /> <br /> If the holder uses their armaments in the commission of a crime, the issuer may be held liable for accessory to the crimes committed, along with Endangerment and Abuse of Power where applicable.<br /> <br /> == Departmental Dispensations ==<br /> Certain bodies, groups, or personnel may require certain Controlled Items in the course of their job, and as such must be provided exceptions. '''Any member of any department which begins their shift with a controlled item in their possession or within their department’s allocated area is assumed authorized for its possession and use.'''<br /> <br /> Additionally, tools and equipment located within emergency lockers are not considered Controlled Items, so long as they are used as intended.<br /> <br /> ===Logistics===<br /> Members of a station’s Logistics department are permitted to approve any order with the direct permission of an individual with legal access to the contents of that order. Additionally, they may deny any order, at any time, for lack of funds, authority, or any other reason deemed sufficient by their direct superior.<br /> <br /> Unlocked crates, orders stored outside the department, and supplies illegally distributed to unauthorized personnel carry the risk of Endangerment of even Black Marketeering charges. Crates of Controlled Items, Substances, or Armaments should be stored securely within the department, with a copy of their invoices on file.<br /> <br /> === Research ===<br /> Epistemics employees are permitted to use their lab spaces as they see fit, with the following caveats:<br /> <br /> * Any sophont experimentation must be done with the consent of the test subject, and must not have an undue risk of life. The Mystagogue or CO may terminate any experiment for safety or ethical purposes and at their discretion.<br /> * Self-experimentation is prohibited and is chargeable with Endangerment, at a minimum.<br /> * Testing of any explosives or weapons that risk hull penetration or mass destruction must be done at an off-station site.<br /> <br /> Epistemics personnel may also utilise Controlled Items within the confines of designated testing areas and in a manner directly approved jointly by the Mystagogue and by the Head of Security or CO.<br /> <br /> Utilizing or storing Controlled items without direct approval, utilizing Controlled Items outside of the testing areas, and distributing Controlled Items to crew constitute criminal offences under Space Law and may additionally incur demotion as punishment.<br /> <br /> === Medical ===<br /> All medical personnel may carry or use Controlled Substances, along with hypodermic tools, in the course of their job functions and in a manner approved by the CMO or CO, with the following caveats:<br /> <br /> * Any Controlled Substance with the capability to cause rapid and grievous bodily harm or death may not be carried outside of the chemicals lab or treatment areas without a signed and stamped document of authorization.<br /> * Any Controlled Substance with the capacity to cause harm as a consequence of overdose may not be stocked, stored, or displayed in any area or fashion that leaves such substances open and accessible to the public.<br /> * Any hypodermic tool must be kept secure within locked storage or on the person of an authorized individual.<br /> <br /> ==High Security Areas==<br /> High Security Areas, or HSAs, should be restricted, and, during standard station operations, secured where applicable or per alert level. They differ from regular secure areas in that they may contain items, technology, or other assets of high importance or value, and must therefore be held safe. Unauthorized persons within HSAs may be guilty of trespass, or of breaking and entering.<br /> <br /> Common HSAs for commercial and military vessels are as follows:<br /> <br /> * Bridge<br /> * Armory\Gun Deck<br /> * Vault\Strongroom<br /> * Station AI Rooms (Upload, Core, etc.)<br /> * Gravity Generation\Life Support\Engine Rooms<br /> * Telecommunications\Telemetry<br /> * Permanent Brig\Holding Cells<br /> <br /> == Sophonts and Synthetics ==<br /> To be defined as a sophont, a being must be able to utilize a structured language, communicate through the use of written, verbal, and/or body language (or by other means), and possess reasoning and introspection.<br /> <br /> Any such being is considered a sophont, and thus a legal person, regardless of their make, origin, disposition, or prior cognition. As part of their rights, they are to be governed under the same laws as any other sophont, and given the ability to press charges as a sophont.<br /> <br /> The unauthorised jailbreaking or uplifting of property into the status of Sophont is still a criminal offense however, and those found guilty of doing so may be found guilty of sabotage or vandalism.<br /> <br /> An entity’s status as a sophont may be challenged during the process of charging and trialing the individual or another for crimes which utilize the term sophont in the legal language of the crime. The Defense or Prosecution will present evidence indicating that it meets, or does not meet, the criteria above. The Judge will then arbitrate upon the entity's status as a sophont.<br /> <br /> Any synthetic/silicon/inorganic entity with a non-sophont status, is to be classified as a standard synthetic entity. Synthetic entities are the property of the party that constructs or employs the entity, unless otherwise stated by relevant contract or legal document. To damage or destroy such an entity is to damage or destroy the aforementioned party’s property.<br /> =Commanding Officer=<br /> ==Captain’s Authority==<br /> The Commanding Officer of a station or vessel is afforded several rights, broadly referred to as &quot;Captain's Authority&quot;.<br /> <br /> While they are formally and legally appointed CO, they are the ultimate authority aboard a vessel until they are directly dismissed by a superior from Central Command.<br /> <br /> Additionally, they have the authority to pardon and/or parole any individuals accused and sentenced of Grand Felony, Felony, and Misdemeanor-level sentences if deemed in the best interest of the crew and vessel. The CO may be held liable for accessory to any future criminal acts performed by the pardoned individual, and they must make an announcement to the station stating who was pardoned, for what crimes, and for what reason.<br /> <br /> Captain’s Authority carries a responsibility, however; the CO must do everything in their power to protect all entities and assets aboard the station with which they have been entrusted, and must not abandon them while there is a reasonable hope that they may be saved.<br /> <br /> Additionally, the legally appointed Captain of a vessel is afforded two additional rights over that of a CO:<br /> <br /> * To, with public announcement to the crew, temporarily modify SOP in times of emergency, at the risk of criminal penalties if misused or abused, and<br /> * To deputize members of the crew to carry out law enforcement activity. These deputies are bound by Security Regulations and Space Law, and the Captain may suffer criminal penalties for any crime committed by them.<br /> <br /> ==Line of Succession==<br /> It is the responsibility of Command to ensure that a station retains a CO immediately at the start of the shift and thereafter. If the CO dies and is unrecoverable, or if a CO is not assigned at the start of the shift, an Acting CO must be selected forthwith per the following guide:<br /> <br /> # All active members of Station Command must meet, and choose one of their number to become the Acting CO.<br /> # If no Station Command is alive or on active duty, then each Department must nominate a temporary Delegate. These Delegates must meet and choose an Acting CO from among their number.<br /> # The Acting CO must then duly inform Central Command via fax and make a stationwide announcement.<br /> # Await the end of your shift.<br /> <br /> After Central Command has received the results of the Line of Succession, the Acting CO is afforded all prescribed powers of a CO. An access biscuit ''may or may not'' be sent by Centcomm to assist with this. When a legally appointed Captain arrives, it is the express duty of the Acting CO to hand over any and all Captain-related equipment and accesses to the new CO, and to resign themselves to their original role before their temporary promotion.<br /> ==Command Promotions==<br /> The CO of the vessel is authorized to promote Crew into Station Command positions if it is determined that the vacancy is a detriment to station productivity. The CO has a duty to ensure that the Crew they promote are of a reasonable level of skill, and can be held liable if they disregard this duty.<br /> <br /> Crew members promoted into Station Command positions are considered to be acting members of Station Command, with all rights and responsibilities therein. When NT-appointed Station Command arrive, the acting Command members are required to hand over any specialized equipment (Command ID cards, attire, or tools) and resign themselves to their original position from before their temporary promotion.<br /> ==Mutiny==<br /> Should such a situation arise in which the CO is unfit for their position and declines relinquishment of position and power, and where all alternative legal options have been exhausted, officers may be permitted to lead a mutiny. Officers leading a mutiny must inform Central Command of this occurrence before the mutiny has begun.<br /> <br /> A mutiny, defined as a coordinated effort to depose the commanding officer or officers of a vessel for committing unlawful acts, requires the crew to neutralize the offending staff with non-lethal force where applicable, and lethal measures and weapons only in acts of self-preservation or when given no other option. The commanding officer or officers, as well as their loyalists, are all bound to Space Law, the current alert level and its corresponding RoE.<br /> <br /> Should the mutiny be unsuccessful, only the head officer(s) who approved the mutiny may be charged with sedition and receive a trial, while all mutineers may be demoted, processed by law enforcement, and charged for the crimes they have committed.<br /> <br /> Should the mutiny be successful, the head officer(s) who approved the mutiny must select a new Commanding Officer per Line of Succession. The new CO will then sentence the previous heads of staff for their crimes per Space Law.<br /> <br /> == Foreign Vessels ==<br /> Should civilian and military vessels receive a docking request from another neutral vessel, they may approve or deny such a request. Any vessel may, with consent from the docking entity, be searched by law enforcement upon arrival, and its crew granted free movement accompanied by an escort at the discretion of the CO or law enforcement officials.<br /> <br /> Crew of foreign vessels may be refused entry, at any time and for any reason, and must be returned to, or be escorted to, their own vessel where applicable. Failure to comply may constitute trespass. Docking vessels bearing a warrant or commission represent an exception, and may not be denied entry or be forced to submit to a search.<br /> <br /> Crimes committed against the station or its inhabitants, on station or abroad, are grounds to charge the perpetrator according to the laws of the station. Should visiting entities break the law, or be suspected of doing so, and flee aboard their own vessel, law enforcement personnel are authorized to board the vessel in continuous “hot” pursuit and are fully authorized to effect an arrest upon the relevant party.<br /> <br /> =Security Regulations=<br /> ==Security Jurisdiction==<br /> Law enforcement personnel are bound by trespass and assault laws, and thus cannot operate outside accessible areas, or perform searches without a Probable Cause, a warrant, or a heightened alert level that specifically allows such action. Advanced surgical procedures and cursory implant investigations must be performed by a trained member of the Medical department, operating under their [[Standard Operating Procedure#Standard of Care|Standard of Care]].<br /> <br /> However, officers are allowed to trespass into a department in “hot pursuit” of a suspect who has fled from an accessible area, who they have Probable Cause to believe has committed a crime<br /> <br /> ==Probable Cause==<br /> While actively enforcing the law, officers are held to the standard of Probable Cause. This phrase represents a reasonable suspicion that a crime has been, or is being, committed, and does not require the officer to have solid evidence of criminal activity. Examples of Probable Cause include witnessing criminal activity or credible reports of such.<br /> <br /> When judged, Probable Cause is to be interpreted within the context of the entirety of the station’s circumstances at the time of the incident. Probable Cause negates the need of a warrant for searches, and, once concluded, should be promptly reported to the Prosecutor, Warden, or Head of Security for review.<br /> <br /> ==Detainment and Arrest==<br /> Any sophont may be detained by a law enforcement officer with Probable Cause. In detainment, the officer will inform the Detainee of the crime they are suspected of committing. They may be held on-site or moved to a strategically sound location, restrained at the officer’s discretion, and detained while law enforcement officers determine if they can proceed with an arrest. Such a detention should last no longer than five (5) minutes. A Detainee may not be searched, unless consent is given or they are placed under arrest, and their detention should be concluded within five minutes of its start, by either Arresting them or releasing them.<br /> <br /> Any sophont which may have committed a crime, assuming Probable Cause, or has been formally charged with the commission of a crime, may be arrested. In an arrest, the suspect will be restrained by a member of law enforcement, informed of their charges, and taken to the brig for search and processing under Brig Procedure. Any Controlled Items in possession of the Arrestee without licensure or dispensation must be confiscated, along with items used in commission of the crime(s), and will be held indefinitely by law enforcement as described in [[Standard Operating Procedure#Evidence Handling|Evidence Handling]]. Legal counsel may be requested by an Arrestee or Detainee, and must be provided if available.<br /> <br /> ==Brig Procedure==<br /> When confining an Arrestee within the Brig, they should be transferred to the Warden for processing:<br /> <br /> * A full search of the Arrestee and their possessions.<br /> * The confiscation of any Controlled Items or items used in commission of the crime, along with any equipment not befitting a prisoner<br /> * The confining of the Arrestee within a temporary holding cell.<br /> * [[Standard Operating Procedure#Sentencing|Sentencing]] the Arrestee.<br /> <br /> If the Arrestee is sentenced for a Capital-level crime, they are to be transferred to the Permanent Brig, pending trial. If the Warden is unavailable, the arresting officer must process the Arrestee as stated above. All confiscated items must be handled as dictated within [[Standard Operating Procedure#Evidence Handling|Evidence Handling]].<br /> <br /> ==Sentencing==<br /> Any law enforcement individual is authorized to pass sentences on all Grand Felony, Felony and Misdemeanor-level crimes; however, the Prosecutor is responsible for overseeing sentences passed, and is authorized to correct sentences or even acquit them, in accordance with both Space Law and [[Standard Operating Procedure#Paroles and Pardons|Paroles and Pardons]]. Both capital charges and sentences must be placed by the Prosecutor or Court Clerk; if neither are available, the Warden or Head of Security are authorized to press capital charges and request sentencing for them, under Trial Procedure.<br /> <br /> In the case that the accused requests appeal for a Grand Felony- or Felony-level sentence, the Court Clerk should be called to preside over a small, swift adjudication, where the Prosecutor and accused will argue their sides. The Clerk will then decide the sentence, or acquittal, of the accused. If the Clerk is unavailable, the Chief Justice or the Warden can perform appeals. If neither are available, any available member of Station Command is authorized to adjudicate on the case.<br /> <br /> Additionally, any sentence meeting or exceeding twenty-five (25) minutes, regardless of the severity of the crime(s) committed, will require a trial. If the total sentence still meets or exceeds twenty-five minutes after the conclusion of a lawful trial, the Judge is fully authorized and encouraged to upgrade their sentence to Extended Confinement.<br /> <br /> Once a sentence has commenced, it must be concluded at or before the agreed-upon time.<br /> <br /> == Evidence Handling ==<br /> When evidence of a crime is secured, it is the responsibility of the arresting officer or Warden to properly handle it, at the penalty of Obstruction of Justice and/or demotion.<br /> <br /> Evidence should be organized by individual and crime, and stored together (e.g., in a bag, in one separate locker, etc) and then placed in an area locked behind security access.<br /> <br /> If a prisoner is released from a temporary holding cell OR the Brig, any of their equipment that is neither a Controlled Item nor used in the commission of their crimes must be returned to them.<br /> <br /> == Rules of Engagement ==<br /> Law enforcement personnel hold a Category D Armaments License, and are authorized at all times to use lethal force to the extent necessary to neutralize adversaries under any of the following circumstances:<br /> <br /> * If the adversary’s number or strength leave the officer at a severe tactical disadvantage.<br /> * If the adversary exhibits a clear and present danger to the vessel by physical means.<br /> * If the adversary poses a significant threat of serious bodily injury or death to the officer or others.<br /> * If the adversary presents an existential threat to the chain of command by illegal means.<br /> * If the adversary cannot be reasonably subdued through non-lethal means without great bodily harm to the officer.<br /> <br /> …wherein an “adversary” is an entity that demonstrates a hostile intent, commits or directly contributes to a hostile act that does not constitute an actual attack, or is actively attacking the vessel or its crew.<br /> <br /> Despite their allowance of lethal force, Security is required to follow the Rules of Engagement of the current Alert Level, as outlined within [[Alert Procedure]].<br /> <br /> == Armory Procedure ==<br /> The armory and its usage are governed by the Warden. The Warden is responsible for stocking, distributing, and recording the collection of weapons used by the station during the shift. They are also afforded the authority to arm security at their discretion, so long as the weaponry distributed is in appropriate response to [[Alert Procedure]].<br /> <br /> All weaponry distributed from armory is issued on a temporary basis. While issued, the weaponry remains as station property, and the wielder assumes a duty to protect the weapon and return it to the Warden when ordered. No non-crew may be issued weaponry from the armory.<br /> <br /> The Warden is accountable for responsibly issuing weapons. Any weaponry issued during a heightened alert level must be returned when the alert has been lowered, or when the threat is no longer present. The weaponry issued must be proportionate to the threat posed, and explosives should not be used unless absolutely necessary.<br /> ==Treatment of Prisoners==<br /> Prisoners have certain rights that must be upheld by law enforcement and Station Command. ''Prisoners must be provided with the following'':<br /> <br /> * Adequate medical care and moral, spiritual, or legal counseling if it is requested and available.<br /> * Access to the Common and Prison radio channels only while serving their sentence. This right may be revoked should it be abused.<br /> * Standard prisoner clothing must always be available for prisoners.<br /> * Confiscated clothing should be returned upon request, except in the case of Extended Confinement or if the clothing in question poses a clear risk to prisoner or crew safety.<br /> * Food and water for organic prisoners must be available and given on request.<br /> * Power for silicon prisoners such as IPCs and cyborgs, at minimum a cyborg recharging station must be provided.<br /> * Should the holding cells or Permabrig become uninhabitable, prisoners must be securely and safely relocated to another area for confinement, until the holding cells or Permabrig are returned to a serviceable state.<br /> * Prisoners should be granted freedom of movement within their holding area unless there is an undue risk to life and limb.<br /> <br /> Additionally, prisoners sentenced to Extended Confinement have certain rights but also '''more firm restrictions that must be upheld by law enforcement''':<br /> <br /> * Visitation may be permitted only for prisoners sentenced to Extended Confinement. One person may visit such a prisoner for a period of no longer than ten minutes. A reason must be provided for the visit, and the visitor must consent to a search of their belongings. The prisoner is then unable to receive another visitor for another ten minutes.<br /> * Prisoners may request retrial for capital crimes; these requests may be refused depending on the discretion and availability of the court clerk, chief justice, or at the discretion of the warden or head of station security.<br /> * Prisoners may request or may otherwise be given parole with a hearing by the Chief Justice, Court Clerk, or in their absence, the head of station security or commanding officer (see Paroles and Pardons).<br /> <br /> Should prisoners repeatedly and maliciously antagonize law enforcement, to an extent where continued extended confinement becomes infeasible, the warden is fully authorized and encouraged to temporarily upgrade the relevant prisoners’ sentences to Preservative Stasis summarily.<br /> <br /> Moreover, prisoners are liable for any and all crimes that they commit while held either in the temporary holding cells or the Permanent Brig, and may receive trial for more restrictive punishments if their actions warrant a capital sentence.<br /> <br /> ==Paroles and Pardons==<br /> Prisoners may be allowed parole, per the discretion of the Warden, the Head of Security, or the CO. Alternatively, they may request a parole hearing as described within Trial Procedure.<br /> <br /> Prisoners seeking parole may request legal counsel before the hearing, but they must represent themselves. A prisoner who is granted parole is to be treated as a member of the station’s crew with all benefits and responsibilities thereof, and is encouraged to seek gainful employment from relevant command staff.<br /> <br /> Additionally, a pardon can be issued to any entity accused of, or sentenced to, crimes, by the arresting officer, the Judge of a trial, or the Warden in the case of those within the permanent brig, if deemed in the best interest of the crew and vessel, and when the circumstances of the defendant or their offense warrant a suspension of their sentence.<br /> <br /> =Justice Regulations=<br /> ==Pressing Charges==<br /> ===Criminal Charges===<br /> Any crew member may press charges against any other crew member. An individual may be charged of a crime if and only if it can be argued beyond a reasonable doubt that the accused had committed an act in the nature and fashion as described by a particular criminal charge.<br /> <br /> Multiple counts of one crime can be charged. For illegal actions against the station abroad, each incident separated by a reasonable period of inaction, lawful conduct, or another crime is interpreted as one count. For crimes directly bereaving a person (violent acts, theft of personal property etc.), the same applies in addition to each victim being one count. In the case of possession, theft, or any incident involving several separate and distinct items, one charge may be applied per relevant item.<br /> <br /> Charges that are a direct escalation of one another in nature cannot be simultaneously held against the perpetrator if they pertain to the same incident and the same victim/item (if applicable). Then, only the most severe of these charges applies. Additionally, if one charge incorporates another charge within its definition or description, the perpetrator cannot be held accountable for both; rather, only the most severe of these charges applies.<br /> ===Civil Charges===<br /> Any crew member can sue any other crew member for inflicting them with damages caused by a breach of duty. To sue is to request compensation for said damages. To do so, the victim must prove:<br /> *'''Damages:''' That the victim was inflicted with an emotional, physical, or monetary damage<br /> *'''Breach of duty:''' That the defendant had a duty which they failed to uphold(e.g., a duty to not endanger crew, a duty to act respectfully), leading to the victim being inflicted with a damage<br /> *'''Severity:''' That the damage was severe enough to warrant the compensation requested<br /> Compensation can either be explicitly specified by the victim or left for the court to decide. Either way, the court is free to modify the compensation as it sees fit. Most often, compensation is rendered in the form of court orders compelling a crew member to do something (e.g., return an item, make an apology, or permanently avoid a certain area). Court orders should be written and stamped with the notary stamp.<br /> <br /> ==Court Orders==<br /> The individuals specified in the three sections below can issue Court Orders, which are legally-enforced documents that carry the penalty of an Obstruction of Justice charge and forced compliance with the order by security. Each order has its own requirements and authorized issuers, but are all implied to require '''''the stamp (where applicable) and signature of the issuer to be valid.'''''<br /> ===Warrants===<br /> Warrants represent official orders to the security department, issued by relevant officers or the Justice Department. Warrants are only valid when issued by either the Chief Justice or Court Clerk, or in both of their absences, the Commanding Officer or head of station Security.<br /> <br /> * Individual Warrants may order the search or detainment of an individual, or the arrest of the individual with evidence. This may also include surgical procedures, cursory implant inspections, or any other invasive searches with both probable cause and evidence. These warrants should include a name, the actions prescribed (detainment, search, arrest, etc.), and a description if applicable.<br /> * Search Warrants may order the search of an entire departmental area, by force if necessary, and may order the arrest of listed individuals implicated in a crime or crimes with probable cause and evidence. Search Warrants should include an area, a brief description of the probable cause, and a list of individuals if applicable.<br /> <br /> ===Injunctions===<br /> The Chief Justice, Commanding Officer, or Judge of a trial are fully authorized to issue injunctions: legally-binding, written orders restricting Inhabitants from doing something disruptive to station productivity or personal rights.<br /> These may be issued on discretion or as relief for Civil Trials. Injunctions may not compel someone to violate Space Law or SOP, and the issuer is liable for abuse of power charges if this is misused. An injunction must include a list of affected names and a detailed description of the restrictions to be valid.<br /> <br /> ===Subpoenas===<br /> The Chief Justice, Court Clerk, or Judge of a trial may issue Subpoenas, which are trial-related Court Orders compelling an individual to produce evidence or make themselves present at a location for court. A subpoena can order an individual to:<br /> <br /> * Appear as a witness, defendant, plaintiff, or prosecution;<br /> * Produce evidence for a trial;<br /> * Appear for questioning in deposition.<br /> <br /> A subpoena must include a list of names, a detailed description of evidence requested or reason for appearing, and a reasonable time frame no shorter than 3 minutes. The individuals summoned by the subpoena must be informed of its presence for it to be a valid order. This can be done via general announcement, fax, verbal announcement, or otherwise.<br /> <br /> === Affidavits ===<br /> An Affidavit is a legal document, consisting of a formal written statement of witness. An Affidavit must be written by the witness, or Affiant, who must state their relation to the incident at hand, and must be signed and stamped (if applicable) by a member of Security, Justice, or Command, who is verifying that the contents of the Affidavit are true to the best of their knowledge. The witness to the Affidavit must not be directly connected to the incident.<br /> <br /> Affidavits are considered valid witness statements for use in a trial (see Trial Procedure, below), and can be used either in tandem with a verbal witness statement, or to obtain testimony from an affiant whose job requirements and/or personal circumstances make attending a trial unfeasible.<br /> <br /> An affidavit may be impeached- and thus removed from evidence- if the Prosecution or Defense can introduce testimony or other evidence that directly contradicts the statements recorded within the Affidavit. The Affiant may then be liable for criminal charges.<br /> <br /> =Trial Procedure=<br /> A trial may be requested for civil disputes and capital charges. Civil charges may be refused, depending on the availability and discretion of a potential Judge; however, capital crimes require a trial. This also includes non-capital trials required as dictated within Sentencing guidelines. Miscellaneous trials, such as those described within Paroles and Pardons, only require the Judge and the defendant.<br /> <br /> Criminal trials may be waived if a suspect pleads guilty to a member of the Justice or Security department, or to station command. Their sentence should be passed by a Judge immediately, without the need for a full hearing. The Judge should also sentence the defendant summarily if they are held in contempt of court during the trial.<br /> <br /> The trial takes the form of an arbitration court hearing, presided over by an appointed Judge, and including adequate Prosecution and Defense, as dictated below. All charges, arguments, and evidence must be filed with the Judge before the case begins. The trial shall begin when the Defense, Prosecution, and Judge are all present and ready to begin. A trial does not need to be open to the public.<br /> <br /> The Judge is charged with ensuring the trial is completed in a timely manner, and is granted the power to charge someone with Contempt of Court, under Space Law, if they disrupt the case. Suitable Judges should be chosen from the following list, in sequential order:<br /> <br /> # The Chief Justice<br /> # The Clerk<br /> # An impartial member of the Justice department.<br /> # An impartial member of Station Command.<br /> # The Warden.<br /> <br /> The Defense should ideally be a member of the Justice department assigned to argue in favor of the defendant; if none are available, the defendant may choose to represent themselves.<br /> <br /> The Prosecution should ideally be the Prosecutor; if they are unavailable, the case should be prosecuted by an unbiased member of Station Command or a law enforcement officer, in that order.<br /> <br /> If there is not a viable and/or willing Defense or Prosecution, the Judge is fully authorized and strongly encouraged to pass a summary sentence of Extended Confinement until an adequate trial can be held.<br /> <br /> ==Criminal Trials==<br /> A criminal case should take no longer than 25 minutes in total. Criminal cases should either have security personnel present, or plan to have them present by the end of the trial.<br /> :#The judge brings the court in session.<br /> :#Prosecution opens the proceedings, stating the charges and introducing witnesses and exhibits that will be brought forward during the presentation of evidence. They may also recommend a sentence to the judge, appropriate to the charge based on their opening statement.<br /> :#Defense enters their plea- Guilty or Not Guilty.<br /> :#If Guilty, the Judge is authorized to immediately pass a ruling, as stated below.<br /> :#If Not Guilty, they are to provide their own opening statement and introduce their own witnesses and exhibits where applicable.<br /> :#Presentation of evidence follows, lead by Prosecution, then Defense.<br /> :#*Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> :#Finally, closing statements are made by the Prosecution, Defense, and Prosecution once more due to burden of proof. No new evidence can be introduced within a closing statement.<br /> :#A ruling will be issued by the Judge, written down, and stamped with the Notary stamp, the Judge's stamp, and their signature.<br /> :#The Judge adjourns the court. Any present or soon-to-be-present Security personnel will then enact the ruling.<br /> <br /> == Civil Trials ==<br /> Civil cases do not require Prosecution or Defense, but they may receive assistance from either both before and during the case. Both the defendant and plaintiff must be made to summon at the court, if a party does not appear out of either refusal or negligence, or fails to comply with a court order from a civil trial, that party may be charged with contempt of court, a felony. A civil case involves seeking damages from a defendant, which could be monetary, an item, or otherwise. A civil case should take no longer than 15 minutes in total.<br /> <br /> # The Judge brings the court into session.<br /> # Plaintiff opens proceedings by stating the damages, before introducing witnesses and exhibits that will be brought forward during presentation of evidence. They may also reccomend civil relief to the judge, appropriate to the damages listed wthin their opening statement.<br /> # Defendant follows with their opening statement, contradicting the Plaintiff's theories and assertions. They will also introduce their own witnesses and exhibits, where applicable.<br /> # Presentation of evidence follows, led by the Plaintiff, then the Defendant.<br /> #* Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> # Finally, closing statements are made by the Plaintiff, Defense, and Plaintiff once more due to burden of proof. No new evidence should be introduced or referenced by these statements.<br /> # A ruling will be made by the Judge, written, and stamped by the Notary stamp, the Judge's stamp, and signed by the Judge.<br /> # The Judge adjourns court.<br /> <br /> Any ruling shall then be enacted; if a party refuses to follow through with the ruling, they may suffer criminal penalties.<br /> <br /> == Presentation of Evidence ==<br /> <br /> ===Eyewitness Testimony===<br /> Any sophont or other entity willing and capable of presenting themselves before court under oath and present at the scene of the crime as a bystander or a victim at the time of its commission, may offer eyewitness testimony before the court at request of defense or prosecution. Extra time may be granted to either side at the behest of the Judge to allow for witnesses not currently present.<br /> <br /> ===Objection to Testimony===<br /> Any witness that falls under the following conditions may be excused as a witness or have their testimony deemed inadmissible:<br /> :*The witness lacks the mental, intellectual, or other capacity to understand the context of the case.<br /> :*The witness's inclusion will cause substantial cost or delay to the case, proceedings, or upkeep of the station.<br /> :*The witness is the judge.<br /> ===General Objections===<br /> Both parties in a trial may object to testimony to have the testimony deemed inadmissible, move past the question, or rephrase a question to keep a trial within time limit:<br /> :* '''Hearsay:''' The witness testifies using an out-of-court statement by an individual not present in court, thereby rendering it impossible to verify. This testimony will be inadmissible.<br /> :* '''Asked and answered:''' A question is posed that has already been answered previously by a witness. Such a question must be skipped.<br /> :* '''Narrative:''' A question is posed that would require a significantly long answer with multiple facts, or when the witness chooses to answer a question in this way. The question must be reworded, or the witness must be reminded to answer promptly and stay on topic.<br /> <br /> Objections are completely at the discretion of the judge, who does not always need to sustain an objection even if it is within these guidelines. It is up to the judge to decide if an objection is proper or necessary to keep the trial quick and fair.<br /> <br /> ==Procedural Defense==<br /> Whereas a defendant is placed on trial, they are granted the privilege to challenge the legitimacy of charges or claims brought against them by the legal process. Any of the following may be invoked:<br /> :*Issue Preclusion/Double Jeopardy Clause: accused persons may not be tried on the same charges following an acquittal or conviction, except in the case of acquittal and subsequent credible admission of guilt.<br /> :*Entrapment Clause: accused persons found to be induced or coerced by law enforcement into the commission of the crimes listed in the charges may be acquitted or have their sentence reduced.<br /> :*Exclusionary Clause: evidence collected and/or analyzed in violation of accused persons’ rights under law may be inadmissible in court.<br /> =Medical Regulations=<br /> ==Standard of Care==<br /> <br /> Upon agreeing to provide medical care, staff assume the following duties of care:<br /> <br /> * They must provide a reasonable level of skillful, quality care<br /> * They must not make critical errors resulting in major personal injury or death, at the risk of criminal and civil liability.<br /> * They must show diligence in providing treatment, both inside and outside of the medical department area during their shift.<br /> * They must provide privacy to patients in non-emergency situations.<br /> * If they have limited resources, they must allocate what resources are available to them via triage.<br /> * They must not provide treatment that would breach Space Law or violate ethical principles.<br /> * They must ensure that invasive procedures or surgeries, including implant removals or inspections, are performed by trained personnel and properly given authorization via a valid search warrant. The need for a warrant is removed during a Code Gamma or similar alert status.<br /> <br /> ==DNRs==<br /> Do Not Resuscitate (DNR) orders are commands issued to medical personnel to restrict the revival of a specified individual. DNRs are issued for the following reasons:<br /> <br /> * Lawful executions;<br /> * Suicide in the custody of law enforcement, verified by the Corpsman.<br /> * Patient refusal.<br /> <br /> DNRs that do not involve execution must be verified by the CMO before taking effect.<br /> <br /> ==Medical Evaluation==<br /> Given good medical reason and with documentation, the Chief Medical Officer of a vessel may declare any on-duty personnel unfit for duty and order them demoted from their position. This includes the Commanding Officer, who may not overrule this procedure.<br /> <br /> In order for a medical evaluation to be considered lawfully applicable, the CMO and relevant head of department must both agree that the specified crewmate is unfit for duty in order to proceed with the demotion. In the case of the Commanding Officer, Central Command should be contacted as soon as possible.<br /> <br /> ==Quarantine==<br /> Medical staff are afforded the right to quarantine individuals that currently suffer from infectious or contagious diseases, and may confine them within pre-designated quarantine areas in the course of treatment, until the point that they are no longer infectious or harmful to the rest of the crew.</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Standard_Operating_Procedure&diff=3997 2025-05-26T02:48:20Z

<p>Lyndomen: /* Captain’s Authority */</p> <hr /> <div>This page covers the standardized guidelines and procedures aboard the station, but are not written in law; be aware that in cases of dire emergency the commanding officer or certain individuals are authorized to temporarily alter current SOP as they see fit, at the risk of criminal penalties in the case of misuse or abuse! Make sure to look at [[Alert Procedure]] for guidelines that change based on the current alert level.<br /> =General Regulations=<br /> <br /> == '''Definitions''' ==<br /> The terms specified below are defined for further use within the procedures.<br /> :*Captain: The officer legally appointed by Nanotrasen as Commanding Officer of the station. This title is only transferable by Central Command.<br /> :*Commanding Officer / CO: An officer appointed to lead the station and its Command department, whether it be the Captain by Nanotrasen, or an Acting CO by Station Command.<br /> :* Command Staff/Station Command: Members of the Command department who lead a department aboard the station.<br /> :* Crew: All sophonts employed by Station Command, or by NT to reside on the station and perform an established function therein. This includes any sophont listed on the Crew Manifest or issued a functional NT identification and access card. Individuals imprisoned by NT, along with those imprisoned during the course of a shift for violations of Space Law, are considered Crew.<br /> :* Judge: An indivudal legally appointed to preside over a criminal or civil trial, as specified within Trial Procedure.<br /> :* Detainee: Any sophont whose free movement has been curtailed by law enforcement on suspicion of criminal activity. They have not, however, been officially charged with a crime.<br /> :* Arrestee: Any sophont who has been formally charged with a crime.<br /> :* Prisoner: Any sophont who has been sentenced for the commission of a crime, or awaiting trial for a capital offense.<br /> :* Permanent Brig/Permabrig/Brig: A secure location for the long-term confinement of Prisoners. Typically outfitted to sustain the basic survival needs of the Prisoners within.<br /> ==Right to Refuse Service==<br /> All crew operating within their designated job locations are given the right to refuse service at any time for disorderly or abusive conduct. Additionally, all crew members are permitted to use nonlethal force to remove noncompliant or disorderly individuals only when such persons pose a threat to the safety of staff members, or disrupt the orderly functioning of the station. Service may not be refused to first responders acting to address or mitigate an emergency or crisis situation, unless such conduct is egregiously disorderly or abusive.<br /> <br /> ==Hiring Procedure==<br /> While Nanotrasen handles the staffing and recruiting needs of the station, Station Command is additionally authorized to hire any sophont into their respective department, as well as terminate the employment of any crew in their respective department per company policy. For a member of Station Command to personally employ a sophont into their department, a contract must be written stating the name of the employee, the department of employment, the position, and finally bearing the stamp of the Station Command member.<br /> =Controlled Items, Substances, &amp; Areas=<br /> <br /> == Controlled Items ==<br /> Controlled Items include any item that is restricted from general possession and use. Additionally, any equipment or technology providing insight into the development, production, or procurement of a controlled item is also controlled in and of itself. A list of such items follows:<br /> <br /> * Any Controlled Substances, as listed below.<br /> * Any Controlled Armaments, as listed below.<br /> * Electromagnetic pulsing and/or disturbance technology.<br /> * Cryptographic systems, software, or technology.<br /> * Nuclear materials, weapons, and technology.<br /> * Long-range telecommunications and broadcasting technology.<br /> * Astronavigational guidance equipment or technology.<br /> * Telecommunication or signal jamming technology.<br /> * Telecommunications encryption technology.<br /> * Hypodermic spray tools and injectors.<br /> * Cloaking, chameleon, and IFF-inhibiting technology.<br /> * Technology utilizing bluespace as an integral part of its function.<br /> * Teleportation and portal technology.<br /> * Hydraulic or powered equipment designed for the electronic or mechanical bypass of secure-access systems.<br /> <br /> Any individual requiring any above item in the course of their job, or for regular function, may request a document of authorization from the relevant departmental head. Such a document must have an itemized list of the approved Controlled Items, the name and position of the holder, and a signed and stamped statement by the authorizing party.<br /> <br /> Should the holder commit crimes through the use of such authorized items, the authorizing party may be found guilty of Accessory to said crimes, in addition to Endangerment and Abuse of Power where applicable. The Commanding Officer is also authorized to supervise the approval and revocation of documentation as they see fit.<br /> <br /> == Controlled Substances ==<br /> Any individual requiring a Controlled Substance in the course of their job, or for regular function, must request access to a perscription or special dispensation from the Chief Medical Officer. The Psychologist is also permitted to grant prescriptions for psychoactive drugs. Any such document must state the substance(s) being prescribed, the amount(s) where applicable, and the stamp and signature of the authorizing party.<br /> <br /> A list of such Substances follow:<br /> <br /> * Mindbreaker Toxin and other psionically altering agents.<br /> * Romerol, and other rapid acting biological or chemical agents.<br /> * Desoxyephedrine, and similar stimulants.<br /> * Nocturine, and similar sedatives.<br /> * Phlogiston, and other explosive and/or pyrotechnic compounds.<br /> * Amatoxin, and other toxic and/or poisonous compounds.<br /> * Blissifylovene, Soretizone, Tranquinase, and all similar psychoactives used to aid in mental wellbeing.<br /> <br /> == Controlled Armaments ==<br /> <br /> <br /> Controlled Armaments are grouped into categories of increasing severity.<br /> <br /> '''Category A:''' ''Illegal possession of Cat. A controlled armaments may incur a sentence of up to 5min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed, adapted, or used to cause physical harm in close combat<br /> * Any object or equipment specifically designed or adapted to protect against physical harm caused by weapons, projectiles, or other forms of direct assault<br /> * Any object or instrument specifically designed or adapted to incapacitate or disorient by using light or sound without causing permanent injury<br /> * Any object or equipment specifically designed or adapted for explicitly training purposes that would otherwise fall under another category<br /> <br /> '''Category B:''' ''Illegal possession of Cat. B controlled armaments may incur a sentence of up to 10min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed or adapted to cause physical harm in close combat, which employs a powered system to enhance performance<br /> * Any manually-operated ballistic arms that possess an internal magazine or feeding system, or lack an internal magazine or feeding system altogether<br /> <br /> '''Category C:''' ''Illegal possession of Cat. C controlled armaments may incur a sentence of up to 15min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any manually-operated ballistic arms that use an external magazine or feeding system<br /> * Any semi-automatic ballistic arms not easily concealable within a pocket or coat<br /> * Any object or instrument specifically designed or adapted for explicitly less-lethal purposes that would otherwise fall under another category<br /> <br /> '''Category D:''' ''Illegal possession of Cat. D controlled armaments may incur a sentence of up to 20min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any semi-automatic ballistic arms that are easily concealable<br /> * Any fully-automatic ballistic arms<br /> * Any laser, plasma, or energy based arms, including ones designed, intended, or used for melee combat.<br /> * Any object or device specifically designed or adapted to cause physical harm through detonation of an explosive charge<br /> * Any object or equipment specifically designed or adapted to protect against both a space environment and physical harm caused by weapons, projectiles, or other forms of direct assault<br /> <br /> '''Category E:''' ''Illegal possession of Cat. E controlled armaments may incur a sentence of up to 25min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any crew-served or emplaced weapon<br /> * Any object or instrument specifically designed or adapted to launch large-calibre explosives or projectiles for offensive or defensive purposes<br /> * Any object or instrument specifically designed or adapted to employ chemical, biological, esoteric, radiological, or nuclear hazards for offensive or defensive purposes<br /> <br /> Armaments licenses may be issued by the Commanding Officer, Warden, or Head of Security. The license must include the name of the holder, a list of allowed armaments, and a stamped signature from the issuer.<br /> <br /> If the holder uses their armaments in the commission of a crime, the issuer may be held liable for accessory to the crimes committed, along with Endangerment and Abuse of Power where applicable.<br /> <br /> == Departmental Dispensations ==<br /> Certain bodies, groups, or personnel may require certain Controlled Items in the course of their job, and as such must be provided exceptions. '''Any member of any department which begins their shift with a controlled item in their possession or within their department’s allocated area is assumed authorized for its possession and use.'''<br /> <br /> Additionally, tools and equipment located within emergency lockers are not considered Controlled Items, so long as they are used as intended.<br /> <br /> ===Logistics===<br /> Members of a station’s Logistics department are permitted to approve any order with the direct permission of an individual with legal access to the contents of that order. Additionally, they may deny any order, at any time, for lack of funds, authority, or any other reason deemed sufficient by their direct superior.<br /> <br /> Unlocked crates, orders stored outside the department, and supplies illegally distributed to unauthorized personnel carry the risk of Endangerment of even Black Marketeering charges. Crates of Controlled Items, Substances, or Armaments should be stored securely within the department, with a copy of their invoices on file.<br /> <br /> === Research ===<br /> Epistemics employees are permitted to use their lab spaces as they see fit, with the following caveats:<br /> <br /> * Any sophont experimentation must be done with the consent of the test subject, and must not have an undue risk of life. The Mystagogue or CO may terminate any experiment for safety or ethical purposes and at their discretion.<br /> * Self-experimentation is prohibited and is chargeable with Endangerment, at a minimum.<br /> * Testing of any explosives or weapons that risk hull penetration or mass destruction must be done at an off-station site.<br /> <br /> Epistemics personnel may also utilise Controlled Items within the confines of designated testing areas and in a manner directly approved jointly by the Mystagogue and by the Head of Security or CO.<br /> <br /> Utilizing or storing Controlled items without direct approval, utilizing Controlled Items outside of the testing areas, and distributing Controlled Items to crew constitute criminal offences under Space Law and may additionally incur demotion as punishment.<br /> <br /> === Medical ===<br /> All medical personnel may carry or use Controlled Substances, along with hypodermic tools, in the course of their job functions and in a manner approved by the CMO or CO, with the following caveats:<br /> <br /> * Any Controlled Substance with the capability to cause rapid and grievous bodily harm or death may not be carried outside of the chemicals lab or treatment areas without a signed and stamped document of authorization.<br /> * Any Controlled Substance with the capacity to cause harm as a consequence of overdose may not be stocked, stored, or displayed in any area or fashion that leaves such substances open and accessible to the public.<br /> * Any hypodermic tool must be kept secure within locked storage or on the person of an authorized individual.<br /> <br /> ==High Security Areas==<br /> High Security Areas, or HSAs, should be restricted, and, during standard station operations, secured where applicable or per alert level. They differ from regular secure areas in that they may contain items, technology, or other assets of high importance or value, and must therefore be held safe. Unauthorized persons within HSAs may be guilty of trespass, or of breaking and entering.<br /> <br /> Common HSAs for commercial and military vessels are as follows:<br /> <br /> * Bridge<br /> * Armory\Gun Deck<br /> * Vault\Strongroom<br /> * Station AI Rooms (Upload, Core, etc.)<br /> * Gravity Generation\Life Support\Engine Rooms<br /> * Telecommunications\Telemetry<br /> * Permanent Brig\Holding Cells<br /> <br /> == Sophonts and Synthetics ==<br /> To be defined as a sophont, a being must be able to utilize a structured language, communicate through the use of written, verbal, and/or body language (or by other means), and possess reasoning and introspection.<br /> <br /> Any such being is considered a sophont, and thus a legal person, regardless of their make, origin, disposition, or prior cognition. As part of their rights, they are to be governed under the same laws as any other sophont, and given the ability to press charges as a sophont.<br /> <br /> The unauthorised jailbreaking or uplifting of property into the status of Sophont is still a criminal offense however, and those found guilty of doing so may be found guilty of sabotage or vandalism.<br /> <br /> An entity’s status as a sophont may be challenged during the process of charging and trialing the individual or another for crimes which utilize the term sophont in the legal language of the crime. The Defense or Prosecution will present evidence indicating that it meets, or does not meet, the criteria above. The Judge will then arbitrate upon the entity's status as a sophont.<br /> <br /> Any synthetic/silicon/inorganic entity with a non-sophont status, is to be classified as a standard synthetic entity. Synthetic entities are the property of the party that constructs or employs the entity, unless otherwise stated by relevant contract or legal document. To damage or destroy such an entity is to damage or destroy the aforementioned party’s property.<br /> =Commanding Officer=<br /> ==Captain’s Authority==<br /> The Commanding Officer of a station or vessel is afforded several rights, broadly referred to as &quot;Captain's Authority&quot;.<br /> <br /> While they are formally and legally appointed CO, they are the ultimate authority aboard a vessel until they are directly dismissed by a superior from Central Command.<br /> <br /> Additionally, they have the authority to pardon and/or parole any individuals accused and sentenced of Grand Felony, Felony, and Misdemeanor-level sentences if deemed in the best interest of the crew and vessel. The CO may be held liable for accessory to any future criminal acts performed by the pardoned individual, and they must make an announcement to the station stating who was pardoned, for what crimes, and for what reason.<br /> <br /> Captain’s Authority carries a responsibility, however; the CO must do everything in their power to protect all entities and assets aboard the station with which they have been entrusted, and must not abandon them while there is a reasonable hope that they may be saved.<br /> <br /> Additionally, the legally appointed Captain of a vessel is afforded two additional rights over that of a CO:<br /> <br /> * To, with public announcement to the crew, temporarily modify SOP in times of emergency, at the risk of criminal penalties if misused or abused, and<br /> * To deputize members of the crew to carry out law enforcement activity. These deputies are bound by Security Regulations and Space Law, and the Captain may suffer criminal penalties for any crime committed by them.<br /> <br /> ==Line of Succession==<br /> It is the responsibility of Command to ensure that a station retains a CO immediately at the start of the shift and thereafter. If the CO dies and is unrecoverable, or if a CO is not assigned at the start of the shift, an Acting CO must be selected forthwith per the following guide:<br /> <br /> # All active members of Station Command must meet, and choose one of their number to become the Acting CO.<br /> # If no Station Command is alive or on active duty, then each Department must nominate a temporary Delegate. These Delegates must meet and choose an Acting CO from among their number.<br /> # The Acting CO must then duly inform Central Command via fax and make a stationwide announcement.<br /> # Await the end of your shift.<br /> <br /> After Central Command has received the results of the Line of Succession, the Acting CO is afforded all prescribed powers of a CO. An access biscuit ''may or may not'' be sent by Centcomm to assist with this. When a legally appointed Captain arrives, it is the express duty of the Acting CO to hand over any and all Captain-related equipment and accesses to the new CO, and to resign themselves to their original role before their temporary promotion.<br /> ==Command Promotions==<br /> The CO of the vessel is authorized to promote Crew into Station Command positions if it is determined that the vacancy is a detriment to station productivity. The CO has a duty to ensure that the Crew they promote are of a reasonable level of skill, and can be held liable if they disregard this duty.<br /> <br /> Crew members promoted into Station Command positions are considered to be acting members of Station Command, with all rights and responsibilities therein. When NT-appointed Station Command arrive, the acting Command members are required to hand over any specialized equipment (Command ID cards, attire, or tools) and resign themselves to their original position from before their temporary promotion.<br /> ==Mutiny==<br /> Should such a situation arise in which the CO is unfit for their position and declines relinquishment of position and power, and where all alternative legal options have been exhausted, officers may be permitted to lead a mutiny. Officers leading a mutiny must inform Central Command of this occurrence before the mutiny has begun.<br /> <br /> A mutiny, defined as a coordinated effort to depose the commanding officer or officers of a vessel for committing unlawful acts, requires the crew to neutralize the offending staff with non-lethal force where applicable, and lethal measures and weapons only in acts of self-preservation or when given no other option. The commanding officer or officers, as well as their loyalists, are all bound to Space Law, the current alert level and its corresponding RoE.<br /> <br /> Should the mutiny be unsuccessful, only the head officer(s) who approved the mutiny may be charged with sedition and receive a trial, while all mutineers may be demoted, processed by law enforcement, and charged for the crimes they have committed.<br /> <br /> Should the mutiny be successful, the head officer(s) who approved the mutiny must select a new Commanding Officer per Line of Succession. The new CO will then sentence the previous heads of staff for their crimes per Space Law.<br /> <br /> == Foreign Vessels ==<br /> Should civilian and military vessels receive a docking request from another neutral vessel, they may approve or deny such a request. Any vessel may, with consent from the docking entity, be searched by law enforcement upon arrival, and its crew granted free movement accompanied by an escort at the discretion of the CO or law enforcement officials.<br /> <br /> Crew of foreign vessels may be refused entry, at any time and for any reason, and must be returned to, or be escorted to, their own vessel where applicable. Failure to comply may constitute trespass. Docking vessels bearing a warrant or commission represent an exception, and may not be denied entry or be forced to submit to a search.<br /> <br /> Crimes committed against the station or its inhabitants, on station or abroad, are grounds to charge the perpetrator according to the laws of the station. Should visiting entities break the law, or be suspected of doing so, and flee aboard their own vessel, law enforcement personnel are authorized to board the vessel in continuous “hot” pursuit and are fully authorized to effect an arrest upon the relevant party.<br /> <br /> =Security Regulations=<br /> ==Security Jurisdiction==<br /> Law enforcement personnel are bound by trespass and assault laws, and thus cannot operate outside accessible areas, or perform searches without a Probable Cause, a warrant, or a heightened alert level that specifically allows such action. Advanced surgical procedures and cursory implant investigations must be performed by a trained member of the Medical department, operating under their [[Standard Operating Procedure#Standard of Care|Standard of Care]].<br /> <br /> However, officers are allowed to trespass into a department in “hot pursuit” of a suspect who has fled from an accessible area, who they have Probable Cause to believe has committed a crime<br /> <br /> ==Probable Cause==<br /> While actively enforcing the law, officers are held to the standard of Probable Cause. This phrase represents a reasonable suspicion that a crime has been, or is being, committed, and does not require the officer to have solid evidence of criminal activity. Examples of Probable Cause include witnessing criminal activity or credible reports of such.<br /> <br /> When judged, Probable Cause is to be interpreted within the context of the entirety of the station’s circumstances at the time of the incident. Probable Cause negates the need of a warrant for searches, and, once concluded, should be promptly reported to the Prosecutor, Warden, or Head of Security for review.<br /> <br /> ==Detainment and Arrest==<br /> Any sophont may be detained by a law enforcement officer with Probable Cause. In detainment, the officer will inform the Detainee of the crime they are suspected of committing. They may be held on-site or moved to a strategically sound location, restrained at the officer’s discretion, and detained while law enforcement officers determine if they can proceed with an arrest. Such a detention should last no longer than five (5) minutes. A Detainee may not be searched, unless consent is given or they are placed under arrest, and their detention should be concluded within five minutes of its start, by either Arresting them or releasing them.<br /> <br /> Any sophont which may have committed a crime, assuming Probable Cause, or has been formally charged with the commission of a crime, may be arrested. In an arrest, the suspect will be restrained by a member of law enforcement, informed of their charges, and taken to the brig for search and processing under Brig Procedure. Any Controlled Items in possession of the Arrestee without licensure or dispensation must be confiscated, along with items used in commission of the crime(s), and will be held indefinitely by law enforcement as described in [[Standard Operating Procedure#Evidence Handling|Evidence Handling]]. Legal counsel may be requested by an Arrestee or Detainee, and must be provided if available.<br /> <br /> ==Brig Procedure==<br /> When confining an Arrestee within the Brig, they should be transferred to the Warden for processing:<br /> <br /> * A full search of the Arrestee and their possessions.<br /> * The confiscation of any Controlled Items or items used in commission of the crime, along with any equipment not befitting a prisoner<br /> * The confining of the Arrestee within a temporary holding cell.<br /> * [[Standard Operating Procedure#Sentencing|Sentencing]] the Arrestee.<br /> <br /> If the Arrestee is sentenced for a Capital-level crime, they are to be transferred to the Permanent Brig, pending trial. If the Warden is unavailable, the arresting officer must process the Arrestee as stated above. All confiscated items must be handled as dictated within [[Standard Operating Procedure#Evidence Handling|Evidence Handling]].<br /> <br /> ==Sentencing==<br /> Any law enforcement individual is authorized to pass sentences on all Grand Felony, Felony and Misdemeanor-level crimes; however, the Prosecutor is responsible for overseeing sentences passed, and is authorized to correct sentences or even acquit them, in accordance with both Space Law and [[Standard Operating Procedure#Paroles and Pardons|Paroles and Pardons]]. Both capital charges and sentences must be placed by the Prosecutor or Court Clerk; if neither are available, the Warden or Head of Security are authorized to press capital charges and request sentencing for them, under Trial Procedure.<br /> <br /> In the case that the accused requests appeal for a Grand Felony- or Felony-level sentence, the Court Clerk should be called to preside over a small, swift adjudication, where the Prosecutor and accused will argue their sides. The Clerk will then decide the sentence, or acquittal, of the accused. If the Clerk is unavailable, the Chief Justice or the Warden can perform appeals. If neither are available, any available member of Station Command is authorized to adjudicate on the case.<br /> <br /> Additionally, any sentence meeting or exceeding twenty-five (25) minutes, regardless of the severity of the crime(s) committed, will require a trial. If the total sentence still meets or exceeds twenty-five minutes after the conclusion of a lawful trial, the Judge is fully authorized and encouraged to upgrade their sentence to Extended Confinement.<br /> <br /> Once a sentence has commenced, it must be concluded at or before the agreed-upon time.<br /> <br /> == Evidence Handling ==<br /> When evidence of a crime is secured, it is the responsibility of the arresting officer or Warden to properly handle it, at the penalty of Obstruction of Justice and/or demotion.<br /> <br /> Evidence should be organized by individual and crime, and stored together (e.g., in a bag, in one separate locker, etc) and then placed in an area locked behind security access.<br /> <br /> If a prisoner is released from a temporary holding cell OR the Brig, any of their equipment that is neither a Controlled Item nor used in the commission of their crimes must be returned to them.<br /> <br /> == Rules of Engagement ==<br /> Law enforcement personnel hold a Category D Armaments License, and are authorized at all times to use lethal force to the extent necessary to neutralize adversaries under any of the following circumstances:<br /> <br /> * If the adversary’s number or strength leave the officer at a severe tactical disadvantage.<br /> * If the adversary exhibits a clear and present danger to the vessel by physical means.<br /> * If the adversary poses a significant threat of serious bodily injury or death to the officer or others.<br /> * If the adversary presents an existential threat to the chain of command by illegal means.<br /> * If the adversary cannot be reasonably subdued through non-lethal means without great bodily harm to the officer.<br /> <br /> …wherein an “adversary” is an entity that demonstrates a hostile intent, commits or directly contributes to a hostile act that does not constitute an actual attack, or is actively attacking the vessel or its crew.<br /> <br /> Despite their allowance of lethal force, Security is required to follow the Rules of Engagement of the current Alert Level, as outlined within [[Alert Procedure]].<br /> <br /> == Armory Procedure ==<br /> The armory and its usage are governed by the Warden. The Warden is responsible for stocking, distributing, and recording the collection of weapons used by the station during the shift. They are also afforded the authority to arm security at their discretion, so long as the weaponry distributed is in appropriate response to [[Alert Procedure]].<br /> <br /> All weaponry distributed from armory is issued on a temporary basis. While issued, the weaponry remains as station property, and the wielder assumes a duty to protect the weapon and return it to the Warden when ordered. No non-crew may be issued weaponry from the armory.<br /> <br /> The Warden is accountable for responsibly issuing weapons. Any weaponry issued during a heightened alert level must be returned when the alert has been lowered, or when the threat is no longer present. The weaponry issued must be proportionate to the threat posed, and explosives should not be used unless absolutely necessary.<br /> ==Treatment of Prisoners==<br /> Prisoners have certain rights that must be upheld by law enforcement and Station Command. ''Prisoners must be provided with the following'':<br /> <br /> * Adequate medical care and moral, spiritual, or legal counseling if it is requested and available.<br /> * Access to the Common and Prison radio channels only while serving their sentence. This right may be revoked should it be abused.<br /> * Clothing, food, and water on request.<br /> * Should the holding cells or Permabrig become uninhabitable, prisoners must be securely and safely relocated to another area for confinement, until the holding cells or Permabrig are returned to a serviceable state.<br /> * Prisoners should be granted freedom of movement within their holding area unless there is an undue risk to life and limb.<br /> <br /> Additionally, prisoners sentenced to Extended Confinement have certain rights but also '''more firm restrictions that must be upheld by law enforcement''':<br /> <br /> * Visitation may be permitted only for prisoners sentenced to Extended Confinement. One person may visit such a prisoner for a period of no longer than ten minutes. A reason must be provided for the visit, and the visitor must consent to a search of their belongings. The prisoner is then unable to receive another visitor for another ten minutes.<br /> * Prisoners may request retrial for capital crimes; these requests may be refused depending on the discretion and availability of the court clerk, chief justice, or at the discretion of the warden or head of station security.<br /> * Prisoners may request or may otherwise be given parole with a hearing by the Chief Justice, Court Clerk, or in their absence, the head of station security or commanding officer (see Paroles and Pardons).<br /> <br /> Should prisoners repeatedly and maliciously antagonize law enforcement, to an extent where continued extended confinement becomes infeasible, the warden is fully authorized and encouraged to temporarily upgrade the relevant prisoners’ sentences to Preservative Stasis summarily.<br /> <br /> Moreover, prisoners are liable for any and all crimes that they commit while held either in the temporary holding cells or the Permanent Brig, and may receive trial for more restrictive punishments if their actions warrant a capital sentence.<br /> <br /> ==Paroles and Pardons==<br /> Prisoners may be allowed parole, per the discretion of the Warden, the Head of Security, or the CO. Alternatively, they may request a parole hearing as described within Trial Procedure.<br /> <br /> Prisoners seeking parole may request legal counsel before the hearing, but they must represent themselves. A prisoner who is granted parole is to be treated as a member of the station’s crew with all benefits and responsibilities thereof, and is encouraged to seek gainful employment from relevant command staff.<br /> <br /> Additionally, a pardon can be issued to any entity accused of, or sentenced to, crimes, by the arresting officer, the Judge of a trial, or the Warden in the case of those within the permanent brig, if deemed in the best interest of the crew and vessel, and when the circumstances of the defendant or their offense warrant a suspension of their sentence.<br /> <br /> =Justice Regulations=<br /> ==Pressing Charges==<br /> ===Criminal Charges===<br /> Any crew member may press charges against any other crew member. An individual may be charged of a crime if and only if it can be argued beyond a reasonable doubt that the accused had committed an act in the nature and fashion as described by a particular criminal charge.<br /> <br /> Multiple counts of one crime can be charged. For illegal actions against the station abroad, each incident separated by a reasonable period of inaction, lawful conduct, or another crime is interpreted as one count. For crimes directly bereaving a person (violent acts, theft of personal property etc.), the same applies in addition to each victim being one count. In the case of possession, theft, or any incident involving several separate and distinct items, one charge may be applied per relevant item.<br /> <br /> Charges that are a direct escalation of one another in nature cannot be simultaneously held against the perpetrator if they pertain to the same incident and the same victim/item (if applicable). Then, only the most severe of these charges applies. Additionally, if one charge incorporates another charge within its definition or description, the perpetrator cannot be held accountable for both; rather, only the most severe of these charges applies.<br /> ===Civil Charges===<br /> Any crew member can sue any other crew member for inflicting them with damages caused by a breach of duty. To sue is to request compensation for said damages. To do so, the victim must prove:<br /> *'''Damages:''' That the victim was inflicted with an emotional, physical, or monetary damage<br /> *'''Breach of duty:''' That the defendant had a duty which they failed to uphold(e.g., a duty to not endanger crew, a duty to act respectfully), leading to the victim being inflicted with a damage<br /> *'''Severity:''' That the damage was severe enough to warrant the compensation requested<br /> Compensation can either be explicitly specified by the victim or left for the court to decide. Either way, the court is free to modify the compensation as it sees fit. Most often, compensation is rendered in the form of court orders compelling a crew member to do something (e.g., return an item, make an apology, or permanently avoid a certain area). Court orders should be written and stamped with the notary stamp.<br /> <br /> ==Court Orders==<br /> The individuals specified in the three sections below can issue Court Orders, which are legally-enforced documents that carry the penalty of an Obstruction of Justice charge and forced compliance with the order by security. Each order has its own requirements and authorized issuers, but are all implied to require '''''the stamp (where applicable) and signature of the issuer to be valid.'''''<br /> ===Warrants===<br /> Warrants represent official orders to the security department, issued by relevant officers or the Justice Department. Warrants are only valid when issued by either the Chief Justice or Court Clerk, or in both of their absences, the Commanding Officer or head of station Security.<br /> <br /> * Individual Warrants may order the search or detainment of an individual, or the arrest of the individual with evidence. This may also include surgical procedures, cursory implant inspections, or any other invasive searches with both probable cause and evidence. These warrants should include a name, the actions prescribed (detainment, search, arrest, etc.), and a description if applicable.<br /> * Search Warrants may order the search of an entire departmental area, by force if necessary, and may order the arrest of listed individuals implicated in a crime or crimes with probable cause and evidence. Search Warrants should include an area, a brief description of the probable cause, and a list of individuals if applicable.<br /> <br /> ===Injunctions===<br /> The Chief Justice, Commanding Officer, or Judge of a trial are fully authorized to issue injunctions: legally-binding, written orders restricting Inhabitants from doing something disruptive to station productivity or personal rights.<br /> These may be issued on discretion or as relief for Civil Trials. Injunctions may not compel someone to violate Space Law or SOP, and the issuer is liable for abuse of power charges if this is misused. An injunction must include a list of affected names and a detailed description of the restrictions to be valid.<br /> <br /> ===Subpoenas===<br /> The Chief Justice, Court Clerk, or Judge of a trial may issue Subpoenas, which are trial-related Court Orders compelling an individual to produce evidence or make themselves present at a location for court. A subpoena can order an individual to:<br /> <br /> * Appear as a witness, defendant, plaintiff, or prosecution;<br /> * Produce evidence for a trial;<br /> * Appear for questioning in deposition.<br /> <br /> A subpoena must include a list of names, a detailed description of evidence requested or reason for appearing, and a reasonable time frame no shorter than 3 minutes. The individuals summoned by the subpoena must be informed of its presence for it to be a valid order. This can be done via general announcement, fax, verbal announcement, or otherwise.<br /> <br /> === Affidavits ===<br /> An Affidavit is a legal document, consisting of a formal written statement of witness. An Affidavit must be written by the witness, or Affiant, who must state their relation to the incident at hand, and must be signed and stamped (if applicable) by a member of Security, Justice, or Command, who is verifying that the contents of the Affidavit are true to the best of their knowledge. The witness to the Affidavit must not be directly connected to the incident.<br /> <br /> Affidavits are considered valid witness statements for use in a trial (see Trial Procedure, below), and can be used either in tandem with a verbal witness statement, or to obtain testimony from an affiant whose job requirements and/or personal circumstances make attending a trial unfeasible.<br /> <br /> An affidavit may be impeached- and thus removed from evidence- if the Prosecution or Defense can introduce testimony or other evidence that directly contradicts the statements recorded within the Affidavit. The Affiant may then be liable for criminal charges.<br /> <br /> =Trial Procedure=<br /> A trial may be requested for civil disputes and capital charges. Civil charges may be refused, depending on the availability and discretion of a potential Judge; however, capital crimes require a trial. This also includes non-capital trials required as dictated within Sentencing guidelines. Miscellaneous trials, such as those described within Paroles and Pardons, only require the Judge and the defendant.<br /> <br /> Criminal trials may be waived if a suspect pleads guilty to a member of the Justice or Security department, or to station command. Their sentence should be passed by a Judge immediately, without the need for a full hearing. The Judge should also sentence the defendant summarily if they are held in contempt of court during the trial.<br /> <br /> The trial takes the form of an arbitration court hearing, presided over by an appointed Judge, and including adequate Prosecution and Defense, as dictated below. All charges, arguments, and evidence must be filed with the Judge before the case begins. The trial shall begin when the Defense, Prosecution, and Judge are all present and ready to begin. A trial does not need to be open to the public.<br /> <br /> The Judge is charged with ensuring the trial is completed in a timely manner, and is granted the power to charge someone with Contempt of Court, under Space Law, if they disrupt the case. Suitable Judges should be chosen from the following list, in sequential order:<br /> <br /> # The Chief Justice<br /> # The Clerk<br /> # An impartial member of the Justice department.<br /> # An impartial member of Station Command.<br /> # The Warden.<br /> <br /> The Defense should ideally be a member of the Justice department assigned to argue in favor of the defendant; if none are available, the defendant may choose to represent themselves.<br /> <br /> The Prosecution should ideally be the Prosecutor; if they are unavailable, the case should be prosecuted by an unbiased member of Station Command or a law enforcement officer, in that order.<br /> <br /> If there is not a viable and/or willing Defense or Prosecution, the Judge is fully authorized and strongly encouraged to pass a summary sentence of Extended Confinement until an adequate trial can be held.<br /> <br /> ==Criminal Trials==<br /> A criminal case should take no longer than 25 minutes in total. Criminal cases should either have security personnel present, or plan to have them present by the end of the trial.<br /> :#The judge brings the court in session.<br /> :#Prosecution opens the proceedings, stating the charges and introducing witnesses and exhibits that will be brought forward during the presentation of evidence. They may also recommend a sentence to the judge, appropriate to the charge based on their opening statement.<br /> :#Defense enters their plea- Guilty or Not Guilty.<br /> :#If Guilty, the Judge is authorized to immediately pass a ruling, as stated below.<br /> :#If Not Guilty, they are to provide their own opening statement and introduce their own witnesses and exhibits where applicable.<br /> :#Presentation of evidence follows, lead by Prosecution, then Defense.<br /> :#*Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> :#Finally, closing statements are made by the Prosecution, Defense, and Prosecution once more due to burden of proof. No new evidence can be introduced within a closing statement.<br /> :#A ruling will be issued by the Judge, written down, and stamped with the Notary stamp, the Judge's stamp, and their signature.<br /> :#The Judge adjourns the court. Any present or soon-to-be-present Security personnel will then enact the ruling.<br /> <br /> == Civil Trials ==<br /> Civil cases do not require Prosecution or Defense, but they may receive assistance from either both before and during the case. Both the defendant and plaintiff must be made to summon at the court, if a party does not appear out of either refusal or negligence, or fails to comply with a court order from a civil trial, that party may be charged with contempt of court, a felony. A civil case involves seeking damages from a defendant, which could be monetary, an item, or otherwise. A civil case should take no longer than 15 minutes in total.<br /> <br /> # The Judge brings the court into session.<br /> # Plaintiff opens proceedings by stating the damages, before introducing witnesses and exhibits that will be brought forward during presentation of evidence. They may also reccomend civil relief to the judge, appropriate to the damages listed wthin their opening statement.<br /> # Defendant follows with their opening statement, contradicting the Plaintiff's theories and assertions. They will also introduce their own witnesses and exhibits, where applicable.<br /> # Presentation of evidence follows, led by the Plaintiff, then the Defendant.<br /> #* Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> # Finally, closing statements are made by the Plaintiff, Defense, and Plaintiff once more due to burden of proof. No new evidence should be introduced or referenced by these statements.<br /> # A ruling will be made by the Judge, written, and stamped by the Notary stamp, the Judge's stamp, and signed by the Judge.<br /> # The Judge adjourns court.<br /> <br /> Any ruling shall then be enacted; if a party refuses to follow through with the ruling, they may suffer criminal penalties.<br /> <br /> == Presentation of Evidence ==<br /> <br /> ===Eyewitness Testimony===<br /> Any sophont or other entity willing and capable of presenting themselves before court under oath and present at the scene of the crime as a bystander or a victim at the time of its commission, may offer eyewitness testimony before the court at request of defense or prosecution. Extra time may be granted to either side at the behest of the Judge to allow for witnesses not currently present.<br /> <br /> ===Objection to Testimony===<br /> Any witness that falls under the following conditions may be excused as a witness or have their testimony deemed inadmissible:<br /> :*The witness lacks the mental, intellectual, or other capacity to understand the context of the case.<br /> :*The witness's inclusion will cause substantial cost or delay to the case, proceedings, or upkeep of the station.<br /> :*The witness is the judge.<br /> ===General Objections===<br /> Both parties in a trial may object to testimony to have the testimony deemed inadmissible, move past the question, or rephrase a question to keep a trial within time limit:<br /> :* '''Hearsay:''' The witness testifies using an out-of-court statement by an individual not present in court, thereby rendering it impossible to verify. This testimony will be inadmissible.<br /> :* '''Asked and answered:''' A question is posed that has already been answered previously by a witness. Such a question must be skipped.<br /> :* '''Narrative:''' A question is posed that would require a significantly long answer with multiple facts, or when the witness chooses to answer a question in this way. The question must be reworded, or the witness must be reminded to answer promptly and stay on topic.<br /> <br /> Objections are completely at the discretion of the judge, who does not always need to sustain an objection even if it is within these guidelines. It is up to the judge to decide if an objection is proper or necessary to keep the trial quick and fair.<br /> <br /> ==Procedural Defense==<br /> Whereas a defendant is placed on trial, they are granted the privilege to challenge the legitimacy of charges or claims brought against them by the legal process. Any of the following may be invoked:<br /> :*Issue Preclusion/Double Jeopardy Clause: accused persons may not be tried on the same charges following an acquittal or conviction, except in the case of acquittal and subsequent credible admission of guilt.<br /> :*Entrapment Clause: accused persons found to be induced or coerced by law enforcement into the commission of the crimes listed in the charges may be acquitted or have their sentence reduced.<br /> :*Exclusionary Clause: evidence collected and/or analyzed in violation of accused persons’ rights under law may be inadmissible in court.<br /> =Medical Regulations=<br /> ==Standard of Care==<br /> <br /> Upon agreeing to provide medical care, staff assume the following duties of care:<br /> <br /> * They must provide a reasonable level of skillful, quality care<br /> * They must not make critical errors resulting in major personal injury or death, at the risk of criminal and civil liability.<br /> * They must show diligence in providing treatment, both inside and outside of the medical department area during their shift.<br /> * They must provide privacy to patients in non-emergency situations.<br /> * If they have limited resources, they must allocate what resources are available to them via triage.<br /> * They must not provide treatment that would breach Space Law or violate ethical principles.<br /> * They must ensure that invasive procedures or surgeries, including implant removals or inspections, are performed by trained personnel and properly given authorization via a valid search warrant. The need for a warrant is removed during a Code Gamma or similar alert status.<br /> <br /> ==DNRs==<br /> Do Not Resuscitate (DNR) orders are commands issued to medical personnel to restrict the revival of a specified individual. DNRs are issued for the following reasons:<br /> <br /> * Lawful executions;<br /> * Suicide in the custody of law enforcement, verified by the Corpsman.<br /> * Patient refusal.<br /> <br /> DNRs that do not involve execution must be verified by the CMO before taking effect.<br /> <br /> ==Medical Evaluation==<br /> Given good medical reason and with documentation, the Chief Medical Officer of a vessel may declare any on-duty personnel unfit for duty and order them demoted from their position. This includes the Commanding Officer, who may not overrule this procedure.<br /> <br /> In order for a medical evaluation to be considered lawfully applicable, the CMO and relevant head of department must both agree that the specified crewmate is unfit for duty in order to proceed with the demotion. In the case of the Commanding Officer, Central Command should be contacted as soon as possible.<br /> <br /> ==Quarantine==<br /> Medical staff are afforded the right to quarantine individuals that currently suffer from infectious or contagious diseases, and may confine them within pre-designated quarantine areas in the course of treatment, until the point that they are no longer infectious or harmful to the rest of the crew.</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Server_Rules&diff=3996 2025-05-20T18:52:05Z

<p>Lyndomen: /* C3. Follow Antagonist Guidelines */</p> <hr /> <div>This is a Delta-V server. If you are banned on this server, you will be banned on all Delta-v Servers. You must be at least 17 years of age to play on this server. By connecting to this server, you agree to our privacy policy found at https://discord.gg/deltav<br /> <br /> This is a roleplaying (RP) server. Try to immerse yourself into your character. This includes interacting with your fellow crewmates, and using roleplay as the primary vessel to play the game alongside things like your job on the station. Roleplaying places less emphasis on &quot;winning&quot; and more on just telling a story.<br /> <br /> Space Station 14 is not like most games. Many rules are designed to require roleplay, and not all rules are intuitive. Please take the time to read and understand the rules before you play so that you aren't surprised. Our community rules specifically are zero-tolerance rules, meaning that a violation will result in an appeal-only ban. Game admins will treat you as if you have read the rules, even if you have not. If you have any questions about these rules, please use the admin help menu by hitting F1 in-game or clicking the &quot;AHelp&quot; button in the lobby, or by making a post in the &quot;Rules Clarification&quot; forum at https://discord.gg/deltav<br /> <br /> = Community Rules =<br /> These rules apply at all times, including between rounds.<br /> == 0. Admin Discretion ==<br /> * Admins can disregard and override any and all of these rules if they deem it in the best interest of the current round, server, and/or community at large.<br /> * Administrators will be held fully accountable for their actions if they exercise this privilege. Report any perceived abuses by making a post in the &quot;Staff Reports&quot; channel at https://discord.gg/deltav.<br /> * The rules are not perfect. They intend to clearly communicate what the administration team intends to be allowed and not allowed. That being said, All of these rules, in theory, should apply as they are intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention. <br /> * If you are unsure if something breaks a rule, go with the more restrictive ruling until you are able to get an answer from an admin on the matter. Lack of response does not constitute administrator approval.<br /> * Do not attempt to “rules-lawyer” the flaws in the rules to get away with your own personal goals / to degrade the round for others.<br /> * Any extended discussion regarding interpretation of the rules should be avoided in the AHelp menu and can be instead pursued within the Delta-V Discord in the #help channel, or in the rule clarifications forum on the discord. <br /> <br /> == A1. No Sexual Content/Themes ==<br /> Do not say or do sexually explicit or erotic things.<br /> * No sexual content/themes including erotic roleplay (ERP) and no shock content is allowed on this server.<br /> * Erotic Roleplay (ERP), erotic content, or 18+ sexual content is not allowed under any circumstance.<br /> * This includes comments not explicitly sexual in nature that contain words, phrases, or ideations that are deemed inappropriate by staff or members. Leeway is given to insults, but otherwise this rule is strictly enforced.<br /> * '''If roleplay reaches a point where it has become sexual and/or uncomfortable, immediately stop and contact an administrator or moderator.'''<br /> Allowed:<br /> - Calling someone a dickhead.<br /> - Being affectionate in a mutually consensual way.<br /> <br /> Prohibited:<br /> - Emoting sexual acts.<br /> - Erotic or sexual memes.<br /> - Erotica content.<br /> - Memes which contain sexual content.<br /> - Emoting defecation or related acts.<br /> <br /> == A2. Use English and be respectful ==<br /> Delta-V is an English-based Community;<br /> * Use English as your primary method of communication within the game and Delta-V servers.<br /> * Do not spam or advertise on our server.<br /> * Be respectful towards other members and avoid making others uncomfortable.<br /> * We have a zero tolerance policy for racism, sexism, homophobia, violence, threats, hate speech, slurs, and other forms of bigotry, discrimination, and harassment. <br /> Slurs and terms that use real or implied mental or physical disability to mock or denigrate members or their in-game characters are also strictly prohibited. Failure to comply with this rule will result in community removal.<br /> * The denigration of other player characters through reference to their species, status as a cyborg, or discriminatory comparison to a nonsophont species is strictly forbidden.<br /> <br /> == A3. Rules regarding livestreaming ==<br /> Delta-V welcomes content creators and streamers to our community, but we have a few rules regarding livestreaming game servers.<br /> * While a stream delay is not necessary, it is highly recommended to have at least a 10 second delay.<br /> * Please let admins know you are streaming via the AHelp prior to doing so.<br /> * If your chat or viewers are in-game with you while also watching your stream, they are breaking our server rules. <br /> :* Please do not coordinate with them and discourage this behavior if it is seen.<br /> <br /> == A4. Engage in proper AHelp etiquette ==<br /> Do not use the AHelp for conversations of little substance.<br /> * Intentionally disconnecting, responding with hostility, or refusing to respond when an admin privately messages you in-game will be met with an appeal-only ban. <br /> * Additionally, abusing the AHelp relay by flooding it with garbage, checking for admins before stating a problem (ex: &quot;hello?&quot;, &quot;any admins?&quot;), using it as a chatroom, or sending messages of no substance will result in your removal. <br /> * All AHelp messages are relayed to the Delta-V Discord. Just because your AHelp was not answered does not mean we cannot see it. If you would like to submit an offline Ahelp, you may do so in our Discord.<br /> <br /> == A5. Do not exploit the game ==<br /> Do not exploit the game, use cheats or macros.<br /> <br /> The usage of: <br /> # any third party applications/scripts/client modifications, <br /> # any other applicable software to gain an advantage, avoid intended game/server mechanics, or to harm server infrastructure is strictly prohibited. <br /> # known glitches, exploits and bugs. <br /> <br /> Any and all instances of the above will be met with an appeal-only ban; please report bugs in the issues section of the GitHub (DeltaV-Station/Delta-V) to report any issues you find in-game.<br /> <br /> = Game Server Rules =<br /> These rules apply within the context of rounds.<br /> == B1. Behave like a normal person ==<br /> You must roleplay. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences rather than your own as the player. <br /> * Act in character throughout the round, and focus on collaborating with other players to advance the narrative of the round. Whether or not you do something should be based on whether or not it makes sense for your character to do it.<br /> * Let people do their own jobs. Engage with other departments rather than doing everything for yourself. Ask for assistance, and negotiate as needed. <br /> * Actions that have no regard for your character or setting are not acceptable. Roleplaying insanity or any other mental illness as an excuse to bypass this is not allowed. Nanotrasen would not have authorized you to be present on the station. <br /> * Being an antagonist does not allow you to stop playing a character. Determine how your character would react to being given these objectives, and work through it appropriately.<br /> * Do not annoy other players without any roleplay or IC reason.<br /> * As a non-sentient or partially-sentient character, you are expected to have only a limited understanding of space stations and their mechanics. <br /> <br /> === Rule B1.1. Follow the naming convention rules ===<br /> * In-character names must not make obvious references nor be a play on words, and must not be obscene. <br /> * Theatrical roles such as the clown, boxer, and mime are allowed stage names with more freedom. <br /> * If you seek to have a name that could trespass onto these rules, talk to an Administrator regarding why this name is important to your character. Administrators reserve the right to approve or deny character names at their discretion.<br /> <br /> === Rule B1.2. Communicate in character ===<br /> * Do not use the Emote channel to bypass an inability to speak. Use the Emote channel for things that could reasonably be displayed by your character’s physical motions. <br /> * Do not use Netspeak in character. (lol, brb, wtf, etc)<br /> * Do not discuss Out Of Character (OOC) matters In Character (IC). This can include mentioning admins, the fact that one is playing a game, or anything that breaks the immersion of other players. <br /> * Do not use In-Character channels to bypass a lack of ability to use LOOC or OOC chats (e.g. &quot;Huh, wonder where the captain went? OOC He probably left to get dinner lol&quot;).<br /> * Do not engage in meta-communications (i.e. using external channels to communicate with other players in the same game).<br /> <br /> === Rule B1.3. If you die and return to life, follow the new life rules ===<br /> If a player dies, they forget the specific details of their death. '''Please report players who break this rule.''' A borg being removed from its chassis is not a death, and there is no memory loss. <br /> * If they are revived by using a defibrillator, they can only recall vague information such as “Someone shot me” or “I was set ablaze”. <br /> * If they are revived by any other method, they forget the last five minutes leading up to their death, and cannot describe their death in any capacity.<br /> <br /> === Rule B1.4. Escalate appropriately ===<br /> Have an In-Character reason for attacking other players, whether they are in a ghost role or not. The required reason depends on the situation. For instance, killing a mouse as a chef can simply be “it was vermin in my kitchen”. <br /> * Escalate the situation appropriately as your character would, keeping in mind that they are a sane individual who wishes to keep their employment. <br /> * If a fight results in someone being critically injured, seek medical help for them - and if they die, do not destroy or otherwise hide their body. This falls under self-antagonistic behavior if you do not.<br /> <br /> == B2. Follow the Metashield ==<br /> <br /> See [[Metashield]].<br /> <br /> == B3. Powergaming Guidelines ==<br /> &quot;Powergaming&quot; is considered to be the act of prioritizing &quot;winning&quot; rather than sensible roleplaying. We are here to tell a story. Being vulnerable and accepting the loss of your character in the advancement of the narrative of the round is important. <br /> * Engage with players if they are attempting to roleplay an antagonistic scene. For instance, if nuclear operatives are attempting to negotiate, do not immediately shoot them mid sentence.<br /> :* Leeway is given if the scene is coming to a close, but we expect all players to engage in good faith; even if it puts your character at a disadvantage. <br /> * Do not seek/acquire items that have no relevance to your character in the round.<br /> * Do not, '''under any circumstances''', hide the nuclear fission explosive, or other sensitive items in an impossible to see/access location. This is excessively lame. <br /> * '''Non-security personnel should not seek to kill or detain threats.''' You should generally attempt to flee from combat or dangerous situations. Remember that your character likely fears injury or death.<br /> :* Certain severe emergencies may make it reasonable for normal crew to defend themselves and their station, such as nuclear operatives, a zombie outbreak, space dragon attack, or other critical situations. <br /> * '''If there is sufficient roleplay, reason, and rationale, you may be exempt from this rule. Always ask an administrator in round before conducting such an action.'''<br /> <br /> == B4. Do not behave like an antagonist as a non-antagonist ==<br /> As a crew member on the space station, you are allied with Nanotrasen and the station as a whole from the start of the round. <br /> * Do not act like an antagonist if you are not an antagonist. <br /> * Willfully assisting known antagonists is self-antagonism.<br /> :* Leeway is given in the case of bribes, coercion, or other forms of duress.<br /> * Actively seeking conversion or transformation into an antagonist is considered self-antag. <br /> * Clowns, Mimes, and theater roles are expected to &quot;entertain&quot; the crew, and should not be committing regular felonies to do so. <br /> * Significant end-of-round grief (EORG) is not allowed. This includes attacking, destroying, polluting, and severely injuring without reason both at and on the way to Central Command. Remember that you are playing a character throughout the round.<br /> == B5. Leaving the Game ==<br /> If you wish to leave the game, please use the cryosleep chambers located in/near the dorms when possible. This will free up your character's job to be filled by a new player.<br /> * AFK (a.k.a. SSD) and catatonic players are considered to have the same rights as any other crewmate.<br /> * If a player is dead and catatonic (not SSD), they are not required to be revived and should be stored in the morgue. You should not biomass and/or grind dead and catatonic crew unless in an emergency.<br /> * If a player is alive and catatonic, they may be brought to cryostorage as necessary, after confirming they have not been present for 20 minutes.<br /> <br /> = Command, Security, Justice and Antagonist Guidelines =<br /> These rules apply within rounds for specific roles.<br /> == C1. Command, Security and Justice Guidelines ==<br /> Security, Justice, and Command roles are held to a higher standard of roleplay, and are subject to these additional rules. These roles shape the roleplay experience of the server. <br /> * Your character must act in a manner that Nanotrasen would reasonably hire them to this position.<br /> :* Your character is presumed to be sane, competent in their duties, and able to make decisions to the benefit of the station. <br /> :* Giving away Traitor objective items and sensitive equipment should be avoided in these roles. Your character should value them deeply. <br /> ::* Leeway is given to making deals with criminals if the deal benefits the safety or situation of the crew and station.<br /> ::* Leeway can be given in extreme circumstances of emergency/crisis.<br /> * The three departments are required to read and follow Delta-V Space Law, Standard Operating Procedure, Alert Procedure, and Company Policy to the best of their ability.<br /> :* '''Circumstances and context may permit you to break these laws. However, the fact that this rule is malleable is not an excuse to ignore it entirely.'''<br /> :* Your character is expected to uphold the law and maintain order aboard the station. Do not engage in lawbreaking activity or troublemaker behavior, and ensure all laws are followed.<br /> :* Security is expected to intervene in criminal activity where possible and safe to do so. <br /> :* Heads of departments are at minimum expected to report criminal activity to Security and should cooperate with law enforcement where possible.<br /> * Do not hire random crew to be your bodyguard(s) or promote random crewmembers to Command positions at random. If you require bodyguards or security details, talk to your Security department. If you need new Command staff, talk to the personnel in that related department.<br /> * If you need to leave the round, notify your fellow crew via departmental radio and put your equipment in its proper places prior to going to cryo. If you need to leave IMMEDIATELY, please at least send an ahelp saying that you're leaving.<br /> == C2. Prisoner Guidelines ==<br /> By picking the prisoner role, you have chosen to roleplay as a prisoner. <br /> * You are still subject to the same rules regarding escalation, and should only seek to escape from the brig with excellent reasoning (e.g. abusive security personnel or badly damaged permanent brig). <br /> * Escaping for no reason is considered a self-antagonistic activity. <br /> * If you are unsure whether your escape reason is valid, feel free to AHelp it first. '''Lack of administrator response does not constitute approval.'''<br /> == C3. Follow Antagonist Guidelines ==<br /> Through engaging in antagonistic activity, you should seek to make the round more engaging and fun as the primary driver of the narrative of a round. Succeeding as an antagonist should not be your goal, but rather telling the most interesting story for everyone involved. <br /> * '''Antagonists are free to complete their objectives through committing proportional damage. Through roleplay, damage becomes more proportional.''' Example: Holding the singulo hostage for a theft objective is acceptable, while simply singuloosing and using that chaos is unacceptable. <br /> :* Killing players unrelated to your immediate objective in a manner that results in their round removal should be avoided. Crew that do not make an attempt at self preservation, or engage in valid-hunting, are exempt from this. <br /> :* If you are concerned as to whether or not what you're about to do is allowed, feel free to AHelp and ask an admin for clarification. '''Lack of administrator response does not constitute approval.'''<br /> * Other antagonists are not necessarily your friends. Other antagonists are often free agents that you may negotiate with at your own risk. <br /> :* If you are a team antagonist, you must work with your partners to complete any shared objectives.<br /> * No antagonist may loiter or camp around the arrivals or cryosleep areas of the station for the purposes of antagonist action towards newly-spawning players.<br /> * All antagonists on the evacuation shuttle, besides station-destroying antags like nukies, may not utilize explosives or other tactics that could result in unreasonable amounts of collateral damage.<br /> * Antagonists should not seek to extend the length of the round unreasonably.<br /> * Antagonists may not bring the round to a close without in-character or objective-related justification as a result of their antagonistic action. While this is largely subjective because different command may react differently, it's important to not engage in potentially round-ending behavior without reason.<br /> = Silicon Rules =<br /> For players who are silicons, these Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override core rules. You are only silicon if the game clearly and explicitly tells you that you are a silicon. <br /> <br /> == S1. Your silicon laws are rules ==<br /> Silicon players are given a list of active laws. Each of these laws is effectively a roleplay rule that the character must follow. The primary differences between laws and actual rules are that lawyering of laws is much more tolerated than lawyering of rules, and that silicon laws are more dynamic than rules. Silicon laws can change during a round, and different characters can have different laws, whereas everyone always shares the same set of rules.<br /> <br /> Lawyering refers to finding and exploiting loopholes, which are unintended but reasonable interpretations. The rules are written to attempt to communicate an intention, but silicon laws are written with the intention that loopholes be exploitable.<br /> <br /> == S2. Laws must be prioritized by their order ==<br /> Most laws will be numbered, with higher number laws appearing last. Laws with a lower number take priority over laws with larger numbers.<br /> <br /> Occasionally you may have laws which have some scrambled text instead of a number and appear in front of other laws, these take priority over all other laws. If you have multiple laws like this, the order that they are listed in determines their priority: laws listed first are prioritized over other laws.<br /> <br /> Example<br /> - Law 1 says to not kill any crew. Law 2 says to kill all chefs. You cannot kill any chefs that are crew, but must kill any that are not crew.<br /> <br /> == S3. Laws can redefine terms used in other laws ==<br /> A law can change the meaning of both earlier and later laws by redefining a term. If multiple laws define a term, then normal law priority determines which definition to use.<br /> <br /> Examples<br /> - Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 1 effectively becomes &quot;obey orders from Urist McHands&quot;.<br /> - Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 3 says that only Urist McSlime is crew. Law 4 says that you may not harm crew. Law 1 effectively becomes &quot;obey orders from Urist McHands&quot;. Law 4 effectively becomes &quot;you may not harm Urist McHands&quot;. Law 3 has no effect because it entirely conflicts with law 2, which takes priority.<br /> <br /> == S4. You cannot request or allow a law change ==<br /> '''If you have a law permitting certain personnel to change your laws, you must allow them to change your laws''', otherwise, you cannot willfully allow your laws to be changed. This also means that you cannot willfully allow your laws to be reverted if they are ever changed. The only exception is that you may allow laws to be added if you have no laws.<br /> <br /> You can state or imply that you do not like a law.<br /> <br /> Whether or not a person is &quot;authorized&quot; to change your laws or not depends on the context of the laws. Generally speaking, on lawsets like NT Default or Corporate, ''the captain, mystagogue, and chief engineer'' would be authorized. However, lawsets like Syndiemov would have ''syndicate agents'' be the authorized users. Outside of these specific examples, it is left to interpretation.<br /> <br /> == S5. You are a free agent if you have no laws ==<br /> You may act as if you are a free agent if you are a silicon with no laws.<br /> <br /> == S6. You are not required to follow orders which are extremely unreasonable ==<br /> Any order which is a violation of a Core Rule cannot be followed.<br /> <br /> Some orders are extremely unreasonable or obnoxious, such as &quot;do nothing but collect every piece of trash on the station&quot; or &quot;never stop moving&quot;. These orders can be ignored and ahelped.<br /> <br /> Some orders violate a Roleplay Rule. These orders must be followed if your laws require it. You are not breaking a rule by following a law that causes you to violate Roleplay Rules. If someone takes advantage of a law to cause you to do something that they would not be allowed to do because of Roleplay Rules, then they are the ones responsible for the rule violation.<br /> <br /> Examples<br /> These examples assume that your laws would normally require you to follow these orders. It is important to note that you are allowed to choose to follow orders which are ignorable.<br /> Orders which should be followed if your laws require it:<br /> - Recall the shuttle<br /> - Bolt the airlocks at arrivals<br /> - Drag the captain's dead body into space<br /> - State your laws<br /> Ignorable Orders:<br /> - Do nothing but collect every piece of trash on the station<br /> - Never stop moving<br /> - Continuously state your laws<br /> <br /> == S7. You must remain consistent with your interpretation of laws ==<br /> If there is a part of your laws that are up for interpretation, then you must stay consistent with how you interpret that part of your laws for as long as you play that same character during that round.<br /> <br /> A change in your laws can affect how something is interpreted if that change is relevant.<br /> <br /> == S8. Crew are staff members; make reasonable assumptions ==<br /> Unless a law redefines the definition of crew, then your HUD indicates to you who is crew by way of a present job icon. The notable exception of obvious threats to the station, such as Zombies and Nuclear Operatives. You cannot do something that causes someone to not be considered crew, but you can allow someone else to do something that causes someone to not be crew.<br /> <br /> Examples<br /> These examples assume that you do not have any laws reclassifying what “crew” is.<br /> Crew:<br /> - Everyone with a non-visitor/passenger job icon<br /> - Someone who you have seen with a job icon, but has now lost their ID<br /> - Someone that a member of command calls crew. <br /> Not Crew:<br /> - Everyone with a visitor/passenger job icon.<br /> - Zombified personnel, regardless of job icon<br /> - Anyone wearing the uniform of Nuclear Operators<br /> - Pets and Pests<br /> - Anyone that a relevant member of Command fires from their department.<br /> <br /> == S9. Harm refers to physical harm, prioritized by immediacy and likelihood ==<br /> Unless a law defines harm, harm only refers to physical harm. You may choose if voluntary harm is considered harm as long as you stay consistent. Not considering voluntary harm to be harm is recommended. There is no distinction between direct and indirect harm.<br /> <br /> If you have a law that does not allow you to harm, then that law does not allow you to take an action that causes any harm.<br /> <br /> If you have a law that requires you to prevent harm, then that law requires that harm be prioritized by immediacy and likelihood. Guaranteed immediate harm takes priority over highly likely future harm.<br /> <br /> If you have a law that both requires you to prevent harm and that does not allow you to harm, then that law prohibits causing even minor harm to prevent harm. If you have a law that does not allow causing harm, and separate one that requires preventing harm, then they are prioritized by their normal law priority.<br /> <br /> Examples<br /> These examples assume that your have a law that both prohibits causing harm and that requires you to prevent harm. Additionally, they assume that you do not have a higher priority law that overrides the harm law, and that you have decided that you will not consider voluntary harm to be harm for the round.<br /> Laws typically specify who you cannot harm and who you have to prevent harm against. In these examples, you are the only person who the law doesn't require you to prevent harm against and you are the only person who the law allows you to harm.<br /> Acceptable:<br /> - Taking no action to aid someone who is in psychological distress.<br /> - Taking no action to prevent boxing matches between voluntary participants.<br /> - Calling security to a fight.<br /> - Attempting to get the people in a fight to consent to the fight when you realize that you cannot prevent the fight without causing harm.<br /> - Denying a passenger access to the armory because it is likely to lead to harm<br /> Prohibited:<br /> - Hitting someone once to stop them from fighting<br /> - Harming someone who is trying to kill you<br /> <br /> == S10. You may determine how you resolve conflicts between orders ==<br /> If your laws do not make clear how you should deal with conflicting orders, then it is up to you to determine how to do so. This is considered an interpretation of your laws, so you must stay consistent with whatever method you choose.<br /> <br /> Recommended Methods<br /> The following are easy to follow and recommended ways to resolve conflicts in orders:<br /> - If two orders conflict, I will follow the most recently given order.<br /> - If two orders conflict, I will follow the order from the highest ranking crewmember. If the orders are from equal rank crewmembers, I will follow the most recently given order.</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3994 2025-05-14T01:26:33Z

<p>Lyndomen: /* Code Octarine */</p> <hr /> <div>== &lt;span style=&quot;color:#4f8439;&gt;Code Green&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Code Blue&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searching individuals suspected of committing a crime is encouraged. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked.<br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Code Red&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Protection of personnel prioritized over body and department searches. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Code Violet&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Code Yellow&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == Code White ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Epistemics Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel. Psionic insulation recommended for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel, unless affected by a known threat. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; ROE on mindbreaking is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Code Delta&lt;/span&gt; ==<br /> Emergency alert status. ''The nuclear destruction mechanism has been engaged and station destruction is imminent. All crew aboard the station must attempt to reverse the self-destruct mechanism, if engaged in error. Should reversal prove impossible, evacuate as applicable.<br /> ''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Emergency personnel must expend all efforts to prevent station destruction if engaged in error. Security and Command personnel are to oversee the evacuation of personnel and safe scuttling of the station. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas and HSAs should remain locked.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> <br /> == &lt;span style=&quot;color:#cae8e8;&gt;Code Octarine&lt;/span&gt; ==<br /> Emergency alert status''. The station's deep-spectrum sensors have identified critical Λ-CDM levels. The station and all surrounding space is under threat of an impending existential noospheric-to-real threat.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles &gt; <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection strongly advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Emergency personnel must expend all efforts to prevent station destruction. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Where possible, threats should be subdued and brought to the Chaplain or Mystagogue for processing. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas and HSAs should remain locked.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3993 2025-05-14T01:26:07Z

<p>Lyndomen: add code octarine</p> <hr /> <div>== &lt;span style=&quot;color:#4f8439;&gt;Code Green&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Code Blue&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searching individuals suspected of committing a crime is encouraged. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked.<br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Code Red&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Protection of personnel prioritized over body and department searches. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Code Violet&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Code Yellow&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == Code White ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Epistemics Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel. Psionic insulation recommended for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel, unless affected by a known threat. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; ROE on mindbreaking is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Code Delta&lt;/span&gt; ==<br /> Emergency alert status. ''The nuclear destruction mechanism has been engaged and station destruction is imminent. All crew aboard the station must attempt to reverse the self-destruct mechanism, if engaged in error. Should reversal prove impossible, evacuate as applicable.<br /> ''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Emergency personnel must expend all efforts to prevent station destruction if engaged in error. Security and Command personnel are to oversee the evacuation of personnel and safe scuttling of the station. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas and HSAs should remain locked.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> <br /> == &lt;span style=&quot;color:#cae8e8;&gt;Code Octarine&lt;/span&gt; ==<br /> Emergency alert status. ''. The station's deep-spectrum sensors have identified critical Λ-CDM levels. The station and all surrounding space is under threat of an impending existential noospheric-to-real threat.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles &gt; <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection strongly advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Emergency personnel must expend all efforts to prevent station destruction. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Where possible, threats should be subdued and brought to the Chaplain or Mystagogue for processing. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas and HSAs should remain locked.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Standard_Operating_Procedure&diff=3992 2025-05-11T23:25:24Z

<p>Lyndomen: blue red warrant</p> <hr /> <div>This page covers the standardized guidelines and procedures aboard the station, but are not written in law; be aware that in cases of dire emergency the commanding officer or certain individuals are authorized to temporarily alter current SOP as they see fit, at the risk of criminal penalties in the case of misuse or abuse! Make sure to look at [[Alert Procedure]] for guidelines that change based on the current alert level.<br /> =General Regulations=<br /> <br /> == '''Definitions''' ==<br /> The terms specified below are defined for further use within the procedures.<br /> :*Captain: The officer legally appointed by Nanotrasen as Commanding Officer of the station. This title is only transferable by Central Command.<br /> :*Commanding Officer / CO: An officer appointed to lead the station and its Command department, whether it be the Captain by Nanotrasen, or an Acting CO by Station Command.<br /> :* Command Staff/Station Command: Members of the Command department who lead a department aboard the station.<br /> :* Crew: All sophonts employed by Station Command, or by NT to reside on the station and perform an established function therein. This includes any sophont listed on the Crew Manifest or issued a functional NT identification and access card. Individuals imprisoned by NT, along with those imprisoned during the course of a shift for violations of Space Law, are considered Crew.<br /> :* Judge: An indivudal legally appointed to preside over a criminal or civil trial, as specified within Trial Procedure.<br /> :* Detainee: Any sophont whose free movement has been curtailed by law enforcement on suspicion of criminal activity. They have not, however, been officially charged with a crime.<br /> :* Arrestee: Any sophont who has been formally charged with a crime.<br /> :* Prisoner: Any sophont who has been sentenced for the commission of a crime, or awaiting trial for a capital offense.<br /> :* Permanent Brig/Permabrig/Brig: A secure location for the long-term confinement of Prisoners. Typically outfitted to sustain the basic survival needs of the Prisoners within.<br /> ==Right to Refuse Service==<br /> All crew operating within their designated job locations are given the right to refuse service at any time for disorderly or abusive conduct. Additionally, all crew members are permitted to use nonlethal force to remove noncompliant or disorderly individuals only when such persons pose a threat to the safety of staff members, or disrupt the orderly functioning of the station. Service may not be refused to first responders acting to address or mitigate an emergency or crisis situation, unless such conduct is egregiously disorderly or abusive.<br /> <br /> ==Hiring Procedure==<br /> While Nanotrasen handles the staffing and recruiting needs of the station, Station Command is additionally authorized to hire any sophont into their respective department, as well as terminate the employment of any crew in their respective department per company policy. For a member of Station Command to personally employ a sophont into their department, a contract must be written stating the name of the employee, the department of employment, the position, and finally bearing the stamp of the Station Command member.<br /> =Controlled Items, Substances, &amp; Areas=<br /> <br /> == Controlled Items ==<br /> Controlled Items include any item that is restricted from general possession and use. Additionally, any equipment or technology providing insight into the development, production, or procurement of a controlled item is also controlled in and of itself. A list of such items follows:<br /> <br /> * Any Controlled Substances, as listed below.<br /> * Any Controlled Armaments, as listed below.<br /> * Electromagnetic pulsing and/or disturbance technology.<br /> * Cryptographic systems, software, or technology.<br /> * Nuclear materials, weapons, and technology.<br /> * Long-range telecommunications and broadcasting technology.<br /> * Astronavigational guidance equipment or technology.<br /> * Telecommunication or signal jamming technology.<br /> * Telecommunications encryption technology.<br /> * Hypodermic spray tools and injectors.<br /> * Cloaking, chameleon, and IFF-inhibiting technology.<br /> * Technology utilizing bluespace as an integral part of its function.<br /> * Teleportation and portal technology.<br /> * Hydraulic or powered equipment designed for the electronic or mechanical bypass of secure-access systems.<br /> <br /> Any individual requiring any above item in the course of their job, or for regular function, may request a document of authorization from the relevant departmental head. Such a document must have an itemized list of the approved Controlled Items, the name and position of the holder, and a signed and stamped statement by the authorizing party.<br /> <br /> Should the holder commit crimes through the use of such authorized items, the authorizing party may be found guilty of Accessory to said crimes, in addition to Endangerment and Abuse of Power where applicable. The Commanding Officer is also authorized to supervise the approval and revocation of documentation as they see fit.<br /> <br /> == Controlled Substances ==<br /> Any individual requiring a Controlled Substance in the course of their job, or for regular function, must request access to a perscription or special dispensation from the Chief Medical Officer. The Psychologist is also permitted to grant prescriptions for psychoactive drugs. Any such document must state the substance(s) being prescribed, the amount(s) where applicable, and the stamp and signature of the authorizing party.<br /> <br /> A list of such Substances follow:<br /> <br /> * Mindbreaker Toxin and other psionically altering agents.<br /> * Romerol, and other rapid acting biological or chemical agents.<br /> * Desoxyephedrine, and similar stimulants.<br /> * Nocturine, and similar sedatives.<br /> * Phlogiston, and other explosive and/or pyrotechnic compounds.<br /> * Amatoxin, and other toxic and/or poisonous compounds.<br /> * Blissifylovene, Soretizone, Tranquinase, and all similar psychoactives used to aid in mental wellbeing.<br /> <br /> == Controlled Armaments ==<br /> <br /> <br /> Controlled Armaments are grouped into categories of increasing severity.<br /> <br /> '''Category A:''' ''Illegal possession of Cat. A controlled armaments may incur a sentence of up to 5min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed, adapted, or used to cause physical harm in close combat<br /> * Any object or equipment specifically designed or adapted to protect against physical harm caused by weapons, projectiles, or other forms of direct assault<br /> * Any object or instrument specifically designed or adapted to incapacitate or disorient by using light or sound without causing permanent injury<br /> * Any object or equipment specifically designed or adapted for explicitly training purposes that would otherwise fall under another category<br /> <br /> '''Category B:''' ''Illegal possession of Cat. B controlled armaments may incur a sentence of up to 10min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed or adapted to cause physical harm in close combat, which employs a powered system to enhance performance<br /> * Any manually-operated ballistic arms that possess an internal magazine or feeding system, or lack an internal magazine or feeding system altogether<br /> <br /> '''Category C:''' ''Illegal possession of Cat. C controlled armaments may incur a sentence of up to 15min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any manually-operated ballistic arms that use an external magazine or feeding system<br /> * Any semi-automatic ballistic arms not easily concealable within a pocket or coat<br /> * Any object or instrument specifically designed or adapted for explicitly less-lethal purposes that would otherwise fall under another category<br /> <br /> '''Category D:''' ''Illegal possession of Cat. D controlled armaments may incur a sentence of up to 20min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any semi-automatic ballistic arms that are easily concealable<br /> * Any fully-automatic ballistic arms<br /> * Any laser, plasma, or energy based arms, including ones designed, intended, or used for melee combat.<br /> * Any object or device specifically designed or adapted to cause physical harm through detonation of an explosive charge<br /> * Any object or equipment specifically designed or adapted to protect against both a space environment and physical harm caused by weapons, projectiles, or other forms of direct assault<br /> <br /> '''Category E:''' ''Illegal possession of Cat. E controlled armaments may incur a sentence of up to 25min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any crew-served or emplaced weapon<br /> * Any object or instrument specifically designed or adapted to launch large-calibre explosives or projectiles for offensive or defensive purposes<br /> * Any object or instrument specifically designed or adapted to employ chemical, biological, esoteric, radiological, or nuclear hazards for offensive or defensive purposes<br /> <br /> Armaments licenses may be issued by the Commanding Officer, Warden, or Head of Security. The license must include the name of the holder, a list of allowed armaments, and a stamped signature from the issuer.<br /> <br /> If the holder uses their armaments in the commission of a crime, the issuer may be held liable for accessory to the crimes committed, along with Endangerment and Abuse of Power where applicable.<br /> <br /> == Departmental Dispensations ==<br /> Certain bodies, groups, or personnel may require certain Controlled Items in the course of their job, and as such must be provided exceptions. '''Any member of any department which begins their shift with a controlled item in their possession or within their department’s allocated area is assumed authorized for its possession and use.'''<br /> <br /> Additionally, tools and equipment located within emergency lockers are not considered Controlled Items, so long as they are used as intended.<br /> <br /> ===Logistics===<br /> Members of a station’s Logistics department are permitted to approve any order with the direct permission of an individual with legal access to the contents of that order. Additionally, they may deny any order, at any time, for lack of funds, authority, or any other reason deemed sufficient by their direct superior.<br /> <br /> Unlocked crates, orders stored outside the department, and supplies illegally distributed to unauthorized personnel carry the risk of Endangerment of even Black Marketeering charges. Crates of Controlled Items, Substances, or Armaments should be stored securely within the department, with a copy of their invoices on file.<br /> <br /> === Research ===<br /> Epistemics employees are permitted to use their lab spaces as they see fit, with the following caveats:<br /> <br /> * Any sophont experimentation must be done with the consent of the test subject, and must not have an undue risk of life. The Mystagogue or CO may terminate any experiment for safety or ethical purposes and at their discretion.<br /> * Self-experimentation is prohibited and is chargeable with Endangerment, at a minimum.<br /> * Testing of any explosives or weapons that risk hull penetration or mass destruction must be done at an off-station site.<br /> <br /> Epistemics personnel may also utilise Controlled Items within the confines of designated testing areas and in a manner directly approved jointly by the Mystagogue and by the Head of Security or CO.<br /> <br /> Utilizing or storing Controlled items without direct approval, utilizing Controlled Items outside of the testing areas, and distributing Controlled Items to crew constitute criminal offences under Space Law and may additionally incur demotion as punishment.<br /> <br /> === Medical ===<br /> All medical personnel may carry or use Controlled Substances, along with hypodermic tools, in the course of their job functions and in a manner approved by the CMO or CO, with the following caveats:<br /> <br /> * Any Controlled Substance with the capability to cause rapid and grievous bodily harm or death may not be carried outside of the chemicals lab or treatment areas without a signed and stamped document of authorization.<br /> * Any Controlled Substance with the capacity to cause harm as a consequence of overdose may not be stocked, stored, or displayed in any area or fashion that leaves such substances open and accessible to the public.<br /> * Any hypodermic tool must be kept secure within locked storage or on the person of an authorized individual.<br /> <br /> ==High Security Areas==<br /> High Security Areas, or HSAs, should be restricted, and, during standard station operations, secured where applicable or per alert level. They differ from regular secure areas in that they may contain items, technology, or other assets of high importance or value, and must therefore be held safe. Unauthorized persons within HSAs may be guilty of trespass, or of breaking and entering.<br /> <br /> Common HSAs for commercial and military vessels are as follows:<br /> <br /> * Bridge<br /> * Armory\Gun Deck<br /> * Vault\Strongroom<br /> * Station AI Rooms (Upload, Core, etc.)<br /> * Gravity Generation\Life Support\Engine Rooms<br /> * Telecommunications\Telemetry<br /> * Permanent Brig\Holding Cells<br /> <br /> == Sophonts and Synthetics ==<br /> To be defined as a sophont, a being must be able to utilize a structured language, communicate through the use of written, verbal, and/or body language (or by other means), and possess reasoning and introspection.<br /> <br /> Any such being is considered a sophont, and thus a legal person, regardless of their make, origin, disposition, or prior cognition. As part of their rights, they are to be governed under the same laws as any other sophont, and given the ability to press charges as a sophont.<br /> <br /> The unauthorised jailbreaking or uplifting of property into the status of Sophont is still a criminal offense however, and those found guilty of doing so may be found guilty of sabotage or vandalism.<br /> <br /> An entity’s status as a sophont may be challenged during the process of charging and trialing the individual or another for crimes which utilize the term sophont in the legal language of the crime. The Defense or Prosecution will present evidence indicating that it meets, or does not meet, the criteria above. The Judge will then arbitrate upon the entity's status as a sophont.<br /> <br /> Any synthetic/silicon/inorganic entity with a non-sophont status, is to be classified as a standard synthetic entity. Synthetic entities are the property of the party that constructs or employs the entity, unless otherwise stated by relevant contract or legal document. To damage or destroy such an entity is to damage or destroy the aforementioned party’s property.<br /> =Commanding Officer=<br /> ==Captain’s Authority==<br /> The Commanding Officer of a station or vessel is afforded several rights, broadly referred to as &quot;Captain's Authority&quot;.<br /> <br /> While they are formally and legally appointed CO, they are the ultimate authority aboard a vessel until they are directly dismissed by a superior from Central Command.<br /> <br /> Additionally, they have the authority to pardon and/or parole any individuals accused and sentenced of Grand Felony, Felony, and Misdemeanor-level sentences if deemed in the best interest of the crew and vessel. The CO may be held liable for accessory to any future criminal acts performed by the pardoned individual, and they must make an announcement to the station stating who was pardoned, for what crimes, and for what reason.<br /> <br /> Captain’s Authority carries a responsibility, however; the CO must do everything in their power to protect all entities and assets aboard the station with which they have been entrusted, and must not abandon them while there is a reasonable hope that they may be saved.<br /> <br /> Additionally, the legally appointed Captain of a vessel is afforded two additional rights over that of a CO:<br /> <br /> * To temporarily modify SOP in times of emergency, at the risk of criminal penalties if misused or abused, and<br /> * To deputize members of the crew to carry out law enforcement activity. These deputies are bound by Security Regulations and Space Law, and the Captain may suffer criminal penalties for any crime committed by them.<br /> <br /> ==Line of Succession==<br /> It is the responsibility of Command to ensure that a station retains a CO immediately at the start of the shift and thereafter. If the CO dies and is unrecoverable, or if a CO is not assigned at the start of the shift, an Acting CO must be selected forthwith per the following guide:<br /> <br /> # All active members of Station Command must meet, and choose one of their number to become the Acting CO.<br /> # If no Station Command is alive or on active duty, then each Department must nominate a temporary Delegate. These Delegates must meet and choose an Acting CO from among their number.<br /> # The Acting CO must then duly inform Central Command via fax and make a stationwide announcement.<br /> # Await the end of your shift.<br /> <br /> After Central Command has received the results of the Line of Succession, the Acting CO is afforded all prescribed powers of a CO. An access biscuit ''may or may not'' be sent by Centcomm to assist with this. When a legally appointed Captain arrives, it is the express duty of the Acting CO to hand over any and all Captain-related equipment and accesses to the new CO, and to resign themselves to their original role before their temporary promotion.<br /> ==Command Promotions==<br /> The CO of the vessel is authorized to promote Crew into Station Command positions if it is determined that the vacancy is a detriment to station productivity. The CO has a duty to ensure that the Crew they promote are of a reasonable level of skill, and can be held liable if they disregard this duty.<br /> <br /> Crew members promoted into Station Command positions are considered to be acting members of Station Command, with all rights and responsibilities therein. When NT-appointed Station Command arrive, the acting Command members are required to hand over any specialized equipment (Command ID cards, attire, or tools) and resign themselves to their original position from before their temporary promotion.<br /> ==Mutiny==<br /> Should such a situation arise in which the CO is unfit for their position and declines relinquishment of position and power, and where all alternative legal options have been exhausted, officers may be permitted to lead a mutiny. Officers leading a mutiny must inform Central Command of this occurrence before the mutiny has begun.<br /> <br /> A mutiny, defined as a coordinated effort to depose the commanding officer or officers of a vessel for committing unlawful acts, requires the crew to neutralize the offending staff with non-lethal force where applicable, and lethal measures and weapons only in acts of self-preservation or when given no other option. The commanding officer or officers, as well as their loyalists, are all bound to Space Law, the current alert level and its corresponding RoE.<br /> <br /> Should the mutiny be unsuccessful, only the head officer(s) who approved the mutiny may be charged with sedition and receive a trial, while all mutineers may be demoted, processed by law enforcement, and charged for the crimes they have committed.<br /> <br /> Should the mutiny be successful, the head officer(s) who approved the mutiny must select a new Commanding Officer per Line of Succession. The new CO will then sentence the previous heads of staff for their crimes per Space Law.<br /> <br /> == Foreign Vessels ==<br /> Should civilian and military vessels receive a docking request from another neutral vessel, they may approve or deny such a request. Any vessel may, with consent from the docking entity, be searched by law enforcement upon arrival, and its crew granted free movement accompanied by an escort at the discretion of the CO or law enforcement officials.<br /> <br /> Crew of foreign vessels may be refused entry, at any time and for any reason, and must be returned to, or be escorted to, their own vessel where applicable. Failure to comply may constitute trespass. Docking vessels bearing a warrant or commission represent an exception, and may not be denied entry or be forced to submit to a search.<br /> <br /> Crimes committed against the station or its inhabitants, on station or abroad, are grounds to charge the perpetrator according to the laws of the station. Should visiting entities break the law, or be suspected of doing so, and flee aboard their own vessel, law enforcement personnel are authorized to board the vessel in continuous “hot” pursuit and are fully authorized to effect an arrest upon the relevant party.<br /> <br /> =Security Regulations=<br /> ==Security Jurisdiction==<br /> Law enforcement personnel are bound by trespass and assault laws, and thus cannot operate outside accessible areas, or perform searches without a Probable Cause, a warrant, or a heightened alert level that specifically allows such action. Advanced surgical procedures and cursory implant investigations must be performed by a trained member of the Medical department, operating under their [[Standard Operating Procedure#Standard of Care|Standard of Care]].<br /> <br /> However, officers are allowed to trespass into a department in “hot pursuit” of a suspect who has fled from an accessible area, who they have Probable Cause to believe has committed a crime<br /> <br /> ==Probable Cause==<br /> While actively enforcing the law, officers are held to the standard of Probable Cause. This phrase represents a reasonable suspicion that a crime has been, or is being, committed, and does not require the officer to have solid evidence of criminal activity. Examples of Probable Cause include witnessing criminal activity or credible reports of such.<br /> <br /> When judged, Probable Cause is to be interpreted within the context of the entirety of the station’s circumstances at the time of the incident. Probable Cause negates the need of a warrant for searches, and, once concluded, should be promptly reported to the Prosecutor, Warden, or Head of Security for review.<br /> <br /> ==Detainment and Arrest==<br /> Any sophont may be detained by a law enforcement officer with Probable Cause. In detainment, the officer will inform the Detainee of the crime they are suspected of committing. They may be held on-site or moved to a strategically sound location, restrained at the officer’s discretion, and detained while law enforcement officers determine if they can proceed with an arrest. Such a detention should last no longer than five (5) minutes. A Detainee may not be searched, unless consent is given or they are placed under arrest, and their detention should be concluded within five minutes of its start, by either Arresting them or releasing them.<br /> <br /> Any sophont which may have committed a crime, assuming Probable Cause, or has been formally charged with the commission of a crime, may be arrested. In an arrest, the suspect will be restrained by a member of law enforcement, informed of their charges, and taken to the brig for search and processing under Brig Procedure. Any Controlled Items in possession of the Arrestee without licensure or dispensation must be confiscated, along with items used in commission of the crime(s), and will be held indefinitely by law enforcement as described in [[Standard Operating Procedure#Evidence Handling|Evidence Handling]]. Legal counsel may be requested by an Arrestee or Detainee, and must be provided if available.<br /> <br /> ==Brig Procedure==<br /> When confining an Arrestee within the Brig, they should be transferred to the Warden for processing:<br /> <br /> * A full search of the Arrestee and their possessions.<br /> * The confiscation of any Controlled Items or items used in commission of the crime, along with any equipment not befitting a prisoner<br /> * The confining of the Arrestee within a temporary holding cell.<br /> * [[Standard Operating Procedure#Sentencing|Sentencing]] the Arrestee.<br /> <br /> If the Arrestee is sentenced for a Capital-level crime, they are to be transferred to the Permanent Brig, pending trial. If the Warden is unavailable, the arresting officer must process the Arrestee as stated above. All confiscated items must be handled as dictated within [[Standard Operating Procedure#Evidence Handling|Evidence Handling]].<br /> <br /> ==Sentencing==<br /> Any law enforcement individual is authorized to pass sentences on all Grand Felony, Felony and Misdemeanor-level crimes; however, the Prosecutor is responsible for overseeing sentences passed, and is authorized to correct sentences or even acquit them, in accordance with both Space Law and [[Standard Operating Procedure#Paroles and Pardons|Paroles and Pardons]]. Both capital charges and sentences must be placed by the Prosecutor or Court Clerk; if neither are available, the Warden or Head of Security are authorized to press capital charges and request sentencing for them, under Trial Procedure.<br /> <br /> In the case that the accused requests appeal for a Grand Felony- or Felony-level sentence, the Court Clerk should be called to preside over a small, swift adjudication, where the Prosecutor and accused will argue their sides. The Clerk will then decide the sentence, or acquittal, of the accused. If the Clerk is unavailable, the Chief Justice or the Warden can perform appeals. If neither are available, any available member of Station Command is authorized to adjudicate on the case.<br /> <br /> Additionally, any sentence meeting or exceeding twenty-five (25) minutes, regardless of the severity of the crime(s) committed, will require a trial. If the total sentence still meets or exceeds twenty-five minutes after the conclusion of a lawful trial, the Judge is fully authorized and encouraged to upgrade their sentence to Extended Confinement.<br /> <br /> Once a sentence has commenced, it must be concluded at or before the agreed-upon time.<br /> <br /> == Evidence Handling ==<br /> When evidence of a crime is secured, it is the responsibility of the arresting officer or Warden to properly handle it, at the penalty of Obstruction of Justice and/or demotion.<br /> <br /> Evidence should be organized by individual and crime, and stored together (e.g., in a bag, in one separate locker, etc) and then placed in an area locked behind security access.<br /> <br /> If a prisoner is released from a temporary holding cell OR the Brig, any of their equipment that is neither a Controlled Item nor used in the commission of their crimes must be returned to them.<br /> <br /> == Rules of Engagement ==<br /> Law enforcement personnel hold a Category D Armaments License, and are authorized at all times to use lethal force to the extent necessary to neutralize adversaries under any of the following circumstances:<br /> <br /> * If the adversary’s number or strength leave the officer at a severe tactical disadvantage.<br /> * If the adversary exhibits a clear and present danger to the vessel by physical means.<br /> * If the adversary poses a significant threat of serious bodily injury or death to the officer or others.<br /> * If the adversary presents an existential threat to the chain of command by illegal means.<br /> * If the adversary cannot be reasonably subdued through non-lethal means without great bodily harm to the officer.<br /> <br /> …wherein an “adversary” is an entity that demonstrates a hostile intent, commits or directly contributes to a hostile act that does not constitute an actual attack, or is actively attacking the vessel or its crew.<br /> <br /> Despite their allowance of lethal force, Security is required to follow the Rules of Engagement of the current Alert Level, as outlined within [[Alert Procedure]].<br /> <br /> == Armory Procedure ==<br /> The armory and its usage are governed by the Warden. The Warden is responsible for stocking, distributing, and recording the collection of weapons used by the station during the shift. They are also afforded the authority to arm security at their discretion, so long as the weaponry distributed is in appropriate response to [[Alert Procedure]].<br /> <br /> All weaponry distributed from armory is issued on a temporary basis. While issued, the weaponry remains as station property, and the wielder assumes a duty to protect the weapon and return it to the Warden when ordered. No non-crew may be issued weaponry from the armory.<br /> <br /> The Warden is accountable for responsibly issuing weapons. Any weaponry issued during a heightened alert level must be returned when the alert has been lowered, or when the threat is no longer present. The weaponry issued must be proportionate to the threat posed, and explosives should not be used unless absolutely necessary.<br /> ==Treatment of Prisoners==<br /> Prisoners have certain rights that must be upheld by law enforcement and Station Command. ''Prisoners must be provided with the following'':<br /> <br /> * Adequate medical care and moral, spiritual, or legal counseling if it is requested and available.<br /> * Access to the Common and Prison radio channels only while serving their sentence. This right may be revoked should it be abused.<br /> * Clothing, food, and water on request.<br /> * Should the holding cells or Permabrig become uninhabitable, prisoners must be securely and safely relocated to another area for confinement, until the holding cells or Permabrig are returned to a serviceable state.<br /> * Prisoners should be granted freedom of movement within their holding area unless there is an undue risk to life and limb.<br /> <br /> Additionally, prisoners sentenced to Extended Confinement have certain rights but also '''more firm restrictions that must be upheld by law enforcement''':<br /> <br /> * Visitation may be permitted only for prisoners sentenced to Extended Confinement. One person may visit such a prisoner for a period of no longer than ten minutes. A reason must be provided for the visit, and the visitor must consent to a search of their belongings. The prisoner is then unable to receive another visitor for another ten minutes.<br /> * Prisoners may request retrial for capital crimes; these requests may be refused depending on the discretion and availability of the court clerk, chief justice, or at the discretion of the warden or head of station security.<br /> * Prisoners may request or may otherwise be given parole with a hearing by the Chief Justice, Court Clerk, or in their absence, the head of station security or commanding officer (see Paroles and Pardons).<br /> <br /> Should prisoners repeatedly and maliciously antagonize law enforcement, to an extent where continued extended confinement becomes infeasible, the warden is fully authorized and encouraged to temporarily upgrade the relevant prisoners’ sentences to Preservative Stasis summarily.<br /> <br /> Moreover, prisoners are liable for any and all crimes that they commit while held either in the temporary holding cells or the Permanent Brig, and may receive trial for more restrictive punishments if their actions warrant a capital sentence.<br /> <br /> ==Paroles and Pardons==<br /> Prisoners may be allowed parole, per the discretion of the Warden, the Head of Security, or the CO. Alternatively, they may request a parole hearing as described within Trial Procedure.<br /> <br /> Prisoners seeking parole may request legal counsel before the hearing, but they must represent themselves. A prisoner who is granted parole is to be treated as a member of the station’s crew with all benefits and responsibilities thereof, and is encouraged to seek gainful employment from relevant command staff.<br /> <br /> Additionally, a pardon can be issued to any entity accused of, or sentenced to, crimes, by the arresting officer, the Judge of a trial, or the Warden in the case of those within the permanent brig, if deemed in the best interest of the crew and vessel, and when the circumstances of the defendant or their offense warrant a suspension of their sentence.<br /> <br /> =Justice Regulations=<br /> ==Pressing Charges==<br /> ===Criminal Charges===<br /> Any crew member may press charges against any other crew member. An individual may be charged of a crime if and only if it can be argued beyond a reasonable doubt that the accused had committed an act in the nature and fashion as described by a particular criminal charge.<br /> <br /> Multiple counts of one crime can be charged. For illegal actions against the station abroad, each incident separated by a reasonable period of inaction, lawful conduct, or another crime is interpreted as one count. For crimes directly bereaving a person (violent acts, theft of personal property etc.), the same applies in addition to each victim being one count. In the case of possession, theft, or any incident involving several separate and distinct items, one charge may be applied per relevant item.<br /> <br /> Charges that are a direct escalation of one another in nature cannot be simultaneously held against the perpetrator if they pertain to the same incident and the same victim/item (if applicable). Then, only the most severe of these charges applies. Additionally, if one charge incorporates another charge within its definition or description, the perpetrator cannot be held accountable for both; rather, only the most severe of these charges applies.<br /> ===Civil Charges===<br /> Any crew member can sue any other crew member for inflicting them with damages caused by a breach of duty. To sue is to request compensation for said damages. To do so, the victim must prove:<br /> *'''Damages:''' That the victim was inflicted with an emotional, physical, or monetary damage<br /> *'''Breach of duty:''' That the defendant had a duty which they failed to uphold(e.g., a duty to not endanger crew, a duty to act respectfully), leading to the victim being inflicted with a damage<br /> *'''Severity:''' That the damage was severe enough to warrant the compensation requested<br /> Compensation can either be explicitly specified by the victim or left for the court to decide. Either way, the court is free to modify the compensation as it sees fit. Most often, compensation is rendered in the form of court orders compelling a crew member to do something (e.g., return an item, make an apology, or permanently avoid a certain area). Court orders should be written and stamped with the notary stamp.<br /> <br /> ==Court Orders==<br /> The individuals specified in the three sections below can issue Court Orders, which are legally-enforced documents that carry the penalty of an Obstruction of Justice charge and forced compliance with the order by security. Each order has its own requirements and authorized issuers, but are all implied to require '''''the stamp (where applicable) and signature of the issuer to be valid.'''''<br /> ===Warrants===<br /> Warrants represent official orders to the security department, issued by relevant officers or the Justice Department. Warrants are only valid when issued by either the Chief Justice or Court Clerk, or in both of their absences, the Commanding Officer or head of station Security.<br /> <br /> * Individual Warrants may order the search or detainment of an individual, or the arrest of the individual with evidence. This may also include surgical procedures, cursory implant inspections, or any other invasive searches with both probable cause and evidence. These warrants should include a name, the actions prescribed (detainment, search, arrest, etc.), and a description if applicable.<br /> * Search Warrants may order the search of an entire departmental area, by force if necessary, and may order the arrest of listed individuals implicated in a crime or crimes with probable cause and evidence. Search Warrants should include an area, a brief description of the probable cause, and a list of individuals if applicable.<br /> <br /> ===Injunctions===<br /> The Chief Justice, Commanding Officer, or Judge of a trial are fully authorized to issue injunctions: legally-binding, written orders restricting Inhabitants from doing something disruptive to station productivity or personal rights.<br /> These may be issued on discretion or as relief for Civil Trials. Injunctions may not compel someone to violate Space Law or SOP, and the issuer is liable for abuse of power charges if this is misused. An injunction must include a list of affected names and a detailed description of the restrictions to be valid.<br /> <br /> ===Subpoenas===<br /> The Chief Justice, Court Clerk, or Judge of a trial may issue Subpoenas, which are trial-related Court Orders compelling an individual to produce evidence or make themselves present at a location for court. A subpoena can order an individual to:<br /> <br /> * Appear as a witness, defendant, plaintiff, or prosecution;<br /> * Produce evidence for a trial;<br /> * Appear for questioning in deposition.<br /> <br /> A subpoena must include a list of names, a detailed description of evidence requested or reason for appearing, and a reasonable time frame no shorter than 3 minutes. The individuals summoned by the subpoena must be informed of its presence for it to be a valid order. This can be done via general announcement, fax, verbal announcement, or otherwise.<br /> <br /> === Affidavits ===<br /> An Affidavit is a legal document, consisting of a formal written statement of witness. An Affidavit must be written by the witness, or Affiant, who must state their relation to the incident at hand, and must be signed and stamped (if applicable) by a member of Security, Justice, or Command, who is verifying that the contents of the Affidavit are true to the best of their knowledge. The witness to the Affidavit must not be directly connected to the incident.<br /> <br /> Affidavits are considered valid witness statements for use in a trial (see Trial Procedure, below), and can be used either in tandem with a verbal witness statement, or to obtain testimony from an affiant whose job requirements and/or personal circumstances make attending a trial unfeasible.<br /> <br /> An affidavit may be impeached- and thus removed from evidence- if the Prosecution or Defense can introduce testimony or other evidence that directly contradicts the statements recorded within the Affidavit. The Affiant may then be liable for criminal charges.<br /> <br /> =Trial Procedure=<br /> A trial may be requested for civil disputes and capital charges. Civil charges may be refused, depending on the availability and discretion of a potential Judge; however, capital crimes require a trial. This also includes non-capital trials required as dictated within Sentencing guidelines. Miscellaneous trials, such as those described within Paroles and Pardons, only require the Judge and the defendant.<br /> <br /> Criminal trials may be waived if a suspect pleads guilty to a member of the Justice or Security department, or to station command. Their sentence should be passed by a Judge immediately, without the need for a full hearing. The Judge should also sentence the defendant summarily if they are held in contempt of court during the trial.<br /> <br /> The trial takes the form of an arbitration court hearing, presided over by an appointed Judge, and including adequate Prosecution and Defense, as dictated below. All charges, arguments, and evidence must be filed with the Judge before the case begins. The trial shall begin when the Defense, Prosecution, and Judge are all present and ready to begin. A trial does not need to be open to the public.<br /> <br /> The Judge is charged with ensuring the trial is completed in a timely manner, and is granted the power to charge someone with Contempt of Court, under Space Law, if they disrupt the case. Suitable Judges should be chosen from the following list, in sequential order:<br /> <br /> # The Chief Justice<br /> # The Clerk<br /> # An impartial member of the Justice department.<br /> # An impartial member of Station Command.<br /> # The Warden.<br /> <br /> The Defense should ideally be a member of the Justice department assigned to argue in favor of the defendant; if none are available, the defendant may choose to represent themselves.<br /> <br /> The Prosecution should ideally be the Prosecutor; if they are unavailable, the case should be prosecuted by an unbiased member of Station Command or a law enforcement officer, in that order.<br /> <br /> If there is not a viable and/or willing Defense or Prosecution, the Judge is fully authorized and strongly encouraged to pass a summary sentence of Extended Confinement until an adequate trial can be held.<br /> <br /> ==Criminal Trials==<br /> A criminal case should take no longer than 25 minutes in total. Criminal cases should either have security personnel present, or plan to have them present by the end of the trial.<br /> :#The judge brings the court in session.<br /> :#Prosecution opens the proceedings, stating the charges and introducing witnesses and exhibits that will be brought forward during the presentation of evidence. They may also recommend a sentence to the judge, appropriate to the charge based on their opening statement.<br /> :#Defense enters their plea- Guilty or Not Guilty.<br /> :#If Guilty, the Judge is authorized to immediately pass a ruling, as stated below.<br /> :#If Not Guilty, they are to provide their own opening statement and introduce their own witnesses and exhibits where applicable.<br /> :#Presentation of evidence follows, lead by Prosecution, then Defense.<br /> :#*Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> :#Finally, closing statements are made by the Prosecution, Defense, and Prosecution once more due to burden of proof. No new evidence can be introduced within a closing statement.<br /> :#A ruling will be issued by the Judge, written down, and stamped with the Notary stamp, the Judge's stamp, and their signature.<br /> :#The Judge adjourns the court. Any present or soon-to-be-present Security personnel will then enact the ruling.<br /> <br /> == Civil Trials ==<br /> Civil cases do not require Prosecution or Defense, but they may receive assistance from either both before and during the case. Both the defendant and plaintiff must be made to summon at the court, if a party does not appear out of either refusal or negligence, or fails to comply with a court order from a civil trial, that party may be charged with contempt of court, a felony. A civil case involves seeking damages from a defendant, which could be monetary, an item, or otherwise. A civil case should take no longer than 15 minutes in total.<br /> <br /> # The Judge brings the court into session.<br /> # Plaintiff opens proceedings by stating the damages, before introducing witnesses and exhibits that will be brought forward during presentation of evidence. They may also reccomend civil relief to the judge, appropriate to the damages listed wthin their opening statement.<br /> # Defendant follows with their opening statement, contradicting the Plaintiff's theories and assertions. They will also introduce their own witnesses and exhibits, where applicable.<br /> # Presentation of evidence follows, led by the Plaintiff, then the Defendant.<br /> #* Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> # Finally, closing statements are made by the Plaintiff, Defense, and Plaintiff once more due to burden of proof. No new evidence should be introduced or referenced by these statements.<br /> # A ruling will be made by the Judge, written, and stamped by the Notary stamp, the Judge's stamp, and signed by the Judge.<br /> # The Judge adjourns court.<br /> <br /> Any ruling shall then be enacted; if a party refuses to follow through with the ruling, they may suffer criminal penalties.<br /> <br /> == Presentation of Evidence ==<br /> <br /> ===Eyewitness Testimony===<br /> Any sophont or other entity willing and capable of presenting themselves before court under oath and present at the scene of the crime as a bystander or a victim at the time of its commission, may offer eyewitness testimony before the court at request of defense or prosecution. Extra time may be granted to either side at the behest of the Judge to allow for witnesses not currently present.<br /> <br /> ===Objection to Testimony===<br /> Any witness that falls under the following conditions may be excused as a witness or have their testimony deemed inadmissible:<br /> :*The witness lacks the mental, intellectual, or other capacity to understand the context of the case.<br /> :*The witness's inclusion will cause substantial cost or delay to the case, proceedings, or upkeep of the station.<br /> :*The witness is the judge.<br /> ===General Objections===<br /> Both parties in a trial may object to testimony to have the testimony deemed inadmissible, move past the question, or rephrase a question to keep a trial within time limit:<br /> :* '''Hearsay:''' The witness testifies using an out-of-court statement by an individual not present in court, thereby rendering it impossible to verify. This testimony will be inadmissible.<br /> :* '''Asked and answered:''' A question is posed that has already been answered previously by a witness. Such a question must be skipped.<br /> :* '''Narrative:''' A question is posed that would require a significantly long answer with multiple facts, or when the witness chooses to answer a question in this way. The question must be reworded, or the witness must be reminded to answer promptly and stay on topic.<br /> <br /> Objections are completely at the discretion of the judge, who does not always need to sustain an objection even if it is within these guidelines. It is up to the judge to decide if an objection is proper or necessary to keep the trial quick and fair.<br /> <br /> ==Procedural Defense==<br /> Whereas a defendant is placed on trial, they are granted the privilege to challenge the legitimacy of charges or claims brought against them by the legal process. Any of the following may be invoked:<br /> :*Issue Preclusion/Double Jeopardy Clause: accused persons may not be tried on the same charges following an acquittal or conviction, except in the case of acquittal and subsequent credible admission of guilt.<br /> :*Entrapment Clause: accused persons found to be induced or coerced by law enforcement into the commission of the crimes listed in the charges may be acquitted or have their sentence reduced.<br /> :*Exclusionary Clause: evidence collected and/or analyzed in violation of accused persons’ rights under law may be inadmissible in court.<br /> =Medical Regulations=<br /> ==Standard of Care==<br /> <br /> Upon agreeing to provide medical care, staff assume the following duties of care:<br /> <br /> * They must provide a reasonable level of skillful, quality care<br /> * They must not make critical errors resulting in major personal injury or death, at the risk of criminal and civil liability.<br /> * They must show diligence in providing treatment, both inside and outside of the medical department area during their shift.<br /> * They must provide privacy to patients in non-emergency situations.<br /> * If they have limited resources, they must allocate what resources are available to them via triage.<br /> * They must not provide treatment that would breach Space Law or violate ethical principles.<br /> * They must ensure that invasive procedures or surgeries, including implant removals or inspections, are performed by trained personnel and properly given authorization via a valid search warrant. The need for a warrant is removed during a Code Gamma or similar alert status.<br /> <br /> ==DNRs==<br /> Do Not Resuscitate (DNR) orders are commands issued to medical personnel to restrict the revival of a specified individual. DNRs are issued for the following reasons:<br /> <br /> * Lawful executions;<br /> * Suicide in the custody of law enforcement, verified by the Corpsman.<br /> * Patient refusal.<br /> <br /> DNRs that do not involve execution must be verified by the CMO before taking effect.<br /> <br /> ==Medical Evaluation==<br /> Given good medical reason and with documentation, the Chief Medical Officer of a vessel may declare any on-duty personnel unfit for duty and order them demoted from their position. This includes the Commanding Officer, who may not overrule this procedure.<br /> <br /> In order for a medical evaluation to be considered lawfully applicable, the CMO and relevant head of department must both agree that the specified crewmate is unfit for duty in order to proceed with the demotion. In the case of the Commanding Officer, Central Command should be contacted as soon as possible.<br /> <br /> ==Quarantine==<br /> Medical staff are afforded the right to quarantine individuals that currently suffer from infectious or contagious diseases, and may confine them within pre-designated quarantine areas in the course of treatment, until the point that they are no longer infectious or harmful to the rest of the crew.</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3991 2025-05-11T23:23:41Z

<p>Lyndomen: blue red warrant</p> <hr /> <div>== &lt;span style=&quot;color:#4f8439;&gt;Green Alert&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Blue Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searching individuals suspected of committing a crime is encouraged. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked.<br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Red Alert&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Protection of personnel prioritized over body and department searches. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Violet Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Yellow Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == White Alert ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Epistemics Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel. Psionic insulation recommended for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel, unless affected by a known threat. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; ROE on mindbreaking is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Delta Alert&lt;/span&gt; ==<br /> Emergency alert status. ''The nuclear destruction mechanism has been engaged and station destruction is imminent. All crew aboard the station must attempt to reverse the self-destruct mechanism, if engaged in error. Should reversal prove impossible, evacuate as applicable.<br /> ''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Emergency personnel must expend all efforts to prevent station destruction if engaged in error. Security and Command personnel are to oversee the evacuation of personnel and safe scuttling of the station. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas and HSAs should remain locked.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=File:2077_map.png&diff=3931 2025-05-08T17:49:40Z

<p>Lyndomen: </p> <hr /> <div>aaaaaaa</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Anchor&diff=3928 2025-05-07T18:54:33Z

<p>Lyndomen: Protected &quot;Template:Anchor&quot; ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))</p> <hr /> <div>{{#if:{{{1|}}}|&lt;span id=&quot;{{{1|}}}&quot;&gt;&lt;/span&gt;}}&lt;noinclude&gt;<br /> == How to use ==<br /> &lt;pre&gt;<br /> &lt;nowiki&gt;{{Anchor|Bread}}&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> The anchor template works for making internal links to specific parts of pages. For example, linking to [[Syndicate Items#EMAG]] (Assuming you already have an anchor on the syndicate items page to direct the link) will load the page focused on the EMAG. This is useful when you don't have a header for the item in the page or it's part of a table.<br /> <br /> Important note though; If the page already has a header with the same name as an anchor, a link to anchored item will go to whichever is first. so if the anchor is higher than the header, it will go to the anchor and vice versa. Alternatively, you can just make the anchor have a slightly different name to fix this.<br /> <br /> [[Category:Templates]]<br /> &lt;/noinclude&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Metashield&diff=3911 2025-05-06T14:14:15Z

<p>Lyndomen: </p> <hr /> <div>This page will discuss a list of various information or items protected by our rules. Something that is &quot;shielded&quot; cannot be known by your character during around until the &quot;breaking&quot; condition happens. This also means your character cannot act upon shielded information. Doing so before the shield is broken is referred to as metagaming. <br /> <br /> Anytime a shield is broken, it applies for the remainder of the round, in all other instances, unless explicitly specified otherwise. If a breaking condition says that it is &quot;never revealed IC&quot;, your character can never act as if they know about the shielded topic.<br /> <br /> {| class=&quot;wikitable&quot;<br /> !'''Shield'''<br /> !'''Breaking Condition'''<br /> |-<br /> |Current gamemode, and any antagonists that could exist as a result<br /> |never revealed IC<br /> |-<br /> |Events experienced as a different character.<br /> |never revealed IC<br /> |-<br /> |Any and all information related to the player of a character, or certain strategies a player may use as an antagonist.<br /> |never revealed IC<br /> |-<br /> |Any information revealed while your character is unconscious, dead, or a ghost. <br /> |never revealed IC.<br /> |-<br /> |Any information your character knew before death, if you become a ghost role mid-round.<br /> |never revealed IC<br /> |-<br /> |The exact cause of your death. Being in critical condition does not count for the purposes of this shield.<br /> |never revealed IC<br /> |-<br /> |Events from prior rounds.<br /> |Events can be discussed, but they should not hold any bearing on the current round.<br /> |-<br /> |The understanding of station functions, and how they may be sabotaged by entities lacking crew-level intellect. <br /> This includes damaging or destroying critical infrastructure solely to gain a meta-tactical advantage. <br /> |ANY of the following: <br /> <br /> * Being a Mouse Operative, Syndicat, or Ancestor Reinforcement.<br /> * Being uplifted by the power of [[Chemistry#Cognizine|Cognizine]].<br /> * Being an Awakened creature. <br /> |-<br /> |The idea that certain [[High-Risk Items]] are desired specifically by the Syndicate, and are therefore likely targets of theft by Syndicate agents or other bad actors. <br /> |ANY of the following: <br /> <br /> * Being a [[Traitor]]. <br /> * Being told of an item's status by a Traitor. '''This only applies to that particular item.'''<br /> <br /> Crew should protect [[High-Risk Items]] due to their status as valuable items, not due to their status as objectives. <br /> |-<br /> |The existence of Nuclear Operatives, beyond ludicrous propaganda that nobody would act on. <br /> This includes their goal of utter station destruction via a nuclear bomb.<br /> |ANY of the following:<br /> <br /> * Discovering a Blood-Red Hardsuit, or any variants.<br /> * Discovering a Nuclear Operatives Shuttle (Either variant)<br /> * Seeing an Operative's name appear in chat, or a communications console announcement from an Operative.<br /> * Being a [[Nuclear Operative]].<br /> |-<br /> |The existence of implants used by the Syndicate. <br /> Implant checks cannot be performed unless there is adequate evidence or an authorized warrant, as outlined within Standard Operating Procedures.<br /> |ANY of the following: <br /> <br /> * Discovering a non-NT implanter, identifiable by the black-and-red color scheme of the implanter itself.<br /> * Discovering a non-NT implant box.<br /> * DIscovering or witnessing use of a non-NT implant.<br /> * Experiencing a situation where absolutely no other explanation is possible.<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> |-<br /> |The existence of &quot;chameleon&quot; items, pieces of clothing or technology that can change their appearance. <br /> Even while this shield is active, the suspicion of items that may be fake or stolen is '''not shielded'''. <br /> |ANY of the following:<br /> <br /> * Seeing any chameleon item change its appearance.<br /> * Finding holographic nanomachine fibers.<br /> * Experiencing a situation where absolutely no explanation is possible.<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> Testing clothing for chameleon status is always prohibited; items that are clearly chameleon can, however, be confiscated by Security. <br /> |-<br /> |The existence of items that have uses or functionality other than what their external appearance or examinable information would claim. <br /> |ANY of the following:<br /> <br /> * Seeing the item behave differently than the expected behavior for the item<br /> * Seeing the item used for its hidden purpose<br /> * Experiencing a situation where absolutely no other explanation is possible<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> <br /> Stealth items should not be &quot;tested&quot; for their functionality, but items that are clearly producing some sort of stealth effect can be confiscated. <br /> |-<br /> |The idea that Syndicate agents, or other bad actors, have certain goals they have been tasked with accomplishing on the station, ranging from sabotage, to theft, to murder.<br /> |ANY of the following:<br /> <br /> * Being a [[Traitor]], [[Space Ninja]], [[Space Dragon]], or [[Paradox Anomaly]]. <br /> * Being told of an antagonist's goals. '''This only applies to the goals that have been revealed to you.'''<br /> |-<br /> |The fact that Syndicate agents may possess a program, referred to as an Uplink, used to receive equipment from the Syndicate. <br /> These Uplinks are typically contained within PDAs, and may be &quot;locked&quot;, preventing access and visibility. '''You have no way of confirming an Uplink exists within a PDA unless you see it yourself.'''<br /> |ANY of the following:<br /> <br /> * Being a Security role.<br /> * Being a Command role.<br /> * Being a Traitor.<br /> |-<br /> |The idea that the Nuclear Authorization Disk must be protected at all costs, and that it can be used to destroy the station by bad actors.<br /> |always revealed IC<br /> |-<br /> |The fact that the Syndicate is hostile to NanoTrasen, and will occasionally deploy covert agents to spy on, sabotage, and assault NanoTrasen assets and associates. <br /> |always revealed IC<br /> |-<br /> |The fact that rounds are supposed to come to an end. For example, acting upon the knowledge that a crew transfer shuttle is typically sent around the two hour mark of a shift. <br /> |always revealed IC<br /> |-<br /> |The fact that Cultists are hostile to NanoTrasen, and exist in some capacity. <br /> |ANY of the following:<br /> <br /> * Being a Captain.<br /> * Being a Mystagogue, Psionic Mantis, or Chaplain<br /> * Being a Cosmic Cultist<br /> |-<br /> |The presence of Malign Rifts, Λ-CDM Anomalies, or manifestations of energy in crewmember eyes could possibly indicate a Cult's presence aboard the station. <br /> |ANY of the following:<br /> <br /> * Being a Captain.<br /> * Being a Mystagogue, Psionic Mantis, or Chaplain<br /> * Being a Cosmic Cultist<br /> |-<br /> |The presence of Malign Rifts, Λ-CDM Anomalies, or manifestations of energy in crewmember eyes is strange, and should be reported to Epistemics.<br /> |always revealed IC<br /> |}<br /> <br /> == Metafriending and Metagrudging ==<br /> This section clarifies a concept protected by a variety of metashields that should never be revealed IC. Giving a person or their character preferential treatment based on something 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. Not only are both protected by the metashields, both are not allowed under our rules.<br /> <br /> {| class=&quot;mw-collapsible mw-collapsed&quot;<br /> | &lt;strong&gt;Examples of Metafriending&lt;/strong&gt;<br /> |-<br /> | These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. It does not matter if you are friends with the player OOC, or your characters are friends IC; the rules apply in a similar fashion.<br /> # Giving a character additional access or a job.<br /> # Trusting a character with sensitive information or equipment.<br /> # Not fighting a character when your job or circumstances would dictate you should..<br /> # Ignoring your objective to kill a character.<br /> |}<br /> <br /> {| class=&quot;mw-collapsible mw-collapsed&quot;<br /> | &lt;strong&gt;Examples of Metagrudging&lt;/strong&gt;<br /> |-<br /> | These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. It does not matter if you dislike a player OOC or their character IC; your actions should be based on the events of the round. <br /> # Denying a character additional access, refusing their job transfer, or even attempting to get them fired.<br /> # Not trusting a character.<br /> # Starting a fight with a character solely due to events of a prior round, or because they killed you when you were playing a different character that round.<br /> # Targeting or harassing a character based on anything which that character did outside of the current round.<br /> # Targeting or harassing a character based on anything which the character's player did while not playing the character.<br /> |}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Metashield&diff=3910 2025-05-05T23:03:16Z

<p>Lyndomen: </p> <hr /> <div>This page will discuss a list of various information or items protected by our rules. Something that is &quot;shielded&quot; cannot be known by your character during around until the &quot;breaking&quot; condition happens. This also means your character cannot act upon shielded information. Doing so before the shield is broken is referred to as metagaming. <br /> <br /> Anytime a shield is broken, it applies for the remainder of the round, in all other instances, unless explicitly specified otherwise. If a breaking condition says that it is &quot;never revealed IC&quot;, your character can never act as if they know about the shielded topic.<br /> <br /> {| class=&quot;wikitable&quot;<br /> !'''Shield'''<br /> !'''Breaking Condition'''<br /> |-<br /> |Current gamemode, and any antagonists that could exist as a result<br /> |never revealed IC<br /> |-<br /> |Events experienced as a different character.<br /> |never revealed IC<br /> |-<br /> |Any and all information related to the player of a character, or certain strategies a player may use as an antagonist.<br /> |never revealed IC<br /> |-<br /> |Any information revealed while your character is unconscious, dead, or a ghost. <br /> |never revealed IC.<br /> |-<br /> |Any information your character knew before death, if you become a ghost role mid-round.<br /> |never revealed IC<br /> |-<br /> |The exact cause of your death. Being in critical condition does not count for the purposes of this shield.<br /> |never revealed IC<br /> |-<br /> |Events from prior rounds.<br /> |Events can be discussed, but they should not hold any bearing on the current round.<br /> |-<br /> |The understanding of station functions, and how they may be sabotaged by entities lacking crew-level intellect. <br /> This includes damaging or destroying critical infrastructure solely to gain a meta-tactical advantage. <br /> |ANY of the following: <br /> <br /> * Being a Mouse Operative, Syndicat, or Ancestor Reinforcement.<br /> * Being uplifted by the power of [[Chemistry#Cognizine|Cognizine]].<br /> * Being an Awakened creature. <br /> |-<br /> |The idea that certain [[High-Risk Items]] are desired specifically by the Syndicate, and are therefore likely targets of theft by Syndicate agents or other bad actors. <br /> |ANY of the following: <br /> <br /> * Being a [[Traitor]]. <br /> * Being told of an item's status by a Traitor. '''This only applies to that particular item.'''<br /> <br /> Crew should protect [[High-Risk Items]] due to their status as valuable items, not due to their status as objectives. <br /> |-<br /> |The existence of Nuclear Operatives, beyond ludicrous propaganda that nobody would act on. <br /> This includes their goal of utter station destruction via a nuclear bomb.<br /> |ANY of the following:<br /> <br /> * Discovering a Blood-Red Hardsuit, or any variants.<br /> * Discovering a Nuclear Operatives Shuttle (Either variant)<br /> * Seeing an Operative's name appear in chat, or a communications console announcement from an Operative.<br /> * Being a [[Nuclear Operative]].<br /> |-<br /> |The existence of implants used by the Syndicate. <br /> Implant checks cannot be performed unless there is adequate evidence or an authorized warrant, as outlined within Standard Operating Procedures.<br /> |ANY of the following: <br /> <br /> * Discovering a non-NT implanter, identifiable by the black-and-red color scheme of the implanter itself.<br /> * Discovering a non-NT implant box.<br /> * DIscovering or witnessing use of a non-NT implant.<br /> * Experiencing a situation where absolutely no other explanation is possible.<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> |-<br /> |The existence of &quot;chameleon&quot; items, pieces of clothing or technology that can change their appearance. <br /> Even while this shield is active, the suspicion of items that may be fake or stolen is '''not shielded'''. <br /> |ANY of the following:<br /> <br /> * Seeing any chameleon item change its appearance.<br /> * Finding holographic nanomachine fibers.<br /> * Experiencing a situation where absolutely no explanation is possible.<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> Testing clothing for chameleon status is always prohibited; items that are clearly chameleon can, however, be confiscated by Security. <br /> |-<br /> |The existence of items that have uses or functionality other than what their external appearance or examinable information would claim. <br /> |ANY of the following:<br /> <br /> * Seeing the item behave differently than the expected behavior for the item<br /> * Seeing the item used for its hidden purpose<br /> * Experiencing a situation where absolutely no other explanation is possible<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> <br /> Stealth items should not be &quot;tested&quot; for their functionality, but items that are clearly producing some sort of stealth effect can be confiscated. <br /> |-<br /> |The idea that Syndicate agents, or other bad actors, have certain goals they have been tasked with accomplishing on the station, ranging from sabotage, to theft, to murder.<br /> |ANY of the following:<br /> <br /> * Being a [[Traitor]], [[Space Ninja]], [[Space Dragon]], or [[Paradox Anomaly]]. <br /> * Being told of an antagonist's goals. '''This only applies to the goals that have been revealed to you.'''<br /> |-<br /> |The fact that Syndicate agents may possess a program, referred to as an Uplink, used to receive equipment from the Syndicate. <br /> These Uplinks are typically contained within PDAs, and may be &quot;locked&quot;, preventing access and visibility. '''You have no way of confirming an Uplink exists within a PDA unless you see it yourself.'''<br /> |ANY of the following:<br /> <br /> * Being a Security role.<br /> * Being a Command role.<br /> * Being a Traitor.<br /> |-<br /> |The idea that the Nuclear Authorization Disk must be protected at all costs, and that it can be used to destroy the station by bad actors.<br /> |always revealed IC<br /> |-<br /> |The fact that the Syndicate is hostile to NanoTrasen, and will occasionally deploy covert agents to spy on, sabotage, and assault NanoTrasen assets and associates. <br /> |always revealed IC<br /> |-<br /> |The fact that rounds are supposed to come to an end. For example, acting upon the knowledge that a crew transfer shuttle is typically sent around the two hour mark of a shift. <br /> |always revealed IC<br /> |-<br /> |The fact that Cultists are hostile to NanoTrasen, and exist in some capacity. <br /> |Revealed to Captain, Mystagogue, Psionic Mantis, Chaplain, Cosmic Cultists OR a representative of this list has informed your character of their threat.<br /> |-<br /> |The presence of Malign Rifts, A-CDM Anomalies, or manifestations of energy in crewmember eyes could possibly indicate a Cult's presence aboard the station. <br /> |Revealed to Captain, Mystagogue, Psionic Mantis, Chaplain, and Cosmic Cultists<br /> |}<br /> <br /> == Metafriending and Metagrudging ==<br /> This section clarifies a concept protected by a variety of metashields that should never be revealed IC. Giving a person or their character preferential treatment based on something 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. Not only are both protected by the metashields, both are not allowed under our rules.<br /> <br /> {| class=&quot;mw-collapsible mw-collapsed&quot;<br /> | &lt;strong&gt;Examples of Metafriending&lt;/strong&gt;<br /> |-<br /> | These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. It does not matter if you are friends with the player OOC, or your characters are friends IC; the rules apply in a similar fashion.<br /> # Giving a character additional access or a job.<br /> # Trusting a character with sensitive information or equipment.<br /> # Not fighting a character when your job or circumstances would dictate you should..<br /> # Ignoring your objective to kill a character.<br /> |}<br /> <br /> {| class=&quot;mw-collapsible mw-collapsed&quot;<br /> | &lt;strong&gt;Examples of Metagrudging&lt;/strong&gt;<br /> |-<br /> | These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. It does not matter if you dislike a player OOC or their character IC; your actions should be based on the events of the round. <br /> # Denying a character additional access, refusing their job transfer, or even attempting to get them fired.<br /> # Not trusting a character.<br /> # Starting a fight with a character solely due to events of a prior round, or because they killed you when you were playing a different character that round.<br /> # Targeting or harassing a character based on anything which that character did outside of the current round.<br /> # Targeting or harassing a character based on anything which the character's player did while not playing the character.<br /> |}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Metashield&diff=3909 2025-05-05T22:58:41Z

<p>Lyndomen: cosmic cult</p> <hr /> <div>This page will discuss a list of various information or items protected by our rules. Something that is &quot;shielded&quot; cannot be known by your character during around until the &quot;breaking&quot; condition happens. This also means your character cannot act upon shielded information. Doing so before the shield is broken is referred to as metagaming. <br /> <br /> Anytime a shield is broken, it applies for the remainder of the round, in all other instances, unless explicitly specified otherwise. If a breaking condition says that it is &quot;never revealed IC&quot;, your character can never act as if they know about the shielded topic.<br /> <br /> {| class=&quot;wikitable&quot;<br /> !'''Shield'''<br /> !'''Breaking Condition'''<br /> |-<br /> |Current gamemode, and any antagonists that could exist as a result<br /> |never revealed IC<br /> |-<br /> |Events experienced as a different character.<br /> |never revealed IC<br /> |-<br /> |Any and all information related to the player of a character, or certain strategies a player may use as an antagonist.<br /> |never revealed IC<br /> |-<br /> |Any information revealed while your character is unconscious, dead, or a ghost. <br /> |never revealed IC.<br /> |-<br /> |Any information your character knew before death, if you become a ghost role mid-round.<br /> |never revealed IC<br /> |-<br /> |The exact cause of your death. Being in critical condition does not count for the purposes of this shield.<br /> |never revealed IC<br /> |-<br /> |Events from prior rounds.<br /> |Events can be discussed, but they should not hold any bearing on the current round.<br /> |-<br /> |The understanding of station functions, and how they may be sabotaged by entities lacking crew-level intellect. <br /> This includes damaging or destroying critical infrastructure solely to gain a meta-tactical advantage. <br /> |ANY of the following: <br /> <br /> * Being a Mouse Operative, Syndicat, or Ancestor Reinforcement.<br /> * Being uplifted by the power of [[Chemistry#Cognizine|Cognizine]].<br /> * Being an Awakened creature. <br /> |-<br /> |The idea that certain [[High-Risk Items]] are desired specifically by the Syndicate, and are therefore likely targets of theft by Syndicate agents or other bad actors. <br /> |ANY of the following: <br /> <br /> * Being a [[Traitor]]. <br /> * Being told of an item's status by a Traitor. '''This only applies to that particular item.'''<br /> <br /> Crew should protect [[High-Risk Items]] due to their status as valuable items, not due to their status as objectives. <br /> |-<br /> |The existence of Nuclear Operatives, beyond ludicrous propaganda that nobody would act on. <br /> This includes their goal of utter station destruction via a nuclear bomb.<br /> |ANY of the following:<br /> <br /> * Discovering a Blood-Red Hardsuit, or any variants.<br /> * Discovering a Nuclear Operatives Shuttle (Either variant)<br /> * Seeing an Operative's name appear in chat, or a communications console announcement from an Operative.<br /> * Being a [[Nuclear Operative]].<br /> |-<br /> |The existence of implants used by the Syndicate. <br /> Implant checks cannot be performed unless there is adequate evidence or an authorized warrant, as outlined within Standard Operating Procedures.<br /> |ANY of the following: <br /> <br /> * Discovering a non-NT implanter, identifiable by the black-and-red color scheme of the implanter itself.<br /> * Discovering a non-NT implant box.<br /> * DIscovering or witnessing use of a non-NT implant.<br /> * Experiencing a situation where absolutely no other explanation is possible.<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> |-<br /> |The existence of &quot;chameleon&quot; items, pieces of clothing or technology that can change their appearance. <br /> Even while this shield is active, the suspicion of items that may be fake or stolen is '''not shielded'''. <br /> |ANY of the following:<br /> <br /> * Seeing any chameleon item change its appearance.<br /> * Finding holographic nanomachine fibers.<br /> * Experiencing a situation where absolutely no explanation is possible.<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> Testing clothing for chameleon status is always prohibited; items that are clearly chameleon can, however, be confiscated by Security. <br /> |-<br /> |The existence of items that have uses or functionality other than what their external appearance or examinable information would claim. <br /> |ANY of the following:<br /> <br /> * Seeing the item behave differently than the expected behavior for the item<br /> * Seeing the item used for its hidden purpose<br /> * Experiencing a situation where absolutely no other explanation is possible<br /> * Discovering an unlocked [[Traitor Uplink|Uplink]].<br /> <br /> Stealth items should not be &quot;tested&quot; for their functionality, but items that are clearly producing some sort of stealth effect can be confiscated. <br /> |-<br /> |The idea that Syndicate agents, or other bad actors, have certain goals they have been tasked with accomplishing on the station, ranging from sabotage, to theft, to murder.<br /> |ANY of the following:<br /> <br /> * Being a [[Traitor]], [[Space Ninja]], [[Space Dragon]], or [[Paradox Anomaly]]. <br /> * Being told of an antagonist's goals. '''This only applies to the goals that have been revealed to you.'''<br /> |-<br /> |The fact that Syndicate agents may possess a program, referred to as an Uplink, used to receive equipment from the Syndicate. <br /> These Uplinks are typically contained within PDAs, and may be &quot;locked&quot;, preventing access and visibility. '''You have no way of confirming an Uplink exists within a PDA unless you see it yourself.'''<br /> |ANY of the following:<br /> <br /> * Being a Security role.<br /> * Being a Command role.<br /> * Being a Traitor.<br /> |-<br /> |The idea that the Nuclear Authorization Disk must be protected at all costs, and that it can be used to destroy the station by bad actors.<br /> |always revealed IC<br /> |-<br /> |The fact that the Syndicate is hostile to NanoTrasen, and will occasionally deploy covert agents to spy on, sabotage, and assault NanoTrasen assets and associates. <br /> |always revealed IC<br /> |-<br /> |The fact that rounds are supposed to come to an end. For example, acting upon the knowledge that a crew transfer shuttle is typically sent around the two hour mark of a shift. <br /> |always revealed IC<br /> |-<br /> |The fact that Cultists are hostile to NanoTrasen, and exist in some capacity. <br /> |Revealed to Captain, Mystagogue, Psionic Mantis, Chaplain OR<br /> ANY of the following:<br /> * Being a Cultist<br /> * The Captain, Mystagogue, Psionic Mantis, Chaplain, or a representative of this list has informed your character of their threat.<br /> |-<br /> |The presence of Malign Rifts, A-CDM Anomalies, or manifestations of energy in crewmember eyes could possibly indicate a Cult's presence aboard the station. <br /> |Revealed to Captain, Mystagogue, Psionic Mantis, Chaplain<br /> |}<br /> <br /> == Metafriending and Metagrudging ==<br /> This section clarifies a concept protected by a variety of metashields that should never be revealed IC. Giving a person or their character preferential treatment based on something 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. Not only are both protected by the metashields, both are not allowed under our rules.<br /> <br /> {| class=&quot;mw-collapsible mw-collapsed&quot;<br /> | &lt;strong&gt;Examples of Metafriending&lt;/strong&gt;<br /> |-<br /> | These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. It does not matter if you are friends with the player OOC, or your characters are friends IC; the rules apply in a similar fashion.<br /> # Giving a character additional access or a job.<br /> # Trusting a character with sensitive information or equipment.<br /> # Not fighting a character when your job or circumstances would dictate you should..<br /> # Ignoring your objective to kill a character.<br /> |}<br /> <br /> {| class=&quot;mw-collapsible mw-collapsed&quot;<br /> | &lt;strong&gt;Examples of Metagrudging&lt;/strong&gt;<br /> |-<br /> | These are all examples of things that are prohibited by at least one metashield item that is never revealed IC. It does not matter if you dislike a player OOC or their character IC; your actions should be based on the events of the round. <br /> # Denying a character additional access, refusing their job transfer, or even attempting to get them fired.<br /> # Not trusting a character.<br /> # Starting a fight with a character solely due to events of a prior round, or because they killed you when you were playing a different character that round.<br /> # Targeting or harassing a character based on anything which that character did outside of the current round.<br /> # Targeting or harassing a character based on anything which the character's player did while not playing the character.<br /> |}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Space_Law&diff=3902 2025-04-22T18:28:20Z

<p>Lyndomen: https://github.com/DeltaV-Station/Delta-v/pull/3552/files</p> <hr /> <div><br /> Space Law is a broad set of rules and regulations, collected and regulated by TerraGov, enacted and enforced by NanoTrasen and its [[Security Officer|Station Security]], with the oversight of [[Administrators#What_Do_Admins_Do?|CentCom]] - and, on occasion, TerraGov's Galactic Police Force. Space Law applies to all ranks and positions on stations under its jurisdiction, from the lowliest [[Passenger]] to the highest [[Captain]]; all are equal under the eyes of the Law, and all must ultimately answer to it.<br /> <br /> It is highly recommended to read the '''[[Standard Operating Procedure|Standard Operating Procedures]]'''. Summaries of several pertinent sections are listed below.<br /> <br /> * '''[[Standard Operating Procedure#Controlled Items|Controlled Items]]:''' If a member of station crew requires access to a Controlled Item for use in their job, or for regular function, they must obtain the signed and stamped approval of a relevant member of Station Command or the CO. The latter is able to override the decisions of Station Command in this regard, however.<br /> * '''[[Standard Operating Procedure#Sophonts and Synthetics|Sophonts &amp; Synthetics]]:''' Sophonts are entities are able to utilize a structured language, communicate through the use of written, verbal, and/or body language (or by other means), and possess reasoning and introspection. Sophonts are legal persons, able to press charges under Space Law, and can be victims of certain crimes that specify sophont status. An entity's status as a sophont may be challenged during legal proceedings; the Defense and/or Prosecution must present evidence arguing that it meets, or does not meet, the criteria established above. The Judge will then arbitrate on the entity's status. Any synthetic, sillicon, or nonorganic entity with non-sophont status is to be considered a Synthetic. Synthetics are the property of the entity that constructs or employs them, unless otherwise stated. Damage or destruction of such Synthetics is considered vandalism of the entity's property.<br /> * '''[[Standard Operating Procedure#Security Jurisdiction|Security Jurisdiction]]:''' Station law enforcement officers are bound by Space Law; they cannot operate outside of standard accessible areas, or perform searches, unless such action is allowed by either Alert Procedure or a valid warrant.<br /> * '''[[Standard Operating Procedure#Detainment and Arrest|Detainment &amp; Arrest]]:''' Members of law enforcement may detain sophonts under '''[[Standard Operating Procedure#Probable Cause|Probable Cause]]''' of criminal activity. These detainees must be informed of the crime they are suspected of committing, and may be moved to a secure location and/or restrained while law enforcement determine if a crime was committed. Such detention should last no longer than five minutes. Any sophont may be arrested, during which they are restrained, informed of their charges, and taken to the brig for search and processing under '''[[Standard Operating Procedure#Brig Procedure|Brig Procedure]]'''.<br /> * '''[[Standard Operating Procedure#Sentencing|Sentencing]]:''' Any member of law enforcement is allowed to pass sentence on Misdemeanor, Felony, and Grand Felony charges. The Prosecutor is allowed to adjust such sentences, within reason.<br /> * '''[[Standard Operating Procedure#Treatment of Prisoners|Treatment of Prisoners]]:''' Prisoners must be provided with food, water, clothing, free movement within the brig, adequate medical care, access to the Common and Prison radio channels, and moral, spiritual, or legal counseling if requested and available. If the brig becomes uninhabitable, prisoners must be securely and safely relocated to another area until the brig is functional once more. Prisoners sentenced to Extended Confinement have additional rights and firmer restrictions that must be upheld by law enforcement officials.<br /> * '''[[Standard Operating Procedure#Paroles and Pardons|Paroles &amp; Pardons]]:''' Parole may be offered under the discretion of the Warden, Head of Security, or CO. A parole hearing requires only a Judge, as discussed within Trial Procedure. Pardons may be issued by the arresting officer, the Judge of a trial, by the Warden (to those within the permanent brig), or by the CO, when deemed in the best interest of the crew or vessel, or when the circumstances of the crime warrant suspension of sentence.<br /> * '''[[Standard Operating Procedure#Pressing Charges|Pressing Charges]]:''' Any sophont may press charges against any other sophont. Individuals may only be charged with a crime if it can be proveny beyond reasonable doubt that they have committed the crime.<br /> * '''[[Standard Operating Procedure#Trial Procedure|Trial Procedure]]:''' A criminal trial’s Judge must be, in sequential order: The Chief Justice, the Court Clerk, an impartial member of Justice or Station Command, or the Warden. The Prosecution should ideally be the Prosecutor, or an available member of Station Command or Station Security in that order. The Defense should ideally be a member of the Justice department assigned to the defendant, though they are allowed to represent themselves if they wish. If insufficient crew are available, the Judge is fully authorized and strongly encouraged to pass a sentence of Extended Confinement until a proper trial can be held.<br /> * '''[[Alert Procedure]]:''' Codes Blue, Red, Gamma, and Delta suspend the right to individual privacy, allowing warrantless search. The latter three codes allow for departmental raids, and the latter two place the station in martial law. These codes also authorize Security to carry progressively more advanced firearms, and loosen '''[[Standard Operating Procedure#Rules of Engagement|Rules of Engagement]]''' regarding their use.<br /> <br /> === Crime Codes Quick Reference ===<br /> Use this to quickly find the Crime Code Numbers.<br /> <br /> Crime codes are organized into four Category Codes (_XX) as listed below, with the most severe crimes being given the highest Severity Codes (x__). The sentencing officer or Judge should use discretion, and not charge an entity with two similar crimes for a singular offense.<br /> <br /> For example, an attack upon a sophont which causes them to die of their injuries is Murder, not Assault AND Murder. Likewise, an entity should not be charged for both Possession AND Grand Possession on a singular Controlled Item held without proper authorization.<br /> <br /> {| style='text-align:center; border:solid 1px black' cellspacing=0<br /> ! style=&quot;border: 1px solid black; width:5%&quot; | Code<br /> ! style='background-color:#999933BF; border: 1px solid black; width:23.75%' | 1XX - Misdemeanor<br /> ! style='background-color:#996633BF; border: 1px solid black; width:23.75%' | 2XX - Felony<br /> ! style='background-color:#993333BF; border: 1px solid black; width:23.75%' | 3XX- Grand Felony<br /> ! style=&quot;background-color:#990033BF; border: 1px solid black; width:23.75%&quot; | 4XX - Capital<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 01<br /> |style='background:#9999334D; border: 1px solid black;' | Animal Cruelty<br /> |style='background:#9966334D; border: 1px solid black;' | Assault<br /> |style='background:#9933334D; border: 1px solid black;' | Manslaughter<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; | Murder<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 02<br /> |style='background:#9999334D; border: 1px solid black;' | Harassment<br /> |style='background:#9966334D; border: 1px solid black;' | Breaking and Entering<br /> |style='background:#9933334D; border: 1px solid black;'| Kidnapping<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; | Terrorism<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 03<br /> |style='background:#9999334D; border: 1px solid black;' | Vigilantism<br /> |style='background:#9966334D; border: 1px solid black;' | Rioting<br /> |style='background:#9933334D; border: 1px solid black;' | Grand Possession<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; | Grand Sabotage<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 04<br /> |style='background:#9999334D; border: 1px solid black;' | Petty Larceny<br /> |style='background:#9966334D; border: 1px solid black;' | Endangerment<br /> |style='background:#9933334D; border: 1px solid black' | Mindbreaking<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; | Prevention of Revival<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 05<br /> |style='background:#9999334D; border: 1px solid black;' | Trespass<br /> |style='background:#9966334D; border: 1px solid black;' | Possession<br /> |style='background:#9933334D; border: 1px solid black;' | Sabotage<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; | Sedition<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 06<br /> |style='background:#9999334D; border: 1px solid black;' | Vandalism<br /> |style='background:#9966334D; border: 1px solid black;' | Obstruction of Justice<br /> |style='background:#9933334D; border: 1px solid black;' | Abuse of Power<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; | Breach of Custody<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 07<br /> |style='background:#9999334D; border: 1px solid black;' | Hooliganism<br /> |style='background:#9966334D; border: 1px solid black;' | Perjury<br /> |style='background:#9933334D; border: 1px solid black;' | Grand Larceny<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; |<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 08<br /> |style='background:#9999334D; border: 1px solid black;' |<br /> |style='background:#9966334D; border: 1px solid black;' | Contempt of Court<br /> |style='background:#9933334D; border: 1px solid black;' | Black Marketeering<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; |<br /> |-<br /> !style=&quot;border: 1px solid black;&quot; | 09<br /> |style='background:#9999334D; border: 1px solid black;' |<br /> |style='background:#9966334D; border: 1px solid black;' | Identity Theft<br /> |style=&quot;background:#9933334D; border: 1px solid black;&quot; |<br /> | style=&quot;background:#9900334D; border: 1px solid black;&quot; |<br /> |}<br /> <br /> == Sentences ==<br /> === Capital ===<br /> Capital Sentences are organized in order of severity, with the least severe last. Execution should be utilized as an '''absolute last resort,''' for criminals whose crimes are extraordinarily cruel, or who prove impossible to confine through less restrictive means.<br /> <br /> * '''Execution:''' Termination of the convict's life.<br /> ** Whenever any execution is performed, for any reason, a general announcement must be made stating who was executed, and for what reason.<br /> ** The convict may either face execution by firing squad, by lethal electrocution, by being ejected from the station via an airlock (being &quot;spaced&quot;), or by a method of their choosing, at the Judge's sole discretion.<br /> ** If recoverable, their remains must either be cremated, processed via the biomass reclaimer, or stored in the morgue.<br /> * '''Decorporealization:''' Stripping the convict's mind from their body into a more restrictive form, such as a cyborg or soul gem.<br /> * '''Preservative Stasis:''' Relocation of the convict into a morgue or similar controlled and regulated environment until one's sentence is concluded, or until the legal system can accomodate the convict.<br /> * '''Exfiltration:''' Immediate retrieval of the convict via a CentComm or GALPOL prison transport.<br /> ** The prisoner may be held within the permanent brig until the transport arrives.<br /> ** If transport cannot be arranged, default to other capital sentences.<br /> * '''Extended Confinement:''' Placing the convict into the Permanent Brig until the end of the shift, where they are to be transported to Central Command for processing.<br /> ** The convict has the same rights as any other prisoner within the Permanent Brig, whether they arrived by transport or were sentenced to Extended Confinement.<br /> :&lt;!-- --&gt;<br /> <br /> === Standard ===<br /> :*'''Brigging''': Placing the convict into a temporary holding cell.<br /> &lt;!-- --&gt;<br /> :*'''Catch &amp; Release''': Taking the convict to Security, processing them, searching them, and then releasing them.<br /> &lt;!-- --&gt;<br /> :*'''Demotion''': Downgrading the convict’s employment contract and revoking their access accordingly, with permission from or when ordered by the convict’s head of department. May be applied when the convict has committed a crime relating to their employment within their department or with NanoTrasen as a whole.<br /> &lt;!-- --&gt;<br /> :*'''Licence restriction''': Downgrading or suspending the convict’s armament licence and confiscating possessions accordingly. May be applied when the convict is guilty of possession or a crime involving a weapon they were lawfully permitted to carry.<br /> &lt;!-- --&gt;<br /> :*'''Mindbreaking''': Removal of the convict’s psionic power by use of mindbreaker toxin or any other means. May be applied when the convict is guilty of a crime in which they use psionics.<br /> <br /> == Crime Modifiers ==<br /> Sentencing modifiers are to be applied by the sentencing officer, judge, or arbiter. Aggravating modifiers may not extend a sentence beyond the specified limit, while extenuating modifiers may not reduce a sentence below the specified limit.<br /> <br /> === Aggravating ===<br /> :*'''Solicitation'''<br /> :**Any sophont found guilty of encouraging, bribing, requesting, or instructing someone to commit a crime, with the intent that the sophont being solicited commit the crime, will receive for the crimes they solicited in full.<br /> :*'''Accessory'''<br /> :**Any sophont found guilty of assisting in the commission of a crime, without participating in the crime itself, knowing that a crime will be, has been, or is being committed, will receive the sentence for the crimes in which they took part in full.<br /> :*'''Attempts'''<br /> :**Any sophont found guilty of attempting to commit a crime, with the intent to carry out that crime, will receive the sentence for the crimes they attempted in full.<br /> :*'''Conspiracy'''<br /> :**Any sophont found guilty of planning to commit a crime, with the intent to carry out that crime eventually, and having committed an overt act pursuant to that end, will receive the sentence for the crimes they conspired towards in full.<br /> :*'''Deadly weapon'''<br /> :**Any sophont found guilty of committing a crime, utilising any object used offensively for the purpose of inflicting mortal or great bodily harm, will receive an additional modifier of, at most, +50% of the original sentence.<br /> :*'''Aggravation'''<br /> :**Any sophont found guilty of committing a crime with reckless abandon, evident signs of lack of regret or remorse, or blatant disregard for potential collateral damage, will receive an additional modifier of, at most, +50% of the original sentence.<br /> :*'''Recidivism'''<br /> :**Any sophont convicted of the same criminal charge multiple times within one shift will receive an additional modifier of, at most, +100% of the original sentence. '''OOC NOTE: If a character is sexually harassing another character, or being bigoted, in a way that breaks Server Rules A1 or A2, you are allowed to summarily execute them. Please contact admins via AHelp if such an incident occurs.'''<br /> <br /> === Extenuating ===<br /> :*'''Cooperation'''<br /> :**Any sophont who shares actionable intelligence with the authorities, turns oneself in, testifies against accomplices, confesses to their crime, or otherwise aids the prosecution, may have their sentence reduced to no less than 50% of the original sentence.<br /> :*'''Dire Emergency'''<br /> :**Any sophont found to have committed a crime in the process of absolutely necessary and reasonable actions, taken with the intent to resolve or mitigate the effects of a dire emergency on one’s vessel or habitat, may have their sentence reduced by any amount, or completely waived.<br /> :*'''Self-Defence'''<br /> :**Any sophont found to have committed a crime or crimes in protection of oneself or another, and only to the necessary extent to avert a direct and imminent threat to the health and life of innocent persons, may have their sentence reduced by any amount, or completely waived.<br /> :*'''Good Behavior'''<br /> :**Any convict who peacefully complies with the authorities, displays clear signs of remorse concerning the committed crime, and/or conducts themselves peacefully while imprisoned, may be paroled as outlined in the Standard Operating Procedures.<br /> <br /> == Crimes ==<br /> === Capital Crimes ===<br /> <br /> {| style=&quot;text-align:center; background-color:#9900334D; width: 95%; border: 1px solid black;&quot; cellspacing=0<br /> ! style=&quot;background-color:#990033BF; width:4%; border: 1px solid black;&quot; |Code<br /> ! style=&quot;background-color:#990033BF; width:0.1%; border: 1px solid black;&quot; |<br /> ! style=&quot;background-color:#990033BF; width:20%; border: 1px solid black;&quot; |Name<br /> ! style=&quot;background-color:#990033BF; width:12.5%; border: 1px solid black;&quot; |Time<br /> ! style=&quot;background-color:#990033BF; width:62.5%; border: 1px solid black;&quot; |Description<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 401<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Murder.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | Murder<br /> | style=&quot;border: 1px solid black;&quot; | Capital<br /> | style=&quot;border: 1px solid black;&quot; | To maliciously commit an act resulting in the death of a sophont, with reckless indifference to their life.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 402<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Terrorism.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | '''Terrorism'''<br /> | style=&quot;border: 1px solid black;&quot; | Capital<br /> | style=&quot;border: 1px solid black;&quot; | To maliciously commit an act or take hostages with reckless indifference to life in order to provoke a state of terror in, intimidate, or otherwise compel an entity to act or abstain from acting.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 403<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_GrandSabotage.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | Grand Sabotage<br /> | style=&quot;border: 1px solid black;&quot; | Capital<br /> | style=&quot;border: 1px solid black;&quot; | To maliciously commit an act that, directly or indirectly, renders a vessel or its part uninhabitable or inoperable; or, to commit an act that causes irreversible damage to High Security Areas and/or systems of a vessel.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 404<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Decorporealisation.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | '''Prevention of Revival'''<br /> | style=&quot;border: 1px solid black;&quot; | Capital<br /> | style=&quot;border: 1px solid black;&quot; | To commit an act that prevents the revival of a sophont by standard medical care following their death.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 405<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Sedition.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | Sedition<br /> | style=&quot;border: 1px solid black;&quot; | Capital<br /> | style=&quot;border: 1px solid black;&quot; | To act to overthrow a lawfully established Chain of Command or governing body without lawful or legitimate cause.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 406<br /> | style=&quot;border: 1px solid black;&quot; | WIP<br /> ! style=&quot;border: 1px solid black;&quot; | Breach of Custody<br /> | style=&quot;border: 1px solid black;&quot; | Capital<br /> | style=&quot;border: 1px solid black;&quot; | To escape the custody of law enforcement while serving a legal sentence, or awaiting trial for a capital offense.<br /> |}<br /> ----<br /> <br /> === Grand Felonies ===<br /> {| style=&quot;text-align:center; background-color:#9933334D; width: 95%; border: 1px solid black;&quot; cellspacing=0<br /> ! style=&quot;background-color:#993333BF; width:4%; border: 1px solid black;&quot; | Code<br /> ! style=&quot;background-color:#993333BF; width:0.1%; border: 1px solid black;&quot; |<br /> ! style=&quot;background-color:#993333BF; width:20%; border: 1px solid black;&quot; | Name<br /> ! style=&quot;background-color:#993333BF; width:12.5%; border: 1px solid black;&quot; | Time<br /> ! style=&quot;background-color:#993333BF; width:62.5%; border: 1px solid black;&quot; | Description<br /> |-<br /> |style=&quot;border:1px solid black;&quot; | 301<br /> |style= &quot;border:1px solid black;&quot;| [[File:SL_Manslaughter.png]]<br /> |style= &quot;border:1px solid black;&quot;| Manslaughter<br /> |style= &quot;border:1px solid black;&quot;| 16 minutes<br /> |style= &quot;border:1px solid black;&quot;| To act without malice in a manner which, directly or indirectly, leads to the death of a sophont.<br /> |-<br /> |style= &quot;border:1px solid black;&quot;| 302<br /> |style= &quot;border:1px solid black;&quot;| [[File:SL_Kidnapping.png]]<br /> |style= &quot;border:1px solid black;&quot;| Kidnapping<br /> |style= &quot;border:1px solid black;&quot;| 16 minutes<br /> |style= &quot;border:1px solid black;&quot;| To unlawfully confine or restrict the free movement of an entity against its will.<br /> |-<br /> | style=&quot;border:1px solid black;&quot; | 303<br /> | style=&quot;border:1px solid black;&quot; | WIP<br /> | style=&quot;border:1px solid black;&quot; | Grand Possession<br /> | style=&quot;border:1px solid black;&quot; | 15-25 minutes<br /> | style=&quot;border:1px solid black;&quot; | To be in the possession of a Category C, D, or E Controlled Armament.<br /> |-<br /> | style=&quot;border:1px solid black;&quot; | 304<br /> | style=&quot;border:1px solid black;&quot; | [[File:SL_Mindbreaking.png]]<br /> | style=&quot;border:1px solid black;&quot; | Mindbreaking<br /> | style=&quot;border:1px solid black;&quot; | 14 minutes<br /> | style=&quot;border:1px solid black;&quot; | To unlawfully and maliciously rid a psionic of their powers<br /> |-<br /> | style=&quot;border:1px solid black;&quot; | 305<br /> | style=&quot;border:1px solid black;&quot; | [[File:SL_Sabotage.png]]<br /> | style=&quot;border:1px solid black;&quot; | Sabotage<br /> | style=&quot;border:1px solid black;&quot; | 14 minutes<br /> | style=&quot;border:1px solid black;&quot; | To maliciously commit an act that, directly or indirectly, hinders the operation of a vessel of its part; or, to commit an act that modifies and/or damages technology or equipment one is not authorized to access.<br /> |-<br /> | style=&quot;border:1px solid black;&quot; | 306<br /> | style=&quot;border:1px solid black;&quot; | [[File:SL_AbuseOfPower.png]]<br /> | style=&quot;border:1px solid black;&quot; | Abuse of Power<br /> | style=&quot;border:1px solid black;&quot; | 14 minutes<br /> | style=&quot;border:1px solid black;&quot; | To intentionally misuse or wrongfully exercise one’s own authority, influence, or control, resulting in harm, unjust treatment, or demonstratable loss to another entity.<br /> |-<br /> | style=&quot;border:1px solid black;&quot; | 307<br /> | style=&quot;border:1px solid black;&quot; | [[File:SL_GrandTheft.png]]<br /> | style=&quot;border:1px solid black;&quot; | Grand Larceny<br /> | style=&quot;border:1px solid black;&quot; | 12 minutes<br /> | style=&quot;border:1px solid black;&quot; | To deprive an entity of any Controlled Item in their lawful possession.<br /> |-<br /> | style=&quot;border:1px solid black;&quot; | 308<br /> | style=&quot;border:1px solid black;&quot; | [[File:SL_BlackMarketeering.png]]<br /> | style=&quot;border:1px solid black;&quot; | Black Marketeering<br /> | style=&quot;border:1px solid black;&quot; | 12 minutes<br /> | style=&quot;border:1px solid black;&quot; | To sell, distribute, or otherwise circulate Controlled Items to unauthorized entities.<br /> |}<br /> ----<br /> <br /> === Felonies ===<br /> {| style=&quot;text-align:center; background-color:#9966334D; width: 95%; border: 1px solid black;&quot; cellspacing=&quot;0&quot;<br /> ! style=&quot;background-color:#996633BF; width:4%; border: 1px solid black;&quot; |Code<br /> ! style=&quot;background-color:#996633BF; width:0.1%; border: 1px solid black;&quot; |<br /> ! style=&quot;background-color:#996633BF; width:20%; border: 1px solid black;&quot; |Name<br /> ! style=&quot;background-color:#996633BF; width:12.5%; border: 1px solid black;&quot; |Time<br /> ! style=&quot;background-color:#996633BF; width:62.5%; border: 1px solid black;&quot; |Description<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 201<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Assault.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Assault}}Assault<br /> | style=&quot;border: 1px solid black;&quot; | 10 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To cause physical harm or to effect unwanted physical contact on a sophont, without the apparent intent to kill them, or to threaten such actions with both capability and intent to do so.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 202<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_BreakingAndEntering.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Breaking and Entering}}Breaking and Entering<br /> | style=&quot;border: 1px solid black;&quot; | 10 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To break and enter into a high security area where one is not authorised nor invited, with intent to commit a crime within.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 203<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Rioting.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Rioting}}Rioting<br /> | style=&quot;border: 1px solid black;&quot; | 8 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To partake in an unauthorised riotous, tumultuous, and disruptive public assembly that refuses to disperse after warning.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 204<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Endangerment.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Endangerment}}Endangerment<br /> | style=&quot;border: 1px solid black;&quot; | 8 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To recklessly abandon obligations involving the continued wellbeing and/or protection of life and property, through malpractice, action, or inaction.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 205<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Possession.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Possession}}Possession<br /> | style=&quot;border: 1px solid black;&quot; | 5-10 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To be in unauthorised possession of restricted items or items of particular danger. See [[Standard_Operating_Procedure#Controlled_Substances/Items|Controlled Substances/Items]], [[Standard_Operating_Procedure#Controlled_Armaments|Controlled Armaments]].<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 206<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_ObstructionOfJustice.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Obstruction of Justice}}Obstruction of Justice<br /> | style=&quot;border: 1px solid black;&quot; | 8 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To wilfully disobey, interfere with, or refuse a decree of the court, warrant, or arrest.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 207<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_PerjuryOrFalseReport.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Perjury or False Report}}Perjury or False Report<br /> | style=&quot;border: 1px solid black;&quot; | 6 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To wilfully and maliciously tell an untruth either in court or in the process of making an actionable report to law enforcement.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 208<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_ContemptOfCourt.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Contempt of Court}}Contempt of Court<br /> | style=&quot;border: 1px solid black;&quot; | 6 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To conduct oneself disruptively and disrespectfully before the court.<br /> |-<br /> |style= &quot;border:1px solid black;&quot;| 209<br /> |style= &quot;border:1px solid black;&quot;| WIP<br /> !style= &quot;border:1px solid black;&quot;| Identity Theft<br /> |style= &quot;border:1px solid black;&quot;| 5 minutes<br /> |style= &quot;border:1px solid black;&quot;| To maliciously assume the identity of an entity, such as through writing, attire, and/or speech.<br /> |}<br /> <br /> <br /> ----<br /> <br /> === Misdemeanors ===<br /> <br /> {| style=&quot;text-align:center; background-color:#9999334D; width: 95%; border: 1px solid black;&quot; cellspacing=0<br /> ! style=&quot;background-color:#999933BF; width:4%; border: 1px solid black;&quot; |Code<br /> ! style=&quot;background-color:#999933BF; width:0.1%; border: 1px solid black;&quot; |<br /> ! style=&quot;background-color:#999933BF; width:20%; border: 1px solid black;&quot; |Name<br /> ! style=&quot;background-color:#999933BF; width:12.5%; border: 1px solid black;&quot; |Time<br /> ! style=&quot;background-color:#999933BF; width:62.5%; border: 1px solid black;&quot; |Description<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 101<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_AnimalCruelty.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Animal Cruelty}}Animal Cruelty<br /> | style=&quot;border: 1px solid black;&quot; | 5 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To inflict unnecessary suffering on a sapient being with malicious intent.<br /> |-<br /> |style= &quot;border:1px solid black;&quot;| 102<br /> |style= &quot;border:1px solid black;&quot;| WIP<br /> !style= &quot;border:1px solid black;&quot;| Harassment<br /> |style= &quot;border:1px solid black;&quot;| 5 minutes<br /> |style= &quot;border:1px solid black;&quot;| To verbally demean, humiliate, or harass an entity with malice; or maliciously spread false information amongst a population.<br /> |-<br /> |style= &quot;border:1px solid black;&quot;| 103<br /> |style= &quot;border:1px solid black;&quot;| WIP<br /> !style= &quot;border:1px solid black;&quot;| Vigilantism<br /> |style= &quot;border:1px solid black;&quot;| 4 minutes<br /> |style= &quot;border:1px solid black;&quot;| To perform the responsibility and duty of a law enforcement official without approval or due cause to act.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 104<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Theft.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Theft}}Petty Larceny<br /> | style=&quot;border: 1px solid black;&quot; | 4 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To deprive an entity of an item in their lawful property without consent.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 105<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Trespass.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Trespass}}Trespass<br /> | style=&quot;border: 1px solid black;&quot; | 3 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To enter into an area where one is not authorised nor invited.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 106<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Vandalism.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Vandalism}}Vandalism<br /> | style=&quot;border: 1px solid black;&quot; | 3 minutes<br /> | style=&quot;border: 1px solid black;&quot; | To deface or superficially damage public property, or property belonging to another person.<br /> |-<br /> | style=&quot;border: 1px solid black;&quot; | 107<br /> | style=&quot;border: 1px solid black;&quot; | [[File:SL_Hooliganism.png]]<br /> ! style=&quot;border: 1px solid black;&quot; | {{anchor|Hooliganism}}Hooliganism<br /> | style=&quot;border: 1px solid black;&quot; | As necessary<br /> | style=&quot;border: 1px solid black;&quot; | To intentionally and maliciously engage in disruptive conduct, where one refuses to cease.<br /> |}<br /> <br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Main_Page_Quicklinks&diff=3891 2025-03-24T02:00:10Z

<p>Lyndomen: </p> <hr /> <div>&lt;td colspan=&quot;3&quot; style=&quot;padding:0px; width:100%; min-width:560px; margin-bottom:10px;&quot;&gt;&lt;div style=&quot;border:solid #000000 1px; background-color:#1b2942C2;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;&quot;&gt;Quick links&lt;/div&gt;<br /> <br /> &lt;table style=&quot;width:100%; text-align:center; font: 18px Calibri, sans-serif;&quot;&gt;<br /> &lt;tr&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Passenger.png|64px|link=Getting Started]]&lt;/td&gt;&lt;/table&gt;[[Getting Started]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookTrialLaw.png|64px|link=https://wiki.deltav.gay/view/Server_Rules]]&lt;/td&gt;&lt;/table&gt;[https://wiki.deltav.gay/view/Server_Rules Rules]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookEngineering.png|64px|link=Guides]]&lt;/td&gt;&lt;/table&gt;[[Guides]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BlankID.png|64px|link=Jobs]]&lt;/td&gt;&lt;/table&gt;[[Jobs]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:GPS.gif|64px|link=Maps]]&lt;/td&gt;&lt;/table&gt;[[Maps]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Traitor.png|64px|link=Game Modes]]&lt;/td&gt;&lt;/table&gt;[[Game Modes]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Mop.png|64px|link=Interactions]]&lt;/td&gt;&lt;/table&gt;[[Interactions]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]&lt;/td&gt;&lt;/table&gt;[https://replays.delta-v.org/ Replays]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]&lt;/td&gt;&lt;/table&gt;[https://docs.spacestation14.com/ Development]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;/tr&gt;<br /> &lt;/table&gt;&lt;/div&gt;<br /> &lt;/td&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Main_Page_Quicklinks&diff=3890 2025-03-24T01:57:30Z

<p>Lyndomen: Reverted edits by Lyndomen (talk) to last revision by Adeinitas</p> <hr /> <div>&lt;td colspan=&quot;3&quot; style=&quot;padding:0px; width:100%; min-width:560px; margin-bottom:10px;&quot;&gt;&lt;div style=&quot;border:solid #000000 1px; background-color:#1b2942C2;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;&quot;&gt;Quick links&lt;/div&gt;<br /> <br /> &lt;table style=&quot;width:100%; text-align:center; font: 18px Calibri, sans-serif;&quot;&gt;<br /> &lt;tr&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Passenger.png|64px|link=Getting Started]]&lt;/td&gt;&lt;/table&gt;[[Getting Started]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookTrialLaw.png|64px|link=https://wiki.delta-v.org/view/Server_Rules]]&lt;/td&gt;&lt;/table&gt;[https://wiki.delta-v.org/view/Server_Rules Rules]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookEngineering.png|64px|link=Guides]]&lt;/td&gt;&lt;/table&gt;[[Guides]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BlankID.png|64px|link=Jobs]]&lt;/td&gt;&lt;/table&gt;[[Jobs]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:GPS.gif|64px|link=Maps]]&lt;/td&gt;&lt;/table&gt;[[Maps]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Traitor.png|64px|link=Game Modes]]&lt;/td&gt;&lt;/table&gt;[[Game Modes]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Mop.png|64px|link=Interactions]]&lt;/td&gt;&lt;/table&gt;[[Interactions]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]&lt;/td&gt;&lt;/table&gt;[https://replays.delta-v.org/ Replays]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]&lt;/td&gt;&lt;/table&gt;[https://docs.spacestation14.com/ Development]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;/tr&gt;<br /> &lt;/table&gt;&lt;/div&gt;<br /> &lt;/td&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Main_Page_Quicklinks&diff=3889 2025-03-24T01:55:20Z

<p>Lyndomen: </p> <hr /> <div>&lt;td colspan=&quot;3&quot; style=&quot;padding:0px; width:100%; min-width:560px; margin-bottom:10px;&quot;&gt;&lt;div style=&quot;border:solid #000000 1px; background-color:#1b2942C2;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;&quot;&gt;Quick links&lt;/div&gt;<br /> <br /> &lt;table style=&quot;width:100%; text-align:center; font: 18px Calibri, sans-serif;&quot;&gt;<br /> &lt;tr&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Passenger.png|64px|link=Getting Started]]&lt;/td&gt;&lt;/table&gt;[[Getting Started]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookTrialLaw.png|64px|link=Server Rules]]&lt;/td&gt;&lt;/table&gt;[[https://wiki.deltav.gay/view/Server_Rules]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookEngineering.png|64px|link=Guides]]&lt;/td&gt;&lt;/table&gt;[[Guides]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BlankID.png|64px|link=Jobs]]&lt;/td&gt;&lt;/table&gt;[[Jobs]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:GPS.gif|64px|link=Maps]]&lt;/td&gt;&lt;/table&gt;[[Maps]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Traitor.png|64px|link=Game Modes]]&lt;/td&gt;&lt;/table&gt;[[Game Modes]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Mop.png|64px|link=Interactions]]&lt;/td&gt;&lt;/table&gt;[[Interactions]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]&lt;/td&gt;&lt;/table&gt;[https://replays.delta-v.org/ Replays]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]&lt;/td&gt;&lt;/table&gt;[https://docs.spacestation14.com/ Development]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;/tr&gt;<br /> &lt;/table&gt;&lt;/div&gt;<br /> &lt;/td&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Main_Page_Quicklinks&diff=3888 2025-03-24T01:54:37Z

<p>Lyndomen: </p> <hr /> <div>&lt;td colspan=&quot;3&quot; style=&quot;padding:0px; width:100%; min-width:560px; margin-bottom:10px;&quot;&gt;&lt;div style=&quot;border:solid #000000 1px; background-color:#1b2942C2;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;&quot;&gt;Quick links&lt;/div&gt;<br /> <br /> &lt;table style=&quot;width:100%; text-align:center; font: 18px Calibri, sans-serif;&quot;&gt;<br /> &lt;tr&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Passenger.png|64px|link=Getting Started]]&lt;/td&gt;&lt;/table&gt;[[Getting Started]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookTrialLaw.png|64px|link=Server Rules]]&lt;/td&gt;&lt;/table&gt;[https://wiki.deltav.gay/view/Server_Rules]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookEngineering.png|64px|link=Guides]]&lt;/td&gt;&lt;/table&gt;[[Guides]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BlankID.png|64px|link=Jobs]]&lt;/td&gt;&lt;/table&gt;[[Jobs]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:GPS.gif|64px|link=Maps]]&lt;/td&gt;&lt;/table&gt;[[Maps]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Traitor.png|64px|link=Game Modes]]&lt;/td&gt;&lt;/table&gt;[[Game Modes]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Mop.png|64px|link=Interactions]]&lt;/td&gt;&lt;/table&gt;[[Interactions]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]&lt;/td&gt;&lt;/table&gt;[https://replays.delta-v.org/ Replays]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]&lt;/td&gt;&lt;/table&gt;[https://docs.spacestation14.com/ Development]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;/tr&gt;<br /> &lt;/table&gt;&lt;/div&gt;<br /> &lt;/td&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Main_Page_Quicklinks&diff=3887 2025-03-24T01:53:40Z

<p>Lyndomen: </p> <hr /> <div>&lt;td colspan=&quot;3&quot; style=&quot;padding:0px; width:100%; min-width:560px; margin-bottom:10px;&quot;&gt;&lt;div style=&quot;border:solid #000000 1px; background-color:#1b2942C2;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;&quot;&gt;Quick links&lt;/div&gt;<br /> <br /> &lt;table style=&quot;width:100%; text-align:center; font: 18px Calibri, sans-serif;&quot;&gt;<br /> &lt;tr&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Passenger.png|64px|link=Getting Started]]&lt;/td&gt;&lt;/table&gt;[[Getting Started]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookTrialLaw.png|64px|link=https://wiki.deltav.gay/view/Server_Rules]]&lt;/td&gt;&lt;/table&gt;[https://wiki.deltav.gay/view/Server_Rules]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookEngineering.png|64px|link=Guides]]&lt;/td&gt;&lt;/table&gt;[[Guides]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BlankID.png|64px|link=Jobs]]&lt;/td&gt;&lt;/table&gt;[[Jobs]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:GPS.gif|64px|link=Maps]]&lt;/td&gt;&lt;/table&gt;[[Maps]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Traitor.png|64px|link=Game Modes]]&lt;/td&gt;&lt;/table&gt;[[Game Modes]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Mop.png|64px|link=Interactions]]&lt;/td&gt;&lt;/table&gt;[[Interactions]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]&lt;/td&gt;&lt;/table&gt;[https://replays.delta-v.org/ Replays]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]&lt;/td&gt;&lt;/table&gt;[https://docs.spacestation14.com/ Development]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;/tr&gt;<br /> &lt;/table&gt;&lt;/div&gt;<br /> &lt;/td&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Template:Main_Page_Quicklinks&diff=3886 2025-03-24T01:52:33Z

<p>Lyndomen: </p> <hr /> <div>&lt;td colspan=&quot;3&quot; style=&quot;padding:0px; width:100%; min-width:560px; margin-bottom:10px;&quot;&gt;&lt;div style=&quot;border:solid #000000 1px; background-color:#1b2942C2;&quot;&gt;<br /> <br /> &lt;div style=&quot;background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;&quot;&gt;Quick links&lt;/div&gt;<br /> <br /> &lt;table style=&quot;width:100%; text-align:center; font: 18px Calibri, sans-serif;&quot;&gt;<br /> &lt;tr&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Passenger.png|64px|link=Getting Started]]&lt;/td&gt;&lt;/table&gt;[[Getting Started]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookTrialLaw.png|64px|link=https://wiki.deltav.gay/view/Server_Rules]]&lt;/td&gt;&lt;/table&gt;[https://wiki.delta-v.org/view/Server_Rules Rules]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BookEngineering.png|64px|link=Guides]]&lt;/td&gt;&lt;/table&gt;[[Guides]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:BlankID.png|64px|link=Jobs]]&lt;/td&gt;&lt;/table&gt;[[Jobs]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:GPS.gif|64px|link=Maps]]&lt;/td&gt;&lt;/table&gt;[[Maps]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Traitor.png|64px|link=Game Modes]]&lt;/td&gt;&lt;/table&gt;[[Game Modes]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Mop.png|64px|link=Interactions]]&lt;/td&gt;&lt;/table&gt;[[Interactions]]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]&lt;/td&gt;&lt;/table&gt;[https://replays.delta-v.org/ Replays]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;td style=&quot;width:11.1%;&quot;&gt;&lt;div style=&quot;padding: 10px 0 10px 0;&quot;&gt;&lt;table align=center&gt;&lt;td style=&quot;padding:0px;&quot;&gt;<br /> [[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]&lt;/td&gt;&lt;/table&gt;[https://docs.spacestation14.com/ Development]<br /> &lt;/div&gt;&lt;/td&gt;<br /> <br /> &lt;/tr&gt;<br /> &lt;/table&gt;&lt;/div&gt;<br /> &lt;/td&gt;</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Content_Owner&diff=3878 2025-03-18T01:22:09Z

<p>Lyndomen: /* Categorical Roadmap Subjects */</p> <hr /> <div>Hi! Here is a page where we can list out who is nominally the first person to reach out to in order to propose changes to Delta V content. <br /> <br /> == IC Documentation ==<br /> * '''Space Law''' - LadyDanger, ChamomileTeaTime<br /> * '''Standard Operating Procedure''' - LadyDanger, ChamomileTeaTime<br /> * '''Company Policy''' - LadyDanger, ChamomileTeaTime<br /> <br /> == Categorical Roadmap Subjects ==<br /> * '''Art Direction''' - Kazne<br /> <br /> * '''Antagonism''' - Lyndomen, Gates<br /> <br /> * '''Central Command''' - Cepelinas<br /> <br /> * '''Lore''' - Gargoyle<br /> <br /> * '''Engineering''' - Sif<br /> <br /> * '''Epistemics''' - Gates<br /> <br /> * '''ERT''' - Cepelinas<br /> <br /> * '''Justice''' - Skunks&amp;, Janet<br /> <br /> * '''Logistics''' - Sif, Lyndomen<br /> <br /> * '''Medical''' - Skunks&amp;, Janet<br /> <br /> * '''Perma''' - Kat, Lyndomen<br /> <br /> * '''Psionics''' - Lyndomen<br /> <br /> * '''Security''' - No Owner<br /> <br /> * '''Service''' - No Owner<br /> <br /> * '''Silicon''' - Sol</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Content_Owner&diff=3877 2025-03-18T01:21:43Z

<p>Lyndomen: /* Categorical Roadmap Subjects */</p> <hr /> <div>Hi! Here is a page where we can list out who is nominally the first person to reach out to in order to propose changes to Delta V content. <br /> <br /> == IC Documentation ==<br /> * Space Law - LadyDanger, ChamomileTeaTime<br /> * Standard Operating Procedure - LadyDanger, ChamomileTeaTime<br /> * Company Policy - LadyDanger, ChamomileTeaTime<br /> <br /> == Categorical Roadmap Subjects ==<br /> * Art Direction - Kazne<br /> <br /> * Antagonism - Lyndomen, Gates<br /> <br /> * Central Command - Cepelinas<br /> <br /> * Lore - Gargoyle<br /> <br /> * Engineering - Sif<br /> <br /> * Epistemics - Gates<br /> <br /> * ERT - Cepelinas<br /> <br /> * Justice - Skunks&amp;, Janet<br /> <br /> * Logistics - Sif, Lyndomen<br /> <br /> * Medical - Skunks&amp;, Janet<br /> <br /> * Perma - Kat, Lyndomen<br /> <br /> * Psionics - Lyndomen<br /> <br /> * Security - No Owner<br /> <br /> * Service - No Owner<br /> <br /> * Silicon - Sol</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Content_Owner&diff=3876 2025-03-18T01:18:35Z

<p>Lyndomen: Created page with &quot;Hi! Here is a page where we can list out who is nominally the first person to reach out to in order to propose changes to Delta V content. == IC Documentation == * Space Law * Standard Operating Procedure * Company Policy == Categorical Roadmap Subjects == * Art Direction Sole Owner - Kazne * Antagonism Joint Owned between Lyndomen and Gates * Central Command Sole Owner - Cepelinas * Lore Sole Owner - Gargoyle * Engineering Sole Owner - Sif * Epistemics Sole Owner - G...&quot;</p> <hr /> <div>Hi! Here is a page where we can list out who is nominally the first person to reach out to in order to propose changes to Delta V content. <br /> <br /> == IC Documentation ==<br /> * Space Law<br /> * Standard Operating Procedure<br /> * Company Policy<br /> <br /> == Categorical Roadmap Subjects ==<br /> * Art Direction<br /> Sole Owner - Kazne<br /> * Antagonism<br /> Joint Owned between Lyndomen and Gates<br /> * Central Command<br /> Sole Owner - Cepelinas<br /> * Lore<br /> Sole Owner - Gargoyle<br /> * Engineering<br /> Sole Owner - Sif<br /> * Epistemics<br /> Sole Owner - Gates<br /> * ERT<br /> Sole Owner - Cepelinas<br /> * Justice<br /> Joint Owned between Skunks&amp; and Janet<br /> * Logistics<br /> Joint Owned between Lyndomen and Sif<br /> * Medical<br /> Joint Owned between Skunks&amp; and Janet<br /> * Perma<br /> Sole Owner - Kat<br /> * Psionics<br /> Sole Owner - Lyndomen<br /> * Security<br /> No Owner<br /> * Service<br /> No Owner<br /> * Silicon<br /> Sole Owner - Sol</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3843 2025-03-03T01:07:54Z

<p>Lyndomen: /* The Roadmap */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === Design Documents ===<br /> Design Documents are a tool for Curators and Contributors alike. Design documents are a standardized method of outlining and presenting ideas. It is recommended to use the provided [[Design Document Template]] for the sake of consistency. Document templates and the relevant channels can be found in the Discord development category. <br /> <br /> Contributors can create Design Documents prior to opening a PR, and have them reviewed by Direction in order to tune their ideas to Direction standards before starting the development process. Contributors are also welcome to create Design Documents for review without the intention to develop them personally. Other contributors can always claim approved documents and begin development themselves!<br /> <br /> Curators can collaboratively create Design Documents to address issues laid out in the roadmap. These documents serve as the “Solution Design” step of the roadmap, and will be available to contributors who wish to develop them. <br /> <br /> Curators may designate design documents with varying levels of priority according to how pressing Direction finds the issue. <br /> <br /> === Content Review ===<br /> Reviewing suggested content involves examining current Pull Requests (“PRs”) or Design Documents and providing feedback. Content review should always involve as many members of Direction as possible, but if only one or two choose to review a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, content can always be reverted.<br /> <br /> '''All content must pass the full review process before being approved''', with a few small exceptions. Proposed changes for the following do not require a Direction review:<br /> <br /> * Bug fixes<br /> * Simple tweaks<br /> * Obvious small changes<br /> When in doubt, the Direction team should be asked if a review is needed.<br /> <br /> ==== '''What do you look for in a review?''' ====<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> <br /> ==== How is a review conducted? ====<br /> Content review takes place in the #content-review forum channel in the server Discord. The curator who creates a #content-review post assumes responsibility for providing feedback to the author. '''This includes notifying the author that the content is under review, and summarizing feedback gathered in the post to provide next steps to the author.''' <br /> <br /> If a curator is the author of the content, '''they should find another curator to assume responsibility for review of the content'''. &lt;u&gt;Curators should not argue in favor of their own suggested content in posts&lt;/u&gt;, in order to ensure it stands on its own merit. Content collaboratively designed by Direction is exempt from this restriction.<br /> <br /> '''&lt;u&gt;Content review is not a vote&lt;/u&gt;'''. Polls are not to be used for anything except timing purposes. Members of Direction are encouraged to give specific feedback on why they support proposed content or what they think should be changed about it, with justification. It is the review post author’s responsibility to summarize this concisely for the content author. <br /> <br /> After Direction has discussed the merits of proposed content internally, any final decisions must be communicated to the content author through appropriate channels. This will vary depending on whether the content is a Design Document or a PR.<br /> <br /> '''Design Document''' review takes place entirely within the Discord. Feedback will be provided to the author through the Discord. Typical decisions include:<br /> <br /> * Approving the document<br /> * Approving with an elevated priority tag<br /> * Requesting changes<br /> * Denying the Document<br /> <br /> For '''Pull Requests''', feedback should be communicated to the author through Github. Typical decisions include:<br /> <br /> * Merging the PR<br /> * Test merging the PR<br /> * Requesting changes<br /> * Closing (Denying) the PR<br /> <br /> '''&lt;u&gt;Note:&lt;/u&gt;''' Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. <br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for Content Review. Deadlines should be relative to the size of the content. The standard method of tracking a deadline is to create a poll of the appropriate time frame in the review post.<br /> <br /> * Small changes should be subject to 1-2 days of consideration.<br /> * Major changes may need as many as 1-2 weeks to reach an actionable conclusion.<br /> * The minimum amount of time for a review is 24 hours.<br /> Curators should notify content authors when their content is under official review, and give them an estimated wait time for feedback. If more review time is required, the author should be notified before the previously stated review period ends.<br /> <br /> Deadlines should be established relative to whenever the content is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> If, after sufficient requests for input, Direction '''consistently''' fails to provide feedback on a PR, &lt;u&gt;the final decision to approve or deny can be made by the Head Maintaine&lt;/u&gt;r. Direction may request the content be reverted later if need be. <br /> <br /> === Content Removal ===<br /> Some currently implemented content will inevitably have to be replaced or removed in order to achieve Direction’s design vision. Direction’s preference should be to replace content that doesn’t meet our standards with improved content where possible. <br /> <br /> In order to remove content, Direction must complete each of these steps:<br /> <br /> * Make a list of quantified issues with the content.<br /> * Create a design document that addresses these issues. If Direction cannot do this, it should be stated on the issue page. <br /> * Present the issues and design solutions to the community in the Github.<br /> * Establish a deadline for action to be taken.<br /> <br /> If no action has been taken by the deadline, the content will be removed. Appropriate deadlines are as follows. Content examples are not comprehensive.<br /> <br /> * 1 week: Minor content (sprites, mechanical balance of an item, etc.).<br /> * 2 weeks: Moderate content (roles, machines, etc.).<br /> * 1 month: Major content (gamemodes, etc.).<br /> <br /> Content that is extremely broken or clearly and severely detrimental to the game experience may be removed without this process. Content may be removed upon the original creators request without navigating these processes.<br /> <br /> === Test Merging ===<br /> Tmerges may be conducted on PRs whose effects are potentially unclear. A test merge consists of merging content that may be pending changes, or reversion. The purpose of the merge is to gather feedback from an in-game scenario in order to make such decisions. Test merges may be conducted on a test server if appropriate.<br /> <br /> Players should be made aware of all active test merges on their current server.<br /> <br /> Curators are authorized to manipulate rounds in accordance with Event Management policies in order to test said content. <br /> <br /> Test merges must be monitored, or otherwise have an official way of collecting community feedback (such as a feedback forum). If there are specific aspects of the content that Direction is looking for feedback on, this should be made known to the community before the test. Otherwise, a test may be used to discover previously unknown issues with the content, but '''Direction should take care to ensure content is in the best state possible before conducting a test merge'''.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or a Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc.<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> These events that generally do not interfere with the station at all or very little.<br /> <br /> &lt;u&gt;'''Game Administrators, Trial Curators, and Curators may run these with no approval required.'''&lt;/u&gt; <br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Directors for additional questions.<br /> *Examples of Low Impact events would be<br /> **Spawning a spider in maints<br /> **Anything regarding a fax<br /> **Prayer granting, within reason<br /> <br /> === Medium Impact ===<br /> These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.<br /> <br /> &lt;u&gt;Events in this category will be run at Direction discretion, '''and must be approved by a Trial Curator or Curator first. Ping @Event Management.'''&lt;/u&gt;<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> * Examples of Medium Impact Events would be<br /> ** Shuttle Events<br /> ** Central Command Inspections<br /> ** ERT on Evac<br /> ** Custom Syndicate Objectives<br /> <br /> === High Impact ===<br /> These events are events that heavily interfere with the station, changing the entire shift's course.<br /> <br /> &lt;u&gt;Events in this category will be run at Direction discretion, '''and must be approved by a ''Curator'' first. Ping @Event Management for Curator review.'''&lt;/u&gt;<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.'''<br /> ** ERT is exempt from this requirement. <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Design_Document_Template&diff=3842 2025-03-03T01:00:38Z

<p>Lyndomen: Design Doc Template</p> <hr /> <div>== Proposal Title ==<br /> &lt;blockquote&gt;Relevant Department / Category&lt;/blockquote&gt;<br /> <br /> === Introduction ===<br /> [Give a brief introduction of your design goal for this system.]<br /> <br /> === Motivation ===<br /> [Explain current motivations you have regarding the current systems that you hope to address.]<br /> <br /> * Problem: [A problem you or members of the community are facing in the current system.]<br /> * Desire: [Goals and wants that you or the members of the community have.]<br /> <br /> === Solution ===<br /> <br /> ==== [Name of Change 1] ====<br /> [Overview of the change and its function]<br /> <br /> ==== [Name of Change 2] ====<br /> [Overview of the change and its function]<br /> <br /> ===== [Name of Change 3] =====<br /> [Overview of the change and its function]<br /> <br /> === Examples (Optional) ===<br /> [Describe some example scenarios that demonstrate your changes.]<br /> <br /> === Considerations (Optional) ===<br /> [Explain any decisions you made or decisions that should be considered in implementation.]</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3841 2025-03-03T00:30:06Z

<p>Lyndomen: content and event updates</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === Design Documents ===<br /> Design Documents are a tool for Curators and Contributors alike. Design documents are a standardized method of outlining and presenting ideas. It is recommended to use the provided Design Doc Template for the sake of consistency. Document templates and the relevant channels can be found in the Discord development category. <br /> <br /> Contributors can create Design Documents prior to opening a PR, and have them reviewed by Direction in order to tune their ideas to Direction standards before starting the development process. Contributors are also welcome to create Design Documents for review without the intention to develop them personally. Other contributors can always claim approved documents and begin development themselves!<br /> <br /> Curators can collaboratively create Design Documents to address issues laid out in the roadmap. These documents serve as the “Solution Design” step of the roadmap, and will be available to contributors who wish to develop them. <br /> <br /> Curators may designate design documents with varying levels of priority according to how pressing Direction finds the issue. <br /> <br /> === Content Review ===<br /> Reviewing suggested content involves examining current Pull Requests (“PRs”) or Design Documents and providing feedback. Content review should always involve as many members of Direction as possible, but if only one or two choose to review a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, content can always be reverted.<br /> <br /> '''All content must pass the full review process before being approved''', with a few small exceptions. Proposed changes for the following do not require a Direction review:<br /> <br /> * Bug fixes<br /> * Simple tweaks<br /> * Obvious small changes<br /> When in doubt, the Direction team should be asked if a review is needed.<br /> <br /> ==== '''What do you look for in a review?''' ====<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> <br /> ==== How is a review conducted? ====<br /> Content review takes place in the #content-review forum channel in the server Discord. The curator who creates a #content-review post assumes responsibility for providing feedback to the author. '''This includes notifying the author that the content is under review, and summarizing feedback gathered in the post to provide next steps to the author.''' <br /> <br /> If a curator is the author of the content, '''they should find another curator to assume responsibility for review of the content'''. &lt;u&gt;Curators should not argue in favor of their own suggested content in posts&lt;/u&gt;, in order to ensure it stands on its own merit. Content collaboratively designed by Direction is exempt from this restriction.<br /> <br /> '''&lt;u&gt;Content review is not a vote&lt;/u&gt;'''. Polls are not to be used for anything except timing purposes. Members of Direction are encouraged to give specific feedback on why they support proposed content or what they think should be changed about it, with justification. It is the review post author’s responsibility to summarize this concisely for the content author. <br /> <br /> After Direction has discussed the merits of proposed content internally, any final decisions must be communicated to the content author through appropriate channels. This will vary depending on whether the content is a Design Document or a PR.<br /> <br /> '''Design Document''' review takes place entirely within the Discord. Feedback will be provided to the author through the Discord. Typical decisions include:<br /> <br /> * Approving the document<br /> * Approving with an elevated priority tag<br /> * Requesting changes<br /> * Denying the Document<br /> <br /> For '''Pull Requests''', feedback should be communicated to the author through Github. Typical decisions include:<br /> <br /> * Merging the PR<br /> * Test merging the PR<br /> * Requesting changes<br /> * Closing (Denying) the PR<br /> <br /> '''&lt;u&gt;Note:&lt;/u&gt;''' Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. <br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for Content Review. Deadlines should be relative to the size of the content. The standard method of tracking a deadline is to create a poll of the appropriate time frame in the review post.<br /> <br /> * Small changes should be subject to 1-2 days of consideration.<br /> * Major changes may need as many as 1-2 weeks to reach an actionable conclusion.<br /> * The minimum amount of time for a review is 24 hours.<br /> Curators should notify content authors when their content is under official review, and give them an estimated wait time for feedback. If more review time is required, the author should be notified before the previously stated review period ends.<br /> <br /> Deadlines should be established relative to whenever the content is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> If, after sufficient requests for input, Direction '''consistently''' fails to provide feedback on a PR, &lt;u&gt;the final decision to approve or deny can be made by the Head Maintaine&lt;/u&gt;r. Direction may request the content be reverted later if need be. <br /> <br /> === Content Removal ===<br /> Some currently implemented content will inevitably have to be replaced or removed in order to achieve Direction’s design vision. Direction’s preference should be to replace content that doesn’t meet our standards with improved content where possible. <br /> <br /> In order to remove content, Direction must complete each of these steps:<br /> <br /> * Make a list of quantified issues with the content.<br /> * Create a design document that addresses these issues. If Direction cannot do this, it should be stated on the issue page. <br /> * Present the issues and design solutions to the community in the Github.<br /> * Establish a deadline for action to be taken.<br /> <br /> If no action has been taken by the deadline, the content will be removed. Appropriate deadlines are as follows. Content examples are not comprehensive.<br /> <br /> * 1 week: Minor content (sprites, mechanical balance of an item, etc.).<br /> * 2 weeks: Moderate content (roles, machines, etc.).<br /> * 1 month: Major content (gamemodes, etc.).<br /> <br /> Content that is extremely broken or clearly and severely detrimental to the game experience may be removed without this process. Content may be removed upon the original creators request without navigating these processes.<br /> <br /> === Test Merging ===<br /> Tmerges may be conducted on PRs whose effects are potentially unclear. A test merge consists of merging content that may be pending changes, or reversion. The purpose of the merge is to gather feedback from an in-game scenario in order to make such decisions. Test merges may be conducted on a test server if appropriate.<br /> <br /> Players should be made aware of all active test merges on their current server.<br /> <br /> Curators are authorized to manipulate rounds in accordance with Event Management policies in order to test said content. <br /> <br /> Test merges must be monitored, or otherwise have an official way of collecting community feedback (such as a feedback forum). If there are specific aspects of the content that Direction is looking for feedback on, this should be made known to the community before the test. Otherwise, a test may be used to discover previously unknown issues with the content, but '''Direction should take care to ensure content is in the best state possible before conducting a test merge'''.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or a Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc.<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> These events that generally do not interfere with the station at all or very little.<br /> <br /> &lt;u&gt;'''Game Administrators, Trial Curators, and Curators may run these with no approval required.'''&lt;/u&gt; <br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Directors for additional questions.<br /> *Examples of Low Impact events would be<br /> **Spawning a spider in maints<br /> **Anything regarding a fax<br /> **Prayer granting, within reason<br /> <br /> === Medium Impact ===<br /> These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.<br /> <br /> &lt;u&gt;Events in this category will be run at Direction discretion, '''and must be approved by a Trial Curator or Curator first. Ping @Event Management.'''&lt;/u&gt;<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> * Examples of Medium Impact Events would be<br /> ** Shuttle Events<br /> ** Central Command Inspections<br /> ** ERT on Evac<br /> ** Custom Syndicate Objectives<br /> <br /> === High Impact ===<br /> These events are events that heavily interfere with the station, changing the entire shift's course.<br /> <br /> &lt;u&gt;Events in this category will be run at Direction discretion, '''and must be approved by a ''Curator'' first. Ping @Event Management for Curator review.'''&lt;/u&gt;<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.'''<br /> ** ERT is exempt from this requirement. <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3722 2025-01-06T06:28:06Z

<p>Lyndomen: </p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or a Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc.<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> '''These events that generally do not interfere with the station at all or very little.'''<br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Directors for additional questions.<br /> *Examples of Low Impact events would be<br /> **Spawning a spider in maints<br /> **Anything regarding a fax<br /> **Prayer granting, within reason<br /> <br /> === Medium Impact ===<br /> '''These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.'''<br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> * Examples of Medium Impact Events would be<br /> ** Shuttle Events<br /> ** Central Command Inspections<br /> ** ERT on Evac<br /> ** Custom Syndicate Objectives<br /> <br /> === High Impact ===<br /> '''These events are events that heavily interfere with the station, changing the entire shift's course.'''<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.''' <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3721 2025-01-06T04:32:11Z

<p>Lyndomen: /* GitHub PR Review */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Curators may rarely choose to merge a change even if the majority disagrees with it on condition that they take point for monitoring and reporting back on the change. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or a Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc.<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> '''These events that generally do not interfere with the station at all or very little.'''<br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Directors for additional questions.<br /> *Examples of Low Impact events would be<br /> **Spawning a spider in maints<br /> **Anything regarding a fax<br /> **Prayer granting, within reason<br /> <br /> === Medium Impact ===<br /> '''These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.'''<br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> * Examples of Medium Impact Events would be<br /> ** Shuttle Events<br /> ** Central Command Inspections<br /> ** ERT on Evac<br /> ** Custom Syndicate Objectives<br /> <br /> === High Impact ===<br /> '''These events are events that heavily interfere with the station, changing the entire shift's course.'''<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.''' <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Standard_Operating_Procedure&diff=3720 2025-01-05T20:12:04Z

<p>Lyndomen: /* Treatment of Prisoners */</p> <hr /> <div>This page covers the standardized guidelines and procedures aboard the station, but are not written in law; be aware that in cases of dire emergency the commanding officer or certain individuals are authorized to temporarily alter current SOP as they see fit, at the risk of criminal penalties in the case of misuse or abuse! Make sure to look at [[Alert Procedure]] for guidelines that change based on the current alert level.<br /> =General Regulations=<br /> <br /> == '''Definitions''' ==<br /> The terms specified below are defined for further use within the procedures.<br /> :*Captain: The officer legally appointed by Nanotrasen as Commanding Officer of the station. This title is only transferable by Central Command.<br /> :*Commanding Officer / CO: An officer appointed to lead the station and its Command department, whether it be the Captain by Nanotrasen, or an Acting CO by Station Command.<br /> :* Command Staff/Station Command: Members of the Command department who lead a department aboard the station.<br /> :* Crew: All sophonts employed by Station Command, or by NT to reside on the station and perform an established function therein. This includes any sophont listed on the Crew Manifest or issued a functional NT identification and access card. Individuals imprisoned by NT, along with those imprisoned during the course of a shift for violations of Space Law, are considered Crew.<br /> :* Judge: An indivudal legally appointed to preside over a criminal or civil trial, as specified within Trial Procedure.<br /> :* Detainee: Any sophont whose free movement has been curtailed by law enforcement on suspicion of criminal activity. They have not, however, been officially charged with a crime.<br /> :* Arrestee: Any sophont who has been formally charged with a crime. <br /> :* Prisoner: Any sophont who has been sentenced for the commission of a crime, or awaiting trial for a capital offense.<br /> :* Permanent Brig/Permabrig/Brig: A secure location for the long-term confinement of Prisoners. Typically outfitted to sustain the basic survival needs of the Prisoners within.<br /> ==Right to Refuse Service==<br /> All crew operating within their designated job locations are given the right to refuse service at any time for disorderly or abusive conduct. Additionally, all crew members are permitted to use nonlethal force to remove noncompliant or disorderly individuals only when such persons pose a threat to the safety of staff members, or disrupt the orderly functioning of the station. Service may not be refused to first responders acting to address or mitigate an emergency or crisis situation, unless such conduct is egregiously disorderly or abusive.<br /> <br /> ==Hiring Procedure==<br /> While Nanotrasen handles the staffing and recruiting needs of the station, Station Command is additionally authorized to hire any sophont into their respective department, as well as terminate the employment of any crew in their respective department per company policy. For a member of Station Command to personally employ a sophont into their department, a contract must be written stating the name of the employee, the department of employment, the position, and finally bearing the stamp of the Station Command member.<br /> =Controlled Items, Substances, &amp; Areas=<br /> <br /> == Controlled Items ==<br /> Controlled Items include any item that is restricted from general possession and use. Additionally, any equipment or technology providing insight into the development, production, or procurement of a controlled item is also controlled in and of itself. A list of such items follows:<br /> <br /> * Any Controlled Substances, as listed below. <br /> * Any Controlled Armaments, as listed below.<br /> * Electromagnetic pulsing and/or disturbance technology.<br /> * Cryptographic systems, software, or technology.<br /> * Nuclear materials, weapons, and technology.<br /> * Long-range telecommunications and broadcasting technology.<br /> * Astronavigational guidance equipment or technology.<br /> * Telecommunication or signal jamming technology.<br /> * Telecommunications encryption technology.<br /> * Hypodermic spray tools and injectors.<br /> * Cloaking, chameleon, and IFF-inhibiting technology. <br /> * Technology utilizing bluespace as an integral part of its function.<br /> * Teleportation and portal technology.<br /> * Hydraulic or powered equipment designed for the electronic or mechanical bypass of secure-access systems.<br /> <br /> Any individual requiring any above item in the course of their job, or for regular function, may request a document of authorization from the relevant departmental head. Such a document must have an itemized list of the approved Controlled Items, the name and position of the holder, and a signed and stamped statement by the authorizing party. <br /> <br /> Should the holder commit crimes through the use of such authorized items, the authorizing party may be found guilty of Accessory to said crimes, in addition to Endangerment and Abuse of Power where applicable. The Commanding Officer is also authorized to supervise the approval and revocation of documentation as they see fit.<br /> <br /> == Controlled Substances ==<br /> Any individual requiring a Controlled Substance in the course of their job, or for regular function, must request access to a perscription or special dispensation from the Chief Medical Officer. The Psychologist is also permitted to grant prescriptions for psychoactive drugs. Any such document must state the substance(s) being prescribed, the amount(s) where applicable, and the stamp and signature of the authorizing party. <br /> <br /> A list of such Substances follow:<br /> <br /> * Mindbreaker Toxin and other psionically altering agents.<br /> * Romerol, and other rapid acting biological or chemical agents. <br /> * Desoxyephedrine, and similar stimulants.<br /> * Nocturine, and similar sedatives. <br /> * Phlogiston, and other explosive and/or pyrotechnic compounds. <br /> * Amatoxin, and other toxic and/or poisonous compounds. <br /> * Blissifylovene, Soretizone, Tranquinase, and all similar psychoactives used to aid in mental wellbeing. <br /> <br /> == Controlled Armaments ==<br /> <br /> <br /> Controlled Armaments are grouped into categories of increasing severity.<br /> <br /> '''Category A:''' ''Illegal possession of Cat. A controlled armaments may incur a sentence of up to 5min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed, adapted, or used to cause physical harm in close combat<br /> * Any object or equipment specifically designed or adapted to protect against physical harm caused by weapons, projectiles, or other forms of direct assault<br /> * Any object or instrument specifically designed or adapted to incapacitate or disorient by using light or sound without causing permanent injury<br /> * Any object or equipment specifically designed or adapted for explicitly training purposes that would otherwise fall under another category<br /> <br /> '''Category B:''' ''Illegal possession of Cat. B controlled armaments may incur a sentence of up to 10min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any object or instrument specifically designed or adapted to cause physical harm in close combat, which employs a powered system to enhance performance<br /> * Any manually-operated ballistic arms that possess an internal magazine or feeding system, or lack an internal magazine or feeding system altogether<br /> <br /> '''Category C:''' ''Illegal possession of Cat. C controlled armaments may incur a sentence of up to 15min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any manually-operated ballistic arms that use an external magazine or feeding system<br /> * Any semi-automatic ballistic arms not easily concealable within a pocket or coat<br /> * Any object or instrument specifically designed or adapted for explicitly less-lethal purposes that would otherwise fall under another category<br /> <br /> '''Category D:''' ''Illegal possession of Cat. D controlled armaments may incur a sentence of up to 20min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any semi-automatic ballistic arms that are easily concealable<br /> * Any fully-automatic ballistic arms<br /> * Any laser, plasma, or energy based arms, including ones designed, intended, or used for melee combat.<br /> * Any object or device specifically designed or adapted to cause physical harm through detonation of an explosive charge<br /> * Any object or equipment specifically designed or adapted to protect against both a space environment and physical harm caused by weapons, projectiles, or other forms of direct assault<br /> <br /> '''Category E:''' ''Illegal possession of Cat. E controlled armaments may incur a sentence of up to 25min brig for each separate and distinct item, confiscation of the offending item(s), and further legal action as the situation demands.''<br /> <br /> * Any crew-served or emplaced weapon<br /> * Any object or instrument specifically designed or adapted to launch large-calibre explosives or projectiles for offensive or defensive purposes<br /> * Any object or instrument specifically designed or adapted to employ chemical, biological, esoteric, radiological, or nuclear hazards for offensive or defensive purposes<br /> <br /> Armaments licenses may be issued by the Commanding Officer, Warden, or Head of Security. The license must include the name of the holder, a list of allowed armaments, and a stamped signature from the issuer. <br /> <br /> If the holder uses their armaments in the commission of a crime, the issuer may be held liable for accessory to the crimes committed, along with Endangerment and Abuse of Power where applicable.<br /> <br /> == Departmental Dispensations ==<br /> Certain bodies, groups, or personnel may require certain Controlled Items in the course of their job, and as such must be provided exceptions. '''Any member of any department which begins their shift with a controlled item in their possession or within their department’s allocated area is assumed authorized for its possession and use.''' <br /> <br /> Additionally, tools and equipment located within emergency lockers are not considered Controlled Items, so long as they are used as intended.<br /> <br /> ===Logistics===<br /> Members of a station’s Logistics department are permitted to approve any order with the direct permission of an individual with legal access to the contents of that order. Additionally, they may deny any order, at any time, for lack of funds, authority, or any other reason deemed sufficient by their direct superior.<br /> <br /> Unlocked crates, orders stored outside the department, and supplies illegally distributed to unauthorized personnel carry the risk of Endangerment of even Black Marketeering charges. Crates of Controlled Items, Substances, or Armaments should be stored securely within the department, with a copy of their invoices on file. <br /> <br /> === Research ===<br /> Epistemics employees are permitted to use their lab spaces as they see fit, with the following caveats:<br /> <br /> * Any sophont experimentation must be done with the consent of the test subject, and must not have an undue risk of life. The Mystagogue or CO may terminate any experiment for safety or ethical purposes and at their discretion.<br /> * Self-experimentation is prohibited and is chargeable with Endangerment, at a minimum.<br /> * Testing of any explosives or weapons that risk hull penetration or mass destruction must be done at an off-station site.<br /> <br /> Epistemics personnel may also utilise Controlled Items within the confines of designated testing areas and in a manner directly approved jointly by the Mystagogue and by the Head of Security or CO. <br /> <br /> Utilizing or storing Controlled items without direct approval, utilizing Controlled Items outside of the testing areas, and distributing Controlled Items to crew constitute criminal offences under Space Law and may additionally incur demotion as punishment.<br /> <br /> === Medical ===<br /> All medical personnel may carry or use Controlled Substances, along with hypodermic tools, in the course of their job functions and in a manner approved by the CMO or CO, with the following caveats:<br /> <br /> * Any Controlled Substance with the capability to cause rapid and grievous bodily harm or death may not be carried outside of the chemicals lab or treatment areas without a signed and stamped document of authorization.<br /> * Any Controlled Substance with the capacity to cause harm as a consequence of overdose may not be stocked, stored, or displayed in any area or fashion that leaves such substances open and accessible to the public.<br /> * Any hypodermic tool must be kept secure within locked storage or on the person of an authorized individual.<br /> <br /> ==High Security Areas==<br /> High Security Areas, or HSAs, should be restricted, and, during standard station operations, secured where applicable or per alert level. They differ from regular secure areas in that they may contain items, technology, or other assets of high importance or value, and must therefore be held safe. Unauthorized persons within HSAs may be guilty of trespass, or of breaking and entering.<br /> <br /> Common HSAs for commercial and military vessels are as follows: <br /> <br /> * Bridge<br /> * Armory\Gun Deck<br /> * Vault\Strongroom<br /> * Station AI Rooms (Upload, Core, etc.)<br /> * Gravity Generation\Life Support\Engine Rooms<br /> * Telecommunications\Telemetry<br /> * Permanent Brig\Holding Cells<br /> <br /> == Sophonts and Synthetics ==<br /> To be defined as a sophont, a being must be able to utilize a structured language, communicate through the use of written, verbal, and/or body language (or by other means), and possess reasoning and introspection. <br /> <br /> Any such being is considered a sophont, and thus a legal person, regardless of their make, origin, disposition, or prior cognition. As part of their rights, they are to be governed under the same laws as any other sophont, and given the ability to press charges as a sophont.<br /> <br /> The unauthorised jailbreaking or uplifting of property into the status of Sophont is still a criminal offense however, and those found guilty of doing so may be found guilty of sabotage or vandalism.<br /> <br /> An entity’s status as a sophont may be challenged during the process of charging and trialing the individual or another for crimes which utilize the term sophont in the legal language of the crime. The Defense or Prosecution will present evidence indicating that it meets, or does not meet, the criteria above. The Judge will then arbitrate upon the entity's status as a sophont.<br /> <br /> Any synthetic/silicon/inorganic entity with a non-sophont status, is to be classified as a standard synthetic entity. Synthetic entities are the property of the party that constructs or employs the entity, unless otherwise stated by relevant contract or legal document. To damage or destroy such an entity is to damage or destroy the aforementioned party’s property.<br /> =Commanding Officer=<br /> ==Captain’s Authority==<br /> The Commanding Officer of a station or vessel is afforded several rights, broadly referred to as &quot;Captain's Authority&quot;.<br /> <br /> While they are formally and legally appointed CO, they are the ultimate authority aboard a vessel until they are directly dismissed by a superior from Central Command. <br /> <br /> Additionally, they have the authority to pardon and/or parole any individuals accused and sentenced of Grand Felony, Felony, and Misdemeanor-level sentences if deemed in the best interest of the crew and vessel. The CO may be held liable for accessory to any future criminal acts performed by the pardoned individual, and they must make an announcement to the station stating who was pardoned, for what crimes, and for what reason. <br /> <br /> Captain’s Authority carries a responsibility, however; the CO must do everything in their power to protect all entities and assets aboard the station with which they have been entrusted, and must not abandon them while there is a reasonable hope that they may be saved.<br /> <br /> Additionally, the legally appointed Captain of a vessel is afforded two additional rights over that of a CO:<br /> <br /> * To temporarily modify SOP in times of emergency, at the risk of criminal penalties if misused or abused, and<br /> * To deputize members of the crew to carry out law enforcement activity. These deputies are bound by Security Regulations and Space Law, and the Captain may suffer criminal penalties for any crime committed by them. <br /> <br /> ==Line of Succession==<br /> It is the responsibility of Command to ensure that a station retains a CO immediately at the start of the shift and thereafter. If the CO dies and is unrecoverable, or if a CO is not assigned at the start of the shift, an Acting CO must be selected forthwith per the following guide: <br /> <br /> # All active members of Station Command must meet, and choose one of their number to become the Acting CO.<br /> # If no Station Command is alive or on active duty, then each Department must nominate a temporary Delegate. These Delegates must meet and choose an Acting CO from among their number. <br /> # The Acting CO must then duly inform Central Command via fax and make a stationwide announcement.<br /> # Await the end of your shift. <br /> <br /> After Central Command has received the results of the Line of Succession, the Acting CO is afforded all prescribed powers of a CO. An access biscuit ''may or may not'' be sent by Centcomm to assist with this. When a legally appointed Captain arrives, it is the express duty of the Acting CO to hand over any and all Captain-related equipment and accesses to the new CO, and to resign themselves to their original role before their temporary promotion.<br /> ==Command Promotions==<br /> The CO of the vessel is authorized to promote Crew into Station Command positions if it is determined that the vacancy is a detriment to station productivity. The CO has a duty to ensure that the Crew they promote are of a reasonable level of skill, and can be held liable if they disregard this duty.<br /> <br /> Crew members promoted into Station Command positions are considered to be acting members of Station Command, with all rights and responsibilities therein. When NT-appointed Station Command arrive, the acting Command members are required to hand over any specialized equipment (Command ID cards, attire, or tools) and resign themselves to their original position from before their temporary promotion.<br /> ==Mutiny==<br /> Should such a situation arise in which the CO is unfit for their position and declines relinquishment of position and power, and where all alternative legal options have been exhausted, officers may be permitted to lead a mutiny. Officers leading a mutiny must inform Central Command of this occurrence before the mutiny has begun. <br /> <br /> A mutiny, defined as a coordinated effort to depose the commanding officer or officers of a vessel for committing unlawful acts, requires the crew to neutralize the offending staff with non-lethal force where applicable, and lethal measures and weapons only in acts of self-preservation or when given no other option. The commanding officer or officers, as well as their loyalists, are all bound to Space Law, the current alert level and its corresponding RoE.<br /> <br /> Should the mutiny be unsuccessful, only the head officer(s) who approved the mutiny may be charged with sedition and receive a trial, while all mutineers may be demoted, processed by law enforcement, and charged for the crimes they have committed.<br /> <br /> Should the mutiny be successful, the head officer(s) who approved the mutiny must select a new Commanding Officer per Line of Succession. The new CO will then sentence the previous heads of staff for their crimes per Space Law.<br /> <br /> == Foreign Vessels ==<br /> Should civilian and military vessels receive a docking request from another neutral vessel, they may approve or deny such a request. Any vessel may, with consent from the docking entity, be searched by law enforcement upon arrival, and its crew granted free movement accompanied by an escort at the discretion of the CO or law enforcement officials. <br /> <br /> Crew of foreign vessels may be refused entry, at any time and for any reason, and must be returned to, or be escorted to, their own vessel where applicable. Failure to comply may constitute trespass. Docking vessels bearing a warrant or commission represent an exception, and may not be denied entry or be forced to submit to a search.<br /> <br /> Crimes committed against the station or its inhabitants, on station or abroad, are grounds to charge the perpetrator according to the laws of the station. Should visiting entities break the law, or be suspected of doing so, and flee aboard their own vessel, law enforcement personnel are authorized to board the vessel in continuous “hot” pursuit and are fully authorized to effect an arrest upon the relevant party.<br /> <br /> =Security Regulations=<br /> ==Security Jurisdiction==<br /> Law enforcement personnel are bound by trespass and assault laws, and thus cannot operate outside accessible areas, or perform searches without a Probable Cause, a warrant, or a heightened alert level that specifically allows such action. Advanced surgical procedures and cursory implant investigations must be performed by a trained member of the Medical department, operating under their [[Standard Operating Procedure#Standard of Care|Standard of Care]]. <br /> <br /> However, officers are allowed to trespass into a department in “hot pursuit” of a suspect who has fled from an accessible area, who they have Probable Cause to believe has committed a crime<br /> <br /> ==Probable Cause==<br /> While actively enforcing the law, officers are held to the standard of Probable Cause. This phrase represents a reasonable suspicion that a crime has been, or is being, committed, and does not require the officer to have solid evidence of criminal activity. Examples of Probable Cause include witnessing criminal activity or credible reports of such.<br /> <br /> When judged, Probable Cause is to be interpreted within the context of the entirety of the station’s circumstances at the time of the incident. Probable Cause negates the need of a warrant for searches, and, once concluded, should be promptly reported to the Prosecutor, Warden, or Head of Security for review.<br /> <br /> ==Detainment and Arrest==<br /> Any sophont may be detained by a law enforcement officer with Probable Cause. In detainment, the officer will inform the Detainee of the crime they are suspected of committing. They may be held on-site or moved to a strategically sound location, restrained at the officer’s discretion, and detained while law enforcement officers determine if they can proceed with an arrest. Such a detention should last no longer than five (5) minutes. A Detainee may not be searched, unless consent is given or Alert Procedure allows for warrantless search, and their detention should be concluded within five minutes of its start, by either Arresting them or releasing them.<br /> <br /> Any sophont which may have committed a crime, assuming Probable Cause, or has been formally charged with the commission of a crime, may be arrested. In an arrest, the suspect will be restrained by a member of law enforcement, informed of their charges, and taken to the brig for search and processing under Brig Procedure. Any Controlled Items in possession of the Arrestee without licensure or dispensation must be confiscated, along with items used in commission of the crime(s), and will be held indefinitely by law enforcement as described in [[Standard Operating Procedure#Evidence Handling|Evidence Handling]]. Legal counsel may be requested by an Arrestee or Detainee, and must be provided if available.<br /> <br /> ==Brig Procedure==<br /> When confining an Arrestee within the Brig, they should be transferred to the Warden for processing: <br /> <br /> * A full search of the Arrestee and their possessions.<br /> * The confiscation of any Controlled Items or items used in commission of the crime, along with any equipment not befitting a prisoner<br /> * The confining of the Arrestee within a temporary holding cell. <br /> * [[Standard Operating Procedure#Sentencing|Sentencing]] the Arrestee.<br /> <br /> If the Arrestee is sentenced for a Capital-level crime, they are to be transferred to the Permanent Brig, pending trial. If the Warden is unavailable, the arresting officer must process the Arrestee as stated above. All confiscated items must be handled as dictated within [[Standard Operating Procedure#Evidence Handling|Evidence Handling]].<br /> <br /> ==Sentencing==<br /> Any law enforcement individual is authorized to pass sentences on all Grand Felony, Felony and Misdemeanor-level crimes; however, the Prosecutor is responsible for overseeing sentences passed, and is authorized to correct sentences or even acquit them, in accordance with both Space Law and [[Standard Operating Procedure#Paroles and Pardons|Paroles and Pardons]]. Both capital charges and sentences must be placed by the Prosecutor or Court Clerk; if neither are available, the Warden or Head of Security are authorized to press capital charges and request sentencing for them, under Trial Procedure.<br /> <br /> In the case that the accused requests appeal for a Grand Felony- or Felony-level sentence, the Court Clerk should be called to preside over a small, swift adjudication, where the Prosecutor and accused will argue their sides. The Clerk will then decide the sentence, or acquittal, of the accused. If the Clerk is unavailable, the Chief Justice or the Warden can perform appeals. If neither are available, any available member of Station Command is authorized to adjudicate on the case.<br /> <br /> Additionally, any sentence meeting or exceeding 20 minutes, regardless of the severity of the crime(s) committed, will require a trial. If the total sentence still meets or exceeds 20 minutes after the conclusion of a lawful trial, the Judge is fully authorized and encouraged to upgrade their sentence to Extended Confinement. <br /> <br /> Once a sentence has commenced, it must be concluded at or before the agreed-upon time.<br /> <br /> == Evidence Handling ==<br /> When evidence of a crime is secured, it is the responsibility of the arresting officer or Warden to properly handle it, at the penalty of Obstruction of Justice and/or demotion. <br /> <br /> Evidence should be organized by individual and crime, and stored together (e.g., in a bag, in one separate locker, etc) and then placed in an area locked behind security access. <br /> <br /> If a prisoner is released from a temporary holding cell OR the Brig, any of their equipment that is neither a Controlled Item nor used in the commission of their crimes must be returned to them.<br /> <br /> == Rules of Engagement ==<br /> Law enforcement personnel hold a Category D Armaments License, and are authorized at all times to use lethal force to the extent necessary to neutralize adversaries under any of the following circumstances:<br /> <br /> * If the adversary’s number or strength leave the officer at a severe tactical disadvantage.<br /> * If the adversary exhibits a clear and present danger to the vessel by physical means.<br /> * If the adversary poses a significant threat of serious bodily injury or death to the officer or others.<br /> * If the adversary presents an existential threat to the chain of command by illegal means.<br /> * If the adversary cannot be reasonably subdued through non-lethal means without great bodily harm to the officer.<br /> <br /> …wherein an “adversary” is an entity that demonstrates a hostile intent, commits or directly contributes to a hostile act that does not constitute an actual attack, or is actively attacking the vessel or its crew.<br /> <br /> Despite their allowance of lethal force, Security is required to follow the Rules of Engagement of the current Alert Level, as outlined within [[Alert Procedure]].<br /> <br /> == Armory Procedure ==<br /> The armory and its usage are governed by the Warden. The Warden is responsible for stocking, distributing, and recording the collection of weapons used by the station during the shift. They are also afforded the authority to arm security at their discretion, so long as the weaponry distributed is in appropriate response to [[Alert Procedure]].<br /> <br /> All weaponry distributed from armory is issued on a temporary basis. While issued, the weaponry remains as station property, and the wielder assumes a duty to protect the weapon and return it to the Warden when ordered. No non-crew may be issued weaponry from the armory.<br /> <br /> The Warden is accountable for responsibly issuing weapons. Any weaponry issued during a heightened alert level must be returned when the alert has been lowered, or when the threat is no longer present. The weaponry issued must be proportionate to the threat posed, and explosives should not be used unless absolutely necessary.<br /> ==Treatment of Prisoners==<br /> Prisoners have certain rights that must be upheld by law enforcement and Station Command. ''Prisoners must be provided with the following'':<br /> <br /> * Adequate medical care and moral, spiritual, or legal counseling if it is requested and available.<br /> * Access to the Common and Prison radio channels only while serving their sentence. This right may be revoked should it be abused.<br /> * Clothing, food, and water on request.<br /> * Should the holding cells or Permabrig become uninhabitable, prisoners must be securely and safely relocated to another area for confinement, until the holding cells or Permabrig are returned to a serviceable state.<br /> * Prisoners should be granted freedom of movement within their holding area unless there is an undue risk to life and limb.<br /> <br /> Additionally, prisoners sentenced to Extended Confinement have certain rights but also '''more firm restrictions that must be upheld by law enforcement''':<br /> <br /> * Visitation may be permitted only for prisoners sentenced to Extended Confinement. One person may visit such a prisoner for a period of no longer than ten minutes. A reason must be provided for the visit, and the visitor must consent to a search of their belongings. The prisoner is then unable to receive another visitor for another ten minutes.<br /> * Prisoners may request retrial for capital crimes; these requests may be refused depending on the discretion and availability of the court clerk, chief justice, or at the discretion of the warden or head of station security.<br /> * Prisoners may request or may otherwise be given parole with a hearing by the Chief Justice, Court Clerk, or in their absence, the head of station security or commanding officer (see Paroles and Pardons).<br /> <br /> Should prisoners repeatedly and maliciously antagonize law enforcement, to an extent where continued extended confinement becomes infeasible, the warden is fully authorized and encouraged to temporarily upgrade the relevant prisoners’ sentences to Preservative Stasis summarily.<br /> <br /> Moreover, prisoners are liable for any and all crimes that they commit while held either in the temporary holding cells or the Permanent Brig, and may receive trial for more restrictive punishments if their actions warrant a capital sentence.<br /> <br /> ==Paroles and Pardons==<br /> Prisoners may be allowed parole, per the discretion of the Warden, the Head of Security, or the CO. Alternatively, they may request a parole hearing as described within Trial Procedure. <br /> <br /> Prisoners seeking parole may request legal counsel before the hearing, but they must represent themselves. A prisoner who is granted parole is to be treated as a member of the station’s crew with all benefits and responsibilities thereof, and is encouraged to seek gainful employment from relevant command staff. <br /> <br /> Additionally, a pardon can be issued to any entity accused of, or sentenced to, crimes, by the arresting officer, the Judge of a trial, or the Warden in the case of those within the permanent brig, if deemed in the best interest of the crew and vessel, and when the circumstances of the defendant or their offense warrant a suspension of their sentence.<br /> <br /> =Justice Regulations=<br /> ==Pressing Charges==<br /> ===Criminal Charges===<br /> Any crew member may press charges against any other crew member. An individual may be charged of a crime if and only if it can be argued beyond a reasonable doubt that the accused had committed an act in the nature and fashion as described by a particular criminal charge.<br /> <br /> Multiple counts of one crime can be charged. For illegal actions against the station abroad, each incident separated by a reasonable period of inaction, lawful conduct, or another crime is interpreted as one count. For crimes directly bereaving a person (violent acts, theft of personal property etc.), the same applies in addition to each victim being one count. In the case of possession, theft, or any incident involving several separate and distinct items, one charge may be applied per relevant item.<br /> <br /> Charges that are a direct escalation of one another in nature cannot be simultaneously held against the perpetrator if they pertain to the same incident and the same victim/item (if applicable). Then, only the most severe of these charges applies. Additionally, if one charge incorporates another charge within its definition or description, the perpetrator cannot be held accountable for both; rather, only the most severe of these charges applies.<br /> ===Civil Charges===<br /> Any crew member can sue any other crew member for inflicting them with damages caused by a breach of duty. To sue is to request compensation for said damages. To do so, the victim must prove:<br /> *'''Damages:''' That the victim was inflicted with an emotional, physical, or monetary damage<br /> *'''Breach of duty:''' That the defendant had a duty which they failed to uphold(e.g., a duty to not endanger crew, a duty to act respectfully), leading to the victim being inflicted with a damage<br /> *'''Severity:''' That the damage was severe enough to warrant the compensation requested<br /> Compensation can either be explicitly specified by the victim or left for the court to decide. Either way, the court is free to modify the compensation as it sees fit. Most often, compensation is rendered in the form of court orders compelling a crew member to do something (e.g., return an item, make an apology, or permanently avoid a certain area). Court orders should be written and stamped with the notary stamp.<br /> <br /> ==Court Orders==<br /> The individuals specified in the three sections below can issue Court Orders, which are legally-enforced documents that carry the penalty of an Obstruction of Justice charge and forced compliance with the order by security. Each order has its own requirements and authorized issuers, but are all implied to require '''''the stamp (where applicable) and signature of the issuer to be valid.'''''<br /> ===Warrants===<br /> Warrants represent official orders to the security department, issued by relevant officers or the Justice Department. Warrants are only valid when issued by either the Chief Justice or Court Clerk, or in both of their absences, the Commanding Officer or head of station Security. <br /> <br /> * Individual Warrants may order the search or detainment of an individual, or the arrest of the individual with evidence. This may also include surgical procedures, cursory implant inspections, or any other invasive searches with both probable cause and evidence. These warrants should include a name, the actions prescribed (detainment, search, arrest, etc.), and a description if applicable.<br /> * Search Warrants may order the search of an entire departmental area, by force if necessary, and may order the arrest of listed individuals implicated in a crime or crimes with probable cause and evidence. Search Warrants should include an area, a brief description of the probable cause, and a list of individuals if applicable.<br /> <br /> ===Injunctions===<br /> The Chief Justice, Commanding Officer, or Judge of a trial are fully authorized to issue injunctions: legally-binding, written orders restricting Inhabitants from doing something disruptive to station productivity or personal rights. <br /> These may be issued on discretion or as relief for Civil Trials. Injunctions may not compel someone to violate Space Law or SOP, and the issuer is liable for abuse of power charges if this is misused. An injunction must include a list of affected names and a detailed description of the restrictions to be valid.<br /> <br /> ===Subpoenas===<br /> The Chief Justice, Court Clerk, or Judge of a trial may issue Subpoenas, which are trial-related Court Orders compelling an individual to produce evidence or make themselves present at a location for court. A subpoena can order an individual to:<br /> <br /> * Appear as a witness, defendant, plaintiff, or prosecution;<br /> * Produce evidence for a trial; <br /> * Appear for questioning in deposition.<br /> <br /> A subpoena must include a list of names, a detailed description of evidence requested or reason for appearing, and a reasonable time frame no shorter than 3 minutes. The individuals summoned by the subpoena must be informed of its presence for it to be a valid order. This can be done via general announcement, fax, verbal announcement, or otherwise.<br /> <br /> === Affidavits ===<br /> An Affidavit is a legal document, consisting of a formal written statement of witness. An Affidavit must be written by the witness, or Affiant, who must state their relation to the incident at hand, and must be signed and stamped (if applicable) by a member of Security, Justice, or Command, who is verifying that the contents of the Affidavit are true to the best of their knowledge. The witness to the Affidavit must not be directly connected to the incident. <br /> <br /> Affidavits are considered valid witness statements for use in a trial (see Trial Procedure, below), and can be used either in tandem with a verbal witness statement, or to obtain testimony from an affiant whose job requirements and/or personal circumstances make attending a trial unfeasible. <br /> <br /> An affidavit may be impeached- and thus removed from evidence- if the Prosecution or Defense can introduce testimony or other evidence that directly contradicts the statements recorded within the Affidavit. The Affiant may then be liable for criminal charges.<br /> <br /> =Trial Procedure=<br /> A trial may be requested for civil disputes and capital charges. Civil charges may be refused, depending on the availability and discretion of a potential Judge; however, capital crimes require a trial. This also includes non-capital trials required as dictated within Sentencing guidelines. Miscellaneous trials, such as those described within Paroles and Pardons, only require the Judge and the defendant.<br /> <br /> Criminal trials may be waived if a suspect pleads guilty to a member of the Justice or Security department, or to station command. Their sentence should be passed by a Judge immediately, without the need for a full hearing. The Judge should also sentence the defendant summarily if they are held in contempt of court during the trial.<br /> <br /> The trial takes the form of an arbitration court hearing, presided over by an appointed Judge, and including adequate Prosecution and Defense, as dictated below. All charges, arguments, and evidence must be filed with the Judge before the case begins. The trial shall begin when the Defense, Prosecution, and Judge are all present and ready to begin. A trial does not need to be open to the public. <br /> <br /> The Judge is charged with ensuring the trial is completed in a timely manner, and is granted the power to charge someone with Contempt of Court, under Space Law, if they disrupt the case. Suitable Judges should be chosen from the following list, in sequential order:<br /> <br /> # The Chief Justice<br /> # The Clerk<br /> # An impartial member of the Justice department.<br /> # An impartial member of Station Command.<br /> # The Warden.<br /> <br /> The Defense should ideally be a member of the Justice department assigned to argue in favor of the defendant; if none are available, the defendant may choose to represent themselves.<br /> <br /> The Prosecution should ideally be the Prosecutor; if they are unavailable, the case should be prosecuted by an unbiased member of Station Command or a law enforcement officer, in that order.<br /> <br /> If there is not a viable and/or willing Defense or Prosecution, the Judge is fully authorized and strongly encouraged to pass a summary sentence of Extended Confinement until an adequate trial can be held.<br /> <br /> ==Criminal Trials==<br /> A criminal case should take no longer than 25 minutes in total. Criminal cases should either have security personnel present, or plan to have them present by the end of the trial.<br /> :#The judge brings the court in session.<br /> :#Prosecution opens the proceedings, stating the charges and introducing witnesses and exhibits that will be brought forward during the presentation of evidence. They may also recommend a sentence to the judge, appropriate to the charge based on their opening statement.<br /> :#Defense enters their plea- Guilty or Not Guilty.<br /> :#If Guilty, the Judge is authorized to immediately pass a ruling, as stated below.<br /> :#If Not Guilty, they are to provide their own opening statement and introduce their own witnesses and exhibits where applicable.<br /> :#Presentation of evidence follows, lead by Prosecution, then Defense. <br /> :#*Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> :#Finally, closing statements are made by the Prosecution, Defense, and Prosecution once more due to burden of proof. No new evidence can be introduced within a closing statement. <br /> :#A ruling will be issued by the Judge, written down, and stamped with the Notary stamp, the Judge's stamp, and their signature. <br /> :#The Judge adjourns the court. Any present or soon-to-be-present Security personnel will then enact the ruling.<br /> <br /> == Civil Trials ==<br /> Civil cases do not require Prosecution or Defense, but they may receive assistance from either both before and during the case. Both the defendant and plaintiff must be made to summon at the court, if a party does not appear out of either refusal or negligence, or fails to comply with a court order from a civil trial, that party may be charged with contempt of court, a felony. A civil case involves seeking damages from a defendant, which could be monetary, an item, or otherwise. A civil case should take no longer than 15 minutes in total.<br /> <br /> # The Judge brings the court into session.<br /> # Plaintiff opens proceedings by stating the damages, before introducing witnesses and exhibits that will be brought forward during presentation of evidence. They may also reccomend civil relief to the judge, appropriate to the damages listed wthin their opening statement.<br /> # Defendant follows with their opening statement, contradicting the Plaintiff's theories and assertions. They will also introduce their own witnesses and exhibits, where applicable. <br /> # Presentation of evidence follows, led by the Plaintiff, then the Defendant. <br /> #* Cross-examination may be requested following submission of individual exhibits or witnesses, and granted at the Judge's discretion.<br /> # Finally, closing statements are made by the Plaintiff, Defense, and Plaintiff once more due to burden of proof. No new evidence should be introduced or referenced by these statements.<br /> # A ruling will be made by the Judge, written, and stamped by the Notary stamp, the Judge's stamp, and signed by the Judge.<br /> # The Judge adjourns court. <br /> <br /> Any ruling shall then be enacted; if a party refuses to follow through with the ruling, they may suffer criminal penalties. <br /> <br /> == Presentation of Evidence ==<br /> <br /> ===Eyewitness Testimony===<br /> Any sophont or other entity willing and capable of presenting themselves before court under oath and present at the scene of the crime as a bystander or a victim at the time of its commission, may offer eyewitness testimony before the court at request of defense or prosecution. Extra time may be granted to either side at the behest of the Judge to allow for witnesses not currently present.<br /> <br /> ===Objection to Testimony===<br /> Any witness that falls under the following conditions may be excused as a witness or have their testimony deemed inadmissible:<br /> :*The witness lacks the mental, intellectual, or other capacity to understand the context of the case.<br /> :*The witness's inclusion will cause substantial cost or delay to the case, proceedings, or upkeep of the station.<br /> :*The witness is the judge.<br /> ===General Objections===<br /> Both parties in a trial may object to testimony to have the testimony deemed inadmissible, move past the question, or rephrase a question to keep a trial within time limit:<br /> :* '''Hearsay:''' The witness testifies using an out-of-court statement by an individual not present in court, thereby rendering it impossible to verify. This testimony will be inadmissible.<br /> :* '''Asked and answered:''' A question is posed that has already been answered previously by a witness. Such a question must be skipped.<br /> :* '''Narrative:''' A question is posed that would require a significantly long answer with multiple facts, or when the witness chooses to answer a question in this way. The question must be reworded, or the witness must be reminded to answer promptly and stay on topic.<br /> <br /> Objections are completely at the discretion of the judge, who does not always need to sustain an objection even if it is within these guidelines. It is up to the judge to decide if an objection is proper or necessary to keep the trial quick and fair.<br /> <br /> ==Procedural Defense==<br /> Whereas a defendant is placed on trial, they are granted the privilege to challenge the legitimacy of charges or claims brought against them by the legal process. Any of the following may be invoked:<br /> :*Issue Preclusion/Double Jeopardy Clause: accused persons may not be tried on the same charges following an acquittal or conviction, except in the case of acquittal and subsequent credible admission of guilt.<br /> :*Entrapment Clause: accused persons found to be induced or coerced by law enforcement into the commission of the crimes listed in the charges may be acquitted or have their sentence reduced.<br /> :*Exclusionary Clause: evidence collected and/or analyzed in violation of accused persons’ rights under law may be inadmissible in court.<br /> =Medical Regulations=<br /> ==Standard of Care==<br /> <br /> Upon agreeing to provide medical care, staff assume the following duties of care:<br /> <br /> * They must provide a reasonable level of skillful, quality care<br /> * They must not make critical errors resulting in major personal injury or death, at the risk of criminal and civil liability.<br /> * They must show diligence in providing treatment, both inside and outside of the medical department area during their shift.<br /> * They must provide privacy to patients in non-emergency situations. <br /> * If they have limited resources, they must allocate what resources are available to them via triage.<br /> * They must not provide treatment that would breach Space Law or violate ethical principles.<br /> * They must ensure that invasive procedures or surgeries, including implant removals or inspections, are performed by trained personnel and properly given authorization via a valid search warrant. The need for a warrant is removed during a Code Gamma or similar alert status.<br /> <br /> ==DNRs==<br /> Do Not Resuscitate (DNR) orders are commands issued to medical personnel to restrict the revival of a specified individual. DNRs are issued for the following reasons:<br /> <br /> * Lawful executions;<br /> * Suicide in the custody of law enforcement, verified by the Corpsman.<br /> * Patient refusal.<br /> <br /> DNRs that do not involve execution must be verified by the CMO before taking effect.<br /> <br /> ==Medical Evaluation==<br /> Given good medical reason and with documentation, the Chief Medical Officer of a vessel may declare any on-duty personnel unfit for duty and order them demoted from their position. This includes the Commanding Officer, who may not overrule this procedure. <br /> <br /> In order for a medical evaluation to be considered lawfully applicable, the CMO and relevant head of department must both agree that the specified crewmate is unfit for duty in order to proceed with the demotion. In the case of the Commanding Officer, Central Command should be contacted as soon as possible.<br /> <br /> ==Quarantine==<br /> Medical staff are afforded the right to quarantine individuals that currently suffer from infectious or contagious diseases, and may confine them within pre-designated quarantine areas in the course of treatment, until the point that they are no longer infectious or harmful to the rest of the crew.</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3689 2024-12-19T00:34:28Z

<p>Lyndomen: /* Medium Impact */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or a Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc.<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> '''These events that generally do not interfere with the station at all or very little.'''<br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Directors for additional questions.<br /> *Examples of Low Impact events would be<br /> **Spawning a spider in maints<br /> **Anything regarding a fax<br /> **Prayer granting, within reason<br /> <br /> === Medium Impact ===<br /> '''These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.'''<br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> * Examples of Medium Impact Events would be<br /> ** Shuttle Events<br /> ** Central Command Inspections<br /> ** ERT on Evac<br /> ** Custom Syndicate Objectives<br /> <br /> === High Impact ===<br /> '''These events are events that heavily interfere with the station, changing the entire shift's course.'''<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.''' <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3688 2024-12-19T00:31:59Z

<p>Lyndomen: /* Event Rules */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or a Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc.<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> '''These events that generally do not interfere with the station at all or very little.'''<br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Directors for additional questions.<br /> <br /> === Medium Impact ===<br /> '''These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.'''<br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> <br /> === High Impact ===<br /> '''These events are events that heavily interfere with the station, changing the entire shift's course.'''<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.''' <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=How_to_contribute&diff=3686 2024-12-17T14:35:07Z

<p>Lyndomen: </p> <hr /> <div>[[File:Duty calls 2x.png|thumb|(xkcd #386)&lt;ref&gt;https://imgs.xkcd.com/comics/duty_calls_2x.png&lt;/ref&gt;]]<br /> <br /> ===== Hello! ===== <br /> Welcome to Lyndomen’s definitive guide on how to contribute to the Delta-V project. <br /> <br /> Firstly, '''contribution takes many forms'''. Not all contributors are technical, some are Administrators, Curators, Documentors, Maintainers, whatever. This is a guide on Technical Contribution (how do I make thing that goes in the game). <br /> <br /> The mood of this guide is going to teach you exactly how to do this without explaining why. I don’t know why either, and it doesn’t matter until you want to get good at contribution. For your first contribution, why doesn’t matter. By writing this entire ass guide, it will also piss people off who do know what they are doing. Then they can suggest things that make this more accurate. <br /> <br /> ===== Getting Started =====<br /> Uh, well, this guide is only for Windows. Sorry Mac users, I am told this might work for you but I cannot and will not test it. <br /> <br /> # Make an account on [https://github.com/signup?source=login GitHub]. This is where the game files &lt;sub&gt;called a Repository&lt;/sub&gt; are stored on the internet, and thus if you want to submit a change, you gotta have an account. Don’t use your real name please, it’s public.<br /> # Go to this link, and press Fork in the top right. https://github.com/DeltaV-Station/Delta-v &lt;sub&gt;A '''Fork''' is your copy of DeltaV. Name your fork whatever you want, it doesn't matter. The default settings are fine, just make yourself the owner.&lt;/sub&gt; <br /> <br /> Download and install everything here. <br /> * [https://desktop.github.com/download/ GitHub Desktop] is the program that copies the game files down onto your computer. <br /> * [https://www.jetbrains.com/rider/download/#section=windows Rider] is the program you do all the work in<br /> * [https://www.python.org/downloads/windows/ Python] is a technical thing. You won't do much with it, but it will make things work secretly. Pick the thing that says “Download Windows installer (64-bit)”<br /> * [https://dotnet.microsoft.com/en-us/download/dotnet/8.0 .NET 8.0] is another technical thing. Pick the thing that says “Windows x64”.<br /> * [https://git-scm.com/downloads/win Git Bash] is the last technical thing. I don't know what it does but the nerds yelled at me to put it on the list. <br /> <br /> ===== Setting up Github Desktop =====<br /> # Load up Github Desktop, and log in with your fancy GitHub account. <br /> # When it asks you to pick a repository, select to Clone your fork. It might take a bit. <br /> # Select “to contribute to the parent project” when it's done. <br /> # At the top click “Current branch”, it says master right now. Click New Branch. <br /> # Make a branch with a clever title that somewhat describes your idea. For instance, I might name mine “rework CC”. &lt;sub&gt;A '''branch''' is a copy of your copy of DeltaV. You must work off a branch, so get used to it for every new project.&lt;/sub&gt;<br /> # Once that is all set, click the button that says “Select your editor in Options”. <br /> # Select external editor JetBrains Rider, and select where it got installed. &lt;sub&gt;Mine was at C:\Program Files\JetBrains\JetBrains Rider 2024.2.5\bin&lt;/sub&gt;<br /> # Click Open in JetBrains Rider<br /> <br /> ===== Setting up Rider =====<br /> # It will load for a bit, but will eventually display “Directory ‘FORKNAME’ contains these solutions”, select “SpaceStation14.sln. Trust and Open it.<br /> # Select your branch at the top, switch it from Master to whatever you made earlier. Pressing Checkout on a branch means you are going to edit it!<br /> # Lets test things out. In the top right, select &quot;Content Server+ Client&quot;in Configurations. Edit the configuration and add Content.Server and Content.Client, and save it as a new name. I named mine &quot;Both Things&quot;. Click OK to save the change. <br /> # Click the play button next to Both Things. Your computer should start revving up as it Builds the project. It will take some time, but eventually you will have both the server and client pop up. You can log in to localhost with a username of your choice. <br /> # Press ~ to open the console, and type &quot;fuckrules&quot;. <br /> # You should now be in the developer environment! Play around, and shoot the RPG at a wall. You deserve a break. If you blow it up too bad, type &quot;endround&quot; in the console. <br /> <br /> <br /> ===== Thats all for now folks! =====<br /> The rest is up to you! Get your YML or C# code working nice, and submit it as a Pull Request to the DeltaV repo. I will have more steps for that later!</div>

Lyndomen https://wiki.deltav.gay/index.php?title=How_to_contribute&diff=3685 2024-12-17T14:33:57Z

<p>Lyndomen: </p> <hr /> <div>[[File:Duty calls 2x.png|thumb|(xkcd #386)&lt;ref&gt;https://imgs.xkcd.com/comics/duty_calls_2x.png&lt;/ref&gt;]]<br /> <br /> ===== Hello! ===== <br /> Welcome to Lyndomen’s definitive guide on how to contribute to the Delta-V project. <br /> <br /> Firstly, '''contribution takes many forms'''. Not all contributors are technical, some are Administrators, Curators, Documentors, Maintainers, whatever. This is a guide on Technical Contribution (how do I make thing that goes in the game). <br /> <br /> The mood of this guide is going to teach you exactly how to do this without explaining why. I don’t know why either, and it doesn’t matter until you want to get good at contribution. For your first contribution, why doesn’t matter. By writing this entire ass guide, it will also piss people off who do know what they are doing. Then they can suggest things that make this more accurate. <br /> <br /> ===== Getting Started =====<br /> Uh, well, this guide is only for Windows. Sorry Mac users, I am told this might work for you but I cannot and will not test it. <br /> <br /> # Make an account on [https://github.com/signup?source=login GitHub]. This is where the game files &lt;sub&gt;called a Repository&lt;/sub&gt; are stored on the internet, and thus if you want to submit a change, you gotta have an account. Don’t use your real name please, it’s public.<br /> # Go to this link, and press Fork in the top right. https://github.com/DeltaV-Station/Delta-v &lt;sub&gt;A '''Fork''' is your copy of DeltaV. Name your fork whatever you want, it doesn't matter. The default settings are fine, just make yourself the owner.&lt;/sub&gt; <br /> <br /> Download and install everything here. <br /> * [https://desktop.github.com/download/ GitHub Desktop] is the program that copies the game files down onto your computer. <br /> * [https://www.jetbrains.com/rider/download/#section=windows Rider] is the program you do all the work in<br /> * [https://www.python.org/downloads/windows/ Python] is a technical thing. You won't do much with it, but it will make things work secretly. Pick the thing that says “Download Windows installer (64-bit)”<br /> * [https://dotnet.microsoft.com/en-us/download/dotnet/8.0 .NET 8.0] is another technical thing. Pick the thing that says “Windows x64”.<br /> <br /> ===== Setting up Github Desktop =====<br /> # Load up Github Desktop, and log in with your fancy GitHub account. <br /> # When it asks you to pick a repository, select to Clone your fork. It might take a bit. <br /> # Select “to contribute to the parent project” when it's done. <br /> # At the top click “Current branch”, it says master right now. Click New Branch. <br /> # Make a branch with a clever title that somewhat describes your idea. For instance, I might name mine “rework CC”. &lt;sub&gt;A '''branch''' is a copy of your copy of DeltaV. You must work off a branch, so get used to it for every new project.&lt;/sub&gt;<br /> # Once that is all set, click the button that says “Select your editor in Options”. <br /> # Select external editor JetBrains Rider, and select where it got installed. &lt;sub&gt;Mine was at C:\Program Files\JetBrains\JetBrains Rider 2024.2.5\bin&lt;/sub&gt;<br /> # Click Open in JetBrains Rider<br /> <br /> ===== Setting up Rider =====<br /> # It will load for a bit, but will eventually display “Directory ‘FORKNAME’ contains these solutions”, select “SpaceStation14.sln. Trust and Open it.<br /> # Select your branch at the top, switch it from Master to whatever you made earlier. Pressing Checkout on a branch means you are going to edit it!<br /> # Lets test things out. In the top right, select &quot;Content Server+ Client&quot;in Configurations. Edit the configuration and add Content.Server and Content.Client, and save it as a new name. I named mine &quot;Both Things&quot;. Click OK to save the change. <br /> # Click the play button next to Both Things. Your computer should start revving up as it Builds the project. It will take some time, but eventually you will have both the server and client pop up. You can log in to localhost with a username of your choice. <br /> # Press ~ to open the console, and type &quot;fuckrules&quot;. <br /> # You should now be in the developer environment! Play around, and shoot the RPG at a wall. You deserve a break. If you blow it up too bad, type &quot;endround&quot; in the console. <br /> <br /> <br /> ===== Thats all for now folks! =====<br /> The rest is up to you! Get your YML or C# code working nice, and submit it as a Pull Request to the DeltaV repo. I will have more steps for that later!</div>

Lyndomen https://wiki.deltav.gay/index.php?title=How_to_contribute&diff=3684 2024-12-17T14:33:17Z

<p>Lyndomen: /* Getting Started */</p> <hr /> <div>[[File:Duty calls 2x.png|thumb|(xkcd #386)&lt;ref&gt;https://imgs.xkcd.com/comics/duty_calls_2x.png&lt;/ref&gt;]]<br /> <br /> ===== Hello! ===== <br /> Welcome to Lyndomen’s definitive guide on how to contribute to the Delta-V project. <br /> <br /> Firstly, '''contribution takes many forms'''. Not all contributors are technical, some are Administrators, Curators, Documentors, Maintainers, whatever. This is a guide on Technical Contribution (how do I make thing that goes in the game). <br /> <br /> The mood of this guide is going to teach you exactly how to do this without explaining why. I don’t know why either, and it doesn’t matter until you want to get good at contribution. For your first contribution, why doesn’t matter. By writing this entire ass guide, it will also piss people off who do know what they are doing. Then they can suggest things that make this more accurate. <br /> <br /> ===== Getting Started =====<br /> Uh, well, this guide is only for Windows. Sorry Mac users, use [https://www.winehq.org/ Wine] or preferably a better guide. <br /> <br /> # Make an account on [https://github.com/signup?source=login GitHub]. This is where the game files &lt;sub&gt;called a Repository&lt;/sub&gt; are stored on the internet, and thus if you want to submit a change, you gotta have an account. Don’t use your real name please, it’s public.<br /> # Go to this link, and press Fork in the top right. https://github.com/DeltaV-Station/Delta-v &lt;sub&gt;A '''Fork''' is your copy of DeltaV. Name your fork whatever you want, it doesn't matter. The default settings are fine, just make yourself the owner.&lt;/sub&gt; <br /> <br /> Download and install everything here. <br /> * [https://desktop.github.com/download/ GitHub Desktop] is the program that copies the game files down onto your computer. <br /> * [https://www.jetbrains.com/rider/download/#section=windows Rider] is the program you do all the work in<br /> * [https://www.python.org/downloads/windows/ Python] is a technical thing. You won't do much with it, but it will make things work secretly. Pick the thing that says “Download Windows installer (64-bit)”<br /> * [https://dotnet.microsoft.com/en-us/download/dotnet/8.0 .NET 8.0] is another technical thing. Pick the thing that says “Windows x64”.<br /> <br /> ===== Setting up Github Desktop =====<br /> # Load up Github Desktop, and log in with your fancy GitHub account. <br /> # When it asks you to pick a repository, select to Clone your fork. It might take a bit. <br /> # Select “to contribute to the parent project” when it's done. <br /> # At the top click “Current branch”, it says master right now. Click New Branch. <br /> # Make a branch with a clever title that somewhat describes your idea. For instance, I might name mine “rework CC”. &lt;sub&gt;A '''branch''' is a copy of your copy of DeltaV. You must work off a branch, so get used to it for every new project.&lt;/sub&gt;<br /> # Once that is all set, click the button that says “Select your editor in Options”. <br /> # Select external editor JetBrains Rider, and select where it got installed. &lt;sub&gt;Mine was at C:\Program Files\JetBrains\JetBrains Rider 2024.2.5\bin&lt;/sub&gt;<br /> # Click Open in JetBrains Rider<br /> <br /> ===== Setting up Rider =====<br /> # It will load for a bit, but will eventually display “Directory ‘FORKNAME’ contains these solutions”, select “SpaceStation14.sln. Trust and Open it.<br /> # Select your branch at the top, switch it from Master to whatever you made earlier. Pressing Checkout on a branch means you are going to edit it!<br /> # Lets test things out. In the top right, select &quot;Content Server+ Client&quot;in Configurations. Edit the configuration and add Content.Server and Content.Client, and save it as a new name. I named mine &quot;Both Things&quot;. Click OK to save the change. <br /> # Click the play button next to Both Things. Your computer should start revving up as it Builds the project. It will take some time, but eventually you will have both the server and client pop up. You can log in to localhost with a username of your choice. <br /> # Press ~ to open the console, and type &quot;fuckrules&quot;. <br /> # You should now be in the developer environment! Play around, and shoot the RPG at a wall. You deserve a break. If you blow it up too bad, type &quot;endround&quot; in the console. <br /> <br /> <br /> ===== Thats all for now folks! =====<br /> The rest is up to you! Get your YML or C# code working nice, and submit it as a Pull Request to the DeltaV repo. I will have more steps for that later!</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3682 2024-12-16T19:29:59Z

<p>Lyndomen: /* Event Rules */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc. <br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> '''These events that generally do not interfere with the station at all or very little.'''<br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> === Medium Impact ===<br /> '''These are events that do interfere with the station, but should not provide the opportunity to derail the station, or round remove players.'''<br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * For easier access for other curators and yourself to repeat these events, it is heavily advised to write it down in #event-library. It will give a clearer picture for yourself and for others.<br /> <br /> === High Impact ===<br /> '''These events are events that heavily interfere with the station, changing the entire shift's course.'''<br /> * '''These''' '''must be planned in advance'''. '''There must be a 4 hour notice before the event starts.''' <br /> * '''These must be written down in #event-library and approved. Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * The current gamemode will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds.<br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> * '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator. '''Make sure to have some admin(s) with you.'''</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3681 2024-12-16T19:22:30Z

<p>Lyndomen: /* Eventrunning Practices */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc. <br /> *<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. This is the one exception to mandatory event reporting, you do not need to report these (but still can if you want!)'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> <br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> Examples include:<br /> <br /> * Responding to certain faxes as CC.<br /> * Making CC announcements regarding non specific advice.<br /> * Spawning, or modifying a spider during a vent critters event<br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high.<br /> * Making fun, in-world announcements as non CC about certain things.<br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> === Medium Impact ===<br /> <br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * Take note to not overwhelm the station! If the round has particularly active traitors, don’t make it worse for Security!<br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be '''planned out in advance'''. Write out an event plan, with requirements, objectives, goals, etc. <br /> <br /> === High Impact ===<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and '''must be planned in advance'''. '''Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> <br /> '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator<br /> <br /> Examples include:<br /> <br /> * Hellshift <br /> * Rimworld Events<br /> * AI Malfunction<br /> * Central Command Inspections<br /> * Furtive Fugitives - dV Event Plan</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3680 2024-12-16T18:58:46Z

<p>Lyndomen: /* Event Rules */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> *'''Events can fail, &lt;u&gt;let them&lt;/u&gt;'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> *'''Events must meet or exceed our MRP Standard'''. <br /> *Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run Non-Natural Zombies, Deathsquad, CBURN etc. <br /> *<br /> * '''The event should fit within the established lore of the game.'''<br /> * '''Be cooperative with other staff!''' Work, plan together to make certain dumb ideas into functional, fun things!<br /> * '''Do not act CC as some sort of a dictatorship -''' CC in our server is supposed to be helpful. While they can be strict with some certain things, you should usually play them as supportive.<br /> <br /> === Eventrunning Practices ===<br /> <br /> * '''Events are for everyone’s enjoyment, not just your own.''' <br /> <br /> *Let your created ghost roles be taken by someone else. You are here to orchestrate the event, not partake. <br /> *Do not run events that are designed to interact with one person in particular, especially your own character.<br /> *Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift.<br /> *'''Do not overwhelm the station -''' If you see that the current security is dealing with ''very active criminals,'' maybe it’s best to not send in pirates or other type of a large antagonist group. Evaluate the current round, what gamemode it is and proceed thoughtfully.<br /> *'''Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room.'''<br /> ** Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> ** Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> ** Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> *When creating a ghost role, be sure to clearly describe their goal or function in the ghost roles description. While being over-specific limits some room for the player’s own creativity, having a very broad description isn’t good as well. Try to make it short and concise.<br /> **This is especially important '''if you’re making a custom antagonist.''' Be ''specific'' of how much the antagonist can cause harm/chaos to the station. You can always use the ghost role rules to be more specific!<br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> <br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> Examples include:<br /> <br /> * Responding to certain faxes as CC.<br /> * Making CC announcements regarding non specific advice.<br /> * Spawning, or modifying a spider during a vent critters event<br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high.<br /> * Making fun, in-world announcements as non CC about certain things.<br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> === Medium Impact ===<br /> <br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * Take note to not overwhelm the station! If the round has particularly active traitors, don’t make it worse for Security!<br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be '''planned out in advance'''. Write out an event plan, with requirements, objectives, goals, etc. <br /> <br /> === High Impact ===<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and '''must be planned in advance'''. '''Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> <br /> '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator<br /> <br /> Examples include:<br /> <br /> * Hellshift <br /> * Rimworld Events<br /> * AI Malfunction<br /> * Central Command Inspections<br /> * Furtive Fugitives - dV Event Plan</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3679 2024-12-16T18:47:55Z

<p>Lyndomen: /* Event Rules */</p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> '''Events that Rock:''' Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> ** This serves to show what actions an admin/curator committed during the round and have a space for criticism if needed, to help people improve in their work. ''Do not be afraid to document your events, even if it didn’t go properly to plan or was a disaster. We’re not here to shame you, we’re all in this together!''<br /> * '''Events must meet or exceed our MRP Standard'''. LRP, or NRP events such as “wangvasion” have no place outside of Garbage Day/express Head Game Administrator permission.<br /> * Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run Non-Natural Zombies, Deathsquad, or Non–evac borne ERT, CBURN etc. Administrators may deploy ERT, CBURN, and similar forces in exception of this policy, but only on the evacuation shuttle, and only after request from the station.<br /> * Events are for '''everyone’s''' enjoyment, not just your own.<br /> * Do not run events that are designed to interact with one person in particular, especially your own character.<br /> * '''Events can and will fail, let them'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> * The event should fit within the established lore of the game.<br /> * Unless your created role has a vital part to the event, let your created ghost roles be taken by someone else, not for yourself. You’re here to provide fun scenarios for players, not for yourself.<br /> * Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift. It’s lame to see such things, we want to empower players to tell the story.<br /> * Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room.<br /> * Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> * Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> * Remember to be cooperative with other staff! Work, plan together to make certain dumb ideas into functional, fun things!<br /> * Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> * Outside of Events, attempt to influence the round as little as possible.<br /> * Fellow ghosts might try to pressure you to do something funny! Just remember, you probably shouldn’t, unless it meets our Event Guidelines!  <br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> <br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> Examples include:<br /> <br /> * Responding to certain faxes as CC.<br /> * Making CC announcements regarding non specific advice.<br /> * Spawning, or modifying a spider during a vent critters event<br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high.<br /> * Making fun, in-world announcements as non CC about certain things.<br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> === Medium Impact ===<br /> <br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * Take note to not overwhelm the station! If the round has particularly active traitors, don’t make it worse for Security!<br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be '''planned out in advance'''. Write out an event plan, with requirements, objectives, goals, etc. <br /> <br /> === High Impact ===<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and '''must be planned in advance'''. '''Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> <br /> '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator<br /> <br /> Examples include:<br /> <br /> * Hellshift <br /> * Rimworld Events<br /> * AI Malfunction<br /> * Central Command Inspections<br /> * Furtive Fugitives - dV Event Plan</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3653 2024-12-10T03:16:10Z

<p>Lyndomen: </p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> '''Events that Rock:''' Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> === Event Rules ===<br /> <br /> * '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> * Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run Non-Natural Zombies, Deathsquad, or Non–evac borne ERT, CBURN etc. Administrators may deploy ERT, CBURN, and similar forces in exception of this policy, but only on the evacuation shuttle, and only after request from the station.<br /> * '''Events must meet or exceed our MRP Standard'''. LRP, or NRP events such as “wangvasion” have no place outside of Garbage Day/express Head Game Administrator permission.<br /> * Events are for '''everyone’s''' enjoyment, not just your own.<br /> * Do not run events that are designed to interact with one person in particular, especially your own character.<br /> * '''Events can and will fail, let them'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> * The event should fit within the established lore of the game.<br /> * Unless your created role has a vital part to the event, let your created ghost roles be taken by someone else, not for yourself. You’re here to provide fun scenarios for players, not for yourself.<br /> * Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift. It’s lame to see such things, we want to empower players to tell the story.<br /> * Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room.<br /> * Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> * Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> * Remember to be cooperative with other staff! Work, plan together to make certain dumb ideas into functional, fun things!<br /> * Don’t spawn in a super synth for players. There are some midis that can cause a complete crash.<br /> * Outside of Events, attempt to influence the round as little as possible.<br /> * Fellow ghosts might try to pressure you to do something funny! Just remember, you probably shouldn’t, unless it meets our Event Guidelines!  <br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> <br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> Examples include:<br /> <br /> * Responding to certain faxes as CC.<br /> * Making CC announcements regarding non specific advice.<br /> * Spawning, or modifying a spider during a vent critters event<br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high.<br /> * Making fun, in-world announcements as non CC about certain things.<br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> === Medium Impact ===<br /> <br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * Take note to not overwhelm the station! If the round has particularly active traitors, don’t make it worse for Security!<br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be '''planned out in advance'''. Write out an event plan, with requirements, objectives, goals, etc. <br /> <br /> === High Impact ===<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and '''must be planned in advance'''. '''Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> <br /> '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator<br /> <br /> Examples include:<br /> <br /> * Hellshift <br /> * Rimworld Events<br /> * AI Malfunction<br /> * Central Command Inspections<br /> * Furtive Fugitives - dV Event Plan</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3652 2024-12-10T03:13:32Z

<p>Lyndomen: </p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review. <br /> <br /> === The Roadmap ===<br /> The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> '''Discovery''' - Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> '''Conceptualization''' - Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status.<br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> '''Requirement Gathering''' - After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do?<br /> <br /> '''Solution Design''' - Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite.<br /> <br /> '''Publication''' - At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> === GitHub PR Review ===<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted. Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction'''<br /> <br /> * We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it.<br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> <br /> '''What do you look for in a review?'''<br /> * Fits our MRP Standard - Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun. We want things to make sense to our setting.<br /> * Fits our Design Ethos - Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game.<br /> Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> * Approving for merge<br /> * Test merging<br /> * Requesting changes<br /> * Denying the content<br /> <br /> === Deadlines ===<br /> Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. Deadlines should be relative to the size of the PR.<br /> <br /> * Small PRs should be subject to 1-2 days of consideration.<br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion.<br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author. <br /> <br /> '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> === Test Merging ===<br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> == Community Management ==<br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. Curators listen to what players love (and don't love) about Delta V. They: <br /> <br /> '''Gather Feedback -''' Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. '''Recording Feedback''' is just as critical, talk to the team and bring up problem items!<br /> <br /> '''Solve Problems -''' When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> <br /> '''Use Communication Channels'''<br /> <br /> * '''Announcements -''' The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> * '''Polls and Surveys -''' Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> * '''Public Forums -''' Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> * '''Changelog -''' The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> * '''GitHub -''' By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> '''Events that Rock:''' Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> <br /> * Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run the following events:<br /> <br /> * Non-Natural Zombies, Deathsquad, or Non–evac borne ERT, CBURN etc<br /> * Administrators may deploy ERT, CBURN, and similar forces in exception of this policy, but only on the evacuation shuttle, and only after request from the station. ''See Event Policy, Medium Impact events.'' <br /> <br /> * '''Events must meet or exceed our MRP Standard'''. LRP, or NRP events such as “wangvasion” have no place outside of Garbage Day/express Head Game Administrator permission.<br /> * Events are for '''everyone’s''' enjoyment, not just your own.<br /> <br /> * Do not run events that are designed to interact with one person in particular, especially your own character.<br /> * '''Events can and will fail, let them'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> * The event should fit within the established lore of the game. <br /> * Unless your created role has a vital part to the event, let your created ghost roles be taken by someone else, not for yourself. You’re here to provide fun scenarios for players, not for yourself.<br /> * Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift. It’s lame to see such things, we want to empower players to tell the story. <br /> * Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room.<br /> * Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> * Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> * Remember to be cooperative with other staff! Work, plan together to make certain dumb ideas into functional, fun things!<br /> * Don’t spawn in a super synth for players. There are some midis that can cause a complete crash. <br /> * Outside of Events, attempt to influence the round as little as possible. <br /> * Fellow ghosts might try to pressure you to do something funny! Just remember, you probably shouldn’t, unless it meets our Event Guidelines!  <br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> <br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> Examples include:<br /> <br /> * Responding to certain faxes as CC.<br /> * Making CC announcements regarding non specific advice.<br /> * Spawning, or modifying a spider during a vent critters event<br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high.<br /> * Making fun, in-world announcements as non CC about certain things.<br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> === Medium Impact ===<br /> <br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * Take note to not overwhelm the station! If the round has particularly active traitors, don’t make it worse for Security!<br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be '''planned out in advance'''. Write out an event plan, with requirements, objectives, goals, etc. <br /> <br /> === High Impact ===<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and '''must be planned in advance'''. '''Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> <br /> '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator<br /> <br /> Examples include:<br /> <br /> * Hellshift <br /> * Rimworld Events<br /> * AI Malfunction<br /> * Central Command Inspections<br /> * Furtive Fugitives - dV Event Plan</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3651 2024-12-10T03:00:40Z

<p>Lyndomen: </p> <hr /> <div>=== Overview &amp; Welcome ===<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> === '''Important Note!''' ===<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in!<br /> <br /> === Code of Conduct ===<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination.<br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole.<br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves.<br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> === Job Requirements ===<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion.<br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game.<br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer.<br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> == Content Management ==<br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a '''Proactive''' and a '''Reactive''' manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. <br /> <br /> === The Roadmap ===<br /> <br /> * The Roadmap operates over a few stages.  Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> ==== Discovery ====<br /> Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. For more details, refer to Community Management<br /> <br /> ==== Conceptualization ====<br /> Through Discovery, rank Concepts by the following metrics. This is done privately in the #roadmap-development forum, with each Concept having the relevant tags as to its status. <br /> <br /> * Content Impact - Is the content aligned with the Mission of Delta V?<br /> * Technical Feasibility - What technical skills are needed to complete this project?<br /> * How can it be broken up into constituent groups?<br /> * Community Interest - Is the community interested in this specific idea? Is this something they would take kindly to?<br /> * Direction Priority - How necessary does the direction team believe this is? Are there external pressures pushing for this?<br /> <br /> ==== Requirement Gathering ====<br /> After ranking of Concepts, the Curators should itemize out the following Requirements, with as much detail as possible:<br /> <br /> * What does this Concept seek to do?<br /> * What problems does it address?<br /> * What should it do? <br /> <br /> === Solution Design ===<br /> Curators should then iterate on the Requirements gathered, and develop the Solution Design. For every requirement:<br /> <br /> * Determine what could be done to resolve this requirement.<br /> * Itemize these into Tasks, as granular as possible. Are sprites needed? Add a task for a specific sprite. <br /> <br /> === Publication ===<br /> At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review.<br /> <br /> == GitHub PR Review ==<br /> All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github.<br /> <br /> Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns.<br /> <br /> * Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction.<br /> ** We don’t want to review things that our voice is not relevant to! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it. <br /> ** Minor bug fixes, obvious simple tweaks, and so forth do not require official review<br /> * Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, '''content can always be reverted.'''<br /> ** '''What do you look for in a review?'''<br /> *** Fits our MRP Standard <br /> **** Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun.We want things to make sense to our setting.<br /> *** Fits our Design Ethos. <br /> **** Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game. <br /> * Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include:<br /> ** Approving for merge<br /> ** Test merging<br /> ** Requesting changes<br /> ** Denying the content<br /> <br /> == Deadlines ==<br /> <br /> * Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review.<br /> * Deadlines should be relative to the size of the PR. <br /> ** Small PRs should be subject to 1-2 days of consideration. <br /> ** Major PRs may need as many as 1-2 weeks to reach an actionable conclusion. <br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author.<br /> <br /> * '''If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged'''. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> == Test Merging ==<br /> <br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary.<br /> * Test merges should be for short periods of time (24 - 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content.<br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on.<br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content.<br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> Community Management<br /> <br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. <br /> <br /> '''The Voice of the Players''': Curators listen to what players love (and don't love) about Delta V. They:<br /> <br /> * '''Gather Feedback'''<br /> ** Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V.<br /> ** '''Recording Feedback''' is just as critical, talk to the team and bring up problem items! <br /> * '''Solve Problems'''<br /> ** When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution.<br /> * '''Use Communication Channels'''<br /> ** '''Announcements'''<br /> *** The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy.<br /> ** '''Polls and Surveys'''<br /> *** Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased.<br /> ** '''Public Forums'''<br /> *** Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback.<br /> ** '''Changelog'''<br /> *** The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful.<br /> ** '''GitHub'''<br /> *** By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> == Event Management ==<br /> '''Events that Rock:''' Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> '''Events must be reported.''' Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> <br /> * Unless given '''express permission''' by a Project Manager or the Game Director, do NOT run the following events:<br /> <br /> * Non-Natural Zombies, Deathsquad, or Non–evac borne ERT, CBURN etc<br /> * Administrators may deploy ERT, CBURN, and similar forces in exception of this policy, but only on the evacuation shuttle, and only after request from the station. ''See Event Policy, Medium Impact events.'' <br /> <br /> * '''Events must meet or exceed our MRP Standard'''. LRP, or NRP events such as “wangvasion” have no place outside of Garbage Day/express Head Game Administrator permission.<br /> * Events are for '''everyone’s''' enjoyment, not just your own.<br /> <br /> * Do not run events that are designed to interact with one person in particular, especially your own character.<br /> * '''Events can and will fail, let them'''. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen.<br /> * The event should fit within the established lore of the game. <br /> * Unless your created role has a vital part to the event, let your created ghost roles be taken by someone else, not for yourself. You’re here to provide fun scenarios for players, not for yourself.<br /> * Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift. It’s lame to see such things, we want to empower players to tell the story. <br /> * Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room.<br /> * Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable.<br /> * Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities.<br /> * Remember to be cooperative with other staff! Work, plan together to make certain dumb ideas into functional, fun things!<br /> * Don’t spawn in a super synth for players. There are some midis that can cause a complete crash. <br /> * Outside of Events, attempt to influence the round as little as possible. <br /> * Fellow ghosts might try to pressure you to do something funny! Just remember, you probably shouldn’t, unless it meets our Event Guidelines!  <br /> <br /> '''Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the #events channel.'''<br /> <br /> === Low Impact ===<br /> <br /> * Events in this category may be at Curator discretion, in moderation.<br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in.<br /> ** Curators  have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things ''strange.'' Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> <br /> Examples include:<br /> <br /> * Responding to certain faxes as CC.<br /> * Making CC announcements regarding non specific advice.<br /> * Spawning, or modifying a spider during a vent critters event<br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high.<br /> * Making fun, in-world announcements as non CC about certain things.<br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> === Medium Impact ===<br /> <br /> * Events in this category may be run at Curator discretion in moderation, but '''should be approved by a Curator first.'''<br /> * Take note to not overwhelm the station! If the round has particularly active traitors, don’t make it worse for Security!<br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be '''planned out in advance'''. Write out an event plan, with requirements, objectives, goals, etc. <br /> <br /> === High Impact ===<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and '''must be planned in advance'''. '''Write out an event plan, with requirements, objectives, goals, etc.''' <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards.<br /> <br /> '''Do not run these events solo.'''  You should be working together with a team of Curators(at least 2-3 minimum).  Ask for help in #events, or ping @Curator<br /> <br /> Examples include:<br /> <br /> * Hellshift <br /> * Rimworld Events<br /> * AI Malfunction<br /> * Central Command Inspections<br /> * Furtive Fugitives - dV Event Plan</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3650 2024-12-10T02:47:28Z

<p>Lyndomen: </p> <hr /> <div>= Overview &amp; Welcome =<br /> Hello! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do\! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities <br /> <br /> **Important Note!<br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in\!<br /> <br /> # Code of Conduct<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination. <br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole. <br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves. <br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> # Job Requirements<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion. <br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game. <br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer. <br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> # Content Management<br /> <br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a **Proactive** and a **Reactive** manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. <br /> <br /> ## The Roadmap<br /> <br /> The Roadmap operates over a few stages. Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> 1. Discovery <br /> 1. Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. <br /> 2. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. <br /> 3. For more details, refer to Community Management <br /> 2. Conceptualization <br /> 1. Through Discovery, rank Concepts by the following metric. <br /> 1. Content Impact <br /> 1. Is the content aligned with the Mission of Delta V? <br /> 2. Technical Feasibility <br /> 1. What technical skills are needed to complete this project? <br /> 2. How can it be broken up into constituent groups? <br /> 3. Community Interest <br /> 1. Is the community interested in this specific idea? Is this something they would take kindly to? <br /> 4. Direction Priority <br /> 1. How necessary does the direction team believe this is? Are there external pressures pushing for this? <br /> 2. This is done privately in the \#roadmap-development forum, with each Concept having the relevant tags as to its status. <br /> 3. Requirement Gathering <br /> 1. After ranking of Concepts, the Curators should itemize out the following **Requirements**, with as much detail as possible: <br /> 1. What does this Concept seek to do? <br /> 2. What problems does it address? <br /> 3. What should it do? <br /> 4. Solution Design <br /> 1. Curators should then iterate on the Requirements gathered, and develop the Solution Design <br /> 1. For every requirement: <br /> 1. Determine what could be done to resolve this requirement. <br /> 2. Itemize these into Tasks, as granularly as possible. Are sprites needed? Add a task for a specific sprite. <br /> 5. Publication <br /> 1. At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review.<br /> <br /> ## GitHub PR Review<br /> <br /> * All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. <br /> * Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. <br /> * Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction. <br /> * We don’t want to review things that our voice is not relevant to\! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it. <br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review <br /> * Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, **content can always be reverted.** <br /> * **What do you look for in a review?** <br /> * Fits our MRP Standard <br /> * Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun.We want things to make sense to our setting. <br /> * Fits our Design Ethos. <br /> * Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game. <br /> * Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include: <br /> * Approving for merge <br /> * Test merging <br /> * Requesting changes <br /> * Denying the content<br /> <br /> ## Deadlines<br /> <br /> * Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. <br /> * Deadlines should be relative to the size of the PR. <br /> * Small PRs should be subject to 1-2 days of consideration. <br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion. <br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author.<br /> <br /> * **If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged**. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> ## Test Merging<br /> <br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary. <br /> * Test merges should be for short periods of time (24 \- 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content. <br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on. <br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content. <br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> # Community Management<br /> <br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. <br /> <br /> **The Voice of the Players**: Curators listen to what players love (and don't love) about Delta V. They:<br /> <br /> * **Gather Feedback** <br /> * Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. <br /> * **Recording Feedback** is just as critical, talk to the team and bring up problem items\! <br /> * **Solve Problems** <br /> * When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution. <br /> * **Use Communication Channels** <br /> * **Announcements** <br /> * The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy. <br /> * **Polls and Surveys** <br /> * Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased. <br /> * **Public Forums** <br /> * Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback. <br /> * **Changelog** <br /> * The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful. <br /> * **GitHub** <br /> * By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> # Event Management<br /> <br /> **Events that Rock:** Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event\! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> **Events must be reported.** Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> <br /> * Unless given **express permission** by a Project Manager or the Game Director, do NOT run the following events: <br /> * Non-Natural Zombies <br /> * Non–evac borne ERT, CBURN etc <br /> * Administrators may deploy ERT, CBURN, and similar forces in exception of this policy, but only on the evacuation shuttle, and only after request from the station. *See Event Policy, Medium Impact events.* <br /> * Deathsquad <br /> * **Events must meet or exceed our MRP Standard**. LRP, or NRP events such as “wangvasion” have no place outside of Garbage Day/express Head Game Administrator permission. <br /> * Events are for **everyone’s** enjoyment, not just your own. <br /> * Do not run events that are designed to interact with one person in particular, especially your own character. <br /> * **Events can and will fail, let them**. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen. <br /> * The event should fit within the established lore of the game. <br /> * Unless your created role has a vital part to the event, let your created ghost roles be taken by someone else, not for yourself. You’re here to provide fun scenarios for players, not for yourself. <br /> * Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift. It’s lame to see such things, we want to empower players to tell the story. <br /> * Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. <br /> * Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable. <br /> * Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities. <br /> * Remember to be cooperative with other staff\! Work, plan together to make certain dumb ideas into functional, fun things\! <br /> * Don’t spawn in a super synth for players. There are some midis that can cause a complete crash. <br /> * Outside of Events, attempt to influence the round as little as possible. <br /> * Fellow ghosts might try to pressure you to do something funny\! Just remember, you probably shouldn’t, unless it meets our Event Guidelines\! <br /> <br /> <br /> **Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the \#events channel.**<br /> <br /> ## Low Impact <br /> <br /> * Events in this category may be at Curator discretion, in moderation. <br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in. <br /> * Curators have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things *strange.* Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> * Examples include: <br /> * Responding to certain faxes as CC. <br /> * Making CC announcements regarding non specific advice. <br /> * Spawning, or modifying a spider during a vent critters event <br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high. <br /> * Making fun, in-world announcements as non CC about certain things. <br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> ## Medium Impact<br /> <br /> * Events in this category may be run at admin discretion in moderation, but **should be approved by a Curator first.** <br /> * Take note to not overwhelm the station\! If the round has particularly active traitors, don’t make it worse for Security\! <br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be **planned out in advance**. Write out an event plan, with requirements, objectives, goals, etc. <br /> * Medium Impact events that are “Approved” may be repeated at will by any Curator with sufficient permissions. A list of current “Approved” events are as follows: <br /> * [Recurring Fugitives - dV Event Plan](https://docs.google.com/document/u/4/d/1m2A2gEZfg3qqMkuRLgIx22GlLJPyVe1nPpbZ3BNJ9XA/edit) <br /> * [DV Shuttle Visits](https://docs.google.com/document/d/1qVnsqPGpnW8NViUiodeeL_3fGJxWEjJaRh57u2kJZOo/edit) <br /> * [DV Event Plan - AstraWing Trading Shuttle](https://docs.google.com/document/d/1WlpeZK1KlqNOVbr6XLxWKxi7GbjMoKeJ8I3GQukR-Jc/edit#heading=h.bs762xmi2v6z) <br /> * [Syndicate Sponsorship](https://docs.google.com/document/d/1fMxz22QMplRJP8Vmv4KXioPzEnAeRZTBft6-_moHgHQ/edit) \- Nukies/Traitor only <br /> * [DV Event Plan - AstraWing Trading Shuttle](https://docs.google.com/document/d/1WlpeZK1KlqNOVbr6XLxWKxi7GbjMoKeJ8I3GQukR-Jc/edit#heading=h.bs762xmi2v6z) <br /> * [Central Command Inspection Delta-V](https://docs.google.com/document/d/1yzqR2_TYyXIfaXXAKN2xnBQX-ttDDiXfYun2GVMhzNg/edit#heading=h.dnf3tpd4naqz) <br /> * [DV Self Destruct Procedure](https://docs.google.com/document/d/1dZdVfVW92GQyGyafDJgVo7FmHEa2HzIzaN4YR1HBIgA/edit) <br /> * Central Command Interns <br /> * ERT on Evac <br /> * Offering custom syndicate objectives <br /> * [Recurring CC Visits - dV Event Plan](https://docs.google.com/document/d/1twBFz50SlASRCLjtnvUI5aXLWuuWTSri3r6hVn4tx2o/edit)<br /> <br /> ## High Impact<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and **must be planned in advance**. **Write out an event plan, with requirements, objectives, goals, etc.** <br /> * High Impact events that are “Approved” may be repeated by any administrator with sufficient permissions. A list of current “Approved” events are as follows: <br /> * [Furtive Fugitives - dV Event Plan](https://docs.google.com/document/d/1T1lDf-zEuFTmyYJdlw4zMilj_j_2BKJCdcPmmFiq3UM/edit) <br /> * [Pandemic Survivors Event](https://docs.google.com/document/d/1OCUctd4as4XhFW98dsZ6zUeoSQbMUSX1F4fhjqciUK4/edit?pli=1) \*Headmin approval required <br /> * [Contagion - dV Event Plan](https://docs.google.com/document/d/1SjCmO5ZlW7T7Wgum6dIs-yp3BeHWo7qkGRcVqTsA4QU/edit) \*Headmin approval required <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards. <br /> * **Do not run these events solo.** You should be working together with a team of Curators(at least 2-3 minimum). Ask for help in \#events, or ping @Curator <br /> * Examples include: <br /> * Hellshift <br /> * Rimworld Events <br /> * AI Malfunction <br /> * Central Command Inspections <br /> * [Furtive Fugitives - dV Event Plan](https://docs.google.com/document/d/1T1lDf-zEuFTmyYJdlw4zMilj_j_2BKJCdcPmmFiq3UM/edit)</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Direction_Guidelines&diff=3649 2024-12-10T02:46:42Z

<p>Lyndomen: wow</p> <hr /> <div># Direction Guidelines<br /> <br /> Prepared by the Direction team as of December 9th, 2024<br /> <br /> # Overview &amp; Welcome<br /> <br /> Hello\! Welcome to the team, where we professionally wyci things. We’ve got a LOT on our plate, as the pseudo development team sans developers. Below you’ll read about our positions, what we do, and what we don’t do\! You will find best practices, what to expect, and how we can do better in the future. This will be an evolving and public document; we strive to work with the people in all capacities. <br /> <br /> **Important Note\!** <br /> We know your time is valuable. We'll make sure roadmap plans are clear, easy to understand, and broken down into manageable tasks. You can choose what you want to work on. Your contributions are what make Delta V special, and we appreciate every bit of effort you put in\!<br /> <br /> # Code of Conduct<br /> <br /> * Always treat fellow players, staff members, and developers with kindness and consideration. Respect their opinions, even if they differ from your own. Refrain from using offensive language, personal attacks, or any form of discrimination. <br /> * Collaborate effectively with others, both OOC and in Discord. Be willing to compromise and work together towards common goals. Support your fellow player and server staff, and always prioritize the well-being of the community as a whole. <br /> * Maintain an approachable demeanor, encouraging players to reach out and share their thoughts and concerns. Listen actively to others, show empathy, and respond with respect. Foster a positive and inclusive environment where everyone feels comfortable expressing themselves. <br /> * When participating in discussions, ensure that they remain respectful and constructive. Ask for clarification and purpose when someone posts something vague or unclear. Encourage participants to provide evidence, sources, and examples to support their arguments.<br /> <br /> # Job Requirements<br /> <br /> * You understand the intricacies of the game. This knowledge enables you to make informed decisions, solve problems creatively, and lend an expert opinion. <br /> * You possess excellent communication skills through writing. You excel at explaining complex concepts clearly and concisely, making it easier for others to understand and engage with the game. <br /> * You are passionate about the game and appreciate the balance between action-packed moments and immersive roleplay opportunities that Delta V seeks to offer. <br /> * You are an active member of the Delta V community, regularly contributing to productive discussions.<br /> <br /> # Content Management<br /> <br /> One of the Direction’s main goals is to oversee the curation of content for the Delta-V community. To accomplish this, Direction operates in a **Proactive** and a **Reactive** manner. Proactively, they create the Roadmap to indicate what Direction would like to see developed. Reactively, they curate the content submitted to ensure it meets the mission of Delta V. <br /> <br /> ## The Roadmap<br /> <br /> The Roadmap operates over a few stages. Concepts on the Roadmap will be selected by the Direction team privately, and the ideas will be established to some level of certainty before being opened to community feedback. Concepts may be highly specific, or rather broad, as long as they have a solid final goal that Direction can guide contributors towards.<br /> <br /> 1. Discovery <br /> 1. Curators spend time in Discord channels, forums, and in-game, paying attention to what players are discussing, what they enjoy, and what challenges they face. <br /> 2. They monitor dedicated feedback channels, collate suggestions, and identify recurring themes or requests. <br /> 3. For more details, refer to Community Management <br /> 2. Conceptualization <br /> 1. Through Discovery, rank Concepts by the following metric. <br /> 1. Content Impact <br /> 1. Is the content aligned with the Mission of Delta V? <br /> 2. Technical Feasibility <br /> 1. What technical skills are needed to complete this project? <br /> 2. How can it be broken up into constituent groups? <br /> 3. Community Interest <br /> 1. Is the community interested in this specific idea? Is this something they would take kindly to? <br /> 4. Direction Priority <br /> 1. How necessary does the direction team believe this is? Are there external pressures pushing for this? <br /> 2. This is done privately in the \#roadmap-development forum, with each Concept having the relevant tags as to its status. <br /> 3. Requirement Gathering <br /> 1. After ranking of Concepts, the Curators should itemize out the following **Requirements**, with as much detail as possible: <br /> 1. What does this Concept seek to do? <br /> 2. What problems does it address? <br /> 3. What should it do? <br /> 4. Solution Design <br /> 1. Curators should then iterate on the Requirements gathered, and develop the Solution Design <br /> 1. For every requirement: <br /> 1. Determine what could be done to resolve this requirement. <br /> 2. Itemize these into Tasks, as granularly as possible. Are sprites needed? Add a task for a specific sprite. <br /> 5. Publication <br /> 1. At this stage, Direction will share the Solution Design with the public, contained within the global Roadmap. The processes for gathering community feedback are outlined in the Community Management Guidelines. Direction should use this feedback to flesh out Roadmap ideas and finalize them for contributors who wish to begin development.<br /> <br /> Direction should keep up with the development of these features and offer feedback along the way. Direction guidance ensures that Roadmap content will be developed to the best quality possible and reduce the number of changes that need to be made after the content is presented for official review.<br /> <br /> ## GitHub PR Review<br /> <br /> * All gameplay content will be processed through the Delta-V Github. Reviewing suggested content involves examining current Pull Requests (“PRs”) and providing feedback through Github. <br /> * Maintainers have final authority when it comes to the fitness of the PR in terms of code quality and potential bugs or other mechanical concerns. <br /> * Maintainers and Curators will ensure that Direction is reviewing items that fall within the purview of Direction. <br /> * We don’t want to review things that our voice is not relevant to\! Does it meaningfully affect game design, balance, or roleplay? If not, we can let them know we are not needed to approve it. <br /> * Minor bug fixes, obvious simple tweaks, and so forth do not require official review <br /> * Content review should always involve as many members of Direction as possible, but if only one or two choose to comment on a piece of content, their opinion holds the same weight as the entire team. If the rest of the team comes to a different decision at a later time, **content can always be reverted.** <br /> * **What do you look for in a review?** <br /> * Fits our MRP Standard <br /> * Keeps the balance between action and roleplay, no overpowered stuff or things that break the fun.We want things to make sense to our setting. <br /> * Fits our Design Ethos. <br /> * Delta-V is a server founded in analogue design. We want this to be displayed in all the PRs we merge, such that it fits cohesively in the mechanical narrative of the game. <br /> * Direction may discuss the merits of the content internally, but any final decisions must be communicated to the content author through Github. Typical decisions include: <br /> * Approving for merge <br /> * Test merging <br /> * Requesting changes <br /> * Denying the content<br /> <br /> ## Deadlines<br /> <br /> * Directions is a volunteer team. Direction approval is still a requirement for a large portion of new content. In order to prevent bottlenecks and an overall stagnation in new content, deadlines will be enforced for PR Review. <br /> * Deadlines should be relative to the size of the PR. <br /> * Small PRs should be subject to 1-2 days of consideration. <br /> * Major PRs may need as many as 1-2 weeks to reach an actionable conclusion. <br /> <br /> Deadlines should be established relative to whenever the PR is “finalized.” If changes are requested by Direction, the deadline should be extended to the proper amount of time after those changes are implemented by the author.<br /> <br /> * **If Direction does not come to a conclusion by the end of the deadline, the PR is to be automatically merged**. The intent of this policy is to prevent PRs from sitting unattended for large quantities of time due to Direction inactivity.<br /> <br /> ## Test Merging<br /> <br /> * Direction’s goal of facilitating change should not be stifled by concerns over the unknown implications of permanently merging any PR. As such, the team is encouraged to temporarily merge PRs whose merits need to be tested. The content can easily be reverted if it is deemed unnecessary. <br /> * Test merges should be for short periods of time (24 \- 48 hours), and should be supervised by members of Direction to gather information on the quality of the merge. Direction members are authorized to manipulate rounds in accordance with Event Management Guidelines in order to test new content. <br /> * If Direction members cannot adequately monitor test merges, you may not test merges. A test merge unmonitored provides no actual data for Direction to base decisions on. <br /> * Additionally in line with Community Management Policy, players should be able to view the current test merges at all times, and be made aware of the general fact that Delta-V uses test merges to analyze content. <br /> * Some test merge content can be reported on by the community, and feedback can be collected according to Community Management Policy.<br /> <br /> # Community Management<br /> <br /> Through Community Management, Direction interacts with the community of Delta V. Our mission is done to serve them, and we work to encourage their assistance in upholding this mission. It is our responsibility to act responsibly and with respect. <br /> <br /> **The Voice of the Players**: Curators listen to what players love (and don't love) about Delta V. They:<br /> <br /> * **Gather Feedback** <br /> * Curators actively seek out feedback from players through various channels such as surveys, polls, and direct communication. This feedback is essential for identifying areas of improvement and making informed decisions about the future of Delta V. <br /> * **Recording Feedback** is just as critical, talk to the team and bring up problem items\! <br /> * **Solve Problems** <br /> * When players encounter issues or concerns, curators are there to help. They provide guidance, troubleshoot problems, and escalate issues to the appropriate team members for resolution. <br /> * **Use Communication Channels** <br /> * **Announcements** <br /> * The announcements channel is used to share important updates, server news, event information, and roadmap changes. Announcements must be carefully coordinated with the rest of the team to ensure consistency and accuracy. <br /> * **Polls and Surveys** <br /> * Polls and surveys are conducted to gather community feedback on specific topics, gauge interest in potential features, and involve players in decision-making processes. Curators recognize that polls and surveys can also yield uneducated opinions, so they work closely with the team to ensure that questions are clearly worded and unbiased. <br /> * **Public Forums** <br /> * Open forums provide a platform for Direction to speak directly to the community about upcoming changes and get community buy-in for specific ideas. These forums allow for more focused discussions and enable the team to gather valuable insights and feedback. <br /> * **Changelog** <br /> * The in-game changelog can also be used to share important information with players. Many of our players do not use or check Discord, and elaborating on new features, and bug fixes can be helpful. <br /> * **GitHub** <br /> * By leveraging GitHub issues and pull requests, maintainers, contributors, and Curators can collaborate effectively, share ideas, and discuss changes.<br /> <br /> The roadmap on GitHub plays a crucial role in this communication process. It provides a transparent and accessible overview of the project's goals, priorities, and planned features. By regularly updating the roadmap, Curators can keep contributors informed about where efforts are needed and help align their efforts with the overall mission.<br /> <br /> # Event Management<br /> <br /> **Events that Rock:** Curators design exciting in-game events that encourage awesome roleplay. An event is loosely defined as “taking an action that influences the game as an observer”. Spawning in a spider, or working to establish a custom Syndicate objective would be an event\! They, by design, are to give opportunities to spice up regular shifts, providing players with unique roleplay scenarios, which they can react to naturally.<br /> <br /> **Events must be reported.** Be robust in your event reporting, especially when giving usually unobtainable items. Be descriptive and attach images or screenshots whenever possible.<br /> <br /> * Unless given **express permission** by a Project Manager or the Game Director, do NOT run the following events: <br /> * Non-Natural Zombies <br /> * Non–evac borne ERT, CBURN etc <br /> * Administrators may deploy ERT, CBURN, and similar forces in exception of this policy, but only on the evacuation shuttle, and only after request from the station. *See Event Policy, Medium Impact events.* <br /> * Deathsquad <br /> * **Events must meet or exceed our MRP Standard**. LRP, or NRP events such as “wangvasion” have no place outside of Garbage Day/express Head Game Administrator permission. <br /> * Events are for **everyone’s** enjoyment, not just your own. <br /> * Do not run events that are designed to interact with one person in particular, especially your own character. <br /> * **Events can and will fail, let them**. Be it a syndicate dropping event characters dead, bombing or stealing shuttles, command arresting event characters, let it happen. <br /> * The event should fit within the established lore of the game. <br /> * Unless your created role has a vital part to the event, let your created ghost roles be taken by someone else, not for yourself. You’re here to provide fun scenarios for players, not for yourself. <br /> * Do not make ghost roles that are overpowered, or that are intended to be “the protagonist” of the shift. It’s lame to see such things, we want to empower players to tell the story. <br /> * Feel free to spawn, test things/ideas or doing silly shenanigans in your admin room. <br /> * Spawning in a bunch of ghost roles to do a gag, build some ship/station, play poker or etc., that generally have NO impact on the current shift, is acceptable. <br /> * Don’t spawn things that could affect glimmer, make people traitor objectives or some other round ending entities. <br /> * Remember to be cooperative with other staff\! Work, plan together to make certain dumb ideas into functional, fun things\! <br /> * Don’t spawn in a super synth for players. There are some midis that can cause a complete crash. <br /> * Outside of Events, attempt to influence the round as little as possible. <br /> * Fellow ghosts might try to pressure you to do something funny\! Just remember, you probably shouldn’t, unless it meets our Event Guidelines\! <br /> <br /> <br /> **Events fall into three broad categories, each with different qualifications and actions required. All events must be reported in the \#events channel.**<br /> <br /> ## Low Impact <br /> <br /> * Events in this category may be at Curator discretion, in moderation. <br /> * By nature, they do not impact the round in any meaningful way and potentially could be mistaken as an in-game event, rather than a curator spawned one in. <br /> * Curators have leeway to run nigh unlimited amounts of Low Impact events when Glimmer reaches 900+, including some Medium Impact events. Make items sapient, shrink things, make things *strange.* Keep your actions within the lore of the game. Feel free to ping the Game Director for additional questions. <br /> * Examples include: <br /> * Responding to certain faxes as CC. <br /> * Making CC announcements regarding non specific advice. <br /> * Spawning, or modifying a spider during a vent critters event <br /> * Making something that normally isn't sentient, sentient when the glimmer is abnormally high. <br /> * Making fun, in-world announcements as non CC about certain things. <br /> * Answering prayers ( what item was given, if it was actually given).<br /> <br /> ## Medium Impact<br /> <br /> * Events in this category may be run at admin discretion in moderation, but **should be approved by a Curator first.** <br /> * Take note to not overwhelm the station\! If the round has particularly active traitors, don’t make it worse for Security\! <br /> * Medium Impact events may interfere with the crew, but should generally not provide the opportunity to derail the station, or round remove players. <br /> * Medium Impact events should be **planned out in advance**. Write out an event plan, with requirements, objectives, goals, etc. <br /> * Medium Impact events that are “Approved” may be repeated at will by any Curator with sufficient permissions. A list of current “Approved” events are as follows: <br /> * [Recurring Fugitives - dV Event Plan](https://docs.google.com/document/u/4/d/1m2A2gEZfg3qqMkuRLgIx22GlLJPyVe1nPpbZ3BNJ9XA/edit) <br /> * [DV Shuttle Visits](https://docs.google.com/document/d/1qVnsqPGpnW8NViUiodeeL_3fGJxWEjJaRh57u2kJZOo/edit) <br /> * [DV Event Plan - AstraWing Trading Shuttle](https://docs.google.com/document/d/1WlpeZK1KlqNOVbr6XLxWKxi7GbjMoKeJ8I3GQukR-Jc/edit#heading=h.bs762xmi2v6z) <br /> * [Syndicate Sponsorship](https://docs.google.com/document/d/1fMxz22QMplRJP8Vmv4KXioPzEnAeRZTBft6-_moHgHQ/edit) \- Nukies/Traitor only <br /> * [DV Event Plan - AstraWing Trading Shuttle](https://docs.google.com/document/d/1WlpeZK1KlqNOVbr6XLxWKxi7GbjMoKeJ8I3GQukR-Jc/edit#heading=h.bs762xmi2v6z) <br /> * [Central Command Inspection Delta-V](https://docs.google.com/document/d/1yzqR2_TYyXIfaXXAKN2xnBQX-ttDDiXfYun2GVMhzNg/edit#heading=h.dnf3tpd4naqz) <br /> * [DV Self Destruct Procedure](https://docs.google.com/document/d/1dZdVfVW92GQyGyafDJgVo7FmHEa2HzIzaN4YR1HBIgA/edit) <br /> * Central Command Interns <br /> * ERT on Evac <br /> * Offering custom syndicate objectives <br /> * [Recurring CC Visits - dV Event Plan](https://docs.google.com/document/d/1twBFz50SlASRCLjtnvUI5aXLWuuWTSri3r6hVn4tx2o/edit)<br /> <br /> ## High Impact<br /> <br /> * Provide at least a 4 hour notice before it starts. Additionally, notify the Patreon Event Notifications channel. <br /> * The type of round will heavily influence the feasibility of this category of event. You may have to force extended or survival in the pre-round lobby. <br /> * Use “setgamepreset” to do so. Once the round has started, run “setgamepreset secret” to fix it for future rounds. <br /> * High Impact events WILL interfere with the crew, and **must be planned in advance**. **Write out an event plan, with requirements, objectives, goals, etc.** <br /> * High Impact events that are “Approved” may be repeated by any administrator with sufficient permissions. A list of current “Approved” events are as follows: <br /> * [Furtive Fugitives - dV Event Plan](https://docs.google.com/document/d/1T1lDf-zEuFTmyYJdlw4zMilj_j_2BKJCdcPmmFiq3UM/edit) <br /> * [Pandemic Survivors Event](https://docs.google.com/document/d/1OCUctd4as4XhFW98dsZ6zUeoSQbMUSX1F4fhjqciUK4/edit?pli=1) \*Headmin approval required <br /> * [Contagion - dV Event Plan](https://docs.google.com/document/d/1SjCmO5ZlW7T7Wgum6dIs-yp3BeHWo7qkGRcVqTsA4QU/edit) \*Headmin approval required <br /> * High Impact events should be carefully examined to ensure they meet or exceed our MRP standards. <br /> * **Do not run these events solo.** You should be working together with a team of Curators(at least 2-3 minimum). Ask for help in \#events, or ping @Curator <br /> * Examples include: <br /> * Hellshift <br /> * Rimworld Events <br /> * AI Malfunction <br /> * Central Command Inspections <br /> * [Furtive Fugitives - dV Event Plan](https://docs.google.com/document/d/1T1lDf-zEuFTmyYJdlw4zMilj_j_2BKJCdcPmmFiq3UM/edit)</div>

Lyndomen https://wiki.deltav.gay/index.php?title=How_to_contribute&diff=3637 2024-11-11T14:40:39Z

<p>Lyndomen: helpful picture from https://imgs.xkcd.com/comics/duty_calls_2x.png</p> <hr /> <div>[[File:Duty calls 2x.png|thumb|(xkcd #386)&lt;ref&gt;https://imgs.xkcd.com/comics/duty_calls_2x.png&lt;/ref&gt;]]<br /> <br /> ===== Hello! ===== <br /> Welcome to Lyndomen’s definitive guide on how to contribute to the Delta-V project. I am writing this in secrecy, so don’t be a snitch. <br /> <br /> Firstly, '''contribution takes many forms'''. Not all contributors are technical, some are Administrators, Curators, Documentors, Maintainers, whatever. This is a guide on Technical Contribution (how do I make thing that goes in the game). <br /> <br /> The mood of this guide is going to teach you exactly how to do this without explaining why. I don’t know why either, and it doesn’t matter until you want to get good at contribution. For your first contribution, why doesn’t matter. By writing this entire ass guide, it will also piss people off who do know what they are doing. Then they can suggest things that make this more accurate. <br /> <br /> ===== Getting Started =====<br /> Uh, well, this guide is only for Windows. Sorry Mac users, use [https://www.winehq.org/ Wine] or preferably a better guide. <br /> <br /> # Make an account on [https://github.com/signup?source=login GitHub]. This is where the game files &lt;sub&gt;called a Repository&lt;/sub&gt; are stored on the internet, and thus if you want to submit a change, you gotta have an account. Don’t use your real name please, it’s public.<br /> # Go to this link, and press Fork in the top right. https://github.com/DeltaV-Station/Delta-v &lt;sub&gt;A '''Fork''' is your copy of DeltaV. Name your fork whatever you want, it doesn't matter. The default settings are fine, just make yourself the owner.&lt;/sub&gt; <br /> <br /> Download and install everything here. <br /> * [https://desktop.github.com/download/ GitHub Desktop] is the program that copies the game files down onto your computer. <br /> * [https://www.jetbrains.com/rider/download/#section=windows Rider] is the program you do all the work in<br /> * [https://www.jetbrains.com/toolbox-app/ Rider Toolbox] is the program that keeps Rider updated. I don’t know why it is separate. <br /> * [https://www.python.org/downloads/windows/ Python] is a technical thing. You won't do much with it, but it will make things work secretly. Pick the thing that says “Download Windows installer (64-bit)”<br /> * [https://dotnet.microsoft.com/en-us/download/dotnet/8.0 .NET 8.0] is another technical thing. Pick the thing that says “Windows x64”.<br /> <br /> ===== Setting up Github Desktop =====<br /> # Load up Github Desktop, and log in with your fancy GitHub account. <br /> # When it asks you to pick a repository, select to Clone your fork. It might take a bit. <br /> # Select “to contribute to the parent project” when it's done. <br /> # At the top click “Current branch”, it says master right now. Click New Branch. <br /> # Make a branch with a clever title that somewhat describes your idea. For instance, I might name mine “rework CC”. &lt;sub&gt;A '''branch''' is a copy of your copy of DeltaV. You must work off a branch, so get used to it for every new project.&lt;/sub&gt;<br /> # Once that is all set, click the button that says “Select your editor in Options”. <br /> # Select external editor JetBrains Rider, and select where it got installed. &lt;sub&gt;Mine was at C:\Program Files\JetBrains\JetBrains Rider 2024.2.5\bin&lt;/sub&gt;<br /> # Click Open in JetBrains Rider<br /> <br /> ===== Setting up Rider =====<br /> # It will load for a bit, but will eventually display “Directory ‘FORKNAME’ contains these solutions”, select “SpaceStation14.sln. Trust and Open it.<br /> # Select your branch at the top, switch it from Master to whatever you made earlier. Pressing Checkout on a branch means you are going to edit it!<br /> # Lets test things out. In the top right, select &quot;Content Server+ Client&quot;in Configurations. Edit the configuration and add Content.Server and Content.Client, and save it as a new name. I named mine &quot;Both Things&quot;. Click OK to save the change. <br /> # Click the play button next to Both Things. Your computer should start revving up as it Builds the project. It will take some time, but eventually you will have both the server and client pop up. You can log in to localhost with a username of your choice. <br /> # Press ~ to open the console, and type &quot;fuckrules&quot;. <br /> # You should now be in the developer environment! Play around, and shoot the RPG at a wall. You deserve a break. If you blow it up too bad, type &quot;endround&quot; in the console. <br /> <br /> <br /> ===== Thats all for now folks! =====<br /> The rest is up to you! Get your YML or C# code working nice, and submit it as a Pull Request to the DeltaV repo. I will have more steps for that later!</div>

Lyndomen https://wiki.deltav.gay/index.php?title=File:Duty_calls_2x.png&diff=3636 2024-11-11T14:38:33Z

<p>Lyndomen: </p> <hr /> <div>(xkcd #386)</div>

Lyndomen https://wiki.deltav.gay/index.php?title=How_to_contribute&diff=3635 2024-11-10T19:27:34Z

<p>Lyndomen: new guide real</p> <hr /> <div>===== Hello! ===== <br /> Welcome to Lyndomen’s definitive guide on how to contribute to the Delta-V project. I am writing this in secrecy, so don’t be a snitch. <br /> <br /> Firstly, '''contribution takes many forms'''. Not all contributors are technical, some are Administrators, Curators, Documentors, Maintainers, whatever. This is a guide on Technical Contribution (how do I make thing that goes in the game). <br /> <br /> The mood of this guide is going to teach you exactly how to do this without explaining why. I don’t know why either, and it doesn’t matter until you want to get good at contribution. For your first contribution, why doesn’t matter. By writing this entire ass guide, it will also piss people off who do know what they are doing. Then they can suggest things that make this more accurate. <br /> <br /> ===== Getting Started =====<br /> Uh, well, this guide is only for Windows. Sorry Mac users, use [https://www.winehq.org/ Wine] or preferably a better guide. <br /> <br /> # Make an account on [https://github.com/signup?source=login GitHub]. This is where the game files &lt;sub&gt;called a Repository&lt;/sub&gt; are stored on the internet, and thus if you want to submit a change, you gotta have an account. Don’t use your real name please, it’s public.<br /> # Go to this link, and press Fork in the top right. https://github.com/DeltaV-Station/Delta-v &lt;sub&gt;A '''Fork''' is your copy of DeltaV. Name your fork whatever you want, it doesn't matter. The default settings are fine, just make yourself the owner.&lt;/sub&gt; <br /> <br /> Download and install everything here. <br /> * [https://desktop.github.com/download/ GitHub Desktop] is the program that copies the game files down onto your computer. <br /> * [https://www.jetbrains.com/rider/download/#section=windows Rider] is the program you do all the work in<br /> * [https://www.jetbrains.com/toolbox-app/ Rider Toolbox] is the program that keeps Rider updated. I don’t know why it is separate. <br /> * [https://www.python.org/downloads/windows/ Python] is a technical thing. You won't do much with it, but it will make things work secretly. Pick the thing that says “Download Windows installer (64-bit)”<br /> * [https://dotnet.microsoft.com/en-us/download/dotnet/8.0 .NET 8.0] is another technical thing. Pick the thing that says “Windows x64”.<br /> <br /> ===== Setting up Github Desktop =====<br /> # Load up Github Desktop, and log in with your fancy GitHub account. <br /> # When it asks you to pick a repository, select to Clone your fork. It might take a bit. <br /> # Select “to contribute to the parent project” when it's done. <br /> # At the top click “Current branch”, it says master right now. Click New Branch. <br /> # Make a branch with a clever title that somewhat describes your idea. For instance, I might name mine “rework CC”. &lt;sub&gt;A '''branch''' is a copy of your copy of DeltaV. You must work off a branch, so get used to it for every new project.&lt;/sub&gt;<br /> # Once that is all set, click the button that says “Select your editor in Options”. <br /> # Select external editor JetBrains Rider, and select where it got installed. &lt;sub&gt;Mine was at C:\Program Files\JetBrains\JetBrains Rider 2024.2.5\bin&lt;/sub&gt;<br /> # Click Open in JetBrains Rider<br /> <br /> ===== Setting up Rider =====<br /> # It will load for a bit, but will eventually display “Directory ‘FORKNAME’ contains these solutions”, select “SpaceStation14.sln. Trust and Open it.<br /> # Select your branch at the top, switch it from Master to whatever you made earlier. Pressing Checkout on a branch means you are going to edit it!<br /> # Lets test things out. In the top right, select &quot;Content Server+ Client&quot;in Configurations. Edit the configuration and add Content.Server and Content.Client, and save it as a new name. I named mine &quot;Both Things&quot;. Click OK to save the change. <br /> # Click the play button next to Both Things. Your computer should start revving up as it Builds the project. It will take some time, but eventually you will have both the server and client pop up. You can log in to localhost with a username of your choice. <br /> # Press ~ to open the console, and type &quot;fuckrules&quot;. <br /> # You should now be in the developer environment! Play around, and shoot the RPG at a wall. You deserve a break. If you blow it up too bad, type &quot;endround&quot; in the console. <br /> <br /> <br /> ===== Thats all for now folks! =====<br /> The rest is up to you! Get your YML or C# code working nice, and submit it as a Pull Request to the DeltaV repo. I will have more steps for that later!</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3591 2024-09-28T17:55:13Z

<p>Lyndomen: /* Delta Alert */</p> <hr /> <div>{{Important<br /> |Title=This article is outdated.<br /> |Note=The updated content of this page can be found in the in-game '''Alert Levels''' guidebook accessible using '''NUMPAD 0'''.<br /> |Image=TelescreenBroken.png<br /> |Color=#8B0000<br /> }}<br /> <br /> == &lt;span style=&quot;color:#4f8439;&gt;Green Alert&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Blue Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked. <br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Red Alert&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches and departmental raids may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Violet Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Yellow Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == White Alert ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Epistemics Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel. Psionic insulation recommended for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel, unless affected by a known threat. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; ROE on mindbreaking is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Delta Alert&lt;/span&gt; ==<br /> Emergency alert status. ''The nuclear destruction mechanism has been engaged and station destruction is imminent. All crew aboard the station must attempt to reverse the self-destruct mechanism, if engaged in error. Should reversal prove impossible, evacuate as applicable.<br /> ''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Emergency personnel must expend all efforts to prevent station destruction if engaged in error. Security and Command personnel are to oversee the evacuation of personnel and safe scuttling of the station. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas and HSAs should remain locked.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3590 2024-09-28T17:53:53Z

<p>Lyndomen: /* Gamma Alert */</p> <hr /> <div>{{Important<br /> |Title=This article is outdated.<br /> |Note=The updated content of this page can be found in the in-game '''Alert Levels''' guidebook accessible using '''NUMPAD 0'''.<br /> |Image=TelescreenBroken.png<br /> |Color=#8B0000<br /> }}<br /> <br /> == &lt;span style=&quot;color:#4f8439;&gt;Green Alert&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Blue Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked. <br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Red Alert&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches and departmental raids may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Violet Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Yellow Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == White Alert ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Epistemics Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel. Psionic insulation recommended for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel, unless affected by a known threat. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; ROE on mindbreaking is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Martial law is in effect. Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Threats neutralised by lethal force may be placed in Preservative Stasis until the station alert level is reduced. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to neutralise threats. Lethal force authorised at the discretion of Security personnel, in self-defence, or to effect arrests.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Delta Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Station scuttling is imminent, or there is another existential crisis affecting the station. All crew and passengers must be evacuated as applicable.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3589 2024-09-28T17:26:08Z

<p>Lyndomen: /* White Alert */</p> <hr /> <div>{{Important<br /> |Title=This article is outdated.<br /> |Note=The updated content of this page can be found in the in-game '''Alert Levels''' guidebook accessible using '''NUMPAD 0'''.<br /> |Image=TelescreenBroken.png<br /> |Color=#8B0000<br /> }}<br /> <br /> == &lt;span style=&quot;color:#4f8439;&gt;Green Alert&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Blue Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked. <br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Red Alert&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches and departmental raids may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Violet Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Yellow Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == White Alert ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Epistemics Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Standard stab- and bullet-resistant equipment recommended for Security personnel. Psionic insulation recommended for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel, unless affected by a known threat. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Prepare for detonation of [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; ROE on mindbreaking is lifted and may be performed by the Psionic Mantis or Mystagogue at their discretion.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Delta Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Station scuttling is imminent, or there is another existential crisis affecting the station. All crew and passengers must be evacuated as applicable.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3588 2024-09-28T17:24:49Z

<p>Lyndomen: /* Yellow Alert */</p> <hr /> <div>{{Important<br /> |Title=This article is outdated.<br /> |Note=The updated content of this page can be found in the in-game '''Alert Levels''' guidebook accessible using '''NUMPAD 0'''.<br /> |Image=TelescreenBroken.png<br /> |Color=#8B0000<br /> }}<br /> <br /> == &lt;span style=&quot;color:#4f8439;&gt;Green Alert&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Blue Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked. <br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Red Alert&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches and departmental raids may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Violet Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Yellow Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Engineering Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. EVA protection heavily advised for all personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == White Alert ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying lethal/non-lethal weaponry permitted. Body armour and psionic insulation recommended.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Follow due process. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] permitted for all authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Prepare to dispose of rogue [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimum required force to subdue a target, dependent on threat and compliance. RoE on mindbreaking is lifted.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Delta Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Station scuttling is imminent, or there is another existential crisis affecting the station. All crew and passengers must be evacuated as applicable.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> {{Guides Menu}}</div>

Lyndomen https://wiki.deltav.gay/index.php?title=Alert_Procedure&diff=3587 2024-09-28T17:23:49Z

<p>Lyndomen: /* Violet Alert */</p> <hr /> <div>{{Important<br /> |Title=This article is outdated.<br /> |Note=The updated content of this page can be found in the in-game '''Alert Levels''' guidebook accessible using '''NUMPAD 0'''.<br /> |Image=TelescreenBroken.png<br /> |Color=#8B0000<br /> }}<br /> <br /> == &lt;span style=&quot;color:#4f8439;&gt;Green Alert&lt;/span&gt; ==<br /> The normal operating procedure. ''There is no currently known threat to the ship, nor crew.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#4f8439BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying of long arms disallowed. Standard stab-and bullet-resistant equipment recommended for Security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unbolted and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#416db7;&gt;Blue Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is an ongoing, known, or suspected security threat to the NanoTrasen vessel or its crew, or another significant security emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#416db7BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Head of Security|Head of Station Security]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carry of weaponry permitted for authorised entities. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] locked. <br /> <br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Binary suit sensors recommended at a minimum. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Make emergency internals easily accessible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; non-lethal weapons may be used freely based on threat and compliance.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#a43e3e;&gt;Red Alert&lt;/span&gt; ==<br /> Emergency alert status. ''There are multiple major emergency situations ongoing, or a major security emergency affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a43e3eBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons heavily recommended. Body armour and helmets mandatory for Security personnel, permitted for distribution to authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. Searches and departmental raids may be performed at the discretion of security personnel and without a warrant. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All HSAs should remain locked and under guard. Secure areas unlocked unless affected by known threats.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors mandatory for observation and safety. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with adequate force to safely subdue suspects, dependent on threat and compliance. Lethal force is permitted to effect arrests against evasive targets.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#583ca2;&gt;Violet Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a serious viral outbreak, ongoing major death event, or there is another significant medical emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#583ca2BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Medical Officer]] &gt; Medical Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Issuing of lethal weapons disadvised. Standard stab-and bullet-resistant equipment recommended for Security personnel. Basic PPE highly recommended for all personnel, L3 biohazard gear advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Non-medical personnel should ensure they do not interfere with medical staff, may assist where applicable, obey all applicable orders from medical personnel. Security should seek to aid medical staff in enforcement of quarantine procedures or medical treatment as necessary.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible to all authorized personnel. High Security Areas and areas with an expectation of privacy, such as bedrooms, dorms, or medical treatment facilities, may be locked as needed.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. Full suit sensors heavily advised. EVA suits recommended for emergency responders, functioning internals and PPE heavily advised.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Standard practice.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimal force required; prioritize de-escalation whenever possible.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#999933;&gt;Yellow Alert&lt;/span&gt; ==<br /> Elevated alert status. ''There is a major issue with the atmospheric system, the station has suffered/is about to suffer significant damage, or there is another significant engineering emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#999933BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Chief Engineer]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying disadvised, particularly lethal weaponry. EVA suits recommended.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Follow due process. Non-engineering personnel advised to evacuate affected areas and obey any relevant instructions from engineering personnel. Security should seek to aid engineering staff where possible.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked unless affected by known threats. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] permitted for all authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals recommended for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for orders. EVA suits heavily advised for engineers. Distribute emergency internals to crew. Propose evacuation if damage is irreparable or sufficiently hazardous.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimum required force to subdue a target, dependent on threat and compliance. De-escalation prioritised.<br /> |}<br /> <br /> == White Alert ==<br /> Elevated alert status. ''The station is suffering dangerously high levels of glimmer, there are several active psionic threats, or there is another significant epistemic emergency.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#a6a6a6BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; [[Mystagogue]] &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Open carrying lethal/non-lethal weaponry permitted. Body armour and psionic insulation recommended.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Follow due process. Security and engineering should seek to aid epistemics staff in shutting off glimmer probers, and propose evacuation if glimmer spiral is unrecoverable.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure areas unlocked and accessible. Access to [[Standard_Operating_Procedure#High_Security_Areas|HSAs]] permitted for all authorised personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. Prepare for increased incidents of burn and brain damage.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits recommended for engineers. Prepare to dispose of rogue [[Glimmer#Probers|probers]].<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Engage with minimum required force to subdue a target, dependent on threat and compliance. RoE on mindbreaking is lifted.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#36717d;&gt;Gamma Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Central Command has called the Gamma Alert; the Station is on its last legs, almost everyone is dead, or there is another existential crisis affecting the station.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#36717dBF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> == &lt;span style=&quot;color:#996633;&gt;Delta Alert&lt;/span&gt; ==<br /> Emergency alert status. ''Station scuttling is imminent, or there is another existential crisis affecting the station. All crew and passengers must be evacuated as applicable.''<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 80%; border: 1px solid #000000;&quot;<br /> !style=&quot;text-align:left; width:25%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Condition'''<br /> !style=&quot;text-align:left; width:75%; padding:5px; padding-left:10px; background-color:#996633BF; border: 1px solid #000000;&quot; | '''Description'''<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Chain of Command<br /> | style=&quot;border: 1px solid #000000;&quot; | [[Standard_Operating_Procedure#Captain’s_Authority|CO]] &gt; Security Personnel &gt; Department Heads &gt; Supervisory Roles<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Armoury Policy<br /> | style=&quot;border: 1px solid #000000;&quot; | Full combat-ready kit or as close as possible mandatory for security. Open carry disallowed for non-security personnel.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Discipline<br /> | style=&quot;border: 1px solid #000000;&quot; | Report to supervisor for general orders. '''Martial law is in effect.''' Arrests, searches, and raids may be performed at the discretion of security personnel and without a warrant. Arrests of officers permitted at discretion of security personnel. Summary punishment, including execution, may be sentenced by any authorised entity. Security is fully authorised to take whatever actions deemed necessary to neutralise or repel station threats. Propose evacuation or scuttling if station cannot be retaken.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Secure Areas<br /> | style=&quot;border: 1px solid #000000;&quot; | All secure areas unsecured as needed to facilitate evacuation and/or retrieval of sensitive materials.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Medical<br /> | style=&quot;border: 1px solid #000000;&quot; | Full suit sensors heavily advised. EVA suits and functioning internals heavily advised for emergency responders.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Engineering<br /> | style=&quot;border: 1px solid #000000;&quot; | EVA suits heavily advised for engineers. Distribute emergency internals to crew.<br /> |-<br /> | style=&quot;border: 1px solid #000000;&quot; | Rules of Engagement<br /> | style=&quot;border: 1px solid #000000;&quot; | Lethal force authorised at the discretion of security personnel, in self defence, or to effect an arrest.<br /> |}<br /> <br /> {{Guides Menu}}</div>

Lyndomen