Sonador

I agree with necaladun, but I also understand - it's really bad sportsmanship to be validhunting as non-security silicons, and really really bad sportsmanship to be playing supercop as the AI. It's not against the rules, but it should and does get you targeted and killed by the antag very frequently, even if they have low-level objectives. If I were staff, I would absolutely greenlight any ahelp for permission to kill or destroy the AI as an antag if it's being a total scrunt to them. If the opportunity presents itself, like if a sling bumbles by an engieborg repairing wires and subsequently gets chased and spotlamped to death, then whatever, gg. I would like to see the administration take a hard tack against AI validhunting, but only in one specific way - as necaladun stated, you are to follow your laws, and if that means someone needs the AI/engiborg's help to fix a breach to a critical station area, or to put out a major fire, or something more important than bolting in a tider or lone cultist and they miss/ignore the order because they're too busy playing supercop, that should be grounds for a note/chat and potentially a silicon ban if it gets crew killed. TL;DR, don't be a dick as a silicon if you value your reputation as a player/member of the crew, and (hopefully) beware getting bonked if you're so busy focusing down one misbehaving crewman or antag that the station's suffering for it. Secborgs are obviously fair game, and I frequently see antags prepped for them, so it is what it is, and when I play a secborg I don't salt a grain if I get owned while trying to nab a baddie.

I have a soft spot for meta. It was our primary map when I hosted both iterations of the Vinesauce SS13 servers going on 10 years ago. Oh god, 10 years ago. Please. Please kill me before my muzzle starts turning greyer than it already is. It's got some real chops, but obviously needs a lot of work. Maybe I'll make this my quiet time wind down before bed project for a while. I'm not entirely stupid when it comes to mapping.

I was about to say, so long as drones and drones alone get cyborg plasteel sheets and an appropriate charge cost to use them, I wouldn't mind drones being able to patch up secure areas. In most cases, the plasteel's already there, so severely nerfing its maximum capacity in the stack would be prudent, too, if the idea is to prevent drones retrofitting every inch of the station into fort asshole. They're not borgs, are REQUIRED to not be involved with players, antags, or the AI, and are heavily encouraged just to be a counterforce to the entropy of the station getting thrashed and tided.

Is there any way to implement one-way windows in the code? Something tells me not. That would be the best option. Another easy solution is to move the shutters to the top of the z-level so the windows are shielded when closed. Tiders that break the windows because they're mad bridge closed it should be bwoinked for self-antagging, that's a spaced section and sabotaging because tide is not okay.

I'm sure it will be clarified and I suspect it was a specific incident that drew the administration's ire given for how long they've just generally been a thing to suddenly crack down on it now would be a pretty terrible look. The CPH fore of the bridge is usually the single busiest area of the station and for civilians with no real job to perform, it's going to be one of the most appealing places to be. As a command player, it's actually quite fun to have the peanut gallery present, it provides opportunity for interesting dialogue and such - and I'm generally never one to hobo, myself. I strongly suspect their were players with jobs hoboing, or they were up to something far beyond the pale of our usual millers about if someone used toggle-build-mode-self to wall off the bridge. It's not a permanent change for certain - I'm online now and the maps is as usual. Insofar as command players being irritated by them... there's literally an off switch for bridge hobos right smack dab in the middle of the bridge and unlike the more annoying tidey assistants that would just hack or break their way into whatever they please, there's not a non-bwoinkable way to open blast shutters. It is literally one click to make any serious conversation on the bridge much less interceptable or interruptable.

Much like any legal profession, conduct has pretty much everything to do with your success. You'll never win, even if your case is watertight, if you're conducting yourself like an asshole. Forgive me if I nerd out a bit, but my boyfriend is a hunky lawyer, so I know a little about this through osmosis. In court, your ability to succeed as an officer of the court (which is a major moving part of what the Magistrate is - they may more taste like a Judge, especially when presiding over a case, but in their day to day, they're as much a lawyer as they are an adjudicator, building a case AND applying law) has equal parts to do with not only having a sound case, but presenting it in a calm and collected manner, following the standards laid out for you to a T. Security, especially in round where they are busy enough to be making legitimate mistakes purely out of their workload and not just being bald, is probably not going to waste their time with you, obligated or not, if you're screeching as loudly and obstinately as the greytider they just brigged 15 minutes for minor trespass. As a Warden, if CC were to bother sending an NT agent over to lecture me for ignoring the magistrate, I'm pretty sure given they're operated by administrators, I could make a pretty good case out of "Look, I get this is an SOP violation, but the Magistrate is behaving as a gibbering fool while we're already overloaded - if I get the time, I'll crack open the space law book and review a sentence if he tells me to, but two of our guys just got nabbed by changelings and there's tiders everywhere, I just don't have the time for another space asshole right now." It works this way in the real world - if you violate the Rules of Civil Procedure, you risk your case, your license, and even being litigated by your client for blowing it - even if the case was unloseable otherwise. I can very easily see the burden of blame shifting from shitsec TO the Magistrate under the eyes of a very pissed Naval Officer if he's been a gibbering scrunt about it all shift, given ultimately it was his baldness that prevented security from changing course. "The state of security is ultimately your blame - you were charged with overseeing their legal processes and dropped the ball so completely that you've made it arguably worse. That's a problem I'm here to correct." Conversely, the Magistrate should most certainly be feared by security if they're speaking softly and carrying a big stick. They have one of the single most terrible powers behind them - the NT Legal Division, a dark council of litigious corporate misers with one goal in mind: cull liability at any other reasonable cost. If, even during a chaotic round, a Magistrate pulls the Warden aside and mentions, "Warden, I appreciate you're busy, but when you get a moment, this prisoner's sentence is 10 minutes too long and he was already in processing for 5 minutes - please adjust the timer as soon as you can" and they get told directly to suck shit or are completely ignored, you can and should absolutely expect that within 30 minutes, the Warden's ID will be at the HoP Line for demotion. The Head of Security should get sweaty palms the moment one of his charges gets snitty with an amicable Magistrate. CentComm - again, as operated by admins - should absolutely be ready to be the sharpest sword sprung forth against a security team (and doubly so if Command does not support him) that ignores a competent and collected Magistrate, to the degree that the clearinghouse that comes from it risking the round for the crew. The Cyberiad is one station out of thousands - and if it means it burns to avoid a class action lawsuit from the unseen estates of harmbatonged crewmen or a union they missed busting worth several times the installation itself, so be it. Security should be aware that playing dirty willfully to the degree of snubbing the guidance that is the robust Magistrate will come at a tangible cost - one not worth taking one minute to adjust a timer, release a prisoner, or otherwise whatever is prudent. A polite word to an offending security officer and the HoS, Command when that fails, and finally a fax to CC where appropriate should readily draw the dreaded, omnipotent, titanic spotlight of Trurl attention onto the Cyberiad. Long story short - shitty Magistrates should fear Centcomm more than Security should fear a Magistrate.

Really stupid question, but is it possible to hex edit or patch the executable to force it to be large address aware (at least to the degree a 32-bit process will allow?) I'm assuming if it were possible, it'd be done already, but a lot of older games I play, people have found methods to force them to enable more RAM usage.

They already have a segway that the warden can elect to hand out. I *believe* it does, or at least did, negates stuns, ensures top speed movement, and for grabcuffed prisoners is pretty much guaranteed they'll reach the brig. The problem with vehicles is it's hard to make a single tile, multi-occupant vehicle to the degree it's impractical (see: spacepods, ripleys, and the other related vehicles and their occupancies.) As someone who works in security, it's also a size vs. necessity problem. A properly fed security guard can get from one side of the station to the other in under half a minute, and for faster responses we have the segway and such. A ripley or janicart style vehicle is also a machine object, so it blocks movement while parked, which would make handling responses in maintenance an actual nightmare. I think security's balanced enough without giving them an additional vehicle.

I could be wrong, but this is how it works for me, beyond ambience. The less pressure there is around you, the quieter sounds around you are. Try knocking on the window repeatedly the next time you cycle an airlock.

--

Just a small bump as I promised I'd upload the old flowchart for the event if I found it.

I hope this automerges my post edit: my feelings! So, those of you who know me know I like to do bits. Silicons that are just the brain of some NT accountant who got caught sleeping in the breakroom one too many times, AIs that are things like Dril or just some decrepit old computer. That sort of thing. So, I decided to do a bit with Luca Cabrillo, my engineer coyote-Vulp as the clown. Her gimmick is that she's just a washed up, demoted engineer wearing clown shoes and assigned "Morale Officer" for accidentally clipping the wrong wire on another station and shutting the lights off on some NT bigwig's big corporate presentation. So, she trundles around the station, depressed, alcoholic, and generally being a mopey wiseass. I had big plans for my first shift, but I get to the bar, have a drink, and suddenly, Nuke Ops. So, I put on my best professional face, and committed entirely. She wound up surviving the nuke in a fridge with Ian, the chef. Also, bonus robustness:

Sent this about half a second before a blob-forced nuke endround

I agree that presently the psych is at a severe disadvantage. You're using an RP role to address what is otherwise, non-mechanically, an issue of poor RP. While it's great if two roleplaying users get up to some actual RP, it's the Psychiatrists job, basically, to roleplay the bald greytide out of people. Adding some mechanical purpose to the psych would make them useful, and make rounds interesting, similar to how the chaplain is a counter to cult and vampires. Might be great for Rev rounds, sling thralls, etc.

Given borers are also inside you and can be suppressed with sugar, it'd make sense that they can tell if you've been poisoned or what have you because they'd be impacted too. So maybe just the equivalent of a self-examine for brute and burn (pain and numbness) as well as something similar to a reagent scanner would be ideal?

I understand! I definitely was trying to work the "Trurl Communications Guy" angle with these. I might try something a little different later on. In terms of new VO for the more serious announcements, I'd definitely be willing to try something like that. For the security levels, I'd like to avoid attaching VO lines to them save for Epsilon given how often they're called. I feel like people would get tired of my voice quick. I like your idea of that "Oh fuck" kind of direct CC intervention flavor. I actually did this up in regards to an event I was working on for Paradise, but gave up the ghost on some years ago now: (There was a lot more planning that went into this than just "eliminate the crew," I promise, it's just that in the end I decided not to suggest it as I wasn't happy with how the end result looked. Maybe I'll post the flowchart in here sometime, if I can find it) That said, here's some sample lines I did for Epsilon and the ERT announcements. Let me know what you think. Epsilon Security Level NVO Epsilon T1.wav ERT Amber NVO AmberERT T2.wav ERT Red NVO RedERT T1.wav ERT Gamma NVO GammaERT T1.wav

Good Morning Cyberiad! I've come to you today with a conundrum. I subjectively dislike the recorded VO for station announcements and such. Huge problem, I know. I realize the announcements were likely generated through a Text-To-Speech system because voice work ain't free (usually) and there's a lot of it to replace. So, I come to you today to take your temperature on something I'd like to do for you: Do some original voicework as a drop-in replacement for the voiceover announcement system, and see if you all prefer it over the old ones. As it stands now, I've prototyped three types of announcements to see if this is even something you'd be interested in me doing (or not opposed outright.) Here's the idea: Type 1 is a fully worked, filtered, and edited clip with microphone/signal foley and public address effects. VO1 Level7 Outbreak Take1.wav Type 2 is a Type 1 recording, without mic foley, just public address effects. VO2 Meteors T1.wav And Type 3 is just a straight filtered recording without public address effects. VO3 Xenos T1.wav All of this is recorded directly by me and if there's interest, I'll produce a full drop-in replacement kit and bundle it into a pull request (or whatever/however github works.) If the Paradise Station staff like these takes enough, I'm more than willing to make this more involved, including doing multiple takes, fiddling with the filtering, and possibly adding more lines, such as narration for security levels changing, contingency records for events, and if this is really liked, a rework of the full VOX library. All samples will be provided with no rights reserved beyond origination, anyone can take and do as they please with it, including Paradise assuming the license of lines produced for the codebase under whatever theirs is. What I'd like to hear from both staff, especially maintainers and lore folks, as well as players that would have to hear my voice all the time is, do you like these samples? Which type do you prefer? Do you have any criticisms? Let me know, and I'll see what I can whip up in response. Thanks!

Just chiming in to say that if you are instructing brig physicians to only heal prisoners and otherwise ignore injured/dying people, including security staff, in the brig, you should probably remove the role. You are asking medical staff to ignore the Hippocratic nature of their role and expecting them to adhere to it as a gameplay rule is unrealistic and shortsighted. It is far more reasonable to expect discretion from and subsequently reprimand a "Brig Technician" for building SecurityStation(tm) instead of hanging around and being lazy when there's no damage to the brig to repair, than it is to instruct *medical personnel* to not perform *medical care.* While we're on the subject of roles doing shit they're not supposed to, let's talk about magistrates interfering with the warden and HoS'es ability to administer the brig, which is far more problematic than an EMT being an EMT.

That's not really a logical argument. It neither requires admin supervision for it to work, nor does pretty much anything on the station have zero requirement for admin intervention if abused. People maliciously blowing borgs just because locking them down has a timer is not acceptable conduct just as executing a prisoner is not acceptable just because once their cell timer expires they're going to go back to greytiding. Borgs may be nonhuman machinery, but they're still players. If anything, this provides *less* requirement for admin intervention as now if someone locks a borg and then forgets about it (or does it maliciously,) it no longer requires admin intervention to remedy and can be delegated to be handled ICly, instead of having to manually unlock the borg and confront the malicious player unless they do it repeatedly. Blowing borgs without warrant is already against the rules and this suggestion doesn't change that. I get admins are *very, very* busy, I used to be one on many servers. In this case however, it's not a legitimate argument against this suggestion.

As a non-malf borg that was locked down once for nearly a half hour before someone found me and managed to get it along the chain, yes, a maximum time for lockdown is a good idea. If you can boink people for improper executions, you can boink them for unwarranted blowing (and already do.)

Is it not a violation of SOP to be randomly searching people just because they're in maints on green? Doesn't the station stay on green until something *actually happens* to indicate imminent danger beyond the round start communication? Seems like it should police itself, why is it not?

Hey ho! Phantasmic didn't post it here (and I don't think I did either) so I'm just replying with a commish I got from them recently. I've very happy with it, and the price was a steal!

God that was my favorite round as AI bar none