Rename Emergency Stop to Force Timeout#104
Open
guyfleeman wants to merge 2 commits into
Open
Conversation
g3force
reviewed
May 10, 2026
| It is not allowed to damage or modify the field or the ball. | ||
|
|
||
| ==== Unsafe Operations | ||
| It is not allowed to have robot failures that endanger the participants or scpectators. Examples of unsafe operations include, but not limited to: high power or high velocity uncontrolled robot operation, electronics fire, high voltage or visible arc discharge. |
Member
There was a problem hiding this comment.
Suggested change
| It is not allowed to have robot failures that endanger the participants or scpectators. Examples of unsafe operations include, but not limited to: high power or high velocity uncontrolled robot operation, electronics fire, high voltage or visible arc discharge. | |
| It is not allowed to have robot failures that endanger the participants or spectators. Examples of unsafe operations include, but not limited to: high power or high velocity uncontrolled robot operation, electronics fire, high voltage or visible arc discharge. |
what is meant by "high power"? The last sentence seems a bit rough.
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
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.
This sets the stage to rename "Emergency Stop" in the league rules and league software. The league discussed that the name "Emergency Stop" generally doesn't describe what the action does and has negative safety implications.
The event has a 10 second delay and is intended for situations where robots have lost partially lost control or software crashes. These are not emergencies. Neither of these are resolved by a field level e-stop and would still require physical intervention by the team either with the robot or the laptop. Also, the 10 second delay is the exact opposite of the expected behavior of "emergency stop" which is that true emergencies should be addressed without delay.
The action is now named "Force Timeout" (verb) and produces a "Forced Timeout" (noun) game state.
Clarify rules under the "Halt" section, that unsafe behavior by robots (e.g. loss of control, fire, electronics failures like unintended arc emission from kickers) is handled at the discretion of the referee, who may immediately halt the game at any time. The referee may penalize teams for repeated robot behavior that makes him question or conclude safety has been compromised.