Updating the metashield(Still a wip + feedback needed) #518
Conversation
github-actions
bot
added
the
S: Untriaged
|
doesn't it directly state in SoP/Entry for blue alert that thievery isn't a reason to move to blue? Or am I misremembering. Also blob forces red why is it considered blue?? |
Can you point? It really depends, it's sort of why I also did mention unique items (reference to command only items) - should be blue because this is more than just "petty theft". I do plan to fix some of the headings |
ahh yeah, makes sense didn't really see that one. |
ThanosDeGraf
left a comment
ThanosDeGraf
left a comment
There was a problem hiding this comment.
I like this PR, though I wish the comedy was driven up some, but since most of the doc is describing threats I get there's not a lot of space for it.
One thing that confuses me is how divulging sensitive information while under NDA is supposed to work.
Take cults for example. Before, it told you they are dangerous, HoS' should tell their department and the chaplain about it and protect the latter. Meanwhile the new version says the chaplain is already well informed about cultists. But you can't tell the crew anything still because before Section I. it says:
Please also remember that all of this material is [bold]confidential,[/bold] as per the NDA you signed on employment.
Failure to comply with the terms of your employment will be met with swift legal action.
Which means the document must also describe when and how you are allowed to bend the NDA. Since you removed most mentioned of who when is allowed to be told what, this aspect needs to be fixed.
| The following material is available for your reference, training, and use. | ||
| The information is designed to assist Command members in their professional development. | ||
| Please use the material to expand your understanding, enhance your professional knowledge, and to further your career. | ||
| Please use the material to expand your understanding, enhance your professional knowledge, and to further your career and possibly receive a stamp of approval from Central Command. |
There was a problem hiding this comment.
enhance your professional knowledge, and to further your career and possibly receive
replace "and to" with a komma
| Carelessly leaking this confidential information will be met with swift action from Central Command; whether that be through one of its representatives or through the organization itself. | ||
| You, as one of the leaders of the station, are to lead the crew through any potential dangers. Needlessly sowing fear within the crew is explicitly against this goal, and it is also against Nanotrasen's will. | ||
| Nanotrasen and its associated ships and stations are safe. You, as a primary representative of corporate's will, must make sure this fact stays true. | ||
| You are to inform security and other heads of any suspicious or dangerous situations. As command members you are to ensure station works as efficently as possible with as little slowdown or inconveniences as you can manage. |
There was a problem hiding this comment.
The section about not leaking confidential information and it's consequences was entirely removed. If it's about maintaining the vibe of the doc I get it, but I would suggest editing the NTR's SOP as well with a line that says something like:
#. The NTR is to keep a lookout for any breaches of confidentiality leaking corporate secrets or hurt profit margins.
Gives something for these corporate lackeys to do
About the PR
I have decided to edit and rewrite the corporate secrets metashield.
Why / Balance
If we're going to larp in our guidebook, we might as well be on brand for Nanotrasen.
The new shield is causing conflicts and annoying pacing within rounds, I am lessening the ridged nature of the metashield for Crew and for command.
Command members have enough on their plate, they are not designed in the game to keep the round moving, they are designed to keep a department running, which is already a handful when half of your department is antags.
I've taken a more comedic and on-brand Nanotrasen approach to the corporate secrets patch. No longer are the crew deaf, dumb and blind. Command will now just be more informed and will use the Nanotrasen logic as their reasoning and believability. I am stressing and encouraging the concept that command should be informing security, as the old shield acts as if command is security.
I have also included the alert levels so newer command members are aware of how we treat these threats.
Requirements
Changelog