ReadThisNamePlz

Locking and Archiving. We were going to rule in favor of @Melariara and the warning, but due to the 'plaintiff' being banned... this is not really necessary.

Hi, @Loorey, @eddymakaveli and I will be taking this complaint. Please allow us a few days to read through this, and reference the logs. Thanks!

Okay, thank you for waiting. It has been a week for sure. I am ruling that there was appropriate escalation. One of our Head Administrators, Garnascus, can be quoted saying the following - This was from a discussion about executions as a whole. Antagonists have more leeway than crew-members regarding executions. In this situation, and please correct me if I have this mixed up - There was a firefight before the conflict. This set up the round to have proper escalation for lethal force from the Security team. While you may not have had any interaction with this person prior to them being locked into the telecomms area, you did - or more importantly, the crew did order the AI to lock them in. So at this point, they are cornered, have already been engaged/their partner had been engaged, weapons are out - So, they escalated to shooting you. I firmly do believe that they did not mean anything intentionally malicious. If anything, I'd blame the mechanics of the firearm. Another player decapped two ninjas with a simple .45 while they were in Dominian hardsuits - without intending to. All in all this situation was rough, but I am going to hold up the ruling that Kermit made.

I want to follow up with this. I firmly believe that there was enough communication from all parties involved about the deaths, study of the lings, and sudden appearance of more lings - I do remember trying my best to keep people informed, but when it comes to Delta - I typically do not tell Staff because it is incredibly easy to prevent it. Also, icly I did not know who was “infected” and who was not.

Hi. Due to lack of reply or follow up on your end, I am denying this. Please reapply when you intend on following through.

Hello, I will be handling this complaint. I will rule on this soon.

Hi, please contact me on discord so we can schedule your interview. minimoosetm I reached out to you but received no response.

Hi, I'll provide my thoughts on this. Both IC and OOC. When I joined the round, I heard about the chef murdering someone and then dying. Almost immediately after I was verbally briefed, the chef vented security and was fought a couple of times before being taken into Xenobiology. So ling #1 was established and already handled by like, 30 - 40 minutes into the round. -- OOC Information -- I made a server announcement asking for two volunteers because it was a high pop round and the sole antagonist had been stopped. I am allowed to do this as an Administrator and none of the other staff members online cared - I picked two volunteers, linged them and then gave them each 7 Genome points instead of 5 to make up for the lost time. The two I picked were the Warden and then some Hangar Tech. The Hangar technician ended up cryoing after a while, and then the game auto-selected an Engineer as a ling. Xim, I think? So over the course of the round, after my announcements, two additional lings began to make themselves known/cause havoc. -- IC Information/POV -- By the end of the round, the Wardens ling had been killed. They were in the horror form, and were killed pretty fast. The shift change was called and we remained in code red with no objections from command until the end of round because of how violet and covert the other two lings had been. Specifically the Warden, who had almost killed the HoS and several officers seemingly out of the blue. So, it's liike five minutes until end of the round - two until the gamemode message comes up - and I hear on the engineering channel that Xim (engineer) is acting weird, then like ten seconds later Security is called over because Xim is another one of these creatures. Great. Normally this would be fine if 1.) The first ling was not back alive as a literal skeleton terrorizing people. We shot it, dismembered it, and had it spaced and it still showed back up on ship. 2.) The Warden did not nearly kill a command member and several others due to being so covert, then turning into a large abomination of flesh and bladed bones. 3.) A third member of the crew showed signs of also being like this anomaly and was actively hurting people (I have no actual confirmation if Xim tried to kill someone, i just am able to go off of comms) So, as I explained in ooc after the round - there was a clear pattern being portrayed. One that others saw as well. The lings were not isolated to one person and if someone had direct contact with them (Like the Warden with the Chef, and the Engineer with the Warden), then they were at risk of turning into or being infected. So, I made an EBS message asking for the nuke code and decided to set the station (in like the last minute or thirty seconds) to code Delta to end the round with some extra spice/flavor. We could not contain it. I'm not sure who you played, but we spent an hour or so trying to contain the first ling in Xenobiology and then xenoarcheology, they kept cutting through walls, and reviving. We even spaced them and they showed back up. Sorry, but we did do everything in our power to try and contain them. Tsisana Caladius's player, Pirouette (I can't mention them for some reason) can verify this. So can the engineering apprentice, Lalu and maybe even @Evandorf (HOS). We exhausted every possible avenue of containment and study, and the lings just kept showing up seemingly out of the blue. Also, the monsters were not dead by the end of the round, it had been proven over and over that they weren't able to be killed/spaced - and that others kept surfacing. I do not need to have meetings or input from other command to reach code Delta. It is solely the Captains call/a Captain level decision. But, the reason I did not consult command or anyone else is because I did not know if anyone else was infected. The only person that would've been able to retain the trust of not being infected from my Char was the XO because he manned the bridge all round. The HoS came into direct contact with a ling that tried to kill him, the CMO was treating people who came into direct contact, etc. I mentioned the Intrepid because I was intending on EBSing central that the intrepid is full of potentially infected crew-members and will need to be handled or quarantined, but it is much easier to do so than to do that for an entire ship with potentially countless of these entities. Also, scuttling would've destroyed all of the fluids, body parts, and trace of the lings that were already on board, which would've isolated the infection to the Intrepid - making it easier to contain. Okay. Sure, maybe from your POV it did not seem like this, but taking mine into account, it definitely did. I think I can see where you're coming from with this? The thing with this is that the round did not end though. The third ling showing up is what finalized my decision to go through with this. I EBS'd the code, Mel and the CCIA Lead both agreed that it was fine as long as the timer was set uber long to avoid the explosion and lag, so I went through with it. I do not think I need to add anymore, feel free to ask for clarification on anything.

Alright, sorry for the delay. It has been a busy two days. @Loorey and I have to come to the following conclusion. While it may not have been intentional, the Captain and XO did indeed railroad the gimmick. The Captain and XO player will be receiving a note about this type of thing. We do not want to see command players sending out faxes to ask for confirmation on gimmicks if there is an announcement about said gimmick beforehand. We also do not want command staff to use third party ships to try and circumvent gimmicks. We recognize that this may not have been your intention, but nonetheless it is what happened.

Also, @LordPwner Why did you fax central command asking for the confirmation of the date after there was an announcement made that confirmed the date/setup the mercenaries gimmick?

Hello, I will be handling this alongside @Loorey. Give me some time to gather logs, and review all of it with the assisting moderator. I will need @Lent23 to weigh in as well. Thanks!

https://pastebin.com/Hi7BmkgP Here is the interview. I apologize that it took so long, I have been very busy.

After much deliberation, I’ve decided that if you want to be unbanned it will have to be done via staff complaint. I simply cannot believe that BOTH of these instances took place because you simply weren’t aware of how it was “coming off”. To put it bluntly, it would be setting an extremely poor precedent to unban someone who is using the “I didn’t mean to!” Or “I didn’t know it was this bad!” Defense when it comes to these topics. I simply don’t believe you. I could be wrong, I’m only human. Though, I am certain in my belief that you’re not as “dumb” as you’re intending to come across as.

To clarify, is this an unban request or a staff complaint?

I will be closing this, as the offender has been handled appropriately.

Congratulations, you passed!

Hi, I will be handling this complaint alongside @Faye <3

Sorry for the delay. Accepted!

Heyo! We've decided to go ahead and give you a trial! So, from today - 5/13/2023 to 5/21/2023 (It's nearly 5/14/2023), you will be on trial. I highly recommend playing as much as you can. If you can't play a lot, let me know and we'll work on some accommodations. Gather feedback! Good luck, and enjoy!

I totally didn't forget. Trial begins today and will end 5/6/23.

Any news, @Arrow768?

Hello, you need to gather some more feedback while the team deliberates on trialing you or not. Thanks!

Reporting Personnel: Artemis Grey Job Title of Reporting Personnel: Captain Personnel in Question: Ska'zaszhk Guwan Job Title of Personnel in Question: Cook - or, Janitor? I believe they were bumped down to Janitorial service. Reason for Review: [X] - Extended Arrest History [ ] - Grievous Infraction on Record [X] - Other: Slandering a Head of Staff. Notes: I have small, distasteful history with this Guwan. I had just filed an IR and it was resolved. Directly after the resolution was handed out, the Guwan began to verbally attack me yet again - calling me racist, accusing me of harassment, insulting me directly with the words "Bitch" and "Heartless woman". She was clearly emotionally charged, and I intended to ignore it, as they clearly lack the maturity to maintain their composure. However, she spit in my food. I ordered an arrest with the charge of Slandering a head of staff - in the sight of several people, mind you. She resisted arrest and I had to get a different officer to carry it out, due to hoping for a de-escalation. I was advised to make a review-request because their employment here is laughable. From threatening me with "This would not go this way where I am from", openly slandering me by calling me a "racist" (The whole reason I made an incident report in the first place.) Refusing to serve me, and then spitting in my food after a different cook made the steak for me. This Guwan is a miserable excuse for a quality employee. The Horizon is meant to staff the Conglomerate's best, and this cook is nothing but trouble.

Locking and archiving.

Hi. No questions really. Cybs and I have taken the time to review everything and we've talked extensively about the situation. It became pretty clear you did this exclusively due to the situation with the ban evader rather than any happenstance, like what happened when you began activity again during the problem with Zulu's discord. It's the same issue and you really have only shown up around these problems at the moment. Because of this, we just don't feel that it is right to have you around due to the nature of what occurred. Also, I can appreciate the attempt at showing that Stars perpetrated this in some manner. Truly. However, this basically just shows that despite all of this, you're continuing to interact with SOS. Which is pretty much the whole reason this situation is an issue. With that said, we're going to uphold Matt's decision. If you feel that this is still wrong, you can make a staff complaint and it'll be reviewed by a Headmin.