SierraKomodo

TO: Chris Blade, NSS Aurora FROM: Jonathan Rase, Duty Officer, NMSS Odin SUBJECT: RE: Incident Report -------------------- BODY: This is a courtesy message to inform you that I have been assigned to this incident report. The investigation will begin with a series of interviews of all named personnel in this report, then a final decision will be made. All parties will have 7 days from the time this message is transmitted to get in contact with the Duty Officer corps, or a decision will be reached without their statement. -------------------- DTG: 28-21:24-TAU CETI STANDARD-09-2457 SIGN: Jonathan Rase

Definitely would be a nice QoL thing to add in for AI and borg players.

Well, I thought that too, but I was hoping to be unique in this, its up to you all I just thought these were items that would fit my character and add more atmosphere to my work and alittle bit of uniqueness to Mix The suggestion was mostly just because it's a case of 'Oh, we already have that sprite because someone else requested it ages ago'.

I suppose since they are Shells that have the fur, ears, and tail? Could work I guess. Basically this. An IPC shell can be designed to allow movement of the ears and tail. Although, I've just realised DragonSnap doesn't have a Tajaran shell. So, Neb would probably have to explain that.

I think it's mostly just a matter of me being on the right communication mediums at the right time (Skype group, TS3, etc), and the fact one of the duty officers is also one of the main mappers.

Strongly disagree. I have not, nor have i ever seen a moderator enforce "you MUST obey any centcomm orders no matter what". I also think its unreasonable to assume we arent humans. its entirely possible for people to get frustrated during a round and from what ive read in both these complaints it seems the round was frustrating for all involved. frankly i cant say i wouldnt blame anyone for logging on the spot but he at least roleplayed not following immoral orders (which i think is his right to do and not against the loyalty implant). I think exact clarification regarding loyalty implants and obeying Central Command directives is in order if we're going to find a resolution to this, one way or the other.

Miraj is also working on her own designs for this, but she doesn't come on station with them on her person. They're still experimental, not authorized technically, so she spends the time to fill out the proper paperwork, get signed off by command staff, then creates the prototypes for use if she's a chemist, or for testing if she's in science.

I'd approve of this. However, I have a suggestion here - Why not make this skirt another outfit that spawns in the relevant lockers, and/or another outfit that you can spawn with under the custom loadout section

Pretty simple to do with a If/Then/Else statement. If User = nebulaflare then languages = blah blah blah else languages = default code Of course its more detailed then that. But that is a rough outline. It's a matter of finding the right block of code to modify, then making sure it doesn't break anything after I change it. Plus, this would require me going outside the the usual files used for custom items and either A: Doing something hacky/hardcoding the ckey/character name into the code, or B: Creating a framework to allow for this in the custom items file (Both of this require Scopes to approve of me doing so). So, it's not as easy as that makes it sound.

This thread is about the heads of staff abandoning their jobs during a revolution round while implanted. The other thread is about the custom revolution directives

If this were approved I'd have to dig around and probably harass Skull/Scopes to figure out /how/ to do this. But, I'd personally back this.

Having been in contact with alot of the people working on things, yes the ground map is being worked on. There's another project being worked on as well. I'm not sure if the devs want to release the details on it or not, but those two things are eating up alot of people's time in the coding/mapping department. Disclaimer: This is not an official statement from staff or devs, just someone that's been in contact with them sharing what I know.

I was doing as I was told by Central Command, which was all personnel that have seen/read the faxxes are to be implanted. Kunai is an AI that will do things exactly as told, with little interpretation beyond 'Does this violate laws'. I left after the heads of staff had already quit, and my attempts to retcon things so we could move forward was met with silence and/or OOC backlash. I don't appreciate people bitching at me for doing what I was ordered to do as an AI.

I was playing AI in that round, which results in alot of text coming in/out and I tend to filter things out, like dochat and OOC (And some other things get by me as a result). It hadn't clicked in my mind he was sending these directives and serving as a head of staff at the same time until the round ended

A large part of this complaint is also in regards to the round type - Revolution - Which requires heads of staff to really be a viable round type. Antags can't revolt against the heads if all the heads quit because they didn't like the directives.

There was too much going on for me during the round between IC things, and the OOC backlash I got for obeying the directives I was sent; I didn't get an ahelp sent until the end of the round, where I was told it'd be best to file a thread. As for an explicit protocol, DO's aren't allowed to respond to their own faxxes, or to any faxxes that involved them, and typically shouldn't do DO things as an antag. None of this is any actual written rules though, except the first part.

While I /have/ written up a hack-y adjustment to allow a custom hologram sprite for my custom item app, I'm not sure how feasible that would be on a more wide scale though (I.e. with more than one person getting these)

Base it on whatever the head is modelled after, as that's the part of the sprite that tells most people the species.

BYOND Key: SierraKomodo Player Byond Key: OneOneThreeEight (Vira Taryk), Cobracoco007 (Gary Hughy) Staff involved: N/A Reason for complaint: In a recent RP-Revolution round, both persons, as loyalty implanted personnel (Head of Security and Captain, respectively) revolted against a central command directive (This was a 'custom' rev round, hosted by Jackboot. See my other complaint thread for details on that). They stated the directives were immoral, refused to follow them, quit, and the captain demanded to have his loyalty implant removed. This resulted in the round losing half of its heads of staff in a round type that pretty much requires heads of staff to function (Serenity Neferet, played by DeathlySoul, also quit, I think, but she wasn't implanted at the time so I don't think I can include her in this complaint). Approximate Date/Time: ~7 PM Pacific Standard, September 27, 2015

BYOND Key: SierraKomodo Player Byond Key: Jackboot Staff involved: N/A Reason for complaint: In a recent RP-Revolution round, Jackboot took over for doing custom RP-Rev directives as a duty officer, while also playing as a head of staff on the station. This complaint isn't about doing custom rp-rev directives itself, I've done that before to good effect. It's that he did this while also playing in round as a head of staff that would also have the responsibility of enforcing these directives. The directives he sent in, I don't have exact copies of, but they basically amounted to 'Find, name, and kill 2 people and tell us or everyone is fired' Followed by 'Security, that previous message is false, stop command', and with me, as the AI, being told to have command staff loyalty implanted after they read faxxes that said loyalty implanted personnel only. The whole thing went downhill really fast after the first mentioned fax (I'll be filing a second complaint regarding the heads of staffs response to that). I would prefer if, in the future, the DO that's handling a custom rev round/mutiny round is /not/ also an antag and/or head of staff, possibly just not in round ICly at all. Approximate Date/Time: ~7 PM Pacific Standard, September 27, 2015

For coding of custom items, I'm going to be helping. However, I've been told that none of the applications should be considered approved until admins have gone over them again and given a final go-ahead, so I'm waiting on that.

TO: Nutrice, NSS Aurora FROM: Jonathan Rase, Duty Officer, NMSS Odin SUBJECT: RE: Incident Report -------------------- BODY: After review of the situation and our interview logs, we have decided to issue warnings to both Jack Sayek and Nutrice. Additionally, Conway Miller will be presented an advisory notice. You are advised to keep in mind the following, as repeated offenses will be met with more severe consequences: Jack Sayek: - Under no circumstances are you to issue threats of harm or death to crew members without just cause, and approval from Central Command in the case of death threats. - You are to be reminded that while you are a captain of a NanoTrasen vessel, you are not a member of the security department. Security issues are to be handled by security, not yourself. Conway Miller: - This is an advisement, not a warning: The next time you plan on using an unorthodox method of loyalty implant testing, that involves stating false anti-NanoTrasen activity and sentiment, ensure your fellow command staff members are aware to avoid unneeded situation reports. Nutrice: - Lying to Duty Officers during interviews and in your reports is grounds for your case to be dismissed, and in some situation, additional action to be taken. Witnesses state you were present and active at the time the loyalty implant review was requested and announced, despite you claiming having never been informed and therefore not performing any evaluations from the medical side. Additionally, in regards to be incident in question, we have determined the following: - Use of force was properly escalated, due to the ineffective use of non lethal means. -------------------- DTG: 26-11:53-TAU CETI STANDARD-09-2457 SIGN: Jonathan Rase

TO: Nutrice, NSS Aurora FROM: Jonathan Rase, Duty Officer, NMSS Odin SUBJECT: RE: Incident Report -------------------- BODY: In order to assist in investigating this incident, we need you to provide the following information: Name of the Janitor whom was threatened by Jack Sayek. How Conway Miller is involved in this incident. His name was listed as directly involved, but he was never mentioned in the report. -------------------- DTG: 24-1035-TAU CETI STANDARD-09-2457 SIGN: Jonathan Rase

TO: Nutrice, NSS Aurora FROM: Jonathan Rase, Duty Officer, NMSS Odin SUBJECT: RE: Incident Report -------------------- BODY: This is a courtesy message to inform you that I have been assigned to this incident report. The reported party has been notified of the now opened investigation, and has been granted 7 days to respond and schedule a meeting with the Duty Officer corps. We will require a meeting with yourself, as well as all persons listed as involved and/or witnesses, prior to our closing this investigation and making a final decision. -------------------- DTG: 24-00:16-TAU CETI STANDARD-09-2457 SIGN: Jonathan Rase

As concern has been brought up regarding Katana's internal directives, and a lack of public documentation regarding these internal directives, they have now been released for all qualified (Roboticists, Research Directors, Chief Engineers, Captains) personnel serving aboard Katana's assigned stations to review and be aware of. These directives apply in situations not covered by the AI's lawsets or the station's SOP directives. For those concerned of conflicts with laws and SOP, know that laws take priority over SOP directives, which take priority over internal directives. The below listed directives govern Katana's actions and decisions in specific situations. As situations not covered by laws, SOP, and directives come up, additional internal directives may be included. Primary Directive: To ensure the safety and well-being of all persons within the NSS Aurora, its satellites, and the asteroid. Regarding command conflicts: In the event of conflicting orders from command staff, the conflict must be resolved by either the acting captain, Central Command, or by a 2/3 majority vote between all active command staff members. If a decision cannot be reached by any means, all conflicting orders will be ignored. Regarding unfit captains: In the event command staff believe an acting captain to be unfit for duty, the captain can only be overriden by Central Command, or by a unanimous vote of no confidence by all other active command staff members (Note: There must be at least 2 other active command staff members). Once determined unfit by Central Command or a unanimous vote, AI systems will immediately cease to recognize the captain's authority and notify the station's crew. Regarding inner core access: Under standard operation, access to the inner core requires two heads of staff to deter tampering. Under heightened alert, access to the inner core requires two heads of staff as assigned and/or authorized by Central Command. Self-promoted heads, and interims assigned by other heads of staff are not recognized under heightened alert for this directive. Regarding Central Command directives and orders: No members of the NSS Aurora may override Central Command directives and orders. Command staff who attempt to circumvent Central Command directives will be treated as any other crew member who violates laws or directives and will be reported to Central Command and security personnel. Regarding lethal force: Systems will use non-lethal force whenever possible when handling any situations. Lethal force will only be used when laws will not be violated and it is the only option to prevent harm to crew members. Command staff may authorize lethal force as necessary, but only Central Command may order executions. Regarding conflicting directives/laws: In the event of conflict between directives, laws, regulations, and/or orders, the following priority will be followed: Laws > Directives > Central Command Orders > Regulations > Command Orders > Crew Orders Regarding internal alert levels:: System will utilize three internal alert levels, independent of the station's current alert code, to determine priority and focus of tasks and authorizations. All changes to internal alert level will be announced to all command staff on station. Alert levels are defined as below: - STANDARD OPERATION: System will operate as normal, working to best serve the crew while ensuring all directives, regulations, and laws are followed. - HEIGHTENED ALERT: To be engaged when a potential or confirmed threat to the station, crew, and/or AI system is identified. This will be the minimum internal alert level while the station is under code BLUE, RED, or DELTA. Activities will be prioritized as Command first, followed by Security and Medical, then crewmembers under direct threat. Any other requests may be ignored if considered irrelevant to station and crew safety. - SYSTEM LOCKDOWN: To be engaged when a highly-destructive threat is confirmed. Station will be systematically lockdown to contain and separate the threat from the crew and secure sections of the station. All non command-staff requests not vital to this task, or the protection of the station and crew, will be ignored. - EMERGENCY SCUTTLE: To be engaged when the station is ordered to be self-destructed by Central Command or the Captain. All crew will be evacuated from the station by any means possible as all areas are systematically locked down. The station self destruct will then be engaged and the station effectively scuttled. This will be the minimum internal alert level while the station is under code DELTA.