remove GenericAntag completely #28218
Draft
+0
−183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
he cookin |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
github-actions
bot
added
the
Merge Conflict
github-actions
bot
removed
the
Merge Conflict
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the PR
depends on:
fixes #28212
Why / Balance
its no longer needed
Technical details
🕯️ 🕯️ 🕯️ 🕯️ 🕯️ rest in piss
Media
Breaking changes
GenericAntagRuleComponentandGenericAntagComponenthave been deleted in favour ofAntagObjectivesComponentand having the rule spawn the antag rather than the other way around. to have a rule easily show up in roundend summary just setagentNameonAntagSelectionComponentlike before.Changelog
no genericantag no fun