Implement timeout counters for each team #14
Conversation
This file contains hidden or 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
DarkView
reviewed
Oct 16, 2025
…k `timeoutState.timeRemaining` rather than creating new timeouts
DarkView
reviewed
Oct 17, 2025
DarkView
reviewed
Oct 23, 2025
Member
DarkView
left a comment
DarkView
left a comment
There was a problem hiding this comment.
Please also add the new timeout things from Tools to the replayplayer (running yarn run build should tell you there's an issue)
…lly ending timeouts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The initial number of timeouts is two, with one added during the first round of overtime (at a maximum of two). Safeguard is in place to only remove a timeout if the keybind is not pressed again within ten seconds of initial activation.