Azande

Brutish accepted this willingly because he's essentially bored of Aurora and the character. I'm not even saying he should be punished - I'm just saying consistency is important.

I want to point out specifically here - the last time a Head Whitelistee decided to torture someone in interrogation, they got a ban and whitelist strip. This being one of our Old Guard, I believe MrIAmTool as Lysanuah Dilgan or somethingorother. May be worthy to note how far rule breaking is allowed to go in events in the future if you haven't been cleared for it by the event manager and other staff.

Basically, we sometimes have issues with players trying to start votes when admins have delayed round ends - whether trying to be funny, or legitimately joining in and being a twit and not knowing whats going on - it is both annoying for staff who have to deal with the vote starting, and also the present issue they're investigating. At round end, there is no need for there to be the ability to start votes - and if the round is delayed it means an admin is online and thus, restart votes aren't needed for if the server breaks (since they have restart commands in discord and in game). So yeah, make delay round end automatically lock the ability to start votes.

This isn't a Security or Command issue really. I've tried incredibly hard to get the community active in doing fun things, and nobody seems to bite. I've run blood drives, I've asked Engineering if they want to do an awesome build project the answer is always no (they have work to do), I've held Captain's Lunches, I've officiated weddings. You can all write super long paragraphs about the good old days, but the Aurora Community has changed considerably over the years, especially since Jackboot and I first arrived on the scene at our own discovery of this server - and people are NOT willing to create their own RP anymore (you can see this in the fact that when I first came here, extended was very frequent, you could not go a secret round or two without having extended after, and staff constantly encouraged this kind of thing. We had someone that created a Chaplain and church based on pizza and everyone including admins loved it. Nowadays, that's something staff would probably bwoink someone over. Our community as a whole has changed to super antag-centered. We're used to staff events killing all of the crew and leaving no one alive because of [mention]Alberyk[/mention] , so naturally during all events Security are on edge and keep people sequestered - it's their lore job. [mention]AmoryBlaine[/mention] comes to mind for getting a warning or soft-warning for literally manning the brig desk and NOT patrolling because that's 'not what officers are supposed to do'. Extra Note Head of Staff Whitelistees get unfairly punished for MAKING LITERALLY ANY FUCKING DECISION THAT DOES NOT FOLLOW REGULATIONS TO A TEE COMPLETELY. I was an IAA, I joined a revolution in a revolution round because the loyalists had made no effort to reasonably engage me - I got warned for it and told IAAs need to be loyal to the captain, even though I saw ICly and OOCly the Revs were much better for NT overall. Whitelistees are expected to be loyal to the Chain of Command, even if not implanted - you can see this in CMO Fernando Gonzales getting a warning for helping an antag team where the warning says 'you're expected to be loyal under duress'.' I boarded as a Captain the other shift to find that the RD and HoS had given Security's Armoury lawgivers, and the HoS and an Officer were testing two out. This was nice, interdepartmental RP. Then, the Officer stupidly did not check or try to sync their gun, which the RD had accidentally bound to themselves - and blew their arm off. The fun stopped there because the HoS decided he was going to arrest and charge the RD for gross negligence without even a word to them about it - I stepped in as Captain, brought them both in for some nice roleplay discussion, took them to the firing range to show why an officer shouldn't be given a lawgiver at all (1 month trained officers dont need explosive weapons), and cancelled the arrest because I didn't think the charge was fair or fitting. I promptly got an IR from [mention]CampinKiller[/mention] for trying to encourage literally any other method of resolution other than 15-20 minutes in a time out box on station.

NO. Do not excuse lazy antags by removing the AI - encourage or empower antags to get by the AI more. We should not become an antag hugbox.

[mention]HouseOfSynth[/mention] did you forget me friend.

That's pretty bad faith. Using a technicality of being visitor to lie to CCIA to avoid owning up to the mean spirited and pretty unnecessary act of burning evidence in front of someone. There's not more I think I have to say. Hopefully administration can see why this is behaving in bad faith. I'm not involved, so [mention]Garnascus[/mention] is welcome to remove this - but speaking as a former CCIA, our policy at the time was that those we interviewed were absolutely welcome to lie; but if this lie was discovered it would result in a very very serious punishment. Because CCIA's work is IC, characters are not obligated to be honest or provide everything they know as they would in a character complaint investigation. Characters simply need to deal with the consequences of their lying if its discovered. This is not an opinion on this complaint or either party in it, but just a note from an individual that was once CCIA and has had people lie about them in IRs.

Why are we even talking about air pumps. Gasses do nothing to slimes, unless you are planning on revamping Xenobiology mechanics as well Burger, I'd say abandon the gas shit entirely.

Seems silly and basic, not hall of fame worthy.

One example I immediately thought of is a journalist helping hostile forces by leaking security information out into the public, for example. Corporate secrets is another. Exactly, so make it a mechanical block on any alert pre-red. Command has no reason to D-Notice a freelancer before code red unless they're chucklefucking, in which case A-Help.

Juani has informed me that [mention]HouseOfSynth[/mention] applied this ban, through MattAtlas as trials cannot apply bans.

Dropping this. [mention]Garnascus[/mention]

BYOND Key: XanderDox Total Ban Length: Permanent Security Job ban Banning staff member's Key: No idea, they did not reach out to me and I cannot recall who the admin I dealt with in round was. Reason of Ban: *Note, this is MY opinion on why, as I was not given a clear ban reason as I was not online or reached out to by the banning individual to my recollection.* I assaulted a vaurca, reported them for being memey/powergamey in combat, then went to cryo or died and ghosted and left my computer. I came back, saw no messages from staff because I was away from my computer, and promptly exited space. It turned out a staff member had messaged me to ask to talk about MY conduct as sec going after the vaurca, and so a secban was applied by whoever this was after the fact. A moderator reached out to me to tell me the ban was applied, but that they were not the banning member nor did they provide a clear reason. I don't remember their discord or ckey either. Reason for Appeal: While I don't fully agree with the ban, I recognize that I most likely was in the wrong in the situation as I was disregarding my safety to try to fight through a spam of viscerators. The vaurcae was in a closet, and was activated three viscerator grenades from inside, keeping them safe but ensuring I was getting attacked. Instead of retreating, I pushed forwards to get them and fight the viscerators. I enjoy Security play a lot, and wish to clear up this misunderstanding and start playing the department again.

that sounds good.

Journalists cannot contact CCIA. Journalists cannot file IRs about command abuse of D-Notice powers if the news being reported was related to antags, which is 90% of D-Noticed content.

I'm going to echo this. I was not banned from promotion. Klaus has served the company for many years, and that is the only incident he has on record. I am not retiring Klaus (I am secbanned) because I enjoy him immensely as a character.

I didn't even know the Project forum was a new project, I've literally just come back after being away for a month and didn't know the rules there were more serious than in other locations. This is just unfair.

Wrong. Dick Captains cannot get canned by the CCIA if the news is in regards to antags - which is most of the news that would ever get D-Noticed. Wrong. CCIA almost always side with Captains, even if they are minorly in the wrong. Please make it mechanical.

If you do this, understand the following: - Security will not care at all if you take further hostages - The above means Security will literally fuck you up regardless of how many people you have hostage, because you are liable to kill them already risking their death to get you is generally seen as collateral - Everyone will operate under the belief you are a hostage-killer, and EVERYONE you try to take hostage will fight back violently, because they risk death just by being caught by you

Can we stop nerfing the telebaton? I have literally batonned a wizard in flowing robes six times in a row and had them shrug it off. It's just become a waste of space.

Just order protohumans and get some RP with cargo.

Do not add the second feature, it encourages bad roleplay if not outright facilitates it. We already have trauma curing tools that can be used to complete roleplay.

I didn't even realize this was an issue. Must have been an oversight as the library check-out system itself is old as balls.

I still wish to have this warning removed because I think what I said did not warrant a warning. Glad to hear that there is no auto-ban system, maybe I was confusing it with Discord?

I've literally just come back from a month hiatus from active-play on the Aurora, my dad is literally in the hospital trying not to die of liver failure. I just want to be in this community without having my actions constantly nitpicked and watched with a hawkeye, is that really so much to ask? What was posted in the thread just did not warrant a warning in the system.