sonicgotnuked

We need something discussed on the Wiki that highlights code Delta for AIs. Something they specifically follow. Code Delta As the station intelligence, you know about the station fail safe. Unless otherwise and clearly told by the station captain, you must not make any reference to the failsafe. On the activation of Code Delta, all orders are prioritized to the captain and central command. Voted captains do not have authority to access or make judgement about the failsafe unless otherwise authorized by central command. In the case of a code Delta activation, the failsafe must be kept at the highest security including a full lockdown unless otherwise ordered by the spawned in captain and central command. This is open to discussion and review.

Hello! For your application to be reviewed, please update your unban request to the correct format found here: Thank you!

You can already print them in RnD if you have illegal tech.

Unless there is a good reason, the only place a captain SHOULD place the spare is either on themselves or in their safe. Someplace dumb like the toilet would be rather bwoinkable unless its for good reason. It would not be fun to be forced to interact with every single door. It sometimes takes three seconds for security to shoot you up regardless. Plus people generally don't even give you their ID if you simply ask it. "Why should I give you my ID? It is working fine" Hacking doors takes time and will be pretty noticeable when you're standing by the vault for a minute with a multi-tool in hand for example. Plus... hacking the AI with no access and not science just sounds like a bad time in general. Unless your ninja because cloak is a powerful meme. Anyway, I support not removing it. People need it for legit reasons when there is no command or there is only one command person. I do support moving it to an emergency location such as the bunker. Maybe make it a separate room with turrets and motion sensors that have general command access. High danger high reward. Command is dead? You better be making a plan to get that spare.

While I can see some moments as an acceptation. These could be ahelped Otherwise, I agree.

I do not agree with limiting merc to 2 or 1 people. RNG just picks sec people sometimes. If RNG wants to pick 4/5 security, then that is something. It doesn't happen every round. It happens because the player base likes to ready up as security.

It always really starts with one person forcing the antag into doing an action that in turn starts a spiral. For example "Security! There's a dude threatening to kill me if I speak in comms!" Of course, you kill them. Security in turn has their valids to kill you. So you kill them. Other crew search for valids to attack you. You kill them. There has been rounds I've played where normal everyday crewmembers decide they're the best loyal NT people and YOU HAVE to be stopped. Other times, it's the AI.

I before hand asked Cnyam about it. This is something that you did do despite us telling you to make a staff complaint if you feel like the situation needs to be evaluated. Regardless, someone will take a look and a discussion will probably be made to determine if the ruling between me and Cnyam was correct. One of your dominates being ignored was handled by me previously. I contacted the player. While turning people into vampires can be rewarding, you are trading off the ability to control them from what I see. I'm sure the embrace power does come with information warning that they don't have to listen to you. While making them another dangerous force, you trade off part of your control. There is nothing stopping them from turning around and attacking you due to their hunger. Summer went through the appropriate channels and asked us. I'm open to being wrong about this, but I do agree with Cnyam. I rest my opinion as well on the matter.

https://github.com/Aurorastation/Aurora.3/pull/7350 Basically on the Do not interact law, it adds an exception to hive bots. Hive bots I guess are considered 'Synthetic beings' It would make sense to allow drones to fight hive bots.

Keep in mind that I did put a thing into the traitor code for borgos to gain their overclock. I feel like this somewhat made them better. But yeah, antag station bound is weak. It wouldn't be that hard to have code red + overclock allow combat. The procs are already around.

While it is possible for malf to give its borg the combat module. It requires it to set the code to delta via the elite encryption hack. Yeah, let's still give this an option to the malf, but it would have a combat specific module it can give. I would also like to see traitor borgs have this ability too if possible because the removal of the sec borg made traitor borgs weak as hell. (Which I somewhat fixed a little by allowing them overclock)

I never really saw this either. The most that this may come down is, like other people have said, if the player is trying to argue after the ruling is placed down. Plus generally I put along the lines "I am going to close this ticket now" and that's the end of it.

Alright, that's understandable. Thanks for clarifying. I banned due to your notes previously listing issues. I'll get someone to unban you.

Wow a topic I actually agree with. Memes aside, yeah, this really does put a good standpoint. I myself am guilty of not giving enough 'choices' Perhaps the most recent example was a raider team I was apart of. We bamboozled security, welded them in an elevator, and stole the armory. Later on, I found out my other raider buddies locked down the cargo account and all of security died due to another raider RCDing a turf away. To be fair, my enjoyment of the round was going down as well. It's not fun to not have opposition. I really do like this point of view. At the end of the day, the 'choices' are limited by mechanics. My frustration with cult (my most hated gamemode) is that there is literally zero other options. It practically mechanically forces you to spread by converting. While Ling, I feel have some good options, is a bit guilty with this as well. This is why I enjoy malfunction so much to be honest because CC announcements are a rather powerful tool and you get endless supplies of them.

If the AI is giving you shit, kill it. Place an emmiter in the command bunker and laugh while it fries in its core. Regardless, this entire thread boils down into one thing: whitelist the role. Malf is a good gamemode. Please don't remove it

Do not remove AI Yes, there have been moments where I fumed with enough salt to make my dinner run white. Yes, there have been times I threw my hands up in the air and screamed "Fuck that role!" It doesn't need to be removed. There have been other efforts over the years suggesting a whitelist. We should whitelist it, not remove it. Like it or not, I just learned to not do shit in front of cameras that can take three seconds to smash. Malfunction is a great gamemode if done properly. It's one of my favorites to play because of the freedom you have to run things like sudo events. My most recent malf, I involved practically the entire crew during deadhour with "there are things outside wanting in the airlocks" I've seen some really good malf rounds. While there sometimes may be shit malfs, the good ones are in my memory. Don't remove this. In general, there are some good AIs who sit in their core and look pretty playing sudoku when they're not called upon instead of actively hunting for bad people. If it's such of a problem, whitelist it and lock it behind command.

I may just readd what the wiki says ODing bicard does when the temp is above 170k. If it takes around 20 minutes in an OD state, I may forget about touching it. I still stand by my proposal to Peridaxon and Alkysine. Locking a recipe behind phoron salts was just a discussion point.

I got two both with OOC perspective and IC perspective. Both technically allowed, by barely scraped by. OOCly, I screwed up a team of raiders with a shock drone. Don't do this. This is bad (and one of the reasons why I agreed to a nerf in general) https://gyazo.com/f9fcc5ac85d604b224d877827aae48e2 ICly, as traitor RD, I ran a gaming experiment and had Fernando play Orion Trail Realism addition. It gibbed him, I got surrounded by sec, but I had paperwork at my disposal to eventually talk myself out of it.

https://github.com/Aurorastation/Aurora.3/pull/7165 From what I understand, the main issue people have is the nerf to Bicardine and removing its Internal Bleeding while painkillers might be able to counter Peridaxon pain. Bicardine could still cure internal bleeding, but it will be set to your body temp being above 170 k to work. (Which is still quoted in the wiki, but not reflected in the code) Peridaxon will send pain and give some weakness based on the dosage. (10 units = 10 percent chance to trigger. 9 units = 9 percent, etc) Alkysine I may also make cause a chance for some brain effects like confusion or hallucinations based on the dosage. Tramadol and Oxycodon addiction chances based on dosage. Tramadol would be a lower chance. Oxycodon would be a higher chance. While I heavily dislike IB counters and the lack of severity between food and bicaridine, it's understandable there may still need to be options. Peridaxon is a simple 2 click drug for organ failure. While I understand it causes issues when people pop lungs, you'll be on pain management as well.

I decided to keep everything else in mind, but not act upon any of the previous actions during the round because it was extremely convoluted and it wouldn't be fair for you if I decided to rule based on speculation from frustration expressed by other players. You may have been in the wrong regarding interaction prior. It may of been fair. I couldn't get enough details to really understand what was going on before then. I could only act on information gathered because I wasn't actively observing the conflict. From what I've gathered, the Diona blatantly told that 'they would kill them' if security attempted to do anything. I also previously asked if it was a hostage situation, which was acknowledged to be correct. Reviewing the information, the hostage did mention for security to back away but sadly it seemed to be too late due to the grenade already being primed. Inside the logs, the Unathi did claim in LOOC they were not AFK as well. While I understand the misunderstanding that may come with the Diona trying to get into tighter spaces, the added detail that I've not gotten during the initial contact and decision process does help Brutish's case in regards to his actions being valid or not. Thank you for taking the time to screenshot. It gave me a greater context of the round and the situation. I do not think a ban is warranted in this case and I'll go ahead and have the ban removed. I'm sorry for the inconvenience it caused.

I was speaking in general terms.