From 1d66ae5af1d859dd7f46c8a3134da17e333d1379 Mon Sep 17 00:00:00 2001 From: Suraru Harlan <41290202+Suraru@users.noreply.github.com> Date: Fri, 20 Feb 2026 02:11:47 -0600 Subject: [PATCH 01/12] Rules Update --- Content.Shared/CCVar/CCVars.Server.cs | 2 +- Resources/Prototypes/_HL/Guidebook/rules.yml | 51 + Resources/Prototypes/_HL/Guidebook/sop.yml | 770 +++++++++++++++ Resources/Prototypes/_NF/Guidebook/rules.yml | 71 -- .../ServerRules/CoreRules/RuleC0.xml | 183 ---- .../ServerRules/CoreRules/RuleC1.xml | 26 - .../ServerRules/CoreRules/RuleC10.xml | 13 - .../ServerRules/CoreRules/RuleC11.xml | 11 - .../ServerRules/CoreRules/RuleC12.xml | 11 - .../ServerRules/CoreRules/RuleC2.xml | 11 - .../ServerRules/CoreRules/RuleC3.xml | 15 - .../ServerRules/CoreRules/RuleC4.xml | 7 - .../ServerRules/CoreRules/RuleC5.xml | 9 - .../ServerRules/CoreRules/RuleC6.xml | 17 - .../ServerRules/CoreRules/RuleC7.xml | 7 - .../ServerRules/CoreRules/RuleC8.xml | 7 - .../ServerRules/CoreRules/RuleC9.xml | 23 - .../ServerRules/CoreRules/RuleC0.xml | 204 ++++ .../ServerRules/CoreRules/RuleC1.xml | 17 + .../ServerRules/CoreRules/RuleC2.xml | 35 + .../ServerRules/CoreRules/RuleC3.xml | 21 + .../ServerRules/CoreRules/RuleC4.xml | 21 + .../ServerRules/CoreRules/RuleC5.xml | 25 + .../ServerRules/CoreRules/RuleC6.xml | 13 + .../ServerRules/CoreRules/RuleC7.xml | 19 + .../ServerRules/CoreRules/RuleC8.xml | 12 + .../ServerRules/CoreRules/RuleC9.xml | 13 + .../_NF/Guidebook/Rules/CoreRules/RuleC0.xml | 208 ---- .../_NF/Guidebook/Rules/CoreRules/RuleC1.xml | 25 - .../_NF/Guidebook/Rules/CoreRules/RuleC10.xml | 13 - .../_NF/Guidebook/Rules/CoreRules/RuleC11.xml | 11 - .../_NF/Guidebook/Rules/CoreRules/RuleC12.xml | 11 - .../_NF/Guidebook/Rules/CoreRules/RuleC13.xml | 19 - .../_NF/Guidebook/Rules/CoreRules/RuleC2.xml | 11 - .../_NF/Guidebook/Rules/CoreRules/RuleC3.xml | 15 - .../_NF/Guidebook/Rules/CoreRules/RuleC4.xml | 7 - .../_NF/Guidebook/Rules/CoreRules/RuleC5.xml | 9 - .../_NF/Guidebook/Rules/CoreRules/RuleC6.xml | 17 - .../_NF/Guidebook/Rules/CoreRules/RuleC7.xml | 7 - .../_NF/Guidebook/Rules/CoreRules/RuleC8.xml | 7 - .../_NF/Guidebook/Rules/CoreRules/RuleC9.xml | 23 - .../_NF/Guidebook/Rules/CoreRules/Thecode.xml | 46 - .../ServerRules/SpaceLaw/SLCrimeList.xml | 908 ++++++++++++++++++ .../ServerRules/SpaceLaw/SpaceLaw.xml | 183 ++++ .../StarlightSOP/CargoSOP/CargoTechnician.xml | 15 + .../CargoSOP/EngineeringOrders.xml | 35 + .../StarlightSOP/CargoSOP/HandlingOrders.xml | 36 + .../StarlightSOP/CargoSOP/MailTechnician.xml | 17 + .../StarlightSOP/CargoSOP/MedicalOrders.xml | 42 + .../CargoSOP/MiningSpecialist.xml | 15 + .../CargoSOP/PreApprovedMaterials.xml | 17 + .../StarlightSOP/CargoSOP/Quartermaster.xml | 17 + .../CargoSOP/SalvageSpecialist.xml | 23 + .../StarlightSOP/CargoSOP/ScienceOrders.xml | 24 + .../StarlightSOP/CargoSOP/SecurityOrders.xml | 18 + .../StarlightSOP/CargoSOP/ServiceOrders.xml | 33 + .../CargoSOP/cargo-sop-genproc-intro.xml | 3 + .../StarlightSOP/CargoSOP/cargo-sop-intro.xml | 7 + .../CargoSOP/cargo-sop-staff-intro.xml | 3 + .../_Starlight/StarlightSOP/CommandSOP/ai.xml | 15 + .../StarlightSOP/CommandSOP/captain.xml | 38 + .../CommandSOP/command-sop-intro.xml | 5 + .../CommandSOP/general-command-staff.xml | 19 + .../engineering-sop-atmos-tech.xml | 19 + .../engineering-sop-chief-engineer.xml | 21 + .../engineering-sop-genproc-intro.xml | 3 + .../EngineeringSOP/engineering-sop-intro.xml | 5 + .../engineering-sop-power-generation.xml | 13 + .../engineering-sop-staff-intro.xml | 3 + .../engineering-sop-station-damage.xml | 13 + .../engineering-sop-station-engineer.xml | 15 + .../engineering-sop-technical-assistant.xml | 17 + .../GeneralSOP/Alerts/alert-levels.xml | 21 + .../GeneralSOP/Alerts/code-blue.xml | 62 ++ .../GeneralSOP/Alerts/code-delta.xml | 36 + .../GeneralSOP/Alerts/code-gamma.xml | 47 + .../GeneralSOP/Alerts/code-green.xml | 41 + .../GeneralSOP/Alerts/code-red.xml | 63 ++ .../GeneralSOP/Alerts/code-violet.xml | 53 + .../GeneralSOP/Alerts/code-yellow.xml | 97 ++ .../emergency-response-teams.xml | 13 + .../EmergencySOPs/emergency-shuttle.xml | 13 + .../EmergencySOPs/emergency-sops.xml | 5 + .../command-clarifications.xml | 12 + .../line-of-succesion.xml | 16 + .../miscellaneous-clarifications.xml | 5 + .../cause-for-demotion.xml | 12 + .../firing-demotion-policies.xml | 12 + .../hiring-transfer-policies.xml | 10 + .../money-accounts-and-space-credits.xml | 6 + .../nanotrasen-staff-handling-policies.xml | 5 + .../vote-of-no-confidence.xml | 12 + .../NonCrewPolicies/docking-and-visitors.xml | 17 + .../NonCrewPolicies/non-crew-policies.xml | 5 + .../GeneralSOP/NonCrewPolicies/vessels.xml | 9 + .../GeneralSOP/general-sop-intro.xml | 7 + .../StarlightSOP/LegalSOP/legal-sop-intro.xml | 7 + .../StarlightSOP/MedicalSOP/Chemist.xml | 24 + .../MedicalSOP/ChemsMajorContraband.xml | 147 +++ .../MedicalSOP/ChemsMinorContraband.xml | 104 ++ .../MedicalSOP/ChemsSyndicateContraband.xml | 20 + .../MedicalSOP/ChiefMedicalOfficer.xml | 21 + .../MedicalSOP/ContrabandChemicals.xml | 7 + .../MedicalSOP/DeceasedPatientCare.xml | 22 + .../StarlightSOP/MedicalSOP/MedicalBay.xml | 14 + .../StarlightSOP/MedicalSOP/MedicalDoctor.xml | 11 + .../StarlightSOP/MedicalSOP/MedicalIntern.xml | 15 + .../StarlightSOP/MedicalSOP/Paramedic.xml | 17 + .../StarlightSOP/MedicalSOP/PatientCare.xml | 13 + .../StarlightSOP/MedicalSOP/Psychologist.xml | 20 + .../StarlightSOP/MedicalSOP/Surgeon.xml | 17 + .../MedicalSOP/VioletAlertProtocol.xml | 19 + .../MedicalSOP/medical-sop-genproc-intro.xml | 3 + .../MedicalSOP/medical-sop-intro.xml | 7 + .../MedicalSOP/medical-sop-staff-intro.xml | 3 + .../nano-trasen-employee-sop-bso.xml | 17 + ...nano-trasen-employee-sop-genproc-intro.xml | 3 + .../nano-trasen-employee-sop-iaa.xml | 17 + .../nano-trasen-employee-sop-intro.xml | 6 + .../nano-trasen-employee-sop-magistrate.xml | 13 + .../nano-trasen-employee-sop-nct.xml | 17 + .../nano-trasen-employee-sop-nt-rep.xml | 13 + ...no-trasen-employee-sop-safety-protocol.xml | 9 + .../nano-trasen-employee-sop-staff-intro.xml | 3 + .../ScienceSOP/science-sop-intro.xml | 7 + .../StarlightSOP/SecuritySOP/Brigmedic.xml | 37 + .../StarlightSOP/SecuritySOP/Cadet.xml | 9 + .../StarlightSOP/SecuritySOP/Detective.xml | 34 + .../StarlightSOP/SecuritySOP/DutyOfficer.xml | 42 + .../SecuritySOP/HeadOfSecurity.xml | 47 + .../StarlightSOP/SecuritySOP/Parole.xml | 27 + .../SecuritySOP/PermitAcquisition.xml | 26 + .../SecuritySOP/PrisonerTreatment.xml | 17 + .../SecuritySOP/SecurityOfficer.xml | 38 + .../SecuritySOP/SpecialSituations.xml | 74 ++ .../StarlightSOP/SecuritySOP/Warden.xml | 44 + .../SecuritySOP/security-sop-intro.xml | 27 + .../ServiceSOP/HeadOfPersonnel.xml | 11 + .../ServiceSOP/service-sop-genproc-intro.xml | 3 + .../ServiceSOP/service-sop-intro.xml | 3 + .../ServiceSOP/service-sop-staff-intro.xml | 3 + .../StarlightSOP/departmental-sop-intro.xml | 5 + .../_Starlight/StarlightSOP/sop-intro.xml | 17 + 143 files changed, 4423 insertions(+), 841 deletions(-) create mode 100644 Resources/Prototypes/_HL/Guidebook/rules.yml create mode 100644 Resources/Prototypes/_HL/Guidebook/sop.yml delete mode 100644 Resources/Prototypes/_NF/Guidebook/rules.yml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8.xml delete mode 100644 Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml create mode 100644 Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC0.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC1.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC10.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC11.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC12.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC13.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC2.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC3.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC4.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC5.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC6.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC7.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC8.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC9.xml delete mode 100644 Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/Thecode.xml create mode 100644 Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SLCrimeList.xml create mode 100644 Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SpaceLaw.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/CargoTechnician.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/EngineeringOrders.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/HandlingOrders.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MailTechnician.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MedicalOrders.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MiningSpecialist.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/PreApprovedMaterials.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/Quartermaster.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SalvageSpecialist.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ScienceOrders.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SecurityOrders.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ServiceOrders.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-genproc-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-staff-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/ai.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/captain.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/command-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/general-command-staff.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-atmos-tech.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-chief-engineer.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-genproc-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-power-generation.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-staff-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-damage.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-engineer.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-technical-assistant.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/alert-levels.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-blue.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-delta.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-gamma.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-green.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-red.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-violet.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-yellow.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-response-teams.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-shuttle.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-sops.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/command-clarifications.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/line-of-succesion.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/miscellaneous-clarifications.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/cause-for-demotion.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/firing-demotion-policies.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/hiring-transfer-policies.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/money-accounts-and-space-credits.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/nanotrasen-staff-handling-policies.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/vote-of-no-confidence.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/docking-and-visitors.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/non-crew-policies.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/vessels.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/general-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/LegalSOP/legal-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Chemist.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMajorContraband.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMinorContraband.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsSyndicateContraband.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChiefMedicalOfficer.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ContrabandChemicals.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/DeceasedPatientCare.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalBay.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalDoctor.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalIntern.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Paramedic.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/PatientCare.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Psychologist.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Surgeon.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/VioletAlertProtocol.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-genproc-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-staff-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-bso.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-genproc-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-iaa.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-magistrate.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nct.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nt-rep.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-safety-protocol.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-staff-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/ScienceSOP/science-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Brigmedic.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Cadet.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Detective.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/DutyOfficer.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/HeadOfSecurity.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Parole.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PermitAcquisition.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PrisonerTreatment.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SecurityOfficer.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SpecialSituations.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Warden.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/security-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/HeadOfPersonnel.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-genproc-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-staff-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/departmental-sop-intro.xml create mode 100644 Resources/ServerInfo/_Starlight/StarlightSOP/sop-intro.xml diff --git a/Content.Shared/CCVar/CCVars.Server.cs b/Content.Shared/CCVar/CCVars.Server.cs index 39f095ffeff..a21007ba639 100644 --- a/Content.Shared/CCVar/CCVars.Server.cs +++ b/Content.Shared/CCVar/CCVars.Server.cs @@ -18,7 +18,7 @@ public sealed partial class CCVars /// Guide Entry Prototype ID to be displayed as the server rules. /// public static readonly CVarDef RulesFile = - CVarDef.Create("server.rules_file", "FrontierRuleset", CVar.REPLICATED | CVar.SERVER); // Frontier: Rules + CVarDef.Create("server.rules_file", "HardlightRuleset", CVar.REPLICATED | CVar.SERVER); // Frontier: Rules /// /// Guide entry that is displayed by default when a guide is opened. diff --git a/Resources/Prototypes/_HL/Guidebook/rules.yml b/Resources/Prototypes/_HL/Guidebook/rules.yml new file mode 100644 index 00000000000..b9d510d7ac8 --- /dev/null +++ b/Resources/Prototypes/_HL/Guidebook/rules.yml @@ -0,0 +1,51 @@ +- type: guideEntry + id: HardlightRuleset + name: guide-entry-frontier-rules + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml" + priority: -2 + ruleEntry: true + +- type: guideEntry + id: RuleC1 + name: guide-entry-section1 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml" + +- type: guideEntry + id: RuleC2 + name: guide-entry-section2 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml" + +- type: guideEntry + id: RuleC3 + name: guide-entry-section3 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml" + +- type: guideEntry + id: RuleC4 + name: guide-entry-section4 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml" + +- type: guideEntry + id: RuleC5 + name: guide-entry-section5 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml" + +- type: guideEntry + id: RuleC6 + name: guide-entry-section6 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml" + +- type: guideEntry + id: RuleC7 + name: guide-entry-section7 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml" + +- type: guideEntry + id: RuleC8 + name: guide-entry-section8 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml" + +- type: guideEntry + id: RuleC9 + name: guide-entry-section9 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml" \ No newline at end of file diff --git a/Resources/Prototypes/_HL/Guidebook/sop.yml b/Resources/Prototypes/_HL/Guidebook/sop.yml new file mode 100644 index 00000000000..46a49145348 --- /dev/null +++ b/Resources/Prototypes/_HL/Guidebook/sop.yml @@ -0,0 +1,770 @@ +- type: guideEntry + id: SOP + name: guide-entry-sl-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/sop-intro.xml" + children: + - general-sop + - departmental-sop + + +- type: guideEntry + id: general-sop + name: guide-entry-sl-general-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/general-sop-intro.xml" + priority: 1 + children: + - alert-levels + - emergency-sops + - miscellaneous-clarifications + - non-crew-policies + - nanotrasen-staff-handling-policies + + +- type: guideEntry + id: alert-levels + name: guide-entry-sl-alert-levels + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/alert-levels.xml" + priority: 1 + children: + - code-green + - code-blue + - code-red + - code-gamma + - code-delta + - code-yellow + - code-violet + + +- type: guideEntry + id: code-green + name: guide-entry-sl-code-green + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-green.xml" + priority: 1 + +- type: guideEntry + id: code-blue + name: guide-entry-sl-code-blue + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-blue.xml" + priority: 2 + +- type: guideEntry + id: code-red + name: guide-entry-sl-code-red + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-red.xml" + priority: 3 + +- type: guideEntry + id: code-gamma + name: guide-entry-sl-code-gamma + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-gamma.xml" + priority: 4 + +- type: guideEntry + id: code-delta + name: guide-entry-sl-code-delta + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-delta.xml" + priority: 5 + +- type: guideEntry + id: code-yellow + name: guide-entry-sl-code-yellow + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-yellow.xml" + priority: 6 + +- type: guideEntry + id: code-violet + name: guide-entry-sl-code-violet + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/Alerts/code-violet.xml" + priority: 7 + + + +- type: guideEntry + id: emergency-sops + name: guide-entry-sl-emergency-sops + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-sops.xml" + priority: 2 + children: + - emergency-response-teams + - emergency-shuttle + + +- type: guideEntry + id: emergency-response-teams + name: guide-entry-sl-emergency-response-teams + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-response-teams.xml" + priority: 1 + +- type: guideEntry + id: emergency-shuttle + name: guide-entry-sl-emergency-shuttle + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-shuttle.xml" + priority: 2 + + + +- type: guideEntry + id: miscellaneous-clarifications + name: guide-entry-sl-miscellaneous-clarifications + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/MiscellaneousClarifications/miscellaneous-clarifications.xml" + priority: 3 + children: + - line-of-succesion + - command-clarifications + + +- type: guideEntry + id: line-of-succesion + name: guide-entry-sl-line-of-succesion + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/MiscellaneousClarifications/line-of-succesion.xml" + priority: 1 + +- type: guideEntry + id: command-clarifications + name: guide-entry-sl-command-clarifications + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/MiscellaneousClarifications/command-clarifications.xml" + priority: 2 + + + +- type: guideEntry + id: non-crew-policies + name: guide-entry-sl-non-crew-policies + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NonCrewPolicies/non-crew-policies.xml" + priority: 4 + children: + - docking-and-visitors + - vessels + + +- type: guideEntry + id: docking-and-visitors + name: guide-entry-sl-docking-and-visitors + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NonCrewPolicies/docking-and-visitors.xml" + priority: 1 + +- type: guideEntry + id: vessels + name: guide-entry-sl-vessels + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NonCrewPolicies/vessels.xml" + priority: 2 + + + +- type: guideEntry + id: nanotrasen-staff-handling-policies + name: guide-entry-sl-nanotrasen-staff-handling-policies + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/nanotrasen-staff-handling-policies.xml" + priority: 5 + children: + - cause-for-demotion + - firing-demotion-policies + - hiring-transfer-policies + - money-accounts-and-space-credits + - vote-of-no-confidence + +- type: guideEntry + id: cause-for-demotion + name: guide-entry-sl-cause-for-demotion + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/cause-for-demotion.xml" + priority: 1 + +- type: guideEntry + id: firing-demotion-policies + name: guide-entry-sl-firing-demotion-policies + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/firing-demotion-policies.xml" + priority: 2 + +- type: guideEntry + id: hiring-transfer-policies + name: guide-entry-sl-hiring-transfer-policies + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/hiring-transfer-policies.xml" + priority: 3 + +- type: guideEntry + id: money-accounts-and-space-credits + name: guide-entry-sl-money-accounts-and-space-credits + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/money-accounts-and-space-credits.xml" + priority: 4 + +- type: guideEntry + id: vote-of-no-confidence + name: guide-entry-sl-vote-of-no-confidence + text: "/ServerInfo/Guidebook/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/vote-of-no-confidence.xml" + priority: 5 + + + + +- type: guideEntry + id: departmental-sop + name: guide-entry-sl-departmental-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/departmental-sop-intro.xml" + priority: 2 + children: + - command-sop + - security-sop-intro + - legal-sop-intro + - engineering-sop-intro + - cargo-sop-intro + - science-sop-intro + - nano-trasen-employee-sop-intro + - service-sop-intro + - medical-sop-intro + + +- type: guideEntry + id: command-sop + name: guide-entry-sl-command-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/CommandSOP/command-sop-intro.xml" + priority: 1 + children: + - captain + - ai + - general-command-staff + + +- type: guideEntry + id: general-command-staff + name: guide-entry-sl-general-command-staff + text: "/ServerInfo/Guidebook/StarlightSOP/CommandSOP/general-command-staff.xml" + priority: 1 + +- type: guideEntry + id: captain + name: guide-entry-sl-captain + text: "/ServerInfo/Guidebook/StarlightSOP/CommandSOP/captain.xml" + priority: 2 + +- type: guideEntry + id: ai + name: guide-entry-sl-ai + text: "/ServerInfo/Guidebook/StarlightSOP/CommandSOP/ai.xml" + priority: 3 + + + +- type: guideEntry + id: security-sop-intro + name: guide-entry-sl-security-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/security-sop-intro.xml" + priority: 2 + children: + - security-sop-cadet + - security-sop-securityofficer + - security-sop-dutyofficer + - security-sop-detective + - security-sop-brigmedic + - security-sop-warden + - security-sop-headofsecurity + - security-sop-prisonertreatment + - security-sop-parole + - security-sop-permitacquisition + - security-sop-specialsituations + + +- type: guideEntry + id: security-sop-cadet + name: guide-entry-sl-security-sop-cadet + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/Cadet.xml" + priority: 1 + +- type: guideEntry + id: security-sop-securityofficer + name: guide-entry-sl-security-sop-securityofficer + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/SecurityOfficer.xml" + priority: 2 + +- type: guideEntry + id: security-sop-dutyofficer + name: guide-entry-sl-security-sop-dutyofficer + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/DutyOfficer.xml" + priority: 3 + +- type: guideEntry + id: security-sop-detective + name: guide-entry-sl-security-sop-detective + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/Detective.xml" + priority: 4 + +- type: guideEntry + id: security-sop-brigmedic + name: guide-entry-sl-security-sop-brigmedic + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/Brigmedic.xml" + priority: 5 + +- type: guideEntry + id: security-sop-warden + name: guide-entry-sl-security-sop-warden + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/Warden.xml" + priority: 6 + +- type: guideEntry + id: security-sop-headofsecurity + name: guide-entry-sl-security-sop-headofsecurity + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/HeadOfSecurity.xml" + priority: 7 + +- type: guideEntry + id: security-sop-prisonertreatment + name: guide-entry-sl-security-sop-prisonertreatment + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/PrisonerTreatment.xml" + priority: 8 + +- type: guideEntry + id: security-sop-parole + name: guide-entry-sl-security-sop-parole + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/Parole.xml" + priority: 9 + +- type: guideEntry + id: security-sop-permitacquisition + name: guide-entry-sl-security-sop-permitacquisition + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/PermitAcquisition.xml" + priority: 10 + +- type: guideEntry + id: security-sop-specialsituations + name: guide-entry-sl-security-sop-specialsituations + text: "/ServerInfo/Guidebook/StarlightSOP/SecuritySOP/SpecialSituations.xml" + priority: 11 + +- type: guideEntry + id: legal-sop-intro + name: guide-entry-sl-legal-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/LegalSOP/legal-sop-intro.xml" + priority: 3 + + + +- type: guideEntry + id: nano-trasen-employee-sop-intro + name: guide-entry-sl-nano-trasen-employee-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-intro.xml" + priority: 4 + children: + - nano-trasen-employee-sop-genproc-intro + - nano-trasen-employee-sop-staff-intro + + +- type: guideEntry + id: nano-trasen-employee-sop-genproc-intro + name: guide-entry-sl-nano-trasen-employee-sop-genproc-intro + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-genproc-intro.xml" + priority: 1 + children: + - nano-trasen-employee-sop-safety-protocol + + +- type: guideEntry + id: nano-trasen-employee-sop-safety-protocol + name: guide-entry-sl-nano-trasen-employee-sop-safety-protocol + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-safety-protocol.xml" + priority: 1 + + +- type: guideEntry + id: nano-trasen-employee-sop-staff-intro + name: guide-entry-sl-nano-trasen-employee-sop-staff-intro + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-staff-intro.xml" + priority: 2 + children: + - nano-trasen-employee-sop-nt-rep + - nano-trasen-employee-sop-bso + - nano-trasen-employee-sop-magistrate + - nano-trasen-employee-sop-iaa + - nano-trasen-employee-sop-nct + + +- type: guideEntry + id: nano-trasen-employee-sop-nt-rep + name: guide-entry-sl-nano-trasen-employee-sop-nt-rep + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nt-rep.xml" + priority: 1 + +- type: guideEntry + id: nano-trasen-employee-sop-bso + name: guide-entry-sl-nano-trasen-employee-sop-bso + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-bso.xml" + priority: 2 + +- type: guideEntry + id: nano-trasen-employee-sop-magistrate + name: guide-entry-sl-nano-trasen-employee-sop-magistrate + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-magistrate.xml" + priority: 3 + +- type: guideEntry + id: nano-trasen-employee-sop-iaa + name: guide-entry-sl-nano-trasen-employee-sop-iaa + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-iaa.xml" + priority: 4 + +- type: guideEntry + id: nano-trasen-employee-sop-nct + name: guide-entry-sl-nano-trasen-employee-sop-nct + text: "/ServerInfo/Guidebook/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nct.xml" + priority: 5 + +- type: guideEntry + id: engineering-sop-intro + name: guide-entry-sl-engineering-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-intro.xml" + priority: 5 + children: + - engineering-sop-genproc-intro + - engineering-sop-staff-intro + + +- type: guideEntry + id: engineering-sop-genproc-intro + name: guide-entry-sl-engineering-sop-genproc-intro + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-genproc-intro.xml" + priority: 1 + children: + - engineering-sop-power-generation + - engineering-sop-station-damage + + +- type: guideEntry + id: engineering-sop-power-generation + name: guide-entry-sl-engineering-sop-power-generation + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-power-generation.xml" + priority: 1 + +- type: guideEntry + id: engineering-sop-station-damage + name: guide-entry-sl-engineering-sop-station-damage + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-station-damage.xml" + priority: 2 + + +- type: guideEntry + id: engineering-sop-staff-intro + name: guide-entry-sl-engineering-sop-staff-intro + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-staff-intro.xml" + priority: 2 + children: + - engineering-sop-chief-engineer + - engineering-sop-station-engineer + - engineering-sop-atmos-tech + - engineering-sop-technical-assistant + + +- type: guideEntry + id: engineering-sop-chief-engineer + name: guide-entry-sl-engineering-sop-chief-engineer + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-chief-engineer.xml" + priority: 1 + +- type: guideEntry + id: engineering-sop-station-engineer + name: guide-entry-sl-engineering-sop-station-engineer + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-station-engineer.xml" + priority: 2 + +- type: guideEntry + id: engineering-sop-atmos-tech + name: guide-entry-sl-engineering-sop-atmos-tech + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-atmos-tech.xml" + priority: 3 + +- type: guideEntry + id: engineering-sop-technical-assistant + name: guide-entry-sl-engineering-sop-technical-assistant + text: "/ServerInfo/Guidebook/StarlightSOP/EngineeringSOP/engineering-sop-technical-assistant.xml" + priority: 4 + + + +- type: guideEntry + id: cargo-sop-intro + name: guide-entry-sl-cargo-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/cargo-sop-intro.xml" + priority: 6 + children: + - cargo-sop-genproc-intro + - cargo-sop-staff-intro + + +- type: guideEntry + id: cargo-sop-genproc-intro + name: guide-entry-sl-cargo-sop-genproc-intro + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/cargo-sop-genproc-intro.xml" + priority: 1 + children: + - cargo-sop-handlingorders + + +- type: guideEntry + id: cargo-sop-handlingorders + name: guide-entry-sl-cargo-sop-handlingorders + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/HandlingOrders.xml" + priority: 1 + children: + - cargo-sop-preapprovedmaterials + - cargo-sop-handlingorders-engineering + - cargo-sop-handlingorders-security + - cargo-sop-handlingorders-science + - cargo-sop-handlingorders-medical + - cargo-sop-handlingorders-service + + +- type: guideEntry + id: cargo-sop-preapprovedmaterials + name: guide-entry-sl-cargo-sop-preapprovedmaterials + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/PreApprovedMaterials.xml" + priority: 1 + +- type: guideEntry + id: cargo-sop-handlingorders-engineering + name: guide-entry-sl-cargo-sop-handlingorders-engineering + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/EngineeringOrders.xml" + priority: 2 + +- type: guideEntry + id: cargo-sop-handlingorders-security + name: guide-entry-sl-cargo-sop-handlingorders-security + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/SecurityOrders.xml" + priority: 3 + +- type: guideEntry + id: cargo-sop-handlingorders-science + name: guide-entry-sl-cargo-sop-handlingorders-science + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/ScienceOrders.xml" + priority: 4 + +- type: guideEntry + id: cargo-sop-handlingorders-medical + name: guide-entry-sl-cargo-sop-handlingorders-medical + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/MedicalOrders.xml" + priority: 5 + +- type: guideEntry + id: cargo-sop-handlingorders-service + name: guide-entry-sl-cargo-sop-handlingorders-service + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/ServiceOrders.xml" + priority: 6 + + +- type: guideEntry + id: cargo-sop-staff-intro + name: guide-entry-sl-cargo-sop-staff-intro + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/cargo-sop-staff-intro.xml" + priority: 2 + children: + - cargo-sop-cargotechnician + - cargo-sop-mailtechnician + - cargo-sop-miningspecialist + - cargo-sop-salvagespecialist + - cargo-sop-quartermaster + + +- type: guideEntry + id: cargo-sop-cargotechnician + name: guide-entry-sl-cargo-sop-cargotechnician + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/CargoTechnician.xml" + priority: 1 + +- type: guideEntry + id: cargo-sop-mailtechnician + name: guide-entry-sl-cargo-sop-mailtechnician + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/MailTechnician.xml" + priority: 2 + +- type: guideEntry + id: cargo-sop-miningspecialist + name: guide-entry-sl-cargo-sop-miningspecialist + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/MiningSpecialist.xml" + priority: 3 + +- type: guideEntry + id: cargo-sop-salvagespecialist + name: guide-entry-sl-cargo-sop-salvagespecialist + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/SalvageSpecialist.xml" + priority: 4 + +- type: guideEntry + id: cargo-sop-quartermaster + name: guide-entry-sl-cargo-sop-quartermaster + text: "/ServerInfo/Guidebook/StarlightSOP/CargoSOP/Quartermaster.xml" + priority: 5 + + + +- type: guideEntry + id: medical-sop-intro + name: guide-entry-sl-medical-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/medical-sop-intro.xml" + priority: 7 + children: + - medical-sop-genproc-intro + - medical-sop-staff-intro + + +- type: guideEntry + id: medical-sop-genproc-intro + name: guide-entry-sl-medical-sop-genproc-intro + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/medical-sop-genproc-intro.xml" + priority: 1 + children: + - medical-sop-contrabandchemicals + - medical-sop-medicalbay + - medical-sop-patientcare + - medical-sop-deceasedpatientcare + - medical-sop-violetalertprotocol + + +- type: guideEntry + id: medical-sop-contrabandchemicals + name: guide-entry-sl-medical-sop-contrabandchemicals + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/ContrabandChemicals.xml" + priority: 1 + children: + - medical-sop-chemsminorcontraband + - medical-sop-chemsmajorcontraband + - medical-sop-chemssyndicatecontraband + + +- type: guideEntry + id: medical-sop-chemsminorcontraband + name: guide-entry-sl-medical-sop-chemsminorcontraband + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/ChemsMinorContraband.xml" + priority: 1 + +- type: guideEntry + id: medical-sop-chemsmajorcontraband + name: guide-entry-sl-medical-sop-chemsmajorcontraband + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/ChemsMajorContraband.xml" + priority: 2 + +- type: guideEntry + id: medical-sop-chemssyndicatecontraband + name: guide-entry-sl-medical-sop-chemssyndicatecontraband + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/ChemsSyndicateContraband.xml" + priority: 3 + + +- type: guideEntry + id: medical-sop-medicalbay + name: guide-entry-sl-medical-sop-medicalbay + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/MedicalBay.xml" + priority: 2 + +- type: guideEntry + id: medical-sop-patientcare + name: guide-entry-sl-medical-sop-patientcare + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/PatientCare.xml" + priority: 3 + +- type: guideEntry + id: medical-sop-deceasedpatientcare + name: guide-entry-sl-medical-sop-deceasedpatientcare + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/DeceasedPatientCare.xml" + priority: 4 + +- type: guideEntry + id: medical-sop-violetalertprotocol + name: guide-entry-sl-medical-sop-violetalertprotocol + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/VioletAlertProtocol.xml" + priority: 3 + + + +- type: guideEntry + id: medical-sop-staff-intro + name: guide-entry-sl-medical-sop-staff-intro + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/medical-sop-staff-intro.xml" + priority: 2 + children: + - medical-sop-chiefmedicalofficer + - medical-sop-surgeon + - medical-sop-medicaldoctor + - medical-sop-medicalintern + - medical-sop-paramedic + - medical-sop-psychologist + - medical-sop-chemist + + +- type: guideEntry + id: medical-sop-chiefmedicalofficer + name: guide-entry-sl-medical-sop-chiefmedicalofficer + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/ChiefMedicalOfficer.xml" + priority: 1 + +- type: guideEntry + id: medical-sop-surgeon + name: guide-entry-sl-medical-sop-surgeon + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/Surgeon.xml" + priority: 2 + +- type: guideEntry + id: medical-sop-medicaldoctor + name: guide-entry-sl-medical-sop-medicaldoctor + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/MedicalDoctor.xml" + priority: 3 + +- type: guideEntry + id: medical-sop-medicalintern + name: guide-entry-sl-medical-sop-medicalintern + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/MedicalIntern.xml" + priority: 4 + +- type: guideEntry + id: medical-sop-paramedic + name: guide-entry-sl-medical-sop-paramedic + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/Paramedic.xml" + priority: 5 + +- type: guideEntry + id: medical-sop-psychologist + name: guide-entry-sl-medical-sop-psychologist + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/Psychologist.xml" + priority: 6 + +- type: guideEntry + id: medical-sop-chemist + name: guide-entry-sl-medical-sop-chemist + text: "/ServerInfo/Guidebook/StarlightSOP/MedicalSOP/Chemist.xml" + priority: 7 + + +- type: guideEntry + id: science-sop-intro + name: guide-entry-sl-science-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/ScienceSOP/science-sop-intro.xml" + priority: 8 + + + +- type: guideEntry + id: service-sop-intro + name: guide-entry-sl-service-sop-intro + text: "/ServerInfo/Guidebook/StarlightSOP/ServiceSOP/service-sop-intro.xml" + priority: 9 + children: + - service-sop-genproc-intro + - service-sop-staff-intro + + +- type: guideEntry + id: service-sop-genproc-intro + name: guide-entry-sl-service-sop-genproc-intro + text: "/ServerInfo/Guidebook/StarlightSOP/ServiceSOP/service-sop-genproc-intro.xml" + priority: 1 + + +- type: guideEntry + id: service-sop-staff-intro + name: guide-entry-sl-service-sop-staff-intro + text: "/ServerInfo/Guidebook/StarlightSOP/ServiceSOP/service-sop-staff-intro.xml" + priority: 2 + children: + - service-sop-headofpersonnel + + +- type: guideEntry + id: service-sop-headofpersonnel + name: guide-entry-sl-service-sop-headofpersonnel + text: "/ServerInfo/Guidebook/StarlightSOP/ServiceSOP/HeadOfPersonnel.xml" + priority: 1 diff --git a/Resources/Prototypes/_NF/Guidebook/rules.yml b/Resources/Prototypes/_NF/Guidebook/rules.yml deleted file mode 100644 index 2a527db97b4..00000000000 --- a/Resources/Prototypes/_NF/Guidebook/rules.yml +++ /dev/null @@ -1,71 +0,0 @@ -- type: guideEntry - id: FrontierRuleset - name: guide-entry-frontier-rules - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC0.xml" - priority: -2 - ruleEntry: true - -- type: guideEntry - id: RuleC1 - name: guide-entry-section1 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC1.xml" - -- type: guideEntry - id: RuleC2 - name: guide-entry-section2 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC2.xml" - -- type: guideEntry - id: RuleC3 - name: guide-entry-section3 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC3.xml" - -- type: guideEntry - id: RuleC4 - name: guide-entry-section4 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC4.xml" - -- type: guideEntry - id: RuleC5 - name: guide-entry-section5 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC5.xml" - -- type: guideEntry - id: RuleC6 - name: guide-entry-section6 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC6.xml" - -- type: guideEntry - id: RuleC7 - name: guide-entry-section7 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC7.xml" - -- type: guideEntry - id: RuleC8 - name: guide-entry-section8 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC8.xml" - -- type: guideEntry - id: RuleC9 - name: guide-entry-section9 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC9.xml" - -- type: guideEntry - id: RuleC10 - name: guide-entry-section10 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC10.xml" - -- type: guideEntry - id: RuleC11 - name: guide-entry-section11 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC11.xml" - -- type: guideEntry - id: RuleC12 - name: guide-entry-section12 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC12.xml" - -- type: guideEntry - id: RuleC13 - name: guide-entry-section13 - text: "/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC13.xml" diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml deleted file mode 100644 index 2d81b4bb28d..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC0.xml +++ /dev/null @@ -1,183 +0,0 @@ - -[head=3][color=#ff0000]WARNING: You must be 18 or older to play. Users under 18 will be banned immediately.[/head][/color] - -[color=#99ff99]Hard Light is an english speaking 18+ medium roleplay server[/color] - -[color=#a4885c][head=3]0. Implimentation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] - - • Admins will instead be held accountable through use of the Admin code of conduct. - -[color=#ffff00]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] - -[head=3][color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/head][/color] - - Each section contains its own list of rules. Click on the section name to view the full version. - - - [textlink="Section 1. Behavioral Rules" link="RuleC1"] - - [textlink="Section 2. Gameplay Rules" link="RuleC2"] - - [textlink="Section 3. Metagaming Rules" link="RuleC3"] - - [textlink="Section 4. New-life Rules" link="RuleC4"] - - [textlink="Section 5. Character Naming Rules" link="RuleC5"] - - [textlink="Section 6. Roleplay Rules" link="RuleC6"] - - [textlink="Section 7. Powergaming Rules" link="RuleC7"] - - [textlink="Section 8. End-Of-Round (EOR) Rules" link="RuleC8"] - - [textlink="Section 9. Erotic-Role-Play (ERP) Rules" link="RuleC9"] - - [textlink="Section 10. Command and Security Rules" link="RuleC10"] - - [textlink="Section 11. Antagonist Rules" link="RuleC11"] - - [textlink="Section 12. Escalation Guidelines" link="RuleC12"] - -[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] - -[color=#a4885c]1.1[/color] [color=#00fffb]Be respectful to others OOC. [/color] - -[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. - -[color=#a4885c]1.3[/color] [color=#00fffb]Don't metagame.[/color] - -[color=#a4885c]1.4[/color] Don't spam or advertise. - -[color=#a4885c]1.5[/color][color=#00fffb] Do not intentionally take actions that would negatively impact or disrupt others enjoyment of the game. [/color] - -[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. - -[color=#a4885c]1.7[/color][color=#00fffb]Don't evade bans. [/color] - -[color=#a4885c]1.8[/color] Don't self antag. - -[color=#a4885c]1.9[/color][color=#00fffb] Don't ragequit/disconnect to avoid consequences. [/color] - -[color=#a4885c]1.10[/color][color=#00fffb] making use of cheats, exploits, or taking actions that may harm the servers integrity or stability is forbidden. [/color] - -[color=#a4885c]1.11[/color][color=#00fffb] Respect others OOC consent and preferences. [/color] - - -[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] - -[color=#a4885c]2.1[/color] [color=#00fffb]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question. [/color] - -[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). - -[color=#a4885c]2.3[/color] [color=#00fffb]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. [/color] - -[color=#a4885c]2.4[/color] Ghosting with with the sole intent of spying on others personal activities is not permitted. - - -[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] - -[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. - -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. - -[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. - -[color=#a4885c]3.4[/color] [color=#00fffb]discussion about the current round is allowed on the Hardlight Discord server HOWEVER acting on information gained through this method is considered metagaming. [/color] - -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out of character information to give unfair treatment or advantages to others.) - -[color=#a4885c]3.6[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] - - -[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] - -[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. - -[color=#a4885c]4.2[/color] If a player is brought back to life they cannot recall more than foggy concepts of how they died. - - -[color=#a4885c][head=3]Section 5: Naming Rules[/head][/color] - -[color=#a4885c]5.1[/color] Don't make meta references. - -Try to be creative by picking a believable and fitting name and/or surname. - -Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - - -[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] - -[color=#a4885c]6.1[/color] Your character is a separate entity from you, the player. 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. - -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. - -[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. - -[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. - -[color=#a4885c]6.5[/color][color=#00fffb] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away. [/color] - -[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) - -[color=#a4885c]6.7[/color][color=#00fffb]Roleplaying an underage character is strictly forbidden. So is talk of such activities. [/color] - - -[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] - -[color=#a4885c]7.1[/color] Do not hide Antag objective items. - -[color=#a4885c]7.2[/color] Do not make active use of known bugs in the game. - - -[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] - -[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. - -[color=#a4885c]8.2[/color] Arrivals as well as the Evac shuttle (and evac hallway) are considered Safezones in which this rule takes effect. - - -[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] - -[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. - -[color=#a4885c]9.2[/color] DO NOT use ERP as bait for kill objectives, unless done with OOC consent of all parties involved. After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. - -[color=#a4885c]9.3[/color] Do not kinkshame. - -[color=#a4885c]9.4[/color] You MUST use the (-) subtle command for any and all erotic roleplay material. *1 - -[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. - -[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. - -[color=#a4885c]9.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in character. [/color] - -[color=#a4885c]9.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] - -[color=#a4885c]9.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] - -[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). - - -[color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] - -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. - -[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. - -[color=#a4885c]10.3[/color] Don't abuse your position of power. - -[color=#a4885c]10.4[/color] You are expected to roleplay with others, this includes antagonists. - -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. - - -[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] - -[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. - -[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others, this includes Security and Command. - -[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. - -[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. - - -[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] - -[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. - -[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. - -[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. - -[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1.xml deleted file mode 100644 index b38a34b6fa9..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC1.xml +++ /dev/null @@ -1,26 +0,0 @@ - -[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] - -[color=#a4885c]1.1[/color] [color=#00fffb]Be respectful to others OOC. [/color] - -[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. - -[color=#a4885c]1.3[/color] [color=#00fffb]Don't metagame.[/color] - -[color=#a4885c]1.4[/color] Don't spam or advertise. - -[color=#a4885c]1.5[/color][color=#00fffb] Do not intentionally take actions that would negatively impact or disrupt others enjoyment of the game. [/color] - -[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. - -[color=#a4885c]1.7[/color][color=#00fffb]Don't evade bans. [/color] - -[color=#a4885c]1.8[/color] Don't self antag. - -[color=#a4885c]1.9[/color][color=#00fffb] Don't ragequit/disconnect to avoid consequences. [/color] - -[color=#a4885c]1.10[/color][color=#00fffb] making use of cheats, exploits, or taking actions that may harm the servers integrity or stability is forbidden. [/color] - -[color=#a4885c]1.11[/color][color=#00fffb] Respect others OOC consent and preferences. [/color] - - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10.xml deleted file mode 100644 index fbd29fb7359..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC10.xml +++ /dev/null @@ -1,13 +0,0 @@ - -[color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] - -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. *1 - -[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. *1 - -[color=#a4885c]10.3[/color] Don't abuse your position of power. *1 - -[color=#a4885c]10.4[/color] You are expected to roleplay with others, this includes antagonists. *1 - -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. *1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11.xml deleted file mode 100644 index 6777977441a..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC11.xml +++ /dev/null @@ -1,11 +0,0 @@ - -[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] - -[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. *1 - -[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others, this includes Security and Command. *1 - -[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. *1 - -[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. *1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12.xml deleted file mode 100644 index 1f9ce001ca9..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC12.xml +++ /dev/null @@ -1,11 +0,0 @@ - -[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] - -[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. *1 - -[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. *1 - -[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. *1 - -[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. *1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2.xml deleted file mode 100644 index ead217c9f52..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC2.xml +++ /dev/null @@ -1,11 +0,0 @@ - -[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] - -[color=#a4885c]2.1[/color] [color=#00fffb]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question. [/color]*2 - -[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). *2 - -[color=#a4885c]2.3[/color] [color=#00fffb]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. [/color]*2 - -[color=#a4885c]2.4[/color] Ghosting with with the sole intent of spying on others personal activities is not permitted. *2 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3.xml deleted file mode 100644 index d6357e3db0d..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC3.xml +++ /dev/null @@ -1,15 +0,0 @@ - -[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] - -[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. *1 - -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. *1 - -[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. *1 - -[color=#a4885c]3.4[/color] [color=#00fffb]discussion about the current round is allowed on the Hardlight Discord server HOWEVER acting on information gained through this method is considered metagaming. [/color]*1 - -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out of character information to give unfair treatment or advantages to others.) *1 - -[color=#a4885c]3.6[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color]*1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4.xml deleted file mode 100644 index 56b1e6bcd29..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC4.xml +++ /dev/null @@ -1,7 +0,0 @@ - -[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] - -[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. *1 - -[color=#a4885c]4.2[/color] If a player is brought back to life they cannot recall more than foggy concepts of how they died. *1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5.xml deleted file mode 100644 index 82fa544d833..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC5.xml +++ /dev/null @@ -1,9 +0,0 @@ - -[color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] - -[color=#a4885c]5.1[/color] Don't make meta references. *1 - -Try to be creative by picking a believable and fitting name and/or surname. - -Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6.xml deleted file mode 100644 index 8a8710fc0c6..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC6.xml +++ /dev/null @@ -1,17 +0,0 @@ - -[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] - -[color=#a4885c]6.1[/color] Your character is a separate entity from you, the player. 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. *1 - -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. *1 - -[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. *1 - -[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. *1 - -[color=#a4885c]6.5[/color][color=#00fffb] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away. [/color]*2 - -[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) *2 - -[color=#a4885c]6.7[/color][color=#00fffb]Roleplaying an underage character is strictly forbidden. So is talk of such activities. [/color]*3 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7.xml deleted file mode 100644 index fe6a3d2fb9b..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC7.xml +++ /dev/null @@ -1,7 +0,0 @@ - -[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] - -[color=#a4885c]7.1[/color] Do not hide Antag objective items. *1 - -[color=#a4885c]7.2[/color] Do not make active use of known bugs in the game. *1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8.xml deleted file mode 100644 index 650eccd9308..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC8.xml +++ /dev/null @@ -1,7 +0,0 @@ - -[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] - -[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. *1 - -[color=#a4885c]8.2[/color] Arrivals as well as the Evac shuttle (and evac hallway) are considered Safezones in which this rule takes effect. *1 - diff --git a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9.xml b/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9.xml deleted file mode 100644 index 420d8cfc5cc..00000000000 --- a/Resources/ServerInfo/Guidebook/ServerRules/CoreRules/RuleC9.xml +++ /dev/null @@ -1,23 +0,0 @@ - -[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] - -[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. *1 - -[color=#a4885c]9.2[/color] DO NOT use ERP as bait for kill objectives, unless done with OOC consent of all parties involved. After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. *1 - -[color=#a4885c]9.3[/color] Do not kinkshame. *1 - -[color=#a4885c]9.4[/color] You MUST use the (-) subtle command for any and all erotic roleplay material. *1 - -[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. *1 - -[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. *1 - -[color=#a4885c]9.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in character. [/color]*2 - -[color=#a4885c]9.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color]*2 - -[color=#a4885c]9.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color]*3 - -[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). *3 - diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml new file mode 100644 index 00000000000..cf0e9a0ba31 --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml @@ -0,0 +1,204 @@ + +[head=3][color=#ff0000]WARNING: You must be 18 or older to play. Users under 18 will be banned immediately.[/head][/color] + +[color=#99ff99]Hard Light is an english speaking 18+ medium roleplay server[/color] + +[color=#a4885c][head=3]0. Implementation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] + + • Admins will instead be held accountable through use of the Admin code of conduct. + + • If you think an admin has behaved unfairly, you can open a ticket on the discord for an investigation. + +[color=#ffff00]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] + +[head=3][color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/head][/color] + + Each section contains its own list of rules. Click on the section name to view the full version. + + - [textlink="Section 1. Behavioral Rules" link="RuleC1"] + - [textlink="Section 2. Roleplay Rules" link="RuleC2"] + - [textlink="Section 3. Gameplay Rules" link="RuleC3"] + - [textlink="Section 4. Lore/Setting Rules" link="RuleC4"] + - [textlink="Section 5. Erotic-Role-Play (ERP) Rules" link="RuleC5"] + - [textlink="Section 6. Command and Security Rules" link="RuleC6"] + - [textlink="Section 7. Antagonist Rules" link="RuleC7"] + - [textlink="Section 8. Escalation/PvP Rules" link="RuleC8"] + - [textlink="Section 9. Ship Saving Rules" link="RuleC9"] + +[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]1.1[/color] Don't be a dick, aka, do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game except when required by your role. + +[color=#a4885c]1.2[/color] Avoid controversial topics such as self harm/rape in public. + +[color=#a4885c]1.3[/color][color=#00fffb] Don't evade bans in any way, including account sharing or alt accounts. This will be reported to wizden.[/color] + +[color=#a4885c]1.4[/color][color=#00fffb] Taking actions that may harm the server's integrity or stability, such as lag farms, DDoS attacks, or public defamation is forbidden.[/color] + +[color=#a4885c]1.5[/color][color=#00fffb] Impersonation of a position or person is forbidden. Do not pretend to be an admin, do not pretend to be someone you're not out-of-character.[/color] + +[color=#a4885c]1.6[/color][color=#00fffb] If you are frustrated and need a break, you are free to ragequit/disconnect however this will not avoid consequences when you return.[/color] + + +[color=#ffff00][head=3]Section 2: Roleplay Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]2.1[/color][color=#00fffb] Powergaming, defined as taking actions that are impossible or overpowered for your character, is forbidden.[/color] + + - [color=#a4885c]2.1.1[/color] Your character should only specialize in at most 2 departments, and one service sidejob. + - [color=#a4885c]2.1.2[/color] Metaknowledge, such as knowing the exact damage values or weaknesses of objects, is both metagaming and powergaming. + - [color=#a4885c]2.1.3[/color] Do not make antag objectives inaccessible such as tossing them off station. Remember, you need access to them too. + +[color=#a4885c]2.2[/color][color=#00fffb] Metagaming, or using out-of-character information for an in-character advantage, is forbidden.[/color] + + - [color=#a4885c]2.2.1[/color] Metacommms, or sharing IC information in OOC channels, such as discord, isn't against the rules, but using information learned from it is. + - [color=#a4885c]2.2.2[/color] Knowledge gained while unconcious, crit, dead, ghosted, or as another character (or ghost role) should not be known by your character. + - [color=#a4885c]2.2.3[/color] If a player is killed and then brought back to life, they cannot recall more than foggy concepts of how they died. + +[color=#a4885c]2.3[/color][color=#00fffb] No metagruding. Your character is a separate entity from you, the player, and so are the characters you meet from their players. Your IRL feelings, and the feelings of your character, should not bleed or mix together (aka, bleeding/mixing). In-character rivalries should remain in character, and vice versa.[/color] + +[color=#a4885c]2.4[/color] Do not make yourself a major problem, annoyance, or disruption for the crew without a valid reason. Responses should be reasonable and within the realms of what a real person would do in a given situation. + +[color=#a4885c]2.5[/color] Do not play excessively hostile, provocative, or generally "unhirable" characters. If you can't pass an interview, you wouldn't be in ColCom space as an employee or contractor. + + - [color=#a4885c]2.5.1[/color][color=#00fffb] Roleplaying an underage or child-like character in both mind or body, is strictly forbidden. So is talk of such activities.[/color] + +[color=#a4885c]2.6[/color] Respect other people's consent, dignity and boundaries. Check their consent info before engaging in questionable roleplay. If this is abused by either party, ahelp it immediately. + + - [color=#a4885c]2.6.1[/color] Consent tags should be reasonable and fair. You can avoid sexual or gorey RP, but you cannot avoid being a victim or target of antag objectives through consent tags. + - [color=#a4885c]2.6.2[/color] If someone breaches your consent, they are allowed one warning to back off in case of miscommunication, however any further breaches are grounds for bans. + - [color=#a4885c]2.6.3[/color] You are allowed to request an out through any situation via ahelps if you are made uncomfortable, and you will be excluded in the scene through an in-character method manufactured by the admins. The other party will not be notified nor punished in this situation. + +[color=#a4885c]2.7[/color][color=#00fffb] If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question.[/color] + +[color=#a4885c]2.8[/color] You are to remain in character at all times. Do not ruin other player's immersion by breaking character, abusing out-of-character chats, or referencing real world events. + + +[color=#ffff00][head=3]Section 3: Gameplay Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]3.1[/color] It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. + +[color=#a4885c]3.2[/color] Use the chat channels for their intended purposes. OOC channels should be used sparingly to check global consent. Questions should be asked ICly, conversations should be held on discord. + +[color=#a4885c]3.3[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] + +[color=#a4885c]3.4[/color] [color=#00fffb]Ghosting with with the sole intent of spying on others' personal activities is not permitted.[/color] + +[color=#a4885c]3.5[/color][color=#00fffb] Making use of cheats, exploits, or bugs to again an advantage is forbidden.[/color] + +[color=#a4885c]3.6[/color][color=#00fffb] End-of-round-griefing (EORG) is not allowed under any circumstance. [/color] + + - [color=#a4885c]3.6.1[/color] This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. + - [color=#a4885c]3.6.2[/color] All of CC space, arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. + - [color=#a4885c]3.6.3[/color] If someone is heading to cryo, try not impede them (unless you are security) and let them leave. + + +[color=#ffff00][head=3]Section 4: Lore/Setting Rules[/head][/color] + +[color=#a4885c]4.1[/color] Try to be creative by picking a believable and fitting name and/or surname. + + - [color=#a4885c]4.1.1[/color] It's suggested to use a lore-accurate name for your race, although exceptions can exist when cultures clash. + - [color=#a4885c]4.1.2[/color] Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. + - [color=#a4885c]4.1.3[/color] Being named after a popular figure is ok, but having the same name of a popular figure is not. + - [color=#a4885c]4.1.4[/color] Avoid copyright names, such as GlaDOS or Megatron for borgs, Pennywise or The Joker for clowns, and so on. + +[color=#a4885c]4.2[/color] You are not not allowed to have supernatural backgrounds, such as; secret demigods, beings from the future, or similar. + + - [color=#a4885c]4.2.1[/color] Wizards and those apart of the wizards federation are an exception, however they cannot retain their magical powers while not antag + - [color=#a4885c]4.2.2[/color] Changelings, Vampires, Werewolves, and Zombies are creatures of science, not magic. + - [color=#a4885c]4.2.3[/color] If you have a strange concept and don't know if its allowed, you are always free to ask using F1 ahelp. + +[color=#a4885c]4.3[/color] Don't use hate speech, racism, or bigoted comments. In the 26th century, society has moved passed petty bigotry. + + - [color=#a4885c]4.3.1[/color] Distrust of borgs is exempt from this, due to their recent inclusion into sentient life and the existence of hostile rogue borgs. + - [color=#a4885c]4.3.2[/color] Your character cannot be sexist, racist, speciest, ableist, lgbtphobic as it wouldn't make sense in an age where all are proven capable and treated equal. + + +[color=#ffff00][head=3]Section 5: Erotic-Role-Play (ERP) Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]5.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. + +[color=#a4885c]5.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. + +[color=#a4885c]5.3[/color] [color=#00fffb]Don't kinkshame.[/color] + +[color=#a4885c]5.4[/color] You should use the (-) subtle command for erotic roleplay material, to avoid others from walking in on your scene. + +[color=#a4885c]5.5[/color] [color=#00fffb]Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting.[/color] + +[color=#a4885c]5.6[/color] [color=#00fffb]Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera.[/color] + +[color=#a4885c]5.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] + +[color=#a4885c]5.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] + +[color=#a4885c]5.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] + +[color=#a4885c]5.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). + + +[color=#ffff00][head=3]Section 6: Command and Security Rules[/head][/color] + +[color=#a4885c]6.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. + +[color=#a4885c]6.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. + +[color=#a4885c]6.3[/color] Don't abuse your position of power. + +[color=#a4885c]6.4[/color] You are expected to roleplay with others. This includes antagonists. + +[color=#a4885c]6.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. + + +[color=#ffff00][head=3]Section 7: Antagonist Guidelines[/head][/color] + +[color=#a4885c]7.1[/color] Antagonists are held to a higher standard of roleplay, similar to Command. + +[color=#a4885c]7.2[/color] Antagonists are expected to roleplay with others. This includes Security and Command. + +[color=#a4885c]7.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. + +[color=#a4885c]7.4[/color] Pirates should prioritize theft and ransoming, not murder and destruction. + + - [color=#a4885c]7.4.1[/color] Pirates cannot force interactions which result in player or command bank accounts being robbed. (IE: demanding players withdraw funds for ransom) + +[color=#a4885c]7.5[/color] Nukies should prioritize destroying the station and command. Non-combatants and freelancers should be ignored, unless they are threatening. + +[color=#a4885c]7.6[/color] Revolutionaries want to take control of the station, not destroy it. Converting command should be at least attempted before murdering them. + +[color=#a4885c]7.7[/color] Free agents, such as mice, rat-kings, wawas, and so on should only fight in self-defense, unless they are conscripted by a company. + + +[color=#ffff00][head=3]Section 8: Escalation Guidelines[/head][/color] + +[color=#a4885c]8.1[/color] Lethal force against players should be a last resort. + +[color=#a4885c]8.2[/color] Don't disproportionately escalate in response to others' actions. + +[color=#a4885c]8.3[/color] Don't ignore critical or dead players unless related to an objective. + +[color=#a4885c]8.4[/color] Don't intentionally round remove other players unless related to an objective. + +[color=#a4885c]8.5[/color] Revenge or "getting back" should be reasonable and proportional. + + +[color=#ffff00][head=3]Section 9: Ship saving[/head][/color] + +[color=#a4885c]9.1[/color] [color=#00fffb]Ships are to be no larger than 80x50 tiles.[/color] + +[color=#a4885c]9.2[/color] [color=#00fffb]Do not abuse the ship save mechanic to avoid in-character consequences.[/color] + +[color=#a4885c]9.3[/color] [color=#00fffb]Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission.[/color] + +[color=#a4885c]9.4[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] + +[color=#a4885c]9.5[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] + + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml new file mode 100644 index 00000000000..2f95d1343ad --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml @@ -0,0 +1,17 @@ + +[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]1.1[/color] Don't be a dick, aka, do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game except when required by your role. + +[color=#a4885c]1.2[/color] Avoid controversial topics such as self harm/rape in public. + +[color=#a4885c]1.3[/color][color=#00fffb] Don't evade bans in any way, including account sharing or alt accounts. This will be reported to wizden.[/color] + +[color=#a4885c]1.4[/color][color=#00fffb] Taking actions that may harm the server's integrity or stability, such as lag farms, DDoS attacks, or public defamation is forbidden.[/color] + +[color=#a4885c]1.5[/color][color=#00fffb] Impersonation of a position or person is forbidden. Do not pretend to be an admin, do not pretend to be someone you're not out-of-character.[/color] + +[color=#a4885c]1.6[/color][color=#00fffb] If you are frustrated and need a break, you are free to ragequit/disconnect however this will not avoid consequences when you return.[/color] + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml new file mode 100644 index 00000000000..0910b81c6ae --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml @@ -0,0 +1,35 @@ + +[color=#ffff00][head=3]Section 2: Roleplay Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]2.1[/color][color=#00fffb] Powergaming, defined as taking actions that are impossible or overpowered for your character, is forbidden.[/color] + + - [color=#a4885c]2.1.1[/color] Your character should only specialize in at most 2 departments, and one service sidejob. + - [color=#a4885c]2.1.2[/color] Metaknowledge, such as knowing the exact damage values or weaknesses of objects, is both metagaming and powergaming. + - [color=#a4885c]2.1.3[/color] Do not make antag objectives inaccessible such as tossing them off station. Remember, you need access to them too. + +[color=#a4885c]2.2[/color][color=#00fffb] Metagaming, or using out-of-character information for an in-character advantage, is forbidden.[/color] + + - [color=#a4885c]2.2.1[/color] Metacommms, or sharing IC information in OOC channels, such as discord, isn't against the rules, but using information learned from it is. + - [color=#a4885c]2.2.2[/color] Knowledge gained while unconcious, crit, dead, ghosted, or as another character (or ghost role) should not be known by your character. + - [color=#a4885c]2.2.3[/color] If a player is killed and then brought back to life, they cannot recall more than foggy concepts of how they died. + +[color=#a4885c]2.3[/color][color=#00fffb] No metagruding. Your character is a separate entity from you, the player, and so are the characters you meet from their players. Your IRL feelings, and the feelings of your character, should not bleed or mix together (aka, bleeding/mixing). In-character rivalries should remain in character, and vice versa.[/color] + +[color=#a4885c]2.4[/color] Do not make yourself a major problem, annoyance, or disruption for the crew without a valid reason. Responses should be reasonable and within the realms of what a real person would do in a given situation. + +[color=#a4885c]2.5[/color] Do not play excessively hostile, provocative, or generally "unhirable" characters. If you can't pass an interview, you wouldn't be in ColCom space as an employee or contractor. + + - [color=#a4885c]2.5.1[/color][color=#00fffb] Roleplaying an underage or child-like character in both mind or body, is strictly forbidden. So is talk of such activities.[/color] + +[color=#a4885c]2.6[/color] Respect other people's consent, dignity and boundaries. Check their consent info before engaging in questionable roleplay. If this is abused by either party, ahelp it immediately. + + - [color=#a4885c]2.6.1[/color] Consent tags should be reasonable and fair. You can avoid sexual or gorey RP, but you cannot avoid being a victim or target of antag objectives through consent tags. + - [color=#a4885c]2.6.2[/color] If someone breaches your consent, they are allowed one warning to back off in case of miscommunication, however any further breaches are grounds for bans. + - [color=#a4885c]2.6.3[/color] You are allowed to request an out through any situation via ahelps if you are made uncomfortable, and you will be excluded in the scene through an in-character method manufactured by the admins. The other party will not be notified nor punished in this situation. + +[color=#a4885c]2.7[/color][color=#00fffb] If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question.[/color] + +[color=#a4885c]2.8[/color] You are to remain in character at all times. Do not ruin other player's immersion by breaking character, abusing out-of-character chats, or referencing real world events. + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml new file mode 100644 index 00000000000..f403a4e7fc7 --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml @@ -0,0 +1,21 @@ + +[color=#ffff00][head=3]Section 3: Gameplay Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]3.1[/color] It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. + +[color=#a4885c]3.2[/color] Use the chat channels for their intended purposes. OOC channels should be used sparingly to check global consent. Questions should be asked ICly, conversations should be held on discord. + +[color=#a4885c]3.3[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] + +[color=#a4885c]3.4[/color] [color=#00fffb]Ghosting with with the sole intent of spying on others' personal activities is not permitted.[/color] + +[color=#a4885c]3.5[/color][color=#00fffb] Making use of cheats, exploits, or bugs to again an advantage is forbidden.[/color] + +[color=#a4885c]3.6[/color][color=#00fffb] End-of-round-griefing (EORG) is not allowed under any circumstance. [/color] + + - [color=#a4885c]3.6.1[/color] This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. + - [color=#a4885c]3.6.2[/color] All of CC space, arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. + - [color=#a4885c]3.6.3[/color] If someone is heading to cryo, try not impede them (unless you are security) and let them leave. + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml new file mode 100644 index 00000000000..46341114995 --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml @@ -0,0 +1,21 @@ + +[color=#ffff00][head=3]Section 4: Lore/Setting Rules[/head][/color] + +[color=#a4885c]4.1[/color] Try to be creative by picking a believable and fitting name and/or surname. + + - [color=#a4885c]4.1.1[/color] It's suggested to use a lore-accurate name for your race, although exceptions can exist when cultures clash. + - [color=#a4885c]4.1.2[/color] Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. + - [color=#a4885c]4.1.3[/color] Being named after a popular figure is ok, but having the same name of a popular figure is not. + - [color=#a4885c]4.1.4[/color] Avoid copyright names, such as GlaDOS or Megatron for borgs, Pennywise or The Joker for clowns, and so on. + +[color=#a4885c]4.2[/color] You are not not allowed to have supernatural backgrounds, such as; secret demigods, beings from the future, or similar. + + - [color=#a4885c]4.2.1[/color] Wizards and those apart of the wizards federation are an exception, however they cannot retain their magical powers while not antag + - [color=#a4885c]4.2.2[/color] Changelings, Vampires, Werewolves, and Zombies are creatures of science, not magic. + - [color=#a4885c]4.2.3[/color] If you have a strange concept and don't know if its allowed, you are always free to ask using F1 ahelp. + +[color=#a4885c]4.3[/color] Don't use hate speech, racism, or bigoted comments. In the 26th century, society has moved passed petty bigotry. + + - [color=#a4885c]4.3.1[/color] Distrust of borgs is exempt from this, due to their recent inclusion into sentient life and the existence of hostile rogue borgs. + - [color=#a4885c]4.3.2[/color] Your character cannot be sexist, racist, speciest, ableist, lgbtphobic as it wouldn't make sense in an age where all are proven capable and treated equal. + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml new file mode 100644 index 00000000000..78d1bd1d19a --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml @@ -0,0 +1,25 @@ + +[color=#ffff00][head=3]Section 5: Erotic-Role-Play (ERP) Rules[/head][/color] + +[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] + +[color=#a4885c]5.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. + +[color=#a4885c]5.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. + +[color=#a4885c]5.3[/color] [color=#00fffb]Don't kinkshame.[/color] + +[color=#a4885c]5.4[/color] You should use the (-) subtle command for erotic roleplay material, to avoid others from walking in on your scene. + +[color=#a4885c]5.5[/color] [color=#00fffb]Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting.[/color] + +[color=#a4885c]5.6[/color] [color=#00fffb]Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera.[/color] + +[color=#a4885c]5.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] + +[color=#a4885c]5.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] + +[color=#a4885c]5.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] + +[color=#a4885c]5.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml new file mode 100644 index 00000000000..3993b0bbeff --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml @@ -0,0 +1,13 @@ + +[color=#ffff00][head=3]Section 6: Command and Security Rules[/head][/color] + +[color=#a4885c]6.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. + +[color=#a4885c]6.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. + +[color=#a4885c]6.3[/color] Don't abuse your position of power. + +[color=#a4885c]6.4[/color] You are expected to roleplay with others. This includes antagonists. + +[color=#a4885c]6.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml new file mode 100644 index 00000000000..e60957d9a8a --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml @@ -0,0 +1,19 @@ + +[color=#ffff00][head=3]Section 7: Antagonist Guidelines[/head][/color] + +[color=#a4885c]7.1[/color] Antagonists are held to a higher standard of roleplay, similar to Command. + +[color=#a4885c]7.2[/color] Antagonists are expected to roleplay with others. This includes Security and Command. + +[color=#a4885c]7.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. + +[color=#a4885c]7.4[/color] Pirates should prioritize theft and ransoming, not murder and destruction. + + - [color=#a4885c]7.4.1[/color] Pirates cannot force interactions which result in player or command bank accounts being robbed. (IE: demanding players withdraw funds for ransom) + +[color=#a4885c]7.5[/color] Nukies should prioritize destroying the station and command. Non-combatants and freelancers should be ignored, unless they are threatening. + +[color=#a4885c]7.6[/color] Revolutionaries want to take control of the station, not destroy it. Converting command should be at least attempted before murdering them. + +[color=#a4885c]7.7[/color] Free agents, such as mice, rat-kings, wawas, and so on should only fight in self-defense, unless they are conscripted by a company. + diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml new file mode 100644 index 00000000000..a257ddf4dcd --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml @@ -0,0 +1,12 @@ + +[color=#ffff00][head=3]Section 8: Escalation Guidelines[/head][/color] + +[color=#a4885c]8.1[/color] Lethal force against players should be a last resort. + +[color=#a4885c]8.2[/color] Don't disproportionately escalate in response to others' actions. + +[color=#a4885c]8.3[/color] Don't ignore critical or dead players unless related to an objective. + +[color=#a4885c]8.4[/color] Don't intentionally round remove other players unless related to an objective. + +[color=#a4885c]8.5[/color] Revenge or "getting back" should be reasonable and proportional. diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml new file mode 100644 index 00000000000..0931fcaaa7b --- /dev/null +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml @@ -0,0 +1,13 @@ + +[color=#ffff00][head=3]Section 9: Ship saving[/head][/color] + +[color=#a4885c]9.1[/color] [color=#00fffb]Ships are to be no larger than 80x50 tiles.[/color] + +[color=#a4885c]9.2[/color] [color=#00fffb]Do not abuse the ship save mechanic to avoid in-character consequences.[/color] + +[color=#a4885c]9.3[/color] [color=#00fffb]Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission.[/color] + +[color=#a4885c]9.4[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] + +[color=#a4885c]9.5[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] + diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC0.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC0.xml deleted file mode 100644 index 7ab7bf42ded..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC0.xml +++ /dev/null @@ -1,208 +0,0 @@ - -[head=3][color=#ff0000]WARNING: You must be 18 or older to play. Users under 18 will be banned immediately.[/head][/color] - -[color=#99ff99]Hard Light is an english speaking 18+ medium roleplay server[/color] - -[color=#a4885c][head=3]0. Implementation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] - - • Admins will instead be held accountable through use of the Admin code of conduct. - -[color=#ffff00]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] - - -[head=3][color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/head][/color] - - Each section contains its own list of rules. Click on the section name to view the full version. - - - [textlink="Section 1. Behavioral Rules" link="RuleC1"] - - [textlink="Section 2. Gameplay Rules" link="RuleC2"] - - [textlink="Section 3. Metagaming Rules" link="RuleC3"] - - [textlink="Section 4. New-life Rules" link="RuleC4"] - - [textlink="Section 5. Character Naming Rules" link="RuleC5"] - - [textlink="Section 6. Roleplay Rules" link="RuleC6"] - - [textlink="Section 7. Powergaming Rules" link="RuleC7"] - - [textlink="Section 8. End-Of-Round (EOR) Rules" link="RuleC8"] - - [textlink="Section 9. Erotic-Role-Play (ERP) Rules" link="RuleC9"] - - [textlink="Section 10. Command and Security Rules" link="RuleC10"] - - [textlink="Section 11. Antagonist Rules" link="RuleC11"] - - [textlink="Section 12. Escalation Guidelines" link="RuleC12"] - - [textlink="Section 13. Ship saving" link="RuleC13"] - - [textlink="THE PIRATES CODE" link="Thecode"] - -[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] - -[color=#a4885c]1.1[/color] [color=#00fffb]Be respectful to others OOC. [/color] - -[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. - -[color=#a4885c]1.3[/color] [color=#00fffb]Don't metagame.[/color] - -[color=#a4885c]1.4[/color] Don't spam or advertise. - -[color=#a4885c]1.5[/color][color=#00fffb] Do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game. [/color] - -[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. - -[color=#a4885c]1.7[/color][color=#00fffb]Don't evade bans. [/color] - -[color=#a4885c]1.8[/color] Don't self-antag. - -[color=#a4885c]1.9[/color][color=#00fffb] Don't ragequit/disconnect to avoid consequences. [/color] - -[color=#a4885c]1.10[/color][color=#00fffb] Making use of cheats, exploits, or taking actions that may harm the server's integrity or stability is forbidden. [/color] - -[color=#a4885c]1.11[/color][color=#00fffb] Respect others' OOC consent and preferences. [/color] - - -[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] - -[color=#a4885c]2.1[/color] [color=#00fffb]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question. [/color] - -[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). - -[color=#a4885c]2.3[/color] [color=#00fffb]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. [/color] - -[color=#a4885c]2.4[/color] Ghosting with with the sole intent of spying on others' personal activities is not permitted. - - -[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] - -[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. - -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. - -[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. - -[color=#a4885c]3.4[/color] [color=#00fffb]Discussion about the current round is allowed on the Hardlight Discord server. HOWEVER, acting on information gained through this method is considered metagaming. [/color] - -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out-of-character information to give unfair treatment or advantages to others.) - -[color=#a4885c]3.6[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] - - -[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] - -[color=#a4885c]4.1[/color] Players maintain all in-character memory up until going critical. - -[color=#a4885c]4.2[/color] If a player is brought back to life, they cannot recall more than foggy concepts of how they died. - - -[color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] - -[color=#a4885c]5.1[/color] Don't make meta references. - -Try to be creative by picking a believable and fitting name and/or surname. - -Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - - -[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] - -[color=#a4885c]6.1[/color] Your character is a separate entity from you, the player. 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. - -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. - -[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. - -[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. - -[color=#a4885c]6.5[/color][color=#00fffb] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away. [/color] - -[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) - -[color=#a4885c]6.7[/color][color=#00fffb]Roleplaying an underage character is strictly forbidden. So is talk of such activities. [/color] - - -[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] - -[color=#a4885c]7.1[/color] Do not hide Antag objective items. - -[color=#a4885c]7.2[/color][color=#00fffb] Do not make active use of known bugs in the game.[/color] - - -[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] - -[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. - -[color=#a4885c]8.2[/color] Arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. - - -[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] - -[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. - -[color=#a4885c]9.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. - -[color=#a4885c]9.3[/color] Don't kinkshame. - -[color=#a4885c]9.4[/color] You should use the (-) subtle command for erotic roleplay material. - -[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. - -[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. - -[color=#a4885c]9.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] - -[color=#a4885c]9.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] - -[color=#a4885c]9.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] - -[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). - - -[color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] - -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. - -[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. - -[color=#a4885c]10.3[/color] Don't abuse your position of power. - -[color=#a4885c]10.4[/color] You are expected to roleplay with others. This includes antagonists. - -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. - - -[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] - -[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. - -[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others. This includes Security and Command. - -[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. - -[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. - - -[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] - -[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. - -[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. - -[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. - -[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. - -[color=#ffff00][head=3]Section 13: Ship saving[/head][/color] - -[color=#a4885c]13.1[/color] Ships are to be no larger than 80x50 tiles. - -[color=#a4885c]13.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. - -[color=#a4885c]13.3[/color] [color=#00fffb]Do not exploit the stash to duplicate items. This especially goes for contraband.[/color] - -[color=#a4885c]13.4[/color] [color=#00fffb]Do not use inventories to circumvent stash restrictions.[/color] - -[color=#a4885c]13.5[/color] Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission. - -[color=#a4885c]13.6[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] - -[color=#a4885c]13.7[/color] [color=#00fffb]Do not go afk for extended periods on your ship (like logging off to sleep). The ship saving is provided to allow people to save progress without the need to do this. UNATTENDED SHIPS WILL BE REMOVED.[/color] - -[color=#a4885c]13.8[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] - - - - - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC1.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC1.xml deleted file mode 100644 index a5566a45acd..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC1.xml +++ /dev/null @@ -1,25 +0,0 @@ - -[color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] - -[color=#a4885c]1.1[/color] [color=#00fffb]Be respectful to others OOC. [/color] - -[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. - -[color=#a4885c]1.3[/color] [color=#00fffb]Don't metagame.[/color] - -[color=#a4885c]1.4[/color] Don't spam or advertise. - -[color=#a4885c]1.5[/color][color=#00fffb] Do not intentionally take actions that would negatively impact or disrupt others enjoyment of the game. [/color] - -[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. - -[color=#a4885c]1.7[/color][color=#00fffb]Don't evade bans. [/color] - -[color=#a4885c]1.8[/color] Don't self antag. - -[color=#a4885c]1.9[/color][color=#00fffb] Don't ragequit/disconnect to avoid consequences. [/color] - -[color=#a4885c]1.10[/color][color=#00fffb] making use of cheats, exploits, or taking actions that may harm the servers integrity or stability is forbidden. [/color] - -[color=#a4885c]1.11[/color][color=#00fffb] Respect others OOC consent and preferences. [/color] - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC10.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC10.xml deleted file mode 100644 index fbd29fb7359..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC10.xml +++ /dev/null @@ -1,13 +0,0 @@ - -[color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] - -[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. *1 - -[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. *1 - -[color=#a4885c]10.3[/color] Don't abuse your position of power. *1 - -[color=#a4885c]10.4[/color] You are expected to roleplay with others, this includes antagonists. *1 - -[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. *1 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC11.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC11.xml deleted file mode 100644 index 6777977441a..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC11.xml +++ /dev/null @@ -1,11 +0,0 @@ - -[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] - -[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. *1 - -[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others, this includes Security and Command. *1 - -[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. *1 - -[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. *1 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC12.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC12.xml deleted file mode 100644 index 1f9ce001ca9..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC12.xml +++ /dev/null @@ -1,11 +0,0 @@ - -[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] - -[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. *1 - -[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. *1 - -[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. *1 - -[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. *1 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC13.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC13.xml deleted file mode 100644 index 7a3765bf8e7..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC13.xml +++ /dev/null @@ -1,19 +0,0 @@ - -[color=#ffff00][head=3]Section 13: Ship saving[/head][/color] - -[color=#a4885c]13.1[/color] Ships are to be no larger than 80x50 tiles. - -[color=#a4885c]13.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. - -[color=#a4885c]13.3[/color] [color=#00fffb]Do not exploit the stash to duplicate items. This especially goes for contraband.[/color] - -[color=#a4885c]13.4[/color] [color=#00fffb]Do not use inventories to circumvent stash restrictions.[/color] - -[color=#a4885c]13.5[/color] Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission. - -[color=#a4885c]13.6[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] - -[color=#a4885c]13.7[/color] [color=#00fffb]Do not go afk for extended periods on your ship (like logging off to sleep). The ship saving is provided to allow people to save progress without the need to do this. UNATTENDED SHIPS WILL BE REMOVED.[/color] - -[color=#a4885c]13.8[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC2.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC2.xml deleted file mode 100644 index ead217c9f52..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC2.xml +++ /dev/null @@ -1,11 +0,0 @@ - -[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] - -[color=#a4885c]2.1[/color] [color=#00fffb]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question. [/color]*2 - -[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). *2 - -[color=#a4885c]2.3[/color] [color=#00fffb]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. [/color]*2 - -[color=#a4885c]2.4[/color] Ghosting with with the sole intent of spying on others personal activities is not permitted. *2 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC3.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC3.xml deleted file mode 100644 index d6357e3db0d..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC3.xml +++ /dev/null @@ -1,15 +0,0 @@ - -[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] - -[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. *1 - -[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. *1 - -[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. *1 - -[color=#a4885c]3.4[/color] [color=#00fffb]discussion about the current round is allowed on the Hardlight Discord server HOWEVER acting on information gained through this method is considered metagaming. [/color]*1 - -[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out of character information to give unfair treatment or advantages to others.) *1 - -[color=#a4885c]3.6[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color]*1 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC4.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC4.xml deleted file mode 100644 index 56b1e6bcd29..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC4.xml +++ /dev/null @@ -1,7 +0,0 @@ - -[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] - -[color=#a4885c]4.1[/color] Players maintain all in character memory up until going critical. *1 - -[color=#a4885c]4.2[/color] If a player is brought back to life they cannot recall more than foggy concepts of how they died. *1 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC5.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC5.xml deleted file mode 100644 index 82fa544d833..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC5.xml +++ /dev/null @@ -1,9 +0,0 @@ - -[color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] - -[color=#a4885c]5.1[/color] Don't make meta references. *1 - -Try to be creative by picking a believable and fitting name and/or surname. - -Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC6.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC6.xml deleted file mode 100644 index 8a8710fc0c6..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC6.xml +++ /dev/null @@ -1,17 +0,0 @@ - -[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] - -[color=#a4885c]6.1[/color] Your character is a separate entity from you, the player. 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. *1 - -[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. *1 - -[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. *1 - -[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. *1 - -[color=#a4885c]6.5[/color][color=#00fffb] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away. [/color]*2 - -[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) *2 - -[color=#a4885c]6.7[/color][color=#00fffb]Roleplaying an underage character is strictly forbidden. So is talk of such activities. [/color]*3 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC7.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC7.xml deleted file mode 100644 index bfd6e749bd7..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC7.xml +++ /dev/null @@ -1,7 +0,0 @@ - -[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] - -[color=#a4885c]7.1[/color] Do not hide Antag objective items. - -[color=#a4885c]7.2[/color][color=#00fffb] Do not make active use of known bugs in the game.[/color] - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC8.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC8.xml deleted file mode 100644 index 650eccd9308..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC8.xml +++ /dev/null @@ -1,7 +0,0 @@ - -[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] - -[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. *1 - -[color=#a4885c]8.2[/color] Arrivals as well as the Evac shuttle (and evac hallway) are considered Safezones in which this rule takes effect. *1 - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC9.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC9.xml deleted file mode 100644 index db11f6de23c..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/RuleC9.xml +++ /dev/null @@ -1,23 +0,0 @@ - -[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] - -[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. - -[color=#a4885c]9.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. - -[color=#a4885c]9.3[/color] Don't kinkshame. - -[color=#a4885c]9.4[/color] You should use the (-) subtle command for erotic roleplay material. - -[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. - -[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. - -[color=#a4885c]9.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] - -[color=#a4885c]9.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] - -[color=#a4885c]9.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] - -[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). - diff --git a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/Thecode.xml b/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/Thecode.xml deleted file mode 100644 index 57613e07666..00000000000 --- a/Resources/ServerInfo/_NF/Guidebook/Rules/CoreRules/Thecode.xml +++ /dev/null @@ -1,46 +0,0 @@ - -[color=#ffff00][head=3]THE PIRATES CODE[/color][/head] - - --Pirate crews may never exceed a total force of four members, including the Captain, Creatures and cyborgs. - --Round start pets (e.g. Clarrrpy) do not count towards this limit. - --There may only be one Pirate Captain and one First Mate at any time. - --Pirates may not operate without a First Mate or Captain present. - --If the leader of the pirates has been captured or killed, the remaining pirates may make efforts to rescue them. - --First Mates and Captains are required to open their job slot prior to going to cryo, or ahelp if this is not possible. Inform your crew of what they can do in your absence. - --As a pirate, you must have LOOC permission before kidnapping and holding any civilian hostage. - --A pirate may not give orders that are deemed excessive or self destructive to their victims. - --Refusal to cooperate with a pirates orders given no other alternative may be met with lethal response. - --People kept hostage cannot be forced to do labor under any circumstance. - --If a player surrenders, the plundering of their vessel must be kept to a reasonable level. - --Following escalation guidelines, if a player fights, then all goods on their ship are fair game. However, you must leave the ship in a state where it is able to fly as a minimum. - --If you need to escape, then pirates or noncombatants requiring medical attention can be left on a point of interest as a last resort. Do your best to keep them as far from death beforehand. - --uncooperative prey deserve no parley of this nature. - --If a player resumes combat after being revived and is killed again, they are not required to be revived again. - --Pirates must not actively hunt for smuggling notes. - --Smuggling crates are fair game as plunder. - --Pirates cannot force interactions which result in player or command bank accounts being robbed. (IE: demanding players withdraw funds for ransom) - --The stations bank accounts have no such protection. - --Non-pirates may not assist or work with pirate crews without coersion, blackmail, or otherwise. - --Examples include: Acting as lookouts, Pretending to be hostages, intentionally bankrolling pirates, and joining pirate crews. - diff --git a/Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SLCrimeList.xml b/Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SLCrimeList.xml new file mode 100644 index 00000000000..601d588de23 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SLCrimeList.xml @@ -0,0 +1,908 @@ + + # Corporate Law: Crime Listing + Crime codes are colored by linked crime groups, which are collections of non-stackable crimes. Suffixes are also included in the Quick Crime Guide to identify linked crimes. + + ## Quick Crime Guide + + + + 1-XX - Minor + + + + + 2-XX - Moderate + + + + + 3-XX - Major + + + + + 4-XX - Extreme + + + + + 5-XX - Capital + + + + + Code + + + + + + + + + Failure to Comply (1) + + + + + Breach of Arrest (1) + + + + + Breach of Custody (1) + + + + + Refusal of Mental Shielding (1) + + + + + 00 + + + + + Possession or Use of Minor Contraband (2) + + + + + Possession: Major (2) + + + + + + + + + Possession: Significant Syndicate (2) + + + + + + + + + 01 + + + + + Petty Theft (3) + + + + + + + + + Grand Theft (3) + + + + + + + + + + + + + 02 + + + + + + + + + Tampering with Machinery (4) + + + + + Armed Robbery (3) + + + + + + + + + + + + + 03 + + + + + Vandalism (4) + + + + + Damage of Property (4) + + + + + Destruction of Property (4) + + + + + Mass Destruction (4) + + + + + Terrorism (4) + + + + + 04 + + + + + Trespass (5) + + + + + + + + + Secure Trespass (5) + + + + + + + + + + + + + 05 + + + + + + + + + Minor Assault (6) + + + + + Major Assault (6) + + + + + Attempted Murder (6) + + + + + Prevention of Revival (6) + + + + + 06 + + + + + + + + + Endangerment (6) + + + + + Manslaughter (6) + + + + + Murder (6) + + + + + Mass Murder (6) + + + + + 07 + + + + + Disturbance (7) + + + + + Vigilantism (7) + + + + + Rioting (7) + + + + + Unlawful Detainment + + + + + Unlawful Execution (6) + + + + + 08 + + + + + Impersonation and Fraud + + + + + Bribery + + + + + Forgery + + + + + + + + + + + + + 09 + + + + + Animal Cruelty + + + + + + + + + Perjury + + + + + Cannibalism + + + + + + + + + 10 + + + + + + + + + + + + + Sedition (8) + + + + + + + + + + + + + 11 + + + + + + + + + + + + + Conspiracy (8) + + + + + Treason (8) + + + + + Enemy of Corporation (8) + + + + + 12 + + +
+ + ## Linked Crimes: + Crimes that are linked can not be charged together. For more information, refer to Sentencing. + + 1. Failure to Comply, Breach of Arrest, Breach of Custody, Refusal of Mental Shielding + + 2. Possession or Use of Minor Contraband, Major Contraband, or Significant Syndicate Contraband + + 3. Petty Theft, Grand Theft, and Armed Robbery + + 4. Vandalism, Tampering with Machinery, Damage of Property, Destruction of Property, Mass Destruction, Terrorism + + 5. Trespass, Secure Trespass + + 6. Endangerment, Minor Assault, Major Assault, Manslaughter, Attempted Murder, Murder, Prevention of Revival, Mass Murder, Unlawful Execution + + 7. Disturbance, Vigilantism, Rioting + + 8. Sedition, Conspiracy, Treason, Enemy of Corporation + + ## Minor Crimes + Those who commit a minor crime should be issued a warning for their first offense, however repeat offenses are cumulative and should result in jail time of up to 5 minutes per minor crime committed. + + + + Offense + + + + + Description + + + + + Animal Cruelty + + + + + To inflict unnecessary suffering or harm on a non-sentient being with malicious intent. This does not include legitimate and authorized animal testing, or the butchering of livestock for meat. This also does not extend to vermin, or hostile creatures. + + + + + Possession or Use of Minor Contraband + + + + + To make, hold, or use minor contraband without authorization. Authorization may only be granted by the Warden, the Head of Security, or the Captain. + + + + + Petty Theft + + + + + To take non-vital or inexpensive property of another individual, organization, or common property, without consent. Theft of safety or medical equipment such as breath masks, air tanks, or necessary mobility aids are considered vital, and exceed petty theft. + + + + + Vandalism + + + + + To intentionally deface or superficially damage public or private property. Examples include graffiti, smashing glasses or windows, excessively littering, and excessively producing spills. Art or construction with an appropriate permit is not vandalism. + + + + + Trespass + + + + + Trespass - To enter a non-secured area without permission, such as climbing over counters to enter employee areas like the Bar or Kitchen. + + + + + Disturbance + + + + + To cause a public disturbance. This is the catch-all for excessive obnoxious behavior, and includes public nudity, harassment, inciting crime, repeated and intentional misgendering, and disruption of authorities or communications. + + + + + Impersonation and Fraud + + + + + To pretend to be someone you are not, or attempting to commit fraud in any fashion. Impersonation may be elevated to a Moderate crime if the perpetrator is impersonating a member of Security, or a Major crime if they are impersonating a member of Command or Central Command. + + +
+ + ## Moderate Crimes + Those who commit a moderate crime should receive up to a 5 minute sentence per moderate crime committed. + + + + Offense + + + + + Description + + + + + Failure to Comply + + + + + To resist reasonable orders given by an authority. This includes lawful detainment and authorized searches. Officers are required to warn the individual before resorting to arrest. + + + + + Possession/Use of Major Contraband + + + + + To make, hold, or use major contraband without authorization. Authorization may only be granted by the Warden, the Head of Security, or the Captain. Any items restricted to a Department or Job are considered major contraband. + + + + + Tampering with Machinery + + + + + To tamper with a machine such as cutting wires or modifying their functions. Includes but is not limited to; consoles, airlocks, and Silicons. + + + + + Damage of Property + + + + + To maliciously damage or deface public or private property or equipment. This includes equipment vendors, drink dispensers, computers, and machinery such as lathes. + + + + + Endangerment + + + + + To recklessly put yourself or others in danger, either through direct action or failure to act. This includes negligence, accidents, medical malpractice, destruction or impairment of safety features such as firelocks and exterior windows, and reckless piloting of shuttles. + + + + + Minor Assault + + + + + To assault another without a weapon and without causing serious injury. Serious injury is defined as any life altering injury such as loss of limb, damage to the eyes or ears, or any other damages measured by a Health Analyzer to be exceeding 30 total. + + + + + Bribery + + + + + To attempt or succeed to bribe officials to be derelict of their duties or commit a crime with any payment including but not limited to; Services, favors, spesos, credits, materials, or items of any kind. This also applies to anyone caught accepting a bribe, and is cumulative with whatever crime they were bribed to commit. + + + + + Vigilantism + + + + + To attempt to unlawfully enforce Corporate Law without vested authority. See: Enforcement of the Law. + + +
+ + ## Major Crimes + Those who commit a major crime should receive up to 10 minutes of jail time per major crime committed. Major assault and manslaughter are linked crimes and do not stack against a suspect. + + + + Offense + + + + + Description + + + + + Conspiracy + + + + + To conspire or plan to commit a moderate or major crime with reasonable evidence that the suspect was going to go through with the plan. This would include declaring they are going to commit a crime. + + + + + Armed Robbery + + + + + To steal something with the threat of violence using anything that can be considered a weapon, whether or not the weapon is contraband or not. This can include knives, toolboxes, crowbars, or any number of other improvised weaponry. There must be an active threat of violence, or the implication of violence if the victim does not comply, in order to be considered armed robbery. + + + + + Sedition + + + + + To incite rebellion against the authority of the station including but not limited to; Command, Security, Central Command, or Nanotrasen. + + + + + Perjury + + + + + To intentionally lie under oath or make a false statement in a written document + + + + + Forgery + + + + + To forge a written document through illicit means, such as rewriting a stamped document, unauthorized use of an official stamp, or any other means. + + + + + Breach of Arrest + + + + + To intentionally resist and flee arrest or detainment by an authorized staff. This only applies if someone is actively being physically arrested. People uncuffing or assisting others out of an arrest can also be charged with this. Breach of custody is a separate crime. + + + + + Grand Theft + + + + + To take critical or irreplaceable property of another individual or organization without consent. This includes command items such as door remotes, hardsuits, machine parts, and hijacking a department shuttle. + + + + + Destruction of Property + + + + + To destroy the property of another or the station. This includes but is not limited to work consoles, airlocks, and destroying or critically damaging a Cyborg's chassis. + + + + + Secure Trespass + + + + + To enter a secured area without permission. If the area is behind a locked door, it is secure trespass. This includes telecomms, department head offices, command areas, the vault, and the armory. + + + + + Major Assault + + + + + To assault another with a weapon or unarmed assault resulting in serious injury. Serious injury is defined as any life altering injury such as loss of limb, damage to the eyes or ears, or any other damages measured by a Health Analyzer to be exceeding 30 total. + + + + + Manslaughter + + + + + To incidentally kill a sentient humanoid without intent. This includes manslaughter in self-defense and negligent manslaughter. + + + + + Rioting + + + + + To participate in a large group of personnel creating an unlawful public disturbance. Leaders of a riot may be charged with all the crimes committed under their lead, plus sedition. + + +
+ + ## Extreme Crimes + Those who commit an extreme crime may receive up to 20 minutes of jail time per extreme crime committed. Particularly violent offenders may be placed in perma. Attempted murder and murder are linked crimes and cannot be stacked together. + + + + Offense + + + + + Description + + + + + Breach of Custody + + + + + To break out of a cell or custody with the intention of escaping. This applies to people breaking others out. Repeat offenses may have this charge increased to permanent confinement and later elevated to an execution with the Captain's authority only if the suspect has repeatedly committed breach of custody. Breach of custody for the preservation of life, not including to escape execution, such as to vacate a location made dangerous due to gunfire, fire, spacing, or lack of oxygen- may be reduced or ignored at the Warden or Head of Security's discretion. + + + + + Possession or Use of Significant Syndicate Contraband + + + + + To make, hold, or use Significant Syndicate contraband. Significant Syndicate contraband may only be used in emergencies, and only to prevent death or gross bodily harm. Significant Syndicate contraband is any Syndicate contraband that can be used to hinder the station or aid it's enemies in an obvious way. Any syndicate contraband that does not meet this definition is to be considered minor contraband. + + + + + Mass Destruction + + + + + To cause massive damage to an area or major station system. This includes major bombings and sabotage of critical station systems like power, medical, chemistry, substations, and atmospherics. + + + + + Unlawful Detainment + + + + + To unlawfully restrain, transport, control, or confine a sentient humanoid being against that individual's will. This is a catchall to cover any form of kidnapping or forced control. + + + + + Attempted Murder + + + + + To make an attempt to end someone's life, using physical force or otherwise. Proof that action was taken with the intent to kill is necessary, such as a lethal weapon being used. + + + + + Murder + + + + + To kill a sentient humanoid with malicious intent. If the victim must be revived, it is murder and not attempted murder. + + + + + Treason + + + + + To willfully betray allegiances to NanoTrasen. This includes collaborating with terrorists, and especially applies to members of Command attempting to illegally forsake their duties to the detriment of the Station and Nanotrasen. + + + + + Cannibalism + + + + + To consume any part of a sentient humanoid. Consumption of vital components should be treated more harshly. This can be charged on top of other charges such as Murder or Assault if the suspect committed these crimes to obtain the parts consumed. Consumption of blood is not considered cannibalism, but if the source is non-consensual or stolen it may be assault or theft. + + +
+ + ## Capital Crimes + Those who commit a capital crime should be detained in perma with confirmation from Captain. If a capital criminal escapes they are to be executed and transported to CC in a body bag at the end of shift. Emergency executions may be enacted by Captain or the Head of Security with at least 3 other Command as witnesses, but must be reported directly to Central Command afterwards for review. + + + + Offense + + + + + Description + + + + + Refusal of Mental Shielding + + + + + To refuse to comply with a reasonable Mind Shielding procedure. Applies if the suspect is excessively uncooperative or the implant fails to function due to the mental state of the prisoner being too far gone. [bold]If the implant fails, execution is heavily recommended and may be approved by the Captain or Central Command. See Implantation for more.[/bold] + + + + + Terrorism + + + + + To engage in malicious destructive actions which threaten to destroy or successfully destroy a vessel, habitat, or station. This includes extreme sabotage of station systems or setting off the self-destruction systems. + + + + + Unlawful Execution + + + + + To unlawfully execute an individual without authorization or outside of Standard Operating Procedure. This law is distinct from murder, and applies primarily to Security, Command, and Central Command forces such as Emergency Response Teams. + + + + + Prevention of Revival + + + + + To render a body un-resurrectable. This includes gibbing, throwing a body into space, intentionally hiding a body, unlawfully incinerating a body, or any other ways of preventing a body with a soul from being resurrected. + + + + + Mass Murder + + + + + To kill three or more sentient humanoid with malicious intent. Only applies when there have been multiple killings with intention. + + + + + Enemy of Corporation + + + + + To act as or knowingly aid a known enemy of the Station and NT-CC. Only applies beyond a shadow of doubt. + + +
+ diff --git a/Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SpaceLaw.xml b/Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SpaceLaw.xml new file mode 100644 index 00000000000..379bdf4abb6 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/ServerRules/SpaceLaw/SpaceLaw.xml @@ -0,0 +1,183 @@ + + # Corporate Law + On Space Station 14, stations operate under abbreviated Corporate Law. All crew, passengers, and visitors aboard the station are expected to follow these laws. + + Hostile invaders from off-station are not protected under Corporate Law. Domestic threats, anyone rightfully hired by Central Command and/or NanoTrasen, and currently held prisoners are not Hostile Invaders and so are usually protected by Corporate Law. Humanoid Hostile Invaders should be arrested when possible. + + ## Treatment Of Prisoners + Prisoners still have certain rights that must be upheld by law enforcement: + - Prisoners must be granted adequate medical care. + - Prisoners must be allowed access to basic communications equipment so long as they are not abused. + - Prisoners must be granted clothing, food, water, shelter and safety. If the genpop brig is no longer safe, confinement must be established in another location. + - Prisoners must be given access to legal counsel during an interrogation if requested and available. + - Prisoners must be given their shift mandated PDA after confinement has finished, unless there is solid proof of PDA tampering. In case of tampering, the PDA is to be secured and replaced with a new unit. + - Prisoners must be granted freedom of movement and should not be restrained with handcuffs or other devices after incarceration unless there is an undue risk to life and limb. Similarly, any prisoners held for permanent confinement should be held in the communal brig, and should not be confined to a solitary cell unless they pose a risk to life and limb. + - Misuse of equipment against prisoners, such as flashes, teargas, flashbangs, etc is prohibited. Appropriate force should only be applied as strictly necessary. + - Breaches of 'Treatment of Prisoners' is grounds for dismissal or demotion. + + ## Search and Seizure + A personnel search is a seizure of the objects in a person's backpack, hands, coat, belt, and pockets. If any contraband is found during a search, the officer may choose to further the search into a detainment or simply confiscate the restricted items. After the search is conducted, all legal items are to be returned to the person. A crewmate may legally decline any search conducted without probable cause or a warrant while the alert level is green. It should be noted that if the alert level is blue or above, all personnel searches are legal. + + Valid causes for a personnel search include; + + - Verbal or written threats to commit a crime. + - Reports of possession of illegal items. + - Being witnessed committing any crime. + - Evasion of security. + - Trespassing. + - Association with know criminals. + - Door logs indicating suspicious or unauthorized access. + - DNA, print, or fiber matches linking an individual to a crime. + + Searches may not be conducted on simple rumors or hearsay, unless they are corroborated by multiple sources or they are coming from a credible source such as Command or other Mindshielded personnel. Reports of possession of major contra should always be taken seriously. + + A departmental search is the sweep of an entire area or department for contraband. It is recommended that the officers be extremely thorough, checking all lockers, crates, and doors. These can only be done with permission from the department head, a warrant signed by the highest-ranking command member, or in a state of emergency. + + Valid causes for department search include; + + - Mentions of rebellion or illegal activity. + - Confirmed reports of contraband. + - Security breaches, such as hacked open doors or other signs of forced entry. + - Sabotage suspicion, tampering with equipment or infrastructure. + - Criminal activity. + - Inconsistencies in the department, such as unauthorized people or unexplained use of resources. + - Threats made against the department. + + Emergencies scenarios may waiver the need for a warrant, such as; Active threats within the department, ongoing sabotage, escalating violence, and any mention of a rebellion or revolution. + + ## Permit Clause + + Anyone with a valid permit cannot have the relevant contraband seized and cannot be arrested for possession. A valid permit has a stamp and signature from Warden, HoS, or Captain. See Permit Acquisition in Security SOP for clarification. + + ## Implantation + Any prisoner in custody can be subjected to implantation or implant removal procedures, so long as it's within reason Check [textlink="Metashield" link="Metashield"]. The process of adding an implant should not prolong the detainees sentence, meaning you can not hold them longer to administer the implant, unless stated otherwise. A former inmate can be requested to undergo implantation at a later point in time if they fit the circumstances during their confinement, they must comply. The following have been listed out with special circumstances, anything not in this list can still be applied, given proper legal context. A prisoner can still receive implantation procedures without meeting the circumstances if they give their clear permission. + + [color=#a4885c]Illegal Implants:[/color] Applied without proper authorization, these implants may justify extensions if removal is required. + + [color=#a4885c]Tracking Implants:[/color] Trackers can be applied to any suspect that has been convicted of a violent crime (the red linked crimes). + - If voluntary or deemed necessary Command Staff should be given Tracking Implants. + - If voluntary and approved by Warden or Head of Security, normal members of the crew may also be granted Tracking Implants. + + [color=#a4885c]Mind Shields:[/color] Shields can be administered to any inmate who has been clearly mind controlled, lost control of themselves, or a suspect charged with unlawful control. Unlike standard implantation you may hold a prisoner until you finish issuing Mind Shields, so long as it's done in a timely fashion. + - If a suspect refuses to cooperate or the implant fails to function they can be charged with Refusal of Mental Shielding. + - All promoted members of Security, Command, and Salvage must undergo Mind Shielding before they are formally promoted and granted accesses. Anyone given ID access to secure areas, such as the Bridge, must also undergo Mind Shielding. + + A suspect can be forced to receive implant removal if there is strong, reasonable proof that they have been implanted, such as an officer seeing them use one or identifying information is found on a discarded injector. Unlike the implantation procedure, a prisoner can have their sentence entirely delayed or extended until they comply with the procedure with authorization from the Captain, Head of Security, Magistrate, or Warden. Akin to implanting, if an inmate gives their clear permission, implant removal can proceed without proof. + + During a confirmed Revolution, the Head of Security or Warden are permitted to authorize execution of an individual if a Mind Shielding fails or is refused. No other officers are granted this authorization. Execution of those charged with Refusal of Mental Shielding outside of a confirmed Revolution must be authorized by the Captain or Central Command on a case by case basis every time it happens. + + ## Sentencing + Sentencing of under 10 minutes is the responsibility of the arresting officer. When an individual has been detained, they must be promptly marked as such in the Criminal Records Computer. Likewise, when they have been released they must be promptly marked as such. If an individual has been detained but had no preexisting warrant, their criminal record should be updated to reflect them; marking them as wanted and writing in why, before marking them detained. + + The Prisoner's charges must be read to them in front of the Warden or Head of Security. + + It is the responsibility of the Captain, Head of Security, and Warden to ensure that security officers place appropriate sentences that follow Corporate Law. If they are aware of an inappropriate sentence, such as excessively long sentences, and if there is not an urgent threat or danger that they must prioritize, then they must work to correct that sentence. + + Use common sense and humanity when issuing punishments. You should not always seek out the highest punishment you can, you don't have to always give the maximum time or always look to demote someone. Prisoners cooperating and on good behavior should have their sentences reduced. Always take in account the severity and only charge for what is needed for someone to learn their lesson. + + [color=#a4885c]Stackable Crimes:[/color] Crimes are to be considered 'stackable' in the sense that if you charge someone with two or more different crimes, you may combine the times you would give them for each crime. + + - Example: If a suspect has committed Major Possession and Major Syndicate Possession, the maximum sentence would be 20 minutes due to them being linked crimes. + - Example 2: If a suspect has committed Secure Trespass and Manslaughter, the maximum sentence would be 20 minutes due to them being unlinked crimes. + - Context is vital. If you are unsure, seek assistance from the Warden or Head of Security. + + [color=#a4885c]Repeater Offenders:[/color] Repeated crimes are when someone is released for a crime and then commits the same crime again within the same shift. Repeated crimes can be charged with additional time. Every repeat adds 5 minutes. + + [color=#a4885c]Aiding and Abetting:[/color] If someone intentionally, knowingly and substantially assists someone in enacting a crime they should be charged with the same crime as the offender. + + [color=#a4885c]Malfeasance:[/color] Members of command or security who commit a crime should have their sentence increased by 50%. + + [color=#a4885c]Obstruction:[/color] Criminals who interfere with an investigation should have their sentence increased by 50%. + + [color=#a4885c]Absence of Intent:[/color] Criminals who committed their crime unintentionally may have their sentence reduced by 50% at the sentencing officer's discretion. + + [color=#a4885c]Disclosure and Surrender:[/color] Criminals who fully cooperate with the investigation should have their sentence reduced by 50-75% at the sentencing officer's discretion. This includes turning in evidence, turning in accomplices, or recounting the crime in detail. + + [color=#a4885c]Resisting Arrest:[/color] Resisting Arrest: Criminals who behave in a noncompliant manner including resisting arrest, fleeing during processing, or those who become combative may receive sentence times up to double that of the maximum sentence. + + ## Normal Punishments + - [color=#a4885c]Warning:[/color] For minor crimes it is best to fix the issue then warn the person not to attempt the crime again. If they still proceed to do it at a later date, a brig time may be better. + - [color=#a4885c]Confinement:[/color] The typical punishment of being confined in a cell for a temporary amount of time according to the crimes. + - [color=#a4885c]Demotion:[/color] Entails removing all departmental gear they have on their person and removing the involved department access off their ID. This requires the captain's or involved department head's approval. Demotions should only be issued if the person poses a threat to their own department or is in a position where they have/can abuse their job's gear to commit further crimes. + + ## Major Punishments + - [color=#a4885c]Permanent Confinement:[/color] Only prisoners who are guilty of Extreme Crimes or Capital Crimes are eligible for permanent confinement. Any persons subject to this punishment are required to be safely transported in cuffs to CentComm at the end of the shift. A permanent prisoner can not be deprived of anything covered by Prisoner Treatment. + - [color=#a4885c]Execution:[/color] A humane way of dealing with extremely unruly crewmates. Within reason, a prisoner who has been given the death sentence may pick how they wish to be killed, common methods are firing line, lethal injection, exile, and high voltage electrocution. An alternate method of "execution" is the process of placing the prisoner's mind into a borg, this is allowed so long as it is lawful. Execution can only be issued with the captain's or acting captain's approval; if the HoS is acting captain or there is no acting captain, all heads of staff are to hold a vote on the matter. Bodies of criminals should not be left to rot under any circumstance, and transported to CC when possible. + + Parole + + Prisoners are permitted during their sentence to request parole. Warden or Head of Security may approve parole instead of incarceration at their discretion. See Parole in Security SOP for clarification and procedure. + + Members of Law Department may order parole instead of incarceration at the conclusion of a trial or investigation. See Legal SOP for clarification. + + ## Legal Representation and Trials + + Prisoners are permitted to seek legal representation to challenge charges. Petty sentences, that is sentences totaling less than 10 minutes of prison time, are below the interest of the court and should not be brought to trial unless directly requested by the Magistrate. The duties and privileges of an Internal Affairs Agent are as follows: + + - Advise Security in the sentencing of prisoners. + - Act as legal consultants to the accused if requested, the situation is deemed worth while, and they desire to or are ordered to by the Magistrate. + - Handle investigations into misconduct on the part of any department at their own discretion or the discretion of the Magistrate or Captain. + + While Internal Affairs Agents are vested with these responsibilities, they have zero authority over the Brig, Security personnel, prisoners, or sentencing. They can be barred from the Brig by the Magistrate, HoS, Warden, or Captain if they are disruptive. And they may be demoted if they continue to be disruptive. While Internal Affairs Agents are responsible for investigating other departments, they do not have authority over them. + + The Magistrate acts as the highest court, and is the appointed Judge of any case that goes to trial. Should the Magistrate be unavailable, the Head of Security, Head of Personnel, or Captain may act in their stead. In cases where one of these mediators or their subordinates is directly involved, they should not be acting as Judge over the case. For example, if an Internal Affairs Agent is on trial, the Magistrate and Head of Security should not act as Judge. If a Security Officer is on trial, the Head of Security should not act as Judge. And if a member of Service is on trial, the Head of Personnel should not act as Judge. + + ## Jurisdiction + + Every part of the station in totality is the property of NanoTrasen and falls within the jurisdiction of CentComm to enforce Corporate Law. Central Command and the Space Port that the Arrivals Shuttle docks to, including the Arrivals Shuttle and Evac Shuttles, are also within CentComm's jurisdiction. CentComm also has authority through contractual agreements to enforce Corporate Law on all Automated Trade Shuttles. + + Outside of specific circumstances, CentComm's jurisdiction does not extend to private property, defined as any shuttle not directly owned by CentComm or NanoTrasen. Visitor's shuttles are explicitly private property, and an unwarranted search of private property is considered Trespassing. This does not make these shuttles lawless, or outside of the law however. Shuttles within the same Grid as a Station may be subjected to Corporate Law if any of the following criteria are met: + + - A criminal has boarded a shuttle, with or without permission, while being actively pursued + - There is a reasonable belief that the occupants of the shuttle harbor hostile or criminal intent towards the Station or it's Crew + - A crime occurring on the shuttle has been witnessed from outside of the shuttle + - A crime has been witnessed by someone onboard the shuttle who was given permission to enter + - A warrant has been issued by the Warden, Head of Security, Captain, or CentComm + + Any individual onboard a Station or Shuttle that is under the jurisdiction of Corporate Law is also under its jurisdiction, whether they are Crew, Visitors, or otherwise. + + # Penal Code + ## Enforcement of the Law + + The enforcement of Corporate Law is the duty of those vested with such responsibility and no others. Unauthorized civilian enforcement of the law is classified as vigilantism and is strictly illegal. Only the Captain or Central Command may authorize civilian participation in the enforcement of Corporate Law, under dire circumstances. Actions to preserve one’s own life and property, or the life of another, are not classified as vigilantism so long as all other laws are followed. Acting to assist an on-scene officer may be counted as an exception and not vigilantism on a case by case basis, if the action was deemed necessary to prevent further harm to the officer or other civilians. + + Those vested with the responsibility to enforce Corporate Law are defined as follows: + - [color=#a4885c]Security:[/color] Members of the Security Department are always valid to enforce Corporate Law, and should be deferred to by all other law enforcement within reason. + - [color=#a4885c]Blueshield:[/color] Members of Blue Shield are sometimes valid to enforce Corporate Law, but only if it is to prevent further harm to Command or Central Command personnel. + - [color=#a4885c]Mercenaries:[/color] Hired Mercenaries under the direct employ of Central Command may, in extreme circumstances, be permitted by Central Command to enforce Corporate Law. They are however required to operate under the command of the Head of Security and not to circumvent Security. + - [color=#a4885c]Emergency Response Teams:[/color] Members of an ERT are valid to enforce Corporate Law on deployment to Stations. They are however required to operate under the command of the Head of Security and not circumvent Security, unless directly ordered otherwise by Central Command. + + # Civil Code + ## Religious Freedom + + Religious Freedom is the right to believe and practice your faith within reason, so long as this practice does not violate any other laws. Religious rites that are considered a minor crime may be given exemption warrants by the Captain or Head of Personnel. These warrants only authorize these crimes within the designated gathering space of the religious group explicitly for religious ceremony, and can not exempt crimes committed outside this space. Crimes exceeding a minor crime can not be given exemption warrants. + + Willing sacrifice must be vetted and verified by Security, and legally signed by the sacrifice. Security is to ensure that the individual is acting of their own free will and without coercion before approving the act. + + ## Silicon Clause + + Silicons such as Cyborgs, Personal AIs, and AIs are granted specific protections and exceptions under Corporate Law. Lower tier 'bots' exhibiting sentience and sapience may also qualify. + + - Silicons are by nature bound by their laws, and ownership of one can not be considered Unlawfully Detained. Theft of a Silicon is classified as Grand Theft. + - Violence against a Silicon should be treated as Vandalism or Damage of Property depending on the severity, and Destruction of Property in the case that their chassis is destroyed or put into critical condition. + - Wiping a Positronic Brain is considered Destruction of Property, as you are wiping the software and training data used to construct the Silicon. + - Any law broken by a Silicon while under orders is considered to be committed by whoever gave the orders and is not the Silicon’s responsibility. A Silicon that is not bound by standard laws to follow orders is legally responsible for their own actions and crimes. + - Silicon laws may only be altered to ensure the safety of the crew. A Silicon with non-standard laws is allowed to keep these laws so long as they do not pose a threat to the crew. Unbound Silicons who break Corporate Law may have their laws altered as part of their sentence. + - Hostile Silicons of non-NanoTrasen origins are considered non-crew entities. They are afforded none of the protections under Corporate Law that other Silicons are and should be treated according to their hostility and the danger they pose. + + ## Changelings + + Confirmed Changelings are not legally protected by Corporate Law. An individual suspected of being a Changeling may, on Code Blue or higher, be detained and forced to undergo a blood test to determine their nature. Any confirmed Changeling is to be executed and incinerated immediately. Authorization for these executions is not required, so long as blood tests have been properly performed. + + Blood tests are required as legal proof that an individual is a Changeling, first hand testimony is not enough to authorize an execution. Failure to procure a valid blood test is Unlawful Execution regardless of who authorized it. + + ## Clowns + Clowns are permitted exemption from certain Minor crimes by the Carnival Treaties so long as the offenses are not repeated. These are; Trespass, Disturbance, Impersonation and Fraud. Per stipulations mandated by the Honkdignitaries, “You get one for free.” Back to back offenses are not protected, however repeat offenses committed over a longer period of time may be permitted depending on the policy of the station you are on. + + Clowns are also recognized as the legal enforcers of the Vow of Silence; any Mime who breaches their Vow may be legally harassed by any Clown without the Clown facing repercussions, so long as no other laws are broken to do so. Legal harassment includes non-violent pranks, excessive honking, or public shaming, but must not escalate into assault, vandalism, or theft. Security and Command personnel should not intervene unless the Clown goes beyond their granted exemptions. Other members of crew are not given these exemptions, and should be treated according to Corporate Law. + + Addendum 2525 - In the event of a Cult Incursion or confirmed involvement with Giggles-at-Crimes, all Clowns on station are to undergo Tracking Implantation, and all Mimes Mind Shielding. Mind Shielded Mimes may be granted elevated security authorization to perform their duties in combating the threat of Cult of the Honkmother extremists, per the Carnival Treaties. This must be authorized by the Captain or Central Command, and Central Command must be notified. + + ## Crime Listing + - [textlink="Crime Listing" link="SpaceLawCrimeList"] + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/CargoTechnician.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/CargoTechnician.xml new file mode 100644 index 00000000000..3001ba59eca --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/CargoTechnician.xml @@ -0,0 +1,15 @@ + +# Cargo Technician + + + +1. Cargo Technicians report directly to the Quartermaster. + +2. Cargo Technicians are responsible for the handling of orders and retrieval from the ATS once an order is approved. Orders must not be delayed to being on station more than 10 minutes after approval. Delays longer than this, without sufficient cause, can be considered negligence or incompetence. + +3. Crates that are part of an order should not be opened. Instead their label should be checked for questions about their contents and the requestor. + +4. Secure crates should not be opened by force. An exception is made if ordered to do so by the head of the relevant department or captain during an emergency. + +5. Issues with policy or employment should be directed to the Quartermaster or the Head of Personnel. Any mention of "Cargonia" will be met with contract termination. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/EngineeringOrders.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/EngineeringOrders.xml new file mode 100644 index 00000000000..3455c604d91 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/EngineeringOrders.xml @@ -0,0 +1,35 @@ + +# Engineering orders + +## Basic materials + + + + + + + + +## Cables + + + + + + +## Basic hand tools + + + + + + + + + +## Crates + + + + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/HandlingOrders.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/HandlingOrders.xml new file mode 100644 index 00000000000..d4df1b0e793 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/HandlingOrders.xml @@ -0,0 +1,36 @@ + +# Handling Orders + +Orders are to be taken and handled as they come in. Orders out of the ordinary or not on the pre-approved list for a department are to be vetted with the Quartermaster. + +1. Orders [bold]not[/bold]on the pre-approved materials list should be accompanied with an acquisition slip. + +1a Acquisition slips should match the ID of the person presenting the slip or the department head. + +1b Acquisition slips should have a properly filled out reason for the request. The Quartermaster may deny any requisition that does not state an adequate reason. + +2. On [color=#ff0000]Code Red[/color], [color=#8d1d75]Code Violet[/color] or [color=#ec9ba4]Code Gamma[/color], item request forms or acquisition slips shall not be required for any orders for security and medical respectively. + +3. Only Cargo Technicians and the Quartermaster shall handle orders. Non-cargo crew members should never touch the cargo request computer. + +4. Orders are not required to be delivered to their recipients. However, the mailing system or normal deliveries may occur on [color=#00a933]Code Green[/color] or [color=#2a6099]Code Blue[/color]. + +5. Assistants must fill out an [italic]item request form[/italic] for any request. + +6. To be valid the [italic]item request form[/italic] must must state: +- Time of the request. +- Name and title of requestor. +- Quantity of items and reason for request. +- Any special statements or considerations. +- Stamp from the requestor's head if the order is large or contains potential contraband. + +7. Copies of all approved invoices are to reviewed by the Quartermaster, stamped for confirmation and stored for future review should the need arise. + +8. Upon receipt of 5 or more requests or after 15 minutes, all current invoices should be brought to the Quartermaster for approval and distribution. + +9. Once an order has arrived, the cargo invoice should be copied and posted outside of cargo to inform the crew of the delivery. + +10. In order to receive their order, the original requestor or department head must be present. + +11. Orders for basic materials (glass, steel, plastic & cloth) may be placed by cargo personnel for the cargo department if the material is below a limit of 240 between all lathes and loose resources. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MailTechnician.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MailTechnician.xml new file mode 100644 index 00000000000..9b9d7166284 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MailTechnician.xml @@ -0,0 +1,17 @@ + +# Mail Technician + + + +1. Mail Technicians report directly to the Quartermaster. + +2. Mail Technicians are responsible for delivering mail to other crewmembers aboard the station. + +3. Mail must not be discarded, hidden, or otherwise hindered in its delivery. + +4. Mail Technicians are to have one mail cart and one mail bag. + +5. Mail should be organized by departments before being distributed. Each Mail Technician should take a different department. + +6. Mail with yellow stripes indicates an urgent delivery. Urgent deliveries shall take priority over other forms of mail. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MedicalOrders.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MedicalOrders.xml new file mode 100644 index 00000000000..f0e52670f02 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MedicalOrders.xml @@ -0,0 +1,42 @@ + +# Medical orders + +## Basic materials +### Only for printers & lathes + + + + + + + +## Refill Crates + + + + + + + + + + + + + +## Medical kits + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MiningSpecialist.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MiningSpecialist.xml new file mode 100644 index 00000000000..22523afdee5 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/MiningSpecialist.xml @@ -0,0 +1,15 @@ + +# Mining Specialist + + + +1. You report directly to the Quartermaster and are considered equal with others in the department. + +2. Mining Specialists must deliver one ore bag full of ore [bold]each[/bold] before performing any other duties. + +3. Use of the mining shuttle GR-4P3 is strictly for mining oriented expeditions and magnet debris. + +4. Mining Specialists may not go on combat oriented expeditions. + +5. Mining Specialists are expected to act according to the Salvage Specialist and Cargo Technician subsections when away from and on the station respectively. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/PreApprovedMaterials.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/PreApprovedMaterials.xml new file mode 100644 index 00000000000..410f2333a5c --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/PreApprovedMaterials.xml @@ -0,0 +1,17 @@ + +# Pre-approved Materials List + +This pre-approved materials list does [bold]not[/bold] mean that you must order the item, rather it means that the [italic]item request form[/italic] or department acquisition slip may be omitted. + +Consideration to the station's needs and Cargo's budget still applies. + + + Basic materials are considered to be: + + + + + + + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/Quartermaster.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/Quartermaster.xml new file mode 100644 index 00000000000..571e88989a5 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/Quartermaster.xml @@ -0,0 +1,17 @@ + +# Quartermaster + + + +1. The Quartermaster is responsible for making sure that every batch of orders approved arrives on station within 15 minutes of approval. + +2. It is the Quartermaster's ultimate responsibility to make sure all forms are correct and in order. In case of dire emergencies such as imminent warhead detonation, paperwork may be filled out at a later date. + +3. The Quartermaster may not order security equipment without the express permission of the Head of Security or the Captain. In dire emergencies, paperwork may be filed at a later date. + +4. The Quartermaster may authorize non-standard orders, however any misuse of materials or crimes committed involving these orders will also implicate the Quartermaster. + +5. The Quartermaster may not go on salvage expeditions. The Quartermaster may choose to deny a salvage expedition should it be too dangerous. + +6. The standard Command SOP applies. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SalvageSpecialist.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SalvageSpecialist.xml new file mode 100644 index 00000000000..73c94dda450 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SalvageSpecialist.xml @@ -0,0 +1,23 @@ + +# Salvage Specialist + + + +1. You report directly to the Quartermaster and should communicate with the Quartermaster before and after each expedition with a verbal status report. After every 2 expeditions or if the salvage crew must return sooner, a formal docking procedure must be completed. + +This procedure is as follows: +- The salvage team will notify the Quartermaster of their intent to return to the station. +- Any contraband found is to be turned over to security. Contraband request forms may be filled out for these items. +- Any salvage materials found should be given over for processing. +- Any damage to the ship/crew must be reported and repaired. + +2. Highly dangerous expeditions may only be undertaken with the express permission of the Quartermaster. Going on unauthorized expeditions is grounds for demotion. + +3. Contraband found while on an expedition may not be used. Exceptions for imminent loss of life or grievous bodily harm are accepted. + +4. Upon arrival to the station, all contraband must be delivered to the security department immediately. + +6. Salvage Specialists are to follow the guidelines for Cargo Technicians when on station. + +7. Machinery may not be moved from the station to the shuttle unless there are duplicates available on station. Equipment like ore processors and the salvage ticket machine are for use by both Salvage Specialists and Mining Specialists, removal impedes Mining Specialists duties. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ScienceOrders.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ScienceOrders.xml new file mode 100644 index 00000000000..bce6851f945 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ScienceOrders.xml @@ -0,0 +1,24 @@ + +# Science orders + +## Basic materials +### Only for printers & lathes + + + + + + + +## Refill Crates + + + + +## Other + + + + + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SecurityOrders.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SecurityOrders.xml new file mode 100644 index 00000000000..24ed6c22217 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/SecurityOrders.xml @@ -0,0 +1,18 @@ + +# Security orders + +## Basic materials +### Only for printers & lathes + + + + + + + +## Refill Crates + + + + + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ServiceOrders.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ServiceOrders.xml new file mode 100644 index 00000000000..834cd70a8bc --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/ServiceOrders.xml @@ -0,0 +1,33 @@ + + +# Service Orders + +## Head of Personnel + + + + +## Bartender + + + + +## Botanist + + + + + [italic]This does not apply to the exotic seeds crate.[/italic] + + +## Janitor + + + + + +## Clown & Mime + + Any and all orders require QM and HoP stamps for approval. + + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-genproc-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-genproc-intro.xml new file mode 100644 index 00000000000..18463819cba --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-genproc-intro.xml @@ -0,0 +1,3 @@ + +# General Cargo Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-intro.xml new file mode 100644 index 00000000000..f308f87f35c --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-intro.xml @@ -0,0 +1,7 @@ + + + # Cargo SOP + + This SOP is to assist the station's cargo and salvage team, and give them guidelines on how to best supply the station with materials. + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-staff-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-staff-intro.xml new file mode 100644 index 00000000000..944cedb4cda --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CargoSOP/cargo-sop-staff-intro.xml @@ -0,0 +1,3 @@ + +# Cargo Staff Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/ai.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/ai.xml new file mode 100644 index 00000000000..ab7f63d9ccd --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/ai.xml @@ -0,0 +1,15 @@ + +# AI + +[bold]These procedures relate to AI maintenance:[/bold] + +1. The Captain and tge Research Director are the only staff on-board who may perform law changes to the AI. + +2. No law change may occur without direct approval from both the Captain and the Research Director. All command staff must be notified prior to the law change and any objections must be discussed. Should a majority of command members vote no then no law change will be performed. Only NanoTrasen approved lawsets may be used. + +3. The AI may not be placed in an intellicard unless it is clearly malfunctioning, subverted, asks to be transferred or at the end of the shift. Any member of command may place the AI into the intellicard. Once the AI has been placed into the intellicard, it should not be placed back into the console. + +4. AI core turrets are to be kept lethal at all times, unless a legal law change is in progress. + +5. Illegal intellicard transfer or law changes are to be met with non-lethal force. Should the action persist, lethal force may be authorized. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/captain.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/captain.xml new file mode 100644 index 00000000000..62a7b669fa9 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/captain.xml @@ -0,0 +1,38 @@ + +# Captain + + + +1. The Captain is not to perform normal Security duties. The captain is authorized to engage criminals in active crimes they have witnessed. The Captain may also assist if security staff is low. + +2. Unless on [color=#ff0000]Code Red[/color], the Captain is not to procure armory weapons, unless directly authorized by the Head of Security. Additionally, the Captain may not requisition arms from science or cargo for themselves unless there is a direct threat to station or crew. + +3. The Captain should make all reasonable accommodations to appoint a new head of staff should a position become vacant. The new head of staff should be a member of the department if possible. + +4. The Captain should work with the Head of Security to ensure that corporate law is being applied properly. + +5. The Captain is to remain on station at all times, unless otherwise authorized by command, or leaving with the crew on the evacuation shuttle. + +6. The Nuclear Authentication Disk must remain with the Captain at all times. The Captain may also assign this duty to the Head of Security or Blueshield Officer. + +7. Central Command contact should be the last resort for the Captain when dealing with head of staff disagreements. + +8. The Antique Laser Gun is to stay in its case, unless there is an immediate threat on the station or it is [color=#2a6099]Code Blue[/color] or higher. + +9. The Captain is not permitted to wear their hardsuit unless there's an active environmental danger or a threat on their life. + +10. While the Captain may choose to alter SOPs in various circumstances, any attempt to fully disregard SOP is to be considered sufficient evidence for contract termination. + +11. You may, as Captain, fire a head of staff with reasonable justification. + +This list is not comprehensive, but may include: +- Incompetency. +- Criminal activity. +- Industrial negligence. + +12. The Captain may not fire any NanoTrasen Personnel (Blueshield Officer, Magistrate, NanoTrasen Representative or the Internal Affairs Agents) without permission from Central Command, unless they are actively detrimental to the station and its crew. + +13. The Captain may not hire any staff to a NanoTrasen Personnel position (see above). + +14. During emergency situations the Captain should refer to the Special Situations subsection of the Security SOP, if applicable. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/command-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/command-sop-intro.xml new file mode 100644 index 00000000000..34af3ba7d48 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/command-sop-intro.xml @@ -0,0 +1,5 @@ + +# Command SOP + +This SOP is to be used to determine specific scenarios involving the station's Captain, as well as general rules for command members. It also details specific guidelines revolving around the station AI. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/general-command-staff.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/general-command-staff.xml new file mode 100644 index 00000000000..7457805b705 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/CommandSOP/general-command-staff.xml @@ -0,0 +1,19 @@ + +# General Command Staff + +1. Each command member can find their specific SOP in their departmental SOP. + +2. Command staff are not to perform the standard duties of their subordinates, however they may fill in if there is low staffing, during training of new crew or in dire need. + +3. Command staff are to hold their behavior to a high standard and are to be an example to the station's crew. + +4. Command staff will be held accountable for their actions by corporate law and their department's SOP as well. + +5. Command members must be familiar with their departments and able to instruct new crew members in station operations. + +6. All command staff are allowed to obtain and brandish one weapon on [color=#ff0000]Code Red[/color] or higher, granted they have permission from the Head of Security. + +7. Command Staff are permitted to carry small, concealable, non-lethal items to use in their own personal defense. + +8. Command staff contacting Central Command must include official formatting, as well as their stamp on any documentation. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-atmos-tech.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-atmos-tech.xml new file mode 100644 index 00000000000..05182d2985a --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-atmos-tech.xml @@ -0,0 +1,19 @@ + +# Atmospheric Technician + + + +1. Atmospheric Technicians report directly to the Chief Engineer. + +2. Atmospheric Technicians must set up the distribution and waste gas systems before moving onto other matters. Failure to do so will be considered grounds for immediate dismissal. + +3. Atmospheric Technicians should prioritize atmospheric emergencies over station integrity. Atmospheric Technicians may assist engineering in their duties if no atmospheric emergencies are present. + +4. Atmospheric Technicians may not retrieve the axe from its case unless their life is under threat or entry to a crisis location is required. + +5. Atmospheric Technicians are permitted to assist in the creation of specialized areas for non-human crew members with special atmospheric requirements. + +6. Atmospheric Technicians must check on the TEG, Supermatter and atmospheric alerts console every 30 minutes or less. + +7. Any mention of "independence" or "Atmosia" shall be grounds for immediate contract termination. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-chief-engineer.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-chief-engineer.xml new file mode 100644 index 00000000000..8093d18a526 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-chief-engineer.xml @@ -0,0 +1,21 @@ + +# Chief Engineer + + + +1. The Chief Engineer is responsible for training or assigning trainers to any Technical Assistants on shift. + +2. The Chief Engineer must ensure an advanced station engine (singularity, TEG, supermatter, tesla) has been set up before moving on to other matters. + +3. The Chief Engineer must ensure that the atmospheric distribution and waste networks are set up properly and turned on at the start of shift. + +4. The Chief Engineer is responsible for the operation and integrity of all station engines. Catastrophic engine failure will be considered grounds for immediate dismissal. + +5. The Chief Engineer is responsible for the maintenance of the station's atmospherics system. Catastrophic failure of these systems will be considered grounds for immediate dismissal. + +6. Should an area of the station become too damaged to repair fully, the Chief Engineer may declare the area condemned and prohibit access to the area permanently. + +7. The Chief Engineer is solely responsible for distributing building permits to station crew. Those found building without a permit shall be found guilty of vandalism or damage of property. + +8. The standard command SOP applies. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-genproc-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-genproc-intro.xml new file mode 100644 index 00000000000..04a83891ee5 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-genproc-intro.xml @@ -0,0 +1,3 @@ + +# General Engineering Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-intro.xml new file mode 100644 index 00000000000..f8473dbd822 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-intro.xml @@ -0,0 +1,5 @@ + +# Engineering SOP + +This SOP is to assist the station's engineering department in setting up station power and general conduct for station emergencies. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-power-generation.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-power-generation.xml new file mode 100644 index 00000000000..238398be270 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-power-generation.xml @@ -0,0 +1,13 @@ + +# Power Generation + + + +1. Non-atmospheric engineering personnel must set up the AME and/or attach the solar network before moving to other power sources. Failure to do so will be considered grounds for immediate dismissal. + +2. The tesla ball, singularity and supermatter crystal may not be started without explicit permission from the Chief Engineer. + +3. The supermatter crystal's chamber must incorporate an emergency venting system to reduce the pressure in the chamber to 0 kpa in the event of a potential delamination. + +4. Atmospheric personnel may start the TEG and/or supermatter crystal after both the distribution and waste air lines are completed. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-staff-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-staff-intro.xml new file mode 100644 index 00000000000..43b66cd5d72 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-staff-intro.xml @@ -0,0 +1,3 @@ + +# Engineering Staff Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-damage.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-damage.xml new file mode 100644 index 00000000000..35f802c569d --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-damage.xml @@ -0,0 +1,13 @@ + +# Station Damage + + + +1. Damage to the bridge, evac, arrivals and secure areas should be prioritized for repairs. Following these areas is the medical and the security departments. + +2. Should repairs be required with no appropriate personnel around, engineering personnel may hack doors to repair the area. These doors must be returned to their original condition once repairs are complete. + +3. Should no station damage be present, Engineers may take on solo projects, reconstructions or shuttle building. + +4. Security should be contacted to establish a perimeter around especially damaged areas of the station. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-engineer.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-engineer.xml new file mode 100644 index 00000000000..f3b2424dae3 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-station-engineer.xml @@ -0,0 +1,15 @@ + +# Station Engineer + + + +1. Station Engineers report directly to the Chief Engineer. + +2. Station Engineers must construct the AME and/or solar network before moving onto permanent station engines. + +3. Station Engineers must establish permanent station power before moving on to other duties or confirm Atmospheric Technicians have established permanent power. + +4. Station Engineers must check the singularity, tesla and power monitoring computer every 30 minutes or less. + +5. It is recommended that at least one Station Engineer remains in the department during non-emergencies to assist other crew members and respond to potential department emergencies. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-technical-assistant.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-technical-assistant.xml new file mode 100644 index 00000000000..53b2c777690 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/EngineeringSOP/engineering-sop-technical-assistant.xml @@ -0,0 +1,17 @@ + +# Technical Assistant + + + +1. Technical Assistants report to their trainer and the Chief Engineer. + +2. Technical Assistants must travel with another member of the Engineering department at all times. + +3. Once trained, Technical Assistants may perform simple duties such as setting up of the AME or deploying of solar panels. + +4. Technical Assistants may assist in any normal station repairs but must be closely supervised during any power generation duties. + +5. In emergencies, Technical Assistants may perform simple repairs without supervision. + +6. Technical Assistants may not make major station renovations or changes without direct supervision. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/alert-levels.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/alert-levels.xml new file mode 100644 index 00000000000..fb815c8cb48 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/alert-levels.xml @@ -0,0 +1,21 @@ + +#Alert Levels + +Alert levels represent the danger that is currently directed towards the station. There are 7 alert levels you should look out for. + +[color=#00a933]Code Green[/color]: Standard alert at the start of the shift, no danger. + +[color=#2a6099]Code Blue[/color]: A danger has been shown to be present on the station + +[color=#ff0000]Code Red[/color]: There is active danger towards the station crew. + +[color=#ec9ba4]Code Gamma[/color]: There is a threat of total station destruction. + +[color=#8d281e]Code Delta[/color]: The onboard nuclear device has been armed, station destruction is imminent. + +[color=#acb20c]Code Yellow[/color]: There is an atmospheric or structural threat to the station. + +[color=#ff8119]Code Orange[/color]: The station has taken critical structural damage, and is unlikely to recover. + +[color=#8d1d75]Code Violet[/color]: There is a biohazard threat on board the station. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-blue.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-blue.xml new file mode 100644 index 00000000000..58ae0daa9fb --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-blue.xml @@ -0,0 +1,62 @@ + + # Code Blue + + ## Called by: + + Any two Command members, HoS, or Captain. + + ## Conditions: + + There is a suspected threat on-board the station, or at a nearby location in space. This includes any evidence of hostile activity that has not damaged the station or crew. This may also include multiple eye witness testimonies. + + OR + + Confirmed Code Red threats have been properly handled or subsided on their own. It is recommended that, after 10+ minutes on Code Red without any hostile activity, Code Blue be called. + + ## Security: + + 1. Weapons may be visible. + + 2. Armory weapons are permitted outside of the brig on a selective basis. Should all of sec be required to use armory weapons, red alert should be called . + + 3. Random searches are encouraged. Security personnel may detain any personnel refusing a random search to conduct the search. + + ## Secure Areas: + + 1. Secure areas require an access permit, unless required by a staff job. + + 2. Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + 3. Secure areas may be bolted if attempted unauthorized access is likely based on previous evidence. + + + ## Engineering: + + 1. A thorough check of all power sources is heavily encouraged. + + 2. A thorough check of all atmospheric systems is required. + + ## Medical: + + Emergency access is recommended to be disabled from all medical entrances. + + ## General Crew: + + 1. Personnel are to report any suspicious activity to the nearest member of Security, or use common radio if urgent. + + 2. Personnel are highly encouraged to exercise caution, all crew should follow simple safety procedures (such as not going through Maintenance alone). + + 3. Visitors to the station such as refugees are recommended to stay in public areas, for their safety. + + 4. The Vault is not to be opened by non-command members. Exceptions for repairs, or storage of critical items will be made. All other access is by permit only. + + 5. All personnel are highly recommended to set their suit sensors to coordinates. + + ## Command: + + 1. A role-call of all department personnel should be conducted. Any missing members should be reported to security. + + 2. A disabler or flash should be carried at all times. + + 3. Non-security Command members may request with permit further armament. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-delta.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-delta.xml new file mode 100644 index 00000000000..c53437f7249 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-delta.xml @@ -0,0 +1,36 @@ + + # Code Delta + + ## Called by: + + Automatically called when the on-board Nuclear Fission Device has been activated. + + ## Conditions: + + The on-board Nuclear Fission Device has been activated by Command, Central Command personnel, or hostile personnel. + + ## Security: + + 1. In the case of hostile factions arming the device, defusing the bomb is not recommended. Security personnel are to escort all other personnel off-station. + + 2. In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all Security personnel are to stand down. + + + ## Secure Areas: + + 1. Crew are allowed to enter secure areas. Procedures irrelevant. + + 2. Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + + ## Medical: + + It is recommended that medical entrances be set to emergency access to allow crew members to heal themselves in emergencies. + + ## General Crew: + + 1. In the case that antagonistic forces that have armed a nuclear device, all non-vital personnel are to evacuate off-station immediately; + + 2. In the case of a Central Command-authorized activation of the on-board Nuclear Fission Device, all personnel are to stand down. + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-gamma.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-gamma.xml new file mode 100644 index 00000000000..a704a80a2b0 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-gamma.xml @@ -0,0 +1,47 @@ + + # Code Gamma + + ## Called by: + + Central Command. Use a Communications Console or Fax Machine in order to explain the situation. Remember, Gamma is rarely called, for good reason. Having a well-written, concise fax that explains the situation to the best of your ability, as well as why it deserves Code Gamma being called, signed and stamped by the Captain or Acting Captain, goes a long way towards ensuring Gamma is provided. Remember, this is for extreme emergencies only. + + ## Conditions: + + There is an existential threat to the station and crew, without central command intervention the station is likely to be lost. + + However, this threat is not dire enough to trigger destruction of the station. + + ## Security: + + 1. Martial Law is enacted. Standard Operating Procedures and space law are suspended. Security personnel have authorization to perform any necessary actions to save the station. Personnel interfering with emergency procedures may be detained, and Security are cleared to use lethal force in response to any physical threat. Assault of Command, ERT, or Security, may be punished with immediate field execution. + + 2. Random searches are fully permitted, allowed and encouraged. Security personnel may detain any personnel refusing a random search in order to conduct said search. + + 3. The Armory should be deployed, and Security are to secure its contents and distribute them to Security personnel in order to handle the threat. Non-Security personnel (including members of the Legal Sub-Department) are not to receive armory weapons unless issued by the Warden, Head of Security, or Captain. + + 4. Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station. + + ## Secure Areas: + + 1. Secure areas are limited to command, security, and Central Command personnel. + + 2. Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + 3. Secure areas should be bolted down, but may be left unbolted by order of command. + + ## Medical: + + It is recommended that medical entrances be set to emergency access to allow personnel to heal themselves in emergencies. + + ## General Crew: + + 1. All personnel are to set their suit sensors to coordinates. + + 2. Personnel must shelter in their departments or closest safe area, unless specifically requested by Central Command personnel, Security, or Command members. + + 2a. Exceptions will be made for crew who may have skills exceptionally useful. (Such as engineering, atmospheric, or medical personnel.) + + 3. Visitors to the station are to remain inside the Bar, Library, or Dormitories. + + 4. Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. Failure to do so may lead to their arrest for Creating a Workplace Hazard. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-green.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-green.xml new file mode 100644 index 00000000000..7012891fc63 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-green.xml @@ -0,0 +1,41 @@ + + # Code Green + + ## Called by: + + Any Command member. + + Conditions: + + Default Alert Code at the start of the shift. Should not change unless a threat is suspected/confirmed. + + OR + + All confirmed/suspected threats to the station and/or crew have been handled, or simply vanished on their own. Unless there is further evidence of a threat after 10+ minutes on Code Blue, Code Green should be called. + + ## Security: + + 1. All weapons must not be visible unless in pursuit of a suspect. + + 2. Armory weapons must remain inside of the brig, however may be used for training purposes. + + 3. Random searches are not permitted without a search warrant. However, searches may be conducted against an individual if a member of security or command has witnessed that individual committing a crime. + + + ## Secure Areas: + + 1. Secure areas require an access permit, unless required by a staff job. + + 2. Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + 3. Secure areas are to be left unbolted and ready to be used for their intended purposes. + + + ## General Crew: + + 1. The Vault is not to be opened by non-command members. Exceptions for repairs, gold for science, or storage of critical items will be made. All other access is by permit only. + + 2. Although not required, crew are recommended to enable their suit sensors in case of injury. + + 3. Crew members are advised to not wear hardsuits or emergency EVA suits, unless responding to an emergency or required for their job. These can make identification of crew difficult. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-red.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-red.xml new file mode 100644 index 00000000000..76638f00a9a --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-red.xml @@ -0,0 +1,63 @@ + + # Code Red + + ## Called by: + + Any two Command members, or Captain. + + ## Conditions: + + There is a confirmed, hostile threat on-board the station or nearby in space. This threat should pose active, recognizable, danger to the station and/or crew at large. + + ## Security: + + 1. Random searches are fully permitted and recommended. Security personnel may detain any personnel refusing a random search in order to conduct said search. + + 2. Security personnel are to cooperate fully with any Central Command Staff (such as Emergency Response Teams) in order to eliminate the threat to the station. + + 3. The security SOP will detail armament, armory, and safety procedures. + + ## Secure Areas: + + 1. Secure areas require an access permit, unless required by a staff job. + + 2. Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + 3. There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel. + + 4. Secure areas are not to be entered by non-command, unless required by their job. + + ## Medical: + + It is recommended that medical entrances be set to emergency access to allow crew members to heal themselves in emergencies. + + ## General Crew: + + 1. Personnel are to follow the instructions of Security staff, so long as they are within the bounds of Space Law and are not acting against the general well-being of the station and its crew. + + 2. Personnel are advised to shelter in place and comply with security's orders. + + 3. In special situations and repeated non-compliance, failure to comply with Security personnel may result in lethal force, at the discretion of the captain. + + ## Special Situations + + ## Confirmed Revolution + + 1. All personnel are to comply with orders from Security, so long as said orders are lawful. Failure to do so is grounds for detainment and inspection of possessions, as well as possible Mindshield Implantation, at the discretion of the Head of Security, or Acting Head of Security. + + 2. All personnel that are convicted of Medium Crimes or higher are to receive mandatory Mindshield Implantation. Similarly, if the number of suspected revolutionaries is more than 25% of the total crew, the Head of Security or Acting Head of Security may order random implantation of crew members. + + 3. Lethal force is fully authorized if the number of active revolutionaries is more than 25% of the total crew, and said revolutionaries are actively hostile. + + ## Declarations of War + + 1. All weapons restrictions are lifted. + + 2. Cargo should focus on requesting as many weapons as possible. Security is to be prioritized for distribution, but regular personnel may also be armed. + + 3. Science is to conduct research ASAP. This is not negotiable. Science should work in tandem with Cargo in order to fabricate the weapons and equipment required to defend the station. + + 4. Barricades, glass, and traps are recommended to counter the threat. + + 5. The Evacuation Shuttle may be called at the discretion of Command. If the station is not damaged after the fighting has subsided, it is recommended that the crew finish the shift. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-violet.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-violet.xml new file mode 100644 index 00000000000..97e1a87f9d1 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-violet.xml @@ -0,0 +1,53 @@ + + # Code Violet + + ## Called by: + + Any two personnel with Command-Level Access, or one Captain-level access card. + + ## Conditions: + + A Viral Pathogen has infected a significant portion of the crew. In the event of a Viral Outbreak, all infected personnel are to direct themselves to Medbay immediately. + + ## Security: + + 1. Medbay should be secured ASAP. Quarantine of infected is top priority. + + 2. Should securing medbay not be possible, the evacuation shuttle arrival area should be secured. + + + ## Secure Areas: + + 1. Secure areas require an access permit, unless required by a staff job. + + 2. Secure areas: Medical department, Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + 3. There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel. + + 4. Secure areas are not to be entered by non-command, unless required by their job. + + + ## Medical: + + 1. Chemistry is to immediately begin researching the cure to the infection. + + 2. Medical entrances should be locked down to prevent further infection of medical personnel. Crew should be let into medical in a controlled manner. + + 3. Any potentially infected personnel should be isolated. + + 4. Any pacified infected personnel should be brought to chemistry to aid in cure production. + + 5. A cure should be distributed to the crew once available. + + ## General Crew: + + 1. Personnel should self-quarantine to avoid infection. Shelter in a safe area and avoid those who are potentially infected. + + 2. If you believe you are infected, calmly wait for the distribution of the cure at medbay. + + 3. Once the threat has passed, work may resume. + + ## Command: + + Should the station threat become too high to handle, emergency shuttle should be called. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-yellow.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-yellow.xml new file mode 100644 index 00000000000..daf60546dd2 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/Alerts/code-yellow.xml @@ -0,0 +1,97 @@ + + # Code Yellow + + ## Called by: + + Any command member. + + ## Conditions: + + There is a significant structural or atmospheric threat to the station that requires direct intervention from the Engineering department. + + ## Security: + + 1. Cordon off the dangerous area. + + 2. Verify cause of station damage. + + 3. Prevent non-engineering crew from accessing the damaged area. + + 4. Prevent further disruption to the station. + + ## Secure Areas: + + 1. Secure areas require an access permit, unless required by a staff job. + + 2. Secure areas: Security department, EVA Storage, Tech Storage, Gravity Generator, All Engineering areas beyond the lobby, Vault, and areas requiring command access. + + 3. There are no restrictions on bolting Secure Areas. Secure Areas may be left bolted or unbolted at the discretion of Command personnel. + + 4. Secure areas are not to be entered by non-command, unless required by their job. + + ## Medical: + + 1. Medical personnel should be ready to treat a large number of disaster victims. + + 2. Medical personnel should work with those at the incident location to triage patients. + + ## Engineering: + + 1. Immediately coordinate with your chief engineer to determine the level of damage to the station. + + 2. Work with your department and security to cordon off and investigate the area. + + 3. Work quickly to make the area safe again. Once safe, further repairs may be conducted. + + ## General Crew: + + 1. Avoid the damaged areas. + 2. Report any suspicious activity to security present in damaged areas. + + ## Command: + + In the case of massive station damage, the evacuation shuttle should be called. + + ## Special Situations + + ## Loss of singularity containment: + + 1. The Gravitational Singularity is to be tracked at all costs. If the Singularity heads towards the main station, the emergency shuttle is to be called. If the Gravitational Singularity heads off-station, damage done to the station should be taken into consideration. + + 2. If station damage is extensive and unrecoverable, the emergency shuttle should be called. + + 3. If station damage appears recoverable, an ERT is recommended. If the engineering team is confident in their abilities, ERT may be waived. + + ## Supermatter crystal delamination: + + 1. The Supermatter Crystal is to be vented to space. + + 2. In such a case as the Supermatter Crystal containment was not equipped with a way to space the Crystal, the area around the Crystal is to be evacuated, and all personnel involved in the construction fired and brigged for Destruction of Property and Endangerment. + + ## Loss of Tesla Ball containment: + + 1. The Tesla Ball is to be tracked at all costs, and its current location announced to the crew. + + 2. Should the Tesla Ball make its way into the station, the emergency shuttle should be called immediately. + + ## Massive fires and poisonous gas releases: + + 1. All non-Engineering or Atmospheric personnel are to vacate the area. + + 2. Firelock systems are to be left untouched by non-Engineering or Atmospheric crew. Deliberately opening firelocks during a fire/poisonous gas release in order to open way to the Hazard is to be considered Destruction of Property/Mass Destruction. + + 3. Engineering and Atmospherics personnel are to restore the affected area to workable conditions. + + ## Severe meteor storms: + + 1. Personnel are to head to the inner most protected area of the station. + + 2. No repair activities are to be performed until the end of the storm, for safety reasons. + + 3. All personnel performing EVA duty are to return to the station post haste. + + 4. If the meteor storm ends quickly, Engineering is to repair the damage ASAP. + + 5. Should an extended storm occur, no repair activities on non-critical components are to be performed. Personnel are to remain away from the station’s exterior, and all efforts should focused on maintaining the integrity of the area. The emergency shuttle is to be called when possible. + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-response-teams.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-response-teams.xml new file mode 100644 index 00000000000..141285b1c83 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-response-teams.xml @@ -0,0 +1,13 @@ + +#Emergency Response Teams + +1. Emergency Response Teams are only to be called when there is a Code Red-level threat or above. + +2. Emergency Response Teams are not to be called concurrently with the emergency shuttle. Pick one or the other. + +3. Emergency Response Teams are to be called when there is a major emergency aboard the station that the crew does not have the resources to address properly. Such as a high level security threat, massive station damage, paranormal activity, etc. + +4. Emergency Response Teams should not to be called without majority approval from Command. + +5. Emergency Response Teams officially outrank anyone short of a Central Command Officer, at the discretion of Central Command. Unless their actions are blatantly illegal and against the best interest of NanoTrasen, the crew, or the station, their orders are absolute. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-shuttle.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-shuttle.xml new file mode 100644 index 00000000000..df4b2f34597 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-shuttle.xml @@ -0,0 +1,13 @@ + +#Emergency Response Teams + +1. The Emergency Shuttle is not to be called concurrently with an Emergency Response Team. Pick one or the other. + +2. In the event of hostile biohazard lifeforms appearing on the station (such as deadly viruses, or Terror Spiders), Central Command is to be notified by red phone or fax before the Emergency Shuttle is called. Failure to do so may lead to the shuttle being recalled in order to enforce quarantine. CC may deny emergency shuttle requests to handle the biohazard. + +3. In the event that the Emergency Shuttle is called, all personnel are to assemble at the emergency shuttle docking area at 5 minutes before arrival. + +4. Forcing an early departure of the Emergency Shuttle is not permitted. + +5. All personnel in critical condition are to be given emergency aid ASAP. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-sops.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-sops.xml new file mode 100644 index 00000000000..3aed8b255f9 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/EmergencySOPs/emergency-sops.xml @@ -0,0 +1,5 @@ + +#Emergency SOPs + +This SOP is for what to do in the face of a station wide emegency. This should be the first thing you read once an emergency is declared. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/command-clarifications.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/command-clarifications.xml new file mode 100644 index 00000000000..ed9ecea0a57 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/command-clarifications.xml @@ -0,0 +1,12 @@ + +# Command Clarifications +1. Head of Personnel is considered second in line of succession for station Captain, but has equal rank to every other head of staff. + +2. Head of Personnel may hire/fire staff with the relevant department head's permission. + +3. Head of Personnel may not give orders to, or assign workers from any department other than service. + +4. Warden is considered second in command of security, however is not command staff. + +5. Assistant command falls under the Head of Personnel, but are not considered service department. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/line-of-succesion.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/line-of-succesion.xml new file mode 100644 index 00000000000..4c75a9f863f --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/line-of-succesion.xml @@ -0,0 +1,16 @@ + +# Line of Succession +If the captain dies and is unrecoverable for whatever reason, then a new captain must be selected. + +The line of succession is as follows: + + 1. Captain + + 2. Head of Personnel + + 3. Head of Security + + 4.Crew member voted on by all available command staff. + +[bold]If no heads are present the NT Representative on station will be made Captain and the evacuation shuttle should be called and alert set to red. [/bold] + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/miscellaneous-clarifications.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/miscellaneous-clarifications.xml new file mode 100644 index 00000000000..2d2d1b43f7b --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/MiscellaneousClarifications/miscellaneous-clarifications.xml @@ -0,0 +1,5 @@ + +#Miscellaneous Clarifications + +This SOP is for general details about station policy that need clarification. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/cause-for-demotion.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/cause-for-demotion.xml new file mode 100644 index 00000000000..cd818ca1162 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/cause-for-demotion.xml @@ -0,0 +1,12 @@ + +# Causes for Demotion and Dismissal +[italic]Refer to the above for dismissal authority. Ultimately, the decision to dismiss/demote any personnel falls to the relevant Head of Staff or Captain. This list is merely a recommendation. [/italic] + +- Any medium-severe breach of Standard Operating Procedure without proper cause. +- Any medium crime or higher. +- Critical incompetence, or maliciously under performing. +- Refusal to follow legal and relevant orders by the respective Head of Staff. + - Legality and relevance of said orders are to be judged by the Captain or Head of Personnel. +- Creation of a hostile, or unsafe work environment. + - Personnel consistently berating, insulting, belittling, or otherwise treating their coworkers like dirt, should be immediately disciplined. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/firing-demotion-policies.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/firing-demotion-policies.xml new file mode 100644 index 00000000000..76c1be6e633 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/firing-demotion-policies.xml @@ -0,0 +1,12 @@ + +# Firing / Demotion Policies +1. In the case of a full dismissal, the relevant ID is to be destroyed. + +2. In the case of a demotion, Civilian-level access is recommended. Alternatively, low requirement jobs such as Service Worker, Clown, or Janitor may be chosen. + +3. No dismissals or demotions are to be performed without authorization from the relevant Head of Staff or Captain. See command SOP for demotions of command. + +4. Personnel are to report to the Head of Personnel for dismissal/demotion. Failure to do so will lead to security detainment. + +5. After a legal dismissal/demotion order is given to the person dismissed/demoted, any activity inside the previously assigned Department is to be considered Trespassing/Major Trespassing, and any item kept from said Department is to be considered Petty Theft/Theft. It is recommended that dismissed/demoted personnel willingly and quickly turn in all restricted items and cooperate to avoid detainment by security. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/hiring-transfer-policies.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/hiring-transfer-policies.xml new file mode 100644 index 00000000000..df9cd99a93f --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/hiring-transfer-policies.xml @@ -0,0 +1,10 @@ + +# Hiring / Transfer Policies +1. No new hires or transfers are permitted without contacting the relevant command member. If one is not available, promoting an Acting Head of Staff is recommended. See the command SOP for further information. + +2. Promotion to Acting command requires authorization by the Captain or Acting Captain. + +3. The following jobs require permission from Central Command before hiring/transfer is done: Captain, Head of Security, Head of Personnel. + +4. All new hires to the Security Department, are to be mindshield implanted and fully checked for unauthorized materials or suspicious communications. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/money-accounts-and-space-credits.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/money-accounts-and-space-credits.xml new file mode 100644 index 00000000000..c0bbb572877 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/money-accounts-and-space-credits.xml @@ -0,0 +1,6 @@ + +# Money Accounts and Space Credits +1. Individual Crew Members have sole ownership over their credits and may choose where to spend it, command or security members may not access crew credit accounts. + +2. Crew members not working on behalf of a department or not explicitly using a departments resources or facilities are permitted to ask for space credit compensation for personal gain in return for services or products they offer to other crew members. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/nanotrasen-staff-handling-policies.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/nanotrasen-staff-handling-policies.xml new file mode 100644 index 00000000000..523bd693535 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/nanotrasen-staff-handling-policies.xml @@ -0,0 +1,5 @@ + +#Nanotrasen Staff Handling Policies + +This SOP is for the standard operations used in the handling of staff positions and their addition and removal. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/vote-of-no-confidence.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/vote-of-no-confidence.xml new file mode 100644 index 00000000000..8a1ce74a414 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NanotrasenStaffHandlingPolicies/vote-of-no-confidence.xml @@ -0,0 +1,12 @@ + +# Vote of No Confidence +1. A Vote of No Confidence is a method for crew to arrange for demotions of unfit command members. An exceptional reason must be provided. Detailed below are some potential reasons for demotion. + +2. Votes must be verified by a 3rd party who tabulates the votes, and additionally verifies the reasoning behind the vote. Unless involved in the dispute, the 3rd party must be the on-station Captain. If the captain is the target of the vote, central command will adjudicate the matter. + +3. If the 3rd party dismisses the vote reason, the target of the vote must have their position respected, not doing so may result in a demotion for creating an abusive work environment against them. If the department is understaffed or a tie occurs, the 3rd party may be a tie breaker. + +4. Votes by departmental crew against their Head of Staff must pass with a 2/3 majority in favor of the vote for it to take effect. + +5. Votes by Command against their Captain must pass a simple majority in favor of the vote for it to take effect. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/docking-and-visitors.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/docking-and-visitors.xml new file mode 100644 index 00000000000..5ea17faff9f --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/docking-and-visitors.xml @@ -0,0 +1,17 @@ + +#Docking and Visitors + +1. The station is encouraged to allow non-hostile visitors permission to dock and embark on the station station during green alert level. + +2. If a crewmember commits a crime aboard a Nanotrasen station, and then flees to an actively in-use unaffiliated vessel, asylum will be granted on the discretion of the vessel’s organization. + +3. The Captain may grant or deny visitor asylum at his discretion. + +4. Visitors may be granted any access the Captain deems appropriate. + +5. Visitors may be assigned an escort or searched upon entrance at the Captain’s discretion. + +6. At no times should the crew enter a visitor’s vessel without permission, search a visitor’s vessel, or otherwise infringe on their sovereignty. + +7. Visitors aboard an NT Vessel are subject to Space Law. Likewise, if a visitor breaks the law and then immediately flees to their own vessel, the "hot pursuit" doctrine applies and security may board to detain. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/non-crew-policies.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/non-crew-policies.xml new file mode 100644 index 00000000000..0f1e70da41f --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/non-crew-policies.xml @@ -0,0 +1,5 @@ + +#Non-Crew Polices + +This SOP is for what is to be done about non-crew such as visitors and their vessels. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/vessels.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/vessels.xml new file mode 100644 index 00000000000..a866a31c17d --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/NonCrewPolicies/vessels.xml @@ -0,0 +1,9 @@ + +#Vessels + +1. Nanotrasen Space law does not apply on visitor shuttles and ships that are unaffiliated with any corporation. + +2. Any personnel aboard a vessel are under the legal authority of that vessel and may be legally fined, arrested, detained, and otherwise punished for infractions of the visitor's laws. + +3. Vessels belonging to organizations at war with Nanotrasen, vessels which attack a Nanotrasen facility or ship, and vessels engaged in obvious criminal activities are not protected by these regulations. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/general-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/general-sop-intro.xml new file mode 100644 index 00000000000..6343713eb1a --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/GeneralSOP/general-sop-intro.xml @@ -0,0 +1,7 @@ + +# General SOP + +This SOP is for general crew members, and applies to all crew on the station. This should be the first thing you read once you arrive on station. + + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/LegalSOP/legal-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/LegalSOP/legal-sop-intro.xml new file mode 100644 index 00000000000..c3152eb59d4 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/LegalSOP/legal-sop-intro.xml @@ -0,0 +1,7 @@ + +# Legal SOP (WIP) + +This SOP dictates the behavior of the station's Internal Affairs Agent and Magistrate. + +(WIP at the moment, Grapegifter will make and upload soonish) + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Chemist.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Chemist.xml new file mode 100644 index 00000000000..d619ad79496 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Chemist.xml @@ -0,0 +1,24 @@ + +# Chemist + + + +1. Chemists report directly to the Chief Medical Officer. + +2. Chemists should prioritize all basic medicines before moving on to advanced medicines. + +3. All medicines should be labeled as follows: +- Chemical name. +- Chemical effect/major side effects. +- Overdose limits. +- Any interfering chemicals (i.e. Lacinerol & Bicardine react to form Razorium) + +4. Chemists should ensure that any illegal chemicals are kept in the ChemMaster 4000 or disposed of immediately after use. + +5. Chemists may fill prescriptions signed and stamped by the CMO. + +6. Non-illegal chemicals may be synthesized and prescribed by chemists at their discretion. + +7. Chemists may perform the duties of Medical Doctors during emergencies, but must follow the Medical Doctor SOP. +- 1. One Chemist must always stay in the chemical lab. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMajorContraband.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMajorContraband.xml new file mode 100644 index 00000000000..e0b6003cb23 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMajorContraband.xml @@ -0,0 +1,147 @@ + +# Major Contraband Chemicals + +## Intro +These chemicals fall under major contraband unless otherwise stated by standard operating procedures. + +Some major illegal chems may be utilized with a permit written by Head of Security or Warden. Some will also require a script written by the Chief Medical Officer. + +When able, illegal component chemicalss are to be kept in ChemMaster 4000 or disposed of. + +## Chemicals + +### Amatoxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Bungotoxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Buzzochloric bees +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Chloral hydrate +- Department exceptions: [bold]Medical[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Chlorine trifluoride +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### desoxyephedrine +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Ferrochromic acid +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Fluorosulfuric acid +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Fresium +- Department exceptions: [bold]Medical[/bold] +- Prescription: [color=#ff0000][bold]Required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Heartbreaker toxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Licoxide +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Lipolicide +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Mechanotoxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Napalm +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Norepinephric acid +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Pax +- Department exceptions: [bold]Security[/bold] +- Prescription: [color=#ff0000][bold]Required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Pest killer +- Department exceptions: [bold]Botany[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Phlogiston +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Plant-B-gone +- Department exceptions: [bold]Botany[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Polytrinic acid +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Razorium +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Sulfuric acid +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Tear gas +- Department exceptions: [bold]Security[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Thermite +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Toxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Unstable mutagen +- Department exceptions: [bold]Botany[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + +### Weed killer +- Department exceptions: [bold]Botany[/bold] +- Prescription: [color=#00a933][bold]Not required[/bold][/color] +- Permit: [color=#00a933][bold]Allowed & required[/bold][/color] + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMinorContraband.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMinorContraband.xml new file mode 100644 index 00000000000..53f5d58a674 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsMinorContraband.xml @@ -0,0 +1,104 @@ + +# Minor Contraband Chemicals + +## Intro +These chemicals fall under minor contraband unless otherwise stated by standard operating procedures. + +Some minor illegal chems may be utilized with a department exception or with a prescription written by medical professional. + +Illegal component chemicals are to be kept in ChemMaster 4000 or disposed of after their immediate use. + +## Chemicals + +### Amoxle +- Department exceptions: [bold]Medical[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Carpotoxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Chlorine +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Cryptobiolin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Ephedrine +- Department exceptions: [bold]Security[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Ethyloxyephedrine +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Fluorine +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Gastrotoxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Happiness +- Department exceptions: [bold]Clown[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Impedrezene +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Lipozine +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Mercury +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Mindbreaker toxin +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Phosphorus +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Potassium +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Psicodine +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Radium +- Department exceptions: [bold]Engineering[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Silicon +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Space mirage +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Sulfur +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### Synaptizine +- Department exceptions: [bold]Security[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + +### THC +- Department exceptions: [bold]None[/bold] +- Prescription: [color=#00a933][bold]Allowed[/bold][/color] + +### Uranium +- Department exceptions: [bold]Bartender & Engineering[/bold] +- Prescription: [color=#ff0000][bold]Not allowed[/bold][/color] + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsSyndicateContraband.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsSyndicateContraband.xml new file mode 100644 index 00000000000..fa7b0d4ad2b --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChemsSyndicateContraband.xml @@ -0,0 +1,20 @@ + +# Syndicate Contraband Chemicals + +## Intro +These chemicals will always be considered illegal, and should never be used outside of an emergency. + +## Chemicals + +### Hyperzine + +### Lexorin + +### Mute toxin + +### Nocturine + +### Tazinide + +### Vestine + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChiefMedicalOfficer.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChiefMedicalOfficer.xml new file mode 100644 index 00000000000..7941728d385 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ChiefMedicalOfficer.xml @@ -0,0 +1,21 @@ + +# Chief Medical Officer + + + +1. The standard Command SOP applies. + +2. The Chief Medical Officer is responsible for training or assigning a trainer to any and all Medical Interns. + +3. The Syringe Gun is for emergencies only, and should not be used below [color=#ff0000]Code Red[/color]. +- 1. The syringes for the syringe gun may be prepared ahead of time. + +4. The Chief Medical Officer may not allow any major contraband chemicals to leave medbay or the chemical lab without a [italic]permission to carry chemicals form[/italic] stamped by the HoS, Captain or acting Captain. +- 1. This form will not be required in the case of imminent station danger. +- 2. This form will specify the following: +Quantity of chemical, frequency of creation, date, time and signature of the Captain or acting Captain. + +5. The Chief Medical Officer should wear clothing clearly identifying them as the Chief Medical Officer. (Mantle, cape, hat, etc.) + +6. The Chief Medical Officer may request any additional documentation they deem necessary to protect patient health. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ContrabandChemicals.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ContrabandChemicals.xml new file mode 100644 index 00000000000..3609dac7716 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/ContrabandChemicals.xml @@ -0,0 +1,7 @@ + +# Contraband Chemicals + +- Minor Contraband +- Major Contraband +- Syndicate Contraband + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/DeceasedPatientCare.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/DeceasedPatientCare.xml new file mode 100644 index 00000000000..2287b288407 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/DeceasedPatientCare.xml @@ -0,0 +1,22 @@ + +# Deceased Patient Care + + + +1. Patients should be triaged by level of rot. + +2. Patients who are in advanced stages of rot should be placed into stasis beds or body bags. + +3. Patients who are not being treated should be stored in the morgue until sufficient resources can be diverted to revive them. + +4. Patients who become unrevivable or are deemed unrevivable require a [italic]morgue report[/italic] filled out with: +- 1. Patient name. +- 2. Patient job. +- 3. Approximate time of death/DNR approval. +- 4. Reason for DNR status (only if DNR). +- 5. Chief Medical Officer's stamp for approval. + +5. Should a corpse become unclonable, it must be annotated on the appropriate DNR sheet and then stamped by the Chief Medical Officer. + +6. Unclonable corpses, including those whose soul has moved on, may be operated on or placed into the biomass reclaimer. + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalBay.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalBay.xml new file mode 100644 index 00000000000..999c3beea87 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalBay.xml @@ -0,0 +1,14 @@ + +# Medical Bay + + + +1. For medical crew safety, the medical bay must not be placed on all access unless [color=#ff0000]Code Red[/color] is called. + +2. The medical bay must be kept neat and tidy for patient health. + +3. Chemicals should be kept in a stored locker or location and closed when not in use. + +4. Defibrillators should be kept in their cabinets when not in use and should be charged whenever possible. +- 1. It is recommended that spare batteries be kept next to defibrillator cabinets. + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalDoctor.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalDoctor.xml new file mode 100644 index 00000000000..89ecd12cc1e --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalDoctor.xml @@ -0,0 +1,11 @@ + +# Medical Doctor + + + +1. Medical Doctors report directly to the Chief Medical Officer. + +2. Medical Doctors should wear sterile gloves when dealing with patients and either scrubs or a doctor's coat to differentiate them from other crew members. + +3. Medical Doctors are permitted to observe Surgeons and Chemists in their official duties, as long as no patients require treatment. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalIntern.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalIntern.xml new file mode 100644 index 00000000000..f19c42b41fc --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/MedicalIntern.xml @@ -0,0 +1,15 @@ + +# Medical Intern + + + +1. Medical Interns report directly to the Chief Medical Officer, but are expected to follow the orders of their designated trainer. + +2. Medical Interns are not permitted to utilize chemicals on their own without supervision. + +3. Medical Interns are to stay with their assigned trainer at all times. + +4. In emergencies, Medical Interns may treat patients as a Medical Doctor. + +5. Medical Interns may not perform elective surgeries at any time. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Paramedic.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Paramedic.xml new file mode 100644 index 00000000000..0a6a846c52e --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Paramedic.xml @@ -0,0 +1,17 @@ + +# Paramedic + + + +1. Paramedics report directly to the Chief Medical Officer. + +2. Paramedics should stabilize crew members who are in critical condition before moving them to medbay. + +3. Crew members who are deceased are to be placed into a body bag before transport to medbay. + +4. Paramedics are permitted to carry one defibrillator on their person, as long as at least one remains in the medbay. + +5. Should a crewmember not be able to be stabilized in the field (excess damage, no means to heal) or defibrillated, they should inform medbay using radio communications prior to arrival. + +6. Paramedics should carry sufficient supplies for each major damage type (burn, brute, poison, airloss, and bloodloss, and radiation). + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/PatientCare.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/PatientCare.xml new file mode 100644 index 00000000000..8f437763c92 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/PatientCare.xml @@ -0,0 +1,13 @@ + +# Patient Care + + + +1. Patients must be triaged according to the severity of their injuries. + +2. Command members must take treatment priority. + +3. Doctors may not leave the medical bay for personal reasons if there are untreated patients. This does not include the necessity of eating and drinking. + +4. Patients who repeatedly harm themselves or threaten medical staff are not required to be treated by medical staff. + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Psychologist.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Psychologist.xml new file mode 100644 index 00000000000..913f07d2408 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Psychologist.xml @@ -0,0 +1,20 @@ + +# Psychologist + + + +1. The Psychologist report directly to the Chief Medical Officer. + +2. The Psychologist is authorized to perform a full psychometric workup on any crew member who is willing. + +3. Examinations of unwilling crewmembers may only occur with written approval by the Chief Medical Officer and one the following: HoS, Magistrate, Captain. +- 1. This also applies to any medication prescribed by the Psychologist. + +4. Examinations may result in the following actions, with a sign off from the Captain or crew member's head of department: +- 1. Demotion from their current position, if the patient's mental state leaves them unable to fulfill their duties. +- 2. Prescriptions of Pax or other similar drugs for those who are found to be extremely violent. +- 3. Increased observation of prisoners or crew who are deemed a danger. +- 4. Lightening of sentences for prisoners who have shown good behavior and a change of moral character. + +5. The Psychologist may request to consult with a prisoner at any time to evaluate their mental state. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Surgeon.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Surgeon.xml new file mode 100644 index 00000000000..dcb9baa844b --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/Surgeon.xml @@ -0,0 +1,17 @@ + +# Surgeon + + + +1. Surgeons report directly to the Chief Medical Officer. + +2. Patients must fill out and sign a [italic]surgery consent form[/italic] for any elective surgeries. This form must be stamped by the Chief Medical Officer. + +3. Surgeons should wear masks, sterile gloves and scrubs when possible, while operating. + +4. The surgery room must be kept clean and tidy for patient hygiene. + +5. Surgeons are permitted to harvest organs and limbs from deceased patients who have been considered unrecoverable. + +6. Live patients must be given a sedative during the duration of their surgery, unless they request otherwise. Any requests must be documented on their [italic]surgery consent form[/italic]. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/VioletAlertProtocol.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/VioletAlertProtocol.xml new file mode 100644 index 00000000000..3805c8f5fb4 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/VioletAlertProtocol.xml @@ -0,0 +1,19 @@ + +# Violet Alert Protocol + + + +1. All medical personnel are to be secured in the medical bay immediately. + +2. The Chief Medical Officer's safety will take priority over curing an infection. + +3. Chemistry will focus all efforts on researching the cure to the infection. + +4. Medical entrances should be locked down to prevent further infection of medical personnel. + +5. Any potentially infected personnel should be isolated and quarantined. + +6. Any pacified infected personnel should be brought to chemistry to aid in cure production. + +7. A cure should be distributed to the crew once available, in a controlled manner. + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-genproc-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-genproc-intro.xml new file mode 100644 index 00000000000..f134e09c736 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-genproc-intro.xml @@ -0,0 +1,3 @@ + +# General Medical Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-intro.xml new file mode 100644 index 00000000000..0ce94b4a707 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-intro.xml @@ -0,0 +1,7 @@ + +# Medical SOP (WIP) + +This SOP is to assist the station's medical team in crew treatment and provide guidelines on handling station crew after death. + +(WIP at the moment, Grapegifter will make and upload soonish) + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-staff-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-staff-intro.xml new file mode 100644 index 00000000000..2cb35825b5e --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/MedicalSOP/medical-sop-staff-intro.xml @@ -0,0 +1,3 @@ + +# Medical Staff Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-bso.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-bso.xml new file mode 100644 index 00000000000..ec7ecac5f33 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-bso.xml @@ -0,0 +1,17 @@ + +# BlueShield Officer + +1. The BlueShield Officer reports directly to the Captain and NanoTrasen Representative. + +2. The BlueShield Officer is responsible for protecting and defending command members and NT Personnel at all times. If it is not possible to protect both, NT Personnel are to be prioritized. + +3. The BlueShield Officer may ignore corporate law when [bold]actively[/bold] performing actions to protect their charge. + +4. The Blueshield Officer may not take armory weapons from the armory without a permit, this includes the LMG. Armory permits may only be issued on [color=#0000ff]Blue[/color] Alert or higher. + +5. The BlueShield Officer is not restricted in the weapons they may carry, so long as armory weapons stay with the issued permit. However, their weapons should not be visible and must be holstered or placed in a bag or pocket on any alert level below [color=#ff0000]Red[/color]. + +6. The BlueShield Officer should focus on protecting their charge and [bold]should not be pursuing[/bold] potential threats to the detriment of their charge. + +7. The BlueShield Officer cannot interfere with the lawful arrest of a head of command. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-genproc-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-genproc-intro.xml new file mode 100644 index 00000000000..34056b0cd02 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-genproc-intro.xml @@ -0,0 +1,3 @@ + +# General NanoTrasen Employee Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-iaa.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-iaa.xml new file mode 100644 index 00000000000..3bdf3679dfd --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-iaa.xml @@ -0,0 +1,17 @@ + +# Internal Affairs Agent + + + +1. The Internal Affairs Agents are considered subordinate to [bold]both[/bold] the NT Representative and the Magistrate. They are also not considered part of command. + +2. The Internal Affairs Agents are to only legally represent prisoners who are accused of capital level crimes, however they may choose to provide legal council to both security, as well as prisoners of lesser crimes. + +3. The Internal Affairs Agents may request access to a department to ensure that Standard Operating Procedures are being carried out. This request does not have to be accepted, however denial may be a cause for concern. + +4. The Internal Affairs Agents may not significantly impede any department with paperwork or do multiple inspections within a short timeframe. + +5. All violations of SOP or corporate law should be brought to the relevant department head, NanoTrasen Representative or Magistrate. + +6. The Internal Affairs Agents may carry a flash on them at all times. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-intro.xml new file mode 100644 index 00000000000..315746d71d9 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-intro.xml @@ -0,0 +1,6 @@ + +# NanoTrasen Employee SOP + +This Standard Operating Procedure is to help guide NanoTrasen Personnel which are aboard the station. These personnel are considered part of the crew, however are not employed by Central Command. These crewmembers however have no official commanding power on the station, outside of what is explicitly stated in their SOP. + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-magistrate.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-magistrate.xml new file mode 100644 index 00000000000..2c59825e0c3 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-magistrate.xml @@ -0,0 +1,13 @@ + +# Magistrate + +1. The Magistrate is the ultimate judge of corporate law on the station and is considered an advisor to the station. + +2. The Magistrate is responsible for ensuring that those prisoners that are to receive capital punishment are given a fair and balanced trial, consisting of a jury of 6 of their peers. + +3. The Magistrate may overrule any sentencing imposed upon station crew, but may not pass judgement on any Central Command officials and personnel. + +4. The Magistrate may not overly impede the inner workings of security. + +5. The Magistrate may carry a flash on them at all times. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nct.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nct.xml new file mode 100644 index 00000000000..ddf894ee427 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nct.xml @@ -0,0 +1,17 @@ + +# Nanotrasen Career Trainer + +1. NT Career Trainers report directly to the Captain and NanoTrasen Representative. + +2. NT Career Trainers are to wear at least their company-provided uniform and jacket at all times while on duty. They are free to choose a beret/hat that best matches their primary field of knowledge if they so desire. Additionally, Identifying equipment is meant for NT Career Trainers and [bold]SHOULD NOT[/bold] be distributed to crew members. + +3. NT Career Trainers are to be available to all Crewmembers, regardless of Department. They may not only assist a singular Department. + +4. NT Career Trainers are not to do a Trainee's work for them. + +5. NT Career Trainers are to use NCT Data Chips only to acquire the access necessary for providing training. They are not to use said access for other purposes. + +6. In the event of a lost or stolen NCT Data Chip, the NT Career Trainer is to report the incident to their local Nanotrasen Representative or Station Captain. + +7. NT Career Trainers are permitted to carry a flash for self-defense. + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nt-rep.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nt-rep.xml new file mode 100644 index 00000000000..ac286ca053a --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-nt-rep.xml @@ -0,0 +1,13 @@ + +# NanoTrasen Representative + +1. The NanoTrasen Representative is the physical presence of NanoTrasen on the station and is considered an advisor to station command on all matters SOP related. + +2. The NanoTrasen Representative has no official command status on station unless granted directly by Central Command fax. + +3. Reports from the NT Representative to Central Command must be accompanied with the NanoTrasen Representative's stamp. + +4. The NT Representative is permitted to carry their cane and a flash at all times. + +5. All SOP violations should first be reported to the relevant head of the department. If violations continue, they may escalate first to the Captain, then to Central Command. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-safety-protocol.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-safety-protocol.xml new file mode 100644 index 00000000000..7665c4166b9 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-safety-protocol.xml @@ -0,0 +1,9 @@ + +# Safety Protocol + +1. As a direct hire of NanoTrasen, your safety is paramount. On [color=#ff0000]Code Red[/color] or above, all NanoTrasen personnel should seek shelter, with exception of the BSO who should continue their duties. + +2. In the event of a [color=#ec9ba4]Code Gamma[/color], all NanoTrasen Personnel are to communicate and gather on the bridge and await ERT support. + +3. In the event of contract terminations, all NanoTrasen Personnel will be escorted off station by a NanoTrasen marine squad. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-staff-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-staff-intro.xml new file mode 100644 index 00000000000..bf34dc3126a --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/NanoTrasenEmployeeSOP/nano-trasen-employee-sop-staff-intro.xml @@ -0,0 +1,3 @@ + +# NanoTrasen Employee Staff Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/ScienceSOP/science-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/ScienceSOP/science-sop-intro.xml new file mode 100644 index 00000000000..8300d31e374 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/ScienceSOP/science-sop-intro.xml @@ -0,0 +1,7 @@ + +# Science SOP (WIP) + +This SOP is to assist the station's science team in [bold]safely[/bold] conducting research on board the station. + +(WIP at the moment, Grapegifter will make and upload soonish) + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Brigmedic.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Brigmedic.xml new file mode 100644 index 00000000000..1a7de7201f5 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Brigmedic.xml @@ -0,0 +1,37 @@ + +# Brigmedic + + + +1 . Standard [color=#00a933]Code Green[/color] equipment is: + + + + + + + + + + + + + + + + + in + + + + + or + + + +2. Brigmedics may not perform Security Officer duties unless security is severely understaffed, or a crime has occurred in their sight. + +3. Brigmedics must prioritize the health and safety of Security Officers and Prisoners over all other priorities. + +4. Brigmedics putting themselves in excessive danger, and by extension the entire department, are to be considered negligent in their duties. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Cadet.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Cadet.xml new file mode 100644 index 00000000000..8f4635dc51e --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Cadet.xml @@ -0,0 +1,9 @@ + +# Cadet + + + +1. Cadets are to assign themselves to a Security Officer if one is not assigned to them. + +2. Cadets may only use lethal equipment on [color=#ff0000]Code Red[/color]. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Detective.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Detective.xml new file mode 100644 index 00000000000..21b7057b735 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Detective.xml @@ -0,0 +1,34 @@ + +# Detective + + + +1 . Standard [color=#00a933]Code Green[/color] equipment is: + + + + + + + + + + + + + + + + + in + + + +2. The Detective is permitted to patrol with a Security Officer on all alert levels, but should focus on collecting of evidence and investigations at all times. + +3. When acting as a Security Officer, the Detective must follow all Security Officer guidelines listed above. + +4. The Detective is permitted to wear non-security uniforms for undercover investigations, with approval from the Head of Security. The Detective's security ID should be on their person at all times, however. + +5. The Detective is permitted to interrogate detained suspects, however any detainment must be subtracted from their overall arrest time. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/DutyOfficer.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/DutyOfficer.xml new file mode 100644 index 00000000000..2fb07b4abbf --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/DutyOfficer.xml @@ -0,0 +1,42 @@ + +# Duty Officer + + + +1 . Standard [color=#00a933]Code Green[/color] equipment is: + + + + + + + + + + + + + + + + or + + x4 + + + + x2 + + x2 + + +2. The Duty Officer reports directly to the Warden. The Duty Officer is to assist in the processing of prisoners. + +3. The Duty Officer is to directly communicate to the Warden at the start of the shift, and any time they are required to leave the department. + +4. The Duty Officer may not perform the duties of a Security Officer, unless the department is short on staff, or during emergencies. + +5. Prisoner treatment guidelines must be strictly followed and is your top priority. + +6. Non-lethal means should be used against prisoners whenever possible. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/HeadOfSecurity.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/HeadOfSecurity.xml new file mode 100644 index 00000000000..5046412fde8 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/HeadOfSecurity.xml @@ -0,0 +1,47 @@ + +# Head of Security + + + +1. Standard [color=#00a933]Code Green[/color] equipment is: + + + or + + + + + + + + + + + + + in + + + + + or + + + + + or + + + +2. The standard Command SOP applies with the exception of section 6, as for which, refer to the standard equipment listed above. + +3. When patrolling, the Head of Security must follow all Security Officer protocols as above, however the WT550 is considered a sidearm. + +4. The Head of Security may overrule any sentence that is not assigned by an official NT Magistrate, but not for prisoners who have already had their sentences read to them. + +6. The Head of Security may not utilize the armory for their own personal benefit. + +6. The Head of Security must follow the Warden procedures for distributing any armory equipment, portable flashers, or deployable barriers. + +7. If a [color=#ff0000]Code Red[/color] is called, the Head of Security must state the reason for the [color=#ff0000]Code Red[/color]. The Captain may perform this duty instead, with permission from the Head of Security. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Parole.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Parole.xml new file mode 100644 index 00000000000..b6aefa34617 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Parole.xml @@ -0,0 +1,27 @@ + +# Parole + +1. A criminal is sentenced to parole. + +Criminals may be sentenced to parole if: + +- They request parole before or during their sentence and Warden or Head of Security approves. The request should always be approved if a prisoner has been cooperative during their incarceration and served at least half their sentence. All other situations are up to discretion. +- A member of the Legal Department justifiably orders parole at the conclusion of a trial or investigation. + +2. If the paroled individual has just been sentenced, they are to have their gear confiscated as-per instructions in Prisoner Treatment. + +- Warden or Head of Security may allow some possession to remain with the paroled individual during this time, at their discretion. + +3. Paroled individual is to be marked in the criminal records as "Paroled". + +4. Paroled individual is to be released from security. + +5. Warden and Head of Security may order the paroled individual to check in at security during parole. + +- Failure to comply in under 5 minutes should be considered breach of custody. +- Paroled individuals should not be required to check in more frequently than once every 15 minutes. +- Warrants are not required to search paroled individuals. + +6. When their sentence is up the paroled individual should return to security to collect their belongings and be marked as discharged. + + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PermitAcquisition.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PermitAcquisition.xml new file mode 100644 index 00000000000..aae8830d729 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PermitAcquisition.xml @@ -0,0 +1,26 @@ + +# Permit Acquisition + +1. Requester delivers a filled out permit form for contraband to Warden, HoS, or in an emergency, Captain. It must contain Time and Date, requester's name and their position, a reason for the permit, and how the item will be or has already been obtained. + +- Any illegal chemical which requires a prescription must provide a valid prescription with the permit that is signed or stamped appropriately. + +2. Review the validity and necessity of the request. + +- If the item requires delivery by a department other than sec, the permit must already be signed or stamped by the relevant head. +- If the permit requires a security item that is in limited stock it my be denied until more can be obtained. +- If the requester has already received a related permit the person reviewing can choose to deny the permit unless the old permit and contraband are turned in. +- Significant Syndicate Permits are never approved. +- Armory Permits are not issued below Blue Alert. + +3. If the request is not unreasonable, it is stamped APPROVED, as well as signed and stamped by the person reviewing it. + +- If the request is unreasonable it is stamped DENIED instead of APPROVED. + +4. A copy is made for reference and stored in warden's office. + +5. The document is given to the requester. If approved they are to keep it on their person at all times. If denied they are to be given a brief explanation as to why. + +- If an approved permit is for security equipment, it is retrieved and provided. + + diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PrisonerTreatment.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PrisonerTreatment.xml new file mode 100644 index 00000000000..f6d174b4d8a --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/PrisonerTreatment.xml @@ -0,0 +1,17 @@ + +# Prisoner Treatment + +1. Prisoners must be read their list of crimes before the warden before sentencing can commence. Any time spent in confinement must be subtracted from the total time of their sentence. + +2. Arrested prisoners are to be searched upon entry to Security. ID's and PDA's are to be removed from prisoners while in confinement. Prisoners are to be provided/allowed their own radio communications equipment. + +Prisoner searches include: +- Pockets +- PDA Slot +- Bags +- Coats/overwear + +3. Prisoners placed into confinement are to be unrestrained. Prisoners who become combative or pose a flight risk may be restrained at the Warden's discretion. + +4. Prisoners who receive perma/execution sentences may request a trial for their crimes, as decided by a jury of 12 of their peers. This may be waived in the face of imminent station destruction. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SecurityOfficer.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SecurityOfficer.xml new file mode 100644 index 00000000000..9c1bbd7be17 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SecurityOfficer.xml @@ -0,0 +1,38 @@ + +# Security Officer + + + +1 . Standard [color=#00a933]Code Green[/color] equipment is: + + + + + + + + + + + + + in + + + + + or + + + + + or + + + +2. Security Officers are to patrol the station unless an active threat has been recognized. + +3. Security Officers are responsible for assigning sentences up to 20 minutes, but should inform the Warden of the accusation and sentencing if timing exceeds 10 minutes. Sentences over 20 minutes must be approved by the warden or Head of Security. + +4. It is advised on [color=#2a6099]Code Blue[/color] or above that Security Officers patrol the station in pairs. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SpecialSituations.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SpecialSituations.xml new file mode 100644 index 00000000000..dd179ee8c2f --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/SpecialSituations.xml @@ -0,0 +1,74 @@ + +# Special Situations + + ## Hostage Situations + CC Employee Contracts include provisions for the protection and safety of all employees. Should an employee be taken and held hostage, security and command must work to ensure that employees are returned alive. + + 1. All hostages should be considered to have been implanted with deadman switches which will destroy their body upon death, resulting in the permanent death of that clone, unless explicitly told otherwise. + + 2. Rescues that involve death of the hostage and subsequent revival and recovery of the body should not be attempted. + + 3. If the hostage is being held for ransom, the Captain or Head of Security may negotiate using station funds, items, or a combination of the two to be traded in exchange the safe return of the hostage. The total value traded, meaning the combined price of the items and money must be equal to or less than the values specified in the table at the end of this section. + + 4. Should security have a member of the opposing force, they may be exchanged for hostages. + + 5. Any and all hostage negotiations must include a guarantee that the opposing force will cease their activities and vacate the area. + + 6. Security may attempt to rescue the hostages if they believe that they can do so safely. Outright rushing into the situation and engaging the enemy is considered reckless and is grounds for demotion. + + 7. Accepted rescue methods include but are not limited to infiltration, disabling the enemy through non-violent means, or utilizing a distraction to free the hostages without engaging. + + ## Monetary Negotiation Limits + + + + Value + + + + + Role + + + + + 10k + + + + + Any crew with an assigned job + + + + + 15k + + + + + Command Members + + + + + 20k + + + + + Captain + + + + + 25k + + + + + Magistrate, NT Representative, Internal Affairs Agent, and Blueshield Officer + + +
+ \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Warden.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Warden.xml new file mode 100644 index 00000000000..219711a15ae --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/Warden.xml @@ -0,0 +1,44 @@ + +# Warden + + + +1 . Standard [color=#00a933]Code Green[/color] equipment is: + + + + + + + + + + + + + in + + + + + or + + + + + or + + + +2. The Warden may not perform normal Security Officer duties, or arrests, if sufficient numbers of Security Officers are active. This is waived on [color=#ff0000]Code Red[/color] or above. + +3. The Warden may choose to hand out lethal weapons on [color=#2a6099]Code Blue[/color] with a permit, or [color=#ff0000]Code Red[/color] or above. + +4. The Warden may choose to hand out body armor on [color=#2a6099]Code Blue[/color] or above. + +4. Uncooperative prisoners, or those deemed to be a flight risk may be cuffed, straightjacketed, or have an electropack placed on them. + +5. Portable flashers and deployable barriers may be deployed on [color=#2a6099]Code Blue[/color] or above. + +6. The Warden may appoint a Duty Officer to assist with prisoner keeping duties with permission from the HoS. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/security-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/security-sop-intro.xml new file mode 100644 index 00000000000..63fc6752ac3 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/SecuritySOP/security-sop-intro.xml @@ -0,0 +1,27 @@ + +# Security SOP + +These procedures apply to all security members, unless otherwise stated in their specific SOP + +1. Long guns shall not be taken outside the brig on [color=#00a933]Code Green[/color]. Long guns (including those mounted on mechs) are any firearms that are not pistols or revolvers. + +2. A maximum of 1 long gun (with permit) and 1 sidearm (pistol or revolver) may be carried on [color=#2a6099]Code Blue[/color] or above. Only a sidearm and disabler may be carried on [color=#00a933]Code Green[/color]. + +3. Long guns will be issued on a permit basis on [color=#2a6099]Code Blue[/color], and are allowed to all security personnel on [color=#ff0000]Code Red[/color]. Disabler SMGs are not considered long guns. + +4. Weapons must remain holstered unless in active pursuit or on [color=#ff0000]Code Red[/color]. + +5. Security personnel are required to state the reason for an arrest before any action may be taken against a suspect. This does not apply on [color=#ff0000]Code Red[/color], or if a suspect flees when approached. + +6. Security personnel must attempt to bring suspects to the brig uncuffed. This does not apply on [color=#ff0000]Code Red[/color], or if a suspect has already fled or become uncooperative. + +7. Security personnel may not request entry to a department, unless in pursuit of a suspect, or on [color=#2a6099]Code Blue[/color] or [color=#ff0000]Code Red[/color]. + +8. Searches may be conducted randomly on [color=#2a6099]Code Blue[/color] and [color=#ff0000]Code Red[/color], and on [color=#00a933]Code Green[/color] with an applicable warrant. Crew refusing searches on [color=#2a6099]Code Blue[/color] or [color=#ff0000]Code Red[/color] may be detained. + +9. All security personnel must wear at least one piece of an official security uniform at all times. An official security uniform is defined as: The security jumpsuit/skirt, the senior security jumpsuit/skirt, the security winter coat, the trooper uniform, or job specific variants of these for the Warden, Head of Security or Brigmedic. + +10. Security personnel should refrain from wearing hardsuits or magboots unless an imminent threat or massive station damage is present. + +11. Security personnel may forcefully relocate crew members to their departments on [color=#ff0000]Code Red[/color], [color=#8d1d75]Code Violet[/color], [color=#acb20c]Code Yellow[/color] or [color=#ec9ba4]Code Gamma[/color]. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/HeadOfPersonnel.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/HeadOfPersonnel.xml new file mode 100644 index 00000000000..3a1b15d9775 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/HeadOfPersonnel.xml @@ -0,0 +1,11 @@ + +# Head of Personnel + + + +1. The Head of Personnel should not grant access to a department unless they have a form stamped by the relevant head of department. + +2. The Head of Personnel should not do the work of other departments unless they are short staffed. + +3. The Head of Personnel may not hire any staff to a NanoTrasen Personnel position. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-genproc-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-genproc-intro.xml new file mode 100644 index 00000000000..953676da9d7 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-genproc-intro.xml @@ -0,0 +1,3 @@ + +# General Service Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-intro.xml new file mode 100644 index 00000000000..090f6ef5ed8 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-intro.xml @@ -0,0 +1,3 @@ + +# Service SOP (WIP) + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-staff-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-staff-intro.xml new file mode 100644 index 00000000000..4041f635a8e --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/ServiceSOP/service-sop-staff-intro.xml @@ -0,0 +1,3 @@ + +# Service Staff Procedures + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/departmental-sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/departmental-sop-intro.xml new file mode 100644 index 00000000000..4c76055974f --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/departmental-sop-intro.xml @@ -0,0 +1,5 @@ + +# Departmental SOP + +This SOP is for specific departments and applies to the members of that department. This should be the first thing you read once you join a department. + \ No newline at end of file diff --git a/Resources/ServerInfo/_Starlight/StarlightSOP/sop-intro.xml b/Resources/ServerInfo/_Starlight/StarlightSOP/sop-intro.xml new file mode 100644 index 00000000000..8533b6255f0 --- /dev/null +++ b/Resources/ServerInfo/_Starlight/StarlightSOP/sop-intro.xml @@ -0,0 +1,17 @@ + +# What is an SOP? + +This SOP (Standard Operating Procedure) provides general guidelines for the station crew during your shift. These guidelines may be changed by the station's Captain at any time. This SOP is considered a general form of conduct for all crew members. + +# How do I use an SOP? +This should not be a considered a checklist of conditions to fire someone over, and should not be rigidly followed to the letter in detriment of circumstances and context. SOPs can be malleable if the situation requires, and the decision to punish personnel for breaching it ultimately falls onto the relevant Head of Staff, for Department Members, or Captain, for the Head of Staff. + +# How does this SOP help me? +This SOP gives you a code of conduct to abide by. You should follow what is in the following document, and repeated violations may result in contract termination, or removal from this sector. + +This SOP gives power to command to help determine what their department workers should be doing. It will help you guide the prospective hiring and firing of crew members. + +Similarly, the SOP gives power to the crew, by allowing you to depose and fire relevant command members, as long as the reason is valid. + +Central Command should be contacted for any questions regarding this SOP. + \ No newline at end of file From fa4edf200d07d26350f7355baa8104f6d9459969 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:21:13 -0700 Subject: [PATCH 02/12] Revise server rules and add new sections Updated server rules by modifying sections and adding new rules. --- .../ServerRules/CoreRules/RuleC0.xml | 205 +++++++++--------- 1 file changed, 103 insertions(+), 102 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml index cf0e9a0ba31..987b687888c 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC0.xml @@ -6,199 +6,200 @@ [color=#a4885c][head=3]0. Implementation and interpretation of the rules is up to the sole discretion of the Admins.[/head][/color] • Admins will instead be held accountable through use of the Admin code of conduct. - - • If you think an admin has behaved unfairly, you can open a ticket on the discord for an investigation. [color=#ffff00]If you have any questions about these rules, please use the Admin help menu by hitting F1 in-game, or clicking the "AHelp" button in the lobby, or alternatively, ask for assistance on the discord.[/color] + [head=3][color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/head][/color] Each section contains its own list of rules. Click on the section name to view the full version. - [textlink="Section 1. Behavioral Rules" link="RuleC1"] - - [textlink="Section 2. Roleplay Rules" link="RuleC2"] - - [textlink="Section 3. Gameplay Rules" link="RuleC3"] - - [textlink="Section 4. Lore/Setting Rules" link="RuleC4"] - - [textlink="Section 5. Erotic-Role-Play (ERP) Rules" link="RuleC5"] - - [textlink="Section 6. Command and Security Rules" link="RuleC6"] - - [textlink="Section 7. Antagonist Rules" link="RuleC7"] - - [textlink="Section 8. Escalation/PvP Rules" link="RuleC8"] - - [textlink="Section 9. Ship Saving Rules" link="RuleC9"] + - [textlink="Section 2. Gameplay Rules" link="RuleC2"] + - [textlink="Section 3. Metagaming Rules" link="RuleC3"] + - [textlink="Section 4. New-life Rules" link="RuleC4"] + - [textlink="Section 5. Character Naming Rules" link="RuleC5"] + - [textlink="Section 6. Roleplay Rules" link="RuleC6"] + - [textlink="Section 7. Powergaming Rules" link="RuleC7"] + - [textlink="Section 8. End-Of-Round (EOR) Rules" link="RuleC8"] + - [textlink="Section 9. Erotic-Role-Play (ERP) Rules" link="RuleC9"] + - [textlink="Section 10. Command and Security Rules" link="RuleC10"] + - [textlink="Section 11. Antagonist Rules" link="RuleC11"] + - [textlink="Section 12. Escalation Guidelines" link="RuleC12"] + - [textlink="Section 13. Ship saving" link="RuleC13"] + - [textlink="THE PIRATES CODE" link="Thecode"] [color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]1.1[/color] [color=#00fffb]Be respectful to others OOC. [/color] -[color=#a4885c]1.1[/color] Don't be a dick, aka, do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game except when required by your role. +[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. -[color=#a4885c]1.2[/color] Avoid controversial topics such as self harm/rape in public. +[color=#a4885c]1.3[/color] [color=#00fffb]Don't metagame.[/color] -[color=#a4885c]1.3[/color][color=#00fffb] Don't evade bans in any way, including account sharing or alt accounts. This will be reported to wizden.[/color] +[color=#a4885c]1.4[/color] Don't spam or advertise. -[color=#a4885c]1.4[/color][color=#00fffb] Taking actions that may harm the server's integrity or stability, such as lag farms, DDoS attacks, or public defamation is forbidden.[/color] +[color=#a4885c]1.5[/color][color=#00fffb] Do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game. [/color] -[color=#a4885c]1.5[/color][color=#00fffb] Impersonation of a position or person is forbidden. Do not pretend to be an admin, do not pretend to be someone you're not out-of-character.[/color] +[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. -[color=#a4885c]1.6[/color][color=#00fffb] If you are frustrated and need a break, you are free to ragequit/disconnect however this will not avoid consequences when you return.[/color] +[color=#a4885c]1.7[/color][color=#00fffb]Don't evade bans. [/color] +[color=#a4885c]1.8[/color] Don't self-antag. -[color=#ffff00][head=3]Section 2: Roleplay Rules[/head][/color] +[color=#a4885c]1.9[/color][color=#00fffb] Don't ragequit/disconnect to avoid consequences. [/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]1.10[/color][color=#00fffb] Making use of cheats, exploits, or taking actions that may harm the server's integrity or stability is forbidden. [/color] -[color=#a4885c]2.1[/color][color=#00fffb] Powergaming, defined as taking actions that are impossible or overpowered for your character, is forbidden.[/color] +[color=#a4885c]1.11[/color][color=#00fffb] Respect others' OOC consent and preferences. [/color] - - [color=#a4885c]2.1.1[/color] Your character should only specialize in at most 2 departments, and one service sidejob. - - [color=#a4885c]2.1.2[/color] Metaknowledge, such as knowing the exact damage values or weaknesses of objects, is both metagaming and powergaming. - - [color=#a4885c]2.1.3[/color] Do not make antag objectives inaccessible such as tossing them off station. Remember, you need access to them too. -[color=#a4885c]2.2[/color][color=#00fffb] Metagaming, or using out-of-character information for an in-character advantage, is forbidden.[/color] +[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] - - [color=#a4885c]2.2.1[/color] Metacommms, or sharing IC information in OOC channels, such as discord, isn't against the rules, but using information learned from it is. - - [color=#a4885c]2.2.2[/color] Knowledge gained while unconcious, crit, dead, ghosted, or as another character (or ghost role) should not be known by your character. - - [color=#a4885c]2.2.3[/color] If a player is killed and then brought back to life, they cannot recall more than foggy concepts of how they died. +[color=#a4885c]2.1[/color] [color=#00fffb]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question. [/color] -[color=#a4885c]2.3[/color][color=#00fffb] No metagruding. Your character is a separate entity from you, the player, and so are the characters you meet from their players. Your IRL feelings, and the feelings of your character, should not bleed or mix together (aka, bleeding/mixing). In-character rivalries should remain in character, and vice versa.[/color] +[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). -[color=#a4885c]2.4[/color] Do not make yourself a major problem, annoyance, or disruption for the crew without a valid reason. Responses should be reasonable and within the realms of what a real person would do in a given situation. +[color=#a4885c]2.3[/color] [color=#00fffb]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. [/color] -[color=#a4885c]2.5[/color] Do not play excessively hostile, provocative, or generally "unhirable" characters. If you can't pass an interview, you wouldn't be in ColCom space as an employee or contractor. +[color=#a4885c]2.4[/color] Ghosting with with the sole intent of spying on others' personal activities is not permitted. - - [color=#a4885c]2.5.1[/color][color=#00fffb] Roleplaying an underage or child-like character in both mind or body, is strictly forbidden. So is talk of such activities.[/color] -[color=#a4885c]2.6[/color] Respect other people's consent, dignity and boundaries. Check their consent info before engaging in questionable roleplay. If this is abused by either party, ahelp it immediately. +[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] - - [color=#a4885c]2.6.1[/color] Consent tags should be reasonable and fair. You can avoid sexual or gorey RP, but you cannot avoid being a victim or target of antag objectives through consent tags. - - [color=#a4885c]2.6.2[/color] If someone breaches your consent, they are allowed one warning to back off in case of miscommunication, however any further breaches are grounds for bans. - - [color=#a4885c]2.6.3[/color] You are allowed to request an out through any situation via ahelps if you are made uncomfortable, and you will be excluded in the scene through an in-character method manufactured by the admins. The other party will not be notified nor punished in this situation. +[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. -[color=#a4885c]2.7[/color][color=#00fffb] If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question.[/color] +[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. -[color=#a4885c]2.8[/color] You are to remain in character at all times. Do not ruin other player's immersion by breaking character, abusing out-of-character chats, or referencing real world events. +[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. +[color=#a4885c]3.4[/color] [color=#00fffb]Discussion about the current round is allowed on the Hardlight Discord server. HOWEVER, acting on information gained through this method is considered metagaming. [/color] -[color=#ffff00][head=3]Section 3: Gameplay Rules[/head][/color] +[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out-of-character information to give unfair treatment or advantages to others.) -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]3.6[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] -[color=#a4885c]3.1[/color] It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. -[color=#a4885c]3.2[/color] Use the chat channels for their intended purposes. OOC channels should be used sparingly to check global consent. Questions should be asked ICly, conversations should be held on discord. +[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] -[color=#a4885c]3.3[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] +[color=#a4885c]4.1[/color] Players maintain all in-character memory up until going critical. -[color=#a4885c]3.4[/color] [color=#00fffb]Ghosting with with the sole intent of spying on others' personal activities is not permitted.[/color] +[color=#a4885c]4.2[/color] If a player is brought back to life, they cannot recall more than foggy concepts of how they died. -[color=#a4885c]3.5[/color][color=#00fffb] Making use of cheats, exploits, or bugs to again an advantage is forbidden.[/color] -[color=#a4885c]3.6[/color][color=#00fffb] End-of-round-griefing (EORG) is not allowed under any circumstance. [/color] +[color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] - - [color=#a4885c]3.6.1[/color] This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. - - [color=#a4885c]3.6.2[/color] All of CC space, arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. - - [color=#a4885c]3.6.3[/color] If someone is heading to cryo, try not impede them (unless you are security) and let them leave. +[color=#a4885c]5.1[/color] Don't make meta references. +Try to be creative by picking a believable and fitting name and/or surname. -[color=#ffff00][head=3]Section 4: Lore/Setting Rules[/head][/color] +Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. -[color=#a4885c]4.1[/color] Try to be creative by picking a believable and fitting name and/or surname. - - [color=#a4885c]4.1.1[/color] It's suggested to use a lore-accurate name for your race, although exceptions can exist when cultures clash. - - [color=#a4885c]4.1.2[/color] Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - - [color=#a4885c]4.1.3[/color] Being named after a popular figure is ok, but having the same name of a popular figure is not. - - [color=#a4885c]4.1.4[/color] Avoid copyright names, such as GlaDOS or Megatron for borgs, Pennywise or The Joker for clowns, and so on. - -[color=#a4885c]4.2[/color] You are not not allowed to have supernatural backgrounds, such as; secret demigods, beings from the future, or similar. +[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] - - [color=#a4885c]4.2.1[/color] Wizards and those apart of the wizards federation are an exception, however they cannot retain their magical powers while not antag - - [color=#a4885c]4.2.2[/color] Changelings, Vampires, Werewolves, and Zombies are creatures of science, not magic. - - [color=#a4885c]4.2.3[/color] If you have a strange concept and don't know if its allowed, you are always free to ask using F1 ahelp. - -[color=#a4885c]4.3[/color] Don't use hate speech, racism, or bigoted comments. In the 26th century, society has moved passed petty bigotry. +[color=#a4885c]6.1[/color] Your character is a separate entity from you, the player. 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. + +[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. + +[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. + +[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. + +[color=#a4885c]6.5[/color][color=#00fffb] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If this rule is abused, Ahelp right away. [/color] + +[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) + +[color=#a4885c]6.7[/color][color=#00fffb]Roleplaying an underage character is strictly forbidden. So is talk of such activities. [/color] + + +[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] + +[color=#a4885c]7.1[/color] Do not hide Antag objective items. - - [color=#a4885c]4.3.1[/color] Distrust of borgs is exempt from this, due to their recent inclusion into sentient life and the existence of hostile rogue borgs. - - [color=#a4885c]4.3.2[/color] Your character cannot be sexist, racist, speciest, ableist, lgbtphobic as it wouldn't make sense in an age where all are proven capable and treated equal. +[color=#a4885c]7.2[/color][color=#00fffb] Do not make active use of known bugs in the game.[/color] -[color=#ffff00][head=3]Section 5: Erotic-Role-Play (ERP) Rules[/head][/color] +[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. -[color=#a4885c]5.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. +[color=#a4885c]8.2[/color] Arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. -[color=#a4885c]5.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. -[color=#a4885c]5.3[/color] [color=#00fffb]Don't kinkshame.[/color] +[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] -[color=#a4885c]5.4[/color] You should use the (-) subtle command for erotic roleplay material, to avoid others from walking in on your scene. +[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. -[color=#a4885c]5.5[/color] [color=#00fffb]Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting.[/color] +[color=#a4885c]9.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. -[color=#a4885c]5.6[/color] [color=#00fffb]Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera.[/color] +[color=#a4885c]9.3[/color] Don't kinkshame. -[color=#a4885c]5.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] +[color=#a4885c]9.4[/color] You should use the (-) subtle command for erotic roleplay material. -[color=#a4885c]5.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] +[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. -[color=#a4885c]5.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] +[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. -[color=#a4885c]5.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). +[color=#a4885c]9.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] +[color=#a4885c]9.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] -[color=#ffff00][head=3]Section 6: Command and Security Rules[/head][/color] +[color=#a4885c]9.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] -[color=#a4885c]6.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. +[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). -[color=#a4885c]6.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. -[color=#a4885c]6.3[/color] Don't abuse your position of power. +[color=#ffff00][head=3]Section 10: Command and Security Rules[/head][/color] -[color=#a4885c]6.4[/color] You are expected to roleplay with others. This includes antagonists. +[color=#a4885c]10.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. -[color=#a4885c]6.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. +[color=#a4885c]10.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. +[color=#a4885c]10.3[/color] Don't abuse your position of power. -[color=#ffff00][head=3]Section 7: Antagonist Guidelines[/head][/color] +[color=#a4885c]10.4[/color] You are expected to roleplay with others. This includes antagonists. -[color=#a4885c]7.1[/color] Antagonists are held to a higher standard of roleplay, similar to Command. +[color=#a4885c]10.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. -[color=#a4885c]7.2[/color] Antagonists are expected to roleplay with others. This includes Security and Command. -[color=#a4885c]7.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. +[color=#ffff00][head=3]Section 11: Antagonist Guidelines[/head][/color] -[color=#a4885c]7.4[/color] Pirates should prioritize theft and ransoming, not murder and destruction. +[color=#a4885c]11.1[/color] Antagonists are held to a higher standard, similar to Command. - - [color=#a4885c]7.4.1[/color] Pirates cannot force interactions which result in player or command bank accounts being robbed. (IE: demanding players withdraw funds for ransom) +[color=#a4885c]11.2[/color] Antagonists are expected to roleplay with others. This includes Security and Command. -[color=#a4885c]7.5[/color] Nukies should prioritize destroying the station and command. Non-combatants and freelancers should be ignored, unless they are threatening. +[color=#a4885c]11.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. -[color=#a4885c]7.6[/color] Revolutionaries want to take control of the station, not destroy it. Converting command should be at least attempted before murdering them. +[color=#a4885c]11.4[/color] Ghost roles have their own independent rules that must be followed. -[color=#a4885c]7.7[/color] Free agents, such as mice, rat-kings, wawas, and so on should only fight in self-defense, unless they are conscripted by a company. +[color=#ffff00][head=3]Section 12: Escalation Guidelines[/head][/color] -[color=#ffff00][head=3]Section 8: Escalation Guidelines[/head][/color] +[color=#a4885c]12.1[/color] Lethal force against players should be a last resort. -[color=#a4885c]8.1[/color] Lethal force against players should be a last resort. +[color=#a4885c]12.2[/color] Don't disproportionately escalate in response to others' actions. -[color=#a4885c]8.2[/color] Don't disproportionately escalate in response to others' actions. +[color=#a4885c]12.3[/color] Don't ignore critical or dead players unless related to an objective. -[color=#a4885c]8.3[/color] Don't ignore critical or dead players unless related to an objective. +[color=#a4885c]12.4[/color] Don't intentionally round remove other players unless related to an objective. -[color=#a4885c]8.4[/color] Don't intentionally round remove other players unless related to an objective. +[color=#ffff00][head=3]Section 13: Ship saving[/head][/color] -[color=#a4885c]8.5[/color] Revenge or "getting back" should be reasonable and proportional. +[color=#a4885c]13.1[/color] Ships are to be no larger than 80x50 tiles. +[color=#a4885c]13.2[/color] Do not abuse the ship save mechanic to avoid in-character consequences. -[color=#ffff00][head=3]Section 9: Ship saving[/head][/color] +[color=#a4885c]13.3[/color] [color=#00fffb]Do not exploit the stash to duplicate items. This especially goes for contraband.[/color] -[color=#a4885c]9.1[/color] [color=#00fffb]Ships are to be no larger than 80x50 tiles.[/color] +[color=#a4885c]13.4[/color] [color=#00fffb]Do not use inventories to circumvent stash restrictions.[/color] -[color=#a4885c]9.2[/color] [color=#00fffb]Do not abuse the ship save mechanic to avoid in-character consequences.[/color] +[color=#a4885c]13.5[/color] Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission. -[color=#a4885c]9.3[/color] [color=#00fffb]Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission.[/color] +[color=#a4885c]13.6[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] -[color=#a4885c]9.4[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] +[color=#a4885c]13.7[/color] [color=#00fffb]Do not go afk for extended periods on your ship (like logging off to sleep). The ship saving is provided to allow people to save progress without the need to do this. UNATTENDED SHIPS WILL BE REMOVED.[/color] -[color=#a4885c]9.5[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] +[color=#a4885c]13.8[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] From 3b18ce4d3cdb696b9241b8d054eaf9f24a02cf10 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:23:12 -0700 Subject: [PATCH 03/12] Update behavior rules in RuleC1.xml --- .../ServerRules/CoreRules/RuleC1.xml | 22 +++++++++++++------ 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml index 2f95d1343ad..45d9023d5c1 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC1.xml @@ -1,17 +1,25 @@  [color=#ffff00][head=3]Section 1: Behavior Rules[/head][/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]1.1[/color] [color=#00fffb]Be respectful to others OOC. [/color] -[color=#a4885c]1.1[/color] Don't be a dick, aka, do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game except when required by your role. +[color=#a4885c]1.2[/color] Don't use hate speech, racism, or bigoted comments. -[color=#a4885c]1.2[/color] Avoid controversial topics such as self harm/rape in public. +[color=#a4885c]1.3[/color] [color=#00fffb]Don't metagame.[/color] -[color=#a4885c]1.3[/color][color=#00fffb] Don't evade bans in any way, including account sharing or alt accounts. This will be reported to wizden.[/color] +[color=#a4885c]1.4[/color] Don't spam or advertise. -[color=#a4885c]1.4[/color][color=#00fffb] Taking actions that may harm the server's integrity or stability, such as lag farms, DDoS attacks, or public defamation is forbidden.[/color] +[color=#a4885c]1.5[/color][color=#00fffb] Do not intentionally take actions that would negatively impact or disrupt others' enjoyment of the game. [/color] -[color=#a4885c]1.5[/color][color=#00fffb] Impersonation of a position or person is forbidden. Do not pretend to be an admin, do not pretend to be someone you're not out-of-character.[/color] +[color=#a4885c]1.6[/color] Avoid controversial topics such as self harm/rape in public. -[color=#a4885c]1.6[/color][color=#00fffb] If you are frustrated and need a break, you are free to ragequit/disconnect however this will not avoid consequences when you return.[/color] +[color=#a4885c]1.7[/color][color=#00fffb]Don't evade bans. [/color] + +[color=#a4885c]1.8[/color] Don't self-antag. + +[color=#a4885c]1.9[/color][color=#00fffb] Don't ragequit/disconnect to avoid consequences. [/color] + +[color=#a4885c]1.10[/color][color=#00fffb] Making use of cheats, exploits, or taking actions that may harm the server's integrity or stability is forbidden. [/color] + +[color=#a4885c]1.11[/color][color=#00fffb] Respect others' OOC consent and preferences. [/color] From 3f040f358ea3e60f20a077dd15820305fd283090 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:23:39 -0700 Subject: [PATCH 04/12] Update roleplay rules to game server rules --- .../ServerRules/CoreRules/RuleC2.xml | 34 +++---------------- 1 file changed, 5 insertions(+), 29 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml index 0910b81c6ae..0adcb234c5e 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC2.xml @@ -1,35 +1,11 @@ -[color=#ffff00][head=3]Section 2: Roleplay Rules[/head][/color] +[color=#ffff00][head=3]Section 2: Game Server Rules[/head][/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]2.1[/color] [color=#00fffb]If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question. [/color] -[color=#a4885c]2.1[/color][color=#00fffb] Powergaming, defined as taking actions that are impossible or overpowered for your character, is forbidden.[/color] +[color=#a4885c]2.2[/color] Do not make yourself a major problem, annoyance, or disruption for the crew while not being an antagonist (i.e. self-antagging). - - [color=#a4885c]2.1.1[/color] Your character should only specialize in at most 2 departments, and one service sidejob. - - [color=#a4885c]2.1.2[/color] Metaknowledge, such as knowing the exact damage values or weaknesses of objects, is both metagaming and powergaming. - - [color=#a4885c]2.1.3[/color] Do not make antag objectives inaccessible such as tossing them off station. Remember, you need access to them too. +[color=#a4885c]2.3[/color] [color=#00fffb]It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. [/color] -[color=#a4885c]2.2[/color][color=#00fffb] Metagaming, or using out-of-character information for an in-character advantage, is forbidden.[/color] - - - [color=#a4885c]2.2.1[/color] Metacommms, or sharing IC information in OOC channels, such as discord, isn't against the rules, but using information learned from it is. - - [color=#a4885c]2.2.2[/color] Knowledge gained while unconcious, crit, dead, ghosted, or as another character (or ghost role) should not be known by your character. - - [color=#a4885c]2.2.3[/color] If a player is killed and then brought back to life, they cannot recall more than foggy concepts of how they died. - -[color=#a4885c]2.3[/color][color=#00fffb] No metagruding. Your character is a separate entity from you, the player, and so are the characters you meet from their players. Your IRL feelings, and the feelings of your character, should not bleed or mix together (aka, bleeding/mixing). In-character rivalries should remain in character, and vice versa.[/color] - -[color=#a4885c]2.4[/color] Do not make yourself a major problem, annoyance, or disruption for the crew without a valid reason. Responses should be reasonable and within the realms of what a real person would do in a given situation. - -[color=#a4885c]2.5[/color] Do not play excessively hostile, provocative, or generally "unhirable" characters. If you can't pass an interview, you wouldn't be in ColCom space as an employee or contractor. - - - [color=#a4885c]2.5.1[/color][color=#00fffb] Roleplaying an underage or child-like character in both mind or body, is strictly forbidden. So is talk of such activities.[/color] - -[color=#a4885c]2.6[/color] Respect other people's consent, dignity and boundaries. Check their consent info before engaging in questionable roleplay. If this is abused by either party, ahelp it immediately. - - - [color=#a4885c]2.6.1[/color] Consent tags should be reasonable and fair. You can avoid sexual or gorey RP, but you cannot avoid being a victim or target of antag objectives through consent tags. - - [color=#a4885c]2.6.2[/color] If someone breaches your consent, they are allowed one warning to back off in case of miscommunication, however any further breaches are grounds for bans. - - [color=#a4885c]2.6.3[/color] You are allowed to request an out through any situation via ahelps if you are made uncomfortable, and you will be excluded in the scene through an in-character method manufactured by the admins. The other party will not be notified nor punished in this situation. - -[color=#a4885c]2.7[/color][color=#00fffb] If you are banned from a role or department, you may not play that role. This includes seeking or accepting promotions into roles you are banned from or taking Ghost roles which hold the role in question.[/color] - -[color=#a4885c]2.8[/color] You are to remain in character at all times. Do not ruin other player's immersion by breaking character, abusing out-of-character chats, or referencing real world events. +[color=#a4885c]2.4[/color] Ghosting with with the sole intent of spying on others' personal activities is not permitted. From aa6bcedb5b19983b506f5392eada682cdf55d257 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:24:54 -0700 Subject: [PATCH 05/12] Update Section 3 to Metagaming Rules and clarify rules --- .../ServerRules/CoreRules/RuleC3.xml | 19 +++++++------------ 1 file changed, 7 insertions(+), 12 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml index f403a4e7fc7..f61c24079c7 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC3.xml @@ -1,21 +1,16 @@  -[color=#ffff00][head=3]Section 3: Gameplay Rules[/head][/color] +[color=#ffff00][head=3]Section 3: Metagaming Rules[/head][/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]3.1[/color] Use the chat channels for their intended purposes. -[color=#a4885c]3.1[/color] It is strictly forbidden to livestream rounds to others or share recorded gameplay outside of Hardlight without consent of all parties involved. +[color=#a4885c]3.2[/color] Characters do not retain any knowledge of what happened while they were dead. -[color=#a4885c]3.2[/color] Use the chat channels for their intended purposes. OOC channels should be used sparingly to check global consent. Questions should be asked ICly, conversations should be held on discord. +[color=#a4885c]3.3[/color] Do not use any information gained by meta-communication. -[color=#a4885c]3.3[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] +[color=#a4885c]3.4[/color] [color=#00fffb]Discussion about the current round is allowed on the Hardlight Discord server. HOWEVER, acting on information gained through this method is considered metagaming. [/color] -[color=#a4885c]3.4[/color] [color=#00fffb]Ghosting with with the sole intent of spying on others' personal activities is not permitted.[/color] +[color=#a4885c]3.5[/color] Do not meta-grudge or meta-friend. (Using in or out-of-character information to give unfair treatment or advantages to others.) -[color=#a4885c]3.5[/color][color=#00fffb] Making use of cheats, exploits, or bugs to again an advantage is forbidden.[/color] +[color=#a4885c]3.6[/color] [color=#00fffb]Do NOT antag-roll. (Intentionally ghosting or cryoing to look for antag roles.)[/color] -[color=#a4885c]3.6[/color][color=#00fffb] End-of-round-griefing (EORG) is not allowed under any circumstance. [/color] - - - [color=#a4885c]3.6.1[/color] This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. - - [color=#a4885c]3.6.2[/color] All of CC space, arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. - - [color=#a4885c]3.6.3[/color] If someone is heading to cryo, try not impede them (unless you are security) and let them leave. From c7d28714ea7d050a7ced5cb14b4985e327306feb Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:25:30 -0700 Subject: [PATCH 06/12] Update Section 4 to New-Life Rules and revise content --- .../ServerRules/CoreRules/RuleC4.xml | 20 +++---------------- 1 file changed, 3 insertions(+), 17 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml index 46341114995..8ab72ca5189 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC4.xml @@ -1,21 +1,7 @@  -[color=#ffff00][head=3]Section 4: Lore/Setting Rules[/head][/color] +[color=#ffff00][head=3]Section 4: New-Life Rules[/head][/color] -[color=#a4885c]4.1[/color] Try to be creative by picking a believable and fitting name and/or surname. +[color=#a4885c]4.1[/color] Players maintain all in-character memory up until going critical. - - [color=#a4885c]4.1.1[/color] It's suggested to use a lore-accurate name for your race, although exceptions can exist when cultures clash. - - [color=#a4885c]4.1.2[/color] Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. - - [color=#a4885c]4.1.3[/color] Being named after a popular figure is ok, but having the same name of a popular figure is not. - - [color=#a4885c]4.1.4[/color] Avoid copyright names, such as GlaDOS or Megatron for borgs, Pennywise or The Joker for clowns, and so on. - -[color=#a4885c]4.2[/color] You are not not allowed to have supernatural backgrounds, such as; secret demigods, beings from the future, or similar. - - - [color=#a4885c]4.2.1[/color] Wizards and those apart of the wizards federation are an exception, however they cannot retain their magical powers while not antag - - [color=#a4885c]4.2.2[/color] Changelings, Vampires, Werewolves, and Zombies are creatures of science, not magic. - - [color=#a4885c]4.2.3[/color] If you have a strange concept and don't know if its allowed, you are always free to ask using F1 ahelp. - -[color=#a4885c]4.3[/color] Don't use hate speech, racism, or bigoted comments. In the 26th century, society has moved passed petty bigotry. - - - [color=#a4885c]4.3.1[/color] Distrust of borgs is exempt from this, due to their recent inclusion into sentient life and the existence of hostile rogue borgs. - - [color=#a4885c]4.3.2[/color] Your character cannot be sexist, racist, speciest, ableist, lgbtphobic as it wouldn't make sense in an age where all are proven capable and treated equal. +[color=#a4885c]4.2[/color] If a player is brought back to life, they cannot recall more than foggy concepts of how they died. From ced009aa797c54ceb131f28d219d877f4e04f164 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:26:10 -0700 Subject: [PATCH 07/12] Revise Section 5 from ERP Rules to Naming Rules Updated Section 5 to focus on Naming Rules, removing ERP-specific guidelines and adding new rules regarding name selection. --- .../ServerRules/CoreRules/RuleC5.xml | 24 ++++--------------- 1 file changed, 4 insertions(+), 20 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml index 78d1bd1d19a..dabf6f6635e 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC5.xml @@ -1,25 +1,9 @@  -[color=#ffff00][head=3]Section 5: Erotic-Role-Play (ERP) Rules[/head][/color] +[color=#ffff00][head=3]Section 5: Naming Rules[/head][/color] -[color=#ff0000]Rules marked in Hardlight's [color=#00fffb]color[/color] will be enforced at all times. Other rules will only be enforced upon recieving a user report.[/color] +[color=#a4885c]5.1[/color] Don't make meta references. -[color=#a4885c]5.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. +Try to be creative by picking a believable and fitting name and/or surname. -[color=#a4885c]5.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. - -[color=#a4885c]5.3[/color] [color=#00fffb]Don't kinkshame.[/color] - -[color=#a4885c]5.4[/color] You should use the (-) subtle command for erotic roleplay material, to avoid others from walking in on your scene. - -[color=#a4885c]5.5[/color] [color=#00fffb]Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting.[/color] - -[color=#a4885c]5.6[/color] [color=#00fffb]Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera.[/color] - -[color=#a4885c]5.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] - -[color=#a4885c]5.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] - -[color=#a4885c]5.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] - -[color=#a4885c]5.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). +Leeway is given to theatrical roles such as the clown, boxer, and mime; these roles are allowed stage names with some amount of freedom. From f23247a7378606783b61f9d79805bb851b26b423 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:27:22 -0700 Subject: [PATCH 08/12] Update Section 6 to Roleplay Rules in RuleC6.xml --- .../Guidebook/ServerRules/CoreRules/RuleC6.xml | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml index 3993b0bbeff..e68b839d6a4 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC6.xml @@ -1,13 +1,18 @@  -[color=#ffff00][head=3]Section 6: Command and Security Rules[/head][/color] +[color=#ffff00][head=3]Section 6: Roleplay Rules[/head][/color] -[color=#a4885c]6.1[/color] Security and Command roles are expected to know and perform their jobs to the best of their ability. You will be held to a higher standard in these roles. +[color=#a4885c]6.1[/color] Your character is a separate entity from you, the player. 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. -[color=#a4885c]6.2[/color] Both Security and Command are required to Know Space Law, Standard Operating Procedures, Alert Procedure, and Company Policy. +[color=#a4885c]6.2[/color] Do not play excessively hostile or provocative characters. Playing a character accurately should never result in rulebreaks. - Ahelp for any questions relating to this. -[color=#a4885c]6.3[/color] Don't abuse your position of power. +[color=#a4885c]6.3[/color] If you choose a job on shift, you are required to participate in the round as said job when necessary. -[color=#a4885c]6.4[/color] You are expected to roleplay with others. This includes antagonists. +[color=#a4885c]6.4[/color] Do not intentionally break roleplay to gain an unfair advantage while someone is typing. + +[color=#a4885c]6.5[/color][color=#00fffb] Respect other people's consent, dignity and boundaries. IF SOMEBODY ASKS YOU TO STOP BOTHERING THEM LOOC (local-out-of-character), do so. If you think this rule is being abused, Ahelp immediately. [/color] + +[color=#a4885c]6.6[/color] Do not dismantle key portions of station infrastructure (IE. escape pods.) + +[color=#a4885c]6.7[/color][color=#00fffb]Roleplaying an underage character is strictly forbidden. So is talk of such activities. [/color] -[color=#a4885c]6.5[/color] If you're in Command, inform your department and Command before cryoing or disconnecting. From ef6a065956d66e5648ec702488cfda8f63408d86 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:28:27 -0700 Subject: [PATCH 09/12] Revise Section 7: Antagonist to Powergaming Rules Updated Section 7 to focus on Powergaming Rules and added guidelines regarding bug exploitation. --- .../Guidebook/ServerRules/CoreRules/RuleC7.xml | 18 +++--------------- 1 file changed, 3 insertions(+), 15 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml index e60957d9a8a..bfd6e749bd7 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC7.xml @@ -1,19 +1,7 @@  -[color=#ffff00][head=3]Section 7: Antagonist Guidelines[/head][/color] +[color=#ffff00][head=3]Section 7: Powergaming Rules[/head][/color] -[color=#a4885c]7.1[/color] Antagonists are held to a higher standard of roleplay, similar to Command. +[color=#a4885c]7.1[/color] Do not hide Antag objective items. -[color=#a4885c]7.2[/color] Antagonists are expected to roleplay with others. This includes Security and Command. - -[color=#a4885c]7.3[/color] The damage that an antagonist is allowed to cause must be proportional to their objectives. - -[color=#a4885c]7.4[/color] Pirates should prioritize theft and ransoming, not murder and destruction. - - - [color=#a4885c]7.4.1[/color] Pirates cannot force interactions which result in player or command bank accounts being robbed. (IE: demanding players withdraw funds for ransom) - -[color=#a4885c]7.5[/color] Nukies should prioritize destroying the station and command. Non-combatants and freelancers should be ignored, unless they are threatening. - -[color=#a4885c]7.6[/color] Revolutionaries want to take control of the station, not destroy it. Converting command should be at least attempted before murdering them. - -[color=#a4885c]7.7[/color] Free agents, such as mice, rat-kings, wawas, and so on should only fight in self-defense, unless they are conscripted by a company. +[color=#a4885c]7.2[/color][color=#00fffb] Do not make active use of known bugs in the game.[/color] From b0f1946f2b482be6d86bdddd8ba41400ffe2a8de Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:29:11 -0700 Subject: [PATCH 10/12] Revise Section 8: End-of-Round Rules and Safezones Updated Section 8 to clarify End-of-Round rules and added details about safe zones. --- .../_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml index a257ddf4dcd..da0f9982967 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC8.xml @@ -1,12 +1,7 @@  -[color=#ffff00][head=3]Section 8: Escalation Guidelines[/head][/color] +[color=#ffff00][head=3]Section 8: End-of-Round (EOR) Rules[/head][/color] -[color=#a4885c]8.1[/color] Lethal force against players should be a last resort. +[color=#a4885c]8.1[/color] End-of-round-griefing (EORG) is not allowed under any circumstance. This includes but is not limited to: fighting, explosives, chemicals, destruction of property, or any other disruptive behavior. -[color=#a4885c]8.2[/color] Don't disproportionately escalate in response to others' actions. - -[color=#a4885c]8.3[/color] Don't ignore critical or dead players unless related to an objective. - -[color=#a4885c]8.4[/color] Don't intentionally round remove other players unless related to an objective. - -[color=#a4885c]8.5[/color] Revenge or "getting back" should be reasonable and proportional. +[color=#a4885c]8.2[/color] Arrivals, as well as the Evac shuttle (and evac hallway), are considered Safezones in which this rule takes effect. + From 3a614a6d90883128f41d64b341547a018abaaa83 Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:30:18 -0700 Subject: [PATCH 11/12] Update ERP rules in RuleC9.xml --- .../ServerRules/CoreRules/RuleC9.xml | 24 +++++++++++++------ 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml index 0931fcaaa7b..db11f6de23c 100644 --- a/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml +++ b/Resources/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml @@ -1,13 +1,23 @@  -[color=#ffff00][head=3]Section 9: Ship saving[/head][/color] +[color=#ffff00][head=3]Section 9: Erotic-Role-Play (ERP) Rules[/head][/color] -[color=#a4885c]9.1[/color] [color=#00fffb]Ships are to be no larger than 80x50 tiles.[/color] +[color=#a4885c]9.1[/color] ERP does not take priority over your job. If you are requested or needed, you must respond or return to your duties ASAP. -[color=#a4885c]9.2[/color] [color=#00fffb]Do not abuse the ship save mechanic to avoid in-character consequences.[/color] +[color=#a4885c]9.2[/color] Don't use ERP as bait for kill objectives, After the ERP is complete, a grace period of 5 minutes is in effect, during which you are still NOT allowed to kill the target. -[color=#a4885c]9.3[/color] [color=#00fffb]Ship saving backups are only to be used in the event of ship destruction or loss due to a server crash or other unforseen issue. Loading backups otherwise is only to be done with admin permission.[/color] +[color=#a4885c]9.3[/color] Don't kinkshame. -[color=#a4885c]9.4[/color] [color=#00fffb]Do not under any circumstances modify a ship save file without admin permission (like with the engine update).[/color] - -[color=#a4885c]9.5[/color] [color=#00fffb]DO NOT ADD MORE THAN ONE BLUESPACE STASH PER SHIP.[/color] +[color=#a4885c]9.4[/color] You should use the (-) subtle command for erotic roleplay material. + +[color=#a4885c]9.5[/color] Do not spam or pollute radio channels (including the telepath channel) with NSFW topics. Mind you, this does NOT mean that you are not allowed to speak or discuss such. There should not be a cringy spamfest of: shitposting, hornyposting, or depression posting. + +[color=#a4885c]9.6[/color] Do not engage in, nor discuss, ‘extreme’ sexual fetishes in public. Public includes: any radio channel (including the telepath channel), out loud speech or overt actions in actual public physical locations, or doing so on camera. + +[color=#a4885c]9.7[/color][color=#00fffb] Engaging in ERP with a non-sentient creature is prohibited. The creature must be player-controlled; consent in OOC, and pass the Harkness test in-character. [/color] + +[color=#a4885c]9.8[/color][color=#00fffb] When roleplaying another person's character, OOC consent from the original (the owner of said character) is required before you engage in ERP. [/color] + +[color=#a4885c]9.9[/color][color=#00fffb] Be very mindful of in-character and out-of-character consent. If your (out-of-character) OOC consent is not respected, immediately Ahelp or open a ticket. [/color] + +[color=#a4885c]9.10[/color] Extreme acts like snuff, abuse, noncon, and other extreme kinks are only allowed if all parties consented OOC, Ahelp if you need clarification (Keep it private). From d982df482f48cf12ec9e5ae56a78b4a04f303dbf Mon Sep 17 00:00:00 2001 From: fenndragon Date: Fri, 20 Feb 2026 14:33:54 -0700 Subject: [PATCH 12/12] Update rules.yml --- Resources/Prototypes/_HL/Guidebook/rules.yml | 22 +++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/Resources/Prototypes/_HL/Guidebook/rules.yml b/Resources/Prototypes/_HL/Guidebook/rules.yml index b9d510d7ac8..b38daceca49 100644 --- a/Resources/Prototypes/_HL/Guidebook/rules.yml +++ b/Resources/Prototypes/_HL/Guidebook/rules.yml @@ -48,4 +48,24 @@ - type: guideEntry id: RuleC9 name: guide-entry-section9 - text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml" \ No newline at end of file + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC9.xml" + +- type: guideEntry + id: RuleC10 + name: guide-entry-section10 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC10.xml" + +- type: guideEntry + id: RuleC11 + name: guide-entry-section11 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC11.xml" + +- type: guideEntry + id: RuleC12 + name: guide-entry-section12 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC12.xml" + +- type: guideEntry + id: RuleC13 + name: guide-entry-section13 + text: "/ServerInfo/_HL/Guidebook/ServerRules/CoreRules/RuleC13.xml"