Skip to content
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

Make MindShielded players immune to becoming Sleeper Agents. #34648

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ewokswagger
Copy link
Contributor

About the PR

Made MindShielded players ineligible to be Sleeper Agent.

Why / Balance

Command members are antag immune due to the damage that can be caused by an antag command member. People promoted into command and mindshielded should be immune for the same reasons. This also allows for Captains to point acting heads more comfortably, knowing that they will not become a sleeper agent.

Technical details

Single line yaml change

Media

2025-01-25.22-59-15.mp4

Requirements

Breaking changes

Changelog

🆑

  • tweak: Mind Shielded players will now be immune from becoming Sleeper Agents.

@github-actions github-actions bot added Changes: No C# Changes: Requires no C# knowledge to review or fix this item. S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. size/XS Denotes a PR that changes 0-9 lines. labels Jan 26, 2025
@ArtisticRoomba ArtisticRoomba added P3: Standard Priority: Default priority for repository items. T: New Feature Type: New feature or content, or extending existing content T: Balance Change Type: Balance changes through direct value changes, or changes to mechanics that affect it DB: Beginner Friendly Difficulty: Great for beginners. Unambiguous in scope, and explains how to achieve the result. A: Roundflow/Antag Area: Roundflow - "What happens in the game", including antagonist roles and their capabilities S: Needs Review Status: Requires additional reviews before being fully accepted and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Jan 26, 2025
@NoElkaTheGod
Copy link
Contributor

Counterpoint: you can be a syndie before you get promoted into command, there's no way to tell if you are a syndie (unless you have a skill issue), and installing a mindshield into a syndie does not stop them from being a syndie. As such, this doesn't really change anything, because promoted member of command can be a syndie anyways.

@Aisu9
Copy link

Aisu9 commented Jan 26, 2025

i would like to point that refusing to promote someone to the rank of department head position is quite literally bursting the following metaprotection rules that is even on lizard, i don't see the point of captain/hos/command members powergaming by denying promotion to department head because "they can be antagonist" nor see the utility in making mindshield crew enable to become antagonist beside pushing powergaming behavior such as mindshielding the entire crew.
xbxbxbbxbxbxbxbccbvb

@a-random-lemurian
Copy link

https://cdn.discordapp.com/attachments/241861037878542336/1333146193177346169/image.png?ex=6797d4a5&is=67968325&hm=c59992746b27d1502ef11d27e0af470e3a9f7efabf640d06ac08d9286f05fa96&

Discord CDN links only last for 24 hours (those are the ex, is, and hm fields). Not permanent enough.

For future reference, the person was quoting rule 4: "Do not metagame, obey the Metashield".

@keronshb keronshb added the S: Undergoing Maintainer Discussion Status: Currently going through an extended discussion amongst maintainers, as per procedure. label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Roundflow/Antag Area: Roundflow - "What happens in the game", including antagonist roles and their capabilities Changes: No C# Changes: Requires no C# knowledge to review or fix this item. DB: Beginner Friendly Difficulty: Great for beginners. Unambiguous in scope, and explains how to achieve the result. P3: Standard Priority: Default priority for repository items. S: Needs Review Status: Requires additional reviews before being fully accepted S: Undergoing Maintainer Discussion Status: Currently going through an extended discussion amongst maintainers, as per procedure. size/XS Denotes a PR that changes 0-9 lines. 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants