This Q&A is now read-only
Official Q&A: VRC 2020-2021: Change Up
713: Tetherbot Tipping
See the previous question regarding the definition of a "tetherbot".
If a robot on the opposing alliance tips over part of a tetherbot, but other parts are still upright, should the opposing robot be penalized for tipping?
Note that the game manual does not contain a definition for tipping. However, rule G12 says:
Don’t destroy other Robots. But, be prepared to encounter defense. Strategies aimed solely at the destruction, damage, tipping over, or Entanglement of opposing Robots are not part of the ethos of the VEX Robotics Competition and are not allowed. If the tipping, Entanglement, or damage is ruled to be intentional or egregious, the offending Team may be Disqualified from that Match. Repeated offenses could result in Disqualification from the entirety of the competition.
...
Note: A Robot which has expanded horizontally in an effort to obstruct the field, or is legally coveringt he top of a Goal in a solely defensive manner, should expect vigorous interactions from opponent Robots. Damage that is caused by opponent Robots pushing, tipping, or Entangling with them would not be considered a violation of G12. Gratuitous damage or dangerous mechanisms may still be considered a violation of R4, S1, G1 or at the Head Referee’s discretion.
As long as the tetherbot is not using itself to obstruct parts of the field, then opposing robots that tip any part of a tetherbot would be in violation of G12. Correct?
It is impossible to provide a blanket ruling that would cover all hypothetical Robot designs and Match contexts. However, a Robot with multiple moving mechanisms should always still be considered one Robot, regardless of how independently moving the separate mechanisms are. This overarching mentality should be kept in mind throughout the following answers.
Note that the game manual does not contain a definition for tipping.
When a VRC-specific definition is not available, a dictionary definition should be used. Merriam Webster defines "tip over" as the following:
: to fall over or to cause (something) to fall over
// He accidentally tipped the lamp over and broke it.
"Tipped over" generally implies that a Robot (or lamp) has been moved from an upright and functional position, to a fallen and non-functional position.
Thus, if a Robot with multiple moving mechanisms has had one mechanism disabled due to falling over, but still has other mechanisms which are upright and able to play the game, then the whole Robot has not been "tipped over".
With that being said, it is still likely that the sub-mechanism was disabled due to an intentional and/or egregious strategic maneuver, and should be treated the same as if an intake or drivetrain was damaged or disabled, i.e. under G12.
As long as the tetherbot is not using itself to obstruct parts of the field, then opposing robots that tip any part of a tetherbot would be in violation of G12. Correct?
The intent of the quoted Note in G12 is to provide a specific application of G13, which states that "Offensive Robots get the 'benefit of the doubt'." A "wall-bot" is a defensive Robot, and is not protected by G12. A Robot which has expanded horizontally in an offensive manner would be protected by G12, whether that expansion contains independently moving sub-parts, or just very large Robot arms.
As always, bear in mind that "tipping over" is not an immediate violation of G12, regardless of the Robot's expansion. Points (b) and (c) of G12 must always be taken into consideration by the Head Referee, which is why it is impossible to provide a blanket answer that would cover all hypothetical scenarios.
b. VEX Robotics Competition Change Up is an interactive game. Some incidental tipping, Entanglement, and damage may occur as a part of normal gameplay without violation. It will be up to the Head Referee’s discretion whether the interaction was incidental or intentional.
c. A Team is responsible for the actions of its Robot at all times, including the Autonomous Period. This applies both to Teams that are driving recklessly or potentially causing damage, and to Teams that drive around with a small wheel base. A Team should design its Robot such that it is not easily tipped over or damaged by minor contact.