-
Notifications
You must be signed in to change notification settings - Fork 249
The Stationary Contraband Detector #378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Mixelz
wants to merge
10
commits into
space-wizards:master
Choose a base branch
from
Mixelz:mixelz-StationaryContrabandDetector
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+72
−0
Open
Changes from 4 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
abd7fed
Create StationaryContrabandDetector.md
Mixelz 37d414d
Typo :(
Mixelz 480d1e6
Closing possible Shitsec loophole
Mixelz 6aad5e2
Reffering to coincidental PR that is exactly what I wanted
Mixelz e410cd6
Review Updates Round 1
Mixelz c0b300d
Typo :((
Mixelz 43ed57b
GRAMMAR :(((
Mixelz a6b59e2
Added Per Person Cooldown
Mixelz e7af2d0
Merge branch 'space-wizards:master' into mixelz-StationaryContrabandD…
Mixelz 7e2a8ed
Merge branch 'space-wizards:master' into mixelz-StationaryContrabandD…
Mixelz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
62 changes: 62 additions & 0 deletions
62
...space-station-14/departments/security/proposals/StationaryContrabandDetector.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
# Stationary Contraband Detector | ||
|
||
| Designers | Implemented | GitHub Links | | ||
|---|---|---| | ||
| [Mixelz] Killerqu00 | ❌ No | TBD | | ||
|
||
## Overview | ||
The Stationary Contraband Detector is a one tile machine that will scan the inventory of any containers or people that pass over it. | ||
If the detector detects any contraband, it will alert those in its vicinity via a loud sound and lights like that of any alarm. | ||
It will also alert security on their communication channel that the detector was triggered and who set it off, but *not* what item set it off; this effect is proposed to be achieved by having the machine automatically update the Records system whenever it is triggered. | ||
|
||
It should additionally have a small percentage chance of displaying a false positive result so that it cannot be a guaranteed method of confirming the presence of contraband. | ||
|
||
## Background | ||
|
||
In the current state of the game, an end of round evac bombing is all but guaranteed and it its almost entirely impossible to stop unless you happen to have all potential agents already detained or very strong suspicion that a specific person will attempt to carry out the bombing. | ||
|
||
There are also very few methods of security being able to accurately confirm that someone has contraband; they must either visibly see them carry the item in their hands or must have prior reasonable suspicion that the target has it due to a prior encounter that would only be possible through contraband. | ||
|
||
A contraband detector, something that is a staple of real world security operations, would be a method to help alleviate these problems, add another layer of protection that traitors will need to bypass and would be a mechanical method of being able to detect if there is contraband in play while allowing sec to search a volume of people larger than themselves without grinding an area to a halt. | ||
|
||
Additionally, it can be used as a method to more reliably indicate the presence of a Storage Implant (I.E. Someone consistently setting one off despite having an empty inventory.), which has been a point of contention as Meta Knowledge due to the limited avenues of knowing when one is in play. | ||
|
||
## Design Intentions | ||
|
||
The intents of this implementation on when, where and why it should be used are as follows: | ||
1. As a starting point, it should trigger on any contraband outside of its owners department or always if it is syndicate contraband. An item in a dragged container cannot be attributed to a specific owner/holder and thus would always set it off without an owner being attached to it. | ||
2. It should be limited ONLY to high priority areas, there should not be a scanner on every hallway or maints shaft and its research restriction & difficulty to setup should be set accordingly. For this reason it should probably only be located on EVAC shuttles themselves baseline so that they cannot be stolen and moved round start. | ||
3. It should not, by itself, be a reason to jail or detain someone. It should ONLY be used to raise a flag for a security officer to engage upon with roleplay, either via following up with a manual search or interrogating the suspect directly. | ||
4. It should be able to be worked around IF it is planned for ahead of time. It should not be easily "cheeseable" through methods such as Q-Dropping the item past the detector, throwing the item past it or using a simple implant to ignore it. These would devalue more involved methods of a traitor getting past it and the point of the machine itself. | ||
|
||
## Addressing Mentioned Concerns | ||
> This would be a hard nerf to Storage Implants. | ||
|
||
I think it would make storage implants easier to detect, but it is an opportunity for more adaptive gameplay to emerge instead of using the implant as risk free storage. | ||
A very simple example could be holding major contraband in the implant while carrying minor contraband in a backpack to act as the scape goat. | ||
A competent Security could then ask for a quick recheck, sending the traitor into a panic for how to resolve this situation with their contraband still in hand. | ||
Effectively, we could roleplay as TSA agents and that itself sounds like it would lead to more fun situations than what we currently have available. | ||
> This would remove evac bombs from being possible. | ||
|
||
It would not since bypassing the detector is planned as part of its core intent. | ||
It WOULD make it much more difficult to achieve for the DaGD objective type, but it is already a trivial objective to accomplish and would be a massive QoL improvement for the Evac portion of a round. | ||
Mixelz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
> Shitsec could abuse this and violate space law with a dubiously "legal" method. | ||
|
||
It would be no different if those same officers decided to randomly search people without the machine and would still be breaking Space Law regardless. | ||
It would fall under being a new reason of probable cause and would be a massive boon for the players that are able to behave themselves. | ||
Its planned implementation is already quite restrictive, and while the potential of abuse is there the same can be said for many other mechanics of the game and I do not think this falls outside those already established boundaries. | ||
> This would potentially nerf traitors too much and/or buff security too much. | ||
|
||
Considering its intended restrictions, I do not see many scenarios beyond Evac Bombing that this would be a major change for. | ||
It would be specifically alerting the behavior in regards to casually carrying contraband, which I feel is something that has not yet been dealt with in any direct capacity. | ||
It would also encourage more RP scenarios as mentioned above, which may not inherently be a buff/nerf to either faction depending on how the "Meta" evolves from it. | ||
|
||
## Potential Follow Ups/ Other Notable PRS | ||
Some potential follow up PRs to this device have been discussed, which will be noted below: | ||
|
||
### Locking Uplink when Evac arrives [#34359](https://github.com/space-wizards/space-station-14/pull/34359) | ||
This would be a very appreciated PR to ensure its intent of evac protection is upheld, without this it would be trivial to bypass it for Evac bombing purposes. | ||
Mixelz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
### Allow the device to be EMAGGED so it always triggers a false positive. | ||
This will not be part of the initial implementation unless a maintainer would approve of it due to the EMAG restriction/freeze. | ||
Mixelz marked this conversation as resolved.
Show resolved
Hide resolved
|
||
### Create a handheld variant for individuals to hold in their hands. | ||
This would allow it to be more flexible in its use, though it should probably come with even harsher restrictions such as being unlocked with late tier research or being part of the armory. | ||
Mixelz marked this conversation as resolved.
Show resolved
Hide resolved
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.