save all opponent penalties #1124
Merged
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
schmidma
approved these changes
Jul 10, 2024
oleflb
pushed a commit
to oleflb/hulk
that referenced
this pull request
Jul 15, 2024
oleflb
pushed a commit
that referenced
this pull request
Sep 30, 2024
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.
Why? What?
If the opponent uses player numbers higher than 7 then using those penalties to determine anything won't work.
Right now this means the if they have a sacrificial lamb for the visual referee that has a jersey number higher than 7 we won't see it.
Fixes #
ToDo / Known Issues
Ideas for Next Iterations (Not This PR)
#1021
How to Test
Test standby/ready with opponent team having player numbers higher than 7. MotionInStandby those players. In the current main will not wait to send in our sacrificial NAO.
In the new one we do.