Jump to content

Dbrg

Members
  • Posts

    11
  • Joined

  • Last visited

1 Follower

Linked Accounts

  • Byond CKey
    doomberg

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Dbrg's Achievements

Barman

Barman (3/37)

  1. I am absolutely against the "hardcore-ification" of the rules and standards of conduct we already have to the point where I'm not permitted an OOC chat/joke with someone without sliding into their DMs. I don't think there's any need for a blanket ban on LOOC usage that doesn't immediately further roleplay. I'd understand a rule restricting LOOC usage in the middle of, say, hostage situations, combat, very crowded areas, etc,, but that's the extent of it. I think that's more than enough to tackle the issues you've presented. More, and you're effectively restricting people to communicating off-server and on the forums, which I think is a net loss to the community as a whole.
  2. I told you I hate involving myself in command whitelist applications, but this has had a slow start, so here we go. I think you're cool headed enough OOCly to handle the responsibility. I know you're not a shitter. Moreover, your wardening so far shows me that Mens' lube boy silliness is an IC trait that doesn't automatically extend to any new characters you make. +1 for you.
  3. Reporting Personnel: IRU-Zenith Job Title of Reporting Personnel: Detective (Idris) Game ID: b7X-chCF Personnel Involved: - IRU-Sentiment, Forensic Technician (Idris): Witness - Stella Palmero, Warden: Witness - Valeria Zhao, Warden: Witness - Patrick Swabey, Security Officer: Offender Secondary Witnesses: N/A Time of Incident: Real Time: 1700GMT 07/04/20 (approx.) Location of Incident: Various Nature of Incident: [ ] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [x] - Neglect of Duty [ ] - Harassment [ ] - Assault [ ] - Misconduct [ ] - Other _____ (Place an x in the box that applies. If other, replace line and specify.) Overview of the Incident: Officer Swabey, despite seeming quite free during the entire shift, was completely absent from his post. We were in fact astonished to see that he was conscious and entirely idle at the kitchen table after being forced to handle multiple security incidents in his stead. Earlier during the shift, an assistant, after dragging a fuel tank through the station, prompting concern from the crew, broke into Engineering and manufactured a sword. Officer Swabey was nowhere to be seen, so warden Zhao was forced to arrest the suspect herself. In addition, he completely failed to respond to a carp migration which resulted in breaches, forcing both myself and unit Sentiment (both investigative personnel) to resolve the matter. Following these incidents, a chemist began attacking coworkers in the medical bay with a glass shard. Amidst calls for help from the crew, Mr. Swabey was nowhere to be seen, prompting myself and unit Sentiment to intervene and arrest him, with warden Palmero's eventual assistance. Naturally, we did not have the appropriate equipment and sustained fairly serious damage in the process. Warden Valeria Zhao witnessed the first two incidents and Swabey's absence, while warden Stella Palmero witnessed the latter incident. I believe both would happily confirm his utterly unacceptable performance. When we confronted Mr. Swabey at the kitchen counter, he claimed that he had heard none of the many calls for help and radio reports. I do not believe he is fit for his duties in any capacity. Submitted Evidence: N/A Did you report it to a Head of Staff or a superior? If so, who? If not, why?: This was not reported to command, as we were seeking repairs at the time and the station underwent a crew transfer immediately after. We furthermore had no command staff until a short time before the shift's end. Actions taken: Myself, unit Sentiment, and the wardens verbally chastised officer Swabey for his poor performance, to no avail. Additional Notes:
  4. I would imagine that, if people don't want back-to-back extended(/merc/whatever), they'll just not vote for it. It's not like only specific people get voting privileges. They very literally choose extended themselves in that case, however. I'd assume (barring staff) they're not compulsive masochists. If you believe that most of the gamemode voting is done by a minority of players, for instance, then I'd say the solution is to make the voting system more obvious/friendly, rather than adding yet more restrictions. I see no value in forcing gamemodes, ever, outside of hosting events. Summarizing: From my point of view, the only valid reason for such a measure is if you believe the majority of players are being forced into gamemodes they don't want to play. Assuming that premise is true, restricting players from voting for the gamemode they want seems entirely nonsensical.
  5. I was the captain. I can personally confirm most of what both Sue and Nienna have posted. From my perspective, this is how the round unfolded. Shortly after joining, I learned of three major issues (order largely forgotten): Security seems to have credible intel that Ethernet was responsible for a bomb threat, as per the radio chatter and search effort (see Nienna's response for why) There is an issue with people actively biting officers I was told Locke was being blackmailed and ordered to kill Ana, after being handed a revolver For context, Dawkins was the only command staff member at the time. Since I had a seemingly competent security team, I left issue number two to them, with their assent, then focused on dealing with investigative's problem. I made an initial judgement call to detain Ethernet for questioning, based on the following items of evidence: A photo of Ethernet in Locke's office, offering either credits or a gun (I forget), as taken and provided by Ana The revolver in question, offered by Locke Security's pre-existing suspicions that Ethernet was dangerous and possibly orchestrating a bombing At this time, I took the revolver from Locke to ensure he doesn't do anything stupid. I was then informed that Likho and Aubrey were in tech storage, watching my office. We raided tech storage, searched and questioned them, and they indicated that they were also in danger, which was consistent with Locke and Ana's testimony. The security officers then said something about "dealing with bloodsuckers", and, in light of the reported bites, panicked yelling via the security radio, and that comment, I decided to allow investigative to handle Ethernet instead. For clarity, they were at no point under any orders to destroy Ethernet. I accepted that risk because security had its hands full, Ethernet was already suspected of planning to bomb something (see Likho's work), and we were pressed for time: you do not want a bomb on a transfer shuttle. As for the IC motivation behind Dawkins' inaction upon realizing that Locke did a fucky-wuck, a few more dreaded bullet points: In the end, Ethernet is, at best, a self-owned piece of equipment. To directly cite the wiki's lore section: "Free IPCs (in this case, those granted citizenship) are held to the same legal expectations as Humans in regards to their positronic - which is, in turn, given responsibility and ownership of the chassis which houses it. They, however, are subject to dismantlement over infractions which Humans would normally serve minor sentences over. Free IPCs are rarely given trials.". This might refer to off-station crimes, but it should give you an idea of the importance of an IPC's existence contrasted with a human's. All security responders on scene clearly intended to cover the matter up, and pragmatically speaking, that makes it easier to feign ignorance with no personal consequences. Loyalty implants are no longer a thing. Finally, a simple calculation: the lives and careers of a bunch of security people you know and trust will naturally have more weight than justice for a dead robot terrorist. That some characters are more readily trusted than others based on prior IC interactions is the nature of a heavy roleplay server. I would urge you to separate how the execution/murder was carried out (in terms of potential gankiness) from how everything else was handled. I understand that you're frustrated, but I think resorting to immediate accusations of meta-cliquing does not strengthen your case, nor does it go over particularly well. Edit: To add a further note on meta-cliquing, I have never OOCly talked to Locke's player, and I exchange about two phrases with Sue once in a blue moon. Edit #2: Questions 1, 2, 3, 4 are irrelevant in light of an ongoing emergency. Contain first, then look for the non-critical info. Allies could be relevant, but we get to them quickest by getting to you, your PDA, your belongings. Question 5: Please refer to the second list, up above.
  6. Being cuffed while typing is pretty shitty, yes. On the other hand, if I've just tazed the Unabomber to the ground and they spam resist being cuffed, I'm going to have to telebaton them until they stop moving one way or the other, which is as healthy for my command whitelist as it is for their enjoyment of the round. If we must have this, then bypassing the requirement of an aggressive grab if someone has just been floored by active stun baton strikes/tazer shots might be a nice middle ground and, in my view, makes more sense for non-hulk characters.
  7. Can't comment (much) on the lore aspects, but I can say I've had good experiences with them, both in the sense of RP quality and general conduct on the server. On top of that, the application seems competently put together to me. +1, lizard away.
  8. Reporting Personnel: Avery Dawkins Job Title of Reporting Personnel: Captain Game ID: b4s-cDv2 Personnel Involved: (Name, Job Title: Offender/Witness/Other. Only three witnesses other than yourself permitted, the rest go to secondary witnesses. Victims count as witnesses) - Victoria Weiss, Surgeon (Offender) - Melissa Al-Mifsud, Chief Medical Officer (Witness) - Nriel Taas'Klin, Visitor (Witness) Secondary Witnesses: (Name, Job Title: Short description of what they witnessed) N/A Time of Incident: Real Time: Just before 8 PM GMT +1, 29/11/2019 Location of Incident: Transfer shuttle, followed by the Odin transfer docking area Nature of Incident: [ ] - Workplace Hazard [ ] - Accident/Injury [ ] - Destruction of Property [ ] - Neglect of Duty [ ] - Harassment [ ] - Assault [ ] - Misconduct [x] - Other: Detection of untagged shell Overview of the Incident: During a routine crew transfer, visitor Nriel Taas'Klin, a skrell, informed me via PDA that they were unable to detect a psionic signature from surgeon Weiss. They stated that this is only ever the case for synthetics, but no tag was present on Dr. Weiss. I reported this to miss Al-Mifsud, and we confronted doctor Weiss with this information after passing through the Odin checkpoint, also notifying Odin security (who were not present at the time). Doctor Weiss was able to escape the area before the responders arrived, which makes her guilt, in my view, quite clear. Her location is currently unknown. Did you report it to a Head of Department or IAA? If so, who?: Reported to Melissa Al-Mifsud, the offender's direct supervisor. Actions taken: We informed Odin security forces and attempted to prevent the offender from leaving the area. Additional Notes: OOC: The round ended as we were trying to confront them and this was a sort of saved by the bell situation. Borya (Al-Mifsud) spoke to the player in question, who said they preferred the outcome to be their character giving us the slip. I have no objections personally.
  9. Sentiment is great and this is both fitting and likely to lead to interesting roleplay. Doesn't stretch suspension of disbelief in any way, either. I will +1 very hard.
  10. I see no reason to take away maintenance access from a department clearly intended for emergency response. Is it reasonable to remove the paramedic's maintenance access next in order to force medical to interact with engineering more? Moreover, I'm not sure "ENGINEER RESEARCH MAINT NOW" is a very satisfying kind of inclusion. If security checking maintenance at round start for "dangerous items" is seen as a major problem by many people, then there are solutions to it that don't involve mechanical changes, such as an OOC ruling or an IC policy against it. Finally, I think you overestimate security's ability to consistently find antags in maintenance quickly. It's big, messy, and dark. There are multiple levels, each with its own mess of tunnels. When the antag doesn't make a campfire by the crusher, locating them becomes a lot more difficult. Overall, I think this is both unnecessary and largely detrimental. There is little to no added roleplay value in forcing security to scream for engineering/command/paramedics to let them into maintenance. The interaction you envision will be brief, painful, and probably in all capitals. The antags already have plenty of room to work with multiple levels of tunnels, they can ambush responders, so on. I see no added value in this proposal.
  11. I play IRU-Zenith, the arresting officer. Some necessary clarification: If memory serves, in responding to the bwoink, I got the murder count wrong. As you said, the person you dismembered in maintenance did survive. My bad: multitasking bwoink + 3-4 separate antags is a bit like having half a brain and a concussion. I had assumed that both of the officers you attacked were dead, since Mens had no pulse and the other one was carted away by medical, never to be heard from again. After I asked Mens' player, they clarified that the other officer also survived, but ghosted. Hence, at the time, you were guilty of two counts of attempted murder, and one count of actual murder. I believe the rest of the information I provided is factually accurate. My guess is that the concern is with your conduct after the fact, not necessarily with the number of people you killed. However, since the universe is merciful, I don't handle complaints/appeals, so I'll leave the interpretation for the staff members involved. Good luck!
×
×
  • Create New...