Jump to content

CampinKiller

Primary Administrators
  • Posts

    520
  • Joined

  • Last visited

Everything posted by CampinKiller

  1. He did? No, but are we just going to wait around until he does?
  2. Reporting Personnel: Marc Price Rank of Reporting Personnel: Head of Security Personnel Involved: John Devereux (Detective), Sslazhir Yinzr (Officer), Ana Roh'hi'tin (Officer), Aersari Yinzr (Warden), Mordred Artorius (Cadet), Kellie Hastings (Executive Assistant), Robin Calanthe (Detective), Ro'grif Sodead (Assistant) Time of Incident: Approx. 8:20 Tau Ceti Standard Time Real time: 12MAR, approx. 2200 CST Location of Incident: Holodeck, Brig Nature of Incident: []Workplace Hazard []Accident/Injury []Destruction of Property []Neglect of Duty []Harassment []Assault [X]Misconduct [X]Murder Overview of the Incident: Ro'grif Sodead failed to utilize proper Holodeck equipment in a fight with Cadet Mordred Artorius, and then used a blunt force object to kill them after said fight. Their spouse, Detective Calanthe, then attempted to cover up the death by hiding the cadet's body, but he was spotted by the station AI. After being apprehended, Calanthe confessed, and implicated his wife, Sodead, who also later confessed. Calanthe then, during his holding until transfer, attempted to kill himself twice, resulting in massive Medical resources being expended. His wife, Sodead, also tried to kill herself, but did not cause as much injury. Did you report it to a Head of Staff or IAA? If so, who?: No. Additional notes: N/A
  3. Some assistant called for Security over comms, reporting,"The Chef has been taken into Mining." We don't know if that meant being kidnapped, or just being taken there to see some things. Regardless, we couldn't raise them or the QM, and the AI wasn't responding. I called for two officers, and went myself to provide access. We then went onto the Mining Outpost, and still couldn't get anyone to respond, and so we had to break into the port section of it. We then simply searched the area, and then opened the door to the dorm room. Our equipment was the standard officer equipment, plus my energy gun as the HoS. All 3 of us were wearing our armored vests, but that's normal for most officers. As to what Pootis said, taking into account what Delta posted, I find that venting it multiple times, the first being before anyone could say a word, to be chucklefuckery. And nobody was armed with a laser rifle, the only person armed with a gun was myself, and the HoS is always armed. Also, making a gnarly scene makes no sense. You'd killed everyone who came to the Outpost, had vented it in multiple places, and then single out two bodies to decapitate, both of which happen to be the only Security who responded and could be a threat if cloned, and cut them into pieces for good measure.
  4. BYOND Key: CampinKiller Player Byond Key: PootisManiac Staff involved: Garnascus Reason for complaint: Atmos griefing, Powergaming Approximate Date/Time: March 11, approx. 1900 CST So, PootisManiac, aka Walter Bash, was a vampire. Security received a report about the Chef missing heading into Cargo. Myself and two officers go to investigate the report, and head onto the Mining Outpost. We eventually get to the outpost dorms, and open the door to one of the rooms. Inside, we see Walter Bash and the Chef, and before we even say a word, Bash vents the room with an RCD they printed off an autolathe. They then proceed to vent the outpost 3 more times in order to kill everyone inside of it, including medical staff that responded to the vitals loss. This was ahelped and I was informed that it's not atmos grief to freely vent areas, nor was it ganking to suddenly kill two Security members who weren't even there to arrest anyone, but looking for the Chef, as well as Medical staff who went to help the Security forces. Later in the round, Bash then decapitates my body, and Nia Snyder's body, for the express reason of preventing us from being cloned. In fact, he didn't just decapitate them, he dismembered them completely. There was no reason to do this other than to prevent cloning, which seems to me to be blatantly over the line of what is acceptable, especially after murderboning said people minutes prior.
  5. You missed my point entirely … but it’s ok don’t worry, no one is surprised That's basically what your point boiled down to. I like this change, considering how conservative and traditional Tajarans are. Not that it matters though, considering that the majority of Tajarans who are straight will be the Super Social Justice Warrior type and love all Tajarans, lore be damned in favor of edginess and not hurting people's feelings.
  6. So, anything? -cries tears of loneliness-
  7. Uh, what? Aurora security isn't mallcops. That's been well established for some time. They are a paramilitary corporate security force. Most RL corporate security forces at a research facility are armed with lethal weapons, because it's better safe than sorry. I'd support giving officers energy pistols.
  8. Appearance - similar to Seon. Please no.
  9. The only problem with that is that when JB said it was canon, Gollee immediately declared it non-canon, per the first post.
  10. Holy necro, batman.
  11. I was just referring back to Standard Operating Procedure, but if that's not valid, then I'll file that away.
  12. Not an admin, but it's pretty clearly spelled out in the SOP that searches are allowed in code blue, period. Not "Captains may override this," not "You must get permission," but "You can search anyone and anything."
  13. People need to start acting like Tajarans are actually distrusted and viewed as terrorists IC. It seems most of the station is just SJWs, and if you even mention Tajaran terrorism, or your dislike for them, you get shouted down, threatened, and even attacked by them. I like the lore for them, but people need to actually ACT like its the lore IC. Also, glass Adhomai.
  14. CampinKiller

    RD Antags

    Oh, yes, I was HoS that round. The Vaurca and I were Head Loyalists. I ordered the entire station searched for dissidents, and also to try and incite the crew to mutiny (since there are no auto messages to do it anymore). The Vaurca did that to escalate it further, and hopefully start resistance.
  15. Glass Adhomai.
  16. Right. Since he was talked to and knows that it's an issue now, then I'm fine with closing it.
  17. BYOND Key: CampinKiller Staff BYOND Key: Killerhurtz, TishinaStalker (?, not sure if Tish was part of the decision, but they were the admin on at the time) Reason for complaint: Allowing blatant gank and greentexting from the AI on a malf round, overriding transfer votes for the 'roleplay' Evidence/logs/etc: I don't have specific logs, I'm on a different computer at the time of writing. Regardless, let me give the gist of the round. It was malf, and the AI was doing stealthmalf/greentexting, and just hacking APCs and not providing any meaningful roleplay to the crew. Their only interactions with the crew at large were faking two Command Announcements. One was regarding the transfer shuttle being disabled, and I don't recall the other. Borgs were ordered to act normally. The AI had no interaction with the crew besides normal functions and the two mentioned announcements until after the crew transfer was voted for at the 2 hour mark. The shuttle was called because nothing was happening, and passed by a vote of like 20-4. The staff online at the time inexplicably allowed the AI to recall the voted for shuttle. The reasoning Killerhurtz provided was because the AI was doing things, but being sneaky about it (read: greentexting/stealthmalfing), and when everything hit the fan "it would be awesome." Other ghosts who'd been ghosted for a majority of the round noted how the AI had literally not done anything to that point. After recalling the shuttle, the AI told the borgs to kill Yinzr, for some arbitrary reason. Yinzr, Ro'hin'tin, and other officers were armed because of a massive carp invasion trigged by random event, but nobody suspected the AI of any malfunctions. The borgs then proceeded to walk up in Medical where Yinzr was being treated and open fire on the group of people without a word, killing Yinzr, and seriously injuring Alex Toner, Skylar Briggs, and Ro'hin'tin. For some reason this was not considered gank, and was the 'awesome roleplay' the staff promised. Shortly after this, the AI vented its core and rushed the self-destruct mechanism, and at one point considered venting the entire station. At the 2:30 mark, a crew transfer passes again, and is again allowed to be recalled by staff. The fact that this blatant gank and greentexting was allowed, and even promoted as "awesome" by staff is laughable. If the new standard for malf AI is AIs that do nothing until suddenly ordering people to be killed, then the gamemode needs to be axed. Additional remarks: N/A
  18. Simple. Reduce the number of them. There are so many random events that fuck the station up, round after round. I've seen two blobs in two hours before. Hordes of space carp that come in and breach everything. Spiders every other round. Can we tone down on the amount of random shit that happens?
  19. Except some of these aggressive actions have happened on extended rounds, thereby making them canon, so it's not like NT doesn't know. Also, saying that it isn't canon so it shouldn't be punished makes no sense. If Security starts executing people regularly, but only on non-extended rounds, then I guess we can't punish those people either.
  20. It also wouldn't be hard to say "If we can't trust these damn insectoids to manage crew, what makes us thing we can trust them to make sure our space station's engine doesn't EXPLODE/research WEAPONS and BOMBS/perform SURGERY on living crewmembers/cook us FOOD!!!" This logic could've applied to any race when we had a lot more restrictive Head of Staff roles, not too long ago. But we never did that. Why in God's name would we start now? Because of a handful of rubbish Vaurca players? I think not. You exaggerate greatly. There's a major difference in not trusting a group of aliens who are acting retardedly and aggressively in Security roles, than ones who calmly contribute to research, or cook food.
  21. Yeah, no corruption, please. Roleplayed corruption is fine, but just brigging people for the lulz isn't. Also, for the people that say being brigged isn't fun, it's because people who get brigged don't want to make it fun. 9/10 times a non-ling antag (or non-antag) is brigged, they simply bitch and moan, refuse to cooperate, yell over comms for a lawyer, yell about how they're being abused, and if they end up in permabrig, simply go to cryo and ghost, then proceed to moan about shitcurity in deadchat. The 10% who do roleplay with security, instead of simply stopping and refusing to once in the Brig, actually seem to have an enjoyable experience, unless a shit officer decides to ignore their roleplay.
  22. ALERT! CODE DELTA REACHED!
  23. Well, it's not like not having them means the HoS/Captain still won't break regs to act in the interests of NanoTrasen without an implant. In fact, all the implant does from an IC perspective is make the responsibility fall on NanoTrasen, considering they're the ones who've implanted this pseudo-mind control device in your brain, and had it affect you in such a way. Not to mention, it removes the HoS/Captain from any possible antag roleplay regarding being converted to a cultist/enthralled. Imagine if the Captain was converted and began attempting to force the people of the station to undergo conversion? That would be pretty damn interesting, IMO.
  24. You want to talk player freedom, how about removing loyalty implants? You know, one of the most RP-stifling things in the game, which were made to prevent heads from being lol-flashed during rev.
×
×
  • Create New...