Jump to content

TullyBBurnalot

Retired Admins
  • Posts

    2,631
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by TullyBBurnalot

  1. This could potentially be solved by making the item stack up to, say, 100 or so, and turning the Stamping Press into something like the Stacking Machine, so it holds up to that amount, then ejects the stack. I wasn't sure if this was possible when I made the suggestion, but if it is, I am absolutely for it. As always, a prisoner may request a specific type of sentence, but the final sentencing is given at the moment of brigging, and prisoners may not be transferred to the workshop/cells if they were already sentenced to cell/workshop time, barring exceptional circumstances (like attempted murder of the jailors).
  2. Edit: Some of the AI maintenance laws seem to be for the AI, which seems silly; the AI is of course not bound by SoP and thus defining what turrets should be set to, etc seems useless. Holy crap, how did I miss that without? Alsl, in regards to that, AI Maintenance SOP is very much directed at Command, not the AI.
  3. Added: To the Captain's "Security Duty" Guideline.
  4. As much as I dislike the Slippery Slope argument, letting Command upload Freeform Laws freely can only lead to disaster. Unless of course we sit down and write up every single possibility in which a Freeform Law is allowed or not. As it stands, the "unless absolutely necessary" requirement holds merit. A Freeform Law can be literally anything, and can therefore be abused to hell and back. It stands to reason that something with that amount of power should be limited to situations that VERY MUCH WARRANT IT.
  5. Stahp posting faster than I can respond, darnit! That reminds me. Adding: To Captain SOP.
  6. Added. Will be added in General SOP. I actually meant it differently, I'll specify it:
  7. That's actually a valid point. However, it's already covered in Guideline 2. I liek this one. Adding. Adding: To the Guideline. Also, the RD should be given priority over other heads in this, as they are, technically, the one person who is, ICly, most qualified to handle AI Units. That said, also adding: To the Guideline. Will be discussed. All demotions will be handled in General SOP.
  8. While I understand your concerns, my particular issue lies in the fact that Command positions are supposed to be the most responsibility-laden and the ones more subject to scrutiny. People should not be picking a Head position in order to just do whatever it is they want to do. At the end of the day, they're still working for NanoTrasen, and should be held accountable whenever they screw up. A lot of these guidelines are actually stuff that either already happen, or people expect to happen (such as the NT Rep not being a douchebag and threatening to fire people, or the HoP not going around with full access 4noraisins). As for the Captain, well... they're intended to be the single most important job on the station. They're meant to be the one person whose job is to literally babysit everyone and make sure they play along. And again, keep in mind, STANDARD Operating Procedure. Even disregarding the Captain's last Guideline, they can, and should, go around SOP if the situation requires it. Again, this is not inflexible. As for the majority vote for promotion, I can see it's getting some flak. As such, I will be changing it to: I believe that would be sufficient?
  9. Even though this is an OOC note, can't hurt adding it again. I honestly thought I changed that. Swapping. Specifying, I hope, would not be needed. ... That said... *scribble* Also a good point. I'll do you one better. I'll make it: Next up. Your nitpicking. It is acceptable. Also a good point. Adding. I am in love with that word. Good points there, actually. Adding. Eehhhhhhh, I dunno. I can see this being abused immensely by Comdoms who send out the Blueshit to validhunt. Already added. Also a good point. Adding. Better safe than sorry? I'm not sure if I like this. "Suspected" can mean literally anything if you stretch it out far enough, and I know some people will deliberately abuse the hell out of this. Also a good point. Again, good point. I do agree it's a big change, but I'd rather get it out of the way rather than stretch it out beyond even SOP. As such, proposing to change: To: In addition, adding:
  10. Foreword: Command roles are among the most important jobs and thus more heavily scrutinized by Administrator Staff There are 9 unique jobs pertaining to the Command Department: Captain, Head of Personnel, Head of Security, Chief Engineer, Chief Medical Officer, Research Director, NanoTrasen Representative, Magistrate and Blueshield. Seeing as the Head of Security, Chief Medical Officer, Chief Engineer and Research Director have already been handled, they will be omitted from this list. The Magistrate will be included in Legal Job SOP, along with the Internal Affairs Agent. Proposed Job SOP is as follows: Captain: The Captain is not permitted to perform regular Security Duty. However, they may still assist Security if they are understaffed, or if they see a crime being committed. However, the Captain is not permitted to take items from the Armory under normal circumstances, unless authorized by the Head of Security. In addition, the Captain may not requisition weaponry for themselves from Cargo and/or Science, unless there's an immediate threat to station and/or crew; If a Department lacks a Head of Staff, the Captain should make reasonable efforts to appoint an Acting Head of Staff, if there are available personnel to fill the position; The Captain is to ensure that Space Law is being correctly applied. This should be done in cooperation with the Head of Security; The Captain is not to leave the NSS Cyberiad unless given specific permission by Central Command, or it happens to be the end of the shift. This includes via space or via the Gateway. To do so is to be considered abandoning their posts and is grounds for termination; The Captain must keep the Nuclear Authentication Disk on their person at all times or, failing that, in the possession of the Head of Security or Blueshield; The Captain is to attempt to resolve every issue that arises in Command locally before contacting Central Command; The Captain is not permitted to carry their Antique Laser Gun or Space Armor unless there's an immediate emergency that requires attending to; The Captain, despite being in charge of the Cyberiad, is not independent from NanoTrasen. Any attempts to disregard general company policy are to be considered an instant condition for contract termination; The Captain may only promote personnel to a Acting Head of Staff position if there is no assigned Head of Staff associated with the Department. Said Acting Head of Staff must be a member of the Department they are to lead. See below for more information on Chain of Command; The Captain may not fire any Head of Staff without reasonable justification (ie, incompetency, criminal activity, or otherwise any action that endangers/compromises the station and/or crew). The Captain may not fire any Central Command VIPs (ie, Blueshield, Magistrate, NanoTrasen Representative) without permission from Central Command, unless they are blatantly acting against the well-being and safety of the crew and station Head of Personnel: The Head of Personnel may not transfer any personnel to another Department without authorization from the relevant Head of Staff. If no Head of Staff is available, the Head of Personnel may make a judgement call. This does not apply to Security, which always requires authorization from the Head of Security, or Genetics, which requires both Chief Medical Officer and Research Director approval. If there is no Head of Security active, no transfers are allowed to Security without authorization from the Captain; The Head of Personnel may not give any personnel increased access without authorization from the relevant Head of Staff. This includes the Head of Personnel. In addition, the Head of Personnel may only give Captain-Level access to someone if they are the Acting Captain. This access is to be removed when a proper Captain arrives on the station; The Head of Personnel may not increase any Job Openings unless the relevant Head of Staff approves; The Head of Personnel may not fire any personnel without authorization from the relevant Head of Staff, unless other conditions apply (see Space Law and General Standard Operating Procedure); The Head of Personnel may not promote any personnel to the following Jobs without authorization from Central Command: Barber, Brig Physician, NanoTrasen Representative, Blueshield, Security Pod Pilot, Mechanic and Magistrate; (This is due to them being karma locked. Do not promote people to these positions without approval from the Administrators) The Head of Personnel is free to utilize paperwork at their discretion. However, during major station emergencies, expediency should take precedence over bureaucracy; The Head of Personnel may not leave their office unmanned if there are personnel waiting in line. Failure to respond to personnel with a legitimate request within ten (10) minutes, either via radio or in person, is to be considered a breach of Standard Operating Procedure; Despite nominally being in charge of Supply, the Head of Personnel should allow the Quartermaster to run the Department, unless they prove themselves to be incompetent/dangerous; The Head of Personnel is bound to the same rules regarding ordering Cargo Crates as the Quartermaster and Cargo Technicians. In addition, the Head of Personnel may not order unneeded, non-essential items against the wishes of Cargo; The Head of Personnel is not permitted to perform Security duty. The Head of Personnel is permitted to carry an Energy Gun, for self-defence only NanoTrasen Representative: The NanoTrasen Representative is to ensure that every Department is following Standard Operating Procedure, up to and including the respective Head of Staff. If a Head of Staff is not available for a Department, the NanoTrasen Representative must ensure that the Captain appoints an Acting Head of Staff for said Department; The NanoTrasen Representative must attempt to resolve any breach of Standard Operating Procedure locally before contacting Central Command. This is an imperative: Standard Operating Procedure should always be followed unless there is a very good reason not to; The NanoTrasen Representative must, together with the Magistrate and Head of Security, ensure that Space Law is being followed and correctly applied; The NanoTrasen Representative may not threaten the use of a fax in order to gain leverage over any personnel, up to and including Command. In addition they may not threaten to fire, or have Central Command, fire anyone, unless they actually possess a demotion note; The NanoTrasen Representative is permitted to carry their Stun-Cane, or a Telescopic Baton if the Stun-Cane is lost Blueshield: The Blueshield may not conduct arrests under the same conditions as Security. However, they may apprehend any personnel that trespass on a Head of Staff Office or Command Area, any personnel that steal from those locations, or any personnel that steal from and/or injure any Head of Staff or Central Command VIP. However, all apprehended personnel are to be processed by Security personnel; The Blueshield is to put the lives of Command over those of any other personnel, the Blueshield included. Their continued well-being is the Blueshield's top priority. This includes applying basic first aid and making sure they are revived if killed; The Blueshield is to protect the lives of Command personnel, not follow their orders to a fault. The Blueshield is not to interfere with legal demotions or arrests. To do so is to place themselves under the Special Modifier Aiding and Abetting; The Blueshield is not to apply Lethal Force unless there is a clear and present danger to their life, or to the life of a member of Command, and the assailant cannot be non-lethally detained AI Maintenance: Only the Captain or Research Director may enter the AI Upload to perform Law Changes (see below), and only the Captain, Research Director or Chief Engineer may enter the AI Core to perform a Carding (see below); No Law Changes are to be performed without approval from the Captain and Research Director. The only Lawsets to be used are those provided by NanoTrasen. Failure to legally perform a Law Change is to be considered Sabotage. Command must be informed prior to the Law Change, and all objections must be taken into consideration. If the number of Command personnel opposing the Law Change is greater than the number of Command personnel in favour, the Law Change is not to be done. If the Law Change is performed, the crew is to be immediately informed of the new Law(s); The AI may not be Carded unless it it clearly malfunctioning or subverted. However, any member of Command may card it if the AI agrees to it, either at the end of the shift, or due to external circumstances (such as massive damage to the AI Satellite); The AI Upload and Minisat Antechamber Turrets are to be kept on Non-Lethal in Code Green and Code Blue. The AI Core Turrets are to be kept on Lethal at all times. If a legal Law Change or Carding is occurring, the Turrets are to be disabled; If the AI Unit is not malfunctioning or subverted, any attempt at performing an illegal Carding or Law Change is to be responded to with non-lethal force. If the illegal attempts persist, and the perpetrator is demonstrably hostile, lethal force from Command/Security is permitted; Freeform Laws are only to be added if absolutely necessary due to external circumstances (such as major station emergencies). Adding unnecessary Freeform Laws is not permitted. Exception is made if the AI Unit and majority of Command agree to the Freeform Law that is proposed; Any use of the "Purge" Module is to be followed by the upload of a NanoTrasen-approved Lawset immediately. AI Units must be bound to a Lawset at all times Revised Chain of Command: The following individuals are to be considered members of the Chain of Command: Captain, Head of Personnel, Head of Security, Chief Medical Officer, Chief Engineer and Research Director. Barring exceptional circumstances (see below), the NanoTrasen Representative and the Magistrate are not to be considered part of Chain of Command, though their input should still be taken into consideration; The Captain is to be considered the top authority in the Chain of Command. In the absence of a Captain, the Head of Personnel is to be considered the Acting Captain. If there is a major station emergency, however, the Head of Security is to be considered the Acting Captain, until such a time as the emergency has passed, at which point the Head of Personnel is to be Acting Captain; In the absence of a Captain, Head of Personnel and Head of Security, a vote is to be held among the available Heads of Staff in order to determine who should be considered the Acting Captain; In the absence of any Heads of Staff, the NanoTrasen Representative is to be considered the Acting Captain; The Acting Captain is to step down once an actual Captain is assigned to the station; A Captain may choose to step down from Command. If they do so, Chain of Command is to be followed, and the former Captain is to be assigned to another job; An Acting Captain may step down from Command. If they do so, Chain of Command is to be followed, and the former Acting Captain is to return to their original rank. If this process reaches the voting stage, any Head may opt out of being a candidate; In the absence of a Head of Security, the Warden is to be considered the Acting Head of Security; In the absence of an assigned Head of Staff, the Captain and/or Head of Personnel may promote a member of the Department to the position of Acting Head of Staff. This Acting Head of Staff is to step down when an official Head of Staff is assigned; All Acting Captains/Heads are to secure all sensitive items associated with their rank. These items are to be returned to their respective office once an official Captain/Head of Staff is assigned
  11. Command Job SOP: Complete! Greetings, aspiring SOP writers. If you've clicked this thread, then you're either interested in contributing to Standard Operating Procedure, or are merely interested in seeing how it's going. Therefore, I shall begin by explaining what this (soon-to-be) megathread is all about: Part 1: What is this? Approximately 4 months ago, Necaladun approached me with a personal project of his: a complete overhaul of Standard Operating Procedure, meant to centralize SOP in such a way that allowed for more interaction with the Legal sub-Department, more actual guidelines on how to conduct one's performance, and generally formalize what was once only nebulous guidelines in an effort to get everyone on the same page. This was the project that led to the current version of Security SOP. However, it was left half done, as Necaladun took his leave shortly after Sec SOP was added, and the project crumbled from lack of interest/time. However, I continued the project, but only recently picked it back up in full. The point of this megathread will be to, at the end of the line, have a single, well-defined, centralized Standard Operating Procedure that everyone can look at and fully comprehend, without any self-contradictory information. This, of course, will be changed in the Wiki, which is still the main source of information for the playerbase. Part 2: How does it work? Seeing as I actually have most of this stuff already written down, the process will be quite simple, and I'll break it down in stages: Stage 1: Selection of which part of SOP to look at, out of provided options (because we have to start somewhere). This will be done via poll; Stage 2: Proposal of new SOP. This will come from myself, again, because I have pretty much most of it already written down, so we have a solid base to go from; Stage 3: General feedback from the community. This is the main part of the process, as it will be the one where everyone can pitch in, say which parts are right, which parts are wrong, what should be changed, etc; Stage 4: Amendments made to SOP based on this feedback, and continued discussion, until a finalized version is produced; Stage 5: SOP is posted on the Wiki; Stage 6: Refer to Stage 1 Do keep in mind the following: everyone is permitted to pitch in. If you believe you have anything to add to the discussion, please do, but do try to keep this on track and problem-oriented, otherwise we'll never get off the drawing board. Part 3: What does it entail? The following are the proposed additions to this new, centralized SOP: Security Job SOP; (added by Necaladun before he took his leave) Engineering Job SOP; (finalized!) Medical Job SOP; (finalized!) Service Job SOP; (finalized!) Supply Job SOP; (finalized!) Science Job SOP (finalized!) In addition to the basic SOP for each Department, I also propose: Departmental SOP (as in, general guidelines for each Department that everyone should follow); (stricken to avoid bloat) Command SOP (in-depth SOP for each member of Command, not in Guideline form); (yes in Guideline form, the hell was I thinking?!) Legal SOP (standardization of Legal procedures and the action of the Legal sub-Department); A revised General SOP, for each Color Code. This will include Safety Regulations As you can see, this is a rather big project and, as such, will be tackled in small stages. At each point, the completed section of SOP will be crossed out, and a notification written. At the end of the journey, a single, massive Standard Operating Procedure page will be added to the wiki, with all the above SOPs for everyone to look at. In addition, of course, to their own specific pages. And now, you've reached the end of the page. It's time to start, ladies and gentlemen.
  12. In the absence of any further discussion, moving on.
  13. Can we please not descend to hostility as the first response to an idea we disagree with? Let's stay on track, please.
  14. My intention for "unruly" was very much "acting overtly hostile towards other bar patrons". Say, someone who continuously treats everyone around them like shit, and/or smacks them around. I shall clarify this by adding: To that particular Guideline. Next up: See, now this is a good point to make. While I'm reticent to tell people how to be funny, I can absolutely see where you're coming from. No one likes slip spammers. As such, the Guideline will have the following added to it: Emphasis added. Next up: This, as far as I care, borders on breaking some base "meta" rules, in that the "Me" emote system is supposed to be used to emote, not talk. The entire point of the Mime being unable to speak unless they break the Vow of Silence is that they're not supposed to communicate normally. Using the "Me" system to go around that and, basically, talk, is something I have personally BWOINK'd people over. Mimes are mute. Act that way. ... good point. Adding: To the Guideline. Far as I know, Null Rods/Holy Swords have no special effect against the supernatural apart from revealing/destroying runes. This reminds me of an ongoing thread. My opinion on this matter can be summed up thusly: TL;DR: It's there, it can be used, just take the proper precautions. I'd rather not encourage people to ignore a method of doing their job because doing so will cause a minor annoyance to whoever can't be bothered to click a button. THAT SAID, adding the following to the Guideline:
  15. 'Dat eyebrow on Tristen. Stellar work, as always.
  16. What the title says. Please. It's a TABLE.
  17. Considering the lack of discussion, I'll be giving this three more days, then I'm moving this to the wiki and starting on... COMMAND SOP! DUN DUN DUUUUUUUUUUUUUUUUUUUUUN!!!!!!
  18. I should point out, only reason that part of Implant SOP is because doing organ manipulation surgery in an unclean environment has a good chance of leaving you with an internal infection that, if untreated, will kill you. If Robotics takes precautions to be clean, I don't see why they shouldn't do implantation as well (most people are too lazy to get implants and go to Medbay anyway). As for the tools... you don't need them. You can bend back the ribcage/skull, then cauterize the incision with a sharp object+cautery.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use