From 926b92455f32fae749455709b56a45bb8d5c51ed Mon Sep 17 00:00:00 2001 From: John Willis <143434770+CerberusWolfie@users.noreply.github.com> Date: Mon, 13 Jan 2025 13:24:11 -0500 Subject: [PATCH] Port changes. (#48) --- .../guidebook/{guides.ftl => sop.ftl} | 12 +++-- .../Prototypes/_Goobstation/Guidebook/sop.yml | 50 ++++++++++++++----- .../SOP/AlertLevels/AlertLevelsSOP.xml | 8 ++- .../Guidebook/SOP/Jobs/Command/CaptainSOP.xml | 6 +-- .../Guidebook/SOP/Jobs/Command/CommandSOP.xml | 5 +- .../SOP/Jobs/Command/HeadOfPersonnelSOP.xml | 2 +- .../SOP/Jobs/Command/HeadOfSecuritySOP.xml | 11 +++- .../Jobs/Dignitary/BlueshieldOfficerSOP.xml | 29 +++++++++++ .../SOP/Jobs/Dignitary/DignitarySOP.xml | 20 ++++++++ .../SOP/Jobs/Dignitary/MagistrateSOP.xml | 40 +++++++++++++++ .../SOP/Jobs/Dignitary/NanotrasenRepSOP.xml | 34 +++++++++++++ .../SOP/Jobs/Epistemics/EpistemicsSOP.xml | 13 ++++- .../SOP/Jobs/Epistemics/GolemancerSOP.xml | 6 +++ .../SOP/Jobs/Epistemics/MantisSOP.xml | 4 ++ .../SOP/Jobs/Epistemics/ResearcherSOP.xml | 6 +++ .../SOP/Jobs/Epistemics/SacrificesSOP.xml | 10 +++- .../ServerInfo/Guidebook/SOP/Jobs/JobsSOP.xml | 1 + .../SOP/Jobs/Security/CorpsmanSOP.xml | 5 +- .../SOP/Jobs/Security/DetectiveSOP.xml | 8 +++ .../SOP/Jobs/Security/OfficerCadetSOP.xml | 9 ++++ .../SOP/Jobs/Security/PrisonGuardSOP.xml | 2 + .../Guidebook/SOP/Jobs/Security/WardenSOP.xml | 8 +++ .../Guidebook/SOP/Legal/ExecutionSOP.xml | 4 +- Resources/ServerInfo/Guidebook/SOP/SoP.xml | 1 + .../StandardProcedures/CommandSuccession.xml | 14 +++--- .../StandardProcedures/EarlyEvacuationSOP.xml | 20 ++++++++ .../SOP/StandardProcedures/FiringDemotion.xml | 18 +++---- .../StandardProcedures/HiringTransfers.xml | 2 +- 28 files changed, 299 insertions(+), 49 deletions(-) rename Resources/Locale/en-US/_Goobstation/guidebook/{guides.ftl => sop.ftl} (93%) create mode 100644 Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/BlueshieldOfficerSOP.xml create mode 100644 Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/DignitarySOP.xml create mode 100644 Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/MagistrateSOP.xml create mode 100644 Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/NanotrasenRepSOP.xml create mode 100644 Resources/ServerInfo/Guidebook/SOP/StandardProcedures/EarlyEvacuationSOP.xml diff --git a/Resources/Locale/en-US/_Goobstation/guidebook/guides.ftl b/Resources/Locale/en-US/_Goobstation/guidebook/sop.ftl similarity index 93% rename from Resources/Locale/en-US/_Goobstation/guidebook/guides.ftl rename to Resources/Locale/en-US/_Goobstation/guidebook/sop.ftl index bc630eea44..3cf200b0ca 100644 --- a/Resources/Locale/en-US/_Goobstation/guidebook/guides.ftl +++ b/Resources/Locale/en-US/_Goobstation/guidebook/sop.ftl @@ -1,14 +1,15 @@ # Goob SOP # - Main Directories guide-entry-sop = SOP -guide-entry-sop-alert-levels = _Alert Levels -guide-entry-sop-emergencies = _Emergencies +guide-entry-sop-alert-levels = Alert Levels +guide-entry-sop-emergencies = Emergencies guide-entry-sop-jobs = Jobs guide-entry-sop-legal = Legal guide-entry-sop-standards = Standard Procedures # - Sub/Nested Directories guide-entry-sop-cargo = Cargo guide-entry-sop-command = Command +guide-entry-sop-dignitary = Dignitary guide-entry-sop-engineering = Engineering guide-entry-sop-epistemics = Epistemics guide-entry-sop-medical = Medical @@ -26,6 +27,7 @@ guide-entry-sop-violetalert = Violet Alert guide-entry-sop-whitealert = White Alert # - Standard Procedures guide-entry-sop-demoting = Dismissal/Demoting +guide-entry-sop-evacuation = Early Evacuation guide-entry-sop-hiring = Hiring/Transfer guide-entry-sop-succession = Chain of Command # - Emergencies @@ -46,8 +48,6 @@ guide-entry-sop-searches = Searches guide-entry-sop-cargotech = Cargo Tech guide-entry-sop-salvage = Salvage Specialist # - Command -guide-entry-sop-ntr = Nanotrasen Rep. -guide-entry-sop-bso = Blueshield Officer guide-entry-sop-captain = Captain guide-entry-sop-hop = Head of Personnel guide-entry-sop-hos = Head of Security @@ -57,6 +57,10 @@ guide-entry-sop-cmo = Chief Medical Ofc. guide-entry-sop-ce = Chief Engineer # Logistics Officer changed by Delta-V (original: Quartermaster) guide-entry-sop-lo = Logistics Officer +# - Dignitary +guide-entry-sop-bso = Blueshield Officer +guide-entry-sop-ntr = Nanotrasen Rep. +guide-entry-sop-magistrate = Magistrate # - Engineering guide-entry-sop-atmostech = Atmos Tech guide-entry-sop-stationengineer = Station Engineer diff --git a/Resources/Prototypes/_Goobstation/Guidebook/sop.yml b/Resources/Prototypes/_Goobstation/Guidebook/sop.yml index 03e1d8c662..39ab359d7a 100644 --- a/Resources/Prototypes/_Goobstation/Guidebook/sop.yml +++ b/Resources/Prototypes/_Goobstation/Guidebook/sop.yml @@ -13,6 +13,7 @@ id: Alert Levels name: guide-entry-sop-alert-levels text: "/ServerInfo/Guidebook/SOP/AlertLevels/AlertLevelsSOP.xml" + priority: 0 children: - GreenAlert SOP - BlueAlert SOP @@ -29,6 +30,7 @@ id: Emergencies SOP name: guide-entry-sop-emergencies text: "/ServerInfo/Guidebook/SOP/Emergencies/Emergencies.xml" + priority: 0 children: - ConfirmedRevs SOP - ContainmentFail SOP @@ -48,6 +50,7 @@ - Alert Levels - Emergencies SOP - Demoting SOP + - EarlyEvacuation SOP - Hiring SOP - Succession @@ -69,6 +72,7 @@ children: - Cargo SOP - Command SOP + - Dignitary SOP - Engineering SOP - Epistemics SOP - Medical SOP @@ -88,8 +92,6 @@ name: guide-entry-sop-command text: "/ServerInfo/Guidebook/SOP/Jobs/Command/CommandSOP.xml" children: - - NanotrasenRep SOP - - BlueshieldOfficer SOP - Captain SOP - HeadOfPersonnel SOP - HeadOfSecurity SOP @@ -98,6 +100,15 @@ - ChiefEngineer SOP - LogisticsOfficer SOP # Changed for Delta-V Naming Scheme - Original: Quartermaster +- type: guideEntry + id: Dignitary SOP + name: guide-entry-sop-dignitary + text: "/ServerInfo/Guidebook/SOP/Jobs/Dignitary/DignitarySOP.xml" + children: + - BlueshieldOfficer SOP + - NanotrasenRep SOP + - Magistrate SOP + - type: guideEntry id: Engineering SOP name: guide-entry-sop-engineering @@ -202,16 +213,25 @@ id: Demoting SOP name: guide-entry-sop-demoting text: "/ServerInfo/Guidebook/SOP/StandardProcedures/FiringDemotion.xml" + priority: 10 + +- type: guideEntry + id: EarlyEvacuation SOP + name: guide-entry-sop-evacuation + text: "/ServerInfo/Guidebook/SOP/StandardProcedures/EarlyEvacuationSOP.xml" + priority: 10 - type: guideEntry id: Hiring SOP name: guide-entry-sop-hiring text: "/ServerInfo/Guidebook/SOP/StandardProcedures/HiringTransfers.xml" + priority: 10 - type: guideEntry id: Succession name: guide-entry-sop-succession # Is named as "Chain of Command" in game. text: "/ServerInfo/Guidebook/SOP/StandardProcedures/CommandSuccession.xml" + priority: 10 # Emergency SOP Entries - type: guideEntry @@ -287,16 +307,6 @@ text: "/ServerInfo/Guidebook/SOP/Jobs/Cargo/SalvageSpecialistSOP.xml" # Command SOP Entries -- type: guideEntry - id: NanotrasenRep SOP - name: guide-entry-sop-ntr - text: "/ServerInfo/Guidebook/SOP/Jobs/Command/NanotrasenRepSOP.xml" - -- type: guideEntry - id: BlueshieldOfficer SOP - name: guide-entry-sop-bso - text: "/ServerInfo/Guidebook/SOP/Jobs/Command/BlueshieldOfficerSOP.xml" - - type: guideEntry id: Captain SOP name: guide-entry-sop-captain @@ -332,6 +342,22 @@ name: guide-entry-sop-lo text: "/ServerInfo/Guidebook/SOP/Jobs/Command/LogisticsOfficerSOP.xml" +# Dignitary SOP Entries +- type: guideEntry + id: NanotrasenRep SOP + name: guide-entry-sop-ntr + text: "/ServerInfo/Guidebook/SOP/Jobs/Dignitary/NanotrasenRepSOP.xml" + +- type: guideEntry + id: BlueshieldOfficer SOP + name: guide-entry-sop-bso + text: "/ServerInfo/Guidebook/SOP/Jobs/Dignitary/BlueshieldOfficerSOP.xml" + +- type: guideEntry + id: Magistrate SOP + name: guide-entry-sop-magistrate + text: "/ServerInfo/Guidebook/SOP/Jobs/Dignitary/MagistrateSOP.xml" + # Engineering SOP Entries - type: guideEntry id: AtmosTech SOP diff --git a/Resources/ServerInfo/Guidebook/SOP/AlertLevels/AlertLevelsSOP.xml b/Resources/ServerInfo/Guidebook/SOP/AlertLevels/AlertLevelsSOP.xml index 67adb7a082..76e90da5f0 100644 --- a/Resources/ServerInfo/Guidebook/SOP/AlertLevels/AlertLevelsSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/AlertLevels/AlertLevelsSOP.xml @@ -3,6 +3,12 @@ The following alert levels are the publicly defined levels on this station and what they entail. Below are the listed pop-ups for each alert and the color associated with them. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + There are individual entries for each alert level and what they entail for station personnel. @@ -126,7 +132,7 @@ The [color=#db7093]Gamma Alert[/color] is rare and often only used in extreme ca The [color=#cc74fc]Violet Alert[/color] is set for viral outbreaks when a zombie infection or other disease occurs.
- + [bold][color=#000000][head=1]White Alert[/head][/color][/bold] diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CaptainSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CaptainSOP.xml index c22a91ce3b..b1e2e972cd 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CaptainSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CaptainSOP.xml @@ -15,7 +15,7 @@ This is the list of procedures, responsibilities, and duties of the [color=#1b67 If neither are available on the current station, refer to the [bold]Chain of Command[/bold]. 5. Captain may keep Captain Space IDs in their room or give it to the appropriate members in the [bold]Chain of Command[/bold]. -The [color=#1b67a5][bold]Nanotrasen Representative[/bold][/color] and [color=#1b67a5][bold]Blueshield Officer[/bold][/color] are not permitted to carry these IDs. +The [color=#1b67a5][bold]Nanotrasen Representative[/bold][/color], [color=#1b67a5][bold]Magistrate[/bold][/color], and [color=#1b67a5][bold]Blueshield Officer[/bold][/color] are not permitted to carry these IDs. 6. The Captain is not to leave the Station unless given specific permission by Central Command. @@ -26,9 +26,9 @@ This is the list of procedures, responsibilities, and duties of the [color=#1b67 9. The Captain, despite being in charge of the Station, is not independent from NanoTrasen. Any attempts to disregard general company policy are to be considered an instant condition for contract termination. 10. Firing a Head of Staff [bold]must[/bold] be done with reasonable justification. Refer to [bold]Dismissal/Demotion Policies[/bold]. -Firing Central Command VIPs ([color=#1b67a5][bold]Nanotrasen Representative[/bold][/color] and [color=#1b67a5][bold]Blueshield Officer[/bold][/color]) [bold]must[/bold] be done with authorization from Central Command. +Firing Central Command VIPs ([color=#1b67a5][bold]Nanotrasen Representative[/bold][/color], [color=#1b67a5][bold]Magistrate[/bold][/color], and [color=#1b67a5][bold]Blueshield Officer[/bold][/color]) [bold]must[/bold] be done with authorization from Central Command. -11. The Captain may not promote anyone to Central Command VIP Positions ([color=#1b67a5][bold]Nanotrasen Representative[/bold][/color] and [color=#1b67a5][bold]Blueshield Officer[/bold][/color]) without authorization from Central Command. +11. The Captain may not promote anyone to Central Command VIP Positions ([color=#1b67a5][bold]Nanotrasen Representative[/bold][/color], [color=#1b67a5][bold]Magistrate[/bold][/color], and [color=#1b67a5][bold]Blueshield Officer[/bold][/color]) without authorization from Central Command. 12. The Captain may carry their weaponry on them at all times. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CommandSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CommandSOP.xml index 892dcd66c6..7186ea3ab9 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CommandSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/CommandSOP.xml @@ -8,12 +8,11 @@ Below are the list of guidelines [bold]all of Command should follow[/bold]: 2. The Command Personnel may defend themselves and perform arrests as needed in self-defense, but may not try, place times, or perform any other Security activities except hand-off arrested personnel to Security. -3. The Command Personnel may not, under any circumstances, promote station personnel to Central Command VIP Positions ([color=#1b67a5][bold]Nanotrasen Representative[/bold][/color] and [color=#1b67a5][bold]Blueshield Officer[/bold][/color]) without authorization from Central Command. +3. The Command Personnel may not, under any circumstances, promote station personnel to Central Command VIP Positions ([color=#1b67a5][bold]Nanotrasen Representative[/bold][/color], [color=#1b67a5][bold]Magistrate[/bold][/color], and [color=#1b67a5][bold]Blueshield Officer[/bold][/color]) without authorization from Central Command. The following jobs have entries in this Department, the Chain of Command being linked at the top, the Central Command VIP being separated in terms of Chain of Command, the Captain being the top of Chain of Command, and all Heads of Staff on equal footing: - [textlink="Chain of Command" link="Succession"] -- [textlink="Nanotrasen Representative" link="NanotrasenRep SOP"] -- [textlink="Blueshield Officer" link="BlueshieldOfficer SOP"] +- [textlink="Captain" link="Captain SOP"] - [textlink="Head of Personnel" link="HeadOfPersonnel SOP"] - [textlink="Head of Security" link="HeadOfSecurity SOP"] - [textlink="Mystagogue" link="Mystagogue SOP"] diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfPersonnelSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfPersonnelSOP.xml index b4bd2a0346..add64218df 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfPersonnelSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfPersonnelSOP.xml @@ -12,7 +12,7 @@ This is the list of procedures, responsibilities, and duties of the [color=#1b67 4. The Head of Personnel may not dismiss/demote any personnel without authorization from the relevant Head of Staff (exceptions apply: see Space Law and General SOP). -5. The Head of Personnel may not promote anyone above Command. This includes positions such as Nanotrasen Representative, Blueshield Officer, and any other Central Command figure. +5. The Head of Personnel may not promote anyone above Command. This includes positions such as Nanotrasen Representative, Magistrate, Blueshield Officer, and any other Central Command figure. 6. The Head of Personnel may utilize paperwork for proceedings, but should expedite requests during major station emergencies. Emergency Access takes precedence over paper. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfSecuritySOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfSecuritySOP.xml index b7b5bf2859..d2902bed29 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfSecuritySOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Command/HeadOfSecuritySOP.xml @@ -2,6 +2,14 @@ # Head of Security (HOS) SOP This is the list of procedures, responsibilities, and duties of the [color=#1b67a5][bold]Head of Security[/bold][/color] of this station. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + +The [color=#1b67a5][bold]Head of Security[/bold][/color] is permitted to carry their shift-start equipment, but should follow escalation procedures and refrain from using lethals. + ## Green Alert 1. The Head of Security is permitted to carry out arrests under the same conditions as their Security Officers. @@ -10,7 +18,8 @@ This is the list of procedures, responsibilities, and duties of the [color=#1b67 3. The Head of Security is not obligated to provide a trial, but is encouraged to allow legal representation should the suspect request it. This only applies to Capital Crimes. -4. The Head of Security may not overrule a Captain/Nanotrasen Representative, unless their decisions are blatantly breaking Standard Operating Procedure and/or Space Law. In which case Central Command is to be contacted as well. +4. The Head of Security may not overrule a Captain/Magistrate, unless their decisions are blatantly breaking Space Law. In which case Central Command is to be contacted as well. +This includes Nanotrasen Representative in cases of Standard Operating Procedure as well. 5. The Head of Security must follow the same guidelines as the Warden for Armory equipment, portable flashers and deployable barriers. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/BlueshieldOfficerSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/BlueshieldOfficerSOP.xml new file mode 100644 index 0000000000..88982c9456 --- /dev/null +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/BlueshieldOfficerSOP.xml @@ -0,0 +1,29 @@ + +# Blueshield Officer (BSO) SOP +This is the list of procedures, responsibilities, and duties of the [color=#1b67a5][bold]Blueshield Officer[/bold][/color] of this station. + + + + The [color=#1b67a5][bold]Blueshield Officer[/bold][/color] should never be Captain nor Head of Staff. + + + +The [bold][color=#fcd12a]most important[/color][/bold] rule of the Blueshield Officer is to protect and maintain the lives of Command personnel on the station. +Command personnel are personnel hired by Nanotrasen (confirmed personnel in command) and any Central Command officials (including BSO). + +1. The Blueshield Officer must listen to and follow orders of the NTR unless it would directly conflict with ensuring the safety of Command personnel or Central Command orders. + +2. The Blueshield Officer is to put the lives of Command over the lives of all others, including the Blueshield Officer. Their well-being is top priority. +This includes first aid, revival, and ensuring they are safe and secure during emergencies. + +3. The Blueshield Officer is to protect the lives of Command, not follow their orders to a fault. + +4. The Blueshield Officer is not permitted to interfere with legal demotions or arrests. To do so would be a violation of their Central Command orders and Space Law. +This primarily pertains to Command and Security work. + +5. The Blueshield Officer should not use lethal force unless there is a clear and present danger to Command and/or their lives. +The Blueshield Officer must also be unable to non-lethally detain the assailant. + +6. The Blueshield Officer is permitted to use lethal force in certain emergencies; refer to Alert Levels. + + diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/DignitarySOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/DignitarySOP.xml new file mode 100644 index 0000000000..d6b1b6b45d --- /dev/null +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/DignitarySOP.xml @@ -0,0 +1,20 @@ + + # Dignitary Department Procedures + These are the list of SOPs that Dignitary Personnel should follow. These are, as stated before, [bold]not checklists[/bold] and should be treated as guidelines. + + Below are the list of guidelines [bold]all of Dignitary should follow[/bold]: + + 1. Dignitaries [bold]are not[/bold] and [bold]should never be[/bold] Commmand Personnel. You are above Command. + + 2. Dignitaries respond to Central Command as needed, and should follow their orders over Command. + + 3. Dignitaries are to stick to their roles, and never become a personnel of the station; unless they are demoted by Central Command. + + 4. Dignitaries are upheld to expectations higher than Command Personnel and Security Personnel. You represent NanoTrasen afterall. + + The following jobs have entries in this department: + - [textlink="Nanotrasen Representative" link="NanotrasenRep SOP"] + - [textlink="Magistrate" link="Magistrate SOP"] + - [textlink="Blueshield Officer" link="BlueshieldOfficer SOP"] + + diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/MagistrateSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/MagistrateSOP.xml new file mode 100644 index 0000000000..97891d7c72 --- /dev/null +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/MagistrateSOP.xml @@ -0,0 +1,40 @@ + + # Magistrate (MAG) SOP + This is the list of procedures, responsibilities, and duties of the [color=#1b67a5][bold]Magistrate[/bold][/color] of this station. + + + + The [color=#1b67a5][bold]Magistrate[/bold][/color] should never be Captain nor Head of Staff. + + + + The [bold][color=#fcd12a]most important[/color][/bold] rule of the Magistrate is to assist ensure Space Law is being followed. + Command personnel are personnel hired by Nanotrasen (confirmed personnel in command) and any Central Command officials (including MAG). + + 1. Magistrates are to ensure that Space Law is applied correctly. If it is not, they are to make it so. + + 2. Magistrates have the final say on whether or not Trials take place, and should ensure they should only occur for Capital Sentences. + Similarly, Magistrates are to ensure that Trials do not happen for Defendants that are self-evidently guilty, or those that do not want to participate in a trial (accepting Capital Punishment). + + 3. Magistrates can overrule anyone in all matters concerning Space Law. This does not extend to Emergency Response Teams, Central Command Officials or direct Central Command communications. + + 4. The Magistrate is permitted to carry their flash and a telescopic baton. + + 5. Magistrates are not above Space Law. Similarly, they cannot overrule Security on a sentence imposed against themselves. If a Magistrate attempts to do this, contact Central Command immediately. + + 6. In the absence of a Nanotrasen Representative, the Magistrate may elect to handle matters of Standard Operating Procedure. Otherwise, they must abide by Nanotrasen Representative's choices if there is one. + + 7. Magistrates may not impede the expedient functioning of Security for the sake of micromanaging every aspect it. They should only concern themselves with crimes that either have fuzzy evidence, or require careful deliberation of circumstances. + + 8. Magistrates are to contact Central Command immediately if their decisions are being ignored, provided said decision actually match up with Space Law and Standard Operating Procedure. Please see this guide for more information on how to write a good fax. + + 9. Magistrates are [bold]not[/bold] lawyers, and should leave the lawyering and talking down of sentences to said Lawyers. + If the Magistrate deems it necessary for a sentence to be adjusted, they may override Security. + + 10. Magistrates are to act as Judges in Trials unless they are connected/part of the crime, whether they be involved by witness or something else. + + 11. Magistrates are to ensure any trial taken place is speedy and thorough. + + 12. Magistrates are to ensure Executions are following standards, and override Captain in such cases for allowing them to take place, as stated in Guideline 3. + + diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/NanotrasenRepSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/NanotrasenRepSOP.xml new file mode 100644 index 0000000000..6b464a3159 --- /dev/null +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Dignitary/NanotrasenRepSOP.xml @@ -0,0 +1,34 @@ + +# Nanotrasen Representative (NTR) SOP +This is the list of procedures, responsibilities, and duties of the [color=#1b67a5][bold]Nanotrasen Representative[/bold][/color] of this station. + + + + The [color=#1b67a5][bold]Nanotrasen Representative[/bold][/color] should never be Captain nor Head of Staff. + + + +The [bold][color=#fcd12a]most important[/color][/bold] rule of the Nanotrasen Representative is to assist Command Personnel and ensure they are following SOP. +Command personnel are personnel hired by Nanotrasen (confirmed personnel in command) and any Central Command officials (including NTR). + +## Resources +1. The Nanotrasen Representative posesses a FAX machine to directly fax to Central Command (with notification to Central Command Officials). + +2. In the event of an emergency, the station is equipped with a minimum of one Red Phone which directly notifies Central Command. + +3. In the event of an emergency, the Nanotrasen Representative possesses a Central Command Encryption Key in their headset for direct communications with Central Command. + +## Rulings +1. The Nanotrasen Representative is to ensure that every Department is following Standard Operating Procedure, including Command personnel. +If a Department does not have a corresponding Head of Staff, NTR must ensure the Captain appoints an Acting Head of Staff and assist in such endeavors to guide them. + +2. The Nanotrasen Representative must attempt to resolve any [bold]major[/bold] breach of SOP before contacting Central Command. This is an imperative. +Standard Operating Procedure must generally be followed with reasonable justifications when it is ignored. + +3. The Nanotrasen Representative is to ensure, along with Captain, Head of Security, and Warden, that Space Law is followed and being applied correctly. +This does not permit NTR to override brig timers, punishments, or any other Security endeavor unless Central Command orders as such. + +4. The Nanotrasen Representative is not to use their direct connection to Central Command for leverage over other crew members. +In addition, they may not threaten to fire anyone (nor contact Central Command to do so) unless a justification for demotion exists. + + diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/EpistemicsSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/EpistemicsSOP.xml index 11a74d4b41..18d389911e 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/EpistemicsSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/EpistemicsSOP.xml @@ -4,8 +4,17 @@ These are the list of SOPs that Epistemics Personnel should follow. These are, a For clarification, Golemancer can extend to any Epistemics personnel working on Robots. -It is expected that [color=#cc74fc]Noviciate[/color], [color=#cc74fc]Acolyte[/color], and [color=#cc74fc]Mystic[/color] coincide in the same SOP guidelines. -This is to consolidate the guidelines. +It is expected that [color=#cc74fc]Noviciate[/color], [color=#cc74fc]Acolyte[/color], and [color=#cc74fc]Mystic[/color] coincide in the same SOP guidelines. This is to consolidate the guidelines. + +[color=#cc74fc]Chaplain[/color] and [color=#cc74fc]Mantis[/color] are Second in-commands to Mystagogue in the Epistemics department, with: +- [color=#cc74fc]Chaplain[/color] overseeing the Oracle and Sacrifices. +- [color=#cc74fc]Mantis[/color] assisting (alongside [color=#cc74fc]Cataloguer[/color]) with finding and keeping track of Psionic Users. + + + + Be sure to read over the guidebook entires of the the Epistemics jobs and to also follow the Sacrifices Rulings. + + The following jobs have entries in this Department, the [color=#1b67a5][bold]Mystagogue[/bold][/color] being the Head of Staff: - [textlink="Mystagogue" link="Mystagogue SOP"] diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/GolemancerSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/GolemancerSOP.xml index 9eb2ba2fe8..c0ad3023f0 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/GolemancerSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/GolemancerSOP.xml @@ -3,6 +3,12 @@ This is the list of procedures, responsibilities, and duties of the [color=#cc74fc]Golemancer[/color] of this station. For clarification, 'Researcher' and 'Golemancer' are both referred to as 'Researcher' in this SOP. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + ## Green Alert 1. The Researcher is not permitted to construct any Combat Mechs without express permission from the Captain and/or Head of Security. The [color=#1b67a5][bold]Research Director[/bold][/color] is placed under these same restrictions. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/MantisSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/MantisSOP.xml index f30db189b6..aa795e221d 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/MantisSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/MantisSOP.xml @@ -17,4 +17,8 @@ The Mantis is a role that works with [color=#cc74fc]Cataloguer[/color] and [colo 6. During [bold][color=#ffffff]White Alert[/color][/bold] the Mantis should assist the [color=#1b67a5][bold]Mystagogue[/bold][/color] with hunting down the Psionic Users and only answers to the [color=#1b67a5][bold]Mystagogue[/bold][/color] and/or [color=#1b67a5][bold]Captain[/bold][/color]. +7. Mantis is permitted mindbreaking chemicals, such as (and including): +- Crystobiolin +- Space Drugs (anything related to Psionics) + diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/ResearcherSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/ResearcherSOP.xml index 1829b8dfc6..835f217951 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/ResearcherSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/ResearcherSOP.xml @@ -4,6 +4,12 @@ This is the list of procedures, responsibilities, and duties of the [color=#cc74 For clarification, 'Researcher' is used as a catch-all-phrase for Noviciate, Acolyte, and Mystic. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + ## Green Alert 1. Researchers are not permitted to bring grenades, harmful chemicals, nor Toxin bombs outside of the Epistemics Department. [bullet/]Exceptions for the Toxin bombs if being handed over to the Cargo Department for Salvaging operations. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/SacrificesSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/SacrificesSOP.xml index e67232618e..353dba6734 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/SacrificesSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Epistemics/SacrificesSOP.xml @@ -2,13 +2,19 @@ # Sacrifices SOP Sacrifice is a procedure that can only be performed by the [color=#cc74fc]Chaplain[/color] or [color=#1b67a5][bold]Mystagogue[/bold][/color]. -1. Sacrifices must be performed on [bold][color=#ffffff]White Alert[/color][/bold] to reduce the Glimmer Levels to a sustainable level. +1. Sacrifices can be performed on [bold][color=#ffffff]White Alert[/color][/bold] to reduce the Glimmer Levels to a sustainable level. -2. Sacrifices should only be performed on Psionic Users that are abusing their powers; unless it is necessary to reduce the Glimmer Levels immediately. +2. Sacrifices should [bold]only be performed[/bold] on Psionic Users that are abusing their powers; unless it is necessary to reduce the Glimmer Levels immediately. +[bold]Mindbreaking[/bold] should be prioritized for users that are [bold][italic]not actively/maliciously[/italic][/bold] misusing their psionic powers. 3. Sacrifices should be performed on Criminal Psionic Users over other Psionic Users. +Sacrifices are permitted on those that are permanently brigged and misusing their powers. 4. Sacrifices should not be performed when it isn't [bold][color=#ffffff]White Alert[/color][/bold] unless it is consentual. The only exception to this rule is if it is necessary due to an immediate and quickly rising Glimmer Level. +5. Mindbreaking Chemicals are permitted to Epistemics when dealing with White Alert and needing to mindbreak instead of sacrifice. + +6. Any sacrificed personnel should be converted into golems or borgified. This is a requirement. + diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/JobsSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/JobsSOP.xml index c7d1d9264e..cf2bcc50f3 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/JobsSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/JobsSOP.xml @@ -9,6 +9,7 @@ Attached below this are several different categories for Job-Specific Standard O The following folders are listed underneath this folder: - [textlink="Cargo Department" link="Cargo SOP"] - [textlink="Command Department" link="Command SOP"] +- [textlink="Dignitary Department" link="Dignitary SOP"] - [textlink="Engineering Department" link="Engineering SOP"] - [textlink="Epistemics Department" link="Epistemics SOP"] - [textlink="Medical Department" link="Medical SOP"] diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/CorpsmanSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/CorpsmanSOP.xml index 587bf3dd71..dd89530f79 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/CorpsmanSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/CorpsmanSOP.xml @@ -2,6 +2,8 @@ # Corpsman SOP This is the list of procedures, responsibilities, and duties of the [color=#ba292c][bold]Corpsman[/bold][/color] of this station. +[color=#ba292c][bold]Corpsman[/bold][/color]s are permitted to carry their shift-start pistols, but should follow escalation laws and leave them holstered on Green Alert. + Corpsman are held to the same guidelines and responsibilities as [textlink="Paramedic" link="DoctorIntern SOP"]; with exceptions that they are to cater to Security Personnel and Prisoners over regular station personnel. 1. Corpsman are to respond to demands from [color=#ba292c][bold]Warden[/bold][/color] for Security Treatment with immediate priority. @@ -10,7 +12,8 @@ Corpsman are held to the same guidelines and responsibilities as [textlink="Para 3. Corpsman are to follow the same guidelines as [textlink="Security Officers" link="OfficerCadet SOP"] for [color=#388c34]Green Alert[/color] and [color=#1b67a5]Blue Alert[/color]. -4. Corpsman are not permitted to carry lethal weapons except on [color=#ba292c]Red Alert[/color] and higher. +4. Corpsman are not permitted to unholster lethal weapons except on [color=#ba292c]Blue Alert[/color] and higher, following escalation procedures and only for self-defense. +If necessary, the Corpsman may use lethal weaponry on clear hostiles, but must take responsibility as a Security Officer would. 5. Corpsman are to prioritize treatment of Prisoners over regular Medical Personnel. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/DetectiveSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/DetectiveSOP.xml index 9d2800e4bf..30e9ea650e 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/DetectiveSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/DetectiveSOP.xml @@ -2,6 +2,14 @@ # Detective SOP This is the list of procedures, responsibilities, and duties of the [color=#ba292c][bold]Detective[/bold][/color] of this station. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + +The [color=#ba292c][bold]Detective[/bold][/color] is permitted to carry their shift-start equipment, but should follow escalation laws and leave them holstered on Green Alert. + ## Green Alert 1. The Detective is permitted to assist Security Officers with all Patrol Duties. This includes stops, searches, and arrests as per the current Alert Code. They should, however, prioritize investigations and the collection of forensic evidence. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/OfficerCadetSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/OfficerCadetSOP.xml index 866f658910..311faaef8c 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/OfficerCadetSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/OfficerCadetSOP.xml @@ -2,6 +2,14 @@ # Officer/Cadet SOP This is the list of procedures, responsibilities, and duties of the [color=#ba292c][bold]Security Officer[/bold][/color] and [color=#ba292c][bold]Security Cadet[/bold][/color] of this station. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + +[color=#ba292c][bold]Security Officer[/bold][/color]s are permitted to carry their shift-start weapons, but should follow escalation laws and leave them holstered on Green Alert. + ## Green Alert 1. Security Officers are required to state the reasons behind an arrest before any further action is taken. Exception is made if the suspect refuses to stop. @@ -16,6 +24,7 @@ This is the list of procedures, responsibilities, and duties of the [color=#ba29 Exceptions apply when a hostile suspect is within an inaccessible area. 6. Security officers are not permitted to have weapons drawn during regular patrols. +Refer to escalation rules for necessary use of shift-start weaponry. 7. Security officers are permitted to conduct searches, provided there is reasonable evidence/suspicion that the person in question has committed a crime. Any further searches require a warrant from the Captain and/or Head of Security. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/PrisonGuardSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/PrisonGuardSOP.xml index 058fa9d10a..4a99a0499d 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/PrisonGuardSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/PrisonGuardSOP.xml @@ -2,6 +2,8 @@ # Prison Guard SOP This is the list of procedures, responsibilities, and duties of the [color=#ba292c][bold]Prison Guard[/bold][/color] of this station. +[color=#ba292c][bold]Prison Guard[/bold][/color]s are permitted to carry their shift-start weaponry, but should follow escalation procedures and keep them holstered, following the Security Officer guidelines. + Prison Guards should follow the same rules as [textlink="Security Officers" link="OfficerCadet SOP"] while remaining in the Security Department much like the [textlink="Warden" link="Warden SOP"] unless transporting Prisoners or taking a break. 1. Prison Guards are not permitted to leave the Security Department unless they are transporting Prisoners. diff --git a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/WardenSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/WardenSOP.xml index 3299904bf3..a279bd354d 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/WardenSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Jobs/Security/WardenSOP.xml @@ -2,6 +2,14 @@ # Warden SOP This is the list of procedures, responsibilities, and duties of the [color=#ba292c][bold]Warden[/bold][/color] of this station. + + + For the purposes of Alert Escalation: Treat higher alerts as if they are still on the previous alert level. (Yellow Alert is Blue Alert if it was Blue Alert prior.) Furthermore, treat Delta, Gamma, Epsilon, and Violet Alert as Red Alert. + + + +The [color=#ba292c][bold]Warden[/bold][/color] is permitted to carry their shift-start equipment, but should follow escalation procedures and refrain from using lethals. + ## Green Alert 1. The Warden is obligated to remain in the Security Department at all times except to assist in transportation of prisoners. The Warden must maintain control over the Armory as well, with only exceptions being allowed for Captain and Head of Security. diff --git a/Resources/ServerInfo/Guidebook/SOP/Legal/ExecutionSOP.xml b/Resources/ServerInfo/Guidebook/SOP/Legal/ExecutionSOP.xml index 67bf471bfb..1440a42537 100644 --- a/Resources/ServerInfo/Guidebook/SOP/Legal/ExecutionSOP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/Legal/ExecutionSOP.xml @@ -17,8 +17,8 @@ These are the procedures that [bold]must[/bold] be followed by Security and Comm 7. It is advised, but not required, to have medical personnel in attendance to verify death. -8. Authorization must be given by the Nanotrasen Representative. If one is not present, dead, or missing, the Captain may authorize an execution in their stead. -Should the Nanotrasen Representative and Captain be unable to provide authorization, it must come from Central Command. Without authorization, executions are murder. +8. Authorization must be given by the Magistrate. If one is not present, dead, or missing, the Captain may authorize an execution in their stead. +Should the Magistrate and Captain be unable to provide authorization, it must come from Central Command. Without authorization, executions are murder. 9. Though not obligatory, it is recommended that all executed prisoners be considered for cyborgification post-execution. diff --git a/Resources/ServerInfo/Guidebook/SOP/SoP.xml b/Resources/ServerInfo/Guidebook/SOP/SoP.xml index 64d49e5435..bed4991318 100644 --- a/Resources/ServerInfo/Guidebook/SOP/SoP.xml +++ b/Resources/ServerInfo/Guidebook/SOP/SoP.xml @@ -31,6 +31,7 @@ The following links are for general knowledge of the station. The following links are for general department SOPs. These will guide you to the folder entry. - [textlink="Cargo Department" link="Cargo SOP"] - [textlink="Command Department" link="Command SOP"] +- [textlink="Dignitary Department" link="Dignitary SOP"] - [textlink="Engineering Department" link="Engineering SOP"] - [textlink="Epistemics Department" link="Epistemics SOP"] - [textlink="Medical Department" link="Medical SOP"] diff --git a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/CommandSuccession.xml b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/CommandSuccession.xml index 8f8eeae6cb..cfebf611cf 100644 --- a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/CommandSuccession.xml +++ b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/CommandSuccession.xml @@ -2,13 +2,13 @@ # Chain of Command This is the ideal list for passing down the Captain role in command. There are several factors to take into respect here, but this boils down to a simple list. -[bullet/][color=#1b67a5]Blueshield Officer[/color] (BSO) and [color=#1b67a5]Nanotrasen Representative[/color] (NTR) should never hold a position of command on this station. +1. [color=#1b67a5]Blueshield Officer[/color] (BSO), [color=#1b67a5]Nanotrasen Representative[/color] (NTR), and [color=#1b67a5]Magistrate[/color] (MAG) should never hold a position of command on this station. -[bullet/]This list can be deviated from for special circumstances, with the vote resting on Command to do so. +2. This list can be deviated from for special circumstances, with the vote resting on Command to do so. -[bullet/][color=#1b67a5]Nanotrasen Representative[/color], if one is present, should assist in this process and guide the new Captain. +3. [color=#1b67a5]Nanotrasen Representative[/color], if one is present, should assist in this process and guide the new Captain. -[bullet/]When choosing the succeeding Captain, they should be marked on their ID as [color=#1b67a5]Acting Captain[/color] (following the same promotion procedures). +4. When choosing the succeeding Captain, they should be marked on their ID as [color=#1b67a5]Acting Captain[/color] (following the same promotion procedures). ~ [bold][color=#1b67a5][head=1]Command Succession[/head][/color][/bold] @@ -29,12 +29,12 @@ The succession list is shown from [bold]top to bottom[/bold] and should be follo If it is deemed necessary, or by wish of the Head of Staff that is being chosen, the next person in the succession may be skipped. -[bullet/]For choices where the Head of Staff is deemed necessary to skip by others, it should be put to a vote by successors (barring Security Officers). +1. For choices where the Head of Staff is deemed necessary to skip by others, it should be put to a vote by successors (barring Security Officers). -[bullet/]For choices where the Head of Staff chooses to not accept the title, they should have a valid reason for doing so and justify it if necessary. +2. For choices where the Head of Staff chooses to not accept the title, they should have a valid reason for doing so and justify it if necessary. ## Choosing Security Officers -When choosing Security Officers for Command Succession, it should be put to a vote by all those included if there is no [color=#1b67a5]Nanotrasen Representative[/color]. +When choosing Security Officers for Command Succession, it should be put to a vote by all those included if there is no [color=#1b67a5]Nanotrasen Representative[/color] or [color=#1b67a5][bold]Magistrate[/bold][/color]. When voting, it should be held as fast as possible. If a tie happens while voting, seniority should prevail. diff --git a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/EarlyEvacuationSOP.xml b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/EarlyEvacuationSOP.xml new file mode 100644 index 0000000000..8f8b2eb72b --- /dev/null +++ b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/EarlyEvacuationSOP.xml @@ -0,0 +1,20 @@ + + # Early Evaucation Procedures + These are the guidelines that should be followed as Command and Security when initiating early-launch procedures. + + 1. Under [bold]no circumstances[/bold] should the evacuation shuttle be early launched when there is no [bold][italic]immediate[/italic][/bold] threat to the evacuation shuttle. + + 2. The Command should wait as [bold]long as possible[/bold] before initiating early launch procedures. + + 3. No member of Command or Station (with access to Command) should initiate early evacuation procedures until every participating member is ready. + To clarify, there should not be individual inputs until everyone is ready, to prevent potential hostiles and/or thieves from taking IDs and starting it with adequate permissions. + + 4. Early Evacuation should be called when a loosed material or threat were to harm the evacuation shuttle imminently. The following would be examples: Teslas, Singularities, Hostile Enemy Ships. + + 5. Early Evacuation should be called when there are hostiles on the evacuation shuttle that are threatening the lives of the station personnel and bridge personnel. + Said hostiles must be, in reasonable suspicion, unable to be taken down without significant loss of life to everyone currently on-board. + + 6. Early Evacuation must be called when there is a Violet Alert to prevent potential specimens from arriving aboard the shuttle. + If it is possible to defend the shuttle, this should be prioritized. + + diff --git a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/FiringDemotion.xml b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/FiringDemotion.xml index 1b4826cd99..6d7e56291b 100644 --- a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/FiringDemotion.xml +++ b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/FiringDemotion.xml @@ -3,19 +3,19 @@ These are the policies/procedures that should be followed when dismissing or demoting personnel from a position. 1. In the event of a full dismissal from a position, the personnel should have their ID marked as "Terminated" and set to an Assistant in terms of accesses (only Maintenance). -[bullet/]Extra access should not be permitted except for special cases with approval from Captain or a relevant Head of Staff (when giving access to a Department). -[bullet/]If dismissed by Central Command orders, authorization for extra access should be given by Central Command. +Extra access should not be permitted except for special cases with approval from Captain or a relevant Head of Staff (when giving access to a Department). +If dismissed by Central Command orders, authorization for extra access should be given by Central Command. 2. In the event of a demotion, the relevant Head of Staff must choose whether to demote them to a lower rank in the Department or have them transferred to a Service position (with HoP approval). -[bullet/]It is recommended that the personnel, when demoted out of a Department, be granted access to a Service job of their choice, or demoted to an Assistant (and marked as such). +It is recommended that the personnel, when demoted out of a Department, be granted access to a Service job of their choice, or demoted to an Assistant (and marked as such). 3. Dismissals and Demotions should not be performed without authorization from the relevant Head of Staff or Captain; unless specified by orders from Central Command or immense violations of Space Law. -[bullet/]In such cases of immense violations of Space Law, the perpetrator must have committed serious crimes and/or actively be punished with Perma Brig. +In such cases of immense violations of Space Law, the perpetrator must have committed serious crimes and/or actively be punished with Perma Brig. 4. Personnel that are dismissed or demoted by a Head of Staff or Authoritative Personnel must report to Head of Personnel for dismissal/demotion. Failure to do so will result in legal authority to detain with force. 5. Personnel that are dismissed or demoted are considered trespassing in areas they would no longer have access. Any materials kept from areas are considered contraband (if listed as such) and should be turned in. -[bullet/]Personnel are allowed to keep items not listed as contraband, but should not inhibit the Department. +Personnel are allowed to keep items not listed as contraband, but should not inhibit the Department. ## Causes for Dismissal or Demotion 1. Any [bold]major[/bold] breach of Standard Operating Procedure without propable cause. @@ -25,19 +25,19 @@ These are the policies/procedures that should be followed when dismissing or dem 3. Unreasonable/Major Incompetence in current position. 4. Refusal to follow legal/relevant orders from respective Head of Staff or Captain. -[bullet/]Legality and relevance of the order must be decided by Captain or Head of Personnel +Legality and relevance of the order must be decided by Captain or Head of Personnel 5. Creation of an abusive, dangerous, and/or unsafe work environment. Written approval for dangerous creations must be approved by respective Head of Staff or Captain. -[bullet/]Abusive environments include berating, insulting, belittling, or otherwise treating coworkers like dirt. +Abusive environments include berating, insulting, belittling, or otherwise treating coworkers like dirt. ## Vote of No Confidence A [italic]Vote of No Confidence[/italic] is a method for crew members to arrange for the removal of a Command Personnel (barring Central Command personnel). It must be justified with reasoning found below. 1. Voting must be verified by a third party who can tally the votes and verify the validity (this should usually be Central Command personnel, such as NTR). -[bullet/]The third party must be on-station. The third party should be the Captain if they are not the target in question. +The third party must be on-station. The third party should be the Captain if they are not the target in question. 2. If the third party dismisses the vote, for any reason, the individual must be treated as if it had not happened. They maintain their authority. -[bullet/]In cases of a tie or understaffed environments, the third party may participate in the vote. +In cases of a tie or understaffed environments, the third party may participate in the vote. 3. Votes by Departmental crew against the Head of Staff must pass with majority in the Department (2/3rd majority in favor). diff --git a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/HiringTransfers.xml b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/HiringTransfers.xml index 47f96be146..a1bab2a6c9 100644 --- a/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/HiringTransfers.xml +++ b/Resources/ServerInfo/Guidebook/SOP/StandardProcedures/HiringTransfers.xml @@ -7,7 +7,7 @@ These are the policies/procedures that should be followed when hiring or transfe 2. Promotions to Acting Head of Staff of a Department requires approval from Captain or Acting Captain. Central Comman may be contacted if so desired. -3. Positions above Command (Nanotrasen Representative and Blueshield Officer) cannot be promoted to without consent/authorization from Central Command. +3. Positions above Command (Nanotrasen Representative, Magistrate, and Blueshield Officer) cannot be promoted to without consent/authorization from Central Command. 4. All new hires to Security and/or Command positions should be mindshielded, checked for implanted materials and/or contraband, and checked for suspicious communication devices.