Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Cyborgs should have access to the crew list #34606

Open
walksanatora opened this issue Jan 23, 2025 · 4 comments
Open

Cyborgs should have access to the crew list #34606

walksanatora opened this issue Jan 23, 2025 · 4 comments
Labels
A: Silicons Area: Relates to Silicon roles, including AI. D3: Low Difficulty: Some codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: Balance Change Type: Balance changes through direct value changes, or changes to mechanics that affect it T: New Feature Type: New feature or content, or extending existing content T: Of Admin Interest Type: Affects administration work a lot, and might require admins to weigh in on

Comments

@walksanatora
Copy link

it makes no sense that a cyborg can only read your ID card to determine crew status. cyborgs should have access to the crew manifesst for checking names. the ammount of times I have seen borgs witness a murder cause a sec/captain/etc takes someone's ID and kills them is stupid (otoh willingly being borged and having them take my ID so the scientist can gib me is nice). borgs are not stupid ofc this may also fall under failing to follow silicon laws.

@github-actions github-actions bot added the S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. label Jan 23, 2025
@BramvanZijp
Copy link
Contributor

it makes no sense that a cyborg can only read your ID card to determine crew status. cyborgs should have access to the crew manifesst for checking names. the ammount of times I have seen borgs witness a murder cause a sec/captain/etc takes someone's ID and kills them is stupid (otoh willingly being borged and having them take my ID so the scientist can gib me is nice). borgs are not stupid ofc this may also fall under failing to follow silicon laws.

This goes 2 ways, and I worry silicons, especially the AI, will use this as an excuse to validhunt ninjas, loneops, etc for not being on the manifest and thus not being crew, which is already a big issue.

If you think losing crew status so easily is truly a problem, a better solution would be to make a rule stating if you have previously seen somebody with a crew ID, and now suddenly somebody who is clearly still that person no longer has that ID, they still count as crew. Also, I am pretty sure borgs can ignore harm if the “victim” is okay with it, wether that be consenting to being borged or threatening to stab yourself if the ai doesnt open caps room.

@walksanatora
Copy link
Author

walksanatora commented Jan 23, 2025

yes but in the case of nukies putting on the ID would make them use a name on the crew manifest. and are therefore no longer valids. same could apply to ninjas since how ID works is if your face is completely covered it uses your ID's name iirc.

@walksanatora
Copy link
Author

but under current borg rules+rulings your ID determines crewmaship. and that determines your validity. if I wanted. right now I could start electrocuting and bolting in everyone who doesn't have a ID.

@ArtisticRoomba
Copy link
Contributor

AIs and Silicons have this intentional double edged sword design philosophy behind them. They're supposed to be really good at their job and be a real treat to have, but they can also inflict great conflict when they're subverted, and that type of chaos is a classic. All in all, there's expected friction when it comes to silicons.

There is one standing issue with them, though, is that many people have difficulty interpreting "who is crew". I don't think this suggested feature will help this desired clarity. This is probably something that should be talked about in a design document.

Also, I believe the AI has access to the manifest through the records console. Surprised nobody's tried to tie crew status to that yet, from what I've seen.

@ArtisticRoomba ArtisticRoomba added P3: Standard Priority: Default priority for repository items. T: New Feature Type: New feature or content, or extending existing content D3: Low Difficulty: Some codebase knowledge required. T: Balance Change Type: Balance changes through direct value changes, or changes to mechanics that affect it A: Silicons Area: Relates to Silicon roles, including AI. T: Of Admin Interest Type: Affects administration work a lot, and might require admins to weigh in on S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Jan 24, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A: Silicons Area: Relates to Silicon roles, including AI. D3: Low Difficulty: Some codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: Balance Change Type: Balance changes through direct value changes, or changes to mechanics that affect it T: New Feature Type: New feature or content, or extending existing content T: Of Admin Interest Type: Affects administration work a lot, and might require admins to weigh in on
Projects
None yet
Development

No branches or pull requests

3 participants