# content
G416       *This isn’t combat robotics. A ROBOT may not intentionally and/or recklessly damage or functionally impair an opponent ROBOT.

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

The intent of this rule is to cover situations where a ROBOT intentionally and/or recklessly, as perceived by the REFEREE, damages another ROBOT anywhere on the FIELD.

Situations where a REFEREE is likely to infer are intentional and would be a violation if they caused damage include, but are not limited to:

A.      A ROBOT REPEATEDLY smashing into an opponent ROBOT intake.

B.      A ROBOT REPEATEDLY hitting another ROBOT with their extension.

Examples that would be reckless and would be a violation if they cause damage, include, but are not limited to:

C.      A ROBOT driving at high speed, across the FIELD, rams into an opponent ROBOT with their extension.

D.      A ROBOT rams into an opponent with their extension REPEATEDLY.

E.      A ROBOT violently driving into an opponent that is already firmly against a FIELD element.

Examples that are not reckless include, but are not limited to:

F.      A ROBOT making REPEATED BUMPER to BUMPER contact with an opponent.

G.     A ROBOT driving at high speed makes BUMPER to BUMPER contact with an opponent.

H.     A red ROBOT is driving around and picking up FUEL in the NEUTRAL ZONE with an extension out. Blue ROBOT is playing defense and moves into their path at the last second resulting in a collision. The red ROBOT is not considered reckless and there is no call because the red ROBOT did not have an opportunity to avoid the contact.

I.        A red ROBOT is travelling slowly and picking up FUEL in the NEUTRAL ZONE with an extension out. A blue ROBOT races towards the red ROBOT such that the red ROBOT’s extension contacts the blue ROBOT causing damage. The red ROBOT is not considered reckless and there is no call because the blue ROBOT initiated the contact because the blue ROBOT was travelling much faster.

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, for approximately ~20+ seconds, 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.

Due to the prevalence of FUEL around the FIELD during gameplay, it is highly unlikely that a REFEREE could determine if an interaction causing an opponent ROBOT to be “beached” on FUEL is intentional versus regular defensive play.

# contentMap.en
G416       *This isn’t combat robotics. A ROBOT may not intentionally and/or recklessly damage or functionally impair an opponent ROBOT.

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

The intent of this rule is to cover situations where a ROBOT intentionally and/or recklessly, as perceived by the REFEREE, damages another ROBOT anywhere on the FIELD.

Situations where a REFEREE is likely to infer are intentional and would be a violation if they caused damage include, but are not limited to:

A.      A ROBOT REPEATEDLY smashing into an opponent ROBOT intake.

B.      A ROBOT REPEATEDLY hitting another ROBOT with their extension.

Examples that would be reckless and would be a violation if they cause damage, include, but are not limited to:

C.      A ROBOT driving at high speed, across the FIELD, rams into an opponent ROBOT with their extension.

D.      A ROBOT rams into an opponent with their extension REPEATEDLY.

E.      A ROBOT violently driving into an opponent that is already firmly against a FIELD element.

Examples that are not reckless include, but are not limited to:

F.      A ROBOT making REPEATED BUMPER to BUMPER contact with an opponent.

G.     A ROBOT driving at high speed makes BUMPER to BUMPER contact with an opponent.

H.     A red ROBOT is driving around and picking up FUEL in the NEUTRAL ZONE with an extension out. Blue ROBOT is playing defense and moves into their path at the last second resulting in a collision. The red ROBOT is not considered reckless and there is no call because the red ROBOT did not have an opportunity to avoid the contact.

I.        A red ROBOT is travelling slowly and picking up FUEL in the NEUTRAL ZONE with an extension out. A blue ROBOT races towards the red ROBOT such that the red ROBOT’s extension contacts the blue ROBOT causing damage. The red ROBOT is not considered reckless and there is no call because the blue ROBOT initiated the contact because the blue ROBOT was travelling much faster.

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, for approximately ~20+ seconds, 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.

Due to the prevalence of FUEL around the FIELD during gameplay, it is highly unlikely that a REFEREE could determine if an interaction causing an opponent ROBOT to be “beached” on FUEL is intentional versus regular defensive play.