<SG9> Alliance Goals are protected
Embedded Files
3249: <SG9>, <SG10>, and Descoring an Alliance's Own Alliance Goal
Robots may remove any Scoring Objects from their own Alliance-colored Goal.
Red Robots may remove objects from Red Alliance Goals, and Blue Robots may remove objects from Blue Alliance Goals.
This is allowed regardless of the Pin’s color or Ownership.
Therefore, in the example, the Blue Robot may strategically remove four or more Pins from its own Blue Alliance Goal without violating <SG9>.
<SG9> only protects the opposing Alliance’s Goal, while <SG10> applies to Neutral Goals.
Your own Alliance Goal: You may remove any Scoring Objects, including those owned by the opposing Alliance.
The opposing Alliance’s Goal: You may not interact with it directly or indirectly
<SG10> Placed Scoring Objects may not be removed from neutral Goals via direct or indirect interactions.
1. Removing Pins from a Neutral Goal may still violate rule <SG10>, even if the Pins belong to your own Alliance.
2. The color of the Pins and which Alliance scored them do not matter when determining a violation.
3. Pins are counted as whole objects, not as individual Pin Halves.
4. The 10–50 point values are only used to determine whether a violation is Match Affecting. These points are not actually deducted from the Alliance's score.
5. Accidentally knocking Pins off a Neutral Goal does not automatically result in Disqualification. The penalty depends on whether the violation is Match Affecting and other relevant circumstances.
Q&A 3233 - Match Affecting calculations when both Alliances commit Violations
Simultaneous Calculation: When both Alliances violate SG10, violation values must be applied to both Alliances simultaneously before determining whether the violations are Match Affecting.
No Actual Score Deduction: The calculated values are only used to assess violations. Official Match scores remain unchanged.
Same Winner = Minor Violations: If the simulated calculations do not change the winning Alliance, both violations are considered Minor Violations under the conditions described in the Q&A.
Winner Changes = Disqualification: If the simulated calculations reverse the winning Alliance, the Alliance whose violation affected the result in its favor receives a Match Affecting Violation and is Disqualified.
Simulated Tie = Both Alliances Disqualified: If the simulated scores result in a tie, both Alliances receive Match Affecting Violations and are Disqualified.
1. Violation Values Stack, Not Pin Counts: When multiple SG10 violations occur, the penalty values from each separate interaction are added together, rather than combining the total number of Pins removed.
2. Same Robot, Multiple Violations: If the same Robot commits multiple SG10 violations, the violation values accumulate, even if they occur at different Neutral Goals.
3. Qualification Matches: Violations are evaluated separately for each Robot. Penalty values are not combined across Robots within the same Alliance.
4. Elimination Matches: Violations committed by both Robots on the same Alliance are combined. If the total is Match Affecting, the entire Alliance receives a Disqualification (DQ).
5. Match Affecting Violations: If the accumulated violation value is sufficient to change the Match outcome, the violation is considered Match Affecting and results in a Major Violation (DQ).
6. No Actual Score Deduction: These penalty values are only used to determine whether violations are Match Affecting. They are not deducted from the official Match scores.
Failed Scoring Attempts: Newly placed Scoring Objects that fall during an unsuccessful placement attempt do not violate SG10.
Previously Placed Objects: Knocking off Scoring Objects that were already Placed on a Neutral Goal violates SG10.
Key Distinction: Referees must distinguish between an unsuccessful scoring attempt and removing previously Placed objects.
<SG11> Drive Team Members may only introduce Match Loads to the Field through Loaders,
a. Drive Team Members may introduce Match Loads through their Alliance-colored Loaders, and may operate (raise/lower) those Loaders, only during the Driver Controlled Period of the Match.
b. Match Loads may only be introduced by placing or dropping them through the top or back of a Loader, either separately or nested together.
c. Match Loads may have momentary, simultaneous contact with both a Drive Team Member and a Robot as the Match Load is introduced, prior to being released by the Drive Team Member. Once a Match Load has been released, it may no longer be contacted by a Drive Team Member.
d. Match Loads may only be removed through the bottom opening of the Loader, and only by Robots.
Page updated
Report abuse