---
title: Coral Scoring Adjustments
description: Review this blog to learn about the adjustments that have been made based on an issue related to scoring of coral that we just learned about.
image: https://community.firstinspires.org/hubfs/PXL_20250328_133042212.jpg
---

Earlier this week, members of the *FIRST* Robotics Competition engineering staff became aware of an issue related to scoring of coral that had impacted a few matches this season. Per the scoring criteria for coral (as noted in [Section 6.5.1](https://firstfrc.blob.core.windows.net/frc2025/Manual/2025GameManual.pdf)), a coral scored in Auto must still be scored at the end of the match to receive the Auto points. The issue was that the Field Management System (FMS) was still counting the coral as scored in Auto even if it was removed in Teleop. There are two effects of this; coral scored in Auto, then de-scored during Teleop and not rescored was still being given the Auto points, and the coral was incorrectly counted toward the Coral RP.

First, I want to apologize to all teams for this mistake. We have corrected this issue for the remaining events, including all Week 5 events.

After evaluating all 11,490 qualification and playoff matches played through Week 4 events, we determined the outcome (either match winner or ranking points) of 8 matches would have been changed. We have evaluated those 8 matches and the scoring error’s impact on each team’s Regional and District Points. We will not be making any changes to Regional or District Points for teams who were positively impacted by the error (e.g. we will not be removing points from a ranking change from winning a match that would have been a loss). We have added Regional or District Points for teams who were negatively impacted by the error. The matches, impacted teams, implications of the error, and associated Regional Points and District Points adjustments are in the table below.

I sincerely apologize again for this error. I’m thankful for the volunteers who alerted us to this issue and the engineering team for putting in the work required to fix the issue and evaluate the impact so that we could fix it.

Adjustments to District Points show up on the District Rankings pages in the “Other” column. Regional Points show up as “Points Adjustments” next to the “Tiebreakers” section for each team.

| **Event & Match** | **Impacted Teams** | **Impact of Error** | **Regional/District Points Adjustment** |
| --- | --- | --- | --- |
| TXWAC, Playoff 13 | Blue: 3310, 2881, 5212, 2950 Red: 2689, 2158, 6672 | Change winner from blue to red alliance. | Red had 7 District Points already assigned to them prior to the discovery of this error. There was a previously identified scoring issue on the red alliance Reef in this match. As a result, no additional points are awarded. |
| CAVE, Playoff 3 | Blue: 971, 4079, 589 Red: 5026, 6060, 3863 | Change winner from blue to red alliance. | No change. This match occurred at a point in the Playoff tournament where no Playoff Performance points are awarded. |
| MOSL, Q16 | Blue: 554, 5583, 2506 Red: 1706, 1329, 4330 | Red should not have received Coral Ranking Point | +1 Regional Point (4500, 4329, 7472) |
| MSLR, Q41 | Blue: 6017, 1912, 9734 Red: 2183, 9503, 456 | Change winner from red to blue | +2 Regional Points (6017) +1 Regional Point (1912, 9734, 8044, 2221, 1421, 10446) |
| CODE, Q62 | Blue: 1822, 4068, 1056 Red: 7485, 3648, 4418 | Change winner from red to blue | +2 Regional Points (1056) +1 Regional Point (3284, 9068, 2036, 159) |
| NCGRE, Q26 | Blue: 9297, 4534, 10072 Red: 8746, 2642, 6240 | Change winner from blue to red | +2 District Points (2642) +1 District Point (8746, 4828, 4829, 2059, 9789, 6240) |
| ORWIL, Q55 | Blue: 9567, 9430, 4043 Red: 5975, 5468, 997 | Change winner from red to blue | +2 District Points (9567) +1 District Point (1425. 9430, 9600, 4043) |
| TXHOU, Q50 | Blue: 10118, 8515, 2585 Red: 4597, 7691, 10014 | Change winner from blue to red | +3 District Points (7691) +2 District Points (4597) +1 District Point (9658, 5261, 10014, 9517) |

 

** [FRC](https://community.firstinspires.org/topic/frc)

#### Share it:

[** ](https://www.facebook.com/sharer/sharer.php?u=https://community.firstinspires.org/coral-scoring-adjustments) [** ](https://twitter.com/share?url=https://community.firstinspires.org/coral-scoring-adjustments) [** ](http://www.linkedin.com/shareArticle?mini=true&url=https://community.firstinspires.org/coral-scoring-adjustments)

![Default Author Image](https://community.firstinspires.org/hubfs/Community%20Blog%20v2/images/FIRST-author-icon.svg)

Author

[Collin Fultz, Senior Director, FIRST Robotics Competition](https://community.firstinspires.org/author/collin-fultz-senior-director-first-robotics-competition)

### Related Posts

<https://community.firstinspires.org/2025-regional-advancement-updates-for-2026>

** [Championship](https://community.firstinspires.org/topic/championship), [FRC](https://community.firstinspires.org/topic/frc)

Regional Advancement Updates for the 2026 Season

August 27, 2025

<https://community.firstinspires.org/advancement-to-the-2025-first-championship>

** [FRC](https://community.firstinspires.org/topic/frc)

Advancement to the 2025 FIRST Championship

December 16, 2024

<https://community.firstinspires.org/2022-priority-waitlist-slot-releases>

** [FRC](https://community.firstinspires.org/topic/frc)

Priority Waitlist Slot Releases

March 18, 2022

![](https://www.facebook.com/tr?id=1200203950045814&ev=PageView&noscript=1) ![](https://ct.pinterest.com/v3/?tid=2615041699514&noscript=1) ![](https://ct.pinterest.com/v3/?tid=2615041699514&event=PageVisit&noscript=1)