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 Pull Request
This fix properly sets the checks_antag_cap in the proper reference so it will do what it says, not check antag cap when the weight of the event grows past 3. Due to how the event system and game_mode system work there is two different references to the same event. So while the event will use the weight(Not even sure if this is true) to call a lone op into game_mode the game_mode subsystem will use its own reference of lone ops and will not see the change applied from events and its reference. Confusing I know sorry. Either way the proper reference has the flag now properly adjusted so lone ops can now ignore antag caps.
Why It's Good For The Game
I honestly don't know. I guess to really punish Captains who ignore the disk. Was told it was a bug that many were sore about so I fixed it. Fixes to bugs are always good for the game.
Changelog
🆑Siro
fix: Lone ops will now ignore the antag cap if the weight grows beyond 3.
code: Reference to loneops in ssgame_mode now has its checks_antag_cap adjusted due to weight.
/:cl: