Habalabam

And, pretty please, make it possible to read pipe flow. Not just pressure. Either a dedicated meter, a combined pressure+flow meter or click it using atmo PDA scanner.

Oh, right. My bad.

Last time I was involved in this discussion, this boiled down to an agreement that HOP should be able to issue time limited passes, which also would create an explicit "audit" context of the IAA visit. And HOP may demand a report each time, which would raise the bar of the IAA doing such a visit. Of course, this doesn't mean that similar discussions haven't concluded differently in the meantime.

Isn't it your job description, alert level and SOP that together states if you can have weapon, what kind and in what manner? In what instances should this be deviated?

I may be outdated on this, but I certainly remember many times when IAA came around to do an "audit" on various departments. I've been a QM and showing the IAA that the forms were filled out and that the cargo area reflected ongoing requests. I've been a CMO and shown an IAA around who was making sure that things weren't a mess. I've been HOS and shown the IAA that security records reflected the brigs. ... and an overall workplace hazard assessment. To me, this is SOP stuff. Yes, IAA has to double as public defender if the public defender is absent. But this is to me a "best fit", since being impartial is already a job requirement as well as already having a duty to support the workings of various departments, including security. The IAA is concerned with the inner workings of departments. Every department viewed in isolation as to their level of competence, compliance etc. The NTR is concerned with how all the efforts come together. The interaction between all parts of the station to serve NT interests.

Yes, the IAA has an oversight on department compliance to SoP. Contrary to popular belief, not just Security. The recipient of this is the department head and notifying the captain. The NT Rep duties have no overlap with this.

I do wish there were better tools at security to coordinate efforts of the officers/secborgs. A tracker map would go a long way. Also, sec computer should be able to filter on non-normal statuses, so that warden can see all with "wanted" status and thus pick up on incomplete arrest orders. And the security records should be traceable with a change log, showing who set what. Maybe swipe your ID on the sec glasses to achieve it so that status changes had your ID. If the secborgs aren't on the available camera feeds at security, then they should. If all those were in place, I think it would be easier to see if there really is a need for somebody to be a dedicated dispatcher. Or maybe the HoS would take a greater interest in the desk part of the job if the tools were in place. But, even then, the HoS could always demand one of the officers to grab the front desk.

It's a role with a lot of potential for building your own character. You have your pick at what the character background can be. Some possibilities for emphasis are: * Cermonial * Inquisitor/"Kick-ass-for-the-lord" person. Either from the supernatural perspective or the spec-ops perspective. * Spiritual-growth-in-others kind of person * Some sort of reject who have been given a bad assignment far out in the galactic wastelands. I see no reason to limit the role in some sort of SOP other than when he/she needs to step up to the plate during cult/vamp rounds. I think the wiki should focus on those aspects of the job. I remember once I played chaplain and security had need of my services. I wanted to make somebody drink the holy water, but instead I broke the flask on their head or something.

You give by having something in your active hand, then right click a person in an adjacent tile and select "give".

The borg itself is not the antag. It is a tool that risks becoming evidence and using it is part of the risk/benefit consideration of the antag. And if the reveal is limited to just ascertain that it is in some way subverted, but without the specifics, then they still need to puzzle it together to find the real perpetrator. When are you suggesting that "state laws" is yielding something useful? I have often played as borg. Subversion laws "always" come with a provision to not state it or hint at its existence.

Not that "stating laws" should be useless, surely?

(I'm so unrobust that I'm dreading playing ling/vamp/shadowling out of fear of embarassing the species) That is what I'm talking about if made relevant for Paradise, both in terms of acting out the Security SOP and doing so within the Paradise community. Not just to be second guessed, but also to illustrate the difficulty in playing security and the level of abuse you face over comms even when doing things correctly. And how many antags are acting in a manner (including over public comms) that leaves the impression to the rest that the suspect player OOC is feeling genuinely abused. A behavior I feel is downright toxic to the community. No matter if: 1. It is an antag, actually caught, who flings out abuse over public comms and OOC. 2. It is an officer being a bully over nothing and causing disdain/frustration which people ignore because they hear the word "shitcurity" every round.

Yes, if easily accessible, it should be combined with the ability for antags (including malf AI) to withhold their play. As described above. Maybe the laws give too much away, maybe just "checksum fault" or something that doesn't distinguish malf AI from emagging from hacked laws. Merely ascertaining at robotics that a law is withheld might be sufficient. I haven't played that much, but it seems that the "state laws" is pretty much useless.

Although relevant, I don't think that the negative angle serves the same purpose of showcasing actual challenges of being security. I don't think the "shitcurity" debate is lacking in straw men. Maybe, just maybe, a person who normally plays security would get some useful feedback. And maybe, just maybe, a person who normally flings the "shitcurity" term around, finds that he would do no better himself. I would say that the majority of EOR OOC nastyness has to do with this single topic. And a common reference would be a good starting point. It's also relevant when discussing SOP and prisoner processing.

I don't think an atmo setup from scratch can be compared to following a step-by-step procedure to set up engine or merely wiring up solars.