Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Floof Mutiny Guidelines and Permits to Guidebook #564

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion Resources/Locale/en-US/Floof/guidebook/guides.ftl
Original file line number Diff line number Diff line change
Expand Up @@ -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
guide-entry-policy-dangersfromcompetitors = Dangers from our Competitors
guide-entry-mutinyguidelines = Mutiny Guidelines
guide-entry-permits = Permits
14 changes: 13 additions & 1 deletion Resources/Prototypes/Floof/Guidebook/sop.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@
text: "/ServerInfo/Floof/Guidebook/SOP/StandardOperatingProcedures.xml"
children:
- Company Policy
- Mutiny Guidelines
- Permits

- type: guideEntry
id: Company Policy
Expand Down Expand Up @@ -40,4 +42,14 @@
- type: guideEntry
id: Dangers from our Competitors
name: guide-entry-policy-dangersfromcompetitors
text: "/ServerInfo/Floof/Guidebook/SOP/DangersfromCompetitors.xml"
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"
19 changes: 19 additions & 0 deletions Resources/ServerInfo/Floof/Guidebook/SOP/MutinyGuidelines.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
<Document>
# 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]

## 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.

</Document>
51 changes: 51 additions & 0 deletions Resources/ServerInfo/Floof/Guidebook/SOP/Permits.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
<Document>
# 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.

</Document>
Loading