Skip to content

Lone Op's Antag Cap Fix #5735

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

Merged
merged 4 commits into from
Mar 3, 2025
Merged

Lone Op's Antag Cap Fix #5735

merged 4 commits into from
Mar 3, 2025

Conversation

Coll6
Copy link
Contributor

@Coll6 Coll6 commented Mar 1, 2025

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:

@Coll6 Coll6 changed the title Lone Op Cap Fix Lone Op's Antag Cap Fix Mar 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code: Fix fix da bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants