# content
G420       *This is not combat robotics. A ROBOT may not deliberately functionally impair an opponent ROBOT. Damage or functional impairment because of contact with a tipped-over or DISABLED opponent ROBOT, which is not perceived by a REFEREE to be deliberate, is not a violation of this rule.

Violation: MAJOR FOUL and YELLOW CARD. MAJOR FOUL and RED CARD if opponent ROBOT is unable to drive.

FIRST Tech Challenge can be a high-contact competition and may include rigorous gameplay. While this rule aims to limit severe damage to ROBOTS, teams should design their ROBOTS to be robust. Teams are expected to act responsibly.

An example of a violation of this rule includes, but is not limited to:

A.      A ROBOT high-speed rams and/or REPEATEDLY smashes an opponent ROBOT and causes damage. The REFEREE infers that the ROBOT was deliberately trying to damage the opponents ROBOT.

Examples of functionally impairing another ROBOT include, but are not limited to:

B.      disconnecting wires for operation of a component inside the ROBOT CHASSIS.

C.      disconnecting the opponent ROBOTS battery (this example also clearly results in a RED CARD because the ROBOT is no longer able to drive).

D.      powering off an opponents ROBOT using their reasonably well-protected power switch (This example also clearly results in a RED CARD because the ROBOT is no longer able to drive).

Teams should mount their main power switch so it is protected per R609. A team that mounts their ROBOTS power switch in an exposed location puts themselves at high risk of incidental contact. Powering off an opponents ROBOT by their exposed power switch during normal interactive gameplay will be considered incidental and not deliberate.

At the conclusion of the MATCH, the Head REFEREE may elect to visually inspect a ROBOT to confirm violations of this rule made during a MATCH and remove the violation if the damage cannot be verified.

"Unable to drive" means that because of the incident, the DRIVER can no longer drive to a desired location in a reasonable time (generally). For example, if a ROBOT can only move in circles, or can only move extremely slowly, the ROBOT is considered unable to drive.

# contentMap.en
G420       *This is not combat robotics. A ROBOT may not deliberately functionally impair an opponent ROBOT. Damage or functional impairment because of contact with a tipped-over or DISABLED opponent ROBOT, which is not perceived by a REFEREE to be deliberate, is not a violation of this rule.

Violation: MAJOR FOUL and YELLOW CARD. MAJOR FOUL and RED CARD if opponent ROBOT is unable to drive.

FIRST Tech Challenge can be a high-contact competition and may include rigorous gameplay. While this rule aims to limit severe damage to ROBOTS, teams should design their ROBOTS to be robust. Teams are expected to act responsibly.

An example of a violation of this rule includes, but is not limited to:

A.      A ROBOT high-speed rams and/or REPEATEDLY smashes an opponent ROBOT and causes damage. The REFEREE infers that the ROBOT was deliberately trying to damage the opponents ROBOT.

Examples of functionally impairing another ROBOT include, but are not limited to:

B.      disconnecting wires for operation of a component inside the ROBOT CHASSIS.

C.      disconnecting the opponent ROBOTS battery (this example also clearly results in a RED CARD because the ROBOT is no longer able to drive).

D.      powering off an opponents ROBOT using their reasonably well-protected power switch (This example also clearly results in a RED CARD because the ROBOT is no longer able to drive).

Teams should mount their main power switch so it is protected per R609. A team that mounts their ROBOTS power switch in an exposed location puts themselves at high risk of incidental contact. Powering off an opponents ROBOT by their exposed power switch during normal interactive gameplay will be considered incidental and not deliberate.

At the conclusion of the MATCH, the Head REFEREE may elect to visually inspect a ROBOT to confirm violations of this rule made during a MATCH and remove the violation if the damage cannot be verified.

"Unable to drive" means that because of the incident, the DRIVER can no longer drive to a desired location in a reasonable time (generally). For example, if a ROBOT can only move in circles, or can only move extremely slowly, the ROBOT is considered unable to drive.