From fb26a79586b720392688e8dd85e284d9ce002538 Mon Sep 17 00:00:00 2001 From: Forzii Date: Mon, 17 Feb 2025 08:10:26 -0400 Subject: [PATCH 1/3] Mutiny and Permit guide entries Added the mutiny guidelines and permits Floof guidebook entries. --- .../Locale/en-US/Floof/guidebook/guides.ftl | 4 +- Resources/Prototypes/Floof/Guidebook/sop.yml | 14 ++++- .../Floof/Guidebook/SOP/MutinyGuidelines.xml | 19 +++++++ .../Floof/Guidebook/SOP/Permits.xml | 51 +++++++++++++++++++ 4 files changed, 86 insertions(+), 2 deletions(-) create mode 100644 Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml create mode 100644 Resources/ServerInfo/Floof/Guidebook/SOP/Permits.xml diff --git a/Resources/Locale/en-US/Floof/guidebook/guides.ftl b/Resources/Locale/en-US/Floof/guidebook/guides.ftl index a424b1882d..ead2aa4d76 100644 --- a/Resources/Locale/en-US/Floof/guidebook/guides.ftl +++ b/Resources/Locale/en-US/Floof/guidebook/guides.ftl @@ -4,4 +4,6 @@ guide-entry-policy-codeofconduct = Code of Conduct guide-entry-policy-self-defence = Self-Defence guide-entry-policy-conductunbecoming = Conduct Unbecoming guide-entry-policy-appearancestandards = Appearance Standards -guide-entry-policy-dangersfromcompetitors = Dangers from our Competitors \ No newline at end of file +guide-entry-policy-dangersfromcompetitors = Dangers from our Competitors +guide-entry-mutinyguidelines = Mutiny Guidelines +guide-entry-permits = Permits \ No newline at end of file diff --git a/Resources/Prototypes/Floof/Guidebook/sop.yml b/Resources/Prototypes/Floof/Guidebook/sop.yml index 591ae8b965..0b21475305 100644 --- a/Resources/Prototypes/Floof/Guidebook/sop.yml +++ b/Resources/Prototypes/Floof/Guidebook/sop.yml @@ -4,6 +4,8 @@ text: "/ServerInfo/Floof/Guidebook/SOP/StandardOperatingProcedures.xml" children: - Company Policy + - Mutiny Guidelines + - Permits - type: guideEntry id: Company Policy @@ -40,4 +42,14 @@ - type: guideEntry id: Dangers from our Competitors name: guide-entry-policy-dangersfromcompetitors - text: "/ServerInfo/Floof/Guidebook/SOP/DangersfromCompetitors.xml" \ No newline at end of file + text: "/ServerInfo/Floof/Guidebook/SOP/DangersfromCompetitors.xml" + +- type: guideEntry + id: Mutiny Guidelines + name: guide-entry-mutinyguidelines + text: "/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml" + +- type: guideEntry + id: Permits + name: guide-entry-permits + text: "/ServerInfo/Floof/Guidebook/SOP/Permits.xml" \ No newline at end of file diff --git a/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml b/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml new file mode 100644 index 0000000000..e5a0929d6b --- /dev/null +++ b/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml @@ -0,0 +1,19 @@ + +# Mutiny Guideline + +[head=3][color=#ff0000]Last Updated 16 FEB 2025. THE WIKI IS AUTHORITATIVE. This is intended as an in-game reference only and may be out of date.[/head][/color] + +## Incompetence or Inability +## of the Commanding Officer + +Should the station's Commanding Officer, such as the Captain appointed by NanoTrasen, become unfit for their duties, such as allowing damages to the station to go unmanaged or that crew becomes endangered or harmed through their incompetence or inability to lead and delegate, the Departmental Heads on the station can initiate a vote of No Confidence. + +When it is reasonably believed and backed by evidence that the Captain or Commanding Officer has acted to the detriment of the station, the Departmental Heads will hold a vote that requires a majority in order to depose the Captain or Commanding Officer non-lethally and remove them from their position. Once this is done, Central Command must be faxed about the circumstances; the Departmental Heads do not need any more instructions. + +The Captain or Commanding Officer must vacate the position once the Majority has ruled against them. However, if the vote does not go into Majority, the Captain or Commanding Officer cannot depose the Departmental Heads who voted against them. They must find a means to de-escalate the situation. + +## True Mutiny + +When the Crew deems that their Departmental Heads and Captain are a significant detriment to how the station is run, there should be a majority vote that takes place, and the Leader of this Mutiny must fax Central Command of their grievances and Central Command may try to address it when available. The crew must not hold a strike, declare independence, or withhold how the station can operate; they must work with Central Command to rectify the issue. + + \ No newline at end of file diff --git a/Resources/ServerInfo/Floof/Guidebook/SOP/Permits.xml b/Resources/ServerInfo/Floof/Guidebook/SOP/Permits.xml new file mode 100644 index 0000000000..7e90f86d82 --- /dev/null +++ b/Resources/ServerInfo/Floof/Guidebook/SOP/Permits.xml @@ -0,0 +1,51 @@ + +# Permits + +[head=3][color=#ff0000]Last Updated 16 FEB 2025. THE WIKI IS AUTHORITATIVE. This is intended as an in-game reference only and may be out of date.[/head][/color] + +## The Issuer + +Below is a table of who can issue what classification of controlled substance or item within the department. + +It is not reasonable for a Chief Engineer to give a Doctor a permit to provide prescribed desoxyephedrine, but the Chief Engineer can give the Doctor a permit for power tools for whatever reason. + +Whereas, the Captain has the absolute authority to issue a permit and revoke it for any reason. + +(Adapted from wiki table due to formatting limitations) +- Captain/Commanding Officer: Class 1/2/3 +- Head of Security/Warden/Security: Class 1/2 only +- Mystagogue/Epistemics: Class 2 only +- Chief Engineer/Engineering: Class 2 only +- Head of Personnel/Service: Class 2 only +- Chief Medical Officer/Medical: Class 2 only +- Logistics Officer/Logistics: N/A + +## Reasonings + +Above as majority of Class 1 things are typically weapons of low grade and caliber, and almost majority, if not all of substances would fall under Class 2. It is reasonable to surmise that most of departments cannot and will not issue permits for this; easiest method to gain a permit is Security, or Medical. + +Epistemics and Engineering can give out specialized tools and should issue permits with it. + +Not all departmental heads have purview over controlled substances and items, though the Service Department and Head of Personnel are allowed to grow certain medicinal plants. + +## The permit + +A weapon license can be issued from Security; it must be signed and stamped by the permit issuer. + +A prescribed medicine can be issued from Medical; it must be signed and stamped by the permit issuer. + +A building permit can be issued from Engineering; it must be signed and stamped by the permit issuer. + +Above are simple examples, the Captain or Commanding Officer, can issue these permits, however, a crew person should seek out the department or the Departmental Head for the appropriate permit to lessen the strain on the Captain or Commanding Officer. + +For cross-departmental permits, such as a weapons permit or license for Salvage, the Logistics Officer can initiate the permit process, put down what the Salvagers need captured on the permit and Security signs it and stamps it for approval. + +Departmental Heads must not sign and stamp their own permits if it's for something outside of their department. They may only do so for items and substances they have control over. + +[italic]It doesn't have to be anything fancy, as long as the conditions are met: Department it was issued from, the name of the permit issuer, the name of the permit receiver, and a signed name and stamped approve or departmental stamp.[/italic] + +## Defiance of Permit + +At any time, as mentioned above, a permit can be recinded due to the commission of a crime, or other extenuating factors, such as Alert Procedure affecting it. There are many conditions that cannot be outlined, but if a simple example would be that someone has a Class 2 object in their possession but not listed on their Permit. Ensure that both parties know what they are writing down. + + \ No newline at end of file From 9f2b1ff35d06c1875b77094c68976f6a20720bd1 Mon Sep 17 00:00:00 2001 From: Forzii Date: Mon, 17 Feb 2025 08:12:42 -0400 Subject: [PATCH 2/3] Update MutinyGuidelines.xml Dang typo --- Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml b/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml index e5a0929d6b..5d53f47ad5 100644 --- a/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml +++ b/Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml @@ -1,5 +1,5 @@ -# Mutiny Guideline +# Mutiny Guidelines [head=3][color=#ff0000]Last Updated 16 FEB 2025. THE WIKI IS AUTHORITATIVE. This is intended as an in-game reference only and may be out of date.[/head][/color] From 12af20d1a99b2a5bf77d199b19b66678c3a250b8 Mon Sep 17 00:00:00 2001 From: Forzii Date: Sat, 1 Mar 2025 23:52:14 -0500 Subject: [PATCH 3/3] Add general regulations --- .../Locale/en-US/Floof/guidebook/guides.ftl | 3 +- Resources/Prototypes/Floof/Guidebook/sop.yml | 8 +++- .../Guidebook/SOP/GeneralRegulations.xml | 41 +++++++++++++++++++ 3 files changed, 50 insertions(+), 2 deletions(-) create mode 100644 Resources/ServerInfo/Floof/Guidebook/SOP/GeneralRegulations.xml diff --git a/Resources/Locale/en-US/Floof/guidebook/guides.ftl b/Resources/Locale/en-US/Floof/guidebook/guides.ftl index ead2aa4d76..56fb3a5911 100644 --- a/Resources/Locale/en-US/Floof/guidebook/guides.ftl +++ b/Resources/Locale/en-US/Floof/guidebook/guides.ftl @@ -6,4 +6,5 @@ guide-entry-policy-conductunbecoming = Conduct Unbecoming guide-entry-policy-appearancestandards = Appearance Standards guide-entry-policy-dangersfromcompetitors = Dangers from our Competitors guide-entry-mutinyguidelines = Mutiny Guidelines -guide-entry-permits = Permits \ No newline at end of file +guide-entry-permits = Permits +guide-entry-generalregulations = General Regulations \ No newline at end of file diff --git a/Resources/Prototypes/Floof/Guidebook/sop.yml b/Resources/Prototypes/Floof/Guidebook/sop.yml index 0b21475305..6b62a005e9 100644 --- a/Resources/Prototypes/Floof/Guidebook/sop.yml +++ b/Resources/Prototypes/Floof/Guidebook/sop.yml @@ -6,6 +6,7 @@ - Company Policy - Mutiny Guidelines - Permits + - General Regulations - type: guideEntry id: Company Policy @@ -52,4 +53,9 @@ - type: guideEntry id: Permits name: guide-entry-permits - text: "/ServerInfo/Floof/Guidebook/SOP/Permits.xml" \ No newline at end of file + text: "/ServerInfo/Floof/Guidebook/SOP/Permits.xml" + +- type: guideEntry + id: General Regulations + name: guide-entry-generalregulations + text: "/ServerInfo/Floof/Guidebook/SOP/GeneralRegulations.xml" \ No newline at end of file diff --git a/Resources/ServerInfo/Floof/Guidebook/SOP/GeneralRegulations.xml b/Resources/ServerInfo/Floof/Guidebook/SOP/GeneralRegulations.xml new file mode 100644 index 0000000000..b79aa60fe3 --- /dev/null +++ b/Resources/ServerInfo/Floof/Guidebook/SOP/GeneralRegulations.xml @@ -0,0 +1,41 @@ + +# General Regulations + +[head=3][color=#ff0000]Last Updated 01 MAR 2025. THE WIKI IS AUTHORITATIVE. This is intended as an in-game reference only and may be out of date.[/head][/color] + +## Right to Refuse Service + +All standard [bold]Service[/bold] and [bold]Logistics[/bold] members working in a secure area have the [italic]right to refuse service[/italic] to patrons when found to be [bold]abusive or disorderly[/bold]. The use of non-lethal force is permitted to remove these individuals from the area if they [bold]pose a risk[/bold] to the staff of the secure area [bold]or[/bold] disrupt the function of the services provided. Essentially, do not attempt to break in or jump the counter to take things that are not for you. + +- [italic]You've been reported to Security for being abusive and demanding of the Cargo Technicians. [/italic] +- [italic]You've been told to leave, but refuse to do so, and thus you receive a ban from the location until you apologize. [/italic] +- [italic]After all levels of attempted de-escalation, you've nonetheless been beaten to near death because you decided to jump the counter to try and snatch materials that were not yours. Shame on you. [/italic] + +[head=3]Additional Conditions[/head] + +The Bar(s) and Maintenance Bar(s) can have additional rules dictated by who is currently running the establishment; they have the authority to carry these out so long as it does not needlessly over-escalate or have draconian requirements to be followed. A few examples of a rule within the bar: + +- [italic]You may be asked to leave, if intimate relations at the bar are disrupting the general tame atmosphere. [/italic] +- [italic]You may be asked to leave, if you become a depressive drunk, and becoming belligerent. [/italic] +- [italic]You may be asked to leave, if you do not meet the requirements of a dress code or no dress code. [/italic] + +## Hiring & Termination Procedure + +Currently, NanoTrasen dictates who is brought in during shift changes and where they are placed within the respective departments; however, when there are staffing shortages, the Departmental Head or Commanding Officer may offer an additional contract to anyone interested in filling in any gaps in a department. An acting command member can be hired this way, as well. Check that people becoming employed for the department have experience; [bold]ask, don't assume[/bold]. Finally, ensure they're given signed and stamped paperwork stating their job change and who approved it. + +A department head or acting department head can be terminated, much like any other worker on the station. Conditions include, but are not limited to, [bold]theft, sabotage, misuse of department accesses and/or tools, negligence, and refusing to do their job title's tasks and role aboard the station.[/bold] + +A worker's right to refuse work outside of the job title's scope is [italic]NOT[/italic] grounds for termination. [bold]What should be done is to ask if they are interested in adding more to their tasks and roles, i.e.[/bold] + +- "Are they reasonably trained and understand the role?" +- "Do they already have more than enough on their plate?" +- "Should I assign more responsibility to someone who's already busy?" +- "Should I instead, hire someone outside of the department for assistance?" + +Finally, [bold]if the new hire is part of Security or Command[/bold], please make sure that they are given a [bold]Mindshield as it is part of any Security or Command contract[/bold]; refusal to be Mindshielded means they will not be employed. + +## Presentation of Identification (ID) + +All crewpersons on the station should have their identification, readily available to present to anyone who requires it. + + \ No newline at end of file