Jump to content

CampinKiller

Primary Administrators
  • Posts

    520
  • Joined

  • Last visited

Everything posted by CampinKiller

  1. During all the testing I did, the radiation was always gone with plenty of time to exit maintenance. I did forget to update the description of the PR with the announcement, which I had intended to change, but gave me a merge conflict no matter which way I did it. Regardless, I've put up a PR to change the announcements slightly and extend the maintenance access time to compensate for the radiation needing to dissipate. https://github.com/Aurorastation/Aurora.3/pull/17250
  2. Reporting Personnel: Logan Wright Job Title of Reporting Personnel: Head of Security Game ID: cpz-a4jG Personnel Involved: Wu'll Xorlaq, Off-Duty Crewmember - Offender/Victim Korza Rokuraz, First Responder - Offender/Victim Xorie'Ayouni Jixktu, Pharmacist - Victim/Witness Secondary Witnesses: Ta'Akaix'Nangeren C'thur, Consular: Interviewed Wu'll Xorlaq and Sidney Taylor regarding the incident, got me up to speed on the incident, and provided evidence and testimony of other witnesses who were no longer on shift. Sidney Taylor, Lab Assistant: Witnessed part of the fight, transcript attached. Reem Faladay, Atmospheric Technician: Believed to had witnessed part of the fight, but had retired below decks. Chimalma Quintana, Security Officer: Assisted in the arrest of Wu'll Xorlaq and processed them. Time of Incident: Unknown Real Time: Before 0730 CDT, 8/31/23 Location of Incident: SCCV Horizon Medical Bay Nature of Incident: [ ] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [ ] - Neglect of Duty [ ] - Harassment [X] - Assault [ ] - Misconduct [X] - Other: Assault with a Deadly Weapon, Attempted Murder Overview of the Incident: Immediately after I came on shift, it was reported to me by the Federation Consular, Ta'akaix'Nangeren C'thur, that a serious security incident had occurred. An off-duty skrell by the name of Wu'll Xorlaq became involved with a knife fight with a First Responder, Korza Rokuraz, in the ship's medical bay. This resulted in both persons being seriously wounded. Additionally, one Xorie'Ayouni Jixktu was wounded by the pair as they attempted to break it up. Nangeren had interviewed Xorlaq and another witness and provided me transcripts. While Xorlaq was claiming self-defense, given the nature of the incident, and questionable reasoning for carrying a knife on them, I elected to place them under arrest on the charges of attempted murder and assault, as I was informed that both offenders in this case had caught Jixktu with their weapons, beyond stabbing each other several times. Rokuraz had fled down to the residential decks, but I received authorization to have them arrested and brought to the brig from the SCC Communications Officer. Additionally, I would recommend placing Xorlaq on suicide watch, as they stated in front of me and Officer Quintana that they would potentially harm themselves as a result of this incident. Submitted Evidence: Transcripts of Nangeren's interviews with Xorlaq and Sidney Taylor: Would you like to be personally interviewed?: [X] - Yes [ ] - No Did you report it to a Head of Staff or a superior? If so, who? If not, why?: A report was faxed to the nearest SCC Communications Post. Actions taken: Wu'll Xorlaq was placed under arrest on the charges of Attempted Murder and Assault. We received authorization to hold them indefinitely during our investigation, as well as apprehend Korza and do the same. Additional Notes: N/A
  3. Okay me and Loorey have taken a look at the logs and what's been posted here, and come to a decision. From what it appears to us, this round had a mess of communication, especially over the security radio. There does appear to have been sufficient reason for @Ricky_the_banshee and @DrPockets to suspect Johnson was up to something, and given the Head of Security ordered him to be detained and searched, which was reported to have been resisted, we don't see an issue with the suspicion. Unfortunately when communication breaks down during a chaotic round, sometimes people get the short end of the stick, but it's not necessarily any one persons fault, nor metagaming. As for the arresting/charges, it appears to have been another issue with the cluster of communication and round coming to an end. In summary, we don't think there was any targeted metagaming of any sort, the round was just chaotic and communication questionable. Additionally, if you do suspect there to be metagaming going on, please ahelp it in round. It is much more difficult to look into in this fashion. If there's nothing else, this will be locked and archived in 24 hours.
  4. Me and @Loorey will be handling this. First would like to get @Ricky_the_banshee and @DrPockets side of the story
  5. This has also always been the case. With few exceptions (ie. orders from Command, ling revival, uncontainable threat, etc.) security has always been expected to arrest someone after the immediate threat has subsided, even if they have just been shot at by said person
  6. You're missing the point of the rule, I believe, which is that we don't want people waltzing up to the downed mercs and one-tapping them or headgibbing them when they're downed. If you're exchanging lethal fire, nobody is expecting your goal to be to arrest them, it's to neutralize the threat. But once they're no longer a threat and are downed, they should be arrested should the circumstances allow it, not given a summary field execution. To pull a real-world example, police do not go up to people they've just shot and put one more in them for good measure, they handcuff them and begin rendering aid.
  7. I was involved as security. Gonna give my perspective. We had 0 clue that the merc team was there until an officer happened to jump on cameras/see a motion alarm (not quite sure which). Until that point, all of security was standing in the main ring chatting. Note that this was at, maybe, 0:25 of round time. By the time we arrived to Ops (probably 3 minutes later), every door had been bolted shut, sandbagged, and it was a position that was suicidal to assault. Before we could even reach out over common, it was reported that the mercs were heading upstairs and trying to leave. This is still before even a half hour has passed in the round. I bumped straight into you guys running from the Ops lift towards your shuttle. I misclicked (the first shot), but even then I think I didn't really have much choice but to fire as you guys ran away with all of our valuable items that we're supposed to protect. Had I simply stood there I imagine I would've been gunned down or everyone was going to keep running, since nobody on the merc team said a word to anyone prior. There was ample opportunity to interact with the crew, and especially security, when you were barricaded in an entrenched position in Ops. Instead, you and your team decided to just bounce and say nothing. Realistically had an officer not happened to see you guys on cameras, I don't think we would've ever run into you
  8. Goolie has been issued a Nanotrasen D-Notice

  9. Reporting Personnel: Logan Wright Job Title of Reporting Personnel: Head of Security Game ID: cpj-dbas Personnel Involved: Jonathan Baum, Hangar Technician - Offender Amelia Dresden, Physician - Witness Ana Roh'hi'tin, Investigator - Witness Faraday Ja'Hadem, Scientist - Witness Secondary Witnesses: N/A Time of Incident: 20:15 Real Time: 1515 CDT, August 15 Location of Incident: SCCV Horizon Medical and R&D Nature of Incident: [ ] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [ ] - Neglect of Duty [ ] - Harassment [ ] - Assault [X] - Misconduct [ ] - Other _____ (Place an x in the box that applies. If other, replace line and specify.) Overview of the Incident: It was reported to me by Doctor Dresden that Mr. Baum was spiking donk pockets with hyperzine and synaptizine, likely from the warehouse, and trying to sell them to people without disclosing this. These sales attempts occurred at both Medical and R&D. Following investigation, and testimony from the witnesses, we had enough evidence to charge him. Unfortunately, he went below decks early in the process, so we were not able to charge him. Submitted Evidence: Would you like to be personally interviewed?: [ ] - Yes [X] - No Did you report it to a Head of Staff or a superior? If so, who? If not, why?: There was no Captain or Ops Manager on duty while Baum was. Actions taken: Filed this report, as Baum retired to residential shortly after the investigation began Additional Notes: N/A
  10. Might could be done as a program where you just list, ala security warrants
  11. For what it's worth, when I VV'd the inhaler it contained space drug reagents, but yeah like you said, I only ended up banning you because you weren't responding and was looking for clarification on what was going on. I'll go ahead an unban you
  12. This isn't really a policy suggestion, so I've moved it to the main suggestion forum. Also I agree, why not
  13. Goolies can't handle my swag

  14. I can't see round stats, so I cannot speak to how many rounds you have or haven't played, but I've only recalled seeing you once or twice as a medborg. Yesterday, you were spoken to by another staff member regarding poor medical play, where it was noted that you were having difficulty in treating simple injuries. They advised you it might be best to play intern, and you took this as an insult, per them, and disregarded this. The very next round I took a ticket regarding the treatment of a Vaurca Bulwark. You had again showed slow response and difficulty in treating the toxin damage they had taken due to a gremorian bite (you did eventually treat it, though by this point they had serious organ issues), and then assisted the surgeon in surgery. While you did not remove the filter port from the Bulwark, if I recall the logs correctly you did then put them on oxygen, and the Bulwark quickly died. I spoke to you again, saying that you should play an intern role, which you again ignored. During this ticket I was told by other staff members online that you have been displaying poor medical play for some time, but I sympathized with Vaurca being a difficult species to treat, given they are different than everyone else, and decided to give you another chance to decide to play intern on your own. The very next round after that (third round in a row), I take an ahelp from the CMO, stating that you were not listening to them and having issues treating people. I had them send me screenshots over discord, which I'll post below. This is again a repeat of the same issue (poor and delayed treatment of injuries, to the point of causing people's health to get worse). You again did eventually inject inaprovaline, but the disregard for superior's orders is yet another issue on top of the poor medical play. The adverse effect you were having on people's rounds by giving them poor treatment, not taking advice from other players, and disregarding superiors is too much to allow you to continue playing as a physician without spending some time in a learner role. You were given two opportunities by myself and another staff member to elect to do so on your own after issues were brought to our attention, so I had little choice but to give you a job ban if you were not going to heed staff and do it yourself. If you'd been playing security like this, you would've been job banned already, that's the sort of adverse effect you were having on people's rounds as a physician.
  15. Ban appeals are for if you agree with your punishment, this reads to me like you wish to contest the action, in which case you should make a staff complaint. Three rounds in a row you had serious issues with your medical play, and were advised in the first two instances to play an intern role, which you flatly refused. As I said, you are free to appeal your jobban in a couple weeks after you've shown improvement, this is denied.
  16. What cybs said. I’m not a fan of this already, but armor at least needs to be touched as well. I feel like this is going to just increase ambushes where people are lightly armored (or not at all) and just cause people to get steam rolled and 1 shot
  17. I did not agree that G2s should be taken out or killed as soon as they step out of line. Specifically, I said that they are difficult to take down non-lethally, because they are a robot, and with armor are quite strong. Never did I agree that they should be instantly valid for killing (other than a clearly meme response of "true" to someone joking that they should be decap'd for jaywalking). My contribution was just that they are difficult to take down in armor. As I stated in the ticket, your opinion was not the issue, but rather the way in which you expressed it (calling other people's beliefs retarded, which is nothing but inflammatory). That kind of inflammatory statement is not something that's allowed, and directly violates the don't be a dick rule as well. I've not (anytime recently) seen other people use retarded in IC or OOC, but something going unnoticed previously by staff does not mean it's a free pass for others. EDIT: Game ID was coF-cLWM
  18. If you can read this message you cannot read

    1. Flpfs

      Flpfs

      Nralakk Quu-xi pu' Zii-pa 🤣

  19. Let me start at the top here: While crew wearing around softsuits aren't exactly common, it's also not something that is rare enough to warrant instant suspicion, beyond a "huh, weird." It being a red softsuit that's commonly used by antags does make it seem odd that you found it suspicious. At this point, all you have witnessed the person doing is trespassing, a very minor offense (one that people are fined for or can even simply be let off with a warning for). There isn't really an indication that this person is going to flee, or would flee when challenged. While calling for backup in and of itself isn't necessarily a problem, the fact that your reasoning is "they might run," despite having no IC justification that they may run, shows that you are taking what you know OOCly into account (them being an antag). As I stated earlier (and rooster as well), this would apply to the entire crew (or anyone in a voidsuit/softsuit). Anyone could be carrying a weapon, by this logic. By calling someone out as "possibly armed," with no actual IC indication that they are armed, you are both needlessly escalating the situation, and again using OOC knowledge that they are an antag, and could buy a weapon, to go after the person. At all points in this situation, you appear to be reaching for IC justification that just simply was not there, and this metagaming aligns with past behavior. You are claiming that, due to someone wearing a softsuit and trespassing behind the medical desk, that they may flee and/or be armed, and needed backup. This is not a logical conclusion from the IC information, especially given that the person hadn't given any indication they were doing anything beyond trespassing. It reeks of metagaming and validhunting behavior, and you were even spoken to shortly before this ban about using antag status to be a super security officer and kill other antags. Overall, I see no issue with the way this was handled by @Roostercat, and a job ban is absolutely justified given your history, and the incident in question. As rooster said, you are free to appeal the ban in a month, and I recommend taking the time in between now and then to show that you are familiar with the rules, and can be trusted to play security again in the future. If nobody has anything to say, this will be locked and archived in 24 hours.
  20. @Jaeger Brothers to make sure I have this right, you saw someone enter the area behind the front desk in medical and print medical records, while wearing a red suit. Because they had a red suit and a bag, you said that they may be armed and required backup. Could you explain why you came to this conclusion (both needing backup and why they may be armed). At first glance, your stated reason of "a bag/the suit can be used to conceal a weapon" is incredibly flimsy, and, as rooster said, would apply to nearly everyone on the ship. You have been spoken to previously (4 days ago) about metagaming a ling's revival ability. That, coupled with other notes/warnings regarding your security play that you have accumulated over a short period of time, would justify a job ban, even for something you have not previously been warned for. Players are expected to be familiar with the rules, and just because someone hasn't explicitly been talked to about X, but has been about Y and Z, doesn't mean that they cannot receive a ban if their overall behavior/play is not improving.
  21. I'll be taking this, should have something soon
  22. It’s a pretty well established precedent that if people are not comfortable with certain things along those lines, players are expected to not continue. While I personally do not find issue with those laws, some people do, and I personally don’t see the need for them if people are going to be made uncomfortable
  23. For the record, you were banned because I do not appreciate being threatened in a ticket with "I WILL FIND YOU," when I was otherwise just informing you about our rules regarding job hopping. This appeal is denied, you are free to re-appeal this ban in a month. If you disagree with my decision to ban you for this, you can make a staff complaint here: https://forums.aurorastation.org/forum/19-staff-complaints/
×
×
  • Create New...