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

setgamepreset command rework (take two) #30812

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

Errant-4
Copy link
Member

@Errant-4 Errant-4 commented Aug 9, 2024

Read this

I asked the admin team if they have any concerns or requests about this, please do not merge before they had their say

About the PR

repeat of #30756, now without stealthy test fails

setgamepreset command currently changes the game mode permanently* (until reset), despite the help strongly implying that it's only for the current round.

After the change, there is an extra parameter where it can be specified how many rounds the set gamemode should stay, after which it will revert to the server default. If it's only for the next/currently upcoming round the second parameter can be omitted and it will take that as 1.

It is no longer possible to set a different gamemode indefinitely with this command alone, but there are at least two workarounds: either change it for some arbitrary high number, or change the default gamemode cvar (and then change to that game mode to also trigger a reset afterwards)

Why / Balance

Anecdotally I was told that at least one admin finds it annoying that they have to manually change the gamemode back after using the command.
Additionally, there have been multiple unconfirmed reports about the some rare gamemode happening many times in succession, which might all have been instances of this command being used and then forgotten. I have not been given enough actual information to do any investigation on occurences, but if it is in fact real, it would also be resolved by this change

Technical details

The command sends the number of rounds to GameTicker. Every time the round is going through the round end steps it checks if there is currently a countdown going and decreases it by one. When it reaches zero, the game preset is set back to what the default cvar is, and the countdown is set to null

@Errant-4 Errant-4 requested a review from EmoGarbage404 as a code owner August 9, 2024 09:06
@github-actions github-actions bot added the S: Needs Review Status: Requires additional reviews before being fully accepted label Aug 9, 2024
@github-actions github-actions bot added the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Aug 26, 2024
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot removed the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Sep 3, 2024
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Sep 29, 2024
@SlamBamActionman SlamBamActionman added the S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. label Nov 14, 2024
@eoineoineoin eoineoineoin added P3: Standard Priority: Default priority for repository items. 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 T: Of Admin Interest Type: Affects administration work a lot, and might require admins to weigh in on and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Nov 20, 2024
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

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. Merge Conflict P3: Standard Priority: Default priority for repository items. S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted S: Needs Review Status: Requires additional reviews before being fully accepted 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

Successfully merging this pull request may close these issues.

3 participants