Skip to main content
Skip to Main Content
Skip to main content
Navigation

Chapter 7: Violations, Penalties, and Documentation


Lesson 2: Score Affecting Decisions

Learning Objectives:

  • Define what it means for a violation to be Score Affecting.
  • Determine whether a violation improved the alliance's score at the end of a match.
  • Explain how multiple violations can cumulatively become Score Affecting.
  • Explain why every Score Affecting violation is, by default, a Major Violation.

After you identify a violation, one question often decides everything that follows: was it Score Affecting? That single judgment usually determines whether a violation is Minor or Major, because — unless a rule says otherwise — every Score Affecting violation is a Major Violation. The good news is that the test is simpler than it sounds, and it always comes down to one idea: did the violation improve the alliance's score?

It is fair to wonder why this matters in a cooperative game. There is no opposing alliance on the field to be harmed, but there is an opponent in a broader sense: every other team at the event. Teams are ranked by their Qualification Match scores, so a score inflated by a violation is unfair to every team it leapfrogs in the standings. Score Affecting decisions are how you protect that fairness.

Before continuing, review Appendix D in the current Game Manual. This section defines Score Affecting and includes specific details about violations by rule.


What Score Affecting Means

A violation is Score Affecting if it improved the alliance's score at the end of the match. The definition points at the score, not the severity of the action. A robot that expands beyond its legal limit but gains nothing from it broke a rule, but it did not improve the score, so the violation was not Score Affecting, and is very likely a Minor Violation.

Making the Determination

Two habits keep this decision clean:

  • Wait for the final score. Whether a violation was Score Affecting can only be determined once the match is complete and the scores have been calculated. You may note a violation the moment it happens, but the classification waits for the math.
  • Focus on robot actions directly related to the violation. The check is whether the violation directly contributed to increasing the alliance’s score. If it did not increase the score, then the violation was not Score Affecting, and it was very likely a Minor Violation.

An example helps make the difference clear. A Bean Bag was introduced illegally by a Loader. If that Bean Bag ended up scored on any Goal, the violation directly contributed points — it was Score Affecting. If the same Bean Bag came to rest on the field and never scored, the alliance gained nothing from the violation, and it stays Minor.

Notice that intent plays no role in this determination. A nervous eight-year-old and a seasoned middle schooler who commit the same violation with the same result on the score receive the same classification. The math is the math — which is actually good news for you, because it means one of the hardest-feeling calls in refereeing is not a judgment of character. Where the rules extend grace, they do it explicitly, as you will see below.

Cumulative Violations

Multiple violations within a match can cumulatively become Score Affecting. Each instance might add only a little on its own, but if together they improved the alliance's score, the violations are Score Affecting as a group. Three illegally introduced Bean Bags that each get scored are not necessarily three harmless moments — they are a set of violations that could have collectively raised the score.


Why Score Affecting Means Major — and When It Doesn't

By default, a Score Affecting violation is a Major Violation, which results in a Disqualification (covered in Lesson 3). The logic follows directly from fairness: if a violation improves the score, the score cannot stand as earned.

The default has exceptions, and they only apply when a rule states them. The clearest example is in the <SG7> violation notes: most Loader violations are expected to be accidental, so the first accidental Score Affecting occurrence in a Qualification Match may be treated as a Minor Violation and a "final notice" that any future violation will result in a Disqualification for the match. In a Finals Match, however, any Score Affecting <SG7> violation — accidental or not — must be treated as a Major Violation.

This is worth pausing on, because it captures how the benefit of the doubt works in VEX IQ. The generosity is written into the rules themselves. You apply it exactly where the Game Manual grants it, consistently for every team. Giving students the grace the manual provides is good refereeing, however inventing grace not provided by the manual is unfair to every other team at the event.