sonicgotnuked

The lower chance for certain jobs to become antag was reverted specifically due to the reasons stated above. The game would be forced to choose between a few game modes with the others being a lot rarer.

I'll let someone delve into the logs.

The round ID is b4B-abP9 I was able to piece together this series of events during my investigation when I was contacting people. The station goes into code delta for 2 seconds due to round progression that the away team was not apart of. There is a disagreement among the group. People want to stay. The RD wants to stay. I'm told there was a vote. During this vote, before VUX's character made their thoughts known, they straight force feed the RD the parapen toxin. There was no further argument. It appeared the RD was trying to explain and VUX decided to result to potential murder. This is poor escalation. VUX made it clear to me that they understood what the toxin was due to me questioning why an engineer would know what it is, and poison people with it. They told me prior that they didn't know that a random engineer does not know what every chemical does before piecing together that it was a scary name so it naturally has to be force fed to the RD over a disagreement that just started. ICly, parapen toxin is logically not as common as cyanide for example. But this wasn't the main reason why I placed the ban. Everything that happened after that. I deemed this as a result of poor escalation. This occurred while I was wrapping up and preparing to allow the round to end due to it stretching out to 20ish minutes at this point. Disarm spam against the RD. There's a scuffle. Phoenix's character gets shot by the laser rifle.

Yeah, perhaps some AI time would be cool. Maybe like 5-10 hours or something

Application Accepted. Locking and archiving

Player made a separate thread found here. This is a duplicate thread. Locking and archiving.

Player has been recently banned from the server due to a separate issue by another staff member. No discord unbans will be considered until this other matter is resolved. Unban Request Denied. Locking and archiving.

Alright, so I did put the ban into place. The reason why I banned you from antag is because you have tons of notes regarding that specific thing and the specific round that I banned you had you at round start going inactive/SSD. I noticed a pattern and I acted on it. The antag ban is not just related to your antag play and that's not for me to decide if valid or not. I simply acted on previous note. I also don't really care if you play visitor and cryo round start, that's not why I banned you. Nor do I really care if you ready up as antag with your pshyc. This is your cargo ban: I'll be willing to lift both these bans based on the following conditions. You will not ready up if you don't intend to play the round as any job other then assistant/visitor You will not ghost out of your body or afk in a corner for long periods of time without using cryo when not an assistant/visitor You will not round start cryo on any job other then assistant/visitor You will ahelp if life is just life to avoid breaking these points and getting yourself banned. Failure to follow these two points will result in a permanent server ban being placed due to your extensive history with this issue. Do you understand?

It already has a month of restriction via the var required_age = 31

Hello, this is a friendly reminder to everyone reading this. Only post if you're involved. Do not ad hominem. The topic will stay constructive. Thank You

Also, by doing this, you'll get an issue with players readying up as AI just for the chance to become malf, then saturating the slot with people who wipe core at round start and get bwoinked. Let's not cause this issue.

Also, about the job restriction.. I don't support that. As someone who enjoys designing malf gimmicks, it's honestly the only time I play AI is when I'm malf. We shouldn't open up that rout just because I want to play an antag and go into the roll for it.

People shouldn't be ticking on the thing in the first place if they have zero idea how AI works. While the new player restriction coded in is rather nice and reduced in a drop, it would be much better to just give a pop up when they toggle the gamemode saying THIS IS A HIGHLY DIFFICULT ANTAG TYPE AND NEEDS SOME GOOD UNDERSTANDING ON HOW SYNTHETIC WORK.

Sorry, I've been busy these last couple of days and I haven't looked into the server much. Anyway, I am willing to agree with garn on this. We had a separate discussion about the acceptability and what is considered power gaming and acceptable to sabotage telecomms and some other general antag stuff. Got some clarification with more of the Why side of things. Does the player have a good reason? Anyway, I'm willing to allow garn (or myself) to remove the warning from your history so it will not appear if other staff members are making a decision in the future.

Ok. Consider this accepted.

Right, we'll post this picture for reference. It was somewhat repaired at this point in the picture with some wires added back to the machines. You also took the a couple of vital boards. Keep in mind, telecomms is a rather vital thing for the general flow of the round. I don't see how you're driving a story by teleporting into telecomms and sabotaging multiple machines with practically little interaction. Now since my points are reinforced, I'll go through yours point by point for why I made my decision then allow another staff member to look over it. I really don't see how cutting telecomms like this really adds anything to the round. I'm not talking about a ganking standpoint. It really just seems like to me that once the engineers came up, stealth, they turn it back on. Then just removed the boards and destroyed the machines. This wasn't something minor that any brain dead engineer could do. I fail to see this as an excuse. You could accomplish even the same thing by bringing a multi tool up to the sec bus and just turning it off instead of ripping apart the vital machines and spacing the boards. This drives into why I exactly warned you. You're story failed to attempt at encompass anyone except for a couple engineers who went up to check why comms suddenly died. It actually reduces and soils the round for the rest of everyone else when comms wordlessly shuts off due to multiple machines being ripped apart. It's because these things retract from the experience. It's not fun for phoron to suddenly flood everywhere. It's not fun for the engine to turn engineering into a hole and power to die. It's not fun fun for telecomms to just be ripped apart when no one, except for maybe a couple engineers after the fact, knew there was even ninjas onboard. I will quote one of our rules. "Note that these rules cannot cover the myriad of situations that will arise during gameplay. As such, the word of Moderators and Administrators ingame is final, and not up for debate past a certain point. If you take issue with an ingame ruling, you are expected to submit a staff complaint about it, or to contact a Head Administrator about it after the round has concluded" From what I personally witnessed, I think it was restored perhaps 10 minutes before CT. I'm sure there will be logs when comm chatter actually started that can double check this. I could be wrong. It doesn't matter much though. I can go into maint and cut a long hall of wires that would be fixed in twenty minutes, but that is still not something that should be done without prior escalation with the crew that is more then just drain APC, cloak away, then watch engineers fix it. The wiki isn't an excuse in my opinion The teleport isn't really a good excuse. It's more there because traditionally, there has always been a beacon at telecomms since the Exodus had a separate satellite you have to teleport too. It's more there for people to try vanishing behind a wall of turrets when being chased or into maintenance by teleporter use. Hell, even as a sneaky way for ninjas to board the station. This is why I don't agree on your reasoning. It's all a matter of perspective and how the rules are interpreted. May I be in the wrong? I very much could be so. It happens. We all make mistakes sometimes. But that's why we're here because it gives us both a reflection after-the-fact on things. That's why we have staff complaints as an option for players.

Ok, future refrence, just make every new point a new line and we'll be golden. For the unban, I'll go ahead and unban. Don't kill yourself then not respond next time. The game does tell you that you click on my name to respond. Please go over the rules. Do you understand?

[b]BYOND Key:[/b] (This is your Byond login/Ckey) [b]Total Ban Length:[/b] (The total time of your ban. You can also note your remaining time, though it is not required) [b]Banning staff member's Key:[/b] (This is the staff member's BYOND key/Ckey who placed the ban) [b]Reason of Ban:[/b] (You can see this when you attempt to log in to the server) [b]Reason for Appeal:[/b] (State your reason for why you think you should be unbanned) Copy and paste this, edit the post, you don't need to make an entire new post. Remove the parenthesis my dude.

Hello, please use the correct format on the appeal. Thank you.

Alright, I clearly screwed up after taking a gander into your player info on the WI. When you were playing rounds in May, I don't think I was active at that time. Plus I think you may of returned on the server when I was inactive later in the year. All and all, I clearly did not recognize your name and I apologize that this was taken this far. In general, I mistaken you for an average shitter. When I made my decision with the behavior that the bartender was also doing. All in all, crapping your pants isn't really something that should be done in game. I'll hop on and lift the ban for you and just replace it as a warning. On the metacomm part, I don't think I saw the IC stuff before hand. I'm going to drop that as well.

I assume that's why this feedback thread still exists. Being in a PR doesn't mean said PR can't change. I guess if they change their mind. I'm curious how this would work out.

This is why I said something like red alert or even code blue. It'll be on a button.

This is why I said 'Generally'. I never claimed it was 100 percent of the time. It's like having no engineers, no power. It's like having no armory access. Like having no AI. Sometimes stuff will be lacking and that's just the nature of the server. Out of everything, zero security or little security is pretty rare.

I'm going to agree with this PR. There are options, like any other department, for security to get inside. If worse comes to worse, command can always enable maint access or the three officers can stun baton a door open. I also bring this up in the perspective of response time. It only takes one second for a single person to yell out bad stuff into comms. It will improve the safety for the antags to do some sneaky crap without one misstep sideways suddenly blowing their entire cover then five officers all showing up. It doesn't really matter how robust you are. One person can not be expected to fight the entirety of security at once. I don't find an issue in reducing their response time to maintenance. Hell, I say test merge it, see how well it goes for a week or two, then decide if there needs to be some adjustments. Security generally is a department that is always staffed. Even during deadhour, there are always 4+ people. Generally, I don't think it's too hard for an officer to track down antags in maint. I'd even be ok with code red giving officers maint access.

Hello, I'm going to post a little bit of what I know with a player side of perspective. By no means am I a deciding staff member of the complaint nor do I want my opinion to be considered as an actual deciding decision in the complaint. I was one of the Tajara guards so my true knowledge of the round came with the three armed cats walking out of the bridge. Their war is bloody, there was a fight, and people got shot. There was then a massive investigation by PRA officials after the Consular faxed for them. In my own opinion, this seemed like an IC issue. The lings in the round still gave some issues to the rest of the crew afterwards.