-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[HOTFIX] Antag ban fix #35308
[HOTFIX] Antag ban fix #35308
Conversation
Why are both of these prototypes handled by a single id string by the way? That looks a little sus. |
wish i knew |
Updating severity to P0 Critical, as per issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't make any sense. The function is still adding the Job:
prefix to the role name, so this would just create invalid database data.
the antag bans aren't even real from the looks of it (#29730 is closed). i can just make it so it ignores the antag bans instead of throwing in order to prevent database pollution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be getting validated (and logged) by the UI that allows admins to place bans instead.
Given that antag bans clearly aren't even a thing at all I'm gonna change the original issue description and lower the priority. I suspect the "server crashes" is just a thing caught by exception tolerance so it's not too important. Probably best to make this not a hotfix anymore but you can do whateevr. |
sure, I'll make a separate PR for this then |
About the PR
fixes #35266
hopefully I am doing a hotfix properly this time
Why / Balance
Technical details
Nukeops isn't a job
Media
server in dev doesn't crash anymore so that's a win, I guess
Requirements
Breaking changes
Changelog