Robotics Education & Competition Foundation
Inspiring students, one robot at a time.

This Q&A is Read Only.

Official Q&A: VRC 2023-2024: Over Under

Usage Guidelines All Questions

<SG6> sections 2a/2b violation - how to determine if match affecting


Andrei Achim
15-Dec-2023

Relevant passages from the General Definitions section of the game manual:

Minor Violation – A Violation which does not result in a Disqualification.

Accidental, momentary, or otherwise non Match Affecting Violations are usually Minor Violations.

Major Violation – A Violation which results in a Disqualification.

Unless otherwise noted in a rule, all Match Affecting Violations are Major Violations. Match Affecting – A Violation which changes the winning and losing Alliance in the Match.

When evaluating if a Violation was Match Affecting, Head Referees will focus primarily on any Robot actions that were directly related to the Violation.

Relevant rule:

<SG6> refers to the conditions required to safely introduce Match Load Triballs. Specifically:

Section 2a. states that

The Robot must be contacting the Match Load Zone or the Match Load Bar

Section 2b. states that

Momentarily / accidentally losing contact with the Match Load Zone or Match Load Bar is permissible, provided that the Robot is still “breaking the plane” of the inside edge of the Match Load Bar.

Scenario 1: Red team matchloads. Robot moves accidentally and a triball is loaded illegally, violating <SG6> sections 2a/2b. This is clearly not egregious or intentional, so head ref issues a verbal warning and records it as a minor violation. Team acknowledges and makes sure to not repeat the violation. Match is scored and Red wins by 1 point. Team claims their illegally loaded triball was shot and ended in the opponent's load zone so it scored 0 points. Refs did not see as they stayed focused on the robot actions. Is this match affecting and should Red be DQ-ed?

Scenario 2: Red team matchloads. Robot moves accidentally and a triball is loaded illegally, violating <SG6> sections 2a/2b. This is clearly not egregious or intentional, so head ref issues a verbal warning and records it as a minor violation. Team acknowledges and makes sure to not repeat the violation. Match is scored and Red wins by 4 points. Nobody can say with certainty where the illegally loaded triball ended. Is this match affecting and should Red be DQ-ed?

Online discussions have revealed that most EPs and refs agree that it is not realistically feasible to monitor where match loaded triballs end due to the very dynamic nature of the game and amount of game elements and that some people consider this to be an automatic 2 point infraction and some an automatic 5 point infraction (with some interesting in between ideas) for the purpose of deciding whether match affecting or not.

The intent of this question is to understand clearly and without ambiguity how to make a fair call in these scenarios.

Thank you!

Answered by committee
18-Jan-2024

Online discussions have revealed that most EPs and refs agree that it is not realistically feasible to monitor where match loaded triballs end due to the very dynamic nature of the game and amount of game elements and that some people consider this to be an automatic 2 point infraction and some an automatic 5 point infraction (with some interesting in between ideas) for the purpose of deciding whether match affecting or not.

Depending on the context and resources available at a given event, we agree that this may be handled slightly differently from event to event at the discretion of the Head Referee. Any of the following outcomes would be acceptable:

  • Attempting to track the final location(s) of any illegally loaded Triballs.
  • Assigning a specific "Match Affecting" point value to each Triball, as described above.
  • Counting each illegal load as a Minor Violation, and setting a consistent guideline within a given event for how many repeated Minor Violations will result in escalation to a Major Violation.

When setting standards such as these within a given event, they should be presented to all Teams, e.g. during a Driver's Meeting. With that being said, we will work to provide more specific guidance on this topic in an upcoming Game Manual update.