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

antags should roll before roles #34025

Open
K-Dynamic opened this issue Dec 23, 2024 · 5 comments
Open

antags should roll before roles #34025

K-Dynamic opened this issue Dec 23, 2024 · 5 comments
Labels
A: Core Tech Area: Underlying core tech for the game and the Github repository. A: Roundflow/Antag Area: Roundflow - "What happens in the game", including antagonist roles and their capabilities D2: Medium Difficulty: A good amount of codebase knowledge required. P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: New Feature Type: New feature or content, or extending existing content

Comments

@K-Dynamic
Copy link
Contributor

K-Dynamic commented Dec 23, 2024

Description

Feature is frequently requested, recent discusions on Discord indicate lack of opposition.

SS14 currently picks antag roles after rolling crew roles first, meaning most players will avoid playing command or security. There should be a cvar option to enable picking antag roles before rolling crew roles.

Example:

  1. Enable cvar
  2. Roll for selected antag (e.g. syndicate)
  3. Rolled syndicate, skip protected crew roles (e.g. captain)
  4. Roll other crew roles (e.g. engineer)
  5. Start shift as syndicate engineer

Regarding metagaming concerns, a common example is if Urist McHands is a regular HoS player and appears as a passenger, then they must be an antag for the shift. However, Urist McHands could have simply decided not to play HoS, and manually unselected the role to roll traitor as most players currently do. It is also possible that their priority was set lower than that of another player.

Either way, round quality severely decreases the more understaffed security and command departments are roundstart. I would personally prefer having a 'hard' character that only plays antag or command/sec rather than possibly rolling on a character I'd rather relax on.

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

ScarKy0 commented Dec 23, 2024

What I'd like from a system like this would be that if you have no antag-rollable jobs selected it should skip you.
Example:

  1. Have only captain enabled
  2. You cannot be pre-rolled for antag as you have no antag job selected
  3. Play captain
    As opposed to
  4. Have only captain enabled
  5. Spawn as a tider due to rolling antag
  6. Cry

For me its less of a worry for metagaming than the fact I don't wonna make additional characters for antag purposes. It's way more convenient if you suddenly decide you wonna play command or something to just toggle the jobs. (And I only have one character)

@ScarKy0 ScarKy0 added P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. T: New Feature Type: New feature or content, or extending existing content D2: Medium Difficulty: A good amount of codebase knowledge required. A: Core Tech Area: Underlying core tech for the game and the Github repository. A: Roundflow/Antag Area: Roundflow - "What happens in the game", including antagonist roles and their capabilities 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 Dec 23, 2024
@K-Dynamic
Copy link
Contributor Author

What I'd like from a system like this would be that if you have no antag-rollable jobs selected it should skip you.

I'm not sure what you mean by this since you could just disable antag roles after selecting sec/command roles only.

@ScarKy0
Copy link
Contributor

ScarKy0 commented Dec 23, 2024

I'm not sure what you mean by this since you could just disable antag roles after selecting sec/command roles only.

Just me being nitpicky. Don't feel like having to constantly jump between the menus (especially since the character menu is less than ideal)

@ilovehans10
Copy link

I've also got to say I like playing chemist and salvage but for both of those I hate rolling antag roles as I'm either stuck in my department all round or stuck off station all round. And don't get me wrong I know you can be a perfectly good syndie chemist, but being a chemistloose feels like I'm asking everyone to look at me and question why I'm approaching the bridge. Maybe this is entirely to personal preference, but it could be nice to have an option in job loadouts to turn off antag for just the one job.

Another feature that would go hand in hand with this would be the option to copy and paste loadouts to different jobs so I don't have to go into every loadout and turn on winter jackets, winter boots, weh plushies, the lesbian pin, and smokes.

@ilovehans10
Copy link

After looking through the issues quick another option would be to have overridable global loadouts as suggested in #28832 and have antag roles tied to loadout. This way by default all my characters can have satchels and zero chance of being an antag, but my bartender will have a duffel bag and a chance of being initial infected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Core Tech Area: Underlying core tech for the game and the Github repository. A: Roundflow/Antag Area: Roundflow - "What happens in the game", including antagonist roles and their capabilities D2: Medium Difficulty: A good amount of codebase knowledge required. P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: New Feature Type: New feature or content, or extending existing content
Projects
None yet
Development

No branches or pull requests

3 participants